Selectively deactivate a bandwidth part

Abstract

The present invention relates to selectively deactivating a bandwidth part. Apparatus, methods, and systems for selectively deactivating a bandwidth part are disclosed. An apparatus includes a transceiver that receives one or more UL BWP configurations and receives an SL BWP configuration. Here, the one or more UL BWP configurations include an active UL BWP, and the SL BWP is associated with a first parameter set. The apparatus further includes a processor that identifies a second parameter set of the active UL BWP and determines whether the first parameter set matches the second parameter set. If the first parameter set does not match the second parameter set, the processor selectively deactivates one of the SL BWP and the active UL BWP.

Description

[0001] This application is a divisional application of the application with PCT application number PCT / IB2020 / 000163, international filing date of February 12, 2020, Chinese application number 202080011418.6, and invention title "Selectively deactivate bandwidth part", which entered the Chinese national phase on July 27, 2021.

[0002] This application claims the priority of U.S. Provisional Patent Application No. 62 / 804,692, titled "EFFICIENT BWP OPERATION FOR SIDELINK OPERATION", filed on February 12, 2019 by Joachim Loehr, Prateek Basu Mallick, and Karthikeyan Ganesan, which is incorporated herein by reference. Technical Field

[0003] The subject matter disclosed herein generally relates to wireless communication, and more particularly to selectively deactivating a bandwidth part in the case of a numerology mismatch between an uplink bandwidth part and a sidelink bandwidth part. Background Art

[0004] The following abbreviations are defined herein, and at least some of these abbreviations are referred to in the following description: 3rd Generation Partnership Project ("3GPP"), 5th Generation Core Network ("5GC"), 5th Generation System ("5GS"), Absolute Radio Frequency Channel Number ("ARFCN"), Authentication, Authorization and Accounting ("AAA"), Access and Mobility Management Function ("AMF"), Access Restricted Local Operator Service ("ARLOS"), Acknowledgement ("ACK"), Application Programming Interface ("API"), Authentication Center ("AuC"), Access Stratum ("AS"), Autonomous Uplink ("AUL"), AUL Downlink Feedback Information ("AUL-DFI"), Base Station ("BS"), Binary Phase Shift Keying ("BPSK"), Bandwidth Part ("BWP"), Ciphering Key ("CK"), Clear Channel Assessment ("CCA"), Control Element ("CE"), Cyclic Prefix ("CP"), Cyclic Redundancy Check ("CRC"), Channel State Information ("CSI"), Common Search Space ("CSS"), Connected Mode ("CM", this is the NAS state in 5GS), Core Network ("CN"), Control Plane ("CP"), Data Radio Bearer ("DRB"), Discrete Fourier Transform Spread ("DFTS"), Downlink Control Information ("DCI"), Downlink ("DL"), Downlink Pilot Time Slot ("DwPTS"), Dual Connectivity ("DC"), Dual Registration Mode ("DR mode"), Discontinuous Transmission ("DTX"), Enhanced Clear Channel Assessment ("eCCA"), Enhanced Licensed-Assisted Access ("eLAA"), Enhanced Mobile Broadband ("eMBB"), Evolved Node B ("eNB"), Evolved Packet Core ("EPC"), Evolved Packet System ("EPS"), EPS Mobility Management ("EMM",This is the NAS state in EPS), evolved UMTS terrestrial radio access ("E-UTRA"), E-UTRA absolute radio frequency channel number ("EARFCN"), evolved UMTS terrestrial radio access network ("E-UTRAN"), European Telecommunications Standards Institute ("ETSI"), frame-based device ("FBE"), frequency division duplexing ("FDD"), frequency division multiple access ("FDMA"), frequency division orthogonal cover code ("FD-OCC"), General Packet Radio Service ("GPRS"), General Public Service Identifier ("GPSI"), guard period ("GP"), Global System for Mobile Communications ("GSM"), globally unique temporary UE identifier ("GUTI"), Hybrid Automatic Repeat reQuest ("HARQ"), home subscriber server ("HSS"), home public land mobile network ("HPLMN"), information element ("IE"), integrity key ("IK"), Internet of Things ("IoT"), International Mobile Subscriber Identity ("IMSI"), key derivation function ("KDF"), Licensed-Assisted Access ("LAA"), load-based device ("LBE"), Listen Before Talk ("LBT"), Long Term Evolution ("LTE"), multiple access ("MA"), mobility management ("MM"), mobility management entity ("MME"), modulation and coding scheme ("MCS"), machine type communication ("MTC"), multiple-input multiple-output ("MIMO"), Mobile Station International Subscriber Directory Number ("MSISDN"), multi-user shared access ("MUSA"), narrowband ("NB"), negative acknowledgement ("NACK") or ("NAK"), new generation (5G) Node B ("gNB"), new generation radio access network ("NG-RAN", the RAN for 5GS networks), new radio ("NR", 5G radio access technology; also known as "5G NR"), next hop ("NH"), next hop chain counter ("NCC"), non-access stratum ("NAS"), network exposure function ("NEF"), non-orthogonal multiple access ("NOMA"), network slice selection assistance information ("NSSAI"), operation, administration and maintenance system ("OAM"), orthogonal frequency division multiplexing ("OFDM"), packet data unit ("PDU", used in combination with 'PDU session'), packet switching ("PS",For example, packet switched domain or packet switched service), primary cell (“PCell”), physical broadcast channel (“PBCH”), physical cell identity (“PCI”), physical downlink control channel (“PDCCH”), physical downlink shared channel (“PDSCH”), pattern division multiple access (“PDMA”), physical hybrid ARQ indicator channel (“PHICH”), physical random access channel (“PRACH”), physical resource block (“PRB”), physical uplink control channel (“PUCCH”), physical uplink shared channel (“PUSCH”), public land mobile network (“PLMN”), quality of service (“QoS”), quadrature phase shift keying (“QPSK”), radio access network (“RAN”), radio access technology (“RAT”), radio resource control (“RRC”), random access channel (“RACH”), random access response (“RAR”), radio network temporary identifier (“RNTI”), reference signal (“RS”), registration area (“RA”, similar to the tracking area list used in LTE / EPC), registration management (“RM”,Refers to NAS layer procedures and states), Remaining Minimum System Information (“RMSI”), Resource Spread Multiple Access (“RSMA”), Round Trip Time (“RTT”), Receive (“RX”), Radio Link Control (“RLC”), Sparse Code Multiple Access (“SCMA”), Scheduling Request (“SR”), Single Carrier Frequency Division Multiple Access (“SC-FDMA”), Secondary Cell (“SCell”), Shared Channel (“SCH”), Session Management (“SM”), Session Management Function (“SMF”), Service Provider (“SP”), Side Link (“SL”), Side Link Control Information (“SCI”), Signal to Interference plus Noise Ratio (“SINR”), Single Network Slice Selection Assistance Information (“S-NSSAI”), Single Registration Mode (“SR mode”), Sounding Reference Signal (“SRS”), System Information Block (“SIB”), Synchronization Signal (“SS”), Subcarrier Spacing (“SCS”), Supplementary Uplink (“SUL”), Subscriber Identity Module (“SIM”), Tracking Area (“TA”), Transport Block (“TB”), Transport Block Size (“TBS”), Time Division Duplex (“TDD”), Time Division Multiplexing (“TDM”), Time Division Orthogonal Cover Code (“TD-OCC”), Transmission Time Interval (“TTI”), Transmission (“TX”), Unified Access Control (“UAC”), Unified Data Management (“UDM”), User Data Repository (“UDR”), Uplink Control Information (“UCI”), User Entity / Equipment (Mobile Terminal) (“UE”), UE Configuration Update (“UCU”), UE Routing Selection Policy (“URSP”), Uplink (“UL”), User Plane (“UP”), Universal Mobile Telecommunications System (“UMTS”), UMTS Subscriber Identity Module (“USIM”), UMTS Terrestrial Radio Access (“UTRA”), UMTS Terrestrial Radio Access Network (“UTRAN”), Uplink Pilot Time Slot (“UpPTS”), Ultra-Reliable Low-Latency Communication (“URLLC”), Access to the Public Land Mobile Network (“VPLMN”) and Worldwide Interoperability for Microwave Access (“WiMAX”). As used herein, “HARQ-ACK” may collectively represent an Acknowledgment (“ACK”) and a Negative Acknowledgment (“NACK”) and Discontinuous Transmission (“DTX”). ACK means that the TB was correctly received, while NACK (or NAK) means that the TB was incorrectly received. DTX means that the TB was not detected.,

[0005] In some wireless communication systems, side link transmissions allow one UE device to communicate directly with another UE, e.g., via Device-to-Device (“D2D”) communication. Bandwidth part operation adapts to the size of the bandwidth available for data transmission (e.g., on a wideband carrier). In a Release 15 3GPP network, a serving cell may be configured with up to four uplink bandwidth parts. Summary of the Invention

