Bandwidth part operations for idle and inactive states

According to an aspect, a wireless device is configured to selectively operate in one of two or more previously configured bandwidth parts (BWPs), each BWP being a different subset of an available bandwidth for uplink and/or downlink operation. The wireless device switches from an active RRC state to an inactive RRC state, and, after the switching, retains a physical layer configuration corresponding to the BWP active just prior to the switching.

TECHNICAL FIELD

The present disclosure generally relates to the field of wireless network communications, and more particularly, to wireless devices configured to selectively operate in one of two or more previously configured bandwidth parts (BWPs), each BWP being a different subset of an available bandwidth for uplink and/or downlink operation.

BACKGROUND

There is an ongoing discussion in the 3rdGeneration Partnership Project (3GPP) 5G standardization about the so-called bandwidth parts (BWPs). One reason for using BWPs are that some user equipments (UEs) might not be able to use the entire bandwidth, in which case they are assigned a smaller BWP that they are capable of handling. Another reason for using BWPs is to save battery power. A UE may be assigned a narrower BWP to reduce the needed energy.

So far, it has been agreed that each UE is assigned with at least an initial BWP (same for all UEs, with a narrow bandwidth enough for all UEs to be able to use it) and a default BWP. The default BWP may be the same as the initial BWP but may also be different (i.e., different UEs will typically have different default BWPs). In addition to initial and default BWPs, the UE can be configured with additional BWPs. It has been agreed that a UE can have up to four downlink/uplink BWPs. An important agreement is also that at any point in time, only one BWP is active for a specific UE. On deactivated BWPs, the UE does not monitor a physical downlink control channel (PDCCH) and does not transmit on a physical uplink control channel (PUCCH), physical random access channel (PRACH) and uplink shared channel (UL-SCH).

The UE is configured with BWPs using radio resource control (RRC) signaling (except the initial signal) and switching between BWPs is done by downlink control information (DCI) on a downlink physical control channel (DPCCH). There is also the possibility of switching to the default BWP when the bwp-InactivityTimer expires.

A configured BWP may have RACH resources, but there may also be BWPs without RACH resources, in which case the UE will perform random access on another BWP where there are RACH resources available. Also, for a physical uplink control channel (PUCCH), a BWP may or may not have a PUCCH configured. The reason for not having a PUCCH configured is that it occupies resources that will lead to overhead (especially in configured but not active BWPs). In the case where the UE is moved to a BWP without PUCCH, the consequence of not having a PUCCH configured in the active BWP is that the UE cannot send scheduling requests (SRs) or hybrid automatic repeat request (HARQ) feedback for downlink transmissions. The PUCCH is also used for channel quality indicators (CQIs) that cannot be transmitted without a PUCCH configured. Most probably, the network would need to reconfigure the BWP with a PUCCH also on the active BWP in case it was not configured from the start for performance reasons.

According to the 3GPP document 3GPP TS 38.331, V15.0.0 (December 2017), a BandwidthPart-Config information element (IE) is used to configure a bandwidth part, which is defined in 3GPP TS 38.211.

For each serving cell, the network configures at least an initial bandwidth part comprising of at least a downlink bandwidth part and one (if the serving cell is configured with an uplink) or two (if using supplementary uplink (SUL)) uplink bandwidth parts. Furthermore, the network may configure additional uplink and downlink bandwidth parts for a serving cell.

The bandwidth configuration is split into uplink and downlink parameters and into common and dedicated parameters. Common parameters (in UplinkBWP-Common and DownlinkBWPCommon) are “cell specific” and the network ensures the necessary alignment with corresponding parameters of other UEs. The common parameters of the initial bandwidth part of the PCell are also provided via system information. For all other serving cells, the network provides the common parameters via dedicated signaling.

One possibility for the contents of a BandwidthPart-config information element is as follows:

The following excerpt pertains to ongoing standardization of PWB operation for 3GPP and includes a preliminary specification for a ServingCellConfigCommon information element is shown, which may be used to configure cell-specific parameters of a UE's serving cell, including, for example, an initial downlink BWP, as well as a ServingCellConfig information element, which may be used to configure certain UE-specific parameters, such as an initial downlink BWP and/or a first active downlink BWP:

TABLE 1Conditional PresenceExplanationHOAndServCellAddThis field is mandatory present for inter-cell handover and upon serving cell(PSCell/SCell) addition. Otherwise, thefield is absent.InterFreqHOAndServCellAddThis field is mandatory present for inter-frequency inter-cell handover and uponserving cell (PSCell/SCell) addition.Otherwise, the field is absent.

