WO2022087276A1 - Commutation bwp basée sur le rrc pour les porteuses composantes uniques et multiples - Google Patents

Commutation bwp basée sur le rrc pour les porteuses composantes uniques et multiples Download PDF

Info

Publication number
WO2022087276A1
WO2022087276A1 PCT/US2021/056069 US2021056069W WO2022087276A1 WO 2022087276 A1 WO2022087276 A1 WO 2022087276A1 US 2021056069 W US2021056069 W US 2021056069W WO 2022087276 A1 WO2022087276 A1 WO 2022087276A1
Authority
WO
WIPO (PCT)
Prior art keywords
scell
bwp
time duration
predetermined time
activated
Prior art date
Application number
PCT/US2021/056069
Other languages
English (en)
Inventor
Hua Li
Andrey Chervyakov
Rui Huang
Ilya BOLOTIN
Original Assignee
Intel Corporation
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 Intel Corporation filed Critical Intel Corporation
Publication of WO2022087276A1 publication Critical patent/WO2022087276A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0096—Indication of changes in allocation
    • H04L5/0098—Signalling of the activation or deactivation of component carriers, subcarriers or frequency bands
    • 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/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
    • 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/0032—Distributed allocation, i.e. involving a plurality of allocating devices, each making partial allocation
    • 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/0078—Timing of allocation
    • H04L5/0082—Timing of allocation at predetermined intervals
    • 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/0001—Arrangements for dividing the transmission path
    • H04L5/0014—Three-dimensional division
    • H04L5/0023—Time-frequency-space
    • 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/0058—Allocation criteria
    • H04L5/0064—Rate requirement of the data, e.g. scalable bandwidth, data priority

