[go: up one dir, main page]

WO2025231797A1 - Systèmes, dispositifs et procédés pour répétitions de pdsch msg4 - Google Patents

Systèmes, dispositifs et procédés pour répétitions de pdsch msg4

Info

Publication number
WO2025231797A1
WO2025231797A1 PCT/CN2024/092206 CN2024092206W WO2025231797A1 WO 2025231797 A1 WO2025231797 A1 WO 2025231797A1 CN 2024092206 W CN2024092206 W CN 2024092206W WO 2025231797 A1 WO2025231797 A1 WO 2025231797A1
Authority
WO
WIPO (PCT)
Prior art keywords
msg4
pdsch
repetition
repetitions
msg4 pdsch
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2024/092206
Other languages
English (en)
Inventor
Chunxuan Ye
Chunhai Yao
Huaning Niu
Hong He
Haitong Sun
Dawei Zhang
Wei Zeng
Ankit Bhamri
Fangli Xu
Yuqin Chen
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Apple Inc
Original Assignee
Apple Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Apple Inc filed Critical Apple Inc
Priority to PCT/CN2024/092206 priority Critical patent/WO2025231797A1/fr
Publication of WO2025231797A1 publication Critical patent/WO2025231797A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0009—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the channel coding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1858—Transmission or retransmission of more than one copy of acknowledgement message
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1896—ARQ related signaling

