Patent Description:
This section is intended to provide a background or context to the invention disclosed below. The description herein may include concepts that could be pursued, but are not necessarily ones that have been previously conceived, implemented or described. Therefore, unless otherwise explicitly indicated herein, what is described in this section is not prior art to the description in this application and is not admitted to be prior art by inclusion in this section. Abbreviations that may be found in the specification and/or the drawing figures are defined below, at the beginning of the detailed description section.

A carrier Bandwidth Part (BWP) is a contiguous set of physical resource blocks, selected from a contiguous subset of common resource blocks on a given carrier. The carrier has some total bandwidth, and the BWPs are part of that. Usually, a limited number (e.g., four) BWPs in uplink (UL) and downlink (DL) can be assigned to a User Equipment (UE).

The network (NW) can configure a wider BWP (e.g., wider than an initial BWP) when the network has received the UE's context/capabilities, but at earliest in the RRCResume message (in the INACTIVE state) or RRCReconfiguration (in the IDLE state) in connection procedures. Because the NW does not know which BWPs the UE can support earlier than at these times, it is not possible to have wider BWP applied, e.g., already ready for use for msg3 (e.g., using an RRCResumeRequest or RRCSetupRequest message). The message msg3 is a message in a Random Access Channel (RACH) procedure where the UE is performing an initial access or reconnection to the network. <NPL>, DISCLOSES FURTHER CLARIFICATION ON THE CONCEPT OF INITIAL ACTIVE BWP AND WELL AS THE REMAINING ISSUES ARE DISCUSSED. ACCORDING TO RANI AGREEMENTS, INITIAL ACTIVE BWP IS USED FOR UE IN IDLE/INACTIVE MODE AND KEEPS VALID UNTIL UE IS EXPLICITLY RECONFIGURED WITH BWPS AFTER RRC CONNECTION IS ESTABLISHED OR RESUMED. FOR INITIAL ACCESS, THE UE USES THE INFORMATION DERIVED FROM MSI UNTIL THE NW CONFIGURES (IF AT ALL) ONE OR MORE BWPS VIA RRC IN SERVINGCELLCONFIGDEDICATED. BRIEF SUMMARY.

According to some aspects, there is provided the subject matter of the independent claims. Some further aspects are defined in the dependent claims. The embodiments that do not fall under the scope of the claims are to be interpreted as examples useful for understanding the disclosure.

The exemplary embodiments herein describe techniques for setting a higher BWP earlier in a connection establishment process to a wireless network. Additional description of these techniques is presented after a system into which the exemplary embodiments may be used is described.

Turning to <FIG>, this figure shows a block diagram of one possible and non-limiting exemplary system in which the exemplary embodiments may be practiced. A user equipment (UE) <NUM>, radio access network (RAN) node <NUM>, and network element(s) <NUM> are illustrated. In <FIG>, a user equipment (UE) <NUM> is in wireless communication with a wireless network <NUM>. A UE is a wireless, typically mobile device that can access a wireless network. The UE <NUM> includes one or more processors <NUM>, one or more memories <NUM>, and one or more transceivers <NUM> interconnected through one or more buses <NUM>. The one or more buses <NUM> may be address, data, or control buses, and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optics or other optical communication equipment, and the like. The UE <NUM> includes a NW access module <NUM>, comprising one of or both parts <NUM>-<NUM> and/or <NUM>-<NUM>, which may be implemented in a number of ways. The NW access module <NUM> may be implemented in hardware as NW access module <NUM>-<NUM>, such as being implemented as part of the one or more processors <NUM>. The NW access module <NUM>-<NUM> may be implemented also as an integrated circuit or through other hardware such as a programmable gate array. In another example, the NW access module <NUM> may be implemented as NW access module <NUM>-<NUM>, which is implemented as computer program code <NUM> and is executed by the one or more processors <NUM>. For instance, the one or more memories <NUM> and the computer program code <NUM> may be configured to, with the one or more processors <NUM>, cause the user equipment <NUM> to perform one or more of the operations as described herein. The UE <NUM> communicates with RAN node <NUM> via a wireless link <NUM>.

