WO2022112947A1

WO2022112947A1 - Enhanced beam failure recovery detection

Info

Publication number: WO2022112947A1
Application number: PCT/IB2021/060879
Authority: WO
Inventors: Jan Lindskog; Niclas Bauer; Per LÖFVING; Jan Wichert; Pär ANKEL; Claes Tidestav
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2020-11-25
Filing date: 2021-11-23
Publication date: 2022-06-02
Also published as: TW202228413A; TWI793872B

Abstract

A method 1900 by a wireless device 610 includes, prior to performing a random access (RA) procedure or while performing the RA procedure, identifying 1902 data in a buffer for transmission on an uplink. While the data is in the buffer, the wireless device transmits 1904, to a network node 160, a message associated with the RA procedure, the message indicating an empty buffer status. The wireless device forgoes 1906 transmitting the data in the buffer on the uplink for a time period associated with a performance of at least a portion of the RA procedure.

Description

ENHANCED BEAM FAILURE RECOVERY DETECTION

BACKGROUND

Beam failure recovery (BFR) is a 3^rd Generation Partnership Project (3GPP) standardized feature that enables fast User Equipment (UE) recovery in fluctuating radio conditions. After detecting a beam failure, a UE will make random access attempts to recover its connection. After a successful beam failure recovery, the UE will remain in connected mode. See, 3GPP TS38.321, Chapter 5.17.

Scheduling Request (SR)

A UE may be configured with zero, one, or more SR configurations. One SR configuration corresponds to one or more logical channels, which may include, for example, different Quality of Service (QoS) services such as Voice over Internet Protocol (VoIP) and background traffic streaming traffic.

SR utilizes Physical Uplink Control Channel (PUCCH) resources where the PUCCH resources occurs periodic in time. Certain embodiments described herein use one logical channel, one SR, and one PUCCH (SR-PUCCH).

The SR configuration has one SR COUNTER. When the UE has pending uplink data and its SR is pending (=1), the UE will utilize its periodic SR-PUCCH resource to notify the gNodeB (gNB). The SR COUNTER is updated (+1) each time a transmission occurs on the SR-PUCCH resource.

The UE resets its SR COUNTER once the gNB allows the UE to transmit its entire amount of pending uplink data. Alternatively, the UE resets the SR COUNTER when the UE transmits a Buffer Status Report (BSR), which contains buffer status up to (and including) the pending data which exists.

If the SR COUNTER reaches its MAX value, the UE will remove its SR- PUCCH resource. If that happens, the UE will no longer be able to use the SR- PUCCH resource. The UE will, from this point, use Random Access Channel (RACH) to notify the gNB about pending uplink data to transmit. See, 3 GPP TS 38.321, Chapter 5.4.4. In both cases, Random Access (RA) attempts are sent by UEs in connected mode. Information about the connection status of the UE can be determined from the Cell-Radio Network Temporary Identifier (C-RNTI) received in Msg3.

FIGURE 1 illustrates the steps for performing RA by a UE. As illustrated, at step 100, it is determined whether a Msgl is detected. If the Msgl is detected, a Msg2 is transmitted at step 101. At step 102, a determination is made as to whether the CRC of a Msg3 received from the network is okay. If the CRC of the Msg3 is okay, the UE transmits a Msg4 at step 103. At step 104, a determination is made as to whether the CRC of a Msg5 received from the network is okay. If the CRC of the Msg5 is okay, the RACH process is complete at step 105.

If at step 102 or 104, it is determined that the CRC of the Msg3 or Msg5, respectively, is not okay, the message continues to steps 106 or 107, respectively, where it is determined whether a retransmission is possible. If retransmission is possible at steps 106 or 107, the method continues to steps 108 or 109, respectively, and the message is retransmitted.

Certain problems exist. For example, in BFR, the UE performs a RA attempt using the beam index that has been identified as providing the best signal quality. At detection of a successful RA attempt, the gNB may conclude that a BFR has occurred atthe UE. This starts the procedure performed at BFR at the gNB. For example, the gNB may perform a beam refinement process to select the best beam for the UE to use for decoding.

As long as the UE’s SR-PUCCH resource exists, the UE will use the SR- PUCCH resource to indicate pending SR.

In a first example scenario, and to illustrate one aspect of the problem, it may be assumed that the UE has pending data. It may also be assumed that the SR- PUCCH exists and that the UE transmits on its SR-PUCCH but does not obtain a PUSCH. FIGURE 2 illustrates an example method by a UE according to 3 GPP 38.321, Ch. 5.17 for the first example scenario.

As illustrated, at steps 201 and 202, respectively, the UE concludes that a BFR has occurred and that the BFI COUNTER is not greater than or equal to a beamFailurelnstanceMaxCount. If it is determined that the BFI Counter is not greater than or equal to the beamFailurelnstanceMaxCount, the method returns to step 201. Conversely, if it is determined that the BFI Counter is greater than or equal to the beamFailureinstanceMaxCount, the message proceeds to step 203, where the UE starts a RA procedure according to 3GPP 38.321, Ch. 5.1.1. At step 204, the UE concludes that the random access procedure started at step 203 was successful/completed as disclosed in chapter 5.1.5 of 3GPP 38.321, which states that a ‘PDCCH transmission is addressed to the C-RNTI and contains a grant for a new transmission’. At step 205, the UE checks whether a pending SR exists. If the pending SR exists, the UE transmits a Msg5 at step 206.

In a second scenario, it may be assumed that SR-PUCCH has been removed at the UE. Same as above, it may also be assumed that the UE has pending data to send. In this scenario, no BFR has occurred at the UE. It may also be assumed that for random access procedure Msg3, the UE will not be given the chance to transmit UL-SCH data since Msg3 transport block size TBS does not allow for it. Though a figure is not provided, it may be appreciated that the UE may execute steps 203, 204, 205, and 206 as disclosed with regard to FIGURE 2 above.

In a third scenario, it is the same case as for 2^nd scenario, with the exception that BFR has occurred at the UE. Specifically, it may be assumed that BFR has occurred and that steps 201, 202, and 203 occur first and then UE obtains pending data. Then, steps 204, 205, and 206 may be the same as above.

In all scenarios above, a problem exists in that it is not clear how the gNB will distinguish between the three scenarios and then start the corresponding actions for BFR or actions for when SR-PUCCH has been removed at UE. For example, if the gNB incorrectly determines that SR-PUCCH has been released at the UE, the gNB will start actions to restore the SR-PUCCH resource. The gNB may also decide to reconfigure the UE by signaling new configuration parameters. The new configuration parameters may include identical or modified SR-PUCCH channel parameters. In response, the UE may be required to restart with the new SR-PUCCH channel parameters. This results in increased and unnecessary control signaling overhead. Additionally, the interruption during the restart procedure at the UE may be unnecessary.

As another example, the gNB may alternatively decide to force the UE to release itself from the New Radio (NR) network. The latter may be required since a UE with a released SR-PUCCH resource implies a higher risk of increased random access signaling. Such signaling may affect other UEs since the random access channel is a shared resource.

As still another example, a gNB may deny further random access attempts from the UE with the released SR-PUCCH to force the UE to leave the NR network.

SUMMARY

Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. For example, according to certain embodiments, methods and systems are provided that make it possible to deterministically identify a BFR attempt during a RA procedure. Certain embodiments improve the gNB detection mechanism for BFR.

According to certain embodiments, a method by a wireless device, prior to performing a RA procedure or while performing the RA procedure, identifying data in a buffer for transmission on an uplink. While the data is in the buffer, the wireless device transmits, to a network node, a message associated with the RA procedure, the message indicating an empty buffer status. The wireless device forgoes transmitting the data in the buffer on the uplink for a time period associated with a performance of at least a portion of the RA procedure.

According to certain embodiments, a wireless device includes processing circuitry configured to, prior to performing a RA procedure or while performing the RA procedure, identify data in a buffer for transmission on an uplink. While the data is in the buffer, the processing circuitry is configured to transmit, to a network node, a message associated with the RA procedure, the message indicating an empty buffer status. The processing circuitry is configured to forgo transmitting the data in the buffer on the uplink for a time period associated with a performance of at least a portion of the RA procedure.

According to certain embodiments, a method by a network node includes receiving, from a wireless device, a message associated with a RA procedure. The message indicates a buffer status of the wireless device. Based on the buffer status, the network node determines a cause for an initiation of the RA procedure by the wireless device. The cause is determined to be a BFR or a release of a resource associated with a SR-PUCCH.

According to certain embodiments, a network node includes processing circuitry configured to receive, from a wireless device, a message associated with a RA procedure. The message indicates a buffer status of the wireless device. Based on the buffer status, the processing circuitry is configured to determine a cause for an initiation of the RA procedure by the wireless device. The cause is determined to be a BFR or a release of a resource associated with a SR-PUCCH.

Certain embodiments may provide one or more of the following technical advantages. For example, one technical advantage may be that certain embodiments enable the gNB to be able deterministically distinguish between BFR and periodic SR types of random access attempts. As such, certain embodiments may improve the performance for both UEs performing BFR and UEs performing periodic SR.

As another example, a technical advantage may be that certain embodiments allowing for the deterministic identification of BFR may result in the UE more reliably recovering its RRC connection instead of experiencing a radio link failure and NR leg release, followed by a new NR leg attach procedure.