Definitions

  • This disclosure relates to wireless communication networks and mobile device capabilities.
  • Wireless communication networks and wireless communication services are becoming increasingly dynamic, complex, and ubiquitous.
  • some wireless communication networks can be developed to implement fourth generation (4G) , fifth generation (5G) or new radio (NR) technology.
  • 4G fourth generation
  • 5G fifth generation
  • NR new radio
  • Such technology can include solutions for enabling user equipment (UE) and network devices, such as base stations, to communicate with one another.
  • UE user equipment
  • network devices such as base stations
  • Some scenarios can extend to communications between a UE and other types of network access points as well, such as satellites and non-terrestrial network (NTN) nodes.
  • NTN non-terrestrial network
  • Fig. 1 is a diagram of an example process for physical uplink (UL) control channel (PUCCH) repetitions for message 4 (Msg4) PUCCH hybrid automatic repeat request (HARQ) acknowledgement (ACK) messages according to one or more implementations described herein.
  • UL physical uplink
  • PUCCH physical uplink control channel
  • Msg4 message 4
  • HARQ PUCCH hybrid automatic repeat request acknowledgement
  • Fig. 2 is a diagram of an example network according to one or more implementations described herein.
  • Fig. 3 is a diagram of an example process for message 4 (Msg4) physical downlink (DL) shared channel (PDSCH) repetitions according to one or more implementations described herein.
  • Msg4 message 4
  • DL physical downlink
  • PDSCH shared channel
  • Fig. 4 is a diagram of an example of system information block (SIB) contents according to one or more implementations described herein.
  • SIB system information block
  • Fig. 5 is a diagram of an example for determining whether to indicate a capability for Msg4 PDSCH repetition and/or request for Msg4 PDSCH repetition according to one or more implementations described herein.
  • Fig. 6 is a diagram of an example techniques for using DCI to schedule an Msg4 PDSCH and indicate a number of Msg4 PDSCH repetitions according to one or more implementations described herein.
  • Fig. 7 is a diagram of an example process for Msg4 PDSCH repetitions according to one or more implementations described herein.
  • Fig. 8 is a diagram of an example process for Msg4 PDSCH repetitions according to one or more implementations described herein.
  • Fig. 9 is a diagram of an example of components of a device according to one or more implementations described herein.
  • Fig. 10 is a block diagram illustrating components, according to one or more implementations described herein, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
  • a machine-readable or computer-readable medium e.g., a non-transitory machine-readable storage medium
  • Telecommunication networks can include user equipment (UEs) capable of communicating with base stations and/or other network access nodes.
  • UEs and base stations can implement various techniques and communications standards for enabling UEs and base stations to discover one another, establish and maintain connectivity, and exchange information in an ongoing manner. Objectives of such techniques can include enhancing the range and reliability of wireless signals. This can involve determining appropriate transmission times and frequencies, transmission power, transmission repetitions, and the like.
  • a UE can connect to a base station or other network access node by performing an attachment procedure, such as a random access channel (RACH) procedure.
  • RACH procedure can be a 2-step RACH procedure or a 4 step RACH procedure.
  • the number of steps can refer to the number of signals or messages, between the UE and the network, involved in completing the attachment procedure.
  • PBCH physical broadcast channel
  • SIBs system information blocks
  • a first message can involve the UE using a physical RACH (PRACH) to transmit a random access preamble and sequence number to the base station.
  • Msg1 can be referred to as a random access (RA) request message, a PRACH, or a PRACH message, and can be used to derive a RA radio network temporary identifier (RA-RNTI) at the base station.
  • the base station can send a second message (Msg2) to the UE, which can include a time advance (TA) for timing adjustment, an uplink (UL) grant for the UE, and more.
  • Msg2 can be referred to as a RA response (RAR) message and can include a temporary cell RNTI (TC-RNTI) assigned to the UE.
  • RAR RA response
  • the UE can use the UL grant to send a third message (Msg3) to the base station via a physical UL shared channel (PUSCH) .
  • Msg3 can include a radio resource control (RRC) message referred to as an RRC request message and one or more additional types of information.
  • RRC request message can indicate a request by the UE to connect to the network.
  • Msg3 can also include an indication that the UE is capable of repeated physical UL control channel (PUCCH) signals for hybrid automatic repeat request (HARQ) acknowledgement (HARQ-ACK) of subsequent downlink (DL) message from the base station.
  • PUCCH physical UL control channel
  • HARQ-ACK hybrid automatic repeat request acknowledgement
  • the base station can respond to the UE by sending a fourth message (Msg4) .
  • Msg4 can include media access control (MAC) information, such as an identity assigned to the UE, confirmation that the base station has correctly identified the UE, and an indication that any contention over wireless resources has been resolved. Contention can result from UEs using the same preamble, receiving the same PUSCH grant, and using the same TC-RNTI while attempting to connect to a base station.
  • Msg4 can also include a cell RNTI (C-RNTI) that the UE can use for communicating with the base station going forward.
  • C-RNTI cell RNTI
  • While currently available technologies can include operations and signaling to enable a UE to connect to a network, such techniques include one or more deficiencies. For example, currently available technologies fail to provide any, or adequate, solutions for enhancing link-level communications for Msg4 signaling. For example, currently available technologies fail to provide any, or adequate, solutions for repeating Msg4 PDSCH transmissions in the event of a Msg4 PDSCH transmission failure.
  • One or more of the techniques described herein can provide solutions for enabling Msg4 PDSCH repetitions.
  • Examples of these solutions can include signaling for Msg4 PDSCH repetitions using one or more SIBs that indicate a number of Msg4 PDSCH repetition and reference signal received power (RSRP) thresholds for indicating a UE capability, or request, for Msg4 PDSCH repetitions.
  • Additional examples of these solutions can include downlink control information (DCI) for scheduling Msg4 PDSCH repetitions based on a reinterpretation of an existing DCI field, a new RNTI, an implicit indication based on Msg4 PUCCH repetitions, or a number of Msg4 PDSCH repetitions requested by the UE.
  • DCI downlink control information
  • Msg4 PDSCH repetitions can include usage of Msg4 PDSCH repetitions, including a number of Msg4 PDSCH repetitions being applied until a dedicated PDSCH configuration is provided to UE.
  • FR1 frequency range 1
  • FR2 frequency range 2
  • NTNs non-terrestrial networks
  • Fig. 1 is a diagram of an example process 100 for PUCCH repetitions for Msg4 PUCCH HARQ-ACK messages according to one or more implementations described herein.
  • process 100 can include UE 110 and base station 120.
  • base station 120 can be implemented by another type of network access node such as a satellite of an NTN.
  • Example 100 is provided as context for one or more of the Msg4 PDSCH repetition techniques described herein, which can involve PUCCH repetitions for Msg4 PUCCH HARQ-ACK and more.
  • one or more operations, messages, or signaling of process 100 can be implemented in combination with one or more of the operations, message, or signaling of the Msg4 PDSCH repetition techniques described herein.
  • process 100 can include base station 120 providing UE 110 with an SIB that includes configuration information for PUCCH repetitions for Msg4 PUCCH HARQ-ACK (at 115) .
  • UE 110 can determine whether to indicate a capability, or request, for PUCCH repetitions for Msg4 PUCCH HARQ-ACK (at 120) and can communicate a Msg1 PRACH to base station 120 (at 125) .
  • Base station 120 can respond by sending UE 110 a Msg2 RAR (at 130) , and in turn, UE 110 can communicate a Msg3 PUSCH to base station 120 (at 135) .
  • the Msg3 PUSCH can indicate a capability, or a request, for PUCCH repetitions for Msg4 HARQ-ACK.
  • Base station 120 can determine a repetition factor or number for PUCCH repetitions for Msg4 PUCCH HARQ-ACK (at 140) and can provide UE 110 with DCI that schedules a Msg4 PDSCH (at 145) .
  • the DCI can also indicate the repetition factor or number for Msg4 HARQ-ACK.
  • process 100 can include base station 120 communicating a Msg 4 to UE 110, and UE 110 and base station 120 can apply the repetition factor or number to Msg4 PUCCH HARQ-ACK messages accordingly (at 150) .
  • Fig. 2 is an example network 200 according to one or more implementations described herein.
  • Example network 200 can include UEs 210-1, 210-2, etc. (referred to collectively as “UEs 210” and individually as “UE 210” ) , a radio access network (RAN) 220, a core network (CN) 230, application servers 240, external networks 250, and satellites 260-1, 260-2, etc. (referred to collectively as “satellites 260” and individually as “satellite 260” ) .
  • network 200 can include a non-terrestrial network (NTN) comprising one or more satellites 260 (e.g., of a global navigation satellite system (GNSS) ) in communication with UEs 210 and RAN 220.
  • NTN non-terrestrial network
  • GNSS global navigation satellite system
  • the systems and devices of example network 200 can operate in accordance with one or more communication standards, such as 2nd generation (2G) , 3rd generation (3G) , 4th generation (4G) (e.g., long-term evolution (LTE) ) , and/or 5th generation (5G) (e.g., new radio (NR) ) communication standards of the 3rd generation partnership project (3GPP) .
  • 3GPP 3rd generation partnership project
  • 5G e.g., new radio (NR)
  • 3GPP 3rd generation partnership project
  • UEs 210 can include smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more wireless communication networks) . Additionally, or alternatively, UEs 210 can include other types of mobile or non-mobile computing devices capable of wireless communications, such as personal data assistants (PDAs) , pagers, laptop computers, desktop computers, wireless handsets, etc. In some implementations, UEs 210 can include internet of things (IoT) devices (or IoT UEs) that can comprise a network access layer designed for low-power IoT applications utilizing short-lived UE connections.
  • IoT internet of things
  • an IoT UE can utilize one or more types of technologies, such as machine-to-machine (M2M) communications or machine-type communications (MTC) (e.g., to exchanging data with an MTC server or other device via a public land mobile network (PLMN) ) , proximity-based service (ProSe) or device-to-device (D2D) communications, sensor networks, IoT networks, and more.
  • M2M or MTC exchange of data can be a machine-initiated exchange
  • an IoT network can include interconnecting IoT UEs (which can include uniquely identifiable embedded computing devices within an Internet infrastructure) with short-lived connections.
  • IoT UEs can execute background applications (e.g., keep-alive messages, status updates, etc. ) to facilitate the connections of the IoT network.
  • UEs 210 can communicate and establish a connection with one or more other UEs 210 via one or more wireless channels 212, each of which can comprise a physical communications interface /layer.
  • the connection can include an M2M connection, MTC connection, D2D connection, SL connection, etc.
  • the connection can involve a PC5 interface.
  • UEs 210 can be configured to discover one another, negotiate wireless resources between one another, and establish connections between one another, without intervention or communications involving RAN node 222 or another type of network node.
  • discovery, authentication, resource negotiation, registration, etc. can involve communications with RAN node 222 or another type of network node.
  • UEs 210 can use one or more wireless channels 212 to communicate with one another.
  • UE 210 can communicate with RAN node 222 to request SL resources.
  • RAN node 222 can respond to the request by providing UE 210 with a dynamic grant (DG) or configured grant (CG) regarding SL resources.
  • DG can include a grant based on a grant request from UE 210.
  • a CG can involve a resource grant without a grant request and can be based on a type of service being provided (e.g., services that have strict timing or latency requirements) .
  • UE 210 can perform a clear channel assessment (CCA) procedure based on the DG or CG, select SL resources based on the CCA procedure and the DG or CG; and communicate with another UE 210 based on the SL resources.
  • the UE 210 can communicate with RAN node 222 using a licensed frequency band and communicate with the other UE 210 using an unlicensed frequency band.
  • CCA clear channel assessment
  • UEs 210 can communicate and establish a connection with RAN 220, which can involve one or more wireless channels 214-1 and 214-2, each of which can comprise a physical communications interface /layer.
  • a UE can be configured with dual connectivity (DC) as a multi-radio access technology (multi-RAT) or multi-radio dual connectivity (MR-DC) , where a multiple receive and transmit (Rx/Tx) capable UE can use resources provided by different network nodes (e.g., 222-1 and 222-2) that can be connected via non-ideal backhaul (e.g., where one network node provides NR access and the other network node provides either E-UTRA for LTE or NR access for 5G) .
  • DC dual connectivity
  • multi-RAT multi-radio access technology
  • MR-DC multi-radio dual connectivity
  • a network node can be referred to herein as a base station 222.
  • one network node can operate as a master node (MN) and the other as the secondary node (SN) .
  • the MN and SN can be connected via a network interface, and at least the MN can be connected to the CN 230.
  • at least one of the MN or the SN can be operated with shared spectrum channel access, and functions specified for UE 210 can be used for an integrated access and backhaul mobile termination (IAB-MT) .
  • IAB-MT integrated access and backhaul mobile termination
  • the IAB-MT can access the network using either one network node or using two different nodes with enhanced dual connectivity (EN-DC) architectures, new radio dual connectivity (NR-DC) architectures, or the like.
  • a base station (as described herein) can be an example of network node 222.
  • UE 210 can also, or alternatively, connect to access point (AP) 216 via connection interface 218, which can include an air interface enabling UE 210 to communicatively couple with AP 216.
  • AP 216 can comprise a wireless local area network (WLAN) , WLAN node, WLAN termination point, etc.
  • the connection 216 can comprise a local wireless connection, such as a connection consistent with any IEEE 702.11 protocol, and AP 216 can comprise a wireless fidelity router or other AP. While not explicitly depicted in Fig. 2, AP 216 can be connected to another network (e.g., the Internet) without connecting to RAN 220 or CN 230.
  • another network e.g., the Internet
  • UE 210, RAN 220, and AP 216 can be configured to utilize LTE-WLAN aggregation (LWA) techniques or LTE WLAN radio level integration with IPsec tunnel (LWIP) techniques.
  • LWA can involve UE 210 in RRC_CONNECTED being configured by RAN 220 to utilize radio resources of LTE and WLAN.
  • LWIP can involve UE 210 using WLAN radio resources (e.g., connection interface 218) via IPsec protocol tunneling to authenticate and encrypt packets (e.g., Internet Protocol (IP) packets) communicated via connection interface 218.
  • IPsec tunneling can include encapsulating the entirety of original IP packets and adding a new packet header, thereby protecting the original header of the IP packets.
  • RAN 220 can include one or more RAN nodes 222-1 and 222-2 (referred to collectively as RAN nodes 222, and individually as RAN node 222) that enable channels 214-1 and 214-2 to be established between UEs 210 and RAN 220.
  • RAN nodes 222 can include network access points configured to provide radio baseband functions for data and/or voice connectivity between users and the network based on one or more of the communication technologies described herein (e.g., 2G, 3G, 4G, 5G, WiFi, etc. ) .
  • a RAN node can be an E-UTRAN Node B (e.g., an enhanced Node B, eNodeB, eNB, 4G base station, etc.
  • RAN nodes 222 can include a roadside unit (RSU) , a transmission reception point (TRxP or TRP) , and one or more other types of ground stations (e.g., terrestrial access points) .
  • RSU roadside unit
  • TRxP transmission reception point
  • RAN node 222 can be a dedicated physical device, such as a macrocell base station, and/or a low power (LP) base station for providing femtocells, picocells or the like having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.
  • LP low power
  • a RAN node can generally be referred to herein as base station 222. Satellites 260 can operate as RAN nodes 222, with respect to UEs 210. As such, references herein to a base station, RAN node 222, etc., can involve implementations where the base station, RAN node 222, etc., is a terrestrial network (TN) node and also to implementation where the base station, RAN node 222, etc., is an NTN node (e.g., satellite 260) .
  • TN terrestrial network
  • RAN nodes 222 can be implemented as one or more software entities running on server computers as part of a virtual network, which can be referred to as a centralized RAN (CRAN) and/or a virtual baseband unit pool (vBBUP) .
  • CRAN centralized RAN
  • vBBUP virtual baseband unit pool
  • the CRAN or vBBUP can implement a RAN function split, such as a packet data convergence protocol (PDCP) split wherein radio resource control (RRC) and PDCP layers can be operated by the CRAN/vBBUP and other Layer 2 (L2) protocol entities can be operated by individual RAN nodes 222; a media access control (MAC) /physical (PHY) layer split wherein RRC, PDCP, radio link control (RLC) , and MAC layers can be operated by the CRAN/vBBUP and the PHY layer can be operated by individual RAN nodes 222; or a “lower PHY” split wherein RRC, PDCP, RLC, MAC layers and upper portions of the PHY layer can be operated by the CRAN/vBBUP and lower portions of the PHY layer can be operated by individual RAN nodes 222.
  • This virtualized framework can allow freed-up processor cores of RAN nodes 222 to perform or execute other virtualized applications.
  • an individual RAN node 222 can represent individual gNB-distributed units (DUs) connected to a gNB-control unit (CU) via individual F1 or other interfaces.
  • the gNB-DUs can include one or more remote radio heads or radio frequency (RF) front end modules (RFEMs)
  • RFEMs radio frequency front end modules
  • the gNB-CU can be operated by a server (not shown) located in RAN 220 or by a server pool (e.g., a group of servers configured to share resources) in a similar manner as the CRAN/vBBUP.
  • one or more of RAN nodes 222 can be next generation eNBs (i.e., gNBs) that can provide evolved universal terrestrial radio access (E-UTRA) user plane and control plane protocol terminations toward UEs 210, and that can be connected to a 5G core network (5GC) 230 via an NG interface.
  • gNBs next generation eNBs
  • E-UTRA evolved universal terrestrial radio access
  • 5GC 5G core network
  • any of the RAN nodes 222 can terminate an air interface protocol and can be the first point of contact for UEs 210.
  • any of the RAN nodes 222 can fulfill various logical functions for the RAN 220 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.
  • RNC radio network controller
  • UEs 210 can be configured to communicate using orthogonal frequency-division multiplexing (OFDM) communication signals with each other or with any of the RAN nodes 222 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an OFDMA communication technique (e.g., for downlink communications) or a single carrier frequency-division multiple access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink (SL) communications) , although the scope of such implementations cannot be limited in this regard.
  • OFDM signals can comprise a plurality of orthogonal subcarriers.
  • a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 222 to UEs 210, and uplink transmissions can utilize similar techniques.
  • the grid can be a time-frequency grid (e.g., a resource grid or time-frequency resource grid) that represents the physical resource for downlink in each slot.
  • a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation.
  • Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively.
  • the duration of the resource grid in the time domain corresponds to one slot in a radio frame.
  • the smallest time-frequency unit in a resource grid is denoted as a resource element.
  • Each resource grid comprises resource blocks, which describe the mapping of certain physical channels to resource elements (REs) .
  • Each resource block can comprise a collection of resource elements; in the frequency domain, this can represent the smallest quantity of resources that currently can be allocated.
  • RAN nodes 222 can be configured to wirelessly communicate with UEs 210, and/or one another, over a licensed medium (also referred to as the “licensed spectrum” and/or the “licensed band” ) , an unlicensed shared medium (also referred to as the “unlicensed spectrum” and/or the “unlicensed band” ) , or combination thereof.
  • a licensed spectrum can correspond to channels or frequency bands selected, reserved, regulated, etc., for certain types of wireless activity (e.g., wireless telecommunication network activity)
  • an unlicensed spectrum can correspond to one or more frequency bands that are not restricted for certain types of wireless activity.
  • Whether a particular frequency band corresponds to a licensed medium or an unlicensed medium can depend on one or more factors, such as frequency allocations determined by a public-sector organization (e.g., a government agency, regulatory body, etc. ) or frequency allocations determined by a private-sector organization involved in developing wireless communication standards and protocols, etc.
  • a public-sector organization e.g., a government agency, regulatory body, etc.
  • UEs 210 and the RAN nodes 222 can operate using stand-alone unlicensed operation, licensed assisted access (LAA) , enhanced LAA (eLAA) , and/or further eLAA (feLAA) mechanisms.
  • LAA licensed assisted access
  • eLAA enhanced LAA
  • feLAA further eLAA
  • UEs 210 and the RAN nodes 222 can perform one or more known medium-sensing operations or carrier-sensing operations in order to determine whether one or more channels in the unlicensed spectrum is unavailable or otherwise occupied prior to transmitting in the unlicensed spectrum.
  • the medium/carrier sensing operations can be performed according to a listen-before-talk (LBT) protocol.
  • LBT listen-before-talk
  • the PDSCH can carry user data and higher layer signaling to UEs 210.
  • the physical downlink control channel (PDCCH) can carry information about the transport format and resource allocations related to the PDSCH channel, among other things.
  • the PDCCH can also inform UEs 210 about the transport format, resource allocation, and hybrid automatic repeat request (HARQ) information related to the uplink shared channel.
  • HARQ hybrid automatic repeat request
  • downlink scheduling e.g., assigning control and shared channel resource blocks to UE 210 within a cell
  • the downlink resource assignment information can be sent on the PDCCH used for (e.g., assigned to) each of UEs 210.
  • UE 210 (or a component thereof, such as a baseband processor) can determine whether to indicate or request Msg4 PDSCH repetition based on the capability of UE 210 and RSRP thresholds.
  • Base station 222 can use DCI for scheduling Msg4 PDSCH repetitions based on one or more of: a reinterpretation of an existing DCI field; a new RNTI; an implicit indication based on Msg4 PUCCH repetitions; and a number of Msg4 PDSCH repetitions requested by UE 210.
  • the number of Msg4 PDSCH repetitions can be applied until a dedicated PDSCH configuration is provided to the UE.
  • the RAN nodes 222 can be configured to communicate with one another via interface 223.
  • interface 223 can be an X2 interface.
  • interface 223 can be an Xn interface.
  • the X2 interface can be defined between two or more RAN nodes 222 (e.g., two or more eNBs /gNBs or a combination thereof) that connect to evolved packet core (EPC) or CN 230, or between two eNBs connecting to an EPC.
  • the X2 interface can include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C) .
  • the X2-U can provide flow control mechanisms for user data packets transferred over the X2 interface and can be used to communicate information about the delivery of user data between eNBs or gNBs.
  • the X2-U can provide specific sequence number information for user data transferred from a master eNB (MeNB) to a secondary eNB (SeNB) ; information about successful in sequence delivery of PDCP packet data units (PDUs) to a UE 210 from an SeNB for user data; information of PDCP PDUs that were not delivered to a UE 210; information about a current minimum desired buffer size at the SeNB for transmitting to the UE user data; and the like.
  • the X2-C can provide intra-LTE access mobility functionality (e.g., including context transfers from source to target eNBs, user plane transport control, etc. ) , load management functionality, and inter-cell interference coordination functionality.
  • RAN 220 can be connected (e.g., communicatively coupled) to CN 230.
  • CN 230 can comprise a plurality of network elements 232, which are configured to offer various data and telecommunications services to customers/subscribers (e.g., users of UEs 210) who are connected to the CN 230 via the RAN 220.
  • CN 230 can include an evolved packet core (EPC) , a 5G CN (5GC) , and/or one or more additional or alternative types of CNs.
  • EPC evolved packet core
  • 5GC 5G CN
  • the components of the CN 230 can be implemented in one physical node or separate physical nodes including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) .
  • network function virtualization NFV
  • NFV network function virtualization
  • a logical instantiation of the CN 230 can be referred to as a network slice, and a logical instantiation of a portion of the CN 230 can be referred to as a network sub-slice.
  • NFV Network function virtualization
  • infrastructures can be used to virtualize one or more network functions, alternatively performed by proprietary hardware, onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches.
  • NFV systems can be used to execute virtual or reconfigurable implementations of one or more EPC components/functions.
  • CN 230, application servers 240, and external networks 250 can be connected to one another via interfaces 234, 236, and 238, which can include IP network interfaces.
  • Application servers 240 can include one or more server devices or network elements (e.g., virtual network functions (VNFs) offering applications that use IP bearer resources with CM 230 (e.g., universal mobile telecommunications system packet services (UMTS PS) domain, LTE PS data services, etc. ) .
  • Application servers 240 can also, or alternatively, be configured to support one or more communication services (e.g., voice over IP (VoIP sessions, push-to-talk (PTT) sessions, group communication sessions, social networking services, etc. ) for UEs 210 via the CN 230.
  • external networks 250 can include one or more of a variety of networks, including the Internet, thereby providing the mobile communication network and UEs 210 of the network access to a variety of additional services, information, interconnectivity, and other network features.
  • Satellites 260 can communicate with UEs 210 via service link or wireless interface 262 and/or RAN 220 via feeder links or wireless interfaces 264 (depicted individually as 264-1 and 264-2) .
  • satellite 260 can operate as a passive or transparent network relay node regarding communications between UE 210 and the terrestrial network (e.g., RAN 220) .
  • satellite 260 can operate as an active or regenerative network node such that satellite 260 can operate as a base station to UEs 210 (e.g., as a base station of RAN 220) .
  • satellites 260 can communicate with one another via a direct wireless interface (e.g., 266) or an indirect wireless interface (e.g., via RAN 220 using interfaces 264-1 and 264-2) .
  • satellite 260 can include a GEO satellite, LEO satellite, or another type of satellite. Satellite 260 can also, or alternatively pertain to one or more satellite systems or architectures, such as a global navigation satellite system (GNSS) , global positioning system (GPS) , global navigation satellite system (GLONASS) , BeiDou navigation satellite system (BDS) , etc. In some implementations, satellites 260 can operate as bases stations (e.g., RAN nodes 222) with respect to UEs 210.
  • GNSS global navigation satellite system
  • GPS global positioning system
  • GLONASS global navigation satellite system
  • BDS BeiDou navigation satellite system
  • satellites 260 can operate as bases stations (e.g., RAN nodes 222) with respect to UEs 210.
  • references herein to a base station, RAN node 222, etc. can involve implementations where the base station, RAN node 222, etc., is a terrestrial network node and implementation, where the base station, RAN node 222, etc., is a non-terrestrial network node (e.g., satellite 260) .
  • UE 210 and base station 222 can communicate with one another, via interface 214, to enable enhanced power saving techniques.
  • Fig. 3 is a diagram of an example process 300 for PDSCH repetitions according to one or more implementations described herein.
  • Process 300 can be implemented by UE 210 and one or more base stations 222. In some implementations, some or all of process 300 can be performed by one or more other systems or devices, including one or more of the devices of Fig. 2. Additionally, process 300 can include one or more fewer, additional, differently ordered and/or arranged operations than those shown in Fig. 3. In some implementations, some or all of the operations of process 300 can be performed independently, successively, simultaneously, etc., of one or more of the other operations of process 300. As such, the techniques described herein are not limited to a number, sequence, arrangement, timing, etc., of the operations or processes depicted in Fig. 3. Fig. 3 is described below with periodic reference to Figs. 4-6.
  • process 300 can include base station 222 sending UE 210 configuration information for Msg4 PDSCH repetition (305) .
  • the configuration information can be sent via a first SIB (e.g., SIB1) .
  • SIB1 can carry scheduling information about one or more other SIBs that can include the configuration information.
  • the configuration information can be included in an SIB (e.g., SIB19) designated for communicating with satellite 260.
  • Configuration information for Msg4 PDSCH repetition may include one or more Msg4 PDSCH repetition factors and one or more RSRP thresholds for Msg4 PDSCH repetitions.
  • An Msg4 PDSCH repetition factor may include a number of Msg4 PDSCH transmissions or repetitions.
  • the configuration information for Msg4 PDSCH repetition may include one or more Msg4 PDSCH repetition factors supported by base station 222. This may enable UE 210 to determine whether UE 210 is capable of implementing the Msg4 PDSCH repetitions supported by base station 222.
  • the actual number of Msg4 PDSCH repetitions applied to Msg4 PDSCH transmission for UE 210 may be indicated later by base station 222 via DCI.
  • Fig. 4 is a diagram of an example of SIB contents 400 according to one or more implementations described herein.
  • SIB contents 400 can be carried by SIB1, SIB19, and/or one or more other SIBs. Additionally, SIB contents 400 can include one or more Msg4 PDSCH repetition factors, one or more types of RSRP thresholds, and one or more RSRP threshold schemes. SIB contents 400 is an example of configuration information for Msg4 PDSCH repetition. In some implementations, SIB contents 400 can include fewer, additional, or different types of information than the configuration information shown in Fig. 4.
  • an Msg4 PDSCH repetition factor can include 1, 2, 4, or 8.
  • An Msg4 PDSCH repetition factor can include a number of Msg4 PDSCH repetitions.
  • an Msg4 PDSCH repetition factor of 4 can indicate that an Msg4 PDSCH transmission can be repeated 4 times.
  • an Msg4 PDSCH repetition factor can be jointly configured with a number of repetitions of another message or transmission.
  • a Msg4 PDSCH repetition factor can be equal to a number of UL or DL transmissions associated with another RACH message or a corresponding HARQ (e.g., a Msg4 PUCCH) .
  • an Msg4 PDSCH repetition factor can be a value (e.g., a scaling factor) that UE 210 can apply to another parameter (e.g., a number of repetitions for another RACH message) to determine a number of Msg4 PDSCH repetitions.
  • SIB contents 400 can also include one or more RSRP thresholds for Msg4 PDSCH repetition.
  • RSRP threshold types can include an absolute RSRP threshold, a relative RSRP threshold, and a default RSRP threshold.
  • An absolute RSRP threshold can include a specific value in an SIB field.
  • the RSRP threshold can be a 7-bit RSRP value.
  • a relative RSRP threshold can be equal to a reference RSRP threshold associated with another RACH message or signal (e.g., a PRACH repetition, Msg3 PUSCH repetition, Msg4 PUCCH repetition, etc. ) .
  • a relative RSRP threshold can include a factor (e.g., a scaling factor) that UE 210 can apply to a reference RSRP threshold associated with another RACH message or signal.
  • the RSRP threshold can be a 4-bit RSRP value of an SIB field.
  • UE 210 can measure a signal strength of a reference signal (e.g., RSRP) and compare the signal strength to one or more RSRP thresholds.
  • a reference signal e.g., RSRP
  • Non-limiting examples of the types of signals that UE 210 can be configured to measure can include a secondary synchronization signal (SSS) , demodulation reference signal (DMRS) of a PBCH, DMRS of a Msg2 PDCCH transmission, DMRS of a Msg2 PDSCH, etc.
  • SSS secondary synchronization signal
  • DMRS demodulation reference signal
  • UE 210 can determine whether to indicate or request Msg4 PDSCH repetition from base station 222.
  • SIB contents 400 do not include an RSRP threshold for Msg4 PDSCH repetition.
  • SIB contents 400 can include one or more RSRP thresholds.
  • the RSRP thresholds can be absolute RSRP thresholds and/or relative RSRP thresholds. Each RSRP threshold can be a different value or threshold level. Additionally, each RSRP threshold can be associated with a different number of Msg4 PDSCH repetitions. For example, a lower RSRP threshold value can be associated with fewer Msg4 PDSCH repetitions than the number of Msg4 PDSCH repetitions associated with a higher RSRP threshold. In some implementations, different RSRP thresholds can be applicable to different types of measured signals and/or different conditions or scenarios.
  • An RSRP threshold scheme can also include instructions for determining an RSRP threshold (e.g., a relative RSRP threshold) , when to apply one RSRP threshold (e.g., an absolute RSRP threshold) instead of another RSRP threshold (e.g., a relative RSRSP threshold) , and how to respond to a scenario in which a measured signal strength is greater than one RSRP threshold be less than another RSRP threshold.
  • An RSRP threshold scheme can also include instructions or an indication of a type of signal to measure, when to measure the signal, times or conditions for measuring one type of signal rather than another type of signal, etc.
  • process 300 can include UE 210 communicating a PRACH message to base station 222 (at 310) .
  • the PRACH message can be a first message (Msg1) of a 4 step RACH procedure.
  • Base station 222 can receive the PRACH message and respond by sending UE 210 a Msg2 RAR message (at 315) .
  • Process 300 can also include UE 210 determining whether to indicate a capability of Msg4 PDSCH repetition or a request for Msg4 PDSCH repetition.
  • Fig. 5 is a diagram of an example 500 for determining whether to indicate a capability for Msg4 PDSCH repetition and/or request for Msg4 PDSCH repetition according to one or more implementations described herein.
  • example 500 includes a logical block diagram of conditions or factors and corresponding responses.
  • the conditions or factors can include whether UE 210 is capable of Msg4 PDSCH repetition and whether a signal strength measured by UE 210 is greater than an RSRP threshold.
  • Example 500 can represent an algorithm, set of instructions, and/or sequence of operations performed by UE 210.
  • UE 210 can determine whether UE is capable of Msg4 PDSCH repetition communications. This can include receiving multiple Msg4 PDSCH transmissions from base station 222, satellite 260, and/or another type of RAN node. This can also include whether UE 210 is capable of Msg4 PDSCH transmissions via multiple Msg4 PUCCH transmissions (e.g., HARQ messages) . UE 210 can also determine whether a measured strength of a DL reference signal (RS) is greater than one or more RSRP thresholds.
  • the DL RS can include one or more of: a SSS, PBCH DMRS, Msg2 PDCCH DMRS, Msg2 PDSCH DMRS, etc.
  • the RSRP threshold can include one or more absolute RSRP thresholds, relative RSRP thresholds, default RSRP thresholds, or a combination thereof.
  • UE 210 when UE 210 is capable of Msg4 PDSCH repetition communications and a measured RS is greater than an RSRP threshold, UE 210 can refrain from communicating an indication to base station 222 that UE 210 is capable of Msg4 PDSCH repetition. UE 210 can also refrain from communicating a request to base station 222 for Msg4 PDSCH repetition. When UE 210 is capable of Msg4 PDSCH repetition communications, but a measured RS is not greater than an RSRP threshold, UE 210 can communicate an indication to base station 222 that UE 210 is capable of Msg4 PDSCH repetition.
  • UE 210 can also, or alternatively, communicate a request to base station 222 for Msg4 PDSCH repetition.
  • UE 210 can refrain from communicating a capability or request for Msg4 PDSCH repetition to base station 222.
  • UE 210 can apply multiple RSRP thresholds to determining whether to communicate a capability and/or request to base station 222 for Msg4 PDSCH repetition. For example, assume that UE 210 is configured to apply 2 RSRP thresholds (e.g., RSRP_Threshold_1 and RSRP_Threshold_2) when determining whether to communicate a capability and/or request to base station 222. Further, assume that RSRP_Threshold_1 is greater than RSRP_Threshold_2. When a measured RS is greater than RSRP_Threshold_1, UE 210 can be configured to refrain from communicating a request for Msg4 PDSCH repetition to base station 222.
  • 2 RSRP thresholds e.g., RSRP_Threshold_1 and RSRP_Threshold_2
  • RSRP_Threshold_1 is greater than RSRP_Threshold_2.
  • UE 210 can be configured to refrain from communicating
  • UE 210 can be configured to communicate to base station 222 that UE 210 is capable of Msg4 PDSCH repetition.
  • UE 210 can be configured to request 2 Msg4 PDSCH repetitions.
  • UE 210 can also communicate to base station 222 that UE 210 is capable of Msg4 PDSCH repetition.
  • UE 210 can be configured to request more (e.g., 4) Msg4 PDSCH repetitions from base station 222.
  • UE 210 can also communicate to base station 222 that UE 210 is capable of Msg4 PDSCH repetition.
  • UE’s capability of Msg4 PDSCH repetition may not be communicated to base station 222 when UE 210 communicates to base station 222 the request of Msg4 PDSCH repetitions, or vice versa.
  • process 300 can include UE 210 communicate a Msg3 PUSCH to base station 222 (block 325) .
  • the Msg3 PUSCH can include an indication for Msg4 PDSCH repetition.
  • the Msg3 PUSCH can include an indication that UE 210 is capable of Msg4 PDSCH repetition.
  • the Msg3 PUSCH can include a request for Msg4 PDSCH repetition.
  • the Msg3 PUSCH can include an indication that UE 210 is capable of Msg4 PDSCH repetition and a request for Msg4 PDSCH repetition.
  • the contents of the Msg3 PUSCH can depend on the determination by UE 210 of whether to indicate a capability for Msg4 PDSCH repetition and/or request for Msg4 PDSCH repetition as described above. In some implementations, the Msg3 PUSCH can indicate a number of Msg4 PDSCH repetitions.
  • the Msg3 PUSCH can include a MAC layer sub-header that indicates a capability for Msg4 PDSCH repetition or a request for Msg4 PDSCH repetition.
  • the indication can include a 1-bit field, which can be a reserved bit of the MAC layer sub-header.
  • the Msg3 PUSCH can include a MAC layer logical channel ID (LCID) code point.
  • the MAC layer LCID code point can be configured to indicate a capability for Msg4 PDSCH repetition or a request for Msg4 PDSCH repetition.
  • dedicated preambles on one or more shared RACH occasions can be reserved to indicate a capability for Msg4 PDSCH repetition or a request for Msg4 PDSCH repetition.
  • one or more dedicated RACH occasions can be configured to indicate a capability for Msg4 PDSCH repetition or a request for Msg4 PDSCH repetition.
  • Process 300 can include base station 222 determining a repetition factor of a Msg4 PDSCH (at 330) .
  • a repetition factor as described herein, can include a number of Msg4 PDSCH repetitions.
  • a repetition factor can also, or alternatively, include a value (e.g., a factor) that can be applied to another value or parameter to determine the number of Msg4 PDSCH repetitions.
  • the repetition factor of the Msg4 PDSCH can correspond to UE 210 (e.g., the RACH procedure involving UE 210) .
  • Base station 222 can determine the repetition factor of the Msg4 PDSCH based on one or more factors, conditions, or parameters, such as a number of Msg4 PDSCH communicated to UE 210 via a SIB, whether base station 222 received an indication of capability from UE 210 for Msg4 PDSCH repetition, and/or whether base station 222 received a request from UE 210 for Msg4 PDSCH repetition.
  • Process 300 can also include base station 222 communicating DCI to UE 210 (at 335) .
  • the DCI can include scheduling information a Msg4 PDSCH.
  • the DCI can also include a repetition factor, which can indicate a number of Msg4 PDSCH repetitions or enable UE 210 to determine a number of Msg4 PDSCH repetitions based on the repetition factor.
  • the DCI can also include scheduling information for the Msg4 PDSCH repetitions. Scheduling information can include a grant or allocation of time and frequency resources for using a PDSCH to transmit the Msg4 and repetitions of Msg4.
  • Fig. 6 is a diagram of an example techniques 600 for using DCI schedule an Msg4 PDSCH and indicate a number of Msg4 PDSCH repetitions according to one or more implementations described herein.
  • example techniques 600 can include DCI 610 that includes parameters, values, fields, and other types of control information that is configured to allocate time and frequency resources of a PDSCH for an Msg4 directed to UE 210. This can include an allocation of time and frequency resources for repetitions of the Msg4 via the PDSCH. This can also include an indication of a maximum number of times that the Msg4 can be repeated (e.g., a repetition number indication) .
  • base station 222 can generate DCI 610 to indicate the number of Msg4 PDSCH repetitions using one or more example techniques 600. Additionally, or alternatively, UE 210 can be configured to determine or derive the number of Msg4 PDSCH repetitions based on DCI 610. DCI 610 can explicitly or implicitly indicate the number of Msg4 PDSCH repetitions.
  • DCI 610 can be configured to indicate the number of repetitions in one or more ways. Examples of such can include using a modulation and coding scheme (MCS) field 620, a HARQ process number field 630, a DL assignment index (DAI) field 640, an RNTI derived from a TC-RNTI 650, an implicit indication of the number of repetitions 660, and more. Implicit indication 660 can be based on a number of Msg4 PUCCH repetitions 680 and/or an Msg2 scaling factor 690. In some implementations, DCI 610 does not include an indication 670 of the number of Msg4 PDSCH repetitions. Rather, the number of Msg4 PDSCH repetitions can be determined based on one or more RSRP thresholds,
  • Some DCI fields (e.g., fields in DCI 1_0) with cyclic redundancy check (CRC) scrambled by TC-RNTI can be used or reinterpreted to indicate a number of Msg4 PDSCH repetitions.
  • An example of such fields can include MCS field 620, HARQ process number field 630, and DAI field 640.
  • MCS field 620 when there are 1 or 2 Msg4 PDSCH repetition numbers configured by an SIB, then 1 most significant bits (MSB) of MCS field 620 can be used to indicate the number of Msg4 PDSCH repetitions; when there are 3 or 4 Msg4 PDSCH repetition numbers configured by an SIB, then 2 MSB of MCS field 620 can be used to indicate the number of Msg4 PDSCH repetitions; and so on.
  • MSB most significant bits
  • HARQ process number field 630 when there are 1 or 2 Msg4 PDSCH repetition numbers configured by an SIB, then 1 MSB of HARQ process number field 630 can be used to indicate the number of Msg4 PDSCH repetitions; when there are 3 or 4 Msg4 PDSCH repetition numbers configured by an SIB, then 2 MSB of HARQ process number field 630 can be used to indicate the number of Msg4 PDSCH repetitions; and so on.
  • DAI field 640 when Msg4 PUCCH repetition is not supported by base station 222 (e.g., when a number of Msg4 PUCCH repetitions is not configured by a SIB) , then a reserved 2-bit DIA field can be used to indicate the number of Msg4 PDSCH repetitions.
  • DAI field 630 When Msg4 PUCCH repetition is supported by base station 222, but only 1 reserved bit in DAI field 630 is used (e.g., only up to 2 Msg4 PUCCH repetition numbers are configured via SIB) , then a remaining 1 reserved bit in DAI field 630 can be used to indicate the number of Msg4 PDSCH repetitions. In such a scenario, only up to 2 Msg4 PDSCH repetition numbers can configured by the corresponding SIB.
  • DCI 610 can indicate a number of Msg4 PDSCH repetitions based on a new RNTI being derived from a TC-RNTI. For example, referring to DCI 610 (e.g., DCI 1_0 format) , when a new RNTI is configured to be equal to TC-RNTI + 1 (mod 2 16 ) , then the number of Msg4 PDSCH repetitions can be 2. When the new RNTI is configured as equal to TC-RNTI + 2 (mod 2 16 ) , then the number of Msg4 PDSCH repetitions can be 4.
  • a new design of DCI 1_0 format can be used to indicate a number of Msg4 PDSCH repetitions based on a new RNTI being derived from a TC-RNTI. For example, when a new RNTI is configured to be equal to TC-RNTI + 1 (mod 2 16 ) , then a new DCI field (e.g., an “Msg4 PDSCH repetition number” field) can be used to indicate the number of Msg4 PDSCH repetitions.
  • Base station 222 and/or UE 210 can be configured to determine the number of Msg4 PDSCH repetitions based on the new RNTI derived from a TC-RNTI.
  • base station 222 can derive the new RNTI from the TC-RNTI and can include the new RNTI in DCI 610.
  • Base station 222 and/or UE 210 can be configured to determine the number of Msg4 PDSCH repetitions based on the new RNTI relative to the TC-RNTI.
  • DCI 610 can indicate a number of Msg4 PDSCH repetitions based on implicit indication 660.
  • Implicit indication 660 can be based on a number of Msg4 PUCCH repetitions 680.
  • the number of Msg4 PUCCH repetitions can be used by base station 222 and/or UE 210 to derive the number of Msg4 PDSCH repetitions.
  • implicit indication 660 can be based on an Msg2 scaling factor 690.
  • an Msg 2 scaling factor e.g., 1/2 or 1/4
  • the number of Msg4 PDSCH repetitions is determined accordingly. For instance, when an Msg2 scaling factor is 1/2, then the number of Msg4 PDSCH repetitions can be 2; when the Msg2 scaling factor is 1/4, then the number of Msg4 PDSCH repetitions can be 4; and so on.
  • DCI 610 does not include an indication of a number of Msg4 PDSCH repetitions. Instead, the number of Msg4 PDSCH repetitions can be determined based on one or more RSRP thresholds. In some implementations, when UE 210 communicates a request to base station 222 for the number of Msg4 PDSCH repetitions to be based on RSRP measurements, then the repetition number can be determined accordingly. For example, UE 210 can be configured to use a single RSRP measurement threshold, and a single repetition number can be configured via SIB.
  • UE 210 and base station 222 can be configured to operate based on the number of Msg4 PDSCH repetitions being equal to the number configured via SIB.
  • SIB multiple RSRP thresholds can be configured, and multiple repetition numbers can be configured via SIB.
  • UE 210 can communicate a request for a certain number of Msg4 PDSCH repetitions (e.g., resulting from a comparison of a measured signal strength to the multiple RSRP thresholds) , then UE 210 and base station 222 can be configured to operate based on the number of Msg4 PDSCH repetitions being equal to the number requested.
  • a certain number of Msg4 PDSCH repetitions e.g., resulting from a comparison of a measured signal strength to the multiple RSRP thresholds
  • process 300 can include base station 222 communicating a Msg4 to UE 210 (at 340) .
  • Base station 222 can repeat the transmission of Msg4 to UE 210 according to a number of Msg4 PDSCH repetitions schedule by DCI or otherwise determined by base station 222 and UE 210.
  • the number of Msg4 PDSCH repetitions is equal to 1
  • base station 222 can communicate the Msg4 once; when the number of Msg4 PDSCH repetitions is equal to 2, base station 222 can communicate the Msg4 twice; and so on.
  • Process 300 can include UE 210 receiving the Msg4 (at 345) .
  • UE 210 can receive the Msg4 of a first transmission of the Msg4 or on a retransmission of Msg4.
  • UE 210 can communicate a HARQ-ACK message about Msg4 to base station 222 (at 350) .
  • base station 222 and UE 210 can continue communicating via the PDSCH using PDSCH repetitions (at 355) .
  • a dedicated PDSCH configuration is not provided in Msg4, then the same number of repetitions determined for the Msg4 PDSCH can be applied to subsequent PDSCH transmissions until a dedicated PDSCH configuration is provided.
  • Fig. 7 is a diagram of an example process 700 for Msg4 PDSCH repetitions according to one or more implementations described herein.
  • Process 700 can be implemented by UE 210.
  • some or all of process 700 can be performed by one or more other systems or devices, including one or more of the devices of Fig. 2.
  • process 700 can include one or more fewer, additional, differently ordered and/or arranged operations than those shown in Fig. 7.
  • some or all of the operations of process 700 can be performed independently, successively, simultaneously, etc., of one or more of the other operations of process 700.
  • the techniques described herein are not limited to the number, sequence, arrangement, timing, etc., of the operations or processes depicted in Fig. 7.
  • process 700 can include receiving configuration information for message 4 (Msg4) physical downlink shared channel (PDSCH) repetition (block 710) .
  • Process 700 can include determining, based on the configuration information, a capability of the baseband circuitry to support the Msg4 PDSCH repetition (block 720) .
  • Process 700 can include communicating an indication of the capability of the baseband circuitry to support the Msg4 PDSCH repetition or a request for Msg4 PDSCH repetition (block 730) .
  • Process 700 can include receiving downlink control information (DCI) comprising an indication of a number of Msg4 PDSCH repetitions (block 740) .
  • DCI downlink control information
  • Process 700 can include receiving a Msg4 PDSCH message number of Msg4 PDSCH repetitions.
  • Fig. 8 is a diagram of an example process 800 for Msg4 PDSCH repetitions according to one or more implementations described herein.
  • Process 800 can be implemented by one or more base stations 222 and/or another access network node, such as satellite 260. In some implementations, some or all of process 800 can be performed by one or more other systems or devices, including one or more of the devices of Fig. 2. Additionally, process 800 can include one or more fewer, additional, differently ordered and/or arranged operations than those shown in Fig. 8. In some implementations, some or all of the operations of process 800 can be performed independently, successively, simultaneously, etc., of one or more of the other operations of process 800. As such, the techniques described herein are not limited to a number, sequence, arrangement, timing, etc., of the operations or processes depicted in Fig. 8.
  • process 800 can include communicating, to a user equipment (UE) , configuration information for message 4 (Msg4) physical downlink shared channel (PDSCH) repetition (block 810) .
  • Process 800 can include receiving, from the UE, an indication for Msg4 PDSCH repetition (block 820) .
  • Process 800 can include determining, in response to the indication for Msg4 PDSCH repetition, a number of Msg4 PDSCH repetitions for the UE (block 830) .
  • Process 800 can include communicating, to the UE, the number of Msg4 PDSCH repetitions (block 840) .
  • Process 800 can include communicating, to the UE, a Msg4 PDSCH in accordance with the number of Msg4 PDSCH repetitions (block 850) .
  • Fig. 9 is a diagram of an example of components of a device according to one or more implementations described herein.
  • the device 900 can include application circuitry 902, baseband circuitry 904, RF circuitry 906, front-end module (FEM) circuitry 908, one or more antennas 910, and power management circuitry (PMC) 912 coupled together at least as shown.
  • the components of the illustrated device 900 can be included in a UE or a RAN node.
  • the device 900 can include fewer elements (e.g., a RAN node does not utilize application circuitry 902, and instead include a processor/controller to process IP data received from a CN or an Evolved Packet Core (EPC) ) .
  • EPC Evolved Packet Core
  • the device 900 can include additional elements such as, for example, memory/storage, display, camera, sensor (including one or more temperature sensors, such as a single temperature sensor, a plurality of temperature sensors at different locations in device 900, etc. ) , or input/output (I/O) interface.
  • additional elements such as, for example, memory/storage, display, camera, sensor (including one or more temperature sensors, such as a single temperature sensor, a plurality of temperature sensors at different locations in device 900, etc. ) , or input/output (I/O) interface.
  • the components described below can be included in more than one device (e.g., said circuitries can be separately included in more than one device for Cloud-RAN (C-RAN) implementations) .
  • C-RAN Cloud-RAN
  • the application circuitry 902 can include one or more application processors.
  • the application circuitry 902 can include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the processor (s) can include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc. ) .
  • the processors can be coupled with or can include memory/storage and can be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the device 900.
  • processors of application circuitry 902 can process IP data packets received from an EPC.
  • the baseband circuitry 904 can include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the baseband circuitry 904 can include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 906 and to generate baseband signals for a transmit signal path of the RF circuitry 906.
  • Baseband circuity 904 can interface with the application circuitry 902 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 906.
  • the baseband circuitry 904 can include a 3G baseband processor 904A, a 4G baseband processor 904B, a 5G baseband processor 904C, or other baseband processor (s) 904D for other existing generations, generations in development or to be developed in the future (e.g., 5G, 6G, etc. ) .
  • the baseband circuitry 904 e.g., one or more of baseband processors 904A-D
  • baseband processors 904A-D can be included in modules stored in the memory 904G and executed via a Central Processing Unit (CPU) 904E.
  • the radio control functions can include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc.
  • modulation/demodulation circuitry of the baseband circuitry 904 can include Fast-Fourier Transform (FFT) , precoding, or constellation mapping/de-mapping functionality.
  • FFT Fast-Fourier Transform
  • encoding/decoding circuitry of the baseband circuitry 904 can include convolution, tail-biting convolution, turbo, Viterbi, or Low-Density Parity Check (LDPC) encoder/decoder functionality. Implementations of modulation/demodulation and encoder/decoder functionality are not limited to these examples and can include other suitable functionality in other implementations.
  • LDPC Low-Density Parity Check
  • memory 904G can receive and/or store information and instructions for enabling Msg4 PDSCH repetitions.
  • UE 210 (or a component thereof, such as a baseband processor) can determine whether to indicate or request Msg4 PDSCH repetition based on the capability of UE 210 and RSRP thresholds.
  • Base station 222 can use DCI for scheduling Msg4 PDSCH repetitions based on one or more of: a reinterpretation of an existing DCI field; a new RNTI; an implicit indication based on Msg4 PUCCH repetitions; and a number of Msg4 PDSCH repetitions requested by UE 210.
  • the number of Msg4 PDSCH repetitions can be applied until a dedicated PDSCH configuration is provided to the UE.
  • the baseband circuitry 904 can include one or more audio digital signal processor (s) (DSP) 904F.
  • the audio DSPs 904F can include elements for compression/decompression and echo cancellation and can include other suitable processing elements in other implementations.
  • Components of the baseband circuitry can be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some implementations.
  • some or all of the constituent components of the baseband circuitry 904 and the application circuitry 902 can be implemented together such as, for example, on a system on a chip (SOC) .
  • SOC system on a chip
  • the baseband circuitry 904 can provide for communication compatible with one or more radio technologies.
  • the baseband circuitry 904 can support communication with a NG-RAN, an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN) , a wireless local area network (WLAN) , a wireless personal area network (WPAN) , etc.
  • EUTRAN evolved universal terrestrial radio access network
  • WMAN wireless metropolitan area networks
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • RF circuitry 906 can enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium.
  • the RF circuitry 906 can include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • RF circuitry 906 can include a receive signal path which can include circuitry to down-convert RF signals received from the FEM circuitry 908 and provide baseband signals to the baseband circuitry 904.
  • RF circuitry 906 can also include a transmit signal path which can include circuitry to up-convert baseband signals provided by the baseband circuitry 904 and provide RF output signals to the FEM circuitry 908 for transmission.
  • the receive signal path of the RF circuitry 906 can include mixer circuitry 906A, amplifier circuitry 906B and filter circuitry 906C.
  • the transmit signal path of the RF circuitry 906 can include filter circuitry 906C and mixer circuitry 906A.
  • RF circuitry 906 can also include synthesizer circuitry 906D for synthesizing a frequency for use by the mixer circuitry 906A of the receive signal path and the transmit signal path.
  • the mixer circuitry 906A of the receive signal path can be configured to down-convert RF signals received from the FEM circuitry 908 based on the synthesized frequency provided by synthesizer circuitry 906D.
  • the amplifier circuitry 906B can be configured to amplify the down-converted signals and the filter circuitry 906C can be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals.
  • Output baseband signals can be provided to the baseband circuitry 904 for further processing.
  • the output baseband signals can be zero-frequency baseband signals, although this is not a requirement.
  • mixer circuitry 906A of the receive signal path can comprise passive mixers, although the scope of the implementations is not limited in this respect.
  • the mixer circuitry 906A of the transmit signal path can be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 906D to generate RF output signals for the FEM circuitry 908.
  • the baseband signals can be provided by the baseband circuitry 904 and can be filtered by filter circuitry 906C.
  • the mixer circuitry 906A of the receive signal path and the mixer circuitry 906A of the transmit signal path can include two or more mixers and can be arranged for quadrature down conversion and up conversion, respectively.
  • the mixer circuitry 906A of the receive signal path and the mixer circuitry 906A of the transmit signal path can include two or more mixers and can be arranged for image rejection (e.g., Hartley image rejection) .
  • the mixer circuitry 906A of the receive signal path and the mixer circuitry ⁇ 1406A can be arranged for direct down conversion and direct up conversion, respectively.
  • the mixer circuitry 906A of the receive signal path and the mixer circuitry 906A of the transmit signal path can be configured for super-heterodyne operation.
  • the output baseband signals, and the input baseband signals can be analog baseband signals, although the scope of the implementations is not limited in this respect.
  • the output baseband signals, and the input baseband signals can be digital baseband signals.
  • the RF circuitry 906 can include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 904 can include a digital baseband interface to communicate with the RF circuitry 906.
  • ADC analog-to-digital converter
  • DAC digital-to-analog converter
  • a separate radio IC circuitry can be provided for processing signals for each spectrum, although the scope of the implementations is not limited in this respect.
  • the synthesizer circuitry 906D can be a fractional-N synthesizer or a fractional N/N+1 synthesizer, although the scope of the implementations is not limited in this respect as other types of frequency synthesizers can be suitable.
  • synthesizer circuitry 906D can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 906D can be configured to synthesize an output frequency for use by the mixer circuitry 906A of the RF circuitry 906 based on a frequency input and a divider control input.
  • the synthesizer circuitry 906D can be a fractional N/N+1 synthesizer.
  • frequency input can be provided by a voltage-controlled oscillator (VCO) , although that is not a requirement.
  • VCO voltage-controlled oscillator
  • Divider control input can be provided by either the baseband circuitry 904 or the applications circuitry 902 depending on the desired output frequency.
  • a divider control input e.g., N
  • N can be determined from a look-up table based on a channel indicated by the applications circuitry 902.
  • Synthesizer circuitry 906D of the RF circuitry 906 can include a divider, a delay-locked loop (DLL) , a multiplexer and a phase accumulator.
  • the divider can be a dual modulus divider (DMD) and the phase accumulator can be a digital phase accumulator (DPA) .
  • the DMD can be configured to divide the input signal by either N or N+1 (e.g., based on a carry out) to provide a fractional division ratio.
  • the DLL can include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop.
  • the delay elements can be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line.
  • Nd is the number of delay elements in the delay line.
  • synthesizer circuitry 906D can be configured to generate a carrier frequency as the output frequency, while in other implementations, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other.
  • the output frequency can be a LO frequency (fLO) .
  • the RF circuitry 906 can include an IQ/polar converter.
  • FEM circuitry 908 can include a receive signal path which can include circuitry configured to operate on RF signals received from one or more antennas 910, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 906 for further processing.
  • FEM circuitry 908 can also include a transmit signal path which can include circuitry configured to amplify signals for transmission provided by the RF circuitry 906 for transmission by one or more of the one or more antennas 910.
  • the amplification through the transmit or receive signal paths can be done solely in the RF circuitry 906, solely in the FEM circuitry 908, or in both the RF circuitry 906 and the FEM circuitry 908.
  • the FEM circuitry 908 can include a TX/RX switch to switch between transmit mode and receive mode operation.
  • the FEM circuitry can include a receive signal path and a transmit signal path.
  • the receive signal path of the FEM circuitry can include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 906) .
  • the transmit signal path of the FEM circuitry 908 can include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 906) , and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 910) .
  • PA power amplifier
  • the PMC 912 can manage power provided to the baseband circuitry 904.
  • the PMC 912 can control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.
  • the PMC 912 can often be included when the device 900 is capable of being powered by a battery, for example, when the device is included in a UE.
  • the PMC 912 can increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.
  • Fig. 9 shows the PMC 912 coupled only with the baseband circuitry 904.
  • the PMC 912 can be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 902, RF circuitry 906, or FEM circuitry 908.
  • the PMC 912 can control, or otherwise be part of, various power saving mechanisms of the device 900. For example, if the device 900 is in an RRC_Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it can enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device 900 can power down for brief intervals of time and thus save power.
  • DRX Discontinuous Reception Mode
  • the device 900 can transition off to an RRC_Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc.
  • the device 900 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again.
  • the device 900 does not receive data in this state; in order to receive data, it can transition back to RRC_Connected state.
  • An additional power saving mode can allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours) . During this time, the device is unreachable to the network and can power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.
  • Processors of the application circuitry 902 and processors of the baseband circuitry 904 can be used to execute elements of one or more instances of a protocol stack.
  • processors of the baseband circuitry 904 alone or in combination, can be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the baseband circuitry 904 can utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers) .
  • Layer 3 can comprise a RRC layer, described in further detail below.
  • Layer 2 can comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below.
  • Layer 1 can comprise a physical (PHY) layer of a UE/RAN node, described in further detail below.
  • Fig. 10 is a block diagram illustrating components, according to some example implementations, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
  • Fig. 10 shows a diagrammatic representation of hardware resources 1000 including one or more processors (or processor cores) 1010, one or more memory/storage devices 1020, and one or more communication resources 1030, each of which can be communicatively coupled via a bus 1040.
  • node virtualization e.g., NFV
  • a hypervisor can be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 1000.
  • the processors 1010 can include, for example, a processor 1012 and a processor 1014.
  • CPU central processing unit
  • RISC reduced instruction set computing
  • CISC complex instruction set computing
  • GPU graphics processing unit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • RFIC radio-frequency integrated circuit
  • the memory/storage devices 1020 can include main memory, disk storage, or any suitable combination thereof.
  • the memory/storage devices 1020 can include, but are not limited to any type of volatile or non-volatile memory such as dynamic random-access memory (DRAM) , static random-access memory (SRAM) , erasable programmable read-only memory (EPROM) , electrically erasable programmable read-only memory (EEPROM) , Flash memory, solid-state storage, etc.
  • DRAM dynamic random-access memory
  • SRAM static random-access memory
  • EPROM erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • Flash memory solid-state storage, etc.
  • memory/storage devices 1020 receive and/or store information and instructions 1055 for enabling Msg4 PDSCH repetitions.
  • UE 210 (or a component thereof, such as a baseband processor) can determine whether to indicate or request Msg4 PDSCH repetition based on a capability of UE 210 and RSRP thresholds.
  • Base station 222 can use DCI for scheduling Msg4 PDSCH repetitions based on one or more of: a reinterpretation of an existing DCI field; a new RNTI; an implicit indication based on Msg4 PUCCH repetitions; and a number of Msg4 PDSCH repetitions requested by UE 210.
  • the number of Msg4 PDSCH repetitions can be applied until a dedicated PDSCH configuration is provided to the UE.
  • the communication resources 1030 can include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices 1004 or one or more databases 1006 via a network 1008.
  • the communication resources 1030 can include wired communication components (e.g., for coupling via a Universal Serial Bus (USB) ) , cellular communication components, NFC components, components (e.g., Low Energy) , components, and other communication components.
  • wired communication components e.g., for coupling via a Universal Serial Bus (USB)
  • USB Universal Serial Bus
  • NFC components e.g., Low Energy
  • components e.g., Low Energy
  • Examples and/or implementations herein can include subject matter such as a method, means for performing acts or blocks of the method, at least one machine-readable medium including executable instructions that, when performed by a machine (e.g., a processor (e.g., processor , etc. ) with memory, an application-specific integrated circuit (ASIC) , a field programmable gate array (FPGA) , or the like) cause the machine to perform acts of the method or of an apparatus or system for concurrent communication using multiple communication technologies according to implementations and examples described.
  • a machine e.g., a processor (e.g., processor , etc. ) with memory, an application-specific integrated circuit (ASIC) , a field programmable gate array (FPGA) , or the like
  • ASIC application-specific integrated circuit
  • FPGA field programmable gate array
  • baseband circuitry may comprise: a memory; and one or more processors configured to, when executing instructions stored in the memory, cause the baseband circuitry to: receive, via radio frequency (RF) circuitry and from a base station, configuration information for message 4 (Msg4) physical downlink shared channel (PDSCH) repetition; determine, based on the configuration information, a capability of the baseband circuitry to support the Msg4 PDSCH repetition; communicate, via the RF circuitry and to the base station, an indication of the capability of the baseband circuitry to support the Msg4 PDSCH repetition or a request for Msg4 PDSCH repetition; receive, via the RF circuitry and from the base station, downlink control information (DCI) comprising an indication of a number of Msg4 PDSCH repetitions; and receive, via the RF circuitry and from the base station, a Msg4 PDSCH message number of Msg4 PDSCH repetitions.
  • DCI downlink control information
  • the configuration information for the Msg4 PDSCH repetition is received via system information block (SIB) .
  • SIB system information block
  • the configuration information for the Msg4 PDSCH repetition comprises at least one reference signal received power (RSRP) threshold for Msg4 PDSCH repetition.
  • the at least one RSRP threshold comprises at least one of: an absolute RSRP threshold; or a reference RSRP threshold.
  • the configuration information for the Msg4 PDSCH repetition comprises an RSRP threshold scheme comprising instructions using the at least one RSRP threshold to enable Msg4 PDSCH repetition.
  • the one or more processors are further configured to cause the baseband circuitry to: determine whether the baseband circuitry is capable of Msg4 PDSCH repetition.
  • the one or more processors are further configured to cause the baseband circuitry to: measure a signal strength of a downlink (DL) reference signal; and determine whether the signal strength of the DL reference signal is greater than the at least one RSRP threshold.
  • DL downlink
  • the configuration information for the Msg4 PDSCH repetition comprises a plurality of reference signal received power (RSRP) thresholds corresponding to different signal strengths
  • the one or more processors are further configured to cause the baseband circuitry to: measure a signal strength of a downlink (DL) reference signal; and determine whether the signal strength of the DL reference signal is greater than each RSRP threshold of the plurality of RSRP thresholds.
  • RSRP reference signal received power
  • the one or more processors are configured to indicate the capability of the baseband circuitry to support the Msg4 PDSCH repetition via at least one of: a media access control (MAC) layer sub-header; a MAC layer logical channel ID (LCID) ; a dedicated random access channel (RACH) occasion configured to indicate Msg4 PDSCH repetition; or a dedicated preamble on a shared random access channel (RACH) occasion reserved to indicate Msg4 PDSCH repetition.
  • MAC media access control
  • LCID MAC layer logical channel ID
  • RACH dedicated random access channel
  • RACH dedicated preamble on a shared random access channel
  • the indication of the number of Msg4 PDSCH repetitions is provided via at least one of: a modulation and coding scheme (MCS) field; a hybrid automatic repeat request (HARQ) process number field; or a downlink (DL) assignment index (DAI) field.
  • MCS modulation and coding scheme
  • HARQ hybrid automatic repeat request
  • DAI downlink assignment index
  • the indication of the number of Msg4 PDSCH repetitions is provided via one of: a radio network temporary identifier (RNTI) derived from a temporary cell RNTI (TC-RNTI) ; a number of Msg4 physical uplink (UL) control channel (PUCCH) repetitions; or a scaling factor used for Msg 2 transmission.
  • RNTI radio network temporary identifier
  • TC-RNTI temporary cell RNTI
  • PUCCH physical uplink
  • scaling factor used for Msg 2 transmission or a scaling factor used for Msg 2 transmission.
  • the one or more processors are further configured to cause the baseband circuitry to: determine a Msg4 PDSCH repetition number based on a measured signal strength a downlink (DL) reference signal relative to a reference signal received power (RSRP) ; and communicate, via the RF circuitry, a request for the Msg4 PDSCH repetition number to the base station.
  • the one or more processors are further configured to cause the baseband circuitry to: apply the number of Msg4 PDSCH repetitions to PDSCH communications until a dedicated PDSCH configuration is received from the base station.
  • a user equipment may comprise: a memory; and one or more processors configured to, when executing instructions stored in the memory, cause the UE to: receive, via radio frequency (RF) circuitry and from a base station, configuration information for message 4 (Msg4) physical downlink shared channel (PDSCH) repetition; determine, based on the configuration information, a capability of the baseband circuitry to support the Msg4 PDSCH repetition; communicate, via the RF circuitry and to the base station, an indication of the capability of the baseband circuitry to support the Msg4 PDSCH repetition or a request for Msg4 PDSCH repetition; receive, via the RF circuitry and from the base station, downlink control information (DCI) comprising an indication of a number of Msg4 PDSCH repetitions; and receive, via the RF circuitry and from the base station, a Msg4 PDSCH message in accordance with the number of Msg4 PDSCH repetitions
  • DCI downlink control information
  • a base station may comprise: a memory; and one or more processors configured to, when executing instructions stored in the memory, cause the base station to: communicate, to a user equipment (UE) , configuration information for message 4 (Msg4) physical downlink shared channel (PDSCH) repetition; receive, from the UE, an indication for Msg4 PDSCH repetition; determine, in response to the indication for Msg4 PDSCH repetition, a number of Msg4 PDSCH repetitions for the UE; communicate, to the UE, the number of Msg4 PDSCH repetitions; and communicate, to the UE, a Msg4 PDSCH in accordance with the number of Msg4 PDSCH repetitions.
  • Msg4 message 4
  • the configuration information comprises a plurality of Msg4 PDSCH repetition factors and at least one reference signal received power (RSRP) threshold.
  • the configuration information is communicated via at least one of: system information block 1 (SIB1) ; and SIB19.
  • SIB1 system information block 1
  • SIB19 system information block 1
  • the indication for Msg4 PDSCH repetition comprises at least one of: an indication of a capability of the UE for Msg4 PDSCH repetition; and a request for Msg4 PDSCH repetition.
  • the indication for Msg4 PDSCH repetition is received via a message 3 (Msg) physical uplink shared channel (PUSCH) .
  • the one or more processors are further configured to cause the base station to: apply the number of Msg4 PDSCH repetitions to PDSCH communications involving the UE until a dedicated PDSCH configuration is provided to the UE.
  • a method, performed by baseband circuitry may comprise: receiving configuration information for message 4 (Msg4) physical downlink shared channel (PDSCH) repetition; determining, based on the configuration information, a capability of the baseband circuitry to support the Msg4 PDSCH repetition; communicating an indication of the capability of the baseband circuitry to support the Msg4 PDSCH repetition or a request for Msg4 PDSCH repetition; receiving downlink control information (DCI) comprising an indication of a number of Msg4 PDSCH repetitions; and receiving a Msg4 PDSCH message number of Msg4 PDSCH repetitions.
  • Msg4 message 4
  • PDSCH physical downlink shared channel
  • a method, performed by user equipment (UE) may comprise: receiving configuration information for message 4 (Msg4) physical downlink shared channel (PDSCH) repetition; determining, based on the configuration information, a capability of the baseband circuitry to support the Msg4 PDSCH repetition; communicating an indication of the capability of the baseband circuitry to support the Msg4 PDSCH repetition or a request for Msg4 PDSCH repetition; receiving downlink control information (DCI) comprising an indication of a number of Msg4 PDSCH repetitions; and receiving a Msg4 PDSCH message number of Msg4 PDSCH repetitions.
  • Msg4 message 4
  • PDSCH physical downlink shared channel
  • a method, performed by a base station may comprise: communicating, to a user equipment (UE) , configuration information for message 4 (Msg4) physical downlink shared channel (PDSCH) repetition; receiving, from the UE, an indication for Msg4 PDSCH repetition; determining, in response to the indication for Msg4 PDSCH repetition, a number of Msg4 PDSCH repetitions for the UE; communicating, to the UE, the number of Msg4 PDSCH repetitions; and communicating, to the UE, a Msg4 PDSCH in accordance with the number of Msg4 PDSCH repetitions.
  • Msg4 message 4
  • the term “or” is intended to mean an inclusive “or” rather than an exclusive “or. ” That is, unless specified otherwise, or clear from context, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B;or X employs both A and B, then “X employs A or B” is satisfied under any of the foregoing instances.
  • the articles “a” and “an” as used in this application and the appended claims should generally be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form.
  • personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users.
  • personally identifiable information data should be managed and handled to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne des solutions pour permettre des répétitions de canal physique partagé de liaison descendante (PDSCH) de liaison descendante (DL) de message 4 (Msg4). Un équipement utilisateur (UE) peut déterminer s'il faut indiquer ou demander une répétition de PDSCH Msg4 sur la base d'informations de capacité et de seuils de puissance reçue de signal de référence (RSRP). Une station de base peut utiliser des informations de commande de liaison descendante (DCI) pour planifier des répétitions de PDSCH de Msg4 sur la base d'une réinterprétation d'un champ de DCI existant, d'un nouvel identifiant temporaire de réseau radio de cellule temporaire (TC-RNTI), d'une indication implicite basée sur des répétitions de canal de commande de liaison montante physique (PUCCH) de Msg4, ou d'un nombre de répétitions de PDSCH de Msg4 demandées par l'UE. Le nombre de répétitions de PDSCH de Msg4 peut être appliqué jusqu'à ce qu'une configuration de PDSCH dédiée soit fournie à l'UE.
