WO2024168539A1 - Accessibilité à un équipement utilisateur à capacité réduite étendue dans des cellules - Google Patents

Accessibilité à un équipement utilisateur à capacité réduite étendue dans des cellules Download PDF

Info

Publication number
WO2024168539A1
WO2024168539A1 PCT/CN2023/076004 CN2023076004W WO2024168539A1 WO 2024168539 A1 WO2024168539 A1 WO 2024168539A1 CN 2023076004 W CN2023076004 W CN 2023076004W WO 2024168539 A1 WO2024168539 A1 WO 2024168539A1
Authority
WO
WIPO (PCT)
Prior art keywords
eredcap
frequency
indication
redcap
cell reselection
Prior art date
Application number
PCT/CN2023/076004
Other languages
English (en)
Inventor
Naveen Kumar R. PALLE VENKATA
Peng Cheng
Haijing Hu
Yuqin Chen
Alexander Sirotkin
Fangli Xu
Sethuraman Gurumoorthy
Zhibin Wu
Ralf ROSSBACH
Ping-Heng Kuo
Original Assignee
Apple Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Apple Inc. filed Critical Apple Inc.
Priority to PCT/CN2023/076004 priority Critical patent/WO2024168539A1/fr
Publication of WO2024168539A1 publication Critical patent/WO2024168539A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/20—Selecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/12—Access restriction or access information delivery, e.g. discovery data delivery using downlink control channel

