DESC:
FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENTS RULES, 2003

COMPLETE SPECIFICATION
(See section 10 and rule 13)
1. TITLE OF THE INVENTION

SYSTEMS AND METHODS FOR MANAGING BANDWIDTH PART SWITCHING FOR USER EQUIPMENTS

2. APPLICANT(S)
Name Nationality Address
JIO PLATFORMS LIMITED INDIAN Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India
3. PREAMBLE TO THE DESCRIPTION
The following specification particularly describes the invention and the manner in which it is to be performed.

RESERVATION OF RIGHTS
[0001] A portion of the disclosure of this patent document contains material, which is subject to intellectual property rights such as, but are not limited to, copyright, design, trademark, Integrated Circuit (IC) layout design, and/or trade dress protection, belonging to JIO PLATFORMS LIMITED or its affiliates (hereinafter referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner.
FIELD OF THE DISCLOSURE
[0002] The embodiments of the present disclosure generally relate to wireless communication networks. In particular, the present disclosure relates to systems and methods for managing bandwidth part (BWP) switching for user equipments (UEs).
DEFINITION
[0003] As used in the present disclosure, the following terms are generally intended to have the meaning as set forth below, except to the extent that the context in which they are used to indicate otherwise.
[0004] The expression ‘bandwidth part (BWP)’ used hereinafter in the specification refers to a contiguous subset of total bandwidth that can be allocated to a user equipment (UE) in a communication network (interchangeably referred to as network).
[0005] The expression ‘bandwidth part (BWP) switching’ used hereinafter in the specification refers to a process by which a UE transitions from operating within one BWP to another BWP. This process enables efficient spectrum utilization, optimizes network performance, and meets diverse service requirements.
[0006] The expression ‘BWP switch request’ used hereinafter in the specification refers to a command or signal initiated by a network (for example, a network node such as gNodeB (gNB)) or UE itself to transition the UE from operating within one BWP to another BWP within the network. The BWP switch request is typically triggered when a BWP switch condition is met for the UE. The BWP switch request may include information necessary for the BWP switch, such as timing for the BWP switch.
[0007] The expression ‘BWP switch condition’ used hereinafter in the specification refers to specific criteria or rules that must be met for a UE to transition from one BWP (current BWP) to another BWP (different BWP) within a network. Examples of the BWP switch condition include high data traffic or congestion in the current BWP, specific requirements of an application or service (such as low latency or high data rates), and movement of the UE necessitating a switch to a different BWP to maintain optimal connectivity.
[0008] The expression ‘BWP switch delay period’ used hereinafter in the specification refers to a specific time interval between the initiation of a BWP switch request and the actual execution of the BWP switch request (or the BWP switch). For example, the BWP switch delay period may refer to a specific duration of time during which UE transitions from one BWP to another BWP within a network. During the BWP switch period, the UE may experience minimal or no data transmission activity to ensure a smooth and efficient BWP switch. The BWP switch delay period is crucial for managing the timing of the BWP switch to minimize disruption to ongoing communications and to optimize the overall network performance and resource utilization.
[0009] The expression ‘data communication slots’ used hereinafter in the specification refers to specific time intervals within a network during which data transmission and reception occur between a UE and the network. Each data communication slot may carry a certain amount of data and is part of the overall frame structure used in Time Division Duplex (TDD) system. The data communication slots may be designated for uplink (UE to network) or downlink (network to UE) communication.
[0010] The expression ‘direction types’ used hereinafter in the specification refers to the classification of data communication between a UE and a network based on the direction of data flow between the UE and the network. The two primary direction types are uplink (UL) (data transmission from the UE to the network) and downlink (DL) (data transmission from the network to the UE).
[0011] The expression ‘pre-scheduled data communication slots’ used hereinafter in the specification refers to specific time intervals within a network that have been allocated in advance for data transmission or reception between a UE and the network. These data communication slots are designated ahead of time by a network scheduler to ensure efficient use of network resources. The duration and timing of these slots are determined by Transmission Time Interval (TTI).
[0012] The expression “Transmission Time Interval (TTI)” used hereinafter in the specification refers to time period during which data can be transmitted or received.
[0013] The expression ‘Time Division Duplex (TDD)’ used hereinafter in the specification refers to a method of communication where the same frequency band is used for both UL and DL transmissions, but the transmissions occur at different times.
[0014] The expression ‘service requirements of user equipment (UE)’ refers to specific performance criteria and operational needs that must be met to ensure optimal functionality and user experience for the UE in a communication network. These service requirements influence the decision-making process in managing BWP switching to ensure minimal disruption to the communication activities of the UE.
[0015] These definitions are in addition to those expressed in the art.
BACKGROUND OF THE DISCLOSURE
[0016] The following description of related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.
[0017] In telecommunications, a Bandwidth Part (BWP) refers to a subset of the total carrier bandwidth, comprising contiguous resource blocks within the broader spectrum allocation. BWP switching is a pivotal technique within Fifth Generation (5G) networks and Sixth Generation (6G) networks, enabling dynamic allocation and reallocation of BWPs to meet varying network demands and quality of service (QoS) based requirements across diverse applications such as Internet of Things (IoT) devices, smartphones, and bandwidth-intensive applications like augmented reality and virtual reality. This dynamic allocation optimizes spectrum utilization, enhancing overall network efficiency and performance. BWP switching involves deactivating the current BWP and activating another pre-configured BWP to adjust bandwidth allocation dynamically. This process ensures that different devices and applications receive the necessary bandwidth resources for optimal functionality. The BWP switching is performed based on a BWP switch delay period. The BWP switch delay period denotes the time required for the network to transition between different BWPs. The BWP switch delay period is critical as it directly impacts the QoS for applications and devices reliant on specific bandwidth allocations. Factors influencing the duration of the BWP switch delay period include network configuration, hardware capabilities, and the complexity of the switching process. During the BWP switch delay period, user equipments (UEs) cannot perform transmission or reception activities. Consequently, if downlink (DL) or uplink (UL) scheduling involves data communication slots with low frequency rates overlapping the BWP switch delay period, it can lead to inefficient resource usage and scheduling conflicts, thereby affecting overall network performance.
[0018] There is, therefore, a need in the art to provide a system and a method that can overcome the shortcomings of the existing prior arts.
SUMMARY OF THE DISCLOSURE
[0019] In an exemplary embodiment, a system for managing bandwidth part (BWP) switching for a user equipment (UE) is described. The system includes a receiving unit configured to receive a BWP switch request for the UE. The system further includes a processing unit communicatively coupled to the receiving unit. The processing unit is configured to evaluate, upon receiving the BWP switch request, whether one or more pre-scheduled data communication slots for the UE are impacted by a BWP switch delay period. The processing unit is further configured to determine, in response to evaluating that the one or more pre-scheduled data communication slots are impacted by the BWP switch delay period, whether to postpone the BWP switch request based on one or more service requirements of the UE. Upon determining to postpone the BWP switch request, the processing unit is further configured to delay the BWP switch request until the one or more pre-scheduled data communication slots are scheduled.
[0020] In some embodiments, the receiving unit is configured to receive the BWP switch request for the UE when a BWP switch condition is met.
[0021] In some embodiments, the one or more pre-scheduled data communication slots are impacted by the BWP switch delay period if the one or more pre-scheduled data communication slots fall within the BWP switch delay period or overlap with the BWP switch delay period.
[0022] In some embodiments, the processing unit is further configured to halt the scheduling of the UE until the BWP switch request is executed.
[0023] In some embodiments, the one or more service requirements of the UE include latency service requirement, throughput service requirement, and Quality of Service (QoS) based requirement.
[0024] In some embodiments, the processing unit is further configured to check whether the one or more pre-scheduled data communication slots have at least one of an uplink scheduling and a downlink scheduling.
[0025] In another exemplary embodiment, a method for managing bandwidth part (BWP) switching for a user equipment (UE) is described. The method includes receiving, by a receiving unit, a BWP switch request for the UE. The method further includes, upon receiving the BWP switch request, evaluating, by a processing unit, whether one or more pre-scheduled data communication slots for the UE are impacted by a BWP switch delay period. The method further includes, in response to evaluating that the one or more pre-scheduled data communication slots are impacted by the BWP switch delay period, determining, by the processing unit, whether to postpone the BWP switch request based on one or more service requirements of the UE. The method includes, upon determining to postpone the BWP switch request, delaying, by the processing unit, the BWP switch request until the one or more pre-scheduled data communication slots are scheduled.
[0026] In some embodiments, the BWP switch request for the UE is received when a BWP switch condition is met.
[0027] In some embodiments, the one or more pre-scheduled data communication slots are impacted by the BWP switch delay period if the one or more pre-scheduled data communication slots fall within the BWP switch delay period or overlap with the BWP switch delay period.
[0028] In some embodiments, the method further comprising halting scheduling of the UE until the BWP switch request is executed.
[0029] In some embodiments, the one or more service requirements of the UE include latency service requirement, throughput service requirement, and Quality of Service (QoS) based requirement.
[0030] In some embodiments, the method further comprising checking whether the one or more pre-scheduled data communication slots have at least one of an uplink scheduling and a downlink scheduling.
[0031] In yet another exemplary embodiment, a user equipment (UE) is described. The UE is communicatively coupled with a network, the coupling comprises steps of receiving, by the network, a connection request from the UE, sending, by the network, an acknowledgment of the connection request to the UE and transmitting a plurality of signals in response to the connection request, the network is configured for managing bandwidth part (BWP) switching for the UE. The method includes receiving, by a receiving unit, a BWP switch request for the UE. The method further includes, upon receiving the BWP switch request, evaluating, by a processing unit, whether one or more pre-scheduled data communication slots for the UE are impacted by a BWP switch delay period. The method further includes, in response to evaluating that the one or more pre-scheduled data communication slots are impacted by the BWP switch delay period, determining, by the processing unit, whether to postpone the BWP switch request based on one or more service requirements of the UE. The method includes, upon determining to postpone the BWP switch request, delaying, by the processing unit, the BWP switch request until the one or more pre-scheduled data communication slots are scheduled.
[0032] The foregoing general description of the illustrative embodiments and the following detailed description thereof are merely exemplary aspects of the teachings of this disclosure and are not restrictive.
OBJECTIVES OF THE DISCLOSURE
[0033] Some of the objects of the present disclosure, which at least one embodiment herein achieves, are as follows:
[0034] An objective of the present disclosure is to provide a system and a method for delaying or postponing bandwidth part (BWP) switching for user equipments (UEs).
[0035] An objective of the present disclosure is to provide a system and a method for managing bandwidth part (BWP) switching to minimize scheduling and resource wastage.
[0036] An objective of the present disclosure is to improve the overall user experience by optimizing BWP switching to minimize disruptions and maintain consistent service quality.
[0037] Other objectives and advantages of the present disclosure will be more apparent from the following description, which is not intended to limit the scope of the present disclosure.
BRIEF DESCRIPTION OF DRAWINGS
[0038] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes the disclosure of electrical components, electronic components or circuitry commonly used to implement such components.
[0039] FIG. 1 illustrates an exemplary network architecture implementing a system for managing bandwidth part (BWP) switching for a user equipment (UE), in accordance with embodiments of the present disclosure.
[0040] FIG. 2 illustrates a block diagram of the system for managing BWP switching for the UE, in accordance with embodiments of the present disclosure.
[0041] FIG. 3 illustrates an example flow diagram for managing BWP switching for the UE, in accordance with embodiments of the present disclosure.
[0042] FIG. 4 illustrates an exemplary flowchart of a method for managing BWP switching for the UE, in accordance with embodiments of the present disclosure.
[0043] FIG. 5 illustrates a computer system in which or with which the embodiments of the present disclosure may be implemented.
[0044] The foregoing shall be more apparent from the following more detailed description of the disclosure.
LIST OF REFERENCE NUMERALS

100 – Network architecture
102 – System
104 – Network
106 – Network Node
108-1, 108-2…108-N – User equipment(s)
110-1, 110-2…110-N – User(s)
200 – Block Diagram
202 – One or more processor(s)
204 – Memory
206 – Plurality of interfaces
208 – Receiving Unit
210 – Processing Unit
212 – Database
300 – Flow Diagram
400 – Flow Chart
500 – Computer System
510 – External Storage Device
520 – Bus
530 – Main Memory
540 – Read Only Memory
550 – Mass Storage Device
560 – Communication Port
570 – Processor
DETAILED DESCRIPTION OF THE DISCLOSURE
[0045] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein. Example embodiments of the present disclosure are described below, as illustrated in various drawings in which like reference numerals refer to the same parts throughout the different drawings.
[0046] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.
[0047] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.
[0048] Also, it is noted that individual embodiments may be described as a process that is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.
[0049] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive like the term “comprising” as an open transition word without precluding any additional or other elements.
[0050] Reference throughout this specification to “one embodiment” or “an embodiment” or “an instance” or “one instance” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
[0051] The terminology used herein is to describe particular embodiments only and is not intended to be limiting the disclosure. As used herein, the singular forms “a”, “an”, and “the” are intended to include the plural forms as well, unless the context indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. As used herein, the term “and/or” includes any combinations of one or more of the associated listed items. It should be noted that the terms “mobile device”, “user equipment”, “user device”, “communication device”, “device” and similar terms are used interchangeably for the purpose of describing the present disclosure. These terms are not intended to limit the scope of the present disclosure or imply any specific functionality or limitations on the described embodiments. The use of these terms is solely for convenience and clarity of description. The present disclosure is not limited to any particular type of device or equipment, and it should be understood that other equivalent terms or variations thereof may be used interchangeably without departing from the scope of the present disclosure as defined herein.
[0052] As used herein, an “electronic device”, or “portable electronic device”, or “user device” or “communication device” or “user equipment” or “device” refers to any electrical, electronic, electromechanical and computing device. The user device is capable of receiving and/or transmitting one or parameters, performing function/s, communicating with other user devices and transmitting data to the other user devices. The user equipment may have a processor, a display, a memory, a battery and an input-means such as a hard keypad and/or a soft keypad. The user equipment may be capable of operating on any radio access technology including but not limited to IP-enabled communication, Zig Bee, Bluetooth, Bluetooth Low Energy, Near Field Communication, Z-Wave, Wi-Fi, Wi-Fi direct, etc. For instance, the user equipment may include, but not limited to, a mobile phone, smartphone, virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other device as may be obvious to a person skilled in the art for implementation of the features of the present disclosure.
[0053] Further, the user device may also comprise a “processor” or “processing unit” includes processing unit, wherein processor refers to any logic circuitry for processing instructions. The processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a digital signal processing (DSP) core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor is a hardware processor.
[0054] As portable electronic devices and wireless technologies continue to improve and grow in popularity, the advancing wireless technologies for data transfer are also expected to evolve and replace the older generations of technologies. In the field of wireless data communications, the dynamic advancement of various generations of cellular technology are also seen. The development, in this respect, has been incremental in the order of Second Generation (2G), Third Generation (3G), Fourth Generation (4G), Fifth Generation (5G), and Sixth Generation (6G), and more such generations are expected to continue in the forthcoming time.
[0055] Radio Access Technology (RAT) refers to the technology used by mobile devices/ user equipment (UE) to connect to a cellular network. It refers to the specific protocol and standards that govern the way devices communicate with base stations, which are responsible for providing the wireless connection. Further, each RAT has its own set of protocols and standards for communication, which define the frequency bands, modulation techniques, and other parameters used for transmitting and receiving data. Examples of RATs include Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA), Universal Mobile Telecommunications System (UMTS), Long-Term Evolution (LTE), 5G, and 6G. The choice of RAT depends on various factors, including the network infrastructure, the available spectrum, and the mobile device's/device's capabilities. Mobile devices often support multiple RATs, allowing the mobile devices to connect to different types of networks and provide optimal performance based on the available network resources.
[0056] While considerable emphasis has been placed herein on the components and component parts of the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiment as well as other embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be interpreted merely as illustrative of the disclosure and not as a limitation.
[0057] In telecommunications, a Bandwidth Part (BWP) refers to a subset of the total carrier bandwidth, comprising contiguous resource blocks within the broader spectrum allocation. BWP switching is a pivotal technique within Fifth Generation (5G) networks and Sixth Generation (6G) networks, enabling dynamic allocation and reallocation of BWPs to meet varying network demands and quality of service (QoS) based requirements across diverse applications such as Internet of Things (IoT) devices, smartphones, and bandwidth-intensive applications like augmented reality and virtual reality. This dynamic allocation optimizes spectrum utilization, enhancing overall network efficiency and performance. BWP switching involves deactivating the current BWP and activating another pre-configured BWP to adjust bandwidth allocation dynamically. This process ensures that different devices and applications receive the necessary bandwidth resources for optimal functionality. The BWP switching is performed based on a BWP switch delay period. The BWP switch delay period denotes the time required for the network to transition between different BWPs. The BWP switch delay period is critical as it directly impacts the QoS for applications and devices reliant on specific bandwidth allocations. Factors influencing the duration of the BWP switch delay period include network configuration, hardware capabilities, and the complexity of the switching process. During the BWP switch delay period, user equipments (UEs) cannot perform transmission or reception activities. Consequently, if downlink (DL) or uplink (UL) scheduling involves data communication slots with low frequency rates overlapping the BWP switch delay period, it can lead to inefficient resource usage and scheduling conflicts, thereby affecting overall network performance.
[0058] Accordingly, there is a need for systems and methods for managing BWP switching for UEs to minimize scheduling and resource wastage.
[0059] Carrier Bandwidth Part is a contiguous set of physical resource blocks, selected from a contiguous subset of the common resource blocks for a given numerology (u) on a given carrier.
[0060] BWP selection and switching can be done with different mechanisms as listed below:
• Radio Resource Control (RRC)-Based Adaptation: It is more suitable for semi-static cases since the processing of RRC messages requires extra time, letting the latency reach ~10 msec. Due to longer switching latency and signaling overhead, an RRC-based method can be used for configuring a BWP set at any stage of the call, or for slow adaptation type services (e.g., voice) where the resource allocation is not changing rapidly within the same data session.
• Medium Access Control (MAC) Control Element (CE): It is used upon initiation of Random Access procedure.
• Downlink Control Information (DCI)-Based Adaptation: It is based on Physical Downlink Control Channel (PDCCH) channel where a specific BWP can be activated by BWP indicator in DCI Format 0_1 (UL Grant) and Format 1-1 (DL scheduling). This method better fits on-the-fly BWP switching as using this method the latency is as low as 2 msec. However, this method requires additional considerations for error handling as UE may fail to decode the DCI with BWP activation/deactivation command.
• Timer-Based implicit fallback to default BWP is a mechanism designed to mitigate possible DCI errors. If the UE is not explicitly scheduled with a BWP after the timer expires, it will automatically switch to the default BWP.
[0061] Bandwidth Switching operation DCI-based
[0062] BWP switching means deactivating the currently active BWP and activating another configured BWP. In TDD, DL and UL BWPs differ only by the transmission bandwidth and numerology; and they are switched together.

