Extended range for delay status reporting

Abstract

Systems and methods for extending the range of a delay status report message are provided. A wireless device obtains configuration information associated with usage of a remaining time field in a delay status report, the configuration information indicating how to convert a remaining time measurement into a remaining time field value. The wireless device converts a remaining time into a remaining time field value in accordance with the configuration information and transmits a delay status report message including the remaining time field value.

Description

P113303W001EXTENDED RANGE FOR DET AY STATUS REPORTINGCROSS REFERENCE TO RELEATED APPLICATIONS

[0001] This application claims the benefit of US Provisional Application No. 63 / 778,795 filed on March 27, 2025, the entire contents of which are hereby incorporated by reference.TECHNICAL FIELD

[0002] The present disclosure generally relates to wireless communications and wireless communication networks.INTRODUCTION

[0003] Standardization bodies such as Third Generation Partnership Project (3 GPP) are studying potential solutions for efficient operation of wireless communication in new radio (NR) networks. The next generation mobile wireless communication system 5G / NR will support a diverse set of use cases and a diverse set of deployment scenarios. The later includes deployment at both low frequencies (e.g. 100s of MHz), similar to LTE today, and very high frequencies (e.g. mm waves in the tens of GHz). Besides the typical mobile broadband use case, NR is being developed to also support machine type communication (MTC), ultra-low latency critical communications (URLCC), side-link device-to-device (D2D) and other use cases.

[0004] Low-latency high-rate applications such as extended Reality (XR) and cloud gaming are important in the 5G era. XR may refer to all real-and-virtual combined environments and human-machine interactions generated by computer technology and wearables. It is an umbrella term for different types of realities including Virtual Reality (VR), Augmented Reality (AR), Mixed Reality (MR), and the areas interpolated among them. The levels of virtuality range from partially sensory inputs to fully immersive VR. 5G / NR is designed to support applications demanding high rate and low latency in line with the requirements posed by the support of XR and cloud gaming applications in NR networks.

[0005] Logical channels (LCHs) for NR are described in the 3 GPP Medium Access Control (MAC) protocol specification (3GPP TS 38.321):P113303W001

[0006] “ The MAC sublayer provides data transfer services on logical channels. To accommodate different kinds of data transfer services, multiple types of logical channels are defined i.e. each supporting transfer of a particular type of information. Each logical channel type is defined by what type of information is transferred.”

[0007] The LCHs are then grouped in logical channel groups (LCGs), where there can be up to eight LCGs per UE.

[0008] The following is the configuration (LogicChannelConfig IE) of the logical channel as defined in 3GPP TS 38.331:— ASN1START— TAG-LOGICALCHANNELCONFIG-STARTLogicalChannelConf ig : : = SEQUENCE {ul-SpecificParameters SEQUENCE {priority INTEGER ( 1. . 16) , prioritisedBitRate ENUMERATED { kBpsO, kBps8 , kBps!6, kBps32 , kBps64 , kBps!28 , kBps256, kBps512 ,kBpslO24 , kBps2048 , kBps4096, kBps8192 , kBps!6384 , kBps32768 , kBps65536, infinity} ,bucketSizeDuration ENUMERATED {ms5, mslO, ms20, ms 50, ms 100, ms 150, ms 300, ms 500, ms 1000,spare7 , spare6, spare5, spare4 , spare3 , spare2 , sparel) ,allowedServingCells SEQUENCE ( SIZE( 1 . . maxNrof ServingCells-1 ) ) OF ServCelllndexOPTIONAL, — Cond PDCP-CADuplicationallowedSCS-List SEQUENCE ( SIZE ( 1 . . maxSCSs ) ) OF SubcarrierSpacing OPTIONAL, -- Need RmaxPUSCH-Duration ENUMERATED {ms0p02 , ms0p04 , ms0p0625, ms0pl25, ms0p25, ms0p5, ms0p01-vl700, sparel }OPTIONAL, — Need Rconf iguredGrantTypelAllowed ENUMERATED { true }OPTIONAL, — Need RlogicalChannelGroup INTEGER ( 0 . .maxLCG-ID) OPTIONAL, — Need RschedulingRequestID SchedulingRequestldOPTIONAL, — Need RlogicalChannelSR-Mask BOOLEAN,1 ogi cal Channel S R- Del ayTimerApplied BOOLEAN, bitRateQueryProhibitTimer ENUMERATED { s0, s0dot4 , s0dot8 , sldot6, s3, s6, sl2 , s30 } OPTIONAL, — Need R[ [allowedCG-List-rl6 SEQUENCE ( SIZE ( 0. . maxNrofConfiguredGrantConfigMAC-l-rl6) ) OF ConfiguredGrantConfigIndexMAC-rl6 OPTIONAL Need SP113303W001allowedPHY-PriorityIndex-rl6 ENUMERATED {p0, pl }OPTIONAL — Need S] ] ,[ [logical Channel Group I AB- Ext-r 17 INTEGER ( 0. . maxLCG-ID-IAB-r!7 ) OPTIONAL, — Need RallowedHARQ-mode-r!7 ENUMERATED { harqModeA, harqModeB} OPTIONAL — Need R] ]}OPTIONAL, — Cond UL[ [channelAccessPriority-rl6 INTEGER ( 1. .4 )OPTIONAL, — Need Rbit Ra t eMult iplier-r 16 ENUMERATED { x40, x70, xlOO, x200 } OPTIONAL — Need R] ]}— TAG-LOGICALCHANNELCONFIG-STOP— ASN1STOP

[0009] PDU Set Delay Budget