Other advantages may be readily apparent to one having skill in the art. Certain embodiments may have none, some, or all of the recited advantages.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which:

FIGURE 1 illustrates the steps for performing RA by a UE;

FIGURE 2 illustrates an example method by a UE according to 3GPP 38.321, Ch. 5.17 for the first example scenario;

FIGURE 3 illustrates an example method for determining that the reason for the RACH is due to BFR by a gNB, according to certain embodiments;

FIGURE 4 illustrates an example method by the UE, according to certain embodiments;

FIGURE 5 illustrates an alternative example method by a UE, according to certain embodiments; FIGURE 6 illustrates an example wireless network, according to certain embodiments;

FIGURE 7 illustrates an example network node, according to certain embodiments;

FIGURE 8 illustrates an example wireless device, according to certain embodiments;

FIGURE 9 illustrate an example user equipment, according to certain embodiments;

FIGURE 10 illustrates a virtualization environment in which functions implemented by some embodiments may be virtualized, according to certain embodiments;

FIGURE 11 illustrates a telecommunication network connected via an intermediate network to a host computer, according to certain embodiments;

FIGURE 12 illustrates a generalized block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection, according to certain embodiments;

FIGURE 13 illustrates a method implemented in a communication system, according to one embodiment;

FIGURE 14 illustrates another method implemented in a communication system, according to one embodiment;

FIGURE 15 illustrates another method implemented in a communication system, according to one embodiment;

FIGURE 16 illustrates another method implemented in a communication system, according to one embodiment;

FIGURE 17 illustrates an example method by a wireless device, according to certain embodiments;

FIGURE 18 illustrates an example virtual apparatus, according to certain embodiments;

FIGURE 19 illustrates an example method by a network node, according to certain embodiments;

FIGURE 20 illustrates another example virtual apparatus, according to certain embodiments; FIGURE 21 illustrates another example method by a wireless device, according to certain embodiments; and

FIGURE 22 illustrates another example method by a network node, according to certain embodiments;.

DETAILED DESCRIPTION

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.

Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description.

In some embodiments, a more general term “network node” may be used and may correspond to any type of radio network node or any network node, which communicates with a UE (directly or via another node) and/or with another network node. Examples of network nodes are NodeB, MeNB, ENB, a network node belonging to MCG or SCG, base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB, gNodeB, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), access point (AP), transmission points, transmission nodes, RRU, RRH, nodes in distributed antenna system (DAS), core network node (e.g. MSC, MME, etc ), O&M, OSS, SON, positioning node (e g. E-SMLC), MDT, test equipment (physical node or software), etc. In some embodiments, the non-limiting term user equipment (UE) or wireless device may be used and may refer to any type of wireless device communicating with a network node and/or with another UE in a cellular or mobile communication system. Examples of UE are target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine (M2M) communication, PDA, PAD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, UE category Ml, UE category M2, ProSe UE, V2V UE, V2X UE, etc.

Additionally, terminologies such as base station/gNodeB and UE should be considered non-limiting and do in particular not imply a certain hierarchical relation between the two; in general, “gNodeB” could be considered as device 1 and “UE” could be considered as device 2 and these two devices communicate with each other over some radio channel. And in the following the transmitter or receiver could be either gNB, or UE.

According to certain embodiments, methods and systems are provided that make it possible to deterministically identify a BFR attempt during a RA procedure. Certain embodiments improve the gNB detection mechanism for BFR.

Additionally, according to certain embodiments, methods and systems are provided to allow the UE to omit UL-SCH data when performing beam failure recovery. With the BSR always being empty when performing BFR, the gNodeB is able to deterministically distinguish between random access attempts originating from periodic SR and random access attempts originating from BFR.

To distinguish between the first, second, and third scenarios described above, certain embodiments enable the gNB to use the reported BSR value from UE at either RACH Msg3 or RACH Msg5. For example, if the BSR value is identical to 0, the gNB may determine that the reason for the RACH is due to BFR since a BFR has been configured and the RACH access is not the initial RACH access from the UE. FIGURE 3 illustrates an example method for determining that the reason for the RACH is due to BFR by a gNB, according to certain embodiments. Although FIGURE 3 illustrates Msg5 being used, it is recognized that Msg3 or another appropriate message may additionally or alternatively be used. Steps 300 through 309 may be similar to steps 100 through 109 as described above with regard to FIGURE 1. However, at step 310, it is determined whether the CRNTI is known. At step 311 of FIGURE 3, the gNB may investigate whether a BSR is present in the transmission (not shown) and whether the BSR is greater than 0. If the BSR is greater than 0, the gNB may determine at step 313 that the SR- PUCCH has been released at UE. Conversely, if the BSR is not present (not shown) or equal to 0, the gNB may determine that a BFR has happened at UE, at step 312.

To further enhance the gNB procedure described above, FIGURE 4 proposes a method by the UE, according to certain embodiments. Steps 401 through 404 may be similar to steps 200 through 204 as described above with regard to FIGURE 2. However, as shown in FIGURE 4, at step 404, the UE has decoded a PDCCH (Msg4) with an UL grant for new transmission. As can be seen at step 405, the UE transmits NO BSR and transmits padding on Msg5 instead. Alternatively, the UE may send a BSR with content equal to 0. Note that this applies independent of whether of UE has pending data. Stated differently, whereas previous methods and systems required the UE to send any data that the UE had stored in the UE’s buffer during a Msg3 or a Msg5 of the RACH procedure, certain embodiments disclosed herein may require the UE to “pause” any such data transmission until after the RACH procedure is complete (e.g., represented by expiration of a time period).

FIGURE 5 illustrates an alternative method by a UE, according to certain embodiments. Steps 501 through 504 may be similar to steps 400 through 404 in FIGURE 4, which are similar to steps 200 through 204 as described above with regard to FIGURE 2. However, As shown in FIGURE 5, at steps 505 and 507, the UE determines if its SR-PUCCH resource has been removed. If ‘YES’, the UE transmits, at steps 506 and 509, respectively, what may be referred to herein as ‘Dummy data.’ According to certain embodiments, the ‘Dummy data’ may be, for example, a legitimate RLC STATUS msg plus padding. However, the Dummy data may include any such data that causes the gNB to determine that pending data existed at UE side. Though FIGURE 5 does not illustrate as much, it is also recognized that pending real data may also be sent if present.

Returning to step 507, if the UE determines that its SR resource has not been removed (i.e., ‘NO’), the UE may continue with step 508 of FIGURE 5 so as to transmit padding or BSR=0 and an indication of the UE’s real pending data status. This step may be similar to step 405 described above with regard to FIGURE 4.

FIGURE 6 illustrates a wireless network, in accordance with some embodiments. 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 FIGURE 6. For simplicity, the wireless network of FIGURE 6 only depicts network 606, network nodes 660 and 660b, and wireless devices 610. 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 node 660 and wireless device 610 are 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.

Network 606 may 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 node 660 and wireless device 610 comprise 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.

FIGURE 7 illustrates an example network node 660, according to certain embodiments. 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, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). 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.

In FIGURE 7, network node 660 includes processing circuitry 670, device readable medium 680, interface 690, auxiliary equipment 684, power source 686, power circuitry 687, and antenna 662. Although network node 660 illustrated in the example wireless network of FIGURE 7 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components (e.g., fewer components, additional components, different 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 node 660 are 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 medium 680 may comprise multiple separate hard drives as well as multiple RAM modules).

Similarly, network node 660 may 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 node 660 comprises 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 node 660 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium 680 for the different RATs) and some components may be reused (e.g., the same antenna 662 may be shared by the RATs). Network node 660 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 660, 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 660.

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

In some embodiments, processing circuitry 670 may include one or more of radio frequency (RF) transceiver circuitry 672 and baseband processing circuitry 674. In some embodiments, radio frequency (RF) transceiver circuitry 672 and baseband processing circuitry 674 may 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 circuitry 672 and baseband processing circuitry 674 may 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 circuitry 670 executing instructions stored on device readable medium 680 or memory within processing circuitry 670. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 670 without 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 circuitry 670 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 670 alone or to other components of network node 660 but are enjoyed by network node 660 as a whole, and/or by end users and the wireless network generally.

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

Interface 690 is used in the wired or wireless communication of signalling and/or data between network node 660, network 606, and/or wireless devices 610. As illustrated, interface 690 comprises port(s)/terminal(s) 694 to send and receive data, for example to and from network 606 over a wired connection. Interface 690 also includes radio front end circuitry 692 that may be coupled to, or in certain embodiments a part of, antenna 662. Radio front end circuitry 692 comprises filters 698 and amplifiers 696. Radio front end circuitry 692 may be connected to antenna 662 and processing circuitry 670. Radio front end circuitry may be configured to condition signals communicated between antenna 662 and processing circuitry 670. Radio front end circuitry 692 may receive digital data that is to be sent out to other network nodes or wireless devices via a wireless connection. Radio front end circuitry 692 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 698 and/or amplifiers 696. The radio signal may then be transmitted via antenna 662. Similarly, when receiving data, antenna 662 may collect radio signals which are then converted into digital data by radio front end circuitry 692. The digital data may be passed to processing circuitry 670. In other embodiments, the interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, network node 660 may not include separate radio front end circuitry 692, instead, processing circuitry 670 may comprise radio front end circuitry and may be connected to antenna 662 without separate radio front end circuitry 692. Similarly, in some embodiments, all or some of RF transceiver circuitry 672 may be considered a part of interface 690. In still other embodiments, interface 690 may include one or more ports or terminals 694, radio front end circuitry 692, and RF transceiver circuitry 672, as part of a radio unit (not shown), and interface 690 may communicate with baseband processing circuitry 674, which is part of a digital unit (not shown).

