TWI793872B - Enhanced beam failure recovery detection - Google Patents

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

Beam Fault Recovery (BFR) is a 3rd Generation Partnership Project (3GPP) standardized feature that enables fast user equipment (UE) recovery under fluctuating radio conditions. After detecting a beam failure, a UE will make random access attempts to restore 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 can be configured with zero, one or multiple SR configurations. An SR configuration corresponds to one or more logical channels, which or the like 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, which occur periodically in time. Certain embodiments described herein use one logical channel, one SR and one PUCCH (SR-PUCCH).

The SR configuration has an SR_COUNTER. When a UE has pending uplink profile and its SR is pending (=1), the UE will notify the gNodeB (gNB) with its periodic SR-PUCCH resource. Whenever a transmission occurs on the SR-PUCCH resource, SR_COUNTER updated (+1).

Once the gNB allows the UE to transmit its full amount of pending uplink data, the UE resets its SR_COUNTER. Alternatively, the UE resets SR_COUNTER when the UE transmits a buffer status report (BSR) containing buffer status depending on (and including) the pending data present.

If SR_COUNTER reaches its maximum value, the UE shall remove its SR-PUCCH resources. If this happens, the UE will no longer be able to use SR-PUCCH resources. From this point on, the UE will use the Random Access Channel (RACH) to inform the gNB about the pending uplink data to be transmitted. See 3GPP TS 38.321, chapter 5.4.4.

In both cases, random access (RA) attempts are sent by the UE in connected mode. Information about the UE's connection status can be determined from the Cell Radio Network Temporary Identifier (C-RNTI) received in Msg3.

FIG. 1 illustrates steps for performing RA by a UE. As shown, in step 100, it is determined whether a Msg1 is detected. If Msg1 is detected, a Msg2 is transmitted in step 101 . In step 102, it is determined whether the CRC of a Msg3 received from the network is okay. If the CRC of Msg3 is good, then in step 103, the UE transmits a Msg4. In step 104, it is determined whether the CRC of a Msg5 received from the network is good. If the CRC of Msg5 is OK, then in step 105, the RACH procedure is completed.

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

There are certain problems. For example, in BFR, UE usage has been identified as providing The best signal quality beam index performs an RA attempt. Upon detection of a successful RA attempt, the gNB may conclude that a BFR has occurred at the UE. This starts the procedure performed at the BFR at the gNB. For example, the gNB may perform a beam refinement procedure to select the best beam for the UE to use for decoding.

As long as there are SR-PUCCH resources for the UE, the UE will use the SR-PUCCH resources to indicate pending SR.

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

As shown, in steps 201 and 202 respectively, the UE determines that a BFR has occurred and the BFI_COUNTER is not greater than or equal to a beamFailureInstanceMaxCount. If it is determined that BFI_Counter is not greater than or equal to beamFailureinstanceMaxCount, the method returns to step 201 . On the contrary, if it is determined that BFI_Counter is greater than or equal to beamFailureinstanceMaxCount, then the message proceeds to step 203, where the UE starts an RA procedure according to 3GPP 38.321 Chapter 5.1.1. In step 204, the UE concludes that the random access procedure started in step 203 is successful/completed, as disclosed in chapter 5.1.5 of 3GPP 38.321, which states that "PDCCH transmission is addressed to the C-RNTI and contains a new Granted by one of the transfers". In step 205, the UE checks whether there is a pending SR. If there is a pending SR, then in step 206, the UE transmits a Msg5.

In a second case, it may be assumed that the SR-PUCCH has been removed at the UE. Same as above, it can also be assumed that the UE has data to send. In this case, BFR has not occurred at the UE. It can also be assumed that, for the random access procedure Msg3, since the Msg3 transmission block size TBS does not allow, UE will not be given the opportunity to transmit UL-SCH data. Although a figure is not provided, it is understood that the UE may perform steps 203, 204, 205 and 206 as disclosed above with respect to FIG. 2 .

In a third case, the situation is the same as the second case, except that BFR has occurred at the UE. In particular, it may be assumed that BFR has occurred, and steps 201, 202 and 203 occur first, and then the UE obtains pending data. Next, steps 204, 205 and 206 may be the same as above.

In all the above cases, there is a problem that it is not clear how the gNB will differentiate the three cases and then initiate the corresponding actions for BFR or when SR-PUCCH has been removed at the UE. For example, if the gNB wrongly determines that the SR-PUCCH has been released at the UE, the gNB will initiate an action 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 the same or modified SR-PUCCH channel parameters. In response, the UE may be required to restart using the new SR-PUCCH channel parameters. This results in increased and unnecessary control signaling additions. Additionally, interruptions during the restart procedure at the UE may be unnecessary.

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

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

Certain aspects of the invention and embodiments thereof may provide solutions to these and other challenges. For example, according to some embodiments, provision is made such that it can be determined during an RA procedure Methods and systems for proactively identifying a BFR attempt. Certain embodiments improve the gNB detection mechanism for BFR.

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

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

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

According to some embodiments, a network node includes processing circuitry configured to receive a message associated with an RA procedure from a wireless device. The message indicates a buffer status of the wireless device. Based on the buffer state, the processing circuitry is configured to determine A reason for initiating the RA procedure by the wireless device is determined. The cause is determined to be a release of a BFR or a resource associated with an 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 deterministically distinguish between BFR and periodic SR types of random access attempts. Thus, certain embodiments may improve the performance of both the UE performing BFR and the UE performing periodic SR.

As another example, a technical advantage may be that certain embodiments that allow deterministic identification of BFRs may result in UEs more reliably resuming their RRC connections, rather than experiencing a radio link failure and NR leg release followed by a New NR branch attachment procedure.

Other advantages will be readily apparent to those skilled in the art. Certain embodiments may have none, some, or all of the stated advantages.

100: steps

101: Steps

102: Step

103: Step

104: Step

105: Step

106: Step

107: Step

108: Step

109: Step

201: Step

202: Step

203: Step

204: step

205: Step

206: Step

300: step

301: Step

302: Step

303: Step

304: step

305: Step

306: Step

307: Step

308: Step

309: Step

310: step

311: Step

312: Step

313: Step

401: step

402: step

403: step

404: step

405: step

501: step

502: Step

503: step

504: step

505: Step

506: Step

507: Step

508: Step

509: Step

606: network

610: wireless device

611: Antenna

612: Radio front-end circuit

614: interface

616: Amplifier

618: filter

620: processing circuit

622: Radio Frequency (RF) Transceiver Circuit

624: Baseband processing circuit

626: Application program processing circuit

630: device readable medium

632: User interface equipment

634: Auxiliary equipment

636: power supply

660: network node

660b: network node

662:antenna

670: Processing circuit

672: Radio Frequency (RF) Transceiver Circuits

674: Baseband processing circuit

680: Device-readable media

684: Auxiliary equipment

686:Power

687: Power circuit

690: interface

692: Radio front-end circuit

694: port/terminal

696: Amplifier

698:Filter

700: User Equipment (UE)

701: processing circuit

702: Bus

705: input/output interface

709:Radio Frequency (RF) Interface

711:Internet connection interface

713: Power

715: memory

717: Random Access Memory (RAM)

719: Read-only memory (ROM)

721: storage media

723: operating system

725: application

727:Data/data file

731: Communication Subsystem

733:transmitter

735: Receiver

743a: Network

743b: Network

800: virtualization environment

820: application

830: Hardware node/hardware/network hardware device/hardware network connection infrastructure

840: virtual machine

850: virtualization layer

860: processing circuit

870:Network Interface Controller (NIC)

880:Physical Network Interface

890-1: memory

890-2: Machine-readable storage media

895: Instructions/Software

910: Telecommunications Network

911: access network

912a to 912c: base stations

913a to 913c: Coverage area

914: core network

915: wired or wireless connection

920: intermediate network

921: connect

922: connect

930: host computer

950: Over-the-cloud (OTT) connection

991: first user equipment (UE)

992: Second User Equipment (UE)

1000: communication system

1010: host computer

1011: software

1012: host application

1015: hardware

1016: communication interface

1018: processing circuit

1020: base station

1021: software

1025: hardware

1026: communication interface

1027: radio interface

1028: processing circuit

1030: User Equipment (UE)

1031: software

1032: client application

1035: hardware

1037: radio interface

1038: processing circuit

1050: Over-the-cloud (OTT) connection

1060: connect

1070: wireless connection

1110:step

1111: sub-step

1120: Step

1130: Step

1140: Step

1210: step

1220: step

1230: step

1310: step

1311: sub-step

1320: step

1321: sub-step

1330: Substep

1340: step

1410: step

1420: step

1430: Step

1500: method

1502: step

1504: step

1506: step

1508: step

1600: Virtual device

1610: detection module

1620: Starting module

1630: Identification module

1640: Transmission module

1700: method

1702: Step

1704: step

1800: Virtual installation

1810: Receive module

1820: Judgment module

1900: Method

1902: Step/Recognition

1904: Step/Transfer

1906: Step/abandon

2000: Method

2002: steps

2004: steps

8100: Management and Orchestration (MANO)

8200: radio unit

8210: Receiver

8220: Transmitter

8225: Antenna

8230: control system

For a more complete understanding of the features and advantages of the disclosed embodiments and the like, reference is now made to the following description taken in conjunction with the accompanying drawings, in which: FIG. 1 illustrates steps for performing RA by a UE; First example case An example method performed by a UE according to 3GPP 38.321 Chapter 5.17; Figure 3 illustrates an example for determining the cause of RACH is due to BFR by a gNB according to some embodiments Method; FIG. 4 illustrates an example method performed by a UE according to certain embodiments; FIG. 5 illustrates an alternative example method performed by a UE according to certain embodiments; FIG. 6 illustrates an example method performed by a UE according to certain implementations Example one instance wireless network; FIG. 7 illustrates an example network node according to some embodiments; FIG. 8 illustrates an example wireless device according to some embodiments; FIG. 9 illustrates an example user equipment according to some embodiments; FIG. 10 illustrates 11 illustrates a telecommunications network connected to a host computer via an intermediate network, according to certain embodiments; FIG. Figure 12 illustrates a generalized block diagram of a host computer communicating with a user equipment via a base station over a portion of a wireless connection, according to some embodiments; Figure 13 illustrates a communication system in accordance with an embodiment; A method of implementation; FIG. 14 illustrates another method implemented in a communication system according to an embodiment; FIG. 15 illustrates another method implemented in a communication system according to an embodiment; FIG. 16 illustrates shows another method implemented in a communication system according to an embodiment; FIG. 17 shows an example method performed by a wireless device according to some embodiments; FIG. 18 shows a method according to one of some embodiments Example virtual device; FIG. 19 illustrates an example method performed by a network node according to certain embodiments; FIG. 20 illustrates another example virtual device according to certain embodiments; Figure 21 illustrates another example method performed by a wireless device in accordance with certain embodiments; and Figure 22 illustrates another example method performed by a network node in accordance with certain embodiments.

Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. However, other embodiments are within the scope of the subject matter disclosed herein, and 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 incorporate The scope of the subject matter is conveyed to those skilled in the art.