µ New Radio (NR) Slot length (ms) BWP switch delay TBWPswitchDelay (slots)
Type 1 Note 1 Type 2 Note 1
0 1 1 3
1 0.5 2 5
2 0.25 3 9
3 0.125 6 18
Note 1: Depends on UE capability.
Note 2: If the BWP switch involves changing of SubCarrier Spacing (SCS), the BWP switch delay is determined by the smaller SCS between the SCS before BWP switch and the SCS after the BWP switch.
[0063] When BWP switching happens, there is a switching delay at UE due to e.g., radio frequency (RF) retuning. Considering this aspect, the delay requirement on BWP switching is defined in the NR specification. For DCI-based BWP switching, the delay requirement is the minimum allowable slot offset between the DL slot in which the UE received BWP switching DCI and the first slot in which the UE is able to receive Physical Downlink Shared Channel (PDSCH) for DL BWP switching or transmit Physical Uplink Shared Channel (PUSCH) for UL BWP switching on the new BWP.
[0064] DL/UL-SCH data transfer
[0065] Downlink assignments received on the PDCCH both indicate that there is a transmission on a DL-SCH for a particular MAC entity and provide the relevant Hybrid Automatic Repeat Request (HARQ) information.
[0066] Uplink grant is either received dynamically on the PDCCH, in a Random Access Response, configured semi-persistently by RRC or determined to be associated with the PUSCH resource of MSGA. The MAC entity shall have an uplink grant to transmit on the UL-SCH. To perform the requested transmissions, the MAC layer receives HARQ information from lower layers.
[0067] Slot Configuration
[0068] If a UE is provided tdd-UL-DL-ConfigurationCommon, the UE sets the slot format per slot over a number of slots as indicated by tdd-UL-DL-ConfigurationCommon.
The tdd-UL-DL-ConfigurationCommon provides:
• a reference SCS configuration by referenceSubcarrierSpacing
• a pattern1
The pattern1 provides:
• a slot configuration period of P msec by dl-UL-TransmissionPeriodicity
• a number of slots with only downlink symbols by nrofDownlinkSlots
• a number of downlink symbols by nrofDownlinkSymbols
• a number of slots with only uplink symbols by nrofUplinkSlots
• a number of uplink symbols by nrofUplinkSymbols