Antenna 662 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 662 may be coupled to radio front end circuitry 692 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 662 may 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, antenna 662 may be separate from network node 660 and may be connectable to network node 660 through an interface or port.

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

FIGURE 8 illustrates an example wireless device 610. According to certain embodiments. 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. Unless otherwise noted, the term wireless device 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 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 Embodiment By implementing a 3 GPP standard for sidelink communication, vehi cl e-to- vehicle (V2V), vehicle-to- infrastructure (V2I), vehicle-to-everything (V2X) 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 3 GPP context be referred to as an 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 device 610 includes antenna 611, interface 614, processing circuitry 620, device readable medium 630, user interface equipment 632, auxiliary equipment 634, power source 636 and power circuitry 637. Wireless device 610 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by wireless device 610, 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 device 610.

Antenna 611 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 614. In certain alternative embodiments, antenna 611 may be separate from wireless device 610 and be connectable to wireless device 610 through an interface or port. Antenna 611, interface 614, and/or processing circuitry 620 may 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 circuitry and/or antenna 611 may be considered an interface. As illustrated, interface 614 comprises radio front end circuitry 612 and antenna 611. Radio front end circuitry 612 comprise one or more filters 618 and amplifiers 616. Radio front end circuitry 612 is connected to antenna 611 and processing circuitry 620 and is configured to condition signals communicated between antenna 611 and processing circuitry 620. Radio front end circuitry 612 may be coupled to or a part of antenna 611. In some embodiments, wireless device 610 may not include separate radio front end circuitry 612; rather, processing circuitry 620 may comprise radio front end circuitry and may be connected to antenna 611. Similarly, in some embodiments, some or all of RF transceiver circuitry 622 may be considered a part of interface 614. Radio front end circuitry 612 may receive digital data that is to be sent out to other network nodes or wireless devices via a wireless connection. Radio front end circuitry 612 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 618 and/or amplifiers 616. The radio signal may then be transmitted via antenna 611. Similarly, when receiving data, antenna 611 may collect radio signals which are then converted into digital data by radio front end circuitry 612. The digital data may be passed to processing circuitry 620. In other embodiments, the interface may comprise different components and/or different combinations of components.

Processing circuitry 620 may 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 device 610 components, such as device readable medium 630, wireless device 610 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 620 may execute instructions stored in device readable medium 630 or in memory within processing circuitry 620 to provide the functionality disclosed herein.

As illustrated, processing circuitry 620 includes one or more of RF transceiver circuitry 622, baseband processing circuitry 624, and application processing circuitry 626. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry 620 of wireless device 610 may comprise a SOC. In some embodiments, RF transceiver circuitry 622, baseband processing circuitry 624, and application processing circuitry 626 may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry 624 and application processing circuitry 626 may be combined into one chip or set of chips, and RF transceiver circuitry 622 may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry 622 and baseband processing circuitry 624 may be on the same chip or set of chips, and application processing circuitry 626 may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry 622, baseband processing circuitry 624, and application processing circuitry 626 may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry 622 may be a part of interface 614. RF transceiver circuitry 622 may condition RF signals for processing circuitry 620.

In certain embodiments, some or all of the functionality described herein as being performed by a wireless device may be provided by processing circuitry 620 executing instructions stored on device readable medium 630, 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 circuitry 620 without 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 circuitry 620 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 620 alone or to other components of wireless device 610, but are enjoyed by wireless device 610 as a whole, and/or by end users and the wireless network generally.

Processing circuitry 620 may 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 circuitry 620, may include processing information obtained by processing circuitry 620 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by wireless device 610, 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 medium 630 may 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 circuitry 620. Device readable medium 630 may 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 circuitry 620. In some embodiments, processing circuitry 620 and device readable medium 630 may be considered to be integrated.

User interface equipment 632 may provide components that allow for a human user to interact with wireless device 610. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment 632 may be operable to produce output to the user and to allow the user to provide input to wireless device 610. The type of interaction may vary depending on the type of user interface equipment 632 installed in wireless device 610. For example, if wireless device 610 is a smart phone, the interaction may be via a touch screen; if wireless device 610 is 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 equipment 632 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 632 is configured to allow input of information into wireless device 610 and is connected to processing circuitry 620 to allow processing circuitry 620 to process the input information. User interface equipment 632 may 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 equipment 632 is also configured to allow output of information from wireless device 610, and to allow processing circuitry 620 to output information from wireless device 610. User interface equipment 632 may 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 equipment 632, wireless device 610 may communicate with end users and/or the wireless network and allow them to benefit from the functionality described herein.

Auxiliary equipment 634 is 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 equipment 634 may vary depending on the embodiment and/or scenario.

Power source 636 may, 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 device 610 may further comprise power circuitry 637 for delivering power from power source 636 to the various parts of wireless device 610 which need power from power source 636 to carry out any functionality described or indicated herein. Power circuitry 637 may in certain embodiments comprise power management circuitry. Power circuitry 637 may additionally or alternatively be operable to receive power from an external power source; in which case wireless device 610 may 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 circuitry 637 may also in certain embodiments be operable to deliver power from an external power source to power source 636. This may be, for example, for the charging of power source 636. Power circuitry 637 may perform any formatting, converting, or other modification to the power from power source 636 to make the power suitable for the respective components of wireless device 610 to which power is supplied.

Although wireless device 610 illustrated in FIGURE 8 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise wireless devices with different combinations of components (e.g., fewer components, additional components, different components). FIGURE 9 illustrates one embodiment of a UE in accordance with various aspects described herein. 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 (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). UE 700 may be any UE identified by the 3^rd Generation Partnership Project (3GPP), including a NB-IoT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE 700, as illustrated in FIGURE 7, is one example of a wireless device configured for communication in accordance with one or more communication standards promulgated by the 3^rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, the term wireless device and UE may be used interchangeable. Accordingly, although FIGURE 9 is a UE, the components discussed herein are equally applicable to a wireless device, and vice-versa.

In FIGURE 9, UE 700 includes processing circuitry 701 that is operatively coupled to input/output interface 705, radio frequency (RF) interface 709, network connection interface 711, memory 715 including random access memory (RAM) 717, read-only memory (ROM) 719, and storage medium 721 or the like, communication subsystem 731, power source 733, and/or any other component, or any combination thereof. Storage medium 721 includes operating system 723, application program 725, and data 727. In other embodiments, storage medium 721 may include other similar types of information. Certain UEs may utilize all of the components shown in FIGURE 9, 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.

In FIGURE 9, processing circuitry 701 may be configured to process computer instructions and data. Processing circuitry 701 may 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 circuitry 701 may 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 interface 705 may be configured to provide a communication interface to an input device, output device, or input and output device. UE 700 may be configured to use an output device via input/output interface 705. 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 UE 700. 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. UE 700 may be configured to use an input device via input/output interface 705 to allow a user to capture information into UE 700. 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.

In FIGURE 9, RF interface 709 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface 711 may be configured to provide a communication interface to network 743a. Network 743a may 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, network 743a may comprise a Wi-Fi network. Network connection interface 711 may 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 interface 711 may 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.

RAM 717 may be configured to interface via bus 702 to processing circuitry 701 to 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. ROM 719 may be configured to provide computer instructions or data to processing circuitry 701. For example, ROM 719 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (EO), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory. Storage medium 721 may 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 medium 721 may be configured to include operating system 723, application program 725 such as a web browser application, a widget or gadget engine or another application, and data file 727. Storage medium 721 may store, for use by UE 700, any of a variety of various operating systems or combinations of operating systems.

Storage medium 721 may 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 medium 721 may allow UE 700 to 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 medium 721, which may comprise a device readable medium.

In FIGURE 9, processing circuitry 701 may be configured to communicate with network 743b using communication subsystem 731. Network 743a and network 743b may be the same network or networks or different network or networks. Communication subsystem 731 may be configured to include one or more transceivers used to communicate with network 743b. For example, communication subsystem 731 may 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 radio access network (RAN) according to one or more communication protocols, such as IEEE 802.7, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter 733 and/or receiver 735 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 733 and receiver 735 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions of communication subsystem 731 may 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 subsystem 731 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network 743b may 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, network 743b may be a cellular network, a Wi-Fi network, and/or a near-field network. Power source 713 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE 700.

The features, benefits and/or functions described herein may be implemented in one of the components of UE 700 or partitioned across multiple components of UE 700. Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem 731 may be configured to include any of the components described herein. Further, processing circuitry 701 may be configured to communicate with any of such components over bus 702. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 701 perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry 701 and communication subsystem 731. 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.

