Buffer status reporting formats, tables, and procedures for extended reality services

Abstract

A communication device in a network may receive a buffer status report (BSR) format configuration that specifies at least one non-legacy BSR format and / or at least one non-legacy buffer status table to be used to report a BSR to a network node. The communication device may further select a non-legacy BSR format from the at least one non-legacy BSR format and / or select a non-legacy buffer status table from the at least one non-legacy buffer status table. The communication device may further generate a BSR report based on the non-legacy BSR format and / or the non-legacy buffer status table. The communication device may further transmit the BSR report toward the network node.

Description

[Technical field]

[0001] The present disclosure relates generally to communications, and more particularly to communication methods and associated devices and nodes supporting wireless communications. [Background technology]

[0002] A communication device, such as a user equipment (UE), reports buffer status to the network awaiting transmission in a media access control ("MAC") control element ("CE") buffer status report ("BSR"). Currently, there are four different BSR formats that a communication device can send to the network. The four different BSR formats are short BSR format (fixed size), short truncated BSR format (fixed size), long truncated BSR format (variable size), and long BSR format (variable size).

[0003] Figure 1 shows the short BSR format and the short truncated BSR format, and Figure 2 shows the long BSR format and the long truncated BSR format.

[0004] There are three types of BSRs: regular BSRs, periodic BSRs, and padding BSRs.

[0005] A regular BSR is triggered when UL data for a logical channel belonging to a logical channel group ("LCG") becomes available to the MAC entity and this UL data belongs to a logical channel with a higher priority than the priority of any logical channel that contains available UL data belonging to any LCG, or none of the logical channels belonging to an LCG contain available UL data. When more than one LCG has data available for transmission, the communication device uses the long BSR format and reports all LCGs that have data. However, if only one LCG has data, the short BSR format is used.

[0006] Periodic BSR is configured by the network. When notified by the network, the communication device periodically reports the BSR via a radio resource control ("RRC") message. When more than one LCG has data available for transmission, the communication device uses the long BSR format and reports all LCGs that have data. However, if only one LCG has data, the short BSR format is used.

[0007] Padding BSR is an opportunistic method to provide buffer status information to the network when a MAC protocol data unit ("PDU") has a number of padding bits equal to or greater than one of the BSR formats. In this case, the wireless terminal adds a padding BSR that replaces the corresponding padding bits. In this case, the BSR format to be used depends on the number of padding bits, the number of logical channels that have data for transmission, and the size of the BSR format. When more than one LCG has data for transmission, one of the following three formats is used: short truncated BSR, long BSR, or long truncated BSR. The selection of the BSR format depends on the number of padding bits available. When only one LCG has data for transmission, the short BSR format is used.

[0008] In a wireless terminal, one MAC PDU can contain at most one BSR MAC CE. Summary of the Invention

[0009] There are several problems with the current BSR tables and procedures: One problem is that in a wireless terminal, one MAC PDU can contain at most one BSR MAC CE.

[0010] Another problem is that Extended Reality ("XR") services generate packet sizes that can be quite large. This causes the index that the BSR can point to to be high. The higher the buffer status index, the larger the buffer size reported. The difference between two consecutive buffer status indexes increases as the index increases. This difference is especially visible in the long BSR table. This causes there to be more uncertainty regarding the actual buffer size at the communication device, which also causes the network to overshoot the grant provided to the communication device, which affects the network capacity overall.

[0011] For the short BSR table, the maximum size that can be reported is 150.000 bytes. Therefore, when the UE has a buffer size above this value, the UE reports an index indicating ">150.000" bytes. This information may be inaccurate and may also lead to overshooting the grant and / or delays if the network does not provide a large enough grant.

[0012] According to various embodiments of the inventive concept, other BSR formats are used that can provide more precise buffer status information, which results in the network not having to overshoot grants excessively, allowing network capacity maximization.

[0013] According to some embodiments, a method is provided for implementation by a communication device in a network. The method can include receiving a BSR format configuration specifying at least one non-legacy BSR format and / or at least one non-legacy buffer status table to be used for reporting a Buffer Status Report (BSR) to a network node. The method can further include selecting a non-legacy BSR format from the at least one non-legacy BSR format and / or selecting a non-legacy buffer status table from the at least one non-legacy buffer status table. The method can further include generating a BSR report based on the non-legacy BSR format and / or the non-legacy buffer status table. The method can further include transmitting the BSR report towards the network node.

[0014] According to another embodiment, a method is provided that is implemented by a network node in a network. The method can include receiving a Buffer Status Report (BSR) indication message from a communication device. The BSR indication message can indicate at least one non-legacy BSR format and / or at least one non-legacy buffer status table that the communication device supports. The method can further include determining which non-legacy BSR formats and / or non-legacy BSR buffer status tables are supported by the communication device based on the BSR indication message. The method can further include determining at least one non-legacy BSR format and / or at least one non-legacy BSR buffer status table for use by the communication device based on which non-legacy BSR formats and / or non-legacy BSR buffer status tables are supported by the communication device. The method can further include transmitting a Radio Resource Control (RRC) configuration message for use by the communication device indicating one or more non-legacy BSR formats and / or one or more non-legacy buffer status tables to use for BSR reporting.

[0015] According to other embodiments, a communications device, a network node, a computer program, or computer program code is provided for implementing the methods described above.

[0016] One advantage that may be achieved using various embodiments of the inventive concept is reduced latency for critical services.

[0017] The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate several non-limiting embodiments of the inventive concepts. [Brief description of the drawings]

[0018] [Figure 1] FIG. 1 is a diagram of short BSR and short truncated BSR MAC CE. [Diagram 2] FIG. 1 is a diagram of a long BSR and a long truncated BSR MAC CE. [Diagram 3] 1 is a graph showing the buffer size difference between two consecutive indexes. [Figure 4] 1 is a block diagram illustrating a wireless device UE in accordance with some embodiments of the inventive concept. [Diagram 5] FIG. 1 is a block diagram illustrating a radio access network RAN ​​node (e.g., a base station eNB / gNB) in accordance with some embodiments of the inventive concept. [Figure 6] A block diagram showing a core network CN node (e.g., an AMF node, an SMF node, etc.) according to some embodiments of the inventive concept. [Figure 7] FIG. 1 is a diagram of a BSR format indicating one LCG and a table index according to some embodiments of the inventive concept. [Figure 8] FIG. 13 is a diagram of a BSR format indicating one LCD and a table index according to some embodiments of the inventive concept. [Figure 9] FIG. 1 is a diagram of a BSR format indicating multiple LCIDs and table indexes according to some embodiments of the inventive concept. [Figure 10] FIG. 2 is a signaling diagram illustrating communication between a communication device and a network device according to some embodiments of the inventive concept. [Figure 11] 4 is a flowchart illustrating the operation of a communications device in accordance with some embodiments of the inventive concept. [Figure 12] 4 is a flowchart illustrating the operation of a communications device in accordance with some embodiments of the inventive concept. [Figure 13A] 4 is a flowchart illustrating the operation of a communications device in accordance with some embodiments of the inventive concept. [Figure 13B]4 is a flowchart illustrating the operation of a communications device in accordance with some embodiments of the inventive concept. [Figure 13C] 4 is a flowchart illustrating the operation of a communications device in accordance with some embodiments of the inventive concept. [Figure 13D] 4 is a flowchart illustrating the operation of a communications device in accordance with some embodiments of the inventive concept. [Figure 14A] 4 is a flowchart illustrating the operation of a communications device in accordance with some embodiments of the inventive concept. [Figure 14B] 4 is a flowchart illustrating the operation of a communications device in accordance with some embodiments of the inventive concept. [Figure 14C] 4 is a flowchart illustrating the operation of a communications device in accordance with some embodiments of the inventive concept. [Figure 14D] 4 is a flowchart illustrating the operation of a communications device in accordance with some embodiments of the inventive concept. [Figure 14E] 4 is a flowchart illustrating the operation of a communications device in accordance with some embodiments of the inventive concept. [Figure 14F] 4 is a flowchart illustrating the operation of a communications device in accordance with some embodiments of the inventive concept. [Figure 15] 4 is a flowchart illustrating the operation of a communications device in accordance with some embodiments of the inventive concept. [Figure 16] 4 is a flowchart illustrating the operation of a communications device in accordance with some embodiments of the inventive concept. [Figure 17] 4 is a flowchart illustrating the operation of a communications device in accordance with some embodiments of the inventive concept. [Figure 18] 4 is a flowchart illustrating the operation of a network node, in accordance with some embodiments of the inventive concept. [Figure 19] 1 is a block diagram of a wireless network according to some embodiments. [Figure 20] FIG. 2 is a block diagram of a user equipment according to some embodiments. [Figure 21]FIG. 1 is a block diagram of a virtualization environment, according to some embodiments. [Figure 22] 1 is a block diagram of a communications network connected to a host computer through an intermediate network according to some embodiments. [Figure 23] FIG. 2 is a block diagram of a host computer communicating with user equipment via a base station over a partially wireless connection according to some embodiments. [Figure 24] 1 is a block diagram of a method implemented in a communications system including a host computer, a base station, and user equipment, according to some embodiments. [Diagram 25] 1 is a block diagram of a method implemented in a communications system including a host computer, a base station, and user equipment, according to some embodiments. [Figure 26] 1 is a block diagram of a method implemented in a communications system including a host computer, a base station, and user equipment, according to some embodiments. [Figure 27] 1 is a block diagram of a method implemented in a communications system including a host computer, a base station, and user equipment, according to some embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0019] The inventive concept will now be described more fully hereinafter with reference to the accompanying drawings, in which examples of embodiments of the inventive concept are shown. However, the inventive concept may be embodied in many different forms and should not be construed as being limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the inventive concept to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. It may be implicitly assumed that an element from one embodiment is present / used in another embodiment.

[0020] The following description presents various embodiments of the disclosed subject matter. These embodiments are presented as teaching examples and should not be construed as limiting the scope of the disclosed subject matter. For example, some details of the described embodiments may be modified, omitted, or expanded without departing from the scope of the described subject matter.

[0021] 4 is a block diagram illustrating elements of a communications device 400 (also referred to as a mobile terminal, mobile communications terminal, wireless device, wireless terminal, mobile device, wireless communications terminal, user equipment (UE), user equipment node / terminal / device, etc.) configured to provide wireless communications, in accordance with an embodiment of the inventive concept. (The communications device 400 may be provided, for example, as described below with respect to wireless device 4110 of FIG. 19.) As shown, the communications device UE may include an antenna 407 (e.g., corresponding to antenna 4111 of FIG. 19) and transceiver circuitry 401 (e.g., corresponding to interface 4114 of FIG. 19, also referred to as a transceiver) including a transmitter and a receiver configured to provide uplink and downlink wireless communications with base station(s) of a radio access network (e.g., corresponding to network node 4160 of FIG. 19, also referred to as a RAN node). The communication device UE may also include a processing circuit 403 (e.g., corresponding to the processing circuit 4120 of FIG. 19, also referred to as a processor) coupled to the transceiver circuit, and a memory circuit 405 (e.g., corresponding to the device-readable medium 4130 of FIG. 19, also referred to as a memory) coupled to the processing circuit. The memory circuit 405 may include computer-readable program code that, when executed by the processing circuit 403, causes the processing circuit to perform operations according to embodiments disclosed herein. According to other embodiments, the processing circuit 403 may be defined to include a memory such that a separate memory circuit is not required. The communication device 400 may also include an interface (such as a user interface) coupled to the processing circuit 403, and / or the communication device 400 may be incorporated into a vehicle.

[0022] As described herein, operations of the communication device 400 may be performed by the processing circuitry 403 and / or the transceiver circuitry 401. For example, the processing circuitry 403 may control the transceiver circuitry 401 to transmit communications through the transceiver circuitry 401 over an air interface to a radio access network node (also referred to as a base station) and / or receive communications through the transceiver circuitry 401 over an air interface from a RAN node. Moreover, modules may be stored in the memory circuitry 405 that may provide instructions such that, when the instructions of the modules are executed by the processing circuitry 403, the processing circuitry 403 performs respective operations (e.g., operations described below with respect to exemplary embodiments relating to a communication device). According to some embodiments, the communication device 400 and / or its element(s) / function(s) may be embodied as one or more virtual nodes and / or one or more virtual machines.

[0023] 5 is a block diagram illustrating elements of a radio access network ("RAN") node 500 (also referred to as a network node, base station, eNodeB / eNB, gNodeB / gNB, etc.) of a radio access network configured to provide cellular communications, according to an embodiment of the inventive concept. (The RAN node 500 may be provided, for example, as described below with respect to network node 4160 of FIG. 19.) As shown, the RAN node may include transceiver circuitry 501 (e.g., corresponding to part of interface 4190 of FIG. 19, also referred to as a transceiver) including a transmitter and a receiver configured to provide uplink and downlink wireless communications with mobile terminals. The RAN node may include network interface circuitry 507 (e.g., corresponding to part of interface 4190 of FIG. 19, also referred to as a network interface) configured to provide communications with other nodes of the RAN and / or core network CN (e.g., with other base stations). The network node may also include a processing circuit 503 (e.g., corresponding to processing circuit 4170, also referred to as a processor) coupled to the transceiver circuit, and a memory circuit 505 (e.g., corresponding to device readable medium 4180 of FIG. 19, also referred to as a memory) coupled to the processing circuit. The memory circuit 505 may include computer readable program code that, when executed by the processing circuit 503, causes the processing circuit to perform operations according to embodiments disclosed herein. According to other embodiments, the processing circuit 503 may be defined to include memory such that a separate memory circuit is not required.

[0024] As described herein, operations of the RAN node may be performed by the processing circuitry 503, the network interface 507, and / or the transceiver 501. For example, the processing circuitry 503 may control the transceiver 501 to transmit downlink communications through the transceiver 501 over the air interface to one or more mobile terminals UEs and / or receive uplink communications through the transceiver 501 over the air interface from one or more mobile terminals UEs. Similarly, the processing circuitry 503 may control the network interface 507 to transmit communications through the network interface 507 to one or more other network nodes and / or receive communications from one or more other network nodes through the network interface. Moreover, modules may be stored in the memory 505 that, when their instructions are executed by the processing circuitry 503, provide instructions such that the processing circuitry 503 performs respective operations (e.g., operations described below with respect to exemplary embodiments relating to a RAN node). According to some embodiments, the RAN node 400 and / or its element(s) / function(s) may be embodied as one or more virtual nodes and / or one or more virtual machines.

[0025] According to some other embodiments, the network node may be implemented as a core network CN node lacking a transceiver. In such embodiments, a transmission to the communication device UE may be initiated by the network node such that the transmission to the communication device UE is provided through a network node that includes a transceiver (e.g., through a base station or a RAN node). According to an embodiment in which the network node is a RAN node that includes a transceiver, initiating the transmission may include transmitting through the transceiver.

[0026] 6 is a block diagram illustrating elements of a core network CN node (e.g., SMF node, AMF node, etc.) of a communications network configured to provide cellular communications, according to an embodiment of the inventive concept. As shown, the CN node may include a network interface circuit 607 (also referred to as a network interface) configured to provide communications with other nodes of the core network and / or radio access network RAN. The CN node may also include a processing circuit 603 (also referred to as a processor) coupled to the network interface circuit, and a memory circuit 605 (also referred to as a memory) coupled to the processing circuit. The memory circuit 605 may include computer readable program code that, when executed by the processing circuit 603, causes the processing circuit to perform operations according to embodiments disclosed herein. According to other embodiments, the processing circuit 603 may be defined to include memory such that a separate memory circuit is not required.

[0027] As described herein, the operations of the CN node may be performed by the processing circuitry 603 and / or the network interface circuitry 607. For example, the processing circuitry 603 may control the network interface circuitry 607 to transmit communications through the network interface circuitry 607 to one or more other network nodes and / or to receive communications through the network interface circuitry from one or more other network nodes. Moreover, modules may be stored in the memory 605 that, when their instructions are executed by the processing circuitry 603, may provide instructions that cause the processing circuitry 603 to perform respective operations (e.g., operations described below with respect to example embodiments relating to core network nodes). According to some embodiments, the CN node 600 and / or its element(s) / function(s) may be embodied as one or more virtual nodes and / or one or more virtual machines.