Definitions

  • Embodiments pertain to wireless communications. Some embodiments relate to wireless networks including 3GPP (Third Generation Partnership Project) and fifth-generation (5G) networks including 5G new radio (NR) (or 5G-NR) networks. Some embodiments relate to bandwidth-part (BWP) switching.
  • 3GPP Third Generation Partnership Project
  • 5G Fifth Generation Partnership Project
  • 5G fifth-generation
  • NR 5G new radio
  • BWP bandwidth-part
  • BWPs Bandwidth Parts
  • 3GPP Release 15 for dynamically adapting the carrier bandwidth and numerology in which a UE operates.
  • BWPs allow multiple services per carrier. Delays associated with BWP switching may impact performance.
  • FIG. 1 A illustrates an architecture of a network, in accordance with some embodiments.
  • FIG. IB and FIG. IC illustrate a non-roaming 5G system architecture in accordance W'ith some embodiments.
  • FIG. 2 is a functional block diagram of a wireless communication device in accordance with some embodiments.
  • Embodiments disclosed herein relate to bandwidth part (BWP) switching. Some embodiments relate to BWP switching for single component carriers (CCs) and some embodiments relate to BWP switching for multiple CCs. These embodiments are described in more detail below.
  • BWP bandwidth part
  • Some embodiments are directed to a user equipment (UE) configured for operation in a fifth -generation (5G) new radio (NR) network.
  • the UE is configured to decode an radio-resource control (RRC) reconfiguration message from a generation node B (gNB) comprising a firstActiveDownlinkBWP-id for switching an active bandwidth part (BWP) (i.e., BWP switching).
  • RRC radio-resource control
  • gNB generation node B
  • BWP-id active bandwidth part
  • the UE may switch the active BWP (i.e., perform the BWP switch) within a first predetermined time duration (i.e., within a switching delay requirement).
  • the firstActiveDownlinkBWP-id may indicate an ID of a downlink (DL) BWP to be used upon activation of the SCell.
  • the configured SCell is in a deactivated status (i.e., a deactivated SCell)
  • the first predetermined time duration for performing the BWP switch begins after the configured SCell is activated.
  • the starting point to switch the active BWP begins when a deactivated SCell is activated.
  • the first predetermined time duration for performing the BWP switch may begin after deactivation of the activated SCell and activation of a new SCell.
  • the starting point to switch the active BWP begins after an activated SCell is deactivated and a new SCell is activated. Accordingly, the total time for the BWP switch depends on whether the configured SCell is deactivated or activated when the BWP switch is triggered.
  • the UE may be configured with a single CC, although the scope of the embodiments is not limited in this respect.
  • the first predetermined time duration for performing the BWP switch may be for switching the active BWT of the configured PCeli or a configured PSCell.
  • the switching delay requirement is applied for a PCeli or PSCell.
  • the UE if the UE is able to switch the active BWP within the first predetermined time duration, the UE is able to receive either a physical downlink control channel (PDCCH) or a physical downlink shared channel (PDSCH) for a newly-acti vated downlink (DL) BWP within the first predetermined time duration.
  • the first predetermined time duration may be calculated as follows:
  • the UE when the UE is configured for an SCell and the configured SCell is in the deactivated status, the UE may switch the active BWP within a total time duration that includes the first predetermined time duration and a time duration for activating the configured SCell. In these embodiments, when the UE is configured for an SCell and the configured SCell is in the activated status, the UE may switch the active BWP within a total time duration that includes deactivation of the activated SCell and activation of the new SCell. In these embodiments, the switching delay requirement may be increased to allow for activating a configured SCell or deactivating an activated SCell and activating a new SCell.
  • the UE may decode a medium-access control layer (MAC) control element (MAC-CE) received from the gNB.
  • the MAC-CE may be encoded to at least one of activate the deactivated SCell, deactivate the activated SCell, and activate the new SCell.
  • the UE when the UE is configured for the PCell and not configured for the SCell, the UE may switch the active BWP in response to receipt of the RRC signalling. In these embodiments, when the UE is configured for the SCell, the UE may switch the active BWP in response to activation of the SCell or the new SCell.
  • the UE when the UE is configured for multiple component carriers (CCs) and when the RRC signalling indicates B WP switching for the multiple CCs comprising the PCell and the SCell, the UE may perform the BWP switch for the PCell within the first predetermined time duration and perform the BWP switch for the SCell within a second predetermined time duration that is greater that the first predetermined time duration.
  • the second predetermined time duration may be dependent on whether the configured SCell is in the deactivated status or the activated status.
  • the UE when the UE is configured for multiple component carriers (CCs) and when the RRC signalling indicates BWP switching for the multiple CCs comprising multiple SCells, the UE may perform the BWP switch for each of SCell within a second predetermined time duration that is greater that the first predetermined time duration upon activation of each SCell.
  • CCs component carriers
  • RRC signalling indicates BWP switching for the multiple CCs comprising multiple SCells
  • the UE may perform the BWP switch for each of SCell within a second predetermined time duration that is greater that the first predetermined time duration upon activation of each SCell.
  • the UE may include a baseband processor and memory to store the firstActiveDownlinkBWP-id.
  • Some embodiments are directed to a non-transitory computer- readable storage medium that stores instructions for execution by processing circuitry of a user equipment (UE) configured for operation in a fifth-generation (5G) new radio (NR) network.
  • the UE may be configured for RRC triggered BWP switching within predetermined time periods depending on whether the UE is configured for an SCell, whether a configured SCell is deactivated or activated, and whether the BWP switching is for a single or multiple CCs.
  • Some embodiments are directed to a generation node B (gNB) configured for operation in a fifth-generation (5G) new radio (NR) network.
  • the gNB may encode an radio-resource control (RRC) reconfiguration message for transmission to a user equipment (UE) comprising a firstActiveDownlinkBWP-id for switching an active bandwidth part (BWP).
  • RRC radio-resource control
  • UE user equipment
  • BWP active bandwidth part
  • the firstActiveDownlinkBWP-id indicates an ID of a downlink (DL) BWP to be used upon activation of the SCell.
  • the gNB may encode a medium-access control layer (MAC) control element (MAC-CE) for transmission to the UE to activate the SCell.
  • MAC-CE medium-access control layer
  • the gNB may decode either a physical downlink control channel (PDCCH) or a physical downlink shared channel (PDSCH) for the activated downlink (DL) BWP after a first predetermined time duration upon activation of the SCell.
  • PDCCH physical downlink control channel
  • PDSCH physical downlink shared channel
  • the first predetermined time duration may begin after the configured SCell is activated. In some embodiments, when the configured SCell is in an activated status, the first predetermined time duration may begin after deactivation of the activated SCell and activation of a new SCell. These embodiments are described in more detail below.
  • FIG. 1 A illustrates an architecture of a network in accordance with some embodiments.
  • the network 140 A is shown to include user equipment (UE) 101 and UE 102.
  • the UEs 101 and 102 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) but may also include any mobile or non-mobile computing device, such as Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, drones, or any other computing device including a wired and/or wireless communications interface.
  • PDAs Personal Data Assistants
  • the UEs 101 and 102 can be collectively referred to herein as UE 101, and EE 101 can be used to perform one or more of the techniques disclosed herein.
  • Any of the radio links described herein may operate according to any exemplary radio communication technology and/or standard.
  • LTE and LTE-Advanced are standards for wireless communications of high-speed data for UE such as mobile telephones.
  • carrier aggregation is a technology according to which multiple carrier signals operating on different frequencies may be used to carry communications for a single UE, thus increasing the bandwidth available to a single device.
  • carrier aggregation may be used where one or more component carriers operate on unlicensed frequencies.
  • Embodiments described herein can be used in the context of any spectrum management scheme including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as Licensed Shared Access (ESA) in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz, and further frequencies and Spectrum Access System (SAS) in 3.55-3.7 GHz and further frequencies).
  • ESA Licensed Shared Access
  • SAS Spectrum Access System
  • Embodiments described herein can also be applied to different Single Carrier or OFDM flavors (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, etc.) and in particular 3GPP NR (New Radio) by allocating the OFDM earner data bit vectors to the corresponding symbol resources.
  • CP-OFDM Single Carrier or OFDM flavors
  • SC-FDMA SC-FDMA
  • SC-OFDM filter bank-based multicarrier
  • OFDMA filter bank-based multicarrier
  • 3GPP NR New Radio
  • any of the UEs 101 and 102 can comprise an Internet-of-Things (loT) UE or a Cellular loT (CIoT) UE, which can comprise a network access layer designed for low-power loT applications utilizing short-lived UE connections.
  • any of the UEs 101 and 102 can include a narrowband (NB) loT UE (e.g., such as an enhanced NB- loT (eNB-IoT) UE and Further Enhanced (FeNB-IoT) UE).
  • NB narrowband
  • eNB-IoT enhanced NB- loT
  • FeNB-IoT Further Enhanced
  • An loT UE can utilize technologies such as machine- to-machine (M2M) or machine -type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or loT networks.
  • M2M or MTC exchange of data may be a machine-initiated exchange of data.
  • An loT network includes interconnecting loT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections.
  • the loT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the loT network.
  • any of the UEs 101 and 102 can include enhanced MTC (eMTC) UEs or further enhanced MTC (FeMTC) UEs.
  • eMTC enhanced MTC
  • FeMTC enhanced MTC
  • the UEs 101 and 102 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 110.
  • the RAN 110 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN.
  • UMTS Evolved Universal Mobile Telecommunications System
  • E-UTRAN Evolved Universal Mobile Telecommunications System
  • NG RAN NextGen RAN
  • the UEs 101 and 102 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 110.
  • UMTS Evolved Universal Mobile Telecommunications System
  • E-UTRAN Evolved Universal Mobile Telecommunications System
  • NG RAN NextGen RAN
  • connections 103 and 104 are illustrated as an air interface to enable communicative coupling and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to- Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth-generation (5G) protocol, a New Radio (NR) protocol, and the like.
  • GSM Global System for Mobile Communications
  • CDMA code-division multiple access
  • PTT Push-to- Talk
  • POC PTT over Cellular
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • 5G fifth-generation
  • NR New Radio
  • the UEs 101 and 102 may further directly exchange communication data via a ProSe interface 105.
  • the ProSe interface 105 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).
  • PSCCH Physical Sidelink Control Channel
  • PSSCH Physical Sidelink Shared Channel
  • PSDCH Physical Sidelink Discovery Channel
  • PSBCH Physical Sidelink Broadcast Channel
  • the UE 102 is shown to be configured to access an access point (AP) 106 via connection 107.
  • AP access point
  • the connection 107 can comprise a local wireless connection, such as, for example, a connection consistent with any IEEE 802.11 protocol, according to which the AP 106 can comprise a wireless fidelity (WiFi) router.
  • WiFi wireless fidelity
  • the AP 106 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).
  • the RAN 110 can include one or more access nodes that enable the connections 103 and 104.
  • These access nodes can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), Next Generation NodeBs (gNBs), RAN nodes, and the like, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell).
  • the communication nodes 111 and 112 can be transmission/reception points (TRPs).
  • the RAN 110 may include one or more RAN nodes for providing macrocells, e.g., macro-RAN node i ll, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 112.
  • macro-RAN node i ll e.g., macro-RAN node i ll
  • femtocells or picocells e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells
  • LP low power
  • any of the RAN nodes 111 and 112 can terminate the air- interface protocol and can be the first point of contact for the UEs 101 and 102.
  • any of the RAN nodes 111 and 112 can fulfill various logical functions for the RAN 110 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.
  • RNC radio network controller
  • any of the nodes 111 and/or 112 can be a new generation Node-B (gNB), tin evolved node-B (eNB ), or another type of RAN node.
  • gNB Node-B
  • eNB tin evolved node-B
  • the RAN 110 is shown to be communicatively coupled to a core network (CN) 120 via an S I interface 113.
  • the CN 120 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN (e.g., as illustrated in reference to FIGS. 1B-1C).
  • EPC evolved packet core
  • NPC NextGen Packet Core
  • the SI interface 113 is split into two parts: the Sl-U interface 114, which carries traffic data between the RAN nodes 111 and 112 and the serving gateway (S-GW) 122, and the Sl-mobility management entity (MME) interface 115, which is a signaling interface between the RAN nodes 111 and 112 and MMEs 121.
  • S-GW serving gateway
  • MME Sl-mobility management entity
  • the CN 120 comprises the MMEs 121, the S-GW 122, the Packet Data Network (PDN) Gateway (P-GW) 123, and a home subscriber server (HSS) 124.
  • the MMEs 121 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN).
  • the MMEs 121 may manage mobility embodiments in access such as gateway selection and tracking area list management.
  • the HSS 124 may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions.
  • the CN 120 may comprise one or several HSSs 124, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc.
  • the HSS 12.4 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
  • the S-GW 122 may terminate the SI interface 113 towards the RAN 110, and routes data packets between the RAN 110 and the CN 120.
  • the S-GW 122 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility.
  • Other responsibilities of the S-GW 122 may include a lawful intercept, charging, and some policy enforcement.
  • the P-GW 123 may terminate an SGi interface toward a PDN.
  • the P-GW 123 may route data packets between the EPC network 120 and external networks such as a network including the application server 184 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 125.
  • the P-GW 123 can also communicate data to other external networks 131 A, which can include the Internet, IP multimedia subsystem (IPS) network, and other networks.
  • the application server 184 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.).
  • PS UMTS Packet Services
  • the P-GW 123 is shown to be communicatively coupled to an application server 184 via an IP interface 125.
  • the application server 184 can also be configured to support one or more communication services (e.g., Voice-over- Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 101 and 102 via the CN 120.
  • VoIP Voice-over- Internet Protocol
  • the P-GW 123 may further be a node for policy enforcement and charging data collection.
  • Policy and Charging Rules Function (PCRF) 126 is the policy and charging control element of the CN 120.
  • PCRF Policy and Charging Rules Function
  • HPLMN Home Public Land Mobile Network
  • IP-CAN Internet Protocol Connectivity Access Network
  • the PCRF 126 may be communicatively coupled to the application server 184 via the P- GW 123.
  • the communication network 140A can be an loT network or a 5G network, including 5G new radio network using communications in the licensed (5G NR) and the unlicensed (5G NR-U) spectrum.
  • One of the current enablers of loT is the narrowband-IoT (NB-IoT).
  • An NG system architecture can include the RAN 110 and a 5G network core (5GC) 120.
  • the NG-RAN 110 can include a plurality of nodes, such as gNBs and NG-eNBs.
  • the core network 120 e.g., a 5G core network or 5GC
  • AMF access and mobility function
  • UPF user plane function
  • the AMF and the UPF can be communicatively coupled to the gNBs and the NG-eNBs via NG interfaces. More specifically, in some embodiments, the gNBs and the NG-eNBs can be connected to the AMF by NG- C interfaces, and to the UPF by NG-U interfaces. The gNBs and the NG-eNBs can be coupled to each other via Xn interfaces.
  • the NG sy stem architecture can use reference points between various nodes as provided by 3GPP Technical Specification (TS) 23.501 (e.g., V15.4.0, 2018-12).
  • TS 3GPP Technical Specification
  • each of the gNBs and the NG-eNBs can be implemented as a base station, a mobile edge server, a small cell, a home eNB, ana so forth.
  • a gNB can be a master node (MN) and NG-eNB can be a secondary node (SN) in a 5G architecture,
  • FIG. IB illustrates a non-roaming 5G system architecture in accordance with some embodiments.
  • a 5G system architecture 140B in a reference point representation. More specifically, UE 102 can be in communication with RAN 110 as well as one or more other 5G core (5GC) network entities.
  • 5GC 5G core
  • the 5G system architecture 140B includes a plurality of network functions (NFs), such as access and mobility management function (AMF) 132, session management function (SMF) 136, policy control function (PCF) 148, application function (AF) 150, user plane function (UPF) 134, network slice selection function (NSSF) 142, authentication server function (AUSF) 144, and unified data management (UDM)/home subscriber server (HSS) 146.
  • the UPF 134 can provide a connection to a data network (DN) 152, which can include, for example, operator services, Internet access, or third-party services.
  • DN data network
  • the AMF 132 can be used to manage access control and mobility and can also include network slice selection functionality.
  • the SMF 136 can be configured to set up and manage various sessions according to network policy.
  • the UPF 134 can be deployed in one or more configurations according to the desired service type.
  • the PCF 148 can be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to PCRF in a 4G communication system).
  • the UDM can be configured to store subscriber profiles and data (similar to an HSS in a 4G communication system).
  • the 5G system architecture 140B includes an IP multimedia subsystem (IMS) 168B as well as a plurality of IP multimedia core network subsystem entities, such as call session control functions (CSCFs). More specifically, the IMS 168B includes a CSCF, which can act as a proxy CSCF (P-CSCF) 162BE, a serving CSCF (S-CSCF) 164B, an emergency CSCF (E-CSCF) (not illustrated in FIG. IB), or interrogating CSCF (I-CSCF) 166B.
  • the P-CSCF 162B can be configured to be the first contact point for the UE 102 within the IM subsystem (IMS) 168B.
  • the S-CSCF 164B can be configured to handle the session states in the network, and the E-CSCF can be configured to handle certain embodiments of emergency sessions such as routing an emergency request to the correct emergency center or PSAP.
  • the I-CSCF 166B can be configured to function as the contact point within an operator's network for all IMS connections destined to a subscriber of that network operator, or a roaming subscriber currently located within that network operator’s service area.
  • the I-CSCF 166B can be connected to another IP multimedia network 170E, e.g. an IMS operated by a different network operator.
  • the UDM/HSS 146 can be coupled to an application server 160E, which can include a telephony application server (TAS) or another application server ( AS).
  • the AS 160B can be coupled to the IMS 168B via the S-CSCF 164B or the I-CSCF 166B.
  • FIG. IB illustrates the following reference points: N1 (between the UE 102 and the AMF 132), N2 (between the RAN 110 and the AMF 132), N3 (between toe RAN 110 and the UPF 134), N4 (between the SMF 136 and the UPF 134), N5 (between the PCF 148 and the AF 150, not shown), N6 (between the UPF 134 and the DN 152), N7 (between the SMF 136 and the PCF 148, not shown), N8 (between the UDM 146 and the AMF 132, not shown), N9 (between two UPFs 134, not shown), N10 (between the UDM 146 and the SMF 136, not shown), N11 (between the AMF 132 and the SMF 136, not shown), N12 (between the AUSF 144 and the AMF 132, not shown), N13 (between the AUSF 144 and the UDM
  • FIG. 1C illustrates a 5G system architecture 140C and a service- based representation.
  • system architecture 140C can also include a network exposure function (NEF) 154 and a network repository function (NRF) 156.
  • NEF network exposure function
  • NRF network repository function
  • 5G system architectures can be service-based and interaction between network functions can be represented by corresponding point-to-point reference points Ni or as service-based interfaces.
  • service-based representations can be used to represent network functions within the control plane that enable other authorized network functions to access their services.
  • 5G system architecture 140C can include the following service-based interfaces: Namf 158H (a service-based interface exhibited by the AMF 132), Nsmf 1581 (a service-based interface exhibited by the SMF 136), Nnef 158B (a service-based interface exhibited by the NEF 154), Npcf 158D (a service-based interface exhibited by the PCF 148), a Nudm 158E (a service-based interface exhibited by the UDM 146), Naf 158F (a service -based interface exhibited by the AF 150), Nnrf 158C (a service-based interface exhibited by the NRF 156), Nnssf 158A (a service-based interface exhibited by the NSSF 142), Nausf 158G (a service-based interface exhibited by the a service-based interface exhibited by the
  • any of the UEs or base stations described in connection with FIGS. 1A-1C can be configured to perform the functionalities described herein.
  • NR next generation wireless communication system
  • 5G next generation wireless communication system
  • NR new radio
  • 3GPP LTE- Advanced with additional potential new Radio Access Technologies (RATs) to enrich people's lives with better, simple, and seamless wireless connectivity solutions.
  • RATs Radio Access Technologies
  • NR-unlicensed a short-hand notation of the NR-based access to unlicensed spectrum, is a technology that enables the operation of NR systems on the unlicensed spectrum.
  • a Bandwidth Part is a contiguous set of physical resource blocks (PRBs) on a given carrier. These RBs are selected from a contiguous subset of the common resource blocks for a given numerology (u). It is denoted by BWP.
  • PRBs physical resource blocks
  • u numerology
  • new WI is assigned to discuss the RRC based BWP switch for single and multiple component carriers (CCs).
  • the firstActiveDownlinkBWP-id is used to switch bandwidth part (B WP) with radio resource control (RRC) signaling.
  • RRC radio resource control
  • the UE switches to firstActiveDownlinkBWP-id immediately upon RRC reconfiguration of firstActiveDownlinkBWP-id.
  • SCell the UE switches to firstActiveDownlinkBWP-id upon activation of an SCell,
  • the UE switches firstActiveDownlinkBWP-id when the UE receives activation of the SCell. Therefore, the current delay requirement of single BWP switch only applies for the PCell and needs more discussion for the SCell.
  • the multiple CCs combination can include multiple scenarios (e.g., PCell+SCell or multiple SCells).
  • the legacy delay requirement can’t be applied for these scenarios when considering the extra SCell activation time.
  • embodiments of the present disclosure provide solutions for both single CC and multiple CCs cases.
  • some embodiments relate to introducing delay requirement for simultaneous RRC based BWP switch on single and multiple CCs.
  • the UE For RRC -based BWP switching, after the UE receives RRC reconfiguration involving an active BWP switching or parameter change of its active BWP, the
  • UE is able to receive PDSCH/PDCCH (for DL active BWP switch) or transmit PUSCH (for UL active BWP switch) on the new BWP on the serving cell on which BWP switch occurs on the first DL or UL slot right after a time duration begins from the beginning of DL slot n, where
  • DL slot n is the last slot containing the RRC command
  • TRRCR processingDelay is the length of the RRC procedure delay in ms as defined in clause 12 in TS 38.331, 16.2.0, 2020-10-07, and
  • T BWPswitchDelayRRC 6ms is the time used by the UE to perform BWP switch.
  • the firstActiveDownlinkBWP-id is used to switch BWP with
  • the UE switch to firstActiveDownlinkBWP-id immediately upon RRC reconfiguration of firstActiveDownlinkBWP-id.
  • the UE switch to firstActiveDownlinkBWP-id upon activation of an SCell, which is shown in TS 38.331 :
  • this field contains the ID of the DL BWP to be activated upon performing the RRC (re-)configuration. If the field is absent, the RRC (re-)configuration does not impose a BWP switch.
  • this field contains the ID of the downlink bandwidth part to be used upon activation of an SCell.
  • the network Upon PCell change and PSCell addition/change, the network sets the firstActiveDownlinkBWP-id and first ActiveUplinkBWP -Id to the same value.
  • the UE switches firstActiveDownlinkBWP-id when the UE receives activation of the SCell. Therefore, the current delay requirement of single BWP switch only applies for PCell and needs more discussion for SCell.
  • Example 1 Current single RRC based BWP switch delay requirement in Rel-15 is only applied for PCell or PSCell.
  • a BWP can be reconfigured by an SCell modification procedure. However, the delay time will depend on the SCell status (e.g., activation/deactivation).
  • Option 1 the start point of delay time can be changed to the time when SCell has been activated.
  • Option 2 the total delay time will consider according to different SCell status.
  • the total delay will need to consider the SCell activation time.
  • the total delay will include the SCell deactivation time and another SCell activation time.
  • Example 2 There are three options for RRC based SCell BWP switch on single CC:
  • Option 1 the start point of delay time can be changed to the time when SCell has been acti vated.
  • Option 2 the total delay time will be defined according to different SCell status. If SCell is in deactivated status, total delay will consider SCell activation time. If SCell is in activated status, the total delay will include the SCell deactivation time and another SCell activation time
  • Option 3 don’t define requirement for SCell BWP switch.
  • issue 2 delay requirement for RRC based BWP switch on multiple CCs
  • Case 1 BWP switches involves both PCell and SCell
  • the applied BWP switch timing may be different for PCell and SCell. If the status of SCell is deactivated, the UE will switch to firstActiveDownlinkBWP-Id upon SCell activation. If the status of SCell is activated, the UE will switch to firstActiveDownlinkBWP-Id upon ‘next’ SCell activation after this SCell is deactivated.
  • BWP switch involves multiple SCells
  • UE can perform BWP switch on each SCell only after each SCell is activated.
  • UE receives one single MAC command for multiple SCell activation: however, it will not guarantee that multiple SCell activation will finish at the same time. Then the BWP switch on multiple SCells may not start at the same time.
  • Example 3 There are several options for RRC based SCell BWP switch on multiple CC:
  • Option 1 total delay time will be defined including the multiple
  • Option 2 Don’t define requirement for this case.
  • Option 1 the start point of delay time can be changed to the time when all the SCells has been activated.
  • Option 2 total delay time will be defined including the multiple SCell activation delay.
  • FIG. 2 illustrates a functional block diagram of a wireless communication device, in accordance with some embodiments.
  • Wireless communication device 200 may be suitable for use as a UE or gNB configured for operation in a 5G NR network.
  • the communication device 200 may include communications circuitry 202 and a transceiver 210 for transmitting and receiving signals to and from other communication devices using one or more antennas 201.
  • the communications circuitry 202 may include circuitry that can operate the physical layer (PHY) communications and/or medium access control (MAC) communications for controlling access to the wireless medium, and/or any other communications layers for transmitting and receiving signals.
  • the communication device 200 may also include processing circuitry 206 and memory 208 arranged to perform the operations described herein.
  • the communications circuitry 202. and the processing circuitry 206 may be configured to perform operations detailed in the above figures, diagrams, and flows.
  • the communications circui try 202 may be arranged to contend for a wireless medium and configure frames or packets for communicating over the wireless medium.
  • the communications circuitry 202 may be arranged to transmit and receive signals.
  • the communications circuitry 202 may also include circuitry for modulation/demodulation, upconversion/downconversion, filtering, amplification, etc.
  • the processing circuitry 206 of the communication device 200 may include one or more processors.
  • two or more antennas 201 may be coupled to the communications circuitry 202 arranged for sending and receiving signals.
  • the memory 208 may store information for configtiring the processing circuitry 206 to perform operations for configuring and transmitting message frames and performing the various operations described herein.
  • the memory 208 may include any type of memory, including non-transitory memory, for storing information in a form readable by a machine (e.g., a computer).
  • the memory 208 may include a computer-readable storage device, read-only memory (ROM), random- access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices and other storage devices and media.
  • the communication device 200 may be part of a portable wireless communication device, such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capability, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), a wearable computer device, or another device that may receive and/or transmit information wirelessly.
  • PDA personal digital assistant
  • laptop or portable computer with wireless communication capability such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capability, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), a wearable computer device, or another device that may receive and/or transmit information wirelessly.
  • the communication device 200 may include one or more antennas 201 .
  • the antennas 201 may include one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas, or other types of antennas suitable for transmission of RF signals.
  • a single antenna with multiple apertures may be used instead of two or more antennas.
  • each aperture may be considered a separate antenna.
  • MIMO multiple -input multiple-output
  • the antennas may be effectively separated for spatial diversity and the different channel characteristics that may result between each of the antennas and the antennas of a transmitting device.
  • the communication device 200 may include one or more of a keyboard, a display, a non-volatile memory port, multiple antennas, a graphics processor, an application processor, speakers, and other mobile device elements.
  • the display may be an LCD screen including a touch screen.
  • the communication device 200 is illustrated as having several separate functional elements, two or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), and/or other hardware elements.
  • processing elements including digital signal processors (DSPs), and/or other hardware elements.
  • DSPs digital signal processors
  • some elements may include one or more microprocessors, DSPs, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio-frequency integrated circuits (RFICs) and combinations of various hardware and logic circuitry for performing at least the functions described herein.
  • the functional elements of the communication device 200 may refer to one or more processes operating on one or more processing elements.
  • Example 1 may include Current single RRC based BWP switch delay requirement in Rel-15 is only applied for PCell or PSCell.
  • Example 2 may include there are three options for RRC based SCell BWP switch on single CC:
  • Option 1 the start point of delay time can be changed to the time when SCell has been acti vated.
  • Option 2 the total delay time will be defined according to different SCell status. If SCell is in deactivated status, total delay will consider SCell activation time. If SCell is in activated status, the total delay will include the SCell deactivation time and another SCell activation time
  • Option 3 don’t define requirement for SCell BWP switch.
  • Example 3 may include there are several options for RRC based SCell BWP switch on multiple CC:
  • Option 1 total delay time will be defined including the multiple
  • Option 2 Don’t define requirement for this case.
  • Option 1 the start point of delay time can be changed to the time when all the SCells has been activated.
  • Option 2 total delay time will be defined including the multiple SCell activation delay.
  • Example 4 includes a method of a user equipment (UE) comprising: receiving, by the UE, a radio resource control (RRC) message that includes an indication of a an identifier of a downlink (DL.) bandwidth part (BWP) for the UE to switch to, wherein the DL BWP is associated with a secondary cell (SCell); determining whether a status of the SCell is currently activated or deactivated; and switching to the identified DL BWP upon activation of the SCell in response to determining the SCell is currently deactivated, or switching to the identified DL BWP on a next activation of the SCell after the SCell is deacti vated in response to determining the SCell is currently activated.
  • RRC radio resource control
  • Example 5 includes the method of example 4 or some other example herein, wherein the identifier of the DL BWP is firstActiveDownlinkBWP-id.
  • Example 6 includes the method of example 4 or some other example herein, wherein a start point of a delay time associated with the switching to the identified DL BW'P is modified to a time when the SCell is activated.
  • Example 7 includes the method of example 4 or some other example herein, wherein the SCell is a first SCell, and a total delay time associated with the switching to the identified DL BWP is based on a status of a second SCell.
  • Example 8 includes the method of example 4 or some other example herein, wherein the switching to the identified DL BWP is performed for a single component carrier (CC).
  • CC single component carrier
  • Example 9 includes the method of example 4 or some other example herein, wherein the switching to the identified DL BWP is performed for multiple CCs.
  • Example 10 includes the method of example 4 or some oilier example herein, wherein the switching to the identified DL BWP involves BWP switching for both the SCell and a primary cell (PCell), wherein timing for the BWP switching for the PCell is different than for the SCell.
  • PCell primary cell
  • Example 11 includes the method of example 4 or some other example herein, wherein the switching to the identified DL BWP involves BWP switching for a plurality of SCells.
  • Example 12 includes the method of example 11 or some other example herein, wherein the switching to the identified DL BWP starts at different times for at least two of the plurality of SCells.

