Patent ID: 12256455

DETAILED DESCRIPTION

Traditional techniques for re-establishing a connection between a UE and a network node have disadvantages that result in latency and/or disrupted communications. As an example, if a UE is initially connected to a first (source) base station that is NR capable, SRB1 may be configured to operate using NR PDCP. Thereafter, problems may arise if the UE is suspended from the network and re-establishes a connection to the network via a second (target) base station that does not support NR (for example, a legacy LTE base station). To illustrate these problems, Table 1, (below) illustrates different scenarios to consider with respect to a PDCP configuration used for SRB1 in the first and second base stations.

TABLE 1Different cases of PDCP version usagefor SRB1 and support of NR PDCPLegacy FirstNR First BaseBase StationLegacy FirstStationNR First BaseLegacyBase StationLegacyStationSecond BaseNR SecondSecond BaseNR Second BaseStationBase StationStationStationSRB1Successful Re-establishmentusesLTEPDCPSRB1Not applicableFailed Re-UE unable tousesestablishmentknow if theNRsecond basePDCPstation supportsNR PDCP

In the instances shown above where the first base station is a legacy base station that does not support NR, SRB1 is configured to use LTE PDCP (and not NR PDCP). Accordingly, because an NR base station is generally backwards compatible with LTE PDCP, the RRC connection re-establishment procedures are able to be successfully completed in a transition of the UE from its connection with the first base station to a connection with the second base station regardless of whether the second base station is a legacy or NR base station. Similarly, if the first base station supports NR, but configures SRB1 to use LTE PDCP, the UE will be able to continue using the LTE PDCP configuration of SRB1 when it switches to a second base station, regardless of whether the second base station is a legacy or NR capable base station.

However, if the first base station is NR capable and configures SRB1 to use NR PDCP, problem occur when transitioning the UE to the second base station. For example, if the second base station is a legacy base station, the UE will be unable to re-establish RRC communications via the SRB1 that is configured with NR PDCP, because the legacy base station is not configured to operate using that protocol. For example, the second base station is unable to even process an RRCConnectionReestablishmentComplete message.

If both the first and the second base station are NR base stations, the UE can re-establish SRB1 with NR PDCP with the second base station. Under traditional signalling standards, however, the UE will not be informed regarding whether the second base station supports NR PDCP.

The present disclosure provides techniques that address PDCP configuration issues during connection re-establishment, like those illustrated above. In some embodiments, upon the reception of the RRCConnectionReestablishment message from a base station, a UE may perform the following steps:1) re-establish PDCP for SRB1;2) re-establish RLC for SRB1;3) perform the radio resource configuration procedure in accordance with the received radioResourceConfigDedicated;4) resume SRB1;5) update the KeNB key based on the KASME key (master security key for current UE connection/session; used to derive other keys) to which the current KeNB is associated, using the nextHopChainingCount value indicated in the RRCConnectionReestablishment message;6) derive the KRRCint key (security key for integrity protecting RRC messages) associated with the previously configured integrity algorithm;7) derive the KRRCenc key (security key for encrypting/decrypting RRC messages) and the KUPenc key (security key for encrypting/decrypting user plane messages) associated with the previously configured ciphering algorithm;8) configure lower layers to activate integrity protection using the previously configured algorithm and the KRRCint key immediately, i.e., integrity protection shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;9) configure lower layers to apply ciphering using the previously configured algorithm, the KRRCenc key and the KUPenc key immediately, i.e., ciphering shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure; and10) Construct and submit the RRCConnectionReestablishmentComplete message to lower layers for transmission.

When the target base station receives the RRCConnectionReestablishmentComplete message, it sends an RRCConnectionReconfiguration that will reconfigure SRB2 and the data radio bearers (DRBs).

The following example techniques may be performed relating to the re-establishing of PDCP for SRB1 (shown in step 1, above), in combination with one or more of the above steps to therefore handle a mismatch between use of NR PDCP and LTE PDCP for SRB1 at a first base station and second base station. These embodiments are not mutually exclusive, and may be combined and/or modified as appropriate. Moreover, while the techniques are described with respect to first and second base station, similar problems may occur with respect to a re-connection to a same base station (i.e., the source and target base stations are the same).

Embodiment 1 (UE): On re-establishment of a connection to the network via the target base station, the UE reverts (by default) to LTE PDCP configuration for SRB1. This technique addresses use cases where the source base station supports NR, and where SRB1 was previously configured with an NR PDCP configuration.