[0028] As indicated before, services including XR services generate packet sizes that can be quite large, which results in the index that the BSR can indicate being of high value. The higher the buffer status index, the larger the buffer size reported. The difference between two consecutive buffer status indexes increases as the index increases. The difference is especially visible in the long BSR table, as shown in FIG. 3. This results in more uncertainty regarding the actual buffer size at the communication device, which also results in the network being able to overshoot the grant provided to the communication device, which affects the overall network capacity.

[0029] For the short BSR table, the maximum size that can be reported is 150.000 bytes. Thus, when a wireless terminal has a buffer size that exceeds this maximum size, the communication device reports an index indicating ">150.000" bytes. This information may be inaccurate and may lead to overshooting of resource grants and / or delays if the network does not provide a large enough resource grant.

[0030] The MAC specification defines two BSR tables, one for short BSR and one for long BSR, but these tables are not suitable for XR services and other services with relatively large packet sizes.

[0031] The current BSR format (i.e., the legacy BSR format) does not allow for new tables other than those currently specified, and the current BSR procedures are not suitable when new tables and formats are introduced. For example, only one BSR MAC CE can be transmitted in a MAC PDU. This is a limiting factor when there are several BSR types that provide more accurate information than the legacy BSR format.

[0032] Various embodiments of the inventive concept provide two main tenets: 1) defining a new BSR format that identifies a BSR among multiple BSR tables, provides buffer status for at least one Logical Channel Identification ("LCID") or Logical Channel Group ("LCG"), and provides a corresponding buffer status index in a designated BSR table; and 2) providing coexistence procedures for legacy and new BSR for regular and periodic BSR procedures, as well as padding BSR procedures.

[0033] Using various embodiments of the inventive concepts described herein achieves more precise buffer status provided to the network, which results in the network not having to overshoot resource grants too much, allowing maximization of network capacity. Latency for critical services can be reduced when various embodiments are used.

[0034] To define the BSR format

[0035] A "new" BSR format is described in which the BSR format can identify one buffer status table of multiple buffer status tables. In one embodiment, this can be accomplished using a new LCID for each new buffer status table. In another embodiment, this can be done by defining a field in the BSR format that indicates the buffer status table.

[0036] Furthermore, the new BSR format should provide buffer status information for at least one LCID. The BSR indicates the LCID for which the buffer status is reported and the buffer status information. Alternatively, the new BSR format may indicate the LCG for which the buffer status is reported and the buffer status.

[0037] Alternatively, the new BSR may provide one or more LCIDs or LCGs along with their respective BSs and respective buffer status tables to be used for each of them. In this case, an L field (length field) may be required in the header, as shown in Figure 9.

[0038] Some example formats are shown in Figures 7, 8, and 9. Note that without limiting the inventive concepts described herein, the length of each of the fields as well as the number of LCGs or LCIDs reported may vary depending on the range one may wish to indicate. For example, other BSR formats may be used.

[0039] Triggering and handling the legacy BSR and the new BSR(s)

[0040] Referring to FIG. 10, a procedure for using a new BSR is shown. In operation 1001, the communication device 400 reports, via RRC, in that the communication device 400 supports one or more of the new buffer status table(s) and the new BSR format(s) (e.g., when there are two or more new BSR formats). These indications of support may be explicit or implicit. For example, the communication device 400 reports that the communication device 400 supports a new BSR format, and implicitly, this implies support of a set of buffer status tables. Alternatively, the communication device 400 reports support of a new BSR, and separately, a second indication indicates support of one or more buffer status tables, either implicitly or explicitly. For example, if the communication device 400 indicates support of a feature, this implicitly means that the communication device 400 also supports buffer tables A and B, but does not support table C. It may also be the case that support of a feature implies support of one or more tables and also support of a new BSR(s).

[0041] In response to receiving a BSR support message indicating support of the new BSR format(s), the network (e.g., network node 500) determines, in operation 1003, which BSR format(s) supported by the communication device should be used. The network sends an RRC configuration message to configure the communication device 400 to use the determined BSR(s) in operation 1005. Furthermore, the network may also instruct the communication device 400 which table from those supported by the communication device 400 should be used. If no table is explicitly indicated, the communication device 400 is allowed to use all tables. Alternatively, the configuration of a feature also implies the configuration of one or more specific tables.

[0042] Additionally, the network may configure and indicate one or more LCIDs or LCGs to which the new BSR and tables apply.

[0043] In an operation 1007, the communications device receives the RRC configuration message and configures the communications device 400. The communications device 400 then transmits an RRC configuration acknowledgement message to the network node 500.

[0044] When the communication device 400 is configured to use the new BSR, the regular BSR is triggered using the legacy condition in operation 1011. The communication device selects the BSR format(s) to use based on the configuration and buffer status in operation 1013. In various embodiments of the inventive concept, the communication device selects the BSR format as follows:

[0045] If only one LCG has data and this LCG or the LCID that received the data and belongs to this LCG is configured to use the new format.

[0046] The new BSR format is used to report data for an LCG or LCID that triggered a regular BSR, in which case the short BSR is not used.

[0047] Alternatively, both a short BSR and a new BSR are triggered: the short BSR format is used to report the LCG (as in the legacy behavior), and the new BSR is used to report the buffers for the LCID.

[0048] In addition to the above, the new BSR is used instead of or in addition to the short BSR if the buffer status is above a certain threshold or the buffer status index in the legacy buffer status table is above a threshold.

[0049] When more than one LCG has data available for transmission, if a regular BSR is triggered by UL data 1) for a logical channel for which a new BSR is configured, or 2) for a logical channel belonging to an LCG configured to use the new BSR, the UE uses the long BSR format as in the legacy case and uses the new BSR format to report the LCID or LCG that triggered the regular BSR.

[0050] Alternatively, all LCIDs or LCGs that are configured to use the new BSR are reported along with the new BSR.

[0051] Alternatively, the long BSR does not include the LCG(s) reported along with the new BSR.

[0052] In addition to the above, the new BSR is used if the buffer status in the configured LCID or LCG is above a certain threshold or if the buffer status index in the legacy buffer status table is above a threshold.

[0053] The periodic BSR follows the same procedure as described above for the regular BSR.

[0054] In the padding BSR, the legacy procedure may be used for the new BSR format. If sufficient padding bits are available after the communication device 400 selects the corresponding legacy BSR format, and if a new BSR (or table) is configured for any LCG or LCID and data for the respective LCG(s) or LCID(s) is in the buffer, the communication device 400 also uses the new BSR to report one or more of the configured LCGs or LCIDs. When not all LCGs or LCIDs can be reported, the communication device 400 selects the one with the highest priority. Alternatively, the new BSR is used if the buffer status for the configured LCG(s) or LCID(s) is above a certain threshold or the buffer status index in the legacy buffer status table is above a threshold.

[0055] In all of these scenarios, the MAC PDU may contain one of the legacy BSR MAC CEs and one or more of the new BSRs.

[0056] When the network receives the new BSR format, the network can allocate more appropriate grants according to the information provided in the new BSR format.

[0057] Operation of communications device 400 (implemented using the block diagram structure of FIG. 4) will now be described with reference to the flowchart of FIG. 11 in accordance with some embodiments of the inventive concept. For example, modules may be stored in memory 405 of FIG. 4 that may provide instructions such that, when the instructions of the modules are executed by respective communications device processing circuitry 403, the processing circuitry 403 performs the respective operations of the flowchart.

[0058] Referring to FIG. 11, in block 1101, the processing circuit 403 receives, via the transceiver circuit 401, a BSR format configuration that specifies at least one non-legacy BSR format and / or a non-legacy buffer status table to be used to report a buffer status report (BSR) to a network node. The BSR format configuration may be in the form of an RRC configuration message. A non-legacy BSR format is defined as a new BSR format that an older communication device (i.e., a legacy device) cannot be configured to use. In other words, a non-legacy BSR format is a format other than a short BSR format, a short truncated BSR format, a long truncated BSR format, and a long BSR format. A legacy BSR format is any one of a short BSR format, a short truncated BSR format, a long truncated BSR format, and a long BSR format.

[0059] The BSR format configuration may be received when the communication device 400 joins the network. One way to receive the configuration is shown in Figure 12. Referring to Figure 12, in block 1201, the processing circuit 403 sends a buffer status report (BSR) indication message via the transceiver circuit 401 to a network node of the network, where the BSR indication message indicates at least one non-legacy BSR format and / or at least one non-legacy buffer status table that the communication device supports.

[0060] In block 1203, the processing circuit 403 receives a configuration message from a network node, the configuration message specifying one or more non-legacy BSR formats and / or one or more non-legacy buffer status tables to be used for BSR reporting. The configuration message may be an RRC configuration message as shown in FIG. 10. The configuration message, in some embodiments, specifies one or more non-legacy BSR formats and / or one or more non-legacy buffer status tables to be used for BSR reporting for an LCG or LCID. In other embodiments, the configuration message specifies an LCG or LCID for which one or more non-legacy BSR formats and / or one or more legacy buffer status tables are to be used.

[0061] At block 1205, the processing circuit 403 configures the communications device 400 for BSR reporting based on the configuration message, thereby creating a BSR reporting configuration. The configuring may include rules to use when selecting a BSR format to use and / or a BSR buffer status table.

[0062] Returning to FIG. 11, in block 1103, the processing circuit 403 selects at least one non-legacy BSR format and / or at least one non-legacy buffer status table from the group of non-legacy BSR formats. The group of non-legacy BSR formats may include one or more non-legacy BSR formats and / or one or more non-legacy buffer status tables. When the BSR format setting limits the non-legacy BSR formats and / or non-legacy buffer status tables to a specific non-legacy BSR format and / or a specific non-legacy buffer status table, the group of non-legacy BSR formats may be limited to the specific non-legacy BSR format and / or the specific non-legacy buffer status table.

[0063] In various other embodiments of the inventive concept, a legacy BSR format and / or a legacy buffer status table are also used. Thus, selecting at least one non-legacy BSR format includes selecting at least one non-legacy BSR format from a group of non-legacy BSR formats and selecting at least one legacy BSR format from a group of legacy BSR formats, and transmitting a BSR report includes transmitting a BSR report including at least one non-legacy BSR format from the group of non-legacy BSR formats and at least one legacy BSR format from the group of legacy BSR formats. Alternatively, at least one non-legacy buffer status table and at least one legacy buffer status table are selected.

[0064] In block 1105, the processing circuit 403 generates a BSR report based on the selected at least one non-legacy BSR format and / or the non-legacy buffer status table. In block 1107, the processing circuit 403 transmits the BSR report toward the network node.

[0065] In some embodiments of the inventive concept, generating a BSR report depends on whether there is only one logical channel group (LCG) with data and this LCG, or the logical channel identification (LCID) belonging to this LCG that received the data, is configured to use a non-legacy BSR format, or whether there is two or more logical channel groups (LCGs) with data available for transmission.

[0066] For example, referring to FIG. 13A, in generating a BSR report in block 1301, in response to only one logical channel group (LCG) having data and the LCG, or the logical channel identification (LCID) belonging to the LCG that received the data, being configured to use the non-legacy BSR format, the processing circuit 403 uses the non-legacy BSR format to generate a BSR report for the data of the LCG or LCID that triggered the BSR report.

[0067] In block 1303, the processing circuit 403 cancels the selection or generation of the short BSR in response to the short BSR being selected or generated. This may occur when the processing circuit 403 triggers a short BSR, but the LCG that triggered the short BSR, or an LCID belonging to this LCG, receives data and is configured to use a non-legacy format. When this occurs, the processing circuit 403 generates a non-legacy BSR and cancels the short BSR.

[0068] Referring to FIG. 13B, in generating a BSR report in block 1305, in response to only one logical channel group (LCG) having data and the LCG or the logical channel identification (LCID) belonging to the LCG that received the data being configured to use the non-legacy BSR format, the processing circuit 403 uses a short BSR to report the LCG and uses the non-legacy BSR format to report the buffer status of the LCID.

[0069] 13C, in generating a BSR report in block 1307, the processing circuit 403 uses the short BSR format to report the BSR in response to only one logical channel group (LCG) having data and the LCG or the logical channel identification (LCID) belonging to the LCG that received the data being configured to use the non-legacy BSR format, and in response to the buffer status being below a first threshold. In response to only one logical channel group (LCG) having data and the LCG or the logical channel identification (LCID) belonging to the LCG that received the data being configured to use the non-legacy BSR format, and in response to the buffer status being above a first threshold, the processing circuit 403 uses the non-legacy BSR format to report the BSR in block 1309.

[0070] In various embodiments, when using a non-legacy BSR format to report the BSR, the processing circuit 403 may also use a short BSR to report the BSR.

[0071] In some embodiments, in response to the buffer status falling below the first threshold and the non-legacy BSR being selected or generated, the processing circuit 403 cancels the selection or generation of the non-legacy BSR. In other embodiments, the processing circuit 403 also uses a short BSR format to report the BSR.

[0072] In block 1311, the processing circuit 403 cancels the selection or generation of the non-legacy BSR in response to the buffer status being below the first threshold and the non-legacy BSR being selected or generated. In block 1313, the processing circuit 403 cancels the selection or generation of the short BSR in response to the buffer status being above the first threshold and the short BSR being selected or generated. This may be done when the processing circuit 403 is triggered to generate a BSR and uses the short BSR format to generate the BSR. When the LCG or LCID that has the data is set to use the non-legacy format and determines that the buffer status is above the first threshold, now the non-legacy BSR should be used to generate the BSR.

[0073] 13D, in generating a BSR report in block 1315, the processing circuit 403 uses a short BSR to report the BSR in response to only one logical channel group (LCG) having data and the LCG or the logical channel identification (LCID) belonging to the LCG that received the data being configured to use the non-legacy BSR format, and in response to the buffer status index being below a second threshold. In response to only one logical channel group (LCG) having data and the LCG or the logical channel identification (LCID) belonging to the LCG that received the data being configured to use the non-legacy BSR format, and in response to the buffer status index being above a second threshold, the processing circuit 403 uses a non-legacy BSR format to report the BSR in block 1317.

[0074] In some embodiments, the processing circuit 403 may have previously selected a non-legacy BSR to use or generated a BSR using a non-legacy BSR. In response to the buffer status index falling below a second threshold and a non-legacy BSR being selected or generated, the processing circuit 403 cancels the selection or generation of the non-legacy BSR in block 1319.

[0075] In some embodiments, the processing circuit 403 may also use a short BSR when using a non-legacy BSR.

[0076] In other embodiments, the processing circuit 403 may have previously selected a non-legacy BSR to use or generated a BSR using a non-legacy BSR when a non-legacy BSR should be used. In response to the buffer status index exceeding a first threshold and a short BSR being selected or generated, the processing circuit 403 cancels the selection or generation of the short BSR in block 1321.

[0077] 14A-14F illustrate various embodiments of the inventive concept when there are two or more logical channel groups (LCGs) with data available for transmission. Referring to FIG. 14A, in block 1401, the processing circuit 403 uses the long BSR format to report buffer status and the non-legacy BSR format to report the LCID or LCG that triggered the BSR in response to there being uplink (UL) data for a logical channel configured with a non-legacy BSR or for a logical channel belonging to an LCG configured to use a non-legacy BSR and the BSR being triggered by the UL data or by a timer expiring.

[0078] 14B, in block 1403, the processing circuit 403 uses the non-legacy BSR format to report buffer status for all LCIDs or LCGs configured to use the non-legacy BSR format in response to there being uplink (UL) data for a logical channel for which the non-legacy BSR is configured or for a logical channel belonging to an LCG configured to use the non-legacy BSR and the BSR being triggered by the UL data or by a timer expiring. In block 1405, the processing circuit 402 uses the legacy BSR, such as the long BSR format, for LCIDs or LCGs that have data and are not configured to use the non-legacy BSR format.

[0079] In other embodiments, the long truncated BSR format is used to report buffer status. Referring to FIG. 14C, in block 1407, the processing circuit 403 uses the long truncated BSR format to report buffer status for an LCID or LCG and uses the non-legacy BSR to report the LCID or LCG in response to there being uplink (UL) data for a logical channel for which a non-legacy BSR is configured or for a logical channel belonging to an LCG configured to use a non-legacy BSR and the BSR being triggered by the UL data or by a timer expiring.

[0080] In response to the long BSR being generated, block 1409 revokes the long BSR.