1.1.1.2—ServingCellConfigThe ServingCellConfig IE is used to configure (add or modify) the UE with a serving cell, which may be the SpCell or an SCell of an MCG or SCG. The parameters herein are mostly UE specific but partly also cell specific (e.g. in additionally configured bandwidth parts).

A problem with the solution defined as of version 15.0.0 of 3GPP TS 38.211 and version 15.0.0 of 3GPP TS 38.331 is that each time the UE enters either an Idle or Inactive state, the UE discards the dedicated BWP configurations. This means that all BWP configurations sent via the RRC signaling to the UE will be discarded.

SUMMARY

Embodiments of the present invention address this problem. When the UE enters a Connected state again, it will use the initial BWP for accessing the network and receiving the dedicated RRC BWP configuration once more. Since the transition from Connected to Idle/Inactive and Idle/Inactive to Connected may be quite frequent, the overhead of transmitting the dedicated BWP configurations via RRC may be rather high. An advantage of the embodiments is that the dedicated BWP configuration signaling may be avoided each time the UE re-enters Connected mode.

According to some embodiments, a method, in a wireless device (e.g., UE) configured to selectively operate in one of two or more previously configured BWPs, where each BWP is a different subset of an available bandwidth for uplink and/or downlink operation, includes switching from an active RRC state to an inactive RRC state and, after said switching, retaining a physical layer configuration corresponding to the BWP active just prior to said switching.

According to some embodiments, a method in a network node serving a wireless device configured to selectively operate in one of two or more previously configured BWPs, where each BWP is a different subset of an available bandwidth for uplink and/or downlink operation, includes sending, to at least one wireless device, an indication to retain, upon switching from an active RRC state to an inactive RRC state, a physical layer configuration corresponding to a BWP in use by the wireless device just prior to said switching.

According to some embodiments, a wireless device configured to selectively operate in one of two or more previously configured BWPs, each BWP being a different subset of an available bandwidth for uplink and/or downlink operation, includes transceiver circuitry configured for communicating with a network node of a wireless communication network and processing circuitry operatively associated with the transceiver circuitry. The processing circuitry is configured to switch from an active RRC state to an inactive RRC state, and after said switching, retain a physical layer configuration corresponding to the BWP active just prior to said switching.

According to some embodiments, a network node configured to serve a wireless device configured to selectively operate in one of two or more previously configured BWPs, where each BWP is a different subset of an available bandwidth for uplink and/or downlink operation, includes transceiver circuitry configured for communicating with the wireless device and processing circuitry operatively associated with the transceiver circuitry. The processing circuitry is configured to send, to at least one wireless device, an indication to retain, upon switching from an active RRC state to an inactive RRC state, a physical layer configuration corresponding to a BWP in use by the wireless device just prior to said switching.

Further aspects of the present invention are directed to an apparatus, wireless device, network node, computer program products or computer readable storage medium corresponding to the methods summarized above and functional implementations of the above-summarized apparatus and wireless device.

Of course, the present invention is not limited to the above features and advantages. Those of ordinary skill in the art will recognize additional features and advantages upon reading the following detailed description, and upon viewing the accompanying drawings.

DETAILED DESCRIPTION

In RAN2 AH1801, the following agreements regarding BWP were made:Agreements for PCell and PSCell (applicability to SCells depends on offline on BWP signalling structure)1: RAN2 understand that the SSB of the cell where Idle/inactive UE camps is the cell defining SSB.2 In idle/inactive states, system information provides the UE with a common configuration that corresponds to the Initial DL and UL BWP (and no other BWPs).FFS Whether the Initial BWP provided in SI and the Initial BWP provided in dedicated signalling are defined as 2 types to simply the specification. Stage 3 issue.2i Common and dedicated configuration of the Initial BWP can be provided in RRC connected state. Common configuration is only provided at synchronous reconfiguration.2ii Other BWPs can only be configured in RRC connected.3 Idle/inactive UE monitors system information and paging information in the initial DL BWP.4 Idle/inactive UE performs random access in the initial UL/DL BWP.5 Initial BWP configuration as provided in system information should be the same as the common configuration of the Initial BWP configuration provided in RRC connected provided at synchronous reconfiguration.6 Upon transition to the idle state, UE releases all dedicated BWP configurations (and therefore UE applies the initial BWP configuration from system information of the cell where the UE is camped).7 Upon transition to the inactive state, UE applies the initial BWP configuration from system information of the cell where the UE is camped.8 BWPs have no specification impact to cell selection and reselection. Cell selection and reselection is based on SSB.FFS Whether any PHY layer configuration are kept while the UE is in Inactive Under these agreements, it is not clear whether the dedicated BWP configuration is kept when the UE makes a transition to inactive. If the UE enters Idle it is clear all dedicated BWP configurations are discarded, as shown inFIG.1.