[0010] In Rel-18, 3GPP has introduced the concept of a Protocol Data Unit (PDU) Set, which represents one or more PDUs carrying the payload of one unit of information at the application (e.g., a frame or video slice).

[0011] For the PDU Set, several parameters have been introduced, e.g. the PDU Set Delay Budget (PDSB) which defines how long the PDU Set is valid.

[0012] Buffer and Delay Status Reports

[0013] The Buffer Status Report (BSR) is used to let the UE inform the gNB how large the UE buffer is. In Rel-18, 3GPP improvements to BSR were specified in order to reduce inaccuracies of the BSR.

[0014] Further, in Rel-18 3 GPP introduced a new report from the UE called Delay Status Report (DSR), which reports the amount of data buffered with a remaining time before discard below the configured threshold, together with the shortest remaining time of any Packet Data Convergence Protocol (PDCP) Service Data Unit (SDU) buffered. The current DSR format is illustrated in Figure 1.

[0015] The Rel-18 DSR fields include:

[0016] - LCGi: indicates presence of delay information for a certain LCGP113303W001

[0017] - Remaining time: indicates the shortest remaining value of running PDCP discardTimer among all PDCP SDUs that are buffered for an LCG but have not been transmitted in any MAC PDU.

[0018] - BT : indicates which table to use for buffer size reporting

[0019] - Buffer size: total amount of delay-critical UL data for an LCG

[0020] One potential shortcoming of Rel-18 DSR is that the information provided to the network does not help much for scheduling, since e.g. it is not possible to tell how large part of the buffer size that has a certain remaining time. Therefore, in Rel-19, discussions are ongoing for an enhancement of DSR where the DSR indicates a buffer size and a shortest remaining time for each portion that has a buffer size larger than zero. The current working assumption for the Rel-19 DSR format in 3 GPP RAN2 is illustrated in Figure 2.

[0021] The (assumed) Rel-19 DSR fields include:

[0022] LCGi: indicates presence of delay information for a certain LCG (i.e. same as for Rel-18 DSR)

[0023] BT : indicates which table to use for buffer size reporting (also same as for Rel-18 DSR)

[0024] Remaining time: indicates the shortest remaining time within a certain pre-configured interval

[0025] Buffer size: indicates the number of bytes that needs to be transmitted so that all PDU sets with remaining time in a certain interval can be transmitted

[0026] n: indicates whether there are more remaining time / buffer size pairs to report for an LCG (1) or not (0)

[0027] There currently exist certain challenges.SUMMARY

[0028] It is an object of the present disclosure to obviate or mitigate at least one disadvantage of the prior art.

[0029] There are provided systems and methods for extending the range of delay status reports.

[0030] In a first aspect there is provided a method performed by a wireless device. The wireless device can comprise a memory and processing circuitry and be configured to obtain configuration information indicating how to convert a remaining time measured in units of time into a remaining time field value. The wireless device converts a remaining time into a remaining time field valueP113303W001in accordance with the configuration information; and transmits a delay status report message including the remaining time field value.

[0031] In some embodiments, the wireless device can trigger a delay status report when a remaining time of one or more data units to be transmitted exceeds a triggering threshold. The data units can comprise Packet Data Convergence Protocol (PDCP) Service Data Units (SDU).

[0032] In some embodiments, the configuration information can include a first number indicating a maximum number of an interval in remaining time values and a second number indicating a corresponding multiplier. In some embodiments, converting the remaining time into the remaining time field value comprises dividing an actual remaining time in milliseconds by its corresponding multiplier to obtain the remaining time field value.

[0033] In some embodiments, the configuration information can include at least one table indicating a plurality of remaining time field values and their corresponding remaining times. The at least one table is applicable to at least one logical channel.

[0034] In some embodiments, the configuration information can include at least one table code point configured to represent a remaining time field value different from a direct numerical representation.

[0035] In some embodiments, the delay status report message is a Delay Status Report (DSR) Medium Access Control (MAC) Control Element (CE).

[0036] In some embodiments, the configuration information is received in Radio Resource Control (RRC) signaling.

[0037] In another aspect there is provided a method performed by a network node. The network node can comprise a memory and processing circuitry and be configured to transmit configuration information indicating how to convert a remaining time measured in units of time into a remaining time field value. The network node receives, from a wireless device, a delay status report message including a remaining time field value.

[0038] In some embodiments, the network node can further determine a remaining time from the remaining time field value included in the delay status report message in accordance with the configuration information. In some embodiments, the remaining time is used for scheduling decisions by the network node.

[0039] In some embodiments, the configuration information can include a first number indicating a maximum number of an interval in remaining time values and a second numberP113303W001indicating a corresponding multiplier. In some embodiments, determining a remaining time from the remaining time field value comprises multiplying the received remaining time field value by its corresponding multiplier to obtain an actual remaining time in milliseconds.

[0040] The various aspects and embodiments described herein can be combined alternatively, optionally and / or in addition to one another.

[0041] Other aspects and features of the present disclosure will become apparent to those ordinarily skilled in the art upon review of the following description of specific embodiments in conjunction with the accompanying figures.BRIEF DESCRIPTION OF THE DRAWINGS

[0042] Embodiments of the present disclosure will now be described, by way of example only, with reference to the attached Figures, wherein:

[0043] Figure 1 illustrates a Rel-18 Delay Status Report format;

[0044] Figure 2 illustrates a Rel-19 Delay Status Report format;

[0045] Figure 3 is an example communication system;

[0046] Figure 4 is a signaling diagram illustrating an example embodiment;

[0047] Figure 5 is a flow chart illustrating a method performed by a wireless device;

[0048] Figure 6 is a flow chart illustrating a method performed by a network node;

[0049] Figure 7 is a block diagram of an example wireless device;