[0081] 14D, in response to two or more logical channel groups (LCGs) having data available for transmission, the processing circuit 403 uses the non-legacy BSR format to report buffer status for the LCIDs or LCGs in block 1411. In some embodiments, the processing circuit 403 uses the non-legacy BSR to report buffer status for any other LCIDs or LCGs that have data and are configured to use the non-legacy BSR.

[0082] 14E, in response to two or more logical channel groups (LCGs) having data available for transmission and in response to the buffer status in an LCID or LCG configured to use the non-legacy BSR being above a first threshold, a non-legacy BSR is used to report buffer status for the LCID or LCG, block 1413. In various other embodiments, a non-legacy BSR and a long BSR are used to report BSR.

[0083] In response to the buffer status in an LCID or LCG configured to use the non-legacy BSR falling below a first threshold, the long BSR is used to report the buffer status at block 1415. In other embodiments, the processing circuit 403 uses the long BSR to report the buffer status.

[0084] In block 1417, in response to the buffer status falling below the first threshold and a non-legacy BSR being selected or generated, the processing circuit 403 cancels the selection or generation of the non-legacy BSR. In block 1419, in response to the buffer status rising above the first threshold and a long BSR being selected or generated, the processing circuit 403 cancels the selection or generation of the long BSR (or long truncated BSR).

[0085] 14F, in response to two or more logical channel groups (LCGs) having data available for transmission and in response to a buffer status index for an LCID or LCG configured to use a non-legacy BSR in the legacy buffer status table being above a second threshold, the processing circuit 403 uses the non-legacy BSR format to report the buffer status in block 1421. In block 1423, in response to two or more logical channel groups (LCGs) having data available for transmission and in response to a buffer status index in the legacy buffer status table being below a second threshold, the processing circuit 403 uses the long BSR format to report the buffer status.

[0086] In response to the buffer status index falling below the second threshold and a non-legacy BSR being selected or generated, the processing circuit 403 cancels the selection or generation of the non-legacy BSR in block 1425. In response to the buffer status index rising above the first threshold and a long BSR being selected or generated, the processing circuit 403 cancels the long BSR in block 1427.

[0087] In some embodiments, in response to the buffer status index in the legacy buffer status table exceeding a second threshold, the non-legacy BSR and the long BSR are used to report the BSR.

[0088] In other embodiments, a long truncated BSR format is used instead of a long BSR to report buffer status, and when this occurs, the processing circuit 403 cancels the long BSR in response to the long BSR being selected or generated.

[0089] In various other embodiments of the inventive concept, padding bits may be used in generating a BSR report. Referring to Figure 15, in block 1501, the processing circuit 401 uses the non-legacy format to report buffer status for the at least one LCG or at least one LCID using the remaining padding bits in response to there being a sufficient number of padding bits remaining in the buffer for messages being sent towards the network node after the legacy BSR format is added to the buffer and there being at least one LCG or at least one LCID configured to use the non-legacy BSR format.

[0090] 16, in some embodiments, there may not be a sufficient number of padding bits remaining for all of the LCGs and LCIDs configured to use the non-legacy BSR format to use the remaining padding bits. Thus, in block 1601, the processing circuit 403 reports the buffer status of the at least one LCG and at least one LCID in the highest priority order using the remaining padding bits in response to not all LCGs or LCIDs of the at least one LCG and at least one LCID being able to use the remaining padding bits.

[0091] 17, in another embodiment, one or more thresholds are used to determine whether to use padding bits. In block 1701, the processing circuit 403 uses the non-legacy format to report the buffer status for the at least one LCG or at least one LCID using the remaining padding bits in response to there being a sufficient number of padding bits remaining in the buffer for a message being sent towards the network node after the legacy BSR format is added to the buffer and there is at least one LCG or at least one LCID configured to use the non-legacy BSR format, and if the buffer status for the configured LCG(s) or LCID(s) exceeds a first threshold or if the buffer status index in the legacy buffer status table exceeds a second threshold.

[0092] Operation of the RAN node 500 (implemented using the structure of FIG. 5) will now be described with reference to the flowchart of FIG. 18, in accordance with some embodiments of the inventive concept. For example, modules may be stored in the memory 505 of FIG. 5 that may provide instructions such that, when the instructions of the modules are executed by the respective RAN node processing circuitry 503, the processing circuitry 503 performs the respective operations of the flowchart.

[0093] Referring to FIG. 18, in block 1801, the processing circuit 503 receives a buffer status report ("BSR") indication message from a communication device, the BSR indication message indicating at least one non-legacy BSR format and / or at least one non-legacy buffer status table supported by the communication device.

[0094] In block 1803, the processing circuit 503 determines which non-legacy BSR formats and / or non-legacy BSR buffer status tables are supported by the communication device based on the BSR indication message. In block 1805, the processing circuit 503 determines at least one non-legacy BSR format and / or at least one non-legacy BSR buffer status table for use by the communication device based on which non-legacy BSR formats and / or non-legacy BSR buffer status tables are supported by the communication device.

[0095] In block 1807, the processing circuit 503 transmits a radio resource control (RRC) configuration message via the transceiver 501 and / or the network interface 507 indicating one or more non-legacy BSR formats and / or one or more non-legacy buffer status tables to be used for BSR reporting for use by the communications device. The processing circuit 503 receives a configuration acknowledgement message from the communications device 200.

[0096] Determining at least one non-legacy BSR format and / or at least one non-legacy BSR buffer status table may be performed by comparing the non-legacy BSR format and non-legacy BSR buffer status table supported by the network node with the non-legacy BSR format and non-legacy BSR buffer status table indicated by the communication device 400. If the comparison results in a no match, the RRC configuration message indicates that the non-legacy BSR format and / or non-legacy BSR buffer status table may not be used. Alternatively, the RRC configuration message may list the non-legacy BSR format and / or non-legacy buffer status table supported by the network node in such a case. A no match may occur when the network node supports a different non-legacy BSR format and / or non-legacy buffer status table than the non-legacy BSR format and / or non-legacy buffer status table.

[0097] When there is a match, the network node determines which of the matching non-legacy BSR formats and / or non-legacy buffer status tables should be used by communications device 200. The network node may specify only one, several, or all of the matching non-legacy BSR formats and / or non-legacy buffer status tables for communications device 200 to use.

[0098] At block 1809, the processing circuit 503 receives a BSR having at least one non-legacy BSR format from the communication device 200.

[0099] Various operations from the flowchart of Figure 18 may be optional with respect to some embodiments of the RAN node and related methods. With respect to the method of example embodiment 37 (described below), for example, the operation of block 1809 of Figure 18 may be optional.

[0100] Exemplary embodiments Exemplary embodiments are described below.

[0101] Embodiment 1. A method implemented by a communication device in a network, the method comprising: Receiving a BSR format configuration (1101) that specifies at least one non-legacy BSR format and / or a non-legacy buffer status table to be used to report a BSR to a network node; selecting (1103) at least one non-legacy BSR format and / or at least one non-legacy buffer status table from a group of non-legacy BSR formats; generating a BSR report based on the selected at least one non-legacy BSR format and / or the non-legacy buffer status table (1105); Sending a BSR report to the network node (1107); A method comprising:

[0102] Embodiment 2. The method of embodiment 1, wherein selecting at least one non-legacy BSR format includes selecting at least one non-legacy BSR format from a group of non-legacy BSR formats and selecting at least one legacy BSR format from a group of legacy BSR formats, and transmitting a BSR report includes transmitting a BSR report including at least one non-legacy BSR format from the group of non-legacy BSR formats and at least one legacy BSR format from the group of legacy BSR formats.

[0103] Embodiment 3. sending a Buffer Status Report (BSR) indication message to a network node of a network (1201), the BSR indication message indicating at least one non-legacy BSR format and / or at least one non-legacy buffer status table supported by the communication device; Receiving a configuration message from a network node (1203), the configuration message specifying one or more non-legacy BSR formats and / or one or more non-legacy buffer status tables to be used for BSR reporting; configuring the communication device for BSR reporting based on the configuration message, thereby creating a BSR reporting configuration (1205); 3. The method of embodiment 1 or 2, further comprising:

[0104] Embodiment 4. The method of embodiment 3, in which the configuration message specifies, for an LCG or LCID, one or more non-legacy BSR formats and / or one or more non-legacy buffer status tables to be used for BSR reporting.

[0105] Embodiment 5. The method of embodiment 3, in which the configuration message specifies an LCG or LCID for which one or more non-legacy BSR formats and / or one or more legacy buffer status tables should be used.

[0106] Embodiment 6. Generating a BSR report comprises: in response to only one logical channel group (LCG) having data and the LCG, or a logical channel identification (LCID) belonging to the LCG that received the data, being configured to use a non-legacy BSR format; Use non-legacy BSR formats to generate BSR reports for LCGs or LCIDs (1301) 6. The method of any one of embodiments 1 to 5, comprising:

[0107] Embodiment 7. In response to the short BSR being selected or generated, canceling the selection or generation of the short BSR (1303). 7. The method of embodiment 6, further comprising:

[0108] Embodiment 8. Generating a BSR report comprises: in response to only one logical channel group (LCG) having data and the LCG, or a logical channel identification (LCID) belonging to the LCG that received the data, being configured to use a non-legacy BSR format; Use short BSR to report LCG or LCID, and use non-legacy BSR format to report buffer status of LCG or LCID (1305) 6. The method of any one of embodiments 1 to 5, comprising:

[0109] Embodiment 9. Generating a BSR report comprises: in response to only one logical channel group (LCG) having data and the LCG, or a logical channel identification (LCID) belonging to the LCG that received the data, being configured to use a non-legacy BSR format; using a short BSR to report a BSR in response to the buffer status falling below a first threshold (1307); using the non-legacy BSR to report the BSR in response to the buffer status exceeding a first threshold (1309); 6. The method of any one of embodiments 1 to 5, comprising:

[0110] Embodiment 10. In response to the buffer status falling below a first threshold and the non-legacy BSR being selected or created, canceling the selection or creation of the non-legacy BSR (1311). 10. The method of embodiment 9, further comprising:

[0111] Embodiment 11. The method of embodiment 9 or 10, wherein using a non-legacy BSR includes using a non-legacy BSR and a short BSR to report the BSR.

[0112] Embodiment 12. In response to the buffer status exceeding the first threshold and the short BSR being selected or generated, canceling the selection or generation of the short BSR (1313). 11. The method of embodiment 9 or 10, further comprising:

[0113] Embodiment 13. The generating of the BSR report comprises: in response to only one logical channel group (LCG) having data and the LCG, or a logical channel identification (LCID) belonging to the LCG that received the data, being configured to use a non-legacy BSR format; using a short BSR to report a BSR in response to the buffer status index falling below a second threshold (1315); using a non-legacy BSR format to report a BSR in response to the buffer status index in the legacy buffer status index exceeding a second threshold (1317); 6. The method of any one of embodiments 1 to 5, comprising:

[0114] Embodiment 14. canceling the selection or creation of the non-legacy BSR in response to the buffer status index falling below a second threshold and the non-legacy BSR being selected or created (1319). 14. The method of embodiment 13, further comprising:

[0115] Embodiment 15. The method of embodiment 13 or 14, wherein using a non-legacy BSR includes using a non-legacy BSR and a short BSR to report the BSR.

[0116] Embodiment 16. In response to the buffer status index exceeding a first threshold and a short BSR being selected or generated, canceling the selection or generation of the short BSR (1321). 15. The method of any one of embodiments 12 to 14, further comprising:

[0117] Embodiment 17. The generating of the BSR report comprises: in response to two or more logical channel groups (LCGs) having data available for transmission; In response to uplink (UL) data for a logical channel for which a non-legacy BSR is configured or for a logical channel belonging to an LCG that is configured to use a non-legacy BSR, the BSR being triggered by the UL data or by a timer expiring, Use the long BSR format to report buffer status and the non-legacy BSR format to report LCID or LCG (1401) 17. The method of any one of embodiments 1 to 16, comprising:

[0118] Embodiment 18. The generating of the BSR report comprises: in response to two or more logical channel groups (LCGs) having data available for transmission; In response to uplink (UL) data for a logical channel for which a non-legacy BSR is configured or for a logical channel belonging to an LCG that is configured to use a non-legacy BSR, the BSR being triggered by the UL data or by a timer expiring, Using a non-legacy BSR format to report buffer status for an LCID or LCG (1403); using the long BSR format to report buffer status for logical channels that have data and for which a non-legacy BSR has not been configured, or for logical channels that have data and belong to an LCG that is not configured to use a non-legacy BSR (1405); 17. The method of any one of embodiments 1 to 16, comprising:

[0119] Embodiment 19. The generating of the BSR report comprises: in response to two or more logical channel groups (LCGs) having data available for transmission; In response to uplink (UL) data for a logical channel for which a non-legacy BSR is configured or for a logical channel belonging to an LCG that is configured to use a non-legacy BSR, the BSR being triggered by the UL data or by a timer expiring, Use the long truncated BSR format for reporting buffer status and the non-legacy BSR format for reporting LCID or LCG (1407) 17. The method of any one of embodiments 1 to 16, comprising:

[0120] EMBODIMENT 20. In response to the creation of a long BSR, cancel the long BSR (1409). 20. The method of embodiment 19, further comprising:

[0121] Embodiment 21. Generating a BSR report comprises: in response to two or more logical channel groups (LCGs) having data available for transmission; In response to uplink (UL) data for a logical channel for which a non-legacy BSR is configured or for a logical channel belonging to an LCG that is configured to use a non-legacy BSR, and the BSR is triggered by the UL data, Use non-legacy BSR format to report buffer status for LCID or LCG (1411) 17. The method of any one of embodiments 1 to 16, comprising:

[0122] EMBODIMENT 22. Use the non-legacy BSR format to report buffer status for any other LCID or LCG that has data and is configured to use the non-legacy BSR format. 22. The method of embodiment 21, further comprising:

[0123] Embodiment 23. Generating a BSR report comprises: in response to two or more logical channel groups (LCGs) having data available for transmission; In response to uplink (UL) data for a logical channel for which a non-legacy BSR is configured or for a logical channel belonging to an LCG that is configured to use a non-legacy BSR, and the BSR is triggered by the UL data, using a non-legacy BSR and using a non-legacy BSR format to report buffer status for all LCIDs or LCGs configured to have data (1411); shall use the long BSR format to report buffer status for all LCIDs or LCGs that are not configured to use the non-legacy BSR and have data. 17. The method of any one of embodiments 1 to 16, comprising:

[0124]

[0036] Embodiment 24. The generating of the BSR report comprises: in response to two or more logical channel groups (LCGs) having data available for transmission; using the non-legacy BSR to report buffer status for the LCID or LCG in response to the buffer status in the LCID or LCG configured to use the non-legacy BSR exceeding a first threshold (1413); using the long BSR to report the buffer status in response to the buffer status in the LCID or LCG configured to use the non-legacy BSR falling below a first threshold (1415); 17. The method of any one of embodiments 1 to 16, comprising:

[0125] 25. In response to the buffer status falling below a first threshold and the non-legacy BSR being selected or created, canceling the selection or creation of the non-legacy BSR (1417). 25. The method of embodiment 24, further comprising:

[0126] Embodiment 26. The method of embodiment 24 or 25, wherein using a non-legacy BSR includes using a non-legacy BSR and a long BSR to report the BSR.

[0127] EMBODIMENT 27. In response to the buffer status exceeding the first threshold and the long BSR being selected or generated, canceling the selection or generation of the long BSR (1419). 24. The method of embodiment 22 or 23, further comprising: Embodiment 28. The generating of the BSR report comprises: in response to two or more logical channel groups (LCGs) having data available for transmission; using the non-legacy BSR to report buffer status for the LCID or LCG in response to the buffer status in the LCID or LCG configured to use the non-legacy BSR exceeding a first threshold (1413); using the long truncated BSR to report buffer status in response to a buffer status in an LCID or LCG configured to use a non-legacy BSR falling below a first threshold (1415); 17. The method of any one of embodiments 1 to 16, comprising:

[0128]

[0046] Embodiment 29. The method of embodiment 28, in response to the long BSR being generated, canceling (1419) the long BSR.

[0129]