Generally speaking, all terms used herein should be interpreted according to their ordinary meanings in the relevant technical field, unless a different meaning is explicitly given and/or implied from the context in which they are used. All references to a/an/the element, means, component, member, step, etc. should be construed openly as referring to at least one instance of the element, means, component, means, step, etc., unless expressly stated otherwise. The steps of any method disclosed herein do not have to be performed in the exact order disclosed, unless one step is explicitly described as being after or before another step and/or it is implied that one step must be after or before another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment as appropriate. Likewise, any advantage of any of the embodiments can be applied to any other embodiment and vice versa. Other objects, features and advantages of the accompanying embodiments will be apparent from the following description.

In some embodiments, the more general term "network node" may be used and may correspond to any type of radio network node communicating with a UE (directly or via another node) and/or with another network node or any network node. Examples of network nodes are NodeB, MeNB, ENB, a network node belonging to MCG or SCG, base station (BS), multi-standard radio Radio Station (MSR) Radio Nodes (such as MSR BS), eNodeB, gNodeB, Network Controller, Radio Network Controller (RNC), Base Station Controller (BSC), Repeater, Donor Node Control Repeater , base transceiver station (BTS), access point (AP), transmission point, transmission node, RRU, RRH, node in distributed antenna system (DAS), core network node (eg, MSC, MME, etc.), O&M, OSS, SON, positioning node (eg, 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 device that communicates with a network node and/or with another UE in a cellular or mobile communication system type of wireless device. Examples of UEs are target devices, device-to-device (D2D) UEs, machine-type UEs or UEs capable of machine-to-machine (M2M) communication, PDAs, PADs, tablets, mobile terminals, smartphones, laptop embedded Equipment (LEE), Laptop Mounted Equipment (LME), USB Hardlock, UE Class M1, UE Class M2, ProSe UE, V2V UE, V2X UE, etc.

Additionally, terms such as base station/gNodeB and UE should be considered non-limiting and specifically do not imply a particular hierarchical relationship between the two; UE" can be regarded as device 2 and these two devices communicate with each other through a certain radio channel. And in the following, a transmitter or a receiver may be a gNB or a UE.

According to certain embodiments, methods and systems are provided that allow deterministic identification of a BFR attempt during an RA procedure. Certain embodiments improve the gNB detection mechanism for BFR.

Additionally, according to some embodiments, methods and systems are provided that allow UEs to omit UL-SCH data when performing beam failure recovery. In case the BSR is always empty when BFR is performed, the gNodeB is able to deterministically distinguish random access attempts originating from periodic SRs from those originating from BFR random access attempts.

To distinguish the first, second and third cases described above, certain embodiments enable the gNB to use the reported BSR value from the UE at RACH Msg3 or RACH Msg5. For example, if the BSR value is the same as 0, the gNB may determine that the cause of RACH is due to BFR because a BFR has been configured and the RACH access is not from the UE's initial RACH access. 3 illustrates an example method for determining that the cause of RACH is due to BFR by a gNB, according to certain embodiments. Although FIG. 3 depicts Msg5 being used, it will be appreciated that Msg3 or another suitable message may additionally or alternatively be used.

Steps 300-309 may be similar to steps 100-109 as described above with respect to FIG. 1 . However, at step 310, it is determined whether the CRNTI is known. In step 311 of FIG. 3 , the gNB may investigate whether there is a BSR (not shown) in the transmission and whether the BSR is greater than zero. If the BSR is greater than 0, the gNB may determine in step 313 that the SR-PUCCH has been released at the UE. Conversely, if the BSR does not exist (not shown) or is equal to 0, then at step 312 the gNB may determine that a BFR has occurred at the UE.

To further enhance the gNB procedure described above, Fig. 4 presents a method by the UE according to some embodiments. Steps 401 - 404 may be similar to steps 200 - 204 as described above with respect to FIG. 2 . However, as shown in Figure 4, at step 404, the UE has decoded a PDCCH (Msg4) using one of the UL grants for the new transmission. As can be seen at step 405, the UE does not transmit a BSR and instead transmits on Msg5. Alternatively, the UE may send a BSR with content equal to 0. Note that this applies independently of whether the UE has pending profiles. In other words, while previous methods and systems required the UE to send any data that the UE has stored in the UE's buffer during either Msg3 or Msg5 of the RACH procedure, certain embodiments disclosed herein may require the UE to "pause" any such data. data transmission until after the RACH procedure is complete (eg, by a period indicated by the expiry of the period).

Figure 5 illustrates an alternative method by a UE according to some embodiments. Steps 501 - 504 may be similar to steps 400 - 404 in FIG. 4 , which are similar to steps 200 - 204 as described above with respect to FIG. 2 . However, as shown in Figure 5, at steps 505 and 507, the UE determines whether its SR-PUCCH resources have been removed. If "Yes", then in steps 506 and 509, the UE transmits what may be referred to as "dummy data" herein. According to some embodiments, the "dummy data" can be, for example, a valid RLC state msg plus padding. However, dummy data may include any such data that causes the gNB to determine that there is pending data at the UE side. Although Figure 5 does not show much, it should also be recognized that pending actual data, if present, can also be sent.

Returning to 507, if the UE determines that its SR resource has not been removed (i.e., "No"), the UE may proceed to step 508 of FIG. 5 in order to transmit an indication of padding or BSR=0 and the UE's actual pending data status . This step may be similar to step 405 described above with respect to FIG. 4 .

Figure 6 illustrates a wireless network according to some embodiments. Embodiments disclosed herein are described with respect to a wireless network, such as the example wireless network depicted in FIG. 6, although the subject matter described herein may be implemented in any suitable type of system using any suitable components. For simplicity, the wireless network of FIG. 6 only depicts network 606 , network nodes 660 and 660 b , and wireless device 610 . In practice, a wireless network may further include devices suitable for supporting 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 terminal device. any additional elements of communication. Among the depicted components, a network node 660 and a wireless device 610 are depicted in additional detail. Wireless networks can provide communications and other types of services to one or more wireless devices to facilitate the wireless devices' access to and/or use of services provided by or via the wireless network.

A wireless network may include and/or interface with any type of communication, telecommunications, data, cellular and/or wireless network or other similar type of system. In some embodiments, wireless networks may be configured to operate according to certain standards or other types of predefined rules or procedures. Accordingly, certain embodiments of wireless networks 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 ; a wireless local area network (WLAN) standard, such as the IEEE 802.11 standard; and/or any other suitable wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-wave and/or ZigBee standard.

The network 606 may include one or more of a backhaul network, a core network, an IP network, a public switched telephone network (PSTN), a packet data network, an optical network, a wide area network (WAN), a local area network (LAN) ), wireless local area network (WLAN), wired network, wireless network, metropolitan area network, and other networks for communication between devices.

Network node 660 and wireless device 610 include various components described in more detail below. These components work together to provide network node and/or wireless device functionality, such as providing wireless connectivity in a wireless network. In various embodiments, a wireless network may include any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or facilitate or participate in data and/or Any other component or system for communication of signals.

Figure 7 illustrates an example network node 660 according to some embodiments. As used herein, a network node refers to capable, configured, configured, and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or devices in a wireless network to enable and and/or equipment that provides wireless access to wireless devices and/or performs other functions (eg, management) in a wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access Node), Base Station (BS) (eg, Radio Base Station, Node B, Evolved Node B (eNB) and NR NodeB (gNB)). Base stations may be classified based on the amount of coverage they provide (or in other words, their transmission power level) and may then also be referred to as femtocells, picocells, microcells or macrocells. A base station may be a relay node controlling a repeater or a relay donor node. A network node may also comprise 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 ( RRH). These remote radio units may or may not be integrated with an antenna into 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), transceiver base stations ( BTS), transmission point, transmission node, multi-cell/multicast coordination entity (MCE), core network node (e.g., MSC, MME), O&M node, OSS node, SON node, positioning node (e.g., E-SMLC) and/or MDT. As another example, a network node may be a virtual network node as described in more detail below. More generally, however, a network node can mean capable, configured, configured, and/or operable to enable and/or provide a wireless device with access to a wireless network or to provide a service to an accessed Any suitable device (or group of devices) of a wireless device of a wireless network.

In FIG. 7 , network node 660 includes processing circuitry 670 , device readable medium 680 , interface 690 , auxiliary equipment 684 , power supply 686 , power supply circuit 687 and antenna 662 . Although the network node 660 depicted in the example wireless network of FIG. 7 may represent a device that includes the illustrated combination of hardware components, other embodiments may include devices with a different combination of components (e.g., fewer components, additional components, network nodes of different components). It should be understood that a network node includes any suitable combination of hardware and/or software required to perform the tasks, features, functions and methods disclosed herein. Furthermore, although the components of network node 660 are depicted as a single box positioned within a larger box or nested within multiple boxes, in practice a network node may include components that make up a single depicted different physical components (for example, device readable medium 680 may include multiple separate hard drives and multiple RAM modules).