[0006] A process for selectively deactivating a bandwidth part is disclosed. A method for a UE to selectively deactivate a bandwidth part includes: receiving one or more UL bandwidth part (“BWP”) configurations for a serving cell, including an active UL BWP; and receiving an SL BWP configuration for the same serving cell, wherein the SL BWP is associated with a first parameter set. The method includes: identifying a second parameter set of the active UL BWP; and determining whether the first parameter set matches the second parameter set. The method includes: if the first parameter set does not match the second parameter set, then selectively deactivating one of the SL BWP and the active UL BWP. Brief Description of the Drawings

[0007] A more specific description of the embodiments briefly described above will be presented by reference to specific embodiments illustrated in the drawings. It should be understood that these drawings only depict some embodiments and should not be considered as limiting the scope. These embodiments will be described and explained with additional features and details by using the drawings, in which:

[0008] Figure 1 is a schematic block diagram illustrating an embodiment of a wireless communication system for selectively deactivating a bandwidth part;

[0009] Figure 2 is a diagram illustrating an embodiment of a network architecture for selectively deactivating a bandwidth part;

[0010] Figure 3 is a flowchart illustrating an embodiment of making UL prior to SL;

[0011] Figure 4 is a diagram illustrating an embodiment of making SL prior to UL;

[0012] Figure 5 is a diagram illustrating an embodiment of activation / deactivation information;

[0013] Figure 6 is a diagram illustrating an embodiment of a user equipment device that can be used to selectively deactivate a bandwidth part;

[0014] Figure 7 is a diagram illustrating an embodiment of a base station device that can be used to selectively deactivate a bandwidth part; and

[0015] Figure 8 is a flowchart illustrating an embodiment of a method that can be used to selectively deactivate a bandwidth part. Detailed Description of the Embodiments

[0016] Those skilled in the art should understand that various aspects of the embodiments can be embodied as a system, apparatus, method, or program product. Therefore, the embodiments can take the form of a complete hardware embodiment, a complete software embodiment (including firmware, resident software, microcode, etc.), or an embodiment combining software aspects and hardware aspects.

[0017] For example, the disclosed embodiments can be implemented as a hardware circuit including a custom very large scale integration (“VLSL”) circuit or gate array, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. The disclosed embodiments can also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, etc. As another example, the disclosed embodiments can include one or more physical or logical blocks of executable code, which can be organized, for example, into objects, procedures, or functions.

[0018] In addition, the embodiments can take the form of a program product embodied in one or more computer-readable storage devices that store machine-readable code, computer-readable code, and / or program code, hereinafter referred to as code. The storage device can be tangible, non-transitory, and / or non-transmissive. The storage device may not contain a signal. In a particular embodiment, the storage device only takes a signal for accessing the code.

[0019] Any combination of one or more computer-readable media can be utilized. The computer-readable medium can be a computer-readable storage medium. The computer-readable storage medium can be a storage device that stores the code. The storage device can be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micro-mechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

[0020] More specific examples (a non-exhaustive list) of the storage device will include the following: an electrical connection having one or more leads, a portable computer disk, a hard disk, a random access memory (“RAM”), a read-only memory (“ROM”), an erasable programmable read-only memory (“EPROM”) or flash memory, a portable compact disc read-only memory (“CD-ROM”), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium can be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0021] The code for operating the embodiments can be any number of lines and can be written in any combination of one or more programming languages, including object-oriented programming languages such as Python, Ruby, Java, Smalltalk, C++, etc.; and conventional procedural programming languages such as the "C" programming language, etc.; and / or machine language such as assembly language. The code can execute entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer via any type of network, including a local area network ("LAN") or a wide area network ("WAN"), or can form a connection with an external computer (e.g., via the Internet using an Internet service provider).

[0022] Throughout this specification, references to "one embodiment", "an embodiment", or similar language mean that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, unless otherwise explicitly specified, the phrases "in one embodiment", "in an embodiment", and similar language that appear throughout this specification may, but do not necessarily, refer to the same embodiment, but rather to "one or more but not all embodiments". Unless otherwise explicitly specified, the terms including "comprises", "comprising", "has", and variations thereof mean "including but not limited to". Unless otherwise explicitly specified, the listing of items in a list does not mean that any or all of the items are mutually exclusive. Unless otherwise explicitly specified, the terms "a", "an", and "the" also refer to "one or more".

[0023] As used herein, a list with the conjunction "and / or" includes a single item in the list or a combination of items in the list. For example, the list of A, B, and / or C includes only A, only B, only C, the combination of A and B, the combination of B and C, the combination of A and C, or the combination of A, B, and C. As used herein, a list using the term "one or more of" includes any single item in the list or a combination of items in the list. For example, one or more of A, B, and C includes only A, only B, only C, the combination of A and B, the combination of B and C, the combination of A and C, or the combination of A, B, and C. As used herein, a list using the term "one of" includes one and only one of any single item in the list. For example, "one of A, B, and C" includes only A, only B, or only C, and does not include the combination of A, B, and C. As used herein, "a member selected from the group consisting of A, B, and C" includes one and only one of A, B, or C, and does not include the combination of A, B, and C. As used herein, "a member selected from the group consisting of A, B, and C and combinations thereof" includes only A, only B, only C, the combination of A and B, the combination of B and C, the combination of A and C, or the combination of A, B, and C.

[0024] In addition, the described features, structures, or characteristics of the embodiments can be combined in any suitable manner. In the following description, several specific details such as programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc. are provided to provide a thorough understanding of the embodiments. However, those skilled in the relevant art should recognize that the embodiments can be practiced without one or more of the specific details or by using other methods, components, materials, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring various aspects of the embodiments.

[0025] Aspects of the embodiments are described below with reference to schematic flowcharts and / or schematic block diagrams of methods, apparatuses, systems, and program products according to the embodiments. It should be understood that each block of the schematic flowcharts and / or schematic block diagrams and combinations of blocks in the schematic flowcharts and / or schematic block diagrams can be implemented by code. The code can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to generate a machine such that the instructions executed by the processor of the computer or other programmable data processing device create a device for implementing the functions / actions specified in the flowchart and / or block diagram.

[0026] The code can also be stored in a storage device that can direct a computer, other programmable data processing device, or other device to operate in a specific manner such that the instructions stored in the storage device produce an article of manufacture that includes instructions for implementing the functions / actions specified in the flowchart and / or block diagram.

[0027] The code can also be loaded onto a computer, other programmable data processing apparatus, or other devices, so that a series of operation steps are performed on the computer, other programmable apparatus, or other devices to generate a computer-implemented process, such that the code executed on the computer or other programmable apparatus provides a process for implementing the functions / actions specified in the flowchart and / or block diagram.

[0028] The flowchart and / or block diagram in the figure illustrate the architecture, functionality, and operation of possible implementations of apparatus, systems, methods, and program products according to various embodiments. In this regard, each block in the flowchart and / or block diagram may represent a module, segment, or portion of code that includes one or more executable instructions for implementing the specified logical function.

[0029] It should also be noted that in some alternative implementations, the functions noted in the blocks may not occur in the order noted in the figure. For example, in fact, depending on the functions involved, two consecutive blocks shown may be executed substantially simultaneously, or these blocks may sometimes be executed in the reverse order. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks or portions thereof of the illustrated figure.

[0030] Although various arrow types and line types may be employed in the flowchart and / or block diagram, these arrow types and line types are not to be construed as limiting the scope of the corresponding embodiments. In fact, some arrows or other connectors may be used only to indicate the logical flow of the depicted embodiments. For example, an arrow may indicate a waiting or monitoring period of unspecified duration between the enumerated steps in the depicted embodiment. It should also be noted that each block of the block diagram and / or flowchart, and combinations of blocks in the block diagram and / or flowchart, may be implemented by a system based on dedicated hardware that performs the specified functions or actions or a combination of dedicated hardware and code.

[0031] The description of the elements in each figure may refer to the elements of the foregoing figure. In all the figures, the same numerals refer to the same elements, including alternative embodiments of the same elements.

[0032] Generally, the present disclosure describes systems, methods, and apparatuses for bandwidth part operation of a remote unit 105 for participating in sidelink (e.g., vehicle) communication. In various embodiments, sidelink (“SL”) communication uses the PC5 interface. Sidelink communication may allocate (unused) UL resources for device-to-device communication with another UE.

[0033] To achieve bandwidth adaptation, i.e., to adapt to the size of the bandwidth for data transmission in the serving cell, the gNB configures UL and DL bandwidth parts (BWPs) for the UE. In paired spectrum, DL and UL can switch BWPs independently. In unpaired spectrum, DL and UL can switch BWPs simultaneously. The switching between configured BWPs occurs by means of DCI - i.e., the PDCCH indicating a switch to another bandwidth part - or an inactivity timer. When an inactivity timer is configured for the serving cell, the expiration of the inactivity timer associated with that cell can switch from the active BWP to the default BWP configured by the network.