Embodiment 2 (network node): The source base station passes a modified UE AS context to the target base station, so that the UE context is understandable by the legacy target base station, i.e. not include the NR PDCP configuration for SRB1 or any other radio bearer that uses NR PDCP. This technique addresses use cases where the source base station supports NR, and where SRB1 was previously configured with an NR PDCP configuration.

Embodiment 2b (network node): An embodiment according to embodiment 2, the source base station passes on a modified UE AS context to the target only if it determines that the target is a legacy base station that doesn't support NR. A drawback is that in case the target is able to support NR PDCP, SRB1 will end up using LTE PDCP.

Embodiment 3 (UE): On re-establishment, the UE will use the PDCP version of the SRB1, be it LTE or NR, that was used before re-establishment. In case the target is able to support NR PDCP, SRB1 will be resumed with NR PDCP.

Embodiment 4 (network node): The source base station, on determining that the target base station is a legacy base station that doesn't support NR, will refrain from passing the UE AS context information to the target.

Embodiment 5 (network node): If the target base station doesn't get a UE AS context from the source base station or it doesn't understand the context passed from the source base station, (e.g. due to the usage of NR PDCP configuration for SRB1 or any other radio bearer), it will initiate NAS recovery (i.e. the target base station to send an RRCConnectionSetup message to the UE, this will trigger the UE to send a NAS message (e.g., NAS service request, NAS tracking area update), when the CN receives the NAS message it will create a new UE S1 context in the target base station, allowing the target base station perform a full reconfiguration of all the bearers by utilizing the S1 context of the UE).

Embodiment 6 (network node): The UE is configured via the RRCConnectionReestablishment message, either implicitly or explicitly, to use either LTE or NR PDCP for SRB1. A flag is included in the RRCConnectionReestablishment message telling the UE which PDCP version to use for SRB1. A legacy base station will use legacy RRCConnectionReestablishment message (i.e. there will be no flag indicating which PDCP version to use).

Embodiment 7 (UE): If the UE receives an RRCConnectionReestablishment message with no PDCP version flag (i.e. the target base station doesn't support NR PDCP and it will use legacy RRCConnectionReestablishment message), or the flag indicates LTE PDCP (i.e. target base station supports NR PDCP, but for some reason doesn't want to configure NR PDCP for SRB1), the UE will resort to using LTE PDCP for SRB1.

Embodiment 8 (UE): If the UE receives an RRCConnectionReestablishment message with a flag indicating NR PDCP version for SRB1, the UE will re-establish SRB1 with NR PDCP. If SRB1 was configured with NR PDCP before re-establishment was initiated, the UE will just reuse/restore that PDCP configuration.

Embodiment 9 (network node): An embodiment according to embodiment 6, where the target base station also provides the NR PDCP configuration in addition to or instead of the PDCP version flag in the RRCConnectionReestablishment message.

Embodiment 10 (UE): An embodiment according to embodiment 9, where the UE receives an RRCConnectionReestablishment message that contains an NR PDCP configuration for SRB1, it will re-establish the SRB1 with NR PDCP, using the included NR PDCP configuration.

Embodiment 11 (network node): An embodiment according to earlier embodiments, where the target base station also provides the NR PDCP configuration (or/and indication) for SRB2 and/or data radio bearers (DRBs) in the RRCConnectionReestablishment message. The NR PDCP configuration could be an explicit flag indicating that NR PDCP should be used and/or a detailed configuration of the NR PDCP protocol, for the concerned bearers (i.e. SRB2 or DRBs).

Embodiment 12 (UE): An embodiment according to any of the previous embodiments, where the UE receives an RRCConnectionReestablishment message that contains an NR PDCP configuration for SRB1, it will re-establish the SRB1 as well as optionally SRB2 and data radio bearers (DRBs) with NR PDCP, using the included NR PDCP configuration. The NR PDCP configuration could be an explicit flag indicating that NR PDCP should be used and/or a detailed configuration of the NR PDCP protocol.

Embodiment 13 (UE): If the UE is changing the PDCP version from NR to LTE due to any of the previous embodiments, it also optionally performs a mapping from NR security algorithms for encryption and integrity protection to pre-defined LTE algorithms. Similar mapping can also be performed when changing from LTE PDCP to NR PDCP (mapping from LTE algorithm to NR algorithm). The mappings could be 1-to-1 for NR and LTE algorithms, which have similar properties. For new NR-only algorithms it is possible to map to a predefined (or default) LTE algorithm. The predefined (or default) LTE algorithm could either be signalled to the UE (e.g. when connected to NR, using NAS or RRC signalling) or it could be “hardcoded” in 3GPP specifications.