Similarly, network node 660 may be composed of a plurality of physically separate components (eg, a NodeB component and an RNC component or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain cases where network node 660 includes multiple separate components (eg, BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC can control multiple NodeBs. In this case, 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 (eg, separate device readable media 680 for different RATs) and some components may be reused (eg, the same antenna 662 may be shared by the RATs). The network node 660 may also include sets of various depicted components for different wireless technologies integrated into the 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 chips or chipsets and other components within network node 660 .

Processing circuitry 670 is configured to perform any decision, calculation, or similar operation described herein as being provided by a network node (eg, certain obtain operations). Such operations performed by the processing circuit 670 may include performing operations by, for example, converting obtained information into other information, comparing obtained or transformed information with information stored in network nodes, and/or based on obtained or transformed information. The information performs one or more operations to process the information obtained by the processing circuitry 670 and to make a decision as a result of the processing.

The processing circuit 670 may include a combination of one or more of the following: a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application specific integrated circuit, field programmable gate array, or any other A suitable computing device, resource, or combination of hardware, software, and/or coded logic operable to provide network node 660 functionality alone or in combination with other network node 660 components, such as device-readable medium 680 . 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 advantages discussed herein. In some embodiments, the processing circuit 670 may comprise a system-on-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 chipsets), boards, or units such as a radio unit and a digital unit. In alternative embodiments, some or all of the RF transceiver circuitry 672 and baseband processing circuitry 674 may be on the same die or chipset, board or unit.

In some embodiments, instructions described herein as being performed by a network node, base station, eNB, or Some or all of the functionality provided by other such network devices. 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 hardwired manner. In any of these embodiments, processing circuitry 670 may be configured to perform the described functionality whether or not executing instructions stored on a device-readable storage medium. The advantages provided by this functionality are not limited to processing circuitry 670 or other components of network node 660 alone, but are enjoyed by network node 660 as a whole and/or by end users and wireless networks generally.

Device readable medium 680 may include any form of volatile or nonvolatile electronic Brain-readable memory, including but not limited to permanent storage, solid-state memory, remotely installed memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., a hard disk), removable storage media (e.g., a flash drive, a compact disc (CD), or a digital video disc (DVD)) and/or store information usable by the processing circuit 670, Any other volatile or non-volatile, non-transitory device readable and/or computer executable memory device for data and/or instructions. 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 capable of being processed by processing circuit 670 Other instructions executed and utilized by network node 660. Device-readable medium 680 may be used to store any calculations performed 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 integral.

Interface 690 is used for signaling and/or wired or wireless communication of data between network node 660 , network 606 and/or wireless device 610 . As shown, interface 690 includes port(s)/terminal(s) 694 to send and receive data to and from network 606, eg, over a wired connection. Interface 690 also includes radio front-end circuitry 692 , which may be coupled to antenna 662 or may be part of antenna 662 in some embodiments. The radio front end circuit 692 includes a filter 698 and an amplifier 696 . Radio front end circuitry 692 may be connected to antenna 662 and processing circuitry 670 . The radio front end circuitry may be configured to condition signals communicated between antenna 662 and processing circuitry 670 . The radio front end circuit 692 can receive digital data to be sent out via a wireless connection to other network nodes or wireless devices. Radio front-end circuitry 692 may use a combination of filter 698 and/or amplifier 696 to convert the digital data into a radio signal having appropriate channel and bandwidth parameters. Radio signals may then be transmitted via antenna 662 . Similarly, when receiving data, the antenna 662 can collect radio signals, which are then passed through the radio front-end circuit 692 converts the radio signals into digital data. The digital data may be passed to processing circuitry 670 . In other embodiments, the interface may include different components and/or different combinations of components.

In some alternative embodiments, the network node 660 may not include a separate radio front-end circuit 692, instead the processing circuit 670 may include a radio front-end circuit and may be connected to the antenna 662 without a separate radio front-end circuit 692 . Similarly, all or some of the RF transceiver circuitry 672 may be considered part of the interface 690 in some embodiments. 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 interface with baseband processing Circuitry 674, which is part of a bit cell (not shown), communicates.

Antenna 662 may include one or more antennas or antenna arrays configured to transmit 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 omnidirectional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omnidirectional antenna can be used to transmit/receive radio signals in any direction, a sector antenna can be used to transmit/receive radio signals from devices within a specific area, and a panel antenna can be used to transmit/receive in a relatively straight line One line-of-sight antenna for radio signals. In some instances, the use of more than one antenna may be referred to as MIMO. In some embodiments, the antenna 662 may be separate from the network node 660 and may be connected to the network node 660 through an interface or port.

Antenna 662, interface 690, and/or processing circuit 670 may be configured to perform any receive operations and/or certain obtain 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 device. Similarly, antenna 662, interface 690, and/or processing circuitry 670 may be configured to perform Perform is described herein as any transport operation performed by a network node. Any information, data and/or signal can be transmitted to a wireless device, another network node and/or any other network equipment.

Power circuit 687 may include or be coupled to power management circuitry and configured to supply power to components of network node 660 for performing the functionality described herein. Power circuit 687 may receive power from power source 686 . Power supply 686 and/or power circuit 687 may be configured to provide power to various components of network node 660 in a form suitable for the respective components (eg, at a voltage and current level required by each respective component). Power supply 686 may be included in or external to power circuit 687 and/or network node 660 . For example, network node 660 may be connected to an external power source (eg, an electrical outlet) via an input circuit or interface (such as a cable), whereby the external power source supplies power to power circuit 687 . As a further example, the power source 686 may include a power source in the form of a battery or battery pack connected to the power circuit 687 or integrated therein. The battery provides backup power if the external power source fails. Other types of power sources, such as photovoltaic devices, may also be used.

Alternative embodiments of the network node 660 may include additional components beyond those shown in FIG. 7, which may be responsible for providing some aspect of the network node's functionality, including any of the functionality described herein and/or Or any functionality required to support the subject matter described herein. For example, network node 660 may include user interface equipment to allow information to be input to network node 660 and to allow information to be output from network node 660 . This may allow a user to perform diagnostics, maintenance, repair and other management functions of the network node 660 .

FIG. 8 illustrates an example wireless device 610 . According to some embodiments. As used herein, a wireless device refers to a device that is capable, configured, configured, and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless mentioned otherwise, the term wireless device may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve the use of electromagnetic Radio waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information over the air to transmit and/or receive wireless signals. In some embodiments, a wireless device can be configured to transmit and/or receive information without direct human interaction. For example, a wireless device can be designed to transmit information to a network on a predetermined schedule when triggered by an internal or external event or in response to a request from the network. Examples of a wireless device include, but are not limited to, a smartphone, a cellular 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 A camera, a game console or device, a music storage device, a playback device, a wearable terminal device, a wireless endpoint, a mobile station, a tablet computer, a laptop computer, a laptop embedded device ( LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer terminal equipment (CPE), a vehicle-mounted wireless terminal device, etc. A wireless device may support device-to-device (D2D) communication (for example embodiments, by implementing a 3GPP standard for side-link communication), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-vehicle (V2X) ), and in this case may be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (IoT) case, a wireless device may represent performing monitoring and/or measurements and transmitting the results of such monitoring and/or measurements to another wireless device and/or A machine or other device at a network node. In this case, the wireless device may be a machine-to-machine (M2M) device, which may be referred to as an MTC device in a 3GPP context. As a specific example, the wireless device may be a UE implementing one of the 3GPP Narrowband Internet of Things (NB-IoT) standards. Specific examples of such machines or devices are sensors, metering devices (such as power meters), industrial machinery, or household or personal appliances (e.g., refrigerators, televisions, etc.), personal wearable devices (e.g., watches, fitness trackers, etc.) ). In other cases, a wireless device may represent a vehicle or other device capable of monitoring and/or reporting its operating 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 shown, the wireless device 610 includes an antenna 611 , an interface 614 , a processing circuit 620 , a device readable medium 630 , a user interface device 632 , auxiliary devices 634 , a power source 636 and a power circuit 637 . Wireless device 610 may include one or more of the depicted components for one or more of the different wireless technologies supported by wireless device 610, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, to name a few. multiple groups. These wireless technologies may be integrated into the same or a different chip or chipset as the other components within wireless device 610 .

Antenna 611 may include one or more antennas or antenna arrays configured to transmit and/or receive wireless signals and connect to interface 614 . In some alternative embodiments, the antenna 611 can be separate from the wireless device 610 and can be connected to the wireless device 610 through an interface or port. Antenna 611, interface 614, and/or processing circuitry 620 may be configured to perform any receive or transmit operation 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, the radio front-end circuit and/or antenna 611 may be considered an interface.

As shown, interface 614 includes radio front-end circuitry 612 and antenna 611 . Radio front-end circuitry 612 includes 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 . The radio front end circuit 612 may be coupled to the antenna 611 or may be a part of the antenna 611 . In some embodiments, the wireless device 610 may not include a separate radio front-end circuit 612 ; instead, the processing circuit 620 may include a radio front-end circuit and may be connected to the antenna 611 . Similarly, some or all of the RF transceiver circuitry 622 may be considered part of the interface 614 in some embodiments. The radio front-end circuit 612 can receive Digital data out to other network nodes or wireless devices. Radio front-end circuitry 612 may use a combination of filter 618 and/or amplifier 616 to convert the digital data into a radio signal having appropriate channel and bandwidth parameters. Radio signals may then be transmitted via the antenna 611 . Similarly, when receiving data, the antenna 611 may collect radio signals, which are then converted into digital data by the radio front-end circuit 612 . The digital data may be passed to processing circuitry 620 . In other embodiments, the interface may include different components and/or different combinations of components.

The processing circuit 620 may include a combination of one or more of the following: a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application specific integrated circuit, field programmable gate array, or any other A suitable computing device, resource, or combination of hardware, software, and/or coded logic operable to provide wireless device 610 functionality alone or in combination with other wireless device 610 components, such as device-readable medium 630 . Such functionality may include providing any of the various wireless features or advantages 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 shown, 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 include different components and/or different combinations of components. In some embodiments, the processing circuit 620 of the wireless device 610 may include a SOC. In some embodiments, RF transceiver circuitry 622, baseband processing circuitry 624, and application processing circuitry 626 may be on separate chips or chipsets. In alternative embodiments, some or all of the baseband processing circuitry 624 and application processing circuitry 626 may be combined into one chip or chipset, and the RF transceiver circuitry 622 may be on a separate chip or chipset. In yet alternative embodiments, some or all of the RF transceiver circuitry 622 and baseband processing circuitry 624 may be on the same chip or chipset, and the application processing circuitry 626 may be on a separate chip. chip or chipset. In yet other alternative embodiments, some or all of the RF transceiver circuitry 622, baseband processing circuitry 624, and application processing circuitry 626 may be combined on the same chip or chipset. In some embodiments, RF transceiver circuitry 622 may be part of interface 614 . The RF transceiver circuit 622 can condition the RF signal of the processing circuit 620 .

In some 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. In some embodiments, the device The readable medium 630 can 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 these particular embodiments, processing circuitry 620 may be configured to perform the described functionality whether or not executing instructions stored on a device-readable storage medium. The advantages provided by this functionality are not limited to processing circuitry 620 or other components of wireless device 610 alone, but are enjoyed by wireless device 610 as a whole and/or by end users and wireless networks generally.