[0034] In some embodiments, the serving cell may be configured with up to four BWPs, and for an active serving cell, there is always one active BWP at any point in time. Although the present disclosure assumes a maximum of four BWPs per serving cell, the principles described herein apply to other wireless communication systems that support more BWPs per serving cell.

[0035] The BWP switch for the serving cell is used to activate an inactive BWP and deactivate the active BWP once, and is controlled by the PDCCH indicating a downlink allocation or an uplink grant. After adding a SpCell or activating an SCell, one BWP is initially active without receiving a PDCCH indicating a downlink allocation or an uplink grant.

[0036] On the active BWP of each active serving cell configured with a BWP, the MAC entity will apply normal operations. This includes: transmitting on the UL-SCH, transmitting on the RACH, monitoring the PDCCH, transmitting the PUCCH, receiving the DL-SCH, and (re)initializing any suspended configured uplink grants of configured grant type 1 according to the stored configuration.

[0037] On the inactive BWP of each active serving cell configured with a BWP, the MAC entity will not transmit on the UL-SCH, will not transmit on the RACH, will not monitor the PDCCH, will not transmit the PUCCH, will not receive the DL-SCH, will clear any configured downlink allocations and configured uplink grants of configured grant type 2, and will suspend any configured uplink grants of configured type 1.

[0038] If there is no configured PRACH resource for the active UL BWP, the UE shall switch to the initial DL BWP and UL BWP and perform the RACH procedure when triggering the RACH procedure. If the MAC entity receives a PDCCH for BWP switching while a random access procedure is in progress in the MAC entity, whether to switch the BWP or ignore the PDCCH for BWP switching depends on the UE implementation. If the MAC entity decides to perform BWP switching, the MAC entity shall stop the ongoing random access procedure and initiate a random access procedure on the new active BWP. If the MAC decides to ignore the PDCCH for BWP switching, the MAC entity shall continue the ongoing random access procedure on the active BWP.

[0039] As previously mentioned, the 3GPP Release 15 NR specification allows only one active BWP at a time. In Release 15, each BWP has an associated parameter set, i.e., each BWP supports only one parameter set. For the case where the UE in Rel-15 supports services that require different parameter sets, the gNB needs to switch between different configured BWPs. However, the radio network may expect the UE to use the same parameter set in the configured SL BWP and the active BWP in the same carrier at a given time.

[0040] In the case where only one SL BWP is configured for a carrier / service cell, it is not possible to switch to another SL BWP, e.g., to align with the parameter set of the current active UL BWP. Therefore, the SL BWP can be considered to be always active. Given the fact that there is only one SL BWP, the SL BWP will be considered to be immediately active as soon as it is configured.

[0041] However, if the UL BWP used at that time point (when receiving the RRC reconfiguration) has a different SCS / parameter set from the configured SL BWP when the SL BWP is configured, then management of the UL BWP is required.

[0042] Processes and related signaling for efficiently managing configured UL and / or SL BWPs in a carrier / service cell are disclosed herein, particularly for the case of a parameter set mismatch between the active UL BWP and the configured SL BWP.

[0043] Figure 1FIG. 0 depicts a wireless communication system 100 for selectively deactivating a bandwidth part according to an embodiment of the present disclosure. In one embodiment, the wireless communication system 100 includes at least one remote unit 105, a radio access network (“RAN”) 120, and a mobile core network 140. The RAN 120 and the mobile core network 140 form a mobile communication network. The RAN 120 may be composed of base station units 110, and the remote unit 105 communicates with the base station unit using a wireless communication link 115. Even in Figure 1 a specific number of remote units 105, base station units 110, wireless communication links 115, RANs 120, and mobile core networks 140 are depicted, those skilled in the art will recognize that any number of remote units 105, base station units 110, wireless communication links 115, RANs 120, and mobile core networks 140 may be included in the wireless communication system 100.

[0044] In one implementation, the wireless communication system 100 complies with the 5G system specified in the 3GPP specifications. However, more generally, in addition to other networks, the wireless communication system 100 may also implement some other open or proprietary communication networks, such as LTE or WiMAX. The present disclosure is not intended to be limited to the implementation of any specific wireless communication system architecture or protocol.

[0045] In one embodiment, the remote unit 105 may include a computing device, such as a desktop computer, a laptop computer, a personal digital assistant (“PDA”), a tablet computer, a smart phone, a smart TV (e.g., a TV connected to the Internet), a smart appliance (e.g., an appliance connected to the Internet), a set-top box, a gaming console, a security system (including security cameras), an in-vehicle computer, a network device (e.g., a router, a switch, a modem), etc. In some embodiments, the remote unit 105 includes a wearable device, such as a smart watch, a fitness bracelet, an optical head-mounted display, etc. Moreover, the remote unit 105 may be referred to as a UE, a user unit, a mobile device, a mobile station, a user, a terminal, a mobile terminal, a fixed terminal, a user station, a user terminal, a wireless transmit / receive unit (“WTRU”), a device, or other terms used in the art.

[0046] The remote unit 105 may communicate directly with one or more of the base station units 110 in the RAN 120 via uplink (“UL”) and downlink (“DL”) communication signals. In addition, the UL and DL communication signals may be carried over the wireless communication link 115. Here, the RAN 120 is an intermediate network that provides the remote unit 105 with access to the mobile core network 140.

[0047] In some embodiments, the remote unit 105 communicates with the application server 151 via a network connection to the mobile core network 140. For example, an application 107 (e.g., a web browser, a media client, a phone / VoIP application) in the remote unit 105 can trigger the remote unit 105 to establish a PDU session (or other data connection) with the mobile core network 140 via the RAN 120. The mobile core network 140 then uses the PDU session to relay traffic between the remote unit 105 and the application server 151 in the packet data network 150. Note that the remote unit 105 can establish one or more PDU sessions (or other data connections) with the mobile core network 140. Thus, the remote unit 105 can simultaneously have at least one PDU session for communicating with the packet data network 150 and at least one PDU session for communicating with another data network (not shown).

[0048] The base station unit 110 can be distributed over a geographical area. In certain embodiments, the base station unit 110 can also be referred to as an access terminal, an access point, a base unit, a base station, a Node B, an eNB, a gNB, a home Node B, a relay node, or by any other term used in the art. The base station unit 110 is generally part of a radio access network (“RAN”) (such as RAN 120), which can include one or more controllers communicatively coupled to one or more corresponding base station units 110. These and other elements of the radio access network are not shown, but are generally well known to those of ordinary skill in the art. The base station unit 110 is connected to the mobile core network 140 via the RAN 120.

[0049] The base station unit 110 can serve multiple remote units 105 within a service area such as a cell or a cell sector via a wireless communication link 115. The base station unit 110 can communicate directly with one or more of the remote units 105 via communication signals. Generally, the base station unit 110 transmits DL communication signals to serve the remote units 105 in the time domain, the frequency domain, and / or the spatial domain. Additionally, the DL communication signals can be carried over the wireless communication link 115. The wireless communication link 115 can be any suitable carrier in the licensed radio spectrum or the unlicensed radio spectrum. The wireless communication link 115 facilitates communication between one or more of the remote units 105 and / or one or more of the base station units 110.

[0050] In one embodiment, the mobile core network 140 can be a 5G Core (“5GC”) or an Evolved Packet Core (“EPC”) that can be coupled to a packet data network 150, such as the Internet and other data networks like private data networks. The remote unit 105 can have a subscription or other account with the mobile core network. Each mobile core network 140 belongs to a single Public Land Mobile Network (“PLMN”). The present disclosure is not intended to be limited to implementations of any particular wireless communication system architecture or protocol.

[0051] The mobile core network 140 includes a number of network functions (“NF”). As depicted, the mobile core network 140 includes multiple User Plane Functions (“UPF”) 145. The mobile core network 140 also includes multiple control plane functions, including but not limited to an Access and Mobility Management Function (“AMF”) 141, a Session Management Function (“SMF”) 143, and a Policy Control Function (“PCF”) 147 that serve the RAN 120. In certain embodiments, the mobile core network 140 can also include an Authentication Server Function (“AUSF”), a Unified Data Management Function (“UDM”) 149, a Network Repository Function (“NRF”) (used by various NFs to discover each other and communicate with each other via APIs), or other NFs defined for the 5GC.

[0052] In various embodiments, the mobile core network 140 supports different types of mobile data connections and different types of network slices, where each mobile data connection utilizes a specific network slice. Here, a “network slice” refers to a part of the mobile core network 140 that is optimized for a specific service type or communication service. In certain embodiments, various network slices can include separate instances of network functions such as the SMF 143 and the UPF 145. In some embodiments, different network slices can share some common network functions, such as the AMF 141. For ease of illustration, different network slices are not shown in Figure 1 but it is assumed that these network slices are supported.