The RAN node <NUM> is a base station that provides access by wireless devices such as the UE <NUM> to the wireless network <NUM>. The RAN node <NUM> may be, for instance, a base station for <NUM>, also called New Radio (NR). In <NUM>, the RAN node <NUM> may be a NG-RAN node, which is defined as either a gNB or an ng-eNB. A gNB is a node providing NR user plane and control plane protocol terminations towards the UE, and connected via the NG interface to a 5GC (e.g., the network element(s) <NUM>). The ng-eNB is a node providing E-UTRA user plane and control plane protocol terminations towards the UE, and connected via the NG interface to the 5GC. In the text below the RAN node <NUM> is mainly referred to as a gNB, but this is merely exemplary and is not intended to be limiting. The NG-RAN node may include multiple gNBs, which may also include a central unit (CU) (gNB-CU) <NUM> and distributed unit(s) (DUs) (gNB-DUs), of which DU <NUM> is shown. Note that the DU may include or be coupled to and control a radio unit (RU). The gNB-CU is a logical node hosting RRC, SDAP and PDCP protocols of the gNB or RRC and PDCP protocols of the en-gNB that controls the operation of one or more gNB-DUs. The gNB-CU terminates the F1 interface connected with the gNB-DU. The F1 interface is illustrated as reference <NUM>, although reference <NUM> also illustrates a link between remote elements of the RAN node <NUM> and centralized elements of the RAN node <NUM>, such as between the gNB-CU <NUM> and the gNB-DU <NUM>. The gNB-DU is a logical node hosting RLC, MAC and PHY layers of the gNB or en-gNB, and its operation is partly controlled by gNB-CU. One gNB-CU supports one or multiple cells. One cell is supported by only one gNB-DU. The gNB-DU terminates the F1 interface <NUM> connected with the gNB-CU. Note that the DU <NUM> is considered to include the transceiver <NUM>, e.g., as part of an RU, but some examples of this may have the transceiver <NUM> as part of a separate RU, e.g., under control of and connected to the DU <NUM>. The RAN node <NUM> may also be an eNB (evolved NodeB) base station, for LTE (long term evolution), or any other suitable base station.

The RAN node <NUM> includes a NW access module <NUM>, comprising one of or both parts <NUM>-<NUM> and/or <NUM>-<NUM>, which may be implemented in a number of ways. The NW access module <NUM> may be implemented in hardware as NW access module <NUM>-<NUM>, such as being implemented as part of the one or more processors <NUM>. The NW access module <NUM>-<NUM> may be implemented also as an integrated circuit or through other hardware such as a programmable gate array. In another example, the NW access module <NUM> may be implemented as NW access module <NUM>-<NUM>, which is implemented as computer program code <NUM> and is executed by the one or more processors <NUM>. For instance, the one or more memories <NUM> and the computer program code <NUM> are configured to, with the one or more processors <NUM>, cause the RAN node <NUM> to perform one or more of the operations as described herein. Note that the functionality of the NW access module <NUM> may be distributed, such as being distributed between the DU <NUM> and the CU <NUM>, or be implemented solely in the DU <NUM>.

Two or more RAN nodes <NUM> communicate using, e.g., link <NUM>. The link <NUM> may be wired or wireless or both and may implement, e.g., an Xn interface for <NUM>, an X2 interface for LTE, or other suitable interface for other standards.

The one or more buses <NUM> may be address, data, or control buses, and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optics or other optical communication equipment, wireless channels, and the like. For example, the one or more transceivers <NUM> may be implemented as a remote radio head (RRH) <NUM> for LTE or a distributed unit (DU) <NUM> for gNB implementation for <NUM>, with the other elements of the RAN node <NUM> possibly being physically in a different location from the RRH/DU, and the one or more buses <NUM> could be implemented in part as, e.g., fiber optic cable or other suitable network connection to connect the other elements (e.g., a central unit (CU), gNB-CU) of the RAN node <NUM> to the RRH/DU <NUM>. Reference <NUM> also indicates those suitable network link(s).