Embodiment 14 (network node): If the UE is changing the PDCP version from NR to LTE due to any of the previous embodiments, the network (e.g. the target or source base station) can optionally perform a mapping from NR security algorithms for encryption and integrity protection to pre-defined LTE algorithms Similar mapping can also be performed when changing from LTE PDCP to NR PDCP (mapping from LTE algorithm to NR algorithm). The mappings could be 1-to-1 for NR and LTE algorithms which have similar properties. For new NR-only algorithms it is possible to map to a predefined (or default) LTE algorithm. The predefined (or default) LTE algorithm could either be configured in the network and signalled to the UE (e.g. when connected to NR, using NAS or RRC signalling) or it could be “hardcoded” in 3gpp specifications.

Certain embodiments may provide one or more of the following technical advantages. According to certain embodiments described herein, a connection can be re-established with an NR PDCP configuration of SRB1 if the target base station supports NR PDCP. Without these embodiments, it is not possible to employ NR PDCP for SRB1 at re-establishment. Certain embodiments may provide all, some, or none of these technical advantages, and additional technical advantages may be readily apparent from the description below.

FIG.1Ais a flow diagram illustrating a method performed by a user equipment for re-establishing a connection to a RAN, according to some examples. In some example, the user equipment is a wireless device. This method may be performed in combination with a method performed by a network node, such as the method described with respect toFIG.1B. Moreover, this method may be implemented by a user equipment apparatus or in a system including a user equipment, as described with respect toFIGS.2-6.

At step102, the user equipment establishes a connection to a RAN via a network node, where the connection provides communications between the UE and the network node using a Signaling Radio Bearer (SRB) configured with a New Radio (NR) Packet Data Convergence Protocol (PDCP) configuration. In some examples, the SRB includes Signaling Radio Bearer 1 (SRB1). Subsequently, the user equipment's connection may be suspended, such that the user equipment is disconnected from the network.

At step104, the user equipment receives an RRC connection re-establishment message from a network node. In some examples, the UE also receives receiving a pre-defined LTE algorithm and/or NR integrity protection algorithm from the network node.

At step106, the user equipment re-establishes the connection to the RAN, where the re-establishing includes applying a Long-Term Evolution (LTE) PDCP configuration to the SRB. In some examples, the UE also maps a received NR encryption algorithm and/or an NR integrity protection algorithm to a pre-defined LTE algorithm. Accordingly, the UE is able to receive messages from the network node on the SRB and decode the messages using the LTE PDCP configuration and security configuration (such as the mapped pre-defined LTE algorithm) of the SRB. These messages may include, for example, an RRCReestablishment command that is received at the UE from the network node, which the UE decodes using the LTE PDCP and security configurations.

In the above example, a same network node interacts with the UE in steps102,104, and106. However, in other examples, the method may be performed by the UE interacting with multiple network nodes. In this multi-node variation of the above example, the UE establishes a connection via a first network node in step102. In step104, after the connection with the first network node is suspended, the UE receives the connection re-establishment message from a second network node that is different than the first network node. In step106, the UE re-establishes the connection to the RAN via the second network node.

Following the re-establishment of the UE's connection to the RAN, the UE may send messages to the network node (or a second network node) using the LTE PDCP configuration on the SRB.

FIG.1Bis a flow diagram illustrating a method performed by a network node for re-establishing a UE's connection to a RAN, according to some examples. In some examples, the network node is a base station, such as an eNB or a gNB. This method may be performed in combination with a method performed by a user equipment, such as the method described with respect toFIG.1A. Moreover, this method may be implemented by a network node apparatus or in a system including a network node, as described with respect toFIGS.2-6.

At step103, the network node in a RAN provides an RRC connection re-establishment message to a UE that was previously connected to the RAN via a Signaling Radio Bearer (SRB) configured with a New Radio (NR) Packet Data Convergence Protocol (PDCP) configuration. In some examples, step103is performed after step102is performed by a user equipment. In some examples, the UE was previously connected to the RAN via the network node, while in other examples, the UE was previously connected to the RAN via a second network node that is different than the network node.

At step105, the network node re-establishes the UE's connection to the RAN, where the re-establishing includes applying a Long-Term Evolution (LTE) PDCP configuration of the SRB. In some examples, step105is performed after step104is performed by a user equipment.

