WO2023014269A1 - Transmissions et surveillance de blocs de signaux de synchronisation (ssb) pour dispositifs sans fil à capacité réduite (redcap) - Google Patents

Transmissions et surveillance de blocs de signaux de synchronisation (ssb) pour dispositifs sans fil à capacité réduite (redcap) Download PDF

Info

Publication number
WO2023014269A1
WO2023014269A1 PCT/SE2022/050736 SE2022050736W WO2023014269A1 WO 2023014269 A1 WO2023014269 A1 WO 2023014269A1 SE 2022050736 W SE2022050736 W SE 2022050736W WO 2023014269 A1 WO2023014269 A1 WO 2023014269A1
Authority
WO
WIPO (PCT)
Prior art keywords
bwp
ssb
wireless device
parameter
legacy wireless
Prior art date
Application number
PCT/SE2022/050736
Other languages
English (en)
Inventor
Mohammad MOZAFFARI
Santhan THANGARASA
Muhammad Ali Kazmi
Yi-Pin Eric Wang
Anders Wallén
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2023014269A1 publication Critical patent/WO2023014269A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • H04L5/005—Allocation of pilot signals, i.e. of signals known to the receiver of common pilots, i.e. pilots destined for multiple users or terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals

Definitions

  • the present disclosure relates to wireless communications, and in particular, to transmissions and monitoring for reduced capability (RedCap)/non-legacy wireless devices.
  • RedCap reduced capability
  • the Third Generation Partnership Project (3GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems.
  • 4G Fourth Generation
  • 5G Fifth Generation
  • Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile wireless devices (WD), as well as communication between network nodes and between WDs.
  • 3GPP introduced both Narrowband Internet-of-Things (NB- loT) and LTE for Machine-Type Communications (LTE-MTC, or LTE-M) in Release 13. These technologies have been further enhanced through all releases up until and including the ongoing 3 GPP Release 17 work.
  • NR was introduced in 3GPP Release 15 and focused mainly on enhanced mobile broadband (eMBB) and cMTC.
  • eMBB enhanced mobile broadband
  • cMTC enhanced mobile broadband
  • RedCap reduced capability NR devices
  • the RedCap wireless devices are required to have one or more of lower cost, lower complexity, a longer battery life, and potentially a smaller form factor than legacy NR wireless devices. Therefore, several different complexity reduction features will be specified for RedCap wireless devices in 3GPP Rel-17. These complexity reduction features are listed in the 3GPP Rel-17 work item description (WID) for RedCap. The relevant description from the WID is as follows: Specify support for the following wireless device complexity reduction features [Radio Access Network 1 (RANI), RAN2, RAN4]:
  • the minimum number of Rx branches supported by specification for a RedCap wireless device is 1.
  • the specification also supports 2 Rx branches for a RedCap wireless device in these bands.
  • the minimum number of Rx branches supported by specification for a RedCap wireless device is 1.
  • the specification also supports 2 Rx branches for a RedCap wireless device in these bands.
  • a means may be specified by which the network node can know the number of Rx branches of the wireless device.
  • the first step in initial access is that a wireless device detects the DL synchronization reference signals, including primary synchronization signal (PSS) and secondary synchronization signal (SSS). Following that, the wireless device reads the physical broadcast channel (PBCH) which includes master information block (MIB). Among other information, MIB contains PDCCH-ConfigSIB 1 , which is the configuration of CORESET#0. After decoding CORESET#0 which is the DL assignment for the remaining system information, the wireless device can receive the SIB 1 including the random access channel (RACH) configuration.
  • PBCH physical broadcast channel
  • MIB master information block
  • RACH random access channel
  • Random access is the procedure of wireless device accessing a cell, receiving a unique identification by the cell and receiving the basic radio resource configurations.
  • the steps of four-step random access i.e., 4 step random access procedure) are as follows:
  • the wireless device transmits a preamble referred to as Physical random access channel (PRACH);
  • PRACH Physical random access channel
  • RAR random access response
  • the wireless device sends a physical uplink shared channel, PUSCH message
  • the network node sends the contention resolution message - Message 4
  • a wireless device aims at acquiring time and frequency synchronization with a cell and to detect physical layer cell ID (PCI) of the cell.
  • the synchronization signal block (SS block or SSB) consists of primary and secondary synchronization signals (PSS and SSS) and physical broadcast channel (PBCH).
  • PSS and SSS primary and secondary synchronization signals
  • PBCH physical broadcast channel
  • the wireless device first aims at detecting PSS and then SSS. Time and frequency synchronization as well as cell ID detection are performed using PSS and SSS. Proper detection of PSS and SSS may be a required step for PBCH demodulation.
  • PBCH carries basic system information such as master information block (MIB) and determines essential parameters for initial access of the cell including the downlink system bandwidth and the system frame number.
  • MIB master information block
  • SSB periodicity can be ⁇ 5, 10, 20, 40, 80, 160 ⁇ ms, configured via radio resource control (RRC) parameters. However, a default periodicity of 20 ms is assumed during initial cell search.
  • RRC radio resource control
  • NR supports SS burst set which consists of multiple SS blocks confined within a 5 ms window. Depending on the carrier frequency, up to 64 SS blocks can be transmitted within a SS burst set. In frequency domain, one SSB block occupies 20 contiguous resource blocks which is equivalent to 240 subcarriers. In time domain, one SSB block spans over 4 OFDM symbols (as illustrated in the example of FIG. 1).
  • the wireless device performs measurements on one or more DL and/or UL reference signal (RS) of one or more cells in different wireless device activity states, e.g., RRC idle state, RRC inactive state, RRC connected state, etc.
  • the measured cell may belong to or operate on the same carrier frequency as of the serving cell (e.g., intra-frequency carrier) or it may belong to or operate on different carrier frequency as of the serving cell (e.g., non-serving carrier frequency).
  • the non-serving carrier may be called as inter-frequency carrier if the serving and measured cells belong to the same radio access technology (RAT) but different carriers.
  • the non-serving carrier may be called as inter-RAT carrier if the serving and measured cells belong to different RATs.
  • downlink RS examples are signals in SSB, CSI-RS, CRS, DMRS, PSS, SSS, signals in SS/PBCH block (SSB), discovery reference signal (DRS), PRS etc.
  • uplink RS examples are signals in SRS, DMRS etc.
  • Each SSB carries NR-PSS, NR-SSS and NR-PBCH in 4 successive symbols.
  • One or multiple SSBs are transmit in one SSB burst which is repeated with certain periodicity, e.g., 5 ms, 10 ms, 20 ms, 40 ms, 80 ms and 160 ms.
  • the wireless device is configured with information about SSB on cells of certain carrier frequency by one or more SS/PBCH block measurement timing configuration (SMTC) configurations.
  • the SMTC configuration includes parameters such as SMTC periodicity, SMTC occasion length in time or duration, SMTC time offset with respect to reference time (e.g., serving cell’s SFN), etc. Therefore, SMTC occasion may also occur with certain periodicity e.g. 5 ms, 10 ms, 20 ms, 40 ms, 80 ms and 160 ms.
  • measurements are cell identification (e.g., PCI acquisition, PSS/SSS detection, cell detection, cell search, etc), Reference Symbol Received Power (RSRP), Reference Symbol Received Quality (RSRQ), secondary synchronization RSRP (SS-RSRP), SS-RSRQ, SINR, RS-SINR, SS-SINR, CSI- RSRP, CSI-RSRQ, received signal strength indicator (RSSI), acquisition of system information (SI), cell global ID (CGI) acquisition, Reference Signal Time Difference (RSTD), UE RX-TX time difference measurement, Radio Link Monitoring (RLM), which consists of Out of Synchronization (out of sync) detection and In Synchronization (in-sync) detection, etc.
  • RSRP Reference Symbol Received Power
  • RSRQ Reference Symbol Received Quality
  • SS-RSRP secondary synchronization RSRP
  • SINR RS-SINR
  • CSI- RSRP CSI-RSRP
  • the wireless device is typically configured by the network node (e.g., via RRC message) with measurement configuration and measurement reporting configuration, e.g., measurement gap pattern, carrier frequency information, types of measurements (e.g., RSRP etc), higher layer filtering coefficient, time to trigger report, reporting mechanism (e.g., periodic, event triggered reporting, event triggered periodic reporting, etc.) etc.
  • measurement configuration and measurement reporting configuration e.g., measurement gap pattern, carrier frequency information, types of measurements (e.g., RSRP etc), higher layer filtering coefficient, time to trigger report, reporting mechanism (e.g., periodic, event triggered reporting, event triggered periodic reporting, etc.) etc.
  • the measurements are performed for various purposes. Some example measurement purposes are: wireless device mobility (e.g., cell change, cell selection, cell reselection, handover, RRC connection re-establishment etc), wireless device positioning or location determination self-organizing network (SON), minimization of drive tests (MDT), operation and maintenance (O&M), network planning and optimization, etc.
  • wireless device mobility e.g., cell change, cell selection, cell reselection, handover, RRC connection re-establishment etc
  • SON wireless device positioning or location determination self-organizing network
  • MDT minimization of drive tests
  • O&M operation and maintenance
  • Initial BWP is used at least during the initial access.
  • the first initial downlink (DL) BWP configured in MIB is CORESET #0 (which is known as MIB-configured initial DL BWP).
  • CORESET #0 which is known as MIB-configured initial DL BWP.
  • a wireless device can have the configuration of a SIB -configured initial DL BWP.
  • the BWP configuration (IE initialDownlinkBWP) provides information about the bandwidth and location of the initial DL BWP, subcarrier spacing, and cell-specific PDCCH and PDSCH parameters of the BWP.
  • an initial DL BWP for RedCap wireless devices (which is not expected to exceed the maximum RedCap wireless device bandwidth) can be optionally configured/defined separately from the initial DL BWP for non- RedCap wireless devices at least after initial access o
  • FFS For Further Study
  • the configuration for a separately configured initial DL BWP for RedCap wireless devices is signalled in SIB.
  • ⁇ whether to support that separate initial DL BWP for RedCap wireless devices can include a configuration of CORESET and CSS(s)
  • this separate initial DL BWP for RedCap wireless devices can be used at least after initial access (i.e., at least after RRC Setup, RRC Resume, or RRC Reestablishment).
  • o FFS during the initial access o FFS: whether a separately configured initial DL BWP for RedCap wireless devices needs to contain the entire CORESET #0, and, if not, the Redcap wireless device behaviour for CORESET #0 monitoring o FFS: supported bandwidths in the separate initial DL BWP o FFS: whether additional SSB is transmitted in the separately configured initial DL BWP for RedCap wireless devices o FFS: FDD case
  • one of the open issues is to determine whether an additional SSB is transmitted in a separately configured initial DL BWP for RedCap wireless devices.
  • the wireless device can be configured DRX cycle to use in all RRC states (e.g., RRC idle state, RRC inactive state and RRC connected state) to save wireless device battery power.
  • RRC states e.g., RRC idle state, RRC inactive state and RRC connected state
  • Examples of lengths of DRX cycles currently used in RRC idle/inactive state are 320 ms, 640 ms, 1.28 s and 2.56 s.
  • Examples of lengths of DRX cycles currently used in RRC connected state may range from 2 ms to 2.56 s.
  • the DRX cycle is configured by the network node and may be defined by one or more of the following parameters:
  • OnDurationTimer a timer that is configured by the network node, is running. This timer specifies the number of consecutive control channel subframes (e.g., PDCCH slots) at the beginning of a DRX Cycle. It is also interchangeably called as DRX ON period. It is the duration (e.g., in number of downlink subframes) during which the wireless device after waking up from DRX may receive control channel (e.g., PDCCH, wake up signal, etc). If the wireless device successfully decodes the control channel (e.g., PDCCH) during the on duration then the wireless device starts a drx-inactivity timer as illustrated in the example of FIG. 2 and stays awake until its expiry.
  • control channel e.g., PDCCH
  • - drx-inactivity timer It specifies the number of consecutive control channel (e.g., PDCCH,) subframe(s) after the subframe in which a control channel (e.g., PDCCH) indicates an initial UL or DL user data transmission for this MAC entity. It is also configured by the network node.
  • PDCCH control channel
  • This time is the duration during which the wireless device monitors the control channel (e.g., PDCCH, wake up signals, etc). In other words, this is the total duration during which the wireless device is awake. This includes the “on- duration” of the DRX cycle, the time during which the wireless device is performing continuous reception while the inactivity timer has not expired and the time the wireless device is performing continuous reception while waiting for a DL retransmission after one HARQ RTT.
  • the duration over which the drx-inactivity timer is running is called as DRX active time, i.e., no DRX is used by the wireless device.
  • DRX inactive time The time during the DRX cycle other than the active time is called as DRX inactive time, i.e., DRX is used by the wireless device.
  • the DRX active time and DRX inactive time are also called as DRX ON and DRX OFF durations of the DRX cycle respectively are shown in FIG. 2.
  • the DRX inactive time may also be called as non-DRX or non-DRX period.
  • the DRX operation with more detailed parameters is illustrated in the example of FIG. 3.
  • DRX configuration herein may also be an enhanced or extended DRX (eDRX) configuration.
  • the wireless device can be configured with DRX cycle length of up to 2.56 seconds.
  • wireless devices supporting extended DRX eDRX
  • the eDRX configuration parameters include an eDRX cycle length, paging window length aka paging time window (PTW) length, etc.
  • PTW paging time window
  • the wireless device is further configured with one or more legacy DRX cycles.
  • DRX inactive may comprise OFF duration (as shown in FIG. 1) as well as time period outside the PTW, e.g., time periods between successive PTWs.
  • RedCap and non-RedCap wireless devices One consideration in coexistence of RedCap and non-RedCap wireless devices is PUSCH resource fragmentation due to PUCCH transmissions which are not scheduled on the carrier edges. More specifically, configuring a separate initial UL BWP for RedCap which occupies a portion of an available carrier bandwidth will fragment the bandwidth and prevents non-RedCap wireless devices from utilizing the entire available carrier. Such PUSCH resource fragmentation results in a significant UL peak data rate reduction for non-RedCap wireless devices that require contiguous frequency allocation in the uplink. For example, FIG. 4 shows the fragmentation of non-RedCap PUSCH resources into three parts. To minimize the PUSCH resource fragmentation, the initial UL BWP for RedCap wireless devices can be placed at one edge of non-RedCap initial UL BWP.
  • both initial UL and DL BWPs for RedCap wireless device may be placed at one edge of the carrier to minimize the PUSCH resource fragmentation. Due to such restriction on the location of the initial DL BWP, it may not contain the reference signals (such as SSB) which are needed for the wireless device to perform essential RRM measurements as the time- and/or frequency tracking may be needed to be able to perform downlink reception.
  • FIG. 5 is an example of initial UL/DL BWPs configuration for RedCap and non-RedCap wireless devices in TDD where the SBB is not positioned with the initial DL BWP for RedCap.
  • Some embodiments advantageously provide methods, systems, and apparatuses for transmissions and monitoring for reduced capability wireless devices.
  • One or more embodiments define efficient rules for transmitting and monitoring SSB for supporting reduced bandwidth wireless devices (e.g., RedCap wireless devices) in coexistence with regular wireless devices (i.e., legacy or non- RedCap wireless devices).
  • One or more rules specify conditions under which: 1) the wireless device can perform RF retuning to monitor SSB located outside its DL BWP (e.g., a SIB -configured initial DL BWP or an RRC-configured DL BWP for RedCap), and 2) the network node may transmit additional SSBs in the DL BWP which does not contain an SSB.
  • One or more rules rely on the relationship between SMTC (or SSB monitoring periodicity) and the DRX cycle.
  • FIG. 1 is a diagram of a SSB time-frequency structure
  • FIG. 2 is a diagram of a DRX cycle illustrating on and off durations
  • FIG. 3 is a diagram of DRX cycle operation illustrating different DRX related parameters
  • FIG. 4 is a diagram of a PUSCH resource fragmentation dur to PUCCH transmissions
  • FIG. 5 is a diagram of an example of initial UL/DL BWPs configuration for RedCap and non-RedCap wireless devices in TDD;
  • FIG. 6 is a schematic diagram of an example network architecture illustrating a communication system connected via an intermediate network to a host computer according to the principles in the present disclosure
  • FIG. 7 is a block diagram of a host computer communicating via a network node with a wireless device over an at least partially wireless connection according to some embodiments of the present disclosure
  • FIG. 8 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for executing a client application at a wireless device according to some embodiments of the present disclosure
  • FIG. 9 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a wireless device according to some embodiments of the present disclosure
  • FIG. 10 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data from the wireless device at a host computer according to some embodiments of the present disclosure
  • FIG. 11 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a host computer according to some embodiments of the present disclosure
  • FIG. 12 is a flowchart of an example process in a network node according to some embodiments of the present disclosure.
  • FIG. 13 is a flowchart of another example process in a network node according to some embodiments of the present disclosure.
  • FIG. 14 is a flowchart of an example process in a wireless device according to some embodiments of the present disclosure.
  • FIG. 15 is a flowchart of another example process in a wireless device according to some embodiments of the present disclosure.
  • FIG. 16 is a diagram of an example legacy SSB and RedCap initial DL BWP positions.
  • relational terms such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements.
  • the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein.
  • the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise.
  • the joining term, “in communication with” and the like may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example.
  • electrical or data communication may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example.
  • Coupled may be used herein to indicate a connection, although not necessarily directly, and may include wired and/or wireless connections.
  • network node can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi -standard radio (MSR) radio node such as MSR BS, multi-cell/multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system
  • BS base station
  • wireless device or a user equipment (UE) are used interchangeably.
  • the WD herein can be any type of wireless device capable of communicating with a network node or another WD over radio signals, such as wireless device (WD).
  • the WD may also be a radio communication device, target device, device to device (D2D) WD, machine type WD or WD capable of machine to machine communication (M2M), low-cost and/or low-complexity WD, a sensor equipped with WD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, Reduced Capability (RedCap) wireless device (also referred to as non-legacy wireless device), non- RedCap wireless device (also referred to as legacy), or a Narrowband loT (NB-IOT) device, etc.
  • D2D device to device
  • M2M machine to machine communication
  • M2M machine to machine communication
  • mobile terminals smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, Reduce
  • radio network node can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell/multicast Coordination Entity (MCE), IAB node, relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).
  • RNC evolved Node B
  • MCE Multi-cell/multicast Coordination Entity
  • IAB node IAB node
  • relay node access point
  • radio access point radio access point
  • RRU Remote Radio Unit
  • RRH Remote Radio Head
  • WCDMA Wide Band Code Division Multiple Access
  • WiMax Worldwide Interoperability for Microwave Access
  • UMB Ultra Mobile Broadband
  • GSM Global System for Mobile Communications
  • Transmitting in downlink may pertain to transmission from the network or network node to the wireless device.
  • Transmitting in uplink may pertain to transmission from the wireless device to the network or network node.
  • Transmitting in sidelink may pertain to (direct) transmission from one wireless device to another.
  • Uplink, downlink and sidelink (e.g., sidelink transmission and reception) may be considered communication directions.
  • uplink and downlink may also be used to described wireless communication between network nodes, e.g. for wireless backhaul and/or relay communication and/or (wireless) network communication for example between base stations or similar network nodes, in particular communication terminating at such. It may be considered that backhaul and/or relay communication and/or network communication is implemented as a form of sidelink or uplink communication or similar thereto.
  • the general description elements in the form of “one of A and B” corresponds to A or B. In some embodiments, at least one of A and B corresponds to A, B or AB, or to one or more of A and B. In some embodiments, at least one of A, B and C corresponds to one or more of A, B and C, and/or A, B, C or a combination thereof.
  • functions described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and/or network nodes.
  • the functions of the network node and wireless device described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.
  • Some embodiments provide transmissions and monitoring for reduced capability wireless devices.
  • FIG. 6 a schematic diagram of a communication system 10, according to an embodiment, such as a 3 GPP -type cellular network that may support standards such as LTE and/or NR (5G), which comprises an access network 12, such as a radio access network, and a core network 14.
  • the access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18).
  • Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20.
  • a first wireless device (WD) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a.
  • a second WD 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of WDs 22a, 22b (collectively referred to as wireless devices 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole WD is in the coverage area or where a sole WD is connecting to the corresponding network node 16. Note that although only two WDs 22 and three network nodes 16 are shown for convenience, the communication system may include many more WDs 22 and network nodes 16.
  • a WD 22 can be in simultaneous communication and/or configured to separately communicate with more than one network node 16 and more than one type of network node 16.
  • a WD 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR.
  • WD 22 can be in communication with an eNB for LTE/E-UTRAN and a gNB for NR/NG-RAN.
  • the communication system 10 may itself be connected to a host computer 24, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm.
  • the host computer 24 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider.
  • the connections 26, 28 between the communication system 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24 or may extend via an optional intermediate network 30.
  • the intermediate network 30 may be one of, or a combination of more than one of, a public, private or hosted network.
  • the intermediate network 30, if any, may be a backbone network or the Internet.
  • the intermediate network 30 may comprise two or more sub-networks (not shown).
  • the communication system of FIG. 6 as a whole enables connectivity between one of the connected WDs 22a, 22b and the host computer 24.
  • the connectivity may be described as an over-the-top (OTT) connection.
  • the host computer 24 and the connected WDs 22a, 22b are configured to communicate data and/or signaling via the OTT connection, using the access network 12, the core network 14, any intermediate network 30 and possible further infrastructure (not shown) as intermediaries.
  • the OTT connection may be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of routing of uplink and downlink communications.
  • a network node 16 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 24 to be forwarded (e.g., handed over) to a connected WD 22a. Similarly, the network node 16 need not be aware of the future routing of an outgoing uplink communication originating from the WD 22a towards the host computer 24.
  • a network node 16 is configured to include a configuration unit 32 which is configured to perform one or more network node 16 functions as described herein such as with respect to transmissions and monitoring for reduced capability wireless devices 22.
  • a wireless device 22 is configured to include a monitoring unit 34 which is configured to perform one or more wireless device 22 functions as described herein such as with respect to transmissions and monitoring for reduced capability wireless devices 22.
  • a host computer 24 comprises hardware (HW) 38 including a communication interface 40 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 10.
  • the host computer 24 further comprises processing circuitry 42, which may have storage and/or processing capabilities.
  • the processing circuitry 42 may include a processor 44 and memory 46.
  • the processing circuitry 42 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • processors and/or processor cores and/or FPGAs Field Programmable Gate Array
  • ASICs Application Specific Integrated Circuitry
  • the processor 44 may be configured to access (e.g., write to and/or read from) memory 46, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read- Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • memory 46 may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read- Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • Processing circuitry 42 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by host computer 24.
  • Processor 44 corresponds to one or more processors 44 for performing host computer 24 functions described herein.
  • the host computer 24 includes memory 46 that is configured to store data, programmatic software code and/or other information described herein.
  • the software 48 and/or the host application 50 may include instructions that, when executed by the processor 44 and/or processing circuitry 42, causes the processor 44 and/or processing circuitry 42 to perform the processes described herein with respect to host computer 24.
  • the instructions may be software associated with the host computer 24.
  • the software 48 may be executable by the processing circuitry 42.
  • the software 48 includes a host application 50.
  • the host application 50 may be operable to provide a service to a remote user, such as a WD 22 connecting via an OTT connection 52 terminating at the WD 22 and the host computer 24.
  • the host application 50 may provide user data which is transmitted using the OTT connection 52.
  • the “user data” may be data and information described herein as implementing the described functionality.
  • the host computer 24 may be configured for providing control and functionality to a service provider and may be operated by the service provider or on behalf of the service provider.
  • the processing circuitry 42 of the host computer 24 may enable the host computer 24 to observe, monitor, control, transmit to and/or receive from the network node 16 and or the wireless device 22.
  • the processing circuitry 42 of the host computer 24 may include an information unit 54 configured to enable the service provider to store, analyze, forward, receive, transmit, relay, etc., information related to transmissions and monitoring for reduced capability wireless devices 22.
  • the communication system 10 further includes a network node 16 provided in a communication system 10 and including hardware 58 enabling it to communicate with the host computer 24 and with the WD 22.
  • the hardware 58 may include a communication interface 60 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 10, as well as a radio interface 62 for setting up and maintaining at least a wireless connection 64 with a WD 22 located in a coverage area 18 served by the network node 16.
  • the radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers.
  • the communication interface 60 may be configured to facilitate a connection 66 to the host computer 24.
  • the connection 66 may be direct or it may pass through a core network 14 of the communication system 10 and/or through one or more intermediate networks 30 outside the communication system 10.
  • the hardware 58 of the network node 16 further includes processing circuitry 68.
  • the processing circuitry 68 may include a processor 70 and a memory 72.
  • the processing circuitry 68 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • FPGAs Field Programmable Gate Array
  • ASICs Application Specific Integrated Circuitry
  • the processor 70 may be configured to access (e.g., write to and/or read from) the memory 72, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • volatile and/or nonvolatile memory e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • the network node 16 further has software 74 stored internally in, for example, memory 72, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection.
  • the software 74 may be executable by the processing circuitry 68.
  • the processing circuitry 68 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by network node 16.
  • Processor 70 corresponds to one or more processors 70 for performing network node 16 functions described herein.
  • the memory 72 is configured to store data, programmatic software code and/or other information described herein.
  • the software 74 may include instructions that, when executed by the processor 70 and/or processing circuitry 68, causes the processor 70 and/or processing circuitry 68 to perform the processes described herein with respect to network node 16.
  • processing circuitry 68 of the network node 16 may include configuration unit 32 configured to perform one or more network node 16 functions described herein such as with respect to transmissions and monitoring for reduced capability wireless devices.
  • the communication system 10 further includes the WD 22 already referred to.
  • the WD 22 may have hardware 80 that may include a radio interface 82 configured to set up and maintain a wireless connection 64 with a network node 16 serving a coverage area 18 in which the WD 22 is currently located.
  • the radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers.
  • RedCap (and/or non-legacy) means a device such as a WD 22 that supports reduced or lower amount of one or more radio access capabilities compared to those supported by non-RedCap (and/or legacy) devices ,e.g., non- RedCap WDs 22.
  • a RedCap WD 22 may also not support some of the radio access capabilities supported by non-RedCap WDs 22.
  • radio access capabilities includes but are not limited to bandwidth, number of receivers, number of MIMO layers, number of carriers used in multicarrier operation (e.g. CA, dual connectivity etc.).
  • a RedCap WD 22 may support a 20 MHz BW in FR1, single receiver, single MIMO layer and no multicarrier operation.
  • non- RedCap WD 22 may support up to 100 MHz BW in FR1, at least 2 receivers, 2 or more MIMO layers and multicarrier operation.
  • the radio access capabilities are used or required or utilized by the WD 22 for performing one or more radio procedures.
  • radio procedures include but are not limited to data scheduling (e.g., in DL and/or in UL), radio link procedure (e.g., link recovery procedure, radio link monitoring, beam failure detection, candidate beam detection, etc.), measurements, cell change (e.g., handover, cell selection, cell reselection), etc.
  • the hardware 80 of the WD 22 further includes processing circuitry 84.
  • the processing circuitry 84 may include a processor 86 and memory 88.
  • the processing circuitry 84 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • the processor 86 may be configured to access (e.g., write to and/or read from) memory 88, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • memory 88 may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • the WD 22 may further comprise software 90, which is stored in, for example, memory 88 at the WD 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the WD 22.
  • the software 90 may be executable by the processing circuitry 84.
  • the software 90 may include a client application 92.
  • the client application 92 may be operable to provide a service to a human or non-human user via the WD 22, with the support of the host computer 24.
  • an executing host application 50 may communicate with the executing client application 92 via the OTT connection 52 terminating at the WD 22 and the host computer 24.
  • the client application 92 may receive request data from the host application 50 and provide user data in response to the request data.
  • the OTT connection 52 may transfer both the request data and the user data.
  • the client application 92 may interact with the user to generate the user data that it provides.
  • the processing circuitry 84 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by WD 22.
  • the processor 86 corresponds to one or more processors 86 for performing WD 22 functions described herein.
  • the WD 22 includes memory 88 that is configured to store data, programmatic software code and/or other information described herein.
  • the software 90 and/or the client application 92 may include instructions that, when executed by the processor 86 and/or processing circuitry 84, causes the processor 86 and/or processing circuitry 84 to perform the processes described herein with respect to WD 22.
  • the processing circuitry 84 of the wireless device 22 may include a monitoring unit 34 configured to perform one or more wireless device 22 functions as described herein such as with respect to monitoring in reduced capability wireless devices 22.
  • the inner workings of the network node 16, WD 22, and host computer 24 may be as shown in FIG. 7 and independently, the surrounding network topology may be that of FIG. 6.
  • the OTT connection 52 has been drawn abstractly to illustrate the communication between the host computer 24 and the wireless device 22 via the network node 16, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure may determine the routing, which it may be configured to hide from the WD 22 or from the service provider operating the host computer 24, or both. While the OTT connection 52 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).
  • the wireless connection 64 between the WD 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure.
  • One or more of the various embodiments improve the performance of OTT services provided to the WD 22 using the OTT connection 52, in which the wireless connection 64 may form the last segment. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and/or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24 or in the software 90 of the WD 22, or both.
  • sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 52 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 48, 90 may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 52 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the network node 16, and it may be unknown or imperceptible to the network node 16. Some such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary WD signaling facilitating the host computer’s 24 measurements of throughput, propagation times, latency and the like.
  • the measurements may be implemented in that the software 48, 90 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 52 while it monitors propagation times, errors, etc.
  • the host computer 24 includes processing circuitry 42 configured to provide user data and a communication interface 40 that is configured to forward the user data to a cellular network for transmission to the WD 22.
  • the cellular network also includes the network node 16 with a radio interface 62.
  • the network node 16 is configured to, and/or the network node’s 16 processing circuitry 68 is configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/supporting/ending a transmission to the WD 22, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the WD 22.
  • the host computer 24 includes processing circuitry 42 and a communication interface 40 that is configured to a communication interface 40 configured to receive user data originating from a transmission from a WD 22 to a network node 16.
  • the WD 22 is configured to, and/or comprises a radio interface 82 and/or processing circuitry 84 configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/supporting/ending a transmission to the network node 16, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the network node 16.
  • FIGS. 6 and 7 show various “units” such as configuration unit 32, and monitoring unit 34 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.
  • FIG. 8 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIGS. 6 and 7, in accordance with one embodiment.
  • the communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIG. 7.
  • the host computer 24 provides user data (Block SI 00).
  • the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50 (Block SI 02).
  • the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block SI 04).
  • the network node 16 transmits to the WD 22 the user data which was carried in the transmission that the host computer 24 initiated, in accordance with the teachings of the embodiments described throughout this disclosure (Block SI 06).
  • the WD 22 executes a client application, such as, for example, the client application 92, associated with the host application 50 executed by the host computer 24 (Block SI 08).
  • FIG. 9 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 6, in accordance with one embodiment.
  • the communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 6 and 7.
  • the host computer 24 provides user data (Block SI 10).
  • the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50.
  • the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block SI 12).
  • the transmission may pass via the network node 16, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the WD 22 receives the user data carried in the transmission (Block SI 14).
  • FIG. 10 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 6, in accordance with one embodiment.
  • the communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 6 and 7.
  • the WD 22 receives input data provided by the host computer 24 (Block SI 16).
  • the WD 22 executes the client application 92, which provides the user data in reaction to the received input data provided by the host computer 24 (Block SI 18).
  • the WD 22 provides user data (Block S120).
  • the WD provides the user data by executing a client application, such as, for example, client application 92 (Block S122).
  • client application 92 may further consider user input received from the user.
  • the WD 22 may initiate, in an optional third substep, transmission of the user data to the host computer 24 (Block S124).
  • the host computer 24 receives the user data transmitted from the WD 22, in accordance with the teachings of the embodiments described throughout this disclosure (Block S126).
  • FIG. 11 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 6, in accordance with one embodiment.
  • the communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 6 and 7.
  • the network node 16 receives user data from the WD 22 (Block S128).
  • the network node 16 initiates transmission of the received user data to the host computer 24 (Block S130).
  • the host computer 24 receives the user data carried in the transmission initiated by the network node 16 (Block SI 32).
  • FIG. 12 is a flowchart of an example process in a network node 16 for according to some embodiments of the present disclosure.
  • One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 68 (including the configuration unit 32), processor 70, radio interface 62 and/or communication interface 60.
  • Network node 16 configured to one of (Block SI 34) cause transmission of a legacy synchronization signal block, SSB, on a frequency outside of an initial bandwidth part, BWP, associated with a wireless device 22 where the wireless device 22 is retuned to monitor for the legacy SSB, and cause transmission of a first SSB for the wireless device 22 in the initial BWP, as described herein.
  • Network node 16 is configured to perform (Block SI 36) synchronization with the wireless device 22 based at least on one of the legacy SSB and first SSB, as described herein.
  • the causing of transmission of the legacy SSB is based at least on one of: a retuning range of the wireless device, whether the legacy SSB occurs during a discontinuous reception, DRX, inactive time, and at least one configuration parameter.
  • the causing of transmission of the first SSB in the initial BWP is based at least on one of: a discontinuous reception, DRX, cycle, reference signal periodicity, and frequency separation between the initial BWP and a legacy BWP.
  • the wireless device 22 is configured with reduced capabilities compared to capabilities of a legacy wireless device 22.
  • FIG. 13 is a flowchart of another example process in a network node 16 for according to some embodiments of the present disclosure.
  • One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 68 (including the configuration unit 32), processor 70, radio interface 62 and/or communication interface 60.
  • Network node 16 is configured to determine (Block S138) whether at least one rule is met, the at least one rule being associated with whether a non-legacy wireless device 22 expects one of a first synchronization signal block, SSB, in a first downlink, DL, bandwidth part, BWP, configured for the non-legacy wireless device 22, and a second SSB that is not in the first DL BWP, as described herein.
  • SSB first synchronization signal block
  • BWP bandwidth part
  • Network node 16 is configured to transmit (Block S140) one of the first SSB and second SSB based at least on the determination, as described herein.
  • Network node 16 is configured to perform (Block S142) at least one action based on the one of the first SSB and second SSB.
  • the at least one action includes at least one of performing time-frequency synchronization with the non-legacy wireless device 22 based on the one of the first SSB and second SSB, and receiving radio resource management, RRM, measurements from the non-legacy wireless device 22, the RRM measurements are based on the one of the first SSB and second SSB.
  • the second SSB is in a second DL BWP for a legacy wireless device 22.
  • the first DL BWP is a system information block, SIB, configured first DL BWP for the non-legacy wireless device 22, and the second DL BWP is a SIB configured second DL BWP for the legacy wireless device 22.
  • the transmission is performed during at least one discontinuous reception, DRX, inactive time of the non-legacy wireless device 22.
  • the at least one rule is associated with a non-legacy wireless device 22 expectation for the first DL BWP to not contain the first SSB, the at least one rule being based on at least one of at least one discontinuous reception, DRX, cycle parameter, reference signal, RS, periodicity parameter, and a predefined relationship between at least one DRX parameter and at least one RS parameter.
  • the at least one rule is associated with a non-legacy wireless device 22 expectation for the first DL BWP to not contain the first SSB and for the second DL BWP to contain the second SSB, the at least one rule being based on at least one of at least one discontinuous reception, DRX, parameter, at least one reference signal, RS, parameter, and a predefined relation between the at least one DRX parameter and the at least one RS parameter.
  • the at least one rule is associated with a non-legacy wireless device 22 expectation for the first DL BWP to contain the first SSB, the at least one rule being based on at least one of at least one discontinuous reception, DRX, parameter, at least one reference signal, RS, parameter, a predefined relation between the at least one DRX parameter and the at least one RS parameter, and a frequency separation of second SSB and the first DL BWP, the second SSB being a legacy SSB.
  • the at least one DRX parameter includes a length of the DRX cycle
  • the at least one RS parameter includes an RS periodicity and the relation between the at least one DRX parameter and the at least one RS parameter includes a relation between the at least one DRX parameter and at least one synchronization signal/physical broadcast channel block measurement timing configuration, SMTC, parameter.
  • the at least one rule is one of: preconfigured at the wireless device 22, and transmitted to the non-legacy wireless device 22 for implementation.
  • one of the first DL BWP is a first initial DL BWP and the second DL BWP is a second initial DL BWP
  • the first DL BWP is a first non-initial DL BWP
  • the second DL BWP is a second non-initial DL BWP
  • the non-legacy wireless device 22 has a first set of capabilities that is less than a second set of capabilities of a legacy wireless device 22.
  • FIG. 14 is a flowchart of an example process in a wireless device 22 (e.g., RedCap/non-legacy wireless device 22) according to some embodiments of the present disclosure.
  • One or more blocks described herein may be performed by one or more elements of wireless device 22 such as by one or more of processing circuitry 84 (including the monitoring unit 34), processor 86, radio interface 82 and/or communication interface 60.
  • Wireless device 22 is configured to one of (Block S144) retune to a frequency outside of an initial bandwidth part, BWP, to monitor for a legacy synchronization signal block, SSB, and monitor for a first SSB in the initial BWP, as described herein.
  • Wireless device 22 is configured to perform (Block S146) synchronization based at least on one of the legacy SSB and first SSB, as described herein.
  • the retuning is based at least on one of: a retuning range of the wireless device 22, whether the legacy SSB occurs during a discontinuous reception, DRX, inactive time, and at least one configuration parameter.
  • the monitoring for the first SSB in the initial BWP is based at least on one of a discontinuous reception, DRX, cycle, reference signal periodicity, and frequency separation between the initial BWP and a legacy BWP.
  • the wireless device 22 is configured with reduced capabilities compared to capabilities of a legacy wireless device 22.
  • FIG. 15 is a flowchart of another example process in a wireless device 22 (e.g., RedCap/non-legacy wireless device 22) according to some embodiments of the present disclosure.
  • One or more blocks described herein may be performed by one or more elements of wireless device 22 such as by one or more of processing circuitry 84 (including the monitoring unit 34), processor 86, radio interface 82 and/or communication interface 60.
  • Non-legacy wireless device 22 is configured to determine (Block S148) whether at least one rule is met, the at least one rule being associated with whether to expect one of: a first synchronization signal block, SSB, in a first downlink, DL, bandwidth part, BWP, for the non-legacy wireless device 22, and a second SSB that is not in the first DL BWP, as described herein.
  • Non-legacy wireless device 22 is configured to monitor (Block SI 50) one of the first SSB and second SSB based at least on the determination, as described herein.
  • Wireless device 22 is configured to perform (Block SI 52) at least one action based on the monitored one of the first SSB and second SSB, as described herein.
  • the at least one action includes at least one of: acquiring a time-frequency synchronization from one of the first SSB and the second SSB, and perform radio resource management, RRM, measurements.
  • the second SSB is in a second DL BWP for a legacy wireless device 22.
  • the first DL BWP is a system information block, SIB, configured first DL BWP for the non-legacy wireless device 22, where the second DL BWP is a SIB configured second DL BWP for the legacy wireless device 22.
  • the monitoring is performed during at least one discontinuous reception, DRX, inactive time.
  • the at least one rule is associated with an expectation for the first DL BWP to not contain the first SSB where the at least one rule is based on at least one of: at least one discontinuous reception, DRX, cycle parameter, reference signal, RS, periodicity parameter, and a predefined relationship between at least one DRX parameter and at least one RS parameter.
  • the at least one rule is associated with an expectation for the first DL BWP to not contain the first SSB and for the second DL BWP to contain the second SSB where the at least one rule is based on at least one of at least one discontinuous reception, DRX, parameter, at least one reference signal, RS, parameter, and a predefined relation between the at least one DRX parameter and the at least one RS parameter.
  • the at least one rule is associated with an expectation for the first DL BWP to contain the first SSB where the at least one rule is based on at least one of: at least one discontinuous reception, DRX, parameter, at least one reference signal, RS, parameter, a predefined relation between the at least one DRX parameter and the at least one RS parameter and a frequency separation of second SSB and the first DL BWP, the second SSB being a legacy SSB.
  • the at least one DRX parameter includes a length of the DRX cycle
  • the at least one RS parameter includes an RS periodicity and the relation between the at least one DRX parameter and the at least one RS parameter includes a relation between the at least one DRX parameter and at least one synchronization signal/physical broadcast channel block measurement timing configuration, SMTC, parameter.
  • the processing circuitry 84 is further configured to determine to expect the first DL BWP to not contain the first SSB where the monitoring of the second SSB is based on the determination that the first DL BWP is expected to not contain the first SSB.
  • the monitoring of the second SSB includes retuning a receiver of the non-legacy wireless device to monitor for the second SSB.
  • the at least one rule is one of: preconfigured at the non-legacy wireless device 22; and received from the network node 16 for implementation by the non-legacy wireless device 22.
  • one of: the first DL BWP is a first initial DL BWP and the second DL BWP is a second initial DL BWP
  • the first DL BWP is a first noninitial DL BWP and the second DL BWP is a second non-initial DL BWP.
  • the non-legacy wireless device 22 has a first set of capabilities that is less than a second set of capabilities of a legacy wireless device 22.
  • SSB transmissions and monitoring for reduced capability wireless devices 22 e.g., RedCap/non-legacy wireless devices 22
  • details for these arrangements, functions and processes are provided as follows, and which may be implemented by the network node 16, wireless device 22 and/or host computer 24.
  • one or more network node 16 functions described below may be performed by one or more of processing circuitry 68, processor 70, configuration unit 32, etc.
  • one or more wireless device 22 functions described below may be performed by one or more of processing circuitry 84, processor 86, monitoring unit 34, etc.
  • Some embodiments provide SSB transmissions and monitoring for reduced capability wireless devices 22 (e.g., RedCap/non-legacy wireless devices 22).
  • RedCap wireless devices 22 and non-RedCap wireless devices 22 are considered.
  • the RedCap wireless device 22 can be configured with a separate SIB-configured initial DL BWP which can be used at least for random access, paging, and SIB transmissions. Depending on the location of the initial DL BWP, it may not contain SSB intended for non-RedCap wireless devices 22. In this case, for enabling the RedCap wireless device 22 to monitor SSB there are two options:
  • Option 1 RedCap wireless devices 22 retune to another frequency location to monitor the existing transmitted SSBs
  • Option 2 The network node 16 transmits additional SSBs within the RedCap SIB-configured initial DL BWP, thus the wireless device 22 does not require the RF retuning.
  • Wireless device 22 may need to monitor SSB for various purposes including the time-frequency synchronization and RRM measurements.
  • the time-frequency synchronization may further comprise or impact wireless device 22 initial transmission timing accuracy.
  • the wireless device 22 derives its initial transmit timing (e.g., to send PRACH, any transmission after DRX, etc.) by monitoring the DL timing of a reference cell, e.g., serving cell.
  • the DL timing is determined by the wireless device 22 based on a reference signal, e.g. SSB.
  • the initial transmit timing may be accurate with respect to the receive timing of the reference cell within the wireless device initial transmit error (Te).
  • Te wireless device initial transmit error
  • the wireless device 22 may be required to monitor SSB at least once every TO period.
  • T0 160 ms.
  • the wireless device 22 in order to acquire an SSB when it is not in the SIB -configured initial DL BWP, the wireless device 22 (e.g., RedCap wireless device 22) can perform retuning of its receiver.
  • the term retuning may also be interchangeably called as tuning, RF tuning, RF switching, frequency tuning, oscillator tuning, oscillator switching, etc.
  • the retuning procedure enables the UE to change the frequency of its radio front end e.g. transceiver, which may comprise a receiver and/or transmitter.
  • the tuning is typically realized by changing the center frequency of its local oscillator (LO) and/or the bandwidth.
  • the wireless device can tune its RF front end (e.g., transceiver - receiver and/or transmitter) in any part of the cell bandwidth.
  • the wireless device 22 may not be able to operate signals.
  • the operating of signals may include transmitting signals and/or receiving signals. Therefore, the wireless device 22 interrupts serving cell operation during the retuning.
  • the wireless device 22 power consumption may also increase if the wireless device 22 has to frequently retune and monitor reference signals (e.g., SSB) in another part of the BW.
  • SSB monitoring can be performed during DRX inactive times to avoid any interruption during DRX ON periods, as long as the wireless device 22 power consumption is not a limiting factor.
  • X [MHz] be the frequency separation of a transmitted legacy SSB and the RedCap DL BWP (as shown in FIG. 16). That is, the minimum RF retuning range needed for the wireless device 22 to monitor the SSB is X [MHz],
  • the wireless device 22 is expected to acquire timefrequency sync from legacy SSB (initial BWP) only during DRX inactive time. This can be realized by a rule, which can be pre-defined or configured by the network node 16. The rule may also be defined as a wireless device 22 requirement. Examples of rules are:
  • the wireless device 22 is expected to acquire the time-frequency sync from the legacy reference signal (e.g., SSB in initial BWP) during DRX inactive time. If the RedCap initial DL BWP does not contain reference cell (e.g., SSB) then wireless device 22 is expected to acquire the time-frequency sync from the legacy reference signal (e.g. SSB in initial BWP) without causing any interruption during the DRX active time.
  • the legacy reference signal e.g., SSB in initial BWP
  • RedCap initial DL BWP does not contain reference cell (e.g. SSB) then wireless device 22 is expected to acquire the time-frequency sync from the legacy from the legacy reference signal (e.g., SSB in initial BWP) without causing any interruption to one or more serving cell signals.
  • a list of the serving cell signals which should not be interrupted may be pre-defined or configured by the network node 16. Examples of serving cell signals are control channel, paging messages, system information (e.g. MIB, SIB, etc.).
  • whether additional SSB(s) are transmitted in the SIB- configured RedCap BWP depends on one or more of the following configuration parameters:
  • - DRX cycle e.g., legacy DRX and/or eDRX
  • RS Reference signal
  • rule This can be realized by a rule, which can be pre-defined or configured by the network node 16.
  • the rule may also be defined as a wireless device 22 requirement. Examples of rules are:
  • RedCap initial DL BWP does not contain reference cell (e.g., SSB)
  • whether the wireless device 22 is expected to acquire the time-frequency sync from the legacy reference signal depends on one or more of the following configuration parameters: the length of DRX cycle, RS periodicity (e.g., SMTC/SSB periodicity) and relation between DRX (e.g., DRX cycle length) and SMTC parameters (e.g., SMTC/SSB periodicity).
  • the wireless device 22 acquires the time-frequency sync from the legacy reference signal (e.g., SSB in initial BWP) then it will acquire it only during DRX inactive time. o Depending on the above one or more configuration parameters, if the wireless device 22 acquires the time-frequency sync from the legacy reference signal (e.g., SSB in initial BWP) then it will acquire it without causing any interruption during the DRX active time.
  • the legacy reference signal e.g., SSB in initial BWP
  • the wireless device 22 may acquire it without causing any interruption one or more serving cell signals, e.g., paging, SI, etc.
  • whether the RS needed for time-frequency sync (e.g., SSB) transmitted by the network node 16 in the RedCap BWP depends on one or more of the following conditions:
  • RS periodicity e.g., SSB/SMTC window periodicity
  • T2 a threshold
  • the frequency separation between the RedCap BWP and the legacy BWP e.g. initial BWP.
  • the above relations may be pre-defined or configured by the network node 16.
  • the relation may be expressed in terms of a mapping table mapping a parameter (e.g., DRX cycle length) and threshold value, e.g., Tl. Examples of relations are greater than, less than, equal, less than or equal, greater than or equal, etc.
  • the additional RS needed for time-frequency sync (e.g., SSB(s)) are always transmitted by the network node 16 in the RedCap BWP; otherwise the additional RS (e.g., SSB(s)) are not transmitted in the RedCap BWP.
  • the additional RS needed for time-frequency sync (e.g., SSB(s)) are always transmitted by the network node 16 in the RedCap BWP under one or more of the following conditions:
  • the additional RS e.g., SSB(s)
  • additional RS e.g., SSB(s)
  • the values of the parameters Tl, T2, T3 and T4 may further depend on one or more of the following configuration or procedure, for example:
  • RRC state e.g., idle state, inactive state, connected state, etc.
  • one set of Tl, T2, T3 and T4 can be defined for idle/inactive state and another set of Tl, T2, T3 and T4 can be defined for connected state.
  • the wireless device 22 is also configured with eDRX cycle.
  • one set of Tl, T2, T3 and T4 can be defined for wireless device 22 configured with eDRX and another set of Tl, T2, T3 and T4 can be defined for wireless device 22 not configured with eDRX.
  • the values of the parameters Tl, T2, T3 and T4 may further depend on the length of eDRX when the wireless device 22 is configured with eDRX.
  • one set of Tl, T2, T3 and T4 can be defined for wireless device 22 configured with eDRX cycle longer than certain threshold (Ht) and another set of Tl, T2, T3 and T4 for wireless device 22 configured with eDRX less than or equal to Ht.
  • Ht certain threshold
  • the values of the parameters Tl, T2, T3 and T4 may further depend on the frequency range (FR) of the cell where redcap BWP is configured.
  • FR frequency range
  • one set of Tl, T2, T3 and T4 can be defined for FR1 and another set of Tl, T2, T3 and T4 for FR2.
  • Examples of frequencies in FR1 are between 410 MHz to 7125 MHz, and frequencies in FR2 are between 24 GHz to 71 GHz.
  • the values of the parameters Tl, T2, T3 and T4 may further depend on the bandwidth (BWc) of the cell where redcap BWP is configured.
  • BWc bandwidth of the cell where redcap BWP is configured.
  • one set of Tl, T2, T3 and T4 can be defined for BWc below threshold and another set of Tl, T2, T3 and T4 for BWc equal to or above the threshold.
  • the values of the parameters Tl, T2, T3 and T4 may further depend on the frequency separation (X) of the DL BWP and the legacy SSB in a cell where redcap BWP is configured.
  • X frequency separation
  • one set of Tl, T2, T3 and T4 can be defined for X below threshold and another set of Tl, T2, T3 and T4 for X equal to or above the threshold.
  • This method can be realized by a rule, which can be pre-defined or configured by the network node 16.
  • the rule may also be defined as a wireless device 22 requirement. Examples of rules are:
  • the wireless device 22 assumes that the RedCap initial DL BWP contains reference cell (e.g., SSB); otherwise the wireless device 22 assumes that RedCap initial DL BWP does not contain reference cell (e.g., SSB). If the RedCap initial DL BWP does not contain reference cell (e.g., SSB) then the wireless device 22 is expected to acquire time-frequency sync from the legacy reference signal (e.g., SSB in initial BWP) while meeting one or more of the following conditions: o Wireless device 22 may acquire it only during DRX inactive time. o Wireless device 22 may acquire it without causing any interruption during the DRX active time. o Wireless device 22 may acquire it without causing any interruption one or more serving cell signals, e.g., paging, SI, etc.
  • the legacy reference signal e.g., SSB in initial BWP
  • the wireless device 22 assumes that the RedCap initial DL BWP contains reference cell (e.g., SSB); otherwise the wireless device 22 assumes that RedCap initial DL BWP does not contain reference cell (e.g., SSB). If the RedCap initial DL BWP does not contain reference cell (e.g., SSB) then the wireless device 22 is expected to acquire time-frequency sync from the legacy reference signal (e.g., SSB in initial BWP) while meeting one or more of the following conditions: o Wireless device 22 may acquire it only during DRX inactive time. o Wireless device 22 may acquire it without causing any interruption during the DRX active time. o Wireless device 22 may acquire it without causing any interruption one or more serving cell signals, e.g., paging, SI, etc.
  • the legacy reference signal e.g., SSB in initial BWP
  • the wireless device 22 assumes that the RedCap initial DL BWP contains reference cell (e.g., SSB); otherwise the wireless device 22 assumes that RedCap initial DL BWP does not contain reference cell (e.g., SSB).
  • RS periodicity e.g., SMTC periodicity
  • the wireless device 22 is expected to acquire time-frequency sync from the legacy reference signal (e.g., SSB in initial BWP) while meeting one or more of the following conditions: o Wireless device 22 may acquire it only during DRX inactive time, o Wireless device 22 may acquire it without causing any interruption during the DRX active time. o Wireless device 22 may acquire it without causing any interruption one or more serving cell signals, e.g., paging, SI, etc.
  • the legacy reference signal e.g., SSB in initial BWP
  • whether additional SSB(s) are transmitted in the SIB- configured RedCap BWP depends on the frequency separation of the DL BWP and the legacy SSB (i.e., depends on X defined in FIG. 16).
  • additional SSB(s) are always transmitted in the RedCap DL BWP if X is greater than a threshold.
  • the wireless device 22 relies on RF retunmg to acquire legacy SSB(s) if X is less than a threshold.
  • the wireless device 22 determines whether the wireless device 22 relies on RF retuning to acquire legacy SSB(s) depending on the RF retuning delay. For example, if the RF retuning delay is less than N symbols (or T seconds), the wireless device 22 performs RF retuning.
  • the aforementioned thresholds for DRX cycle, SMTC periodicity, and frequency separation X[MHz] is determined based on various factors including wireless device 22 power consumption, wireless device 22 capability, latency requirements, and wireless device 22 mobility.
  • the wireless device 22 and network node 16 rely on a method based on the combination of additional SSBs transmissions and RF retuning for acquiring legacy SSBs.
  • network node 16 can transmit additional SSBs with a periodicity Pl and the wireless device 22 can periodically (e.g., periodicity P2) perform RF retuning to acquire legacy SSBs.
  • the values of Pl and P2 can be determined based on various factors including DRX cycle, SSB/SMTC parameters, wireless device 22 power consumption, wireless device 22 capability, RF retuning delay, retuning frequency range, latency requirements, and wireless device 22 mobility.
  • the aforementioned periodicities and thresholds can be fixed or time varying (e.g., dynamically changes) depending on the scenario and system parameters.
  • SIB -configured DL BWP has been used for RedCap wireless devices 22 to describe one or more embodiments, the embodiments can be applied to RRC-configured DL BWP for RedCap wireless devices 22.
  • one or more embodiments described herein define rules for transmitting and monitoring SSBs for supporting reduced bandwidth wireless devices 22 (e.g., RedCap wireless devices 22) in coexistence with regular wireless devices 22 (i.e., legacy or non-RedCap wireless devices 22) based on the SMTC (or SSB monitoring periodicity) and the DRX cycle.
  • reduced bandwidth wireless devices 22 e.g., RedCap wireless devices 22
  • regular wireless devices 22 i.e., legacy or non-RedCap wireless devices 22
  • RedCap wireless device 22 may have one set of capabilities that are less than a second set of capabilities of a non-RedCap wireless device 22.
  • the solutions capture the tradeoffs between wireless device power consumption and RRM measurement and time-frequency synchronization via SSB monitoring and network energy/spectral efficiency.
  • the solutions can be beneficial for efficient SSB monitoring and SSB transmission considering: 1) network energy efficiency, spectral efficiency, resource utilization, and inter-cell interference, and 2) wireless device complexity, power consumption, and RRM measurements, and time-frequency synchronization.
  • a network node 16 configured to communicate with a wireless device 22 (WD 22), the network node 16 configured to, and/or comprising a radio interface 82 and/or comprising processing circuitry 84 configured to: one of: cause transmission of a legacy synchronization signal block, SSB, on a frequency outside of an initial bandwidth part, BWP, associated with a wireless device 22, the wireless device 22 being retuned to monitor for the legacy SSB; and cause transmission of a first SSB for the wireless device in the initial BWP; and perform synchronization with the wireless device 22 based at least on one of the legacy SSB and first SSB.
  • SSB legacy synchronization signal block
  • BWP initial bandwidth part
  • Example A2 The network node 16 of Example Al, wherein the cause of transmission of the legacy SSB is based at least on one of: a retuning range of the wireless device 22; whether the legacy SSB occurs during a discontinuous reception, DRX, inactive time; and at least one configuration parameter.
  • Example A3 The network node 16 of Example Al, wherein the causing of transmission of the first SSB in the initial BWP is based at least on one of: a discontinuous reception, DRX, cycle; reference signal periodicity; and frequency separation between the initial BWP and a legacy BWP.
  • Example A4 The network node 16 of Example Al, wherein the wireless device 22 is configured with reduced capabilities compared to capabilities of a legacy wireless device 22.
  • Example Bl A method implemented in a network node 16 that is configured to communicate with a wireless device 22, the method comprising: one of: causing transmission of a legacy synchronization signal block, SSB, on a frequency outside of an initial bandwidth part, BWP, associated with a wireless device 22, the wireless device 22 being retuned to monitor for the legacy SSB; and causing transmission of a first SSB for the wireless device 22 in the initial BWP; and performing synchronization with the wireless device 22 based at least on one of the legacy SSB and first SSB.
  • SSB legacy synchronization signal block
  • BWP initial bandwidth part
  • Example B2 The method of Example Bl, wherein the cause of transmission of the legacy SSB is based at least on one of: a retuning range of the wireless device 22; whether the legacy SSB occurs during a discontinuous reception, DRX, inactive time; and at least one configuration parameter.
  • Example B3 The method of Example Bl, wherein the causing of transmission of the first SSB in the initial BWP is based at least on one of: a discontinuous reception, DRX, cycle; reference signal periodicity; and frequency separation between the initial BWP and a legacy BWP.
  • Example B4 The method of Example Bl, wherein the wireless device 22 is configured with reduced capabilities compared to capabilities of a legacy wireless device 22.
  • a wireless device 22 configured to communicate with a network node 16, the WD 22 configured to, and/or comprising a radio interface 82 and/or processing circuitry 84 configured to: one of: retune to a frequency outside of an initial bandwidth part, BWP, to monitor for a legacy synchronization signal block, SSB; and monitor for a first SSB in the initial BWP; and perform synchronization based at least on one of the legacy SSB and first SSB.
  • BWP initial bandwidth part
  • SSB legacy synchronization signal block
  • SSB legacy synchronization signal block
  • Example C2 The WD 22 of Example Cl, wherein the retuning is based at least on one of: a retuning range of the wireless device 22; whether the legacy SSB occurs during a discontinuous reception, DRX, inactive time; and at least one configuration parameter;
  • Example C3 The WD 22 of Example Cl, wherein the monitoring for the first SSB in the initial BWP is based at least on one of: a discontinuous reception, DRX, cycle; reference signal periodicity; and frequency separation between the initial BWP and a legacy BWP.
  • Example C4 The wireless device 22 of Example Cl, wherein the wireless device 22 is configured with reduced capabilities compared to capabilities of a legacy wireless device 22.
  • Example DI A method implemented in a wireless device 22 (WD 22), the method comprising: one of: retuning to a frequency outside of an initial bandwidth part, BWP, to monitor for a legacy synchronization signal block, SSB; and monitoring for a first SSB in the initial BWP; and perform synchronization based at least on one of the legacy SSB and first SSB.
  • Example D2 The method of Example DI, wherein the retuning is based at least on one of: a retuning range of the wireless device 22; whether the legacy SSB occurs during a discontinuous reception, DRX, inactive time; and at least one configuration parameter.
  • Example D3 The method of Example D 1 , wherein the monitoring for the first SSB in the initial BWP is based at least on one of a discontinuous reception, DRX, cycle; reference signal periodicity; and frequency separation between the initial BWP and a legacy BWP.
  • Example D4 The method of Example DI, wherein the wireless device 22 is configured with reduced capabilities compared to capabilities of a legacy wireless device 22.
  • the concepts described herein may be embodied as a method, data processing system, computer program product and/or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and/or functionality described herein may be performed by, and/or associated to, a corresponding module, which may be implemented in software and/or firmware and/or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.
  • These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.
  • the computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
  • Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++.
  • the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language.
  • the program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer.
  • the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
  • LAN local area network
  • WAN wide area network
  • Internet Service Provider for example, AT&T, MCI, Sprint, EarthLink, MSN, GTE, etc.