[0050] Figure 8 is a block diagram of an example network node;

[0051] Figure 9 is a block diagram illustrating an example virtualization environment.DETAILED DESCRIPTION

[0052] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the description and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the description.

[0053] In the following description, numerous specific details are set forth. However, it is understood that embodiments may be practiced without these specific details. In other instances, well-known circuits, structures, and techniques have not been shown in detail in order not toP113303W001obscure the understanding of the description. Those of ordinary skill in the art, with the included description, will be able to implement appropriate functionality without undue experimentation.

[0054] References in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to implement such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

[0055] Figure 1 illustrates an example of a communication system 100 in accordance with some embodiments.

[0056] In the example, the communication system 100 includes a telecommunication network 102 that includes an access network 104, such as a radio access network (RAN), and a core network 106, which includes one or more core network nodes 108. The access network 104 includes one or more access network nodes, such as network nodes 110a and 110b (one or more of which may be generally referred to as network nodes 110), or any other similar 3rd Generation Partnership Project (3 GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 102, including one or more network nodes 110 and / or core network nodes 108.

[0057] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g.,P113303W001xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the 0-RAN Alliance or comparable technologies. The network nodes 110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 112A, 112B, 112C, and 112D (one or more of which may be generally referred to as UEs 112) to the core network 106 over one or more wireless connections.

[0058] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 100 may include any number of wired or wireless networks, network nodes, UEs, 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. The communication system 100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0059] The UEs 112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 110 and other communication devices. Similarly, the network nodes 110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 112 and / or with other network nodes or equipment in the telecommunication network 102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 102.

[0060] In the depicted example, the core network 106 connects the network nodes 110 to one or more host computing systems, such as host 116. These connections may be direct or indirectP113303W001via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 106 includes one more core network nodes (e.g., core network node 108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0061] The host 116 may be under the ownership or control of a service provider other than an operator or provider of the access network 104 and / or the telecommunication network 102. The host 116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0062] As a whole, the communication system 100 of Figure 1 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.P113303W001

[0063] In some examples, the telecommunication network 102 is a cellular network that implements 3 GPP standardized features. Accordingly, the telecommunications network 102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 102. For example, the telecommunications network 102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.

[0064] In some examples, the UEs 112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 104. Additionally, a UE may be configured for operating in single- or multi -RAT or multi -standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi -radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0065] In the example, the hub 114 communicates with the access network 104 to facilitate indirect communication between one or more UEs (e.g., UE 112C and / or 112D) and network nodes (e.g., network node HOB). In some examples, the hub 114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 114 may be a broadband router enabling access to the core network 106 for the UEs. As another example, the hub 114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 110, or by executable code, script, process, or other instructions in the hub 114. As another example, the hub 114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 114 may be a content source. For example, for a UE that is a VR device, display, loudspeaker, or other media delivery device, the hub 114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 114 actsP113303W001as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0066] The hub 114 may have a constant / persistent or intermittent connection to the network node HOB. The hub 114 may also allow for a different communication scheme and / or schedule between the hub 114 and UEs (e.g., UE 112C and / or 112D), and between the hub 114 and the core network 106. In other examples, the hub 114 is connected to the core network 106 and / or one or more UEs via a wired connection. Moreover, the hub 114 may be configured to connect to an M2M service provider over the access network 104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 110 while still connected via the hub 114 via a wired or wireless connection. In some embodiments, the hub 114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node HOB. In other embodiments, the hub 114 may be a nondedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 110B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0067] Note that some embodiments given herein refer to a 3 GPP cellular communications system and, as such, 3GPP terminology or terminology similar to 3GPP terminology is oftentimes used. However, the concepts disclosed herein are not limited to a 3GPP system.

[0068] Note that, in the description herein, reference may be made to the term “cell”. However, particularly with respect to 5G / NR concepts, beams may be used instead of cells and, as such, it is important to note that the concepts described herein are equally applicable to both cells and beams.

[0069] Returning to the discussion of logical channel configuration and delay status reports, one issue that is common to both the Rel-18 and Rel-19 DSR formats is that six bits are used to indicate the “remaining time” field and thus, they are used to indicate a remaining time between 0 and 63 ms. However, in some cases, the shortest remaining time may be larger than 63 ms.

[0070] As discussed, the Delay Status Reporting procedure is used to provide the serving gNB with the delay status of LCGs. This delay status for an LCG includes a “remaining time”, which is the smallest remaining value of the running PDCP discardTimers among PDCP SDUs that are buffered for the LCG but have not been transmitted in any MAC PDU, and the total amount of delay-critical UL data for the LCG according to the data volume calculation procedure for the associated RLC and PDCP entities, respectively.P113303W001

[0071] RRC controls the DSR procedure by configuring the remainingTimeThreshold (per LCG) parameter: the threshold on remaining time for a UE to trigger a DSR for a logical channel within an LCG.

[0072] Embodiments described herein allow for further configuration of the remaining time field signaled in the DSR MAC control element (CE) message.

[0073] In some embodiments, instead of letting the (e.g. 6-bit binary) numerical value for remaining time to directly represent a value in milliseconds, the numerical value field could be used to represent other values. The network can configure the UE on how the numerical values in the field remaining time can be converted / translated into actual time values, e.g. into milliseconds, and vice versa.

[0074] Accordingly, some embodiments can decrease the risk that the maximum value of the DSR field for remaining time is not sufficiently large.

[0075] In a first embodiment, the network configures the UE on how the UE should use the DRS field for remaining time. This is done via several pairs of numbers, where the first number in the pair denotes the maximum number of an interval in the remaining time values, and the second number in the pair indicates a multiplier. The numerical value in the field remaining time in a certain interval is then interpreted as the numerical value multiplied by the multiplier, which gives a value for actual remaining time in milliseconds.

