Abstract: The present disclosure is related to a method of selecting at least one bandwidth part for a user equipment (UE) (204) connected to a network (203). The method includes receiving a radio resource control (RRC) connection setup request from the UE (204). The method includes checking an establishment cause associated with the received RRC connection setup request. The method comprises configuring a plurality of bandwidth parts based on the checked establishment cause. The method includes selecting at least one bandwidth part from the plurality of configured bandwidth parts. The method includes allocating, to the UE (204), the at least one selected bandwidth part. The method includes transmitting, to the UE (204), an RRC reconfiguration message comprising the allocated at least one bandwidth part and attaching the UE (204) to the allocated at least one bandwidth part. [FIGURE 2B]
FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
THE PATENTS RULES, 2003
COMPLETE
SPECIFICATION
(See section 10; rule 13)
TITLE OF THE INVENTION
SYSTEM AND METHOD FOR ACTIVE BANDWIDTH PART (BWP) SELECTION
APPLICANT
JIO PLATFORMS LIMITED
of Office-101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad -
380006, Gujarat, India; Nationality : India
The following specification particularly describes
the invention and the manner in which
it is to be performed
2
RESERVATION OF RIGHTS
[001] 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 5 Limited (JPL) or its affiliates (herein
after 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.
10
TECHNICAL FIELD
[002] The present disclosure relates to wireless communications, and
specifically to a system and a method for selecting an active Bandwidth Part (BWP)
upon receiving a connection setup request.
15
BACKGROUND
[003] 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
20 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.
[004] Conventional mechanisms for selecting an active Bandwidth Part
(BWP) from multiple available BWPs are inefficient. This is due to non25
consideration of BWP attributes such as Subcarrier Spacing (SCS), load,
aggregation level, core set size, interleaved/non-interleaved Control Channel
Element (CCE) indexes, and channel report during the selection and may result in
an incorrect matching of the active BWP with respect to a service request received
from a User Equipment (UE).
3
[005] There is, therefore, a need in the art for an improved mechanism to
select the active BWP that best matches the service request based on the BWP
attributes.
DEFINITION
[006] As used in the present 5 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.
[007] The term RRC as used herein, refers to radio resource control. The
RRC is a protocol is used in Universal Mobile Telecommunications Service
10 (UMTS), long-term evolution (LTE) and 5G on the air interface. It is a layer 3
(network layer) protocol used between a user equipment (UE) and a base station.
[008] The term SCS as used herein, refers to subcarrier spacing. The SCS
is the distance between two adjacent subcarriers in an Orthogonal Frequency
Division Multiplexing (OFDM) signal. It is a key parameter that affects the
15 bandwidth and performance of a 5G network.
[009] The term SSB as used herein, refers to synchronization signal block.
The SSB is used by the UE for 5G NR cell search and synchronization.
[0010] The term CORESET as used herein refers to the control resource set.
The CORESET is a set of physical resources (i.e., a specific area on the NR
20 downlink resource grid) and a set of parameters that are used to carry Physical
Downlink Control Channel (PDDCH))/Downlink Channel Indicator (DCI).
[0011] The term PUSCH as used herein, refers to Physical Uplink Shared
Channel. The E-UTRA PUSCH is the main uplink channel and is used to carry the
uplink shared channel (UL-SCH) transport channel.
25 [0012] The term PUCCH, as used herein, refers to the Physical Uplink
Control Channel. The PUCCH carries a set of information called Uplink Control
Information (UCI).
[0013] The term NAS as used herein, refers to non-access stratum. The
Non-Access Stratum (NAS) is a functional layer running between the User
30 Equipment (UE) and the Core Network (CN).
4
[0014] The term BWP as used herein, refers to bandwidth part. The BWP is
a part of the total channel bandwidth configured for a cell that is used for a UE at a
specific moment of operation.
5 OBJECTS OF THE PRESENT DISCLOSURE
[0015] It is an object of the present disclosure to select an active Bandwidth
Part (BWP) upon receiving a Radio Resource Control (RRC) setup request.
[0016] It is an object of the present disclosure to allocate the active BWP to
a User Equipment (UE) while considering BWP attributes.
10 [0017] It is an object of the present disclosure to select the active BWP
based on either of a BWP subcarrier spacing attribute, an aggregation level
attribute, a current load attribute that best matches a requested service.
[0018] It is an object of the present disclosure to provide better resource
utilization for a wireless network leading to enhanced user experience.
15 [0019] It is an object of the present disclosure to prioritize the BWP
attributes based on an establishment cause mentioned in the received RRC setup
request.
SUMMARY
20
[0020] In an exemplary embodiment, the present invention discloses a
method of selecting at least one bandwidth part for a user equipment (UE)
connected to a network. The method comprising receiving a radio resource control
(RRC) connection setup request from the UE. The method comprising checking an
25 establishment cause associated with the received RRC connection setup request.
The method comprising configuring a plurality of bandwidth parts based on the
checked establishment cause. The method comprising selecting at least one
bandwidth part from the plurality of configured bandwidth parts. The method
comprising allocating, to the UE, the at least one selected bandwidth part. The
30 method comprising transmitting, to the UE, a RRC reconfiguration message
5
comprising the allocated at least one bandwidth part. The method comprising
attaching the UE to the at least one allocated bandwidth part.
[0021] In some embodiments, the establishment cause includes of a
plurality of parameters associated with a service requirement of the UE.
[0022] In 5 some embodiments, the plurality of configured bandwidth parts
comprises of a plurality of bandwidth part characteristics.
[0023] In some embodiments, the method further comprising matching the
plurality of bandwidth part characteristics with the plurality of parameters.
[0024] In some embodiments, the method further comprising ranking the
10 plurality of bandwidth parts based on the matched plurality of bandwidth part
characteristics.
[0025] In some embodiments, the method further comprising selecting the
at least one bandwidth part from the plurality of ranked bandwidth parts.
[0026] In some embodiments, the at least one selected bandwidth part
15 comprises of at least one bandwidth part characteristic having a maximum match
with the plurality of parameters included in the establishment cause.
[0027] In some embodiments, the method the plurality of parameters
included in the establishment cause comprising one or more of an emergency
access, a high priority access, a mobile terminating (MT) access, a mobile
20 originating (MO) signalling, a mobile originating (MO) data, a mobile originated
(MO) voice call, a mobile originated (MO) video call, a mobile originated SMS, a
multimedia priority service (MPS) priority access, and a mission critical service
(MCS) priority access.
[0028] In some embodiments, the plurality of bandwidth part characteristics
25 comprising one or more of a subcarrier spacing (SCS), load, an aggregation level,
a coreset size, interleaved control channel element (CCE) indexes, non-interleaved
control channel element (CCE) indexes, and channel report.
[0029] In some embodiments, the method further comprising monitoring a
channel measurement report of the UE attached to the at least one allocated
30 bandwidth part.
6
[0030] In some embodiments, the method further comprising switching the
UE to at least one other ranked bandwidth part based on the monitored channel
measurement report.
[0031] In an exemplary embodiment, the present invention discloses a
system for selecting at least one 5 bandwidth part for a user equipment (UE)
connected to a network. The system comprising a receiving unit (212) configured
to receive a radio resource control (RRC) connection setup request from the UE.
The system comprising a processing unit (214) configured to check an
establishment cause associated with the received RRC connection setup request.
10 The system is configured to configure a plurality of bandwidth parts based on the
checked establishment cause. The system is configured to select at least one
bandwidth part from the plurality of configured bandwidth parts. The system is
configured to allocate, to the UE, the at least one selected bandwidth part. The
system is configured to transmit, to the UE, a RRC reconfiguration message
15 comprising the allocated at least one bandwidth part. The system is configured to
attach the UE to the at least one allocated bandwidth part.
[0032] In some embodiments, the establishment cause includes of a
plurality of parameters associated with a service requirement of the UE.
[0033] In some embodiments, the plurality of configured bandwidth parts
20 comprises of a plurality of bandwidth part characteristics.
[0034] In some embodiments, the system is configured to match the
plurality of bandwidth part characteristics with the plurality of parameters.
[0035] In some embodiments, the system is configured to rank the plurality
of bandwidth parts based on the matched plurality of bandwidth part characteristics.
25 [0036] In some embodiments, the system is configured to select the at least
one bandwidth part from the plurality of ranked bandwidth parts.
[0037] In some embodiments, the at least one selected bandwidth part
comprises of at least one bandwidth part characteristic having a maximum match
with the plurality of parameters included in the establishment cause.
30 [0038] In some embodiments, the plurality of parameters included in the
establishment cause comprising one or more of an emergency access, a high priority
7
access, a mobile terminating (MT) access, a mobile originating (MO) signalling, a
mobile originating (MO) data, a mobile originated (MO) voice call, a mobile
originated (MO) video call, a mobile originated SMS, a multimedia priority service
(MPS) priority access, and a mission critical service (MCS) priority access.
[0039] In some embodiments, the 5 plurality of bandwidth part characteristics
comprising one or more of a subcarrier spacing (SCS), load, an aggregation level,
a coreset size, interleaved control channel element (CCE) indexes, non-interleaved
control channel element (CCE) indexes, and channel report.
[0040] In some embodiments, the system is configured to monitor a channel
10 measurement report of the UE attached to the at least one allocated bandwidth part.
[0041] In some embodiments, the system is configured to switch the UE to
at least one other ranked bandwidth part based on the monitored channel
measurement report.
[0042] In an exemplary embodiment, the present invention discloses
15 network comprising one or more network elements for selecting at least one
bandwidth part for a user equipment (UE) communicatively coupled to the network.
The one or more network elements are configured to receive a radio resource
control (RRC) connection setup request from the UE. The system is configured to
check an establishment cause associated with the received RRC connection setup
20 request. The system is configured to configure a plurality of bandwidth parts based
on the checked establishment cause. The system is configured to select at least one
bandwidth part from the plurality of configured bandwidth parts. The system is
configured to allocate, to the UE, the at least one selected bandwidth part. The
system is configured to transmit, to the UE, a RRC reconfiguration message
25 comprising the allocated at least one bandwidth part. The system is configured to
attach the UE to the at least one allocated bandwidth part.
[0043] In an exemplary embodiment, the present invention discloses user
equipment (UE) communicatively coupled with a network. The network
comprising one or more network elements configured for receiving a radio resource
30 control (RRC) connection setup request from the UE, sending an acknowledgment
of the RRC connection setup request to the UE, and checking an establishment
8
cause associated with the received RRC connection setup request for configuring a
plurality of bandwidth parts. The one or more network elements are further
configured for allocating, to the UE, the at least one bandwidth part and
transmitting, to the UE, a RRC reconfiguration message for attaching the UE to the
5 at least one bandwidth part.
[0044] 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.
10 BRIEF DESCRIPTION OF THE DRAWINGS
[0045] In the figures, similar components and/or features may have the
same reference label. Further, various components of the same type may be
distinguished by following the reference label with a second label that distinguishes
among the similar components. If only the first reference label is used in the
15 specification, the description is applicable to any one of the similar components
having the same first reference label irrespective of the second reference label.
[0046] The diagrams are for illustration only, which thus is not a limitation
of the present disclosure, and wherein:
[0047] FIG. 1 illustrates an exemplary representation of elements of a Radio
20 Resource Control (RRC) setup request including an establishment cause, in
accordance with an embodiment of the present disclosure.
[0048] FIG. 2A illustrates a network architecture for selecting at least one
bandwidth part for a user equipment (UE), in accordance with embodiments of the
present disclosure.
25 [0049] FIG. 2B illustrates an exemplary flow representation for a selection
of an active Bandwidth Part (BWP) upon receiving a Radio Resource Control
(RRC) setup request, in accordance with an embodiment of the present disclosure.
[0050] FIG. 3 illustrates an exemplary flow representation of the UE
switching the BWP based on a generated periodic channel report, in accordance
30 with an embodiment of the present disclosure.
9
[0051] FIG. 4 illustrates an exemplary computer system in which or with
which embodiments of the present disclosure may be implemented.
[0052] FIG. 5 illustrates an exemplary flow chart for selecting at least one
bandwidth part for the UE, in accordance with an embodiment of the present
5 disclosure.
LIST OF REFERENCE NUMERALS
100 - Exemplary representation of Radio Resource Control (RRC) setup request
200A – Network architecture
10 202, 302 - gNodeB (gNB)/access and mobility function (AMF)
203- Network
204, 304 - User equipment (UE)
210 - System
212 - Receiving unit
15 214 - Processing unit
216 - Database
218 - Interfacing unit
200B - Flow diagram
300 - Flow diagram
20 400 - A computer system
410 - External storage device
420 - Bus
430 - Main memory
440 - Read only memory
10
450 - Mass storage device
460 - Communication port(s)
470 - Processor
500 - Flow diagram
5
DETAILED DESCRIPTION
[0053] In the following description, for the purposes of explanation, various
specific details are set forth in order to provide a thorough understanding of
embodiments of the present disclosure. It will be apparent, however, that
10 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 all of the problems discussed above or might address only some of the
problems discussed above. Some of the problems discussed above might not be
15 fully addressed by any of the features described herein.
[0054] 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
20 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 invention as set forth.
[0055] Specific details are given in the following description to provide a
thorough understanding of the embodiments. However, it will be understood by one
25 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
30 unnecessary detail in order to avoid obscuring the embodiments.
11
[0056] Also, it is noted that individual embodiments may be described as a
process which 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 5 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
10 function or the main function.
[0057] 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
15 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—in a manner
20 similar to the term “comprising” as an open transition word—without precluding
any additional or other elements.
[0058] 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
25 in at least one embodiment of the present invention. 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.
30 [0059] The terminology used herein is for the purpose of describing
particular embodiments only and is not intended to be limiting of the invention. As
12
used herein, the singular forms “a,” “an,” and “the” are intended to include the
plural forms as well, unless the context clearly 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 5 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 and all combinations
of one or more of the associated listed items.
[0060] Bandwidth Parts (BWPs) is a Fifth Generation (5G) New Radio
10 (NR) feature introduced in 3rd Generation Partnership Project (3GPP) Release 15.
The BWP dynamically adapts carrier bandwidth and numerology in which a User
Equipment (UE) operates. The BWP allows supporting multiple services per
carrier, for example, an Enhanced Mobile Broadband (eMBB) service, and a
Massive Machine-Type Communications (mMTC) service.
15 [0061] The disclosed system and method facilitate to choose an appropriate
active BWP based on a service request mentioned in a received Radio Resource
Control (RRC) connection establishment request. The appropriate active BWP may
be selected based on the real-time status of one or more attributes of each of the
BWPs. The attributes may be, for example, Subcarrier Spacing (SCS), load,
20 aggregation level, coreset size, interleaved/non-interleaved Control Channel
Element (CCE) indexes, channel report. The appropriate active BWP may be
selected based on one of the establishment causes that is prioritized during the RRC
setup establishment. The establishment cause may be, for example, Mobile
Originated (MO) signalling/data, Mobile Terminated (MT) access, emergency,
25 high-priority access, and the like.
[0062] As may be appreciated, the BWP is a carrier bandwidth part that 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.
[0063] The BWP allocation for Downlink (DL) involves:
30 1. The UE to be configured with up to four carrier bandwidth parts.
13
2. Setting the bandwidth of each of the Bandwidth part (BWP) to be
equal or greater than Synchronization Signal Block (SSB) BW, but
it may or may not contain SSB.
3. Setting only one carrier BWP to be active at a given time.
4. The UE to not expect to receive 5 a physical downlink shared channel
(PDSCH), Physical Downlink Control Channel (PDCCH), Channel-
State Information - Reference Signals (CSI-RS), or Tracking
Reference Signal (TRS) outside an active BWP.
5. Each DL BWP is to include at least one Control Resource Set
10 (CORESET) with UE Specific Search Space (USS).
6. In a primary carrier, at least one of the configured DL BWPs may
include one CORESET with common search space (CSS).
[0064] The BWP allocation for Uplink (UL) involves:
1. The UE is to be configured with up to four carrier bandwidth parts.
15 2. Only one carrier bandwidth part may be active at a given time.
3. If a UE is configured with a supplementary uplink
4. The UE may, in addition, be configured with up to four carrier
bandwidth parts in a supplementary uplink.
5. Only one carrier bandwidth part may be active at a given time.
20 6. The UE may not transmit the PUSCH or the PUCCH outside an
active bandwidth part.
[0065] In an example, the establishment cause in the RRC setup request may
be, for example, an emergency, a high priority access, a mobile terminating access,
a mobile originating signalling, a mobile originating data, and the like. In some
25 examples, the establishment cause may be determined by a Non-access stratum
(NAS) procedure for which the RRC setup is being established.
[0066] An initial step in a 5G Standalone (SA) call processing is to
synchronize the UE with a gNodeB (gNB). After synchronization, the UE may
initiate the RRC setup establishment procedure by sending an RRC SetupRequest
30 message to the gNB. Further, the gNB may respond with an RRC Setup message,
14
which includes essential configuration information for the UE to access network
resources.
[0067] As per 3GPP Technical Specification (TS) 38.331, the establishment
cause may be represented as:
EstablishmentCause: 5 = ENUMERATED {emergency,
highPriorityAccess, MT-Access, MO-Signalling, MO-Data, MOVoiceCall,
MO-VideoCall, MO-SMS, Multimedia Priority Service
((MPS)-PriorityAccess, Mission Critical Service (MCS)-
PriorityAccess, spare6, spare5, spare4, spare3, spare2, spare1}
10 [0068] FIG. 1 illustrates an exemplary representation 100 of elements of the
RRC setup request including the establishment cause, in accordance with an
embodiment of the present disclosure. As illustrated, the RRC setup request (102)
includes parameters such as UE-Identity (104), and the establishment cause (106).
The UE-Identity (104) may be, for example, a Serving Temporary Mobile
15 Subscriber Identity (S-TMSI) or it may be a random allocated identity.
[0069] In an embodiment, selection of the active BWP is initiated when the
gNB receives the RRC setup request at step (102). Upon receiving the RRC setup
request, the establishment cause is evaluated. Based on the evaluation, for the
connection request cases with the establishment cause mentioned as, for example,
20 the MO voice, the MT voice, and the MCS/MPS high priority access, an active
BWP may be configured that has a low latency (i.e., high sub carrier spacing), low
load, and higher aggregation level, i.e., better channel measurement reports. In
addition, for the connection request cases with the establishment cause mentioned
as the MO data or the MT access, any active BWP may be assigned whose load or
25 channel characteristics have the capacity to service the requested connection
request.
[0070] In addition, a BWP ranking may be generated for each of the
available BWP based on the channel characteristics. The BWP ranking may be
generated for each of the requested services of the RRC setup request. Based on the
30 generated BWP ranking, an active BWP may be selected that best suits the
requested service in the establishment cause. The BWP may be ranked in an
15
ascending order based on attributes such as SCS, load, aggregation level, core set
size, interleaved/non-interleaved CCE indexes, and channel report. In an aspect, the
BWP may be ranked in descending order based on the attributes such as SCS, load,
aggregation level, core set size, interleaved/non-interleaved CCE indexes, channel
report, etc. In an aspect, the BWP may be 5 ranked using a combination of one or
more attributes such as SCS, load, aggregation level, core set size, interleaved/noninterleaved
CCE indexes, channel report, etc, in ascending or descending order. In
an aspect, the BWP may be ranked based on a weightage of the one or more
attributes such as SCS, load, aggregation level, core set size, interleaved/non10
interleaved CCE indexes, and channel report etc.
[0071] Further, a channel measurement report may be generated when the
UE is attached to the active BWP. The channel measurement report may be
monitored regularly to determine if the selected active BWP satisfies the requested
service. Else, selection of the active BWP is switched to the next best BWP.
15 [0072] FIG. 2A illustrates a network architecture for selecting at least one
bandwidth part for a user equipment (UE), in accordance with embodiments of the
present disclosure.
[0073] Referring to FIG. 2A, the network architecture (200A) may include
a user equipment UE (204) and a gNodeB (202). A person of ordinary skill in the
20 art will understand that. A person of ordinary skill in the art will appreciate that the
terms “computing device(s)” and “user equipment” may be used interchangeably
throughout the disclosure. Although a single UE (204) is depicted in FIG. 1,
however, any number of the UEs may be included without departing from the scope
of the ongoing description.
25 [0074] In an embodiment, the UE (204) may include smart devices
operating in a smart environment, for example, an Internet of Things (IoT) system.
In such an embodiment, the UE (204) may include, but is not limited to, smart
phones, smart watches, smart sensors (e.g., mechanical, thermal, electrical,
magnetic, etc.), networked appliances, networked peripheral devices, networked
30 lighting system, communication devices, networked vehicle accessories, networked
vehicular devices, smart accessories, tablets, smart television (TV), computers,
16
smart security system, smart home system, other devices for monitoring or
interacting with or for the users and/or entities, or any combination thereof. A
person of ordinary skill in the art will appreciate that the UE (204) may include, but
is not limited to, intelligent, multi-sensing, network-connected devices, that can
integrate seamlessly with each other and/or 5 with a central server or a cloudcomputing
system or any other device that is network-connected.
[0075] In an embodiment, the UE (204) may include, but is not limited to,
a handheld wireless communication device (e.g., a mobile phone, a smart phone, a
phablet device, and so on), a wearable computer device(e.g., a head-mounted
10 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 (204) may
15 include, but is not limited to, any electrical, electronic, electro-mechanical, or an
equipment, or a combination of one or more of the above devices such as virtual
reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose
computer, desktop, personal digital assistant, tablet computer, mainframe
computer, or any other computing device, wherein the UE (204) may include one
20 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 (102) or the entity such as touch pad,
touch enabled screen, electronic pen, and the like. A person of ordinary skill in the
art will appreciate that the UE (204) may not be restricted to the mentioned devices
25 and various other devices may be used.
[0076] The UE (204) may communicate with a system (210), through a
network (203). In an embodiment, the network (203) may include at least one of a
Second Generation (2G), Third Generation (3G), Fourth Generation (4G) network,
a Fifth Generation (5G) network, Sixth Generation (6G) and beyond or the like.
30 The network (203) may enable the user equipment (204) to communicate with other
devices in the network architecture (200A) and/or with the system (210). The
17
network (203) may include a wireless card or some other transceiver connection to
facilitate this communication. In another embodiment, the network (203) 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 5 Network (VPN), the Internet, the
Public Switched Telephone Network (PSTN), or the like.
[0077] The system (210) may include a receiving unit (212), a processing
unit (214), a database (216), and an interfacing unit (218). The receiving unit (212)
is configured to receive a radio resource control (RRC) connection setup request
10 from the UE. The processing unit (214) is coupled to the receiving unit (212). The
processing unit (214) is configured to check an establishment cause associated with
the received RRC connection setup request. The RRC connection setup request is
a message used in cellular networks, particularly in the context of LTE (Long-Term
Evolution) and 5G networks. When a device, such as a smartphone or IoT device,
15 wants to establish a connection with the network, it sends an RRC connection setup
request to the base station (eNodeB in LTE or gNodeB in 5G). The RRC
connection setup request includes essential information such as the device's
identity, capabilities, and the type of service it is requesting. Upon receiving this
request, a base station processes it and initiates the necessary procedures to establish
20 a connection with the device, allowing it to access the network services.
[0078] Further, the processing unit (214) configures a plurality of
bandwidth parts based on the checked establishment cause. The processing unit
(214) is configured to select at least one bandwidth part from the plurality of
configured bandwidth parts. The processing unit (214) allocates at least one
25 selected bandwidth part to the UE (204) and transmits the RRC reconfiguration
message comprising the allocated at least one bandwidth part to the UE (204). The
RRC reconfiguration message includes instructions for the device to adjust its radio
configuration parameters, such as modulation and coding schemes, bandwidth
allocation, power control, handover parameters, and other network-related settings
30 along with the allocated at least one bandwidth part. The RRC reconfiguration
message allows the network to adapt dynamically to changing conditions, optimize
18
resource allocation, and enhance overall network performance while maintaining
the continuity of service for connected devices.
[0079] Further, the processing unit (214) attaches the UE (204) to the at
least one allocated bandwidth part. The processing unit (214) may be implemented
as one or more microprocessors, 5 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
processing unit (214) may be configured to fetch and execute computer-readable
instructions stored in a memory of the system (210). The memory may be
10 configured to store one or more computer-readable instructions or routines in a nontransitory
computer readable storage medium, which may be fetched and executed
to create or share data packets over a network service. The memory may comprise
any non-transitory storage device including, for example, volatile memory such as
random-access memory (RAM), or non-volatile memory such as erasable
15 programmable read only memory (EPROM), flash memory, and the like. The
database (216) may store information including the RRC connection setup request,
the RRC configuration message, bandwidth parts, and the like.
[0080] In an embodiment, the interfacing unit (218) may comprise a variety
of interfaces, for example, interfaces for data input and output devices (I/O), storage
20 devices, and the like. The interfacing unit (218) may facilitate communication
through the system (210). The interfacing unit (218) may also provide a
communication pathway for one or more components of the system (210).
[0081] FIG. 2B illustrates an exemplary flow representation 200B for the
selection of the active BWP upon receiving the RRC setup request, in accordance
25 with an embodiment of the present disclosure. As is illustrated, at 206, step 1, the
UE 204 sends the RRC setup request with the establishment cause mentioned as
MO Voice (i.e., a high-priority access) to the gNB/AMF 202. Upon receiving the
request, the gNB, at 208, step 2, evaluates a best BWP out of available four BWPs
based on the attributes such as the SCS, the load, and channel estimates. The BWP
30 that best matches a service request received from the RRC setup request is selected
as the active BWP for the UE. By way of an example, a high-priority access request
19
may require a BWP that supports low latency (i.e., high SCS), low load, and has
the best channel characteristics (or maximum match with the plurality of parameters
included in the establishment clause). Further, a RRC setup message is sent to the
UE having information about an active BWP with index 2. The UE sets the BWP
as the active BWP with the 5 index 2. The BWP whose subcarrier spacing, load, and
channel configuration best matches the service and latency requirements for the
type of service requested may be set as the active BWP. The matching of parameters
helps in finding the correct BWP. Further, the service level agreement (SLA)
requirement for the requested service should be fulfilled by the BWP (to be
10 selected). Thus, this mechanism for selection of the active BWP enables better
resource utilization and provides enhanced user experience.
[0082] In an embodiment are disclosed various scenarios for mapping of the
establishment cause to the BWP attributes:
Scenario 1: For establishment cause mentioned as: MO/MT
15 VoiceCall/VideoCall:
1. Rank the BWP as per highest Sub Carrier Spacing (SCS) to lowest
for lowest latency requirement.
2. Perform next level ranking on Aggregation Level (AL) (higher AL
is ranked higher)
20 3. Perform next level ranking on load on the BWP (lowest load ranked
higher)
Scenario 2: For establishment cause mentioned as: Emergency/High Priority
Access
1. Rank the BWP based on the AL (higher AL is ranked higher)
25 2. Perform next level ranking on load on the BWP (lowest load ranked
higher)
Scenario 3: For establishment cause mentioned as:
MobileOriginatingSignalling/MO-SMS
1. Rank the BWP based on the AL (higher AL is ranked higher)
30 2. Perform next level ranking on the load on the BWP (lowest load
ranked higher)
20
Scenario 4: For establishment cause mentioned as: MCS-PriorityAccess
1. Rank the BWP as per highest SCS to lowest for lowest latency
requirement.
2. Perform next level ranking on the AL (higher AL ranked higher)
3. Perform next 5 level ranking on the load on the BWP (lowest load
ranked higher)
Scenario 5: For establishment cause mentioned as: MPS-PriorityAccess
1. Rank the BWP as per highest SCS to lowest for lowest latency
requirement.
10 2. Perform next level ranking on the load on the BWP (lowest load
ranked higher)
Scenario 6: For establishment cause mentioned as: MO/MT Data
1. Rank the BWP as per Load on the BWP (lowest load ranked higher)
[0083] As may be appreciated, the BWP attributes such as the Core set size,
15 the CCE indexes (interleaved/non-interleaved), and the other BWP attributes may
be taken into account to determine the best suit for the establishment cause service.
In addition, after selecting a particular BWP as the active BWP, periodic channel
measurement may be performed and monitored. Also, switching to the next best
BWP ranking may be done if current channel reports are not sufficient enough to
20 sustain the Quality Of service (QoS) requirements of the establishment cause
service.
[0084] In an exemplary embodiment, the present invention discloses a
method of selecting at least one bandwidth part for a user equipment (UE). The
method comprises receiving a radio resource control (RRC) connection setup
25 request from the UE. The method comprises checking an establishment cause
associated with the received RRC connection setup request. The method comprises
configuring a plurality of bandwidth parts based on the checked establishment
cause. The method comprises selecting at least one bandwidth part from the
plurality of configured bandwidth parts. The method comprises allocating, to the
30 UE, at least one selected bandwidth part. The method comprises transmitting, to the
UE, an RRC reconfiguration message comprising the allocated at least one
21
bandwidth part. The method comprises attaching the UE to at least one allocated
bandwidth part.
[0085] In some embodiments, the establishment cause includes of a
plurality of parameters associated with a service requirement of the UE.
[0086] 5 In some embodiments, the plurality of configured bandwidth parts
comprises a plurality of bandwidth part characteristics.
[0087] In some embodiments, the method further comprises matching the
plurality of bandwidth part characteristics with the plurality of parameters.
[0088] In some embodiments, the method further comprises ranking the
10 plurality of bandwidth parts based on the matched plurality of bandwidth part
characteristics.
[0089] In some embodiments, the method further comprises selecting at
least one bandwidth part from the plurality of ranked bandwidth parts.
[0090] In some embodiments, at least one selected bandwidth part
15 comprises at least one bandwidth part characteristic having a maximum match with
the plurality of parameters included in the establishment clause.
[0091] In some embodiments, the method the plurality of parameters
included in the establishment cause comprising one or more of emergency access,
a high priority access, a mobile terminating (MT) access, a mobile originating (MO)
20 signalling, a mobile originating (MO) data, a mobile originated (MO) voice call, a
mobile originated (MO) video call, a mobile originated SMS, a multimedia priority
service (MPS) priority access, and a mission-critical service (MCS) priority access.
[0092] In some embodiments, the plurality of bandwidth part characteristics
comprising one or more of a subcarrier spacing (SCS), load, an aggregation level,
25 a coreset size, interleaved control channel element (CCE) indexes, non-interleaved
control channel element (CCE) indexes, and channel report.
[0093] In some embodiments, the method further comprises monitoring a
channel measurement report of the UE attached to at least one allocated bandwidth
part.
22
[0094] In some embodiments, the method further comprises switching the
UE to at least one other ranked bandwidth part based on the monitored channel
measurement report.
[0095] In an exemplary embodiment, the present invention discloses a
system for selecting at least one bandwidth part 5 for a user equipment (UE). The
system is configured to receive a radio resource control (RRC) connection setup
request from the UE. The system is configured to check an establishment cause
associated with the received RRC connection setup request. The system is
configured to configure a plurality of bandwidth parts based on the checked
10 establishment cause. The system is configured to select at least one bandwidth part
from the plurality of configured bandwidth parts. The system is configured to
allocate, to the UE, the at least one selected bandwidth part. The system is
configured to transmit, to the UE, a RRC reconfiguration message comprising the
allocated at least one bandwidth part. The system is configured to attach the UE to
15 the at least one allocated bandwidth part.
[0096] FIG. 3 illustrates an exemplary flow representation 300 of the UE
304 switching the BWP based on a generated periodic channel report, in accordance
with an embodiment of the present disclosure. As is illustrated, at 306, step 1, the
UE is informed about a best-suited active BWP by the Gnb/AMF 302. The UE
20 attaches itself to the best-suited active BWP and periodically generates a channel
report. At 308 step 2, the periodically generated channel report is shared with the
gNB comprising information related to quality and performance of the active BWP.
When the report is not satisfactory and implies that the channel quality of the
selected BWP is not enough to sustain the requested service, the gNB, at 310 step
25 3, informs the UE of the next best available active BWP to be used. The next best
active BWP is selected based on the rank assigned to each of the available BWP.
[0097] The disclosure facilitates the provision of a system and a method for
allocating the active BWP to the UE based on the establishment cause mentioned
in the RRC setup request. The BWP whose subcarrier spacing, load, and channel
30 configuration best matches the service and latency requirements for the type of
service requested may be set as the active BWP. This mechanism for selection of
23
the active BWP enables better resource utilization and provides enhanced user
experience.
[0098] In an aspect, the present disclosure prioritizes the BWP attributes
based on an establishment cause mentioned in the received RRC setup request. In
an aspect the present invention can be 5 implemented in a wireless communication
network architecture for better resource utilization.
[0099] FIG. 4 illustrates an exemplary computer system 400 in which or
with which embodiments of the present disclosure may be implemented. As shown
in FIG. 4, the computer system 400 may include an external storage device 410, a
10 bus 420, a main memory 430, a read-only memory 440, a mass storage device 450,
communication port(s) 460, and a processor 470. A person skilled in the art will
appreciate that the computer system 400 may include more than one processor and
communication ports. The processor 470 may include various modules associated
with embodiments of the present disclosure. The communication port(s) 460 may
15 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) 460 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 400 connects.
20 [00100] The main memory 430 may be random access memory (RAM), or
any other dynamic storage device commonly known in the art. The read-only
memory 440 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
25 470. The mass storage device 450 may be any current or future mass storage
solution, which can be used to store information and/or instructions. Exemplary
mass storage device 450 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
30 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.
24
[00101] The bus 420 communicatively couples the processor 470 with the
other memory, storage, and communication blocks. The bus 420 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, 5 drives, and other subsystems as well as other buses,
such a front side bus (FSB), which connects the processor 470 to the computer
system 400.
[00102] Optionally, operator and administrative interfaces, e.g., a display,
keyboard, joystick, and a cursor control device, may also be coupled to the bus 420
10 to support direct operator interaction with the computer system 400. Other operator
and administrative interfaces can be provided through network connections
connected through the communication port(s) 460. Components described above
are meant only to exemplify various possibilities. In no way should the
aforementioned exemplary computer system 400 limit the scope of the present
15 disclosure.
[00103] FIG. 5 illustrates an exemplary flow diagram 500 for a method of
selecting at least one bandwidth part for a user equipment (UE) (204) connected to
a network (203).
[00104] At step 502, the method includes receiving a radio resource control
20 (RRC) connection setup request from the UE (204).
[00105] At step 504, the method includes checking an establishment cause
associated with the received RRC connection setup request.
[00106] At step 506, the method includes configuring a plurality of
bandwidth parts based on the checked establishment cause.
25 [00107] At step 508, the method includes selecting at least one bandwidth
part from the plurality of configured bandwidth parts.
[00108] At step 510, the method includes allocating, to the UE (204), the at
least one selected bandwidth part.
[00109] At step 512, the method includes transmitting, to the UE (204), a
30 RRC reconfiguration message comprising the allocated at least one bandwidth part.
25
[00110] At step 514, the method includes attaching the UE (204) to the at
least one allocated bandwidth part.
[00111] In some embodiments, the establishment cause includes of a
plurality of parameters associated with a service requirement of the UE. In some
embodiments, the plurality 5 of configured bandwidth parts comprises of a plurality
of bandwidth part characteristics. In some embodiments, the method further
comprises matching the plurality of bandwidth part characteristics with the plurality
of parameters. In some embodiments, the method further comprises ranking the
plurality of bandwidth parts based on the matched plurality of bandwidth part
10 characteristics. In some embodiments, the method further comprises selecting at
least one bandwidth part from the plurality of ranked bandwidth parts. In some
embodiments, at least one selected bandwidth part comprises at least one bandwidth
part characteristic having a maximum match with the plurality of parameters
included in the establishment clause. In some embodiments, the method the
15 plurality of parameters included in the establishment cause comprising one or more
of an emergency access, a high priority access, a mobile terminating (MT) access,
a mobile originating (MO) signalling, a mobile originating (MO) data, a mobile
originated (MO) voice call, a mobile originated (MO) video call, a mobile
originated SMS, a multimedia priority service (MPS) priority access, and a mission
20 critical service (MCS) priority access. In some embodiments, the plurality of
bandwidth part characteristics comprising one or more of a subcarrier spacing
(SCS), load, an aggregation level, a coreset size, interleaved control channel
element (CCE) indexes, non-interleaved control channel element (CCE) indexes,
and channel report. In some embodiments, the method further comprises
25 monitoring a channel measurement report of the UE attached to at least one
allocated bandwidth part. In some embodiments, the method further comprises
switching the UE to at least one other ranked bandwidth part based on the monitored
channel measurement report.
[00112] In an exemplary embodiment, the present invention discloses a
30 system for selecting at least one bandwidth part for a user equipment (UE)
connected to a network. The system comprises a receiving unit (212) configured to
26
receive a radio resource control (RRC) connection setup request from the UE. The
system comprises a processing unit (214) configured to check an establishment
cause associated with the received RRC connection setup request. The system is
configured to configure a plurality of bandwidth parts based on the checked
establishment cause. The system is configured to 5 select at least one bandwidth part
from the plurality of configured bandwidth parts. The system is configured to
allocate, to the UE, the at least one selected bandwidth part. The system is
configured to transmit, to the UE, a RRC reconfiguration message comprising the
allocated at least one bandwidth part. The system is configured to attach the UE to
10 the at least one allocated bandwidth part.
[00113] In an exemplary embodiment, the present invention discloses
network comprising one or more network elements for selecting at least one
bandwidth part for a user equipment (UE) communicatively coupled to the network.
The one or more network elements are configured to receive a radio resource
15 control (RRC) connection setup request from the UE. The system is configured to
check an establishment cause associated with the received RRC connection setup
request. The system is configured to configure a plurality of bandwidth parts based
on the checked establishment cause. The system is configured to select at least one
bandwidth part from the plurality of configured bandwidth parts. The system is
20 configured to allocate, to the UE, the at least one selected bandwidth part. The
system is configured to transmit, to the UE, a RRC reconfiguration message
comprising the allocated at least one bandwidth part. The system is configured to
attach the UE to the at least one allocated bandwidth part.
[00114] In an exemplary embodiment, the present invention discloses user
25 equipment (UE) communicatively coupled with a network. The network
comprising one or more network elements configured for receiving a radio resource
control (RRC) connection setup request from the UE, sending an acknowledgment
of the RRC connection setup request to the UE, and checking an establishment
cause associated with the received RRC connection setup request for configuring a
30 plurality of bandwidth parts. The one or more network elements are further
configured for allocating, to the UE, the at least one bandwidth part and
27
transmitting, to the UE, a RRC reconfiguration message for attaching the UE to the
at least one bandwidth part.
[00115] While the foregoing describes various embodiments of the
invention, other and further embodiments of the invention may be devised without
departing from the basic scope 5 thereof. The scope of the invention is determined by
the claims that follow. The invention is not limited to the described embodiments,
versions or examples, which are included to enable a person having ordinary skill
in the art to make and use the invention when combined with information and
knowledge available to the person having ordinary skill in the art.
10
ADVANTAGES OF THE PRESENT DISCLOSURE
[00116] The present disclosure facilitates selection of an active Bandwidth
Part (BWP) upon receiving a Radio Resource Control (RRC) setup request.
[00117] The present disclosure allocates the active BWP to a User
15 Equipment (UE) while considering BWP attributes.
[00118] The present disclosure selects the active BWP based on a BWP
subcarrier spacing attribute, an aggregation level attribute, a current load attribute
that best matches a requested service.
[00119] The present disclosure provides better resource utilization of a
20 wireless network and enhanced user experience.
[00120] The present disclosure prioritizes the BWP attributes based on an
establishment cause mentioned in the received RRC setup request.
1. A method (500) of selecting a bandwidth part for a user equipment (UE) (204) connected to a network (203), the method comprising:
receiving (502) a radio resource control (RRC) connection setup request from the UE (204);
checking (504) an establishment cause associated with the received RRC connection setup request;
configuring (506) a plurality of bandwidth parts based on the checked establishment cause;
selecting (508) at least one bandwidth part from the plurality of configured bandwidth parts;
allocating (510), to the UE (204), the at least one selected bandwidth part;
transmitting (512), to the UE (204), a RRC reconfiguration message comprising the allocated at least one bandwidth part; and
attaching (514) the UE (204) to the allocated at least one bandwidth part.
2. The method (500) as claimed in claim 1, wherein the
establishment cause includes a plurality of parameters associated with a
service requirement of the UE (204).
3. The method (500) as claimed in claim 2, wherein the plurality of
configured bandwidth parts comprises a plurality of bandwidth part
characteristics.
4. The method (500) as claimed in claim 3, further comprising matching the plurality of bandwidth part characteristics with the plurality of parameters.
5. The method (500) as claimed in claim 4, further comprising ranking the plurality of bandwidth parts based on the matched plurality of bandwidth part characteristics.
6. The method (500) as claimed in claim 5, further comprising selecting the at least one bandwidth part from the plurality of ranked bandwidth parts.
7. The method (500) as claimed in claim 6, wherein the at least one selected bandwidth part comprises of at least one bandwidth part characteristic having a maximum match with the plurality of parameters included in the establishment cause.
8. The method (500) as claimed in claim 2, wherein the plurality of parameters included in the establishment cause comprising one or more of an emergency access, a high priority access, a mobile terminating (MT) access, a mobile originating (MO) signalling, a mobile originating (MO) data, a mobile originated (MO) voice call, a mobile originated (MO) video call, a mobile originated SMS, a multimedia priority service (MPS) priority access, and a mission critical service (MCS) priority access.
9. The method (500) as claimed in claim 3, wherein the plurality of bandwidth part characteristics comprising one or more of a subcarrier spacing (SCS), load, an aggregation level, a coreset size, interleaved control channel element (CCE) indexes, non-interleaved control channel element (CCE) indexes, and channel report.
10. The method (500) as claimed in claim 1, further comprising monitoring a channel measurement report of the UE (204) attached to the allocated at least one bandwidth part.
11. The method (500) as claimed in claim 10, further comprising switching the UE (204) to at least one other ranked bandwidth part based on the monitored channel measurement report.
12. A system (210) for selecting at least one bandwidth part for a user equipment (UE) (204) connected to a network (203), the system (210) comprising :
a receiving unit (212) configured to receive a radio resource control (RRC) connection setup request from the UE (204);
a processing unit (214) coupled to the receiving unit (212) and is configured to:
check an establishment cause associated with the received RRC connection setup request;
configure a plurality of bandwidth parts based on the checked establishment cause;
select at least one bandwidth part from the plurality of configured bandwidth parts;
allocate, to the UE (204), the at least one selected bandwidth part;
transmit, to the UE (204), a RRC reconfiguration message comprising the allocated at least one bandwidth part; and
attach the UE (204) to the allocated at least one bandwidth part.
13. The system (210) as claimed in claim 12, wherein the establishment cause includes a plurality of parameters associated with a service requirement of the UE (204).
14. The system (210) as claimed in claim 13, wherein the plurality of configured bandwidth parts comprises a plurality of bandwidth part characteristics.
15. The system (210) as claimed in claim 14, further configured to match the plurality of bandwidth part characteristics with the plurality of parameters.
16. The system (210) as claimed in claim 15, further configured to rank the plurality of bandwidth parts based on matched plurality of bandwidth part characteristics.
17. The system (210) as claimed in claim 16, further configured to select the at least one bandwidth part from the plurality of ranked bandwidth parts.
18. The system (210) as claimed in claim 17, wherein the at least one selected bandwidth part comprises of at least one bandwidth part characteristic having a maximum match with the plurality of parameters included in the establishment cause.
19. The system (210) as claimed in claim 13, wherein the plurality of parameters included in the establishment cause comprising one or more of an emergency access, a high priority access, a mobile terminating (MT) access, a mobile originating (MO) signalling, a mobile originating (MO) data, a mobile originated (MO) voice call, a mobile originated (MO) video call, a mobile originated SMS, a multimedia priority service (MPS) priority access, and a mission critical service (MCS) priority access.
20. The system (210) as claimed in claim 14, wherein the plurality of bandwidth part characteristics comprising one or more of a subcarrier
spacing (SCS), load, an aggregation level, a coreset size, interleaved control channel element (CCE) indexes, non-interleaved control channel element (CCE) indexes, and channel report.
21. The system (210) as claimed in claim 12, further configured to monitor a channel measurement report of the UE (204) attached to the allocated at least one bandwidth part.
22. The system (210) as claimed in claim 21, further configured to switch the UE (204) to at least one other ranked bandwidth part based on the monitored channel measurement report.
23. A network (203) comprising one or more network elements for selecting at least one bandwidth part for a user equipment (UE) (204) communicatively coupled to the network (203), the one or more network elements are configured to:
receive a radio resource control (RRC) connection setup request from the UE (204);
check an establishment cause associated with the received RRC connection setup request;
configure a plurality of bandwidth parts based on the checked establishment cause;
select at least one bandwidth part from the plurality of configured bandwidth parts;
allocate, to the UE (204), the at least one selected bandwidth part;
transmit, to the UE (204), a RRC reconfiguration message comprising the allocated at least one bandwidth part; and
attach the UE (204) to the allocated at least one bandwidth part.
24. A user equipment (UE) (204) communicatively coupled with a network
(203), said communicatively coupling comprises steps of:
receiving a connection request;
sending an acknowledgment of the connection request to one or more network elements;
transmitting a plurality of signals in response to the connection request, wherein the one or more network elements are configured for:
receiving a radio resource control (RRC) connection setup request from the UE (204);
sending an acknowledgment of the RRC connection setup request to the UE (204);
checking an establishment cause associated with the received RRC connection setup request for configuring a plurality of bandwidth parts;
allocating, to the UE (204), at least one bandwidth part based on the checked establishment cause; and
transmitting, to the UE (204), a RRC reconfiguration message for attaching the UE (204) to the at least one bandwidth part.
| # | Name | Date |
|---|---|---|
| 1 | 202321043757-STATEMENT OF UNDERTAKING (FORM 3) [29-06-2023(online)].pdf | 2023-06-29 |
| 2 | 202321043757-PROVISIONAL SPECIFICATION [29-06-2023(online)].pdf | 2023-06-29 |
| 3 | 202321043757-FORM 1 [29-06-2023(online)].pdf | 2023-06-29 |
| 4 | 202321043757-DRAWINGS [29-06-2023(online)].pdf | 2023-06-29 |
| 5 | 202321043757-DECLARATION OF INVENTORSHIP (FORM 5) [29-06-2023(online)].pdf | 2023-06-29 |
| 6 | 202321043757-FORM-26 [12-09-2023(online)].pdf | 2023-09-12 |
| 7 | 202321043757-RELEVANT DOCUMENTS [27-02-2024(online)].pdf | 2024-02-27 |
| 8 | 202321043757-POA [27-02-2024(online)].pdf | 2024-02-27 |
| 9 | 202321043757-FORM 13 [27-02-2024(online)].pdf | 2024-02-27 |
| 10 | 202321043757-AMENDED DOCUMENTS [27-02-2024(online)].pdf | 2024-02-27 |
| 11 | 202321043757-Request Letter-Correspondence [04-03-2024(online)].pdf | 2024-03-04 |
| 12 | 202321043757-Power of Attorney [04-03-2024(online)].pdf | 2024-03-04 |
| 13 | 202321043757-Covering Letter [04-03-2024(online)].pdf | 2024-03-04 |
| 14 | 202321043757-CORRESPONDENCE(IPO)-(WIPO DAS)-13-03-2024.pdf | 2024-03-13 |
| 15 | 202321043757-ORIGINAL UR 6(1A) FORM 26-090524.pdf | 2024-05-15 |
| 16 | 202321043757-ENDORSEMENT BY INVENTORS [27-05-2024(online)].pdf | 2024-05-27 |
| 17 | 202321043757-DRAWING [27-05-2024(online)].pdf | 2024-05-27 |
| 18 | 202321043757-CORRESPONDENCE-OTHERS [27-05-2024(online)].pdf | 2024-05-27 |
| 19 | 202321043757-COMPLETE SPECIFICATION [27-05-2024(online)].pdf | 2024-05-27 |
| 20 | Abstract1.jpg | 2024-06-25 |
| 21 | 202321043757-FORM-9 [30-09-2024(online)].pdf | 2024-09-30 |
| 22 | 202321043757-FORM 18A [04-10-2024(online)].pdf | 2024-10-04 |
| 23 | 202321043757-FORM 3 [12-11-2024(online)].pdf | 2024-11-12 |
| 24 | 202321043757-FER.pdf | 2024-12-13 |
| 25 | 202321043757-FER_SER_REPLY [13-02-2025(online)].pdf | 2025-02-13 |
| 26 | 202321043757-FORM 3 [13-03-2025(online)].pdf | 2025-03-13 |
| 27 | 202321043757-US(14)-HearingNotice-(HearingDate-30-07-2025).pdf | 2025-07-10 |
| 28 | 202321043757-FORM-26 [25-07-2025(online)].pdf | 2025-07-25 |
| 29 | 202321043757-Correspondence to notify the Controller [25-07-2025(online)].pdf | 2025-07-25 |
| 30 | 202321043757-Written submissions and relevant documents [13-08-2025(online)].pdf | 2025-08-13 |
| 31 | 202321043757-Retyped Pages under Rule 14(1) [13-08-2025(online)].pdf | 2025-08-13 |
| 32 | 202321043757-2. Marked Copy under Rule 14(2) [13-08-2025(online)].pdf | 2025-08-13 |
| 1 | 202321043757E_13-12-2024.pdf |