The wireless network <NUM> may include a network element or elements <NUM> that may include core network functionality, and which provides connectivity via a link or links <NUM> with a further network, such as a telephone network and/or a data communications network (e.g., the Internet). Such core network functionality for <NUM> may include access and mobility management function(s) (AMF(s)) and/or user plane functions (UPF(s)) and/or session management function(s) (SMF(s)). Such core network functionality for LTE may include MME (Mobility Management Entity)/SGW (Serving Gateway) functionality. These are merely exemplary functions that may be supported by the network element(s) <NUM>, and note that both <NUM> and LTE functions might be supported. The RAN node <NUM> is coupled via a link <NUM> to a network element <NUM>. The link <NUM> may be implemented as, e.g., an NG interface for <NUM>, or an S1 interface for LTE, or other suitable interface for other standards. The network element <NUM> includes one or more processors <NUM>, one or more memories <NUM>, and one or more network interfaces (N/W I/F(s)) <NUM>, interconnected through one or more buses <NUM>. The one or more memories <NUM> and the computer program code <NUM> are configured to, with the one or more processors <NUM>, cause the network element <NUM> to perform one or more operations.

The computer readable memories <NUM>, <NUM>, and <NUM> may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory. The computer readable memories <NUM>, <NUM>, and <NUM> may be means for performing storage functions. The processors <NUM>, <NUM>, and <NUM> may be of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on a multi-core processor architecture, as non-limiting examples. The processors <NUM>, <NUM>, and <NUM> may be means for performing functions, such as controlling the UE <NUM>, RAN node <NUM>, and other functions as described herein.

In general, the various embodiments of the user equipment <NUM> can include, but are not limited to, cellular telephones such as smart phones, tablets, personal digital assistants (PDAs) having wireless communication capabilities, portable computers having wireless communication capabilities, image capture devices such as digital cameras having wireless communication capabilities, gaming devices having wireless communication capabilities, music storage and playback appliances having wireless communication capabilities, Internet appliances (including Internet of Things devices) permitting wireless Internet access and possibly browsing, tablets with wireless communication capabilities, as well as portable units or terminals that incorporate combinations of such functions.

Having thus introduced one suitable but non-limiting technical context for the practice of the exemplary embodiments of this invention, the exemplary embodiments will now be described with greater specificity.

As described above, the network (NW) can configure a wider BWP (e.g., wider than an initial BWP) when the network has received the UE's context/capabilities, but at earliest in the RRCResume message (in the INACTIVE state) or RRCReconfiguration (in the IDLE state) in connection procedures. Because the NW does not know which BWPs the UE can support earlier than at these times, it was not previously possible to have wider BWP applied earlier in this process such as already available for use for msg3, as this is part of a connection (e.g., RACH) procedure.

To address this, the exemplary embodiments set a wider BWP earlier (e.g., than currently performed) in a connection establishment process to a wireless network. An introduction to these concepts is presented now and more detail is provided below. As an introduction, the following are examples of how to configure a wider BWP as early as practical in a connection procedure.

In terms of how the NW might select the configured BWP, this selection of BWP may be based on one or more of the following multiple considerations: incoming data type; required quality for connection; and the like.

Additional detail is now presented. Referring to <FIG>, this figure is a signaling diagram of an existing procedure for connection of a UE from an idle state or inactive state to connect to a wireless network which requires the UE to use an initial BWP which is limited in bandwidth. In <FIG>, the UE is in an RRC idle (also IDLE or RRC_IDLE) state or inactive (also INACTIVE or RRC_INACTIVE) state. See block <NUM>. At block <NUM>, the UE determines it needs to establish a connection with the network <NUM>. This determination could be made because the UE has data to send, paging, signaling. Signaling here means other signaling different from paging in downlink, which also can trigger UE to establish connection to network. In block <NUM>, the UE has an initial BWP configuration (previously received) from one or more system information blocks (SIBs) and will use this BWP configuration to send the msg3 (e.g., RRCSetupRequest or ResumeRequest), but this is limited to the initial BW in the initial BWP. Block <NUM> illustrates the transmission by the UE of the RRCSetupRequest or ResumeRequest (also known as msg3), block <NUM> illustrates the gNB <NUM> sending an RRCSetup or RRCResume to the UE, and block <NUM> illustrates the UE <NUM> sending an RRCSetupComplete or RRCResumeComplete. This ends the connection process.