FIG.1illustrates a schematic picture of UE behavior when the UE makes a transition to Idle/Inactive.

The following sections describe embodiments for the Inactive case. It should be noted that these solutions can also be applied to the case when the UE enters the Idle state and then reconnects to the Connected state.

According to a first approach, the UE keeps the current dedicated BWP configuration when entering into an Inactive state. With such a solution, the need for dedicated RRC BWP configuration signaling may be decreased or completely avoided when the UE re-enters Connected mode again (i.e., seeFIG.2). Note that when the UE enters into the Inactive state, the network can still release the resources for a subset of PHY layer configurations for the UE (see BWP1 inFIG.2). For example, configured PUCCH and channel state information reference signal (CSI-RS) resources, synchronization reference signal (SRS) reporting, or teardown indication (TCI)-states can be released, and the resources used for such procedures can be used by another UE still active in BWP1.

FIG.2illustrates a first embodiment with an initial bandwidth part202and bandwidth part 1204. If the dedicated BWP configurations206have changed, the network must update the UE with the new dedicated BWP configurations via RRC, at least for the changed part of the configuration. Accordingly, the UE shall keep or retain the dedicated BWP configurations when it enters into an Inactive state212and the network can assume that the UE has the same BWP configurations as before entering the Inactive state212.

In a further embodiment, the network signals to the UE during the transition to an Inactive state212to keep the dedicated BWP configurations214or a subset of these.

In yet another embodiment, when the UE re-enters into Connected mode216again, the network transmits only the new dedicated BWP configurations via RRC (overriding the old ones) entirely or by means of a delta signaling, which means overriding only the changed ones.

A further optimization of the solution, according to an embodiment, is that when the UE enters Inactive212it will also continue to monitor BWP1204(earlier active BWP), listen to the system information and paging from BWP1204, and also make random access in BWP1204. In other words, BWP1204can be used as a default BWP and/or an initial BWP. This removes the need for a switch to and from initial BWP202, seeFIG.3. If the random access fails, the UE switches automatically to initial BWP202and discards the dedicated BWP configurations.

A possible problem is that after the UE enters Inactive212, it might move and change cells, as in a handover. The normal procedure is then, as usual, to read the system information (SI) and get the initial BWP configuration and make a random access on the initial BWP. Thereafter, the UE can receive dedicated BWP configurations via RRC.

In this case of a handover, as illustrated byFIG.4, it is likely that the BWP configurations for adjacent cells are the same, since the cell properties are probably the same (e.g., same frequencies, same capabilities etc.). A solution to avoid sending the dedicated BWP configurations via RRC when the UE has changed its cell is then as follows. The source node sends the dedicated BWP configuration to the new cell via the Xn interface408. Assuming the example inFIG.4, the dedicated BWP configuration is sent from the source gNB1402to the target gNB2404when the UE406changes its cell to gNB2404.

If the BWP configuration is the same for both cells, then either: 1) the target node404indicates whether this is still valid or not (the source node402can then indicate to the UE406to keep the latest BWP configuration or not); or 2) the target node404directly indicates to the UE406to keep the latest BWP configuration.

In another embodiment, the UE may use the stored dedicated configurations conditionally based on: an RRC suspend (or similar RRC message) indication of whether to keep the dedicated BWP configuration or not (in some cases, the network may ask UE to keep the all/subset of configurations for all/subset of BWPs); the SI indicates a change in BWP related configuration; and/or the SI information of the current cell (the UE is camped on) is different than the SI information of the cell that the UE is configured with (regarding the BWP related information).

Even though the previous embodiment suggests a more optimized solution, the UE may also assume that the stored BWP configuration is invalid and can be released if the cell or the node the UE is camped on changes.

The UE can be configured with dedicated BWP configurations by means RRC connection setup, RRC (connection) reconfiguration or RRC (connection) resume or similar messages. RRC (connection) suspend or release messages can explicitly indicate whether to keep BWP configurations such as physical layer configurations, or implicitly the message itself can indicate whether the physical layer configuration is kept. For example, when an RRC suspend message is sent, the UE always keeps the BWP configuration.

Even though the embodiments refer to the dedicated configurations, the stored information may also be common configurations (additionally or solely), and in some cases, the common configuration stored may override the common configuration broadcast by the SI.

