PDCP UL split and pre-processing

This application is a continuation of co-pending U.S. patent application Ser. No. 16/227,430 filed Dec. 20, 2018, which is a Continuation of International Patent Application PCT/IB2018/057464, filed Sep. 26, 2018, which claims the benefit of U.S. Provisional Application No. 62/564,640, filed Sep. 28, 2017 and entitled “PDCP SPLIT AND PRE-PROCESSING,” the disclosures of which are all hereby incorporated by reference.

The present invention is related to wireless communication networks, and particularly related to uplink split-bearer configurations for UEs that transmit packet data units, PDUs, by a first Radio Link Control, RLC, entity via a first uplink transmission path and/or by a second RLC entity via a second uplink transmission path.

In 3GPP Long Term Evolution (LTE), a user equipment (UE) can be configured with dual connectivity (DC), where the UE is connected to two separate eNBs, associated via separate Medium Access Control (MAC) entities/cell groups. In the uplink (UL) split bearer configuration of DC, the UE maintains one Packet Data Convergence Protocol (PDCP) entity that routes the data via two separate Radio Link Control (RLC) entities, via the two cell groups to the two eNBs.

When a UE is configured with DC and UL split bearer, the UE is configured with two UL transmission paths associated with two separate RLC entities. Transmission on these transmission paths is triggered by reception of an UL transmission grant from the eNB for the respective path. In LTE, the PDCP entity delivers PDCP Protocol Data Units (PDUs) to the RLC entity for transmission when a transmission opportunity is indicated by lower layers, or when requested by lower layers for this path (i.e., upon grant reception). A PDCP PDU is then delivered to the RLC entity and the RLC entity builds an RLC PDU. This implies that PDCP stores the PDCP PDUs and does not deliver them to lower layers until requested by them. The RLC state variables are only updated when PDCP delivers a PDCP PDU to the RLC entity.

When the PDCP data volume is above a configured split threshold, the UE reports that data as available for transmission to both eNBs, otherwise the report is only towards a configured prioritized eNB (i.e., for a single prioritized path). In both cases, the network may then issue grants independently to each of the paths. This behavior allows the network to control the load that each of the paths carries. This is currently specified as a procedure to report uplink data available at PDCP to a Master Cell Group (MCG) and Secondary Cell Group (SCG) when a pre-configured threshold amount of data is exceeded.

In 3GPP New Radio (NR), the PDCP entity can deliver a PDCP PDU to the RLC entity at any point in time and the RLC entity can also build an RLC PDU at any point in time, even before a transmission opportunity is indicated by lower layers. This means that the UE pre-selects the path in which the PDCP PDUs are placed regardless of whether the UE has a grant or not in that path. In contrast to LTE, the UE in NR reports part of the available data to the first path, part of the other data to the second path, and may still report part of the data that was not yet delivered to one of the two RLC entities to both paths.

The existing solution for NR, as indicated above, greatly reduces the ability of the network to control the load on each of the paths. Compared to LTE, in NR, the RLC entity will buffer data (RLC PDUs) and will wait for a grant to be received. The RLC state variable TX_NEXT (which indicates the next Sequence Number to be set for the upcoming RLC SDU) is also updated any time a new RLC PDU is created and queued.

Creating RLC PDUs without having a transmission opportunity creates a number of issues. For example, the network is not able to control the traffic load in each of the paths because the UE pre-determines in which path the UE stores data and in which path grants are requested. Also, if RLC PDUs are stored for a long period of time due to the fact that no grants are received, very few grants or small grant sizes are received. If there are many RLC PDU retransmissions in at least one of the RLC entities in which RLC PDUs are stored, undesirable events may occur. The PDCP discard timer may expire, leading to data loss. The T-reordering timer in the PDCP receiver side may expire, leading to the discard of the data that was not received. Another issue is that data cannot be discarded (i.e., current LTE procedures for RLC SDU discard are obsolete). Unwanted jitter may also be introduced when the UE does not split the data to be transmitted according to the uplink grant ratio.

Another consideration involved with the pre-processing of PDUs by the RLC entities involves the buffer data volume that is to be compared to the PDCP uplink split bearer threshold. According to some embodiments, when PDCP PDUs are moved to RLC for the purpose of pre-processing, and the data is not transmitted yet, the pre-processed data at the RLC entity or entities should be considered as part of the data volume calculation for comparison with the uplink split bearer threshold. The threshold determines the amount of data buffered for transmission on the prioritized UL path, and thus should consider all data on both RLC and PDCP that is not yet transmitted.