Processing circuitry 620 may be configured to perform any determination, calculation, or similar operation described herein as being performed by a wireless device (eg, certain obtain operations). Such operations as performed by the processing circuitry 620 may include processing the obtained information by, for example, converting it to other information, comparing the obtained or transformed information with information stored by the wireless device 610, and/or based on the obtained or transformed information The information performs one or more operations to process the information obtained by the processing circuitry 620 and to make a decision as a result of the processing.

The device readable medium 630 is operable to store a computer program, software, an application program (including one or more of logic, rules, code, tables, etc.), and/or other instructions executable by the processing circuit 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 drive disc), removable storage media (e.g., a compact disc (CD) or a digital video disc (DVD)), and/or any other volatile or non-volatile storage medium that stores information, data, and/or instructions that may be used by the processing circuit Volatile, non-transitory device readable and/or computer executable memory devices. In some embodiments, processing circuitry 620 and device-readable medium 630 may be considered integral.

User interface device 632 may provide components that allow a human user to interact with wireless device 610 . This interaction can take many forms, such as visual, auditory, tactile, etc. The user interface device 632 is operable to generate output to a user and to allow the user to provide input to the wireless device 610 . The type of interaction may vary depending on the type of user interface device 632 installed in the wireless device 610 . For example, if the wireless device 610 is a smart phone, the interaction may be through a touch screen; if the wireless device 610 is a smart meter, the interaction may be through A screen or a speaker that provides an audible alarm (for example, if smoke is detected). The user interface device 632 may include input interfaces, devices, and circuits and output interfaces, devices, and circuits. User interface device 632 is configured to allow input of information to wireless device 610 and is connected to processing circuitry 620 to allow processing circuitry 620 to process the input information. User interface device 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 circuits. 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 . The user interface device 632 may include, for example, a speaker, a display, vibration circuits, a USB port, a headphone interface, or other output circuits. Using one or more input and output interfaces, devices, and circuits of user interface device 632, wireless device 610 can communicate with end users and/or wireless networks and allow them to benefit from the functionality described herein sex.

Auxiliary device 634 is operable to provide updates that would normally not be performed by a wireless device specific functionality. This may include specialized sensors for making measurements for various purposes, interfaces for additional types of communications such as wired communications, and the like. The inclusion and type of components of auxiliary equipment 634 may vary depending on the embodiment and/or case.

In some embodiments, the power source 636 may be in the form of a battery or battery pack. Other types of power sources may also be used, such as an external power source (eg, an electrical outlet), photovoltaic devices, or batteries. Wireless device 610 may further include power circuitry 637 for delivering power from power supply 636 to various parts of wireless device 610 that require power from power supply 636 to perform any functionality described or indicated herein. In some embodiments, power circuit 637 may include power management circuitry. Additionally or alternatively, the power circuit 637 is operable to receive power from an external power source; in this case, the wireless device 610 may be connectable to the external power source (such as an electrical outlet) via the input circuit or an interface (such as a power cable) . In some embodiments, the power circuit 637 is also operable to deliver power to the power source 636 from an external power source. This can be used to charge the power supply 636, for example. The power circuit 637 may perform any formatting, conversion, or other modification of the power from the power source 636 to make the power suitable for the respective components of the wireless device 610 to which the power is supplied.

Although the wireless device 610 depicted in FIG. 8 may represent a device comprising the illustrated combination of hardware components, other embodiments may include wireless devices having a different combination of components (e.g., fewer components, additional components, different components) .

Figure 9 illustrates an embodiment of a UE according to one of the 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 associated device. Alternatively, a UE may represent a device intended to be sold to or operated by a human user but which may not or may not initially be associated with a particular human user (e.g., a smart sprinkler controller) . Instead, A UE may represent a device not intended for sale to or operated 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 3rd Generation Partnership Project (3GPP), including an NB-IoT UE, a Machine Type Communication (MTC) UE and/or an Enhanced MTC (eMTC) UE. As shown in FIG. 7, UE 700 is configured to perform communications according to one or more communication standards promulgated by the Third Generation Partnership Project (3GPP), such as the GSM, UMTS, LTE, and/or 5G standards of 3GPP. An example of a wireless device for communication. As mentioned previously, the terms wireless device and UE are used interchangeably. Therefore, although FIG. 9 is a UE, the components discussed herein are equally applicable to a wireless device, and vice versa.

In FIG. 9, UE 700 includes processing circuit 701 (which 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 supply 713 and/or any other components or any combination thereof. The storage medium 721 includes an operating system 723 , application programs 725 and data 727 . In other embodiments, the storage medium 721 may contain other similar types of information. Certain UEs may utilize all or only a subset of the components shown in FIG. 9 . The level of integration between components may vary between UEs. Furthermore, some UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, and so on.

In FIG. 9, processing circuit 701 may be configured to process computer instructions and data. Processing circuitry 701 may be configured to implement any sequential state machine operable to execute machine instructions stored in memory as a machine-readable computer program, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic with appropriate firmware; one or more stored programs, a general-purpose processor (such as a microprocessor or digital signal processor (DSP)) together with appropriate software; or any combination of the above. For example, processing circuit 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 both input and output devices. UE 700 can be configured to use an output device via input/output interface 705 . An output device can use the same type of 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 can be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, a transmitter, a smart card, another output device, or any combination thereof. UE 700 can be configured to use an input device via input/output interface 705 to allow a user to retrieve information into UE 700 . Input devices may include a touch-sensitive or presence-sensitive display, a camera (eg, a digital camera, a digital video camera, a webcam, etc.), a microphone, a sensor, a mouse , a trackball, a directional pad, a track pad, a scroll wheel, a smart card and the like. Presence sensitive displays may include a capacitive or resistive touch sensor to sense input from a user. For example, a sensor can be an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another similar sensor or any combination thereof. For example, the input device can be an accelerometer, a magnetometer, a digital camera, a microphone and an optical sensor.

In FIG. 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. The network 743a can include wired and/or wireless networks, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a network, another similar network, or any combination thereof. For example, the network 743a may include a Wi-Fi network. Network connection interface 711 may be configured to include communication with one or more other A receiver and a transmitter interface for device communication. Networking interface 711 may implement receiver and transmitter functionality suitable for communication network links (eg, optical, electrical, and the like). Transmitter and receiver functions may share circuit components, software or firmware or alternatively may be implemented separately.

RAM 717 can be configured to interface to processing circuitry 701 via bus 702 to provide storage or caching of data or computer instructions during execution of software programs such as operating systems, application programs, and device drivers. ROM 719 may be configured to provide computer instructions or data to processing circuit 701 . For example, ROM 719 may be configured to store data for basic system functions such as basic input and output (I/O), booting, or receipt of keystrokes from a keyboard stored in a non-volatile memory. Invariant low-level system code or data. 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 EEPROM, floppy disk, CD-ROM, floppy disk, hard disk, removable cartridge, or flash pen drive. In one example, storage medium 721 may be configured to include operating system 723, application 725 (such as a web browser application, a widget or gadget engine, or another application) and data file 727. Storage medium 721 may store any of a number of operating systems or combinations of operating systems for use by UE 700 .

The storage medium 721 can be configured to include several physical drive units, such as redundant array of independent disks (RAID), floppy drives, flash memory, USB flash drives, external hard drives, thumb drives (thumb drives) drive), pen drive (pen drive), security disk (key drive), High Density Digital Versatile Disc (HD-DVD) drive, internal hard drive, Blu-ray drive, Holographic Digital Data Storage (HDDS) drive, external Mini Dual Inline Memory Module (DIMM) ), Synchronous Dynamic Random Access Memory (SDRAM), External Micro DIMM SDRAM, Smart Card memory (such as a Subscriber Identity Module or a Removable User Identity Module (SIM/RUIM) module), other memory or any combination thereof. Storage medium 721 may allow UE 700 to access computer-executable instructions, applications, or the like stored on a transitory or non-transitory memory medium to offload data or upload data. An article of manufacture, such as an article of manufacture utilizing a communication system, can be tangibly embodied in storage medium 721, which can include a device-readable medium.

In FIG. 9 , processing circuit 701 may be configured to communicate with network 743b using communication subsystem 731 . Network 743a and network 743b may be one or more of the same network or one or more different networks. Communication subsystem 731 may be configured to include one or more transceivers for communicating with network 743b. For example, the communication subsystem 731 may be configured to include one or more transceivers for communication in accordance with one or more communication protocols such as IEEE 802.7, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax or the like) communicate with one or more remote transceivers of another device capable of wireless communication, such as another wireless device, a UE, or a base station of a Radio Access Network (RAN). Each transceiver may include a transmitter 733 and/or a receiver 735 to implement transmitter or receiver functionality, respectively, appropriate for the RAN link (eg, frequency allocation and the like). Furthermore, the transmitter 733 and receiver 735 of each transceiver may share circuit components, software or firmware or may alternatively be implemented separately.

In the depicted embodiment, the communication functions of the communication subsystem 731 may include data communication, voice communication, multimedia communication, short-range communication (such as Bluetooth), near-field communication, location-based communication (such as using the Global Positioning System (GPS) to determine a location), another similar communication functions or any combination thereof. For example, the communication subsystem 731 may include cellular communication, Wi-Fi communication, Bluetooth communication and GPS communication. Network 743b may comprise 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 similar network, or any combination thereof. For example, the network 743b can be a cellular network, a Wi-Fi network and/or a near field network. Power supply 713 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE 700 .

Features, advantages and/or functions described herein may be implemented in one of the components of UE 700 or divided across multiple components of UE 700 . Furthermore, the features, advantages and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem 731 can be configured to include any of the components described herein. Furthermore, processing circuitry 701 may be configured to communicate with any of these components through bus 702 . In another example, any of these components may be represented by program instructions stored in memory that when executed by processing circuit 701 perform corresponding functions described herein. In another example, the functionality of any of these components may be split between processing circuitry 701 and communication subsystem 731 . In another example, the non-computationally intensive functions of any of these components may be implemented in software or firmware, and the computationally intensive functions may be implemented in hardware.

FIG. 10 is a schematic block diagram illustrating a virtualization environment 800 in which functions performed by some embodiments may be virtualized. In this context, virtualization means creating a virtual version of a device or device, which may include virtualizing hardware platforms, storage devices, and network connection resources. As used herein, virtualization may be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or a device (e.g., a UE, a wireless device, or any other type of communication device) or components and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (for example, via one or more Execute one or more applications, components, functions, virtual machines, or containers on a physical processing node).