PCT/CN2024/092206 2024-05-10 2024-05-10 Systèmes, dispositifs et procédés pour répétitions de pdsch msg4 Pending WO2025231797A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/092206 WO2025231797A1 (fr) 2024-05-10 2024-05-10 Systèmes, dispositifs et procédés pour répétitions de pdsch msg4

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/092206 WO2025231797A1 (fr) 2024-05-10 2024-05-10 Systèmes, dispositifs et procédés pour répétitions de pdsch msg4

Publications (1)

Publication Number Publication Date
WO2025231797A1 true WO2025231797A1 (fr) 2025-11-13

Family

ID=91375758

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/092206 Pending WO2025231797A1 (fr) 2024-05-10 2024-05-10 Systèmes, dispositifs et procédés pour répétitions de pdsch msg4

Country Status (1)

Country Link
WO (1) WO2025231797A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022185184A1 (fr) * 2021-03-01 2022-09-09 Lenovo (Singapore) Pte. Ltd. Configuration basée sur une mesure de puissance reçue d'un signal de référence
US20230269778A1 (en) * 2020-09-28 2023-08-24 Qualcomm Incorporated Indication of tbs scaling and repetition for msg4 pdsch
WO2024036150A1 (fr) * 2022-08-09 2024-02-15 Apple Inc. Amélioration de la fiabilité pour la transmission du msg4

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230269778A1 (en) * 2020-09-28 2023-08-24 Qualcomm Incorporated Indication of tbs scaling and repetition for msg4 pdsch
WO2022185184A1 (fr) * 2021-03-01 2022-09-09 Lenovo (Singapore) Pte. Ltd. Configuration basée sur une mesure de puissance reçue d'un signal de référence
WO2024036150A1 (fr) * 2022-08-09 2024-02-15 Apple Inc. Amélioration de la fiabilité pour la transmission du msg4

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
NAVEEN PALLE ET AL: "HL signaling design for the PUCCH repetition request", vol. 3GPP RAN 2, no. Toulouse, FR; 20230821 - 20230825, 11 August 2023 (2023-08-11), XP052443550, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/TSG_RAN/WG2_RL2/TSGR2_123/Docs/R2-2307839.zip R2-2307839_HL signaling design for the PUCCH repetition request_v0.doc> [retrieved on 20230811] *