FIGURE 10 is a schematic block diagram illustrating a virtualization environment 800 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 800 hosted by one or more of hardware nodes 830. 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 applications 820 (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. Applications 820 are run in virtualization environment 800 which provides hardware 830 comprising processing circuitry 860 and memory 890. Memory 890 contains instructions 895 executable by processing circuitry 860 whereby application 820 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

Virtualization environment 800, comprises general-purpose or special- purpose network hardware devices 830 comprising a set of one or more processors or processing circuitry 860, 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 memory 890-1 which may be non-persistent memory for temporarily storing instructions 895 or software executed by processing circuitry 860. Each hardware device may comprise one or more network interface controllers (NICs) 870, also known as network interface cards, which include physical network interface 880. Each hardware device may also include non-transitory, persistent, machine-readable storage media 890-2 having stored therein software 895 and/or instructions executable by processing circuitry 860. Software 895 may include any type of software including software for instantiating one or more virtualization layers 850 (also referred to as hypervisors), software to execute virtual machines 840 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

Virtual machines 840, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 850 or hypervisor. Different embodiments of the instance of virtual appliance 820 may be implemented on one or more of virtual machines 840, and the implementations may be made in different ways.

During operation, processing circuitry 860 executes software 895 to instantiate the hypervisor or virtualization layer 850, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 850 may present a virtual operating platform that appears like networking hardware to virtual machine 840.

As shown in FIGURE 10, hardware 830 may be a standalone network node with generic or specific components. Hardware 830 may comprise antenna 8225 and may implement some functions via virtualization. Alternatively, hardware 830 may 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) 8100, which, among others, oversees lifecycle management of applications 820.

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 machine 840 may 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 machines 840, and that part of hardware 830 that 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 machines 840, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines 840 on top of hardware networking infrastructure 830 and corresponds to application 820 in FIGURE 10.

In some embodiments, one or more radio units 8200 that each include one or more transmitters 8220 and one or more receivers 8210 may be coupled to one or more antennas 8225. Radio units 8200 may communicate directly with hardware nodes 830 via 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 affected with the use of control system 8230 which may alternatively be used for communication between the hardware nodes 830 and radio units 8200.

FIGURE 11 illustrates a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments.

With reference to FIGURE 11, in accordance with an embodiment, a communication system includes telecommunication network 910, such as a 3GPP- type cellular network, which comprises access network 911, such as a radio access network, and core network 914. Access network 911 comprises a plurality of base stations 912a, 912b, 912c, such asNBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 913a, 913b, 913c. Each base station 912a, 912b, 912c is connectable to core network 914 over a wired or wireless connection 915. A first UE 991 located in coverage area 913c is configured to wirelessly connect to, or be paged by, the corresponding base station 912c. A second UE 992 in coverage area 913a is wirelessly connectable to the corresponding base station 912a. While a plurality of UEs 991, 992 are 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 station 912.

Telecommunication network 910 is itself connected to host computer 930, 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 computer 930 may 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. Connections 921 and 922 between telecommunication network 910 and host computer 930 may extend directly from core network 914 to host computer 930 or may go via an optional intermediate network 920. Intermediate network 920 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 920, if any, may be a backbone network or the Internet; in particular, intermediate network 920 may comprise two or more sub-networks (not shown).

The communication system of FIGURE 11 as a whole enables connectivity between the connected UEs 991, 992 and host computer 930. The connectivity may be described as an over-the-top (OTT) connection 950. Host computer 930 and the connected UEs 991, 992 are configured to communicate data and/or signaling via OTT connection 950, using access network 911, core network 914, any intermediate network 920 and possible further infrastructure (not shown) as intermediaries. OTT connection 950 may be transparent in the sense that the participating communication devices through which OTT connection 950 passes are unaware of routing of uplink and downlink communications. For example, base station 912 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 930 to be forwarded (e.g., handed over) to a connected UE 991. Similarly, base station 912 need not be aware of the future routing of an outgoing uplink communication originating from the UE 991 towards the host computer 930.

FIGURE 12 illustrates a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments.

Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to FIGURE 12. In communication system 1000, host computer 1010 comprises hardware 1015 including communication interface 1016 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 1000. Host computer 1010 further comprises processing circuitry 1018, which may have storage and/or processing capabilities. In particular, processing circuitry 1018 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. Host computer 1010 further comprises software 1011, which is stored in or accessible by host computer 1010 and executable by processing circuitry 1018. Software 1011 includes host application 1012. Host application 1012 may be operable to provide a service to a remote user, such as UE 1030 connecting via OTT connection 1050 terminating at UE 1030 and host computer 1010. In providing the service to the remote user, host application 1012 may provide user data which is transmitted using OTT connection 1050.

Communication system 1000 further includes base station 1020 provided in a telecommunication system and comprising hardware 1025 enabling it to communicate with host computer 1010 and with UE 1030. Hardware 1025 may include communication interface 1026 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 1000, as well as radio interface 1027 for setting up and maintaining at least wireless connection 1070 with UE 1030 located in a coverage area (not shown in FIGURE 12) served by base station 1020. Communication interface 1026 may be configured to facilitate connection 1060 to host computer 1010. Connection 1060 may be direct or it may pass through a core network (not shown in FIGURE 12) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware 1025 of base station 1020 further includes processing circuitry 1028, 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 station 1020 further has software 1021 stored internally or accessible via an external connection.

Communication system 1000 further includes UE 1030 already referred to. Its hardware 1035 may include radio interface 1037 configured to set up and maintain wireless connection 1070 with a base station serving a coverage area in which UE 1030 is currently located. Hardware 1035 of UE 1030 further includes processing circuitry 1038, 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. UE 1030 further comprises software 1031, which is stored in or accessible by UE 1030 and executable by processing circuitry 1038. Software 1031 includes client application 1032. Client application 1032 may be operable to provide a service to a human or non-human user via UE 1030, with the support of host computer 1010. In host computer 1010, an executing host application 1012 may communicate with the executing client application 1032 via OTT connection 1050 terminating at UE 1030 and host computer 1010. In providing the service to the user, client application 1032 may receive request data from host application 1012 and provide user data in response to the request data. OTT connection 1050 may transfer both the request data and the user data. Client application 1032 may interact with the user to generate the user data that it provides.

It is noted that host computer 1010, base station 1020 and UE 1030 illustrated in FIGURE 12 may be similar or identical to host computer 930, one of base stations 912a, 912b, 912c and one of UEs 991, 992 of FIGURE 11, respectively. This is to say, the inner workings of these entities may be as shown in FIGURE 12 and independently, the surrounding network topology may be that of FIGURE 11.

In FIGURE 12, OTT connection 1050 has been drawn abstractly to illustrate the communication between host computer 1010 and UE 1030 via base station 1020, 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 UE 1030 or from the service provider operating host computer 1010, or both. While OTT connection 1050 is 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 connection 1070 between UE 1030 and base station 1020 is 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 UE 1030 using OTT connection 1050, in which wireless connection 1070 forms the last segment. More precisely, the teachings of these embodiments may improve the data rate, latency, and/or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, and/or extended battery lifetime.

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 connection 1050 between host computer 1010 and UE 1030, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection 1050 may be implemented in software 1011 and hardware 1015 of host computer 1010 or in software 1031 and hardware 1035 of UE 1030, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection 1050 passes; 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 software 1011, 1031 may compute or estimate the monitored quantities. The reconfiguring of OTT connection 1050 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 1020, and it may be unknown or imperceptible to base station 1020. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer 1010’ s measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software 1011 and 1031 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 1050 while it monitors propagation times, errors etc.

FIGURE 13 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 11 and 12. For simplicity of the present disclosure, only drawing references to FIGURE 13 will be included in this section. In step 1110, the host computer provides user data. In substep 1111 (which may be optional) of step 1110, the host computer provides the user data by executing a host application. In step 1120, the host computer initiates a transmission carrying the user data to the UE. In step 1130 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1140 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer. FIGURE 14 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 11 and 12. For simplicity of the present disclosure, only drawing references to FIGURE 14 will be included in this section. In step 1210 of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application. In step 1220, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1230 (which may be optional), the UE receives the user data carried in the transmission.

FIGURE 15 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 11 and 12. For simplicity of the present disclosure, only drawing references to FIGURE 15 will be included in this section. In step 1310 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 1320, the UE provides user data. In substep 1321 (which may be optional) of step 1320, the UE provides the user data by executing a client application. In substep 1311 (which may be optional) of step 1310, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep 1330 (which may be optional), transmission of the user data to the host computer. In step 1340 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

FIGURE 16 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 11 and 12. For simplicity of the present disclosure, only drawing references to FIGURE 16 will be included in this section. In step 1410 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 1420 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 1430 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

FIGURE 17 depicts a method 1500 by a wireless device 110, according to certain embodiments. At step 1502, the wireless device detects a BFR. In response to detecting the BFR, the wireless device initiates a RA procedure, at step 1504. At step 1506, prior to performing the RA procedure or while performing the RA procedure, the wireless device identifies data in a buffer for transmission on an uplink. At step 508, the wireless device transmits, to a network node, a message associated with the RA procedure. The message indicates an empty buffer status, and the data in the buffer is not transmitted on the uplink for a time period associated with the performance of at least a portion of the RA procedure.

In a particular embodiment, the empty buffer status indicates that there is no data in the buffer for transmission on the uplink.

In a particular embodiment, the message includes padding, and the padding indicates the empty buffer status.