Referring to <FIG>, this figure is a signaling diagram for a BWP provided in paging option, in accordance with an exemplary embodiment. The UE is in an idle state or an inactive state in block <NUM>. The gNB <NUM> sends paging to the UE <NUM> in step <NUM>. The paging includes a selected (e.g., optimized) BWP based on, e.g., UE capabilities (capas) or NW deployment, the latter where the enabling feature is controlled by the NW. Step <NUM>-<NUM> uses a wider BWP as compared with the initial BWP used in step <NUM> in <FIG>, and steps <NUM>, and <NUM> are assumed to be the same as previously described. Note that the paging in step <NUM> causes the UE to establish a connection to the network.

Turning to <FIG>, this figure is a signaling diagram for a BWP provided in a release message option, in accordance with an exemplary embodiment. In this figure, the UE starts in the connected (also CONNECTED or RRC_CONNECTED) state in block <NUM>, and the gNB <NUM> sends a release message (e.g., RRCRelease) in reference <NUM>. The release message includes a selected (e.g., optimized) BWP based on, e.g., UE capas or NW deployment. The release message also causes the UE to transition from the connected state to one of the idle state or the inactive state (see block <NUM>). In block <NUM>, the UE needs to connect to the NW for a reason, such as to transmit data. In block <NUM>, the UE uses the BWP provided in the release message to send the msg3 (RRCSetupRequest/RRCResumeRequest). Step <NUM>-<NUM> uses a wider BWP as compared with the initial BWP used in step <NUM> in <FIG>, and steps <NUM>, and <NUM> are assumed to be the same as previously described.

Referring to <FIG>, this figure is a signaling diagram for a BWP provided in system information option, in accordance with an exemplary embodiment. In this figure, the UE starts in an idle state or an inactive state (block <NUM>). The UE reads SIB(s) from a cell (belonging to the gNB <NUM>) and gets knowledge of possible BWPs (e.g., broadcast in the SIB(s)) to be applied in this cell. Note that this example has the gNB <NUM> broadcasting to multiple (e.g., all) UEs in a cell. In block <NUM>, the UE needs to establish connection to the wireless network <NUM> for a reason. In block <NUM>, the UE supporting the new proposed feature will use a new, wider BWP provided in the SIB(s) (and not the SIB with the initial, narrower BWP), if the UE also supports the proposed and selected wider BWP. The UE <NUM> will send the RRCSetupRequest or ResumeRequest message in step <NUM>-<NUM> (using a wider BWP than used in the initial BWP used in step <NUM> of <FIG>), and the other steps <NUM>, and <NUM> are assumed to be the same as previously described.

Turning to <FIG>, this figure is a logic flow diagram performed by a network node for setting a wider BWP earlier in a connection establishment process to a wireless network. This figure further illustrates the operation of an exemplary method or methods, a result of execution of computer program instructions embodied on a computer readable memory, functions performed by logic implemented in hardware, and/or interconnected means for performing functions in accordance with exemplary embodiments. For instance, the NW access module <NUM> may include multiples ones of the blocks in <FIG>, where each included block is an interconnected means for performing the function in the block. The blocks in <FIG> are assumed to be performed by a network node such as (e.g., or under control of) a base station such as gNB <NUM>, e.g., under control of the NW access module <NUM> at least in part.