[0076] Example 1:

[0077] The network configures the remaining time field usage for a UE by two pairs: (32, 1) and (63, 2).

[0078] This would mean that if the value in the remaining time field is 21 (binary 010101), the remaining time would be calculated / interpreted as 21*1= 21 ms.

[0079] If the value in the remaining time field is 45 (binary 101101), the remaining time is calculated as 45*2 = 90 ms.

[0080] Example 2:

[0081] The network configures the remaining time field usage for a UE by three pairs: (20, 1), (40, 2) and (63, 3). The same remaining time numbers as above will then be interpreted / calculated as:

[0082] Value 21 (binary 010101) => 21*2= 42 ms.

[0083] Value 45 (binary 101101) => 45*3=155 ms.P113303W001

[0084] In another embodiment, the multipliers can have a decimal representation in order to have a better granularity of the different remaining time values. The remaining time will then be the result of the multiplication and rounded down.

[0085] In another embodiment, the interpretation of specific table code points can be configured. For example, the value 1 may not be deemed necessary to use by network and is used to represent a higher value, e.g. 70. Thus, if remaining time is above the highest code point in table 63 but below 70, value 1 can be used. If remaining time is below 2 but above 0 the reported remaining time needs to use code point 2, i.e. the table will provide lower granularity for the range of the code points that are configured to represent other values.

[0086] In a related embodiment to all types of table construction, the UE can be configured by the network with different tables to be used. The table could be applicable for all LCID(s) which can trigger the DSR, or for one or more specific LCID. These tables can be indicated over control signaling, like RRC, or they can be specified in the standards. In the latter case, the network would indicate the table index or tables indexes which the UE would use.

[0087] In a further embodiment, the DSR can report for any range above the reporting thresholds by using the extension bit in the DSR format (NOTE: it has been agreed that Rel-19 format will contain an extension bit that indicates if a further reporting threshold will be reported for the same LCG). By extending the use of the extension bit, if the highest (or lowest) reporting threshold has been used for reporting a value pair the UE can still indicate that a further value pair will be reported for that LCG. This would then indicate that the value is outside of the reporting thresholds range. The UE can be configured with a new interpretation of the table values for this range (or standard has it defined). E.g. the table includes the code points of 0...63 but the remaining time values will be interpreted as above these values, e.g. 64-127. The buffer size reported would then be everything inside this new table range. Another option is to report for this range without needing data in the highest / lowest reporting threshold would be by reporting a value for that threshold with zero buffer size. Another related option is that as soon as a threshold (or specific threshold configured by network) is reporting 0 buffer size it is an indication that the next reporting value will be outside the reporting threshold range. To get further granularity on higher remaining time values, multiple table ranges can be defined / configured so that the first value reported for above the highest reporting threshold would only indicate a certain range, e.g. 64...80. In this case, yet another value pair needs to be used to report above 80 ms remaining time.P113303W001

[0088] Accordingly, a UE can be configured with information for converting the actual remaining time into a remaining time field value to be included in a DSR message. A gNB or other network node can convert / translate a received remaining time field value into actual time (e.g. milliseconds) in accordance with this configuration information.

[0089] Figure 4 is a signaling diagram illustrating an example embodiment. In step 120, the gNB 110 transmits a configuration message including configuration information associated with a logical channel and / or delay status reporting. The configuration information can indicate remaining time field usage for delay status reports. In step 122, the UE 112 can trigger a delay status report in accordance with one or more triggers. In step 124, the UE 112 converts a remaining time into a remaining time field value in accordance with the configuration information. In step 126, UE 112 transmits a delay status report message including the remaining time field value generated in step 124.

[0090] The various example messages, IES, fields, parameters described herein can be used to communicate information in the non-limiting embodiment of Figure 4.

[0091] Figure 5 is a flow chart illustrating an example method performed by a wireless device, such as UE 112 as described herein.

[0092] Step 130: The wireless device obtains configuration information. The configuration information can be received from an access node, such as gNB 110. In some embodiments, the configuration information can be received via RRC signaling. The configuration information can include information associated with usage of a remaining time field in a delay status report. The information associated with usage of the remaining time field can indicate how the wireless device can convert a remaining time (e.g. measured in units of time, such as milliseconds) into a value to be signaled in the “remaining time” field in a delay status report. As discussed, the remaining time is the amount of time until packet data (e.g. PDCP) is discarded.

[0093] Step 132: Optionally, the wireless device triggers delay status reporting. The wireless device can be configured to trigger generation of a DSR when a remaining time of one or more first data units to be transmitted exceeds a triggering threshold, the remaining time of a data unit indicating a remaining time until the data unit will be discarded. The wireless device can be configured with one or more triggering thresholds.

[0094] In some embodiments, the DSR reporting performed by the wireless device may be performed as part of an XR or cloud gaming application, for example, and the data units to beP113303W001transmitted by the wireless device (being subject to DSR reporting) may form part of data traffic of such XR application. The data units to be transmitted by the wireless device may correspond to SDUs / PDUs on one of a PDCP layer and an RLC layer, for example. As a mere example, the data units may be PDCP SDUs (e.g., originating from an IP packet arriving at the PDCP layer, e.g., conveying part of a video frame associated with the XR or cloud gaming application), for which the PDCP layer starts corresponding PDCP discard timers which, when expired, cause the PDCP SDUs (as well as the corresponding PDCP PDUs / RLC SDUs) to be discarded. In some variants, the data units may be delay-critical PDCP SDUs. In other variants, the data units may correspond to several PDUs forming a PDU Set.