The terminology used herein is for describing the embodiments and may change or be different in the technology specifications or implementations. In some cases, the default BWP and initial BWP can be replaced. RAN1 defines default BWP (downlink only) for power saving purpose and agreed that the default BWP can be different from the initial downlink BWP, and the DL default BWP may not contain a synchronization signal block (SSB). The default BWP can be UE specific and different UEs can be configured with different default BWP according to their services and capabilities. However, the initial downlink/uplink BWPs are common for different UEs configured with the same cell defining SSB.

In some cases, the stored configuration could be for all BWPs or a subset of BWPs. It may include the default BWP and/or the initial BWP configuration, or it may not. Various embodiments can be applied in the downlink only, the uplink only, or both.

Upon entering an Inactive state, the dedicated BWP configuration is kept, and when the UE re-enters in Connected mode, it re-applies the dedicated BWP configurations even though no dedicated BWP configurations are transmitted from the network.

In further embodiments, the network signals to the UE during the transition to the Inactive state to keep the dedicated BWP configurations.

In yet another embodiment, when the UE re-enters Connected mode again, the network transmits parts of the new dedicated BWP configurations via RRC (partly overriding the old BWP configuration).

In yet another embodiment, when the UE enters the Inactive state, it will also continue to monitor the BWP1 and listen to the system information and paging from the active BWP (not initial BWP) and when the UE re-enters Connected mode, the UE will try to make a random access in the dedicated BWP.

FIG.5shows a network node30, such as a base station, which may be configured to carry out one or more of these disclosed techniques. The base station may be an evolved Node B (eNodeB), Node B or gNB. These operations can be performed by other kinds of network nodes or relay nodes. In the non-limiting embodiments described below, the network node30will be described as being configured to operate as a cellular network access node in an LTE network or NR network.

Those skilled in the art will readily appreciate how each type of node may be adapted to carry out one or more of the methods and signaling processes described herein, e.g., through the modification of and/or addition of appropriate program instructions for execution by processing circuits32.

The network node30facilitates communication between wireless terminals, other network access nodes and/or the core network. The network node30may include communication interface circuitry38that includes circuitry for communicating with other nodes in the core network, radio nodes, and/or other types of nodes in the network for the purposes of providing data and/or cellular communication services. The network node30communicates with wireless devices using antennas34and transceiver circuitry36. The transceiver circuitry36may include transmitter circuits, receiver circuits, and associated control circuits that are collectively configured to transmit and receive signals according to a radio access technology, for the purposes of providing cellular communication services.

The network node30also includes one or more processing circuits32that are operatively associated with the transceiver circuitry36and, in some cases, the communication interface circuitry38. The processing circuitry32comprises one or more digital processors42, e.g., one or more microprocessors, microcontrollers, Digital Signal Processors (DSPs), Field Programmable Gate Arrays (FPGAs), Complex Programmable Logic Devices (CPLDs), Application Specific Integrated Circuits (ASICs), or any mix thereof. More generally, the processing circuitry32may comprise fixed circuitry, or programmable circuitry that is specially configured via the execution of program instructions implementing the functionality taught herein, or may comprise some mix of fixed and programmed circuitry. The processor42may be multi-core, i.e., having two or more processor cores utilized for enhanced performance, reduced power consumption, and more efficient simultaneous processing of multiple tasks.

The processing circuitry32also includes a memory44. The memory44, in some embodiments, stores one or more computer programs46and, optionally, configuration data48. The memory44provides non-transitory storage for the computer program46and it may comprise one or more types of computer-readable media, such as disk storage, solid-state memory storage, or any mix thereof. Here, “non-transitory” means permanent, semi-permanent, or at least temporarily persistent storage and encompasses both long-term storage in non-volatile memory and storage in working memory, e.g., for program execution. By way of non-limiting example, the memory44comprises any one or more of SRAM, DRAM, EEPROM, and FLASH memory, which may be in the processing circuitry32and/or separate from the processing circuitry32. The memory44may also store any configuration data48used by the network access node30. The processing circuitry32may be configured, e.g., through the use of appropriate program code stored in memory44, to carry out one or more of the methods and/or signaling processes detailed hereinafter.

The processing circuitry32of the network node30is configured, according to some embodiments, to serve a wireless device configured to selectively operate in one of two or more previously configured BWPs, where each BWP being a different subset of an available bandwidth for uplink and/or downlink operation. The processing circuitry32of the network node30is configured to send, to at least one wireless device, an indication to retain, upon switching from an active RRC state to an inactive RRC state, a physical layer configuration corresponding to a BWP in use by the wireless device just prior to said switching.