In block <NUM>, the gNB <NUM> sends an initial bandwidth part to a UE in system information. The initial BWP is the BWP that would be used by the UE except for the techniques presented herein, which supply a wider BWP to the UE. That is, the bandwidth (BW) of the supplied BWP is wider than the BW of the (narrower) initial BWP. In block <NUM>, the eNB <NUM> selects a selected bandwidth part based on one or more of the following: incoming data type or required quality for connection or UE power saving state.

In block <NUM>, the gNB <NUM> sends the selected bandwidth part to be used by the user equipment during a connection procedure used to connect the user equipment to the wireless network after the user equipment enters an idle or inactive state. The selected bandwidth part is different from (e.g., wider or smaller than) an initial bandwidth part that would have been used by the user equipment during the connection procedure, e.g., as sent in block <NUM>. The typical scenario is that the selected BWP is wider than the initial BWP. However, this idea may be extended to the other use case, for example, a smaller BWP case, which may be useful, e.g., for UE power saving. The selected BWP could be sent via the following: sent in paging (block <NUM>, see <FIG>); sent in a release message (block <NUM>, see <FIG>); or broadcast in system information (block <NUM>, see <FIG>). In block <NUM>, the gNB <NUM> receives a message from the UE for connection to the wireless network using the selected bandwidth part (e.g., using msg3). In block <NUM>, the gNB <NUM> completes the connection process, e.g., using steps <NUM> and <NUM> previously described.

<FIG> also illustrates another example, where in block <NUM> the gNB <NUM> selects multiple BWPs that might be used by the UE <NUM>. In block <NUM>, as part of the sending in block <NUM>, the gNB <NUM> sends indications of multiple BWPs to the UE <NUM>. The idea is to let the UE select one of the multiple BWPs, and the gNB <NUM> needs to monitor (see block <NUM>) all these BWPs to identify which is used for msg3 and to receive (block <NUM>) the message. In additional detail, it has been previously indicated that the NW knows if UE is using default (e.g. UE not supporting new feature) or wider BWP allowed in this cell via at least these two options:.

The network monitors all selected multiple BWPs to determine which one is used, and this is one possible technique. The network also can get help from the UE, e.g., where the UE indicates the selected BWP index in MSG1, or uses dedicated RACH resource allocated to each BWP.

<FIG> is a logic flow diagram performed by a UE for setting a wider BWP earlier in a connection establishment process to a wireless network. This figure further illustrates the operation of an exemplary method or methods, a result of execution of computer program instructions embodied on a computer readable memory, functions performed by logic implemented in hardware, and/or interconnected means for performing functions in accordance with exemplary embodiments. For instance, the NW access module <NUM> may include multiples ones of the blocks in <FIG>, where each included block is an interconnected means for performing the function in the block. The blocks in <FIG> are assumed to be performed by the UE <NUM>, e.g., under control of the NW access module <NUM> at least in part.

In block <NUM>, the UE <NUM> receives an initial bandwidth part from a network node in system information. This is the initial, narrower BWP. In block <NUM>, the UE <NUM> receives a selected bandwidth part to be used by the user equipment during a connection procedure used to connect the user equipment to the wireless network after the user equipment enters an idle or inactive state. The selected bandwidth part is different from (e.g., wider or smaller than) an initial bandwidth part that would have been used by the user equipment during the connection procedure and that was delivered to the UE in block <NUM>. The receiving may be performed in paging (after transition to idle/inactive mode), see block <NUM> and <FIG>. The receiving may also be performed in a release message (prior to transition to idle/inactive mode), see block <NUM> and <FIG>. Finally, the receiving may be performed in broadcast in system information (after transition to idle/inactive mode), see block <NUM> and <FIG>.

In block <NUM>, the UE <NUM> sends a message to the wireless network using the selected bandwidth part (e.g., using msg3). In block <NUM>, the UE <NUM> completes the connection process, e.g., using steps <NUM> and <NUM> previously described.