In the examples where the UE was previously connected to the RAN via a second network node, the second network node may determine that the network node does not support the NR PDCP configuration. Accordingly, the network node may receive, from the second network node, a modified Access Stratum (AS) context corresponding to the UE, where the modified AS context includes an indication to change from the NR PDCP configuration to the LTE PDCP configuration.

FIG.1Cis a signaling diagram illustrating a method performed by a user equipment and one or more network nodes. In some examples, the network node(s) include one or more base stations, such as eNBs and/or gNBs. The sequence illustrated in the signaling diagram may be implemented by a user equipment, network node, and/or in a system including a user equipment and network node, as described with respect toFIGS.2-6.

At step108, a UE and a network node establish a connection to a network (such as a RAN network) to provide communications using an SRB configured with an NR PDCP configuration.

At step110, the UE's connection to the network is suspended. At step112, the network node or a second network node provides an RRC connection re-establishment message to the UE.

At step114, the UE applies an LTE PDCP configuration to the SRB. In the present example, the LTE PDCP configuration is a default configuration that the UE applies when interacting with a network node during an RRC connection re-establishment procedure. Accordingly, at step116a connection is established from the UE to the network using the LTE PDCP configuration for the SRB.

In some examples, at step118the network node provides a pre-defined LTE algorithm to the UE, which the UE may use for network communications. In this example, at step120the UE maps an NR encryption algorithm and/or integrity protection algorithm to the received pre-defined LTE algorithm. In some examples, the UE is pre-configured with the NR encryption algorithm and/or integrity protection algorithm. Accordingly, the UE can use the pre-defined LTE algorithm and LTE PDCP configuration of the SRB to decode messages that are received on the SRB from the network node.

In the event that the UE's connection with the network is through a second network node, at step122, the network node may determine that the second network does not support an NR PDCP configuration. Accordingly, if the second network node does not support the NR PDCP configuration, at step124the network node provides the second node with a modified access stratum (AS) context that indicates to change from an NR PDCP configuration to the LTE PDCP configuration. Accordingly, the second network node is notified to change to an NR PDCP configuration so that it may communicate with the UE. Steps122and124may be skipped if the connection to the network is re-established in step116via the network node rather than a second network node.

At step126, the UE sends a message to the RAN network, via the network node or the second network node, using the LTE PDCP configuration on the SRB.

FIG.2is a block diagram illustrating a wireless network, according to some examples. Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated inFIG.2. For simplicity, the wireless network ofFIG.2depicts network206, network nodes260and260b,and wireless devices210,210b,and210c.In practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node260and wireless device210are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices' access to and/or use of the services provided by, or via, the wireless network.

The wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system. In some embodiments, the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.

Network206may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

Network node260and wireless device210comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.

As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, next generation Node B's (gNBs), and evolved Node Bs (eNBs)). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Yet further examples of network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. As another example, a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.

InFIG.2, network node260includes processing circuitry270, device readable medium280, interface290, auxiliary equipment284, power source286, power circuitry287, and antenna262. Although network node260illustrated in the example wireless network ofFIG.2may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, while the components of network node260are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium280may comprise multiple separate hard drives as well as multiple RAM modules).

Similarly, network node260may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which network node260comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeB's. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, network node260may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium280for the different RATs) and some components may be reused (e.g., the same antenna262may be shared by the RATs). Network node260may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node260, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node260.

Processing circuitry270is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry270may include processing information obtained by processing circuitry270by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Processing circuitry270may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node260components, such as device readable medium280, network node260functionality. For example, processing circuitry270may execute instructions stored in device readable medium280or in memory within processing circuitry270. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry270may include a system on a chip (SOC).

In some embodiments, processing circuitry270may include one or more of radio frequency (RF) transceiver circuitry272and baseband processing circuitry274. In some embodiments, radio frequency (RF) transceiver circuitry272and baseband processing circuitry274may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry272and baseband processing circuitry274may be on the same chip or set of chips, boards, or units.

In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB, gNB, or other such network device may be performed by processing circuitry270executing instructions stored on device readable medium280or memory within processing circuitry270. In alternative embodiments, some or all of the functionality may be provided by processing circuitry270without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry270can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry270alone or to other components of network node260, but are enjoyed by network node260as a whole, and/or by end users and the wireless network generally.