The processing circuitry32of the network node30may also be configured to perform a corresponding method600, as shown inFIG.6. The method600includes sending, to at least one wireless device, an indication to retain, upon switching from an active RRC state to an inactive RRC state, a physical layer configuration corresponding to a BWP in use by the wireless device just prior to said switching (block602). The sending may be performed in conjunction with transitioning the wireless device to the inactive RRC state. The sending may be via broadcasted SI.

The method600may further include sending to the wireless device, after said sending the indication to retain, one or more updates to the physical layer configuration corresponding to the BWP in use by the wireless device just prior to said switching.

FIG.7illustrates a diagram of a wireless device, shown as wireless device50, according to some embodiments. The wireless device50may be considered to represent any wireless terminals that may operate in a network, such as a UE in a cellular network. Other examples may include a communication device, target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine communication (M2M), a sensor equipped with UE, PDA (personal digital assistant), Tablet, mobile terminal, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), etc.

The wireless device50is configured to communicate with a radio network node or base station in a wide-area cellular network via antennas54and transceiver circuitry56. The transceiver circuitry56may include transmitter circuits, receiver circuits, and associated control circuits that are collectively configured to transmit and receive signals according to a radio access technology, for the purposes of using cellular communication services. This radio access technologies are NR and LTE for the purposes of this discussion.

The wireless device50also includes one or more processing circuits52that are operatively associated with the radio transceiver circuitry56. The processing circuitry52comprises one or more digital processing circuits, e.g., one or more microprocessors, microcontrollers, DSPs, FPGAs, CPLDs, ASICs, or any mix thereof. More generally, the processing circuitry52may comprise fixed circuitry, or programmable circuitry that is specially adapted via the execution of program instructions implementing the functionality taught herein, or may comprise some mix of fixed and programmed circuitry. The processing circuitry52may be multi-core.

The processing circuitry52also includes a memory64. The memory64, in some embodiments, stores one or more computer programs66and, optionally, configuration data68. The memory64provides non-transitory storage for the computer program66and it may comprise one or more types of computer-readable media, such as disk storage, solid-state memory storage, or any mix thereof. By way of non-limiting example, the memory64comprises any one or more of SRAM, DRAM, EEPROM, and FLASH memory, which may be in the processing circuitry52and/or separate from processing circuitry52. The memory64may also store any configuration data68used by the wireless device50. The processing circuitry52may be configured, e.g., through the use of appropriate program code stored in memory64, to carry out one or more of the methods and/or signaling processes detailed hereinafter.

The processing circuitry52of the wireless device50is configured, according to some embodiments, to selectively operate in one of two or more previously configured BWPs, where each BWP being a different subset of an available bandwidth for uplink and/or downlink operation. The processing circuitry52is configured to switch from an active RRC state to an inactive RRC state, and after said switching, retain a physical layer configuration corresponding to the BWP active just prior to said switching.

According to some embodiments, the processing circuitry52is configured to perform a corresponding method800for the wireless device50, shown inFIG.8. For example, the method800includes switching from an active RRC state to an inactive RRC state (block802), and after said switching, retaining a physical layer configuration corresponding to the BWP active just prior to said switching (block804).

The physical layer configuration may be a dedicated physical layer configuration corresponding uniquely to the BWP active just prior to said switching, among the two or more previously configured BWPs. The retaining may include retaining a dedicated physical layer configuration for each of two or more of the previously configured BWPs, including the BWP active just prior to said switching.

In some embodiments, the physical layer configuration is a common physical layer configuration corresponding to two or more of the previously configured BWPs, including the BWP active just prior to said switching.

The method800may include, upon subsequently returning to the active RRC state, using the physical layer configuration corresponding to the BWP active just prior to said switching. The method800may also include, while in the inactive RRC state, after said switching, monitoring for system information and/or paging, using the physical layer configuration corresponding to the BWP active just prior to said switching. The method800may then include, while in the inactive RRC state, using the physical layer configuration corresponding to the BWP active just prior to said switching for making a random access attempt. The method800may further include, upon failure of the random access attempt, discarding the retained physical layer configuration corresponding to the BWP active just prior to said switching and reverting to an initial BWP for a subsequent random access attempt.

In some embodiments, any of the using of the physical layer configuration corresponding to the BWP active just prior to said switching is conditioned upon not receiving, while in the inactive state, system information (SI) indicating a change in the dedicated physical layer configuration for the BWP active just prior to said switching.