For any buffer status reporting (BSR) or reporting of data volume, if the data volume falls below the split threshold, data is indicated only to the configured UL path. If the data volume is higher than the threshold, data is indicated to both UL paths.

According to some embodiments, a method by a UE configured to transmit PDUs by a first RLC entity via a first uplink transmission path and/or by a second RLC entity via a second uplink transmission path includes determining a total amount of data volume buffered for PDU transmission, where the total amount of data volume includes PDCP data volume and RLC data volume pending for initial transmission in the two RLC entities. The method also includes reporting the PDCP data volume to at least the first uplink transmission path, based on whether the total amount of data volume meets or exceeds a first threshold. The reporting includes, in response to determining that the total amount of data volume meets or exceeds the first threshold, indicating the PDCP data volume to both the first uplink transmission path and the second uplink transmission path, and, in response to determining that the total amount of data volume does not meet the first threshold, indicating the PDCP data volume to only the first uplink transmission path.

The first uplink transmission path may be configured as a prioritized uplink transmission path and the second uplink transmission path may be configured as an unprioritized uplink transmission path. The first RLC entity may belong to a Master Cell Group (MCG), and the second RLC entity may belong to a Secondary Cell Group (SCG).

While the (PDCP) data volume for BSR operation is the same as in LTE, for effective pre-processing implementation, the actual submission to lower procedure may need to be slightly different than in LTE. That is, when data volume is below the split threshold, it must be transmitted via the configured UL (while in LTE it was possible via either UL). In some embodiments, in response to determining that the total amount of data does not meet a first threshold, the method includes submitting the data volume only to the first RLC entity.

According to certain embodiments, when the data volume is below the PDCP split threshold, UE is not expected to have data available for transmission on the unprioritized UL path.

According to some embodiments, a method by a UE configured to transmit PDUs by a first RLC entity via a first uplink transmission path and/or by a second RLC entity via a second uplink transmission path includes determining a total amount of data volume buffered for PDU transmission, where the total amount of data volume includes PDCP data volume and RLC data volume pending for initial transmission in the two associated RLC entities. The method also includes deciding whether submission of the PDCP data volume is allowed to either of the two RLC entities or to only the first RLC entity, based on whether the total amount of data volume meets or exceeds a first threshold. The deciding includes, in response to determining that the total amount of data volume meets or exceeds the first threshold, deciding that the PDCP data volume is allowed to be submitted to either of the two RLC entities, and, in response to determining that the total amount of data volume does not meet the first threshold, deciding that the PDCP data volume is allowed to be submitted to only the first RLC entity.

The method may further include submitting the PDCP data volume according to the decision. The method may include, in response to deciding that the PDCP data volume is allowed to be submitted to either of the two RLC entities, submitting the PDCP data volume to whichever of the two RLC entities requested the PDCP data volume.

According to some embodiments, a UE is configured to transmit PDUs by a first RLC entity via a first uplink transmission path and/or by a second RLC entity via a second uplink transmission path. The UE includes transceiver circuitry configured to send and receive radio signals and processing circuitry operatively associated with the transceiver circuitry. The processing circuitry is configured to determine a total amount of data volume buffered for PDU transmission, where the total amount of data volume includes PDCP data volume and RLC data volume pending for initial transmission in the two RLC entities. The processing circuitry is also configured to report the PDCP data volume to at least the first uplink transmission path, based on whether the total amount of data volume meets or exceeds a first threshold. The reporting includes, in response to determining that the total amount of data volume meets or exceeds the first threshold, indicating the PDCP data volume to both the first uplink transmission path and the second uplink transmission path, and, in response to determining that the total amount of data volume does not meet the first threshold, indicating the PDCP data volume to only the first uplink transmission path.

According to some embodiments, a UE is configured to transmit PDUs by a first RLC entity via a first uplink transmission path and/or by a second RLC entity via a second uplink transmission path. The UE includes transceiver circuitry configured to send and receive radio signals and processing circuitry operatively associated with the transceiver circuitry. The processing circuitry is configured to determine a total amount of data volume buffered for PDU transmission, where the total amount of data volume comprises PDCP data volume and RLC data volume pending for initial transmission in the two associated RLC entities. The processing circuitry is also configured to decide whether submission of the PDCP data volume is allowed to either of the two RLC entities or to only the first RLC entity, based on whether the total amount of data volume meets or exceeds a first threshold. The deciding includes, in response to determining that the total amount of data volume meets or exceeds the first threshold, deciding that the PDCP data volume is allowed to be submitted to either of the two RLC entities, and, in response to determining that the total amount of data volume does not meet the first threshold, deciding that the PDCP data volume is allowed to be submitted to only the first RLC entity.