In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments hosted by one or more of hardware nodes 830 . Furthermore, in embodiments where the virtual node is not a radio access node or does not require radio connectivity (eg, a core network node), the network node can then be fully virtualized.

One or more application programs 820 (which or the like may be referred to alternatively as software instances, virtual appliances, network functions) operable to implement some of the features, functions, and/or advantages of some embodiments disclosed herein , virtual nodes, virtual network functions, etc.) to implement these functions. Application 820 runs in virtualized environment 800 providing hardware 830 including processing circuitry 860 and memory 890 . Memory 890 contains instructions 895 executable by processing circuit 860 whereby application 820 is operable to provide one or more of the features, advantages and/or functions disclosed herein.

The virtualization environment 800 includes a general-purpose or special-purpose network hardware device 830 that includes a set of one or more processors or processing circuits 860, which may be commercial off-the-shelf (COTS) processors , Application Specific Integrated Circuit (ASIC) or any other type of processing circuit comprising digital or analog hardware components or a dedicated processor. Each hardware device may include memory 890 - 1 , which may be non-permanent memory for temporarily storing instructions 895 or software executed by processing circuit 860 . Each hardware device may include one or more network interface controllers (NICs) 870 (also known as network interface cards) that include a physical network interface 880 . Each hardware device may also include a non-transitory, non-transitory, machine-readable storage medium 890-2 storing software 895 executable by processing circuitry 860 and/or instructions. Software 895 may comprise any type of software, including software for instantiating one or more virtualization layers 850 (also referred to as hypervisors), software for executing virtual machines 840, and allowing their execution. Some embodiments described describe software that describes functions, features and/or advantages.

A virtual machine 840 includes virtual processing, virtual memory, virtual network connections or interfaces, and virtual storage and can be run by a corresponding virtualization layer 850 or hypervisor. Different embodiments of an instance of virtual appliance 820 may be implemented on one or more of virtual machines 840 and implemented in different ways.

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

As shown in FIG. 10, hardware 830 may be an independent network node with generic or specific components. Hardware 830 may include antenna 8225 and may implement some functions via virtualization. Alternatively, hardware 830 may be part of a larger hardware cluster (eg, such as in a data center or customer premises equipment (CPE)) where many hardware nodes work together and are managed and orchestrated (MANO) Management is performed by 8100 , the Management and Orchestration (MANO) 8100 oversees, among other things, the life cycle management of applications 820 .

Virtualization of hardware is referred to in some contexts as Network Functions Virtualization (NFV). NFV can be used to consolidate many network equipment types onto industry-standard high-capacity server hardware, physical switches and physical storage that can be located in data centers and customer terminal 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 the virtual machine 840 and the portion of the hardware 830 executing the virtual machine (whether hardware dedicated to the virtual machine and/or hardware shared by the virtual machine with other virtual machines 840) form a separate Virtual Network Element (VNE).

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

In some embodiments, one or more radio units 8200 each comprising one or more transmitters 8220 and one or more receivers 8210 may be coupled to one or more antennas 8225 . The radio unit 8200 can communicate directly with the hardware node 830 via one or more suitable network interfaces and can be used in combination with 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 may be achieved by virtue of the use of the control system 8230 which may alternatively be used for communication between the hardware node 830 and the radio unit 8200 .

Figure 11 illustrates a telecommunications network connected to a host computer via an intermediate network, according to some embodiments.

Referring to FIG. 11 , according to one embodiment, a communication system includes a telecommunications network 910 (such as a 3GPP-type cellular network) including an access network 911 (such as a radio access network) and core Network 914. The access network 911 includes a plurality of base stations 912a, 912b, 912c, such as NBs, eNBs, gNBs or other types of wireless access points, each of which defines a corresponding coverage area 913a, 913b, 913c. Each base station 912a, 912b, 912c can be connected to the core network 914 through a wired or wireless connection 915 . A first UE 991 located in the coverage area 913c is configured to wirelessly connect to or be paged by the corresponding base station 912c. cover A second UE 992 in the area 913a may be wirelessly connected to the corresponding base station 912a. Although multiple UEs 991 , 992 are shown in this example, the disclosed embodiments are equally applicable to situations where a unique UE is in the coverage area or where a unique UE is connected to the corresponding base station 912 .

The telecommunications network 910 is itself connected to a 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 part of a server farm. Process resources. Host computer 930 may be owned or controlled by a service provider, or may be operated by or on behalf of a service provider. Connections 921 and 922 between telecommunications network 910 and host computer 930 may extend directly from core network 914 to host computer 930 or may pass through an optional intermediate network 920 . Intermediate network 920 can be one of a public, a private, or hosted network, or a combination of more than one of these; intermediate network 920 (if present) can be a backbone network or the Internet; specific In other words, the intermediate network 920 may include two or more sub-networks (not shown).

The communication system of FIG. 11 realizes the connectivity between the connected UEs 991, 992 and the host computer 930 as a whole. Connectivity can be described as an over-the-top (OTT) connection 950 . The host computer 930 and connected UEs 991, 992 are configured to communicate data via the OTT connection 950, using the access network 911, the core network 914, any intermediate networks 920 and possibly further infrastructure (not shown) as intermediates and/or send a letter. OTT connection 950 may be transparent in the sense that the participating communication devices through which OTT connection 950 passes are unaware of the routing of uplink and downlink communications. For example, the base station 912 may not or need not be informed of the past route of an incoming downlink communication with data originating from the host computer 930 to be forwarded (eg, handed over) to a connected UE 991 . Similarly, base station 912 need not know the future route of an outgoing uplink communication originating from UE 991 towards host computer 930 .

FIG. 12 illustrates the transmission of a portion of a wireless network through a base station according to some embodiments. A host computer connected to communicate with a user device.

An example implementation of the UE, base station, and host computer discussed in the preceding paragraphs will now be described with reference to FIG. 12, according to an embodiment. In communication system 1000 , host computer 1010 includes hardware 1015 including a communication interface 1016 configured to establish and maintain a wired or wireless connection with one of the interfaces of various communication devices of communication system 1000 . Host computer 1010 further includes processing circuitry 1018, which may have storage and/or processing capabilities. In particular, processing circuitry 1018 may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The host computer 1010 further includes software 1011 stored in or accessible by the host computer 1010 and executable by the processing circuit 1018 . Software 1011 includes host application 1012 . Host application 1012 is operable to provide a service to a remote user, such as UE 1030 connected via OTT connection 1050 terminating at UE 1030 and host computer 1010 . Host application 1012 may provide user data transmitted using OTT connection 1050 when providing services to remote users.

The communication system 1000 further includes a base station 1020 provided in a telecommunication system and including hardware 1025 enabling it to communicate with a host computer 1010 and a UE 1030 . The hardware 1025 may include a communication interface 1026 for establishing and maintaining a wired or wireless connection with an interface of various communication devices of the communication system 1000 and for establishing and maintaining and positioning in a coverage area served by the base station 1020 At least the radio interface 1027 of the wireless connection 1070 of the UE 1030 in (not shown in FIG. 12 ). Communication interface 1026 can be configured to facilitate connection 1060 to host computer 1010 . The connection 1060 may be direct or it may be through a core network of the telecommunication system (not shown in FIG. 12 ) and/or through one or more intermediate networks outside the telecommunication system. In the illustrated embodiment, the hardware 1025 of the base station 1020 further includes a processing circuit 1028, The processing circuitry 1028 may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The base station 1020 further has software 1021 stored internally or accessible via an external connection.

The communication system 1000 further includes the aforementioned UE 1030 . Its hardware 1035 may include a radio interface 1037 configured to establish and maintain a wireless connection 1070 with a base station serving a coverage area in which the UE 1030 is currently located. The hardware 1035 of the UE 1030 further includes processing circuitry 1038, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or the like adapted to execute instructions combination (not shown). The UE 1030 further includes software 1031 stored in or accessible by the UE 1030 and executable by the processing circuit 1038 . The software 1031 includes a client application 1032 . The client application 1032 is operable to provide a service to a human or non-human user via the UE 1030 with the support of the host computer 1010 . In the host computer 1010 , an executing host application 1012 can communicate with an executing client application 1032 via an OTT connection 1050 terminating at the UE 1030 and the host computer 1010 . In providing services to users, client application 1032 may receive request data from host application 1012 and provide user data in response to the request data. The OTT connection 1050 can transmit both request data and user data. The client application 1032 can interact with the user to generate user information provided by it.

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

In Figure 12, the OTT connection 1050 has been drawn abstractly to illustrate the host computer Communication between 1010 and UE 1030 via base station 1020 without explicit reference to any intermediate devices and the precise routing of messages through such devices. The network infrastructure can determine the route, which can be configured to hide the route from the UE 1030 or the service provider operating the host computer 1010 or both. While the OTT connection 1050 is active, further decisions may be made by the network infrastructure by which the network infrastructure dynamically changes routing (eg, based on load balancing considerations or reconfiguration of the network).

The 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 (with wireless connection 1070 forming the last segment). More precisely, the teachings of these embodiments may improve data rates, latency, and/or power consumption and thereby provide benefits such as reduced user latency, relaxed constraints on file size, better responsiveness, and/or extended battery life. benefit.

A measurement procedure may be provided for the purpose of monitoring data rate, latency, and other factors that improve one or more embodiments. There may further be an optional network functionality for reconfiguring the OTT connection 1050 between the host computer 1010 and the UE 1030 in response to changes in the measurement results. Measurement procedures and/or network functionality for reconfiguring the OTT connection 1050 may be implemented in the software 1011 and hardware 1015 of the host computer 1010 or in the software 1031 and hardware 1035 of the UE 1030 or both. In an embodiment, sensors (not shown) may be deployed in or associated with the communication devices through which the OTT connection 1050 passes; The software 1011, 1031 can participate in the measurement program by computing or estimating the value of other physical quantities of the monitored quantity. The reconfiguration of the OTT connection 1050 may include message format, retransmission settings, preferred routing, etc.; the reconfiguration does not need to affect the base station 1020, and it may be unknown or unaware of the base station 1020. Such procedures and functionality may be known and implemented in the art practical. In some embodiments, measurements may involve dedicated UE signaling that facilitates host computer 1010 measurements of throughput, propagation time, latency, and the like. Measurements may be implemented where the software 1011 and 1031 cause a message (in particular, an empty or "dummy" message) to be transmitted using the OTT connection 1050 as it monitors propagation time, errors, and the like.