[0095] In some embodiments, triggering a DSR can be in line with the known Rel-18 / Rel-19 functionalities as described above. A DSR may thus be triggered when a remaining time of one or more data units to be transmitted exceeds a triggering threshold (or “trigger threshold”). The “remaining time” for a data unit may indicate a remaining time until the data unit will be discarded and will as such sometimes also be called a “remaining time to discard” herein. Discarding a data unit may be implemented by a discard timer, such as a PDCP discard timer, for example. The data units may be waiting for transmission in a transmission buffer of the UE and discarding such data units may discard them from the transmission buffer accordingly. In variants in line with the background description of the DSR as a MAC CE above, the “remaining time” may be a shortest remaining value of a PDCP discard timer among all PDCP SDUs buffered for an LCG, for example.

[0096] Step 134: The wireless device converts the remaining time to a remaining time field value in accordance with the received configuration information. The wireless device can calculate and / or translate a remaining time from units of time (e.g. ms) to a value, corresponding to those units of time, that can be signaled in the remaining time field in a DSR message. The conversion can be in accordance with any of the various embodiments described herein. Accordingly, the wireless device generates a remaining time field value to be included in a triggered DSR.

[0097] In some embodiments, the configuration information indicates a mechanism for converting a measurement in units of time into a corresponding remaining time field value. In some embodiments, the configuration information includes a first number indicating a maximum number of an interval in remaining time values and a second number indicating a corresponding multiplier. In some embodiments, the configuration information includes at least one table codeP113303W001point indicating at least one remaining time value. In some embodiments, the configuration information includes at least one table indicating a plurality of remaining time values and their corresponding remaining time(s).

[0098] Step 136: The wireless device transmits a delay status report including the generated remaining time field value. The delay status report can be a DSR MAC CE. The delay status report can be transmitted to a network node such as gNB 110. The DSR message can further include one or more of the fields as described with respect to the known Rel-18 / Rel-19 DSR formats.

[0099] It will be appreciated that one or more of the above steps can be performed simultaneously and / or in a different order. Also, steps illustrated in dashed lines are optional and can be omitted in some embodiments.

[0100] It will be appreciated that in some embodiments, a wireless device 112 can communicate (e.g. transmit / receive messages) directly with a network node such as core network node 108. In other embodiments, messages and signals between the entities may be communicated via other nodes, such as radio access node (e.g. gNB, eNB) 110.

[0101] Figure 6 is a flow chart illustrating an example method performed by a network node. The network node can be an access node 110 such as the gNB as described herein.

[0102] Step 140: The network node transmits configuration information. The configuration information can be transmitted to one or more wireless devices. The configuration information can be transmitted via RRC signaling. The configuration information can include information associated with usage of a remaining time field in a delay status report. The information associated with usage of the remaining time field can indicate how the wireless device can convert a remaining time (e.g. measured in units of time, such as milliseconds) into a value to be signaled in the “remaining time” field in a delay status report.

[0103] Step 142: The network node receives a delay status report. The delay status report can be received from a wireless device. The delay status report can be a DSR MAC CE. The delay status report can include a remaining time field. The DSR message can further include one or more of the fields as described with respect to the known Rel-18 / Rel-19 DSR formats.

[0104] Step 144: Optionally, the network node determines a remaining time from the remaining time field value included in the delay status report message. The remaining time can be determined in accordance with the configuration information. The network node canP113303W001convert / calculate / generate a remaining time (in units of time such as milliseconds) from a corresponding value signaled in the remaining time filed included in the received DSR.

[0105] It will be appreciated that one or more of the above steps can be performed simultaneously and / or in a different order. Also, steps illustrated in dashed lines are optional and can be omitted in some embodiments.

[0106] Example Embodiments

[0107] Al. A method performed by a wireless device, the method comprising at least one of:

[0108] obtaining configuration information associated with usage of a remaining time field in a delay status report;

[0109] converting a remaining time into a remaining time field value in accordance with the configuration information; and

[0110] transmitting a delay status report message including the remaining time field value.[OHl] A2. The method of Al, further comprising, triggering a delay status report.

[0112] A3. The method of Al to A2, wherein the configuration information indicates a mechanism for converting a measurement in units of time into a corresponding remaining time field value.

[0113] A4. The method of Al to A3, wherein the configuration information includes a first number indicating a maximum number of an interval in the remaining time values and a second number indicating a multiplier.

[0114] A5. The method of Al to A3, wherein the configuration information includes at least one table code point indicating at least one remaining time field value.

[0115] A6. The method of Al to A3, wherein the configuration information includes at least one table indicating a plurality of remaining time field values.

[0116] A7. The method of Al to A6, wherein the delay status report is a DSR MAC CE.

[0117] A8. A wireless device comprising a radio interface and processing circuitry configured to perform the methods of any of embodiments A1-A7.

[0118] Bl. A method performed by a network node the method comprising:

[0119] transmitting configuration information associated with usage of a remaining time field in a delay status report; and

[0120] receiving a delay status report including a remaining time field value.P113303W001

[0121] B2. The method of Bl, further comprising, determining a remaining time from the remaining time field value included in the delay status report.

[0122] B3. The method of B2, wherein the remaining time is determined in accordance with the configuration information.

[0123] B4. The method of B1-B3, wherein the configuration information indicates a mechanism for converting a measurement in units of time into a corresponding remaining time field value.

[0124] B5. The method of B1-B4, wherein the configuration information includes a first number indicating a maximum number of an interval in the remaining time values and a second number indicating a multiplier.