[0036] Embodiment 30. The generating of the BSR report comprises: in response to two or more logical channel groups (LCGs) having data available for transmission; using a non-legacy BSR format to report buffer status in response to a buffer status index for an LCID or LCG configured to use a non-legacy BSR in the legacy buffer status table exceeding a second threshold (1421); using a long BSR format to report buffer status in response to a buffer status index for an LCID or LCG configured to use a non-legacy BSR in the legacy buffer status table falling below a second threshold (1423); 17. The method of any one of embodiments 1 to 16, comprising:

[0130] EMBODIMENT 31. and canceling the selection or creation of the non-legacy BSR in response to the buffer status index falling below a second threshold and the non-legacy BSR being selected or created (1425). 31. The method of embodiment 30, further comprising:

[0131] Embodiment 32. The method of embodiment 30 or 31, wherein using a non-legacy BSR includes using a non-legacy BSR and a long BSR to report the BSR.

[0132] EMBODIMENT 33. In response to the buffer status index exceeding a first threshold and the long BSR being selected or generated, canceling the selection or generation of the long BSR (1427). 32. The method of embodiment 30 or 31, further comprising:

[0133]

[0036] Embodiment 34. The generating of the BSR report comprises: in response to two or more logical channel groups (LCGs) having data available for transmission; using the non-legacy BSR to report buffer status for the LCID or LCG in response to the buffer status index in the LCID or LCG configured to use the non-legacy BSR exceeding a second threshold (1421); using the long truncated BSR to report buffer status in response to a buffer status index in an LCID or LCG configured to use a non-legacy BSR falling below a first threshold (1423); 17. The method of any one of embodiments 1 to 16, comprising:

[0134]

[0036] Embodiment 35. In response to the long BSR being generated, canceling (1427) the long BSR. The method of embodiment 34.

[0135] Embodiment 36. Generating a BSR report based on a selected BSR format and a buffer status table includes: in response to a sufficient number of padding bits remaining in the buffer after the legacy BSR format has been added to the buffer for a message being sent toward the network node and to at least one LCG or at least one LCID configured to use the non-legacy BSR format, using the remaining padding bits to report buffer status for the at least one LCG or at least one LCID (1501). 36. The method of any one of the preceding embodiments, comprising:

[0136] Embodiment 37. The method of embodiment 36, in response to not all LCGs or LCIDs of the at least one LCG and at least one LCID being able to use the remaining padding bits, reporting (1601) the buffer status of the at least one LCG and at least one LCID in the order of highest priority using the remaining padding bits.

[0137] Embodiment 38. The step of generating a BSR report based on a selected BSR format and a buffer status table includes: in response to a sufficient number of padding bits remaining in the buffer after the legacy BSR format is added to the buffer for a message being sent towards the network node and at least one LCG or at least one LCID configured to use the non-legacy BSR format, and if the buffer status for the configured LCG(s) or LCID(s) exceeds a first threshold or if a buffer status index in the legacy buffer status table exceeds a second threshold, using the non-legacy format to report buffer status for the at least one LCG or at least one LCID using the remaining padding bits (1701). 36. The method of any one of the preceding embodiments, comprising:

[0138] Embodiment 39. A communication device (400) adapted to perform operations, the operations including: Receiving a BSR format configuration (1101) that specifies at least one non-legacy BSR format and / or a non-legacy buffer status table to be used to report a BSR to a network node; selecting (1103) at least one non-legacy BSR format and / or at least one non-legacy buffer status table from a group of non-legacy BSR formats; generating a BSR report based on the selected at least one non-legacy BSR format and / or the non-legacy buffer status table (1105); Sending a BSR report to the network node (1107); A communication device (400).

[0139] Embodiment 40. A communications device as described in embodiment 39, wherein the communications device is adapted to perform the operations described in any one of embodiments 2 to 38.

[0140] Embodiment 41. A communication device (400), comprising: A processing circuit (403); and a memory (405) coupled to the processing circuit, the memory containing instructions that, when executed by the processing circuit, cause the communications device to perform operations, the operations including: Receiving a BSR format configuration (1101) that specifies at least one non-legacy BSR format and / or a non-legacy buffer status table to be used to report a BSR to a network node; selecting (1103) at least one non-legacy BSR format and / or at least one non-legacy buffer status table from a group of non-legacy BSR formats; generating a BSR report based on the selected at least one non-legacy BSR format and / or the non-legacy buffer status table (1105); Sending a BSR report to the network node (1107); A communication device (400).

[0141] Embodiment 42. The communications device (400) of embodiment 41, wherein, in selecting at least one non-legacy BSR format, the memory includes instructions that, when executed by the processing circuit, cause the communications device to perform operations, the operations including selecting at least one non-legacy BSR format from a group of non-legacy BSR formats and selecting at least one legacy BSR format from a group of legacy BSR formats, and transmitting a BSR report includes transmitting a BSR report including at least one non-legacy BSR format from the group of non-legacy BSR formats and at least one legacy BSR format from the group of legacy BSR formats.

[0142] Embodiment 43. A memory includes instructions that, when executed by a processing circuit, cause a communications device to perform operations, the operations including: sending a Buffer Status Report (BSR) indication message to a network node of a network (1201), the BSR indication message indicating at least one non-legacy BSR format and / or at least one non-legacy buffer status table supported by the communication device; Receiving a configuration message from a network node (1203), the configuration message specifying one or more non-legacy BSR formats and / or one or more non-legacy buffer status tables to be used for BSR reporting; configuring the communication device for BSR reporting based on the configuration message, thereby creating a BSR reporting configuration (1205); 43. The communication device (400) of embodiment 41 or 42, further comprising:

[0143]

[0023] Embodiment 44. A communications device (400) as described in embodiment 43, wherein the configuration message specifies, for an LCG or LCID, one or more non-legacy BSR formats and / or one or more non-legacy buffer status tables to be used for BSR reporting.

[0144]

[0023] Embodiment 45. The communications device (400) of embodiment 43, wherein the configuration message specifies an LCG or LCID for which one or more non-legacy BSR formats and / or one or more legacy buffer status tables are to be used.

[0145]

[0036] Embodiment 46. In generating a BSR report, the memory includes instructions that, when executed by the processing circuit, cause the communications device to perform operations, the operations including: in response to only one logical channel group (LCG) having data and the LCG, or a logical channel identification (LCID) belonging to the LCG that received the data, being configured to use a non-legacy BSR format; Use non-legacy BSR formats to generate BSR reports for data on the LCG or LCID that triggered the BSR report (1301) 46. ​​The communication device (400) of any one of embodiments 41 to 45, comprising:

[0146] EMBODIMENT 47. In response to the short BSR being selected or generated, canceling the selection or generation of the short BSR (1303). 47. The communication device (400) of embodiment 46, further comprising:

[0147]

[0036] Embodiment 48. In generating a BSR report, the memory includes instructions that, when executed by the processing circuit, cause the communications device to perform operations, the operations including: in response to only one logical channel group (LCG) having data and the LCG, or a logical channel identification (LCID) belonging to the LCG that received the data, being configured to use a non-legacy BSR format; Use short BSR to report LCG and non-legacy BSR format to report buffer status for LCID (1305) 46. ​​The communication device (400) of any one of embodiments 41 to 45, comprising:

[0148]

[0036] Embodiment 49. In generating a BSR report, the memory includes instructions that, when executed by the processing circuit, cause the communications device to perform operations, the operations including: in response to only one logical channel group (LCG) having data and the LCG, or a logical channel identification (LCID) belonging to the LCG that received the data, being configured to use a non-legacy BSR format; using a short BSR to report a BSR in response to the buffer status falling below a first threshold (1307); using the non-legacy BSR to report the BSR in response to the buffer status exceeding a first threshold (1309); 46. ​​The communication device (400) of any one of embodiments 41 to 45, comprising:

[0149]

[0046] Embodiment 50. The memory includes further instructions that, when executed by the processing circuit, cause the communications device to perform operations, the operations being: canceling the selection or creation of the non-legacy BSR in response to the buffer status falling below a first threshold and the non-legacy BSR being selected or created (1311); 50. The communication device (400) of embodiment 49, further comprising:

[0150] Embodiment 51. A communications device (400) as described in embodiment 49 or 50, wherein when using a non-legacy BSR, the memory includes instructions that, when executed by the processing circuit, cause the communications device to perform operations, the operations including using a non-legacy BSR and a short BSR to report a BSR.

[0151]

[0046] Embodiment 52. The memory includes further instructions that, when executed by the processing circuit, cause the communications device to perform operations, the operations being: In response to the buffer status exceeding the first threshold and the short BSR being selected or generated, canceling the selection or generation of the short BSR (1313). The communication device (400) of embodiment 49 or 50, further comprising:

[0152]

[0023] Embodiment 53. In generating a BSR report, the memory includes instructions that, when executed by the processing circuit, cause the communications device to perform operations, the operations including: in response to only one logical channel group (LCG) having data and the LCG, or a logical channel identification (LCID) belonging to the LCG that received the data, being configured to use a non-legacy BSR format; using a short BSR to report a BSR in response to the buffer status index falling below a second threshold (1315); using a non-legacy BSR format to report a BSR in response to the buffer status index in the legacy buffer status index exceeding a second threshold (1317); 46. ​​The communication device (400) of any one of embodiments 41 to 45, comprising:

[0153]

[0046] Embodiment 54. The memory includes further instructions that, when executed by the processing circuit, cause the communications device to perform operations, the operations being: canceling the selection or creation of the non-legacy BSR in response to the buffer status index falling below a second threshold and the non-legacy BSR being selected or created (1319). 54. The communication device (400) of embodiment 53, further comprising:

[0154] Embodiment 55. A communications device (400) as described in embodiment 53 or 54, wherein when using a non-legacy BSR, the memory includes instructions that, when executed by the processing circuit, cause the communications device to perform operations, the operations including using a non-legacy BSR and a short BSR to report a BSR.

[0155]

[0046] Embodiment 56. The memory includes further instructions that, when executed by the processing circuit, cause the communications device to perform operations, the operations being: In response to the buffer status index exceeding a first threshold and a short BSR being selected or generated, canceling the selection or generation of the short BSR (1321). 55. The communication device (400) of embodiment 53 or 54, further comprising:

[0156]

[0023] Embodiment 57. In generating a BSR report, the memory includes instructions that, when executed by the processing circuit, cause the communications device to perform operations, the operations including: in response to two or more logical channel groups (LCGs) having data available for transmission; In response to uplink (UL) data for a logical channel for which a non-legacy BSR is configured or for a logical channel belonging to an LCG that is configured to use a non-legacy BSR, the BSR being triggered by the UL data or by a timer expiring, Use the long BSR format to report buffer status and the non-legacy BSR format to report the LCID or LCG that triggered the BSR (1401) 57. The communication device (400) of any one of embodiments 41 to 56, comprising:

[0157]

[0023] Embodiment 58. In generating a BSR report, the memory includes instructions that, when executed by the processing circuit, cause the communications device to perform operations, the operations including: in response to two or more logical channel groups (LCGs) having data available for transmission; In response to uplink (UL) data for a logical channel for which a non-legacy BSR is configured or for a logical channel belonging to an LCG that is configured to use a non-legacy BSR, the BSR being triggered by the UL data or by a timer expiring, Use of a non-legacy BSR format for reporting buffer status and the LCID or LCG that triggered the BSR (1403); Using the long BSR format to report buffer status for logical channels for which a non-legacy BSR has not been configured or for logical channels belonging to an LCG that is not configured to use a non-legacy BSR (1405); 57. The communication device (400) of any one of embodiments 41 to 56, comprising:

[0158]

[0023] Embodiment 59. In generating a BSR report, the memory includes instructions that, when executed by the processing circuit, cause the communications device to perform operations, the operations including: in response to two or more logical channel groups (LCGs) having data available for transmission; In response to uplink (UL) data for a logical channel for which a non-legacy BSR is configured or for a logical channel belonging to an LCG that is configured to use a non-legacy BSR, the BSR being triggered by the UL data or by a timer expiring, Use the long truncated BSR format for reporting buffer status and the non-legacy BSR format for reporting LCID or LCG (1407) 57. The communication device (400) of any one of embodiments 41 to 56, comprising:

[0159]

[0036] Embodiment 60. The memory includes further instructions that, when executed by the processing circuit, cause the communications device to perform operations, the operations being: In response to the creation of a long BSR, cancel the long BSR (1409). 60. The communication device (400) of embodiment 59, further comprising:

[0160]

[0023] Embodiment 61. In generating a BSR report, the memory includes instructions that, when executed by the processing circuit, cause the communications device to perform operations, the operations including: in response to two or more logical channel groups (LCGs) having data available for transmission; Use non-legacy BSR format to report buffer status for LCID or LCG (1411) 47. The method of any one of embodiments 41 to 46, comprising:

[0161] 62. Use the non-legacy BSR format to report buffer status for any other LCID or LCG that has data and is configured to use the non-legacy BSR format. 62. The method of embodiment 61, further comprising:

[0162]

[0026] Embodiment 63. The generating of the BSR report comprises: in response to two or more logical channel groups (LCGs) having data available for transmission; In response to uplink (UL) data for a logical channel for which a non-legacy BSR is configured or for a logical channel belonging to an LCG that is configured to use a non-legacy BSR, and the BSR is triggered by the UL data, using a non-legacy BSR and using a non-legacy BSR format to report buffer status for all LCIDs or LCGs configured to have data (1411); shall use the long BSR format to report buffer status for all LCIDs or LCGs that are not configured to use the non-legacy BSR and have data. 47. The method of any one of embodiments 41 to 46, comprising:

[0163]

[0023] Embodiment 64. In generating a BSR report, the memory includes instructions that, when executed by the processing circuit, cause the communications device to perform operations, the operations including: in response to two or more logical channel groups (LCGs) having data available for transmission; using the non-legacy BSR to report buffer status for the LCID or LCG in response to the buffer status in the LCID or LCG configured to use the non-legacy BSR exceeding a first threshold (1413); using the long BSR to report the buffer status in response to the buffer status in the LCID or LCG configured to use the non-legacy BSR falling below a first threshold (1415); 47. The method of any one of embodiments 41 to 46, comprising:

[0164]

[0023] Embodiment 65. The memory includes further instructions that, when executed by the processing circuit, cause the communications device to perform operations, the operations being: In response to the buffer status falling below a first threshold and the non-legacy BSR being selected or created, canceling the selection or creation of the non-legacy BSR (1417). 65. The communication device (400) of embodiment 64, further comprising:

[0165] Embodiment 66. A communications device (400) as described in embodiment 64 or 65, wherein when using a non-legacy BSR, the memory includes instructions that, when executed by the processing circuit, cause the communications device to perform operations, the operations including using a non-legacy BSR and a long BSR to report a BSR.

[0166]

[0046] Embodiment 67. The memory includes further instructions that, when executed by the processing circuit, cause the communications device to perform operations, the operations being: In response to the buffer status exceeding the first threshold and the long BSR being selected or generated, canceling the selection or generation of the long BSR (1419). 66. The communication device (400) of embodiment 64 or 65, further comprising:

[0167]

[0023] Embodiment 68. In generating a BSR report, the memory includes instructions that, when executed by the processing circuit, cause the communications device to perform operations, the operations including: in response to two or more logical channel groups (LCGs) having data available for transmission; using the non-legacy BSR to report buffer status for the LCID or LCG in response to the buffer status in the LCID or LCG configured to use the non-legacy BSR exceeding a first threshold (1413); using the long truncated BSR to report buffer status in response to a buffer status in an LCID or LCG configured to use a non-legacy BSR falling below a first threshold (1415); 47. The communication device (400) of any one of embodiments 41 to 46, comprising:

[0168] Embodiment 69. The communications device (400) of embodiment 67, wherein the memory includes further instructions that, when executed by the processing circuit, cause the communications device to perform operations, the operations further including canceling (1419) the long BSR in response to the long BSR being generated.

[0169]

[0023] Embodiment 70. In generating a BSR report, the memory includes instructions that, when executed by the processing circuit, cause the communications device to perform operations, the operations including: in response to two or more logical channel groups (LCGs) having data available for transmission; using a non-legacy BSR format to report buffer status in response to a buffer status index for an LCID or LCG configured to use a non-legacy BSR in the legacy buffer status table exceeding a second threshold (1421); using a long BSR format to report buffer status in response to a buffer status index for an LCID or LCG configured to use a non-legacy BSR in the legacy buffer status table falling below a second threshold (1423); 47. The communication device (400) of any one of embodiments 41 to 46, comprising:

[0170]