Landscapes

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

Abstract

Un procédé, un système et un appareil sont divulgués. Selon un ou plusieurs modes de réalisation, un dispositif sans fil non existant (22) est divulgué. Le dispositif sans fil non existant (22) comprend un circuit de traitement (84) configuré pour : déterminer si au moins une règle est satisfaite, l'au moins une règle étant associée au fait de savoir s'il faut attendre l'un d'un premier bloc de signal de synchronisation, SSB, dans une première partie de bande passante, BWP, de liaison descendante, DL pour le dispositif sans fil non existant (22) et d'un second SSB qui n'est pas dans la première BWP DL, surveiller l'un du premier SSB et du second SSB sur la base au moins de la détermination, et effectuer au moins une action sur la base d'un SSB parmi le premier SSB et le second SSB surveillés.
PCT/SE2022/050736 2021-08-06 2022-08-05 Transmissions et surveillance de blocs de signaux de synchronisation (ssb) pour dispositifs sans fil à capacité réduite (redcap) WO2023014269A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202163230610P 2021-08-06 2021-08-06
US63/230,610 2021-08-06

Publications (1)

Publication Number Publication Date
WO2023014269A1 true WO2023014269A1 (fr) 2023-02-09

Family

ID=83115564

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2022/050736 WO2023014269A1 (fr) 2021-08-06 2022-08-05 Transmissions et surveillance de blocs de signaux de synchronisation (ssb) pour dispositifs sans fil à capacité réduite (redcap)