Landscapes

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

Abstract

Un UE configuré pour la commutation de BWP déclenchée par RRC, commute le BWP actif dans des périodes de temps prédéterminées selon que l'UE est configuré pour un SCell, qu'un SCell configuré est désactivé ou activé, et que la commutation de BWP concerne un seul ou plusieurs CC. Dans certains cas, l'exigence de délai de commutation ne commence pas avant qu'un SCell désactivé soit activé. Dans certains cas, le délai de commutation requis ne commence qu'après la désactivation du SCell activé et l'activation d'un nouveau SCell.
PCT/US2021/056069 2020-10-23 2021-10-21 Commutation bwp basée sur le rrc pour les porteuses composantes uniques et multiples WO2022087276A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202063104888P 2020-10-23 2020-10-23
US63/104,888 2020-10-23

Publications (1)

Publication Number Publication Date
WO2022087276A1 true WO2022087276A1 (fr) 2022-04-28

Family

ID=81289409

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2021/056069 WO2022087276A1 (fr) 2020-10-23 2021-10-21 Commutation bwp basée sur le rrc pour les porteuses composantes uniques et multiples

Country Status (1)

Country Link
WO (1) WO2022087276A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020067342A1 (fr) * 2018-09-27 2020-04-02 Sharp Kabushiki Kaisha Configurations de parties de bande passante pour une communication v2x
US20200213067A1 (en) * 2019-01-02 2020-07-02 Ali Cagatay Cirik Simultaneous Bandwidth Parts Switching
US20200229241A1 (en) * 2019-01-10 2020-07-16 Comcast Cable Communications, Llc Access Procedures In Wireless Communications

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020067342A1 (fr) * 2018-09-27 2020-04-02 Sharp Kabushiki Kaisha Configurations de parties de bande passante pour une communication v2x
US20200213067A1 (en) * 2019-01-02 2020-07-02 Ali Cagatay Cirik Simultaneous Bandwidth Parts Switching
US20200229241A1 (en) * 2019-01-10 2020-07-16 Comcast Cable Communications, Llc Access Procedures In Wireless Communications

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
LG ELECTRONICS INC.: "Handling of bwp-InactivityTimer upon RRC-triggered BWP", 3GPP DRAFT; R2-2001299, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Online; 20200224 - 20200306, 14 February 2020 (2020-02-14), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051849607 *
OPPO: "Summary of fast SCell activation (OPPO)", 3GPP DRAFT; R2-2002110, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. 20200224 - 20200306, 11 March 2020 (2020-03-11), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051864643 *