Definitions

  • the present disclosure generally relates to wireless communication, and in particular, to extended reduced capability user equipment accessibility in cells.
  • Cellular communications can be defined in various standards to enable communications between a user equipment and a cellular network.
  • LTE long-term evolution
  • 5G Fifth generation
  • LTE long-term evolution
  • 5G Fifth generation
  • Figure 1 is an illustration of a reduced capability user equipment (RedCap UE) and an extended reduced capability user equipment (eRedCap UE) , according to one or more embodiments.
  • RedCap UE reduced capability user equipment
  • eRedCap UE extended reduced capability user equipment
  • Figure 2 is a signaling diagram for determining eRedCAP UE accessibility, according to one or more embodiments.
  • Figure 3 is an example abstract syntax notation 1 (ASN1) code for cell accessibility, according to one or more embodiments.
  • Figure 4 is an example ASN1 code for cell accessibility, according to one or more embodiments.
  • Figure 5 is a signaling diagram for determining eRedCap UE accessibility for intra-frequency cell reselection, according to one or more embodiments.
  • Figure 6 is an example ASN1 code for intra-frequency cell reselection, according to one or more embodiments.
  • Figure 7 is a signaling diagram for inter-frequency cell reselection for an eRedCap UE, according to one or more embodiments.
  • Figure 8 is an example ASN1 code for inter-frequency cell reselection, according to one or more embodiments.
  • Figure 9 is a signaling diagram for exchanging frequencies between base stations for inter-frequency cell reselection, according to one or more embodiments.
  • Figure 10 is a narrative describing that an IE carried over a SIB1 broadcast of a corresponding cell, according to one or more embodiments.
  • Figure 11 is a signaling diagram for a cell that does not support an eRedCap UE, according to one or more embodiments.
  • Figure 12 is a signaling diagram for a cell that does support an eRedCap UE, according to one or more embodiments.
  • Figure 13 is a process flow for determining eRedCap UE accessibility for a cell, according to one or more embodiments.
  • Figure 14 illustrates an example of receive components, according to one or more embodiments.
  • Figure 15 illustrates an example of a UE, according to one or more embodiments.
  • Figure 16 illustrates an example of a base station, according to one or more embodiments.
  • the phrase “A or B” means (A) , (B) , or (A and B) ; and the phrase “based on A” means “based at least in part on A, ” for example, it could be “based solely on A” or it could be “based in part on A. ”
  • circuitry refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) or memory (shared, dedicated, or group) , an Application Specific Integrated Circuit (ASIC) , a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA) , a programmable logic device (PLD) , a complex PLD (CPLD) , a high-capacity PLD (HCPLD) , a structured ASIC, or a programmable system-on-a-chip (SoC) ) , digital signal processors (DSPs) , etc., that are configured to provide the described functionality.
  • FPD field-programmable device
  • FPGA field-programmable gate array
  • PLD programmable logic device
  • CPLD complex PLD
  • HPLD high-capacity PLD
  • SoC programmable system-on-a-chip
  • DSPs digital signal processors
  • the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality.
  • the term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.
  • processor circuitry refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, or transferring digital data.
  • processor circuitry may refer to an application processor, baseband processor, a central processing unit (CPU) , a graphics processing unit, a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, or functional processes.
  • interface circuitry refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices.
  • interface circuitry may refer to one or more hardware interfaces, for example, buses, I/O interfaces, peripheral component interfaces, network interface cards, or the like.
  • user equipment refers to a device with radio communication capabilities and may describe a remote user of network resources in a communications network.
  • the term “user equipment” or “UE” may be considered synonymous to, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc.
  • the term “user equipment” or “UE” may include any type of wireless/wired device or any computing device including a wireless communications interface.
  • base station refers to a device with radio communication capabilities, that is a network component of a communications network (or, more briefly, a network) , and that may be configured as an access node in the communications network.
  • a UE’s access to the communications network may be managed at least in part by the base station, whereby the UE connects with the base station to access the communications network.
  • the base station can be referred to as a gNodeB (gNB) , eNodeB (eNB) , access point, etc.
  • gNB gNodeB
  • eNB eNodeB
  • network as used herein reference to a communications network that includes a set of network nodes configured to provide communications functions to a plurality of user equipment via one or more base stations.
  • the network can be a public land mobile network (PLMN) that implements one or more communication technologies including, for instance, 5G communications.
  • PLMN public land mobile network
  • computer system refers to any type of interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” or “system” may refer to multiple computer devices or multiple computing systems that are communicatively coupled with one another and configured to share computing or networking resources.
  • resource refers to a physical or virtual device, a physical or virtual component within a computing environment, or a physical or virtual component within a particular device, such as computer devices, mechanical devices, memory space, processor/CPU time, processor/CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input/output operations, ports or network sockets, channel/link allocation, throughput, memory usage, storage, network, database and applications, workload units, or the like.
  • a “hardware resource” may refer to compute, storage, or network resources provided by physical hardware element (s) .
  • a “virtualized resource” may refer to compute, storage, or network resources provided by virtualization infrastructure to an application, device, system, etc.
  • network resource or “communication resource” may refer to resources that are accessible by computer devices/systems via a communications network.
  • system resources may refer to any kind of shared entities to provide services and may include computing or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable.
  • channel refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream.
  • channel may be synonymous with or equivalent to “communications channel, ” “data communications channel, ” “transmission channel, ” “data transmission channel, ” “access channel, ” “data access channel, ” “link, ” “data link, ” “carrier, ” “radio-frequency carrier, ” or any other like term denoting a pathway or medium through which data is communicated.
  • link refers to a connection between two devices for the purpose of transmitting and receiving information.
  • instantiate, ” “instantiation, ” and the like as used herein refer to the creation of an instance.
  • An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code.
  • connection may mean that two or more elements, at a common communication protocol layer, have an established signaling relationship with one another over a communication channel, link, interface, or reference point.
  • network element refers to physical or virtualized equipment or infrastructure used to provide wired or wireless communication network services.
  • network element may be considered synonymous to or referred to as a networked computer, networking hardware, network equipment, network node, virtualized network function, or the like.
  • information element refers to a structural element containing one or more fields.
  • field refers to individual contents of an information element, or a data element that contains content.
  • An information element may include one or more additional information elements.
  • 3GPP Access refers to accesses (e.g., radio access technologies) that are specified by 3GPP standards. These accesses include, but are not limited to, GSM/GPRS, LTE, LTE-A, 5G NR, and/or 6G. In general, 3GPP access refers to various types of cellular access technologies.
  • Non-3GPP Access refers any accesses (e.g., radio access technologies) that are not specified by 3GPP standards. These accesses include, but are not limited to, WiMAX, CDMA2000, Wi-Fi, WLAN, and/or fixed networks. Non-3GPP accesses may be split into two categories, “trusted” and “untrusted. " Trusted non-3GPP accesses can interact directly with an evolved packet core (EPC) and/or a 5G core (5GC) , whereas untrusted non-3GPP accesses interwork with the EPC/5GC via a network entity, such as an Evolved Packet Data Gateway and/or a 5G NR gateway. In general, non-3GPP access refers to various types on non-cellular access technologies.
  • EPC evolved packet core
  • 5GC 5G core
  • 5G NR gateway an Evolved Packet Data Gateway
  • non-3GPP access refers to various types on non-cellular access technologies.
  • FIG. 1 is an illustration 100 of a reduced capability user equipment (RedCap UE) and an extended reduced capability user equipment (eRedCap UE) , according to one or more embodiments.
  • a 3GPP release 17 reduced capability user equipment (RedCap UE) 102 can be configured to have reduced capabilities than a UE, including less peak throughput, longer latency, less reliability, more power consumption efficiency, less system overhead, or fewer resource costs.
  • a 3GPP release 18 extended RedCap UE (eRedCap UE) 104 can be configured to have less capability than the RedCap UE 102.
  • the eRedCap UE 104 can have a reduced complexity in frequency range one (FR1) in relation to RedCap UE 102.
  • FR1 frequency range one
  • the radio access network one (RAN1) , RAN2, and RAN4 aspects for radio frequency (RF) requirements for FR1 for the eRedCap UE 104 can be less complex than for the RedCap UE 102.
  • the eRedCap UE 104 can operate using a 5 MHz bandwidth for physical downlink shared channel (PDSCH) messages (unicast and broadcast) and physical uplink shared channel (PUSCH) , with a 20 MHz RF requirements for uplink (UL) and downlink (DL) transmissions.
  • PDSCH physical downlink shared channel
  • PUSCH physical uplink shared channel
  • the eRedCap 104 can still use the other physical channels and signals with a bandwidth part (BWP) up to 20 MHz maximum RR and baseband (BB) bandwidth.
  • BWP bandwidth part
  • BB baseband
  • the eRedCap UE 104 can be configured for peak data rate reduction.
  • V layers ⁇ Q m ⁇ f ⁇ 4 can be a relaxation of the peak data reduction constraint, V layers ⁇ Q m ⁇ f ⁇ 4, wherein the relaxation of constraint can include changing the value to 1 from a 4 (e.g., V layers ⁇ Q m ⁇ f ⁇ 1) .
  • the arguments for the parameters V layers , Q m , and f can be the same as for the RedCap UE 102, where V layers is a number of multiple-input multiple-output (MIMO) layers, Q m can be a modulation order, and f can be a scaling factor.
  • MIMO multiple-input multiple-output
  • Both 15KHz subcarrier spacing (SCS) and 30 kHz can be supported by the eRedCap UE 104.
  • the existing UE capability framework can be used for the eRedCap UE 104, and changes to UE capability signaling can be specified if necessary.
  • a default position can be that UE capabilities applicable to the RedCap UE 102 can be applicable to the eRedCap UE 104.
  • a RedCap UE 102 and an eRedCap UE are located in a cell 106 with service provided by a base station 108.
  • some networks can support only the RedCap UE 102, only the eRedCap UE 104, or both the RedCap UE 102 and the eRedCap UE 114.
  • the eRedCap UE 104 needs to be able to determine whether the cell 106 supports eRedCap UE capabilities.
  • Embodiments described herein address the above-referenced issues by providing techniques for capability signaling to enable the eRedCap UE 104 to determine whether the cell 106 supports eRedCap UE capabilities and to receive assistance with redirection/reselection in the event that there the cell 106 does not support eRedCap UE capabilities.
  • the techniques described herein include system information block (SIB) information elements (IEs) that can inform the RedCap UE 102 or the eRedCap UE 104, as to which capabilities are supported.
  • the techniques further include IEs that help the RedCap UE 102 or the eRedCap UE 104 to select/reselect the correct serving cell in radio resource control (RRC) IDLE mode/RRC INACTIVE mode.
  • SIB system information block
  • IEs information elements
  • RRC radio resource control
  • Figure 2 is a signaling diagram 200 for determining eRedCap UE accessibility, according to one or more embodiments.
  • an eRedCap UE 202 can receive, from a base station 204, a SIB1 broadcast for a network.
  • the SIB1 can include an indication as to whether the cell supports eRedCap UE accessibility.
  • the eRedCap UE 202 can determine that the network supports eRedCap UE accessibility for a cell based on the indication in the SIB1.
  • the indication can be a presence of a bit in a field to indicate the network supports eRedCap UE accessibility. An absence of the bit can be an indication that the network does not support eRedCap UE accessibility for the cell.
  • the indication can be an indication that the network supports RedCap UE accessibility.
  • the eRedCap UE 202 can be configured to assume that the support for RedCap UE accessibility implies support for eRedCap UE accessibility.
  • the SIB1 does not include any RedCap UE IE indicating support of RedCap UE accessibility. Rather, the SIB1 only includes an indication of supporting eRedCap UE accessibility. In some other instances, the indication is a first indication, and the SIB1 further includes a second indication that the eRedCap UE cannot use a RedCap UE camping procedure. It should be noted that a RedCap UE can be expected to ignore eRedCap extensions, and therefore, the RedCap UE is not expected to use an eRedCap UE IE.
  • the indication can be a first indication, where the SIB1 broadcast includes a second indication indicating an accessibility restriction for a RedCap UE, and wherein the eRedCap UE is configured to follow the accessibility restriction.
  • the accessibility restriction can be based on, for example, a UE receiver chain type, such as a one receiver chain UE type or a two receiver chain UE type.
  • the second indication can be for barring a RedCap UE or the eRedCap UE 202 based on a UE receiver chain type.
  • the eRedCap UE 202 can camp on the cell based on determining that the network supports eRedCap UE accessibility.
  • Figure 3 is an example abstract syntax notation 1 (ASN1) code 300 for cell accessibility, according to one or more embodiments.
  • the ASNI code 300 includes a first portion 302 for either barring or not barring a RedCap UE based on a receiver chain type of the RedCap UE.
  • the ASNI code 300 also includes a second portion 304 for either barring or not barring an eRedCap UE based on a receiver chain type of the eRedCap UE.
  • Figure 4 is an example ASN1 code 400 or cell accessibility, according to one or more embodiments.
  • the ASNI code 400 includes a first portion 402 for either barring or not barring an eRedCap UE based on a receiver chain type of the eRedCap UE. It should be noted that the ASNI code 400 does not include an IE for either barring or not barring a RedCap UE based on a receiver chain type of the RedCap UE.
  • FIG. 5 is a signaling diagram 500 for determining eRedCap UE accessibility for intra-frequency cell reselection, according to one or more embodiments.
  • an eRedCap UE 502 can be in operable communication with a base station 504. It should be appreciated that networks that support RedCap UE accessibility are likely to reuse the same frequency for multi-cells. The scope of an eRedCap UE feature can be to continue to use RedCap UE logic for intra-frequency cell reselection, but with a PDSCH/PUSCH reduction, as indicated above. In some networks, however, some cells can be upgraded for eRedCap UE accessibility, while other cells are not.
  • the eRedCap UE 502 can receive from the base station 504, a SIB1 broadcast for a network.
  • the SIB1 can include an indication (e.g., an IE) as to the allowability of eRedCap UE intra-frequency cell reselection.
  • the eRedCap UE 502 can determine whether to search a plurality cells on the same frequency of a current cell for intra-frequency cell reselection based on the IE, where the eRedCap UE is camped on the current cell that is barred for a RedCap UE.
  • intra-frequency cell reselection is allowed for the RedCap UE based on the IE.
  • the eRedCap UE 502 can be configured to consider the allowability of intra-frequency cell reselection for the RedCap UE as an allowability of intra-frequency cell reselection for the eRedCap UE 502.
  • the eRedCap UE 502 can search other cells that are on the same frequency as the current cell.
  • intra-frequency cell reselection for a RedCap UE is not allowed based on the IE.
  • the eRedCap UE 502 can consider that intra-cell reselection for other cells on the same frequency as the current cell for the eRedCap UE is not allowed. Therefore, the eRedCap UE 502 does not search other cells that are on the same frequency as the current cell.
  • the IE in the SIB1 for intra-frequency cell reselection is a first indication directed toward the allowability of intra-frequency cell reselection for a RedCap UE.
  • the eRedCap UE 502 can receive a second indication as to the allowability of intra-frequency cell reselection for the eRedCap UE 502.
  • Figure 6 is an example ASN1 code 600 for intra-frequency cell reselection, according to one or more embodiments.
  • the ASNI code 600 includes a first portion 602 for either allowing or not allowing an eRedCap UE to perform intra-frequency cell reselection.
  • FIG. 7 is a signaling diagram 700 for inter-frequency cell reselection for an eRedCap UE, according to one or more embodiments.
  • an eRedCap UE 702 can be in operable communication with a base station 704.
  • a network can broadcast an indication (e.g., using SIB4) of inter-frequency cell reselection, including a list of SIB4 frequencies to be used for the reselection procedure.
  • the SIB4 broadcast can further include a field for indicating whether the SIB4 frequencies support a RedCap UE inter-frequency cell reselection procedure.
  • the eRedCap UE 702 can receive from the base station 704, an SIB broadcast that includes a list of frequencies for inter-frequency cell reselection.
  • the eRedCap UE 702 can determine to search the list of frequencies based on the SIB broadcast.
  • the list of frequencies is included in an IE for supporting a RedCap UE, and the eRedCap UE 702 considers each frequency of the list of frequencies as a candidate frequency for supporting eRedCap UE 702 inter-frequency cell reselection.
  • the eRedCap UE 702 can then measure the list of frequencies for inter-frequency cell reselection.
  • the list of frequencies is included in an IE for supporting the eRedCap UE 702.
  • the eRedCap UE 702 can consider each frequency of the list of frequencies as a candidate frequency for supporting the eRedCap UE 702.
  • the eRedCap UE 702 can then measure the list of frequencies for inter-frequency cell reselection.
  • the eRedCap UE 702 can determine whether a candidate frequency actually supports the eRedCap UE 702 based on measuring an SIB1 associated with the candidate frequency.
  • the SIB1 can include an indication of supporting eRedCap UE accessibility.
  • Figure 8 is an example ASN1 code 800 for inter-frequency cell reselection, according to one or more embodiments.
  • the ASNI code 800 includes a first portion 802 for allowing an eRedCap UE to perform inter-frequency cell reselection.
  • Figure 9 is a signaling diagram 900 for exchanging frequencies between base stations for inter-frequency cell reselection, according to one or more embodiments.
  • a first base station 902 can be in operable communication with a second base station 904.
  • the first base station 902 can provide service from a cell that neighbors a cell that receives service from the second base station 904.
  • a first base station associated with a first cell can transmit to the second base station 904, an indication of a first frequency that supports eRedCap UE inter-frequency cell reselection.
  • the transmission can be performed using Xn signaling.
  • the first frequency can be associated with the first base station 902.
  • the first base station can receive from the second base station 904 an indication of a second frequency that supports the eRedCap UE inter-frequency cell reselection.
  • the transmission can be performed using Xn signaling.
  • the second frequency can be associated with the second base station 904.
  • the first base station 902 can broadcast the indication of the first frequency and the indication of the second frequency.
  • An eRedCap UE receiving the broadcast can determine that both the first frequency and the second frequency support eRedCap UE inter-frequency cell reselection.
  • the second base station 904 can also broadcast the indication of the first frequency and the indication of the second frequency.
  • An eRedCap UE receiving the broadcast can again determine that both the first frequency and the second frequency support eRedCap UE inter-frequency cell reselection.
  • Figure 10 is a narrative 1000 describing that an IE carried over a SIB1 broadcast of a corresponding cell, according to one or more embodiments.
  • the narrative 1000 indicates that the corresponding cell supports RedCap UE inter-frequency cell reselection.
  • An eRedCap UE can be configured to assume that if the corresponding cell supports RedCap UE inter-frequency cell reselection, then the corresponding cell supports eRedCap UE inter-frequency cell reselection.
  • FIG 11 is a signaling diagram for a cell that does not support an eRedCap UE, according to one or more embodiments.
  • a new radio (NR) cell 1102 can transmit an SIB1 1104 with no 3GPP release 18 IEs for an eRedCap UE 1106.
  • the NR cell 1102 can support accessibility for a 3GPP release 17 RedCap UE 1108.
  • the 3GPP release 17 RedCap UE 1108 can engage in a registration procedure and exchange UE capability information with a core network (CN) 1110.
  • the 3GPP release 17 RedCap UE 1108 can further be configured by the NR cell 1102 based on the UE’s capabilities.
  • FIG. 12 is a signaling diagram for a cell that does support an eRedCap UE, according to one or more embodiments.
  • a new radio (NR) cell 1202 can transmit an SIB1 1204 with 3GPP release 17 IEs for a RedCap UE 1206 and 3GPP release 18 IEs for an eRedCap UE 1208.
  • the NR cell 1202 can support accessibility for the 3GPP release 17 RedCap UE 1206 and accessibility for the 3GPP release 18 eRedCap UE 1208.
  • the 3GPP release 18 eRedCap UE 1208 can engage in a registration procedure and exchange UE capability information with a core network (CN) 1210.
  • the 3GPP release 18 eRedCap UE 1208 can further be configured by the NR cell 1202 based on the UE’s capabilities.
  • Figure 13 is a process flow 1300 for determining eRedCap UE accessibility for a cell, according to one or more embodiments.
  • a method can include an eRedCap UE receiving, from a base station, a SIB1 broadcast for a network.
  • the SIB1 can include an indication as to whether the cell supports eRedCap UE accessibility.
  • the method can include the eRedCap UE determining that the network supports eRedCap UE accessibility for a cell based on the indication in the SIB1.
  • the indication can be a presence of a bit in a field to indicate the network supports eRedCap UE accessibility. An absence of the bit can be an indication that the network does not support eRedCap UE accessibility for the cell.
  • the indication can be an indication that the network supports RedCap UE accessibility.
  • the eRedCap UE can be configured to assume that the support for RedCap UE accessibility implies support for eRedCap UE accessibility.
  • the SIB1 does not include any RedCap UE IE indicating support of RedCap UE accessibility. Rather, the SIB1 only includes an indication of supporting eRedCap UE accessibility. In some other instances, the indication is a first indication, and the SIB1 further includes a second indication that the eRedCap UE cannot use a RedCap UE camping procedure. It should be noted that a RedCap UE can be expected to ignore eRedCap UE extensions, and therefore, the RedCap UE is not expected to use an eRedCap UE IE.
  • the indication can be a first indication, where the SIB1 broadcast includes a second indication indicating an accessibility restriction for a RedCap UE, and wherein the eRedCap UE is configured to follow the accessibility restriction.
  • the accessibility restriction can be based on, for example, a UE receiver chain type, such as a one receiver chain UE type or a two receiver chain UE type.
  • the second indication can be for barring a RedCap UE or the eRedCap UE based on a UE receiver chain type.
  • the method can include the eRedCap UE camping on the cell based on determining that the network supports eRedCap UE accessibility for the cell.
  • FIG. 14 illustrates receive components 1400 of the UE 1406, in accordance with some embodiments.
  • the receive components 1400 may include an antenna panel 1404 that includes a number of antenna elements.
  • the panel 1404 is shown with four antenna elements, but other embodiments may include other numbers.
  • the antenna panel 1404 may be coupled to analog beamforming (BF) components that include a number of phase shifters 1408 (1) –1408 (4) .
  • the phase shifters 1408 (1) –1408 (4) may be coupled with a radio-frequency (RF) chain 1412.
  • the RF chain 1412 may amplify a receive analog RF signal, downconvert the RF signal to baseband, and convert the analog baseband signal to a digital baseband signal that may be provided to a baseband processor for further processing.
  • control circuitry which may reside in a baseband processor, may provide BF weights (e.g., W1 –W4) , which may represent phase shift values, to the phase shifters 1408 (1) –1408 (4) to provide a receive beam at the antenna panel 1404.
  • BF weights e.g., W1 –W4
  • W1 –W4 may represent phase shift values
  • FIG 15 illustrates a UE 1500, in accordance with some embodiments.
  • the UE 1500 may be similar to and substantially interchangeable with UE 1406 of Figure 14.
  • the UE 1500 may be any mobile or non-mobile computing device, such as, for example, mobile phones, computers, tablets, industrial wireless sensors (for example, microphones, carbon dioxide sensors, pressure sensors, humidity sensors, thermometers, motion sensors, accelerometers, laser scanners, fluid level sensors, inventory sensors, electric voltage/current meters, actuators, etc. ) , video surveillance/monitoring devices (for example, cameras, video cameras, etc. ) , wearable devices, or relaxed-IoT devices.
  • the UE may be a reduced capacity UE or NR-Light UE.
  • the components of the UE 1500 may be coupled with various other components over one or more interconnects 1532, which may represent any type of interface, input/output, bus (local, system, or expansion) , transmission line, trace, optical connection, etc. that allows various circuit components (on common or different chips or chipsets) to interact with one another.
  • interconnects 1532 may represent any type of interface, input/output, bus (local, system, or expansion) , transmission line, trace, optical connection, etc. that allows various circuit components (on common or different chips or chipsets) to interact with one another.
  • the processors 1504 may include processor circuitry such as, for example, baseband processor circuitry (BB) 1504A, central processor unit circuitry (CPU) 1504B, and graphics processor unit circuitry (GPU) 1504C.
  • the processors 1504 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions, such as program code, software modules, or functional processes from memory/storage 1512 to cause the UE 1500 to perform operations as described herein.
  • the baseband processor circuitry 1504A may access a communication protocol stack 1536 in the memory/storage 1512 to communicate over a 3GPP compatible network.
  • the baseband processor circuitry 1504A may access the communication protocol stack to: perform user plane functions at a PHY layer, MAC layer, RLC layer, PDCP layer, SDAP layer, and PDU layer; and perform control plane functions at a PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and a non-access stratum “NAS” layer.
  • the PHY layer operations may additionally/alternatively be performed by the components of the RF interface circuitry 1508.
  • the baseband processor circuitry 1504A may generate or process baseband signals or waveforms that carry information in 3GPP-compatible networks.
  • the waveforms for NR may be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and discrete Fourier transform spread OFDM (DFT-S-OFDM) in the uplink.
  • CP-OFDM cyclic prefix OFDM
  • DFT-S-OFDM discrete Fourier transform spread OFDM
  • the baseband processor circuitry 1504A may also access group information 1524 from memory/storage 1512 to determine search space groups in which a number of repetitions of a PDCCH may be transmitted.
  • the memory/storage 1512 may include any type of volatile or non-volatile memory that may be distributed throughout the UE 1500. In some embodiments, some of the memory/storage 1512 may be located on the processors 1504 themselves (for example, L1 and L2 cache) , while other memory/storage 1512 is external to the processors 1504 but accessible thereto via a memory interface.
  • the memory/storage 1512 may include any suitable volatile or non-volatile memory such as, but not limited to, dynamic random access memory (DRAM) , static random access memory (SRAM) , erasable programmable read only memory (EPROM) , electrically erasable programmable read only memory (EEPROM) , Flash memory, solid-state memory, or any other type of memory device technology.
  • DRAM dynamic random access memory
  • SRAM static random access memory
  • EPROM erasable programmable read only memory
  • EEPROM electrically erasable programmable read only memory
  • Flash memory solid-state memory, or any other type of
  • the RF interface circuitry 1508 may include transceiver circuitry and a radio frequency front module (RFEM) that allows the UE 1500 to communicate with other devices over a radio access network.
  • RFEM radio frequency front module
  • the RF interface circuitry 1508 may include various elements arranged in transmit or receive paths. These elements may include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, control circuitry, etc.
  • the RFEM may receive a radiated signal from an air interface via an antenna 1524 and proceed to filter and amplify (with a low-noise amplifier) the signal.
  • the signal may be provided to a receiver of the transceiver that down-converts the RF signal into a baseband signal that is provided to the baseband processor of the processors 1504.
  • the transmitter of the transceiver up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM.
  • the RFEM may amplify the RF signal through a power amplifier prior to the signal being radiated across the air interface via the antenna 1524.
  • the RF interface circuitry 1508 may be configured to transmit/receive signals in a manner compatible with NR access technologies.
  • the antenna 1524 may include a number of antenna elements that each convert electrical signals into radio waves to travel through the air and to convert received radio waves into electrical signals.
  • the antenna elements may be arranged into one or more antenna panels.
  • the antenna 1524 may have antenna panels that are omnidirectional, directional, or a combination thereof to enable beamforming and multiple input, multiple output communications.
  • the antenna 1524 may include microstrip antennas, printed antennas fabricated on the surface of one or more printed circuit boards, patch antennas, phased array antennas, etc.
  • the antenna 1524 may have one or more panels designed for specific frequency bands including bands in FR1 or FR2.
  • the user interface circuitry 1516 includes various input/output (I/O) devices designed to enable user interaction with the UE 1500.
  • the user interface 1516 includes input device circuitry and output device circuitry.
  • Input device circuitry includes any physical or virtual means for accepting an input including, inter alia, one or more physical or virtual buttons (for example, a reset button) , a physical keyboard, keypad, mouse, touchpad, touchscreen, microphones, scanner, headset, or the like.
  • the output device circuitry includes any physical or virtual means for showing information or otherwise conveying information, such as sensor readings, actuator position (s) , or other like information.
  • Output device circuitry may include any number or combinations of audio or visual display, including, inter alia, one or more simple visual outputs/indicators (for example, binary status indicators such as light emitting diodes (LEDs) and multi-character visual outputs, or more complex outputs such as display devices or touchscreens (for example, liquid crystal displays (LCDs) , LED displays, quantum dot displays, projectors, etc. ) , with the output of characters, graphics, multimedia objects, and the like being generated or produced from the operation of the UE 1500.
  • simple visual outputs/indicators for example, binary status indicators such as light emitting diodes (LEDs) and multi-character visual outputs, or more complex outputs such as display devices or touchscreens (for example, liquid crystal displays (LCDs) , LED displays, quantum dot displays, projectors, etc.
  • LCDs liquid crystal displays
  • LED displays for example, LED displays, quantum dot displays, projectors, etc.
  • the sensors 1520 may include devices, modules, or subsystems whose purpose is to detect events or changes in its environment and send the information (sensor data) about the detected events to some other device, module, subsystem, etc.
  • sensors include, inter alia, inertia measurement units comprising accelerometers; gyroscopes; or magnetometers; microelectromechanical systems or nanoelectromechanical systems comprising 3-axis accelerometers; 3-axis gyroscopes; or magnetometers; level sensors; flow sensors; temperature sensors (for example, thermistors) ; pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (for example; cameras or lensless apertures) ; light detection and ranging sensors; proximity sensors (for example, infrared radiation detector and the like) ; depth sensors; ambient light sensors; ultrasonic transceivers; microphones or other like audio capture devices; etc.
  • inertia measurement units comprising accelerometers; gyroscopes; or magnet
  • the driver circuitry 1522 may include software and hardware elements that operate to control particular devices that are embedded in the UE 1500, attached to the UE 1500, or otherwise communicatively coupled with the UE 1500.
  • the driver circuitry 1522 may include individual drivers allowing other components to interact with or control various input/output (I/O) devices that may be present within, or connected to, the UE 1500.
  • I/O input/output
  • driver circuitry 1522 may include a display driver to control and allow access to a display device, a touchscreen driver to control and allow access to a touchscreen interface, sensor drivers to obtain sensor readings of sensor circuitry 1520 and control and allow access to sensor circuitry 1520, drivers to obtain actuator positions of electro-mechanic components or control and allow access to the electro-mechanic components, a camera driver to control and allow access to an embedded image capture device, audio drivers to control and allow access to one or more audio devices.
  • a display driver to control and allow access to a display device
  • a touchscreen driver to control and allow access to a touchscreen interface
  • sensor drivers to obtain sensor readings of sensor circuitry 1520 and control and allow access to sensor circuitry 1520
  • drivers to obtain actuator positions of electro-mechanic components or control and allow access to the electro-mechanic components drivers to obtain actuator positions of electro-mechanic components or control and allow access to the electro-mechanic components
  • a camera driver to control and allow access to an embedded image capture device
  • audio drivers to control and allow access
  • the PMIC 1524 may manage power provided to various components of the UE 1500.
  • the PMIC 1524 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.
  • the PMIC 1524 may control, or otherwise be part of, various power saving mechanisms of the UE 1500. For example, if the platform UE is in an RRC_Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the UE 1500 may power down for brief intervals of time and thus save power. If there is no data traffic activity for an extended period of time, then the UE 1500 may transition off to an RRC_Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc.
  • DRX Discontinuous Reception Mode
  • the UE 1500 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again.
  • the UE 1500 may not receive data in this state; in order to receive data, it must transition back to RRC_Connected state.
  • An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours) . During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.
  • a battery 1528 may power the UE 1500, although in some examples the UE 1500 may be mounted deployed in a fixed location, and may have a power supply coupled to an electrical grid.
  • the battery 1528 may be a lithium ion battery, a metal-air battery, such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, and the like. In some implementations, such as in vehicle-based applications, the battery 1528 may be a typical lead-acid automotive battery.
  • FIG 16 illustrates a gNB 1600, in accordance with some embodiments.
  • the gNB node 1600 may be similar to and substantially interchangeable with the base stations 164, 166 of Figure 1.
  • the gNB 1600 may include processors 1604, RF interface circuitry 1608, core network (CN) interface circuitry 1612, and memory/storage circuitry 1616.
  • processors 1604, RF interface circuitry 1608, core network (CN) interface circuitry 1612, and memory/storage circuitry 1616 may include processors 1604, RF interface circuitry 1608, core network (CN) interface circuitry 1612, and memory/storage circuitry 1616.
  • CN core network
  • the components of the gNB 1600 may be coupled with various other components over one or more interconnects 1628.
  • the processors 1604, RF interface circuitry 1608, memory/storage circuitry 1616 (including communication protocol stack 1610) , antenna 1624, and interconnects 1628 may be similar to like-named elements shown and described with respect to Figure 14.
  • the CN interface circuitry 1612 may provide connectivity to a core network, for example, a 4th Generation Core network (5GC) using a 4GC-compatible network interface protocol such as carrier Ethernet protocols, or some other suitable protocol.
  • Network connectivity may be provided to/from the gNB 1600 via a fiber optic or wireless backhaul.
  • the CN interface circuitry 1612 may include one or more dedicated processors or FPGAs to communicate using one or more of the aforementioned protocols.
  • the CN interface circuitry 1612 may include multiple controllers to provide connectivity to other networks using the same or different protocols.
  • personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users.
  • personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.
  • At least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, or methods as set forth in the example section below.
  • the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below.
  • circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.
  • Example 1 includes a method performed by an extended reduced capability user equipment (eRedCap UE) , the method comprising: receiving a system information block one (SIB1) broadcast for a network; determining that the network supports eRedCap UE accessibility for a cell based on an indication in the SIB1; and camping on the cell based on determining that the network supports eRedCap UE accessibility for the cell.
  • SIB1 system information block one
  • Example 2 includes the method of example 1, wherein the indication is a presence of a bit in a field to indicate the network supports eRedCap UE accessibility for the cell, and wherein in an absence of the bit is an indication that the network does not support eRedCap UE accessibility for the cell.
  • Example 3 includes the method of example 1 or 2, wherein the indication is to indicate that the network supports reduced capability user equipment (RedCap UE) accessibility.
  • RedCap UE reduced capability user equipment
  • Example 4 includes the method any of examples 1-3, wherein the SIB1 does not include any RedCap UE information element (IE) indicating support of RedCap UE accessibility.
  • IE RedCap UE information element
  • Example 5 includes the method any of examples 1-3, wherein the indication is a first indication, and wherein the SIB1 includes a second indication that the eRedCap UE cannot use a RedCap UE camping procedure.
  • Example 6 includes the method any of examples 1-3, wherein the eRedCap UE supports a RedCap UE feature, wherein the indication is a first indication, wherein the SIB1 includes a second indication that the eRedCap UE is not to use an eRedCap UE information element (IE) to support the RedCap UE feature.
  • IE eRedCap UE information element
  • Example 7 includes the method any of examples 1-3, wherein the indication is a first indication, wherein the SIB1 broadcast includes a second indication indicating an accessibility restriction for a RedCap UE, and wherein the eRedCap UE is configured to follow the accessibility restriction.
  • Example 8 includes the method any of examples 1-3, wherein the indication is a first indication, wherein the SIB1 broadcast includes a second indication for barring the eRedCap UE based on a UE receiver chain type.
  • Example 9 includes the method of example 7, wherein the UE receiver chain type is a one receiver chain UE type or a two receiver chain UE type.
  • Example 10 includes a user equipment (UE) comprising: one or more processors; a communication interface; radio frequency (RF) interface circuitry; and a computer-readable medium including instructions that, when executed by the one or more processors, cause the UE to perform one or more elements described in or related to any of examples 1-9.
  • UE user equipment
  • RF radio frequency
  • Example 11 includes a non-transitory computer-readable media comprising instructions to cause a network, upon execution of the instructions by one or more processors of the network, to perform one or more elements described in or related to any of examples 1-9.
  • Example 12 includes an extended reduced capability user equipment (eRedCap UE) , comprising: one or more processors; a communication interface; radio frequency (RF) interface circuitry; and a computer-readable medium including instructions that, when executed by the one or more processors, cause the eRedCap UE to: receive a system information (SIB) broadcast that includes an information element (IE) for an allowability of intra-frequency cell reselection for a reduced capability user equipment (RedCap UE) ; and determine whether to search a plurality cells on the same frequency of a current cell for intra-frequency cell reselection based on the IE.
  • SIB system information
  • IE information element
  • Example 13 includes the eRedCap UE of example 12, wherein intra-frequency cell reselection is allowed for the RedCap UE based on the IE, wherein the eRedCap UE is configured to consider the allowability of intra-frequency cell reselection for the RedCap UE as an allowability of intra-frequency cell reselection for the eRedCap UE, and wherein the eRedCap UE searches other cells that are on the same frequency as the current cell.
  • Example 14 includes the eRedCap UE of example 12, wherein intra-frequency cell reselection for the RedCap UE is not allowed based on the IE, and wherein the eRedCap UE considers that intra-cell reselection for other cells on the same frequency as the current cell for the eRedCap UE is not allowed.
  • Example 15 includes the eRedCap UE of example 12, wherein the IE for intra-frequency cell reselection is a first indication, and wherein the eRedCap UE receives a second indication as to the allowability of intra-frequency cell reselection for the eRedCap UE.
  • Example 16 includes a method including performing one or more elements examples 12-15.
  • Example 17 includes a non-transitory computer-readable media comprising instructions to cause a network, upon execution of the instructions by one or more processors of the network, to perform one or more elements described in or related to examples 12-15.
  • Example 18 includes an extended reduced capability user equipment (eRedCap UE) , comprising: one or more processors; a communication interface; radio frequency (RF) interface circuitry; and a computer-readable medium including instructions that, when executed by the one or more processors, cause the eRedCap UE to: receive a system information (SIB) broadcast that includes a list of frequencies for inter-frequency cell reselection; and determine to search the list of frequencies for inter-frequency cell reselection based on the SIB broadcast.
  • SIB system information
  • Example 19 includes the eRedCap UE of example 18, wherein the list of frequencies is included in an information element (IE) for supporting a reduced capability user equipment (RedCap UE) , and wherein the eRedCap UE considers each frequency of the list of frequencies as a candidate frequency for supporting the eRedCap UE, and wherein the instructions that, when executed by the one or more processors, further cause the eRedCap UE to measure the list of frequencies for inter-frequency cell reselection.
  • IE information element
  • RedCap UE reduced capability user equipment
  • Example 20 includes the eRedCap UE of example 18 or 19, wherein the list of frequencies is included in an information element for supporting an eRedCap UE, wherein the eRedCap UE considers each frequency of the list of frequencies as a candidate frequency for supporting the eRedCap UE, and wherein the instructions that, when executed by the one or more processors, further cause the eRedCap UE to measure the list of frequencies for inter-frequency cell reselection.
  • Example 21 includes the eRedCap UE of any of examples 18-20, wherein the eRedCap UE determines that a frequency of the list of frequencies supports eRedCap UE accessibility based on an SIB1 broadcast associated with the frequency.
  • Example 22 includes a method including performing one or more elements of examples 18-21.
  • Example 23 includes a non-transitory computer-readable media comprising instructions to cause a network, upon execution of the instructions by one or more processors of the network, to perform one or more elements of examples 18-21.
  • Example 24 includes a first base station, comprising: one or more processors; a communication interface; radio frequency (RF) interface circuitry; and a computer-readable medium including instructions that, when executed by the one or more processors, cause the first base station to: transmit, to a second base station, an indication of a first frequency that supports eRedCap UE inter-frequency cell reselection, receive, from the second base station, an indication of a second frequency that supports the eRedCap UE inter-frequency cell reselection.
  • RF radio frequency
  • Example 25 includes the first base station of example 24, wherein the first base station transmits the indication of the first frequency to the second base station using Xn signaling.
  • Example 26 includes the first base station of example 24 or 25, wherein the instructions that, when executed by the one or more processors, further cause the first base station to broadcast the indication of the first frequency and indication of the second frequency.
  • Example 27 includes a method including performing one or more elements of examples 24-26.
  • Example 28 includes a non-transitory computer-readable media comprising instructions to cause a network, upon execution of the instructions by one or more processors of the network, to perform one or more elements of examples 24-26.

Landscapes

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

Abstract

L'invention concerne des techniques d'accessibilité à un équipement utilisateur à capacité réduite étendue (UE eRedCap). Un procédé donné à titre d'exemple peut consister à recevoir, par un UE eRedCap, un bloc d'informations de système 1 (SIB1) diffusé pour un réseau. L'UE eRedCap peut déterminer que le réseau prend en charge une accessibilité à l'UE eRedCap pour une cellule sur la base d'une indication dans le SIB1. L'UE eRedCap peut résider sur la cellule sur la base de la détermination selon laquelle le réseau prend en charge l'accessibilité à l'UE eRedCap pour la cellule.
PCT/CN2023/076004 2023-02-14 2023-02-14 Accessibilité à un équipement utilisateur à capacité réduite étendue dans des cellules WO2024168539A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/076004 WO2024168539A1 (fr) 2023-02-14 2023-02-14 Accessibilité à un équipement utilisateur à capacité réduite étendue dans des cellules

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/076004 WO2024168539A1 (fr) 2023-02-14 2023-02-14 Accessibilité à un équipement utilisateur à capacité réduite étendue dans des cellules

Publications (1)

Publication Number Publication Date
WO2024168539A1 true WO2024168539A1 (fr) 2024-08-22

Family

ID=92421928

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/076004 WO2024168539A1 (fr) 2023-02-14 2023-02-14 Accessibilité à un équipement utilisateur à capacité réduite étendue dans des cellules

Country Status (1)

Country Link
WO (1) WO2024168539A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022027407A1 (fr) * 2020-08-06 2022-02-10 Zte Corporation Procédés, appareil et systèmes de programmation et de transmission d'informations système dans une communication sans fil
WO2022241373A1 (fr) * 2021-05-10 2022-11-17 Qualcomm Incorporated Mesures efficaces de gestion de ressources radio pour équipement utilisateur à capacité réduite

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022027407A1 (fr) * 2020-08-06 2022-02-10 Zte Corporation Procédés, appareil et systèmes de programmation et de transmission d'informations système dans une communication sans fil
WO2022241373A1 (fr) * 2021-05-10 2022-11-17 Qualcomm Incorporated Mesures efficaces de gestion de ressources radio pour équipement utilisateur à capacité réduite

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Identification and access restriction of RedCap UE", 3GPP DRAFT; R2-2109577, vol. RAN WG2, 22 October 2021 (2021-10-22), pages 1 - 5, XP052066057 *
QUALCOMM INCORPORATED: "Access and camping restriction for RedCap UEs", 3GPP DRAFT; R2-2104775, vol. RAN WG2, 11 May 2021 (2021-05-11), pages 1 - 6, XP052006537 *

Similar Documents

Publication Publication Date Title
KR102713889B1 (ko) 이웃 셀 송신 구성 표시자(tci) 상태 스위치
US20220304036A1 (en) Unsynchronized multi-transmission reception point scheduling operation
US20220046443A1 (en) Channel state information-reference signal based measurement
US11917652B2 (en) Carrier aggregation in a high speed mode of a user equipment
US20230040675A1 (en) Data transmission in an inactive state
US20220330066A1 (en) Dynamic measurement period for wireless communications in a high-speed mode
WO2022081287A1 (fr) Surveillance de liaison radio dans des réseaux comprenant des parties de bande passante spécifiques au faisceau
US20230087707A1 (en) Serving cell measurements in idle mode
WO2024055298A1 (fr) Technologies de sélection et de resélection de cellule dans des réseaux d'économie d'énergie de réseau
WO2022232966A1 (fr) Amélioration de la lecture d'identifiant global de cellule
WO2024168539A1 (fr) Accessibilité à un équipement utilisateur à capacité réduite étendue dans des cellules
US20240056846A1 (en) Load balancing in new radio
US20230370966A1 (en) Smart cell selection
WO2024031257A1 (fr) Règles de politique de sélection de routage (ursp) d'équipement utilisateur (ue) pour un ue itinérant
US20240007891A1 (en) Technologies for autonomous serving cell measurement
US20240098644A1 (en) Reporting and triggering for low-power wake-up signal monitoring
WO2024207261A1 (fr) Changement de nœud primaire tout en maintenant des nœuds secondaires candidats pour une mobilité améliorée
WO2024168458A1 (fr) Défaillance de liaison radio et défaillance de transfert dans une mobilité de couche 1/couche 2
WO2024020939A1 (fr) Fourniture de service vocal pour itinérance inter-opérateurs
US20240098645A1 (en) Low-power wake-up signal monitoring
US20240032095A1 (en) Technologies for listen-before-talk indication in high-frequency networks
US11979828B2 (en) Interruption mechanism for deactivated secondary cell measurement
US20240031950A1 (en) Power headroom report trigger for simultaneous multi-panel transmission
WO2024207255A1 (fr) Réinitialisation de commande d'accès au support (mac) et/ou réinitialisation de commande de liaison radio (rlc) pour mobilité de couche 1 ou couche 2
WO2022151232A1 (fr) Protection de transmission en cours et gestion d'interférence

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

Country of ref document: EP

Kind code of ref document: A1