Device readable medium280may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry270. Device readable medium280may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry270and, utilized by network node260. Device readable medium280may be used to store any calculations made by processing circuitry270and/or any data received via interface290. In some embodiments, processing circuitry270and device readable medium280may be considered to be integrated.

Interface290is used in the wired or wireless communication of signaling and/or data between network node260, network206, and/or wireless devices210,210b,210c. As illustrated, interface290comprises port(s)/terminal(s)294to send and receive data, for example to and from network206over a wired connection. Interface290also includes radio front end circuitry292that may be coupled to, or in certain embodiments a part of, antenna262. Radio front end circuitry292comprises filters298and amplifiers296. Radio front end circuitry292may be connected to antenna262and processing circuitry270. Radio front end circuitry may be configured to condition signals communicated between antenna262and processing circuitry270. Radio front end circuitry292may receive digital data that is to be sent out to other network nodes or wireless devices via a wireless connection. Radio front end circuitry292may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters298and/or amplifiers296. The radio signal may then be transmitted via antenna262. Similarly, when receiving data, antenna262may collect radio signals which are then converted into digital data by radio front end circuitry292. The digital data may be passed to processing circuitry270. In other embodiments, the interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, network node260may not include separate radio front end circuitry292, instead, processing circuitry270may comprise radio front end circuitry and may be connected to antenna262without separate radio front end circuitry292. Similarly, in some embodiments, all or some of RF transceiver circuitry272may be considered a part of interface290. In still other embodiments, interface290may include one or more ports or terminals294, radio front end circuitry292, and RF transceiver circuitry272, as part of a radio unit (not shown), and interface290may communicate with baseband processing circuitry274, which is part of a digital unit (not shown).

Antenna262may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna262may be coupled to radio front end circuitry292and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna262may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna262may be separate from network node260and may be connectable to network node260through an interface or port.

Antenna262, interface290, and/or processing circuitry270may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna262, interface290, and/or processing circuitry270may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.

Power circuitry287may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node260with power for performing the functionality described herein. Power circuitry287may receive power from power source286. Power source286and/or power circuitry287may be configured to provide power to the various components of network node260in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source286may either be included in, or external to, power circuitry287and/or network node260. For example, network node260may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry287. As a further example, power source286may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry287. The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used.

Alternative embodiments of network node260may include additional components beyond those shown inFIG.2that may be responsible for providing certain aspects of the network node's functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, network node260may include user interface equipment to allow input of information into network node260and to allow output of information from network node260. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node260.

As used herein, wireless device refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. In some examples, a UE is implemented as a wireless device. Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. In some embodiments, a wireless device may be configured to transmit and/or receive information without direct human interaction. For instance, a wireless device may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a wireless device include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE), a vehicle-mounted wireless terminal device, etc. A wireless device may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, and may in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (IoT) scenario, a wireless device may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another wireless device and/or a network node. The wireless device may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as a machine-type communication (MTC) device. As one particular example, the wireless device may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a wireless device may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A wireless device as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a wireless device as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

As illustrated, wireless device210includes antenna211, interface214, processing circuitry220, device readable medium230, user interface equipment232, auxiliary equipment234, power source236and power circuitry237. Wireless device210may include multiple sets of one or more of the illustrated components for different wireless technologies supported by wireless device210, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within wireless device210.

Antenna211may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface214. In certain alternative embodiments, antenna211may be separate from wireless device210and be connectable to wireless device210through an interface or port. Antenna211, interface214, and/or processing circuitry220may be configured to perform any receiving or transmitting operations described herein as being performed by a wireless device. Any information, data and/or signals may be received from a network node and/or another wireless device. In some embodiments, radio front end circuitry212and/or antenna211may be considered an interface.

As illustrated, interface214comprises radio front end circuitry212and antenna211. Radio front end circuitry212comprise one or more filters218and amplifiers216. Radio front end circuitry212is connected to antenna211and processing circuitry220, and is configured to condition signals communicated between antenna211and processing circuitry220. Radio front end circuitry212may be coupled to or a part of antenna211. In some embodiments, wireless device210may not include separate radio front end circuitry212; rather, processing circuitry220may comprise radio front end circuitry and may be connected to antenna211. Similarly, in some embodiments, some or all of RF transceiver circuitry222may be considered a part of interface214. Radio front end circuitry212may receive digital data that is to be sent out to other network nodes or wireless devices via a wireless connection. Radio front end circuitry212may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters218and/or amplifiers216. The radio signal may then be transmitted via antenna211. Similarly, when receiving data, antenna211may collect radio signals which are then converted into digital data by radio front end circuitry212. The digital data may be passed to processing circuitry220. In other embodiments, the interface may comprise different components and/or different combinations of components.