[0046] Embodiment 71. The memory includes further instructions that, when executed by the processing circuit, cause the communications device to perform operations, the operations being: and canceling the selection or creation of the non-legacy BSR in response to the buffer status index falling below a second threshold and the non-legacy BSR being selected or created (1425). 71. The communication device (400) of embodiment 70, further comprising:

[0171] Embodiment 72. A communications device (400) as described in embodiment 70 or 71, wherein when using a non-legacy BSR, the memory includes instructions that, when executed by the processing circuit, cause the communications device to perform operations, the operations including using a non-legacy BSR and a long BSR to report a BSR.

[0172]

[0046] Embodiment 73. The memory includes further instructions that, when executed by the processing circuit, cause the communications device to perform operations, the operations being: In response to the buffer status index exceeding a first threshold and the long BSR being selected or generated, canceling the selection or generation of the long BSR (1427). 72. The communication device (400) of embodiment 70 or 71, further comprising:

[0173]

[0023] Embodiment 74. In generating a BSR report, the memory includes instructions that, when executed by the processing circuit, cause the communications device to perform operations, the operations including: in response to two or more logical channel groups (LCGs) having data available for transmission; using the non-legacy BSR to report buffer status for the LCID or LCG in response to a buffer status index in the LCID or LCG configured to use the non-legacy BSR exceeding a first threshold (1421); using the long truncated BSR to report buffer status in response to a buffer status index in an LCID or LCG configured to use a non-legacy BSR falling below a first threshold (1423); 47. The communication device (400) of any one of embodiments 41 to 46, comprising:

[0174] Embodiment 75. The communications device (400) of embodiment 74, wherein the memory includes further instructions that, when executed by the processing circuit, cause the communications device to perform operations, the operations further including canceling (1427) the long BSR in response to the long BSR being generated.

[0175]

[0036] Embodiment 76. In generating a BSR report based on a selected BSR format and a buffer status table, the memory includes instructions that, when executed by the processing circuit, cause the communications device to perform operations, the operations including: in response to a sufficient number of padding bits remaining in the buffer after the legacy BSR format has been added to the buffer for a message being sent toward the network node and to at least one LCG or at least one LCID configured to use the non-legacy BSR format, using the remaining padding bits to report buffer status for the at least one LCG or at least one LCID (1501). 76. The communication device (400) of any one of embodiments 41 to 75, comprising:

[0176] Embodiment 77. A communications device (400) as described in embodiment 76, wherein the memory includes further instructions that, when executed by the processing circuit, cause the communications device to perform operations, the operations further including: reporting (1601) a buffer status of the at least one LCG and at least one LCID in highest priority order using the remaining padding bits in response to not all LCGs or LCIDs of the at least one LCG and at least one LCID being able to use the remaining padding bits.

[0177]

[0036] Embodiment 78. In generating a BSR report based on a selected BSR format and a buffer status table, the memory includes instructions that, when executed by the processing circuit, cause the communications device to perform operations, the operations including: in response to a sufficient number of padding bits remaining in the buffer after the legacy BSR format is added to the buffer for a message being sent towards the network node and at least one LCG or at least one LCID configured to use the non-legacy BSR format, and if the buffer status for the configured LCG(s) or LCID(s) exceeds a first threshold or if a buffer status index in the legacy buffer status table exceeds a second threshold, using the non-legacy format to report buffer status for the at least one LCG or at least one LCID using the remaining padding bits (1701). 76. The communication device (400) of any one of embodiments 41 to 75, comprising:

[0178] Embodiment 79. A computer program comprising a program code to be executed by a processing circuit (403) of a communications device (400), whereby execution of the program code causes the communications device (400) to perform the operations described in any one of embodiments 1 to 38.

[0179] Embodiment 80. A computer program product comprising a non-transitory storage medium containing program code to be executed by a processing circuit (403) of a communications device (400), whereby execution of the program code causes the communications device (400) to perform the operations described in any one of embodiments 1 to 38.

[0180]

[0023] Embodiment 81. A method implemented by a network node in a network, the method comprising: Receiving a Buffer Status Report (BSR) indication message from a communication device (1801), the BSR indication message indicating at least one non-legacy BSR format and / or at least one non-legacy buffer status table supported by the communication device; determining (1803) which non-legacy BSR formats and / or non-legacy BSR buffer status tables are supported by the communication device based on the BSR indication message; determining (1805) at least one non-legacy BSR format and / or at least one non-legacy BSR buffer status table for use by the communications device based on which non-legacy BSR formats and / or non-legacy BSR buffer status tables are supported by the communications device; Transmitting a radio resource control (RRC) configuration message (1807) for use by the communication device indicating one or more non-legacy BSR formats and / or one or more non-legacy buffer status tables to be used for BSR reporting; A method comprising:

[0181] 82. Receiving a configuration acknowledgment message 82. The method of embodiment 81, further comprising:

[0182] 83. Receiving a BSR having at least one non-legacy BSR format from a communication device (1809). 83. The method of embodiment 81 or 82, further comprising:

[0183]

[0023] Embodiment 84. A radio access network (RAN) node (500) adapted to perform operations, the operations including: Receiving a Buffer Status Report (BSR) indication message from a communication device (1801), the BSR indication message indicating at least one non-legacy BSR format and / or at least one non-legacy buffer status table supported by the communication device; determining (1803) which non-legacy BSR formats and / or non-legacy BSR buffer status tables are supported by the communication device based on the BSR indication message; determining (1805) at least one non-legacy BSR format and / or at least one non-legacy BSR buffer status table for use by the communications device; Transmitting a radio resource control (RRC) configuration message (1807) for use by the communication device indicating one or more non-legacy BSR formats and / or one or more non-legacy buffer status tables to be used for BSR reporting; A radio access network (RAN) node (500) including:

[0184] Embodiment 85. The RAN node (500) of embodiment 84, wherein the RAN node is further adapted to perform the operations of embodiment 82 or 83.

[0185]

[0023] Embodiment 86. A radio access network (RAN) node (500), comprising: A processing circuit (503); and a memory (505) coupled to the processing circuitry, the memory containing instructions that, when executed by the processing circuitry, cause the RAN node to perform operations, the operations including: Receiving a Buffer Status Report (BSR) indication message from a communication device (1801), the BSR indication message indicating at least one non-legacy BSR format and / or at least one non-legacy buffer status table supported by the communication device; determining (1803) which non-legacy BSR formats and / or non-legacy BSR buffer status tables are supported by the communication device based on the BSR indication message; determining (1805) at least one non-legacy BSR format and / or at least one non-legacy BSR buffer status table for use by the communications device; Transmitting a radio resource control (RRC) configuration message (1807) for use by the communication device indicating one or more non-legacy BSR formats and / or one or more non-legacy buffer status tables to be used for BSR reporting; A radio access network (RAN) node (500) including:

[0186]

[0023] Embodiment 87. The memory includes further instructions that, when executed by the processing circuit, cause the RAN node to perform operations, the operations including: Receiving a configuration acknowledgment message 87. The RAN node (500) of embodiment 86, further comprising:

[0187]

[0023] Embodiment 88. The memory includes further instructions that, when executed by the processing circuit, cause the RAN node to perform operations, the operations including: Receiving a BSR having at least one non-legacy BSR format from a communication device (1809). 88. The RAN node (500) of any one of embodiments 86 to 87, further comprising:

[0188] Embodiment 89. A computer program comprising program code to be executed by a processing circuit (503) of a radio access network (RAN) node (500), whereby execution of the program code causes the RAN node (500) to perform an operation described in any one of embodiments 81 to 83.

[0189] Further explanation is provided below.

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

[0191] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings, in which: However, other embodiments are included within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as being limited to only the embodiments described herein, but rather, these embodiments are provided as examples to convey the scope of the subject matter to those skilled in the art.

[0192] FIG. 19 illustrates a wireless network according to some embodiments.

[0193] Although the subject matter described herein may be implemented in any suitable type of system using any suitable components, the embodiments disclosed herein are described with respect to a wireless network, such as the exemplary wireless network shown in FIG. 19. For simplicity, the wireless network of FIG. 19 illustrates only the network 4106, the network nodes 4160 and 4160b, and the WDs 4110, 4110b, and 4110c (also referred to as mobile terminals). In practice, the wireless network may further include any additional elements suitable for supporting communication between wireless devices, or between a wireless device and another communication device, such as a landline, a service provider, or any other network node or end device. Of the components shown, the network node 4160 and the wireless device (WD) 4110 are illustrated with additional details. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless device's access to the wireless network and / or use of services provided by or via the wireless network.

[0194] The wireless network may include and / or interface with any type of communication, telecommunication, data, cellular, and / or radio network, or other similar type of system. In some embodiments, the wireless network may be configured to operate according to a particular standard or other type of predefined rules or procedures. Thus, particular embodiments of the wireless network may implement a communications standard, 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 Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, and / or ZigBee standards.

[0195] The network 4106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTN), packet data networks, optical networks, wide area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

[0196] The network node 4160 and WD 4110 comprise various components, which are described in more detail below. These components cooperate to provide network node and / or wireless device functionality, such as providing wireless connectivity in a wireless network. In different embodiments, a wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals, whether via wired or wireless connections.

[0197] A network node, as used herein, refers to a device capable of, set up, configured, and / or operable to communicate directly or indirectly with wireless devices and / or other network nodes or devices in a wireless network to enable and / or provide wireless access to wireless devices and / or to perform other functions (e.g., administration) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., wireless access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR Node Bs (gNBs)). Base stations may be categorized based on the amount of coverage they provide (or, in other words, their transmit power levels), and may then be referred to as femto, pico, micro, or macro base stations. A base station may be a relay node or a relay donor node that controls a relay. A network node may also include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio head (RRH). Such a remote radio unit may or may not be integrated with an antenna as an antenna-integrated radio. A part of a distributed radio base station may also be referred to as a node in a distributed antenna system (DAS). Still further examples of a network node include MSR equipment such as a multi-standard radio (MSR) BS, a network controller such as a radio network controller (RNC) or a base station controller (BSC), a base transceiver station (BTS), a transmission point, a transmitting node, a multi-cell / multicast coordination entity (MCE), a core network node (e.g., MSC, MME), an O&M node, an OSS node, a SON node, a positioning node (e.g., E-SMLC), and / or an 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 may represent any suitable device (or group of devices) capable of, configured to, and / or operable to enable and / or provide wireless devices with access to a wireless network or to provide some service to wireless devices that have accessed the wireless network.

[0198] In FIG. 19, the network node 4160 includes a processing circuit 4170, a device readable medium 4180, an interface 4190, an auxiliary device 4184, a power source 4186, a power circuit 4187, and an antenna 4162. Although the network node 4160 shown in the example wireless network of FIG. 19 may represent a device including the shown combination of hardware components, other embodiments may comprise a network node with a different combination of components. It should be understood that a network node comprises any suitable combination of hardware and / or software required to perform the tasks, features, functions and methods disclosed herein. Moreover, although the components of the network node 4160 are illustrated as a single box located within a larger box or nested within multiple boxes, in reality the network node may comprise multiple different physical components that make up a single shown component (e.g., the device readable medium 4180 may comprise multiple separate hard drives as well as multiple RAM modules).

[0199] Similarly, the network node 4160 may be assembled from multiple physically separate components (e.g., a Node B component and an RNC component, or a BTS component and a BSC component, etc.), each of which may have their own respective components. In some scenarios in which the network node 4160 comprises multiple separate components (e.g., a BTS component and a BSC component), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control several Node Bs. In such scenarios, each unique Node B and RNC pair may be considered as a single separate network node in some cases. In some embodiments, the network node 4160 may be configured to support several radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device-readable media 4180 for different RATs) and some components may be reused (e.g., the same antenna 4162 may be shared by the RATs). The network node 4160 may also include multiple sets of the various illustrated components for different wireless technologies, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies, integrated into the network node 4160. These wireless technologies may be integrated in the same or different chips or sets of chips and other components within the network node 4160.

[0200] The processing circuit 4170 is configured to perform any decision, computation, or similar operations (e.g., some acquisition operations) described herein as being provided by a network node. These operations performed by the processing circuit 4170 may include processing information acquired by the processing circuit 4170, for example, by converting the acquired information into other information, comparing the acquired or converted information with information stored in the network node, and / or performing one or more operations based on the acquired or converted information and as a result of the processing making a decision.

[0201] The processing circuit 4170 may comprise one or more combinations of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and / or coded logic operable to provide network node 4160 functionality, either alone or in conjunction with other network node 4160 components, such as device readable medium 4180. For example, the processing circuit 4170 may execute instructions stored on the device readable medium 4180 or in memory within the processing circuit 4170. Such functionality may include providing any of the various wireless features, functions, or benefits described herein. In some embodiments, the processing circuit 4170 may include a system on a chip (SOC).

[0202] In some embodiments, the processing circuitry 4170 may include one or more of a radio frequency (RF) transceiver circuitry 4172 and a baseband processing circuitry 4174. In some embodiments, the radio frequency (RF) transceiver circuitry 4172 and the baseband processing circuitry 4174 may be on separate chips (or sets of chips), boards, or units, such as a radio unit and a digital unit. In alternative embodiments, some or all of the RF transceiver circuitry 4172 and the baseband processing circuitry 4174 may be on the same chip or set of chips, board, or unit.

[0203] In some embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB, or other such network device may be performed by the processing circuitry 4170 executing instructions stored in a device-readable medium 4180, or in a memory within the processing circuitry 4170. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry 4170 without executing instructions stored in a separate or distinct device-readable medium, such as in a hardwired manner. In any of those embodiments, the processing circuitry 4170 may be configured to perform the described functionality, whether or not it executes instructions stored in a device-readable storage medium. Benefits provided by such functionality are enjoyed by the processing circuitry 4170 alone, or by other components of the network node 4160, but by the network node 4160 as a whole, and / or by end users and wireless networks in general.

[0204] The device readable medium 4180 may comprise any form of volatile or non-volatile computer readable memory, including, but not limited to, persistent storage, solid state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disk (CD) or digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory device readable and / or computer executable memory device that stores information, data, and / or instructions that may be used by the processing circuit 4170. The device readable medium 4180 may store any suitable instructions, data or information, including applications including one or more of computer programs, software, logic, rules, codes, tables, etc., and / or other instructions that may be executed by the processing circuit 4170 and utilized by the network node 4160. The device-readable medium 4180 may be used to store calculations performed by the processing circuit 4170 and / or data received via the interface 4190. In some embodiments, the processing circuit 4170 and the device-readable medium 4180 may be considered to be integrated.

[0205] The interface 4190 is used in wired or wireless communication of signaling and / or data between the network node 4160, the network 4106, and / or the WD 4110. As shown, the interface 4190 comprises a port(s) / terminal(s) 4194 for sending and receiving data to and from the network 4106, for example over a wired connection. The interface 4190 also includes a wireless front-end circuit 4192, which is coupled to the antenna 4162 or, in some embodiments, may be part of the antenna 4162. The wireless front-end circuit 4192 comprises a filter 4198 and an amplifier 4196. The wireless front-end circuit 4192 may be connected to the antenna 4162 and the processing circuit 4170. The wireless front-end circuit may be configured to condition signals communicated between the antenna 4162 and the processing circuit 4170. The wireless front-end circuit 4192 may receive digital data to be sent to other network nodes or WDs via a wireless connection. The radio front-end circuit 4192 may convert the digital data into a radio signal having appropriate channel and bandwidth parameters using a combination of filters 4198 and / or amplifiers 4196. The radio signal may then be transmitted via the antenna 4162. Similarly, when receiving data, the antenna 4162 may collect the radio signal, which is then converted to digital data by the radio front-end circuit 4192. The digital data may be passed to the processing circuit 4170. In other embodiments, the interface may comprise different components and / or different combinations of components.

[0206] In some alternative embodiments, the network node 4160 may not include a separate radio front-end circuit 4192, and instead the processing circuit 4170 may comprise a radio front-end circuit and be connected to the antenna 4162 without a separate radio front-end circuit 4192. Similarly, in some embodiments, all or a portion of the RF transceiver circuit 4172 may be considered part of the interface 4190. In still other embodiments, the interface 4190 may include one or more ports or terminals 4194, the radio front-end circuit 4192, and the RF transceiver circuit 4172 as part of a radio unit (not shown), and the interface 4190 may communicate with a baseband processing circuit 4174 that is part of a digital unit (not shown).

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