FIG. 13 is a flowchart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station, and a UE, which may be those described with reference to FIGS. 11 and 12 . For the sake of brevity of the present disclosure, only the schematic reference to FIG. 13 will be included in this section. In step 1110, the host computer provides user information. In sub-step 1111 of step 1110, which may be optional, the host computer provides user data by executing a host application. In step 1120, the host computer initiates a transmission of user data to the UE. In step 1130 (which may be optional), the base station transmits to the UE the user data carried in the host computer-initiated transmission according to the teachings of the embodiments described throughout the invention. In step 1140 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

Fig. 14 is a flowchart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station, and a UE, which may be those described with reference to FIGS. 11 and 12 . For the sake of brevity of the present disclosure, only the schematic reference to FIG. 14 will be included in this section. In step 1210 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides user data by executing a host application. In step 1220, the host computer initiates a transmission of user data to the UE. Transmissions may be through a 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 illustrates a method implemented in a communication system according to an embodiment One of the flow charts. The communication system includes a host computer, a base station, and a UE, which may be those described with reference to FIGS. 11 and 12 . For the sake of brevity of the present disclosure, only the schematic reference to FIG. 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 profile. In sub-step 1321 of step 1320 (which may be optional), the UE provides user data by executing a client application. In sub-step 1311 of step 1310, which may be optional, the UE executes a client application that provides user data in response to received input data provided by the host computer. The executed client application may further consider user input received from the user when providing user data. Regardless of the particular manner in which the user data is provided, the UE initiates the transmission of the user data to the host computer in sub-step 1330 (which may be optional). According to the teachings of the embodiments described throughout the present invention, in step 1340 of the method, the host computer receives user data transmitted from the UE.

Fig. 16 is a flowchart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station, and a UE, which may be those described with reference to FIGS. 11 and 12 . For the sake of brevity of the present disclosure, only the schematic reference to FIG. 16 will be included in this section. In step 1410 (which may be optional), the base station receives user data from the UE according to the teachings of the embodiments described throughout the present invention. 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 performed by a wireless device 110 according to some embodiments. In step 1502, the wireless device detects a BFR. In response to detecting the BFR, at step 1504, the wireless device initiates an RA procedure. At step 1506, before performing the RA procedure Or when performing RA procedures, the wireless device identifies data in a buffer for transmission on an uplink. At step 1508, the wireless device transmits a message associated with the RA procedure to a network node. The message indicates an empty buffer status and no data in the buffer was transmitted on the uplink for a period of time associated with performance of at least a portion of the RA procedure.

In a particular embodiment, an 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 an empty buffer status.

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

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

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

In a particular embodiment, the message transmitted to the network node indicating the empty buffer status includes a fifth message ( Msg5 ) of the RA procedure. In a further specific embodiment, before transmitting Msg5, the wireless device receives a fourth message (Msg4) of the RA procedure from the network node. Msg4 is a physical downlink control channel (PDCCH) transmission that includes an uplink grant authorizing the wireless device to transmit Msg5 on an uplink common data channel. In a further particular embodiment, the wireless device determines not to include data in the buffer in Msg5, and the time period associated with execution of at least a portion of the RA procedure extends beyond the transmission of Msg5.

In a specific embodiment, initiating the RA procedure includes transmitting a first message (Msg1) of the RA procedure.

In a particular embodiment, the time period begins before the transmission of the message.

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 the end of one of the time periods 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 an SR-PUCCH.

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

FIG. 18 shows a schematic block diagram of a virtual device 1600 in a wireless network such as the wireless network shown in FIG. 6 . The means may be implemented in a wireless device or network node, such as wireless device 610 or network node 660 shown in FIG. 6 . The device 1600 is operable to perform the example method described with reference to FIG. 17 and possibly any other procedure or method disclosed herein. It should also be understood that the method of FIG. 17 is not necessarily implemented by the device 1600 only. At least some operations of the method may be performed by one or more other entities.

Virtual device 1600 may include processing circuitry (which may include one or more microprocessors 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, Flash memory devices, optical storage devices, etc. In some embodiments, the program code stored in memory includes instructions for performing one or more telecommunications and/or data communication program instructions for communication protocols and instructions for implementing one or more of the techniques described herein. In some embodiments, processing circuitry may be used to cause detection module 1610, initiation module 1620, identification module 1630, transmission module 1640, and any other suitable elements of device 1600 to perform corresponding tasks according to one or more embodiments of the invention. Function.

According to some embodiments, the detection module 1610 may perform certain detection functions of the device 1600 . For example, the detection module 1610 can detect a BFR.

According to some embodiments, the initial module 1620 may perform some initial functions of the device 1600 . For example, the initiation module 1620 may initiate an RA procedure in response to detection of BFR by the detection module 1610 .

According to some embodiments, the recognition module 1630 can perform certain recognition functions of the device 1600 . For example, the identification module 1630 can identify data in a buffer for transmission on an uplink. The identification of the data in the buffer can be at any point before execution of the RA procedure or at any point during the execution of the RA procedure.

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

The term unit may have a conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, components for implementing respective tasks, programs, calculations, output and/or display functions, etc. (such as those described herein) ) electrical and/or electronic circuits, devices, modules, processors, memories, logical solid state and/or discrete devices, computer programs or instructions.

FIG. 19 depicts a process performed by a network node 660 according to some embodiments Method 1700. In step 1702, the network node receives a message associated with an RA procedure from a wireless device, and the message indicates a buffer status of the wireless device. At step 1704, based on the buffer status, the wireless device determines one of the reasons for initiating the RA procedure by the wireless device. According to some embodiments, the cause is determined to be a release of a BFR or a resource associated with an SR-PUCCH.

In a particular embodiment, the network node takes an action based on the initiation cause of the RA procedure. For example, if the network node determines that the cause of the RA procedure is the release of resources associated with the SR-PUCCH, the network node may re-initiate the SR. Alternatively, if the network node determines that the cause of the RA procedure is BFR, the network node may forego restarting 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. Based on the buffer status indicating that there is data in the buffer of the wireless device, the network node can determine that the cause of initiation of the RA procedure is the release of resources associated with the SR-PUCCH.

In a particular embodiment, the message may include a buffer status report (BSR) value greater than zero. 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 RA procedure was initiated due to the release of resources 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 can determine that the cause of initiation of the RA procedure is BFR.

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

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 to be BFR based on the BSR value of 0.

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

In a specific embodiment, the message includes a third message (Msg3) of the RA procedure.

In another specific embodiment, the message includes a fifth message (Msg5) of the RA procedure. In a further specific embodiment, before receiving Msg5, the network node may transmit a fourth message (Msg4) of the RA procedure to the wireless device. Msg4 may be a physical downlink control channel (PDCCH) transmission that includes an uplink grant authorizing the wireless device to transmit Msg5 on an uplink common data channel.

In a particular embodiment, the network node may configure the wireless device to not 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 can configure the wireless device to start a timer during the RA procedure. A timer may represent a time period associated with an RA procedure and/or an expiration of one of the timers may mark the end of one of the time periods associated with an RA procedure.

FIG. 20 shows a schematic block diagram of a virtual device 1800 in a wireless network such as the wireless network shown in FIG. 6 . The means may be implemented in a wireless device or network node, such as wireless device 610 or network node 660 shown in FIG. 6 . The device 1800 is operable to perform the example method described with reference to FIG. 19 and possibly any other procedure or method disclosed herein. It should also be understood that the method of FIG. 19 is not necessarily implemented by the device 1800 only. At least some operations of the method may be performed by one or more other entities.

Virtual appliance 1800 may include processing circuitry (which may include one or more microprocessors controllers or microcontrollers), and other digital hardware (which may include digital signal processors (DSPs)), application-specific 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, Flash memory devices, optical storage devices, etc. In some embodiments, the program code stored in memory includes program instructions for executing one or more telecommunications and/or data communication protocols and instructions for implementing one or more of the techniques described herein. In some implementations, the processing circuit can be used to cause the receiving module 1810, the determining module 1820, and any other suitable units of the device 1800 to perform corresponding functions according to one or more embodiments of the present invention.

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

According to some embodiments, the determination module 1820 may perform certain determination functions of the device 1800 . For example, the determination module 1820 can determine a reason for initiating the RA procedure by the wireless device based on the buffer status. According to some embodiments, the cause is determined to be a release of a BFR or a resource associated with an SR-PUCCH. The term unit may have a conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, components for implementing respective tasks, programs, calculations, output and/or display functions, etc. (such as those described herein) ) electrical and/or electronic circuits, devices, modules, processors, memories, logical solid state and/or discrete devices, computer programs or instructions.

Figure 21 depicts another method 1900 performed by a wireless device 610 in accordance with certain embodiments. At step 1902, before or while performing an RA procedure, the wireless device 610 identifies data in a buffer for transmission on an uplink. in step 1904. The wireless device 610 transmits a message associated with the RA procedure to a network node 660 while the data is in the buffer. The message indicates an empty buffer status. At step 1906, the wireless device 610 discards data in the uplink transmit buffer for a period of time associated with execution of at least a portion of the RA procedure.

In a specific embodiment, the wireless device 610 detects a beam failure recovery, and in response to detecting the beam failure recovery, transmits a first message Msg1 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 includes padding, and the padding indicates an empty buffer status.

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

In a specific embodiment, the message includes a BSR value of 0 and padding. Filled indicates an empty buffer state.

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

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

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

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

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

In a particular embodiment, the time period begins before the transmission of the message.

In a particular embodiment, wireless device 610 starts a timer representing a time period associated with the RA procedure. Alternatively, the expiration of one of the timers marks the end of one of the time periods 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 an SR-PUCCH.

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

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

In a particular embodiment, network node 660 takes an action based on the initiation cause of the RA procedure. For example, if the cause of the RA procedure is determined to be the release of resources associated with the SR-PUCCH, the network node 660 restarts the SR-PUCCH. As another example, if RA If the cause of the procedure is determined to be BFR, the network node 660 aborts restarting the SR-PUCCH.

In a particular embodiment, the buffer status indicates that data exists in a buffer of the wireless device for transmission on the uplink, and based on the buffer status indicating that data exists in the buffer of the wireless device, the network node 660 determines The RA procedure is initiated due to the release of resources associated with SR-PUCCH.