Processing circuitry220may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other wireless device210components, such as device readable medium230, wireless device210functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry220may execute instructions stored in device readable medium230or in memory within processing circuitry220to provide the functionality disclosed herein.

As illustrated, processing circuitry220includes one or more of RF transceiver circuitry222, baseband processing circuitry224, and application processing circuitry226. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry220of wireless device210may comprise a SOC. In some embodiments, RF transceiver circuitry222, baseband processing circuitry224, and application processing circuitry226may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry224and application processing circuitry226may be combined into one chip or set of chips, and RF transceiver circuitry222may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry222and baseband processing circuitry224may be on the same chip or set of chips, and application processing circuitry226may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry222, baseband processing circuitry224, and application processing circuitry226may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry222may be a part of interface214. RF transceiver circuitry222may condition RF signals for processing circuitry220.

In certain embodiments, some or all of the functionality described herein as being performed by a wireless device may be provided by processing circuitry220executing instructions stored on device readable medium230, which in certain embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry220without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner In any of those particular embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry220can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry220alone or to other components of wireless device210, but are enjoyed by wireless device210as a whole, and/or by end users and the wireless network generally.

Processing circuitry220may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a wireless device. These operations, as performed by processing circuitry220, may include processing information obtained by processing circuitry220by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by wireless device210, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Device readable medium230may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry220. Device readable medium230may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry220. In some embodiments, processing circuitry220and device readable medium230may be considered to be integrated.

User interface equipment232may provide components that allow for a human user to interact with wireless device210. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment232may be operable to produce output to the user and to allow the user to provide input to wireless device210. The type of interaction may vary depending on the type of user interface equipment232installed in wireless device210. For example, if wireless device210is a smart phone, the interaction may be via a touch screen; if wireless device210is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface equipment232may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment232is configured to allow input of information into wireless device210, and is connected to processing circuitry220to allow processing circuitry220to process the input information. User interface equipment232may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment232is also configured to allow output of information from wireless device210, and to allow processing circuitry220to output information from wireless device210. User interface equipment232may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment232, wireless device210may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.

Auxiliary equipment234is operable to provide more specific functionality which may not be generally performed by wireless devices. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment234may vary depending on the embodiment and/or scenario.

Power source236may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used. Wireless device210may further comprise power circuitry237for delivering power from power source236to the various parts of wireless device210which need power from power source236to carry out any functionality described or indicated herein. Power circuitry237may in certain embodiments comprise power management circuitry. Power circuitry237may additionally or alternatively be operable to receive power from an external power source; in which case wireless device210may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry237may also in certain embodiments be operable to deliver power from an external power source to power source236. This may be, for example, for the charging of power source236. Power circuitry237may perform any formatting, converting, or other modification to the power from power source236to make the power suitable for the respective components of wireless device210to which power is supplied.

FIG.3is a block diagram illustrating a user equipment, according to some examples. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user. A UE may also comprise any UE identified by the 3rd Generation Partnership Project (3GPP), including a NB-IoT UE that is not intended for sale to, or operation by, a human user. UE300, as illustrated inFIG.3, is one example of a wireless device configured for communication in accordance with one or more communication standards promulgated by the 3rd Generation Partnership Project (3GPP), such as 3GPP's GSM, UMTS, LTE, and/or 5G standards. Accordingly, althoughFIG.3is a UE, the components discussed herein are equally applicable to a wireless device, and vice-versa.

InFIG.3, UE300includes processing circuitry301that is operatively coupled to input/output interface305, radio frequency (RF) interface309, network connection interface311, memory315including random access memory (RAM)317, read-only memory (ROM)319, and storage medium321or the like, communication subsystem331, power source313, and/or any other component, or any combination thereof. Storage medium321includes operating system323, application program325, and data327. In other embodiments, storage medium321may include other similar types of information. Certain UEs may utilize all of the components shown inFIG.3, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

InFIG.3, processing circuitry301may be configured to process computer instructions and data. Processing circuitry301may be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry301may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

In the depicted embodiment, input/output interface305may be configured to provide a communication interface to an input device, output device, or input and output device. UE300may be configured to use an output device via input/output interface305. An output device may use the same type of interface port as an input device. For example, a USB port may be used to provide input to and output from UE300. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. UE300may be configured to use an input device via input/output interface305to allow a user to capture information into UE300. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