[0069] The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing a system and a method for handling or managing BWP switching for user equipment (UE) to minimize scheduling and resource wastage. According to an implementation, the system and the method may delay or postpone the BWP switch if one or more pre-scheduled data communication slots for the UE fall within a BWP switch delay period or overlap with the BWP switch delay period. The BWP switch is delayed until the one or more pre-scheduled data communication slots are scheduled. Further, scheduling of the UE is halted until the BWP switch is executed.
[0070] The various embodiments throughout the disclosure will be explained in more detail with reference to FIG. 1- FIG. 5.
[0071] FIG. 1 illustrates an exemplary network architecture 100implementing a system 102 for managing bandwidth part (BWP) switching for a user equipment 108, in accordance with an embodiment of the present disclosure.
[0072] As illustrated in FIG. 1, the network architecture 100 may include the system 102, a network 104 (interchangeably referred to as communication network 104 or telecommunications network 104), a network node 106, and one or more user equipments (UEs) 108-1, 108-2…108-N associated with one or more users 110-1, 110-2…110-N. A person of ordinary skill in the art will understand that the one or more users 110-1, 110-2…110-N may be collectively referred to as the user 110 or users 110. Similarly, a person of ordinary skill in the art will understand that one or more UEs 108-1, 108-2…108-N may be collectively referred to as the UE 108 or the UEs 108. Although only three UEs 108 are depicted in FIG. 1, however, any number of the UEs 108 may be included without departing from the scope of the ongoing description.
[0073] In an embodiment, the UE 108 may include smart devices operating in a smart environment, for example, an Internet of Things (IoT) system. In such an embodiment, the UE 108 may include, but are not limited to, smartphones, smart watches, smart sensors (e.g., mechanical, thermal, electrical, magnetic, etc.), networked appliances, networked peripheral devices, networked lighting system, communication devices, networked vehicle accessories, networked vehicular devices, smart accessories, tablets, a smart television (TV), computers, a smart security system, a smart home system, other devices for monitoring or interacting with or for the users 110 and/or entities, or any combination thereof. A person of ordinary skill in the art will appreciate that the UE 108 may include, but not limited to, intelligent, multi-sensing, network-connected devices, that may integrate seamlessly with each other and/or with a central server or a cloud-computing system or any other device that is network-connected.
[0074] Additionally, in some embodiments, the UE 108 may include, but not limited to, a handheld wireless communication device (e.g., a mobile phone, a smartphone, a phablet device, and so on), a wearable computer device (e.g., a head-mounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a Global Positioning System (GPS) device, a laptop computer, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, and/or any other type of computer device with wireless communication capabilities, and the like. In an embodiment, the UE 108 may include, but are not limited to, any electrical, electronic, electromechanical, or equipment, or a combination of one or more of the above devices, such as virtual reality (VR) devices, augmented reality (AR) devices, a laptop, a general-purpose computer, a desktop, a personal digital assistant, a tablet computer, a mainframe computer, or any other computing device. Further, the UE 108 may include one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as a camera, an audio aid, a microphone, a keyboard, and input devices for receiving input from the user 110 or an entity such as a touchpad, a touch-enabled screen, an electronic pen, and the like. A person of ordinary skill in the art will appreciate that the UE 108 may not be restricted to the mentioned devices and various other devices may be used.
[0075] Referring to FIG. 1, the UE 108 may communicate with the system 102 through the network 104 (also referred to as communication network 104) for sending or receiving various types of data. In an embodiment, the network 104 may include at least one of a 5G network, 6G network, or the like. The network 104 may enable the UE 108 to communicate with other devices in the network architecture 100 and/or with the system 102. The network 104 may include a wireless card or some other transceiver connection to facilitate this communication. In another embodiment, the network 104 may be implemented as, or include any of a variety of different communication technologies such as a wide area network (WAN), a local area network (LAN), a wireless network, a mobile network, a Virtual Private Network (VPN), the Internet, the Public Switched Telephone Network (PSTN), or the like.
[0076] In an embodiment, the network 104 may include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. The network 104 may also include, by way of example but not limitation, one or more of a radio access network (RAN), a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof.
[0077] In an embodiment, the UE 108 is communicatively coupled with the network 104. The network 104 may receive a connection request from the UE 108. The network 104 may send an acknowledgment of the connection request to the UE 108. The UE 108 may transmit a plurality of signals in response to the connection request. The plurality of signals is responsible for communicating with the system 102 to manage BWP switching for the UE 108.
[0078] According to an implementation, the network node 106 may be a base station or a gNodeB (gNB). The network node 106 may be in communication with the UE 108 and the system 102 through the network 104. Although it has been shown that the network node 106 is implemented outside the system 102, in some implementations, the network node 106 may be implemented within the system 102.
[0079] Although FIG. 1 shows exemplary components of the network architecture 100, in other embodiments, the network architecture 100 may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 1. Additionally, or alternatively, one or more components of the network architecture 100 may perform functions described as being performed by one or more other components of the network architecture 100.
[0080] FIG. 2 illustrates an exemplary block diagram 200 of the system 102 for managing BWP switching for the UE 108, in accordance with an embodiment of the present disclosure. FIG. 2 is described in conjunction with FIG. 1.
[0081] Referring to FIG. 1B, in an embodiment, the system 102 may include one or more processor(s) 202, a memory 204, a plurality of interface(s) 206, a receiving unit 208, a processing unit 210, and a database 212. The one or more processor(s) 202 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and/or any devices that process data based on operational instructions. Among other capabilities, the one or more processor(s) 202 may be configured to fetch and execute computer-readable instructions stored in the memory 204 of the system 102. The memory 204 may be configured to store one or more computer-readable instructions or routines in a non-transitory computer readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory 204 may include any non-transitory storage device including, for example, volatile memory such as a Random Access Memory (RAM), or a non-volatile memory such as an Erasable Programmable Read Only Memory (EPROM), a flash memory, and the like.
[0082] In an embodiment, the interface(s) 206 may include a variety of interfaces, for example, interfaces for data input and output devices (I/O), storage devices, and the like. The interface(s) 206 may facilitate communication through the system 102. The interface(s) 206 may also provide a communication pathway for one or more components of the system 102. Examples of such components include, but are not limited to, the receiving unit 208, the processing unit 210, and the database 212. In an implementation, the network node 106 may be implemented within the processing unit 210.
[0083] The processing unit 210 may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing unit 210. In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing unit 210 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processing unit 210 may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing unit 210. In such examples, the system may comprise the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the system and the processing resource. In other examples, the processing unit 210 may be implemented by electronic circuitry. In an embodiment, the database 212 includes data that may be either stored or generated because of functionalities implemented by any of the components of the processor 202 or the processing unit 210.
[0084] A data communication slot is a time interval during which specific communication activities (such as transmitting or receiving data) occur between the UE 108 and the network 104. In 5G and 6G networks, a data communication slot typically includes multiple symbols (for example, 14 symbols in a 1 millisecond (ms) slot with 15 kilohertz (kHz) subcarrier spacing (SCS). The duration of a data communication slot depends on the SCS. For example, with a 15 kHz SCS, a data communication slot is 1 ms long. However, higher SCS values, like 30 kHz or 60 kHz, result in shorter slot durations (0.5 ms and 0.25 ms, respectively). A data communication slot can be of a specific direction type. For example, a data communication slot can be a downlink (DL) data communication slot or an uplink (UL) data communication slot. DL data communication slots are dedicated to transmitting data from the network 104 to the UE 108. The DL data communication slots carry data such as web pages, streaming content, and other information intended for the user 110. UL data communication slots are dedicated to transmitting data from the UE 108 to the network 104. The UL data communication slots carry data such as voice, user-generated content, or responses to the downlink transmissions of the network 104. The DL data communication slots may be used for transmitting data from the network 104 to the UE 108. The UL data communication slots may be used for transmitting data from the UE 108 to the network 104.
[0085] During a BWP switch, the UE 108 may temporarily halt its transmission and reception activities, leading to a period of inactivity. Suppose a BWP switch is triggered at a time when a critical data communication slot (especially a low frequency uplink or downlink data communication slot) is scheduled. In that case, it can result in wasted resources and degraded service quality.
[0086] In an implementation, data communication slots may be pre-scheduled for the UE 108. The data communication slots that are pre-scheduled for the UE 108 may be referred to as pre-scheduled data communication slots. These data communication slots are planned and reserved before they are used, based on scheduling decisions made by the network 104. In examples, these data communication slots may be determined by a network scheduler before they occur. For example, the network scheduler may allocate these data communication slots some Transmission Time Intervals (TTIs) before they are used. TTIs are time periods during which data can be transmitted or received. For example, if a data communication slot is scheduled to occur in the next frame or subframe, the scheduling decisions and slot allocations are made a few TTIs ahead.
[0087] In operation, when a BWP switch condition is met for the UE 108, the receiving unit 208 may be configured to receive a BWP switch request for the UE 108 from a network source, such as the network node 106, from other network controllers that manage the BWP switching process for the UE 108, or from the UE 108 itself. In examples, the BWP switch condition refers to a specific situation or a set of criteria or triggers that must be met to initiate a switch from one BWP to another BWP in the network 104. For example, factors such as high traffic load, changes in network conditions, or UE requirements may necessitate BWP switching. For example, if it is detected that the UE 108 is using a BWP that is becoming congested or no longer meets the requirements of the UE 108, a BWP switch condition might be met. The BWP switch condition may prompt the network 104 to switch to a different BWP with better performance characteristics or more suitable parameters.
[0088] Additionally, the BWP switch request may include information about the conditions or triggers that have been met, necessitating the BWP switch. This may include factors such as changes in the traffic load, the need to optimize power consumption or to meet specific service requirements of the UE 108.
[0089] Upon receiving the BWP switch request, the receiving unit 208 may forward the BWP switch request and relevant information pertaining to the BWP switch request to the processing unit 210 for further action. The processing unit 210 is configured to evaluate whether one or more pre-scheduled data communication slots for the UE 108 are impacted by a BWP switch delay period. The BWP switch delay period refers to a specific timeframe during which the UE 108 switches from one BWP to another BWP. During this delay, the UE 108 temporarily halts all transmission and reception activities. In examples, the BWP switch delay period may be determined based on prescheduling delta (i.e., time between pre-scheduled data communication slots for upcoming slots and actual scheduling for the slot). The processing unit 210 is further configured to check whether the one or more pre-scheduled data communication slots have at least one of an uplink scheduling and a downlink scheduling.
[0090] In examples, the one or more pre-scheduled data communication slots may be of a specific direction type. For example, the one or more pre-scheduled data communication slots may have downlink/uplink scheduling for the UE 108. For example, the specific direction type comprises one of an uplink type and a downlink type. In this context, there may be a possibility that one or more pre-scheduled data communication slots for the UE 108 might be affected by the BWP switch delay period. For example, these data communication slots could experience some degree of disruption, delay, or inefficiency in data transmission or reception due to the timing of the BWP switch. In examples, the one or more pre-scheduled data communication slots are impacted by the BWP switch delay period if the one or more pre-scheduled data communication slots fall within the BWP switch delay period or overlap with the BWP switch delay period.
[0091] According to an implementation, the processing unit 210 may identify which of the pre-scheduled data communication slots (either UL data communication slots or DL data communication slots) may fall within the BWP switch delay period or overlap with the BWP switch delay period. In an implementation, the processing unit 210 may examine the timing of pre-scheduled data communication slots to determine if any of these data communication slots are scheduled during the BWP switch delay period. Suppose any of the data communication slots is impacted by the BWP switch delay period. In that case, this may disrupt service quality, as the UE 108 will not be able to perform transmission and/or reception activities during the BWP switch.
[0092] According to an implementation, in response to evaluating that the one or more pre-scheduled data communication slots are impacted by a BWP switch delay period, the processing unit 210 may determine whether to postpone the BWP switch request (or the BWP switch) based on one or more service requirements of the UE 108. In examples, the one or more service requirements of the UE 108 refer to specific performance criteria and operational needs that must be met to ensure optimal functionality and user experience for the UE 108 in the network 104. The one or more service requirements influence the decision-making process in managing BWP switching to ensure minimal disruption to the communication activities of the UE 108. The one or more service requirements of the UE 108 include, but are not limited to, latency service requirement, throughput service requirement, and Quality of Service (QoS) based requirement.
[0093] For example, the processing unit 210 may determine whether to postpone the BWP switch request based on error and latency requirements of UE service. In examples, for services requiring low error rate, the processing unit 210 may determine to postpone or delay the BWP switch request (or the BWP switch). For instance, if the UE 108 is involved in applications needing high reliability, such as medical data transmission or industrial controls, the processing unit 210 may delay the BWP switch request to avoid the potential loss of critical data during the BWP switch as any errors or delays caused by the BWP switch may result in vital information being lost leading to severe consequences. In another example, if the UE 108 is involved in low-latency communication, such as video conferencing, the processing unit 210 may delay the BWP switch request if it affects the network services.
[0094] According to an implementation, to minimize disruption to network services, upon determining to postpone the BWP switch request (or the BWP switch), the processing unit 210 may delay the BWP switch request until the one or more pre-scheduled data communication slots are scheduled. This ensures that the UE 108 continues its data transmission or reception activities without interruption during the pre-scheduled data communication slots. By postponing or delaying the BWP switch request, the processing unit 210 minimizes the risk of service degradation, ensuring that the UE 108 maintains high performance and reliability. To manage the transition effectively, the processing unit 210 is configured to temporarily stop or halt the scheduling of new data communication slots for the UE 108 until the BWP switch request is executed.
[0095] To manage the transition effectively, the processing unit 210 also temporarily halts the scheduling of new data communication slots for the UE 108. This halt is crucial because it prevents new data communication slots from being scheduled when the BWP switch request (or the BWP switch) is pending, which could lead to potential disruptions if the BWP switch were to occur. The halt in scheduling ensures that the BWP switch can be executed smoothly without overlapping with any critical communication activities. Once the BWP switch request is completed, the scheduling of new data communication slots resumes, allowing the UE 108 to continue normal operations on the new BWP. Therefore, the processing unit 210 ensures that the BWP switching is managed in a way that aligns with the ongoing communication needs of the UE 108, thereby reducing the risk of service interruptions and maintaining optimal network performance.
[0096] FIG. 3 illustrates an example flow diagram 300 for managing BWP switching for the UE 108, in accordance with an embodiment of the present disclosure.
[0097] At step 302 of the flow diagram 300, the system 102 may receive a BWP switch trigger (or BWP switch request) for the UE 108. In an example, the system 102 may receive the BWP switch trigger from the network node 106 or the UE 108 itself. In an implementation, the system 102 may receive the BWP switch trigger when a BWP switch condition is met for the UE 108.
[0098] At step 304, the system 102 may check if one or more pre-scheduled data communication slots (pre-processed slots) for the UE 108 are impacted by a BWP switch delay period. The system 102 may further check if the one or more pre-scheduled data communication slots have downlink or uplink scheduling. The system 102 may further evaluate whether the one or more pre-scheduled data communication slots for the UE 108 are impacted by the BWP switch delay period. In examples, the one or more pre-scheduled data communication slots are impacted by the BWP switch delay period if the one or more pre-scheduled data communication slots fall within the BWP switch delay period or overlap with the BWP switch delay period. The system 102 further determines, in response to evaluating that the one or more pre-scheduled data communication slots are impacted by the BWP switch delay period, whether to postpone the BWP switch based on one or more service requirements of the UE 108.
[0099] At step 306 of the flow diagram 300, upon determining to postpone the BWP switch, the system 102 delays the BWP switch until the one or more pre-scheduled data communication slots are scheduled. In an implementation, the system 102 evaluates the impact of the BWP switch on the ongoing and upcoming communication needs of the UE 108. Suppose the BWP switch is likely to disrupt critical data communication slots (either uplink or downlink) that are pre-scheduled and crucial for maintaining service quality. In that case, the system 102 may determine to postpone the BWP switch. For instance, if the UE 108 is engaged in activities requiring uninterrupted service, such as a real-time video call or transmitting critical data, any disruption during the BWP switch could degrade service quality or result in data loss.
[00100] At step 308, once the one or more pre-scheduled data communication slots are scheduled, the system 102 sends or executes the BWP switch. In an implementation, the system 102 schedules the BWP switch after the pre-scheduled data communication slots are completed.
[00101] While the steps 302, 304, 306, and 308 of FIG. 3 have been described as performed by the system 102, it should be understood that in some embodiments, these steps may alternatively be performed by the network node 106.
[00102] FIG. 4 illustrates an exemplary flowchart of a method 400 for managing BWP switching for the UE 108, in accordance with an embodiment of the present disclosure.
[00103] At step 402, the method 400 includes receiving a BWP switch request for the UE 108. The BWP switch request may be received from the network node 106 or the UE 108 itself. In an implementation, the network node 106 and/or the receiving unit 208 of the system 102 may receive the BWP switch request for the UE 108. The BWP switch request may be received when a BWP switch condition is met. Examples of the BWP switch condition include high data traffic or congestion in the current BWP, specific requirements of an application or service of the UE 108, such as low latency or high data rates, and movement of the UE 108 necessitating a switch to a different BWP to maintain optimal connectivity.
[00104] At step 404, the method 400 includes evaluating whether one or more pre-scheduled data communication slots for the UE 108 are impacted by a BWP switch delay period. The BWP switch delay period may refer to a specific duration of time during which UE 108 transitions from one BWP to another BWP within the network 104. The one or more pre-scheduled data communication slots are impacted by the BWP switch delay period if the one or more pre-scheduled data communication slots fall within the BWP switch delay period or overlap with the BWP switch delay period. In an implementation, the network node 106 and/or the processing unit 210 of the system 102 may be configured to evaluate whether one or more pre-scheduled data communication slots for the UE 108 are impacted by the BWP switch delay period. In an implementation, the processing unit 210 may be configured to check whether the one or more pre-scheduled data communication slots have at least one of an uplink scheduling and a downlink scheduling.
[00105] At step 406, the method 400 includes determining, in response to evaluate that the one or more pre-scheduled data communication slots are impacted by the BWP switch delay period, whether to postpone the BWP switch request based on one or more service requirements of the UE 108. In an implementation, the network node 106 and/or the processing unit 210 of the system 102 may be configured to determine whether to postpone the BWP switch request based on one or more service requirements of the UE 108 in response to evaluating that the one or more pre-scheduled data communication slots are impacted by the BWP switch delay period.
[00106] At step 406, the method 400 includes upon determining to postpone the BWP switch request, delaying the BWP switch request until the one or more pre-scheduled data communication slots are scheduled. In an implementation, upon determining to postpone the BWP switch request, the network node 106 and/or the processing unit 210 may delay the BWP switch request until the one or more pre-scheduled data communication slots are scheduled. In some implementations, the network node 106 and/or the processing unit 210 may temporarily halt the scheduling of the UE 108 until the BWP switch request is executed.
[00107] In an exemplary embodiment, the UE 108 is described. The UE 108 is communicatively coupled with the network 104, the coupling comprises steps of receiving, by the network 104, a connection request from the UE 108, sending, by the network 104, an acknowledgment of the connection request to the UE 108 and transmitting a plurality of signals in response to the connection request, the network 104 is configured for managing BWP switching for the UE 108. The method includes receiving a BWP switch request for the UE 108. The method further includes evaluating, upon receiving the BWP switch request, whether one or more pre-scheduled data communication slots for the UE 108 are impacted by a BWP switch delay period. The method further includes determining, in response to evaluating that the one or more pre-scheduled data communication slots are impacted by the BWP switch delay period, whether to postpone the BWP switch request based on one or more service requirements of the UE 108. The method further includes, upon determining to postpone the BWP switch request, delaying the BWP switch request until the one or more pre-scheduled data communication slots are scheduled.
[00108] In an embodiment, a Serving Cell may be configured with one or multiple BWPs, and the maximum number of BWP per Serving Cell. The BWP switching for a Serving Cell is used to activate an inactive BWP and deactivate an active BWP at a time. The BWP switching is controlled by the PDCCH indicating a downlink assignment or an uplink grant, by the bwp-InactivityTimer, by RRC signalling, or by the MAC entity itself upon initiation of Random Access procedure. Upon RRC (re-)configuration of firstActiveDownlinkBWP-Id and/or firstActiveUplinkBWP-Id for SpCell or activation of an SCell, the DL BWP and/or UL BWP indicated by firstActiveDownlinkBWP-Id and/or firstActiveUplinkBWP-Id respectively is active without receiving PDCCH indicating a downlink assignment or an uplink grant. The active BWP for a Serving Cell is indicated by either RRC or PDCCH. For unpaired spectrum, a DL BWP is paired with a UL BWP, and BWP switching is common for both UL and DL.
[00109] Upon initiation of the Random Access procedure on a Serving Cell, after the selection of carrier for performing Random Access procedure as specified, the MAC entity shall for the selected carrier of this Serving Cell:
- if Physical Random Access Channel (PRACH) occasions are not configured for the active UL BWP:
- switch the active UL BWP to BWP indicated by initialUplinkBWP;
- if the Serving Cell is a SpCell:
- switch the active DL BWP to BWP indicated by initialDownlinkBWP.
- else:
- if the Serving Cell is a SpCell:
- if the active DL BWP does not have the same bwp-Id as the active UL BWP:
- switch the active DL BWP to the DL BWP with the same bwp-Id as the active UL BWP.
- stop the bwp-InactivityTimer associated with the active DL BWP of this Serving Cell, if running.
- if the Serving Cell is SCell:
- stop the bwp-InactivityTimer associated with the active DL BWP of SpCell, if running.
- perform the Random Access procedure on the active DL BWP of SpCell and active UL BWP of this Serving Cell.
[00110] If the MAC entity receives a PDCCH for BWP switching of a Serving Cell, the MAC entity shall:
- if there is no ongoing Random Access procedure associated with this Serving Cell; or
- if the ongoing Random Access procedure associated with this Serving Cell is successfully completed upon reception of this PDCCH addressed to Cell Radio Network Temporary Identifier (C-RNTI)
- perform BWP switching to a BWP indicated by the PDCCH.
[00111] If the MAC entity receives a PDCCH for BWP switching for a Serving Cell while a Random Access procedure associated with that Serving Cell is ongoing in the MAC entity, it is up to UE implementation whether to switch BWP or ignore the PDCCH for BWP switching, except for the PDCCH reception for BWP switching addressed to the C-RNTI for successful Random Access procedure completion in which case the UE shall perform BWP switching to a BWP indicated by the PDCCH. Upon reception of the PDCCH for BWP switching other than successful contention resolution, 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 after performing the BWP switching; if the MAC decides to ignore the PDCCH for BWP switching, the MAC entity shall continue with the ongoing Random Access procedure on the Serving Cell.
[00112] Upon reception of RRC (re-)configuration for BWP switching for a Serving Cell while a Random Access procedure associated with that Serving Cell is ongoing in the MAC entity, the MAC entity shall stop the ongoing Random Access procedure and initiate a Random Access procedure after performing the BWP switching.
[00113] The MAC entity shall for each activated Serving Cell configured with bwp-InactivityTimer:
- if the defaultDownlinkBWP-Id is configured, and the active DL BWP is not the BWP indicated by the defaultDownlinkBWP-Id; or
- if the defaultDownlinkBWP-Id is not configured, and the active DL BWP is not the initialDownlinkBWP:
- if a PDCCH addressed to C-RNTI or configured scheduling radio network temporary identifier (CS-RNTI) indicating downlink assignment or uplink grant is received on the active BWP; or
- if a PDCCH addressed to C-RNTI or CS-RNTI indicating downlink assignment or uplink grant is received for the active BWP; or
- if a MAC PDU is transmitted in a configured uplink grant or received in a configured downlink assignment:
- if there is no ongoing Random Access procedure associated with this Serving Cell; or
- if the ongoing Random Access procedure associated with this Serving Cell is successfully completed upon reception of this PDCCH addressed to C-RNTI
- start or restart the bwp-InactivityTimer associated with the active DL BWP.
- if the bwp-InactivityTimer associated with the active DL BWP expires:
- if the defaultDownlinkBWP-Id is configured:
- perform BWP switching to a BWP indicated by the defaultDownlinkBWP-Id.
- else:
- perform BWP switching to the initialDownlinkBWP.
- if a PDCCH for BWP switching is received, and the MAC entity switches the active DL BWP:
- if the defaultDownlinkBWP-Id is configured, and the MAC entity switches to the DL BWP which is not indicated by the defaultDownlinkBWP-Id; or
- if the defaultDownlinkBWP-Id is not configured, and the MAC entity switches to the DL BWP which is not the initialDownlinkBWP:
- start or restart the bwp-InactivityTimer associated with the active DL BWP.
[00114] FIG. 5 illustrates an exemplary computer system 500 in which or with which embodiments of the present disclosure may be implemented.
[00115] As shown in FIG. 5, the computer system 500 may include an external storage device 510, a bus 520, a main memory 530, a read-only memory 540, a mass storage device 550, communication port(s) 560, and a processor 570. A person skilled in the art will appreciate that the computer system 500 may include more than one processor and communication ports. The processor 570 may include various modules associated with embodiments of the present disclosure. The communication port(s) 560 may be any of an RS-232 port for use with a modem-based dialup connection, a 10/100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication port(s) 560 may be chosen depending on a network, such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system 500 connects.
[00116] In an embodiment, the main memory 530 may be random access memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory 540 may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chips for storing static information e.g., start-up or Basic Input/Output System (BIOS) instructions for the processor 570. The mass storage device 550 may be any current or future mass storage solution, which can be used to store information and/or instructions. Exemplary mass storage device 550 includes, but is not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and/or Firewire interfaces), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g., an array of disks.
[00117] In an embodiment, the bus 520 communicatively couples the processor 570 with the other memory, storage, and communication blocks. The bus 520 may be, e.g., a Peripheral Component Interconnect (PCI)/PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), Universal Serial Bus (USB), or the like, for connecting expansion cards, drives, and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor 570 to the computer system 500.
[00118] In some embodiments, operator, and administrative interfaces, e.g., a display, keyboard, joystick, and a cursor control device, may also be coupled to the bus 520 to support direct operator interaction with the computer system 500. Other operator and administrative interfaces can be provided through network connections connected through the communication port(s) 560. Components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system 500 limit the scope of the present disclosure.
[00119] The method and system of the present disclosure may be implemented in a number of ways. For example, the methods and systems of the present disclosure may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above-described order for the steps of the method is for illustration only, and the steps of the method of the present disclosure are not limited to the order specifically described above unless specifically stated otherwise. Further, in some embodiments, the present disclosure may also be embodied as programs recorded in a recording medium, the programs including machine-readable instructions for implementing the methods according to the present disclosure. Thus, the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.
[00120] While considerable emphasis has been placed herein on the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter to be implemented merely as illustrative of the disclosure and not as limitation.
[00121] The present disclosure provides a technically advanced solution by providing a system and a method for handling or managing BWP switching. In an implementation, if there is a BWP switch trigger condition and previous pre-processed slots have downlink or uplink scheduling for a UE that may fall in the BWP switch delay period. The BWP switch may be delayed till the pre-processed scheduling for the UE is completed. Furthermore, UE scheduling for further slots is halted. As a result, resources are not wasted. Moreover, the system and the method provide better resource utilization, user experience, and quality of service (QOS).
TECHNICAL ADVANTAGES OF THE PRESENT DISCLOSURE
[00122] The present disclosure provides a system and a method for managing bandwidth part (BWP) switching for user equipment (UE) in a communication network.
[00123] The present disclosure provides a system and a method for delaying the BWP switch until one or more pre-scheduled data communication slots for the UE are scheduled. As a result, scheduling and resource wastage is minimized.
[00124] The present disclosure provides a system and a method for better resource utilization, user experience, and quality of service (QOS).
,CLAIMS:CLAIMS
We Claim:
1. A system (102) for managing bandwidth part (BWP) switching for a user equipment (UE) (108), the system (102) comprising:
a receiving unit (208) configured to receive a BWP switch request for the UE (108);
a processing unit (210) communicatively coupled to the receiving unit (208), wherein the processing unit (210) is configured to:
evaluate, upon receiving the BWP switch request, whether one or more pre-scheduled data communication slots for the UE (108) are impacted by a BWP switch delay period;
determine, in response to evaluating that the one or more pre-scheduled data communication slots are impacted by the BWP switch delay period, whether to postpone the BWP switch request based on one or more service requirements of the UE (108); and
upon determining to postpone the BWP switch request, delay the BWP switch request until the one or more pre-scheduled data communication slots are scheduled.