[0053] Although a specific number and type of network functions are depicted in Figure 1 , those skilled in the art will recognize that any number and type of network functions can be included in the mobile core network 140. Moreover, in the case where the mobile core network 140 is an EPC, the depicted network functions can be replaced with appropriate EPC entities such as an MME, an S-GW, a P-GW, an HSS, etc. In certain embodiments, the mobile core network 140 can include an AAA server.

[0054] In various embodiments, the remote units 105 may communicate directly with each other (e.g., device-to-device communication) using sidelink (“SL”) communication signals 125. Here, the sidelink transmissions from the “transmitting” remote units 105 may be broadcast, multicast, or unicast. Multicast refers to group communication, where the transmitting remote unit 105 in the group transmits a multicast packet to all of its group members.

[0055] Although Figure 1 the components of the 5G RAN and 5G core network are depicted, the described embodiments for selectively deactivating a bandwidth part are applicable to other types of communication networks, including IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, CDMA 2000, Bluetooth, ZigBee, Sigfoxx, etc. For example, in an LTE variant involving the EPC, the AMF 141 may be mapped to the MME, the SMF 143 may be mapped to the control plane part of the PGW and / or the MME, the UPF 145 may be mapped to the user plane parts of the SGW and PGW, the UDM / UDR 149 may be mapped to the HSS, etc.

[0056] To support BWP operation for SL communication, especially when there is a mismatch between the parameter sets of the active UL BWP and the configured SL BWP, the remote units 105 may be configured with a communication priority policy, such as a set of one or more communication priority rules.

[0057] In some embodiments, UL communication is prioritized over SL communication. Here, when the active UL BWP has a different parameter set from the SL BWP, the SL BWP may be implicitly deactivated by the UE. As used herein, “deactivate” means that when deactivating a (single) configured SL BWP—e.g., there is no SL communication on the configured SL resource pool (“RP”)—the serving cell / carrier does not support SL transmission and reception. Additionally, the phrase “implicitly deactivate” means that the remote unit 105 will deactivate the SL BWP based on the different parameter sets and without having explicit signaling from the base station unit 110 to the remote unit 105 for deactivating the SL BWP.

[0058] Moreover, in the UL first priority scenario, when the active UL BWP has the same parameter set as the SL BWP, the SL BWP can be implicitly activated by the UE. As used herein, "activation" means that SL transmission and reception are (again) available on the serving cell / carrier, e.g., the configured SL (resource pool) RP is available again for SL communication. Additionally, the phrase "implicitly activate" means that the remote unit 105 will activate (e.g., reactivate) the SL BWP based on the same parameter set and without having explicit signaling from the base station unit 110 to the remote unit 105 for activating the SL BWP. Note that an instruction to switch to a UL BWP having the same parameter set as the configured SL BWP implicitly instructs the remote unit 105 to activate the SL BWP (which may have been deactivated previously).

[0059] In some embodiments, SL communication is prioritized over UL communication. Here, if the current UL BWP has a different parameter set from the SL BWP, then the remote unit 105 can autonomously switch from the current UL BWP to the configured UL BWP (e.g., without having an explicit instruction from the base station unit 110) that has the same parameter set as the SL BWP. In the case where the remote unit 105 is configured with multiple UL BWPs (that have the same parameter set as the SL BWP), then there can be rules that govern which of the multiple UL BWPs the remote unit 105 will switch to. In one example, the rule can instruct the remote unit 105 to switch to the UL BWP with the smallest BWP identifier (among the multiple matching BWPs).

[0060] Moreover, in the SL first priority scenario, if there is no configured UL BWP having the same parameter set as the SL BWP, then the remote unit 105 can deactivate the SL BWP.

[0061] In other embodiments, the activation / deactivation of the configured SL BWP will be signaled explicitly by the base station unit 110. Here, the SL BWP can be activated / deactivated by a separate message from the DCI for switching (activating / deactivating) the (UL) BWP. In certain embodiments, a control message is used to signal the SL BWP activation / deactivation. In one embodiment, the control message is a compact DCI. In another embodiment, the control message is a MAC CE. In certain embodiments, the SL BWP activation / deactivation is signaled by means of an SL resource allocation message. In certain embodiments, the SL BWP is activated at a fixed (e.g., default) time after receiving an RRC reconfiguration message (e.g., to configure the same parameter set as the UL BWP).

[0062] Figure 2 FIG. 200 depicts a network architecture for selectively deactivating a bandwidth part in accordance with an embodiment of the present disclosure. The network architecture 200 includes a first UE 205 communicating with a gNB 210 and a second UE 215. Here, the first UE 205 is configured with a UL BWP 220, a DL BWP 225, and an SL BWP 230

[0063] In the depicted embodiment, the UE 205 supports simultaneous UL BWP 220 and SL BWP 230 with the same parameter set, but does not support simultaneous UL BWP 220 and SL BWP 230 with different parameter sets. Thus, if a parameter set mismatch is detected, the UE 205 selectively deactivates the configured BWP (e.g., SL BWP and / or UL BWP).

[0064] According to a first solution, when the parameter set of the active UL BWP 220 in a given carrier / service cell is different from the parameter set of the SL BWP 230 configured for the same carrier / service cell, the UE 205 deactivates the configured SL BWP 230. The deactivation of the SL BWP 230 is autonomously performed in the UE 205. This solution is described in more detail below with reference to Figure 3 FIG.

[0065] According to a second solution, in a case where the parameter set of the current active UL BWP is different from the parameter set of the SL BWP 230, the UE 205 autonomously switches to the configured UL BWP 220 having the same parameter set as the SL BWP 230. This solution is described in more detail below with reference to Figure 4 FIG.

[0066] According to a third solution, a network entity (such as the gNB 210) explicitly activates / deactivates the configured SL BWP 230 by means of control signaling.

[0067] According to a fourth solution, the UE 205 is allowed to communicate on the active UL BWP 220 having a parameter set different from the parameter set of the SL BWP in a time slot reserved for NR UL and at least a predefined time (e.g., x ms) before the next time slot configured for SL communication, i.e., there should be at least a gap of x ms between NR UL operation and NR SL communication.

[0068] According to the fifth solution, when the UE 205 receives an RRC (re)configuration message that configures an SL BWP 230 with a parameter set that does not match the parameter set of the active UL BWP, that is, the parameter set of the SL BWP is different from the parameter set of the active UL BWP, the UE 205 regards the configuration as invalid, that is, the UE 205 cannot comply with the configuration. As a result, the UE 205 ignores the RRC (re)configuration message, that is, the UE 205 continues to use the configuration used before receiving the RRC Reconfiguration message.

[0069] According to the sixth solution, the UE 205 can ignore a PDCCH (DCI) that commands the UE 205 to switch to a UL BWP 220 associated with a parameter set different from the parameter set of the configured SL BWP. Similarly, the UE 205 can ignore an RRC message that commands the UE 205 to switch / activate a UL BWP 220 associated with a parameter set different from the parameter set of the configured SL BWP.

[0070] According to the seventh solution, the UE 205 is configured whether it should act according to the behavior described in the first solution, such as deactivating the SL BWP 230 autonomously when there is a parameter set mismatch to give priority to UL over SL; or whether it should act according to the behavior described in the second solution, such as switching the UL BWP 220 when there is a parameter set mismatch to give priority to SL over UL.

[0071] Figure 3 A process 300 for selectively deactivating a configured BWP according to an embodiment of the present disclosure is depicted. The process 300 can be implemented by a UE such as the UE 205. The process 300 illustrates a first solution for a BWP parameter set mismatch. The UE determines whether the active UL BWP and the SL BWP have the same parameter set (see block 305). If the active UL BWP and the SL BWP have the same parameter set, then they both remain active (see block 310). Otherwise, according to the first solution, when a parameter set mismatch is detected, the UE 205 autonomously deactivates the SL BWP (see block 315).

[0072] In some embodiments, such a parameter set mismatch may occur when the gNB 210 commands the UE 205—e.g., by means of a PDCCH indicating a downlink allocation or an uplink grant or—to switch to one of the UL BWPs 220 configured with a parameter set different from that associated with the co-configured SL BWP 230. Another situation in which such a parameter set mismatch may occur is when the UE autonomously switches to the default / initial BWP with a parameter set different from that of the SL BWP 230. The UE 205 may switch to the default / initial BWP, for example, when there is no RACH resource configured on the serving cell.

[0073] As discussed above, deactivating the SL BWP 230 should be understood as deactivating SL communication on the corresponding carrier / serving cell. For example, the UE 205 cannot transmit or receive SL communication on the configured resource pool. As described above, for the case where the UE 205 has multiple active UL BWPs 220 for a carrier / serving cell, at least one of the parameter sets associated with the active UL BWPs 220 needs to match the parameter set of the SL BWP; otherwise, the UE 205 will autonomously deactivate the SL BWP 230.