Country Status (1)

Country Link
WO (1) WO2023014269A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021162829A1 (fr) * 2020-02-13 2021-08-19 Qualcomm Incorporated Blocs de signal de synchronisation pauvre pour dispositifs à capacité réduite

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021162829A1 (fr) * 2020-02-13 2021-08-19 Qualcomm Incorporated Blocs de signal de synchronisation pauvre pour dispositifs à capacité réduite

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
CMCC: "Discussion on principles and framework of reduced capability NR", vol. RAN WG1, no. e-Meeting; 20200817 - 20200828, 7 August 2020 (2020-08-07), XP051915259, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG1_RL1/TSGR1_102-e/Docs/R1-2006220.zip R1-2006220.docx> [retrieved on 20200807] *
LENOVO ET AL: "UE complexity reduction features for RedCap", vol. RAN WG1, no. E-meeting; 20201026 - 20201113, 16 October 2020 (2020-10-16), XP051939522, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG1_RL1/TSGR1_103-e/Docs/R1-2008294.zip R1-2008294_complexity reduction.docx> [retrieved on 20201016] *
VIVO ET AL: "Discussion on UE Complexity reduction", vol. RAN WG1, no. e-Meeting; 20210125 - 20210205, 18 January 2021 (2021-01-18), XP051970371, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG1_RL1/TSGR1_104-e/Docs/R1-2100449.zip R1-2100449_Discussion on UE Complexity reduction.docx> [retrieved on 20210118] *