InFIG.3, RF interface309may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface311may be configured to provide a communication interface to network343a.Network343amay encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network343amay comprise a Wi-Fi network. Network connection interface311may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like. Network connection interface311may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.

RAM317may be configured to interface via bus302to processing circuitry301to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM319may be configured to provide computer instructions or data to processing circuitry301. For example, ROM319may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory. Storage medium321may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium321may be configured to include operating system323, application program325such as a web browser application, a widget or gadget engine or another application, and data file327. Storage medium321may store, for use by UE300, any of a variety of various operating systems or combinations of operating systems.

Storage medium321may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof. Storage medium321may allow UE300to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium321, which may comprise a device readable medium.

InFIG.3, processing circuitry301may be configured to communicate with network343busing communication subsystem331. Network343aand network343bmay be the same network or networks or different network or networks. Communication subsystem331may be configured to include one or more transceivers used to communicate with network343b.For example, communication subsystem331may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another wireless device, UE, or base station of a RAN according to one or more communication protocols, such as IEEE 802.3, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter333and/or receiver335to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter333and receiver335of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions of communication subsystem331may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. For example, communication subsystem331may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network343bmay encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network343bmay be a cellular network, a Wi-Fi network, and/or a near-field network. Power source313may be configured to provide alternating current (AC) or direct current (DC) power to components of UE300.

The features, benefits and/or functions described herein may be implemented in one of the components of UE300or partitioned across multiple components of UE300. Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem331may be configured to include any of the components described herein. Further, processing circuitry301may be configured to communicate with any of such components over bus302. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry301perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry301and communication subsystem331. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.

FIG.4is a block diagram illustrating a virtualization environment, in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).

In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments hosted by one or more of hardware nodes430. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.

The functions may be implemented by one or more applications420(which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Applications420are run in virtualization environment that provides hardware430comprising processing circuitry460and memory490. Memory490contains instructions495executable by processing circuitry460whereby application420is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

Virtualization environment comprises general-purpose or special-purpose network hardware devices430comprising a set of one or more processors or processing circuitry460, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory490which may be non-persistent memory for temporarily storing instructions495or software executed by processing circuitry460. Each hardware device may comprise one or more network interface controllers (NICs)470, also known as network interface cards, which include physical network interface480. Each hardware device may also include non-transitory, persistent, machine-readable storage media490having stored therein software495and/or instructions executable by processing circuitry460. Software495may include any type of software including software for instantiating one or more virtualization layers450(also referred to as hypervisors), software to execute virtual machines440as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

Virtual machines440, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer450or hypervisor. Different embodiments of the instance of virtual appliance420may be implemented on one or more of virtual machines440, and the implementations may be made in different ways.

During operation, processing circuitry460executes software495to instantiate the hypervisor or virtualization layer450, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer450may present a virtual operating platform that appears like networking hardware to virtual machine440.

As shown inFIG.4, hardware430may be a standalone network node with generic or specific components. Hardware430may comprise antenna4225and may implement some functions via virtualization. Alternatively, hardware430may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO)4100, which, among others, oversees lifecycle management of applications420.

Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

In the context of NFV, virtual machine440may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of virtual machines440, and that part of hardware430that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines440, forms a separate virtual network elements (VNEs).

Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines440on top of hardware networking infrastructure430and corresponds to application420inFIG.4.

In some embodiments, one or more radio units4200that each include one or more transmitters4220and one or more receivers4210may be coupled to one or more antennas4225. Radio units4200may communicate directly with hardware nodes430via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.

In some embodiments, some signaling can be effected with the use of control system4230which may alternatively be used for communication between the hardware nodes430and radio units4200.

FIG.5is a block diagram illustrating a telecommunication network connected via an intermediate network to a host computer, according to some examples. In accordance with an embodiment, a communication system includes telecommunication network510, such as a 3GPP-type cellular network, which comprises access network511, such as a radio access network, and core network514. Access network511comprises a plurality of base stations512a,512b,512c,such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area513a,513b,513c.Each base station512a,512b,512cis connectable to core network514over a wired or wireless connection515. A first UE591located in coverage area513cis configured to wirelessly connect to, or be paged by, the corresponding base station512c.A second UE592in coverage area513ais wirelessly connectable to the corresponding base station512a.While a plurality of UEs591,592are 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 station512.