In a specific embodiment, the message includes a BSR value 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 of initiation of the RA procedure is BFR.

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

In a specific embodiment, the message includes 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 includes padding and a BSR value of zero, and the network node 660 determines the empty buffer status based on the padding and a BSR value of zero.

In a specific embodiment, the message includes a third message Msg3 of the RA procedure.

In a specific embodiment, the message includes a fifth message Msg5 of the RA procedure.

In a specific embodiment, the network node 660 transmits a fourth message Msg4 of the RA procedure to the wireless device 610 before receiving the Msg5. Msg4 contains a PDCCH transmission including an uplink grant authorizing the wireless device to transmit Msg5 on an uplink shared data channel.

In a particular embodiment, the network node 660 configures the wireless device 610 to not 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 time period associated with the RA procedure and/or wherein the expiration of one of the timers marks One of the time periods associated with the RA procedure ends.

Example embodiment

The following are example embodiments of the invention. In an example, a cross-reference to a particular embodiment (such as Embodiment 1) may refer to that embodiment (eg, Embodiment 1) and/or any of its sub-embodiment(s).

A group example embodiment

Example Embodiment A1. A method by a wireless device, comprising: detecting a beam failure restoration (BFR); in response to detecting the BFR, initiating a random access (RA) procedure; executing the RA procedure prior to or while performing the RA procedure, identifying data in a buffer for transmission on an uplink; and transmitting a message associated with the RA procedure to a network node, the message indicating an empty buffer status , and wherein the data in the buffer is not transmitted on the uplink during 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 of example embodiments A1 to A2, wherein the message includes padding, and wherein the padding indicates the empty buffer status.

Example embodiment A4. The method of any one of example embodiments A1 to A2, wherein the message includes a buffer status report (BSR) value of 0, and wherein the BSR value of 0 indicates the empty buffer status state.

Example embodiment A5. The method of any one of example embodiments A1 to A2, wherein the message includes 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 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 embodiment 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 execution of the at least a portion of the RA procedure The transmission extends beyond the Msg3.

Example embodiment A8. The method of any 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: receiving a fourth message (Msg4) of the RA procedure from the network node prior to transmitting the Msg5, the Msg4 including a physical downlink control Channel (PDCCH) transmission, the physical downlink control channel (PDCCH) transmission includes an uplink grant authorizing the wireless device to transmit the Msg5 on an uplink common data channel.

Example Embodiment 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 execution of the at least a portion of the RA procedure is related to The associated time period extends beyond 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 (Msg1 ) of the RA procedure.

Example Embodiment A12. The method of any one of example embodiments A1 to A11, wherein the time period begins before transmitting the message.

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 time period associated with the RA procedure and/or wherein the timer An expiration marks the end of one of the time periods 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 of example embodiments A1 to A14, wherein the wireless device has an active resource associated with a SR-Physical Uplink Control Channel (SR-PUCCH).

Example embodiment A16. The method of any 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 for performing any of the methods of example embodiments A1 to A16 when executed on a computer.

Example Embodiment A19. A computer program product comprising a computer program comprising instructions for performing any of the methods of example embodiments A1 to A16 when executed on a computer.

Example Embodiment A20. A non-transitory computer-readable medium storing instructions that when executed by a computer perform any of the methods of example embodiments Al-A16.

Group B Example

Example Embodiment B1. A method, performed 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 state, determining a reason for initiating the RA procedure by the wireless device, the reason being determined to be: a buffer failure recovery (BFR) or a SR-PHY (SR-PUCCH) One of the associated one of the resources is released.

Example embodiment B2. The method of example embodiment B1, further comprising taking an action based on the initiation cause of the RA procedure, wherein taking the action comprises: if the cause of the RA procedure is determined to be related to the SR-PUCCH The associated release of the resource restarts the SR-PUCCH; or abandons restarting the SR-PUCCH if the cause of the RA procedure is determined to be the BFR.

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 indicating the With the buffer status of data present in the buffer of the wireless device, the network node determines that the cause of initiation of the RA procedure is the release of the resource associated with the SR-PUCCH.

Example embodiment B4. The method of example embodiment B3, wherein: the message includes a buffer status report (BSR) value greater than 0, and the network node determines that the wireless device is in the buffer based on the BSR value greater than 0 There is data in the device.

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

Example Embodiment B6. The method of Example Embodiment B5, wherein: the message includes 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 includes a buffer status report (BSR) value of zero, and the network node determines the empty buffer status based on the BSR value of zero.

Example embodiment B8. The method of example embodiment B5, wherein: the message includes padding and a buffer status report (BSR) value of 0, and the network node determines the empty buffer based on the padding and the BSR value of 0 state.

Example Embodiment B9. The method of any one of example embodiments B1 to B8, wherein the message includes a third message (Msg3) of the RA procedure.

Example Embodiment B10. The method of any one of example embodiments B1 to B8, wherein the message includes a fifth message (Msg5) of the RA procedure.

Example Embodiment B11. The method of Example Embodiment B10, further comprising: prior to receiving the Msg5, transmitting a fourth message (Msg4) of the RA procedure to the wireless device, the Msg4 including a physical downlink control Channel (PDCCH) transmission, the physical downlink control channel (PDCCH) transmission includes an uplink grant authorizing the wireless device to transmit the Msg5 on an uplink common data channel.

Example Embodiment B12. The method of any one of example embodiments B1 to B11, further comprising: configuring the wireless device to not transmit data stored in one of the wireless devices during a time period associated with the RA procedure Any data in the buffer.

Example Embodiment B13. 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 time period associated with the RA procedure and /or wherein the expiration of one of the timers marks the end of one of the time periods associated with the RA procedure.

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

Example Embodiment B15. A computer program comprising instructions for performing any of the methods of example embodiments B1 to B13 when executed on a computer.

Example Embodiment B16. A computer program product comprising a computer program comprising instructions for performing any of the methods of example embodiments B1 to B13 when executed on a computer.

Example Embodiment B17. A non-transitory computer-readable medium storing instructions that, when executed by a computer, perform any of the methods of example embodiments B1-B13.

Group C example embodiment

Example Embodiment C1. A wireless device comprising: a processing circuit configured to perform any of the steps of any of example embodiments A1 to A15; and a power supply circuit 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-B13; power supply circuitry configured to supply power to the wireless device.

Example Embodiment C3. A wireless device comprising: an antenna configured to transmit and receive wireless signals; radio front-end circuitry connected to the antenna and processing circuitry and configured to regulate A signal communicated between the antenna and the processing circuit; the processing circuit configured to perform any of the steps of any of example embodiments A1 to A15; an input interface connected to the processing circuit and via configured to allow input of information into the wireless device for processing by the processing circuit; an output interface connected to the processing circuit and configured to output from the wireless device information processed by the processing circuit; and a battery connected to the connected to the processing circuit and configured to supply power to the wireless device.

Example Embodiment C4. A communication system comprising 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 includes network nodes having a radio interface and processing circuitry configured to perform as in example embodiment B1 Any of the steps to any of B13.

Example Embodiment C5. The communication system of the previous embodiment, further comprising the network node.

Example Embodiment C6. The communication system of the previous two embodiments, further comprising the wireless device, wherein the wireless device is configured to communicate with the network node.

Example Embodiment C7. The communication system of the preceding three embodiments, wherein: the processing circuit of the host computer is configured to execute a host application, thereby providing the user data; and the wireless device includes a configured Processing circuitry for executing a client application associated with the host application.

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

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

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

Example Embodiment C11. A wireless device configured to communicate with a network node, the wireless device comprising a radio interface and processing circuitry configured to perform the three preceding embodiments.

Example Embodiment C12. A communication system comprising a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward user data to a The cellular network is used for transmission to a wireless device, wherein the wireless device includes a radio interface and processing circuitry, the components of the wireless device being configured to perform any of the steps of any of example embodiments A1 to A15.

Example Embodiment C13. The communication system of the previous embodiment, wherein the cellular network further comprises a network node configured to communicate with the wireless device.

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

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

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

Example Embodiment C17. A communication system comprising a host computer comprising: a communication interface configured to receive a transmission originating from a wireless device to a network node User data for , wherein the wireless device includes a radio interface and processing circuitry, the processing circuitry of the wireless device being configured to perform any of the steps of any of example embodiments A1 to A15.

Example Embodiment C18. The communication system of the previous embodiment, further comprising the wireless device.

Example Embodiment C19. The communication system of the previous two embodiments, further comprising the network node, wherein the network node includes a radio interface configured to communicate with the wireless device and is configured to communicate with the wireless device from the The user data carried in a transmission from the wireless device to the network node is forwarded to a communication interface of the host computer.

Example Embodiment C20. The communication system of the preceding three embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; and the processing circuitry of the wireless device is configured to execute a host application A client application associated with the program to provide this user data.

Example Embodiment C21. The communication system of the preceding four embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing requested data; and the processing circuitry of the wireless device is configured to execute a client application associated with the host application, thereby providing the user data in response to the request for data.

Example Embodiment C22. A method implemented in a communication system comprising a host computer, a network node, and a wireless device, the method comprising: receiving, at the host computer, communication transmitted from the wireless device to the network node User data 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 providing, at the wireless device, the user data to the network node.

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

Example Embodiment C25. The method of the preceding three embodiments, further comprising: executing a client application at the wireless device; and receiving input data to the client application at the wireless device, by executing A host application associated with the client application provides the input data at the host computer, wherein the user data is provided by the client application for transmission in response to the input data.

Example Embodiment C26. A communication system comprising a host computer including a communication interface configured to receive user data resulting from a transmission from a wireless device to a network node, Where the network node includes a radio interface and processing circuitry, the processing circuitry of the network node is configured to perform any of the steps as any of example embodiments B1 to B13.

Example embodiment C27. The communication system of the previous embodiment, further comprising the network node.

Example Embodiment C28. The communication system of the previous two embodiments, further comprising the wireless device, wherein the wireless device is configured to communicate with the network node.

Example Embodiment C29. The communication system of the preceding three embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; the wireless device is configured to execute a host application associated with the host application A client application whereby the user data is provided for receipt by the host computer.

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

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

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

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

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

Modifications, additions or omissions may be made to the systems and devices described herein without departing from the scope of the present invention. Components of systems and devices can be integrated or separated. Furthermore, operations of the systems and devices may be performed by more, fewer or other components. Additionally, operations of the systems and devices may be performed using any suitable logic, including 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 invention. The methods may contain more, fewer or other steps. Additionally, the steps may be performed in any suitable order.