<FIG> also illustrates another example also illustrated by <FIG>, where in block <NUM>, as part of the receiving in block <NUM>, the UE <NUM> receives indications of multiple BWPs to be used by the UE <NUM>. As described above, the idea is to let the UE select (block <NUM>) one of the multiple BWPs indicated in block <NUM>, and the UE sends the message (e.g., msg3) on the selected BW in block <NUM>. The gNB <NUM> needs to monitor (see block <NUM> of <FIG>) all these BWPs to identify which is used for msg3 and to receive (block <NUM>) the message.

Additional exemplary embodiments are as follows.

Example <NUM>. The method of example <NUM>, wherein the initial bandwidth part was previously supplied to the user equipment by the network node in system information.

Example <NUM>. The method of any of examples <NUM> or <NUM>, further comprising, prior to the sending, selecting the selected bandwidth part based on one or more of the following: incoming data type or required quality for connection or power saving state of the user equipment.

Example <NUM>. The method of any of examples <NUM> to <NUM>, wherein:.

Example <NUM>. The method of any of examples <NUM> to <NUM>, wherein sending the selected bandwidth part or parts to be used by the user equipment further comprises sending the selected bandwidth part or parts in a paging message after the user equipment has entered one of an idle state or an inactive state.

Example <NUM>. The method of any of examples <NUM> to <NUM>, wherein sending the selected bandwidth part or parts to be used by the user equipment further comprises sending the selected bandwidth part or parts in a release message used to cause the user equipment to transition from a connected state to one of an idle state or an inactive state.

Example <NUM>. The method of any of examples <NUM> to <NUM>, wherein sending the selected bandwidth part or parts to be used by the user equipment further comprises sending the selected bandwidth part in system information.

Example <NUM>. The method of example <NUM>, wherein the sending multiple selected bandwidth part parts further comprises including a validity time over which one or more of the multiple selected bandwidth parts may be used.

Example <NUM>. The method of either example <NUM> or example <NUM>, wherein the sending multiple selected bandwidth part further comprises including an area in which the one or more of the multiple selected bandwidth parts may be used.

Example <NUM>. The method of any of examples <NUM> or <NUM>, wherein the sending multiple selected bandwidth part is performed by one of the following: broadcasting the multiple selected bandwidth parts in system information; sending the multiple selected bandwidth parts in one or more paging messages; or sending the multiple selected bandwidth parts in one or more release messages.

Example <NUM>. The method of any of examples <NUM> to <NUM>, wherein the selected bandwidth part is one of the following: wider than initial bandwidth part; or smaller than the initial bandwidth part.

Example <NUM>. The method of example <NUM>, wherein the initial bandwidth part was previously received by the user equipment and sent by the network node in system information.

Example <NUM>. The method of any of examples <NUM> or <NUM>, wherein:.

Example <NUM>. The method of example <NUM>, wherein the user equipment performs one of the following: performing an access via one or more associated dedicated resources, or sending an indication from the user equipment of the one selected bandwidth part in one or more resources.

Example <NUM>. The method of any of examples <NUM> to <NUM>, wherein receiving the selected bandwidth part or parts to be used by the user equipment further comprises receiving the selected bandwidth part or parts in a paging message after the user equipment has entered one of an idle state or an inactive state.

Example <NUM>. The method of any of examples <NUM> to <NUM>, wherein receiving the selected bandwidth part or parts to be used by the user equipment further comprises receiving the selected bandwidth part or parts in a release message used to cause the user equipment to transition from a connected state to one of an idle state or an inactive state.

Example <NUM>. The method of any of examples <NUM> to <NUM>, wherein receiving the selected bandwidth part or parts to be used by the user equipment further comprises receiving the selected bandwidth part in system information.

Example <NUM>. The method of example <NUM>, wherein the receiving the multiple selected bandwidth part or parts further comprises receiving a validity time over which one or more of the multiple bandwidth parts may be used, and performing the selecting the one selected bandwidth part and the sending the message based on the validity time.

Example <NUM>. The method of either example <NUM> or example <NUM>, wherein the receiving the multiple selected bandwidth parts further comprises receiving an area in which the one or more of the multiple bandwidth parts may be used, and performing the selecting the one selected bandwidth part and the sending the message based on the area.

