Patent Grant
11902994
Examples of several of the various embodiments of the present disclosure are described herein with reference to the drawings.
Example embodiments of the present disclosure enable handling resource conflict. Embodiments of the technology disclosed herein may be employed in the technical field of multicarrier communication systems. More particularly, the embodiments of the technology disclosed herein may relate to resource conflict handling in multicarrier communication systems.
The following Acronyms are used throughout the present disclosure:
Example embodiments of the disclosure may be implemented using various physical layer modulation and transmission mechanisms. Example transmission mechanisms may include, but are not limited to: Code Division Multiple Access (CDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Time Division Multiple Access (TDMA), Wavelet technologies, and/or the like. Hybrid transmission mechanisms such as TDMA/CDMA, and OFDM/CDMA may also be employed. Various modulation schemes may be applied for signal transmission in the physical layer. Examples of modulation schemes include, but are not limited to: phase, amplitude, code, a combination of these, and/or the like. An example radio transmission method may implement Quadrature Amplitude Modulation (QAM) using Binary Phase Shift Keying (BPSK), Quadrature Phase Shift Keying (QPSK), 16-QAM, 64-QAM, 256-QAM, and/or the like. Physical radio transmission may be enhanced by dynamically or semi-dynamically changing the modulation and coding scheme depending on transmission requirements and radio conditions.
A gNB or an ng-eNB may host functions such as: radio resource management and scheduling, IP header compression, encryption and integrity protection of data, selection of Access and Mobility Management Function (AMF) at User Equipment (UE) attachment, routing of user plane and control plane data, connection setup and release, scheduling and transmission of paging messages (originated from the AMF), scheduling and transmission of system broadcast information (originated from the AMF or Operation and Maintenance (O&M)), measurement and measurement reporting configuration, transport level packet marking in the uplink, session management, support of network slicing, Quality of Service (QoS) flow management and mapping to data radio bearers, support of UEs in RRC_INACTIVE state, distribution function for Non-Access Stratum (NAS) messages, RAN sharing, and dual connectivity or tight interworking between NR and E-UTRA.
In an example, one or more gNBs and/or one or more ng-eNBs may be interconnected with each other by means of Xn interface. A gNB or an ng-eNB may be connected by means of NG interfaces to 5G Core Network (5GC). In an example, 5GC may comprise one or more AMF/User Plan Function (UPF) functions (e.g. 130A or 130B). A gNB or an ng-eNB may be connected to a UPF by means of an NG-User plane (NG-U) interface. The NG-U interface may provide delivery (e.g. non-guaranteed delivery) of user plane Protocol Data Units (PDUs) between a RAN node and the UPF. A gNB or an ng-eNB may be connected to an AMF by means of an NG-Control plane (NG-C) interface. The NG-C interface may provide, for example, NG interface management, UE context management, UE mobility management, transport of NAS messages, paging, PDU session management, configuration transfer and/or warning message transmission, combinations thereof, and/or the like.
In an example, a UPF may host functions such as anchor point for intra-/inter-Radio Access Technology (RAT) mobility (when applicable), external PDU session point of interconnect to data network, packet routing and forwarding, packet inspection and user plane part of policy rule enforcement, traffic usage reporting, uplink classifier to support routing traffic flows to a data network, branching point to support multi-homed PDU session, QoS handling for user plane, e.g. packet filtering, gating, Uplink (UL)/Downlink (DL) rate enforcement, uplink traffic verification (e.g. Service Data Flow (SDF) to QoS flow mapping), downlink packet buffering and/or downlink data notification triggering.
In an example, an AMF may host functions such as NAS signaling termination, NAS signaling security, Access Stratum (AS) security control, inter Core Network (CN) node signaling for mobility between 3rd Generation Partnership Project (3GPP) access networks, idle mode UE reachability (e.g., control and execution of paging retransmission), registration area management, support of intra-system and inter-system mobility, access authentication, access authorization including check of roaming rights, mobility management control (subscription and policies), support of network slicing and/or Session Management Function (SMF) selection.
In an example, a base station may configure a plurality of logical channels for a wireless device. A logical channel in the plurality of logical channels may correspond to a radio bearer and the radio bearer may be associated with a QoS requirement. In an example, a base station may configure a logical channel to be mapped to one or more TTIs/numerologies in a plurality of TTIs/numerologies. The wireless device may receive a Downlink Control Information (DCI) via Physical Downlink Control CHannel (PDCCH) indicating an uplink grant. In an example, the uplink grant may be for a first TTI/numerology and may indicate uplink resources for transmission of a transport block. The base station may configure each logical channel in the plurality of logical channels with one or more parameters to be used by a logical channel prioritization procedure at the MAC layer of the wireless device. The one or more parameters may comprise priority, prioritized bit rate, etc. A logical channel in the plurality of logical channels may correspond to one or more buffers comprising data associated with the logical channel. The logical channel prioritization procedure may allocate the uplink resources to one or more first logical channels in the plurality of logical channels and/or one or more MAC Control Elements (CEs). The one or more first logical channels may be mapped to the first TTI/numerology. The MAC layer at the wireless device may multiplex one or more MAC CEs and/or one or more MAC SDUs (e.g., logical channel) in a MAC PDU (e.g., transport block). In an example, the MAC PDU may comprise a MAC header comprising a plurality of MAC sub-headers. A MAC sub-header in the plurality of MAC sub-headers may correspond to a MAC CE or a MAC SUD (logical channel) in the one or more MAC CEs and/or one or more MAC SDUs. In an example, a MAC CE or a logical channel may be configured with a Logical Channel IDentifier (LCID). In an example, LCID for a logical channel or a MAC CE may be fixed/pre-configured. In an example, LCID for a logical channel or MAC CE may be configured for the wireless device by the base station. The MAC sub-header corresponding to a MAC CE or a MAC SDU may comprise LCID associated with the MAC CE or the MAC SDU.
In an example, a base station may activate and/or deactivate and/or impact one or more processes (e.g., set values of one or more parameters of the one or more processes or start and/or stop one or more timers of the one or more processes) at the wireless device by employing one or more MAC commands. The one or more MAC commands may comprise one or more MAC control elements. In an example, the one or more processes may comprise activation and/or deactivation of PDCP packet duplication for one or more radio bearers. The base station may transmit a MAC CE comprising one or more fields, the values of the fields indicating activation and/or deactivation of PDCP duplication for the one or more radio bearers. In an example, the one or more processes may comprise Channel State Information (CSI) transmission of on one or more cells. The base station may transmit one or more MAC CEs indicating activation and/or deactivation of the CSI transmission on the one or more cells. In an example, the one or more processes may comprise activation or deactivation of one or more secondary cells. In an example, the base station may transmit a MA CE indicating activation or deactivation of one or more secondary cells. In an example, the base station may transmit one or more MAC CEs indicating starting and/or stopping one or more Discontinuous Reception (DRX) timers at the wireless device. In an example, the base station may transmit one or more MAC CEs indicating one or more timing advance values for one or more Timing Advance Groups (TAGs).
A base station may comprise many sectors for example: 1, 2, 3, 4, or 6 sectors. A base station may comprise many cells, for example, ranging from 1 to 50 cells or more. A cell may be categorized, for example, as a primary cell or secondary cell. At Radio Resource Control (RRC) connection establishment/re-establishment/handover, one serving cell may provide the NAS (non-access stratum) mobility information (e.g. Tracking Area Identifier (TAI)). At RRC connection re-establishment/handover, one serving cell may provide the security input. This cell may be referred to as the Primary Cell (PCell). In the downlink, a carrier corresponding to the PCell may be a DL Primary Component Carrier (PCC), while in the uplink, a carrier may be an UL PCC. Depending on wireless device capabilities, Secondary Cells (SCells) may be configured to form together with a PCell a set of serving cells. In a downlink, a carrier corresponding to an SCell may be a downlink secondary component carrier (DL SCC), while in an uplink, a carrier may be an uplink secondary component carrier (UL SCC). An SCell may or may not have an uplink carrier.
A cell, comprising a downlink carrier and optionally an uplink carrier, may be assigned a physical cell ID and a cell index. A carrier (downlink or uplink) may belong to one cell. The cell ID or cell index may also identify the downlink carrier or uplink carrier of the cell (depending on the context it is used). In the disclosure, a cell ID may be equally referred to a carrier ID, and a cell index may be referred to a carrier index. In an implementation, a physical cell ID or a cell index may be assigned to a cell. A cell ID may be determined using a synchronization signal transmitted on a downlink carrier. A cell index may be determined using RRC messages. For example, when the disclosure refers to a first physical cell ID for a first downlink carrier, the disclosure may mean the first physical cell ID is for a cell comprising the first downlink carrier. The same concept may apply to, for example, carrier activation. When the disclosure indicates that a first carrier is activated, the specification may equally mean that a cell comprising the first carrier is activated.
A base station may transmit to a wireless device one or more messages (e.g. RRC messages) comprising a plurality of configuration parameters for one or more cells. One or more cells may comprise at least one primary cell and at least one secondary cell. In an example, an RRC message may be broadcasted or unicasted to the wireless device. In an example, configuration parameters may comprise common parameters and dedicated parameters.
Services and/or functions of an RRC sublayer may comprise at least one of: broadcast of system information related to AS and NAS; paging initiated by 5GC and/or NG-RAN; establishment, maintenance, and/or release of an RRC connection between a wireless device and NG-RAN, which may comprise at least one of addition, modification and release of carrier aggregation; or addition, modification, and/or release of dual connectivity in NR or between E-UTRA and NR. Services and/or functions of an RRC sublayer may further comprise at least one of security functions comprising key management; establishment, configuration, maintenance, and/or release of Signaling Radio Bearers (SRBs) and/or Data Radio Bearers (DRBs); mobility functions which may comprise at least one of a handover (e.g. intra NR mobility or inter-RAT mobility) and a context transfer; or a wireless device cell selection and reselection and control of cell selection and reselection. Services and/or functions of an RRC sublayer may further comprise at least one of QoS management functions; a wireless device measurement configuration/reporting; detection of and/or recovery from radio link failure; or NAS message transfer to/from a core network entity (e.g. AMF, Mobility Management Entity (MME)) from/to the wireless device.
An RRC sublayer may support an RRC_Idle state, an RRC_Inactive state and/or an RRC_Connected state for a wireless device. In an RRC_Idle state, a wireless device may perform at least one of: Public Land Mobile Network (PLMN) selection; receiving broadcasted system information; cell selection/re-selection; monitoring/receiving a paging for mobile terminated data initiated by 5GC; paging for mobile terminated data area managed by 5GC; or DRX for CN paging configured via NAS. In an RRC_Inactive state, a wireless device may perform at least one of: receiving broadcasted system information; cell selection/re-selection; monitoring/receiving a RAN/CN paging initiated by NG-RAN/5GC; RAN-based notification area (RNA) managed by NG-RAN; or DRX for RAN/CN paging configured by NG-RAN/NAS. In an RRC_Idle state of a wireless device, a base station (e.g. NG-RAN) may keep a 5GC-NG-RAN connection (both C/U-planes) for the wireless device; and/or store a UE AS context for the wireless device. In an RRC_Connected state of a wireless device, a base station (e.g. NG-RAN) may perform at least one of: establishment of 5GC-NG-RAN connection (both C/U-planes) for the wireless device; storing a UE AS context for the wireless device; transmit/receive of unicast data to/from the wireless device; or network-controlled mobility based on measurement results received from the wireless device. In an RRC_Connected state of a wireless device, an NG-RAN may know a cell that the wireless device belongs to.
System information (SI) may be divided into minimum SI and other SI. The minimum SI may be periodically broadcast. The minimum SI may comprise basic information required for initial access and information for acquiring any other SI broadcast periodically or provisioned on-demand, i.e. scheduling information. The other SI may either be broadcast, or be provisioned in a dedicated manner, either triggered by a network or upon request from a wireless device. A minimum SI may be transmitted via two different downlink channels using different messages (e.g. MasterInforrnationBlock and SystemInformationBlockType1). Another SI may be transmitted via SystemInformationBlockType2. For a wireless device in an RRC_Connected state, dedicated RRC signaling may be employed for the request and delivery of the other SI. For the wireless device in the RRC_Idle state and/or the RRC_Inactive state, the request may trigger a random-access procedure.
A wireless device may report its radio access capability information which may be static. A base station may request what capabilities for a wireless device to report based on band information. When allowed by a network, a temporary capability restriction request may be sent by the wireless device to signal the limited availability of some capabilities (e.g. due to hardware sharing, interference, or overheating) to the base station. The base station may confirm or reject the request. The temporary capability restriction may be transparent to 5GC (e.g., static capabilities may be stored in 5GC).
When CA is configured, a wireless device may have an RRC connection with a network. At RRC connection establishment/re-establishment/handover procedure, one serving cell may provide NAS mobility information, and at RRC connection re-establishment/handover, one serving cell may provide a security input. This cell may be referred to as the PCell. Depending on the capabilities of the wireless device, SCells may be configured to form together with the PCell a set of serving cells. The configured set of serving cells for the wireless device may comprise one PCell and one or more SCells.
The reconfiguration, addition, and removal of SCells may be performed by RRC. At intra-NR handover, RRC may also add, remove, or reconfigure SCells for usage with the target PCell. When adding a new SCell, dedicated RRC signaling may be employed to send all required system information of the SCell i.e. while in connected mode, wireless devices may not need to acquire broadcasted system information directly from the SCells.
The purpose of an RRC connection reconfiguration procedure may be to modify an RRC connection, (e.g. to establish, modify and/or release RBs, to perform handover, to setup, modify, and/or release measurements, to add, modify, and/or release SCells and cell groups). As part of the RRC connection reconfiguration procedure, NAS dedicated information may be transferred from the network to the wireless device. The RRCConnectionReconfiguration message may be a command to modify an RRC connection. It may convey information for measurement configuration, mobility control, radio resource configuration (e.g. RBs, MAC main configuration and physical channel configuration) comprising any associated dedicated NAS information and security configuration. If the received RRC Connection Reconfiguration message includes the sCellToReleaseList, the wireless device may perform an SCell release. If the received RRC Connection Reconfiguration message includes the sCellToAddModList, the wireless device may perform SCell additions or modification.
An RRC connection establishment (or reestablishment, resume) procedure may be to establish (or reestablish, resume) an RRC connection. an RRC connection establishment procedure may comprise SRB1 establishment. The RRC connection establishment procedure may be used to transfer the initial NAS dedicated information/message from a wireless device to E-UTRAN. The RRCConnectionReestablishment message may be used to reestablish SRB1.
A measurement report procedure may be to transfer measurement results from a wireless device to NG-RAN. The wireless device may initiate a measurement report procedure after successful security activation. A measurement report message may be employed to transmit measurement results.
The wireless device 110 may comprise at least one communication interface 310 (e.g. a wireless modem, an antenna, and/or the like), at least one processor 314, and at least one set of program code instructions 316 stored in non-transitory memory 315 and executable by the at least one processor 314. The wireless device 110 may further comprise at least one of at least one speaker/microphone 311, at least one keypad 312, at least one display/touchpad 313, at least one power source 317, at least one global positioning system (GPS) chipset 318, and other peripherals 319.
The processor 314 of the wireless device 110, the processor 321A of the base station 1120A, and/or the processor 321B of the base station 2120B may comprise at least one of a general-purpose processor, a digital signal processor (DSP), a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) and/or other programmable logic device, discrete gate and/or transistor logic, discrete hardware components, and the like. The processor 314 of the wireless device 110, the processor 321A in base station 1120A, and/or the processor 321B in base station 2120B may perform at least one of signal coding/processing, data processing, power control, input/output processing, and/or any other functionality that may enable the wireless device 110, the base station 1120A and/or the base station 2120B to operate in a wireless environment.
The processor 314 of the wireless device 110 may be connected to the speaker/microphone 311, the keypad 312, and/or the display/touchpad 313. The processor 314 may receive user input data from and/or provide user output data to the speaker/microphone 311, the keypad 312, and/or the display/touchpad 313. The processor 314 in the wireless device 110 may receive power from the power source 317 and/or may be configured to distribute the power to the other components in the wireless device 110. The power source 317 may comprise at least one of one or more dry cell batteries, solar cells, fuel cells, and the like. The processor 314 may be connected to the GPS chipset 318. The GPS chipset 318 may be configured to provide geographic location information of the wireless device 110.
The processor 314 of the wireless device 110 may further be connected to other peripherals 319, which may comprise one or more software and/or hardware modules that provide additional features and/or functionalities. For example, the peripherals 319 may comprise at least one of an accelerometer, a satellite transceiver, a digital camera, a universal serial bus (USB) port, a hands-free headset, a frequency modulated (FM) radio unit, a media player, an Internet browser, and the like.
The communication interface 320A of the base station 1, 120A, and/or the communication interface 320B of the base station 2, 120B, may be configured to communicate with the communication interface 310 of the wireless device 110 via a wireless link 330A and/or a wireless link 330B respectively. In an example, the communication interface 320A of the base station 1, 120A, may communicate with the communication interface 320B of the base station 2 and other RAN and core network nodes.
The wireless link 330A and/or the wireless link 330B may comprise at least one of a bi-directional link and/or a directional link. The communication interface 310 of the wireless device 110 may be configured to communicate with the communication interface 320A of the base station 1120A and/or with the communication interface 320B of the base station 2120B. The base station 1120A and the wireless device 110 and/or the base station 2120B and the wireless device 110 may be configured to send and receive transport blocks via the wireless link 330A and/or via the wireless link 330B, respectively. The wireless link 330A and/or the wireless link 330B may employ at least one frequency carrier. According to some of various aspects of embodiments, transceiver(s) may be employed. A transceiver may be a device that comprises both a transmitter and a receiver. Transceivers may be employed in devices such as wireless devices, base stations, relay nodes, and/or the like. Example embodiments for radio technology implemented in the communication interface 310, 320A, 320B and the wireless link 330A, 330B are illustrated in
In an example, other nodes in a wireless network (e.g. AMF, UPF, SMF, etc.) may comprise one or more communication interfaces, one or more processors, and memory storing instructions.
A node (e.g. wireless device, base station, AMF, SMF, UPF, servers, switches, antennas, and/or the like) may comprise one or more processors, and memory storing instructions that when executed by the one or more processors causes the node to perform certain processes and/or functions. Example embodiments may enable operation of single-carrier and/or multi-carrier communications. Other example embodiments may comprise a non-transitory tangible computer readable media comprising instructions executable by one or more processors to cause operation of single-carrier and/or multi-carrier communications. Yet other example embodiments may comprise an article of manufacture that comprises a non-transitory tangible computer readable machine-accessible medium having instructions encoded thereon for enabling programmable hardware to cause a node to enable operation of single-carrier and/or multi-carrier communications. The node may include processors, memory, interfaces, and/or the like.
An interface may comprise at least one of a hardware interface, a firmware interface, a software interface, and/or a combination thereof. The hardware interface may comprise connectors, wires, electronic devices such as drivers, amplifiers, and/or the like. The software interface may comprise code stored in a memory device to implement protocol(s), protocol layers, communication drivers, device drivers, combinations thereof, and/or the like. The firmware interface may comprise a combination of embedded hardware and code stored in and/or in communication with a memory device to implement connections, electronic device operations, protocol(s), protocol layers, communication drivers, device drivers, hardware operations, combinations thereof, and/or the like.
An example structure for modulation and up-conversion to the carrier frequency of the complex-valued SC-FDMA or CP-OFDM baseband signal for an antenna port and/or the complex-valued Physical Random Access CHannel (PRACH) baseband signal is shown in
An example structure for downlink transmissions is shown in
In an example, a gNB may transmit a first symbol and a second symbol on an antenna port, to a wireless device. The wireless device may infer the channel (e.g., fading gain, multipath delay, etc.) for conveying the second symbol on the antenna port, from the channel for conveying the first symbol on the antenna port. In an example, a first antenna port and a second antenna port may be quasi co-located if one or more large-scale properties of the channel over which a first symbol on the first antenna port is conveyed may be inferred from the channel over which a second symbol on a second antenna port is conveyed. The one or more large-scale properties may comprise at least one of: delay spread; doppler spread; doppler shift; average gain; average delay; and/or spatial Receiving (Rx) parameters.
An example modulation and up-conversion to the carrier frequency of the complex-valued OFDM baseband signal for an antenna port is shown in
In an example embodiment, a radio network may comprise one or more downlink and/or uplink transport channels. For example, a diagram in
There may be one or more physical channels without a corresponding transport channel. The one or more physical channels may be employed for Uplink Control Information (UCI) 509 and/or Downlink Control Information (DCI) 517. For example, Physical Uplink Control CHannel (PUCCH) 504 may carry UCI 509 from a UE to a base station. For example, Physical Downlink Control CHannel (PDCCH) 515 may carry DCI 517 from a base station to a UE. NR may support UCI 509 multiplexing in PUSCH 503 when UCI 509 and PUSCH 503 transmissions may coincide in a slot at least in part. The UCI 509 may comprise at least one of CSI, Acknowledgement (ACK)/Negative Acknowledgement (NACK), and/or scheduling request. The DCI 517 on PDCCH 515 may indicate at least one of following: one or more downlink assignments and/or one or more uplink scheduling grants
In uplink, a UE may transmit one or more Reference Signals (RSs) to a base station. For example, the one or more RSs may be at least one of Demodulation-RS (DM-RS) 506, Phase Tracking-RS (PT-RS) 507, and/or Sounding RS (SRS) 508. In downlink, a base station may transmit (e.g., unicast, multicast, and/or broadcast) one or more RSs to a UE. For example, the one or more RSs may be at least one of Primary Synchronization Signal (PSS)/Secondary Synchronization Signal (SSS) 521, CSI-RS 522, DM-RS 523, and/or PT-RS 524.
In an example, a UE may transmit one or more uplink DM-RSs 506 to a base station for channel estimation, for example, for coherent demodulation of one or more uplink physical channels (e.g., PUSCH 503 and/or PUCCH 504). For example, a UE may transmit a base station at least one uplink DM-RS 506 with PUSCH 503 and/or PUCCH 504, wherein the at least one uplink DM-RS 506 may be spanning a same frequency range as a corresponding physical channel. In an example, a base station may configure a UE with one or more uplink DM-RS configurations. At least one DM-RS configuration may support a front-loaded DM-RS pattern. A front-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1 or 2 adjacent OFDM symbols). One or more additional uplink DM-RS may be configured to transmit at one or more symbols of a PUSCH and/or PUCCH. A base station may semi-statistically configure a UE with a maximum number of front-loaded DM-RS symbols for PUSCH and/or PUCCH. For example, a UE may schedule a single-symbol DM-RS and/or double symbol DM-RS based on a maximum number of front-loaded DM-RS symbols, wherein a base station may configure the UE with one or more additional uplink DM-RS for PUSCH and/or PUCCH. A new radio network may support, e.g., at least for CP-OFDM, a common DM-RS structure for DL and UL, wherein a DM-RS location, DM-RS pattern, and/or scrambling sequence may be same or different.
In an example, whether uplink PT-RS 507 is present or not may depend on a RRC configuration. For example, a presence of uplink PT-RS may be UE-specifically configured. For example, a presence and/or a pattern of uplink PT-RS 507 in a scheduled resource may be UE-specifically configured by a combination of RRC signaling and/or association with one or more parameters employed for other purposes (e.g., Modulation and Coding Scheme (MCS)) which may be indicated by DCI. When configured, a dynamic presence of uplink PT-RS 507 may be associated with one or more DCI parameters comprising at least MCS. A radio network may support plurality of uplink PT-RS densities defined in time/frequency domain. When present, a frequency domain density may be associated with at least one configuration of a scheduled bandwidth. A UE may assume a same precoding for a DMRS port and a PT-RS port. A number of PT-RS ports may be fewer than a number of DM-RS ports in a scheduled resource. For example, uplink PT-RS 507 may be confined in the scheduled time/frequency duration for a UE.
In an example, a UE may transmit SRS 508 to a base station for channel state estimation to support uplink channel dependent scheduling and/or link adaptation. For example, SRS 508 transmitted by a UE may allow for a base station to estimate an uplink channel state at one or more different frequencies. A base station scheduler may employ an uplink channel state to assign one or more resource blocks of good quality for an uplink PUSCH transmission from a UE. A base station may semi-statistically configure a UE with one or more SRS resource sets. For an SRS resource set, a base station may configure a UE with one or more SRS resources. An SRS resource set applicability may be configured by a higher layer (e.g., RRC) parameter. For example, when a higher layer parameter indicates beam management, a SRS resource in each of one or more SRS resource sets may be transmitted at a time instant. A UE may transmit one or more SRS resources in different SRS resource sets simultaneously. A new radio network may support aperiodic, periodic and/or semi-persistent SRS transmissions. A UE may transmit SRS resources based on one or more trigger types, wherein the one or more trigger types may comprise higher layer signaling (e.g., RRC) and/or one or more DCI formats (e.g., at least one DCI format may be employed for a UE to select at least one of one or more configured SRS resource sets. An SRS trigger type 0 may refer to an SRS triggered based on a higher layer signaling. An SRS trigger type 1 may refer to an SRS triggered based on one or more DCI formats. In an example, when PUSCH 503 and SRS 508 are transmitted in a same slot, a UE may be configured to transmit SRS 508 after a transmission of PUSCH 503 and corresponding uplink DM-RS 506.
In an example, a base station may semi-statistically configure a UE with one or more SRS configuration parameters indicating at least one of following: a SRS resource configuration identifier, a number of SRS ports, time domain behavior of SRS resource configuration (e.g., an indication of periodic, semi-persistent, or aperiodic SRS), slot (mini-slot, and/or subframe) level periodicity and/or offset for a periodic and/or aperiodic SRS resource, a number of OFDM symbols in a SRS resource, starting OFDM symbol of a SRS resource, a SRS bandwidth, a frequency hopping bandwidth, a cyclic shift, and/or a SRS sequence ID.
In an example, in a time domain, an SS/PBCH block may comprise one or more OFDM symbols (e.g., 4 OFDM symbols numbered in increasing order from 0 to 3) within the SS/PBCH block. An SS/PBCH block may comprise PSS/SSS 521 and PBCH 516. In an example, in the frequency domain, an SS/PBCH block may comprise one or more contiguous subcarriers (e.g., 240 contiguous subcarriers with the subcarriers numbered in increasing order from 0 to 239) within the SS/PBCH block. For example, a PSS/SSS 521 may occupy 1 OFDM symbol and 127 subcarriers. For example, PBCH 516 may span across 3 OFDM symbols and 240 subcarriers. A UE may assume that one or more SS/PBCH blocks transmitted with a same block index may be quasi co-located, e.g., with respect to Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters. A UE may not assume quasi co-location for other SS/PBCH block transmissions. A periodicity of an SS/PBCH block may be configured by a radio network (e.g., by an RRC signaling) and one or more time locations where the SS/PBCH block may be sent may be determined by sub-carrier spacing. In an example, a UE may assume a band-specific sub-carrier spacing for an SS/PBCH block unless a radio network has configured a UE to assume a different sub-carrier spacing.
In an example, downlink CSI-RS 522 may be employed for a UE to acquire channel state information. A radio network may support periodic, aperiodic, and/or semi-persistent transmission of downlink CSI-RS 522. For example, a base station may semi-statistically configure and/or reconfigure a UE with periodic transmission of downlink CSI-RS 522. A configured CSI-RS resources may be activated ad/or deactivated. For semi-persistent transmission, an activation and/or deactivation of CSI-RS resource may be triggered dynamically. In an example, CSI-RS configuration may comprise one or more parameters indicating at least a number of antenna ports. For example, a base station may configure a UE with 32 ports. A base station may semi-statistically configure a UE with one or more CSI-RS resource sets. One or more CSI-RS resources may be allocated from one or more CSI-RS resource sets to one or more UEs. For example, a base station may semi-statistically configure one or more parameters indicating CSI RS resource mapping, for example, time-domain location of one or more CSI-RS resources, a bandwidth of a CSI-RS resource, and/or a periodicity. In an example, a UE may be configured to employ a same OFDM symbols for downlink CSI-RS 522 and control resource set (coreset) when the downlink CSI-RS 522 and coreset are spatially quasi co-located and resource elements associated with the downlink CSI-RS 522 are the outside of PRBs configured for coreset. In an example, a UE may be configured to employ a same OFDM symbols for downlink CSI-RS 522 and SSB/PBCH when the downlink CSI-RS 522 and SSB/PBCH are spatially quasi co-located and resource elements associated with the downlink CSI-RS 522 are the outside of PRBs configured for SSB/PBCH.
In an example, a UE may transmit one or more downlink DM-RSs 523 to a base station for channel estimation, for example, for coherent demodulation of one or more downlink physical channels (e.g., PDSCH 514). For example, a radio network may support one or more variable and/or configurable DM-RS patterns for data demodulation. At least one downlink DM-RS configuration may support a front-loaded DM-RS pattern. A front-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1 or 2 adjacent OFDM symbols). A base station may semi-statistically configure a UE with a maximum number of front-loaded DM-RS symbols for PDSCH 514. For example, a DM-RS configuration may support one or more DM-RS ports. For example, for single user-MIMO, a DM-RS configuration may support at least 8 orthogonal downlink DM-RS ports. For example, for multiuser-MIMO, a DM-RS configuration may support 12 orthogonal downlink DM-RS ports. A radio network may support, e.g., at least for CP-OFDM, a common DM-RS structure for DL and UL, wherein a DM-RS location, DM-RS pattern, and/or scrambling sequence may be same or different.
In an example, whether downlink PT-RS 524 is present or not may depend on a RRC configuration. For example, a presence of downlink PT-RS 524 may be UE-specifically configured. For example, a presence and/or a pattern of downlink PT-RS 524 in a scheduled resource may be UE-specifically configured by a combination of RRC signaling and/or association with one or more parameters employed for other purposes (e.g., MCS) which may be indicated by DCI. When configured, a dynamic presence of downlink PT-RS 524 may be associated with one or more DCI parameters comprising at least MCS. A radio network may support plurality of PT-RS densities defined in time/frequency domain. When present, a frequency domain density may be associated with at least one configuration of a scheduled bandwidth. A UE may assume a same precoding for a DMRS port and a PT-RS port. A number of PT-RS ports may be fewer than a number of DM-RS ports in a scheduled resource. For example, downlink PT-RS 524 may be confined in the scheduled time/frequency duration for a UE.
In an example, a gNB and a wireless device may communicate with multiple CCs when configured with CA. In an example, different component carriers may have different bandwidth and/or subcarrier spacing, if CA is supported. In an example, a gNB may transmit a first type of service to a UE on a first component carrier. The gNB may transmit a second type of service to the UE on a second component carrier. Different type of services may have different service requirement (e.g., data rate, latency, reliability), which may be suitable for transmission via different component carrier having different subcarrier spacing and/or bandwidth.
As shown in
In an example, a gNB may transmit a downlink control information comprising a downlink or uplink resource block assignment to a wireless device. A base station may transmit to or receive from, a wireless device, data packets (e.g. transport blocks) scheduled and transmitted via one or more resource blocks and one or more slots according to parameters in a downlink control information and/or RRC message(s). In an example, a starting symbol relative to a first slot of the one or more slots may be indicated to the wireless device. In an example, a gNB may transmit to or receive from, a wireless device, data packets scheduled on one or more RBGs and one or more slots.
In an example, a gNB may transmit a downlink control information comprising a downlink assignment to a wireless device via one or more PDCCHs. The downlink assignment may comprise parameters indicating at least modulation and coding format; resource allocation; and/or HARQ information related to DL-SCH. In an example, a resource allocation may comprise parameters of resource block allocation; and/or slot allocation. In an example, a gNB may dynamically allocate resources to a wireless device via a Cell-Radio Network Temporary Identifier (C-RNTI) on one or more PDCCHs. The wireless device may monitor the one or more PDCCHs in order to find possible allocation when its downlink reception is enabled. The wireless device may receive one or more downlink data package on one or more PDSCH scheduled by the one or more PDCCHs, when successfully detecting the one or more PDCCHs.
In an example, a gNB may allocate Configured Scheduling (CS) resources for down link transmission to a wireless device. The gNB may transmit one or more RRC messages indicating a periodicity of the CS grant. The gNB may transmit a DCI via a PDCCH addressed to a Configured Scheduling-RNTI (CS-RNTI) activating the CS resources. The DCI may comprise parameters indicating that the downlink grant is a CS grant. The CS grant may be implicitly reused according to the periodicity defined by the one or more RRC messages, until deactivated.
In an example, a gNB may transmit a downlink control information comprising an uplink grant to a wireless device via one or more PDCCHs. The uplink grant may comprise parameters indicating at least modulation and coding format; resource allocation; and/or HARQ information related to UL-SCH. In an example, a resource allocation may comprise parameters of resource block allocation; and/or slot allocation. In an example, a gNB may dynamically allocate resources to a wireless device via a C-RNTI on one or more PDCCHs. The wireless device may monitor the one or more PDCCHs in order to find possible resource allocation. The wireless device may transmit one or more uplink data package via one or more PUSCH scheduled by the one or more PDCCHs, when successfully detecting the one or more PDCCHs.
In an example, a gNB may allocate CS resources for uplink data transmission to a wireless device. The gNB may transmit one or more RRC messages indicating a periodicity of the CS grant. The gNB may transmit a DCI via a PDCCH addressed to a CS-RNTI activating the CS resources. The DCI may comprise parameters indicating that the uplink grant is a CS grant. The CS grant may be implicitly reused according to the periodicity defined by the one or more RRC message, until deactivated.
In an example, a base station may transmit DCI/control signaling via PDCCH. The DCI may take a format in a plurality of formats. A DCI may comprise downlink and/or uplink scheduling information (e.g., resource allocation information, HARQ related parameters, MCS), request for CSI (e.g., aperiodic CQI reports), request for SRS, uplink power control commands for one or more cells, one or more timing information (e.g., TB transmission/reception timing, HARQ feedback timing, etc.), etc. In an example, a DCI may indicate an uplink grant comprising transmission parameters for one or more transport blocks. In an example, a DCI may indicate downlink assignment indicating parameters for receiving one or more transport blocks. In an example, a DCI may be used by base station to initiate a contention-free random access at the wireless device. In an example, the base station may transmit a DCI comprising slot format indicator (SFI) notifying a slot format. In an example, the base station may transmit a DCI comprising pre-emption indication notifying the PRB(s) and/or OFDM symbol(s) where a UE may assume no transmission is intended for the UE. In an example, the base station may transmit a DCI for group power control of PUCCH or PUSCH or SRS. In an example, a DCI may correspond to an RNTI. In an example, the wireless device may obtain an RNTI in response to completing the initial access (e.g., C-RNTI). In an example, the base station may configure an RNTI for the wireless (e.g., CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI). In an example, the wireless device may compute an RNTI (e.g., the wireless device may compute RA-RNTI based on resources used for transmission of a preamble). In an example, an RNTI may have a pre-configured value (e.g., P-RNTI or SI-RNTI). In an example, a wireless device may monitor a group common search space which may be used by base station for transmitting DCIs that are intended for a group of UEs. In an example, a group common DCI may correspond to an RNTI which is commonly configured for a group of UEs. In an example, a wireless device may monitor a UE-specific search space. In an example, a UE specific DCI may correspond to an RNTI configured for the wireless device.
A NR system may support a single beam operation and/or a multi-beam operation. In a multi-beam operation, a base station may perform a downlink beam sweeping to provide coverage for common control channels and/or downlink SS blocks, which may comprise at least a PSS, a SSS, and/or PBCH. A wireless device may measure quality of a beam pair link using one or more RSs. One or more SS blocks, or one or more CSI-RS resources, associated with a CSI-RS resource index (CRI), or one or more DM-RSs of PBCH, may be used as RS for measuring quality of a beam pair link. Quality of a beam pair link may be defined as a reference signal received power (RSRP) value, or a reference signal received quality (RSRQ) value, and/or a CSI value measured on RS resources. The base station may indicate whether an RS resource, used for measuring a beam pair link quality, is quasi-co-located (QCLed) with DM-RSs of a control channel. A RS resource and DM-RSs of a control channel may be called QCLed when a channel characteristics from a transmission on an RS to a wireless device, and that from a transmission on a control channel to a wireless device, are similar or same under a configured criterion. In a multi-beam operation, a wireless device may perform an uplink beam sweeping to access a cell.
In an example, a wireless device may be configured to monitor PDCCH on one or more beam pair links simultaneously depending on a capability of a wireless device. This may increase robustness against beam pair link blocking. A base station may transmit one or more messages to configure a wireless device to monitor PDCCH on one or more beam pair links in different PDCCH OFDM symbols. For example, a base station may transmit higher layer signaling (e.g. RRC signaling) or MAC CE comprising parameters related to the Rx beam setting of a wireless device for monitoring PDCCH on one or more beam pair links. A base station may transmit indication of spatial QCL assumption between an DL RS antenna port(s) (for example, cell-specific CSI-RS, or wireless device-specific CSI-RS, or SS block, or PBCH with or without DM-RSs of PBCH), and DL RS antenna port(s) for demodulation of DL control channel. Signaling for beam indication for a PDCCH may be MAC CE signaling, or RRC signaling, or DCI signaling, or specification-transparent and/or implicit method, and combination of these signaling methods.
For reception of unicast DL data channel, a base station may indicate spatial QCL parameters between DL RS antenna port(s) and DM-RS antenna port(s) of DL data channel. The base station may transmit DCI (e.g. downlink grants) comprising information indicating the RS antenna port(s). The information may indicate RS antenna port(s) which may be QCLed with the DM-RS antenna port(s). Different set of DM-RS antenna port(s) for a DL data channel may be indicated as QCL with different set of the RS antenna port(s).
A wireless device may further use CSI-RS in the multi-beam operation for estimating a beam quality of a links between a wireless device and a base station. A beam may be associated with a CSI-RS. For example, a wireless device may, based on a RSRP measurement on CSI-RS, report a beam index, as indicated in a CRI for downlink beam selection, and associated with a RSRP value of a beam. A CSI-RS may be transmitted on a CSI-RS resource including at least one of one or more antenna ports, one or more time or frequency radio resources. A CSI-RS resource may be configured in a cell-specific way by common RRC signaling, or in a wireless device-specific way by dedicated RRC signaling, and/or L1/L2 signaling. Multiple wireless devices covered by a cell may measure a cell-specific CSI-RS resource. A dedicated subset of wireless devices covered by a cell may measure a wireless device-specific CSI-RS resource.
A CSI-RS resource may be transmitted periodically, or using aperiodic transmission, or using a multi-shot or semi-persistent transmission. For example, in a periodic transmission in
A wireless device 110 may transmit one or more beam management reports to a base station 120. In one or more beam management reports, a wireless device 110 may indicate some beam pair quality parameters, comprising at least, one or more beam identifications; RSRP; Precoding Matrix Indicator (PMI)/Channel Quality Indicator (CQI)/Rank Indicator (RI) of a subset of configured beams. Based on one or more beam management reports, a base station 120 may transmit to a wireless device 110 a signal indicating that one or more beam pair links are one or more serving beams. A base station 120 may transmit PDCCH and PDSCH for a wireless device 110 using one or more serving beams.
In an example embodiment, new radio network may support a Bandwidth Adaptation (BA). In an example, receive and/or transmit bandwidths configured by an UE employing a BA may not be large. For example, a receive and/or transmit bandwidths may not be as large as a bandwidth of a cell. Receive and/or transmit bandwidths may be adjustable. For example, a UE may change receive and/or transmit bandwidths, e.g., to shrink during period of low activity to save power. For example, a UE may change a location of receive and/or transmit bandwidths in a frequency domain, e.g. to increase scheduling flexibility. For example, a UE may change a subcarrier spacing, e.g. to allow different services.
In an example embodiment, a subset of a total cell bandwidth of a cell may be referred to as a Bandwidth Part (BWP). A base station may configure a UE with one or more BWPs to achieve a BA. For example, a base station may indicate, to a UE, which of the one or more (configured) BWPs is an active BWP.
In an example, a UE, configured for operation in one or more BWPs of a cell, may be configured by one or more higher layers (e.g. RRC layer) for a cell a set of one or more BWPs (e.g., at most four BWPs) for receptions by the UE (DL BWP set) in a DL bandwidth by at least one parameter DL-BWP and a set of one or more BWPs (e.g., at most four BWPs) for transmissions by a UE (UL BWP set) in an UL bandwidth by at least one parameter UL-BWP for a cell.
To enable BA on the PCell, a base station may configure a UE with one or more UL and DL BWP pairs. To enable BA on SCells (e.g., in case of CA), a base station may configure a UE at least with one or more DL BWPs (e.g., there may be none in an UL).
In an example, an initial active DL BWP may be defined by at least one of a location and number of contiguous PRBs, a subcarrier spacing, or a cyclic prefix, for a control resource set for at least one common search space. For operation on the PCell, one or more higher layer parameters may indicate at least one initial UL BWP for a random access procedure. If a UE is configured with a secondary carrier on a primary cell, the UE may be configured with an initial BWP for random access procedure on a secondary carrier.
In an example, for unpaired spectrum operation, a UE may expect that a center frequency for a DL BWP may be same as a center frequency for a UL BWP.
For example, for a DL BWP or an UL BWP in a set of one or more DL BWPs or one or more UL BWPs, respectively, a base statin may semi-statistically configure a UE for a cell with one or more parameters indicating at least one of following: a subcarrier spacing; a cyclic prefix; a number of contiguous PRBs; an index in the set of one or more DL BWPs and/or one or more UL BWPs; a link between a DL BWP and an UL BWP from a set of configured DL BWPs and UL BWPs; a DCI detection to a PDSCH reception timing; a PDSCH reception to a HARQ-ACK transmission timing value; a DCI detection to a PUSCH transmission timing value; an offset of a first PRB of a DL bandwidth or an UL bandwidth, respectively, relative to a first PRB of a bandwidth.
In an example, for a DL BWP in a set of one or more DL BWPs on a PCell, a base station may configure a UE with one or more control resource sets for at least one type of common search space and/or one UE-specific search space. For example, a base station may not configure a UE without a common search space on a PCell, or on a PSCell, in an active DL BWP.
For an UL BWP in a set of one or more UL BWPs, a base station may configure a UE with one or more resource sets for one or more PUCCH transmissions.
In an example, if a DCI comprises a BWP indicator field, a BWP indicator field value may indicate an active DL BWP, from a configured DL BWP set, for one or more DL receptions. If a DCI comprises a BWP indicator field, a BWP indicator field value may indicate an active UL BWP, from a configured UL BWP set, for one or more UL transmissions.
In an example, for a PCell, a base station may semi-statistically configure a UE with a default DL BWP among configured DL BWPs. If a UE is not provided a default DL BWP, a default BWP may be an initial active DL BWP.
In an example, a base station may configure a UE with a timer value for a PCell. For example, a UE may start a timer, referred to as BWP inactivity timer, when a UE detects a DCI indicating an active DL BWP, other than a default DL BWP, for a paired spectrum operation or when a UE detects a DCI indicating an active DL BWP or UL BWP, other than a default DL BWP or UL BWP, for an unpaired spectrum operation. The UE may increment the timer by an interval of a first value (e.g., the first value may be 1 millisecond or 0.5 milliseconds) if the UE does not detect a DCI during the interval for a paired spectrum operation or for an unpaired spectrum operation. In an example, the timer may expire when the timer is equal to the timer value. A UE may switch to the default DL BWP from an active DL BWP when the timer expires.
In an example, a base station may semi-statistically configure a UE with one or more BWPs. A UE may switch an active BWP from a first BWP to a second BWP in response to receiving a DCI indicating the second BWP as an active BWP and/or in response to an expiry of BWP inactivity timer (for example, the second BWP may be a default BWP). For example,
In an example, if a UE is configured for a secondary cell with a default DL BWP among configured DL BWPs and a timer value, UE procedures on a secondary cell may be same as on a primary cell using the timer value for the secondary cell and the default DL BWP for the secondary cell.
In an example, if a base station configures a UE with a first active DL BWP and a first active UL BWP on a secondary cell or carrier, a UE may employ an indicated DL BWP and an indicated UL BWP on a secondary cell as a respective first active DL BWP and first active UL BWP on a secondary cell or carrier.
When multi connectivity is configured for a wireless device 110, the wireless device 110, which may support multiple reception/transmission functions in an RRC connected state, may be configured to utilize radio resources provided by multiple schedulers of a multiple base stations. Multiple base stations may be inter-connected via a non-ideal or ideal backhaul (e.g. Xn interface, X2 interface, and/or the like). A base station involved in multi connectivity for a certain wireless device may perform at least one of two different roles: a base station may either act as a master base station or as a secondary base station. In multi connectivity, a wireless device may be connected to one master base station and one or more secondary base stations. In an example, a master base station (e.g. the MN 1130) may provide a master cell group (MCG) comprising a primary cell and/or one or more secondary cells for a wireless device (e.g. the wireless device 110). A secondary base station (e.g. the SN 1150) may provide a secondary cell group (SCG) comprising a primary secondary cell (PSCell) and/or one or more secondary cells for a wireless device (e.g. the wireless device 110).
In multi connectivity, a radio protocol architecture that a bearer employs may depend on how a bearer is setup. In an example, three different type of bearer setup options may be supported: an MCG bearer, an SCG bearer, and/or a split bearer. A wireless device may receive/transmit packets of an MCG bearer via one or more cells of the MCG, and/or may receive/transmits packets of an SCG bearer via one or more cells of an SCG. Multi-connectivity may also be described as having at least one bearer configured to use radio resources provided by the secondary base station. Multi-connectivity may or may not be configured/implemented in some of the example embodiments.
In an example, a wireless device (e.g. Wireless Device 110) may transmit and/or receive: packets of an MCG bearer via an SDAP layer (e.g. SDAP 1110), a PDCP layer (e.g. NR PDCP 1111), an RLC layer (e.g. MN RLC 1114), and a MAC layer (e.g. MN MAC 1118); packets of a split bearer via an SDAP layer (e.g. SDAP 1110), a PDCP layer (e.g. NR PDCP 1112), one of a master or secondary RLC layer (e.g. MN RLC 1115, SN RLC 1116), and one of a master or secondary MAC layer (e.g. MN MAC 1118, SN MAC 1119); and/or packets of an SCG bearer via an SDAP layer (e.g. SDAP 1110), a PDCP layer (e.g. NR PDCP 1113), an RLC layer (e.g. SN RLC 1117), and a MAC layer (e.g. MN MAC 1119).
In an example, a master base station (e.g. MN 1130) and/or a secondary base station (e.g. SN 1150) may transmit/receive: packets of an MCG bearer via a master or secondary node SDAP layer (e.g. SDAP 1120, SDAP 1140), a master or secondary node PDCP layer (e.g. NR PDCP 1121, NR PDCP 1142), a master node RLC layer (e.g. MN RLC 1124, MN RLC 1125), and a master node MAC layer (e.g. MN MAC 1128); packets of an SCG bearer via a master or secondary node SDAP layer (e.g. SDAP 1120, SDAP 1140), a master or secondary node PDCP layer (e.g. NR PDCP 1122, NR PDCP 1143), a secondary node RLC layer (e.g. SN RLC 1146, SN RLC 1147), and a secondary node MAC layer (e.g. SN MAC 1148); packets of a split bearer via a master or secondary node SDAP layer (e.g. SDAP 1120, SDAP 1140), a master or secondary node PDCP layer (e.g. NR PDCP 1123, NR PDCP 1141), a master or secondary node RLC layer (e.g. MN RLC 1126, SN RLC 1144, SN RLC 1145, MN RLC 1127), and a master or secondary node MAC layer (e.g. MN MAC 1128, SN MAC 1148).
In multi connectivity, a wireless device may configure multiple MAC entities: one MAC entity (e.g. MN MAC 1118) for a master base station, and other MAC entities (e.g. SN MAC 1119) for a secondary base station. In multi-connectivity, a configured set of serving cells for a wireless device may comprise two subsets: an MCG comprising serving cells of a master base station, and SCGs comprising serving cells of a secondary base station. For an SCG, one or more of following configurations may be applied: at least one cell of an SCG has a configured UL CC and at least one cell of a SCG, named as primary secondary cell (PSCell, PCell of SCG, or sometimes called PCell), is configured with PUCCH resources; when an SCG is configured, there may be at least one SCG bearer or one Split bearer; upon detection of a physical layer problem or a random access problem on a PSCell, or a number of NR RLC retransmissions has been reached associated with the SCG, or upon detection of an access problem on a PSCell during a SCG addition or a SCG change: an RRC connection re-establishment procedure may not be triggered, UL transmissions towards cells of an SCG may be stopped, a master base station may be informed by a wireless device of a SCG failure type, for split bearer, a DL data transfer over a master base station may be maintained; an NR RLC acknowledged mode (AM) bearer may be configured for a split bearer; PCell and/or PSCell may not be de-activated; PSCell may be changed with a SCG change procedure (e.g. with security key change and a RACH procedure); and/or a bearer type change between a split bearer and a SCG bearer or simultaneous configuration of a SCG and a split bearer may or may not supported.
With respect to interaction between a master base station and a secondary base stations for multi-connectivity, one or more of the following may be applied: a master base station and/or a secondary base station may maintain RRM measurement configurations of a wireless device; a master base station may (e.g. based on received measurement reports, traffic conditions, and/or bearer types) may decide to request a secondary base station to provide additional resources (e.g. serving cells) for a wireless device; upon receiving a request from a master base station, a secondary base station may create/modify a container that may result in configuration of additional serving cells for a wireless device (or decide that the secondary base station has no resource available to do so); for a UE capability coordination, a master base station may provide (a part of) an AS configuration and UE capabilities to a secondary base station; a master base station and a secondary base station may exchange information about a UE configuration by employing of RRC containers (inter-node messages) carried via Xn messages; a secondary base station may initiate a reconfiguration of the secondary base station existing serving cells (e.g. PUCCH towards the secondary base station); a secondary base station may decide which cell is a PSCell within a SCG; a master base station may or may not change content of RRC configurations provided by a secondary base station; in case of a SCG addition and/or a SCG SCell addition, a master base station may provide recent (or the latest) measurement results for SCG cell(s); a master base station and secondary base stations may receive information of SFN and/or subframe offset of each other from OAM and/or via an Xn interface, (e.g. for a purpose of DRX alignment and/or identification of a measurement gap). In an example, when adding a new SCG SCell, dedicated RRC signaling may be used for sending required system information of a cell as for CA, except for a SFN acquired from a MIB of a PSCell of a SCG.
In an example embodiment, a random access procedure may be at least one of a contention based random access procedure and a contention free random access procedure. For example, a contention based random access procedure may comprise, one or more Msg 1 1220 transmissions, one or more Msg2 1230 transmissions, one or more Msg3 1240 transmissions, and contention resolution 1250. For example, a contention free random access procedure may comprise one or more Msg 1 1220 transmissions and one or more Msg2 1230 transmissions.
In an example, a base station may transmit (e.g., unicast, multicast, or broadcast), to a UE, a RACH configuration 1210 via one or more beams. The RACH configuration 1210 may comprise one or more parameters indicating at least one of following: available set of PRACH resources for a transmission of a random access preamble, initial preamble power (e.g., random access preamble initial received target power), an RSRP threshold for a selection of a SS block and corresponding PRACH resource, a power-ramping factor (e.g., random access preamble power ramping step), random access preamble index, a maximum number of preamble transmission, preamble group A and group B, a threshold (e.g., message size) to determine the groups of random access preambles, a set of one or more random access preambles for system information request and corresponding PRACH resource(s), if any, a set of one or more random access preambles for beam failure recovery request and corresponding PRACH resource(s), if any, a time window to monitor RA response(s), a time window to monitor response(s) on beam failure recovery request, and/or a contention resolution timer.
In an example, the Msg1 1220 may be one or more transmissions of a random access preamble. For a contention based random access procedure, a UE may select a SS block with a RSRP above the RSRP threshold. If random access preambles group B exists, a UE may select one or more random access preambles from a group A or a group B depending on a potential Msg3 1240 size. If a random access preambles group B does not exist, a UE may select the one or more random access preambles from a group A. A UE may select a random access preamble index randomly (e.g. with equal probability or a normal distribution) from one or more random access preambles associated with a selected group. If a base station semi-statistically configures a UE with an association between random access preambles and SS blocks, the UE may select a random access preamble index randomly with equal probability from one or more random access preambles associated with a selected SS block and a selected group.
For example, a UE may initiate a contention free random access procedure based on a beam failure indication from a lower layer. For example, a base station may semi-statistically configure a UE with one or more contention free PRACH resources for beam failure recovery request associated with at least one of SS blocks and/or CSI-RSs. If at least one of SS blocks with a RSRP above a first RSRP threshold amongst associated SS blocks or at least one of CSI-RSs with a RSRP above a second RSRP threshold amongst associated CSI-RSs is available, a UE may select a random access preamble index corresponding to a selected SS block or CSI-RS from a set of one or more random access preambles for beam failure recovery request.
For example, a UE may receive, from a base station, a random access preamble index via PDCCH or RRC for a contention free random access procedure. If a base station does not configure a UE with at least one contention free PRACH resource associated with SS blocks or CSI-RS, the UE may select a random access preamble index. If a base station configures a UE with one or more contention free PRACH resources associated with SS blocks and at least one SS block with a RSRP above a first RSRP threshold amongst associated SS blocks is available, the UE may select the at least one SS block and select a random access preamble corresponding to the at least one SS block. If a base station configures a UE with one or more contention free PRACH resources associated with CSI-RSs and at least one CSI-RS with a RSRP above a second RSPR threshold amongst the associated CSI-RSs is available, the UE may select the at least one CSI-RS and select a random access preamble corresponding to the at least one CSI-RS.
A UE may perform one or more Msg1 1220 transmissions by transmitting the selected random access preamble. For example, if a UE selects an SS block and is configured with an association between one or more PRACH occasions and one or more SS blocks, the UE may determine an PRACH occasion from one or more PRACH occasions corresponding to a selected SS block. For example, if a UE selects a CSI-RS and is configured with an association between one or more PRACH occasions and one or more CSI-RSs, the UE may determine a PRACH occasion from one or more PRACH occasions corresponding to a selected CSI-RS. A UE may transmit, to a base station, a selected random access preamble via a selected PRACH occasions. A UE may determine a transmit power for a transmission of a selected random access preamble at least based on an initial preamble power and a power-ramping factor. A UE may determine a RA-RNTI associated with a selected PRACH occasions in which a selected random access preamble is transmitted. For example, a UE may not determine a RA-RNTI for a beam failure recovery request. A UE may determine an RA-RNTI at least based on an index of a first OFDM symbol and an index of a first slot of a selected PRACH occasions, and/or an uplink carrier index for a transmission of Msg1 1220.
In an example, a UE may receive, from a base station, a random access response, Msg 2 1230. A UE may start a time window (e.g., ra-Response Window) to monitor a random access response. For beam failure recovery request, a base station may configure a UE with a different time window (e.g., bfr-Response Window) to monitor response on beam failure recovery request. For example, a UE may start a time window (e.g., ra-Response Window or bfr-Response Window) at a start of a first PDCCH occasion after a fixed duration of one or more symbols from an end of a preamble transmission. If a UE transmits multiple preambles, the UE may start a time window at a start of a first PDCCH occasion after a fixed duration of one or more symbols from an end of a first preamble transmission. A UE may monitor a PDCCH of a cell for at least one random access response identified by a RA-RNTI or for at least one response to beam failure recovery request identified by a C-RNTI while a timer for a time window is running.
In an example, a UE may consider a reception of random access response successful if at least one random access response comprises a random access preamble identifier corresponding to a random access preamble transmitted by the UE. A UE may consider the contention free random access procedure successfully completed if a reception of random access response is successful. If a contention free random access procedure is triggered for a beam failure recovery request, a UE may consider a contention free random access procedure successfully complete if a PDCCH transmission is addressed to a C-RNTI. In an example, if at least one random access response comprises a random access preamble identifier, a UE may consider the random access procedure successfully completed and may indicate a reception of an acknowledgement for a system information request to upper layers. If a UE has signaled multiple preamble transmissions, the UE may stop transmitting remaining preambles (if any) in response to a successful reception of a corresponding random access response.
In an example, a UE may perform one or more Msg 3 1240 transmissions in response to a successful reception of random access response (e.g., for a contention based random access procedure). A UE may adjust an uplink transmission timing based on a timing advanced command indicated by a random access response and may transmit one or more transport blocks based on an uplink grant indicated by a random access response. Subcarrier spacing for PUSCH transmission for Msg3 1240 may be provided by at least one higher layer (e.g. RRC) parameter. A UE may transmit a random access preamble via PRACH and Msg3 1240 via PUSCH on a same cell. A base station may indicate an UL BWP for a PUSCH transmission of Msg3 1240 via system information block. A UE may employ HARQ for a retransmission of Msg 3 1240.
In an example, multiple UEs may perform Msg 1 1220 by transmitting a same preamble to a base station and receive, from the base station, a same random access response comprising an identity (e.g., TC-RNTI). Contention resolution 1250 may ensure that a UE does not incorrectly use an identity of another UE. For example, contention resolution 1250 may be based on C-RNTI on PDCCH or a UE contention resolution identity on DL-SCH. For example, if a base station assigns a C-RNTI to a UE, the UE may perform contention resolution 1250 based on a reception of a PDCCH transmission that is addressed to the C-RNTI. In response to detection of a C-RNTI on a PDCCH, a UE may consider contention resolution 1250 successful and may consider a random access procedure successfully completed. If a UE has no valid C-RNTI, a contention resolution may be addressed by employing a TC-RNTI. For example, if a MAC PDU is successfully decoded and a MAC PDU comprises a UE contention resolution identity MAC CE that matches the CCCH SDU transmitted in Msg3 1250, a UE may consider the contention resolution 1250 successful and may consider the random access procedure successfully completed.
In an example, at least one cell in a SCG may have a configured UL CC, wherein a cell of at least one cell may be called PSCell or PCell of SCG, or sometimes may be simply called PCell. A PSCell may be configured with PUCCH resources. In an example, when a SCG is configured, there may be at least one SCG bearer or one split bearer. In an example, upon detection of a physical layer problem or a random access problem on a PSCell, or upon reaching a number of RLC retransmissions associated with the SCG, or upon detection of an access problem on a PSCell during a SCG addition or a SCG change: an RRC connection re-establishment procedure may not be triggered, UL transmissions towards cells of an SCG may be stopped, a master base station may be informed by a UE of a SCG failure type and DL data transfer over a master base station may be maintained.
In an example, a MAC sublayer may provide services such as data transfer and radio resource allocation to upper layers (e.g. 1310 or 1320). A MAC sublayer may comprise a plurality of MAC entities (e.g. 1350 and 1360). A MAC sublayer may provide data transfer services on logical channels. To accommodate different kinds of data transfer services, multiple types of logical channels may be defined. A logical channel may support transfer of a particular type of information. A logical channel type may be defined by what type of information (e.g., control or data) is transferred. For example, BCCH, PCCH, CCCH and DCCH may be control channels and DTCH may be a traffic channel. In an example, a first MAC entity (e.g. 1310) may provide services on PCCH, BCCH, CCCH, DCCH, DTCH and MAC control elements. In an example, a second MAC entity (e.g. 1320) may provide services on BCCH, DCCH, DTCH and MAC control elements.
A MAC sublayer may expect from a physical layer (e.g. 1330 or 1340) services such as data transfer services, signaling of HARQ feedback, signaling of scheduling request or measurements (e.g. CQI). In an example, in dual connectivity, two MAC entities may be configured for a wireless device: one for MCG and one for SCG. A MAC entity of wireless device may handle a plurality of transport channels. In an example, a first MAC entity may handle first transport channels comprising a PCCH of MCG, a first BCH of MCG, one or more first DL-SCHs of MCG, one or more first UL-SCHs of MCG and one or more first RACHs of MCG. In an example, a second MAC entity may handle second transport channels comprising a second BCH of SCG, one or more second DL-SCHs of SCG, one or more second UL-SCHs of SCG and one or more second RACHs of SCG.
In an example, if a MAC entity is configured with one or more SCells, there may be multiple DL-SCHs and there may be multiple UL-SCHs as well as multiple RACHs per MAC entity. In an example, there may be one DL-SCH and UL-SCH on a SpCell. In an example, there may be one DL-SCH, zero or one UL-SCH and zero or one RACH for an SCell. A DL-SCH may support receptions using different numerologies and/or TTI duration within a MAC entity. A UL-SCH may also support transmissions using different numerologies and/or TTI duration within the MAC entity.
In an example, a MAC sublayer may support different functions and may control these functions with a control (e.g. 1355 or 1365) element. Functions performed by a MAC entity may comprise mapping between logical channels and transport channels (e.g., in uplink or downlink), multiplexing (e.g. 1352 or 1362) of MAC SDUs from one or different logical channels onto transport blocks (TB) to be delivered to the physical layer on transport channels (e.g., in uplink), demultiplexing (e.g. 1352 or 1362) of MAC SDUs to one or different logical channels from transport blocks (TB) delivered from the physical layer on transport channels (e.g., in downlink), scheduling information reporting (e.g., in uplink), error correction through HARQ in uplink or downlink (e.g. 1363), and logical channel prioritization in uplink (e.g. 1351 or 1361). A MAC entity may handle a random access process (e.g. 1354 or 1364).
In an example, a base station CU may comprise an RRC function, an SDAP layer, and a PDCP layer, and base station DUs may comprise an RLC layer, a MAC layer, and a PHY layer. In an example, various functional split options between a base station CU and base station DUs may be possible by locating different combinations of upper protocol layers (RAN functions) in a base station CU and different combinations of lower protocol layers (RAN functions) in base station DUs. A functional split may support flexibility to move protocol layers between a base station CU and base station DUs depending on service requirements and/or network environments.
In an example, functional split options may be configured per base station, per base station CU, per base station DU, per UE, per bearer, per slice, or with other granularities. In per base station CU split, a base station CU may have a fixed split option, and base station DUs may be configured to match a split option of a base station CU. In per base station DU split, a base station DU may be configured with a different split option, and a base station CU may provide different split options for different base station DUs. In per UE split, a base station (base station CU and at least one base station DUs) may provide different split options for different wireless devices. In per bearer split, different split options may be utilized for different bearers. In per slice splice, different split options may be applied for different slices.
In an example, a wireless device may transition a UE RRC state between an RRC idle state and an RRC connected state in both ways (e.g. connection release 1540 or connection establishment 1550; or connection reestablishment) and/or between an RRC inactive state and an RRC connected state in both ways (e.g. connection inactivation 1570 or connection resume 1580). In an example, a wireless device may transition its RRC state from an RRC inactive state to an RRC idle state (e.g. connection release 1560).
In an example, an anchor base station may be a base station that may keep a UE context (a wireless device context) of a wireless device at least during a time period that a wireless device stays in a RAN notification area (RNA) of an anchor base station, and/or that a wireless device stays in an RRC inactive state. In an example, an anchor base station may be a base station that a wireless device in an RRC inactive state was lastly connected to in a latest RRC connected state or that a wireless device lastly performed an RNA update procedure in. In an example, an RNA may comprise one or more cells operated by one or more base stations. In an example, a base station may belong to one or more RNAs. In an example, a cell may belong to one or more RNAs.
In an example, a wireless device may transition a UE RRC state from an RRC connected state to an RRC inactive state in a base station. A wireless device may receive RNA information from the base station. RNA information may comprise at least one of an RNA identifier, one or more cell identifiers of one or more cells of an RNA, a base station identifier, an IP address of the base station, an AS context identifier of the wireless device, a resume identifier, and/or the like.
In an example, an anchor base station may broadcast a message (e.g. RAN paging message) to base stations of an RNA to reach to a wireless device in an RRC inactive state, and/or the base stations receiving the message from the anchor base station may broadcast and/or multicast another message (e.g. paging message) to wireless devices in their coverage area, cell coverage area, and/or beam coverage area associated with the RNA through an air interface.
In an example, when a wireless device in an RRC inactive state moves into a new RNA, the wireless device may perform an RNA update (RNAU) procedure, which may comprise a random access procedure by the wireless device and/or a UE context retrieve procedure. A UE context retrieve may comprise: receiving, by a base station from a wireless device, a random access preamble; and fetching, by a base station, a UE context of the wireless device from an old anchor base station. Fetching may comprise: sending a retrieve UE context request message comprising a resume identifier to the old anchor base station and receiving a retrieve UE context response message comprising the UE context of the wireless device from the old anchor base station.
In an example embodiment, a wireless device in an RRC inactive state may select a cell to camp on based on at least a on measurement results for one or more cells, a cell where a wireless device may monitor an RNA paging message and/or a core network paging message from a base station. In an example, a wireless device in an RRC inactive state may select a cell to perform a random access procedure to resume an RRC connection and/or to transmit one or more packets to a base station (e.g. to a network). In an example, if a cell selected belongs to a different RNA from an RNA for a wireless device in an RRC inactive state, the wireless device may initiate a random access procedure to perform an RNA update procedure. In an example, if a wireless device in an RRC inactive state has one or more packets, in a buffer, to transmit to a network, the wireless device may initiate a random access procedure to transmit one or more packets to a base station of a cell that the wireless device selects. A random access procedure may be performed with two messages (e.g. 2 stage random access) and/or four messages (e.g. 4 stage random access) between the wireless device and the base station.
In an example embodiment, a base station receiving one or more uplink packets from a wireless device in an RRC inactive state may fetch a UE context of a wireless device by transmitting a retrieve UE context request message for the wireless device to an anchor base station of the wireless device based on at least one of an AS context identifier, an RNA identifier, a base station identifier, a resume identifier, and/or a cell identifier received from the wireless device. In response to fetching a UE context, a base station may transmit a path switch request for a wireless device to a core network entity (e.g. AMF, MME, and/or the like). A core network entity may update a downlink tunnel endpoint identifier for one or more bearers established for the wireless device between a user plane core network entity (e.g. UPF, S-GW, and/or the like) and a RAN node (e.g. the base station), e.g. changing a downlink tunnel endpoint identifier from an address of the anchor base station to an address of the base station.
A gNB may communicate with a wireless device via a wireless network employing one or more new radio technologies. The one or more radio technologies may comprise at least one of: multiple technologies related to physical layer; multiple technologies related to medium access control layer; and/or multiple technologies related to radio resource control layer. Example embodiments of enhancing the one or more radio technologies may improve performance of a wireless network. Example embodiments may increase the system throughput, or data rate of transmission. Example embodiments may reduce battery consumption of a wireless device. Example embodiments may improve latency of data transmission between a gNB and a wireless device. Example embodiments may improve network coverage of a wireless network. Example embodiments may improve transmission efficiency of a wireless network.
In an example, a wireless device may receive configuration parameters of a plurality of configured grant configurations on cell. In an example, the plurality of configured grant configurations may be for a BWP of a cell. The wireless device may receive one or more messages comprising configuration parameters of the plurality of configured grant configurations. In an example, a configured grant configuration in the plurality of configured grant configurations may be configured with a configured grant configuration identifier. In an example, a configured grant configuration in the plurality of configured grant configurations may be a Type 1 configured grant configuration. In an example, a configured grant configuration in the plurality of configured grant configurations maybe a Type 2 configured grant configuration.
In an example, a wireless device may support separate activation of different configured grant Type 2 configurations for a BWP of a serving cell. In an example, for separate activation of the different configured grant Type 2 configurations, the wireless device may receive separate activation DCIs (e.g., one DCI for each configured grant configuration to be activated).
In an example, the wireless device may support joint activation of a plurality of configured grant configurations. With joint activation of multiple configured grant configuration, the wireless device may receive one DCI for activation of two or more configured grant Type 2 configurations.
In an example, a wireless device may support separate release of different configured grant Type 2 configurations for a BWP of a serving cell. In an example, for separate release of the different configured grant Type 2 configurations, the wireless device may receive separate DCIs indicating release (e.g., one DCI for each configured grant configuration to be release).
In an example, the wireless device may support joint release of a plurality of configured grant configurations. With joint release of multiple configured grant configuration, the wireless device may receive one DCI for release of two or more configured grant Type 2 configurations.
In an example, a wireless device may be configured with one or more first configured grant configuration of a first Type and one or more second configured grant configurations of a second type. The first type configured grant configuration may be a Type 1 configured grant configuration. A wireless device may activate a plurality of resources in response to receiving configuration parameters of a Type 1 configured grant. The second type configured grant configuration may be a Type 2 configured grant. A wireless device may activate a plurality of resources in response to receiving configuration parameters of a Type 2 configured grant and receiving an activation DCI indicating activating the Type 2 configured grant.
In an example, a wireless device support multiple active configured grant configurations with different Types for a given BWP of a serving cell. In an example, the wireless device may indicate (e.g., in a capability message), that the wireless device may support multiple active configured grant configurations of different types. The wireless device may receive (e.g., in response to indicating the support of active configured grant configurations with different Types for a given BWP of a serving cell), configuration parameters and/or activation DCIs indicating multiple active configured grant with different Types (e.g., one or more active configured grant Type 1 and one or more active configured grant Type 2) on a BWP of a cell of the wireless device.
In an example, a wireless device may receive configuration parameters of a plurality of downlink SPS configurations. In an example, the plurality of downlink SPS configurations may be for a downlink BWP of a cell. The wireless device may receive one or more messages comprising configuration parameters of the plurality of downlink SPS configurations. In an example, a downlink SPS configuration in the plurality of downlink SPS configurations may be configured with a downlink SPS configuration identifier.
In an example, a wireless device may support separate activation for different DL SPS configurations for a given BWP of a serving cell. In an example, for separate activation of different DL SPS configurations for a given BWP of a serving cell, the wireless device may receive separate activation DCIs (e.g., one DCI for each downlink SPS configuration to be activated).
In an example, the wireless device may support joint activation of a plurality of downlink SPS configurations. With joint activation of multiple downlink SPS configuration, the wireless device may receive one DCI for activation of two or more downlink SPS configurations.
In an example, a wireless device may support separate release of different DL SPS configurations for a given BWP of a serving cell. In an example, for separate release of different DL SPS configurations for a given BWP of a serving cell, the wireless device may receive separate release DCIs (e.g., one DCI for each downlink SPS configuration to be released).
In an example, a wireless device may support joint release of a plurality of downlink SPS configurations. With joint release of multiple downlink SPS configurations, the wireless device may receive one DCI for release of two or more downlink SPS configurations.
In an example downlink SPS may be configured for a wireless device to support periodic traffic for various URLLC use cases such as power distribution, factory automation, and transport industry (including remote driving. Support of multiple simultaneous active DL SPS configurations for a given BWP may reduce the latency and provide the possibility to support different service types for a wireless device.
In an example, a downlink SPS configuration may indicate a periodicity of downlink SPS assignments. In an example, a periodicity of shorter than 1 slot may be supported by a wireless device. In an example, support for multiple active downlink SPS configurations on a cell (e.g., a DL BWP of a cell) and/or shorter periodicities of DL SPS may require enhancements to HARQ-ACK codebook determination processes. In an example, a larger PUCCH payload may be needed to carry the HARQ ACK bits corresponding to several SPS PDSCH in the a slot. In an example, in case of DL SPS with dynamic scheduling, the size of semi-static HARQ codebook may need to be increased to support DL SPS with smaller periodicities. In an example, a number of HARQ-ACK bits, bit position, and PUCCH resource determination need to be taken into account. In an example, HARQ-ACK for multiple SPS PDSCHs may need to be aggregated.
In an example, a wireless device may receive configuration parameters of an uplink configured grant configuration on a bandwidth part of a cell. In an example, the wireless device may activate a plurality of uplink resources, associated with the uplink configured grant configuration, based on the receiving the configuration parameters and the uplink configured grant configuration being of a first type (e.g., Type 1 configured grant). In an example, the wireless device may activate a plurality of uplink resources, associated with the uplink configured grant configuration, based on the receiving the configuration parameters and an activation DCI indicating activation of the uplink configured grant configuration and the uplink configured grant configuration being of a second type (e.g., Type 2 configured grant).
In an example, the wireless device may transmit a transport block based on a first uplink resource, associated with an uplink configured grant configuration, in response to having data that can be transmitted via the first uplink resource. The uplink configured grant configuration may be associated with a first service type (e.g., URLLC) and the wireless device may transmit at the first resource if data corresponding to the first service type being available.
The wireless device may receive a DCI indicating an uplink grant (e.g., a dynamic grant) for transmission via a second resource that has overlap (e.g., time overlap) and/or conflict/collision with the first resource. A prioritization procedure may be used to determine the priority between the configured grant (for the first uplink resource) and the dynamic grant (for the second uplink resource).
In an example, the priority may be determined at the MAC layer, e.g., based on data in a first transport block for transmission via the dynamic grant and data of a second transport block for transmission based on the configured grant. The MAC layer may indicate to the Physical layer to transmit or drop which transport block.
In an example, the priority may be determined at the Physical layer based on Physical layer channel(s)/signal(s)/parameter(s) to enable the prioritization. In an example, to select between the dynamic grant and the configured grant, one or more parameters in a DCI indicating the dynamic grant may be used. In an example, a length and/or resource priority or a priority indicator in the DCI may indicate the priority.
In an example, Semi-Persistent Scheduling (SPS) may be configured by RRC per Serving Cell and per BWP. In an example, activation and deactivation of the DL SPS may be independent among the Serving Cells. For the DL SPS, a DL assignment may be provided by PDCCH, and stored or cleared based on L1 signalling indicating SPS activation or deactivation.
In an example, RRC may configure the following parameters when SPS is configured: cs-RNTI: CS-RNTI for activation, deactivation, and retransmission; nrofHARQ-Processes: the number of configured HARQ processes for SPS; periodicity: periodicity of configured downlink assignment for SPS.
In an example, when SPS is released by upper layers, the corresponding configurations may be released.
In an example, in response to a downlink assignment being configured for SPS, the MAC entity may consider sequentially that the Nth downlink assignment occurs in the slot for which:
(numberOfSlotsPerFrame×SFN+slot number in the frame)=[(numberOfSlotsPerFrame×SFNstart time+slotstart time)+N×periodicity×numberOfSlotsPerFrame/10]modulo (1024×numberOfSlotsPerFrame)
where SFNstart time and slotstart time are the SFN and slot, respectively, of the first transmission of PDSCH where the configured downlink assignment was (re-)initialized.
In an example, two types of transmission without dynamic grant may be configured: configured grant Type 1 where an uplink grant is provided by RRC, and stored as configured uplink grant; and configured grant Type 2 where an uplink grant is provided by PDCCH, and stored or cleared as configured uplink grant based on L1 signalling indicating configured uplink grant activation or deactivation.
In an example, Type 1 and Type 2 configured grants may be configured by RRC per Serving Cell and per BWP. In an example, multiple configurations may be active simultaneously on different Serving Cells. For Type 2 configured grant, activation and deactivation may be independent among the Serving Cells.
In an example, RRC may configure the following parameters when the configured grant Type 1 is configured: cs-RNTI: CS-RNTI for retransmission; periodicity: periodicity of the configured grant Type 1; timeDomainOffset: Offset of a resource with respect to SFN=0 in time domain; timeDomainAllocation: Allocation of configured uplink grant in time domain which contains startSymbolAndLength; nrofHARQ-Processes: the number of HARQ processes for configured grant.
In an example, RRC may configure the following parameters when the configured grant Type 2 is configured: cs-RNTI: CS-RNTI for activation, deactivation, and retransmission; periodicity: periodicity of the configured grant Type 2; nrofHARQ-Processes: the number of HARQ processes for configured grant.
In an example, upon configuration of a configured grant Type 1 for a Serving Cell by upper layers, the MAC entity may: store the uplink grant provided by upper layers as a configured uplink grant for the indicated Serving Cell; and initialize or re-initialize the configured uplink grant to start in the symbol according to timeDomainOffset and S (derived from SLIV), and to reoccur with periodicity.
In an example, after an uplink grant is configured for a configured grant Type 1, the MAC entity may consider that the uplink grant recurs associated with each symbol for which:
[(SFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot)+(slot number in the frame×numberOfSymbolsPerSlot)+symbol number in the slot]=(timeDomainOffset×numberOfSymbolsPerSlot+S+N×periodicity)modulo(1024×numberOfSlotsPerFrame×numberOfSymbolsPerSlot), for all N>=0.
In an example, after an uplink grant is configured for a configured grant Type 2, the MAC entity may consider that the uplink grant recurs associated with each symbol for which:
[(SFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot)+(slot number in the frame×numberOfSymbolsPerSlot)+symbol number in the slot]=[(SFNstart time×numberOfSlotsPerFrame×numberOfSymbolsPerSlot+slotstart time×numberOfSymbolsPerSlot+symbolstart time)+N×periodicity]modulo(1024×numberOfSlotsPerFrame×numberOfSymbolsPerSlot), for all N>=0,
where SFNstart time, slotstart time, and symbolstart time are the SFN, slot, and symbol, respectively, of the first transmission opportunity of PUSCH where the configured uplink grant was (re-)initialized.
In an example, when a configured uplink grant is released by upper layers, all the corresponding configurations may be released and all corresponding uplink grants shall be cleared.
In an example, if the configured uplink grant confirmation has been triggered and not cancelled; and if the MAC entity has UL resources allocated for new transmission, a MAC entity may instruct the Multiplexing and Assembly procedure to generate an Configured Grant Confirmation MAC CE and cancel the triggered configured uplink grant confirmation.
In an example, for a configured grant Type 2, the MAC entity may clear the configured uplink grant in response to a first transmission of Configured Grant Confirmation MAC CE triggered by the configured uplink grant deactivation. In an example, retransmissions except for repetition of configured uplink grants may use uplink grants addressed to CS-RNTI.
In an example, a MAC entity may use a Power Headroom reporting procedure to provide a serving base station with the following information: Type 1 power headroom: the difference between the nominal UE maximum transmit power and the estimated power for UL-SCH transmission per activated Serving Cell; Type 2 power headroom: the difference between the nominal UE maximum transmit power and the estimated power for UL-SCH and PUCCH transmission on SpCell of another MAC entity (e.g., E-UTRA MAC entity in EN-DC case); and Type 3 power headroom: the difference between the nominal UE maximum transmit power and the estimated power for SRS transmission per activated Serving Cell.
In an example, RRC may control Power Headroom reporting by configuring the following parameters: phr-PeriodicTimer; phr-ProhibitTimer; phr-Tx-PowerFactorChange; phr-Type2OtherCell; phr-ModeOtherCG; multiplePHR.
In an example, a Power Headroom Report (PHR) may be triggered if phr-ProhibitTimer expires or has expired and the path loss has changed more than phr-Tx-PowerFactorChange dB for at least one activated Serving Cell of any MAC entity which is used as a pathloss reference since the last transmission of a PHR in this MAC entity when the MAC entity has UL resources for new transmission. In an example, the path loss variation for one cell assessed above is between the pathloss measured at present time on the current pathloss reference and the pathloss measured at the transmission time of the last transmission of PHR on the pathloss reference in use at that time, irrespective of whether the pathloss reference has changed in between.
In an example, a Power Headroom Report (PHR) may be triggered if phr-PeriodicTimer expires.
In an example, a Power Headroom Report (PHR) may be triggered upon configuration or reconfiguration of the power headroom reporting functionality by upper layers, which is not used to disable the function.
In an example, a Power Headroom Report (PHR) may be triggered in response to activation of an SCell of any MAC entity with configured uplink.
In an example, a Power Headroom Report (PHR) may be triggered in response to addition of the PSCell (e.g., if PSCell is newly added or changed).
In an example, a Power Headroom Report (PHR) may be triggered if phr-ProhibitTimer expires or has expired, when the MAC entity has UL resources for new transmission, and the following is true for an activated Serving Cells of any MAC entity with configured uplink: there are UL resources allocated for transmission or there is a PUCCH transmission on this cell, and the required power backoff due to power management (e.g., as allowed by P-MPRc) for this cell has changed more than phr-Tx-PowerFactorChange dB since the last transmission of a PHR when the MAC entity had UL resources allocated for transmission or PUCCH transmission on this cell. In an example, the MAC entity may avoid triggering a PHR when the required power backoff due to power management decreases only temporarily (e.g. for up to a few tens of milliseconds) and it may avoid reflecting such temporary decrease in the values of PCMAX,f,c/PH when a PHR is triggered by other triggering conditions.
In an example, if the MAC entity has UL resources allocated for a new transmission and if it is the first UL resource allocated for a new transmission since the last MAC reset, the MAC entity may start phr-PeriodicTimer.
In an example, if the MAC entity has UL resources allocated for a new transmission and if the Power Headroom reporting procedure determines that at least one PHR has been triggered and not cancelled; and if the allocated UL resources can accommodate the MAC CE for PHR which the MAC entity is configured to transmit, plus its subheader, as a result of logical channel prioritization (LCP) procedure, if multiplePHR with value true is configured: for each activated Serving Cell with configured uplink associated with a MAC entity, the MAC entity may: obtain the value of the Type 1 or Type 3 power headroom for the corresponding uplink carrier; if this MAC entity has UL resources allocated for transmission on this Serving Cell; or if the other MAC entity, if configured, has UL resources allocated for transmission on this Serving Cell and phr-ModeOtherCG is set to real by upper layers: obtain the value for the corresponding PCMAX,f,c field from the physical layer.
In an example, if the MAC entity has UL resources allocated for a new transmission and if the Power Headroom reporting procedure determines that at least one PHR has been triggered and not cancelled; and if the allocated UL resources can accommodate the MAC CE for PHR which the MAC entity is configured to transmit, plus its subheader, as a result of logical channel prioritization (LCP) procedure, if multiplePHR with value true is configured: if phr-Type2OtherCell with value true is configured: if the other MAC entity is E-UTRA MAC entity: obtain the value of the Type 2 power headroom for the SpCell of the other MAC entity (i.e. E-UTRA MAC entity); the MAC entity may obtain the value of the Type 2 power headroom for the SpCell of the other MAC entity (e.g., E-UTRA MAC entity); and if phr-ModeOtherCG is set to real by upper layers: the MAC entity may obtain the value for the corresponding PCMAX,f,c field for the SpCell of the other MAC entity (i.e. E-UTRA MAC entity) from the physical layer.
In an example, if the MAC entity has UL resources allocated for a new transmission and if the Power Headroom reporting procedure determines that at least one PHR has been triggered and not cancelled; and if the allocated UL resources can accommodate the MAC CE for PHR which the MAC entity is configured to transmit, plus its subheader, as a result of logical channel prioritization (LCP) procedure, if multiplePHR with value true is configured: the MAC entity may instruct a Multiplexing and Assembly procedure to generate and transmit the Multiple Entry PHR MAC CE based on the values reported by the physical layer.
In an example, if the MAC entity has UL resources allocated for a new transmission and if the Power Headroom reporting procedure determines that at least one PHR has been triggered and not cancelled; and if the allocated UL resources can accommodate the MAC CE for PHR which the MAC entity is configured to transmit, plus its subheader, as a result of logical channel prioritization (LCP) procedure, Single Entry PHR format may be used. The MAC entity may obtain the value of the Type 1 power headroom from the physical layer for the corresponding uplink carrier of the PCell. The MAC entity may instruct the Multiplexing and Assembly procedure to generate and transmit the Single Entry PHR MAC CE based on the values reported by the physical layer.
In an example, if the MAC entity has UL resources allocated for a new transmission and if the Power Headroom reporting procedure determines that at least one PHR has been triggered and not cancelled; and if the allocated UL resources can accommodate the MAC CE for PHR which the MAC entity is configured to transmit, plus its subheader, as a result of logical channel prioritization (LCP) procedure, the MAC entity may start or restart phr-PeriodicTimer; start or restart phr-ProhibitTimer; and cancel all triggered PHR(s).
In example, a Single Entry PHR MAC CE may be identified by a MAC subheader with a corresponding LCID.
The single Entry PHR MA CE may have a fixed size and may consist of two octets as shown in
In an example, a Multiple Entry PHR MAC CE may be identified by a MAC subheader with a corresponding LCID.
In an example, a Multiple Entry PHR may have a variable size, and may include a bitmap, a Type 2 PH field and an octet containing the associated PCMAX,f,c field (if reported) for SpCell of the other MAC entity, a Type 1 PH field and an octet containing the associated PCMAX,f,c field (if reported) for the PCell. It further may include, in ascending order based on the ServCellIndex, one or multiple of Type X PH fields and octets containing the associated PCMAX,f,c fields (if reported) for Serving Cells other than PCell indicated in the bitmap. X may be either 1 or 3.
In an example, a presence of Type 2 PH field for SpCell of the other MAC entity may be configured by phr-Type2OtherCell with value true.
In an example, a single octet bitmap may be used for indicating the presence of PH per Serving Cell when the highest ServCellIndex of Serving Cell with configured uplink is less than 8, otherwise four octets may be used.
In an example, the MAC entity may determine whether PH value for an activated Serving Cell is based on real transmission or a reference format by considering the configured grant(s) and downlink control information which has been received until and including the PDCCH occasion in which the first UL grant for a new transmission is received since a PHR has been triggered if the PHR MAC CE is reported on an uplink grant received on the PDCCH or until the first uplink symbol of PUSCH transmission minus PUSCH preparation time if the PHR MAC CE is reported on a configured grant.
In an example, for a band combination in which the UE does not support dynamic power sharing, the UE may omit the octets containing Power Headroom field and PCMAX,f,c field for Serving Cells in the other MAC entity except for the PCell in the other MAC entity and the reported values of Power Headroom and PCMAX,f,c for the PCell may be up to UE implementation.
In an example, the PHR MAC CEs are defined as follows: Ci may indicate the presence of a PH field for the Serving Cell with ServCellIndex i. The Ci field set to 1 may indicate that a PH field for the Serving Cell with ServCellIndex i is reported. The Ci field may be set to 0 and may indicate that a PH field for the Serving Cell with ServCellIndex i is not reported; R may be a Reserved bit, set to 0; V may indicate if the PH value is based on a real transmission or a reference format. For Type 1 PH, the V field set to 0 may indicate real transmission on PUSCH and the V field set to 1 may indicate that a PUSCH reference format is used. For Type 2 PH, the V field set to 0 may indicate real transmission on PUCCH and the V field set to 1 may indicate that a PUCCH reference format is used. For Type 3 PH, the V field set to 0 may indicate real transmission on SRS and the V field set to 1 may indicate that an SRS reference format is used. Furthermore, for Type 1, Type 2, and Type 3 PH, the V field set to 0 may indicate the presence of the octet containing the associated PCMAX,f,c field, and the V field set to 1 may indicate that the octet containing the associated PCMAX,f,c field is omitted; Power Headroom (PH) may indicate the power headroom level. The length of the field may be 6 bits. The reported PH and the corresponding power headroom levels are shown in
In an example, the MAC entity may not generate a MAC PDU for the HARQ entity if the following conditions are satisfied: the MAC entity is configured with skipUplinkTxDynamic with value true and the grant indicated to the HARQ entity was addressed to a C-RNTI, or the grant indicated to the HARQ entity is a configured uplink grant; and there is no aperiodic CSI requested for this PUSCH transmission; and the MAC PDU includes zero MAC SDUs; and the MAC PDU includes the periodic BSR and there is no data available for any LCG, or the MAC PDU includes only the padding BSR.
In an example, an uplink grant for a PDCCH occasion may be received for a Serving Cell on the PDCCH for the MAC entity's CS-RNTI and the NDI in the received HARQ information may be 1. The MAC entity may consider the NDI for the corresponding HARQ process not to have been toggled. The MAC entity may start or restart the configuredGrantTimer for the corresponding HARQ process, if configured. The MAC entity may deliver the uplink grant and the associated HARQ information to the HARQ entity.
In an example, an uplink grant for a PDCCH occasion may be received for a Serving Cell on the PDCCH for the MAC entity's CS-RNTI and the NDI in the received HARQ information may be 0. If PDCCH contents indicate configured grant Type 2 deactivation, the MAC entity may trigger configured uplink grant confirmation. If PDCCH contents indicate configured grant Type 2 activation, the MAC entity may trigger configured uplink grant confirmation; the MAC entity may store the uplink grant for this Serving Cell and the associated HARQ information as configured uplink grant; the MAC entity may initialize or re-initialize the configured uplink grant for this Serving Cell to start in the associated PUSCH duration and to recur according to rules; and the MAC entity may stop the configuredGrantTimer for the corresponding HARQ process, if running.
In an example, a Configured Grant Confirmation MAC CE may be identified by a MAC subheader with a corresponding LCID. The LCID for a Configured Grant Conformation MAC CE may be pre-configured.
In an example, a PDCCH for configured UL grant Type 2 activation, configured UL grant Type 2 release, DL SPS activation and DL SPS release may be validated before activation/release of resources. In an example, in response to a CRC of a corresponding DCI format is scrambled with a CS-RNTI provided by the RRC parameter cs-RNTI, and a new data indicator field for the enabled transport block is set to ‘0’, a wireless device may validate the PDCCH for scheduling activation or scheduling release of a DL SPS assignment or configured UL grant Type 2.
In an example, validation of a DCI format may be achieved if fields of a DCI format are set according to pre-defined values. In an example, if validation is achieved, a UE may consider information in the DCI format as a valid activation or valid release of DL SPS or configured UL grant Type 2. If validation is not achieved, the UE may discard the information in the DCI format.
In an example, a wireless device may provide HARQ-ACK information in response to a SPS PDSCH release after N symbols from the last symbol of a PDCCH providing the SPS PDSCH release. In an example, N may be based on wireless device capability. For a first wireless device processing capability and for the SCS of the PDCCH reception, N=10 for 15 kHz, N=12 for 30 kHz, N=22 for 60 kHz, and N=25 for 120 kHz. For a wireless device with capability 2 in FR1 and for the SCS of the PDCCH reception, N=5 for 15 kHz, N=5.5 for 30 kHz, and N=11 for 60 kHz.
In an example, an IE ConfiguredGrantConfig may be used to configure uplink transmission without dynamic grant according to two possible schemes. The actual uplink grant may either be configured via RRC (type1) or provided via the PDCCH (addressed to CS-RNTI) (type2).
In an example, a parameter antennaPort may Indicates the antenna port(s) to be used for this configuration. In an example, a parameter cg-DMRS-Configuration may indicate DMRS configuration. In an example, a parameter configuredGrantTimer may indicate the initial value of a configured grant timer in multiples of periodicity. In an example, a parameter frequencyDomainAllocation may indicate the frequency domain resource allocation. In an example, a parameter dmrs-SeqInitialization may be configured field if transformPrecoder is disabled. Otherwise the field may be absent. In an example, an intraSlot value of a parameter frequencyHopping may indicate enabling of ‘Intra-slot frequency hopping’ and a value interSlot may indicate enabling ‘Inter-slot frequency hopping’. If the field is absent, frequency hopping may not be configured. In an example, a parameter frequencyHoppingOffset may indicate enabling intra-slot frequency hopping with the given frequency hopping offset. Frequency hopping offset may be used when frequency hopping is enabled. In an example, a parameter mcs-Table may indicates the MCS table the UE may use for PUSCH without transform precoding. If the field is absent the UE may apply the value qam64. In an example, a parameter mcs-TableTransformPrecoder may indicate the MCS table the UE may use for PUSCH with transform precoding. If the field is absent the UE may apply the value qam64. In an example, a parameter mcsAndTBSmay indicate a modulation order, target code rate and TB size. In an example, a parameter nrofHARQ-Processes may indicate the number of HARQ processes configured. It may apply for both Type 1 and Type 2. In an example, a parameter p0-PUSCH-Alpha may indicate an index of the P0-PUSCH-AlphaSet to be used for this configuration. In an example, a parameter periodicity may indicate a Periodicity for UL transmission without UL grant for type 1 and type 2. In an example, powerControlLoopToUse may indicate closed control loop to apply. In an example, a parameter repK-RV may indicate the redundancy version (RV) sequence to use. The network may configure this field if repetitions are used, e.g., if repK is set to n2, n4 or n8. Otherwise, the field may be absent. In an example, a parameter repK may indicate a number of repetitions of K. In an example, a parameter resourceAllocation may indicate Configuration of resource allocation type 0 and resource allocation type 1. For Type 1 UL data transmission without grant, “resourceAllocation” may be resourceAllocationType0 or resourceAllocationType1. In an example, a parameter rrc-ConfiguredUplinkGrant may indicate configuration for “configured grant” transmission with fully RRC-configured UL grant (Type1). If this field is absent the UE uses UL grant configured by DCI addressed to CS-RNTI (Type2). In an example, Type 1 configured grant may be configured for UL or SUL, but not for both simultaneously. In an example, a parameter timeDomainAllocation may indicate a combination of start symbol and length and PUSCH mapping type. In an example, a parameter transformPrecoder may enable or disable transform precoding for type1 and type2. If the field is absent, the UE may enable or disable transform precoding in accordance with the field msg3-transformPrecoder in RACH-ConfigCommon.
In an example, an IE SPS-Config may be used to configure downlink semi-persistent transmission. Downlink SPS may be configured on the SpCell and/or on SCells. In an example, a parameter mcs-Table may indicate the MCS table the wireless device may use for DL SPS. If present, the wireless device may use the MCS table of low-SE 64QAM. In an example, if this field is absent and field mcs-table in PDSCH-Config is set to ‘qam256’ and the activating DCI is of format 1_1, the UE may apply the 256QAM table. Otherwise, the UE may apply a non-low-SE 64QAM table. In an example, a parameter n1PUCCH-AN may indicate HARQ resource for PUCCH for DL SPS. The network may configure the resource either as format0 or format1. The actual PUCCH-Resource may be configured in PUCCH-Config and referred to by its ID.
In an example, a parameter nrofHARQ-Processes may indicate number of configured HARQ processes for SPS DL. In an example, a parameter periodicity may indicate Periodicity for DL SPS.
A wireless device may be configured with a plurality of uplink configured grant configurations on a cell (e.g., on a BWP of the cell). The plurality of uplink configured grant configurations may comprise a first uplink configured grant configuration of a first type (e.g., Type 1 uplink configured grant configuration) and a second uplink configured grant configuration of a second type (e.g. Type 2 uplink configured grant). A second plurality of uplink resources may be activated in response to receiving configuration parameters of the second uplink configured grant configuration. A first plurality of resources may be activated in response to the receiving the configuration parameters of the first uplink configure grant configuration and a first activation DCI. In an example the first plurality of uplink resources may have a first periodicity and the second plurality of uplink resources may have a second periodicity. In an example, a first resource of the first plurality of resources and a second resource of the second plurality of resources may have overlap in time (e.g., in one or more symbols). Transmission of transport blocks via the first resource and the second resource may increase wireless device complexity and degrade network performance. There is a need to enhance legacy processes when there is a conflict between a first resource of a first Type configured grant and a second resource of a second type configured grant. Example embodiments enhance the legacy processes.
In an example embodiment as shown in
The wireless device may activate a first plurality of resources, associated with the first configured grant configuration, comprising a first resource. The activation may, based on a first type of the first configured grant configuration, be in response to the receiving the first configuration parameters or in response to the receiving the first configuration parameters and a first DCI indicating activation of the first configured grant configuration. The wireless device may activate a second plurality of resources, associated with the second configured grant configuration, comprising a second resource. The activation may, based on a second type of the second configured grant configuration, be in response to the receiving the first configuration parameters or in response to the receiving the second configuration parameters and a second DCI indicating activation of the second configured grant configuration.
In an example, receiving a Type 1 configured grant configuration may indicate activation of a plurality of resource. In an example, receiving a Type 2 configured grant configuration and an activation DCI indicating the activation of the Type2 configured grant configuration may indicate activation of a plurality of resources.
The wireless device may determine, as a selected resource, one of the first resource associated with the first configured grant configuration and the second resource associated with the second configured grant configuration. The first resource and the second resource may overlap in one or more symbols in time.
In an example embodiment as shown in
In an example, the selected resource may be the first resource, associated with the first configured grant configuration, based on the first type of the first configured grant configuration being Type 1 and the second type of the second configured grant configuration being Type 2.
In an example, the selected resource may be the second resource, associated with the second configured grant configuration, based on the first type of the first configured grant configuration being Type 1 and the second type of the second configured grant configuration being Type 2.
In an example, the determining/selecting the one of the first resource and the second resource may be based on the first type of the first configured grant configuration and the second type of the second configured grant configuration and may further be based on a first service type associated with the first configured grant configuration and a second service type associated with the second configured grant configuration. In an example, the configuration parameters of the first configured grant configuration may indicate the first service type. Ina an example, the configuration parameters of the second configured grant configuration may indicate the second service type. In an example, the configuration parameters of the first configured grant configuration may comprise one or more first transmission parameters of transport blocks via resources associated with the first configured grant configuration. The one or more first transmission parameters may indicate the first service type. In an example, the configuration parameters of the second configured grant configuration may comprise one or more second transmission parameters of transport blocks via resources associated with the second configured grant configuration. The one or more second transmission parameters may indicate the second service type. In an example, the first service type may be one of a plurality of service types. In an example, the second service type may be one of a plurality of service types. The plurality of service types may comprise eMBB, URLLC, etc.
In an example, the determining/selecting the one of the first resource and the second resource may be based on an activation DCI indicating activation of one or more of the first configured grant configuration and the second configured grant configuration. In an example, the activation DCI may indicate a service type. The determining/selecting may be based on the service type. In an example, the service type may be URLLC.
In an example, the activation DCI may be associated with a radio network temporary identifier (RNTI). The determining/selecting may be based on the RNTI associated with the activation DCI. In an example, the RNTI may indicate a service type. The determining/selecting may be based on the service type. In an example, the service type may be URLLC.
In an example embodiment as shown in
The wireless device may receive a first activation DCI. The first activation DCI may be associated with a first RNTI. In an example a first CRC field of the first activation DCI may be scrambled with the first RNTI. The first DCI may further be associated with the first configured grant configuration (e.g., may comprise a field indicating a first identifier of the first configured grant configuration). The first activation DCI may indicate activation of a first plurality of resources associated with the first configured grant configuration. The wireless device may activate the first plurality of resources based on the receiving the first activation DCI.
The wireless device may receive a second activation DCI. The second activation DCI may be associated with a second RNTI. In an example a second CRC field of the second activation DCI may be scrambled with the second RNTI. The second DCI may further be associated with second first configured grant configuration (e.g., may comprise a field indicating a second identifier of the second configured grant configuration). The second activation DCI may indicate activation of a second plurality of resources associated with the second configured grant configuration. The wireless device may activate the second plurality of resources based on the receiving the second activation DCI.
In an example, the first RNTI may indicate a first service type. The second RNTI may indicate a second service type. The wireless device may, based on the service type indicated by an RNTI associated with a DCI, determine logical channels to be included in a transport block, wherein the transport block is transmitted via a resource activated by the DCI. The service type may indicate the one or more logical channels. In an example, the first service type may be one of a plurality of service types comprising URLLC, eMBB, etc. The second service type may be one of a plurality of service types comprising URLLC, eMBB, etc. In an example, there may be a mapping between logical channels and a service type.
The first plurality of resources may comprise a first resource and the second plurality of resources may comprise a second resource. The first resource and the second resource may overlap, e.g., in one or more symbols. The wireless device may determine/select, as a selected resource, one of the first resource and the second resource based on the first RNTI associate with the first activation DCI and the second RNTI associated with the second activation DCI. The wireless device may transmit a transport block via the selected resource. The wireless device may transmit a transport block via the selected resource and based on configuration parameters of a configured grant associate with the selected resource.
In an example, the wireless device may select the first resource based on the first RNTI indicating that the first service type is a first type of service. In an example, the first type of service may be URLLC.
In an example embodiment as shown in
The one or more messages may further comprise a priority parameter. The priority parameter may indicate a priority of a first type configured grant configuration over a second type configured grant configuration. In an example, the priority parameter may indicate priority of a first type configured grant over a second type configured grant if one or more conditions are satisfied. In an example, the one or more conditions may be based one or more first logical channels and/or service type, wherein the data of the one or more first logical channels and/or service type is transmitted via a first resource of the first configured grant configuration and one or more second logical channels/service types, wherein data of the one or more second logical channels/service types are transmitted via a second resource of the second configured grantconfiguation.
The wireless device may activate a first plurality of resources, associated with the first configured grant configuration, comprising a first resource. The activation may, based on a first type of the first configured grant configuration, be in response to the receiving the first configuration parameters or in response to the receiving the first configuration parameters and a first DCI indicating activation of the first configured grant configuration. The wireless device may activate a second plurality of resources, associated with the second configured grant configuration, comprising a second resource. The activation may, based on a second type of the second configured grant configuration, be in response to the receiving the first configuration parameters or in response to the receiving the second configuration parameters and a second DCI indicating activation of the second configured grant configuration.
In an example, receiving a Type 1 configured grant configuration may indicate activation of a plurality of resource. In an example, receiving a Type 2 configured grant configuration and an activation DCI indicating the activation of the Type2 configured grant configuration may indicate activation of a plurality of resources.
The wireless device may determine, as a selected resource, one of the first resource associated with the first configured grant configuration and the second resource associated with the second configured grant configuration. The first resource and the second resource may overlap in one or more symbols in time. The determining may be based on the priority parameter. In an example the determining may be based on the priority parameter, the first type of the first configured grant and the second type of the second configured grant.
In an example, the first type of the first configure grant configuration is one of the Type 1 and Type 2. The second type of the second configured grant configuration is one of the Type 1 and Type 2. In an example, receiving a type 1 configured grant configuration indicates activation of a plurality of resources. In an example, receiving a type 2 configured grant configuration and a downlink control indicates activation of a plurality of resources. In an example, the first type configured grant configuration is one of a type 1 configured grant configuration and a type 2 configured grant configuration. The second type configured grant configuration is one of a type 1 configured grant configuration and a type 2 configured grant configuration.
A wireless device may be configured with an uplink configured grant configuration. The wireless device may receive an activation DCI and in response to the receiving the activation DCI, a plurality of uplink resources, associated with the uplink configured grant configuration, may be activated. The wireless device may or may not transmit based on a first resource of the plurality resources based on availability of data or availability of data corresponding to a service type associated with the uplink configured grant configuration. The wireless device may receive a second DCI comprising a second uplink grant indicating a second resource which has overlap with the first resource. The legacy processes for determining power and power headroom report (if triggered) leads to inefficient and degraded network performance for example inefficient scheduling by the base station. There is a need to enhance the legacy power and PHR determination processes in response to conflict between dynamic and configured grants. Example embodiments enhance the legacy power and PHR determination processes in case of conflict between dynamic and configured grants.
In an example embodiment as shown in
The wireless device may receive a downlink control information (DCI) indicating a first resource of the cell for transmission of a transport block. The DCI may comprise transmission parameters (e.g., power control parameters, HARQ related parameters, etc.) for transmission of the transport block. The first resource, indicated by the DCI, may overlap with a second resource in the plurality of resources activated based on the configured grant configuration. In an example, the first resource may overlap (e.g., have conflict) with the second resource in one or more symbols.
The wireless device may determine, as a selected resource. one of the first resource (for transmission of the transport block based on the DCI) or the second resource (for transmission of a second transport block based on the configured grant configuration). The determining the one of the first resource and the second resource may be based on one or more criteria. The wireless device may transmit a transmission (e.g., transport block or the second transport block based on the selection) via the selected resource and may drop a transmission (e.g., transport block or the second transport block based on the selection) based on the unselected resource.
In an example, the transport block may comprise one or more first logical channels and the second transport block may comprise one or more second logical channels. The determining one of the first resource and the second resource may be based on the one or more first logical channels and the one or more second logical channels. In an example, the DCI may indicate the one or more first logical channels. In an example, the first resource may be associated with a service type and the second resource may be associated with a second service type. The first service type may be one a plurality of service types comprising eMBB, URLLC, etc. In an example, the DCI may indicate the first service type. The second service type may be one a plurality of service types comprising eMBB, URLLC, etc. The determining one of the first resource and the second resource may be based on the first service type and the second service type.
In an example embodiment as shown in
In an example, calculating the power headroom report further comprises calculating one or more power levels of one or more signals. The wireless device may calculate the power levels assuming that wireless device transmits the transport block based on the DCI regardless of selecting or dropping the transport block. The wireless device may also calculate the one or more power levels assuming that the wireless device drops the transport block and use the power levels calculated with this assumption for transmitting signals in response to the wireless device dropping the transport block. The wireless device may however calculate the power headroom report assuming that wireless device transmits the transport block based on the DCI regardless of selecting or dropping the transport block.
In an example embodiment as shown in
In an example, calculating the power headroom report further comprises calculating one or more power levels of one or more signals. The wireless device may calculate the power levels assuming that wireless device drops the transport block based on the DCI and transmit the second transport block based on the configured grant configuration regardless of selecting or dropping the transport block. The wireless device may also calculate the one or more power levels assuming that the wireless device transmits the transport block and use the power levels calculated with this assumption for transmitting signals in response to the wireless device transmitting the transport block. The wireless device may however calculate the power headroom report assuming that wireless device drops the transport block based on the DCI and transmits the second transport block based on the configured grant configuration regardless of selecting or dropping the transport block.
In an example embodiment as shown in
In an example, calculating the power headroom report further comprises calculating one or more power levels of one or more signals. The wireless device may calculate the power levels assuming that wireless device transmits both of the transport block based on the DCI and transmit the second transport block based on the configured grant configuration regardless of selecting or dropping the transport block. The wireless device may also calculate the one or more power levels assuming that the wireless device transmits the transport block and use the power levels calculated with this assumption for transmitting signals in response to the wireless device transmitting the transport block. The wireless device may also calculate the one or more power levels assuming that the wireless device drops the transport block and transmits the second transport block and use the power levels calculated with this assumption for transmitting signals in response to the wireless device dropping the transport block and transmitting the second transport block. The wireless device may however calculate the power headroom report assuming that wireless device transmits both the transport block based on the DCI and the second transport block based on the configured grant configuration regardless of selecting or dropping the transport block.
In an example embodiment as shown in
In an example, the determining the power headroom may be based on the first power headroom in response to the first power headroom being larger than the second power headroom report.
In an example, the determining the power headroom may be based on the first power headroom in response to the first power headroom being smaller than the second power headroom report.
In an example, the determining the power headroom may be based on the second power headroom in response to the first power headroom being larger than the second power headroom report.
In an example, the determining the power headroom may be based on the second power headroom in response to the first power headroom being smaller than the second power headroom report.
The wireless device may transmit the power headroom. In an example, the wireless device may multiplex the power headroom report with the transport block and transmit it via the first resource in response to the selecting the first resource. In an example, the wireless device may multiplex the power headroom report with the transport block. The wireless device may receive a second DCI indicating a retransmission grant and may transmit the power headroom report based on the second DCI in response to selecting the second resource and dropping the transport block.
In an example, calculating the first power headroom report and the second power headroom report further comprises calculating one or more power levels of one or more signals. To determine the first power headroom report, the wireless device may calculate the power levels assuming that wireless device transmits the transport block based on the DCI and drops the second transport block based on the configured grant configuration. To determine the second power headroom report, the wireless device may calculate the power levels assuming that wireless device drops the transport block based on the DCI and transmits the second transport block based on the configured grant configuration. The wireless device may also calculate the one or more power levels assuming that the wireless device transmits the transport block and use the power levels calculated with this assumption for transmitting signals in response to the wireless device transmitting the transport block. The wireless device may also calculate the one or more power levels assuming that the wireless device drops the transport block and transmits the second transport block and use the power levels calculated with this assumption for transmitting signals in response to the wireless device dropping the transport block and transmitting the second transport block.
In an example embodiment as shown in
In an example, the first resource and the second resource may be for a bandwidth part of the cell. In an example, the first resource and the second resource may have conflict in time domain (e.g., in one or more symbols). In an example, the first resource and the second resource may have conflict in frequency domain (e.g., in one or more resource blocks)
In an example, the wireless device may further transmit a signal of a third resource of a second cell. The third resource may have overlap in time (e.g., in one or more symbols) with the first resource and the second resource. The wireless device may determine the power headroom report based on a power level of the third signal. In an example, the third signal may be a PUSCH for transmission of a TB. In an example, the third signal may be PUCCH. In an example, the third signal may be a sounding reference signal.
In an example embodiment, a wireless device may receive one or more messages comprising: first configuration parameters of a first configured grant configuration on a cell; and second configuration parameters of a second configured grant configuration on the cell. The wireless device may determine/select, as a selected resource, one of: a first resource associated with the first configured grant configuration; and a second resource associated with the second configured grant configuration; wherein: the determining/selecting is based on a first type of the first configured grant configuration and a second type of the second configured grant configuration; and the first resource and the second resource overlap in one or more symbols. The wireless device may transmit a transport block via the selected resource.
In an example, receiving a type 1 configured grant configuration may indicate activation of a plurality of resources; and receiving a type 2 configured grant configuration and a downlink control, associated with the type 2 configured grant configuration, may indicate activation of a plurality of resources.
In an example, the selected resource may be the first resource based on: the first type being type 1; and the second type being type 2.
In an example, the selected resource may be the second resource based on: the first type being type 1; and the second type being type 2.
In an example, the determining may be further based on a first service type associated with the first configured grant configuration and a second service type associated with the second configured grant configuration.
In an example, the first service type may be one of a plurality of service types comprising URLLC and eMBB; and the second service type may be one of a plurality of service types comprising URRLC and eMBB.
In an example, the first configuration parameters may indicate the first service type; and the second configuration parameters may indicate the second service type.
In an example, the determining may be further based on a radio network temporary identifier (RNTI) associated with the downlink control information. In an example, the RNTI may indicate a first service type.
In an example, the selected resource may be the second resource based on the RNTI indicating the first service type. In an example, the first service type may be URLLC.
In an example, the first configured grant configuration and the second configured grant configuration may be for a bandwidth part of the cell.
In an example embodiment, a wireless device may receive one or more messages comprising: a first configured grant configuration on a cell; and a second configured grant configuration on the cell. The wireless device may receive a first downlink control information, associated with a first radio network temporary identifier (RNTI) and the first configured grant configuration, indicating activation of a first plurality of resources. The wireless device may receive a second downlink control information, associated with a second RNTI and the second configured grant configuration, indicating activation of a second plurality of resources. The wireless device may determine/select as a selected resource, one of: a first resource in the first plurality of resources; and a second resource in the second plurality of resources; wherein: the determining/selecting is based on the first RNTI and the second RNTI; and the first resource and the second resource overlap in one or more symbols. The wireless device may transmit a transport block via the selected resource.
In an example, the first RNTI may indicate a first service type; and the second RNTI may indicate a second service type.
In an example, the first service type may be one of a plurality of service types comprising URLLC and eMBB; and the second service type may be one of a plurality of service types comprising URLLC and eMBB.
In an example, the selected resource may be the first resource based on the first RNTI indicating a first service type. In an example, the first service type may be URLLC.
In an example embodiment, a wireless device may receive one or more messages comprising: a first configured grant configuration on a cell; a second configured grant configuration on the cell; and a priority parameter indicating a priority of a first type configured grant configuration over a second type configured grant configuration. The wireless device may determine/select, as a selected resource, one of a first resource associated with the first configured grant configuration; and a second resource associated with the second configured grant configuration; wherein: the determining/selecting is based on a first type of the first configured grant configuration, a second type of the second configured grant configuration and the priority parameter; and the first resource and the second resource overlap in one or more symbols. The wireless device may transmit a transport block via the selected resource.
In an example, the first type of the first configured grant configuration may be one of a type 1 and type 2; and the second type of the second configured grant configuration may be one of a type 1 and type 2.
In an example, receiving a type 1 configured grant configuration may indicate activation of a plurality of resources; and receiving a type 2 configured grant configuration and a downlink control may indicate activation of a plurality of resources.
In an example, the first type configured grant configuration may be one of a type 1 configured grant configuration and a type 2 configured grant configuration; and the second type configured grant configuration may be one of a type 1 configured grant configuration and a type 2 configured grant configuration.
In an example embodiment, a wireless device may receive configuration parameters of a configured grant configuration on a cell. The wireless device may receive a downlink control information indicating a first resource of the cell for transmission of a transport block, wherein the first resource overlaps/has conflict with a second resource associated with the configured grant configuration. The wireless device may determine a power headroom report assuming that the wireless device transmits the transport block regardless of transmitting or dropping the transport block. The wireless device may transmit the power headroom report.
In an example, the wireless device may calculate a transmission power of the transport block assuming that the wireless device transmits the transport block regardless of transmitting or dropping the transport block.
In an example embodiment, a wireless device may receive configuration parameters of a configured grant configuration on a cell. The wireless device may receive a downlink control information indicating a first resource of the cell for transmission of a transport block, wherein the first resource overlaps/has conflict with a second resource associated with the configured grant configuration. The wireless device may determine a power headroom report based on the transmission of the transport block. The wireless device may drop the transport block based on the first resource overlapping/having conflict with a second resource associated with the configured grant configuration. The wireless device may transmit the power headroom report.
In an example embodiment, a wireless device may receive configuration parameters of a configured grant configuration on a cell. The wireless device may receive a downlink control information indicating a first resource of the cell for transmission of a transport block, wherein the first resource overlaps/has conflict with a second resource associated with the configured grant configuration. The wireless device may determine a power headroom report assuming that the wireless device drops the transport block regardless of transmitting or dropping the transport block. The wireless device may transmit the power headroom report.
In an example, the wireless device may calculate a transmission power of a second transport block, for transmission via the second resource, assuming that the wireless device drops the transport block regardless of transmitting or dropping the transport block.
In an example embodiment, a wireless device may receive configuration parameters of a configured grant configuration on a cell. The wireless device may receive a downlink control information indicating a first resource of the cell for transmission of a transport block, wherein the first resource overlaps/has conflict with a second resource associated with the configured grant configuration. The wireless device may determine a power headroom report based on dropping the transport block and transmitting a second transport block via the second resource. The wireless device may transmit the transport block via the first resource. The wireless device may transmit the power headroom report.
In an example embodiment, a wireless device may receive configuration parameters of a configured grant configuration on a cell. The wireless device may receive a downlink control information indicating a first resource of the cell for transmission of a transport block, wherein the first resource overlaps/has conflict with a second resource associated with the configured grant configuration. The wireless device may determine a power headroom report assuming that the wireless device transmits both of the transport block and a transmission via the second resources. The wireless device may transmit the power headroom report.
In an example, the wireless device may calculate a transmission power of the transport block and a second transport block, for transmission via the second resource, assuming that the wireless device transmits both the transport block and the second transport block.
In an example embodiment, a wireless device may receive configuration parameters of a configured grant configuration on a cell. The wireless device may receive a downlink control information indicating a first resource of the cell for transmission of a transport block, wherein the first resource overlaps/has conflict with a second resource associated with the configured grant configuration. The wireless device may select, as a selected transport block, one of the transport block and the second transport block. The wireless device may transmit the selected transport block. The wireless device may transmit the power headroom report.
In an example embodiment, a wireless device may receive configuration parameters of a configured grant configuration on a cell. The wireless device may receive a downlink control information indicating a first resource of the cell for transmission of a transport block, wherein the first resource overlaps/has conflict with a second resource associated with the configured grant configuration. The wireless device may determine a first power headroom based on transmitting the transport block and dropping a second transport block for transmission via the second resource. The wireless device may determine a second power headroom based on dropping the transport block and transmitting the second transport block for transmission via the second resource. The wireless device may determine a power headroom report based on the first power headroom and the second power headroom. The wireless device may transmit the power headroom report.
In an example, the determining the power headroom report may be based on the first power headroom report in response to the first power headroom being larger than the second power headroom.
In an example, the determining the power headroom report may be based on the first power headroom in response to the first power headroom being smaller than the second power headroom.
In an example, the determining the power headroom report may be based on the second power headroom in response to the first power headroom being larger than the second power headroom.
In an example, the second power headroom in response to the first power headroom being smaller than the second power headroom.
In an example, the wireless device may select one of the transport block and a second transport block for transmission via the second resource, based on one or more criteria.
In an example, the transport block comprises one or more first logical channels; the second transport block comprises one or more second logical channels; and the selecting is based on the one or more first logical channels and the one or more second logical channels. In an example, the downlink control information indicates the one or more first logical channels.
In an example, the transport block comprises the power headroom report. In an example, the transport block further comprises one or more first logical channels.
In an example, the wireless device may select the transport block for transmission via the first resource. The wireless device may transmit the transport block via the first resource. The wireless device may drop a second transport block for transmission via the second resource.
In an example, the wireless device may select a second transport block for transmission via the second resource. The wireless device may drop the transport block. The wireless device may receive a second downlink control information indicating retransmission of the transport block. The wireless device may transmit the transport block based on the second downlink control information.
In an example, the first resource and the second resource may be for a bandwidth part of the cell.
In an example, the first resource and the second resource may have conflict in time-domain.
In an example, the first resource and the second resource may overlap in one or more symbols.
In an example, the first resource and the second resource have conflict in frequency-domain.
In an example, the wireless device may transmit a signal via a third resource of a second cell, wherein the third resource overlaps with the first resource and the second resource in time. In an example, the third signal may be a third transport block. In an example, the third signal may be transmitted via a physical uplink control channel. In an example, the third signal may be a sounding reference signal.
In an example embodiment, a wireless device may receive configuration parameters of a configured grant configuration on a cell. The wireless device may receive a first downlink control information indicating a first resource of the cell for transmission of a transport block, wherein: the first resource overlaps/has conflict with a second resource associated with the configured grant configuration; and the transport block is associated with a HARQ process. The wireless device may select, as a selected resource, one of the transport block and a second transport block for transmission via the second resource. The wireless device may transmit one of the transport block or the second transport block via the selected resource, wherein the transmitting fails. The wireless device may receive a second downlink control information indicating a transmission corresponding to the HRQ process. The wireless device may consider a new data indicator field of the second downlink control information not being toggled regardless of a value of the new data indicator field.
According to various embodiments, a device such as, for example, a wireless device, off-network wireless device, a base station, and/or the like, may comprise one or more processors and memory. The memory may store instructions that, when executed by the one or more processors, cause the device to perform a series of actions. Embodiments of example actions are illustrated in the accompanying figures and specification. Features from various embodiments may be combined to create yet further embodiments.
According to an example embodiment, the wireless device may determine a first power headroom value of the cell based on the selected uplink resource. The power headroom report may comprise the first power headroom value of the cell. The wireless device may determine a second power headroom value of the cell based on a resource of the first resource and the second resource, wherein the resource is not the selected uplink resource based on the determining. The power headroom report further comprises the second power headroom value of the cell. The power headroom report does not comprise the second power headroom value of the cell.
According to an example embodiment, the wireless device may determine the first priority of the first configured grant configuration based on one or more first logical channels configured to be mapped to the first configured grant configuration. The wireless device may determine the second priority of the second configured grant configuration based on one or more second logical channels configured to be mapped to the second configured grant configuration. For example, the first priority is a highest logical channel index among the one or more first logical channels. For example, the first priority is a lowest logical channel index among the one or more first logical channels. For example, the second priority is a highest logical channel index among the one or more second logical channels. For example, the second priority is a lowest logical channel index among the one or more second logical channels.
According to an example embodiment, the wireless device may further determine the selected uplink resource based on a first service type associated with the first configured grant configuration; and a second service type associated with the second configured grant configuration. The first service type may be one of a plurality of service types comprising ultra-reliable and low latency communication (URLLC) and enhanced mobile broadband (eMBB). The second service type may be one of the plurality of service types comprising URLLC and eMBB. The first configuration parameters may indicate the first service type. The second configuration parameters may indicate the second service type. For example, the first service type may be URLLC. For example, second first service type may be eMBB.
According to an example embodiment, the wireless device may further determine the selected uplink resource based on a radio network temporary identifier (RNTI) associated with a downlink control information. For example, the RNTI may indicate a first service type. The selected uplink resource may be the second resource based on the RNTI indicating the first service type.
According to an example embodiment, the first type may be URLLC. The first configured grant configuration and the second configuration grant configurations may be configured for a bandwidth part of the cell. For example, the power headroom report may comprise an allowed power of the cell.
According to an example embodiment, a wireless device may receive one or more messages comprising first parameters of a first configured grant configuration of a cell; and a downlink control information (DCI) comprising a second priority and resource assignments for a second resource. The wireless device may trigger a power headroom report. The wireless device may determine, as a selected uplink resource for transmitting the power headroom report, one of: a first resource associated with the first configured grant configuration; and the second resource, wherein the first resource and the second resource overlap in one or more symbols. The wireless device may further determine the selected uplink resource based on a first priority of the first configured grant configuration and the second priority indicated in the DCI. The wireless device may transmit the power headroom report via the selected uplink resource.
According to an example embodiment, a wireless device may receive one or more radio resource control (RRC) messages comprising configuration parameters for a cell. The configuration parameters may comprise first configuration parameters of a first configured grant configuration on the cell. The configuration parameters may comprise second configuration parameters of a second configured grant configuration on the cell. The wireless device may determine, as a selected resource, one of: a first resource associated with the first configured grant configuration; and a second resource associated with the second configured grant configuration. The wireless device may determine the selected resource based on a first type of the first configured grant configuration and a second type of the second configured grant configuration. The first resource and the resource may overlap in one or more OFDM symbols. The wireless device may transmit a transport block via the selected resource.
Embodiments may be configured to operate as needed. The disclosed mechanism may be performed when certain criteria are met, for example, in a wireless device, a base station, a radio environment, a network, a combination of the above, and/or the like. Example criteria may be based, at least in part, on for example, wireless device or network node configurations, traffic load, initial system set up, packet sizes, traffic characteristics, a combination of the above, and/or the like. When the one or more criteria are met, various example embodiments may be applied. Therefore, it may be possible to implement example embodiments that selectively implement disclosed protocols.
A base station may communicate with a mix of wireless devices. Wireless devices and/or base stations may support multiple technologies, and/or multiple releases of the same technology. Wireless devices may have some specific capability(ies) depending on wireless device category and/or capability(ies). A base station may comprise multiple sectors. When this disclosure refers to a base station communicating with a plurality of wireless devices, this disclosure may refer to a subset of the total wireless devices in a coverage area. This disclosure may refer to, for example, a plurality of wireless devices of a given LTE or 5G release with a given capability and in a given sector of the base station. The plurality of wireless devices in this disclosure may refer to a selected plurality of wireless devices, and/or a subset of total wireless devices in a coverage area which perform according to disclosed methods, and/or the like. There may be a plurality of base stations or a plurality of wireless devices in a coverage area that may not comply with the disclosed methods, for example, because those wireless devices or base stations perform based on older releases of LTE or 5G technology.
In this disclosure, “a” and “an” and similar phrases are to be interpreted as “at least one” and “one or more.” Similarly, any term that ends with the suffix “(s)” is to be interpreted as “at least one” and “one or more.” In this disclosure, the term “may” is to be interpreted as “may, for example.” In other words, the term “may” is indicative that the phrase following the term “may” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments.
If A and B are sets and every element of A is also an element of B, A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B={cell1, cell2} are: {cell1}, {cell2}, and {cell1, cell2}. The phrase “based on” (or equally “based at least on”) is indicative that the phrase following the term “based on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “in response to” (or equally “in response at least to”) is indicative that the phrase following the phrase “in response to” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “depending on” (or equally “depending at least to”) is indicative that the phrase following the phrase “depending on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “employing/using” (or equally “employing/using at least”) is indicative that the phrase following the phrase “employing/using” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments.
The term configured may relate to the capacity of a device whether the device is in an operational or non-operational state. Configured may also refer to specific settings in a device that effect the operational characteristics of the device whether the device is in an operational or non-operational state. In other words, the hardware, software, firmware, registers, memory values, and/or the like may be “configured” within a device, whether the device is in an operational or nonoperational state, to provide the device with specific characteristics. Terms such as “a control message to cause in a device” may mean that a control message has parameters that may be used to configure specific characteristics or may be used to implement certain actions in the device, whether the device is in an operational or non-operational state
In this disclosure, various embodiments are disclosed. Limitations, features, and/or elements from the disclosed example embodiments may be combined to create further embodiments within the scope of the disclosure.
In this disclosure, parameters (or equally called, fields, or Information elements: IEs) may comprise one or more information objects, and an information object may comprise one or more other objects. For example, if parameter (IE) N comprises parameter (IE) M, and parameter (IE) M comprises parameter (IE) K, and parameter (IE) K comprises parameter (information element) J. Then, for example, N comprises K, and N comprises J. In an example embodiment, when one or more (or at least one) message(s) comprise a plurality of parameters, it implies that a parameter in the plurality of parameters is in at least one of the one or more messages, but does not have to be in each of the one or more messages. In an example embodiment, when one or more (or at least one) message(s) indicate a value, event and/or condition, it implies that the value, event and/or condition is indicated by at least one of the one or more messages, but does not have to be indicated by each of the one or more messages.
Furthermore, many features presented above are described as being optional through the use of “may” or the use of parentheses. For the sake of brevity and legibility, the present disclosure does not explicitly recite each and every permutation that may be obtained by choosing from the set of optional features. However, the present disclosure is to be interpreted as explicitly disclosing all such permutations. For example, a system described as having three optional features may be embodied in seven different ways, namely with just one of the three possible features, with any two of the three possible features or with all three of the three possible features.
Many of the elements described in the disclosed embodiments may be implemented as modules. A module is defined here as an element that performs a defined function and has a defined interface to other elements. The modules described in this disclosure may be implemented in hardware, software in combination with hardware, firmware, wetware (i.e. hardware with a biological element) or a combination thereof, all of which may be behaviorally equivalent. For example, modules may be implemented as a software routine written in a computer language configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, Matlab or the like) or a modeling/simulation program such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript. Additionally, it may be possible to implement modules using physical hardware that incorporates discrete or programmable analog, digital and/or quantum hardware. Examples of programmable hardware comprise: computers, microcontrollers, microprocessors, application-specific integrated circuits (ASICs); field programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers and microprocessors are programmed using languages such as assembly, C, C++ or the like. FPGAs, ASICs and CPLDs are often programmed using hardware description languages (HDL) such as VHSIC hardware description language (VHDL) or Verilog that configure connections between internal hardware modules with lesser functionality on a programmable device. The above mentioned technologies are often used in combination to achieve the result of a functional module.
The disclosure of this patent document incorporates material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, for the limited purposes required by law, but otherwise reserves all copyright rights whatsoever.
While various embodiments have been described above, it should be understood that they have been presented by way of example, and not limitation. It will be apparent to persons skilled in the relevant art(s) that various changes in form and detail can be made therein without departing from the scope. In fact, after reading the above description, it will be apparent to one skilled in the relevant art(s) how to implement alternative embodiments. Thus, the present embodiments should not be limited by any of the above described exemplary embodiments.
In addition, it should be understood that any figures which highlight the functionality and advantages, are presented for example purposes only. The disclosed architecture is sufficiently flexible and configurable, such that it may be utilized in ways other than that shown. For example, the actions listed in any flowchart may be re-ordered or only optionally used in some embodiments.
Further, the purpose of the Abstract of the Disclosure is to enable the U.S. Patent and Trademark Office and the public generally, and especially the scientists, engineers and practitioners in the art who are not familiar with patent or legal terms or phraseology, to determine quickly from a cursory inspection the nature and essence of the technical disclosure of the application. The Abstract of the Disclosure is not intended to be limiting as to the scope in any way.
Finally, it is the applicant's intent that only claims that include the express language “means for” or “step for” be interpreted under 35 U.S.C. 112. Claims that do not expressly include the phrase “means for” or “step for” are not to be interpreted under 35 U.S.C. 112.
This application is a continuation of U.S. application Ser. No. 16/857,386, filed Apr. 24, 2020, which claims the benefit of U.S. Provisional Application No. 62/842,154, filed May 2, 2019, all of which are hereby incorporated by reference in their entireties.
| Number | Name | Date | Kind |
|---|---|---|---|
| 11343844 | Babaei | May 2022 | B2 |
| 20140177573 | Han et al. | Jun 2014 | A1 |
| 20160142984 | Lee et al. | May 2016 | A1 |
| 20180279348 | Huang et al. | Sep 2018 | A1 |
| 20180368133 | Park et al. | Dec 2018 | A1 |
| Entry |
|---|
| R1-1903959; 3GPP TSG RAN WG1 Meeting #96bis; Xi'an, China, Apr. 8-Apr. 12, 2019; Source: Huawei, HiSilicon; Title: Enhanced UL configured grant transmission; Agenda Item: 7.2.6.6; Document for: Discussion and Decision. |
| R1-1904047; 3GPP TSG RAN WG1 #96bis; Xi'an, China, Apr. 8-12, 2019; Source: OPPO; Title: Configured grant enhancements for URLLC; Agenda Item: 7.2.6.6; Document for: Discussion and Decision. |
| R1-1904048; 3GPP TSG RAN WG1 #96bis; Xi'an, China, Apr. 8-12, 2019; Source: OPPO; Title: Consideration on UL intra UE Tx prioritization and multiplexing; Agenda Item: 7.2.6.7; Document for: Discussion and Decision. |
| R1-1904086; 3GPP TSG RAN WG1 #96bis; Xi'an, China, Apr. 8-12, 2019; Source: vivo; Title: Enhanced UL configured grant transmissions for URLLC; Agenda Item: 7.2.6.6; Document for: Discussion and Decision. |
| R1-1904087; 3GPP TSG RAN WG1 #96bis; Xi'an, China, Apr. 8-12, 2019; Source: vivo; Title: Intra UE multiplexing for UL configured grant transmissions; Agenda Item: 7.2.6.7; Document for: Discussion and Decision. |
| R1-1904127; 3GPP TSG RAN WG1 Meeting #96bis; Xi'an, China, Apr. 8-12, 2019; Source: Ericsson; Title: Enhancement of Configured Grant for NR URLLC; Agenda Item: 7.2.6.6; Document for: Discussion, Decision. |
| R1-1904128; 3GPP TSG-RAN WG1 Meeting #96bis; Xi'an, China, Apr. 8-12, 2019; Source: Ericsson; Title: Intra-UE Prioritization and Multiplexing of UL Data Transmissions; Agenda Item: 7.2.6.7; Document for: Discussion, Decision. |
| R1-1904129; 3GPP TSG-RAN WG1 Meeting #96bis; Xi'an, China, Apr. 8-12, 2019; Source: Ericsson; Title: Intra-UE Prioritization and Multiplexing of DL Transmissions; Agenda Item: 7.2.6.7; Document for: Discussion, Decision. |
| R1-1904130; 3GPP TSG RAN WG1 Meeting #96bis; Xian, China, Apr. 8-Apr. 12, 2019; Source: Ericsson; Title: On intra-UE prioritization enablers; Agenda Item: 7.2.6.7; Document for: Discussion, Decision. |
| R1-1904148; 3GPP TSG RAN WG1 #96bis; Xi'an, China, Apr. 8-12, 2019; Source: ZTE; Title: Enhanced for UL grant free transmission; Agenda item: 7.2.6.6; Document for: Discussion and Decision. |
| R1-1904149; 3GPP TSG RAN WG1 #96bis; Xi'an, China, Apr. 8-12, 2019; Source: ZTE; Title: Discussion on prioritization and/or multiplexing between dynamic grant and configured grant PUSCH; Agenda item: 7.2.6.7; Document for: Discussion and Decision. |
| R1-1904152; 3GPP TSG RAN WG1 #96bis; Xi'an, China, Apr. 8-12, 2019; Source: ZTE; Title: Conflicts among multiple configured grant PUSCH; Agenda item: 7.2.6.7; Document for: Discussion and Decision. |
| R1-1904239; 3GPP TSG RAN WG1 #96bis; Xi'an, China, Apr. 8-12, 2019; Source: Sony; Title: Consideration on enhanced UL grant-free transmissions; Agenda Item: 7.2.6.6; Document for: Discussion/decision. |
| R1-1904310; 3GPP TSG RAN WG1 #96bis; Xi'an, China, Apr. 8-12, 2019; Source: Intel Corporation; Title: Enhanced UL CG PUSCH; Agenda item: 7.2.6.6; Document for: Discussion and Decision. |
| R1-1904445; 3GPP TSG RAN WG1 #96bis; Xi'an, China, Apr. 8-12, 2019; Source: Samsung; Title: Multiple active configured grants for URLLC; Agenda Item: 7.2.6.6; Document for: Discussion and decision. |
| R1-1904508; 3GPP TSG RAN WG1 Meeting #96bis; Xi'an, China, Apr. 8-12, 2019; Source: MediaTek Inc.; Title: Enhancements for NR configured-grant; Agenda Item: 7.2.6.6; Document for: Discussion and Decision. |
| R1-1904632; 3GPP TSG RAN WG1 #96; Athens, Greece, Feb. 25-Mar. 1, 2019; Source: LG Electronics; Title: Enhanced UL configured grant transmission for NR URLLC; Agenda Item: 7.2.6.6; Document for: Discussion and decision. |
| R1-1904633; 3GPP TSG RAN WG1 #96; Athens, Greece, Feb. 25-Mar. 1, 2019; Source: LG Electronics; Title: Discussion on resource conflict between PUSCHs; Agenda Item: 7.2.6.7; Document for: Discussion and decision. |
| R1-1904694; 3GPP TSG RAN WG1 Meeting #96b; Xian, China, Apr. 8-12, 2019; Source: Huawei, HiSilicon; Title: Discussion on resource conflicts between uplink grants; Agenda Item: 7.2.6.7; Document for: Discussion and Decision. |
| R1-1904787; 3GPP TSG RAN WG1 #96bis; Xi'an, China, Apr. 8-12, 2019; Source: Spreadtrum Communications; Title: Discussion on UL grant-free transmission enhancements for URLLC; Agenda item: 7.2.6.6; Document for: Discussion and Decision. |
| R1-1904830; 3GPP TSG RAN WG1 Meeting #96bis; Xi'an, China, Apr. 8-12, 2019; Source: Nokia, Nokia Shanghai Bell; Title: On resource conflicts between UL grants; Agenda item:7.2.6.7; Document for: Discussion and Decision. |
| R1-1904962; 3GPP TSG RAN WG1 #96bis; Xi'an, China, Apr. 8-12, 2019; Source: NTT DOCOMO, INC.; Title: Enhanced UL transmission with configured grant for URLLC; Agenda Item: 7.2.6.6; Document for: Discussion and Decision. |
| R1-1904964; 3GPP TSG RAN WG1 #96bis; Athens, Greece, Feb. 25-Mar. 1, 2019; Source: NTT DOCOMO, INC.; Title: UL intra-UE transmission prioritization/multiplexing and physical layer enhancements for DL SPS; Agenda Item: 7.2.6.7; Document for: Discussion and Decision. |
| R1-1905024; 3GPP TSG-RAN WG1 Meeting #96b; Xi'an, China, Apr. 8-12, 2019; Source: Qualcomm Incorporated; Title: Enhanced Grant-Free Transmissions for eURLLC; Agenda item: 7.2.6.6; Document for: Discussion/Decision. |
| R1-1905096; 3GPP TSG RAN WG1 #96bis; Xi'an, China, Apr. 8-12, 2019; Source: Panasonic; Title: Discussion on URLLC enhancements for grant-free transmission; Agenda Item: 7.2.6.6; Document for: Discussion. |
| R1-1905364; 3GPP TSG RAN WG1 Meeting #96bis; Xi'an, China, Apr. 8-12, 2019; Source: CATT; Title: Discussion on enhanced UL configured grant transmission; Agenda Item: 7.2.6.6; Document for: Discussion and Decision. |
| R1-1905365; 3GPP TSG RAN WG1 Meeting #96bis; Xi'an, China, Apr. 8-12, 2019; Source: CATT; Title: Discussion on PUSCH resource collision; Agenda Item: 7.2.6.7; Document for: Discussion and Decision. |
| R1-1905399; 3GPP TSG RAN WG1 Meeting #96bis; Xi'an, China, Apr. 8-12, 2019; Source: Sharp; Title: Discussion on Intra-UE prioritization and multiplexing; Agenda Item: 7.2.6.7; Other; Document for: Discussion and Decision. |
| R1-1905449; 3GPP TSG-RAN WG1 Meeting #96bis; Xi'an, China, Apr. 8-12, 2019; Source: Convida Wireless; Title: On Intra-UE prioritization; Agenda item: 7.2.6.7; Document for: Discussion. |
| R1-1905452; 3GPP TSG RAN WG1 Meeting #96bis; Xi'an, China, Apr. 8-12, 2019; Source: Huawei, HiSilicon; Title: DL intra-UE transmission prioritization and multiplexing; Agenda Item: 7.2.6.7; Document for: Discussion and Decision. |
| R1-1905456; 3GPP TSG RAN WG1 Meeting #96b; Xi'an, China, Apr. 8-12, 2019; Source: Huawei, HiSilicon; Title: UL intra-UE multiplexing between control channels; Agenda Item: 7.2.6.7; Document for: Discussion and Decision. |
| R1-1905457; 3GPP TSG RAN WG1 Meeting #96b; Xi'an, China, Apr. 8-12, 2019; Source: Huawei, HiSilicon; Title: UL intra-UE multiplexing between control channel and data channel; Agenda Item: 7.2.6.7; Document for: Discussion and Decision. |
| R1-1905460; 3GPP TSG RAN WG1 #96bis; Xi'an, People's Republic of China, Apr. 8-Apr. 12, 2019; Source: KDDI; Title: Discussion on enhanced UL configured grant transmission; Agenda Item: 7.2.6.6; Document for: Discussion and Decision. |
| R1-1905489; 3GPP TSG RAN WG1 Meeting #96bis; Xi'an, China, Apr. 8-12, 2019; Source: Fujitsu; Title: Considerations on handling resource conflicts between dynamic grant and configured grant PUSCHs; Agenda Item: 7.2.6.7; Document for: Discussion/Decision. |
| R1-1905609; 3GPP TSG RAN WG1 Meeting #96bis; Xi'an, China, Apr. 8-12, 2019; Source: NTT DOCOMO, INC.; Title: Summary of 7.2.6.6 Enhanced UL configured grant transmission; Agenda Item: 7.2.6.6; Document for: Discussion and Decision. |
| R1-1905625; 3GPP TSG RAN WG1 #96bis; Xi'an, China, Apr. 8-12, 2019; Source: LG Electronics; Title: Summary of 7.2.6.7 Others; Agenda Item: 7.2.6.7; Document for: Discussion and decision. |
| R1-1905813; 3GPP TSG RAN WG1 #96bis; Xi'an, China, Apr. 8-12, 2019; Source: LG Electronics; Title: Summary#2 of 7.2.6.7 Others; Agenda Item:7.2.6.7; Document for: Discussion and decision. |
| R1-1905893; 3GPP TSG RAN WG1 Meeting #96bis; Xi'an, China, Apr. 8-12, 2019; Source: NTT DOCOMO, INC.; Title: Offline discussion on 7.2.6.6 Enhanced UL configured grant transmission; Agenda Item: 7.2.6.6; Document for: Discussion and Decision. |
| Number | Date | Country | |
|---|---|---|---|
| 20220264634 A1 | Aug 2022 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62842154 | May 2019 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16857386 | Apr 2020 | US |
| Child | 17734603 | US |
