User equipment, base station and method for activating and releasing authorization for multiple configurations
Patent Information
- Application Number
- CN202080073261.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2019-11-07
- Filing Date
- 2020-10-27
- Publication Date
- 2024-11-05
- Estimated Expiration
- 2040-10-27
AI Technical Summary
然而,所使用的通信结构可能仅提供有限的灵活性和/或效率
Smart Images

Figure CN114600406B_ABST
Abstract
Description
Technical Field
[0001] The present disclosure generally relates to communication systems. More specifically, the present disclosure relates to new signaling, procedures, user equipment (UE) and base stations for authorization of multiple active configurations. Background Art
[0002] To meet consumer demands and improve portability and convenience, wireless communication devices have become smaller and more powerful. Consumers have become dependent on wireless communication devices and expect reliable service, expanded coverage areas, and enhanced functionality. A wireless communication system may provide communication for multiple wireless communication devices, each of which may be served by a base station. A base station may be a device that communicates with a wireless communication device.
[0003] With the development of wireless communication equipment, people have been seeking ways to improve communication capacity, speed, flexibility and / or efficiency. However, improving communication capacity, speed, flexibility and / or efficiency may bring certain problems.
[0004] For example, a wireless communication device may communicate with one or more devices using a communication structure. However, the communication structure used may only provide limited flexibility and / or efficiency. As shown in this discussion, systems and methods for improving communication flexibility and / or efficiency may be advantageous. Summary of the invention
[0005] In one example, a user equipment (UE) communicating with a base station device includes: a receiving circuit configured to receive a hybrid automatic repeat request (HARQ) process number (HPN), wherein the HPN indicates a grant (CG) configuration of one or more configurations that are activated and / or released / deactivated; and a processing circuit configured to activate and / or release / deactivate one or more CG configurations based on the HPN.
[0006] In one example, a base station device that communicates with a user equipment (UE) includes: a processing circuit configured to activate and / or release / deactivate one or more configured grant (CG) configurations; and a transmission circuit configured to transmit a hybrid automatic repeat request (HARQ) process number (HPN), wherein the HPN indicates the one or more CG configurations that are activated and / or released / deactivated.
[0007] In one example, a communication method for a user equipment (UE) communicating with a base station device includes: receiving a hybrid automatic repeat request (HARQ) process number (HPN), wherein the HPN indicates a grant (CG) configuration of one or more configurations that are activated and / or released / deactivated; and activating and / or releasing / deactivating one or more CG configurations based on the HPN.
[0008] In one example, a communication method of a base station device that communicates with a user equipment (UE) includes: activating and / or releasing / deactivating one or more configured grant (CG) configurations; and transmitting a hybrid automatic repeat request (HARQ) process number (HPN), wherein the HPN indicates the one or more CG configurations that are activated and / or released / deactivated. BRIEF DESCRIPTION OF THE DRAWINGS
[0009] [ Figure 1 ] Figure 1 is a block diagram illustrating one specific implementation of one or more base station devices (gNBs) and one or more user equipment (UEs) in which systems and methods for activation and / or release / deactivation may be implemented.
[0010] [ Figure 2 ] Figure 2 Examples of multiple parameters are shown.
[0011] [ Figure 3 ] Figure 3 is a diagram showing one example of a resource grid and resource blocks.
[0012] [ Figure 4 ] Figure 4 An example of a resource area is shown.
[0013] [ Figure 5 ] Figure 5 An example of UL transmission corresponding to a configured grant is shown.
[0014] [ Figure 6 ] Figure 6 An example of a configured authorization confirmation medium access control (MAC) control element (CE) is shown.
[0015] [ Figure 7 ] Figure 7 Various components that may be utilized in a UE are shown.
[0016] [ Figure 8 ] Figure 8 Various components that may be utilized in a gNB are shown.
[0017] [ Fig. 9 ] Fig. 9 is a block diagram illustrating one embodiment of a UE in which one or more of the systems and / or methods described herein may be implemented.
[0018] [ Fig.10 ] Fig.10 is a block diagram illustrating one specific implementation of a gNB in which one or more of the systems and / or methods described herein may be implemented.
[0019] [ Fig.11 ] Fig.11 is a block diagram illustrating a specific implementation of a gNB.
[0020] [ Fig.12 ] Fig.12 is a block diagram illustrating a specific implementation of a UE. DETAILED DESCRIPTION
[0021] A user equipment (UE) communicating with a base station apparatus is described. The UE includes a receiving circuit configured to receive a hybrid automatic repeat request (HARQ) process number (HPN). The HPN indicates one or more configured grant (CG) configurations that are activated and / or released / deactivated. The UE also includes a processing circuit configured to activate and / or release / deactivate one or more CG configurations based on the HPN.
[0022] A base station apparatus for communicating with a user equipment (UE) is also described. The base station apparatus includes processing circuitry configured to activate and / or release / deactivate one or more configured grant (CG) configurations. The base station apparatus also includes transmission circuitry configured to transmit a hybrid automatic repeat request (HARQ) process number (HPN). The HPN indicates the one or more CG configurations that are activated and / or released / deactivated.
[0023] A communication method for a user equipment (UE) communicating with a base station apparatus is also described. The method includes receiving a hybrid automatic repeat request (HARQ) process number (HPN). The HPN indicates one or more configured grant (CG) configurations to be activated and / or released / deactivated. The method also includes activating and / or releasing / deactivating one or more CG configurations based on the HPN.
[0024] A communication method of a base station apparatus communicating with a user equipment (UE) is also described. The method includes activating and / or releasing / deactivating one or more configured grant (CG) configurations. The method also includes transmitting a hybrid automatic repeat request (HARQ) process number (HPN). The HPN indicates the one or more CG configurations that are activated and / or released / deactivated.
[0025] The 3rd Generation Partnership Project (also known as "3GPP") is a collaborative agreement that develops globally applicable technical specifications and technical reports for third and fourth generation wireless communication systems. 3GPP develops specifications for next generation mobile networks, systems and devices.
[0026] 3GPP Long Term Evolution (LTE) is the name given to a project to improve the Universal Mobile Telecommunications System (UMTS) mobile phone or device standard to cope with future requirements. 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).
[0027] At least some aspects of the systems and methods disclosed herein may be described in conjunction with 3GPP LTE, Advanced LTE (LTE-A), and other standards (e.g., 3GPP Releases 8, 9, 10, 11, 12, 13, 14, and / or 15). However, the scope of the present disclosure should not be limited in this regard. At least some aspects of the systems and methods disclosed herein may be used in other types of wireless communication systems.
[0028] A wireless communication device may be an electronic device that is used to transmit voice and / or data to a base station, which in turn may communicate with a network of devices (e.g., a public switched telephone network (PSTN), the Internet, etc.). When describing the systems and methods herein, a wireless communication device may alternatively be referred to as a mobile station, UE, access terminal, subscriber station, mobile terminal, remote station, user terminal, terminal, subscriber unit, mobile device, etc. Examples of wireless communication devices include cellular phones, smart phones, personal digital assistants (PDAs), laptop computers, netbooks, e-readers, wireless modems, etc. In the 3GPP specification, a wireless communication device is generally referred to as a UE. However, since the scope of the present disclosure should not be limited to the 3GPP standard, the terms "UE" and "wireless communication device" are used interchangeably herein to represent the more general term "wireless communication device". UE may also be more generally referred to as a terminal device.
[0029] In the 3GPP specifications, a base station is often referred to as a Node B, an evolved Node B (eNB), a home enhanced or evolved Node B (HeNB), or some other similar term. Since the scope of the present disclosure should not be limited to the 3GPP standards, the terms "base station", "Node B", "eNB", "gNB", and "HeNB" may be used interchangeably herein to represent the more general term "base station". In addition, the term "base station" may be used to represent an access point. An access point may be an electronic device that provides wireless communication devices with access to a network (e.g., a local area network (LAN), the Internet, etc.). The term "communication device" may be used to represent a wireless communication device and / or a base station. An eNB may also be more generally referred to as a base station device.
[0030] It should be noted that, as used herein, a "cell" may be any communication channel that is specified by a standardization or regulatory body for use with International Mobile Telecommunications-Advanced (IMT-Advanced) and all or a subset thereof, so that it is adopted by 3GPP as an authorized band (e.g., frequency band) for communication between an eNB and a UE. It should also be noted that in the E-UTRA and E-UTRAN general description, as used herein, a "cell" may be defined (e.g., specified) as "a combination of downlink resources and optional uplink resources". The link between the carrier frequency of the downlink resources and the carrier frequency of the uplink resources may be indicated in system information transmitted on the downlink resources.
[0031] The fifth generation communication system, referred to as NR (New Radio Technology) by 3GPP, envisions the use of time, frequency and / or space resources to enable services such as eMBB (enhanced mobile broadband) communication, URLLC (ultra-reliable and low latency communication) and MMTC (massive machine type communication). Also, in NR, one or more bandwidth parts (BWPs) in a serving cell and / or one or more serving cells may be designated (e.g., configured) for transmission of different services. A user equipment (UE) may receive downlink signals and / or transmit uplink signals in the BWPs of one and / or multiple serving cells.
[0032] In order for the service to use time, frequency and / or space resources efficiently, it would be useful to be able to effectively control downlink and / or uplink transmissions. Therefore, a process for effectively controlling downlink and / or uplink transmissions should be designed. Therefore, a detailed design of the process for downlink and / or uplink transmissions may be beneficial. In order to meet delay targets and provide high reliability, mini-slot based repetitions with flexible transmission timings may be supported. This article describes some methods for applying mini-slot based repetitions.
[0033] Various examples of the systems and methods disclosed herein will now be described with reference to the accompanying drawings, wherein like reference numerals may indicate functionally similar elements. The systems and methods as generally described and illustrated in the drawings herein can be arranged and designed in a variety of different specific implementations. Therefore, the following more detailed description of several specific implementations presented in the drawings is not intended to limit the scope of the claims, but is merely representative of the systems and methods.
[0034] Figure 11 is a block diagram illustrating one implementation of one or more gNBs 160 and one or more UEs 102 in which systems and methods for activation and / or release / deactivation may be implemented. The one or more UEs 102 communicate with the one or more gNBs 160 using one or more physical antennas 122a-n. For example, the UE 102 transmits electromagnetic signals to the gNB 160 and receives electromagnetic signals from the gNB 160 using the one or more physical antennas 122a-n. The gNB 160 communicates with the UE 102 using one or more physical antennas 180a-n. In some implementations, the terms “base station,” “eNB,” and / or “gNB” may refer to and / or be replaced by the term “transmission reception point (TRP).” For example, in some implementations, in conjunction with Figure 1 The gNB 160 described may be a TRP.
[0035] The UE 102 and the gNB 160 may communicate with each other using one or more channels and / or one or more signals 119, 121. For example, the UE 102 may transmit information or data to the gNB 160 using one or more uplink channels 121. Examples of uplink channels 121 include physical shared channels (e.g., PUSCH (Physical Uplink Shared Channel)) and / or physical control channels (e.g., PUCCH (Physical Uplink Control Channel)), etc. For example, the one or more gNBs 160 may also transmit information or data to the one or more UEs 102 using one or more downlink channels 119. Examples of downlink channels 119 include physical shared channels (e.g., PDSCH (Physical Downlink Shared Channel)) and / or physical control channels (PDCCH (Physical Downlink Control Channel)), etc.). Other types of channels and / or signals may be used.
[0036] Each of the one or more UEs 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 paths and / or transmit paths may be implemented in the UE 102. For convenience, only a single transceiver 118, decoder 108, demodulator 114, encoder 150, and modulator 154 are shown in the UE 102, but multiple parallel elements (e.g., multiple transceivers 118, decoders 108, demodulators 114, encoders 150, and modulators 154) may be implemented.
[0037] The transceiver 118 may include one or more receivers 120 and one or more transmitters 158. The one or more receivers 120 may receive signals from the gNB 160 using one or more antennas 122a-n. For example, the receiver 120 may receive and downconvert the signals to produce one or more received signals 116. The one or more received signals 116 may be provided to the demodulator 114. The one or more transmitters 158 may transmit signals to the gNB 160 using one or more physical antennas 122a-n. For example, the one or more transmitters 158 may upconvert and transmit the one or more modulated signals 156.
[0038] The demodulator 114 may demodulate one or more received signals 116 to generate one or more demodulated signals 112. The one or more demodulated signals 112 may be provided to the decoder 108. The UE 102 may use the decoder 108 to decode the signal. The decoder 108 may generate a decoded signal 110, which may include the UE-decoded signal 106 (also referred to as the first UE-decoded signal 106). For example, the first UE-decoded signal 106 may include received payload data, which may be stored in the data buffer 104. Another signal in the decoded signal 110 (also referred to as the second UE-decoded signal) may include overhead data and / or control data. For example, the second UE-decoded signal may provide data that the UE operation module 124 can use to perform one or more operations.
[0039] In general, the UE operation module 124 may enable the UE 102 to communicate with one or more gNBs 160. The UE operation module 124 may include a UE scheduling module 126.
[0040] UE 102 may utilize UE scheduling module 126 to perform downlink reception and uplink transmission. Downlink reception may include reception of data, reception of downlink control information, and / or reception of downlink reference signals. In addition, uplink transmission may include transmission of data, transmission of uplink control information, and / or transmission of uplink reference signals. In some examples, UE scheduling module 126 may perform one or more operations for SPS configuration and / or CG configuration activation and / or release / deactivation.
[0041] In a radio communication system, physical channels (uplink physical channels and / or downlink physical channels) may be defined. The physical channels (uplink physical channels and / or downlink physical channels) may be used to transmit information delivered from a higher layer.
[0042] For example, in the uplink, a PRACH (physical random access channel) may be defined. In some methods, the PRACH (e.g., random access procedure) may be used for an initial access connection establishment procedure, a handover procedure, a connection reestablishment, timing adjustment (e.g., for synchronization of uplink transmissions, for UL synchronization), and / or for requesting uplink shared channel (UL-SCH) resources (e.g., uplink physical shared channel (PSCH) (e.g., PUSCH) resources).
[0043] In another example, a physical uplink control channel (PUCCH) may be defined. The PUCCH may be used to transmit uplink control information (UCI). The UCI may include a hybrid automatic repeat request acknowledgement (HARQ-ACK), channel state information (CSI), and / or a scheduling request (SR). The HARQ-ACK is used to indicate a positive acknowledgement (ACK) or a negative acknowledgement (NACK) of downlink data (e.g., a transport block, a medium access control protocol data unit (MAC PDU), and / or a downlink shared channel (DL-SCH)). The CSI is used to indicate the state of a downlink channel (e.g., a downlink signal). In addition, the SR is used to request resources for uplink data (e.g., a transport block, a MAC PDU, and / or an uplink shared channel (UL-SCH)).
[0044] In some examples, DL-SCH and / or UL-SCH may be transport channels used in the MAC layer. In addition, a transport block (TB) and / or a MAC PDU may be defined as a unit of a transport channel used in the MAC layer. A transport block may be defined as a unit of data delivered from the MAC layer to the physical layer. The MAC layer may deliver a transport block to the physical layer (e.g., the MAC layer delivers data as a transport block to the physical layer). In the physical layer, a transport block may be mapped to one or more codewords.
[0045] In the downlink, a physical downlink control channel (PDCCH) may be defined. The PDCCH may be used to transmit downlink control information (DCI). In some examples, more than one DCI format may be defined for DCI transmission on the PDCCH. For example, fields may be defined in a DCI format and mapped to information bits (e.g., DCI bits).
[0046] For example, DCI format 1_0 for scheduling PDSCH in a cell may be defined as a DCI format for downlink. In addition, as described herein, one or more radio network temporary identifiers (e.g., cell RNTI (C-RNTI), configured scheduling RNTI (CS-RNTI), system information RNTI (SI-RNTI), and / or random access RNTI (RA-RNTI) may be used to transmit DCI format 1_0. Moreover, DCI format 1_0 may be monitored (e.g., transmitted, mapped) in a common search space (CSS) and / or a UE-specific search space (USS). In some examples, DCI format 1_0 may be monitored (e.g., transmitted, mapped) only in the CSS.
[0047] For example, the DCI included in DCI format 1_0 may be a frequency domain resource allocation (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_0 may be a time domain resource allocation (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_0 may be a modulation and coding scheme (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_0 may be a new data indicator. Additionally or alternatively, the DCI included in DCI format 1_0 may be a HARQ process number (HPN). Additionally or alternatively, the DCI included in DCI format 1_0 may be a TPC (e.g., transmit power control) command for a scheduled PUCCH.
[0048] Additionally or alternatively, DCI format 1_1 for scheduling PDSCH in a cell may be defined as a DCI format for downlink. Additionally or alternatively, C-RNTI and / or CS-RNTI may be used to transmit DCI format 1_1. Additionally or alternatively, DCI format 1_1 may be monitored (e.g., transmitted and / or mapped) in CSS and / or USS.
[0049] For example, the DCI included in DCI format 1_1 may be a BWP indicator (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_1 may be a frequency domain resource allocation (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_1 may be a time domain resource allocation (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_1 may be a modulation and coding scheme (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_1 may be a new data indicator. Additionally or alternatively, the DCI included in DCI format 1_1 may be a HARQ process number (HPN). Additionally or alternatively, the DCI included in DCI format 1_1 may be a TPC command for a scheduled PUCCH. Additionally or alternatively, the DCI included in the DCI format 1_1 may be a CSI request for requesting (e.g., triggering) transmission of CSI (e.g., CSI report (e.g., aperiodic CSI report)). Additionally or alternatively, as described below, the DCI included in the DCI format 1_1 may be information for indicating an index of a configuration of DL semi-persistent scheduling (SPS) (e.g., an SPS configuration index).
[0050] Additionally or alternatively, a new DCI format (e.g., DCI format 1_2) for scheduling PDSCH in a cell may be defined as a DCI format for a downlink. Additionally or alternatively, C-RNTI and / or CS-RNTI may be used to transmit the new DCI format (e.g., DCI format 1_2). Additionally or alternatively, DCI format 1_2 may be monitored (e.g., transmitted and / or mapped) in a CSS and / or USS.
[0051] For example, the DCI included in DCI format 1_2 may be a BWP indicator (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_2 may be a frequency domain resource allocation (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_2 may be a time domain resource allocation (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_2 may be a modulation and coding scheme (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_2 may be a new data indicator. Additionally or alternatively, the DCI included in DCI format 1_2 may be a HARQ process number (HPN). Additionally or alternatively, the DCI included in DCI format 1_2 may be a TPC command for a scheduled PUCCH. Additionally or alternatively, the DCI included in the DCI format 1_2 may be a CSI request for requesting (e.g., triggering) transmission of CSI (e.g., CSI report (e.g., aperiodic CSI report)). Additionally or alternatively, the DCI included in the DCI format 1_2 may be a configurable field, for example, antenna port [0 to 2 bits], transmission configuration indication [0 to 3 bits], rate matching indicator [0 to 2 bits], SRS request [0 to 3 bits], PRB bundling size indicator [0 to 1 bit], carrier indicator [0 to 3 bits], CSI request [0 to 3 bits], ZP CSI-RS trigger [0 to 2 bits], Beta offset indicator [0 to 2 bits], SRS resource indicator [0 to 4 bits], repetition factor [0 to 2 bits] and / or priority indication [0 to 3 bits]. Additionally or alternatively, as described below, the DCI included in DCI format 1_2 may be information for indicating an index of a configuration of DL semi-persistent scheduling (SPS) (e.g., an SPS configuration index).
[0052] Additionally or alternatively, DCI format 0_0 for scheduling PUSCH in a cell may be defined as a DCI format for uplink. Additionally or alternatively, C-RNTI, CS-RNTI, and / or temporary C-RNTI may be used to transmit DCI format 0_0. Additionally or alternatively, DCI format 0_0 may be monitored (e.g., transmitted, mapped) in the CSS and / or USS. In some examples, DCI format 0_0 may be monitored (e.g., transmitted, mapped) only in the CSS.
[0053] For example, the DCI included in DCI format 0_0 may be a frequency domain resource allocation (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_0 may be a time domain resource allocation (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_0 may be a modulation and coding scheme (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_0 may be a new data indicator. Additionally or alternatively, the DCI included in DCI format 0_0 may be a HARQ process number (HPN). Additionally or alternatively, the DCI included in DCI format 0_0 may be a redundancy version. Additionally or alternatively, the DCI included in DCI format 0_0 may be a TPC command for a scheduled PUSCH.
[0054] Additionally or alternatively, DCI format 0_1 for scheduling PUSCH in a cell may be defined as a DCI format for uplink. Additionally or alternatively, C-RNTI and / or CS-RNTI may be used to transmit DCI format 0_1. Additionally or alternatively, DCI format 0_1 may be monitored (e.g., transmitted, mapped) in CSS and / or USS.
[0055] For example, the DCI included in DCI format 0_1 may be a BWP indicator (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_1 may be a frequency domain resource allocation (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_1 may be a time domain resource allocation (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_1 may be a modulation and coding scheme (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_1 may be a new data indicator. Additionally or alternatively, the DCI included in DCI format 0_1 may be a HARQ process number (HPN). Additionally or alternatively, the DCI included in DCI format 0_1 may be a TPC command for a scheduled PUSCH. Additionally or 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 for indicating an index of a configuration of a configured authorization (e.g., a CG configuration index).
[0056] Additionally or alternatively, a new DCI format (e.g., DCI format 0_2) for scheduling PDSCH in a cell may be defined as a DCI format for uplink. Additionally or alternatively, C-RNTI and / or CS-RNTI may be used to transmit DCI format 0_2. Additionally or alternatively, DCI format 0_2 may be monitored (e.g., transmitted, mapped) in CSS and / or USS.
[0057] For example, the DCI included in DCI format 0_2 may be a BWP indicator (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_2 may be a frequency domain resource allocation (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_2 may be a time domain resource allocation (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_2 may be a modulation and coding scheme (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_2 may be a new data indicator. Additionally or alternatively, the DCI included in DCI format 0_2 may be a HARQ process number (HPN). Additionally or alternatively, the DCI included in DCI format 0_2 may be a TPC command for a scheduled PUSCH. Additionally or alternatively, the DCI included in DCI format 0_2 may be a CSI request for requesting a CSI report. Additionally or alternatively, the DCI included in DCI format 0_2 may be a configurable field, for example, antenna port [0 to 2 bits], transmission configuration indication [0 to 3 bits], rate matching indicator [0 to 2 bits], SRS request [0 to 3 bits], PRB bundling size indicator [0 to 1 bit], carrier indicator [0 to 3 bits], CSI request [0 to 3 bits], ZP CSI-RS trigger [0 to 2 bits], Beta offset indicator [0 to 2 bits], SRS resource indicator [0 to 4 bits], repetition factor [0 to 2 bits] and / or priority indication [0 to 3 bits]. Additionally or alternatively, as described below, the DCI included in DCI format 0_2 may be information of a configured index for indicating a configured grant (e.g., a CG configuration index).
[0058] Additionally or alternatively, upon receiving DCI format 1_0 and / or DCI format 1_1 and / or DCI format 1_2 (e.g., based on detecting DCI format 1_0 and / or DCI format 1_1 and / or DCI format 1_2), UE 102 may perform PDSCH transmission. Additionally or alternatively, upon receiving DCI format 0_0 and / or DCI format 0_1 and / or DCI format 0_2 (e.g., based on detecting DCI format 0_0 and / or DCI format 0_1 and / or DCI format 0_2), UE 102 may perform PUSCH transmission.
[0059] In some examples, as described above, an RNTI (e.g., a radio network temporary identifier) allocated to UE 102 may be used for transmission of DCI (e.g., one or more DCI formats, one or more DL control channels (e.g., one or more PDCCHs)). For example, gNB 160 may transmit information for configuring (e.g., allocating) the RNTI to UE 102 (e.g., by using an RRC message).
[0060] For example, a CRC (cyclic redundancy check) parity bit (also referred to as CRC) generated based on the DCI is attached to the DCI, and after attachment, the CRC parity bit is scrambled by the RNTI. The UE 102 may attempt to decode (e.g., blindly decode, monitor, detect) the DCI to which the CRC parity bit scrambled by the RNTI is attached. For example, the UE 102 detects a DL control channel (e.g., PDCCH, DCI, DCI format) based on blind decoding. That is, the UE 102 may decode the DL control channel using the CRC scrambled by the RNTI. In other words, the UE 102 may monitor the DL control channel using the RNTI. For example, the UE 102 may detect the DCI format using the RNTI.
[0061] In some examples, the RNTI may include a C-RNTI (Cell-RNTI), a CS-RNTI (Configured Scheduling C-RNTI), a SI-RNTI (System Information RNTI), a RA-RNTI (Random Access RNTI) and / or a Temporary C-RNTI.
[0062] For example, C-RNTI can be a unique identifier for identifying an RRC connection and / or scheduling. Additionally or alternatively, CS-RNTI can be a unique identifier for configuration-based authorization scheduling transmission. Additionally or alternatively, SI-RNTI can be used to identify a system message (SI) (e.g., SI message) mapped on BCCH and dynamically carried on DL-SCH. Additionally or alternatively, SI-RNTI can be used for broadcasting of SI. Additionally or alternatively, RA-RNTI can be an identifier for a random access procedure (e.g., Msg.2 transmission). Additionally or alternatively, a temporary C-RNTI can be used for a random access procedure (e.g., scheduling of Msg.3 (re)transmission (e.g., Msg.3 PUSCH (re)transmission)).
[0063] Additionally or alternatively, a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH) may be defined. For example, in the case where PDSCH (e.g., PDSCH resources) are scheduled by using a DCI format, UE 102 may receive downlink data on the scheduled PDSCH (e.g., PDSCH resources). Additionally or alternatively, in the case where PUSCH (e.g., PUSCH resources) are scheduled by using a DCI format, UE 102 transmits uplink data on the scheduled PUSCH (e.g., PUSCH resources). For example, PDSCH may be used to transmit downlink data (e.g., DL-SCH, downlink transport blocks). Additionally or alternatively, PUSCH may be used to transmit uplink data (e.g., UL-SCH, uplink transport blocks).
[0064] In addition, the PDSCH and / or PUSCH may be used to transmit information of higher layers (e.g., a radio resource control (RRC) layer and / or a MAC layer). For example, the PDSCH (e.g., from the gNB 160 to the UE 102) and / or the PUSCH (e.g., from the UE 102 to the gNB 160) may be used to transmit RRC messages (RRC signals). Additionally or alternatively, the PDSCH (e.g., from the gNB 160 to the UE 102) and / or the PUSCH (e.g., from the UE 102 to the gNB 160) may be used to transmit MAC control elements (MAC CEs). In some examples, the RRC messages and / or the MAC CEs are also referred to as higher layer signals.
[0065] In some methods, a physical broadcast channel (PBCH) may be defined. For example, the PBCH may be used to broadcast a MIB (Master Information Block). In some examples, the system information may be divided into a MIB and multiple SIBs (System Information Blocks). For example, the MIB may be used to carry minimum system information. Additionally or alternatively, the SIB may be used to carry system information messages.
[0066] In some methods, in the downlink, a SS (synchronization signal) may be defined. The SS may be used to acquire time and / or frequency synchronization with a cell. Additionally or alternatively, the SS may be used to detect a physical layer cell ID of a cell.
[0067] In radio communication for uplink, UL RS may be used as an uplink physical signal. Additionally or alternatively, in radio communication for downlink, DL RS may be used as a downlink physical signal. The uplink physical signal and / or the downlink physical signal may not be used to transmit information provided from a higher layer, but may be used by a physical layer.
[0068] In some examples, for simplicity of description, in some implementations, it may be assumed that the downlink physical channels and / or downlink physical signals described herein are included in a downlink signal (e.g., a DL signal). Additionally or alternatively, for simplicity of description, in some implementations, it may be assumed that the uplink physical channels and / or uplink physical signals described herein are included in an uplink signal (i.e., a UL signal).
[0069] The UE operations module 124 may provide the information 148 to the one or more receivers 120. For example, the UE operations module 124 may inform the one or more receivers 120 when to receive a retransmission.
[0070] The UE operations module 124 may provide information 138 to the demodulator 114. For example, the UE operations module 124 may inform the demodulator 114 of the modulation pattern expected for transmissions from the gNB 160.
[0071] The UE operations module 124 may provide information 136 to the decoder 108. For example, the UE operations module 124 may inform the decoder 108 of the encoding expected for the transmission from the gNB 160.
[0072] The UE operation module 124 may provide information 142 to the encoder 150. The information 142 may include data to be encoded and / or instructions for encoding. For example, the UE operation module 124 may instruct the encoder 150 to encode the transmission data 146 and / or other information 142. The other information 142 may include PDSCH HARQ-ACK information.
[0073] The encoder 150 may encode the transmission data 146 and / or other information 142 provided by the UE operations module 124. For example, encoding the data 146 and / or other information 142 may involve error detection and / or correction coding, mapping the data to spatial, time, and / or frequency resources for transmission, multiplexing, etc. The encoder 150 may provide the encoded data 152 to a modulator 154.
[0074] The UE operations module 124 may provide information 144 to the modulator 154. For example, the UE operations module 124 may inform the modulator 154 of the type of modulation (e.g., constellation mapping) to be used for transmission to the gNB 160. The modulator 154 may modulate the coded data 152 to provide one or more modulated signals 156 to one or more transmitters 158.
[0075] The UE operations module 124 may provide information 140 to the one or more transmitters 158. The information 140 may include instructions for the one or more transmitters 158. For example, the UE operations module 124 may instruct the one or more transmitters 158 when to transmit signals to the gNB 160. For example, the one or more transmitters 158 may transmit during a UL subframe. The one or more transmitters 158 may up-convert the modulated signal 156 and transmit the modulated signal to the one or more gNBs 160.
[0076] Each of the one or more gNBs 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 paths and / or transmit paths may be implemented in the gNB 160. For convenience, only a single transceiver 176, decoder 166, demodulator 172, encoder 109, and modulator 113 are shown in the gNB 160, but multiple parallel elements (e.g., multiple transceivers 176, decoders 166, demodulators 172, encoders 109, and modulators 113) may be implemented.
[0077] The transceiver 176 may include one or more receivers 178 and one or more transmitters 117. The one or more receivers 178 may receive signals from the UE 102 using one or more physical antennas 180a-n. For example, the receiver 178 may receive and downconvert the signals to produce one or more received signals 174. The one or more received signals 174 may be provided to the demodulator 172. The one or more transmitters 117 may transmit signals to the UE 102 using one or more physical antennas 180a-n. For example, the one or more transmitters 117 may upconvert and transmit one or more modulated signals 115.
[0078] The demodulator 172 may demodulate one or more received signals 174 to produce one or more demodulated signals 170. The one or more demodulated signals 170 may be provided to the decoder 166. The gNB 160 may decode the signal using the decoder 166. The decoder 166 may produce one or more decoded signals 164, 168. For example, the first eNB decoded signal 164 may include received payload data, which may be stored in the data buffer 162. The second eNB decoded signal 168 may include overhead data and / or control data. For example, the second eNB decoded signal 168 may provide data (e.g., PDSCH HARQ-ACK information) that the gNB operations module 182 may use to perform one or more operations.
[0079] In general, the gNB operations module 182 may enable the gNB 160 to communicate with one or more UEs 102. The gNB operations module 182 may include one or more of the gNB scheduling modules 194. The gNB scheduling module 194 may perform scheduling of downlink and / or uplink transmissions as described herein. For example, the gNB scheduling module 182 may perform one or more operations for SPS configuration and / or CG configuration activation and / or release / deactivation.
[0080] The gNB operations module 182 may provide information 188 to the demodulator 172. For example, the gNB operations module 182 may inform the demodulator 172 of the modulation pattern expected for transmissions from one or more UEs 102.
[0081] The gNB operations module 182 may provide information 186 to the decoder 166. For example, the gNB operations module 182 may inform the decoder 166 of the encoding expected for transmissions from one or more UEs 102.
[0082] The gNB operation module 182 may provide information 101 to the encoder 109. The information 101 may include data to be encoded and / or instructions for encoding. For example, the gNB operation module 182 may instruct the encoder 109 to encode the information 101, including the transmission data 105.
[0083] The encoder 109 may encode the transmission data 105 and / or other information included in the information 101 provided by the gNB operation module 182. For example, encoding the transmission data 105 and / or other information included in the information 101 may involve error detection and / or correction coding, mapping the data to space, time and / or frequency resources for transmission, multiplexing, etc. The encoder 109 may provide the encoded data 111 to the modulator 113. The transmission data 105 may include network data to be relayed to the UE 102.
[0084] The gNB operations module 182 may provide information 103 to the modulator 113. The information 103 may include instructions for the modulator 113. For example, the gNB operations module 182 may inform the modulator 113 of the type of modulation (e.g., constellation mapping) to be used for transmission to the UE 102. The modulator 113 may modulate the coded data 111 to provide one or more modulated signals 115 to one or more transmitters 117.
[0085] The gNB operations module 182 may provide information 192 to the one or more transmitters 117. The information 192 may include instructions for the one or more transmitters 117. For example, the gNB operations module 182 may instruct the one or more transmitters 117 when (and when not) to transmit signals to the one or more UEs 102. The one or more transmitters 117 may upconvert the one or more modulated signals 115 and transmit the one or more modulated signals to the one or more UEs 102.
[0086] It should be noted that DL subframes may be transmitted from the gNB 160 to one or more UEs 102, and UL subframes may be transmitted from one or more UEs 102 to the gNB 160. In addition, both the gNB 160 and one or more UEs 102 may transmit data in standard special subframes.
[0087] It should also be noted that one or more of the elements or components thereof included in one or more eNBs 160 and one or more UEs 102 may be implemented in hardware. For example, one or more of these elements or components thereof may be implemented as a chip, a circuit, a hardware component, etc. It should also be noted that one or more of the functions or methods described herein may be implemented in hardware and / or performed using hardware. For example, one or more of the methods described herein may be implemented in and / or implemented using a chipset, an application specific integrated circuit (ASIC), a large scale integrated circuit (LSI), or an integrated circuit, etc.
[0088] Figure 2 Examples of multiple parameters are shown. Figure 2As shown, multiple parameters (e.g., multiple subcarrier spacings) may be supported. For example, μ (e.g., subcarrier space configuration) and cyclic prefix (e.g., μ and cyclic prefix of a carrier bandwidth portion) may be configured by high-level parameters (e.g., RRC messages) for downlink and / or uplink. In some examples, 15kHz may be a reference parameter. For example, the RE of the reference parameter may be defined as having a subcarrier spacing of 15kHz in the frequency domain and a 2048Ts+CP length (e.g., 160Ts or 144Ts) in the time domain, where Ts represents a baseband sampling time unit defined as 1 / (15000*2048) seconds.
[0089] Additionally or alternatively, each time slot may be determined based on μ (eg, subcarrier spatial configuration). In some examples, for example, a slot configuration 0 (eg, the number of OFDM symbols per slot may be 14) and / or a slot configuration (eg, the number of OFDM symbols per slot may be 7) may be defined.
[0090] Figure 3 is a diagram showing one example of a resource grid 301 and resource blocks 391 (eg, for downlink and / or uplink). Figure 3 The resource grid 301 and resource block 391 shown may be used in some implementations of the systems and methods disclosed herein.
[0091] exist Figure 3 In the example, a subframe 369 may include Symbols 387. Additionally or alternatively, a resource block 391 may include a plurality of resource elements (REs) 389. In some examples, in the downlink, an OFDM access scheme with a cyclic prefix (CP) may be adopted, which may also be referred to as CP-OFDM. A downlink radio frame may include multiple pairs of downlink resource blocks (RBs) 391, which are also referred to 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 a time slot. A downlink RB pair may include two downlink RBs 391 that are consecutive in the time domain. Additionally or alternatively, a downlink RB 391 may include twelve subcarriers in the frequency domain, and seven (for normal CP) or six (for extended CP) OFDM symbols in the time domain. An area defined by one subcarrier in the frequency domain and one OFDM symbol in the time domain is referred to as a resource element (RE) 389, and is uniquely identified by an index pair (k, l), where k and l are indices in the frequency domain and the time domain, respectively.
[0092] Additionally or alternatively, in the uplink, in addition to CP-OFDM, a single carrier frequency division multiple access (SC-FDMA) access scheme may be adopted, which is also called discrete Fourier transform spread OFDM (DFT-S-OFDM). An uplink radio frame may include multiple pairs of uplink resource blocks 391. An uplink RB pair is a unit for allocating uplink radio resources defined by a predetermined bandwidth (RB bandwidth) and a time slot. An uplink RB pair may include two uplink RBs 391 that are consecutive in the time domain. An uplink RB may include twelve subcarriers in the frequency domain and seven (for normal CP) or six (for extended CP) OFDM / DFT-S-OFDM symbols in the time domain. An area defined by one subcarrier in the frequency domain and one OFDM / DFT-S-OFDM symbol in the time domain is called a resource element (RE) 389 and is uniquely identified by an index pair (k, l) in a time slot, where k and l are indexes in the frequency domain and the time domain, respectively.
[0093] Each element in the resource grid 301 (eg, antenna port p) and subcarrier configuration p is referred to as a resource element 389 and is uniquely identified by an index pair (k, l), where k=0, ..., is an index in the frequency domain, and l refers to the symbol position in the time domain. The resource element (k, l) 389 on antenna port p and the subcarrier spacing configuration μ are denoted as (k,.l)p,μ. The physical resource block 391 is defined as The physical resource block 391 is from 0 to Number. Physical resource block number in the frequency domain n The relationship between PRB and resource element (k, l) is given by:
[0094] Figure 4 An example of a resource region (e.g., a resource region for a downlink) is shown. One or more PRB 491 sets 401 (e.g., a control resource set (i.e., CORESET)) may be configured for DL control channel monitoring (e.g., PDCCH monitoring). For example, a CORESET is a PRB 491 set 401 in the frequency domain and / or time domain, within which the UE 102 attempts to decode DCI (e.g., DCI format, PDCCH), and in the case where the PRB 491 may or may not be frequency-contiguous and / or time-contiguous, the UE 102 may be configured with one or more control resource sets (e.g., CORESET), and one DCI message may be mapped within one control resource set. In the frequency domain, a PRB 491 is a resource unit size of a DL control channel (which may or may not include a DM-RS).
[0095] UE 102 may monitor a candidate set of PDCCHs in one or more control resource sets (e.g., CORESETs) on an active DL bandwidth part (BWP) on each activated serving cell according to a corresponding search space set. In some examples, the term "monitoring" may imply that UE 102 attempts to decode each DL control channel (e.g., a candidate set of PDCCHs) according to the monitored DCI format. In addition, the candidates of the PDCCHs may be candidates to which the DL control channels may be mapped, allocated, and / or transmitted.
[0096] A candidate set of PDCCHs to be monitored by UE 102 may be defined according to a search space set (e.g., also referred to as a search space for short). UE 102 may monitor a set of PDCCH candidates in a search space. A search space set may include a common search space (CSS, UE common search space) and / or a user equipment specific search space (USS, UE specific search space).
[0097] For example, a CSS and / or USS may be defined (e.g., configured) in a region of a DL control channel. For example, a CSS may be used to send a DCI to multiple UEs 102. For example, a Type0-PDCCH common search space may be defined for one or more DCI formats having a CRC scrambled by a SI-RNTI. Additionally or alternatively, a Type1-PDCCH common search space may be defined for a DCI format having a CRC scrambled by a RA-RNTI, a temporary C-RNTI, and / or a C-RNTI. Additionally or alternatively, a Type3-PDCCH common search space may be defined for a DCI format having a CRC scrambled by a C-RNTI and / or a CS-RNTI.
[0098] The USS may be used to send the DCI to a specific UE 102. For example, the USS may be determined based on a radio network temporary identifier (RNTI) (e.g., C-RNTI). For example, the USS may be defined for a DCI format having a CRC scrambled by the C-RNTI and / or CS-RNTI.
[0099] In some examples, gNB 160 may transmit first information for configuring (e.g., determining) one or more CORESETs by using an RRC message. For example, for each DL BWP in a DL BWP (e.g., each DL BWP in a serving cell), gNB 106 may transmit first information for configuring the one or more CORESETs by using an RRC message. For example, the first information may include information for configuring an index of the CORESET. In addition, the first information may include information for configuring a plurality of consecutive symbols of the CORESET. In addition, the first information may include information for configuring a resource block set of the CORESET.
[0100] Additionally or alternatively, the gNB 160 may transmit second information for configuring the search space set by using an RRC message. For example, the second information may be configured for each search space set. For example, the second information may include information for configuring an index of the search space set. Additionally or alternatively, the second information may include information for configuring an index of a CORESET associated with the search space set. Additionally or alternatively, the second information may include information for indicating a PDCCH monitoring period and / or a PDCCH monitoring offset in which the UE 102 monitors the PDCCH in the search space set. Additionally or alternatively, the second information may include information for indicating a PDCCH monitoring mode within a time slot. For example, the information for indicating the PDCCH monitoring mode may be used to indicate the first symbol within the time slot monitored by the PDCCH. For example, the UE 102 may determine the PDCCH monitoring timing based on the PDCCH monitoring period, the PDCCH monitoring offset, and / or the PDCCH monitoring mode within the time slot.
[0101] Additionally or alternatively, the second information may include information indicating the type of the search space set (e.g., information indicating whether the search space set is a CSS or a USS). Additionally or alternatively, the second information may include information indicating one or more DCI formats for indicating that the UE 102 monitors the PDCCH in the search space set accordingly. For example, if the search space set is a CSS (e.g., if the search space set is configured as a CSS), DCI format 0_0 and / or DCI format 1_0 may be configured to monitor the PDCCH (e.g., a PDCCH candidate). In some examples, the DCI format for monitoring the PDCCH in the CSS may be scrambled by a C-RNTI, a CS-RNTI, a RA-RNTI, a temporary C-RNTI, a P-RNTI, and / or an SI-RNTI.
[0102] Additionally or alternatively, if the search space set is USS (e.g., if the search space set is configured as USS), DCI format 0_0 and / or DCI format 1_0 may be configured to monitor PDCCH (e.g., a candidate for PDCCH). Additionally or alternatively, if the search space set is USS, DCI format 0_1 and / or DCI format 1_1 may be configured to monitor PDCCH (e.g., a candidate for PDCCH). Additionally or alternatively, if the search space set is USS, DCI format 0_2 and / or DCI format 1_2 may be configured to monitor PDCCH (e.g., a candidate for PDCCH). For example, if the search space set is a USS, any one of the first group of DCI formats (e.g., DCI format 0_0 and / or DCI format 1_0) and / or the second group of DCI formats (e.g., DCI format 0_1 and / or DCI format 1_1) and / or the third group of DCI formats (e.g., DCI format 0_2 and / or DCI format 1_2) may be configured to monitor a PDCCH (e.g., a PDCCH candidate). In some examples, the DCI format for monitoring a PDCCH in a USS may be scrambled by a C-RNTI and / or a CS-RNTI. For example, the second information may be configured for a search space set. For example, the second information may be configured for each search space set in the search space set.
[0103] In some examples, for a serving cell, gNB 160 may configure a set of four DLBWPs (e.g., up to four DL BWPs, a DL BWP set) using an RRC message (e.g., for reception by UE 102). Additionally or alternatively, gNB 160 may indicate an active DL BWP using a DCI format for the downlink. For example, for each DL BWP in the set of DL BWPs, gNB 160 may configure a subcarrier spacing, a cyclic prefix, a number of consecutive PRBs 491 (e.g., a bandwidth of the PRBs), and / or an index (e.g., an index of the DL BWP, a DL BWP ID) in the set of DL BWPs using an RRC message.
[0104] Additionally or alternatively, for the serving cell, the gNB 160 may configure four UL BWP sets (e.g., up to four UL BWPs, one UL BWP set) by using an RRC message (e.g., for transmission by the UE 102). Additionally or alternatively, the gNB 160 may indicate the active UL BWP by using a DCI format for the uplink. Additionally or alternatively, for each UL BWP in the UL BWP set, the gNB 160 may configure the subcarrier spacing, cyclic prefix, number of consecutive PRBs 491 (e.g., bandwidth of the PRBs), index (e.g., index of the UL BWP) in the UL BWP set by using an RRC message.
[0105] Additionally or alternatively, the UE 102 may perform reception on the PDCCH in the DL BWP and / or reception on the PDSCH in the DL BWP based on the configuration for the DL BWP. Additionally or alternatively, the UE 102 may perform based on the configuration for the UL BWP.
[0106] Figure 5 An example of UL transmission corresponding to a configured grant is shown. Figure 5 As described, the UE 102 may perform UL transmission (e.g., (re)transmission on the UL-SCH and / or (re)transmission on the PUSCH 503a-d). For example, the UE 102 may perform UL transmission on the PUSCH 503a-d on the UL BWP in the serving cell. In some examples, the DL BWP and the UL BWP are linked together when the index of the DL BWP and the index of the UL BWP are the same. And, based on detecting a downlink signal (e.g., PDCCH 501a-d) on the DL BWP (e.g., active DL BWP), the UE 102 performs UL transmission corresponding to the configured grant on the UL BWP (e.g., active UL BWP) linked with the DLBWP on which the downlink signal was detected.
[0107] For example, UL transmissions may be dynamically scheduled by an uplink grant in a DCI (e.g., a DCI format for uplink with a CRC scrambled by C-RNTI). Additionally or alternatively, UL transmissions may correspond to a configured grant type 1 and / or a configured grant type 2. Transmissions corresponding to a configured grant type 1 may be semi-statically configured to operate upon receiving parameters of a configured ConfiguredGrantConfig including rrc-ConfiguredUplinkGrant without detecting an uplink grant in the DCI (e.g., a DCI format for uplink). Transmissions corresponding to a configured grant type 2 may be scheduled by an uplink grant in a valid activation DCI (e.g., an activation DCI format for uplink with a CRC scrambled by CS-RNTI) after receiving parameters of a ConfiguredGrantConfig not including rrc-ConfiguredUplinkGrant.
[0108] For example, a UL transmission corresponding to a configured grant may be scheduled (e.g., activated) by using a DCI format having a CRC scrambled by a CS-RNTI. And, two types of UL transmissions correspond to the configured grants. For example, one of the two types of UL transmissions may be referred to as a transmission corresponding to a configured grant type 1 (e.g., a configured grant type 1 transmission for a configured UL transmission of grant type 1). In addition, one of the two types of UL transmissions may be referred to as a transmission corresponding to a configured grant type 2 (e.g., a configured grant type 2 transmission for a configured UL transmission of grant type 2).
[0109] In some examples, for a configured grant type 1 transmission, an uplink grant can be provided by RRC (e.g., an RRC layer). For example, in the event that UE 102 receives an RRC message including an uplink grant (e.g., a configuration for a configured grant type 1 transmission), UE 102 can store the uplink grant as a configured grant.
[0110] In addition, for the configured grant type 2, the uplink grant may be provided by the PDCCH 501 (e.g., an activation DCI format to be used to indicate activation, a configured grant activation, and / or an activation of a configured grant (e.g., a configured grant corresponding to the configured grant configuration). For example, in the case where the UE 102 receives an uplink grant (e.g., an activation DCI format), the UE 102 may store the uplink grant as the configured grant. In addition, in the case where the UE 102 receives an uplink grant (e.g., a deactivation DCI format to be used to indicate deactivation, a configured grant deactivation, and / or a deactivation of a configured grant (e.g., a configured grant corresponding to the configured grant configuration)), the UE 102 clears the configured uplink grant (e.g., a configured grant corresponding to the deactivation configured grant configuration with an index). For example, in the case where the UE 102 receives an uplink grant (e.g., a deactivation DCI format to be used to indicate deactivation, a configured grant deactivation, and / or a deactivation of a configured grant (e.g., a configured grant corresponding to the configured grant configuration)), the UE 102 clears the configured uplink grant (e.g., a configured grant corresponding to the deactivation configured grant configuration with an index). The uplink grant provided by PDCCH 501 may be stored as a configured grant based on a DCI format (e.g., L1 signaling) indicating activation of the configured grant (e.g., a DCI format for indicating activation of the configured grant). Additionally or alternatively, the uplink grant provided by PDCCH 501 may be cleared based on a DCI format (e.g., L1 signaling) indicating deactivation of the configured grant (e.g., a DCI format for indicating deactivation of the configured grant).
[0111] For example, for a configured grant type 2 transmission, a DCI format with a CRC scrambled by the CS-RNTI may be used to indicate activation (e.g., a configured grant activation). Additionally, for a configured grant type 2 transmission, a DCI format with a CRC scrambled by the CS-RNTI may be used to indicate deactivation (e.g., a configured grant deactivation).
[0112] In some examples, a DCI format with a CRC scrambled by a CS-RNTI may be used to indicate a retransmission (e.g., a retransmission of a TB (e.g., a retransmission of a TB transmitted by a configured grant type 1 transmission and / or a configured grant type 2 transmission). For example, a retransmission may be indicated by using an NDI set to "1" (i.e., an NDI field is set to "1", NDI="1"). In some examples, as described above, an NDI (i.e., an NDI field) may be included in a DCI format with a CRC scrambled by a CS-RNTI. For example, a PUSCH retransmission may be scheduled by using a PDCCH 501 (e.g., a DCI format for an uplink) with an NDI set to "1" having a CRC scrambled by a CS-RNTI.
[0113] In some examples, for a configured grant type 1 transmission, based on the configuration of the configured grant type 1 (e.g., for the serving cell), the UE 102 may store the uplink grant as the configured grant (e.g., for the serving cell). Additionally, the UE 102 may initialize (if not active) or reinitialize (if already active) the configured grant to start in the symbol according to the parameter (e.g., timeDomainoffset) and reoccur with the parameter (e.g., period). Also, after the uplink grant is configured for the configured grant type 1, the UE 102 may sequentially consider the Nth uplink grant to occur in association with the symbol for which:
[0114] [(SFN*numberOfSlotsPerFrame*numberOfSymbolsPerSlof)+(number of slots in frame*numberOfSymbolsPerSlot)+number of slots in frame]=timeDomainOffset+N*period) modulo 1024. (1)
[0116] Additionally, for example, for a configured grant type 2 transmission, after an uplink grant is configured for the configured grant type 2, the UE 102 may sequentially consider that the Nth uplink grant occurs in association with a symbol for which:
[0117] [(SFN*numberOfSlotsPerFrame*numberOfSymbolsPerSlot)+(number of slots in a frame*numberOfSymbolsPerSlot)+number of slots in a frame]=[(SFN start time *numberOfSlotsPerFrame*numberOfSymbolsPerSlot+slot starttime*numberOfSymbolsPerSlot+symbol start time )+N*cycle] modulo 1024. (2)
[0119] In some examples, SFN start time 、slot start time and symbol start time The SFN (i.e., system frame number), time slot, and symbol, respectively, when the configured uplink grant is (re)initialized. In addition, for example, the parameters (e.g., periodicity) may be configured by gNB 160 using an RRC message.
[0120] For example, for a configured grant type 1 transmission, the UE 102 may initiate an uplink transmission based on the reception of the parameters included in the RRC message. Additionally, for a configured grant type 2 transmission, the UE 102 may initiate an uplink transmission based on the reception of a DCI format for uplink having a CRC scrambled by the C-RNTI. Additionally, the UE 102 may perform a retransmission of a TB (e.g., a retransmission on the UL-SCH, a retransmission on the PUSCH 503) based on the reception of a DCI format for uplink having a CRC scrambled by the C-RNTI, wherein the NDI included in the DCI format for uplink is set to "1".
[0121] For example, gNB 160 may transmit parameters for configured grant type 1 transmission by using an RRC message (e.g., a dedicated RRC message, a UE-specific RRC message). And, UE 102 may perform the configured grant type 1 transmission based on the parameters included in the RRC message. Additionally, gNB 160 may transmit parameters for configured grant type 2 transmission by using an RRC message (e.g., a dedicated RRC message, a UE-specific RRC message). And, UE 102 may perform the configured grant type 2 transmission based on the parameters included in the RRC message.
[0122] In some examples, for a transmission corresponding to a configured grant (i.e., a configured grant type 1 transmission and / or a configured grant type 2 transmission), the following parameters may be configured. For example, these parameters may be included in a ConfiguredGrantConfig in a ConfiguredGrantConfig information element (IE). For example, an RRC message may include a ConfiguredGrantConfig IE.
[0123] -frequencyhopping: The value "intraSlot" enables "intra-slot frequency hopping", and the value "interSlot" enables "inter-slot frequency hopping"
[0124] -mcs-Table: Indicates the MCS table that the UE 102 should use for PUSCH (e.g., PUSCH transmission) (e.g., without transform precoding)
[0125] -mcs-TableTransformPrecoder: Indicates the MCS table that the UE 102 should use for PUSCH (e.g., PUSCH transmission) (e.g., with transform precoding)
[0126] -powerControlLoopToUse: The closed control loop to be applied. Parameters used to determine the transmit power for PUSCH transmissions (e.g., transmissions corresponding to a configured grant)
[0127] -p0-PUSCH-Alpha: Index to the P0-PUSCH-AlphaSet to be used for this configuration. Parameter used to determine the transmit power for PUSCH transmissions (e.g., transmissions corresponding to a configured grant)
[0128] -transformPrecoder: Enable or disable transform precoding for transmissions corresponding to configured grants (i.e., configured grant type 1 transmissions and / or configured grant type 2 transmissions)
[0129] -nrofHARQ-Processes: The number of HARQ processes configured for configured grant type 1 transmissions and / or configured grant type 2 transmissions
[0130] -repK : The number of repetitions to apply to configured grant type 1 transfers and / or configured grant type 2 transfers
[0131] -repK-RV: sequence of redundancy versions to be applied to configured grant type 1 transmissions and / or configured grant type 2 transmissions
[0132] Additionally or alternatively, for a configured grant type 1 transmission, the following parameters may be configured: For example, the flow parameters may be included in the rrc-ConfiguredUplinkGrant in the ConfiguredGrantConfig IE.
[0133] - timeDomainOffset: offset value associated with system frame number (SFN) = 0. For example, an offset value used to indicate the timing of a configured grant type 1 transmission.
[0134] -timeDomainAllocation: indicates the combination of the start symbol and length and the PUSCH mapping type
[0135] -frequencyDomainAllocation: indicates frequency domain resource allocation
[0136] -antennaport: Indicates the antenna port to be used for this configuration
[0137] -mcsAndTBS: indicates modulation order, target bit rate and / or TB size
[0138] -frequencyHoppingOffset: The frequency hopping offset used when frequency hopping is enabled
[0139] -pathlossReferenceIndex: Parameters for power control of configured grant type 1 transmissions (ie, for this configuration)
[0140] In some examples, multiple configurations of ConfiguredGrantConfig may be supported. For example, one or more configurations in ConfiguredGrantConfig may be configured. Additionally, multiple configurations of rrc-ConfiguredUplinkGrant may be supported. For example, one or more configurations in rrc-ConfiguredUplinkGrant may be configured. In some examples, a configuration of ConfiguredGrantConfig and / or a configuration of rrc-ConfiguredUplinkGrant may be referred to as a configuration of a configured grant. For example, a single configuration of a configured grant may be supported. Additionally, multiple configurations of a configured grant may be supported.
[0141] For example, the gNB 160 may transmit the third information by using an RRC message, the third information being used to configure the multiple configurations of the configured grant to be enabled (e.g., allowed). For example, the gNB 160 may transmit the third information by using an RRC message, the third information being used to indicate whether the single configuration of the configured grant or the multiple configurations of the configured grant is used for transmission corresponding to the configured grant.
[0142] For example, in the case where the single configuration of the configured authorization is configured, the single configuration of the configured authorization can be used for transmission corresponding to the configured authorization. In addition, in the case where the multiple configurations of the configured authorization are configured, the multiple configurations of the configured authorization can be used for transmission corresponding to the configured authorization. In addition, in the case where the multiple configurations of the configured authorization are not configured, the single configuration of the configured authorization can be used for transmission corresponding to the configured authorization.
[0143] In some examples, the third information may be configured per serving cell. For example, the third information may be configured for each of the serving cells (e.g., the primary cell and / or the one or more secondary cells). Additionally or alternatively, the third information may be configured per UL bandwidth part (UL BWP). For example, the third information may be configured for each UL BWP in the UL BWP (each UL BWP in the UL BWP in the serving cell). Additionally or alternatively, the third information may be configured for a configured grant type 1 transmission and / or a configured grant type 2 transmission. For example, the third information may be generally configured for a configured grant type 1 transmission and a configured grant type 2 transmission. Additionally or alternatively, the third information may be configured separately for a configured grant type 1 transmission and a configured grant type 2 transmission.
[0144] For example, as described below, in the case where the third information is generally configured for configured grant type 1 transmission and configured grant type 2 transmission, the configured index may be configured for ConfiguredGrantConfig. Additionally or alternatively, in the case where the third information is separately configured for configured grant type 1 transmission and configured grant type 2 transmission, the index of the configured index may be configured for ConfiguredGrantConfig and / or the configured index may be configured for rrc-ConfiguredUplinkGrant.
[0145] Additionally or alternatively, the single configuration of the configured grant may be activated. For example, the single active configuration of the configured grant may be supported. Additionally or alternatively, the multiple configurations of the configured grant may be activated. For example, the multiple active configurations of the configured grant may be supported. For example, the multiple active configurations of the configured grant for a given BWP (e.g., UL BWP) for a serving cell may be supported at least for different service / traffic types and / or to enhance reliability and reduce latency.
[0146] For example, the single configuration of the configured grant may be configured (and / or activated) for a given BWP (e.g., UL BWP) of a single serving cell. Additionally or alternatively, the multiple configurations of the configured grant may be configured (and / or activated) for a given BWP (e.g., UL BWP) of a single serving cell.
[0147] UE 102 may perform configured grant type 1 transmission based on the single configuration of configured grants (if the single configuration of configured grants is used) and / or the multiple configurations of configured grants (if the multiple configurations of configured grants are used).
[0148] Additionally or alternatively, for transmission on PUSCH 503, the following parameters may be configured. For example, flow parameters may be included in PUSCH-Config in the PUSCH-Config IE (e.g., included in the BWP-UplinkDedicated IE). The IE PUSCH-Config may be used to configure UE-specific parameters applicable to a specific BWP (e.g., UL BWP). In addition, the IE BWP-UplinkDedicated may be used to configure dedicated parameters for the UL BWP (i.e., UE-specific parameters). For example, the gNB 160 may transmit parameters for transmission on PUSCH 503 by using an RRC message (e.g., a dedicated RRC message, a UE-specific RRC message). For example, the following parameters may be used for transmission on PUSCH 503 scheduled by using a DCI format with a CRC scrambled by a C-RNTI.
[0149] -dataScramblingIdentityPUSCH: Identifier used to initiate data scrambling of PUSCH (e.g., PUSCH transmission)
[0150] -txConfig: Indicates whether the UE uses codebook-based transmission or non-codebook-based transmission
[0151] -PUSCH-PowerControl: Parameter used to determine the transmission power of PUSCH transmission
[0152] -frequencyHopping: The value "intraSlot" enables "intra-slot frequency hopping", and the value "interSlot" enables "inter-slot frequency hopping"
[0153] -pusch-TimeDomainAllocationList: List of time-domain resource allocations for DCI formats used for uplink and UL transmissions
[0154] -pusch-AggregationFactor: The number of repetitions of UL transmission (e.g., PUSCH transmission)
[0155] -mcs-Table: Indicates which MCS table the UE should use for PUSCH transmission (e.g. without transform precoding)
[0156] -mcs-TableTransformPrecoder: Indicates which MCS table the UE should use for PUSCH transmission (e.g. with transform precoding)
[0157] -transformPrecoder: UE-specific selection of transformer precoder for PUSCH transmission
[0158] -scaling of UCI-OnPUSCH: Indicates the scaling factor that limits the number of resource elements allocated to UCI transmitted on PUSCH
[0159] In some examples, the parameter PUSCH-PowerControl may include the following parameters.
[0160] -tpc-Accumulation: If enabled, the UE 102 applies the transmit power (TPC) command via accumulation. If not enabled, the UE 102 applies the TPC command without accumulation. The parameter indicates the configuration of the TPC command (e.g., whether the TPC command is accumulated or not (i.e., the absolute value is used as the TPC command))
[0161] -p0-NominalWithoutGrant: Parameter used to determine the transmission power for transmissions corresponding to the configured grant
[0162] -p0-Alpha: Parameter used to determine the transmission power of PUSCH transmission
[0163] In some examples, multiple configurations of PUSCH-Config may be supported. For example, one or more configurations in PUSCH-Config may be configured. In some examples, the configuration of PUSCH-Config may be referred to as a configuration of PUSCH 503. For example, a single configuration of PUSCH 503 may be supported. In addition, multiple configurations of PUSCH 503 may be supported.
[0164] For example, in the case where the multiple configurations of the configured grants are configured, the multiple configurations of PUSCH 503 may be configured. For example, in the case where the gNB 160 configures the multiple configurations of the configured grants, the gNB 160 may always configure the multiple configurations of PUSCH 503. For example, in the case where the single configuration of the configured grants is configured, the single configuration of PUSCH 503 may be configured. For example, in the case where the gNB 160 configures the single configuration of the configured grants, the gNB 160 may always configure the single configuration of PUSCH 503.
[0165] In some examples, where the multiple configurations of the configured grant are configured, the configured index may be configured. For example, the configured index may be included in ConfiguredGrantConfig (e.g., or ConfiguredGrantConfigIE). Additionally or alternatively, the configured index may be included in rrc-ConfiguredUplinkGrant (e.g., in ConfiguredGrantConfig IE). Additionally or alternatively, the configured index may be included in PUSCH-config.
[0166] In some examples, the index of the configuration may be an index of the configuration of ConfiguredGrantConfig. Additionally or alternatively, the index of the configuration may be an index of the configuration of rrc-ConfiguredUplinkGrant. Additionally or alternatively, the index of the configuration may be an index of the configuration of PUSCH-Config.
[0167] For example, each of the multiple configurations of the configured grants may be identified by using an index of the configuration (e.g., an index of the configured grant configuration). In addition, each of the multiple configurations of the PUSCH 503 may be identified by using an index of the configuration (e.g., an index of the PUSCH configuration). In addition, a link between each of the multiple configurations of the configured grants and each of the multiple configurations of the PUSCH 503 (e.g., a corresponding relationship between each of the multiple configurations of the configured grants and each of the multiple configurations of the PUSCH 503) may be identified by using an index of the configuration.
[0168] For example, in a case where multiple configurations of the configured authorization (e.g., four configurations of the configured authorization) are configured for configured authorization transmission, index "0" (e.g., value "0"), index "1" (e.g., value "1"), index "2" (e.g., value "2") and / or index "3" (e.g., value "3") may be configured as the index of the configuration for each of the multiple configurations of the configured authorization.
[0169] For example, index "0" may be configured for a first configuration in the plurality of configurations of the configured authorization (e.g., as configuration index #0). Additionally, index "1" may be configured for a second configuration in the plurality of configurations of the configured authorization (e.g., as configuration index #1). Additionally, index "2" may be configured for a third configuration in the plurality of configurations of the configured authorization (e.g., as configuration index #2). Additionally, index "1" may be configured for a fourth configuration in the plurality of configurations of the configured authorization (e.g., as configuration index #3).
[0170] For example, in the case where the multiple configurations of the PUSCH (e.g., four configurations of the PUSCH) are configured, index "0", index "1", index "2", and / or index "3" may be configured as the index of the configuration of each of the multiple configurations of the PUSCH 503. For example, in the case where the multiple configurations of the PUSCH 503 (e.g., four configurations of the PUSCH 503) are configured, index "0", index "1", index "2", and / or index "3" may be configured as the index of the configuration of each of the multiple configurations of the PUSCH 503.
[0171] For example, index "0" may be configured for a first configuration in the plurality of configurations of the PUSCH (e.g., as configuration index #0). Additionally, index "1" may be configured for a second configuration in the plurality of configurations of the PUSCH (e.g., as configuration index #1). Additionally, index "2" may be configured for a third configuration in the plurality of configurations of the PUSCH (e.g., as configuration index #2). Additionally, index "1" may be configured for a fourth configuration in the plurality of configurations of the PUSCH (e.g., as configuration index #3).
[0172] And, in the case where the configured index of the configured grant and the configured index of the PUSCH 503 are the same, the configured grant configuration may be linked with the configuration of the PUSCH 503. For example, in the case where the configured index of the configured grant and the configured index of the PUSCH 503 are the same, the configured grant configuration and the PUSCH 503 configuration may be linked together.
[0173] In some examples, one of the multiple configurations of the configured authorization (e.g., a configuration of the configured authorization having an index "X (X=0, 1, 2, or 3)" (e.g., an index corresponding to one of the multiple configurations of the configured authorization)) may be pre-defined by a specification and may be known information between the gNB 160 and the UE 102. Additionally or alternatively, one of the multiple configurations of the configured authorization may be configured by the gNB 160. For example, the gNB 160 may transmit information for configuring one of the multiple configurations of the configured authorization (e.g., an index corresponding to the one or more configurations of the configured authorization) by using an RRC message. The UE 102 may identify one of the multiple configurations of the configured authorization (e.g., an index corresponding to one of the multiple configurations of the configured authorization) based on the information. In some examples, one of the multiple configurations of the configured authorization may be referred to as a configuration having an index "X". For example, the index corresponding to one of the multiple configurations of the configured authorization may be referred to as an index "X".
[0174] As described above, the configuration with index "X" may be the configuration with index "0". Additionally or alternatively, the configuration with index "X" may be the configuration with index "1". Additionally or alternatively, the configuration with index "X" may be the configuration with index "2". Additionally or alternatively, the configuration with index "X" may be the configuration with index "3". For example, the configuration with index "X" may be the configuration with index "predetermined value".
[0175] Additionally or alternatively, the index of the configuration of the authorization of the configuration may not be configured for (e.g., applied to) the configuration with index "X". For example, the index of the configuration of the authorization of the configuration may be configured only for (e.g., applied only to) the configuration of the authorization of the configuration other than the configuration with index "X".
[0176] Additionally or alternatively, in the case of using the single configuration of the configured grant, the single configuration of the configured grant may correspond to the configuration with index "X". Additionally or alternatively, in the case of using the single configuration of the configured grant, the single configuration of PUSCH 503 may be linked with the configuration with index "X". Additionally or alternatively, in the case of using the single configuration of the configured grant, the single configuration of PUSCH 503 may be linked with the configuration with index "X".
[0177] In some examples, the configuration of the grant of configurations other than the configuration with index "X" may include a portion of the parameters included in the PUSCH-config. Also, the configuration with index "X" may not include a portion of the parameters included in the PUSCH-config.
[0178] For example, the authorized configurations of configurations other than the configuration with index "X" may include scaling of dataScramblingIdentityPUSCH, txConfig, PUSCH-PowerControl, frequencyHopping, pusch-TimeDomainAllocationList, pusch-AggregationFactor, mcs-Table, mcs-TableTransformPrecoder and / or UCI-OnPUSCH.
[0179] For example, the configurations granted for configurations other than the configuration with index "X" may include scaling of dataScramblingIdentityPUSCH, txConfig, and / or UCI-OnPUSCH. Also, the configurations granted for configurations other than the configuration with index "X" may not include PUSCH-PowerControl, frequencyHopping, pusch-TimeDomainAllocationList, pusch-AggregationFactor, mcs-Table, and / or mcs-TableTransformPrecoder.
[0180] For example, in a case where the multiple configurations of the configured grant are configured, a portion of the parameters (eg, the parameters described as included in the PUSCH-config) may be configured in the ConfiguredGrantConfig IE (eg, ConfiguredGrantConfig and / or rrc-ConfiguredUplinkGrant).
[0181] Additionally or alternatively, the configuration of the PUSCH 503 linked with the configuration of the grant of the configuration other than the configuration with index "X" may include a portion of the parameters (e.g., a portion of the parameters included in the PUSCH-config). And, the configuration of the PUSCH 503 linked with the configuration with index "X" may include parameters (e.g., all parameters included in the above-mentioned PUSCH-config).
[0182] For example, the configuration of PUSCH 503 linked with the configuration of the grant of configurations other than the configuration with index "X" may not include scaling of dataScramblingIdentityPUSCH, txConfig, PUSCH-PowerControl, frequencyHopping, pusch-TimeDomainAllocationList, pusch-AggregationFactor, mcs-Table, mcs-TableTransformPrecoder and / or UCI-OnPUSCH.
[0183] For example, the configuration of PUSCH 503 linked with the configuration of the grant configured other than the configuration with index "X" may include scaling of dataScramblingIdentityPUSCH, txConfig, tpc-Accumulation, and / or UCI-OnPUSCH. Also, the configuration of PUSCH 503 linked with the configuration of the grant configured other than the configuration with index "X" may not include p0-NominalWithoutGrant, p0-Alpha, frequencyHopping, pusch-TimeDomainAllocationList, pusch-AggregationFactor, mcs-Table, and / or mcs-TableTransformPrecoder.
[0184] For example, only a portion of the parameters (e.g., the parameters included in the PUSCH-config) may be configured as the multiple configurations (e.g., the multiple configurations of the PUSCH 503). For example, the multiple configurations of the configured grant are configured, and a portion of the parameters (e.g., a portion of the parameters included in the PUSCH-config) may be configured as the multiple configurations.
[0185] In some examples, in a case where the single configuration of the configured authorization is configured (ie, in a case where the multiple configurations of the configured authorization are not configured), UE 102 may perform transmission corresponding to the configured authorization based on the single configuration of the configured authorization.
[0186] For example, for a configured grant type 1 transmission, in a case where a configuration of a configured grant having an index of “1” is configured, the UE 102 may perform a transmission corresponding to the configured grant based on the configuration of the configured grant having an index of “1” (i.e., a parameter included in the configuration of the configured grant having an index of “1”). Additionally or alternatively, as described above, for a configured grant type 1 transmission, in a case where the single configuration of the configured grant is configured, the UE 102 may perform a transmission corresponding to the configured grant based on a configuration having an index of “X”. For example, in a case where the single configuration of the configured grant is configured, the configuration having an index of “X” may always be applied to a transmission corresponding to the configured grant.
[0187] Additionally or alternatively, for a configured grant type 2 transmission, in the case where the single configuration of the configured grant is configured, the UE 102 may identify the index of the configuration of the configured grant (i.e., the index of the configuration of the configured grant to be applied for the transmission) based on information included in a DCI format (e.g., a DCI format for indicating activation of the configured grant) having a CRC scrambled by the CS-RNTI. For example, the DCI format may include information for indicating the index of the configuration of the configured grant.
[0188] For example, for a configured grant type 2 transmission, in a case where the single configuration of the configured grant is configured and the configuration of the configured grant with index “1” is indicated by using a DCI format with a CRC scrambled by a CS-RNTI, the UE 102 may perform a transmission corresponding to the configured grant based on the configuration of the configured grant with index “1” (i.e., a parameter included in the configuration of the configured grant with index “1”). For example, the configuration of the configured grant with index “1” may be activated by using a DCI format with a CRC scrambled by a CS-RNTI. Additionally or alternatively, as described above, for a configured grant type 2 transmission, in a case where the single configuration of the configured grant is configured, the UE 102 may perform a transmission corresponding to the configured grant based on a configuration with index “X”. For example, in a case where the single configuration of the configured grant is configured, the configuration with index “X” may always be applied to the transmission corresponding to the configured grant.
[0189] Additionally or alternatively, for retransmission scheduled by using a DCI format with an NDI set to "1" having a CRC scrambled by the CS-RNTI, in the case where the single configuration of the configured grant is configured, the UE 102 may identify the index of the configuration of the PUSCH 503 (i.e., the index of the configuration of the PUSCH 503 to be applied for transmission) based on information included in the DCI format with an NDI set to "1" having a CRC scrambled by the CS-RNTI. For example, the DCI format for the uplink may include information for indicating the index of the configuration of the PUSCH 503.
[0190] For example, in the case where the single configuration of the configured grant is configured and the configuration of the PUSCH 503 with index "1" is indicated by using a DCI format with an NDI set to "1" with a CRC scrambled by the CS-RNTI, the UE 102 may perform retransmission based on the configuration of the PUSCH 503 with index "1" (i.e., parameters included in the configuration of the PUSCH 503 with index "1"). For example, the configuration of the PUSCH 503 with index "1" may be activated by using a DCI format with an NDI set to "1" with a CRC scrambled by the CS-RNTI. Additionally or alternatively, as described above, in the case where the single configuration of the configured grant is configured, the UE 102 may perform retransmission based on the configuration of the PUSCH 503 linked with the configuration with index "X". For example, in the case where the single configuration of the configured grant is configured, the configuration of the PUSCH 503 linked with the configuration with index "X" may always be applied to retransmission.
[0191] Additionally or alternatively, information indicating the index of the configuration of the configured grant may be included in the DCI format only when the multiple configurations of the configured grant are configured. For example, information indicating the index of the configuration of the configured grant may not be included in the DCI format for the uplink grant when the single configuration of the configured grant is configured. In some examples, as described below, information indicating the index of the configuration of the configured grant may be included only in DCI format 0_1.
[0192] Additionally or alternatively, information indicating an index of the configuration of PUSCH 503 may be included in the DCI format only when the multiple configurations of the configured grant are configured. For example, information indicating an index of the configuration of PUSCH 503 may not be included in the DCI format when the single configuration of the configured grant is configured. In some examples, as described below, information indicating an index of the configuration of PUSCH 503 may be included only in DCI format 0_1.
[0193] Additionally or alternatively, in a case where the multiple configurations of the configured grants are configured, the UE 102 may perform transmission corresponding to the configured grants based on the multiple configurations of the configured grants.
[0194] For example, for a configured authorization type 1 transmission, in a case where a configuration with an index “1” and a configuration with an index “3” are configured, UE 102 may perform transmission corresponding to the configured authorization based on the configuration of the authorization with an index “1” and the configuration of the authorization with an index “3” (i.e., parameters included in the configuration of the authorization with an index “1” and parameters included in the configuration of the authorization with an index “3”).
[0195] Additionally or alternatively, for a configured grant type 2 transmission, where multiple configurations of the configured grant are configured, UE 102 may identify an index of a configuration of the configured grant (i.e., an index of a configuration of the configured grant to be applied for the transmission) based on information included in a DCI format having a CRC scrambled by the CS-RNTI (e.g., a DCI format for indicating activation of the configured grant).
[0196] For example, for a configured grant type 2 transmission, in the case where the multiple configurations of the configured grants are configured and the configuration of the configured grant with index "1" is indicated by using a DCI format with a CRC scrambled by a CS-RNTI, the UE 102 may perform transmission corresponding to the configured grant based on the configuration with index "1" (i.e., the parameters included in the configuration of the configured grant with index "1"). For example, the configuration of the configured grant with index "1" may be activated by using a DCI format with a CRC scrambled by a CS-RNTI. In addition, in the case where the multiple configurations of the configured grants are configured and the configuration of the configured grant with index "3" is indicated by using a DCI format with a CRC scrambled by a CS-RNTI, the UE 102 may perform transmission corresponding to the configured grant based on the configuration with index "3" (i.e., the parameters included in the configuration of the configured grant with index "3"). For example, the configuration of the configured grant with index "3" may be activated by using a DCI format with a CRC scrambled by a CS-RNTI.
[0197] In some examples, the multiple configurations of the configured grants may be activated simultaneously (e.g., in overlapping time periods, simultaneously, or at the same time) by using the single DCI format with a CRC scrambled by the CS-RNTI. For example, the single DCI format may include information indicating one or more indexes of the configuration of the configured grants to be applied to the transmission corresponding to the configured grants. For example, in a case where the multiple configurations are configured and a configuration of a configured grant with index "1" and a configuration of a configured grant with index "3" are indicated, the UE 102 may perform the transmission corresponding to the configured grant based on the configuration of the configured grant with index "1" and the configuration of the configured grant with index "3".
[0198] Additionally or alternatively, for retransmission scheduled by using a DCI format having a CRC scrambled by a CS-RNTI with an NDI set to "1", in a case where the multiple configurations of the configured grant are configured, the UE 102 may identify the index of the configuration of the PUSCH 503 (i.e., the index of the configuration of the PUSCH 503 to be applied for transmission) based on information included in the DCI format having a CRC scrambled by a CS-RNTI with an NDI set to "1". For example, the DCI format for uplink may include information for indicating the index of the configuration of the PUSCH 503.
[0199] For example, in the case where the multiple configurations of the configured grant are configured and the configuration of the PUSCH 503 with index “1” is indicated by using a DCI format having a CRC scrambled by the CS-RNTI and having an NDI set to “1”, the UE 102 may perform retransmission based on the configuration of the PUSCH 503 with index “1” (i.e., parameters included in the configuration of the PUSCH 503 with index “1”). For example, the configuration of the PUSCH 503 with index “1” may be activated by using a DCI format having a CRC scrambled by the CS-RNTI and having an NDI set to “1”. In addition, in the case where the multiple configurations of the configured grant are configured and the configuration of the PUSCH 503 with the index "3" is indicated by using a DCI format with the NDI of the CRC scrambled by the CS-RNTI set to "1", the UE 102 may perform retransmission based on the configuration of the PUSCH 503 with the index "3" (i.e., the parameters included in the configuration of the PUSCH 503 with the index "3"). For example, the configuration of the PUSCH 503 with the index "3" may be activated by using a DCI format with the NDI of the CRC scrambled by the CS-RNTI set to "1".
[0200] In some examples, the multiple configurations of PUSCH 503 may be activated simultaneously (e.g., in overlapping time periods, simultaneously, or at the same time) by using the single DCI format with the NDI of the CRC scrambled by the CS-RNTI set to "1". For example, the single DCI format may include information indicating one or more indexes of the configuration of PUSCH 503 to be applied for retransmission. For example, in the case where the multiple configurations are configured and the configuration of PUSCH 503 with index "1" and the configuration of PUSCH 503 with index "3" are indicated, UE 102 may perform retransmission based on the configuration of PUSCH 503 with index "1" and the configuration of PUSCH 503 with index "3".
[0201] Additionally or alternatively, for transmissions corresponding to a configured grant (i.e., a configured grant type 1 and / or a configured grant type 2), the UE 102 may apply the parameters provided by ConfiguredGrantConfig in addition to the scaling of dataScramblingIdentityPUSCH, txConfig, and / or UCI-OnPUSCH provided by PUSCH-config. For example, for transmissions corresponding to a configured grant, the UE 102 may apply a portion of the parameters included in ConfiguredGrantConfig. Additionally, for transmissions corresponding to a configured grant, the UE 102 may apply a portion of the parameters included in PUSCH-config (e.g., scaling of dataScramblingIdentityPUSCH, txConfig, and / or UCI-OnPUSCH).
[0202] Additionally or alternatively, for retransmissions scheduled using a DCI format with NDI set to "1" with a CRC scrambled by the CS-RNTI, the UE 102 may apply the parameters of the PUSCH-config provided to expect p0-NominalWithoutGrant, p0-PUSCH-Alpha, mcs-Table, mcs-TableTransformPreder and / or transformPrecoder.
[0203] For example, for a retransmission scheduled by using a DCI format with NDI set to "1" with a CRC scrambled by the CS-RNTI, the UE 102 may apply the parameters of the provided PUSCH-config to expect p0-NominalWithoutGrant, p0-PUSCH-Alpha, mcs-Table, mcs-TableTransformPreder and / or transformPrecoder. And, instead of p0-NominalWithoutGrant, p0-PUSCH-Alpha, mcs-Table, mcs-TableTransformPrecoder and / or transformPrecoder included in PUSCH-config, p0-PUSCH-Alpha, mcs-Table, mcs-TableTransformPrecoder and / or transformPrecoder included in ConfiguredGrantConfig may be used for the retransmission. For example, for a retransmission scheduled by using a DCI format with an NDI set to "1" with a CRC scrambled by the CS-RNTI, the UE 102 may apply a portion of the parameters (e.g., p0-PUSCH-Alpha, mcs-Table, mcs-TableTransformPrecoder, and / or transformPrecoder) included in ConfiguredGrantConfig. Additionally, for a retransmission scheduled by using a DCI format with an NDI set to "1" with a CRC scrambled by the CS-RNTI, the UE 102 may apply a portion of the parameters included in PUSCH-config.
[0204] In some examples, in case the UE 102 applies a portion of the parameters included in the ConfiguredGrantConfig and a portion of the parameters included in the PUSCH-config, the configuration of the configured grant and the configuration of the PUSCH 503 linked together may be used for (re)transmission.
[0205] For example, for (re) transmission, in the case of applying the configuration of the grant having the configuration of index "0" (for example, in the case of applying a part of the configured parameters of the grant having the configuration of index "0"), the configuration of the PUSCH 503 having the index "0" may be applied (for example, a part of the configured parameters of the PUSCH 503 having the index "0"). In addition, for (re) transmission, in the case of applying the configuration of the grant having the configuration of index "1" (that is, in the case of applying a part of the configured parameters of the grant having the configuration of index "1"), the configuration of the PUSCH 503 having the index "1" (that is, a part of the configured parameters of the PUSCH 503 having the index "1") may be applied. In addition, for (re) transmission, in the case of applying the configuration of the grant having the configuration of index "2" (i.e., in the case of applying a part of the configured parameters of the grant having the configuration of index "2"), the configuration of the PUSCH 503 having the index "2" (i.e., a part of the configured parameters of the PUSCH 503 having the index "2") may be applied. In addition, for (re) transmission, in the case of applying the configuration of the grant having the configuration of index "3" (i.e., in the case of applying a part of the configured parameters of the grant having the configuration of index "3"), the configuration of the PUSCH 503 having the index "3" (i.e., a part of the configured parameters of the PUSCH 503 having the index "3") may be applied.
[0206] In addition, for (re)transmission, in case of applying a configuration of an authorization with a configuration having an index "X" (i.e., in case of applying a part of the parameters of the configuration of an authorization with a configuration having an index "X"), a configuration of PUSCH 503 linked with the authorization with a configuration having an index "X" (i.e., a part of the parameters of the configuration of PUSCH 503 linked with the configuration with an index "X") may be applied.
[0207] Additionally or alternatively, for (re) transmission, in the case of applying the configuration of the PUSCH 503 with index “0” (i.e., in the case of applying a portion of the parameters of the configuration of the PUSCH 503 with index “0”), the configuration of the grant with the configuration with index “0” (i.e., a portion of the parameters of the grant with the configuration with index “0”) may be applied. Also, for (re) transmission, in the case of applying the configuration of the PUSCH 503 with index “1” (i.e., in the case of applying a portion of the parameters of the configuration of the PUSCH 503 with index “1”), the configuration of the grant with the configuration with index “1” (i.e., a portion of the parameters of the grant with the configuration with index “1”) may be applied. In addition, for (re) transmission, in the case of applying the configuration of the PUSCH 503 with the index "2" (i.e., in the case of applying a part of the parameters of the configuration of the PUSCH 503 with the index "2"), the configuration of the grant with the configuration with the index "2" (i.e., a part of the parameters of the grant with the configuration with the index "2") may be applied. In addition, in the case of applying the configuration of the PUSCH 503 with the index "3" (i.e., in the case of applying a part of the parameters of the configuration of the PUSCH 503 with the index "3"), the configuration of the grant with the configuration with the index "3" (i.e., a part of the parameters of the grant with the configuration with the index "3") may be applied.
[0208] In addition, for (re)transmission, in the case of applying a configuration of PUSCH 503 linked with a configuration having an index "X" (i.e., in the case of applying a part of the parameters of the configuration of PUSCH 503 linked with a configuration having an index "X"), the configuration having an index "X" (i.e., a part of the parameters of the configuration having an index "X") may be applied.
[0209] Additionally or alternatively, for simplicity of description, in some implementations, it may be assumed that the single configuration of the grant of the configuration described herein and / or the single configuration of the PUSCH 503 are included in a single configuration “A.” In addition, for simplicity of description, in some implementations, it may be assumed that the multiple configurations of the grant of the configuration described herein and / or the multiple configurations of the PUSCH 503 are included in multiple configurations “B.”
[0210] As described above, information indicating the configured index of the configured grant may be included only in DCI format 0_1 (ie, DCI format 0_1 with CRC scrambled by CS-RNTI). For example, DCI format 0_0 may not include information indicating the configured index of the configured grant.
[0211] For example, in a case where the multiple configurations of the configured grant are configured, based on detecting (e.g., detecting, decoding) DCI format 0_1 with a CRC scrambled by CS-RNTI (e.g., NDI is set to "0"), UE 102 may perform transmission corresponding to the configured grant based on the multiple configurations "B" (e.g., as described above).
[0212] Additionally or alternatively, in the case of the multiple configurations of the configured authorization, based on detecting DCI format 0_1 with a CRC scrambled by the CS-RNTI (e.g., NDI is set to "1"), UE 102 may perform a retransmission (e.g., retransmission of a TB) based on the multiple configurations "B" (e.g., as described above).
[0213] Additionally or alternatively, in the case of detecting DCI format 0_0 with a CRC scrambled by CS-RNTI (e.g., NDI is set to "0"), UE 102 may perform transmission corresponding to the configured grant based on the single configuration "A" (e.g., as described above). For example, even if the multiple configurations of the configured grant are configured, in the case of detecting DCI format 0_0 with a CRC scrambled by CS-RNTI (e.g., NDI is set to "0"), UE 102 may perform transmission corresponding to the configured grant based on the single configuration "A".
[0214] For example, in the event of detecting DCI format 0_0 with a CRC encrypted by CS-RNTI (e.g., NDI is set to "0"), UE 102 may perform a transmission corresponding to the configured authorization based on the configuration with index "X" and / or the configuration of PUSCH503 linked to the configuration with index "X".
[0215] Additionally or alternatively, in the event that a DCI format 0_0 with a CRC scrambled by a CS-RNTI is detected (e.g., NDI is set to "1"), the UE 102 may perform retransmission (e.g., retransmission of a TB) based on the single configuration "A" (e.g., as described above). For example, even if the multiple configurations of the configured grant are configured, in the event that a DCI format 0_0 with a CRC scrambled by a CS-RNTI is detected (e.g., NDI is set to "1"), the UE 102 may perform retransmission based on the single configuration "A".
[0216] For example, in the event of detecting DCI format 0_0 with a CRC scrambled by CS-RNTI (e.g., NDI set to “1”), UE 102 may perform a retransmission based on a configuration with index “X” and / or a configuration of PUSCH 503 linked to a configuration with index “X”.
[0217] Additionally or alternatively, in the case where a DCI format having a CRC scrambled by a CS-RNTI (e.g., NDI is set to “0”) (e.g., DCI format 0_0 and / or DCI format 0_1) is detected in the CSS (i.e., CSS set), the UE 102 may perform transmission corresponding to the configured grant based on the single configuration “A” (e.g., as described above). For example, even if the multiple configurations of the configured grant are configured, in the case where a DCI format having a CRC scrambled by a CS-RNTI (e.g., NDI is set to “0”) (e.g., DCI format 0_0 and / or DCI format 0_1) is detected in the CSS, the UE 102 may perform transmission corresponding to the configured grant based on the single configuration “A”. For example, in the event that a DCI format (e.g., NDI is set to "0") having a CRC scrambled by a CS-RNTI is detected in a USS (i.e., a USS set) (e.g., DCI format 0_0 and / or DCI format 0_1), UE 102 may perform a transmission corresponding to the configured grant based on the multiple configurations "B" (e.g., as described above).
[0218] For example, in the case where a DCI format (e.g., NDI is set to "0") having a CRC scrambled by a CS-RNTI is detected in a CSS (i.e., a CSS set) (e.g., DCI format 0_0 and / or DCI format 0_1), the UE 102 may perform a transmission corresponding to the configured authorization based on the configuration having an index "X" and / or the configuration of the PUSCH 503 linked to the configuration having an index "X".
[0219] Additionally or alternatively, in the case where a DCI format (e.g., NDI is set to "0") (e.g., DCI format 0_0 and / or DCI format 0_1) with a CRC scrambled by a CS-RNTI is detected in the CSS (i.e., CSS set), the UE 102 may perform retransmission (e.g., retransmission of a TB) based on the single configuration "A" (e.g., as described above). For example, even if the multiple configurations of the configured grant are configured, in the case where a DCI format (e.g., NDI is set to "0") (e.g., DCI format 0_0 and / or DCI format 0_1) with a CRC scrambled by a CS-RNTI is detected in the CSS (i.e., CSS set), the UE 102 may perform retransmission based on the single configuration "A".
[0220] For example, in the event that a DCI format (e.g., NDI set to "0") having a CRC scrambled by a CS-RNTI is detected in a CSS (i.e., a CSS set) (e.g., DCI format 0_0 and / or DCI format 0_1), the UE 102 may perform a retransmission based on a configuration having an index "X" and / or a configuration of a PUSCH 503 linked to a configuration having an index "X".
[0221] Additionally or alternatively, in the case where a DCI format having a CRC scrambled by a CS-RNTI (e.g., NDI is set to “0”) (e.g., DCI format 0_0 and / or DCI format 0_1) is detected in CORESET #0, the UE 102 may perform transmission corresponding to the configured grant based on the single configuration “A” (e.g., as described above). For example, even if the multiple configurations of the configured grant are configured, in the case where a DCI format having a CRC scrambled by a CS-RNTI (e.g., NDI is set to “0”) (e.g., DCI format 0_0 and / or DCI format 0_1) is detected in CORESET #0, the UE 102 may perform transmission corresponding to the configured grant based on the single configuration “A”. For example, in the event that a DCI format having a CRC scrambled by CS-RNTI (e.g., NDI is set to "0") (e.g., DCI format 0_0 and / or DCI format 0_1) is detected in a CORESET other than CORESET#0, UE 102 may perform transmission corresponding to the configured grant based on the multiple configurations "B" (e.g., as described above).
[0222] For example, in the event that a DCI format having a CRC scrambled by CS-RNTI (e.g., NDI is set to “0”) (e.g., DCI format 0_0 and / or DCI format 0_1) is detected in CORESET#0, UE 102 may perform a transmission corresponding to the configured grant based on the configuration having index “X” and / or the configuration of PUSCH 503 linked with the configuration having index “X”.
[0223] Additionally or alternatively, in the case where a DCI format with a CRC scrambled by a CS-RNTI (e.g., NDI is set to "0") (e.g., DCI format 0_0 and / or DCI format 0_1) is detected in CORESET #0, the UE 102 may perform retransmission (e.g., retransmission of a TB) based on the single configuration "A" (e.g., as described above). For example, even if the multiple configurations of the configured grant are configured, in the case where a DCI format with a CRC scrambled by a CS-RNTI (e.g., NDI is set to "0") (e.g., DCI format 0_0 and / or DCI format 0_1) is detected in CORESET #0, the UE 102 may perform retransmission based on the single configuration "A".
[0224] For example, in the event that a DCI format having a CRC scrambled by CS-RNTI (e.g., NDI set to “0”) is detected in CORESET#0 (e.g., DCI format 0_0 and / or DCI format 0_1), the UE 102 may perform retransmission based on the configuration having index “X” and / or the configuration of the PUSCH 503 linked with the configuration having index “X”.
[0225] Additionally or alternatively, in the case where a DCI format having a CRC scrambled by a CS-RNTI (e.g., NDI is set to “0”) (e.g., DCI format 0_0 and / or DCI format 0_1) is detected in the search space set with index “0” (i.e., search space set #0), the UE 102 may perform transmission corresponding to the configured grant based on the single configuration “A” (e.g., as described above). For example, even if the multiple configurations of the configured grant are configured, in the case where a DCI format having a CRC scrambled by a CS-RNTI (e.g., NDI is set to “0”) (e.g., DCI format 0_0 and / or DCI format 0_1) is detected in the search space set #0, the UE 102 may perform transmission corresponding to the configured grant based on the single configuration “A”. For example, in the event that a DCI format with a CRC scrambled by CS-RNTI (e.g., NDI set to "0") is detected in a search space other than search space set #0 (e.g., DCI format 0_0 and / or DCI format 0_1), UE 102 may perform a transmission corresponding to the configured authorization based on the multiple configurations "B" (e.g., as described above).
[0226] For example, in the event that a DCI format having a CRC scrambled by CS-RNTI (e.g., NDI set to “0”) is detected in search space set #0 (e.g., DCI format 0_0 and / or DCI format 0_1), UE 102 may perform a transmission corresponding to the configured authorization based on the configuration having index “X” and / or the configuration of PUSCH 503 linked to the configuration having index “X”.
[0227] Additionally or alternatively, in the case where a DCI format with a CRC scrambled by a CS-RNTI (e.g., NDI is set to "0") (e.g., DCI format 0_0 and / or DCI format 0_1) is detected in search space set #0, UE 102 may perform retransmission (e.g., retransmission of a TB) based on the single configuration "A" (e.g., as described above). For example, even if the multiple configurations of the configured grant are configured, in the case where a DCI format with a CRC scrambled by a CS-RNTI (e.g., NDI is set to "0") (e.g., DCI format 0_0 and / or DCI format 0_1) is detected in search space set #0, UE 102 may perform retransmission based on the single configuration "A".
[0228] For example, in the event that a DCI format having a CRC scrambled by CS-RNTI (e.g., NDI set to “0”) is detected in search space set #0 (e.g., DCI format 0_0 and / or DCI format 0_1), the UE 102 may perform a retransmission based on a configuration having an index “X” and / or a configuration of the PUSCH 503 linked to the configuration having an index “X”.
[0229] In addition, grouping of configurations of configured authorizations may be supported. For example, gNB 160 may transmit information for a correspondence relationship between a configured authorization configuration group (e.g., an authorization configuration group of configurations having an index) and a configured authorization configuration (e.g., an authorization configuration of configurations having an index) by using an RRC message. For example, a configuration of a configuration of authorizations having an index of "0" may correspond to a configuration of an authorization configuration group having an index of "0". In addition, a configuration of a configuration of authorizations having an index of "1" may correspond to a configuration of an authorization configuration group having an index of "1". In addition, a configuration of a configuration of authorizations having an index of "2" may correspond to a configuration of an authorization configuration group having an index of "0". For example, a configuration of a configuration of authorizations having an index of "0" and a configuration of a configuration of authorizations having an index of "2" may belong to the same group (i.e., a configuration of authorization configuration group "0"). In addition, a configuration of a configuration of authorizations having an index of "4" may correspond to a configuration of an authorization configuration group having an index of "1". For example, the authorized configuration of the configuration with index "1" and the authorized configuration of the configuration with index "4" may belong to the same group (ie, the authorized configuration group "1" of the configurations).
[0230] In addition, grouping of PUSCH configurations may be supported. For example, the gNB 160 may transmit information for configuring a correspondence between a PUSCH configuration group (e.g., a PUSCH configuration group with an index) and a PUSCH configuration (e.g., a PUSCH configuration with an index) by using an RRC message. For example, the configuration of a PUSCH with an index "0" may correspond to a PUSCH configuration group with an index "1". In addition, the configuration of a PUSCH with an index "1" may correspond to a PUSCH configuration group with an index "0". In addition, the configuration of a PUSCH with an index "2" may correspond to a PUSCH configuration group with an index "0". For example, the configuration of a PUSCH with an index "1" and the configuration of a PUSCH with an index "2" may belong to the same group (i.e., PUSCH configuration group "0"). In addition, the configuration of a PUSCH with an index "3" may correspond to a PUSCH configuration group with an index "1". For example, the configuration of a PUSCH with an index of '0' and the configuration of a PUSCH with an index of '3' may belong to the same group (ie, PUSCH configuration group '1').
[0231] For example, in the systems and methods disclosed herein, a configured authorized configuration (e.g., a configuration of an authorized configuration having an index) may be replaced by a configured authorized configuration group (e.g., a group of configured authorized configurations having an index). In some examples, a configured authorized configuration group may include one or more configurations of a configured authorized configuration (e.g., one or more configurations of an authorized configuration having an index). For example, a configured authorized configuration having an index "X" may be replaced by a configured authorized configuration group having an index "X".
[0232] Additionally, in the systems and methods disclosed herein, a configuration of a PUSCH (e.g., a configuration of a PUSCH with an index) may be replaced by a PUSCH configuration group (e.g., a PUSCH configuration group with an index). In some examples, a PUSCH configuration group may include one or more PUSCH configurations (e.g., one or more PUSCH configurations with an index).
[0233] Figure 6An example of a configured grant confirmation medium access control (MAC) control element (CE) 601 is shown. As described above, for a configured grant type 2, the gNB 160 may transmit an activated DCI format (e.g., a second DCI and / or PDCCH) for indicating a configured grant (e.g., a configured grant corresponding to a configuration of a configured grant having an index of "2"). For example, based on receiving an activated DCI format (e.g., a second DCI and / or PDCCH) for indicating a configured grant (e.g., a configured grant corresponding to a configuration of a configured grant having an index of "2"), the UE 102 may perform a transmission on the PUSCH (e.g., perform a transmission on the PUSCH based on parameters configured by the configuration of the configured grant having an index of "2"). In addition, based on receiving the activated DCI format for indicating a configured grant (e.g., a configured grant corresponding to a configured grant with index “2” and a configured grant corresponding to a configured grant with index “3”), UE 102 may perform transmission on the PUSCH (e.g., perform transmission on the PUSCH based on parameters configured by the configuration of the configured grant with index “2” and / or parameters configured by the configuration of the configured grant with index “3”).
[0234] Additionally or alternatively, for a configured grant type 2, the gNB 160 may transmit a deactivated DCI format (e.g., a first DCI and / or PDCCH) for indicating a configured grant (e.g., a configured grant corresponding to a configuration having an index of a configured grant). For example, based on receiving a deactivated DCI format (e.g., a first DCI and / or PDCCH) for indicating a configured grant (e.g., a configured grant corresponding to a configuration having an index of “2”), the UE 102 may clear the configured grant (e.g., clear the configured grant corresponding to the configuration having an index of the configured grant). Additionally, based on receiving a deactivated DCI format for indicating a configured grant (e.g., a configured grant corresponding to a configuration having an index of “2” and a configured grant corresponding to a configuration having an index of “3”), the UE 102 may clear the configured grant (e.g., clear the configured grant corresponding to the configuration having an index of the configured grant and the configured grant corresponding to the configuration having an index of “3”). For example, based on receiving a DCI format for deactivating a grant for a configuration corresponding to a configuration with an indexed grant, UE 102 may clear the grant for the corresponding configuration (e.g., only clear the grant for the corresponding configuration) and maintain storage of grants for configurations that do not correspond to the configuration with an indexed grant.
[0235] For example, for a configured grant type 2, the UE 102 may clear the configured grant (e.g., the corresponding configured grant for the configured deactivated grant). In some examples, the UE 102 may clear the configured grant immediately after the first transmission of the configured grant confirmation MAC CE 601. For example, based on receiving a DCI format for deactivating a configured grant, the configured grant confirmation MAC CE 601 may be triggered. For example, the UE 102 may trigger the configured grant confirmation MAC CE 601, and clear the configured grant immediately after the first transmission of the configured grant confirmation MAC CE 601. In some examples, in the case of triggering the configured grant confirmation MAC CE 601, the UE 102 may transmit the configured grant confirmation MAC CE 601. For example, in the case of triggering the configured grant confirmation MAC CE 601 and not canceling the configured grant, and in the case where UL resources are allocated for new transmission, the configured grant confirmation MAC CE 601 may be transmitted.
[0236] In addition, as described above, the configuration of the configured grant may be linked to the configuration of the PUSCH. And, the UE 102 may clear the configuration of the PUSCH linked to the configuration of the deactivated configured grant. In some examples, the UE 102 may clear the configuration of the PUSCH linked to the configuration of the configured grant immediately after the first transmission of the configured grant confirmation MAC CE 601. For example, based on the DCI format received for deactivating the configured grant, the configured grant confirmation MAC CE 601 may be triggered, and / or the configuration of the PUSCH linked to the configuration of the configured grant may be cleared. For example, the UE 102 may trigger the configured grant confirmation MAC CE 601, and clear the configured grant immediately after the first transmission of the configured grant confirmation MAC CE 601. In addition, the UE 102 may trigger the configured grant confirmation MAC CE 601, and clear the configuration of the PUSCH linked to the configuration of the configured grant immediately after the first transmission of the configured grant confirmation MAC CE 601.
[0237] In some examples, the configured authorization confirmation MAC CE 601 can be identified by using a MAC subheader with an LCID (e.g., logical channel identifier), such as a value (e.g., index) (e.g., 55) of the LCID of the UL-SCH. In addition, the size (e.g., length) of the configured authorization confirmation MAC CE 601 can be defined (e.g., specified) as fixed. For example, the size (e.g., length) of the configured authorization confirmation MAC CE 601 can be defined as 16 bits. Additionally or alternatively, the size (e.g., length) of the configured authorization confirmation MAC CE 601 can be defined (e.g., specified) as 24 bits.
[0238] For example, for the configured authorization confirmation MAC CE 601, a field of a serving cell identification (e.g., serving cell ID) 603 may be defined. For example, the field of the serving cell ID 603 may be used to indicate the index of the serving cell to which the configured authorization confirmation MAC CE 601 applies (e.g., the index of the primary cell (e.g., "000" (i.e., zero)) and / or the index of the secondary cell (e.g., a value other than "000")). For example, the size (e.g., length) of the field of the serving cell ID 603 may be defined as 5 bits.
[0239] Additionally or alternatively, for the configured grant confirmation MAC CE 601, a field of a bandwidth part identification (e.g., BWP ID) 605 may be defined. For example, the field of the BWP ID 605 may be used to indicate the index of the UL BWP applied by the configured grant confirmation MAC CE 601. For example, the field of the BWP ID 605 may be used to indicate the index of the UL BWP applied by the configured grant confirmation MAC CE 601 as a code point of a BWP indicator field included in the DCI format. For example, the size (e.g., length) of the field of the BWP ID 605 may be defined (e.g., specified) as 2 bits.
[0240] Additionally or alternatively, for the configured authorization confirmation MAC CE 601, a field (e.g., S i (For example, the maximum number of i = 7 (for example, 0 to 7) or 15 (for example, 0 to 15)). For example, the field (for example, S i ) may be used to indicate an activation state and / or deactivation state of a configured authorization configuration within the plurality of active configurations (e.g., the plurality of active configurations configured by gNB 160 using an RRC message). For example, a field (e.g., S i) can be used to indicate that the state of the corresponding configuration of the configuration authorization is active (e.g., activated). In addition, a field set to a value of "0" (e.g., S i ) may be used to indicate that the state of the corresponding configuration of the configured authorization is deactivated (eg, deactivated).
[0241] Additionally or alternatively, a field (eg, S i For example, the field (e.g., S ) may be determined based on the number of configurations of the authorization configured within the plurality of active configurations (e.g., configured using an RRC message). i ). For example, in the case where the number of configurations of the configured authorization is configured as "4" (for example, as the number of multiple active configurations), the size of the field (for example, S1) may be "4" (for example, S0, S1, S2, and S3 may be used to indicate an activation state and / or a deactivation state). In addition, in the case where the number of configurations of the configured authorization is configured as "10" (for example, as the number of authorization configurations of multiple configurations), the size of the field (for example, S1) may be "4" (for example, S0, S1, S2, and S3 may be used to indicate an activation state and / or a deactivation state). i ) may be '10' (for example, S0, S1, S2, S3, S4, S5, S6, S7, S8, and S9 may be used to indicate an activation state and / or a deactivation state).
[0242] Additionally or alternatively, a field (eg, S i ) may be defined (e.g., specified) in ascending order (e.g., or in descending order) based on the index of the configurations of the authorization of the configurations. For example, S0 may refer to the configuration of the authorization of the configuration with the lowest index (e.g., the configuration of the authorization of the configuration with the lowest index within the multiple active configurations (e.g., configured by using an RRC message). In addition, S1 may refer to the configuration of the authorization of the configuration with the second lowest index (e.g., the configuration of the authorization of the configuration with the second lowest index within the multiple active configurations (e.g., configured by using an RRC message). In addition, S2 may refer to the configuration of the authorization of the configuration with the third lowest index (e.g., the configuration of the authorization of the configuration with the third lowest index within the multiple active configurations (e.g., configured by using an RRC message).
[0243] For example, in a case where an authorized configuration with a configuration having an index “1”, an authorized configuration with a configuration having an index “8”, and an authorized configuration with a configuration having an index “3” are configured (for example, as the multiple active configurations), S0 may refer to the activation state and / or deactivation state of the authorized configuration with the configuration having an index “1”, S1 may refer to the activation state and / or deactivation state of the authorized configuration with the configuration having an index “3”, and S2 may refer to the activation state and / or deactivation state of the authorized configuration with the configuration having an index “8”.
[0244] For example, UE 102 may determine the field (e.g., S i ) and the configuration of the configured authorization (eg, the field corresponding to the configuration of the configured authorization (eg, S i ). And, based on the configured index of the configured authorization, the UE 102 may set (eg, map) a value for indicating the activation state or the deactivation state to the field (eg, the determined field “S i ”).
[0245] As described above, in the systems and methods disclosed herein, the configuration of the configured authorization may be replaced by the configured authorization configuration group. In some examples, the configured authorization configuration group may include the configuration of the one or more configured authorizations. As described above, gNB 160 may transmit information for configuring the correspondence between the configured authorization configuration group and the configuration of the one or more configured authorizations by using an RRC message.
[0246] For example, for the configured authorization confirmation MAC CE 601, the fields (eg, S i (e.g., the maximum number of i=7 (e.g., 0 to 7) or 15 (e.g., 0 to 15))) to indicate the activation state and / or deactivation state of the configured authorization configuration group (e.g., the activation state and / or deactivation state of the configured authorization configuration group with index). For example, this field (e.g., S i ) may be used to indicate the activation state and / or deactivation state of a configured authorization configuration group within the plurality of active configurations (e.g., the plurality of active configurations configured by gNB 160 using an RRC message). For example, a field set to a value of “1” (e.g., S i ) can be used to indicate that the state of the corresponding configured authorization configuration group is active (e.g., activated). In addition, a field set to a value of "0" (e.g., S i ) may be used to indicate that the status of the corresponding configured authorization configuration group is deactivated (eg, deactivated).
[0247] Additionally or alternatively, the field (eg, S iFor example, the field (eg, S ) may be determined based on the number of configured authorization configuration groups within the plurality of active configurations (eg, configured using an RRC message). i ). For example, in the case where the number of configured authorization configuration groups is configured as "4" (for example, as the number of multiple active configurations), the size of the field (for example, S1) may be "4" (for example, S0, S1, S2, and S3 may be used to indicate an activation state and / or a deactivation state). In addition, in the case where the number of configured authorization configuration groups is configured as "10" (for example, as the number of multiple configured authorization configurations), the size of the field (for example, S1) may be "4" (for example, S0, S1, S2, and S3 may be used to indicate an activation state and / or a deactivation state). i ) may be '10' (for example, S0, S1, S2, S3, S4, S5, S6, S7, S8, and S9 may be used to indicate an activation state and / or a deactivation state).
[0248] Additionally or alternatively, a field (eg, S i ) may be defined (e.g., specified) in ascending order (e.g., or in descending order) based on the index of the configured authorization configuration group. For example, S0 may refer to the authorization configuration group of the configuration with the lowest index (e.g., the authorization configuration group of the configuration with the lowest index within the multiple active configurations (e.g., configured by using an RRC message)). In addition, S1 may refer to the authorization configuration group of the configuration with the second lowest index (e.g., the authorization configuration group of the configuration with the second lowest index within the multiple active configurations (e.g., configured by using an RRC message)). In addition, S2 may refer to the authorization configuration group of the configuration with the third lowest index (e.g., the authorization configuration group of the configuration with the third lowest index within the multiple active configurations (e.g., configured by using an RRC message)).
[0249] For example, in the case where an authorization configuration group having a configuration with index "1", an authorization configuration group having a configuration with index "8", and an authorization configuration group having a configuration with index "3" are configured, S0 may refer to the activation state and / or deactivation state of the authorization configuration group having the configuration with index "1", S1 may refer to the activation state and / or deactivation state of the authorization configuration group having the configuration with index "3", and S2 may refer to the activation state and / or deactivation state of the authorization configuration group having the configuration with index "8". In some examples, the authorization configuration group having a configuration with index "1" may include an authorized configuration having a configuration with index "1" and an authorized configuration having a configuration with index "8". In addition, the authorization configuration group having a configuration with index "8" may include an authorized configuration having a configuration with index "6", an authorized configuration having a configuration with index "10", and an authorized configuration having a configuration with index "14". In addition, the authorization configuration group having a configuration with index "3" may include an authorized configuration having a configuration with index "5".
[0250] For example, UE 102 may determine the field (e.g., S i ) and the configured authorization configuration group (e.g., the field corresponding to the configured authorization configuration group (e.g., S i )) and, based on the index of the configured authorization configuration group, the UE 102 may set (eg, map) a value for indicating an activation state or a deactivation state to a field (eg, a determined field S "i” ).
[0251] Additionally or alternatively, for the configured authorization confirmation MAC CE 601, a field of reserved bits (eg, "R") may be defined. For example, the field of reserved bits may be set to "0" (ie, zero).
[0252] In order to support multiple configurations of configured grants, some RRC parameters may be introduced.
[0253] An RRC parameter (e.g., UL-Configuredgrantconfig-index) may be introduced to indicate the index of the UL configured grant configuration. The RRC parameter (e.g., UL-Configuredgrantconfig-index) may be included in each RRC configuration of the configured grant (e.g., ConfiguredGrantConfig IE). The value of the RRC parameter (e.g., UL-Configuredgrantconfig-index) may be 0, 1, 2, ..., maxNrofConfiguredgrantconfig-2, or maxNrofConfiguredgrantconfig-1. maxNrofConfiguredgrantconfig may be the maximum number of CG (e.g., configured grant) configurations, which may be 12.
[0254] An RRC parameter (e.g., UL-Configuredgrantconfig-ToAddModList) may be introduced to configure more than one UL configured grant configuration. The RRC parameter (e.g., UL-Configuredgrantconfig-ToAddModList) may be a list or sequence of elements. The element here may be a configured grant configuration (e.g., ConfiguredGrantConfig) or an equivalent mapping. The elements of the list or sequence may contain an identifier (INTEGER) (e.g., ElementId) that explicitly identifies the element when adding, modifying, and removing. The ElementId here may be an index of a UL configured grant configuration (e.g., UL-Configuredgrantconfig-index). For each element (e.g., ConfiguredGrantConfig) in the RRC parameter (e.g., UL-Configuredgrantconfig-ToAddModList), if the current UE configuration includes an element (e.g., ConfiguredGrantConfig) with a given ElementId (e.g., UL-Configuredgrantconfig-index), the UE modifies the configured element (e.g., ConfiguredGrantConfig) according to the received element, otherwise the UE adds the received element (e.g., ConfiguredGrantConfig) to the UE configuration. For example, if the UE receives a CG configuration corresponding to the index, and the list in the UE configuration has a CG configuration corresponding to the index, the UE updates the CG configuration according to the received CG configuration. If the UE receives a CG configuration corresponding to the index, and the list in the UE configuration does not have a CG configuration corresponding to the index, the UE adds the CG configuration to the list and / or its configuration according to the received CG configuration. The RRC parameter (e.g., UL-Configuredgrantconfig-ToAddModList) can be 1 to maxNrofConfiguredgrantconfig of ConfiguredGrantConfig (e.g., 12).
[0255] An RRC parameter (e.g., UL-Configuredgrantconfig-ToReleaseList) may be introduced to release grant configurations of more than one UL configuration. The RRC parameter (e.g., UL-Configuredgrantconfig-ToReleaseList) may be a list or sequence of ElementIds (e.g., UL-Configuredgrantconfig-index). For each ElementId (e.g., UL-ConfiguredGrantConfig-index) in the RRC parameter (e.g., UL-Configuredgrantconfig-ToReleaseList), if the current UE configuration includes an element (UL configured grant configuration, e.g., ConfiguredGrantConfig) with a given ElementId (e.g., UL-Configuredgrantconfig-index), the UE releases the element (UL configured grant configuration, e.g., ConfiguredGrantConfig) from the current UE configuration. For example, if the list includes a configured grant configuration index, and the current UE configuration includes a configured grant configuration corresponding to the index, the UE releases the configured grant configuration corresponding to the index.
[0256] In order to support the joint release and / or separate release of authorized configurations of multiple configurations, a DCI field (e.g., HPN field) in a release DCI (e.g., DCI format 0_0, DCI format 0_1, and / or DCI format 0_2) and / or a high-level configurable table (e.g., a CG configuration release table) and / or a fixed / default table may be used to indicate which CG configuration or configurations are released. For example, an M (e.g., M<=4) bit indication in a release DCI is used to indicate which CG configuration or configurations are released, wherein the association between each state indicated by the indication and the CG configuration is that a maximum of 2^M states are high-level configurable, wherein each state can be mapped to a single or multiple CG configurations to be released. In the absence of a high-level configured state, a separate release is used, wherein the release corresponds to the CG configuration index indicated by the indication. M can be determined by the bit length of the HPN field of each DCI format used to activate and release type 2CGs.
[0257] For example, a DCI field (e.g., CG configuration index, which may reuse the HPN field) value m of the DCI may provide a row index m+1 for the allocated table. The determination of using the table may be defined below. The indexed row defines which CG configuration or configurations are released.
[0258] The table (e.g., UL-Type2Configuredgrantconfig-ReleaseStateList) can be high-level configured. The table can be UE-specific (e.g., UL-Type2Configuredgrantconfig-ReleaseStateList in pusch-Config) and / or commonly configured (e.g., UL-Type2Configuredgrantconfig-ReleaseStateList in pusch-ConfigCommon). The table (e.g., UL-Type2Configuredgrantconfig-ReleaseStateList) can be a list / sequence of CG configuration index sets (e.g., UL-Type2Configuredgrantconfig-ReleaseState). Each CG configuration index set can include one or more CG configuration indexes that can be released. The CG configuration index set can be empty, which means that the CG configuration will not be released. An example of an RRC configured table is shown in List 1. The maximum number of entries in the table / sequence / list (e.g., maxNrofUL-CG-ReleaseState) can be 16 or depend on the number of bits in the DCI field (e.g., CG configuration index).
[0259]
[0260] List 1
[0261] In some examples, the table may be fixed. For example, one or more default tables may be applied to the joint and / or separate release of multiple CG configurations. Some examples are shown in Table 1, Table 2, and Table 3.
[0262]
[0263]
[0264] Table 1
[0265] Row Index CG configuration index set 1 0 2 1 3 2 4 3 5 4 6 5 7 6 8 7 9 8 10 9 11 10 12 11 13 0、1、2 14 3、4、5 15 6、7、8 16 9、10、11
[0266] Table 2
[0267]
[0268]
[0269] Table 3
[0270] In some examples, more than one table to be used for CG configuration release may be defined and / or configured. In the case of more than one table (e.g., a CG configuration release table, including an RRC configuration table and / or a default table), and / or the determination of a table to be used for CG configuration release, it may depend on the DCI format used to release the DCI, the RRC configuration (e.g., whether a UE-specific table and / or a common configuration table is configured), the PDCCH search space in which the UE detects the release DCI, and / or the CORESET in which the UE detects the release DCI.
[0271] For example, if there is no RRC configured table (for example, if the parameter for indicating the table is not configured (for example, the value of the parameter for indicating the table is not configured)), the default table (for example, Table 1, Table 2, Table 3, or any table specified in the specification) may be applied to the joint / individual CG configuration release. For another example, if there is no RRC configured table, the joint release of multiple CG configurations may not be supported. For example, only individual release may be supported (for example, only releasing one CG configuration by using a single DCI format to release the DCI in a certain timing). Each value in the DCI field (e.g., CG configuration index) can have a one-to-one mapping with a CG configuration that can be released. For example, a DCI field (e.g., CG configuration index) value m of the DCI can indicate that a CG configuration with index m can be released.
[0272] For example, if a UE-specific RRC table (e.g., UL-Type2Configuredgrantconfig-ReleaseStateList in pusch-Config) is configured for the UE and the UE detects a release DCI in a UE-specific search space (e.g., DCI format 0_2, DCI format 0_1, and / or DCI format 0_0), the UE-specific RRC table (e.g., UL-Type2Configuredgrantconfig-ReleaseStateList in pusch-Config) may be applied (e.g., always applied) to a joint / individual CG configuration release (e.g., regardless of whether other tables (e.g., UL-Type2Configuredgrantconfig-ReleaseStateList in pusch-ConfigCommon and / or any default tables)) may be configured and / or provided.
[0273] For example, if a common RRC table (e.g., UL-Type2Configuredgrantconfig-ReleaseStateList in pusch-ConfigCommon) is configured (e.g., and there is no UE-specific RRC table for the UE (e.g., UL-Type2Configuredgrantconfig-ReleaseStateList in pusch-Config)), then the common RRC table (e.g., UL-Type2Configuredgrantconfig-ReleaseStateList in pusch-ConfigCommon) may be applied for joint / individual CG configuration release. For example, if a common RRC table and a UE-specific RRC table are configured, the UE may apply the UE-specific RRC table to be used for CG configuration release. For example, if a common RRC table and a UE-specific RRC table are configured for the UE, the UE-specific RRC table (e.g., the configuration of the UE-specific RRC table) may overwrite the common RRC table (e.g., the configuration of the common RRC table).
[0274] For example, if the UE detects a release DCI (e.g., DCI format 0_2, DCI format 0_1, and / or DCI format 0_0) in a common search space associated with CORESET 0 (e.g., and / or a common search space not associated with CORESET 0), a default table (e.g., Table 1, Table 2, Table 3, or any table specified in (e.g., defined by) the specification) may be applied for joint / individual CG configuration release. For another example, if the UE detects a release DCI (e.g., DCI format 0_2, DCI format 0_1, and / or DCI format 0_0) in a common search space associated with CORESET 0 (e.g., and / or a common search space not associated with CORESET 0), joint release of multiple CG configurations may not be supported. For example, only individual release may be supported. Each value in a DCI field (e.g., a CG configuration index) may have a one-to-one mapping with a CG configuration that can be released. For example, a DCI field (e.g., CG configuration index) value m of the DCI may indicate that a CG configuration with index m can be released.
[0275] Another example is shown in Table 4. As shown in Table 4, the UE may determine the table to be applied for the CG configuration release (e.g., from a default table, a common RRC table, and / or a UE-specific RRC table). For example, as described above, the UE may determine the table (e.g., from a default table, a common RRC table, and / or a UE-specific RRC table) based on the DCI format of the release DCI, the RRC configuration (e.g., whether the UE-specific RRC table is configured and / or whether the common RRC table is configured), the PDCCH search space of the DCI format for the release DCI detected by the UE, and / or the CORESET of the DCI format for the release DCI detected by the UE (e.g., the index of the CORESET).
[0276]
[0277] Table 4
[0278] If the released DCI is a fallback DCI (e.g., DCI format 0_0), there may be no DCI field (e.g., CG configuration index) to indicate which CG configuration is released, and some fallback behaviors can be described here. For example, if the UE detects DCI format 0_0 for CG configuration release, the UE can release all CG configurations (e.g., all type 2CG configurations). For another example, if the UE detects DCI format 0_0 for CG configuration release, the UE can release a specific configuration (e.g., a specific type 2Cg configuration) and / or a default configuration (e.g., a default type 2CG configuration). For example, if the UE detects DCI format 0_0 for CG configuration release, the UE can release a CG configuration with a predetermined index (e.g., a CG configuration with index "0" (e.g., as a specific type 2CG configuration and / or a default type 2CG configuration)). Additionally or alternatively, if the UE detects DCI format 0_0 for CG configuration release, the UE can release the CG configuration with the lowest index (e.g., the minimum index). For example, in a case where a CG configuration with an index of "1", a CG configuration with an index of "3", and a CG configuration with an index of "5" are configured, and if the UE detects DCI format 0_0 for CG configuration release, the UE may release the CG configuration with "1". Additionally or alternatively, if the UE detects DCI format 0_0 for CG configuration release, the UE may release the CG configuration with the highest index (e.g., the largest index). For example, in a case where a CG configuration with an index of "1", a CG configuration with an index of "3", and a CG configuration with an index of "5" are configured, and if the UE detects DCI format 0_0 for CG configuration release, the UE may release the CG configuration with "5". In some examples, a specific configuration and / or a default configuration may be defined by a specification and known information between the gNB and the UE. For example, for detection of DCI format 0_0 for CG configuration release, the UE may determine which CG configuration to release based on the index of the CG configuration (e.g., configured by the gNB). As another example, if multiple CG configurations are configured, the UE may not be expected to receive DCI format 0_0 for CG configuration release.
[0279] Additionally or alternatively, if the UE detects DCI format 0_0 for CG configuration release in the CSS, the UE may release all CG configurations (e.g., all type 2CG configurations). For another example, if the UE detects DCI format 0_0 for CG configuration release in the CSS, the UE may release a specific configuration (e.g., a specific type 2CG configuration) and / or a default configuration (e.g., a default type 2CG configuration). For example, if the UE detects DCI format 0_0 for CG configuration release in the CSS, the UE may release a CG configuration with a predetermined index (e.g., a CG configuration with index "0" (e.g., as a specific type 2CG configuration and / or a default type 2CG configuration)). Additionally or alternatively, if the UE detects DCI format 0_0 for CG configuration release in the CSS, the UE may release the CG configuration with the lowest index (e.g., the smallest index). For example, in a case where a CG configuration with an index of "1", a CG configuration with an index of "3", and a CG configuration with an index of "5" are configured, and if the UE detects DCI format 0_0 for CG configuration release in the CSS, the UE may release the CG configuration with "1". Additionally or alternatively, if the UE detects DCI format 0_0 for CG configuration release in the CSS, the UE may release the CG configuration with the highest index (e.g., the largest index). For example, in a case where a CG configuration with an index of "1", a CG configuration with an index of "3", and a CG configuration with an index of "5" are configured, and if the UE detects DCI format 0_0 for CG configuration release in the CSS, the UE may release the CG configuration with "5". For example, for DCI format 0_0 for CG configuration release detected in the CSS, the UE may determine which CG configuration to release based on the index of the CG configuration (e.g., configured by the gNB).
[0280] Additionally or alternatively, if the UE detects DCI format 0_0 for CG configuration release in the CSS associated with CORESET#0, the UE may release all CG configurations (e.g., all type 2CG configurations). For another example, if the UE detects DCI format 0_0 for CG configuration release in the CSS associated with CORESET#0, the UE may release a specific configuration (e.g., a specific type 2CG configuration) and / or a default configuration (e.g., a default type 2CG configuration). For example, if the UE detects DCI format 0_0 for CG configuration release in the CSS associated with CORESET#0, the UE may release a CG configuration with a predetermined index (e.g., a CG configuration with index "0" (e.g., as a specific type 2CG configuration and / or a default type 2CG configuration)). Additionally or alternatively, if the UE detects DCI format 0_0 for CG configuration release in the CSS associated with CORESET#0, the UE may release the CG configuration with the lowest index (e.g., the smallest index). For example, in a case where a CG configuration with an index of "1", a CG configuration with an index of "3", and a CG configuration with an index of "5" are configured, and if the UE detects DCI format 0_0 for CG configuration release in the CSS associated with CORESET#0, the UE may release the CG configuration with "1". Additionally or alternatively, if the UE detects DCI format 0_0 for CG configuration release in the CSS associated with CORESET#0, the UE may release the CG configuration with the highest index (e.g., the largest index). For example, in a case where a CG configuration with an index of "1", a CG configuration with an index of "3", and a CG configuration with an index of "5" are configured, and if the UE detects DCI format 0_0 for CG configuration release in the CSS associated with CORESET#0, the UE may release the CG configuration with "5". For example, for DCI format 0_0 for CG configuration release detected in the CSS associated with CORESET#0, the UE may determine which CG configuration to release based on the index of the CG configuration (e.g., configured by the gNB).
[0281] Semi-persistent scheduling (SPS) is configured by RRC per serving cell and per BWP. Activation and deactivation of DL SPS can be independent between serving cells. For DL SPS, DL allocations are provided by PDCCH (e.g., DCI format 1_0, DCI format 1_1, and / or DCI format 1_2) and are stored or cleared based on L1 signaling indicating SPS activation or deactivation / release.
[0282] The RRC configures the following parameters when SPS is configured (e.g., SPS-Config IE):
[0283] -cs-RNTI: CS-RNTI used for activation, deactivation and retransmission;
[0284] -nrofHARQ-Processes: the number of configured HARQ processes for SPS;
[0285] -periodicity: The periodicity of the downlink allocation for the SPS configuration.
[0286] When SPS is released by the upper layer, all corresponding configurations will be released. After the downlink allocation is configured for SPS, the MAC entity will consider the Nth downlink allocation to occur in the timeslot in turn, for which:
[0287] (numberOfSlotsPerFrame×SFN+time slot number in frame)=
[0288] [(NumberOfSlotsPerFrame×SFN start time +slot start time )+N×cycle×NumberOfS-LotsPerFrame / 10]modulo(1024×NumberOfSlotsPerFrame)
[0289] SFN start time and slot start time They are respectively the SFN and timeslot of the first transmission of the PDSCH of the (re)initialized downlink allocation.
[0290] In order to support multiple configurations of SPS, some RRC parameters may be introduced.
[0291] An RRC parameter (e.g., DL-SPSconfig-index) may be introduced to indicate the index of the SPS configuration. The RRC parameter (e.g., DL-SPSconfig-index) may be included in each RRC configuration of the SPS (e.g., SPS-Config IE). The value of the RRC parameter (e.g., DL-SPSconfig-index) may be 0, 1, 2, ..., maxNrofSPSconfig-2, or maxNrofSPSconfig-1. maxNrofSPSconfig is the maximum number of SPS configurations, which may be 8 (12 or 16).
[0292] RRC parameters (e.g., DL-SPSconfig-ToAddModList) may be introduced to configure more than one DL SPS configuration. The RRC parameter (e.g., DL-SPSconfig-ToAddModList) may be a list or sequence of elements. The element here may be an SPS configuration (e.g., SPS-Config) or an equivalent mapping. The elements of the list or sequence may contain an identifier (INTEGER) (e.g., ElementId) that explicitly identifies the element when adding, modifying, and removing. The ElementId here may be an index (e.g., DL-SPSconfig-index) of the DL SPS configuration. For each element (e.g., SPS-Config) in the RRC parameter (e.g., DL-SPSconfig-ToAddModList), if the current UE configuration includes an element (e.g., SPS-Config) with a given ElementId (e.g., DL-SPSconfig-index), the UE modifies the configured element (e.g., SPS-Config) according to the received element, otherwise the UE adds the received element (e.g., SPS-Config) to the UE configuration. For example, if the UE receives an SPS configuration corresponding to an index, and the list in the UE configuration has an SPS configuration corresponding to the index, the UE updates the SPS configuration according to the received SPS configuration. If the UE receives an SPS configuration corresponding to an index, and the list in the UE configuration does not have an SPS configuration corresponding to the index, the UE adds the SPS configuration to the list and / or its configuration according to the received SPS configuration. The RRC parameter (e.g., DL-SPSconfig-ToAddModList) can be 1 to maxNrofSPSconfig of SPS-Config (e.g., 8, 12, 16).
[0293] An RRC parameter (e.g., DL-SPSconfig-ToReleaseList) may be introduced to release more than one DL SPS configuration. The RRC parameter (e.g., DL-SPSconfig-ToReleaseList) may be a list or sequence of ElementIds (e.g., DL-SPSconfig-index). For each ElementId (e.g., DL-SPSconfig-index) in the RRC parameter (e.g., DL-SPSconfig-ToReleaseList), if the current UE configuration includes an element (DL SPS configuration, e.g., SPS-Config) with a given ElementId (e.g., DL-SPSconfig-index), the UE releases the element (DL SPS configuration, e.g., SPS-Config) from the current UE configuration. For example, if the list includes an SPS configuration index and the current UE configuration includes an SPS configuration corresponding to the index, the UE releases the SPS configuration corresponding to the index.
[0294] In order to support the joint release and / or separate release of multiple SPS configurations, a DCI field (e.g., HPN field) in the release DCI (e.g., DCI format 1_0, DCI format 1_1, and / or DCI format 1_2) and / or a high-level configurable table (e.g., SPS configuration release table) and / or a fixed / default table can be used to indicate which SPS configuration or configurations are released. For example, an M (e.g., M<=4) bit indication in the release DCI is used to indicate which SPS configuration or configurations are released, wherein the association between each state indicated by the indication and the SPS configuration is a maximum of 2^M states that are configurable by the high level, wherein each state can be mapped to a single or multiple SPS configurations to be released. In the absence of a state configured by a high level, a separate release can be used, wherein the release corresponds to the SPS configuration index indicated by the indication. M can be determined by the bit length of the HPN field of each DCI format used to activate and release the SPS.
[0295] For example, a DCI field (e.g., SPS configuration index, which may reuse the HPN field) value m of the DCI may provide a row index m+1 for the allocated table. The determination of using the table may be defined below. The indexed row defines which SPS configuration or configurations are released.
[0296] The table (e.g., DL-SPSconfig-ReleaseStateList) can be a high-level configuration. The table can be UE-specific (e.g., DL-SPSconfig-ReleaseStateList in pdsch-Config) and / or commonly configured (e.g., DL-SPSconfig-ReleaseStateList in pdsch-ConfigCommon). The table (e.g., DL-SPSconfig-ReleaseStateList) can be a list / sequence of SPS configuration index sets (e.g., DL-SPSconfig-ReleaseState). Each SPS configuration index set may include one or more SPS configuration indexes that can be released. The SPS configuration index set may be empty, which means that the SPS configuration will not be released. An example of an RRC configured table is shown in List 2. The maximum number of entries in the table / sequence / list (e.g., maxNrofDL-SPS-ReleaseState) can be 16 or can depend on the number of bits in the DCI field (e.g., SPS configuration index).
[0297]
[0298] List 2
[0299] This table may be fixed in the specification. For example, one or more default tables may be applied to the joint and / or individual release of multiple SPS configurations. Some examples are shown in Table 5, Table 6 and Table 7.
[0300]
[0301]
[0302] Table 5
[0303] Row Index SPS Configuration Index Set 1 0 2 1 3 2 4 3 5 4 6 5 7 6 8 7 9 8 10 9 11 10 12 11 13 12 14 13 15 14 16 15
[0304] Table 6
[0305]
[0306]
[0307] Table 7
[0308] In some examples, more than one table to be used for SPS configuration release may be defined and / or configured. In the case of more than one table (e.g., an SPS configuration release table, including an RRC configuration table and / or a default table), and / or the determination of a table to be used for SPS configuration release, it may depend on the DCI format used to release the DCI, the RRC configuration (e.g., whether a UE-specific table and / or a common configuration table is configured), the PDCCH search space in which the UE detects the release DCI, and / or the CORESET in which the UE detects the release DCI.
[0309] For example, if there is no RRC configured table (e.g., if a parameter for indicating a table is not configured (e.g., a value for a parameter for indicating a table is not configured)), a default table (e.g., Table 5, Table 6, Table 7, or any table specified in the specification) may be applied to joint / individual SPS configuration release. For another example, if there is no RRC configured table, joint release of multiple SPS configurations may not be supported. For example, only individual release may be supported (e.g., releasing one SPS configuration only by using a single DCI format to release the DCI in a certain timing). Each value in a DCI field (e.g., an SPS configuration index) may have a one-to-one mapping with an SPS configuration that can be released. For example, a DCI field (e.g., an SPS configuration index) value m of a DCI may indicate that an SPS configuration with index m can be released.
[0310] For example, if a UE-specific RRC table (e.g., DL-SPSconfig-ReleaseStateList in pdsch-Config) is configured for the UE and the UE detects a release DCI in a UE-specific search space (e.g., DCI format 1_2, DCI format 1_1, and / or DCI format 1_0), the UE-specific RRC table (e.g., DL-SPSconfig-ReleaseStateList in pdsch-Config) may be applied (e.g., always applied) to the joint / individual SPS configuration release (e.g., regardless of whether other tables (e.g., DL-SPSconfig-ReleaseStateList in pdsch-ConfigCommon and / or any default tables)) may be configured and / or provided.
[0311] For example, if a common RRC table (e.g., DL-SPSconfig-ReleaseStateList in pdsch-ConfigCommon) is configured (e.g., and there is no UE-specific RRC table for the UE (e.g., DL-SPSconfig-ReleaseStateList in pdsch-Config)), then the common RRC table (e.g., DL-SPSconfig-ReleaseStateList in pdsch-ConfigCommon) may be applied for joint / individual SPS configuration release. For example, if a common RRC table and a UE-specific RRC table are configured, the UE may apply the UE-specific RRC table to be used for CG configuration release. For example, if a common RRC table and a UE-specific RRC table are configured for the UE, the UE-specific RRC table (e.g., the configuration of the UE-specific RRC table) may overwrite the common RRC table (e.g., the configuration of the common RRC table).
[0312] For example, if the UE detects a release DCI (e.g., DCI format 1_2, DCI format 1_1, and / or DCI format 1_0) in a common search space associated with CORESET 0 (e.g., and / or a common search space not associated with CORESET 0), a default table (e.g., Table 5, Table 6, Table 7, or any table specified in (e.g., defined by) the specification) may be applied for joint / individual SPS configuration release. For another example, if the UE detects a release DCI (e.g., DCI format 1_2, DCI format 1_1, and / or DCI format 1_0) in a common search space associated with CORESET 0 (e.g., and / or a common search space not associated with CORESET 0), joint release of multiple SPS configurations may not be supported. For example, only individual release may be supported. Each value in a DCI field (e.g., an SPS configuration index) may have a one-to-one mapping with an SPS configuration that can be released. For example, a DCI field (eg, SPS configuration index) value m of the DCI may indicate that the SPS configuration with index m can be released.
[0313] Another example is shown in Table 8. As shown in Table 8, the UE may determine the table to be applied for the SPS configuration release (e.g., from a default table, a common RRC table, and / or a UE-specific RRC table). For example, as described above, the UE may determine the table (e.g., from a default table, a common RRC table, and / or a UE-specific RRC table) based on the DCI format of the release DCI, the RRC configuration (e.g., whether the UE-specific RRC table is configured and / or whether the common RRC table is configured), the PDCCH search space of the DCI format for the release DCI detected by the UE, and / or the CORESET of the DCI format for the release DCI detected by the UE (e.g., the index of the CORESET).
[0314]
[0315]
[0316] Table 8
[0317] If the released DCI is a fallback DCI (e.g., DCI format 1_0), there may be no DCI field (e.g., SPS configuration index) to indicate which SPS configuration is released, and some fallback behaviors may be described here. For example, if the UE detects DCI format 1_0 for SPS configuration release, the UE may release all SPS configurations (e.g., all SPS configurations). As another example, if the UE detects DCI format 1_0 for SPS configuration release, the UE may release a specific configuration (e.g., a specific SPS configuration) and / or a default configuration (e.g., a default SPS configuration). For example, if the UE detects DCI format 1_0 for SPS configuration release, the UE may release an SPS configuration with a predetermined index (e.g., an SPS configuration with index "0" (e.g., as a specific SPS configuration and / or a default SPS configuration)). Additionally or alternatively, if the UE detects DCI format 1_0 for SPS configuration release, the UE may release the SPS configuration with the lowest index (e.g., the minimum index). For example, in a case where an SPS configuration with an index of "1", an SPS configuration with an index of "3", and an SPS configuration with an index of "5" are configured, and if the UE detects DCI format 1_0 for SPS configuration release, the UE may release the SPS configuration with "1". Additionally or alternatively, if the UE detects DCI format 1_0 for SPS configuration release, the UE may release the SPS configuration with the highest index (e.g., the maximum index). For example, in a case where an SPS configuration with an index of "1", an SPS configuration with an index of "3", and an SPS configuration with an index of "5" are configured, and if the UE detects DCI format 0_0 for SPS configuration release, the UE may release the SPS configuration with "5". In some examples, a specific configuration and / or a default configuration may be defined by a specification and known information between the gNB and the UE. For example, for detection of DCI format 0_0 for SPS configuration release, the UE may determine which SPS configuration to release based on the index of the SPS configuration (e.g., configured by the gNB). As another example, if multiple SPS configurations are configured, it may not be desirable for the UE to receive DCI format 1_0 for SPS configuration release.
[0318] Additionally or alternatively, if the UE detects DCI format 1_0 for SPS configuration in the CSS, the UE may release all SPS configurations (e.g., all SPS configurations). For another example, if the UE detects DCI format 1_0 for SPS configuration release in the CSS, the UE may release a specific configuration (e.g., a specific SPS configuration) and / or a default configuration (e.g., a default SPS configuration). For example, if the UE detects DCI format 1_0 for SPS configuration release in the CSS, the UE may release an SPS configuration with a predetermined index (e.g., an SPS configuration with index "0" (e.g., as a specific SPS configuration and / or a default SPS configuration)). Additionally or alternatively, if the UE detects DCI format 1_0 for SPS configuration release in the CSS, the UE may release an SPS configuration with the lowest index (e.g., the minimum index). For example, in a case where an SPS configuration with an index of "1", an SPS configuration with an index of "3", and an SPS configuration with an index of "5" are configured, and if the UE detects DCI format 1_0 for SPS configuration release in the CSS, the UE may release the SPS configuration with "1". Additionally or alternatively, if the UE detects DCI format 1_0 for SPS configuration release in the CSS, the UE may release the SPS configuration with the highest index (e.g., the maximum index). For example, in a case where an SPS configuration with an index of "1", an SPS configuration with an index of "3", and an SPS configuration with an index of "5" are configured, and if the UE detects DCI format 1_0 for SPS configuration release in the CSS, the UE may release the SPS configuration with "5". For example, for DCI format 1_0 for SPS configuration release detected in the CSS, the UE may determine which SPS configuration to release based on the index of the SPS configuration (e.g., configured by the gNB).
[0319] Additionally or alternatively, if the UE detects DCI format 1_0 for SPS configuration release in the CSS associated with CORESET#0, the UE may release all SPS configurations (e.g., all SPS configurations). For another example, if the UE detects DCI format 1_0 for SPS configuration release in the CSS associated with CORESET#0, the UE may release a specific configuration (e.g., a specific SPS configuration) and / or a default configuration (e.g., a default SPS configuration). For example, if the UE detects DCI format 1_0 for SPS configuration release in the CSS associated with CORESET#0, the UE may release an SPS configuration with a predetermined index (e.g., an SPS configuration with index "0" (e.g., as a specific SPS configuration and / or a default SPS configuration)). Additionally or alternatively, if the UE detects DCI format 1_0 for SPS configuration release in the CSS associated with CORESET#0, the UE may release an SPS configuration with the lowest index (e.g., the minimum index). For example, in a case where an SPS configuration with an index of "1", an SPS configuration with an index of "3", and an SPS configuration with an index of "5" are configured, and if the UE detects DCI format 1_0 for SPS configuration release in the CSS associated with CORESET#0, the UE may release the SPS configuration with "1". Additionally or alternatively, if the UE detects DCI format 1_0 for SPS configuration release in the CSS associated with CORESET#0, the UE may release the SPS configuration with the highest index (e.g., the largest index). For example, in a case where an SPS configuration with an index of "1", an SPS configuration with an index of "3", and an SPS configuration with an index of "5" are configured, and if the UE detects DCI format 1_0 for SPS configuration release in the CSS associated with CORESET#0, the UE may release the SPS configuration with "5". For example, for DCI format 1_0 for SPS configuration release detected in the CSS associated with CORESET#0, the UE may determine which SPS configuration to release based on the index of the SPS configuration (e.g., configured by the gNB).
[0320] This document describes an example of PDCCH verification for grant type 2 configured for DL SPS and UL. If the CRC of the corresponding DCI format (e.g., DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 1_0, DCI format 1_1, and / or DCI format 0_2) is scrambled using the CS-RNTI provided by the cs-RNTI, and the new data indicator (NDI) field for the enabled transport block is set to "0", the UE can verify the DL SPS allocation PDCCH or the configured UL grant type 2 PDCCH for scheduling activation or scheduling release. If all fields of the DCI format are set according to predefined rules, verification of the DCI format (e.g., DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 1_0, DCI format 1_1, and / or DCI format 0_2) is implemented (e.g., a special field in the DCI format can be set to a specific value for DL SPS and UL grant type 2 scheduling activation PDCCH verification and / or scheduling release PDCCH verification). If verification is implemented, the UE regards the information in the DCI format as a valid activation or valid release of the DL SPS or the configured UL grant type 2. If verification is not implemented, the UE shall discard all information in the DCI format. For example, if the HARQ process number field in the DCI format is set to "0" and / or the redundancy version (RV) field in the DCI format is set to "00", the UE may regard the information in the DCI format as a valid activation of the DL SPS or the configured UL grant type 2. In the case of supporting multiple configurations (multiple SPS configurations and / or CG configurations), the configuration index field in the DCI format may be used to indicate which SPS configuration or configurations and / or CG configurations are activated. For example, if the HARQ process number field in the DCI format is set to all "0", and / or the redundancy version field in the DCI format is set to "00", and / or the modulation and coding scheme field in the DCI format is set to all "1", and / or the frequency domain resource allocation is set to all "1", the UE may regard the information in the DCI format as a valid release of the DL SPS or the configured UL grant type 2. When multiple configurations (multiple SPS configurations and / or CG configurations) are supported, the configuration index field in the DCI format may be used to indicate which SPS configuration(s) and / or CG configuration(s) are released / deactivated.
[0321] As described above, the HPN field in the DCI format may be reused to indicate which SPS configuration(s) and / or CG configuration(s) are activated and / or released / deactivated. In this case, the HPN field in the DCI format may not be used for DL SPS and UL grant type 2 scheduling activation PDCCH verification and / or scheduling release PDCCH verification. In some examples, only the RV field may be used for DL SPS and UL grant type 2 scheduling activation PDCCH verification. An example of a special field for DL SPS and UL grant type 2 scheduling activation PDCCH verification is shown in Table 9. An example of a special field for DL SPS and UL grant type 2 scheduling release PDCCH verification is shown in Table 10.
[0322]
[0323] Table 9
[0324]
[0325] Table 10
[0326] In some examples, using only a 2-bit RV field for DL SPS and UL grant type 2 scheduling activation PDCCH confirmation may be unreliable. In some examples, a new DCI field (e.g., verification) may be introduced for DL SPS and UL grant type 2 scheduling activation PDCCH verification and / or scheduling release PDCCH verification. The number of bits in the DCI field (e.g., verification) may be configurable or fixed. The number of bits in the DCI field (e.g., verification) may be 1, 2, 3, or 4. For DL SPS and UL grant type 2 scheduling activation PDCCH verification and / or scheduling release PDCCH verification, the DCI field (e.g., verification) may be set to all "0" or all "1".
[0327] In some examples, existing fields or portions of existing fields in a DCI format (e.g., DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 1_0, DCI format 1_1, and / or DCI format 0_2) may be reused for DLSPS and UL grant type 2 scheduling activation PDCCH verification and / or scheduling release PDCCH verification. These existing fields may be antenna port, transmission configuration indication, rate matching indicator, SRS request, PRB bundling size indicator, carrier indicator, CSI request, ZP CSI-RS trigger, beta offset indicator, SRS resource indicator, repetition factor, priority indication, frequency domain resource allocation, time domain resource allocation, frequency hopping flag, TPC command, padding bit, UL / SUL indicator, precoding information and number of layers, CBG transmission information (CBGTI), PTRS-DMRS association, DMRS sequence initialization, UL-SCH indicator, CBG clearing information (CBGFI) and / or any other field in the DCI format (e.g., DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 1_0, DCI format 1_1 and / or DCI format 0_2). For DL SPS and UL grant type 2 scheduling activation PDCCH verification and / or scheduling release PDCCH verification, the reused DCI field or the reused bit of the DCI field may be set to all "0" or all "1".
[0328] In some examples of introducing and / or utilizing a new UL DCI format (e.g., DCI format 0_2), the UE may detect the new UL DCI format for different purposes. For example, the UE may detect a new UL DCI format for dynamic grants (e.g., DCI format 0_2 with CRC scrambled by C-RNTI). Additionally or alternatively, the UE may detect a new UL DCI format for grant type 2 for activation and / or release configuration (e.g., DCI format 0_2 with CRC scrambled by CS-RNTI and NDI=0). Additionally or alternatively, the UE may detect a new UL DCI format for grants of retransmission configuration (e.g., DCI format 0_2 with CRC scrambled by CS-RNTI and NDI=1). The new UL DCI format with CRC scrambled by CS-RNTI (e.g., DCI format 0_2) and the new UL DCI format with CRC scrambled by C-RNTI (e.g., DCI format 0_2) may have the same total DCI size.
[0329] For PUSCH transmissions corresponding to a configured grant (e.g., CG type 2 activated by DCI format 0_2), the parameters applied to the transmission may be provided by configuredGrantConfig, in addition to dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, scaling of UCI-OnPUSCH which may be provided by pusch-Config. If the UE has TransformCrecoder in configuredGrantConfig, the UE may apply the higher layer parameter tp-pi2BPSK (if provided in PUSCH-config) according to the procedure for PUSCH transmissions corresponding to the configured grant. If the time domain resource allocation (TDRA) table is RRC configured for DCI format 0_2 (e.g., PUSCH-TimeDomainResourceAllocationList-ForDCIformat0_2 in pusch-Config), the TDRA table may also be applied to CG type 2 activated by DCI format 0_2.
[0330] Retransmissions of PUSCH scheduled by a new UL DCI format (e.g., DCI format 0_2) with a CRC scrambled by CS-RNTI with NDI=1 may follow the same higher layer configuration defined for dynamic PUSCH transmissions associated with the new UL DCI format (e.g., DCI format 0_2). In some examples, for PUSCH retransmissions scheduled by a PDCCH (e.g., DCI format 0_2) with a CRC scrambled by CS-RNTI with NDI=1, the parameters in pusch-Config may be applied to PUSCH transmissions in addition to the configured grant-specific P0 (e.g., p0-NominalWithoutGrant in the PUSCH-PowerControl information element, and / or p0-PUSCH-Alpha, powerControlLoopToUse, mcs-Table, and / or mcs-TableTransformPrecoder in ConfiguredGrantConfig, and / or pathlossReferenceIndex in rrc-ConfiguredUplinkGrant).
[0331] Figure 7 Various components that may be used in a UE 702 are shown. Figure 7 The UE 702 described may be based on the combination of Figure 1102 described herein. The UE 702 includes a processor 703 that controls the operation of the UE 702. The processor 703 may also be referred to as a central processing unit (CPU). The memory 705 (which may include a read-only memory (ROM), a random access memory (RAM), a combination of these two memories, or any type of device that can store information) provides instructions 707a and data 709a to the processor 703. A portion of the memory 705 may also include a non-volatile random access memory (NVRAM). The instructions 707b and data 709b may also reside in the processor 703. The instructions 707b and / or data 709b loaded into the processor 703 may also include instructions 707a and / or data 709a from the memory 705 and loaded for execution or processing by the processor 703. The instructions 707b may be executed by the processor 703 to implement the method described herein.
[0332] The UE 702 may also include a housing that houses one or more transmitters 758 and one or more receivers 720 to allow transmission and reception of data. The transmitters 758 and receivers 720 may be combined into one or more transceivers 718. One or more antennas 722a-n are attached to the housing and electrically coupled to the transceiver 718.
[0333] The various components of the UE 702 are coupled together via a bus system 711 (which may include a power bus, a control signal bus, and a status signal bus in addition to a data bus). However, for the sake of clarity, the various buses are described in detail in the following sections. Figure 7 702 is shown as bus system 711. UE 702 may also include a digital signal processor (DSP) 713 for processing signals. UE 702 may also include a communication interface 715 that provides user access to the functions of UE 702. Figure 7 The UE 702 is shown as a functional block diagram rather than a listing of specific components.
[0334] Figure 8 Various components that may be used in gNB 860 are shown. Figure 8 The gNB 860 described may be configured in accordance with the Figure 1The gNB 860 described herein is implemented by the gNB 160. The gNB 860 includes a processor 803 that controls the operation of the gNB 860. The processor 803 may also be referred to as a central processing unit (CPU). The memory 805 (which may include a read-only memory (ROM), a random access memory (RAM), a combination of the two memories, or any type of device that can store information) provides instructions 807a and data 809a to the processor 803. A portion of the memory 805 may also include a non-volatile random access memory (NVRAM). Instructions 807b and data 809b may also reside in the processor 803. The instructions 807b and / or data 809b loaded into the processor 803 may also include instructions 807a and / or data 809a from the memory 805 and loaded for execution or processing by the processor 803. The instructions 807b may be executed by the processor 803 to implement the method described herein.
[0335] The gNB 860 may also include a housing that houses one or more transmitters 817 and one or more receivers 878 to allow transmission and reception of data. The transmitters 817 and receivers 878 may be combined into one or more transceivers 876. One or more antennas 880a-n are attached to the housing and electrically coupled to the transceiver 876.
[0336] The various components of gNB 860 are coupled together via bus system 811 (which may include a power bus, a control signal bus, and a status signal bus in addition to a data bus). However, for the sake of clarity, the various buses are described in detail in the following sections. Figure 8 860 is shown as bus system 811. gNB 860 may also include a digital signal processor (DSP) 813 for processing signals. gNB 860 may also include a communication interface 815 that provides user access to the functions of gNB 860. Figure 8 The gNB 860 shown is a functional block diagram rather than a listing of specific components.
[0337] Fig. 9 9 is a block diagram illustrating one embodiment of a UE 902 in which one or more of the systems and / or methods described herein may be implemented. The UE 902 includes a transmission device 958, a reception device 920, and a control device 924. The transmission device 958, the reception device 920, and the control device 924 may be configured to perform one or more of the functions described above. Figure 7 Shows Fig. 9 This is an example of a specific device structure of . Various other structures can be implemented to achieve one or more of the functions described herein. For example, the DSP can be implemented by software.
[0338] Fig.101 is a block diagram illustrating one embodiment of a gNB 1060 in which one or more of the systems and / or methods described herein may be implemented. The gNB 1060 includes a transmission device 1017, a reception device 1078, and a control device 1082. The transmission device 1017, the reception device 1078, and the control device 1082 may be configured to perform one or more of the functions described above. Figure 8 Shows Fig.10 This is an example of a specific device structure of . Various other structures can be implemented to achieve one or more of the functions described herein. For example, the DSP can be implemented by software.
[0339] Fig.11 is a block diagram illustrating a specific implementation of gNB 1160. gNB 1160 may be combined with Figure 1 An example of a gNB 160 is described. The gNB 1160 may include a higher layer processor 1123, a DL transmitter 1125, a UL receiver 1133, and one or more antennas 1131. The DL transmitter 1125 may include a PDCCH transmitter 1127 and a PDSCH transmitter 1129. The UL receiver 1133 may include a PUCCH receiver 1135 and a PUSCH receiver 1137.
[0340] The high-level processor 1123 may manage the behavior of the physical layer (the behavior of the DL transmitter and the UL receiver) and provide high-level parameters to the physical layer. The high-level processor 1123 may obtain a transport block from the physical layer. The high-level processor 1123 may send / obtain high-level messages such as RRC messages and MAC messages to / from the high-level layer of the UE. The high-level processor 1123 may provide a transport block to the PDSCH transmitter and provide a transmission parameter related to the transport block to the PDCCH transmitter.
[0341] The DL transmitter 1125 may multiplex downlink physical channels and downlink physical signals (including reserved signals) and transmit them via the transmit antenna 1131. The UL receiver 1133 may receive and demultiplex the multiplexed uplink physical channels and uplink physical signals via the receive antenna 1131. The PUCCH receiver 1135 may provide UCI to the higher layer processor 1123. The PUSCH receiver 1137 may provide the received transport block to the higher layer processor 1123.
[0342] Fig.12 1 is a block diagram showing a specific implementation of UE 1202. UE 1202 may be combined with Figure 1An example of a UE 102 is described. The UE 1202 may include a higher layer processor 1223, a UL transmitter 1251, a DL receiver 1243, and one or more antennas 1231. The UL transmitter 1251 may include a PUCCH transmitter 1253 and a PUSCH transmitter 1255. The DL receiver 1243 may include a PDCCH receiver 1245 and a PDSCH receiver 1247.
[0343] The high-level processor 1223 may manage the behavior of the physical layer (the behavior of the DL transmitter and the UL receiver) and provide high-level parameters to the physical layer. The high-level processor 1223 may obtain a transport block from the physical layer. The high-level processor 1223 may send / obtain high-level messages such as RRC messages and MAC messages to / from the high-level of the UE. The high-level processor 1223 may provide a transport block to the PUSCH transmitter and provide UCI to the PUCCH transmitter 1253.
[0344] The DL receiver 1243 may receive and demultiplex the multiplexed downlink physical channel and the downlink physical signal via the reception antenna 1231. The PDCCH receiver 1245 may provide the DCI to the higher layer processor 1223. The PDSCH receiver 1247 may provide the higher layer processor 1223 with the received transport block.
[0345] As described above, some methods for DL and / or UL transmissions may be applied (e.g., specified). In some examples, a combination of one or more of the methods described herein or their functions may be applied to DL and / or UL transmissions. The systems and methods may not exclude a combination of one or more of the methods described herein or their functions.
[0346] It should be noted that the names of the physical channels described herein are examples. Other names may be used, such as "NRPDCCH, NRPDSCH, NRPUCCH, and NRPUSCH," "new generation (G) PDCCH, GPDSCH, GPUCCH, and GPUSCH," etc.
[0347] The term "computer-readable medium" refers to any available medium that can be accessed by a computer or processor. As used herein, the term "computer-readable medium" may refer to a non-transitory and tangible computer-readable medium and / or a processor-readable medium. By way of example, and not limitation, a computer-readable medium or a processor-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and that can be accessed by a computer or processor. As used herein, disks and optical disks include compact disks (CDs), laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks. Optical disks, where magnetic disks usually reproduce data magnetically, optical disks reproduce data optically using lasers.
[0348] It should be noted that one or more of the methods described herein may be implemented in hardware and / or performed using hardware. For example, one or more of the methods described herein may be implemented in and / or performed using a chipset, an application specific integrated circuit (ASIC), a large scale integrated circuit (LSI), or an integrated circuit, etc.
[0349] Each of the methods disclosed herein includes one or more steps or actions for implementing the method. These method steps and / or actions may be interchangeable with each other and / or combined into a single step without departing from the scope of the claims. In other words, unless a specific order of steps or actions is required for the correct operation of the method, the order and / or use of specific steps and / or actions may be modified without departing from the scope of the claims.
[0350] It is to be understood that the claims are not limited to the precise configuration and components shown above. Various modifications, changes and variations may be made in the arrangement, operation and details of the systems, methods, and apparatus described herein without departing from the scope of the claims.
[0351] The program running on the gNB 160 or UE 102 according to the system and method is a program that controls the CPU, etc. in a manner that implements the functions according to the system and method (a program that causes the computer to operate). Then, the information processed in these devices is temporarily stored in the RAM while being processed. Subsequently, the information is stored in various ROMs or HDDs, and is read by the CPU whenever necessary for modification or writing. As a recording medium on which the program is stored, any of a semiconductor (e.g., ROM, nonvolatile memory card, etc.), an optical storage medium (e.g., DVD, MO, MD, CD, BD, etc.), a magnetic storage medium (e.g., a magnetic tape, a floppy disk, etc.), etc. is possible. In addition, in some cases, the functions according to the system and method described herein are implemented by running the loaded program, and in addition, the functions according to the system and method are implemented based on instructions from the program and in combination with an operating system or other application programs.
[0352] In addition, in the case where the program is available on the market, the program stored on a portable recording medium may be distributed, or the program may be transferred to a server computer connected via a network such as the Internet. In this case, a storage device in the server computer is also included. In addition, some or all of the gNB 160 and UE 102 according to the systems and methods described herein may be implemented as LSI as an integrated circuit. Each functional block of the gNB 160 and UE 102 may be built into a chip separately, and some or all of the functional blocks may be integrated into a chip. In addition, the technology of the integrated circuit is not limited to LSI, and the integrated circuit for the functional block may be implemented using a dedicated circuit or a general-purpose processor. In addition, if an integrated circuit technology that replaces LSI emerges as semiconductor technology continues to advance, an integrated circuit applying the technology may also be used.
[0353] In addition, each functional block or various features of the base station equipment and terminal equipment used in each of the above-mentioned embodiments can be realized or executed by a circuit (usually an integrated circuit or multiple integrated circuits). The circuit designed to perform the functions described in this specification may include a general-purpose processor, a digital signal processor (DSP), a dedicated or general-purpose integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices or discrete hardware components or a combination thereof. The general-purpose processor can be a microprocessor, or alternatively, the processor can be a conventional processor, a controller, a microcontroller or a state machine. The general-purpose processor or each circuit described herein can be configured by a digital circuit, or can be configured by an analog circuit. In addition, when the technology of making an integrated circuit replacing the current integrated circuit appears due to the progress of semiconductor technology, the integrated circuit produced by the technology can also be used.
[0354] As used herein, the term "and / or" should be interpreted as meaning one or more items. For example, the phrase "A, B, and / or C" should be interpreted as meaning any of the following: only A, only B, only C, A and B (but not C), B and C (but not A), A and C (but not B), or all of A, B, and C. As used herein, the phrase "at least one" should be interpreted as meaning one or more items. For example, the phrase "at least one of A, B, and C" or the phrase "at least one of A, B, or C" should be interpreted as meaning any of the following: only A, only B, only C, A and B (but not C), B and C (but not A), A and C (but not B), or all of A, B, and C. As used herein, the phrase "one or more" should be understood to refer to one or more items. For example, the phrase "one or more of A, B, and C" or the phrase "one or more of A, B, or C" should be interpreted to mean any of the following: only A, only B, only C, A and B (but not C), B and C (but not A), A and C (but not B), or all of A, B, and C.
[0355] <Cross Reference>
[0356] This nonprovisional application claims priority under 35 U.S.C. 119 to provisional application No. 62 / 932,408, filed on November 7, 2019, the entire contents of which are hereby incorporated by reference.
Claims
1. A user equipment UE communicating with a base station, the UE comprising: A receiving circuit configured to receive a radio resource control RRC message, the RRC message comprising first information for configuring more than one configured authorized CG physical uplink shared channel PUSCH configuration, the more than one CG PUSCH configuration comprising respective configuration indexes, wherein The receiving circuit is configured to receive an RRC configuration for configuring second information, the second information indicating a list for CGPUSCH configuration release, and The receiving circuit is configured to detect a physical downlink control channel PDCCH for a downlink control information DCI format having a cyclic redundancy check CRC scrambled by a first radio network temporary identifier RNTI, the DCI format being used to activate or deactivate at least one of the more than one CG PUSCH configurations; a processing circuit configured to determine whether the DCI based on the DCI format is a first DCI including third information or a second DCI including fourth information, the third information being used to indicate activation of at least one of the more than one CG PUSCH configurations, and the fourth information being used to indicate release of at least one of the more than one CG PUSCH configurations; as well as a transmission circuit configured to perform uplink data transmission on a CG PUSCH based on the at least one of the more than one CG PUSCH configurations based on the detection of the first DCI, wherein: The processing circuit is configured to release the at least one CG PUSCH configuration among the more than one CG PUSCH configurations based on detection of the second DCI, the at least one of the more than one CG PUSCH configurations being determined based on the second DCI and the second information, the index of the one or more CG PUSCH configurations released in the list being given by the second DCI, The third information includes a redundancy version field set to all "0" and a HARQ process number field for indicating which CG PUSCH configuration or configurations are activated, The fourth information includes a redundancy version field set to all "0", a modulation and coding scheme field set to all "1", and a HARQ process number field for indicating which CG PUSCH configuration or configurations are released. The third information further includes a plurality of fields, each of the plurality of fields is neither the redundancy version field nor the HARQ process number field, and The redundancy version field is set to all "0", and a plurality of fields are used for verification of the activated PDCCH.
2. A base station for communicating with a user equipment UE, the base station comprising: A transmission circuit configured to transmit a radio resource control RRC message, the RRC message comprising first information for configuring more than one configured authorized CG physical uplink shared channel PUSCH configuration, the more than one CG PUSCH configuration comprising respective configuration indexes, wherein The transmission circuit is configured to transmit an RRC configuration for configuring second information, wherein the second information indicates a list for CGPUSCH configuration release, and The transmission circuit is configured to transmit a physical downlink control channel PDCCH for downlink control information DCI format, the DCI format having a cyclic redundancy check CRC scrambled by a first radio network temporary identifier RNTI, the DCI format being used to activate or deactivate at least one of the more than one CG PUSCH configurations; a receiving circuit configured to, after transmitting a first DCI generated based on the DCI format and including third information for indicating activation of at least one of the more than one CG PUSCH configurations, receive uplink data transmission on a CG PUSCH based on the at least one of the more than one CG PUSCH configurations, wherein The transmission circuit is configured to transmit a second DCI generated based on the DCI format and including fourth information for indicating the release of at least one of the more than one CG PUSCH configurations, the fourth information being information for causing the UE to release the at least one of the more than one CG PUSCH configurations, the at least one of the more than one CG PUSCH configurations being determined based on the second DCI and the second information, the indexes of the one or more CG PUSCH configurations released in the list being given by the second DCI, wherein The third information includes a redundancy version field set to all "0" and a HARQ process number field for indicating which CG PUSCH configuration or configurations are activated, The fourth information includes a redundancy version field set to all "0", a modulation and coding scheme field set to all "1", and a HARQ process number field for indicating which CG PUSCH configuration or configurations are released. The third information further includes a plurality of fields, each of the plurality of fields is neither the redundancy version field nor the HARQ process number field, and The redundancy version field is set to all "0", and a plurality of fields are used for verification of the activated PDCCH.
3. A method performed by a user equipment UE communicating with a base station, the method comprising: A radio resource control (RRC) message is received, the RRC message comprising first information for configuring more than one configured authorized CG physical uplink shared channel (PUSCH) configuration, the more than one CG PUSCH configuration comprising respective configuration indexes, wherein receiving an RRC configuration for configuring second information, wherein the second information indicates a list for CG PUSCH configuration release, and detecting a physical downlink control channel (PDCCH) for a downlink control information (DCI) format having a cyclic redundancy check (CRC) scrambled by a first radio network temporary identifier (RNTI), the DCI format being used to activate or deactivate at least one of the more than one CG PUSCH configurations; determining whether the DCI based on the DCI format is a first DCI including third information or a second DCI including fourth information, wherein the third information is used to indicate activation of at least one of the more than one CG PUSCH configurations, and the fourth information is used to indicate release of at least one of the more than one CG PUSCH configurations; performing, based on the detection of the first DCI, uplink data transmission on the CG PUSCH based on the at least one of the more than one CG PUSCH configurations; and at least one of the more than one CG PUSCH configurations is released based on the detection of the second DCI, the at least one of the more than one CG PUSCH configurations is determined based on the second DCI and the second information, and the index of the one or more CG PUSCH configurations released in the list is given by the second DCI, wherein The third information includes a redundancy version field set to all "0" and a HARQ process number field for indicating which CG PUSCH configuration or configurations are activated, The fourth information includes a redundancy version field set to all "0", a modulation and coding scheme field set to all "1", and a HARQ process number field for indicating which CG PUSCH configuration or configurations are released. The third information further includes a plurality of fields, each of the plurality of fields is neither the redundancy version field nor the HARQ process number field, and The redundancy version field is set to all "0", and a plurality of fields are used for verification of the activated PDCCH.