[0074] Similar to the (implicit) deactivation of the SL BWP when there is a mismatch between the parameter set of the active UL BWP and the parameter set of the configured SL BWP, the UE 205 activates the configured SL BWP 230 when the parameter sets of the active UL BWP and the configured SL BWP are the same. For example, when the UE 205—e.g., by a network command—switches to a UL BWP 220 with the same parameter set as that of the SL BWP, the UE 205 implicitly activates the SL BWP 230 (which was, for example, previously deactivated). Activating the SL BWP 230 should be understood as enabling SL communication in the corresponding carrier / serving cell. For example, the UE 205 cannot transmit or receive SL communication on the configured resource pool in the cell.

[0075] Figure 4 A process 400 for selectively deactivating a bandwidth part according to an embodiment of the present disclosure is depicted. The process 400 may be implemented by a UE such as the UE 205. The process 400 illustrates a second solution to the BWP parameter set mismatch. The UE determines whether the active UL BWP and the SL BWP have the same parameter set (see block 405). If the active UL BWP and the SL BWP have the same parameter set, then both remain active (see block 410). Otherwise, according to the second solution, the UE 205 autonomously switches to the configured UL BWP with the same parameter set as the SL BWP after detecting the parameter set mismatch.

[0076] In some embodiments, such a parameter set mismatch (e.g., SCS mismatch) may occur when the gNB 210 configures an SL BWP 230 with a parameter set different from that of the current active UL BWP for a carrier / serving cell. For the case where there are multiple configured UL BWPs 220 having the same parameter set (e.g., SCS) as that of the SL BWP, the UE 205 may switch to one of the multiple configured UL BWPs 220 having the same parameter set according to at least one of the following selection rules:

[0077] In one embodiment, the selected UL BWP is the one with the smallest BWP ID. In another embodiment, the selected UL BWP is the one with the highest BWP ID.

[0078] In some embodiments, the selected UL BWP is the one having the largest overlap with the SL BWP - that is, the overlap of the PRBs of the UL BWP and the PRBs of the SL BWP.

[0079] In one embodiment, the selected UL BWP is the default UL BWP provided that the default UL BWP has the same parameter set as the SL BWP. In another embodiment, the selected UL BWP is the initial UL BWP provided that the initial UL BWP has the same parameter set as the SL BWP.

[0080] Accordingly, the UE 205 attempts to maintain both UL communication and SL communication by switching to a compatible UL BWP (e.g., one having the same parameter set as the SL BWP). In one implementation of the second solution, for the case where there is no configured UL BWP 220 having the same parameter set as the SL BWP 230, the UE 205 deactivates the SL BWP 230.

[0081] Figure 5 Control signaling 500 for selectively activating / deactivating a bandwidth part in accordance with embodiments of the present disclosure is depicted. The control signaling 500 may be transmitted by a RAN node such as the gNB 210 to a UE such as the UE 205. The control signaling 500 may be used to explicitly activate and / or deactivate a configured SL BWP.

[0082] According to the third solution, a network entity such as gNB 210 explicitly activates / deactivates a configured SL BWP 230 by means of control signaling. For example, when the configured SL BWP 230 is currently deactivated due to a mismatched parameter set as described in the first embodiment, gNB 210 may decide to quickly activate the SL BWP 230 to ensure that SL communication can be performed in the serving cell.

[0083] According to one embodiment of the third solution, for example, in the case of a parameter set mismatch, as explained in the above embodiments, activating the SL BWP 230 by means of some explicit signaling may cause the UE 205 to deactivate / switch the currently active UL BWP 220.

[0084] According to some embodiments of the third solution, the activation / deactivation information may be conveyed in an existing V2X control channel for allocating resources for SL communication, for example, as Figure 5 shown.

[0085] A new field indicating the activation / deactivation status of the SL BWP 230 may be introduced in the existing V2X control channel. Alternatively, resource allocation on the SL BWP 230 may implicitly activate the SL BWP 230. Similarly, invalid resource allocation may implicitly indicate deactivation of the SL BWP 230.

[0086] Alternatively, PHY signaling is used to activate / deactivate the SL BWP 230. For example, a new PDCCH format (e.g., DCI) indicating that the UE 205 activates (alternatively, deactivates) the configured SL BWP 230 may be used. The DCI may contain a flag indicating whether to activate or deactivate the configured SL BWP 230, and the configured SL BWP may be identified by a certain BWP ID also signaled within the SL-DCI.

[0087] According to another embodiment of the third solution, DCI indicating the activation of a UL BWP 220 having a parameter set (SCS) different from that of the SL BWP implicitly deactivates the SL BWP 230.

[0088] According to another embodiment of the third solution, MAC control elements may be used to activate / deactivate the configured SLBWP 230. In one alternative, the configured SL BWP 230 is activated after a fixed / default duration after receiving an RRC reconfiguration message configuring the SL BWP 230 with the same parameter set as the active UL BWP, for example, after receiving the RRC message.

[0089] According to the fourth solution, the UE 205 is allowed to communicate on the active UL BWP 220 with a parameter set different from the parameter set of the SL BWP in a time slot reserved for NR UL and at least a predefined time, e.g., x ms, before the next time slot configured for SL communication, i.e., there should be a gap of at least x ms between NR UL operation and NR SL communication. It should be noted that all time slots / subframes providing PRBs intended for PC5 (SL) communication constitute the SL resource pool. To allow sufficient time to switch the parameter set, the UE 205 stops UL transmission on the active UL BWP 220 at a predefined time, e.g., x ms, before the next SL time slot, i.e., the time slot / subframe belonging to the SL resource pool. After UL transmission has been stopped (e.g., deactivating the UL BWP 220), the UE 205 autonomously switches its parameter set to the parameter set of the SL BWP in order to be able to perform SL communication in the next SL time slot / subframe.

[0090] The predefined time for switching the parameter set can be derived, for example, based on RAN4 requirements regarding BWP switching latency. Similarly, the UE 205 stops SL communication (e.g., deactivating the SL BWP 230) at a predefined time before the next UL time slot in order to switch the parameter set to the parameter set of the active UL BWP.

[0091] According to the fifth solution, when the UE 205 receives an RRC (re)configuration message configuring an SL BWP 230 with a parameter set that does not match the parameter set of the active UL BWP, i.e., the parameter set of the SL BWP is different from the parameter set of the active UL BWP, the UE 205 considers the configuration invalid, i.e., the UE 205 cannot comply with the configuration. As a result, the UE 205 ignores the RRC (re)configuration message, i.e., the UE 205 continues to use the configuration used before receiving the RRC Reconfiguration message.

[0092] According to one embodiment of the fifth solution, the UE 205 may further trigger a connection re - establishment procedure. The behavior when receiving an RRC reconfiguration message configuring an SL BWP 230 with a parameter set different from the parameter set of the active UL BWP is according to another embodiment of the fifth solution similar to the procedure "Unable to comply with RRC Reconfiguration" specified in TS38.331.

[0093] Specifically, if the UE 205 is operating in EN-DC, then if the UE fails to comply with the configuration (portion) included in the RRCReconfiguration message received via SRB3, the UE 205 will continue to use the configuration used prior to receiving the RRCReconfiguration message and will initiate a SCG failure information procedure to report the SCG reconfiguration error, after which the connection reconfiguration procedure ends. Otherwise, if the UE 205 operating in EN-DC fails to comply with the configuration (portion) included in the RRCReconfiguration message received via SRB1, then the UE will continue to use the configuration used prior to receiving the RRCReconfiguration message and will initiate a connection re-establishment procedure, after which the connection reconfiguration procedure ends.

[0094] Otherwise, if an RRCReconfiguration is received via NR, then if the UE fails to comply with the configuration (portion) included in the RRCReconfiguration message, the UE will continue to use the configuration used prior to receiving the RRCReconfiguration message and - if security has not been activated - the UE will take action after entering RRC_IDLE with a release cause of "other". However, if AS security has been activated but SRB2 and at least one DRB have not been configured, then the UE will take action after entering RRC_IDLE with a release cause of 'RRC connection failure'. Otherwise, the UE will initiate a connection re-establishment procedure, after which the reconfiguration procedure ends.

[0095] According to another embodiment of the fifth solution, the UE 205 enters the RRC_IDLE state after receiving an RRC reconfiguration message that configures the SL BWP 230 with an associated parameter set different from the parameter set of the active UL BWP.

[0096] According to the sixth solution, the UE 205 may ignore a PDCCH (DCI) that commands the UE 205 to switch to a UL BWP 220 associated with a parameter set different from the parameter set of the configured SL BWP. Similarly, the UE 205 may ignore an RRC message that commands the UE 205 to switch / activate a UL BWP 220 associated with a parameter set different from the parameter set of the configured SL BWP. According to one embodiment of the sixth solution, the UE 205 does not switch to the default or initial UL BWP 220 when the parameter set associated with the default / initial UL BWP 220 is different from the parameter set of the SL BWP.