[0208] The antenna 4162, the interface 4190, and / or the processing circuit 4170 may be configured to perform any receiving operation and / or some obtaining operation described herein as being performed by a network node. Any information, data, and / or signal may be received from a wireless device, another network node, and / or any other network equipment. Similarly, the antenna 4162, the interface 4190, and / or the processing circuit 4170 may be configured to perform any transmitting operation described herein as being performed by a network node. Any information, data, and / or signal may be transmitted to a wireless device, another network node, and / or any other network equipment.

[0209] The power circuit 4187 may comprise or be coupled to a power management circuit and is configured to supply power to the components of the network node 4160 for performing the functions described herein. The power circuit 4187 may receive power from a power source 4186. The power source 4186 and / or the power circuit 4187 may be configured to provide power to the various components of the network node 4160 in a form suitable for the respective components (e.g., at the voltage and current levels required for each respective component). The power source 4186 may either be included in the power circuit 4187 and / or the network node 4160 or may be external to the power circuit 4187 and / or the network node 4160. For example, the network node 4160 may be connectable to an external power source (e.g., an electrical outlet) via an input circuit or interface such as an electrical cable, whereby the external power source supplies power to the power circuit 4187. As a further example, power supply 4186 may include a power source in the form of a battery or battery pack connected to or integrated in power circuit 4187. The battery may provide backup power in the event that an external power source fails. Other types of power sources, such as photovoltaic devices, may also be used.

[0210] Alternative embodiments of the network node 4160 may include additional components other than those shown in FIG. 19 that may be responsible for providing some aspects of the network node's functionality, including any of the functionality described herein and / or functionality necessary to support the subject matter described herein. For example, the network node 4160 may include user interface devices to enable input of information into the network node 4160 and output of information from the network node 4160. This may enable a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 4160.

[0211] A wireless device (WD) as used herein refers to a device capable of, configured to, and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and / or receiving wireless signals using electromagnetic, radio, infrared, and / or other types of signals suitable for conveying information over the air. In some embodiments, a WD may be configured to transmit and / or receive information without direct human interaction. For example, a WD may be designed to transmit information to a network on a predefined schedule, when triggered by an internal or external event, or in response to a request from the network. Examples of WDs include, but are not limited to, smartphones, mobile phones, cell phones, voice-over-IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback appliances, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptop computers, laptop embedded equipment (LEE), laptop mounted equipment (LME), smart devices, wireless customer premises equipment (CPE), in-vehicle wireless terminal devices, etc. A WD may support device-to-device (D2D) communications, for example, by implementing 3GPP standards for sidelink communications, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X), in which case it may be referred to as a D2D communications device. As yet another specific example, in an Internet of Things (IoT) scenario, a WD may represent a machine or other device that performs monitoring and / or measurements and transmits results of such monitoring and / or measurements to another WD and / or network node. The WD may in this case be a machine-to-machine (M2M) device, which may be referred to as an MTC device in the 3GPP context.As one particular example, the WD may be a UE implementing the 3GPP Narrowband Internet of Things (NB-IoT) standard. Particular 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 wearables (e.g., watches, fitness trackers, etc.). In other scenarios, the WD may represent a vehicle or other equipment capable of monitoring and / or reporting on its operational status or other functions related to its operation. The WD described above may represent an endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Additionally, the WD described above may be mobile, in which case the device may be referred to as a mobile device or mobile terminal.

[0212] As shown, the wireless device 4110 includes an antenna 4111, an interface 4114, a processing circuit 4120, a device readable medium 4130, a user interface device 4132, an auxiliary device 4134, a power source 4136, and a power circuit 4137. The WD4110 may include multiple sets of one or more of the shown components for different wireless technologies supported by the WD4110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to name a few. These wireless technologies may be integrated on the same or different chips or sets of chips as other components within the WD4110.

[0213] The antenna 4111 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals and is connected to the interface 4114. In some alternative embodiments, the antenna 4111 may be separate from the WD 4110 and connectable to the WD 4110 through an interface or port. The antenna 4111, the interface 4114, and / or the processing circuit 4120 may be configured to perform any receiving or transmitting operation described herein as being performed by a WD. Any information, data, and / or signal may be received from a network node and / or another WD. In some embodiments, the wireless front-end circuit and / or the antenna 4111 may be considered an interface.

[0214] As shown, the interface 4114 comprises a radio front-end circuit 4112 and an antenna 4111. The radio front-end circuit 4112 comprises one or more filters 4118 and an amplifier 4116. The radio front-end circuit 4112 is connected to the antenna 4111 and the processing circuit 4120 and is configured to condition signals communicated between the antenna 4111 and the processing circuit 4120. The radio front-end circuit 4112 may be coupled to the antenna 4111 or may be part of the antenna 4111. In some embodiments, the WD 4110 may not include a separate radio front-end circuit 4112, rather the processing circuit 4120 may comprise a radio front-end circuit and be connected to the antenna 4111. Similarly, in some embodiments, some or all of the RF transceiver circuit 4122 may be considered part of the interface 4114. The radio front-end circuit 4112 may receive digital data to be sent to other network nodes or WDs via a wireless connection. The radio front-end circuitry 4112 may convert the digital data into a radio signal having appropriate channel and bandwidth parameters using a combination of filters 4118 and / or amplifiers 4116. The radio signal may then be transmitted via the antenna 4111. Similarly, when receiving data, the antenna 4111 may collect the radio signal, which is then converted to digital data by the radio front-end circuitry 4112. The digital data may be passed to the processing circuitry 4120. In other embodiments, the interface may comprise different components and / or different combinations of components.

[0215] The processing circuitry 4120 may comprise one or more combinations of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and / or coded logic operable to provide WD4110 functionality, either alone or in conjunction with other WD4110 components such as device readable medium 4130. Such functionality may include providing any of the various wireless features or benefits described herein. For example, the processing circuitry 4120 may execute instructions stored on the device readable medium 4130 or in memory within the processing circuitry 4120 to provide the functionality disclosed herein.

[0216] As shown, the processing circuit 4120 includes one or more of an RF transceiver circuit 4122, a baseband processing circuit 4124, and an application processing circuit 4126. In other embodiments, the processing circuit may comprise different components and / or different combinations of components. In some embodiments, the processing circuit 4120 of the WD4110 may comprise a SOC. In some embodiments, the RF transceiver circuit 4122, the baseband processing circuit 4124, and the application processing circuit 4126 may be on separate chips or sets of chips. In alternative embodiments, some or all of the baseband processing circuit 4124 and the application processing circuit 4126 may be combined into one chip or set of chips, and the RF transceiver circuit 4122 may be on a separate chip or set of chips. In yet alternative embodiments, some or all of the RF transceiver circuit 4122 and the baseband processing circuit 4124 may be on the same chip or set of chips, and the application processing circuit 4126 may be on a separate chip or set of chips. In yet other alternative embodiments, some or all of the RF transceiver circuitry 4122, the baseband processing circuitry 4124, and the application processing circuitry 4126 may be combined in the same chip or set of chips. In some embodiments, the RF transceiver circuitry 4122 may be part of the interface 4114. The RF transceiver circuitry 4122 may condition RF signals for the processing circuitry 4120.

[0217] In some embodiments, some or all of the functionality described herein as being performed by the WD may be provided by the processing circuitry 4120 executing instructions stored on a device-readable medium 4130, which in some embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry 4120 without executing instructions stored on a separate or distinct device-readable storage medium, such as in a hardwired manner. In any of those particular embodiments, the processing circuitry 4120 may be configured to perform the described functionality, whether or not it executes instructions stored on a device-readable storage medium. Benefits provided by such functionality are enjoyed by the WD 4110 as a whole, and / or by end users and wireless networks in general, but not limited to the processing circuitry 4120 alone or other components of the WD 4110.

[0218] The processing circuit 4120 may be configured to perform any of the decision, calculation, or similar operations (e.g., some of the acquisition operations) described herein as being performed by the WD. These operations as performed by the processing circuit 4120 may include processing information acquired by the processing circuit 4120, for example, by converting the acquired information into other information, comparing the acquired or converted information with information stored by the WD 4110, and / or performing one or more operations based on the acquired or converted information and as a result of the processing making a decision.

[0219] The device-readable medium 4130 may be operable to store applications including one or more of computer programs, software, logic, rules, codes, tables, etc., and / or other instructions that may be executed by the processing circuit 4120. The device-readable medium 4130 may include computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), mass storage media (e.g., hard disk), removable storage media (e.g., compact disc (CD) or digital video disc (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device that stores information, data, and / or instructions that may be used by the processing circuit 4120. In some embodiments, the processing circuit 4120 and the device-readable medium 4130 may be considered to be integrated.

[0220] The user interface device 4132 may provide components that allow a human user to interact with the WD4110. Such interaction may be of many forms, such as visual, auditory, tactile, etc. The user interface device 4132 may be operable to produce output to the user and to allow the user to provide input to the WD4110. The type of interaction may vary depending on the type of user interface device 4132 installed on the WD4110. For example, if the WD4110 is a smartphone, the interaction may be via a touch screen, and if the WD4110 is a smart meter, the interaction may be through a screen that provides usage (e.g., number of gallons used), or a speaker that provides an audible alarm (e.g., if smoke is detected). The user interface device 4132 may include input interfaces, devices and circuits, as well as output interfaces, devices and circuits. The user interface device 4132 is configured to allow input of information to the WD4110 and is connected to the processing circuit 4120 to allow the processing circuit 4120 to process the input information. The user interface device 4132 may include, for example, a microphone, proximity or other sensors, keys / buttons, a touch display, one or more cameras, a USB port, or other input circuitry. The user interface device 4132 is also configured to enable output of information from the WD4110 and to enable the processing circuitry 4120 to output information from the WD4110. The user interface device 4132 may include, for example, a speaker, a display, a vibration circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits of the user interface device 4132, the WD4110 may communicate with an end user and / or a wireless network, enabling the end user and / or the wireless network to benefit from the functionality described herein.

[0221] The auxiliary device 4134 is operable to provide more specific functionality that may not generally be implemented by a WD. It may include specialized sensors for taking measurements for various purposes, interfaces for additional types of communication such as wired communication, etc. The inclusion and type of components of the auxiliary device 4134 may vary depending on the embodiment and / or scenario.

[0222] The power source 4136 may be in the form of a battery or battery pack in some embodiments. Other types of power sources may also be used, such as an external power source (e.g., an electrical outlet), a photovoltaic device, or a battery. The WD4110 may further comprise a power circuit 4137 for delivering power from the power source 4136 to various parts of the WD4110 that require power from the power source 4136 to perform any of the functions described or indicated herein. The power circuit 4137 may comprise a power management circuit in some embodiments. The power circuit 4137 may additionally or alternatively be operable to receive power from an external power source, in which case the WD4110 may be connectable to an external power source (such as an electrical outlet) via an input circuit or interface, such as a power cable. The power circuit 4137 may also be operable in some embodiments to deliver power from the external power source to the power source 4136. This may be for example for charging the power source 4136. The power circuitry 4137 may perform any formatting, converting, or other modification on the power from the power source 4136 to make the power suitable for the respective components of the WD4110 that are being powered.

[0223] FIG. 20 illustrates a user equipment according to some embodiments.

[0224] FIG. 20 illustrates an embodiment of a UE according to various aspects described herein. User equipment or UE as used herein does not necessarily have a user in the sense of a human user who owns and / or operates an associated device. Instead, a UE may represent a device (e.g., a smart sprinkler controller) that is intended for sale to or operation by a human user, but may not be associated with or may not be initially associated with a particular human user. Alternatively, a UE may represent a device (e.g., a smart power meter) that is not intended for sale to or operation by an end user, but may be associated with or operated for the benefit of a user. The UE 42200 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. The UE 4200 shown in Figure 20 is an example of a WD configured for communication according to one or more communications standards promulgated by the 3rd Generation Partnership Project (3GPP), such as the 3GPP GSM, UMTS, LTE, and / or 5G standards. As previously mentioned, the terms WD and UE may be used interchangeably. Thus, although Figure 20 is a UE, the components described herein are equally applicable to a WD and vice versa.

[0225] In FIG. 20, the UE 4200 includes a processing circuit 4201 operatively coupled to an input / output interface 4205, a radio frequency (RF) interface 4209, a network connection interface 4211, a memory 4215 including a random access memory (RAM) 4217, a read only memory (ROM) 4219, a storage medium 4221, etc., a communication subsystem 4231, a power source 4213, and / or any other components, or any combination thereof. The storage medium 4221 includes an operating system 4223, an application program 4225, and data 4227. In other embodiments, the storage medium 4221 may include other similar types of information. Some UEs may utilize all of the components shown in FIG. 20 or only a subset of those components. The level of integration between components may vary from UE to UE. Additionally, some UEs may include multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0226] In FIG. 20, the processing circuit 4201 may be configured to process computer instructions and data. The processing circuit 4201 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 pre-programmed, general-purpose processors, such as a microprocessor or digital signal processor (DSP) with appropriate software, or any combination of the above. For example, the processing circuit 4201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

[0227] In the illustrated embodiment, the input / output interface 4205 may be configured to provide an input device, an output device, or a communication interface to an input / output device. The UE 4200 may be configured to use an output device via the input / output interface 4205. The output device may use the same type of interface port as the input device. For example, a USB port may be used to provide input to and output from the UE 4200. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smart card, another output device, or any combination thereof. The UE 4200 may be configured to use an input device via the input / output interface 4205 to allow a user to capture information into the UE 4200. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a webcam, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smart card, etc. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. The sensor may be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, a light sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and a light sensor.

[0228] In FIG. 20, the RF interface 4209 may be configured to provide a communication interface to RF components, such as a transmitter, a receiver, and an antenna. The network connection interface 4211 may be configured to provide a communication interface to a network 4243a. The network 4243a may encompass a wired and / or wireless network, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a communication network, another similar network, or any combination thereof. For example, the network 4243a may comprise a Wi-Fi network. The network connection interface 4211 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP / IP, SONET, ATM, etc. The network connection interface 4211 may implement receiver and transmitter functions suitable for a communication network link (e.g., optical, electrical, etc.). The transmitter and receiver functions may share circuit components, software or firmware, or may alternatively be implemented separately.

[0229] The RAM 4217 may be configured to interface to the processing circuit 4201 via the bus 4202 to provide storage or caching of data or computer instructions during execution of software programs, such as an operating system, application programs, and device drivers. The ROM 4219 may be configured to provide computer instructions or data to the processing circuit 4201. For example, the ROM 4219 may be configured to store unchanging low-level system code or data for basic system functions, such as basic input / output (I / O), booting, or receiving keystrokes from a keyboard, stored in non-volatile memory. The storage medium 4221 may be configured to include memory, such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk, optical disk, floppy disk, hard disk, removable cartridge, or flash drive. In one example, the storage medium 4221 may be configured to include an operating system 4223, an application program 4225, such as a web browser application, a widget or gadget engine, or another application, and data files 4227. The storage medium 4221 may store any of a variety of different operating systems or combinations of operating systems for use by the UE 4200.

[0230] The storage medium 4221 may be configured to include several physical drive units, such as a redundant array of independent disks (RAID), a floppy disk drive, a flash memory, a USB flash drive, an external hard disk drive, a thumb drive, a pen drive, a key drive, a high density digital versatile disk (HD-DVD) optical disk drive, an internal hard disk drive, a Blu-Ray optical disk drive, a holographic digital data storage (HDDS) optical disk drive, an external mini dual in-line memory module (DIMM), a synchronous dynamic random access memory (SDRAM), an external micro-DIMM SDRAM, a smart card memory such as a subscriber identity module or a removable user identity (SIM / RUIM) module, other memory, or any combination thereof. The storage medium 4221 may enable the UE 4200 to access computer executable instructions, application programs, etc. stored in a temporary or non-transitory memory medium, offload data, or upload data. An article of manufacture, such as an article of manufacture utilizing a communication system, may be tangibly embodied in the storage medium 4221, and the storage medium 4221 may comprise a device-readable medium.

[0231] In FIG. 20, the processing circuit 4201 may be configured to communicate with the network 4243b using the communication subsystem 4231. The network 4243a and the network 4243b may be the same network or networks or different networks or networks. The communication subsystem 4231 may be configured to include one or more transceivers used to communicate with the network 4243b. For example, the communication subsystem 4231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication, such as another WD, UE, or base station of a radio access network (RAN), according to one or more communication protocols, such as IEEE 802.11, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, etc. Each transceiver may include a transmitter 4233 and / or a receiver 4235 for implementing a transmitter function or a receiver function, respectively, appropriate for a RAN link (e.g., frequency allocation, etc.). Furthermore, the transmitter 4233 and receiver 4235 of each transceiver may share circuit components, software or firmware, or may alternatively be implemented separately.

[0232] In the illustrated embodiment, the communication capabilities of the communication subsystem 4231 may include data communications, voice communications, multimedia communications, short-range communications such as Bluetooth, near-field communications, location-based communications such as using a global positioning system (GPS) to determine location, another similar communication capability, or any combination thereof. For example, the communication subsystem 4231 may include cellular communications, Wi-Fi communications, Bluetooth communications, and GPS communications. The network 4243b may encompass wired and / or wireless networks, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a communications network, another similar network, or any combination thereof. For example, the network 4243b may be a cellular network, a Wi-Fi network, and / or a near-field network. The power source 4213 may be configured to provide alternating current (AC) or direct current (DC) power to the components of the UE 4200.

[0233] The features, benefits and / or functions described herein may be implemented in one of the components of the UE 4200 or distributed across multiple components of the UE 4200. Furthermore, the features, benefits and / or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, the communication subsystem 4231 may be configured to include any of the components described herein. Furthermore, the processing circuit 4201 may be configured to communicate with any of such components over the bus 4202. In another example, any of such components may be represented by program instructions stored in memory that, when executed by the processing circuit 4201, perform the corresponding functions described herein. In another example, the functions of any of such components may be distributed between the processing circuit 4201 and the communication subsystem 4231. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware, and computationally intensive functions may be implemented in hardware.

[0234] FIG. 21 illustrates a virtualization environment according to some embodiments.

[0235] FIG. 21 is a schematic block diagram illustrating a virtualization environment 4300 in which functions implemented by some embodiments may be virtualized. In this context, virtualizing means creating a virtual version of an apparatus or device, which may include virtualizing a hardware platform, storage devices, and networking resources. Virtualization as used herein may be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device, or any other type of communication device) or to a component of that device, and relates to implementations in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines, or containers running on one or more physical processing nodes in one or more networks).