Similar Documents

Publication Publication Date Title
US11871423B2 (en) Transmission on a PCell scheduled by an SCell PDCCH in a 5G NR network
US11838915B2 (en) One-shot feedback and SCell dormancy behavior in 5G NR networks
US11457511B2 (en) Enhanced downlink semi-persistent scheduling (SPS)
US20240155636A1 (en) Multi-slot pdcch monitoring in search space sets for higher carrier frequency operation
EP4275381A1 (fr) Prise en charge de capacité d'ue pour de multiples configurations d'intervalle de mesure simultanées et indépendantes
US20240098539A1 (en) Network controlled small gap (ncsg) operations for new radio (nr)
US20220104235A1 (en) Aperiodic csi-rs resource set triggering by dci with aperiodic triggering offset
WO2022146637A1 (fr) Capacité d'équipement utilisateur (ue) pour un nombre maximal d'instances d'intervalle d'un motif d'intervalles simultanés multiples
US11956646B2 (en) Enhancements for uplink beam operations
US20220095381A1 (en) Determination of rnti for performing rach procedure at carrier frequencies above 52.6 ghz
US20210250977A1 (en) Generation node b (gnb) configured for slot-less operation at frequencies above a 52.6 ghz carrier frequency
WO2022031617A1 (fr) Indication dmrs dans des créneaux spéciaux permettant des opérations de spectre non appariées
US20240172243A1 (en) Sounding reference signal (srs) transmissions triggered via downlink control information (dci) formats without scheduling information
WO2022087276A1 (fr) Commutation bwp basée sur le rrc pour les porteuses composantes uniques et multiples
US20240114507A1 (en) Multi-tti scheduling of pdsch and pusch by dci
US20240014995A1 (en) Timing for non-overlapping sub-band full duplex (sbfd) operations in 5g nr
US20240155637A1 (en) Dci format configured for varied bit interpretations
EP3908050A1 (fr) Aspects de strate de non-accès sur la restriction de l'utilisation d'une couverture améliorée dans des systèmes de cinquième génération
US20240187190A1 (en) Out-of-order handling for tboms scheduling in 5g nr
US20240163868A1 (en) Configured grant based small data transmission (cg-sdt) in multibeam operation
US20230413336A1 (en) Frequency hopping for multiple prach transmissions of a prach repetition
WO2023069486A1 (fr) Retard de rapport de mesure pour des intervalles de mesure pré-configurés
WO2022031743A1 (fr) Configuration de canal prach et détermination d'identifiant rnti pour une fréquence supérieure à 52,6 ghz
EP4275384A1 (fr) Ue configurable pour prendre en charge de multiples intervalles de mesure
EP4201097A1 (fr) Équipement utilisateur configurable avec plusieurs motifs d'intervalle de mesure

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21883900

Country of ref document: EP

Kind code of ref document: A1