Example <NUM>. The method of any of examples <NUM> or <NUM>, wherein the receiving the multiple selected bandwidth part is performed by one of the following: receiving in a broadcast the multiple selected bandwidth parts in system information; receiving the multiple selected bandwidth parts in one or more paging messages; or receiving the multiple selected bandwidth parts in one or more release messages.

Example <NUM>. A computer program, comprising code for performing the methods of any of examples <NUM> to <NUM>, when the computer program is run on a computer.

Example <NUM>. The computer program according to example <NUM>, wherein the computer program is a computer program product comprising a computer-readable medium bearing computer program code embodied therein for use with the computer.

Example <NUM>. The computer program according to example <NUM>, wherein the computer program is directly loadable into an internal memory of the computer.

Example <NUM>. An apparatus, comprising:.

Example <NUM>. The apparatus of example <NUM>, wherein the initial bandwidth part was previously supplied to the user equipment by the network node in system information.

Example <NUM>. The apparatus of any of examples <NUM> or <NUM>, further comprising means, performed prior to the means for sending, for selecting the selected bandwidth part based on one or more of the following: incoming data type or required quality for connection or power saving state of the user equipment.

Example <NUM>. The apparatus of any of examples <NUM> to <NUM>, wherein:.

Example <NUM>. The apparatus of any of examples <NUM> to <NUM>, wherein the means for sending the selected bandwidth part or parts to be used by the user equipment further comprises means for sending the selected bandwidth part or parts in a paging message after the user equipment has entered one of an idle state or an inactive state.

Example <NUM>. The apparatus of any of examples <NUM> to <NUM>, wherein means for sending the selected bandwidth part or parts to be used by the user equipment further comprises means for sending the selected bandwidth part or parts in a release message used to cause the user equipment to transition from a connected state to one of an idle state or an inactive state.

Example <NUM>. The apparatus of any of examples <NUM> to <NUM>, wherein the means for sending the selected bandwidth part or parts to be used by the user equipment further comprises means for sending the selected bandwidth part in system information.

Example <NUM>. The apparatus of example <NUM>, wherein the means for sending multiple selected bandwidth part parts further comprises means for including a validity time over which one or more of the multiple selected bandwidth parts may be used.

Example <NUM>. The apparatus of either example <NUM> or example <NUM>, wherein the means for sending multiple selected bandwidth part further comprises means for including an area in which the one or more of the multiple selected bandwidth parts may be used.

Example <NUM>. The apparatus of any of examples <NUM> or <NUM>, wherein the means for sending multiple selected bandwidth part is performed by performing one of the following: broadcasting the multiple selected bandwidth parts in system information; sending the multiple selected bandwidth parts in one or more paging messages; or sending the multiple selected bandwidth parts in one or more release messages.

Example <NUM>. The apparatus of any of examples <NUM> to <NUM>, wherein the selected bandwidth part is one of the following: wider than initial bandwidth part; or smaller than the initial bandwidth part.

Example <NUM>. A base station comprising any of the apparatus of examples <NUM> to <NUM>.

Example <NUM>. The apparatus of example <NUM>, wherein the initial bandwidth part was previously received by the user equipment and sent by the network node in system information.

Example <NUM>. The apparatus of any of examples <NUM> or <NUM>, wherein:.

Example <NUM>. The apparatus of example <NUM>, wherein the user equipment operates one of the following: means for performing an access via one or more associated dedicated resources, or means for sending an indication from the user equipment of the one selected bandwidth part in one or more resources.

Example <NUM>. The apparatus of any of examples <NUM> to <NUM>, wherein the means for receiving the selected bandwidth part or parts to be used by the user equipment further comprises means for receiving the selected bandwidth part or parts in a paging message after the user equipment has entered one of an idle state or an inactive state.

Example <NUM>. The apparatus of any of examples <NUM> to <NUM>, wherein the means for receiving the selected bandwidth part or parts to be used by the user equipment further comprises means for receiving the selected bandwidth part or parts in a release message used to cause the user equipment to transition from a connected state to one of an idle state or an inactive state.