[0236] In some embodiments, some or all of the functionality described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 4300 hosted by one or more of the hardware nodes 4330. Furthermore, in embodiments where the virtual nodes are not wireless access nodes or do not require wireless connectivity (e.g., core network nodes), the network nodes may be fully virtualized.

[0237] The functionality may be implemented by one or more applications 4320 (which may alternatively be referred to as software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operable to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein. The applications 4320 are run in a virtualization environment 4300, which provides hardware 4330 comprising a processing circuit 4360 and a memory 4390. The memory 4390 includes instructions 4395 executable by the processing circuit 4360 such that the applications 4320 are operable to provide one or more of the features, benefits, and / or functions disclosed herein.

[0238] The virtualization environment 4300 includes a general-purpose or dedicated network hardware device 4330 including a set of one or more processors or processing circuitry 4360, which may be a commercial off-the-shelf (COTS) processor, a dedicated application specific integrated circuit (ASIC), or any other type of processing circuitry including digital or analog hardware components or dedicated processors. Each hardware device may include a memory 4390-1, which may be a non-persistent memory for temporarily storing instructions 4395 or software executed by the processing circuitry 4360. Each hardware device may include one or more network interface controllers (NICs) 4370, also known as network interface cards, which include a physical network interface 4380. Each hardware device may also include a non-transitory, persistent, machine-readable storage medium 4390-2 having stored thereon software 4395 and / or instructions executable by the processing circuitry 4360. Software 4395 may include any type of software, including software for instantiating one or more virtualization layers 4350 (also called hypervisors), software for running virtual machines 4340, and software that enables it to perform the functions, features and / or benefits described in connection with some embodiments described herein.

[0239] The virtual machines 4340 may comprise virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and may be run by a corresponding virtualization layer 4350 or hypervisor. Different embodiments of the virtual appliance 4320 instances may be implemented on one or more of the virtual machines 4340, and the implementations may be done in different ways.

[0240] During operation, the processing circuitry 4360 executes software 4395 to instantiate a hypervisor or virtualization layer 4350, which may sometimes be referred to as a virtual machine monitor (VMM). The virtualization layer 4350 may present to the virtual machine 4340 a virtual operating platform that looks like networking hardware.

[0241] 21, the hardware 4330 may be a standalone network node with general or specific components. The hardware 4330 may include an antenna 43225 and may implement some functions via virtualization. Alternatively, the hardware 4330 may be part of a larger cluster of hardware (e.g., as in the case of a data center or customer premises equipment (CPE)) where many hardware nodes work together and are managed via a management and orchestration (MANO) 43100 that, among other things, oversees the lifecycle management of the applications 4320.

[0242] Hardware virtualization is referred to in some contexts as network function virtualization (NFV). NFV can be used to consolidate many network equipment types onto industry-standard high-volume server hardware, physical switches, and physical storage that may be located in data centers and customer premises equipment.

[0243] In the context of NFV, virtual machine 4340 may be a software implementation of a physical machine that runs programs as if those programs were running on a physical, non-virtualized machine. Each virtual machine 4340 and the portion of hardware 4330 on which it runs, whether hardware dedicated to that virtual machine and / or hardware shared by that virtual machine with other ones of virtual machines 4340, form a separate virtual network element (VNE).

[0244] Further in the context of NFV, a virtual network function (VNF) is responsible for handling a specific network function running on one or more virtual machines 4340 on top of the hardware networking infrastructure 4330 and corresponds to application 4320 in FIG. 21.

[0245] In some embodiments, one or more radio units 43200, each including one or more transmitters 43220 and one or more receivers 43210, may be coupled to one or more antennas 43225. The radio units 43200 may communicate directly with the hardware node 4330 via one or more suitable network interfaces and may be used in combination with a virtualization component to provide a virtualization node with wireless capabilities, such as a wireless access node or base station.

[0246] In some embodiments, some signaling may be accomplished using the control system 43230, which may alternatively be used for communication between the hardware node 4330 and the wireless unit 43200.

[0247] FIG. 22 illustrates a communications network connected to a host computer through an intermediate network, according to some embodiments.

[0248] Referring to Fig. 22, according to one embodiment, a communication system includes a communication network 4410, such as a 3GPP type cellular network, comprising an access network 4411, such as a wireless access network, and a core network 4414. The access network 4411 comprises a number of base stations 4412a, 4412b, 4412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 4413a, 4413b, 4413c. Each base station 4412a, 4412b, 4412c can be connected to the core network 4414 over a wired or wireless connection 4415. A first UE 4491 located in the coverage area 4413c is configured to wirelessly connect to the corresponding base station 4412c or to be paged by the corresponding base station 4412c. A second UE 4492 in the coverage area 4413a can be wirelessly connected to the corresponding base station 4412a. Although multiple UEs 4491, 4492 are shown in this example, the disclosed embodiments are equally applicable to situations where only one UE is in a coverage area or where only one UE is connected to a corresponding base station 4412.

[0249] The communication network 4410 is itself connected to a host computer 4430, which may be embodied in hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as a processing resource in a server farm. The host computer 4430 may be owned or under the control of a service provider, or may be operated by or on behalf of the service provider. The connections 4421 and 4422 between the communication network 4410 and the host computer 4430 may extend directly from the core network 4414 to the host computer 4430, or may proceed via an optional intermediate network 4420. The intermediate network 4420 may be one of a public network, a private network, or a hosted network, or a combination of two or more of them, and the intermediate network 4420 may be a backbone network or the Internet, if any, and in particular the intermediate network 4420 may comprise two or more sub-networks (not shown).

[0250] The communication system of FIG. 22 as a whole enables connectivity between the connected UEs 4491, 4492 and the host computer 4430. The connectivity may be described as an over-the-top (OTT) connection 4450. The host computer 4430 and the connected UEs 4491, 4492 are configured to communicate data and / or signaling via the OTT connection 4450 using the access network 4411, the core network 4414, any intermediate networks 4420, and possible further infrastructure (not shown) as intermediaries. The OTT connection 4450 may be transparent in the sense that the participating communication devices through which the OTT connection 4450 passes are unaware of the routing of the uplink and downlink communications. For example, the base station 4412 may not be or need not be informed about the past routing of incoming downlink communications involving data originating from the host computer 4430 to be forwarded (e.g., handed over) to the connected UE 4491. Similarly, the base station 4412 does not need to be aware of the future routing of outgoing uplink communications originating from the UE 4491 and destined for the host computer 4430.

[0251] FIG. 23 illustrates a host computer communicating with user equipment via a base station over a partially wireless connection according to some embodiments.

[0252] Next, an exemplary implementation of the UE, base station and host computer described in the previous paragraph according to an embodiment will be described with reference to FIG. 23. In the communication system 4500, the host computer 4510 comprises hardware 4515 including a communication interface 4516 configured to set up and maintain wired or wireless connections with interfaces of different communication devices of the communication system 4500. The host computer 4510 further comprises a processing circuit 4518, which may have storage and / or processing capabilities. In particular, the processing circuit 4518 may comprise 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 4510 further comprises software 4511, which is stored in or accessible by the host computer 4510 and is executable by the processing circuit 4518. The software 4511 includes a host application 4512. The host application 4512 may be operable to provide services to a remote user, such as a UE 4530 connecting via an OTT connection 4550 that terminates at the UE 4530 and the host computer 4510. In providing services to the remote user, the host application 4512 may provide user data that is transmitted using the OTT connection 4550.

[0253] The communication system 4500 further includes a base station 4520 provided in the communication system, the base station 4520 comprising hardware 4525 enabling the base station 4520 to communicate with the host computer 4510 and the UE 4530. The hardware 4525 may include a communication interface 4526 for setting up and maintaining wired or wireless connections with interfaces of different communication devices of the communication system 4500, as well as a wireless interface 4527 for setting up and maintaining at least a wireless connection 4570 with a UE 4530 located in a coverage area (not shown in FIG. 23) served by the base station 4520. The communication interface 4526 may be configured to facilitate a connection 4560 to the host computer 4510. The connection 4560 may be direct or alternatively the connection 4560 may pass through a core network (not shown in FIG. 23) of the communication system and / or one or more intermediate networks outside the communication system. In the illustrated embodiment, the hardware 4525 of the base station 4520 further includes processing circuitry 4528, which may comprise 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 4520 further has software 4521 stored internally or accessible via an external connection.

[0254] The communication system 4500 further includes the UE 4530 already mentioned. The hardware 4535 of the UE 4530 may include a wireless interface 4537 configured to set up and maintain a wireless connection 4570 with a base station serving the coverage area in which the UE 4530 is currently located. The hardware 4535 of the UE 4530 further includes a processing circuit 4538, which may comprise one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The UE 4530 further includes software 4531 stored in or accessible by the UE 4530 and executable by the processing circuit 4538. The software 4531 includes a client application 4532. The client application 4532 may be operable to provide services to a human or non-human user via the UE 4530 with the support of the host computer 4510. At the host computer 4510, a running host application 4512 may communicate with a running client application 4532 via an OTT connection 4550 that terminates at the UE 4530 and the host computer 4510. In providing a service to a user, the client application 4532 may receive request data from the host application 4512 and provide user data in response to the request data. The OTT connection 4550 may transfer both the request data and the user data. The client application 4532 may interact with the user to generate the user data that the client application 4532 provides.

[0255] It should be noted that the host computer 4510, base station 4520 and UE 4530 shown in Figure 23 may be similar or equivalent to the host computer 4430, one of the base stations 4412a, 4412b, 4412c, and one of the UEs 4491, 4492, respectively, of Figure 22. That is, the inner workings of these entities may be as shown in Figure 23, and separately, the surrounding network topology may be that of Figure 22.

[0256] In Figure 23, the OTT connection 4550 is depicted abstractly to show communication between the host computer 4510 and the UE 4530 via the base station 4520, without explicit reference to intermediary devices and the exact routing of messages through these devices. The network infrastructure may determine the routing, and the network infrastructure may be configured to hide the routing from the UE 4530 or from the service provider operating the host computer 4510, or both. The network infrastructure may also make decisions to dynamically change the routing while the OTT connection 4550 is active (e.g., based on load balancing considerations or reconfiguration of the network).

[0257] The wireless connection 4570 between the UE 4530 and the base station 4520 follows the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments may improve the performance of the OTT service provided to the UE 4530 using the OTT connection 4550 of which the wireless connection 4570 forms the last segment. More precisely, the teachings of these embodiments may improve the random access speed and / or reduce the random access failure rate, thereby providing benefits such as faster and / or more reliable random access.

[0258] Measurement procedures may be provided for the purpose of monitoring data rates, latency and other factors that one or more embodiments improve upon. There may further be an optional network function for reconfiguring the OTT connection 4550 between the host computer 4510 and the UE 4530 in response to fluctuations in the measurement results. The measurement procedures and / or the network function for reconfiguring the OTT connection 4550 may be implemented in the software 4511 and hardware 4515 of the host computer 4510 or in the software 4531 and hardware 4535 of the UE 4530, or both. In an embodiment, sensors (not shown) may be deployed in or in association with the communication device through which the OTT connection 4550 passes, and the sensors may participate in the measurement procedures by providing values ​​of the monitored quantities exemplified above, or other physical quantities from which the software 4511, 4531 may calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 4550 may include message formats, retransmission settings, preferred routing, etc., and the reconfiguration need not affect the base station 4520, and the reconfiguration may be unknown or imperceptible to the base station 4520. Such procedures and functions may be known and practiced in the art. In some embodiments, the measurements may involve proprietary UE signaling that facilitates the host computer 4510 measurements of throughput, propagation time, latency, etc. The measurements may be implemented in the software 4511 and 4531 causing messages, particularly empty or "dummy" messages, to be sent using the OTT connection 4550 while the software 4511 and 4531 monitors propagation times, errors, etc.

[0259] FIG. 24 illustrates a method implemented in a communications system including a host computer, a base station, and user equipment, according to some embodiments.

[0260] FIG. 24 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 22 and FIG. 23. For simplicity of the disclosure, only drawing references to FIG. 24 are included in this section. In step 4610, the host computer provides user data. In sub-step 4611 (which may be optional) of step 4610, the host computer provides the user data by executing a host application. In step 4620, the host computer initiates a transmission carrying the user data to the UE. In step 4630 (which may be optional), the base station transmits the user data carried in the host computer initiated transmission to the UE, according to the teachings of the embodiments described throughout this disclosure. In step 4640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0261] FIG. 25 illustrates a method implemented in a communications system including a host computer, a base station, and user equipment, according to some embodiments.

[0262] FIG. 25 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 22 and FIG. 23. For simplicity of the disclosure, only drawing references to FIG. 25 are included in this section. In step 4710 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides the user data by executing a host application. In step 4720, the host computer initiates a transmission carrying the user data to the UE. The transmission may proceed via the base station according to the teachings of the embodiments described throughout this disclosure. In step 4730 (which may be optional), the UE receives the user data carried in the transmission.

[0263] FIG. 26 illustrates a method implemented in a communications system including a host computer, a base station, and user equipment, according to some embodiments.

[0264] FIG. 26 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 22 and FIG. 23. For simplicity of the disclosure, only drawing references to FIG. 26 are included in this section. In step 4810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 4820, the UE provides user data. In sub-step 4821 (which may be optional) of step 4820, the UE provides the user data by executing a client application. In sub-step 4811 (which may be optional) of step 4810, the UE executes a client application that provides the user data in response to the received input data provided by the host computer. In providing the user data, the executed client application may further take into account user input received from the user. Regardless of the particular manner in which the user data is provided, the UE initiates transmission of the user data to the host computer in sub-step 4830 (which may be optional). In method step 4840, the host computer receives user data transmitted from the UE in accordance with the teachings of the embodiments described throughout this disclosure.

[0265] FIG. 27 illustrates a method implemented in a communications system including a host computer, a base station, and user equipment, according to some embodiments.