In a particular embodiment, the message includes a BSR value of 0, and the BSR value of 0 indicates the empty buffer status.

In a particular embodiment, the message includes a BSR value of 0 and padding, and the BSR value of 0 and the padding indicate the empty buffer status.

In a particular embodiment, the message transmitted to the network node indicating the empty buffer status comprises a third message (Msg3) of the RA procedure. In a further particular embodiment, the wireless device determines not to include the data in the buffer in the Msg3, and the time period associated with the performance of the at least a portion of the RA procedure extends past the transmission of the Msg3.

In a particular embodiment, the message transmitted to the network node indicating the empty buffer status comprises a fifth message (Msg5) of the RA procedure. In a further particular embodiment, prior to transmitting the Msg5, the wireless device receives a fourth message (Msg4) of the RA procedure from the network node. The Msg4 is a Physical Downlink Control Channel (PDCCH) transmission comprising an uplink grant authorizing the wireless device to transmit the Msg5 on an uplink shared data channel. In a further particular embodiment, the wireless device determines not to include the data in the buffer in the Msg5, and the time period associated with the performance of the at least a portion of the RA procedure extends past the transmission of the Msg5.

In a particular embodiment, initiating the RA procedure comprises transmitting a first message (Msgl) of the RA procedure.

In a particular embodiment, the time period begins before the message is transmitted.

In a particular embodiment, the wireless device starts a timer. The timer represents the time period associated with the RA procedure and/or an expiration of the timer marks an end of the time period associated with the RA procedure. In a further particular embodiment, the wireless device detects the expiration of the timer and transmits the data in the buffer.

In a particular embodiment, the wireless device has an active resource associated with a SR-PUCCH.

In a particular embodiment, the wireless device has released a resource associated with a SR-PUCCH.

FIGURE 18 illustrates a schematic block diagram of a virtual apparatus 1600 in a wireless network (for example, the wireless network shown in FIGURE 6). The apparatus may be implemented in a wireless device or network node (e.g., wireless device 610 or network node 660 shown in FIGURE 6). Apparatus 1600 is operable to carry out the example method described with reference to FIGURE 17 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 17 is not necessarily carried out solely by apparatus 1600. At least some operations of the method can be performed by one or more other entities.

Virtual Apparatus 1600 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause detecting module 1610, initiating module 1620, identifying module 1630, transmitting module 1640, and any other suitable units of apparatus 1600 to perform corresponding functions according one or more embodiments of the present disclosure.

According to certain embodiments, detecting module 1610 may perform certain of the detecting functions of the apparatus 1600. For example, detecting modulel610 may detect a BFR.

According to certain embodiments, initiating module 1620 may perform certain of the initiating functions of the apparatus 1600. For example, initiating module 1620 may initiate a RA procedure in response to the detection of the BFR by the detecting module 1610.

According to certain embodiments, identifying module 1630 may perform certain of the identifying functions of the apparatus 1600. For example, identifying module 1630 may identify data in a buffer for transmission on an uplink. The identification of the data in the buffer may be prior to performing the RA procedure or at any point during the performance of the RA procedure.

According to certain embodiments, transmitting module 1640 may perform certain of the transmitting functions of the apparatus 1600. For example, transmitting module 1640 may transmit, to a network node, a message associated with the RA procedure. According to certain embodiments, the message indicates an empty buffer status, and the data in the buffer is not transmitted on the uplink for a time period associated with the performance of at least a portion of the RA procedure.

The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.

FIGURE 19 depicts a method 1700 by a network node 660, according to certain embodiments. At step 1702, the network node receives, from a wireless device, a message associated with a RA procedure, and the message indicates a buffer status of the wireless device. Based on the buffer status, the wireless device determines a cause for an initiation of the RA procedure by the wireless device, at step 1704. According to certain embodiments, the cause being determined to be a BFR or a release of a resource associated with a SR-PUCCH.

In a particular embodiment, the network node takes an action based on the cause for the initiation of the RA procedure. For example, if the network node determines that the cause for the RA procedure is the release of the resource associated with the SR-PUCCH, the network node may reinitiate the SR. Alternatively, if the network node determines that the cause for the RA procedure is the BFR, the network node may forego reinitiating the SR-PUCCH if the network node determines that the cause for the RA procedure is the BFR.

In a particular embodiment, the buffer status indicates that there is data in a buffer of the wireless device for transmission on the uplink. Based on the buffer status indicating that there is data in the buffer of the wireless device, the network node may determine that the cause for the initiation of the RA procedure is the release of the resource associated with the SR-PUCCH.

In a particular embodiment, the message may include a Buffer Status Report (BSR) value of greater than 0. Based on the BSR value being greater than 0, the network node may determine that the wireless device has data in the buffer. In a particular embodiment, this may indicate to the network node that the cause for the initiation of the RA procedure is the release of the resource associated with the SR- PUCCH.

In another particular embodiment, the buffer status may indicate an empty buffer status. Based on the empty buffer status, the network node may determine that the cause for the initiation of the RA procedure is the BFR. For example, in a further particular embodiment, the message may include padding, and the network node may determine the empty buffer status and/or the cause of the RA procedure being the BFR based on the padding.

As another example, in a further particular embodiment, the message may include a BSR value of 0, and the network node may determine the empty buffer status and/or the cause of the RA procedure as being the BFR based on the BSR value of 0.

As still another example, in a further particular embodiment, the message may include padding and a BSR value of 0, and the network node may determine the empty buffer status and/or the cause of the RA procedure as being the BFR based on the padding and the BSR value of 0.

In a particular embodiment, the message comprises a third message (Msg3) of the RA procedure.

In another particular embodiment, the message comprises a fifth message (Msg5) of the RA procedure. In a further particular embodiment, prior to receiving the Msg5, the network node may transmit a fourth message (Msg4) of the RA procedure to the wireless device. The Msg4 may be a Physical Downlink Control Channel (PDCCH) transmission comprising an uplink grant authorizing the wireless device to transmit the Msg5 on an uplink shared data channel.

In a particular embodiment, the network node may configure the wireless device not to transmit any data stored in a buffer of the wireless device during a time period associated with the RA procedure.

In a particular embodiment, the network node may configure the wireless device to start a timer during the RA procedure. The timer may represent the time period associated with the RA procedure and/or an expiration of the timer may mark an end of the time period associated with the RA procedure.

FIGURE 20 illustrates a schematic block diagram of a virtual apparatus 1800 in a wireless network (for example, the wireless network shown in FIGURE 6). The apparatus may be implemented in a wireless device or network node (e.g., wireless device 610 or network node 660 shown in FIGURE 6). Apparatus 1800 is operable to carry out the example method described with reference to FIGURE 19 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 19 is not necessarily carried out solely by apparatus 1800. At least some operations of the method can be performed by one or more other entities.

Virtual Apparatus 1800 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause receiving module 1810, determining module 1820, and any other suitable units of apparatus 1800 to perform corresponding functions according one or more embodiments of the present disclosure.

According to certain embodiments, receiving module 1810 may perform certain of the receiving functions of the apparatus 1800. For example, receiving module 1810 may receive, from a wireless device, a message associated with a RA procedure, and the message indicates a buffer status of the wireless device.

According to certain embodiments, determining module 1820 may perform certain of the determining functions of the apparatus 1800. For example, determining module 1820 may determine a cause for an initiation of the RA procedure by the wireless device based on the buffer status. According to certain embodiments, the cause being determined to be a BFR or a release of a resource associated with a SR-PUCCH. The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein. FIGURE 21 depicts another method 1900 by a wireless device 610, according to certain embodiments. At step 1902, prior to performing a RA procedure or while performing the RA procedure, the wireless device 610 identifies data in a buffer for transmission on an uplink. While the data is in the buffer, the wireless device 610 transmits, to a network node 660, a message associated with the RA procedure, at step 1904. The message indicates an empty buffer status. At step 1906, the wireless device 610 forgoes transmitting the data in the buffer on the uplink for a time period associated with a performance of at least a portion of the RA procedure.

In a particular embodiment, wireless device 610 detects a beam failure recovery and, in response to detecting the beam failure recovery, transmits a first message, Msgl, of the RA procedure to initiate the RA procedure.

In a particular embodiment, the empty buffer status indicates to the network node that there is no data in the buffer for transmission on the uplink.

In a particular embodiment, the message comprises padding, and the padding indicates the empty buffer status.

In a particular embodiment, the message comprises a BSR value of 0, and wherein the BSR value of 0 indicates the empty buffer status.

In a particular embodiment, the message comprises a BSR value of 0 and padding. The padding indicates the empty buffer status.

In a particular embodiment, the message transmitted to the network node indicating the empty buffer status comprises a third message, Msg3, of the RA procedure.

In a further particular embodiment, the Msg3 does not include the data in the buffer, and the time period associated with the performance of the at least a portion of the RA procedure extends past the transmission of the Msg3.

In a particular embodiment, the message transmitted to the network node indicating the empty buffer status comprises a fifth message, Msg5, of the RA procedure.

In a further particular embodiment, prior to transmitting the Msg5, the wireless device 610 receives a fourth message, Msg4, of the RA procedure from the network node. The Msg4 includes a PDCCH transmission comprising an uplink grant authorizing the wireless device to transmit the Msg5 on an uplink shared data channel.