In some cases, the retaining may be responsive to receiving, from a wireless network node, an indication to keep the physical layer configuration corresponding to the BWP. The wireless device may change cells from a source cell to a target cell, while in the inactive RRC state, and wherein the indication is received from a network node operating the target cell. In other cases, the wireless device may change cells from a source cell to a target cell, while in the inactive RRC state, and wherein the indication is received from a network node operating the source cell. The indication may be received in a RRC suspend message.

The physical layer configuration corresponding to the BWP active just prior to said switching may include parameters relating to any one or more of the following: channel-state information (CSI) reporting; interference measurement reporting; and sounding reference signal (SRS) configuration.

FIG.9, according to some embodiments, illustrates a communication system that includes a telecommunication network910, such as a 3GPP-type cellular network, which comprises an access network911, such as a radio access network, and a core network914. The access network911comprises a plurality of base stations912a,912b,912c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area913a,913b,913c. Each base station912a,912b,912cis connectable to the core network914over a wired or wireless connection915. A first UE991located in coverage area913cis configured to wirelessly connect to, or be paged by, the corresponding base station912c. A second UE992in coverage area913ais wirelessly connectable to the corresponding base station912a. While a plurality of UEs991,992are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station912.

The telecommunication network910is itself connected to a host computer930, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. The host computer930may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. The connections921,922between the telecommunication network910and the host computer930may extend directly from the core network914to the host computer930or may go via an optional intermediate network920. The intermediate network920may be one of, or a combination of more than one of, a public, private or hosted network; the intermediate network920, if any, may be a backbone network or the Internet; in particular, the intermediate network920may comprise two or more sub-networks (not shown).

The communication system ofFIG.9as a whole enables connectivity between one of the connected UEs991,992and the host computer930. The connectivity may be described as an over-the-top (OTT) connection950. The host computer930and the connected UEs991,992are configured to communicate data and/or signaling via the OTT connection950, using the access network911, the core network914, any intermediate network920and possible further infrastructure (not shown) as intermediaries. The OTT connection950may be transparent in the sense that the participating communication devices through which the OTT connection950passes are unaware of routing of uplink and downlink communications. For example, a base station912may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer930to be forwarded (e.g., handed over) to a connected UE991. Similarly, the base station912need not be aware of the future routing of an outgoing uplink communication originating from the UE991towards the host computer930.

Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference toFIG.10. In a communication system1000, a host computer1010comprises hardware1015including a communication interface1016configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system1000. The host computer1010further comprises processing circuitry1018, which may have storage and/or processing capabilities. In particular, the processing circuitry1018may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. The host computer1010further comprises software1011, which is stored in or accessible by the host computer1010and executable by the processing circuitry1018. The software1011includes a host application1012. The host application1012may be operable to provide a service to a remote user, such as a UE1030connecting via an OTT connection1050terminating at the UE1030and the host computer1010. In providing the service to the remote user, the host application1012may provide user data which is transmitted using the OTT connection1050.

The communication system1000further includes a base station1020provided in a telecommunication system and comprising hardware1025enabling it to communicate with the host computer1010and with the UE1030. The hardware1025may include a communication interface1026for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system1000, as well as a radio interface1027for setting up and maintaining at least a wireless connection1070with a UE1030located in a coverage area (not shown inFIG.10) served by the base station1020. The communication interface1026may be configured to facilitate a connection1060to the host computer1010. The connection1060may be direct or it may pass through a core network (not shown inFIG.10) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, the hardware1025of the base station1020further includes processing circuitry1028, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. The base station1020further has software1021stored internally or accessible via an external connection.

The communication system1000further includes the UE1030already referred to. Its hardware1035may include a radio interface1037configured to set up and maintain a wireless connection1070with a base station serving a coverage area in which the UE1030is currently located. The hardware1035of the UE1030further includes processing circuitry1038, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. The UE1030further comprises software1031, which is stored in or accessible by the UE1030and executable by the processing circuitry1038. The software1031includes a client application1032. The client application1032may be operable to provide a service to a human or non-human user via the UE1030, with the support of the host computer1010. In the host computer1010, an executing host application1012may communicate with the executing client application1032via the OTT connection1050terminating at the UE1030and the host computer1010. In providing the service to the user, the client application1032may receive request data from the host application1012and provide user data in response to the request data. The OTT connection1050may transfer both the request data and the user data. The client application1032may interact with the user to generate the user data that it provides.

It is noted that the host computer1010, base station1020and UE1030illustrated inFIG.10may be identical to the host computer930, one of the base stations912a,912b,912cand one of the UEs991,992ofFIG.9, respectively. This is to say, the inner workings of these entities may be as shown inFIG.10and independently, the surrounding network topology may be that ofFIG.9.