[0266] FIG. 27 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 22 and FIG. 23. For simplicity of the disclosure, only drawing references to FIG. 27 are included in this section. In step 4910 (which may be optional), the base station receives user data from the UE, according to the teachings of the embodiments described throughout this disclosure. In step 4920 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 4930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0267] Any suitable steps, methods, features, functions, or benefits disclosed herein may be implemented through one or more functional units or modules of one or more virtual devices. Each virtual device may comprise several of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), dedicated 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 (RAM), cache memory, flash memory devices, optical storage devices, and the like. The program code stored in memory includes program instructions for implementing one or more communication and / or data communication protocols, as well as instructions for performing one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause each functional unit to perform a corresponding function according to one or more embodiments of the present disclosure.

[0268] The term unit may have its conventional meaning in the field of electronics, electrical devices, and / or electronic devices and may include, for example, electric and / or electronic circuits, devices, modules, processors, memories, logical solid and / or discrete devices, computer programs or instructions, etc., for performing a respective task, procedure, computation, output, and / or display function, such as those described herein.

[0269] Abbreviation

[0270] At least some of the following abbreviations may be used in this disclosure. In case of inconsistencies between abbreviations, how the abbreviation is used above should be preferred. If listed multiple times below, the first listing should be preferred over subsequent listing(s). 1x RTT CDMA2000 1x wireless transmission technology 3GPP 3rd Generation Partnership Project 5G 5th Generation ABS Almost Blank Subframe ARQ Automatic Repeat Request AWGN Additive White Gaussian Noise BCCH Broadcast Control Channel BCH Broadcast Channel CA Carrier Aggregation CC Carrier Components CCCH SDU Common Control Channel SDU CDMA Code Division Multiple Access CGI Cell Global Identifier CIR Channel Impulse Response CP Cyclic Prefix CPICH Common Pilot Channel CPICH Ec / No CPICH received energy per chip divided by power density in band CQI Channel Quality Information C-RNTI Cell RNTI CSI Channel State Information DCCH Dedicated Control Channel DL Downlink DM Demodulation DMRS demodulation reference signal DRX Intermittent reception DTX Intermittent transmission DTCH Dedicated Traffic Channel DUT Device under test E-CID Extended Cell ID (positioning method) E-SMLC Evolved Serving Mobile Location Center ECGI Evolved CGI eNB E-UTRAN Node B ePDCCH Enhanced Physical Downlink Control Channel E-SMLC Evolved Serving Mobile Location Center E-UTRA (Extended UTRA) E-UTRAN (Extended UTRAN) FDD Frequency Division Duplex FFS Further consideration needed GERAN GSM EDGE Radio Access Network gNB NR base station GNSS Global Navigation Satellite System GSM Global System for Mobile Communications HARQ Hybrid Automatic Repeat Request HO Handover HSPA High Speed ​​Packet Access HRPD High Speed ​​Packet Data LOS Line of Sight LPP LTE Positioning Protocol LTE Long-Term Evolution MAC Media Access Control MBMS Multimedia Broadcast Multicast Service MBSFN Multimedia Broadcast Multicast Service Single Frequency Network MBSFN ABS MBSFN Almost Blank Subframe MDT Drive Test Minimization MIB Master Information Block MME Mobility Management Entity MSC Mobile Switching Center NPDCCH Narrowband Physical Downlink Control Channel NR new radio OCNG OFDMA Channel Noise Generator OFDM Orthogonal Frequency Division Multiplexing OFDMA Orthogonal Frequency Division Multiple Access OSS Operation Support System OTDOA Observation Arrival Time Difference O&M operation and maintenance PBCH Physical Broadcast Channel P-CCPCH Primary Common Control Physical Channel PCell Primary Cell PCFICH Physical Control Format Indicator Channel PDCCH Physical Downlink Control Channel PDP Profile Delay Profile PDSCH Physical Downlink Shared Channel PGW Packet Gateway PHICH Physical Hybrid Automatic Repeat Request Indication Channel PLMN Public Land Mobile Network PMI Precoder Matrix Indicator PRACH Physical Random Access Channel PRS Positioning Reference Signal PSS primary synchronization signal PUCCH Physical Uplink Control Channel PUSCH Physical Uplink Shared Channel RACH Random Access Channel QAM Quadrature Amplitude Modulation RAN Radio Access Network RAT Radio Access Technology RLM Radio Link Management RNC Radio Network Controller RNTI Radio Network Temporary Identifier RRC Radio Resource Control RRM Radio Resource Management RS reference signal RSCP Received Signal Code Power RSRP Reference Symbol Received Power or Reference signal received power RSRQ Reference Signal Reception Quality or Reference symbol reception quality RSSI Received Signal Strength Indicator RSTD reference signal time difference SCH Synchronization Channel SCell Secondary Cell SDU Service Data Unit SFN System Frame Number SGW Serving Gateway SI System Information SIB System Information Block SNR Signal to Noise Ratio SON Self-optimizing Network SS Sync Signal SSS secondary synchronization signal TDD Time Division Duplex TDOA arrival time difference TOA arrival time TSS tertiary sync signal TTI Transmission Time Interval UE User Equipment UL Uplink UMTS Universal Mobile Telecommunication System USIM Universal Subscriber Identity Module UTDOA Uplink Time Difference of Arrival UTRA Universal Terrestrial Radio Access UTRAN Universal Terrestrial Radio Access Network WCDMA Wide CDMA WLAN Wide Local Area Network

[0271] Further definitions and embodiments are described below.

[0272] In the above description of various embodiments of the inventive concept, it should be understood that the terminology used herein is merely for describing specific embodiments, and is not intended to limit the inventive concept. Unless otherwise specified, all terms (including technical and scientific terms) used herein have the same meaning as those commonly understood by those skilled in the art to which the inventive concept belongs. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning according to the meaning of those terms in the context of this specification and related art, and should not be interpreted in an ideal or overly formal sense unless expressly so defined herein.

[0273] When an element is referred to as being "connected," "coupled," "responsive" to another element, or variations thereof, the element may be directly connected, coupled, or responsive to the other element, or there may be intervening elements. In contrast, when an element is referred to as being "directly connected," "directly coupled," "directly responsive" to another element, or variations thereof, there are no intervening elements. Like numbers refer to like elements throughout. Furthermore, as used herein, "coupled," "connected," "responsive," or variations thereof may include wirelessly coupled, wirelessly connected, or wirelessly responsive. As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms unless the context clearly dictates otherwise. For the sake of brevity and / or clarity, well-known functions or constructions may not be described in detail. The term "and / or" (abbreviated as " / ") includes any and all combinations of one or more of the associated listed items.

[0274] Terms such as first, second, third, etc. may be used herein to describe various elements / operations, but it will be understood that these elements / operations should not be limited by these terms. These terms are merely used to distinguish one element / operation from another. Thus, a first element / operation in some embodiments may be called a second element / operation in other embodiments without departing from the teachings of the inventive concept. The same reference numbers or characters refer to the same or similar elements throughout this specification.

[0275] As used herein, the terms "comprise," "comprising," "comprises," "include," "including," "includes," "have," "has," "having," or variations thereof, are open-ended and include one or more stated features, integers, elements, steps, components, or functions, but do not exclude the presence or addition of one or more other features, integers, elements, steps, components, functions, or groups thereof. Additionally, as used herein, the common abbreviation "eg," from the Latin phrase "exempli gratia," may be used to introduce or specifically name one or more general examples of the aforementioned items, without being limiting of such items. The common abbreviation "ie," from the Latin phrase "id est," may be used to specifically name a particular item from a more general statement.

[0276] Exemplary embodiments have been described herein with reference to block diagrams and / or flowchart illustrations of computer-implemented methods, apparatus (systems and / or devices) and / or computer program products. It should be understood that blocks of the block diagrams and / or flowchart illustrations, and combinations of blocks in the block diagrams and / or flowchart illustrations, may be implemented by computer program instructions carried out by one or more computer circuits. These computer program instructions may be provided to processor circuits of general-purpose computer circuits, special-purpose computer circuits, and / or other programmable data processing circuits to create machines, such that the instructions executing via the processor of the computer and / or other programmable data processing apparatus transform and control transistors, values ​​stored in memory locations, and other hardware components in such circuits to implement the functions / acts specified in one or more blocks of the block diagrams and / or flowcharts, and thereby create means (functions) and / or structures for implementing the functions / acts specified in the block(s) of the block diagrams and / or flowcharts.

[0277] These computer program instructions may also be stored on a tangible computer readable medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored on the computer readable medium produce an article of manufacture that includes instructions that implement the functions / acts specified in one or more blocks of the block diagrams and / or flowcharts. Thus, embodiments of the inventive concepts may be embodied in hardware and / or in software (including firmware, resident software, microcode, etc.) running on a processor, such as a digital signal processor, which may be collectively referred to as a "circuit," "module," or variations thereof.

[0278] It should also be noted that in some alternative implementations, the functions / acts noted in the blocks may occur out of the order noted in the flowcharts. For example, two blocks shown in succession may in fact be performed substantially concurrently, or the blocks may sometimes be performed in reverse order, depending on the functions / acts involved. Moreover, the functionality of a given block of the flowcharts and / or block diagrams may be separated into multiple blocks, and / or the functionality of two or more blocks of the flowcharts and / or block diagrams may be at least partially integrated. Finally, other blocks may be added / inserted between the blocks shown, and / or blocks / acts may be omitted without departing from the scope of the inventive concept. Moreover, while some of the figures include arrows on communication paths to indicate a primary direction of communication, it should be understood that communication may occur in the opposite direction to the illustrated arrows.

[0279] Many variations and modifications may be made to the embodiments without substantially departing from the principles of the inventive concept. All such variations and modifications are intended to be included herein within the scope of the inventive concept. Accordingly, the subject matter disclosed above should be considered as illustrative and not limiting, and the example embodiments are intended to encompass all such modifications, extensions, and other embodiments that fall within the spirit and scope of the inventive concept. Thus, to the fullest extent permitted by law, the scope of the inventive concept should be determined by the broadest permissible interpretation of the present disclosure, including the example embodiments and their equivalents, and should not be limited or restricted by the above detailed description.

Claims

1. 1. A method implemented by a communications device in a network including a network node, the method comprising: receiving a Buffer Status Report (BSR) format configuration (1101) that specifies at least one non-legacy BSR format to be used for reporting a BSR to the network node; In response to receiving the non-legacy BSR format, selecting (1103) a non-legacy BSR format from the at least one non-legacy BSR format; generating a BSR report based on the non-legacy BSR format or the legacy BSR format according to a buffer size of the communication device (1105); Sending the BSR report towards the network node (1107); Including, generating the BSR report according to a buffer size of the communication device, in response to only one logical channel group (LCG) having data and a logical channel identification (LCID) having data and belonging to the LCG being configured to use the non-legacy BSR format; using a short BSR format, which is a legacy BSR format, to report the BSR in response to the buffer status index falling below a second threshold (1315); using the non-legacy BSR format to report the BSR in response to the buffer status index being above the second threshold (1317); A method comprising:

2. Selecting the non-legacy BSR format includes: selecting, in addition to the non-legacy BSR format, at least one legacy BSR format from a group of legacy BSR formats. Including, The method of claim 1 , wherein the BSR report comprises the non-legacy BSR format and the at least one legacy BSR format.

3. Sending a BSR indication message to the network node (1201), the BSR indication message indicating that the communication device supports the at least one non-legacy BSR format; Receiving a configuration message from the network node (1203), the configuration message specifying one or more non-legacy BSR formats to be used for BSR reporting; configuring the communication device for BSR reporting based on the configuration message, thereby creating a BSR reporting configuration (1205); The method of claim 1 or 2, further comprising:

4. The configuration message includes: the one or more non-legacy BSR formats to be used for BSR reporting for a Logical Channel Group (LCG) or Logical Channel Identification (LCID); the LCG or LCID for which the one or more non-legacy BSR formats should be used; The method of claim 3 , further comprising specifying at least one of:

5. generating the BSR report in response to two or more logical channel groups (LCGs) having data available for transmission and in response to there being uplink (UL) data for logical channels for which the non-legacy BSR format is configured or for logical channels belonging to an LCG configured to use the non-legacy BSR format, and the BSR being triggered by the UL data or by a timer expiring; using a long BSR format to report buffer status and using the non-legacy BSR format to report a logical channel identifier (LCID) or the LCG (1401); using the non-legacy BSR format to report a logical channel identifier (LCID) or buffer status for the LCG (1403); using the long BSR format to report buffer status for logical channels having data and for which the non-legacy BSR format was not configured or for logical channels having data and belonging to an LCG that is not configured to use the non-legacy BSR format (1405); using a long truncated BSR format to report buffer status and using the non-legacy BSR format to report a logical channel identifier (LCID) or the LCG (1407); Using the non-legacy BSR format to report buffer status for a logical channel identifier (LCID) or LCG (1411); The method according to claim 1 , further comprising at least one of the following steps:

6. generating a BSR report based on the selected non-legacy BSR format or legacy BSR format; in response to a sufficient number of padding bits remaining in a buffer for a message being sent towards the network node after a legacy BSR format has been added to the buffer and there being at least one LCG or at least one LCID configured to use the non-legacy BSR format, using the non-legacy BSR format to report a buffer status for the at least one LCG or the at least one LCID using the remaining padding bits (1501). Including, The method comprises: reporting a buffer status of the at least one LCG and the at least one LCID in order from highest priority using the remaining padding bits in response to not all LCGs or LCIDs of the at least one LCG and the at least one LCID being able to use the remaining padding bits (1601); The method of claim 1 , further comprising:

7. generating a BSR report based on the selected non-legacy BSR format or legacy BSR format; in response to there being a sufficient number of padding bits remaining in a buffer for a message being sent towards the network node after a legacy BSR format has been added to the buffer and there being at least one LCG or at least one LCID configured to use the non-legacy BSR format, and if a buffer status for the configured at least one LCG or at least one LCID is above a first threshold, using the non-legacy BSR format to report the buffer status for the at least one LCG or at least one LCID using the remaining padding bits (1701). The method of any one of claims 1 to 5, comprising:

8. A communication device (400) adapted to perform the method according to any one of claims 1 to 7.

9. A communication device (400), A processing circuit (403); and a memory (405) coupled to said processing circuit, said memory containing instructions that, when executed by said processing circuit, cause said communications device to perform the method of any one of claims 1 to 7. A communication device (400).

10. A computer program comprising a program code to be executed by a processing circuit (403) of a communications device (400), whereby execution of said program code causes said communications device (400) to perform a method according to any one of claims 1 to 7.

11. A computer program product comprising a non-transitory storage medium containing program code to be executed by a processing circuit (403) of a communications device (400), whereby execution of the program code causes the communications device (400) to perform a method according to any one of claims 1 to 7.

12. 1. A method implemented by a network node in a network, the method comprising: Receiving a Buffer Status Report (BSR) indication message from a communication device (1801), the BSR indication message indicating at least one non-legacy BSR format supported by the communication device; determining (1803) which non-legacy BSR formats are supported by the communication device based on the BSR indication message; determining (1805) at least one non-legacy BSR format for use by the communication device based on which non-legacy BSR formats are supported by the communication device; transmitting (1807) a radio resource control (RRC) configuration message for use by the communications device indicating one or more non-legacy BSR formats to be used for reporting a BSR; receiving (1809) from the communication device a BSR having at least one non-legacy BSR format or a legacy BSR format, generated according to a buffer size of the communication device, in response to only one logical channel group (LCG) having data and a logical channel identification (LCID) having data and belonging to this LCG being set to use the non-legacy BSR format; in response to the buffer status index falling below a second threshold, a BSR is generated using a legacy BSR format, a short BSR format, for reporting the BSR; in response to the buffer status index exceeding the second threshold, the BSR is generated using the non-legacy BSR format for reporting; A method comprising:

13. A Radio Access Network (RAN) node (500) adapted to perform the method of claim 12.

14. A radio access network (RAN) node (500), comprising: A processing circuit (503); and a memory (505) coupled to the processing circuit, the memory containing instructions that, when executed by the processing circuit, cause the RAN node to perform the method of claim 12. A Radio Access Network (RAN) node (500).

15. A computer program comprising program code to be executed by a processing circuit (503) of a Radio Access Network (RAN) node (500), whereby execution of said program code causes said RAN node (500) to perform the method of claim 12.

16. 13. A computer program product comprising a non-transitory storage medium containing program code to be executed by a processing circuit (503) of a Radio Access Network (RAN) node (500), whereby execution of the program code causes the RAN node (500) to perform the method of claim 12.

Images