[0125] B6. The method of B1-B4, wherein the configuration information includes at least one table code point indicating at least one remaining time field value.

[0126] B7. The method of B1-B4, wherein the configuration information includes at least one table indicating a plurality of remaining time field values.

[0127] B8. The method of B 1 to B7, wherein the delay status report is a DSR MAC CE.

[0128] B9. A network node comprising a radio interface and processing circuitry configured to perform the methods of any of embodiments B1-B8.

[0129] Figure 7 shows a wireless device UE 200 in accordance with some embodiments. The UE 200 presents additional details of some embodiments of the UE 112 of Figure 3. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage / playback device, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), an Augmented Reality (AR) or Virtual Reality (VR) device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.P113303W001

[0130] A UE may support device-to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0131] The UE 200 includes processing circuitry 202 that is operatively coupled via a bus 204 to an input / output interface 206, a power source 208, a memory 210, a communication interface 212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in this figure. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0132] The processing circuitry 202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 210. The processing circuitry 202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 202 may include multiple central processing units (CPUs).

[0133] In the example, the input / output interface 206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, aP113303W001directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0134] In some embodiments, the power source 208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 208 may further include power circuitry for delivering power from the power source 208 itself, and / or an external power source, to the various parts of the UE 200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 208 to make the power suitable for the respective components of the UE 200 to which power is supplied.

[0135] The memory 210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 210 includes one or more application programs 214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 216. The memory 210 may store, for use by the UE 200, any of a variety of various operating systems or combinations of operating systems.

[0136] The memory 210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, orP113303W001any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 210 may allow the UE 200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 210, which may be or comprise a device-readable storage medium.

[0137] The processing circuitry 202 may be configured to communicate with an access network or other network using the communication interface 212. The communication interface 212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 222. The communication interface 212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 218 and / or a receiver 220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 218 and receiver 220 may be coupled to one or more antennas (e.g., antenna 222) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0138] In the illustrated embodiment, communication functions of the communication interface 212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0139] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a networkP113303W001node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0140] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0141] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 200.

[0142] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3 GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipmentP113303W001that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0143] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0144] Figure 8 shows a network node 300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), 0-RAN nodes or components of an 0-RAN node (e g., 0-RU, 0-DU, O-CU).

[0145] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an 0-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0146] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi -standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes,P113303W001Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0147] The network node 300 includes a processing circuitry 302, a memory 304, a communication interface 306, and a power source 308. The network node 300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 304 for different RATs) and some components may be reused (e.g., a same antenna 310 may be shared by different RATs). The network node 300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 300.

[0148] The processing circuitry 302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node 300 components, such as the memory 304, to provide network node 300 functionality.

[0149] In some embodiments, the processing circuitry 302 includes a system on a chip (SOC).In some embodiments, the processing circuitry 302 includes one or more of radio frequency (RF) transceiver circuitry 312 and baseband processing circuitry 314. In some embodiments, the radio frequency (RF) transceiver circuitry 312 and the baseband processing circuitry 314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternativeP113303W001embodiments, part or all of RF transceiver circuitry 312 and baseband processing circuitry 314 may be on the same chip or set of chips, boards, or units.

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

[0151] The communication interface 306 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 306 comprises port(s) / terminal(s) 316 to send and receive data, for example to and from a network over a wired connection. The communication interface 306 also includes radio front-end circuitry 318 that may be coupled to, or in certain embodiments a part of, the antenna 310. Radio front-end circuitry 318 comprises filters 320 and amplifiers 322. The radio front-end circuitry 318 may be connected to an antenna 310 and processing circuitry 302. The radio front-end circuitry may be configured to condition signals communicated between antenna 310 and processing circuitry 302. The radio front-end circuitry 318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 320 and / or amplifiers 322. The radio signal may then be transmitted via the antenna 310. Similarly, when receiving data, the antenna 310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 318. The digital data may be passed to the processing circuitry 302. In other embodiments, theP113303W001communication interface may comprise different components and / or different combinations of components.

[0152] In certain alternative embodiments, the network node 300 does not include separate radio front-end circuitry 318, instead, the processing circuitry 302 includes radio front-end circuitry and is connected to the antenna 310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 312 is part of the communication interface 306. In still other embodiments, the communication interface 306 includes one or more ports or terminals 316, the radio front-end circuitry 318, and the RF transceiver circuitry 312, as part of a radio unit (not shown), and the communication interface 306 communicates with the baseband processing circuitry 314, which is part of a digital unit (not shown).

[0153] The antenna 310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 310 may be coupled to the radio front-end circuitry 318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 310 is separate from the network node 300 and connectable to the network node 300 through an interface or port.

[0154] The antenna 310, communication interface 306, and / or the processing circuitry 302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 310, the communication interface 306, and / or the processing circuitry 302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0155] The power source 308 provides power to the various components of network node 300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 300 with power for performing the functionality described herein. For example, the network node 300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 308. As a further example, the power source 308 mayP113303W001comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0156] Embodiments of the network node 300 may include additional components beyond those shown in this figure for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 300 may include user interface equipment to allow input of information into the network node 300 and to allow output of information from the network node 300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 300. In some embodiments providing a core network node, such as core network node 108 of Figure 3, some components, such as the radio front-end circuitry 318 and the RF transceiver circuitry 312 may be omitted.

[0157] Figure 9 is a block diagram illustrating a virtualization environment 400 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 400 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 400 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface. Virtualization may facilitate distributed implementations of a network node, UE, core network node, or host.

[0158] Applications 402 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in theP113303W001virtualization environment 400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0159] Hardware 404 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 406 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 408A and 408B (one or more of which may be generally referred to as VMs 408), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 406 may present a virtual operating platform that appears like networking hardware to the VMs 408.