[0097] According to the seventh solution, the UE 205 is configured to determine whether it should act according to the behavior described in the first solution, for example, by autonomously deactivating the SL BWP 230 when the parameter sets do not match to give UL priority over SL; or whether it should act according to the behavior described in the second solution, for example, by switching the UL BWP 220 when the parameter sets do not match to give SL priority over UL.

[0098] In an alternative implementation of the seventh solution, depending on the priority of the logical channels configured for NR UL and SL, the UE 205 acts according to the behavior described in the first solution or the second solution. As described above, when the NR service has a higher priority than the SL service, the UE 205 exhibits behavior that gives UL priority over SL when the parameter sets do not match. As described above, when the SL service has a higher priority than the NR UL service (e.g., the logical channel priority of SL LCH / RB is higher than that of NR LCH / RB), the UE 205 gives SL priority over UL when the parameter sets do not match.

[0099] Note that the priorities of different interfaces such as NR-Uu and SL PC5 can also be defined by the V2X control function of the geographical area. That is, in a certain geographical area (e.g., zone), NR-Uu (UL) is given priority over SL that takes the lead when the parameter sets do not match, while in other geographical areas, SL PC5 operation is given priority over Uu that forces the UE 205 to act according to the second solution.

[0100] According to another implementation of the seventh solution, if such a UL BWP 220 is configured, then the UE 205 switches to the UL BWP 220 that has the same parameter set as the SL BWP 230 when the parameter sets do not match; otherwise, the UE 205 deactivates the SL BWP 230.

[0101] Figure 6Illustrates a user equipment device 600 according to an embodiment of the present disclosure that can be used to selectively deactivate a bandwidth part. In various embodiments, the user equipment device 600 is used to implement one or more of the solutions described above. The user equipment device 600 can be an embodiment of the UE 205 described above. Additionally, the user equipment device 600 can include a processor 605, a memory 610, an input device 615, an output device 620, and a transceiver 625. In some embodiments, the input device 615 and the output device 620 are combined into a single device, such as a touch screen. In certain embodiments, the user equipment device 600 may not include any input device 615 and / or output device 620. In various embodiments, the user equipment device 600 can include one or more of the following: the processor 605, the memory 610, and the transceiver 625, and may not include the input device 615 and / or the output device 620.

[0102] In one embodiment, the processor 605 can include any known controller capable of executing computer-readable instructions and / or capable of performing logical operations. For example, the processor 605 can be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), a co-processing unit, a field-programmable gate array (“FPGA”), or a similar programmable controller. In some embodiments, the processor 605 executes instructions stored in the memory 610 to perform the methods and routines described herein. The processor 605 is communicatively coupled to the memory 610, the input device 615, the output device 620, and the transceiver 625.

[0103] In various embodiments, the transceiver 625 receives a sidelink bandwidth part (“BWP”) configuration and also receives one or more uplink BWP configurations. The processor 605 can identify a first subcarrier spacing of the sidelink BWP, identify a second subcarrier spacing of the active uplink BWP, and determine whether the first subcarrier spacing matches the second subcarrier spacing. If the subcarrier spacings do not match, then the processor 605 selectively deactivates one of the sidelink BWP and the active uplink BWP.

[0104] In some embodiments, the processor 605 determines the priority of the sidelink BWP relative to the active uplink BWP, where selectively deactivating one of the sidelink BWP and the active uplink BWP is based on the determined priority. In certain embodiments, the processor 605 determines the priority of the sidelink BWP relative to the active uplink BWP, where selectively deactivating one of the sidelink BWP and the active uplink BWP is based on the determined priority. If the active uplink BWP has a higher priority than the sidelink BWP, then selectively deactivating one of the sidelink BWP and the active uplink BWP includes: deactivating the sidelink BWP.

[0105] In certain embodiments, the transceiver 625 receives an instruction to switch to a second uplink BWP that has a subcarrier spacing that matches the subcarrier spacing of the sidelink BWP. Here, the processor 605 reactivates the sidelink BWP in response to switching to the second uplink BWP.

[0106] In certain embodiments, the sidelink BWP has a higher priority than the active uplink BWP. In such an embodiment, selectively deactivating one of the sidelink BWP and the active uplink BWP includes: switching from the active uplink BWP to a second uplink BWP that has a subcarrier spacing that matches the subcarrier spacing of the sidelink BWP. In cases where multiple configured uplink BWPs have a subcarrier spacing that matches the subcarrier spacing of the sidelink BWP, the processor 605 uses a selection rule to select the second uplink BWP from among the multiple matching uplink BWPs.

[0107] In certain embodiments, selectively deactivating one of the sidelink BWP and the active uplink BWP includes: deactivating the sidelink BWP in response to none of the one or more uplink BWP configurations having a subcarrier spacing that matches the subcarrier spacing of the sidelink BWP. In certain embodiments, the transceiver 625 receives a control message from a network entity, where the processor 605 deactivates a specified one of the sidelink BWP and the active uplink BWP according to the control message.

[0108] In one embodiment, the memory 610 is a computer-readable storage medium. In some embodiments, the memory 610 includes volatile computer storage media. For example, the memory 610 may include RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). In some embodiments, the memory 610 includes non-volatile computer storage media. For example, the memory 610 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 610 includes both volatile computer storage media and non-volatile computer storage media.

[0109] In some embodiments, the memory 610 stores data related to selectively deactivating a bandwidth part. For example, the memory 610 may store UL BWP configurations, SL BWP configurations, BWP parameter sets, etc. In certain embodiments, the memory 610 also stores program code and related data, such as an operating system or other controller algorithms running on the remote unit 105.

[0110] In one embodiment, the input device 615 may include any known computer input device, including a touch panel, buttons, a keyboard, a stylus, a microphone, etc. In some embodiments, the input device 615 may be integrated with the output device 620, such as a touch screen or a similar touch-sensitive display. In some embodiments, the input device 615 includes a touch screen such that text can be input using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. In some embodiments, the input device 615 includes two or more different devices, such as a keyboard and a touch panel.

[0111] In one embodiment, the output device 620 can be designed to output visual signals, auditory signals, and / or tactile signals. In some embodiments, the output device 620 includes an electrically controllable display or display device capable of outputting visual data to a user. For example, the output device 620 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or a similar display device capable of outputting images, text, etc. to a user. As another non-limiting example, the output device 620 may include a wearable display that is separate from the rest of the user equipment device 600 but communicatively coupled to the rest of the user equipment device 600, such as a smartwatch, smart glasses, a head-up display, etc. Additionally, the output device 620 may be a component of a smart phone, a personal digital assistant, a television, a desktop computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, etc.

[0112] In some embodiments, output device 620 includes one or more speakers for generating sound. For example, output device 620 can generate an audible alert or notification (e.g., a beep or a buzz). In some embodiments, output device 620 includes one or more haptic devices for generating vibration, movement, or other tactile feedback. In some embodiments, all or part of output device 620 can be integrated with input device 615. For example, input device 615 and output device 620 can form a touch screen or a similar touch-sensitive display. In other embodiments, output device 620 can be located near input device 615.

[0113] As discussed above, transceiver 625 communicates with one or more network functions of a mobile communication network via one or more access networks. Transceiver 625 operates under the control of processor 605 to transmit messages, data, and other signals, and also to receive messages, data, and other signals. For example, processor 605 can selectively activate transceiver 625 (or a portion thereof) at a particular time to send and receive messages.

[0114] Transceiver 625 can include one or more transmitters 630 and one or more receivers 635. Although only one transmitter 630 and one receiver 635 are illustrated, user equipment device 600 can have any suitable number of transmitters 630 and receivers 635. Additionally, transmitters 630 and receivers 635 can be any suitable type of transmitter and receiver. Further, transceiver 625 can support at least one network interface 640. Here, at least one network interface 640 facilitates communication with a RAN node such as an eNB or gNB, for example, using the "Uu" interface. Additionally, at least one network interface 640 can include an interface for communicating with one or more network functions in a mobile core network such as a UPF, an AMF, and / or an SMF.

[0115] In one embodiment, transceiver 625 includes a first transmitter / receiver pair for communicating with a mobile communication network over an authorized radio spectrum and a second transmitter / receiver pair for communicating with the mobile communication network over an unlicensed radio spectrum. In certain embodiments, the first transmitter / receiver pair for communicating with the mobile communication network over the authorized radio spectrum and the second transmitter / receiver pair for communicating with the mobile communication network over the unlicensed radio spectrum can be combined into a single transceiver unit, such as a single chip for performing functions for use with both the authorized radio spectrum and the unlicensed radio spectrum. In some embodiments, the first transmitter / receiver pair and the second transmitter / receiver pair can share one or more hardware components. For example, certain transceivers 625, transmitters 630, and receivers 635 can be implemented as physically separate components that access shared hardware resources and / or software resources - such as, for example, network interface 640.