InFIG.10, the OTT connection1050has been drawn abstractly to illustrate the communication between the host computer1010and the use equipment1030via the base station1020, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from the UE1330or from the service provider operating the host computer1010, or both. While the OTT connection1050is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

The wireless connection1070between the UE1030and the base station1020is in accordance with the teachings of the embodiments described throughout this disclosure, such as provided by nodes such as wireless device50and network node30, along with the corresponding methods600and800. A problem is that each time the UE enters either Idle or Inactive state, the UE discards the dedicated BWP configurations. This means all BWP configurations sent via the RRC signaling to the UE will be discarded. The advantage of the embodiments is that the dedicated BWP configuration signaling may be avoided each time the UE re-enters Connected mode. This improves the UE transition time and the data rate, capacity, latency and/or power consumption for the network and UE1030using the OTT connection1050and thereby provide benefits such as reduced user waiting time, more capacity, better responsiveness, and better device battery time.

A measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection1050between the host computer1010and UE1030, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection1050may be implemented in the software1011of the host computer1010or in the software1031of the UE1030, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection1050passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software1011,1031may compute or estimate the monitored quantities. The reconfiguring of the OTT connection1050may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the base station1020, and it may be unknown or imperceptible to the base station1020. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating the host computer's1010measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that the software1011,1031causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection1050while it monitors propagation times, errors etc.

FIG.13is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference toFIGS.9and10. For simplicity of the present disclosure, only drawing references toFIG.13will be included in this section. In an optional first step1310of the method, the UE receives input data provided by the host computer. Additionally, or alternatively, in an optional second step1320, the UE provides user data. In an optional substep1321of the second step1320, the UE provides the user data by executing a client application. In a further optional substep1311of the first step1310, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in an optional third substep1330, transmission of the user data to the host computer. In a fourth step1340of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

According to some embodiments, a communication system including a host computer comprises processing circuitry configured to provide user data and a communication interface configured to forward the user data to a cellular network for transmission to a UE configured to selectively operate in one of two or more previously configured BWPs, each BWP being a different subset of an available bandwidth for uplink and/or downlink operation. The cellular network comprises a base station configured to serve the UE and configured to send, to at least one wireless device, an indication to retain, upon switching from an active RRC state to an inactive RRC state, a physical layer configuration corresponding to a BWP in use by the wireless device just prior to said switching. The communication system may comprise the base station and/or the UE, where the UE is configured to communicate with the base station. The processing circuitry of the host computer may be configured to execute a host application, thereby providing the user data, and the UE may comprise processing circuitry configured to execute a client application associated with the host application.

According to some embodiments, a method implemented in a communication system including a host computer, a base station and a UE configured to selectively operate in one of two or more previously configured BWPs, each BWP being a different subset of an available bandwidth for uplink and/or downlink operation, comprises, at the host computer, providing user data and initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, configured to serve the UE, where the method at the base station comprises sending, to at least one wireless device, an indication to retain, upon switching from an active RRC state to an inactive RRC state, a physical layer configuration corresponding to a BWP in use by the wireless device just prior to said switching. The method may comprise, at the base station, transmitting the user data. The user data may be provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application.

According to some embodiments, a communication system including a host computer comprises processing circuitry configured to provide user data and a communication interface configured to forward user data to a cellular network for transmission to a UE configured to selectively operate in one of two or more previously configured BWPs, each BWP being a different subset of an available bandwidth for uplink and/or downlink operation, where the UE comprises a radio interface and processing circuitry configured to switch from an active RRC state to an inactive RRC state, and after said switching, retain a physical layer configuration corresponding to the BWP active just prior to said switching. The communication system may further include the UE, and the cellular network may further include a base station configured to communicate with the UE. The processing circuitry of the host computer may be configured to execute a host application, thereby providing the user data, and the UE's processing circuitry may be configured to execute a client application associated with the host application.

According to some embodiments, a method implemented in a communication system including a host computer, a base station and a UE configured to selectively operate in one of two or more previously configured BWPs, each BWP being a different subset of an available bandwidth for uplink and/or downlink operation, comprises, at the host computer, providing user data and initiating a transmission carrying the user data to the UE via a cellular network comprising the base station. The method comprises, at the UE, switching from an active RRC state to an inactive RRC state and after said switching, retaining a physical layer configuration corresponding to the BWP active just prior to said switching. The method may further comprise, at the UE, receiving the user data from the base station.

