WO2023158362A1 - Informations diffusées par signalisation commune ou dédiée en mode connecté lors de l'utilisation de ncd-ssb - Google Patents

Informations diffusées par signalisation commune ou dédiée en mode connecté lors de l'utilisation de ncd-ssb Download PDF

Info

Publication number
WO2023158362A1
WO2023158362A1 PCT/SE2023/050143 SE2023050143W WO2023158362A1 WO 2023158362 A1 WO2023158362 A1 WO 2023158362A1 SE 2023050143 W SE2023050143 W SE 2023050143W WO 2023158362 A1 WO2023158362 A1 WO 2023158362A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
notification
system information
etws
cmas
Prior art date
Application number
PCT/SE2023/050143
Other languages
English (en)
Inventor
Emre YAVUZ
Tuomas TIRRONEN
Andreas HÖGLUND
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 WO2023158362A1 publication Critical patent/WO2023158362A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/90—Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H04W72/232—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the physical layer, e.g. DCI signalling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]

Definitions

  • the present disclosure relates to a cellular communications system and, more specifically, to transmission and reception of broadcasted information.
  • RedCap UE supports the following five UE complexity reduction features.
  • a RedCap UE has a reduced maximum UE bandwidth.
  • Maximum bandwidth of a Frequency Range 1 (FR1) RedCap UE during and after initial access is 20 Megahertz (MHz).
  • Maximum bandwidth of a Frequency Range 2 (FR2) RedCap UE during and after initial access is 100 MHz.
  • a RedCap UE has a reduced minimum number of receive (Rx) branches.
  • Rx receive
  • the minimum number of Rx branches supported by the specification for a RedCap UE is one (1).
  • the specification also supports two (2) Rx branches for a RedCap UE in these bands.
  • NR New Radio
  • the minimum number of Rx branches supported by the specification for a RedCap UE is one (1).
  • the specification also supports two (2) Rx branches for a RedCap UE in these bands.
  • a RedCap UE has a reduced maximum number of downlink (DL) Multiple-Input Multiple-Output (MIMO) layers.
  • MIMO Multiple-Input Multiple-Output
  • a RedCap UE has a relaxed maximum modulation order. Support of 256 Quadrature Amplitude Modulation (QAM) in DL is optional (instead of mandatory) for an FR1 RedCap UE. No other relaxations of maximum modulation order are specified for a RedCap UE.
  • QAM Quadrature Amplitude Modulation
  • a RedCap UE has a reduction in complexing in regard to duplex operations such as Frequency Division Duplex (FDD), Half Duplex FDD (HD-FDD), and Frequency Division Duplex (FDD).
  • FDD Frequency Division Duplex
  • HD-FDD Half Duplex FDD
  • FDD Frequency Division Duplex
  • a RedCap UE uses the initial DL BWP at least during the initial access.
  • the first initial DL BWP configured in Master Information Block (MIB) is Control Resource Set (CORESET) #0, which is known as MIB-configured initial DL BWP.
  • the RedCap UE can receive the configuration of initial DL BWP in System Information Block (SIB) after receiving CORESET #0.
  • SIB System Information Block
  • the BWP configuration i.e., initialDownlinkBWP Information Element (IE) provides information about the bandwidth and location of the initial DL BWP, subcarrier spacing, and cell-specific Physical Downlink Control Channel (PDCCH) and Physical Downlink Shared Channel (PDSCH) parameters of the BWP.
  • IE initialDownlinkBWP Information Element
  • a UE aims at acquiring time and frequency synchronization with a cell and detecting a physical layer cell ID (PCI) of the cell.
  • PCI physical layer cell ID
  • the SSB comprises a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS) and a Physical Broadcast Channel (PBCH).
  • PSS Primary Synchronization Signal
  • SSS Secondary Synchronization Signal
  • PBCH Physical Broadcast Channel
  • a UE During an initial cell search, a UE first aims at detecting a PSS followed by an SSS. Time and frequency synchronization as well as cell ID detection are done using the PSS and the SSS. Proper detection of the PSS and the SSS is needed for PBCH demodulation.
  • the PBCH carries basic system information such as MIB, which includes essential parameters for initial access to the cell including the downlink system bandwidth and the system frame number.
  • MIB basic system information
  • QPSK Quadrature Phase Shift Keying
  • the SSB periodicity can be ⁇ 5, 10, 20, 40, 80, 160 ⁇ milliseconds (ms), configured via Radio Resource Control (RRC) parameters. However, a default periodicity of 20 ms is assumed during initial cell search.
  • NR supports a Synchronization Signal (SS) burst set that comprises multiple SS blocks confined within a 5 ms window.
  • SS Synchronization Signal
  • up to 64 SS blocks can be transmitted within a SS burst set.
  • one SSB block occupies 20 contiguous resource blocks which is equivalent to 240 subcarriers.
  • one SSB block spans over 4 OFDM symbols, as illustrated in Figure 1.
  • SSBs can be transmitted.
  • An SSB associated with the minimum essential system information (i.e., SIB1) the UE is required to acquire for initial access in a cell is called a cell-defining SSB (CD-SSB).
  • CD-SSB cell-defining SSB
  • NCD-SSBs non cell-defining SSBs
  • a UE can detect and measure SSBs for the purpose of cell selection or reselection if the SSB is on the sync raster. If the UE detects an SSB, the MIB therein tells the UE whether it has an associated SIB 1. If it does, the UE acquires the associated SIB1 and uses the information therein, e.g., barring, cell Selectioninfo etc., to determine whether it may select or reselect the cell. Subsequently, the UE acquires the other SIBs, e.g., SIB2, 3, 4 etc., and uses the information therein to find out where to search for potential target cells for re-selection. But even if the UE detects such SSB, it may only select the SSB after reading and validating its SIB1.
  • NCD-SSBs may also be necessary to extend the cell- reselection related system information in SIB2-4, e.g., to inform the UE about a different SSB Measurement Timing Configuration (SMTC) or SSB-Positions on the NCD-SSB frequency or about different neighbor cell lists. Supporting measurements and cell (re-)selection on NCD- SSBs may turn out quite complex.
  • SMTC Measurement Timing Configuration
  • SSB-Positions on the NCD-SSB frequency or about different neighbor cell lists. Supporting measurements and cell (re-)selection on NCD- SSBs may turn out quite complex.
  • RedCap UEs perform idle and inactive mode reselection on the regular CD-SSB and the SIBs associated to the regular CB-SSB.
  • the RedCap UEs should also read paging there while in idle/inactive node.
  • the RedCap UEs could still use a “separate initial DL BWP” at the edge of the carrier, especially in Time Division Duplexing (TDD) if both uplink (UL) and DL BWPs are located at the edge.
  • TDD Time Division Duplexing
  • a NR base station configures “measurement objects” to inform a UE at which frequency position to search for SSBs.
  • the UE does not need to distinguish CD-SSBs and NCD-SSBs.
  • the current RRC signaling allows configuring SSB-based Radio Resource Management (RRM) on any (CD- or NCD-) SSB.
  • RRM Radio Resource Management
  • the UE should also include the latest measurements for its serving cells. To do so, the UE needs to know which SSB (frequency) is associated with which serving cell. To do this, each ServingCell configuration points to a corresponding measurement object and thereby also to the CD-SSB.
  • absoluteFrequencySSB (representing the center frequency of SSB) in an RRC message, is configured for each ServingCell.
  • the UE is supposed to use this CD-SSB for (SSB-based) Radio Link Management (RLM), Beam Failure Detection (BFD), in Transmission Configuration Indicator (TCI) states, for Random Access Channel (RACH) Occasion (RO) selection, and for all other purposes that require an SSB.
  • RLM Radio Link Management
  • BFD Beam Failure Detection
  • TCI Transmission Configuration Indicator
  • RACH Random Access Channel
  • RO Occasion
  • NCD-SSB frequency in the absoluteFrequencySSB ASN. l field according to the current specifications.
  • the network would have to ensure that this NCD-SSB has the same properties as the CD-SSB, e.g., same ssb-PositionsInBurst, PCI, ss-PBCH-BlockPower, etc. If it is necessary to configure a parameter, e.g., ssb- periodicityServingCell, differently for CD-SSB and NCD-SSB, additional signaling would need to be added.
  • a parameter e.g., ssb- periodicityServingCell
  • an SSB is associated with a Remaining Minimum System Information (RMSI)
  • RMSI Remaining Minimum System Information
  • a primary cell (PCell) is always associated to a CD-SSB located on the synchronization raster. If a separate initial/RRC configured DL BWP is configured to contain the entire CORESETO, a CD-SSB is expected by RedCap UE.
  • NCD-SSB which is not associated with CORESETO is mainly used for some RRM procedures e.g., performing measurements.
  • a RedCap UE For a separate initial DL BWP (if it does not include CD-SSB and the entire CORESETO), if it is configured for paging, a RedCap UE expects it (the separate initial DL BWP) to contain NCD-SSB for serving cell but not CORESET#0/SIB.
  • a RedCap UE supporting mandatory FG 6-1 (but not optional FG 6- la) expects it (the RRC-configured active DL BWP) to contain NCD- SSB for serving cell but not CORESET#0/SIB.
  • a method performed by UE configured with an active DL BWP that does not contain a CD-SSB comprises receiving, from a network node, a message on a Physical Downlink Shared Channel (PDSCH), wherein the message comprises information related to a notification for either (a) system information update or (b) Earthquake and Tsunami Warning System (ETWS) and/or Commercial Mobile Alert System (CMAS).
  • PDSCH Physical Downlink Shared Channel
  • ETWS Earthquake and Tsunami Warning System
  • CMAS Commercial Mobile Alert System
  • the method further comprises receiving, from the network node, the notification for either (a) system information update or (b) ETWS and/or CMAS, on a Physical Downlink Control Channel (PDCCH).
  • PDCH Physical Downlink Control Channel
  • the receiving the notification comprises receiving the notification via Downlink Control Information (DCI) carried on a PDCCH.
  • DCI Downlink Control Information
  • the notification is comprised in a short message field in the DCI.
  • the DCI is scrambled with a Paging Radio Network Temporary Identifier (P-RNTI).
  • P-RNTI Paging Radio Network Temporary Identifier
  • the message received on the PDSCH is scheduled by the DCI.
  • receiving the notification comprises receiving the notification via a Medium Access Control (MAC) Control Element (CE).
  • MAC Medium Access Control
  • CE Control Element
  • the message received on the PDSCH is scheduled by DCI in a PDCCH that is received by the UE after the notification.
  • the message is a dedicated message to the UE.
  • the dedicated message is a dedicated Radio Resource Control (RRC) message comprising the information related to the notification for either (a) system information update or (b) ETWS and/or CMAS.
  • RRC Radio Resource Control
  • the dedicated message is a MAC CE comprising the information related to the notification for either (a) system information update or (b) ETWS and/or CMAS.
  • the message is a common message to a group of UEs comprising the UE.
  • the information comprises information related to a system information update. In one embodiment, the information related to the system information update comprises updated system information.
  • the information comprises information related to ETWS and/or CMAS.
  • the information related to ETWS and/or CMAS comprises System Information Block 6, System Information Block 7, and/or System Information Block 8.
  • receiving the message comprises receiving the message on the active DL BWP.
  • the method further comprises performing one or more actions responsive to receiving the message on the PDSCH.
  • the one or more actions comprise presenting an alert on an associated display.
  • the method further comprises performing one or more actions responsive to the notification.
  • the one or more actions performed responsive to the notification comprise stopping a Connected mode Discontinuous Reception (C-DRX) operation to continuously monitor for a scheduling of the message.
  • C-DRX Connected mode Discontinuous Reception
  • a UE configured with an active DL BWP that does not contain a CD-SSB the UE comprises one or more transmitters, one or more receivers, and processing circuitry associated with the one or more transmitters and the one or more receivers.
  • the processing circuitry is configured to cause the UE to receive, from a network node, a message on a PDSCH, wherein the message comprises information related to a notification for either (a) system information update or (b) ETWS and/or CMAS.
  • a method performed by a network node comprises sending a message on a PDSCH to a UE configured with an active DL BWP that does not contain a Cell CD-SSB, wherein the message comprises information related to a notification for either (a) system information update or (b) ETWS and/or CMAS.
  • the method further comprises sending, to the UE, the notification for either (a) system information update or (b) ETWS and/or CMAS, on a PDCCH.
  • a network node comprises processing circuitry configured to cause the network node to send a message on a PDSCH to a UE configured with an active DL BWP that does not contain a CD- SSB, wherein the message comprises information related to a notification for either (a) system information update or (b) ETWS and/or CMAS.
  • Figure 1 illustrates the structure of a Synchronization Signal Block (SSB) in 3 rd Generation Partnership Project (3 GPP) New Radio (NR);
  • SSB Synchronization Signal Block
  • 3 GPP 3 rd Generation Partnership Project
  • NR New Radio
  • Figure 2 shows an example of a communication system in which embodiments of the present disclosure may be implemented
  • FIGS. 3 A and 3B illustrate the operation of a network node and a User Equipment (UE) in accordance with embodiments of the present disclosure
  • Figure 4 shows a UE in accordance with some embodiments.
  • Figure 5 shows a network node in accordance with some embodiments.
  • Radio Resource Control RRC
  • BWP Bandwidth Part
  • CD-SSB Cell-Defining Synchronization Signal Block
  • CORESET Control Resource Set #0
  • the active DL BWP contains either (a) a Non- Cell-Defining Synchronization Signal Block (NCD-SSB) for the serving cell or (b) no Synchronization Signal Block (SSB) but measurement gaps configured for the UE to retune to the BWP that contains an SSB.
  • NCD-SSB Non- Cell-Defining Synchronization Signal Block
  • SSB Synchronization Signal Block
  • a UE In connected mode, a UE typically monitors for Physical Downlink Control Channel (PDCCH) to receive downlink and/or uplink scheduling information for transmission in the downlink and/or uplink. It is also possible for the UE to receive (a) system information update notification or (b) indication for Earthquake and Tsunami Warning System (ETWS) and/or Commercial Mobile Alert System (CMAS), as a part(s) of the short message.
  • PDCCH Physical Downlink Control Channel
  • ETWS Earthquake and Tsunami Warning System
  • CMAS Commercial Mobile Alert System
  • SIB System Information Block
  • the UE would require a measurement gap for retuning to a BWP that contains CD-SSB and the entire CORESET#0 to acquire such information.
  • the network may configure a gap once such indication is transmitted. If the indication is to notify the UE that a system information update is going to take place in the next modification period, it may be acceptable that a gap is configured by the network following the indication even though it would not be preferable. However, if the indication is for ETWS and/or CMAS, it may be late by the time the network configures a gap for the UE to retune to a BWP that contains CD-SSB and the entire CORESETO to acquire SIB6, SIB7, and/or SIB8.
  • the UE There is a timing requirement for the UE to acquire the corresponding SIB, e.g., SIB6, SIB7, and/or SIB8, once the UE is notified for ETWS and/or CMAS. So, the UE needs to be sufficiently fast. Therefore, it would be better if there is an alternative way for the network to provide such information, i.e., either the indication or the information, to the UE configured with an active DL BWP that does not contain CD-SSB and thus the entire CORESETO.
  • SIB6 SIB6, SIB7, and/or SIB8
  • the present disclosure proposes systems and methods for the network to provide updated system information or SIB6, SIB7, and/or SIB8 (sometimes referred to herein as “SIB6/SIB7/SIB8”) to a UE configured with an active DL BWP that does not contain CD- SSB and thus the entire CORESET 0 following an indication regarding a notification for system information update or ETWS and/or CMAS.
  • SIB6, SIB7, and/or SIB8 sometimes referred to herein as “SIB6/SIB7/SIB8”
  • the network can transmit a temporary System Information (SI) message (e.g., a Radio Resource Control (RRC) message containing the notification for system information update or ETWS and/or CMAS) to UEs sharing a dedicated BWP.
  • SI System Information
  • RRC Radio Resource Control
  • the network provides the updated system information or SIB6/SIB7/SIB8 to a UE configured with an active DL BWP that does not contain CD-SSB (and thus the entire CORESET 0) following an indication regarding the notification for system information update or ETWS and/or CMAS, so that there would not be any need for the UE to retune to a BWP that contains CD-SSB.
  • Certain embodiments may provide one or more of the following technical advantage(s).
  • the solutions of the present disclosure remove the need for a UE to retune to a BWP that contains CD-SSB in case the network indicates notification for system information update or ETWS and/or CMAS.
  • the UE may reduce the time needed to acquire SIBs, e.g., SIB6, SIB7, and/or SIB8, that correspond to the notification for system information update.
  • SIB6/SIB7/SIB8 by providing the updated system information or SIB6/SIB7/SIB8 to all of the UEs sharing a BWP, signaling overhead is reduced because the dedicated transmission does not have to be repeated for each of the UEs.
  • Figure 2 shows an example of a communication system 200 in accordance with some embodiments.
  • the communication system 200 includes a telecommunication network 202 that includes an access network 204, such as a Radio Access Network (RAN), and a core network 206, which includes one or more core network nodes 208.
  • the access network 204 includes one or more access network nodes, such as network nodes 210A and 210B (one or more of which may be generally referred to as network nodes 210), or any other similar Third Generation Partnership Project (3GPP) access node or non-3GPP Access Point (AP).
  • 3GPP Third Generation Partnership Project
  • the network nodes 210 facilitate direct or indirect connection of User Equipment (UE), such as by connecting UEs 212A, 212B, 212C, and 212D (one or more of which may be generally referred to as UEs 212) to the core network 206 over one or more wireless connections.
  • UE User Equipment
  • Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors.
  • the communication system 200 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • the communication system 200 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 212 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 210 and other communication devices.
  • the network nodes 210 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 212 and/or with other network nodes or equipment in the telecommunication network 202 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 202.
  • the core network 206 connects the network nodes 210 to one or more hosts, such as host 216. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts.
  • the core network 206 includes one more core network nodes (e.g., core network node 208) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 208.
  • Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-Concealing Function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).
  • MSC Mobile Switching Center
  • MME Mobility Management Entity
  • HSS Home Subscriber Server
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • AUSF Authentication Server Function
  • SIDF Subscription Identifier De-Concealing Function
  • UDM Unified Data Management
  • SEPP Security Edge Protection Proxy
  • NEF Network Exposure Function
  • UPF User Plane Function
  • the host 216 may be under the ownership or control of a service provider other than an operator or provider of the access network 204 and/or the telecommunication network 202, and may be operated by the service provider or on behalf of the service provider.
  • the host 216 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.
  • the communication system 200 of Figure 2 enables connectivity between the UEs, network nodes, and hosts.
  • the communication system 200 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable Second, Third, Fourth, or Fifth Generation (2G, 3G, 4G, or 5G) standards, or any applicable future generation standard (e.g., Sixth Generation (6G)); Wireless Local Area Network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any Low Power Wide Area Network (LPWAN) standards such as LoRa and Sigfox.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile
  • the telecommunication network 202 is a cellular network that implements 3 GPP standardized features. Accordingly, the telecommunication network 202 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 202. For example, the telecommunication network 202 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing enhanced Mobile Broadband (eMBB) services to other UEs, and/or massive Machine Type Communication (mMTC)/massive Internet of Things (loT) services to yet further UEs.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB enhanced Mobile Broadband
  • mMTC massive Machine Type Communication
  • LoT massive Internet of Things
  • the UEs 212 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 204 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 204.
  • a UE may be configured for operating in single- or multi -Radio Access Technology (RAT) or multi-standard mode.
  • RAT Radio Access Technology
  • a UE may operate with any one or combination of WiFi, New Radio (NR), and LTE, i.e. be configured for Multi -Radio Dual Connectivity (MR-DC), such as Evolved UMTS Terrestrial RAN (E-UTRAN) NR - Dual Connectivity (EN-DC).
  • MR-DC Multi -Radio Dual Connectivity
  • E-UTRAN Evolved UMTS Terrestrial RAN
  • EN-DC Dual Connectivity
  • a hub 214 communicates with the access network 204 to facilitate indirect communication between one or more UEs (e.g., UE 212C and/or 212D) and network nodes (e.g., network node 210B).
  • the hub 214 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub 214 may be a broadband router enabling access to the core network 206 for the UEs.
  • the hub 214 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • the hub 214 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data.
  • the hub 214 may be a content source. For example, for a UE that is a Virtual Reality (VR) headset, display, loudspeaker or other media delivery device, the hub 214 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 214 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub 214 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.
  • the hub 214 may have a constant/persistent or intermittent connection to the network node 210B.
  • the hub 214 may also allow for a different communication scheme and/or schedule between the hub 214 and UEs (e.g., UE 212C and/or 212D), and between the hub 214 and the core network 206.
  • the hub 214 is connected to the core network 206 and/or one or more UEs via a wired connection.
  • the hub 214 may be configured to connect to a Machine-to-Machine (M2M) service provider over the access network 204 and/or to another UE over a direct connection.
  • M2M Machine-to-Machine
  • UEs may establish a wireless connection with the network nodes 210 while still connected via the hub 214 via a wired or wireless connection.
  • the hub 214 may be a dedicated hub - that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 210B.
  • the hub 214 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and the network node 21 OB, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • “information” refers to updated system information or broadcasted SIB6/SIB7/SIB8 following ETWS and/or CMAS notification.
  • the former (the updated system information) follows an indication in the “Short Message” field in Downlink Control Information (DCI) transmitted on the Physical Downlink Control Channel (PDCCH) for system information update notification and the latter (SIB6/SIB7/SIB8) follows an indication in the “Short Message” field in DCI transmitted on the PDCCH for ETWS and/or CMAS notification.
  • DCI Downlink Control Information
  • PDCCH Physical Downlink Control Channel
  • the “information” is received by UE 212 via dedicated RRC signaling or a dedicated RRC message.
  • the RRC message containing the “information” can be scheduled via the transmission on the PDCCH that contains the DCI scrambled with Paging Radio Network Temporary Identifier (P-RNTI) and the “Short Message” field that indicates the system information update notification or ETWS and/or CMAS notification.
  • P-RNTI Paging Radio Network Temporary Identifier
  • the “information” can be provided using optional field parameters that correspond to the field parameters in broadcasted system information, or in a container.
  • the RRC message (mentioned in the embodiment above), which contains the “information,” can be scheduled via any transmission on the PDCCH after the indication (or the notification), i.e., the system information update notification or the ETWS and/or CMAS notification, is received.
  • Figure 3A is a flow chart of the UE 212 in accordance with some embodiments of the present disclosure.
  • the UE 212 is in connected state and configured with an active DL BWP that does not contain CD-SSB (and therefore does not contain the entire CORESET 0).
  • step 300 A the UE 212 receives, from a network node 210, a notification for either (a) system information update or (b) ETWS and/or CMAS. As discussed above, this notification may be received via a DCI message.
  • the UE 212 receives, from the network node 210, a message (e.g., a RRC message or MAC CE) comprising information related to the received notification after (e.g., responsive to) receiving the notification in step 300 A.
  • a message e.g., a RRC message or MAC CE
  • this information may be updated system information in the case of receiving a notification of a system information update or information related to the ETWS or CMAS in the case of ETWS or CMAS notification (e.g., SIB6, SIB7, and/or SIB8).
  • the information received in step 304A is received without retuning to another BWP that contains a CD-SSB.
  • the UE 212 perform one or more actions based on the received information.
  • the action(s) performed depend on the received information.
  • the UE 212 may present an alert via an associated display.
  • the “information” is received (in step 302A) via dedicated RRC signaling or a dedicated RRC message.
  • the RRC message containing the “information” can be scheduled via the transmission on the PDCCH that contains the DCI scrambled with Paging Radio Network Temporary Identifier (P-RNTI) and the “Short Message” field that indicates the system information update notification or ETWS and/or CMAS notification (e.g., by the notification in step 300A).
  • P-RNTI Paging Radio Network Temporary Identifier
  • the “information” can be provided using optional field parameters that correspond to the field parameters in broadcasted system information, or in a container.
  • the RRC message (mentioned in the embodiment above) which contains the “information”, can be scheduled via any transmission on the PDCCH after the indication (or the notification), i.e., system information update notification or ETWS and/or CMAS notification, is received.
  • the “information” is received in step 302A is via a message on a Medium Access Control (MAC) layer.
  • the MAC message containing the “information” can be scheduled via the transmission on the PDCCH that contains the DCI scrambled with P-RNTI and the “Short Message” field that indicates the system information update notification or ETWS and/or CMAS notification.
  • the “information” in the message can be provided in a MAC Control Element (CE).
  • CE MAC Control Element
  • the message on a MAC layer (mentioned in the embodiment above) containing the “information” can be scheduled via any transmission on the PDCCH after the indication (i.e., the indication of system information update notification or ETWS and/or CMAS notification) is received.
  • the “information” can be provided using optional field parameters that correspond to the field parameters in broadcasted system information, or in a container.
  • the “information” in the message can be provided in a MAC CE.
  • the indication (or the notification) related to system information update or ETWS and/or CMAS notification in step 300A is provided on a MAC layer, for example, in a new MAC CE specified for this purpose. Reception of the MAC CE triggers the UE to monitor for the “information.”
  • the MAC CE contains instructions for the UE on how to receive the “information”, for example, the MAC CE contains the scheduling information or parameters where to obtain the “information” in the time/frequency domain.
  • the “information” can be provided (as in the previous embodiments) either using a dedicated RRC message or via a message on a MAC layer.
  • a specific Radio Network Temporary Identifier is defined for the purpose of indicating and/or scheduling the transmission of the “information.”
  • the new RNTI indicates that the “information” is transmitted in another BWP (i.e., in BWP containing the CD-SSB and system information).
  • a new code point is defined for the Short Message (in TS 38.331 vl6.7.0 (2021-12-23) clause 6.5) transmitted on the PDCCH with DCI scrambled with P-RNTI.
  • the new code point is specific to UEs operating on BWP with NCD-SSB and indicates to a UE that the UE should immediately switch to a BWP containing the system information that requires to be updated.
  • the “information” is obtained in the BWP containing a CD-SSB.
  • the RRC message an example of a System Information message
  • the system information update notification (contained in the RRC message) may still be dedicated, i.e., addressed to the UE 212 on PDCCH, but the scheduled RRC message is common.
  • the present disclosure proposes that multiple PDCCHs can be used to ensure that all UEs 212 in the BWP are reached, but the scheduling (e.g., the scheduling of the RRC message) points to the same PDSCH resource.
  • the notification for the system information update or the ETWS and/or CMAS may be transmitted on the PDCCHs, while the information related to the notification (e.g., updated system information) may be transmitted on the PDSCH, which is commonly received by the UEs 212.
  • a first transmission on a PDCCH includes the system information update notification or the ETWS and/or CMAS notification (a notification or an indication for the “information”).
  • the PDCCH may include information on a scheduling of a System Information (SI) message (e.g., a RRC message).
  • SI System Information
  • RRC message e.g., the RRC message
  • the RRC message may contain the “information” (updated system information or broadcasted SIB6/SIB7/SIB8).
  • C-DRX Connected mode Discontinuous Reception
  • UEs 212 in Connected mode Discontinuous Reception may be required to stop a C-DRX operation to continuously monitor the PDCCH to receive a scheduling of the SI message (e.g., RRC message).
  • a timer may be configured during which UEs 212 are required to monitor the PDCCH of the SI scheduling (e.g., scheduling of the RRC message) after receiving the notification (the system information update notification or the ETWS and/or CMAS notification).
  • the search space could be user-specific search space (USS), but typically since all UEs in the BWP should be reached, common search space (CSS) would be used.
  • the SI message’s e.g., the RRC message scheduling parameters (which is normally carried in SIB1) could, in this case, be included as an extension to the configuration of NCD- SSB, or by a dedicated RRC signaling (i.e., in associating to receiving the dedicated BWP configuration).
  • the system information update notification or the ETWS and/or CMAS notification is omitted and the SI message (e.g., the RRC message) (on the PDSCH) is directly scheduled by a PDCCH (scrambled either with P-RNTI or C-RNTI). That is, in this case, the system information update notification or the ETWS and/or CMAS notification is implicit to the UE 212 from the scheduling of the SI message (e.g., the RRC message).
  • the SI message e.g., the RRC message
  • the ETWS and/or CMAS notification is implicit to the UE 212 from the scheduling of the SI message (e.g., the RRC message).
  • the SI (the “information”, which is the system information update notification or the ETWS and/or CMAS notification) could temporarily be broadcasted in the BWP containing NCD-SSB, either just one occasion or during a configured period of time (e.g., after the indication of the SI).
  • Figure 3B is a flow chart of the UE 212 in accordance with the above-discussed embodiments (Example A and Example B) of the present disclosure.
  • the UE 212 receives, from a network node 210, a notification for either (a) system information update or (b) ETWS and/or CMAS on a PDCCH (e.g., as described above with respect to Example A). As discussed above regarding Example B, this step can be omitted.
  • the PDCCH may contain DCI.
  • the UE 212 receives a SI message (containing the “information” or information related to the notification) on a PDSCH.
  • a SI message (containing the “information” or information related to the notification) on a PDSCH.
  • the SI message on the PDSCH may be scheduled by DCI in PDCCH scrambled by C-RNTI.
  • the SI message on the PDSCH may be directly scheduled by PDCCH scrambled either with P-RNTI or C-RNTI.
  • the PDSCH is a common PDSCH for multiple UEs, where, for example, each of the UEs is scheduled by respective PDCCHs each containing DCI that points to the common PDSCH.
  • the UE 212 may perform one or more actions when the UE 212 receives the notification on the PDCCH or the SI message on the PDSCH. For example, the UE 212 may stop C-DRX operation to continuously monitor the PDCCH to receive a scheduling of the SI message (e.g., RRC message).
  • the SI message e.g., RRC message
  • the UE 212 may be configured to perform (e.g., as part of step 302B of Figure 3B or likewise as part of step 302A of Figure 3A) whether (a) to retune to CD-SSB to acquire the required SI message(s), or (b) to, using a legacy procedure, request to obtain the SI by dedicated signaling in the dedicated BWP (i.e., using existing procedures to obtain on-demand SI).
  • the UE 212 is configured to obtain the on-demand SI, for example, the PRACH configuration, dedicated preamble, etc., can be provided to the UE 212 as an extension to the configuration of NCD-SSB, or by dedicated RRC signaling (i.e., in associating to receiving the dedicated BWP configuration).
  • the PRACH configuration for example, the PRACH configuration, dedicated preamble, etc.
  • dedicated RRC signaling i.e., in associating to receiving the dedicated BWP configuration.
  • SI-RequestConfig would be provided to UEs 212 operating in a dedicated BWP which does not contain CD-SSB.
  • CFRA contention-free random access
  • CBRA contention-based random access
  • the requested SI is related to indication in paging, i.e. in case of the ETWS and/or CMAS notification, the request would implicitly be understood to be ETWS information.
  • the “information” is received in step 302B of Figure 3B is via a message on a Medium Access Control (MAC) layer.
  • the SI message can be a message on a MAC layer or a MAC message.
  • the MAC message containing the “information” can be scheduled via the transmission on the PDCCH that contains the DCI scrambled with P-RNTI and the “Short Message” field that indicates the system information update notification or ETWS and/or CMAS notification.
  • the “information” in the message can be provided in a MAC Control Element (CE).
  • CE MAC Control Element
  • the message on a MAC layer (mentioned in the embodiment above) containing the “information” can be scheduled via any transmission on the PDCCH after the indication (i.e., the indication of system information update notification or ETWS and/or CMAS notification) is received.
  • the “information” can be provided using optional field parameters that correspond to the field parameters in broadcasted system information, or in a container.
  • the “information” in the message can be provided in a MAC CE.
  • the indication (or the notification) related to system information update or ETWS and/or CMAS notification is provided on a MAC layer, for example, in a new MAC CE specified for this purpose. Reception of the MAC CE triggers the UE to monitor for the “information.”
  • the MAC CE contains instructions for the UE on how to receive the “information,” for example, the MAC CE contains the scheduling information or parameters where to obtain the “information” in the time/frequency domain.
  • the “information” can be provided (as in the previous embodiments) either using a dedicated RRC message or via a message on a MAC layer.
  • a specific Radio Network Temporary Identifier is defined for the purpose of indicating and/or scheduling the transmission of the “information.”
  • the new RNTI indicates that the “information” is transmitted in another BWP (i.e., in BWP containing the CD-SSB and system information).
  • a new code point is defined for the Short Message (in TS 38.331 vl6.7.0 (2021-12-23) clause 6.5) transmitted on the PDCCH with DCI scrambled with P-RNTI.
  • the new code point is specific to UEs operating on BWP with NCD-SSB and indicates to a UE that the UE should immediately switch to a BWP containing the system information that requires to be updated. That is, the “information” is obtained in the BWP containing a CD-SSB.
  • a UE refers to a device capable, configured, arranged, and/or operable to communicate wirelessly with network nodes and/or other UEs.
  • a UE include, but are not limited to, a smart phone, mobile phone, cell phone, Voice over Internet Protocol (VoIP) phone, wireless local loop phone, desktop computer, Personal Digital Assistant (PDA), wireless camera, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, Laptop Embedded Equipment (LEE), Laptop Mounted Equipment (LME), smart device, wireless Customer Premise Equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc.
  • Other examples include any UE identified by the 3 GPP, including a Narrowband Internet of Things (NB-IoT) UE, a Machine Type Communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • NB-IoT Narrowband Internet of Things
  • MTC Machine Type Communication
  • eMTC
  • a UE may support Device-to-Device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), Vehi cl e-to- Vehicle (V2V), Vehicle-to-Infrastructure (V2I), or Vehicle- to-Everything (V2X).
  • D2D Device-to-Device
  • DSRC Dedicated Short-Range Communication
  • V2V Vehi cl e-to- Vehicle
  • V2I Vehicle-to-Infrastructure
  • V2X Vehicle- to-Everything
  • a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller).
  • a UE may represent
  • the UE 400 includes processing circuitry 402 that is operatively coupled via a bus 404 to an input/output interface 406, a power source 408, memory 410, a communication interface 412, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Figure 4. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
  • the processing circuitry 402 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 410.
  • the processing circuitry 402 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general purpose processors, such as a microprocessor or Digital Signal Processor
  • processing circuitry 402 may include multiple Central Processing Units (CPUs).
  • CPUs Central Processing Units
  • the input/output interface 406 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices.
  • Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof.
  • An input device may allow a user to capture information into the UE 400.
  • Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like.
  • the presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user.
  • a sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof.
  • An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.
  • USB Universal Serial Bus
  • the power source 408 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used.
  • the power source 408 may further include power circuitry for delivering power from the power source 408 itself, and/or an external power source, to the various parts of the UE 400 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging the power source 408.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source 408 to make the power suitable for the respective components of the UE 400 to which power is supplied.
  • the memory 410 may be or be configured to include memory such as Random Access Memory (RAM), Read Only Memory (ROM), Programmable ROM (PROM), Erasable PROM (EPROM), Electrically EPROM (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth.
  • the memory 410 includes one or more application programs 414, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 416.
  • the memory 410 may store, for use by the UE 400, any of a variety of various operating systems or combinations of operating systems.
  • the memory 410 may be configured to include a number of physical drive units, such as Redundant Array of Independent Disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, High Density Digital Versatile Disc (HD- DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, Holographic Digital Data Storage (HDDS) optical disc drive, external mini Dual In-line Memory Module (DIMM), Synchronous Dynamic RAM (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a tamper resistant module in the form of a Universal Integrated Circuit Card (UICC) including one or more Subscriber Identity Modules (SIMs), such as a Universal SIM (USIM) and/or Internet Protocol Multimedia Services Identity Module (ISIM), other memory, or any combination thereof.
  • RAID Redundant Array of Independent Disks
  • HD- DVD High Density Digital Versatile Disc
  • HD- DVD High Density Digital Versatile Disc
  • HD- DVD Compact
  • the UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as a ‘SIM card.’
  • the memory 410 may allow the UE 400 to access instructions, application programs, and the like stored on transitory or non-transitory memory media, to off-load data, or to upload data.
  • An article of manufacture, such as one utilizing a communication system, may be tangibly embodied as or in the memory 410, which may be or comprise a device-readable storage medium.
  • the processing circuitry 402 may be configured to communicate with an access network or other network using the communication interface 412.
  • the communication interface 412 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 422.
  • the communication interface 412 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network).
  • Each transceiver may include a transmitter 418 and/or a receiver 420 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • the transmitter 418 and receiver 420 may be coupled to one or more antennas (e.g., the antenna 422) and may share circuit components, software, or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface 412 may include cellular communication, WiFi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, NFC, location-based communication such as the use of the Global Positioning System (GPS) to determine a location, another like communication function, or any combination thereof.
  • GPS Global Positioning System
  • Communications may be implemented according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband CDMA (WCDMA), GSM, LTE, NR, UMTS, WiMax, Ethernet, Transmission Control Protocol/Internet Protocol (TCP/IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), Quick User Datagram Protocol Internet Connection (QUIC), Hypertext Transfer Protocol (HTTP), and so forth.
  • a UE may provide an output of data captured by its sensors, through its communication interface 412, or via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE.
  • the output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).
  • a UE comprises an actuator, a motor, or a switch related to a communication interface configured to receive wireless input from a network node via a wireless connection.
  • the states of the actuator, the motor, or the switch may change.
  • the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.
  • a UE when in the form of an loT device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application, and healthcare.
  • Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a television, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or VR, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or itemtracking device, a sensor for
  • a UE may represent a machine or other device that performs monitoring and/or measurements and transmits the results of such monitoring and/or measurements to another UE and/or a network node.
  • the UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device.
  • the UE may implement the 3 GPP NB-IoT standard.
  • a UE may represent a vehicle, such as a car, a bus, a truck, a ship, an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • any number of UEs may be used together with respect to a single use case.
  • a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone.
  • the first UE may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone’s speed.
  • the first and/or the second UE can also include more than one of the functionalities described above.
  • a UE might comprise the sensor and the actuator and handle communication of data for both the speed sensor and the actuators.
  • FIG. 5 shows a network node 500 in accordance with some embodiments.
  • network node refers to equipment capable, configured, arranged, and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment in a telecommunication network.
  • Examples of network nodes include, but are not limited to, APs (e.g., radio APs), Base Stations (BSs) (e.g., radio BSs, Node Bs, evolved Node Bs (eNBs), and NR Node Bs (gNBs)).
  • APs e.g., radio APs
  • BSs Base Stations
  • eNBs evolved Node Bs
  • gNBs NR Node Bs
  • BSs may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto BSs, pico BSs, micro BSs, or macro BSs.
  • a BS may be a relay node or a relay donor node controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio BS such as centralized digital units and/or Remote Radio Units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such RRUs may or may not be integrated with an antenna as an antenna integrated radio.
  • RRUs Remote Radio Heads
  • Parts of a distributed radio BS may also be referred to as nodes in a Distributed Antenna System (DAS).
  • DAS Distributed Antenna System
  • network nodes include multiple Transmission Point (multi-TRP) 5G access nodes, Multi -Standard Radio (MSR) equipment such as MSR BSs, network controllers such as Radio Network Controllers (RNCs) or BS Controllers (BSCs), Base Transceiver Stations (BTSs), transmission points, transmission nodes, Multi-Cell/Multicast Coordination Entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).
  • MSR Transmission Point
  • MSR Multi -Standard Radio
  • RNCs Radio Network Controllers
  • BSCs Base Transceiver Stations
  • MCEs Multi-Cell/Multicast Coordination Entities
  • OFM Operation and Maintenance
  • OSS Operations Support System
  • SON Self-Organizing Network
  • the network node 500 includes processing circuitry 502, memory 504, a communication interface 506, and a power source 508.
  • the network node 500 may be composed of multiple physically separate components (e.g., a Node B component and an RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • the network node 500 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple Node Bs.
  • each unique Node B and RNC pair may in some instances be considered a single separate network node.
  • the network node 500 may be configured to support multiple RATs.
  • the network node 500 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 500, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, Long Range Wide Area Network (LoRaWAN), Radio Frequency Identification (RFID), or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within the network node 500.
  • the processing circuitry 502 may comprise a combination of one or more of a microprocessor, controller, microcontroller, CPU, DSP, ASIC, FPGA, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other network node 500 components, such as the memory 504, to provide network node 500 functionality.
  • the processing circuitry 502 includes a System on a Chip (SOC). In some embodiments, the processing circuitry 502 includes one or more of Radio Frequency (RF) transceiver circuitry 512 and baseband processing circuitry 514. In some embodiments, the RF transceiver circuitry 512 and the baseband processing circuitry 514 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part, or all of the RF transceiver circuitry 512 and the baseband processing circuitry 514 may be on the same chip or set of chips, boards, or units.
  • SOC System on a Chip
  • the processing circuitry 502 includes one or more of Radio Frequency (RF) transceiver circuitry 512 and baseband processing circuitry 514.
  • RF transceiver circuitry 512 and the baseband processing circuitry 514 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part, or all of
  • the memory 504 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid state memory, remotely mounted memory, magnetic media, optical media, RAM, ROM, mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD), or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable, and/or computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry 502.
  • volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid state memory, remotely mounted memory, magnetic media, optical media, RAM, ROM, mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD), or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable, and/or computer
  • the memory 504 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 502 and utilized by the network node 500.
  • the memory 504 may be used to store any calculations made by the processing circuitry 502 and/or any data received via the communication interface 506.
  • the processing circuitry 502 and the memory 504 are integrated.
  • the communication interface 506 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 506 comprises port(s)/terminal(s) 516 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 506 also includes radio front-end circuitry 518 that may be coupled to, or in certain embodiments a part of, the antenna 510.
  • the radio front-end circuitry 518 comprises filters 520 and amplifiers 522.
  • the radio front-end circuitry 518 may be connected to the antenna 510 and the processing circuitry 502.
  • the radio front-end circuitry 518 may be configured to condition signals communicated between the antenna 510 and the processing circuitry 502.
  • the radio front-end circuitry 518 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection.
  • the radio front-end circuitry 518 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of the filters 520 and/or the amplifiers 522.
  • the radio signal may then be transmitted via the antenna 510.
  • the antenna 510 may collect radio signals which are then converted into digital data by the radio front-end circuitry 518.
  • the digital data may be passed to the processing circuitry 502.
  • the communication interface 506 may comprise different components and/or different combinations of components.
  • the network node 500 does not include separate radio front-end circuitry 518; instead, the processing circuitry 502 includes radio front-end circuitry and is connected to the antenna 510.
  • the processing circuitry 502 includes radio front-end circuitry and is connected to the antenna 510.
  • all or some of the RF transceiver circuitry 512 is part of the communication interface 506.
  • the communication interface 506 includes the one or more ports or terminals 516, the radio frontend circuitry 518, and the RF transceiver circuitry 512 as part of a radio unit (not shown), and the communication interface 506 communicates with the baseband processing circuitry 514, which is part of a digital unit (not shown).
  • the antenna 510 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 510 may be coupled to the radio front-end circuitry 518 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna 510 is separate from the network node 500 and connectable to the network node 500 through an interface or port.
  • the antenna 510, the communication interface 506, and/or the processing circuitry 502 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node 500. Any information, data, and/or signals may be received from a UE, another network node, and/or any other network equipment.
  • the antenna 510, the communication interface 506, and/or the processing circuitry 502 may be configured to perform any transmitting operations described herein as being performed by the network node 500. Any information, data, and/or signals may be transmitted to a UE, another network node, and/or any other network equipment.
  • the power source 508 provides power to the various components of the network node 500 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 508 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 500 with power for performing the functionality described herein.
  • the network node 500 may be connectable to an external power source (e.g., the power grid or an electricity outlet) via input circuitry or an interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 508.
  • the power source 508 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.
  • Embodiments of the network node 500 may include additional components beyond those shown in Figure 5 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein.
  • the network node 500 may include user interface equipment to allow input of information into the network node 500 and to allow output of information from the network node 500. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 500.
  • computing devices described herein may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions, and methods disclosed herein. Determining, calculating, obtaining, or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing circuitry may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components.
  • a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface.
  • non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.
  • processing circuitry executing instructions stored in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium.
  • some or all of the functionalities may be provided by the processing circuitry without executing instructions stored on a separate or discrete device- readable storage medium, such as in a hardwired manner.
  • the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole and/or by end users and a wireless network generally.
  • Embodiment 1 A method performed by User Equipment, UE, (212) configured with an active downlink, DL, bandwidth part, BWP, that does not contain a Cell Defining Synchronization Signal Block, CD-SSB, the method comprising: receiving (300), from a network node (210), a notification for either (a) system information update or (b) Earthquake and Tsunami Warning System, ETWS, and/or Commercial Mobile Alert System, CMAS; and receiving (302), from the network node (210), a message comprising information related to the received notification after (e.g., responsive to) receiving (300) the notification.
  • a notification for either (a) system information update or (b) Earthquake and Tsunami Warning System, ETWS, and/or Commercial Mobile Alert System, CMAS
  • CMAS Commercial Mobile Alert System
  • Embodiment 2 The method of embodiment 1 further comprising performing (304) one or more actions based on the received information.
  • Embodiment 3 The method of embodiment 1 or 2, wherein the information related to the (a) system information update is updated system information or the information related to the (b) ETWS and/or CMAS is SIB6, SIB7, and/or SIB8.
  • Embodiment 4 The method of any of embodiments 1 to 3, wherein the notification is received via an indication in a “Short Message” field in Downlink Control Information, DCI, received on Physical Downlink Control Channel, PDCCH.
  • Embodiment 5 The method of any of embodiments 1 to 4, wherein receiving the information comprises receiving the information via a dedicated Radio Resource Control, RRC, message.
  • RRC Radio Resource Control
  • Embodiment 6 The method of any of embodiments 1 to 4, wherein receiving the information comprising receiving the information via a dedicated RRC message using optional field parameters that correspond to field parameters in broadcasted system information.
  • Embodiment 7 The method of embodiment 6, wherein the RRC message is scheduled via any transmission on Physical Downlink Control Channel, PDCCH, after the notification is received.
  • PDCCH Physical Downlink Control Channel
  • Embodiment 8 The method of any of embodiments 1 to 7, wherein receiving the message comprises receiving the message on a Medium Access Control, MAC, layer.
  • MAC Medium Access Control
  • Embodiment 9 The method of embodiment 8, wherein the message on a MAC layer is scheduled via a Physical Downlink Control Channel, PDCCH, that contains Downlink Control Information, DCI, scrambled with Paging Radio Network Temporary Identifier, P-RNTI.
  • PDCCH Physical Downlink Control Channel
  • DCI Downlink Control Information
  • P-RNTI Paging Radio Network Temporary Identifier
  • Embodiment 10 The method of embodiment 8, the message on a MAC layer is scheduled via a Physical Downlink Control Channel, PDCCH, received after the notification is received.
  • PDCCH Physical Downlink Control Channel
  • Embodiment 11 The method of any of embodiments 1 to 9, receiving the notification comprises receiving the notification on a Medium Access Control, MAC, layer.
  • MAC Medium Access Control
  • Embodiment 12 A User Equipment, UE, (212) configured with an active downlink, DL, bandwidth part, BWP, that does not contain a Cell Defining Synchronization Signal Block, CD- SSB, the UE (212) adapted to: receive (300), from a network node (210), a notification for either (a) system information update or (b) Earthquake and Tsunami Warning System, ETWS, and/or Commercial Mobile Alert System, CMAS; and receive (302), from the network node (210), a message comprising information related to the received notification after (e.g., responsive to) receiving (300) the notification.
  • a notification for either (a) system information update or (b) Earthquake and Tsunami Warning System, ETWS, and/or Commercial Mobile Alert System, CMAS
  • receive (302) from the network node (210), a message comprising information related to the received notification after (e.g., responsive to) receiving (300) the notification.
  • Embodiment 13 The UE (212) of embodiment 12 wherein the UE (212) is further adapted to perform the method of any of embodiments 2 to 11.
  • Embodiment 14 A User Equipment, UE, (212) comprising: one or more transmitters; one or more receivers; and processing circuitry associated with the one or more transmitters and the one or more receivers, the processing circuitry configured to cause the UE (212) to: receive (300), from a network node (210), a notification for either (a) system information update or (b) Earthquake and Tsunami Warning System, ETWS, and/or Commercial Mobile Alert System, CMAS; and receive (302), from the network node (210), a message comprising information related to the received notification after (e.g., responsive to) receiving (300) the notification.
  • a notification for either (a) system information update or (b) Earthquake and Tsunami Warning System, ETWS, and/or Commercial Mobile Alert System, CMAS
  • receive (302) from the network node (210), a message comprising information related to the received notification after (e.g., responsive to) receiving (300) the notification.
  • Embodiment 15 The UE (212) of embodiment 14, wherein the processing circuitry is further configured to cause the UE (212) to perform the method of any of embodiments 2 to 11.
  • Embodiment 16 A method performed by User Equipment, UE, (212) configured with an active downlink, DL, bandwidth part, BWP, that does not contain a Cell Defining Synchronization Signal Block, CD-SSB, the method comprising receiving (302), from a network node (210), a System Information, SI, message, on a Physical Downlink Shared Channel, PDSCH, the SI message comprising information related to a notification for either (a) system information update or (b) Earthquake and Tsunami Warning System, ETWS, and/or Commercial Mobile Alert System, CMAS.
  • UE User Equipment
  • UE configured with an active downlink, DL, bandwidth part, BWP, that does not contain a Cell Defining Synchronization Signal Block, CD-SSB
  • the method comprising receiving (302), from a network node (210), a System Information, SI, message, on a Physical Downlink Shared Channel, PDSCH, the SI message comprising information related to a notification for either (a) system
  • Embodiment 17 The method of embodiment 16 further comprising receiving (300), from the network node (210), the notification for either (a) system information update or (b) ETWS and/or CMAS, on a Physical Downlink Control Channel, PDCCH.
  • Embodiment 18 The method of embodiment 16 or 17, wherein the SI message received on the PDSCH is scheduled by Downlink Control Information, DCI, in a Physical Downlink Control Channel, PDCCH, scrambled by Cell Radio Network Temporary Identifier, C-RNTI.
  • DCI Downlink Control Information
  • PDCCH Physical Downlink Control Channel
  • C-RNTI Cell Radio Network Temporary Identifier
  • Embodiment 19 The method of embodiments 16 or 17, wherein the SI message received on the PDSCH is directly scheduled by a Physical Downlink Control Channel, PDCCH, scrambled either with Paging Radio Network Temporary Identifier, P-RNTI or Cell Radio Network Temporary Identifier, C-RNTI.
  • PDCCH Physical Downlink Control Channel
  • Embodiment 20 The method of any of embodiments 16 to 19 further comprising performing (304) one or more actions when the UE (212) receives the notification on the PDCCH or the SI message on the PDSCH.
  • Embodiment 21 The method of embodiment 20, performing (304) one or more actions comprises stopping a Connected mode Discontinuous Reception, C-DRX, operation to continuously monitor the PDCCH to receive a scheduling of the SI message.
  • C-DRX Connected mode Discontinuous Reception
  • Embodiment 22 The method of any of embodiments 16 to 21, wherein the information related to the (a) system information update is updated system information or the information related to the (b) ETWS and/or CMAS is SIB6, SIB7, and/or SIB8.
  • Embodiment 23 The method of any of embodiments 16 to 22, wherein the notification is received via an indication in a “Short Message” field in Downlink Control Information, DCI, received on Physical Downlink Control Channel, PDCCH.
  • Embodiment 24 The method of any of embodiments 16 to 23, wherein receiving (302) the SI message comprises receiving the SI message via a dedicated Radio Resource Control, RRC, message.
  • RRC Radio Resource Control
  • Embodiment 25 The method of any of embodiments 16 to 24, wherein receiving (302) the SI message comprising receiving the SI message via a dedicated Radio Resource Control, RRC, message using optional field parameters that correspond to field parameters in broadcasted system information.
  • RRC Radio Resource Control
  • Embodiment 26 The method of embodiment 25, wherein the RRC message is scheduled via any transmission on Physical Downlink Control Channel, PDCCH, after the notification is received.
  • PDCCH Physical Downlink Control Channel
  • Embodiment 27 The method of any of embodiments 16 to 23, wherein receiving (302) the SI message comprises receiving the SI message on a Medium Access Control, MAC, layer.
  • receiving (302) the SI message comprises receiving the SI message on a Medium Access Control, MAC, layer.
  • Embodiment 28 The method of embodiment 27, wherein the SI message on the MAC layer is scheduled via a Physical Downlink Control Channel, PDCCH, that contains Downlink Control Information, DCI, scrambled with Paging Radio Network Temporary Identifier, P-RNTI.
  • PDCCH Physical Downlink Control Channel
  • DCI Downlink Control Information
  • P-RNTI Paging Radio Network Temporary Identifier
  • Embodiment 29 The method of embodiment 27, the SI message on the MAC layer is scheduled via a Physical Downlink Control Channel, PDCCH, received after the notification is received.
  • PDCCH Physical Downlink Control Channel
  • Embodiment 30 The method of any of embodiments 17 to 29, receiving (300) the notification comprises receiving the notification on a Medium Access Control, MAC, layer.
  • MAC Medium Access Control
  • Embodiment 31 A User Equipment, UE, (212) configured with an active downlink, DL, bandwidth part, BWP, that does not contain a Cell Defining Synchronization Signal Block, CD- SSB, the UE (212) adapted to receive (302), from the network node (210), a System Information, SI, message, on a Physical Downlink Shared Channel, PDSCH, the SI message comprising information related to a notification for either (a) system information update or (b) Earthquake and Tsunami Warning System, ETWS, and/or Commercial Mobile Alert System, CMAS.
  • Embodiment 32 The UE (212) of embodiment 31 wherein the UE (212) is further adapted to perform the method of any of embodiments 17 to 30.
  • Embodiment 33 A User Equipment, UE, (212) comprising: one or more transmitters; one or more receivers; and processing circuitry associated with the one or more transmitters and the one or more receivers, the processing circuitry configured to cause the UE (212) to receive (302), from the network node (210), a System Information, SI, message, on a Physical Downlink Shared Channel, PDSCH, the SI message comprising information related to a notification for either (a) system information update or (b) Earthquake and Tsunami Warning System, ETWS, and/or Commercial Mobile Alert System, CMAS.
  • Embodiment 34 The UE (212) of embodiment 33, wherein the processing circuitry is further configured to cause the UE (212) to perform the method of any of embodiments 17 to 30.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Health & Medical Sciences (AREA)
  • Emergency Management (AREA)
  • Environmental & Geological Engineering (AREA)
  • Public Health (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Sont divulgués des systèmes et des procédés qui se rapportent à des informations diffusées lorsqu'un équipement utilisateur (UE) est configuré avec une partie de bande passante (BWP) de liaison descendante active (DL) qui ne contient pas de bloc de signal de synchronisation définissant une cellule (CD-SSB). Dans un mode de réalisation, un procédé mis en œuvre par un UE configuré avec une BWP DL active qui ne contient pas de CD-SSB consiste à recevoir, en provenance d'un nœud de réseau, un message sur un canal partagé de liaison descendante physique (PDSCH), le message comprenant des informations relatives à une notification pour (A) une mise à jour d'informations de système ou (b) un système d'avertissement de tremblement de terre et de tsunami (ETWS) et/ou un système d'alerte mobile commercial (CMAS). De cette manière, le besoin pour l'UE d'effectuer un réajustement par rapport à une BWP qui contient un CD-SSB dans le cas où le réseau indique une notification pour une mise à jour d'informations de système ou un ETWS et/ou un CMAS peuvent être éliminés.
PCT/SE2023/050143 2022-02-17 2023-02-17 Informations diffusées par signalisation commune ou dédiée en mode connecté lors de l'utilisation de ncd-ssb WO2023158362A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US202263311373P 2022-02-17 2022-02-17
US63/311,373 2022-02-17
US202263312885P 2022-02-23 2022-02-23
US63/312,885 2022-02-23

Publications (1)

Publication Number Publication Date
WO2023158362A1 true WO2023158362A1 (fr) 2023-08-24

Family

ID=87578715

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2023/050143 WO2023158362A1 (fr) 2022-02-17 2023-02-17 Informations diffusées par signalisation commune ou dédiée en mode connecté lors de l'utilisation de ncd-ssb

Country Status (1)

Country Link
WO (1) WO2023158362A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200053811A1 (en) * 2018-08-09 2020-02-13 Qualcomm Incorporated Bandwidth configuration techniques in wireless communications
WO2021085990A1 (fr) * 2019-10-28 2021-05-06 Lg Electronics Inc. Procédé et appareil pour éliminer des ressources de retransmission sur la base d'un accusé de réception
WO2021138854A1 (fr) * 2020-01-08 2021-07-15 华为技术有限公司 Procédé, appareil et dispositif d'envoi et de réception de signal
WO2022212122A1 (fr) * 2021-03-29 2022-10-06 Intel Corporation Fonctionnements faisant appel à une bwp pour équipements utilisateurs à capacité réduite
WO2023022986A1 (fr) * 2021-08-18 2023-02-23 Qualcomm Incorporated Configurations de bwp pour des ue ayant des capacités différentes

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200053811A1 (en) * 2018-08-09 2020-02-13 Qualcomm Incorporated Bandwidth configuration techniques in wireless communications
WO2021085990A1 (fr) * 2019-10-28 2021-05-06 Lg Electronics Inc. Procédé et appareil pour éliminer des ressources de retransmission sur la base d'un accusé de réception
WO2021138854A1 (fr) * 2020-01-08 2021-07-15 华为技术有限公司 Procédé, appareil et dispositif d'envoi et de réception de signal
WO2022212122A1 (fr) * 2021-03-29 2022-10-06 Intel Corporation Fonctionnements faisant appel à une bwp pour équipements utilisateurs à capacité réduite
WO2023022986A1 (fr) * 2021-08-18 2023-02-23 Qualcomm Incorporated Configurations de bwp pour des ue ayant des capacités différentes

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Monitoring POs in connected mode when using NCD-SSB", 3GPP DRAFT; R2-2203505, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Electronic meeting; 20220221 - 20220303, 20 February 2022 (2022-02-20), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052131219 *
QUALCOMM INCORPORATED: "BW Reduction for RedCap UE", 3GPP DRAFT; R1-2112223, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20211111 - 20211119, 6 November 2021 (2021-11-06), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052075329 *

Similar Documents

Publication Publication Date Title
JP2023027034A (ja) 初期測定におけるビーム情報
US20230189338A1 (en) COT/FFP Scheduling in Unlicensed Spectrum
US11792693B2 (en) Methods and apparatuses for redirecting users of multimedia priority services
EP4381884A1 (fr) Partitionnement d'accès aléatoire et rapport d'accès aléatoire
WO2023163629A1 (fr) Adaptation de puissance de transmission de réseau économe en énergie
WO2023113674A1 (fr) Fonctionnement d'équipement utilisateur (ue) avec configuration d'économie d'énergie de station de base
WO2023037004A1 (fr) Transmissions sur la liaison latérale dans une bande de fréquence non soumise à licence
WO2023158362A1 (fr) Informations diffusées par signalisation commune ou dédiée en mode connecté lors de l'utilisation de ncd-ssb
WO2024035327A1 (fr) Économies d'énergie de nœud de réseau par l'intermédiaire d'un mécanisme de réponse d'accès aléatoire flexible
WO2024045176A1 (fr) Signalisation et configuration d'accès aléatoire (ra) d'amélioration de couverture (ce)
US20240224371A1 (en) Network traffic management
WO2023068982A1 (fr) Écart de mesure multi-usim basé sur une condition de proximité de réception de signal
WO2023152376A1 (fr) Procédés et appareils de commande d'un dispositif terminal
WO2024102048A1 (fr) Adressage d'ue avec des codes wus
WO2024009198A1 (fr) Détermination de faisceaux pour transmissions en liaison montante suivant de multiples transmissions sur un canal physique d'accès aléatoire avec différents faisceaux
WO2023014267A1 (fr) Systèmes et procédés de transformation entre des motifs d'intervalle de mesure simultanés
WO2024096809A1 (fr) Signal de découverte
WO2024096810A1 (fr) Détermination et transmission de signal de réveil
WO2023211329A1 (fr) Informations de commande de liaison latérale pour communication multicanal
WO2024099949A1 (fr) Inclusion d'identité de pcell (cellule primaire) dans un rapport ra tout en effectuant une procédure ra vers une cellule scg
WO2023132783A1 (fr) Détermination d'une configuration, envoi d'un rapport à un nœud de réseau, et réception d'un rapport à partir d'un équipement utilisateur
WO2024095231A1 (fr) Inclusion conditionnelle d'une combinaison de caractéristiques dans un rapport de ra
WO2024028832A1 (fr) Signalisation de groupe pour économies d'énergie de réseau
WO2024008284A1 (fr) Réactivation rapide de cellule secondaire (scell) au moyen d'un équipement utilisateur
WO2023059240A1 (fr) Amélioration d'un rapport d'accès aléatoire avec indication d'accès aléatoire effectué vers mn ou sn

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: 23756724

Country of ref document: EP

Kind code of ref document: A1