[0116] In various embodiments, one or more transmitters 630 and / or one or more receivers 635 can be implemented and / or integrated into a single hardware component (such as a multi-transceiver chip, a system-on-chip, an application-specific integrated circuit (“ASIC”), or other types of hardware components). In certain embodiments, one or more transmitters 630 and / or one or more receivers 635 can be implemented and / or integrated into a multi-chip module. In some embodiments, other components, such as network interface 640 or other hardware components / circuits, can be integrated into a single chip with any number of transmitters 630 and / or receivers 635. In such embodiments, transmitters 630 and receivers 635 can be logically configured as transceiver 625 using one or more common control signals or as modular transmitters 630 and receivers 635 implemented in the same hardware chip or multi-chip module.

[0117] Figure 7 A base station device 700 that can be used to selectively deactivate a bandwidth part according to an embodiment of the present disclosure is depicted. The base station device 700 can be an embodiment of the base station unit 110 described above. Additionally, the base station device 700 can include a processor 705, a memory 710, an input device 715, an output device 720, and a transceiver 725. In some embodiments, the input device 715 and the output device 720 are combined into a single device, such as a touch screen. In certain embodiments, the base station device 700 may not include any input device 715 and / or output device 720. In various embodiments, the base station device 700 can include one or more of the following: processor 705, memory 710, and transceiver 725, and may not include input device 715 and / or output device 720.

[0118] In one embodiment, processor 705 may include any known controller capable of executing computer-readable instructions and / or capable of performing logical operations. For example, processor 705 may be a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, or a similar programmable controller. In some embodiments, processor 705 executes instructions stored in memory 710 to perform the methods and routines described herein. Processor 705 is communicatively coupled to memory 710, input device 715, output device 720, and transceiver 725.

[0119] In various embodiments, processor 705 controls base station device 700 to perform the behaviors described above. In some embodiments, base station device 700 transmits one or more UL BWP configurations and SL BWP configurations to a UE (e.g., via transceiver 725). Here, one or more UL BWP configurations include an active UL BWP. The SL BWP is associated with a first parameter set, and the active UL BWP is associated with a second parameter set. As described above, if the first parameter set does not match the second parameter set, then the UE selectively deactivates one of the SL BWP and the active UL BWP.

[0120] In one embodiment, memory 710 is a computer-readable storage medium. In some embodiments, memory 710 includes volatile computer storage media. For example, memory 710 may include RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). In some embodiments, memory 710 includes non-volatile computer storage media. For example, memory 710 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 710 includes both volatile computer storage media and non-volatile computer storage media.

[0121] In some embodiments, memory 710 stores data related to selectively deactivating a bandwidth part. For example, memory 710 may store UL BWP configurations, SL BWP configurations, BWP parameter sets, etc. In certain embodiments, memory 710 also stores program code and related data, such as an operating system or other controller algorithms running on remote unit 105.

[0122] In one embodiment, the input device 715 may include any known computer input device, including a touch panel, buttons, a keyboard, a stylus, a microphone, etc. In some embodiments, the input device 715 may be integrated with the output device 720, such as a touch screen or a similar touch-sensitive display. In some embodiments, the input device 715 includes a touch screen such that text can be input using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. In some embodiments, the input device 715 includes two or more different devices, such as a keyboard and a touch panel.

[0123] In one embodiment, the output device 720 may be designed to output visual signals, auditory signals, and / or tactile signals. In some embodiments, the output device 720 includes an electrically controllable display or a display device capable of outputting visual data to a user. For example, the output device 720 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or a similar display device capable of outputting images, text, etc. to a user. As another non-limiting example, the output device 720 may include a wearable display separated from the rest of the base station device 700 but communicatively coupled to the rest of the base station device 700, such as a smart watch, smart glasses, a head-up display, etc. Additionally, the output device 720 may be a component of a smart phone, a personal digital assistant, a television, a desktop computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, etc.

[0124] In certain embodiments, the output device 720 includes one or more speakers for generating sound. For example, the output device 720 may generate an audible alarm or notification (e.g., a beep or a ringtone). In some embodiments, the output device 720 includes one or more haptic devices for generating vibration, movement, or other haptic feedback. In some embodiments, all or part of the output device 720 may be integrated with the input device 715. For example, the input device 715 and the output device 720 may form a touch screen or a similar touch-sensitive display. In other embodiments, the output device 720 may be located near the input device 715.

[0125] The transceiver 725 includes at least a transmitter 730 and at least one receiver 735. As described herein, one or more transmitters 730 may be used to communicate with a UE. Similarly, as described herein, one or more receivers 735 may be used to communicate with other network functions in a PLMN. Although only one transmitter 730 and one receiver 735 are illustrated, the base station device 700 may have any suitable number of transmitters 730 and receivers 735. Additionally, the transmitter 725 and the receiver 730 may be any suitable type of transmitter and receiver.

[0126] Figure 8 FIG. Figure 8 depicts an embodiment of method 800 for selectively deactivating a bandwidth part according to an embodiment of the present disclosure. In various embodiments, method 800 is performed by the remote unit 105, UE 205, and / or user equipment device 600 described above. In some embodiments, method 800 is performed by a processor such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0127] Method 800 begins and receives 805 one or more UL BWP configurations for a serving cell, including an active UL BWP. Method 800 includes receiving 810 an SL BWP configuration for the same serving cell, where the SL BWP is associated with a first parameter set. Method 800 includes identifying 815 a second parameter set of the active UL BWP.

[0128] Method 800 includes determining 820 whether the first parameter set matches the second parameter set. Method 800 includes selectively deactivating 825 one of the SL BWP and the active UL BWP if the first parameter set does not match the second parameter set. Method 800 ends.

[0129] A first apparatus for selectively deactivating a bandwidth part according to an embodiment of the present disclosure is disclosed herein. The first apparatus may be implemented by a UE such as the remote unit 105, UE 205, and / or user equipment device 600. The first apparatus includes a transceiver that receives one or more UL BWP configurations and receives an SL BWP configuration. Here, the one or more UL BWP configurations include an active UL BWP, and the SL BWP is associated with a first parameter set. The first apparatus further includes a processor that identifies a second parameter set of the active UL BWP and determines whether the first parameter set matches the second parameter set. If the first parameter set does not match the second parameter set, the processor selectively deactivates one of the SL BWP and the active UL BWP.

[0130] In some embodiments, selectively deactivating one of the SL BWP and the active UL BWP includes deactivating the SL BWP, where the processor further stops SL communication on the serving cell. In other embodiments, the transceiver may receive an instruction to switch to a second UL BWP that has a parameter set that matches the parameter set of the SL BWP. In such an embodiment, the processor reactivates the SL BWP in response to switching to the second UL BWP.

[0131] In some embodiments, selectively deactivating one of the SL BWP and the active UL BWP includes: the processor switching from the active UL BWP to a second UL BWP having a parameter set that matches the parameter set of the SL BWP. In such an embodiment, multiple configured UL BWPs may have parameter sets that match the parameter set of the SL BWP. Accordingly, the processor selects the second UL BWP from among the multiple matching UL BWPs using a selection rule.

[0132] In some embodiments, selectively deactivating one of the SL BWP and the active UL BWP includes: the processor deactivating the SL BWP in response to none of one or more UL BWP configurations having a parameter set that matches the parameter set of the SL BWP.

[0133] In some embodiments, the transceiver receives a control message from a network entity that activates the SL BWP. In certain embodiments, selectively deactivating one of the SL BWP and the active UL BWP includes: the processor deactivating the active UL BWP in response to activating the SL BWP according to the control message. In other embodiments, selectively deactivating one of the SL BWP and the active UL BWP includes: the processor switching from the active UL BWP to a second UL BWP having a parameter set that matches the parameter set of the SL BWP in response to activating the SL BWP according to the control message.

[0134] In some embodiments, the transceiver receives a control message from a network entity that activates a configured UL BWP having a parameter set different from that of the SL BWP. In such an embodiment, selectively deactivating one of the SL BWP and the active UL BWP includes: the processor deactivating the SL BWP in response to activating the UL BWP according to the control message.

[0135] In some embodiments, selectively deactivating one of the SL BWP and the active UL BWP includes: the processor providing a communication gap between UL operations and SL operations; and adjusting (e.g., retuning and / or reconfiguring) the transceiver during the communication gap to switch between a first parameter set and a second parameter set.

[0136] In some embodiments, the processor further determines the priority of the SL BWP relative to the active UL BWP. In such an embodiment, selectively deactivating one of the SL BWP and the active UL BWP includes: the processor deactivating the one with the lower priority of the SL BWP and the active UL BWP.