Although the invention has been described in terms of certain embodiments, alterations and permutations of those embodiments will be apparent to those skilled in the art. Therefore, the above description of the embodiments does not limit the invention. Other changes, substitutions and alterations are possible without departing from the spirit and scope of the present invention.

1900: Method

1902: Step/Recognition

1904: Step/Transfer

1906: Step/abandon

Claims (58)

A method performed 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 after the data while in the buffer, transmitting to a network node a message associated with the RA procedure, the message indicating an empty buffer status, and for a time period associated with execution of at least a portion of the RA procedure , abort transmitting the data in the buffer on the uplink. 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 Msg1 of the RA procedure to initiate the RA procedure. 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. The method of any one of claims 1 to 2, wherein the message includes padding, and wherein the padding indicates the empty buffer status. The method of any one of claims 1 to 2, wherein the message includes a buffer status report (BSR) value of 0, and wherein the BSR value of 0 indicates the empty buffer status. The method of any one of claims 1 to 2, wherein the message includes a buffer status report with a BSR value of 0 and padding, wherein the BSR value of 0 and the padding indicate the empty buffer status. The method according to any one of claims 1 to 2, wherein the message indicating the empty buffer status transmitted to the network node comprises a third message Msg3 of the RA procedure. The method of claim 7, wherein the Msg3 does not contain the data in the buffer, wherein the time period associated with the execution of the at least a portion of the RA procedure extends beyond the transmission of the Msg3. The method according to any one of claims 1 to 2, wherein the message indicating the empty buffer status transmitted to the network node includes a fifth message Msg5 of the RA procedure. The method according to claim 9, further comprising: before transmitting the Msg5, receiving a fourth message Msg4 of the RA procedure from the network node, the Msg4 includes a physical downlink control channel PDCCH transmission, and the physical downlink Control channel PDCCH transmission includes an uplink grant authorizing the wireless device to transmit the Msg5 on an uplink shared data channel. The method of claim 9, wherein the Msg5 does not contain the data in the buffer, wherein the time period associated with the execution of the at least a portion of the RA procedure extends beyond the transmission of the Msg5. The method as claimed in any one of claims 1 to 2, wherein the time period begins before transmitting the message. The method according to any one of claims 1 to 2, further comprising starting a timer, and wherein the timer represents the time period associated with the RA procedure, and/or wherein expiration of one of the timers marks One of the time periods associated with the RA procedure ends. The method of claim 13, further comprising detecting the expiration of the timer, and transmitting the data in the buffer in response to the expiration of the timer. The method of any one of claims 1 to 2, wherein the wireless device has an active resource associated with a SR-PUCCH. The method of any one of claims 1 to 2, wherein the wireless device has released a resource associated with a SR-PUCCH. A method performed 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 The device state determines one of the reasons for initiating the RA procedure by the wireless device, the reason is determined to be: a buffer fault recovery BFR, or one associated with a scheduling request-physical uplink control channel SR-PUCCH resource One is released. The method of claim 17, further comprising taking an action based on the initiation cause of the RA procedure, wherein taking the action includes: if the cause of the RA procedure is determined to be the resource associated with the SR-PUCCH If the release is performed, then restart the SR-PUCCH; or if the cause of the RA procedure is determined to be the BFR, then give up restarting the SR-PUCCH. The method of any one of claims 17 to 18, wherein: the buffer status indicates that there is data for transmission on the uplink in a buffer of the wireless device, and is based on indicating the buffer of the wireless device In the buffer status where data exists, the network node determines that the cause of initiation of the RA procedure is the release of the resource associated with the SR-PUCCH. The method of claim 19, wherein: the message includes a buffer status report (BSR) value greater than 0, and the network node determines that the wireless device has data in the buffer based on the BSR value greater than 0. 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 of initiation of the RA procedure is the BFR. The method of claim 21, wherein: the message includes padding, and the network node determines the empty buffer status based on the padding. The method of claim 21, wherein: the message includes a buffer status report with a BSR value of 0, and the network node determines the empty buffer status based on the BSR value of 0. The method of claim 21, wherein: the message includes padding and a buffer status report with a BSR value of 0, and the network node determines the empty buffer status based on the padding and the BSR value of 0. The method according to any one of claims 17-18, wherein the message includes a third message Msg3 of the RA procedure. The method according to any one of claims 17 to 18, wherein the message includes a fifth message Msg5 of the RA procedure. The method according to claim 26, further comprising: before receiving the Msg5, transmitting a fourth message Msg4 of the RA procedure to the wireless The device, the Msg4 includes a physical downlink control channel PDCCH transmission, the physical downlink control channel PDCCH transmission includes an uplink grant authorizing the wireless device to transmit the Msg5 on an uplink common data channel. The method of any one of claims 17 to 18, further comprising: configuring the wireless device to not transmit any data stored in a buffer of the wireless device during a time period associated with the RA procedure . The method of any one of claims 17 to 18, further comprising: configuring the wireless device to start a timer during the RA procedure, and wherein the timer represents the time period associated with the RA procedure, and /or wherein the expiration of one of the timers marks the end of one of the time periods associated with the RA procedure. 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 data; 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 executing one of at least a portion of the RA procedure During an associated time period, abort transmitting the data in the buffer on the uplink. The wireless device of claim 30, wherein the processing circuit is further configured to: detect a light beam failure recovery; and In response to detecting the beam failure recovery, a first message Msg1 of the RA procedure is transmitted to initiate the RA procedure. 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. The wireless device of any one of claims 30 to 31, wherein the message includes padding, and wherein the padding indicates the empty buffer status. The wireless device of any one of claims 30 to 31, wherein the message includes a buffer status report (BSR) value of 0, and wherein the BSR value of 0 indicates the empty buffer status. The wireless device according to any one of claims 30 to 31, wherein the message includes a buffer status report with a BSR value of 0 and padding, wherein the BSR value of 0 and the padding indicate the empty buffer status. The wireless device according to any one of claims 30 to 31, wherein the message indicating the empty buffer status transmitted to the network node includes a third message Msg3 of the RA procedure. The wireless device of claim 36, wherein the Msg3 does not contain the data in the buffer, wherein the time period associated with the execution of the at least a portion of the RA procedure extends beyond the transmission of the Msg3. The wireless device according to any one of claims 30 to 31, wherein transmitted to the network node The message indicating the empty buffer status includes a fifth message Msg5 of the RA procedure. The wireless device of claim 38, wherein the processing circuit is configured to: receive a fourth message Msg4 of the RA procedure from the network node prior to transmitting the Msg5, and wherein the Msg4 includes a PDCCH transmission, the PDCCH Transmitting includes an uplink grant authorizing the wireless device to transmit the Msg5 on an uplink shared data channel. The wireless device of claim 38, wherein the Msg5 does not contain the data in the buffer, wherein the time period associated with the execution of the at least a portion of the RA procedure extends beyond the transmission of the Msg5. The wireless device of any one of claims 30 to 31, wherein the time period begins before transmitting the message. The wireless device according to any one of claims 30 to 31, wherein the processing circuit is configured to start a timer, and wherein the timer represents the time period associated with the RA procedure, and/or wherein the timing An expiration of the timer marks the end of one of the time periods associated with the RA procedure. The wireless device of claim 42, wherein the processing circuit is configured to detect the expiration of the timer, and transmit the data in the buffer in response to the expiration of the timer. The wireless device of any one of claims 30 to 31, wherein the wireless device has an active resource associated with a Scheduling Request-Physical Uplink Control Channel (SR-PUCCH). The wireless device according to any one of claims 30 to 31, wherein the wireless device has released a resource associated with a SR-PUCCH. A network node comprising processing circuitry configured to: 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 state, determine one of the reasons for initiating the RA procedure by the wireless device, the reason is determined to be: a buffer failure recovery BFR, or a scheduling request-physical uplink control channel SR-PUCCH One of the associated resources is freed. The network node of claim 46, wherein the processing circuit is configured to take an action based on the initiation cause of the RA procedure, wherein taking the action comprises: if the cause of the RA procedure is determined to be related to the SR - the release of the resource associated with the PUCCH, restarting the SR-PUCCH; or abandoning restarting the SR-PUCCH if the cause of the RA procedure is determined to be the BFR. The network node according to any one of claims 46 to 47, wherein: the buffer status indicates that there is data for transmission on the uplink in a buffer of the wireless device, and Based on the buffer status indicating data exists in the buffer of the wireless device, the processing circuit is configured to determine that the initiation cause of the RA procedure is the release of the resource associated with the SR-PUCCH. The network node of claim 48, wherein: the message includes a buffer status report BSR value greater than 0, and the processing circuit is configured to determine that the wireless device has a buffer in the buffer based on the BSR value greater than 0 material. The network node of claim 46, wherein: the buffer status indicates an empty buffer status, and based on the empty buffer status, the processing circuit is configured to determine that the cause of initiation of the RA procedure is the BFR. The network node of claim 50, wherein: the message includes padding, and the processing circuit is configured to determine the empty buffer status based on the padding. The network node of claim 51, wherein: the message includes a buffer status report with a BSR value of 0, and the processing circuit is configured to determine the empty buffer status based on the BSR value of 0. As the network node of claim item 50, wherein: The message includes padding and a buffer status report BSR value of zero, and the processing circuit is configured to determine the empty buffer status based on the padding and the BSR value of zero. The network node according to any one of claims 46-47, wherein the message includes a third message Msg3 of the RA procedure. The network node according to any one of claims 46-47, wherein the message includes a fifth message Msg5 of the RA procedure. The network node of claim 55, wherein the processing circuit is configured to: transmit a fourth message Msg4 of the RA procedure to the wireless device before receiving the Msg5, the Msg4 including a physical downlink control channel PDCCH transmission, the physical downlink control channel PDCCH transmission includes an uplink grant authorizing the wireless device to transmit the Msg5 on an uplink common data channel. The network node of any one of claims 46 to 47, further comprising: configuring the wireless device to not transmit data stored in a buffer of the wireless device during a time period associated with the RA procedure any information. The network node according to any one of claims 46 to 47, wherein the processing circuit is configured to: configure the wireless device to start a timer during the RA procedure, and wherein the timer indicates that it is related to the RA procedure The time period associated, and/or wherein an expiration of one of the timers marks the end of one of the time periods associated with the RA procedure.

Images