In a further particular embodiment, the Msg5 does not include the data in the buffer, and the time period associated with the performance of the at least a portion of the RA procedure extends past the transmission of the Msg5.

In a particular embodiment, the wireless device 610 starts a timer, which represents the time period associated with the RA procedure. Alternatively, an expiration of the timer marks an end of the time period associated with the RA procedure.

In a further particular embodiment, the wireless device 610 detects the expiration of the timer and transmits the data in the buffer in response to the expiration of the timer.

In a particular embodiment, the wireless device 610 has an active resource associated with a SR-PUCCH.

In a particular embodiment, the wireless device 610 has released a resource associated with a SR-PUCCH.

FIGURE 22 depicts another method 2000 by a network node 660, according to certain embodiments. At step 2002, the network node 660 receives, from a wireless device 610, a message associated with a RA procedure. The message indicates a buffer status of the wireless device. At step 2004, based on the buffer status, the network node 660 determines a cause for an initiation of the RA procedure by the wireless device. The cause is determined to be a BFR or a release of a resource associated with a SR-PUCCH.

In a particular embodiment, the network node 660 takes an action based on the cause for the initiation of the RA procure. For example, if the cause for the RA procedure is determined to be the release of the resource associated with the SR- PUCCH, the network node 660 reinitiates the SR-PUCCH. As another example, if the cause for the RA procedure is determined to be the BFR, the network node 660 forgoes reinitiating the SR-PUCCH. In a particular embodiment, the buffer status indicates that there is data in a buffer of the wireless device for transmission on the uplink and, based on the buffer status indicating that there is data in the buffer of the wireless device, the network node 660 determines that the cause for the initiation of the RA procedure is the release of the resource associated with the SR-PUCCH.

In a particular embodiment, the message comprises a BSR value of greater than 0, and the network node 660 determines that the wireless device 610 has data in the buffer based on the BSR value being greater than 0.

In a particular embodiment, the buffer status indicates an empty buffer status and, based on the empty buffer status, the network node determines that the cause for the initiation of the RA procedure is the BFR.

In a particular embodiment, the message comprises padding, and the network node determines the empty buffer status based on the padding.

In a particular embodiment, the message comprises a BSR value of 0, and the network node 660 determines the empty buffer status based on the BSR value of 0.

In a further particular embodiment, the message comprises padding and a BSR value of 0, and the network node 660 determines the empty buffer status based on the padding and the BSR value of 0.

In a particular embodiment, the message comprises a third message, Msg3, of the RA procedure.

In a particular embodiment, the message comprises a fifth message, Msg5, of the RA procedure.

In a particular embodiment, prior to receiving the Msg5, the network node 660 transmits a fourth message, Msg4, of the RA procedure to the wireless device 610. The Msg4 includes a PDCCH transmission comprising an uplink grant authorizing the wireless device to transmit the Msg5 on an uplink shared data channel.

In a particular embodiment, the network node 660 configures the wireless device 610 not to transmit any data stored in a buffer of the wireless device 610 during a time period associated with the RA procedure.

In a particular embodiment, the network node 660 configures the wireless device 610 to start a timer during the RA procedure, and the timer represents the timer period associated with the RA procedure and/or wherein an expiration of the timer marks an end of the time period associated with the RA procedure.

EXAMPLE EMBODIMENTS

The following are example embodiments of the present disclosure. In the examples, cross-references to a particular embodiment (such as embodiment 1) may refer to that embodiment (e.g., embodiment 1) and/or any of its sub-embodiment(s).

Grow A Example Embodiments

Example Embodiment Al. A method by a wireless device comprising: detecting a beam failure recovery (BFR); in response to detecting the BFR, initiating a random access (RA) procedure; prior to performing the RA procedure or while performing the RA procedure, identifying data in a buffer for transmission on an uplink; and transmitting, to a network node, a message associated with the RA procedure, the message indicating an empty buffer status, and wherein the data in the buffer is not transmitted on the uplink for a time period associated with the performance of at least a portion of the RA procedure.

Example Embodiment A2. The method of Example Embodiment Al, wherein the empty buffer status indicates to the network node that there is no data in the buffer for transmission on the uplink.

Example Embodiment A3. The method of any one of Example Embodiments Al to A2, wherein the message comprises padding, and wherein the padding indicates the empty buffer status.

Example Embodiment A4. The method of any one of Example Embodiments Al to A2, wherein the message comprises a Buffer Status Report (BSR) value of 0, and wherein the BSR value of 0 indicates the empty buffer status.

Example Embodiment A5. The method of any one of Example Embodiments Al to A2, wherein the message comprises a Buffer Status Report (BSR) value of 0 and padding, wherein the BSR value of 0 and the padding indicate the empty buffer status. Example Embodiment A6. The method of any one of Example Embodiments A1 to A5, wherein the message transmitted to the network node indicating the empty buffer status comprises a third message (Msg3) of the RA procedure.

Example Emboidment A7. The method of Example Embodiment A6, further comprising determining not to include the data in the buffer in the Msg3, wherein the time period associated with the performance of the at least a portion of the RA procedure extends past the transmission of the Msg3.

Example Embodiment A8. The method of any one of Example Embodiments A1 to A5, wherein the message transmitted to the network node indicating the empty buffer status comprises a fifth message (Msg5) of the RA procedure.

Example Embodiment A9. The method of Example Embodiment A8, further comprising: prior to transmitting the Msg5, receiving a fourth message (Msg4) of the RA procedure from the network node, the Msg4 comprising a Physical Downlink Control Channel (PDCCH) transmission comprising an uplink grant authorizing the wireless device to transmit the Msg5 on an uplink shared data channel.

Example Emboidment A10. The method of any one of Example

Embodiments A8 to A9, further comprising determining not to include the data in the buffer in the Msg5, wherein the time period associated with the performance of the at least a portion of the RA procedure extends past the transmission of the Msg5.

Example Embodiment A11. The method of any one of Example

Embodiments A1 to A10, wherein initiating the RA procedure comprises transmitting a first message (Msgl) of the RA procedure.

Example Emboidment A12. The method of any one of Example

Embodiments A1 to All, wherein the time period begins before the message is transmitted.

Example Embodiment A13. The method of any one of Example

Embodiments A1 to A12, further comprising starting a timer, and wherein the timer represents the timer period associated with the RA procedure and/or wherein an expiration of the timer marks an end of the time period associated with the RA procedure. Example Embodiment A14. The method of Example Embodiment A14, further comprising detecting the expiration of the timer and transmitting the data in the buffer.

Example Embodiment A15. The method of any one of Example

Embodiments A1 to A14, wherein the wireless device has an active resource associated with a scheduling request-physical uplink control channel (SR-PUCCH)

Example Embodiment A16. The method of any one of Example

Embodiments A1 to A14, wherein the wireless device has released a resource associated with a scheduling request-physical uplink control channel (SR-PUCCH)

Example Embodiment A17. A wireless device comprising processing circuitry configured to perform any of the methods of Example Embodiments A1 to A16.

Example Embodiment A18. A computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments A1 to A16.

Example Embodiment A19. A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments A1 to A16.

Example Embodiment A20. A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of Example Embodiments A1 to A16.

Group B Embodiments

Example Embodiment Bl. A method by a network node comprising: receiving, from a wireless device, a message associated with a random access (RA) procedure, the message indicating a buffer status of the wireless device; and based on the buffer status, determining a cause for an initiation of the RA procedure by the wireless device, the cause being determined to be: a buffer failure recovery (BFR), or a release of a resource associated with a scheduling request-physical uplink control channel (SR-PUCCH). Example Embodiment B2. The method of Example Embodiment B 1, further comprising taking an action based on the cause for the initiation of the RA procure, wherein taking the action comprises: if the cause for the RA procedure is determined to be the release of the resource associated with the SR-PUCCH, reinitiating the SR- PUCCH; or if the cause for the RA procedure is determined to be the BFR, forgoing reinitiating the SR-PUCCH

Example Embodiment B3. The method of any one of Example Embodiments B1 to B2, wherein: the buffer status indicates that there is data in a buffer of the wireless device for transmission on the uplink, and based on the buffer status indicating that there is data in the buffer of the wireless device, the network node determines that the cause for the initiation of the RA procedure is the release of the resource associated with the SR-PUCCH.

Example Emboidment B4. The method of Example Embodiment B3, wherein: the message comprises a Buffer Status Report (BSR) value of greater than 0, and the network node determines that the wireless device has data in the buffer based on the BSR value being greater than 0.

Example Embodiment B5. The method of Example Embodiment Bl, wherein: the buffer status indicates an empty buffer status, and based on the empty buffer status, the network node determines that the cause for the initiation of the RA procedure is the BFR.

Example Emboidment B6. The method of Example Embodiment B5, wherein: the message comprises padding, and the network node determines the empty buffer status based on the padding.

Example Embodiment B7. The method of Example Embodiment B5, wherein: the message comprises a Buffer Status Report (BSR) value of 0, and the network node determines the empty buffer status based on the BSR value of 0.

Example Embodiment B8. The method of Example Embodiment B5, wherein: the message comprises padding and a Buffer Status Report (BSR) value of 0, and the network node determines the empty buffer status based on the padding and the BSR value of 0. Example Embodiment B9. The method of any one of Example Embodiments B1 to B8, wherein the message comprises a third message (Msg3) of the RA procedure.