[0137] Disclosed herein is a first method for selectively deactivating a bandwidth part according to an embodiment of the present disclosure. The first method may be performed by a UE such as remote unit 105, UE 205, and / or user equipment device 600. The first method includes: receiving one or more UL BWP configurations for a serving cell and receiving an SL BWP configuration for the same serving cell. Here, the one or more UL BWP configurations for the serving cell include an active UL BWP, and the SL BWP is associated with a first parameter set. The first method includes: identifying a second parameter set of the active UL BWP; and determining whether the first parameter set matches the second parameter set. The first method includes: if the first parameter set does not match the second parameter set, then selectively deactivating one of the SL BWP and the active UL BWP.

[0138] In some embodiments, selectively deactivating one of the SL BWP and the active UL BWP includes: deactivating the SL BWP. In some embodiments, the first method further includes: stopping SL communication on the serving cell. In certain embodiments, the first method further includes: receiving an instruction to switch to a second UL BWP that has a parameter set matching the parameter set of the SL BWP; and reactivating the SL BWP in response to switching to the second UL BWP.

[0139] In some embodiments, selectively deactivating one of the SL BWP and the active UL BWP includes: switching from the active UL BWP to a second UL BWP that has a parameter set matching the parameter set of the SL BWP. In various embodiments, a plurality of configured UL BWPs have parameter sets that match the parameter set of the SL BWP. In such embodiments, the first method includes: selecting the second UL BWP from the plurality of matching UL BWPs using a selection rule.

[0140] In some embodiments, selectively deactivating one of the SL BWP and the active UL BWP includes: deactivating the SL BWP in response to none of the one or more UL BWP configurations having a parameter set that matches the parameter set of the SL BWP.

[0141] In some embodiments, the first method includes: receiving a control message from a network entity, the control message activating the SL BWP. In such an embodiment, selectively deactivating one of the SL BWP and the active UL BWP may include: deactivating the active UL BWP in response to activating the SL BWP according to the control message. In other embodiments, selectively deactivating one of the SL BWP and the active UL BWP may include: switching from the active UL BWP to a second UL BWP having a parameter set matching the parameter set of the SL BWP in response to activating the SL BWP according to the control message.

[0142] In some embodiments, the first method includes: receiving a control message from a network entity, the control message activating a UL BWP configured with a parameter set different from that of the SL BWP. In such an embodiment, selectively deactivating one of the SL BWP and the active UL BWP may include: deactivating the active SL BWP in response to activating the UL BWP according to the control message.

[0143] In some embodiments, selectively deactivating one of the SL BWP and the active UL BWP includes: providing a communication gap between UL operation and SL operation; and adjusting (e.g., retuning and / or reconfiguring) a transceiver during the communication gap to switch between a first parameter set and a second parameter set.

[0144] In some embodiments, the first method includes: determining a priority of the SL BWP relative to the active UL BWP. In such an embodiment, selectively deactivating one of the SL BWP and the active UL BWP includes: deactivating the one with the lower priority of the SL BWP and the active UL BWP.

[0145] Embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects only illustrative and not restrictive. Thus, the scope of the present invention is indicated by the appended claims rather than the foregoing description. All changes within the meaning and scope of equivalents of the claims are to be embraced within their scope.

Claims

1. A user equipment (UE) for wireless communication, comprising: at least one memory; and at least one processor, the at least one processor being coupled to the at least one memory and configured to cause the UE to: receive a first configuration of one or more uplink bandwidth parts (BWPs) of a carrier for a serving cell, wherein at least one of the one or more uplink BWPs is an active uplink bandwidth part (BWP) associated with a first parameter set; receive a second configuration of a sidelink BWP of the carrier for the serving cell, wherein the sidelink BWP is associated with a second parameter set; and deactivate the sidelink BWP in response to the first parameter set being different from the second parameter set.

2. The UE according to claim 1, wherein the first configuration and the second configuration are received in different messages.

3. The UE according to claim 1, wherein to deactivate the sidelink BWP, the at least one processor is further configured to cause the UE to: stop sidelink communication on the carrier of the serving cell.

4. The UE according to claim 1, wherein the at least one processor is configured to cause the UE to: receive an instruction to switch to a second uplink BWP associated with the second parameter set; and activate the sidelink BWP in response to switching to the second uplink BWP.

5. The UE according to claim 1, wherein to deactivate the sidelink BWP, the at least one processor is further configured to cause the UE to: deactivate the sidelink BWP in response to none of the one or more uplink BWPs being associated with the second parameter set.

6. The UE according to claim 1, wherein the at least one processor is configured to cause the UE to: receive a control message from a network entity, the control message signaling the activation of the sidelink BWP; and deactivate the active uplink BWP in response to activating the sidelink BWP according to the control message.

7. The UE according to claim 1, wherein the at least one processor is configured to cause the UE to: receive a control message from a network entity, the control message signaling the activation of the sidelink BWP; and deactivate the active uplink BWP in response to the first parameter set being different from the second parameter set.

8. The UE according to claim 1, wherein the at least one processor is configured to cause the UE to: receive a control message from a network entity, the control message signaling the activation of the sidelink BWP; and switch from the active uplink BWP to a second uplink BWP associated with the second parameter set in response to activating the sidelink BWP according to the control message.

9. The UE according to claim 1, wherein the at least one processor is configured to cause the UE to: Receive a control message from a network entity, the control message signaling the activation of a configured uplink BWP associated with a parameter set different from the sidelink BWP, wherein, to deactivate the sidelink BWP, the at least one processor is further configured to cause the UE: to deactivate the sidelink BWP in response to activating the configured uplink BWP according to the control message.

10. The UE according to claim 1, wherein, the at least one processor is configured to cause the UE: determine the priority of the sidelink BWP, wherein, to deactivate the sidelink BWP, the at least one processor is further configured to cause the UE: to deactivate the sidelink BWP in response to the priority of the sidelink BWP being lower than the corresponding priority of the active uplink BWP.

11. A processor for wireless communication, comprising: at least one controller coupled to at least one memory and configured to cause the processor: receive a first configuration for one or more uplink bandwidth parts (BWPs) of a carrier of a serving cell, wherein at least one of the one or more uplink BWPs is an active uplink BWP associated with a first parameter set; receive a second configuration for a sidelink BWP of the carrier of the serving cell, wherein the sidelink BWP is associated with a second parameter set; and deactivate the sidelink BWP in response to the first parameter set being different from the second parameter set.

12. The processor according to claim 11, wherein, the first configuration and the second configuration are received in different messages, and wherein, to deactivate the sidelink BWP, the at least one controller is configured to: stop sidelink communication on the carrier of the serving cell.

13. The processor according to claim 11, wherein, the at least one controller is configured to cause the processor: receive an instruction to switch to a second uplink BWP associated with the second parameter set; and activate the sidelink BWP in response to switching to the second uplink BWP.

14. The processor according to claim 11, wherein, to deactivate the sidelink BWP, the at least one controller is further configured to cause the processor: to deactivate the sidelink BWP in response to none of the one or more uplink BWPs being associated with the second parameter set.

15. The processor according to claim 11, wherein, the at least one controller is configured to cause the processor: receive a control message from a network entity, the control message signaling the activation of the sidelink BWP; and deactivate the active uplink BWP in response to activating the sidelink BWP according to the control message.

16. The processor according to claim 11, wherein, the at least one controller is configured to cause the processor: receive a control message from a network entity, the control message signaling the activation of the sidelink BWP; and Deactivate the active uplink BWP in response to the first parameter set being different from the second parameter set.

17. The processor according to claim 11, wherein, the at least one controller is configured to cause the processor to: receive a control message from a network entity, the control message signaling the activation of the sidelink BWP; and switch from the active uplink BWP to a second uplink BWP associated with the second parameter set in response to activating the sidelink BWP.

18. The processor according to claim 11, wherein, the at least one controller is configured to cause the processor to: receive a control message from a network entity, the control message signaling the activation of a configured uplink BWP associated with a parameter set different from the sidelink BWP, wherein, to deactivate the sidelink BWP, the at least one controller is further configured to cause the processor to: deactivate the sidelink BWP in response to activating the configured uplink BWP according to the control message.

19. The processor according to claim 11, wherein, the at least one controller is configured to cause the processor to: determine the priority of the sidelink BWP, wherein, to deactivate the sidelink BWP, the at least one processor is further configured to cause the processor to: deactivate the sidelink BWP in response to the priority of the sidelink BWP being lower than the corresponding priority of the active uplink BWP.

20. A method performed by a user equipment (UE), the method comprising: receiving a first configuration of one or more uplink bandwidth parts (BWPs) of a carrier for a serving cell, wherein at least one of the one or more uplink BWPs is an active uplink BWP associated with a first parameter set; receiving a second configuration of a sidelink BWP of the carrier for the serving cell, wherein the sidelink BWP is associated with a second parameter set; and deactivating the sidelink BWP in response to the first parameter set being different from the second parameter set.

Images