Embodiments described herein provide solutions to these or other challenges. According to one embodiment, a UE is configured to: 1) determine when an RLC PDU will be delivered too late (causing data losses); 2) re-route the data to a second path when the RLC PDU cannot be delivered on time in the first path; and 3) remove the RLC PDUs from the first path.

According to some embodiments, a UE is configured with a maximum pre-processing limit. This configuration may be indicated in RRC signaling from the gNB. The maximum pre-processing limit limits, in terms of time, pre-processing to close a transmission gap that may be created when, for example, PDU n+1 is transmitted while PDU n is not transmitted. The UE may not exceed the pre-processing limit and thus the UE may discard a pre-processed PDU for transmission via one path (cell group) and/or retransmit a pre-processed PDU via another path (another cell group).

The various embodiments described herein address one or more of the issues with uplink split-bearer transmission of PDUs. Certain embodiments may provide one or more technical advantages. For instance, certain embodiments may avoid packet loss that might occur when reordering delays that are too high are introduced. Unwanted jitter may also be avoided. According to certain embodiments, high throughputs may be enabled for UL resource aggregation with UL split configuration. All of these benefits lead to higher end user performance. Certain embodiments may provide all, some, or none of these specific advantages, and other advantages may be readily apparent.

Additional embodiments may include the method implemented by apparatus, wireless devices, computer readable medium, computer program products and functional implementations.

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

Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

Embodiments of the present invention improve UE operations in an uplink split bearer configuration. To improve the accuracy of transmission decisions, according to some embodiments, any PDCP PDUs that are moved to RLC for the purpose of pre-processing and are pending for initial transmission in RLC entities are considered with the PDCP data volume when the data volume is being compared to the PDCP uplink split bearer threshold. The uplink split bearer threshold determines the amount of data buffered for transmission on the prioritized uplink transmission path, and thus all data on both RLC and PDCP that is not yet transmitted should be considered.

Buffer status reporting (BSR) or other PDCP data reporting then involves the total amount of data volume that considers both the PDCP data volume and the data volume that is being pre-processed or buffered in the RLC layer before an uplink grant is received and before the data is transmitted. If the total data volume is below the uplink split bearer threshold, PDCP data volume is indicated only to the configured uplink transmission path. If the PDCP data volume is higher than the threshold, PDCP data volume is indicated to both uplink transmission paths.

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 in. For simplicity, the wireless network ofonly depicts network, network nodesandb, and wireless devices (WDs),b, andc. 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 nodeand WDare 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 (NR) 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.

Networkmay 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 nodeand WDcomprise 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, 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 and positioning nodes. 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.

In, network nodeincludes processing circuitry, device readable medium, interface, auxiliary equipment, power source, power circuitry, and antenna. Although network nodeillustrated in the example wireless network ofmay 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 nodeare 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 mediummay comprise multiple separate hard drives as well as multiple RAM modules).

Similarly, network nodemay be composed of multiple physically separate components (e.g., a NodeB component and an 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 nodecomprises 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 nodemay be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable mediumfor the different RATs) and some components may be reused (e.g., the same antennamay be shared by the RATs). Network nodemay also include multiple sets of the various illustrated components for different wireless technologies integrated into network node, 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 node.

Processing circuitryis 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 circuitrymay include processing information obtained by processing circuitryby, 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 circuitrymay 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 nodecomponents, such as device readable medium, network nodefunctionality. For example, processing circuitrymay execute instructions stored in device readable mediumor in memory within processing circuitry. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitrymay include a system on a chip (SOC).

In some embodiments, processing circuitrymay include one or more of radio frequency (RF) transceiver circuitryand baseband processing circuitry. In some embodiments, RF transceiver circuitryand baseband processing circuitrymay 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 circuitryand baseband processing circuitrymay 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 or other such network device may be performed by processing circuitryexecuting instructions stored on device readable mediumor memory within processing circuitry. In alternative embodiments, some or all of the functionality may be provided by processing circuitrywithout 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 circuitrycan be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitryalone or to other components of network nodebut are enjoyed by network nodeas a whole, and/or by end users and the wireless network generally.

Device readable mediummay 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 circuitry. Device readable mediummay 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 circuitryand, utilized by network node. Device readable mediummay be used to store any calculations made by processing circuitryand/or any data received via interface. In some embodiments, processing circuitryand device readable mediummay be considered to be integrated.