Example Embodiment BIO. The method of any one of Example Embodiments B1 to B8, wherein the message comprises a fifth message (Msg5) of the RA procedure.

Example Embodiment B11. The method of Example Embodiment BIO, further comprising: prior to receiving the Msg5, transmitting a fourth message (Msg4) of the RA procedure to the wireless device, the Msg4 comprising a Physical Downlink Control Channel (PDCCH) transmission comprising an uplink grant authorizing the wireless device to transmit the Msg5 on an uplink shared data channel.

Example Emboidment B12.The method of any one of Example Embodiments B1 to Bll, further comprising: configuring the wireless device not to transmit any data stored in a buffer of the wireless device during a time period associated with the RA procedure.

Example Embodiment B 13. The method of Example Embodiment B12, further comprising: configuring the wireless device to start a timer during the RA procedure, and wherein the timer represents the timer period associated with the RA procedure and/or wherein an expiration of the timer marks an end of the time period associated with the RA procedure.

Example Embodiment B 14. A network node comprising processing circuitry configured to perform any of the methods of Example Embodiments B1 to B13.

Example Embodiment B 15. A computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments B1 to B13.

Example Embodiment B 16. A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments B 1 to B13. Example Embodiment B 17. A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of Example Embodiments B1 to B13.

Group C Example Embodiments

Example Embodiment Cl. A wireless device comprising: processing circuitry configured to perform any of the steps of any of Example Embodiments A1 to A15; and power supply circuitry configured to supply power to the wireless device.

Example Embodiment C2. A network node comprising: processing circuitry configured to perform any of the steps of any of Example Embodiments B1 to B13; power supply circuitry configured to supply power to the wireless device.

Example Embodiment C3. A wireless device, the wireless device comprising: an antenna configured to send and receive wireless signals; radio front- end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of Example Embodiments A1 to A15; an input interface connected to the processing circuitry and configured to allow input of information into the wireless device to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the wireless device that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the wireless device.

Example Embodiment C4. A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a wireless device, wherein the cellular network comprises a network node having a radio interface and processing circuitry, the network node’s processing circuitry configured to perform any of the steps of any of Example Embodiments B 1 to B13.

Example Embodiment C5. The communication system of the pervious embodiment further including the network node. Example Embodiment C6. The communication system of the previous 2 embodiments, further including the wireless device, wherein the wireless device is configured to communicate with the network node.

Example Embodiment C7. The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the wireless device comprises processing circuitry configured to execute a client application associated with the host application.

Example Embodiment C8. A method implemented in a communication system including a host computer, a network node and a wireless device, the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the wireless device via a cellular network comprising the network node, wherein the network node performs any of the steps of any of Example Embodiments B1 to B13.

Example Embodiment C9. The method of the previous embodiment, further comprising, at the network node, transmitting the user data.

Example Embodiment CIO. The method of the previous 2 embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the wireless device, executing a client application associated with the host application.

Example Embodiment Cl 1. A wireless device configured to communicate with a network node, the wireless device comprising a radio interface and processing circuitry configured to performs the of the previous 3 embodiments.

Example Embodiment C12. A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward user data to a cellular network for transmission to a wireless device, wherein the wireless device comprises a radio interface and processing circuitry, the wireless device’s components configured to perform any of the steps of any of Example Embodiments A1 to A15.

Example Embodiment Cl 3. The communication system of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the wireless device. Example Embodiment C14. The communication system of the previous 2 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the wireless device’s processing circuitry is configured to execute a client application associated with the host application.

Example Embodiment Cl 5. A method implemented in a communication system including a host computer, a network node and a wireless device, the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the wireless device via a cellular network comprising the network node, wherein the wireless device performs any of the steps of any of Example Embodiments A1 to A15.

Example Embodiment Cl 6. The method of the previous embodiment, further comprising at the wireless device, receiving the user data from the network node.

Example Embodiment C17. A communication system including a host computer comprising: communication interface configured to receive user data originating from a transmission from a wireless device to a network node, wherein the wireless device comprises a radio interface and processing circuitry, the wireless device’s processing circuitry configured to perform any of the steps of any of Example Embodiments A1 to A15.

Example Embodiment Cl 8. The communication system of the previous embodiment, further including the wireless device.

Example Embodiment Cl 9. The communication system of the previous 2 embodiments, further including the network node, wherein the network node comprises a radio interface configured to communicate with the wireless device and a communication interface configured to forward to the host computer the user data carried by a transmission from the wireless device to the network node.

Example Embodiment C20. The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; and the wireless device’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data. Example Embodiment C21. The communication system of the previous 4 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and the wireless device’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.

Example Embodiment C22. A method implemented in a communication system including a host computer, a network node and a wireless device, the method comprising: at the host computer, receiving user data transmitted to the network node from the wireless device, wherein the wireless device performs any of the steps of any of Example Embodiments A1 to A15.

Example Embodiment C23.The method of the previous embodiment, further comprising, at the wireless device, providing the user data to the network node.

Example Embodiment C24. The method of the previous 2 embodiments, further comprising: at the wireless device, executing a client application, thereby providing the user data to be transmitted; and at the host computer, executing a host application associated with the client application.

Example Embodiment C25. The method of the previous 3 embodiments, further comprising: at the wireless device, executing a client application; and at the wireless device, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application, wherein the user data to be transmitted is provided by the client application in response to the input data.

Example Embodiment C26. A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a wireless device to a network node, wherein the network node comprises a radio interface and processing circuitry, the network node’s processing circuitry configured to perform any of the steps of any of Example Embodiments B1 to B13.

Example Embodiment C27. The communication system of the previous embodiment further including the network node. Example Embodiment C28. The communication system of the previous 2 embodiments, further including the wireless device, wherein the wireless device is configured to communicate with the network node.

Example Embodiment C29. The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; the wireless device is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.

Example Embodiment C30. A method implemented in a communication system including a host computer, a network node and a wireless device, the method comprising: at the host computer, receiving, from the base station, user data originating from a transmission which the network node has received from the wireless device, wherein the wireless device performs any of the steps of any of Example Embodiments A1 to A15.

Example Embodiment C31.The method of the previous embodiment, further comprising at the network node receiving the user data from the wireless device.

Example Embodiment C32. The method of the previous 2 embodiments, further comprising at the network node, initiating a transmission of the received user data to the host computer.

Example Embodiment C33.The method of any of the previous embodiments, wherein the network node comprises a base station.

Example Embodiment C34.The method of any of the previous embodiments, wherein the wireless device comprises a user equipment (TIE).

Modifications, additions, or omissions may be made to the systems and apparatuses described herein without departing from the scope of the disclosure. 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. Modifications, additions, or omissions may be made to the methods 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.

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.

Claims

1. A method by a wireless device comprising: prior to performing a random access, RA, procedure or while performing the RA procedure, identifying data in a buffer for transmission on an uplink; and while the data is in the buffer, transmitting, to a network node, a message associated with the RA procedure, the message indicating an empty buffer status, and forgoing transmitting the data in the buffer on the uplink for a time period associated with a performance of at least a portion of the RA procedure.

2. The method of Claim 1, further comprising: detecting a beam failure recovery; and in response to detecting the beam failure recovery, transmitting a first message, Msgl, of the RA procedure to initiate the RA procedure.

3. The method of any one of Claims 1 to 2, wherein the empty buffer status indicates to the network node that there is no data in the buffer for transmission on the uplink.

4. The method of any one of Claims 1 to 3, wherein the message comprises padding, and wherein the padding indicates the empty buffer status.

5. The method of any one of Claims 1 to 3, wherein the message comprises a Buffer Status Report, BSR, value of 0, and wherein the BSR value of 0 indicates the empty buffer status.

6. The method of any one of Claims 1 to 3, wherein the message comprises a Buffer Status Report, BSR, value of 0 and padding, wherein the BSR value of 0 and the padding indicate the empty buffer status.

7. The method of any one of Claims 1 to 6, wherein the message transmitted to the network node indicating the empty buffer status comprises a third message, Msg3, of the RA procedure.

8. The method of Claim 7, wherein the Msg3 does not include the data in the buffer, wherein the time period associated with the performance of the at least a portion of the RA procedure extends past the transmission of the Msg3.

9. The method of any one of Claims 1 to 6, wherein the message transmitted to the network node indicating the empty buffer status comprises a fifth message, Msg5, of the RA procedure.

10. The method of Claim 9, further comprising: prior to transmitting the Msg5, receiving a fourth message, Msg4, of the RA procedure from the network node, the Msg4 comprising a Physical Downlink Control Channel, PDCCH, transmission comprising an uplink grant authorizing the wireless device to transmit the Msg5 on an uplink shared data channel.

11. The method of any one of Claims 9 to 10, wherein the Msg5 does not include the data in the buffer, wherein the time period associated with the performance of the at least a portion of the RA procedure extends past the transmission of the Msg5.

12. The method of any one of Claims 1 to 11, wherein the time period begins before the message is transmitted.

13. The method of any one of Claims 1 to 12, further comprising starting a timer, and wherein the timer represents the time period associated with the RA procedure and/or wherein an expiration of the timer marks an end of the time period associated with the RA procedure.