According to some embodiments, a communication system including a host computer comprises a communication interface configured to receive user data originating from a transmission from a UE to a base station, the UE configured to selectively operate in one of two or more previously configured BWPs, each BWP being a different subset of an available bandwidth for uplink and/or downlink operation. The UE's processing circuitry is configured to switch from an active RRC state to an inactive RRC state and after said switching, retain a physical layer configuration corresponding to the BWP active just prior to said switching. The communication system may further include the UE. The communication system may further include the base station, where the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station. The processing circuitry of the host computer may be configured to execute a host application; and the UE's processing circuitry may be configured to execute a client application associated with the host application, thereby providing the user data. The processing circuitry of the host computer may be configured to execute a host application, thereby providing request data, and the UE's processing circuitry may be configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.

According to some embodiments, a method implemented in a UE configured to selectively operate in one of two or more previously configured BWPs, each BWP being a different subset of an available bandwidth for uplink and/or downlink operation, comprises switching from an active RRC state to an inactive RRC state, and after said switching, retaining a physical layer configuration corresponding to the BWP active just prior to said switching. The method may further comprise providing user data and forwarding the user data to a host computer via the transmission to the base station.

According to some embodiments, a method implemented in a communication system including a host computer, a base station and a UE configured to selectively operate in one of two or more previously configured BWPs, each BWP being a different subset of an available bandwidth for uplink and/or downlink operation, comprises, at the host computer, receiving user data transmitted to the base station from the UE. The method comprises, at the UE, switching from an active RRC state to an inactive RRC state and after said switching, retaining a physical layer configuration corresponding to the BWP active just prior to said switching. The method may further comprise, at the UE, providing the user data to the base station. The method may further comprise, at the UE, executing a client application, thereby providing the user data to be transmitted, and at the host computer, executing a host application associated with the client application. The method may further comprise, at the UE, executing a client application, and at the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application. The user data to be transmitted is provided by the client application in response to the input data.

According to some embodiments, a communication system includes a host computer comprising a communication interface configured to receive user data originating from a transmission from a UE to a base station, the UE configured to selectively operate in one of two or more previously configured BWPs, each BWP being a different subset of an available bandwidth for uplink and/or downlink operation. The base station comprises a radio interface and processing circuitry configured to send, to at least one wireless device, an indication to retain, upon switching from an active RRC state to an inactive RRC state, a physical layer configuration corresponding to a BWP in use by the wireless device just prior to said switching. The communication system may further include the base station. The communication system may further include the UE, where the UE is configured to communicate with the base station. The processing circuitry of the host computer may be configured to execute a host application. The UE may be configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.

According to some embodiments, a method implemented in a communication system including a host computer, a base station and a UE configured to selectively operate in one of two or more previously configured BWPs, each BWP being a different subset of an available bandwidth for uplink and/or downlink operation, comprises, at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE. The method at the UE comprises switching from an active RRC state to an inactive RRC state and after said switching, retaining a physical layer configuration corresponding to the BWP active just prior to said switching. The method may further comprise, at the base station, receiving the user data from the UE. The method may further comprise, at the base station, initiating a transmission of the received user data to the host computer.

As discussed in detail above, the techniques described herein, e.g., as illustrated in the process flow diagrams ofFIGS.6and8, may be implemented, in whole or in part, using computer program instructions executed by one or more processors. It will be appreciated that a functional implementation of these techniques may be represented in terms of functional modules, where each functional module corresponds to a functional unit of software executing in an appropriate processor or to a functional digital hardware circuit, or some combination of both.

FIG.15illustrates an example functional module or circuit architecture as may be implemented in the network node30. The functional implementation includes a sending module1502for sending, to at least one wireless device, an indication to retain, upon switching from an active RRC state to an inactive RRC state, a physical layer configuration corresponding to a BWP in use by the wireless device just prior to said switching.

FIG.16illustrates an example functional module or circuit architecture as may be implemented in the wireless device50. The implementation includes a switching module1602for switching from an active RRC state to an inactive RRC state. The implementation also includes a retaining module1604for, after said switching, retaining a physical layer configuration corresponding to the BWP active just prior to said switching.

Many variations and modifications can be made to the embodiments without substantially departing from the principles of the present inventive concepts. All such variations and modifications are intended to be included herein within the scope of present inventive concepts. Accordingly, the above disclosed subject matter is to be considered illustrative, and not restrictive, and the examples of embodiments are intended to cover all such modifications, enhancements, and other embodiments, which fall within the spirit and scope of present inventive concepts. Thus, to the maximum extent allowed by law, the scope of present inventive concepts is to be determined by the broadest permissible interpretation of the present disclosure including the examples of embodiments and their equivalents, and shall not be restricted or limited by the foregoing detailed description.