Example <NUM>. The apparatus of any of examples <NUM> to <NUM>, wherein the means for receiving the selected bandwidth part or parts to be used by the user equipment further comprises means for receiving the selected bandwidth part in system information.

Example <NUM>. The apparatus of example <NUM>, wherein the means for receiving the multiple selected bandwidth part or parts further comprises means for receiving a validity time over which one or more of the multiple bandwidth parts may be used, and means for performing the selecting the one selected bandwidth part and the sending the message based on the validity time.

Example <NUM>. The apparatus of either example <NUM> or example <NUM>, wherein the means for receiving the multiple selected bandwidth parts further comprises means for receiving an area in which the one or more of the multiple bandwidth parts may be used, and means for performing the selecting the one selected bandwidth part and the sending the message based on the area.

Example <NUM>. The apparatus of any of examples <NUM> or <NUM>, wherein the means for receiving the multiple selected bandwidth part is performed by one of the following: receiving in a broadcast the multiple selected bandwidth parts in system information; receiving the multiple selected bandwidth parts in one or more paging messages; or receiving the multiple selected bandwidth parts in one or more release messages.

Example <NUM>. A user equipment comprising any of the apparatus of examples <NUM> to <NUM>.

Example <NUM>. A wireless communication system comprising any of the apparatus of examples <NUM> to <NUM> and any of the apparatus of examples <NUM> to <NUM>.

Example <NUM>. The apparatus of example <NUM>, wherein the at least one memory and the computer program code are further configured, with the at least one processor, to cause the apparatus to perform operations in any of the methods of examples <NUM> to <NUM>.

Without in any way limiting the scope, interpretation, or application of the claims appearing below, a technical effect and advantage of one or more of the example embodiments disclosed herein is a maximum BWP used as soon as possible, which means connected sessions last a minimum time resulting in reduced power consumption and application perceived delays. Another technical effect and advantage of one or more of the example embodiments disclosed herein is the msg3 size can be larger, which means that a lot of enhancements potential is opened. Via frequency diversity, also the performance on msg3 (at least in interference limited scenarios) can be improved. Another technical effect and advantage of one or more of the example embodiments disclosed herein includes avoiding BWP switching time. That is, the first setting of the initial BWP then the subsequent setting of the wider BWP takes time in the UE to get the new BWP active, and the instant techniques avoid this time.

Embodiments herein may be implemented in software (executed by one or more processors), hardware (e.g., an application specific integrated circuit), or a combination of software and hardware. In an example embodiment, the software (e.g., application logic, an instruction set) is maintained on any one of various conventional computer-readable media. In the context of this document, a "computer-readable medium" may be any media or means that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer, with one example of a computer described and depicted, e.g., in <FIG>. A computer-readable medium may comprise a computer-readable storage medium (e.g., memories <NUM>, <NUM>, <NUM> or other device) that may be any media or means that can contain, store, and/or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer. A computer-readable storage medium does not comprise propagating signals.

Claim 1:
A method, comprising:
broadcasting (<NUM>), by a network node in a wireless network, an initial bandwidth part to a user equipment in system information; wherein the method further comprises:
selecting (<NUM>), by the network node, at least one bandwidth part based on incoming data type and/or required quality for a connection to be established;
sending (<NUM>), by the network node toward a user equipment, an indication of the at least one selected bandwidth part to be used by the user equipment during a connection establishment procedure to connect the user equipment to the wireless network, wherein the at least one selected bandwidth part is wider than the initial bandwidth part, and wherein the at least one selected bandwidth part is sent via paging (<NUM>) or system information (<NUM>) after the user equipment transition to idle/inactive state, or in a release message (block <NUM>) prior to the user equipment transition to idle/inactive state, for the wider bandwidth part being in use for an msg3 message of random access procedure, and
in response to receiving, by the network node and from the user equipment, the msg3 message for a connection establishment procedure in the selected bandwidth part, performing (<NUM>) connection establishment.