Interfaceis used in the wired or wireless communication of signalling and/or data between network node, network, and/or WDs. As illustrated, interfacecomprises port(s)/terminal(s)to send and receive data, for example to and from networkover a wired connection. Interfacealso includes radio front end circuitrythat may be coupled to, or in certain embodiments a part of, antenna. Radio front end circuitrycomprises filtersand amplifiers. Radio front end circuitrymay be connected to antennaand processing circuitry. Radio front end circuitry may be configured to condition signals communicated between antennaand processing circuitry. Radio front end circuitrymay receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitrymay convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filtersand/or amplifiers. The radio signal may then be transmitted via antenna. Similarly, when receiving data, antennamay collect radio signals which are then converted into digital data by radio front end circuitry. The digital data may be passed to processing circuitry. In other embodiments, the interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, network nodemay not include separate radio front end circuitry, instead, processing circuitrymay comprise radio front end circuitry and may be connected to antennawithout separate radio front end circuitry. Similarly, in some embodiments, all or some of RF transceiver circuitrymay be considered a part of interface. In still other embodiments, interfacemay include one or more ports or terminals, radio front end circuitry, and RF transceiver circuitry, as part of a radio unit (not shown), and interfacemay communicate with baseband processing circuitry, which is part of a digital unit (not shown).

Antennamay include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antennamay be coupled to radio front end circuitryand may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antennamay 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 multiple-in-multiple-out (MIMO). In certain embodiments, antennamay be separate from network nodeand may be connectable to network nodethrough an interface or port.

Antenna, interface, and/or processing circuitrymay 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, antenna, interface, and/or processing circuitrymay 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 circuitrymay comprise, or be coupled to, power management circuitry and is configured to supply the components of network nodewith power for performing the functionality described herein. Power circuitrymay receive power from power source. Power sourceand/or power circuitrymay be configured to provide power to the various components of network nodein a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power sourcemay either be included in, or external to, power circuitryand/or network node. For example, network nodemay 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 circuitry. As a further example, power sourcemay comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. 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 nodemay include additional components beyond those shown inthat 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 nodemay include user interface equipment to allow input of information into network nodeand to allow output of information from network node. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node.

As used herein, wireless device (WD) refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). 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 WD may be configured to transmit and/or receive information without direct human interaction. For instance, a WD 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 WD 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 WD 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 WD 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 WD and/or a network node. The WD 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 WD 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 WD 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 WD 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 WD 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 deviceincludes antenna, interface, processing circuitry, device readable medium, user interface equipment, auxiliary equipment, power sourceand power circuitry. WDmay include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD, 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 WD.

Antennamay include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface. In certain alternative embodiments, antennamay be separate from WDand be connectable to WDthrough an interface or port. Antenna, interface, and/or processing circuitrymay be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antennamay be considered an interface.

As illustrated, interfacecomprises radio front end circuitryand antenna. Radio front end circuitrycomprise one or more filtersand amplifiers. Radio front end circuitryis connected to antennaand processing circuitry, and is configured to condition signals communicated between antennaand processing circuitry. Radio front end circuitrymay be coupled to or a part of antenna. In some embodiments, WDmay not include separate radio front end circuitry; rather, processing circuitrymay comprise radio front end circuitry and may be connected to antenna. Similarly, in some embodiments, some or all of RF transceiver circuitrymay be considered a part of interface. Radio front end circuitrymay receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitrymay convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filtersand/or amplifiers. The radio signal may then be transmitted via antenna. Similarly, when receiving data, antennamay collect radio signals which are then converted into digital data by radio front end circuitry. The digital data may be passed to processing circuitry. In other embodiments, the interface may comprise different components and/or different combinations of components.

Processing circuitrymay 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 WDcomponents, such as device readable medium, WDfunctionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitrymay execute instructions stored in device readable mediumor in memory within processing circuitryto provide the functionality disclosed herein.

As illustrated, processing circuitryincludes one or more of RF transceiver circuitry, baseband processing circuitry, and application processing circuitry. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitryof WDmay comprise a SOC. In some embodiments, RF transceiver circuitry, baseband processing circuitry, and application processing circuitrymay be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitryand application processing circuitrymay be combined into one chip or set of chips, and RF transceiver circuitrymay be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitryand baseband processing circuitrymay be on the same chip or set of chips, and application processing circuitrymay be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry, baseband processing circuitry, and application processing circuitrymay be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitrymay be a part of interface. RF transceiver circuitrymay condition RF signals for processing circuitry.