Similar Documents

Publication Publication Date Title
US20230164701A1 (en) Power control for signal interference management
US20240388391A1 (en) Systems, methods, and devices for secondary cell activation with ue-specific reference signal
US12463772B2 (en) Systems, methods, and devices for scheduling restrictions based on needforgap capabilities of user equipment
WO2020063757A1 (fr) Appareil et procédé pour reprise sur défaillance de faisceau dans une cellule secondaire
US12368486B2 (en) Systems, methods, and apparatuses for quasi-co-location (QCL) and spatial relation assumptions during random access procedures
US20240172148A1 (en) Systems, methods, and devices for initial access signaling in a wireless communication network
US20250331032A1 (en) Systems, methods, and devices for ul timing advance acquisition and update in a wireless communication network
US12457641B2 (en) Systems, methods, and devices for NR sidelink in the unlicensed spectrum
WO2025231797A1 (fr) Systèmes, dispositifs et procédés pour répétitions de pdsch msg4
US20240179633A1 (en) Systems, methods, and devices for power control and beam selection in mixed traffic
KR20240134974A (ko) Mac 계층 사용자 장비간 조정(iuc)을 위한 시스템들, 방법들 및 디바이스들
KR20240134973A (ko) Mac 계층 ue간 조정(iuc) 및 리소스 활용을 위한 시스템들, 방법들 및 디바이스들
WO2025231795A1 (fr) Réduction de surdébit de signalisation occ pour transmissions pusch configurées dynamiques et de type 2
US20250317935A1 (en) Systems, methods, and devices for ue-initiated beam indication based on ul configured grant
WO2025208607A1 (fr) Systèmes, procédés et dispositifs d&#39;adaptation de prach pour une amélioration de nes
WO2024031727A1 (fr) Systèmes, procédés et dispositifs pour une priorité de liaison latérale sans licence pour un mappage de classe d&#39;accès
US20250185078A1 (en) Systems, methods, and devices for signaling and procedure for communication to ul-only trp
WO2024031729A1 (fr) Systèmes, procédés et dispositifs pour une priorité de liaison latérale sans licence à un mappage de classe d&#39;accès
US20250150985A1 (en) Systems, methods, and devices for power sharing between control and backhaul links of a network-controlled repeater
WO2023206011A1 (fr) Systèmes, procédés et dispositifs pour une transmission de données courtes (sdt) améliorée
US20250151047A1 (en) Systems, methods, and devices for using dci to indicate scell dormancy
WO2024000171A1 (fr) Systèmes, procédés et dispositifs de gestion de mac de mtrp pour la mobilité inter-du et intra-cu d&#39;un ue
US20250379715A1 (en) Systems, methods, and devices for smart ul resource selection algorithm for tdd problematic bands
US20250343632A1 (en) Systems, methods, and devices for aggregated sidelink feedback
WO2024035580A1 (fr) Systèmes, procédés et dispositifs de partage de temps d&#39;occupation de canal sans licence de liaison latérale