2. The system (102) as claimed in claim 1, wherein the receiving unit (208) is configured to receive the BWP switch request for the UE (108) when a BWP switch condition is met.

3. The system (102) as claimed in claim 1, wherein the one or more pre-scheduled data communication slots are impacted by the BWP switch delay period if the one or more pre-scheduled data communication slots fall within the BWP switch delay period or overlap with the BWP switch delay period.

4. The system (102) as claimed in claim 1, wherein the processing unit (210) is further configured to halt scheduling of the UE (108) until the BWP switch request is executed.
5. The system (102) as claimed in claim 1, wherein the one or more service requirements of the UE (108) comprise latency service requirement, throughput service requirement, and Quality of Service (QoS) based requirement.

6. The system (102) as claimed in claim 1, wherein the processing unit (210) is further configured to check whether the one or more pre-scheduled data communication slots have at least one of an uplink scheduling and a downlink scheduling.

7. A method (400) for managing bandwidth part (BWP) switching for a user equipment (UE) (108), the method (400) comprising steps of:
receiving (402), by a receiving unit (208), a BWP switch request for the UE (108);
upon receiving the BWP switch request, evaluating (404), by a processing unit (210), whether one or more pre-scheduled data communication slots for the UE (108) are impacted by the BWP switch delay period;
in response to evaluating that the one or more pre-scheduled data communication slots are impacted by the BWP switch delay period, determining (406), by the processing unit (210), whether to postpone the BWP switch request based on one or more service requirements of the UE (108); and
upon determining to postpone the BWP switch request, delaying (408), by the processing unit (210), the BWP switch request until the one or more pre-scheduled data communication slots are scheduled.

8. The method (400) as claimed in claim 7, wherein the BWP switch request for the UE (108) is received when a BWP switch condition is met.

9. The method (400) as claimed in claim 7, wherein the one or more pre-scheduled data communication slots are impacted by the BWP switch delay period if the one or more pre-scheduled data communication slots fall within the BWP switch delay period or overlap with the BWP switch delay period.

10. The method (400) as claimed in claim 7 further comprising halting scheduling of the UE (108) until the BWP switch request is executed.

11. The method (102) as claimed in claim 7, wherein the one or more service requirements of the UE (108) comprise latency service requirement, throughput service requirement, and Quality of Service (QoS) based requirement.

12. The method (102) as claimed in claim 7 further comprising checking whether the one or more pre-scheduled data communication slots have at least one of an uplink scheduling and a downlink scheduling.

13. A user equipment (UE) (108) communicatively coupled with a communication network (104), the coupling comprises of:
receiving, by the communication network (104), a connection request from UE (108);
sending, by the communication network (104), an acknowledgment of the connection request to the UE (108); and
transmitting a plurality of signals in response to the connection request, wherein the communication network (104) is configured for performing a method (400) for managing bandwidth part (BWP) switching for the UE (108) as claimed in claim 7.