[0160] The VMs 408 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 406. Different embodiments of the instance of a virtual appliance 402 may be implemented on one or more of VMs 408, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0161] In the context of NFV, a VM 408 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 408, and that part of hardware 404 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 408 on top of the hardware 404 and corresponds to the application 402.

[0162] Hardware 404 may be implemented in a standalone network node with generic or specific components. Hardware 404 may implement some functions via virtualization. Alternatively, hardware 404 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 410, which, among others, oversees lifecycle management of applications 402. InP113303W001some embodiments, hardware 404 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 412 which may alternatively be used for communication between hardware nodes and radio units.

[0163] Although the computing devices described herein (e.g., UEs, network nodes) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. 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.

[0164] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discreteP113303W001device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0165] The above-described embodiments are intended to be examples only. Alterations, modifications and variations may be effected to the particular embodiments by those of skill in the art without departing from the scope of the description.P113303W001ABBREVIATIONSAt least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s).3 GPP 3rd Generation Partnership Project5G 5th Generation6G 6thGenerationABS Almost Blank SubframeARQ Automatic Repeat RequestAWGN Additive White Gaussian NoiseBCCH Broadcast Control ChannelBCH Broadcast ChannelCA Carrier AggregationCC Carrier ComponentCCCH SDU Common Control Channel SDUCDMA Code Division Multiplex AccessCGI Cell Global IdentityCIR Channel Impulse ResponseCP Cyclic PrefixCPICH Common Pilot ChannelCQI Channel Quality InformationC-RNTI Cell RNTICSI Channel State InformationDCCH Dedicated Control ChannelDL DownlinkDM DemodulationDMRS Demodulation Reference SignalDRX Discontinuous ReceptionDTX Discontinuous TransmissionDTCH Dedicated Traffic ChannelDUT Device Under TestE-CID Enhanced Cell-ID (positioning method)Ec / No Received energy per chip divided by the power density in the band eMBMS Evolved Multimedia Broadcast Multicast ServicesECGI Evolved CGIeNB E-UTRAN NodeBePDCCH Enhanced Physical Downlink Control ChannelE-SMLC Evolved Serving Mobile Location CenterE-UTRAN Evolved Universal Terrestrial Radio Access NetworkFDD Frequency Division DuplexFFS For Further StudyBase station in NRGNSS Global Navigation Satellite SystemP113303W001HARQ Hybrid Automatic Repeat RequestHO HandoverHSPA High Speed Packet AccessHRPD High Rate Packet DataLOS Line of SightLPP LTE Positioning ProtocolLTE Long-Term EvolutionMAC Medium Access ControlMAC Message Authentication CodeMBSFN Multimedia Broadcast Multicast Service Single Frequency Network MBSFN ABS MBSFN Almost Blank SubframeMDT Minimization of Drive TestsMIB Master Information BlockMME Mobility Management EntityMSC Mobile Switching CenterNPDCCH Narrowband Physical Downlink Control ChannelNR New RadioOCNG OFDMA Channel Noise GeneratorOFDM Orthogonal Frequency Division MultiplexingOFDMA Orthogonal Frequency Division Multiple AccessOSS Operations Support SystemOTDOA Observed Time Difference of ArrivalO&M Operation and MaintenancePBCH Physical Broadcast ChannelP-CCPCH Primary Common Control Physical ChannelPCell Primary CellPCFICH Physical Control Format Indicator ChannelPDCCH Physical Downlink Control ChannelPDCP Packet Data Convergence ProtocolPDP Power Delay ProfilePDSCH Physical Downlink Shared ChannelPGW Packet GatewayPHICH Physical Hybrid-ARQ Indicator ChannelPLMN Public Land Mobile NetworkPMI Precoding Matrix IndicatorPRACH Physical Random Access ChannelPRS Positioning Reference SignalPSS Primary Synchronization SignalPUCCH Physical Uplink Control ChannelPUSCH Physical Uplink Shared ChannelRACH Random Access ChannelQAM Quadrature Amplitude ModulationRAN Radio Access NetworkRAT Radio Access TechnologyREC Radio Link ControlRLM Radio Link MonitoringRNC Radio NetworkP113303W001RNTI Radio Network Temporary IdentifierRRC Radio Resource ControlRRM Radio Resource ManagementRS Reference SignalRSCP Received Signal Code PowerRSRP Reference Symbol Received Power ORReference Signal Received PowerRSRQ Reference Signal Received Quality ORReference Symbol Received QualityRS SI Received Signal Strength IndicatorRSTD Reference Signal Time DifferenceSCH Synchronization ChannelSCell Secondary CellSDAP Service Data Adaptation ProtocolSDU Service Data UnitSFN System Frame NumberSGW Serving GatewaySI System InformationSIB System Information BlockSNR Signal to Noise RatioSON Self-Organizing Networkss Synchronization Signalsss Secondary Synchronization SignalTDD Time Division DuplexTDOA Time Difference of ArrivalTOA Time of ArrivalTSS Tertiary Synchronization SignalTTI Transmission Time IntervalUE User EquipmentUL UplinkUMTS Universal Mobile Telecommunications SystemUSIM Universal Subscriber Identity ModuleUTDOA Uplink Time Difference of ArrivalWCDMA Wideband CDMAWLAN Wireless Local Area Network

Claims

P113303W001CLAIMS1. A method performed by a wireless device, comprising:obtaining configuration information indicating how to convert a remaining time measured in units of time into a remaining time field value;converting a remaining time into a remaining time field value in accordance with the configuration information; andtransmitting a delay status report message including the remaining time field value.