Telecommunication network510is itself connected to host computer530, 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. Host computer530may 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. Connections521and522between telecommunication network510and host computer530may extend directly from core network514to host computer530or may go via an optional intermediate network520. Intermediate network520may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network520, if any, may be a backbone network or the Internet; in particular, intermediate network520may comprise two or more sub-networks (not shown).

The communication system ofFIG.5as a whole enables connectivity between the connected UEs591,592and host computer530. The connectivity may be described as an over-the-top (OTT) connection550. Host computer530and the connected UEs591,592are configured to communicate data and/or signaling via OTT connection550, using access network511, core network514, any intermediate network520and possible further infrastructure (not shown) as intermediaries. OTT connection550may be transparent in the sense that the participating communication devices through which OTT connection550passes are unaware of routing of uplink and downlink communications. For example, base station512may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer530to be forwarded (e.g., handed over) to a connected UE591. Similarly, base station512need not be aware of the future routing of an outgoing uplink communication originating from the UE591towards the host computer530.

FIG.6is a block diagram illustrating a host computer communicating via a base station with a user equipment over a partially wireless connection, according to some examples. In communication system600, host computer610comprises hardware615including communication interface616configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system600. Host computer610further comprises processing circuitry618, which may have storage and/or processing capabilities. In particular, processing circuitry618may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer610further comprises software611, which is stored in or accessible by host computer610and executable by processing circuitry618. Software611includes host application612. Host application612may be operable to provide a service to a remote user, such as UE630connecting via OTT connection650terminating at UE630and host computer610. In providing the service to the remote user, host application612may provide user data which is transmitted using OTT connection650.

Communication system600further includes base station620provided in a telecommunication system and comprising hardware625enabling it to communicate with host computer610and with UE630. Hardware625may include communication interface626for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system600, as well as radio interface627for setting up and maintaining at least wireless connection670with UE630located in a coverage area (not shown inFIG.6) served by base station620. Communication interface626may be configured to facilitate connection660to host computer610. Connection660may be direct or it may pass through a core network (not shown inFIG.6) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware625of base station620further includes processing circuitry628, 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. Base station620further has software621stored internally or accessible via an external connection.

Communication system600further includes UE630having hardware635including radio interface637that is configured to set up and maintain wireless connection670with a base station serving a coverage area in which UE630is currently located. Hardware635of UE630further includes processing circuitry638, 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. UE630further comprises software631, which is stored in or accessible by UE630and executable by processing circuitry638. Software631includes client application632. Client application632may be operable to provide a service to a human or non-human user via UE630, with the support of host computer610. In host computer610, an executing host application612may communicate with the executing client application632via OTT connection650terminating at UE630and host computer610. In providing the service to the user, client application632may receive request data from host application612and provide user data in response to the request data. OTT connection650may transfer both the request data and the user data. Client application632may interact with the user to generate the user data that it provides.

InFIG.6, OTT connection650has been drawn abstractly to illustrate the communication between host computer610and UE630via base station620, 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 UE630or from the service provider operating host computer610, or both. While OTT connection650is 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).

Wireless connection670between UE630and base station620is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE630using OTT connection650, in which wireless connection670forms the last segment. More precisely, the teachings of these embodiments may improve the data rate and latency and thereby provide benefits such as reduced user waiting time and better responsiveness.

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 OTT connection650between host computer610and UE630, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection650may be implemented in software611and hardware615of host computer610or in software631and hardware635of UE630, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection650passes; 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 software611,631may compute or estimate the monitored quantities. The reconfiguring of OTT connection650may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station620, and it may be unknown or imperceptible to base station620. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer610′s measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software611and631causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection650while it monitors propagation times, errors etc.

Modifications, additions, or omissions may be made to the methods, systems, and apparatuses described herein without departing from the scope of the disclosure. The methods may include more, fewer, or other steps. Additionally, steps may be performed in any suitable order. The components of the systems and apparatuses may be integrated or separated. Moreover, the operations of the systems and apparatuses may be performed by more, fewer, or other components. Additionally, operations of the systems and apparatuses may be performed using any suitable logic comprising software, hardware, and/or other logic. As used in this document, “each” refers to each member of a set or each member of a subset of a set.

Although this disclosure has been described in terms of certain embodiments, alterations and permutations of the embodiments will be apparent to those skilled in the art. Accordingly, the above description of the embodiments does not constrain this disclosure. Other changes, substitutions, and alterations are possible without departing from the spirit and scope of this disclosure, as defined by the following claims.