Similar Documents

Publication Publication Date Title
US20210392658A1 (en) Method for reducing serving cell interruption due to prose operation
US11856430B2 (en) Methods for managing parallel measurement gap patterns for radio resource management and positioning measurements
AU2018313633B2 (en) Radio network node, wireless device and methods performed therein
WO2018143864A1 (fr) Systèmes et procédés d&#39;utilisation d&#39;informations d&#39;une cellule voisine pour effectuer des mesures
US20220345926A1 (en) Enhanced procedure for early measurement reporting
EP3857986B1 (fr) Procédés de transition d&#39;état pour des économies d&#39;énergie de dispositif sans fil
EP3777458B1 (fr) Configurations de ressources de communication pour la double connectivité
US20220345993A1 (en) Limited cell search mode for wireless devices
US20240236714A1 (en) Sidelink triggered minimization of drive test (mdt) logging
EP4039045A1 (fr) Adaptation de défaillances de cca maximales autorisées sur la base d&#39;une périodicité d&#39;occasion unique
WO2023014269A1 (fr) Transmissions et surveillance de blocs de signaux de synchronisation (ssb) pour dispositifs sans fil à capacité réduite (redcap)
US20240214142A1 (en) Beam failure detection for single-dci based multi-trp schemes
US20220116976A1 (en) Scell management for ca
EP4397084A1 (fr) Adaptation de fourniture de bloc de signal de synchronisation (ssb) pour dispositifs sans fil
WO2023131923A1 (fr) Espaces pour lecture de si dans multiples usim
WO2023014278A1 (fr) Nœud de réseau, dispositif sans fil et procédés de fonctionnement en mode edrx
WO2024025452A1 (fr) Procédé et appareil de rapport de mesure
WO2020225130A1 (fr) Configuration de déploiement de rss dans un réseau de communication sans fil

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22761298

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22761298

Country of ref document: EP

Kind code of ref document: A1