2. The method of claim 1, further comprising, triggering the delay status report when a remaining time of one or more data units to be transmitted exceeds a triggering threshold.

3. The method of claim 2, wherein the data units comprise Packet Data Convergence Protocol (PDCP) Service Data Units (SDU).

4. The method of any one of claims 1 to 3, wherein the configuration information includes a first number indicating a maximum number of an interval in remaining time values and a second number indicating a corresponding multiplier.

5. The method of claim 4, wherein converting the remaining time into the remaining time field value comprises dividing an actual remaining time in milliseconds by its corresponding multiplier to obtain the remaining time field value.

6. The method of any one of claims 1 to 3, wherein the configuration information includes at least one table indicating a plurality of remaining time field values and their corresponding remaining times.

7. The method of claim 6, wherein the at least one table is applicable to at least one logical channel.

8. The method of any one of claims 1 to 3, wherein the configuration information includes at least one table code point configured to represent a remaining time field value different from a direct numerical representation.

9. The method of any one of claims 1 to 8, wherein the delay status report message is a Delay Status Report (DSR) Medium Access Control (MAC) Control Element (CE).P113303W00110. The method of any one of claims 1 to 9, wherein the configuration information is received in Radio Resource Control (RRC) signaling.

11. A wireless device comprising a memory and processing circuitry configured to:obtain configuration information indicating how to convert a remaining time measured in units of time into a remaining time field value;convert a remaining time into a remaining time field value in accordance with the configuration information; andtransmit a delay status report message including the remaining time field value.

12. The wireless device of claim 11, further configured to trigger the delay status report when a remaining time of one or more data units to be transmitted exceeds a triggering threshold.

13. The wireless device of claim 12, wherein the data units comprise Packet Data Convergence Protocol (PDCP) Service Data Units (SDU).

14. The wireless device of any one of claims 11 to 13, wherein the configuration information includes a first number indicating a maximum number of an interval in remaining time values and a second number indicating a corresponding multiplier.

15. The wireless device of claim 4, wherein converting the remaining time into the remaining time field value comprises dividing an actual remaining time in milliseconds by its corresponding multiplier to obtain the remaining time field value.

16. The wireless device of any one of claims 11 to 13, wherein the configuration information includes at least one table indicating a plurality of remaining time field values and their corresponding remaining times.

17. The wireless device of claim 16, wherein the at least one table is applicable to at least one logical channel.

18. The wireless device of any one of claims 11 to 13, wherein the configuration information includes at least one table code point configured to represent a remaining time field value different from a direct numerical representation.

19. The wireless device of any one of claims 11 to 18, wherein the delay status report message is a Delay Status Report (DSR) Medium Access Control (MAC) Control Element (CE).P113303W00120. The wireless device of any one of claims 11 to 19, wherein the configuration information is received in Radio Resource Control (RRC) signaling.

21. A method performed by a network node, comprising:transmitting configuration information indicating how to convert a remaining time measured in units of time into a remaining time field value; andreceiving, from a wireless device, a delay status report message including a remaining time field value.

22. The method of claim 21, further comprising, determining a remaining time from the remaining time field value included in the delay status report message in accordance with the configuration information.

23. The method of claim 22, wherein the remaining time is used for scheduling decisions by the network node.

24. The method of any one of claims 21 to 23, wherein the configuration information includes a first number indicating a maximum number of an interval in remaining time values and a second number indicating a corresponding multiplier.

25. The method of claim 24, wherein determining a remaining time from the remaining time field value comprises multiplying the received remaining time field value by its corresponding multiplier to obtain an actual remaining time in milliseconds.

26. The method of any one of claims 21 to 23, wherein the configuration information includes at least one table indicating a plurality of remaining time field values and their corresponding remaining times.

27. The method of claim 26, wherein the at least one table is applicable to at least one logical channel.

28. The method of any one of claims 21 to 23, wherein the configuration information includes at least one table code point configured to represent a remaining time value different from a direct numerical representation.

29. The method of any one of claims 21 to 28, wherein the delay status report message is a Delay Status Report (DSR) Medium Access Control (MAC) Control Element (CE).P113303W00130. The method of any one of claims 21 to 29, wherein the configuration information is transmitted in Radio Resource Control (RRC) signaling.

31. A network node comprising a memory and processing circuitry configured to:transmit configuration information indicating how to convert a remaining time measured in units of time into a remaining time field value; andreceive, from a wireless device, a delay status report message including a remaining time field value.

32. The network node of claim 31, further configured to determine a remaining time from the remaining time field value included in the delay status report message in accordance with the configuration information.

33. The network node of claim 32, wherein the remaining time is used for scheduling decisions by the network node.

34. The network node of any one of claims 31 to 33, wherein the configuration information includes a first number indicating a maximum number of an interval in remaining time values and a second number indicating a corresponding multiplier.

35. The network node of claim 34, wherein determining a remaining time from the remaining time field value comprises multiplying the received remaining time field value by its corresponding multiplier to obtain an actual remaining time in milliseconds.

36. The network node of any one of claims 31 to 33, wherein the configuration information includes at least one table indicating a plurality of remaining time field values and their corresponding remaining times.

37. The network node of claim 36, wherein the at least one table is applicable to at least one logical channel.

38. The network node of any one of claims 31 to 33, wherein the configuration information includes at least one table code point configured to represent a remaining time value different from a direct numerical representation.

39. The network node of any one of claims 31 to 38, wherein the delay status report message is a Delay Status Report (DSR) Medium Access Control (MAC) Control Element (CE).P113303W00140. The network node of any one of claims 31 to 39, wherein the configuration information is transmitted in Radio Resource Control (RRC) signaling.

Images