14. The method of Claim 14, further comprising detecting the expiration of the timer and transmitting the data in the buffer in response to the expiration of the timer.

15. The method of any one of Claims 1 to 14, wherein the wireless device has an active resource associated with a scheduling request-physical uplink control channel, SR-PUCCH.

16. The method of any one of Claims 1 to 14, wherein the wireless device has released a resource associated with a scheduling request-physical uplink control channel, SR-PUCCH.

17. A method by a network node comprising: receiving, from a wireless device, a message associated with a random access (RA) procedure, the message indicating a buffer status of the wireless device; and based on the buffer status, determining a cause for an initiation of the RA procedure by the wireless device, the cause being determined to be: a buffer failure recovery, BFR, or a release of a resource associated with a scheduling request-physical uplink control channel, SR-PUCCH.

18. The method of Claim 17, further comprising taking an action based on the cause for the initiation of the RA procure, wherein taking the action comprises: if the cause for the RA procedure is determined to be the release of the resource associated with the SR-PUCCH, reinitiating the SR-PUCCH; or if the cause for the RA procedure is determined to be the BFR, forgoing reinitiating the SR-PUCCH.

19. The method of any one of Claims 17 to 18, wherein: the buffer status indicates that there is data in a buffer of the wireless device for transmission on the uplink, and based on the buffer status indicating that there is data in the buffer of the wireless device, the network node determines that the cause for the initiation of the RA procedure is the release of the resource associated with the SR-PUCCH.

20. The method of Claim 19, wherein: the message comprises a Buffer Status Report, BSR, value of greater than 0, and the network node determines that the wireless device has data in the buffer based on the BSR value being greater than 0.

21. The method of Claim 17, wherein: the buffer status indicates an empty buffer status, and based on the empty buffer status, the network node determines that the cause for the initiation of the RA procedure is the BFR.

22. The method of Claim 21, wherein: the message comprises padding, and the network node determines the empty buffer status based on the padding.

23. The method of Claim 21, wherein: the message comprises a Buffer Status Report, BSR, value of 0, and the network node determines the empty buffer status based on the BSR value of 0.

24. The method of Claim 21, wherein: the message comprises padding and a Buffer Status Report, BSR, value of 0, and the network node determines the empty buffer status based on the padding and the BSR value of 0.

25. The method of any one of Claims 17 to 24, wherein the message comprises a third message, Msg3, of the RA procedure.

26. The method of any one of Claims 17 to 24, wherein the message comprises a fifth message, Msg5, of the RA procedure.

27. The method of Claim 26, further comprising: prior to receiving the Msg5, transmitting a fourth message, Msg4, of the RA procedure to the wireless device, the Msg4 comprising a Physical Downlink Control Channel, PDCCH, transmission comprising an uplink grant authorizing the wireless device to transmit the Msg5 on an uplink shared data channel.

28. The method of any one of Claims 17 to 27, further comprising: configuring the wireless device not to transmit any data stored in a buffer of the wireless device during a time period associated with the RA procedure.

29. The method of any one of Claims 17 to 28, further comprising: configuring the wireless device to start a timer during the RA procedure, and wherein the timer represents the timer period associated with the RA procedure and/or wherein an expiration of the timer marks an end of the time period associated with the RA procedure.

30. A wireless device comprising processing circuitry configured to: prior to performing a random access, RA, procedure or while performing the RA procedure, identify data in a buffer for transmission on an uplink; and while the data is in the buffer, transmit, to a network node, a message associated with the RA procedure, the message indicating an empty buffer status, and forgo transmitting the data in the buffer on the uplink for a time period associated with a performance of at least a portion of the RA procedure.

31. The wireless device of Claim 30, wherein the processing circuitry is further configured to: detect a beam failure recovery; and in response to detecting the beam failure recovery, transmit a first message, Msgl, of the RA procedure to initiate the RA procedure.

32. The wireless device of any one of Claims 30 to 31, wherein the empty buffer status indicates to the network node that there is no data in the buffer for transmission on the uplink.

33. The wireless device of any one of Claims 30 to 32, wherein the message comprises padding, and wherein the padding indicates the empty buffer status.

34. The wireless device of any one of Claims 30 to 32, wherein the message comprises a Buffer Status Report, BSR, value of 0, and wherein the BSR value of 0 indicates the empty buffer status.

35. The wireless device of any one of Claims 30 to 32, wherein the message comprises a Buffer Status Report, BSR, value of 0 and padding, wherein the BSR value of 0 and the padding indicate the empty buffer status.

36. The wireless device of any one of Claims 30 to 35, wherein the message transmitted to the network node indicating the empty buffer status comprises a third message, Msg3, of the RA procedure.

37. The wireless device of Claim 36, wherein the Msg3 does not include the data in the buffer, wherein the time period associated with the performance of the at least a portion of the RA procedure extends past the transmission of the Msg3.

38. The wireless device of any one of Claims 30 to 36, wherein the message transmitted to the network node indicating the empty buffer status comprises a fifth message, Msg5, of the RA procedure.

39. The wireless device of Claim 38, wherein the processing circuitry is configured to: prior to transmitting the Msg5, receive a fourth message, Msg4, of the RA procedure from the network node, and wherein the Msg4 comprising a PDCCH transmission comprising an uplink grant authorizing the wireless device to transmit the Msg5 on an uplink shared data channel.

40. The wireless device of any one of Claims 38 to 39, wherein the Msg5 does not include the data in the buffer, wherein the time period associated with the performance of the at least a portion of the RA procedure extends past the transmission of the Msg5.

41. The wireless device of any one of Claims 30 to 40, wherein the time period begins before the message is transmitted.

42. The wireless device of any one of Claims 30 to 41, wherein the processing circuitry is configured to start a timer, and wherein the timer represents the time period associated with the RA procedure and/or wherein an expiration of the timer marks an end of the time period associated with the RA procedure.

43. The wireless device of Claim 42, wherein the processing circuitry is configured to detect the expiration of the timer and transmit the data in the buffer in response to the expiration of the timer.

44. The wireless device of any one of Claims 30 to 43, wherein the wireless device has an active resource associated with a scheduling request-physical uplink control channel, SR-PUCCH.

45. The wireless device of any one of Claims 1 to 14, wherein the wireless device has released a resource associated with a scheduling request-physical uplink control channel, SR-PUCCH.

46. A network node comprising processing circuitry configured: receive, from a wireless device, a message associated with a random access (RA) procedure, the message indicating a buffer status of the wireless device; and based on the buffer status, determine a cause for an initiation of the RA procedure by the wireless device, the cause being determined to be: a buffer failure recovery, BFR, or a release of a resource associated with a scheduling request-physical uplink control channel, SR-PUCCH.

47. The network node of Claim 46, wherein the processing circuitry is configured to take an action based on the cause for the initiation of the RA procure, wherein taking the action comprises: if the cause for the RA procedure is determined to be the release of the resource associated with the SR-PUCCH, reinitiating the SR-PUCCH; or if the cause for the RA procedure is determined to be the BFR, forgoing reinitiating the SR-PUCCH.

48. The network node of any one of Claims 46 to 47, wherein: the buffer status indicates that there is data in a buffer of the wireless device for transmission on the uplink, and based on the buffer status indicating that there is data in the buffer of the wireless device, the processing circuitry is configured to determine that the cause for the initiation of the RA procedure is the release of the resource associated with the SR-PUCCH.

49. The network node of Claim 48, wherein: the message comprises a Buffer Status Report, BSR, value of greater than 0, and the processing circuitry is configured to determine that the wireless device has data in the buffer based on the BSR value being greater than 0.

50. The network node of Claim 46, wherein: the buffer status indicates an empty buffer status, and based on the empty buffer status, the processing circuitry is configured to determine that the cause for the initiation of the RA procedure is the BFR.

51. The network node of Claim 50, wherein: the message comprises padding, and the processing circuitry is configured to determine the empty buffer status based on the padding.

52. The network node of Claim 51, wherein: the message comprises a Buffer Status Report, BSR, value of 0, and the processing circuitry is configured to determine the empty buffer status based on the BSR value of 0.

53. The network node of Claim 50, wherein: the message comprises padding and a Buffer Status Report, BSR, value of 0, and the processing circuitry is configured to determine the empty buffer status based on the padding and the BSR value of 0.

54. The network node of any one of Claims 46 to 53, wherein the message comprises a third message, Msg3, of the RA procedure.

55. The network node of any one of Claims 46 to 53, wherein the message comprises a fifth message, Msg5, of the RA procedure.

56. The network node of Claim 55, wherein the processing circuitry is configured to : prior to receiving the Msg5, transmit a fourth message, Msg4, of the RA procedure to the wireless device, the Msg4 comprising a Physical Downlink Control Channel, PDCCH, transmission comprising an uplink grant authorizing the wireless device to transmit the Msg5 on an uplink shared data channel.

57. The network node of any one of Claims 46 to 56, further comprising: configuring the wireless device not to transmit any data stored in a buffer of the wireless device during a time period associated with the RA procedure.

58. The network node of any one of Claims 46 to 57, wherein the processing circuitry is configured to: configure the wireless device to start a timer during the RA procedure, and wherein the timer represents the timer period associated with the RA procedure and/or wherein an expiration of the timer marks an end of the time period associated with the RA procedure.