Signaling method for drop indication on control plane for augmented reality traffic data

Abstract

A method, system, and apparatus are disclosed. A first network node configured to communicate with a wireless device (WD) and a second network node is described. The first network node comprises: processing circuitry configured to determine a configuration comprising one or more discard rules for discarding one or more resources associated with a data unit; configuring one or both of the second network node and the WD with the determined configuration; and causing a drop activation request to be sent to one or both of the second network node and the WD based on the determined configuration. The drop activation request requests one or both of the second network node and the WD to activate the one or more drop rules.

Description

Technical Field

[0001] The present disclosure relates to wireless communications, and more particularly, to discarding signaling resources in an extended reality environment. Background Art

[0002] The 3rd Generation Partnership Project (3GPP) has developed and is developing standards for fourth-generation (4G) (also known as Long Term Evolution (LTE)) and fifth-generation (5G) (also known as New Radio (NR)) wireless communication systems. Such systems provide broadband communications between network nodes (such as base stations) and mobile wireless devices (WDs), as well as communications between network nodes and between WDs, among other capabilities. In particular, 5G capabilities can be used to support extended reality (XR) and cloud gaming, which are some examples of 5G media applications.

[0003] XR can be used as a general term for different types of reality, and can refer to a combination of real and virtual environments and human-computer interactions, such as those generated by computer technology and wearable devices. XR can include representative forms such as augmented reality (AR), mixed reality (MR), and virtual reality (VR), and / or intervening areas between them.

[0004] Additionally, edge computing as an aspect of the role of network architecture can be viewed as providing and / or supporting XR and cloud gaming, for example, XR and cloud gaming enabled by 3GPP Release 15 (Rel-15) NR networks. Edge computing is the concept of enabling the deployment of cloud computing capabilities and service environments close to cellular networks. Additionally, edge computing promises several benefits, such as lower latency, greater bandwidth, reduced backhaul traffic, and the prospect of providing several services on top of application architectures for enabling edge applications (e.g., 3GPP Technical Report (TR) 23.758). Edge applications are expected to leverage the low latency achieved by 5G and edge network architectures to reduce end-to-end application-level latency of typical systems.

[0005] Generally, 5G NR can support applications that require high throughput and low latency, which can meet the requirements for supporting XR and edge computing applications.

[0006] Figure 1 An example of the challenging nature of edge-based XR is shown. -5 Compared to edge-based XR, which can have latency constraints / requirements of 5ms minimum up to several 10ms and / or up to 10 -4However, XR services may require much higher bit rates (compared to other services), and in XR services, due to the low efficiency of codecs, the file sizes processed are larger, 10KB-100KB.

[0007] Additionally, other traffic features of edge-based XR may require predetermined dynamics associated with eye / viewport tracking. In some cases, although the traffic (i.e., data traffic) may appear to be periodic, the file size may vary, such as Figure 2 As shown. For example, XR applications may periodically generate traffic of different sizes. When an application packet enters the Internet (i.e., is sent, received, routed in the network, etc.), the application packet may initially be sent as a single protocol data unit (PDU) in the network, or it may be segmented into several PDUs. For example, one application packet may correspond to one or several Internet Protocol (IP) packets.

[0008] With respect to the radio access network, an IP packet may arrive at the RAN PDCP layer (i.e., a Packet Data Convergence Protocol (PDCP) Service Data Unit (SDU)), and the PDCP layer may be configured to create a PDCP PDU and / or pass it to lower layers. When an IP packet arrives at the PDCP, the PDCP layer starts a PDCP discard timer. When the discard timer expires, the PDCP discards the PDCP SDU and the corresponding PDCP data PDU. If the PDCP PDU has been passed to the lower layers, the PDCP indicates the discard to the lower layers. The lower layers (such as the Radio Link Control (RLC)) may discard the PDCP PDU (RLC SDU) if the RLC SDU or any fragment of the RLC SDU has not been sent to a lower layer.

[0009] In addition, the XR application PDU may have a time constraint, that is, one or a group of application PDUs may need to arrive at the receiver within a predetermined time (e.g., with a predetermined delay). If the application PDU is not received within the predetermined time, the application PDU will be of no use and can be discarded.

[0010] Although PDCP can start a discard timer whenever a PDCP SDU is received by a higher layer, the PDCP layer does not have any indication about how many PDCP SDUs correspond to one application PDU (or how many IP PDUs correspond to one application PDU). IP packets may arrive at PDCP with some jitter because they may traverse network segments, such as the Internet and the 3GPP core network. For example, an XR application PDU may be segmented into 5 IP packets, and the individual IP packets may arrive at the PDCP layer sequentially or out of order at times X+delta1, X+delta2, etc. Each packet may have a discard timer that runs at a predetermined time. In addition, these 5 PDCP SDUs (i.e., IP packets) must be delivered within a defined time budget. If the delay budget of an application packet has been exhausted, the 5 PDCP SDUs corresponding to the application packet may be discarded, even if the PDCP discard timer is running or not running.

[0011] The value of the current PDCP discard timer may not depend on the number of PDCP SDUs that may correspond to a single application PDU, for example, because the number of PDCP SDUs corresponding to a single application PDU may be different for different application PDUs. Setting the PDCP discard timer to a small fraction of the maximum delay for an application PDU may also impose a false limit that may result in unnecessary discards. For example, if the maximum delay is 10 milliseconds and the PDCP discard timer is set to 2 milliseconds, any single PDCP PDU may be discarded 2ms after it arrives at the PDCP. In the example using 5 IP packets, these 5 PDCP PDUs may be sent simultaneously 7ms after the first PDCP SDU is received, and these 5 PDCP PDUs may be delivered within the delay budget (e.g., 10 milliseconds). However, if the discard timer is a small fraction of the delay budget, then a small number of packets may be discarded within this small fraction of the delay budget.

[0012] Figure 3An example architecture where discard inefficiencies may exist is shown. In this example, an application generates one or more application PDUs, and all PDUs share the same delay budget (i.e., the PDUs need to be delivered within a maximum delay time). The application may also generate other additional application PDUs with different delay constraints, or may generate the PDUs at a later time. These application PDUs may traverse one or more networks, or may be directly connected to the 3GPP network. The application PDUs may be modified (e.g., segmented) by protocols below the application protocol to adapt to transmission characteristics. A challenge for the gNB (PDCP) (i.e., network node) may be to identify PDUs that belong to a set of application PDUs that are set with the same delay constraints and which PDUs need to be delivered first. For example, a PDU generated at t0 may need to be delivered before a PDU generated at t1.

[0013] Similar challenges may arise in uplink communications. For example, there may be more than one PDCP SDU associated with one application PDU arriving at the PDCP layer from the application layer. The WD may need to receive an UL grant to send the PDCP SDU. In addition, when the uplink grant does not arrive within a predetermined time or is not large enough (for example, its size is less than a predetermined threshold), the time budget for delivering the application PDU will be consumed, while there are still PDCP SDUs associated with the application PDU to be sent. In this example, the PDCP will still attempt to send these PDCP SDUs, even though these PDCP SDUs are no longer useful to the receiving node. In addition, attempting to send a "late" PDCP SDU may actually delay other PDCP SDUs associated with the second application PDU that arrives after the first application PDU.

[0014] In other words, current PDCP timers are not efficient (and / or may be difficult) for handling XR services due to one or more of the following reasons:

[0015] -XR applications may generate one or more application PDUs that need to be delivered within the delay budget. The application or the underlying layers may segment / concatenate the application PDUs.

[0016] - PDCP can receive IP PDUs from upper layers (if IP is used); however, PDCP does not know anything about how PDCP SDUs (IP PDUs) are mapped to application PDUs that need to be delivered within the same delay budget.

[0017] - The existing PDCP discard timer for a single PDCP SDU is not sufficient to handle the situations outlined in the above points.

[0018] When an application PDU that should have been delivered within a specific delay constraint is late, the subsequent application PDU will no longer be needed because the subsequent application PDU may depend on the previous application PDU for video decoding. Sending the corresponding PDCP SDU / PDU will result in a waste of resources. In addition, the existing independent discard timer between PDCP SDUs is not suitable for handling the unique situation of XR services, which allows PDCP SDUs to stay in the buffer for a longer time, although these PDCP SDUs are no longer needed from the application perspective. In other words, the method of PDCP using a PDCP discard timer to discard PDCP SDUs and / or PDUs is not efficient for XR applications.

[0019] Furthermore, existing methods / systems are unable to determine (e.g., a network node determines): that an independent frame (I frame) has been dropped or its delivery will exceed the packet delay budget; and how the network can drop all PDCP SDUs and PDUs in related frames (i.e., B frames, P frames) associated with the I frame and subsequent frames that depend on the I frame. Furthermore, in a split architecture, the PDCP entity and the entity holding the scheduling buffer may be located in different nodes: for example, in a gNodeB centralized unit (gNB-CU) and a gNodeB distributed unit (gNB-DU); in the case of multi-radio dual connectivity (MR-DC), the PDCP entity is located in a secondary node (SN).

[0020] In summary, the prior art fails to provide an efficient process for discarding resources such as PDUs in a frame. Summary of the invention

[0021] Some embodiments advantageously provide methods, systems, and apparatus for signaling (eg, signaling via a control plane) one or more indications that may be used to discard / drop resources, such as resources associated with XR service data.

[0022] In some embodiments, one or more methods are described for a PDCP entity to discard PDCP PDUs. PDCP PDUs in B frames and / or P frames associated with a discarded or to-be-discarded I frame or P frame are to be discarded.

[0023] In some other embodiments, the discarding rules for discarding the associated PDU set are determined by the network (i.e., the network node) and configured via radio resource control (RRC). After configuration, the PDCP entity can activate and / or deactivate the discarding rules, for example, activating and / or deactivating the discarding rules in the network and / or WD.

[0024] - In case of F1 split architecture, the discard rule activation / deactivation request is signaled by the network node, for example, by the gNB-CU to the gNB-DU.

[0025] - For SN terminated bearers in Multi-Radio Dual Connectivity (MR-DC) scenario, drop rule activation / deactivation may be sent from the PDCP entity in the SN over an interface (eg, Xn).

[0026] In one embodiment, the discard rules are configured by the RLC entity. In another embodiment, the discard rules are preconfigured in the WD, gNB-DU, and / or configured by the gNB-CU via RRC, where the discard rules can be signaled via other interfaces / protocols (such as XnAP and F1AP).

[0027] In some embodiments, activation / deactivation of the initial state of the drop rule may be performed via RRC and / or dynamically changed by RRC and / or lower layers (eg, medium access control (MAC) control element (CE)).

[0028] In some other embodiments, the discard rule configuration is performed by a network node (e.g., a network node that is / includes a gNB-CU and / or a PDCP entity). The discard rule configuration value and / or the initial activation state may be provided to the WD via RRC. The discard rule may also be activated and / or deactivated using control elements of the MAC layer or the PDCP layer. For a split NG-RAN architecture, the activation / deactivation request may be performed via F1AP. For dual connectivity, the discard rule may be signaled via XnAP. For SN terminated bearers, the SN may notify the MN (e.g., a network node configured to send RRC signaling to the WD) of the discard rule and activation / deactivation state. Control plane and / or user plane protocols may be used, for example, where the user plane protocol is enhanced.

[0029] In some embodiments, the discard rule configuration may be performed by another network node (e.g., a network node that is / includes a gNB-DU). The discard rule configuration values ​​may be signaled via the MAC / PHY (physical) layer. The initial configuration values ​​may be provided by the gNB-DU, which is provided to the gNB-CU. The discard rules may be activated and / or deactivated using control elements of the MAC layer or PDCP layer. In a split NG-RAN architecture, the activation and / or deactivation requests may be sent / received via F1AP. In dual connectivity, the requests (and / or discard rules) may be signaled via XnAP. Control plane and / or user plane protocols may be used, for example, where the user plane protocols are enhanced.

[0030] The methods, devices and systems described in the present disclosure benefit at least by preventing the network (network nodes) from sending data that is useless to the recipient. This can bring several benefits: for example, the system capacity is increased because useless data is not transmitted; latency can be reduced because physical resources can be reused for other data, thereby reducing buffering and / or latency; the number of satisfied XR users in the network may also increase because resources are allocated to data that can meet given requirements. In addition, a signaling solution is provided for configuring and / or providing discard rules by the network to the WD via a control plane (CP). In addition, support for discard rule configuration in dual connectivity is provided.

[0031] According to one aspect, a first network node configured to communicate with a wireless device (WD) and a second network node is described. The first network node includes: a processing circuit configured to determine a configuration including one or more discard rules, the discard rules being used to discard one or more resources associated with a data unit; cause one or both of the second network node and the WD to be configured with the determined configuration; and cause a discard activation request to be sent to one or both of the second network node and the WD based on the determined configuration. The discard activation request requests one or both of the second network node and the WD to activate the one or more discard rules.

[0032] In some embodiments, the one or more resources include any of frames and packets.

[0033] In some other embodiments, the frame is one of a B frame, a P frame, and an I frame.

[0034] In some embodiments, the frame has a protocol data unit set tag, and at least one of the one or more discard rules can be used for PDU set level discard based on the protocol data unit set tag. When at least one rule that can be used for PDU set level discard is activated, the frame and at least one other frame having the same protocol data unit set tag are discarded.

[0035] In some other embodiments, the data unit includes any one of a protocol data unit, a service data unit, and a set of protocol data units.

[0036] In some embodiments, the one or more dropping rules are based on an importance level associated with one or both of the resource and the data unit.

[0037] In some other embodiments, the activated one or more drop rules trigger one or both of the second network node and the WD to drop one or more resources associated with the data unit.

[0038] In some embodiments, the processing circuit is further configured to cause a discard deactivation request to be sent to one or both of the second network node and the WD. The discard deactivation request requests one or both of the second network node and the WD to deactivate the one or more discard rules.

[0039] In some other embodiments, the deactivated one or more drop rules trigger one or both of the second network node and the WD to refrain from dropping one or more resources associated with the data unit.

[0040] In some embodiments, one or more of the first network nodes include one of: a centralized unit, a packet data convergence protocol entity, and a distribution unit; and, when the first network node is one of the centralized unit and the packet data convergence protocol entity, the second network node includes a distribution unit; and when the first network node is a distribution unit, the second network node includes a centralized unit; and, one or both of the one or more resources and the data units are associated with extended reality signaling.

[0041] According to another aspect, a method in a first network node configured to communicate with a wireless device (WD) and a second network node is described. The method includes: determining a configuration including one or more discard rules for discarding one or more resources associated with a data unit; causing one or both of the second network node and the WD to be configured with the determined configuration; and sending a discard activation request to one or both of the second network node and the WD based on the determined configuration. The discard activation request requests one or both of the second network node and the WD to activate the one or more discard rules.

[0042] In some embodiments, the one or more resources include any of frames and packets.

[0043] In some other embodiments, the frame is one of a B frame, a P frame, and an I frame.

[0044] In some embodiments, the frame has a protocol data unit set tag, and at least one of the one or more discard rules is capable of PDU set level discarding based on the protocol data unit set tag. When the at least one rule capable of PDU set level discarding is activated, the frame and at least one other frame having the same protocol data unit set tag are discarded.

[0045] In some other embodiments, the data unit includes any one of a protocol data unit, a service data unit, and a set of protocol data units.

[0046] In some embodiments, the one or more dropping rules are based on an importance level associated with one or both of the resource and the data unit.

[0047] In some other embodiments, the activated one or more drop rules trigger one or both of the second network node and the WD to drop one or more resources associated with the data unit.

[0048] In some embodiments, the method further comprises sending a discard deactivation request to one or both of the second network node and the WD. The discard deactivation request requests one or both of the second network node and the WD to deactivate one or more discard rules.

[0049] In some other embodiments, the deactivated one or more drop rules trigger one or both of the second network node and the WD to refrain from dropping one or more resources associated with the data unit.

[0050] In some embodiments, one or more of the first network nodes include one of: a centralized unit, a packet data convergence protocol entity, and a distribution unit; and, when the first network node is one of the centralized unit and the packet data convergence protocol entity, the second network node includes a distribution unit; and when the first network node is a distribution unit, the second network node includes a centralized unit; and, one or both of the one or more resources and the data units are associated with extended reality signaling.

[0051] According to one aspect, a wireless device (WD) configured to communicate with a first network node and a second network node is described. The wireless device includes a processing circuit configured to: receive a configuration including one or more discard rules, the discard rules being used to discard one or more resources associated with a data unit; receive a discard activation request associated with the received configuration, wherein the discard activation request requests one or both of the second network node and the WD to activate the one or more discard rules; and, based on the discard activation request and the received configuration, discard the one or more resources associated with the data unit.

[0052] In some embodiments, the one or more resources include any of frames and packets.

[0053] In some other embodiments, the frame is one of a B frame, a P frame, and an I frame.

[0054] In some embodiments, the frame has a protocol data unit set tag. At least one of the one or more discard rules can be used for PDU set level discard based on the protocol data unit set tag. The method also includes: when at least one rule that can be used for PDU set level discard is activated, discarding the frame and at least one other frame having the same protocol data unit set tag.

[0055] In some other embodiments, the data unit includes any one of a protocol data unit, a service data unit, and a set of protocol data units.

[0056] In some embodiments, the one or more dropping rules are based on an importance level associated with one or both of the resource and the data unit.

[0057] In some other embodiments, the processing circuit further activates the one or more drop rules based on the drop activation request. The activated one or more drop rules trigger the WD to drop the one or more resources associated with the data unit.

[0058] In some embodiments, the processing circuit is further configured to: receive a discard deactivation request requesting one or both of the second network node and the WD to deactivate the one or more discard rules.

[0059] In some other embodiments, the deactivated one or more drop rules trigger the WD to refrain from dropping the one or more resources associated with the data unit.

[0060] In some embodiments, one or more of the first network nodes include one of: a centralized unit, a packet data convergence protocol entity, and a distribution unit; and, when the first network node is one of the centralized unit and the packet data convergence protocol entity, the second network node includes a distribution unit; and when the first network node is a distribution unit, the second network node includes a centralized unit; and, one or both of the one or more resources and the data units are associated with extended reality signaling.

[0061] According to another aspect, a method in a wireless device (WD) configured to communicate with a first network node and a second network node is described. The method comprises: receiving a configuration comprising one or more discard rules, the discard rules being used to discard one or more resources associated with a data unit; receiving a discard activation request associated with the received configuration, wherein the discard activation request requests one or both of the second network node and the WD to activate the one or more discard rules; and, based on the discard activation request and the received configuration, discarding the one or more resources associated with the data unit.

[0062] In some embodiments, the one or more resources include any of frames and packets.

[0063] In some other embodiments, the frame is one of a B frame, a P frame, and an I frame.

[0064] In some embodiments, the frame has a protocol data unit set tag. At least one of the one or more discard rules can be used for PDU set level discard based on the protocol data unit set tag. The method also includes: when the at least one rule that can be used for PDU set level discard is activated, discarding the frame and at least one other frame having the same protocol data unit set tag.

[0065] In some other embodiments, the data unit includes any one of a protocol data unit, a service data unit, and a set of protocol data units.

[0066] In some embodiments, one or more drop rules are based on an importance level associated with one or both of the resource and the data unit.

[0067] In some other embodiments, the method further includes: activating the one or more drop rules based on the drop activation request, wherein the activated one or more drop rules trigger the WD to drop the one or more resources associated with the data unit.

[0068] In some embodiments, the method further comprises: receiving a discard deactivation request requesting one or both of the second network node and the WD to deactivate the one or more discard rules.

[0069] In some other embodiments, the deactivated one or more drop rules trigger the WD to refrain from dropping the one or more resources associated with the data unit.

[0070] In some embodiments, one or more of the first network nodes include one of: a centralized unit, a packet data convergence protocol entity, and a distribution unit; and, when the first network node is one of the centralized unit and the packet data convergence protocol entity, the second network node includes a distribution unit; and when the first network node is a distribution unit, the second network node includes a centralized unit; and, one or both of the one or more resources and the data units are associated with extended reality signaling. BRIEF DESCRIPTION OF THE DRAWINGS

[0071] A more comprehensive understanding of the embodiments of the present application and the attendant advantages and features thereof will be more readily appreciated by reference to the following detailed description when considered in conjunction with the accompanying drawings, in which:

[0072] Figure 1 Examples of challenging characteristics of typical edge-based XR are shown;

[0073] Figure 2 shows the file sizes associated with a typical XR service profile;

[0074] Figure 3shows an example architecture where discard inefficiencies may exist;

[0075] Figure 4 is a schematic diagram illustrating an exemplary network architecture of a communication system connected to a host computer via an intermediate network according to the principles of the present disclosure;

[0076] Figure 5 is a block diagram of a host computer communicating with a wireless device via a network node over an at least partially wireless connection according to some embodiments of the present disclosure;

[0077] Figure 6 is a flow chart illustrating an exemplary method for executing a client application at a wireless device implemented in a communication system including a host computer, a network node, and a wireless device according to some embodiments of the present disclosure;

[0078] Figure 7 is a flow chart illustrating an exemplary method for receiving user data at a wireless device implemented in a communication system including a host computer, a network node, and a wireless device according to some embodiments of the present disclosure;

[0079] Figure 8 is a flow chart illustrating an exemplary method for receiving user data from a wireless device at a host computer implemented in a communication system including a host computer, a network node, and a wireless device according to some embodiments of the present disclosure;

[0080] Fig. 9 is a flow chart illustrating an exemplary method for receiving user data at a host computer implemented in a communication system including a host computer, a network node, and a wireless device according to some embodiments of the present disclosure;

[0081] Fig.10 is a flow chart of an exemplary process in a network node according to some embodiments of the present disclosure;

[0082] Fig.11 is a flow chart of an exemplary process in a wireless device according to some embodiments of the present disclosure;

[0083] Fig.12 is a flow chart of another exemplary process in a network node according to some embodiments of the present disclosure;

[0084] Fig.13 is a flow chart of another exemplary process in a wireless device according to some embodiments of the present disclosure;

[0085] Fig.14 is a flow chart of an example drop rule configuration according to some embodiments of the present disclosure;

[0086] Fig.15 is a flow chart of an example drop rule configuration according to some embodiments of the present disclosure. DETAILED DESCRIPTION

[0087] Before describing the exemplary embodiments in detail, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps associated with signaling (e.g., signaling via a control plane) one or more indications that may be used to discard / drop resources (e.g., resources associated with XR service data). Accordingly, components are appropriately represented in the drawings by conventional symbols, and only those specific details associated with understanding the embodiments are shown so as not to obscure the disclosure with details that would be apparent to one of ordinary skill in the art having the benefit of the description herein. Like reference numerals refer to like elements throughout the specification.

[0088] The relational terms used herein (such as "first" and "second", "top" and "bottom", etc.) may be used only to distinguish one entity or element from another entity or element, without necessarily requiring or implying any physical or logical relationship or order between these entities or elements. The terms used herein are for the purpose of describing specific embodiments only and are not intended to limit the concepts described herein. As used herein, the singular forms "a", "an", and "the" are intended to also include the plural forms, unless the context clearly indicates the contrary. It will also be understood that the terms "comprises", "comprising", "includes", and / or "including" when used herein indicate the presence of stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or combinations thereof.

[0089] In the embodiments described herein, the connection terms "in communication with..." and the like may be used to indicate electrical or data communication, which may be achieved, for example, by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling, or optical signaling. Those skilled in the art will appreciate that the multiple components may interoperate and that modifications and variations may be implemented for electrical and data communication.

[0090] In some embodiments described herein, the terms "coupled," "connected," and the like may be used herein to indicate a connection (although not necessarily a direct connection) and may include wired and / or wireless connections.

[0091] The term "network node (NN)" as used herein may be any type of network node included in a radio network, which may further include any of the following: a base station (BS), a radio base station, a base transceiver site (BTS), a base station controller (BSC), a radio network controller (RNC), an evolved Node B (eNB or eNodeB), a gNode B (gNB), an en-gNB (a gNB capable of connecting to an evolved packet core (EPC) and an eNB), a centralized unit (CU) (such as a gNB-CU), a distributed unit (DU) (such as a gNB-DU), a PDCP entity (e.g., a network node configured to perform one or more actions associated with PDCP), a Node B, a multi-standard radio (MSR) radio node (e.g., an MSR) BS), multi-cell / multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlled relay, radio access point (AP), transmission point, transmission node, remote radio unit (RRU), remote radio head (RRH), core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, coordination node, positioning node, MDT node, etc.), external node (e.g., third-party node, node outside the current network), node in distributed antenna system (DAS), spectrum access system (SAS) node, element management system (EMS), etc. The network node may also include test equipment. In some embodiments, two or more network nodes, such as gNB-CU and gNB-DU, may be located in the same physical location, so that the two or more network nodes may be collectively referred to as one network node. However, the network node is not limited thereto, and each of the gNB-CU and gNB-DU may be located in a different network node. In addition, the term "network node" may refer to a network entity (and / or network function) such as a DU, CU, etc., such that one or more network entities may be implemented in the same physical location and the same physical computing / communication node / device. A network node may also include a test device. The term "radio node" used herein may also be used to represent a wireless device (WD) or a radio network node such as a wireless device (WD).

[0092] In some other embodiments, a gNB-DU (i.e., DU) may refer to a logical node hosting the radio link control (RLC), media access control (MAC), and physical (PHY) layers of a network node (i.e., gNB, en-gNB). The operation of the gNB-DU may be at least partially controlled by the gNB-CU. One gNB-DU may support one or more cells. One cell may be supported by one gNB-DU. The gNB-DU may terminate the F1 interface connected to the gNB-CU. The gNB-CU control plane (gNB-CU-CP) may refer to a logical node hosting the control plane portion of the PDCP protocol and / or the radio resource control (RRC) of the gNB-CU of the network node (e.g., en-gNB or gNB). The gNB-CU-CP may terminate the E1 interface connected to the gNB-CU-user plane (gNB-CU-UP), and the F1-C interface connected to the gNB-DU.

[0093] In some embodiments, the non-limiting terms wireless device (WD) or user equipment (UE) are used interchangeably. The WD in this article can be any type of wireless device capable of communicating with a network node or another WD via a radio signal, such as a wireless device (WD). The WD can also be a radio communication device, a target device, a device-to-device (D2D) WD, a machine type WD, or a WD capable of machine-to-machine communication (M2M), a low-cost and / or low-complexity WD, a sensor equipped with a WD, a tablet computer, a mobile terminal, a smart phone, a laptop embedded device (LEE), a laptop mounted device (LME), a USB adapter, a client terminal device (CPE), an Internet of Things (IoT) device, or a narrowband IoT (NB-IoT) device, etc.

[0094] Furthermore, in some embodiments, the generic term "radio network node" is used. It may be any type of radio network node, including any of the following: base station, radio base station, base transceiver site, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, multi-cell / multicast coordination entity (MCE), IAB node, relay node, access point, radio access point, remote radio unit (RRU), remote radio head (RRH).

[0095] Note that although terminology from one particular wireless system such as 3GPP LTE and / or New Radio (NR) may be used in the present disclosure, this should not be considered to limit the scope of the present disclosure to only the above systems. Other wireless systems (including but not limited to Wideband Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB), and Global System for Mobile Communications (GSM)) may also benefit from utilizing the ideas covered by the present disclosure.

[0096] It should also be noted that the functions performed by a wireless device or network node described herein may be distributed across multiple wireless devices and / or network nodes. In other words, it is contemplated that the functions of the network nodes and wireless devices described herein are not limited to being performed by a single physical device and may in fact be distributed across several physical devices.

[0097] In some embodiments, the term "data unit" is used and may refer to a protocol data unit (PDU), a service data unit (SDU), etc. In some other embodiments, the term "PDU set" is used and may refer to one or more PDUs that carry an information payload.

[0098] In some embodiments, the term "discard" is used. For example, a resource such as a frame or packet that can be sent, received and / or processed is discarded. Discarding can refer to rejecting because it is unavailable, stopping sending, receiving and / or processing, buffering, deleting, not using, etc. For example, discarding a frame can refer to rejecting the frame because it is unavailable, stopping sending, receiving and / or processing, buffering, deleting, not using the frame, etc.

[0099] In some other embodiments, the term "drop rule" is used, which may refer to a rule by which one or more devices / nodes may drop a resource. The rule may include one or more conditions associated with a resource and / or communications with the resource.

[0100] In some embodiments, the term "frame" is used and may include bidirectional frames (B frames), predicted frames (P frames), intra frames (I frames), and / or any other type of frames. In some embodiments, a frame may be part of signaling sent, received, and / or processed by a device / node.

[0101] In some other embodiments, the term "activate" is used and may refer to triggering one or more devices and / or nodes to perform one or more actions. Activation may be requested as in an activation request. For example, the activation request may be a discard activation request configured to activate a discard rule (and / or a process associated with a discard rule). Similarly, deactivation may refer to triggering one or more devices and / or nodes to stop performing one or more actions. For example, a deactivation request may be a discard deactivation request configured to deactivate a discard rule (and / or a process associated with a discard rule).

[0102] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by those of ordinary skill in the art to which the present disclosure belongs. It will also be understood that the terms used herein should be interpreted as being consistent with their meanings in the context of this specification and the relevant art, and not interpreted as ideal or overly formal meanings, unless so explicitly defined herein.

[0103] Referring again to the drawings, wherein like elements are represented by like reference numerals, Figure 4 shown. Figure 4 A schematic diagram of a communication system 10 according to an embodiment is shown, the communication system 10 is, for example, a 3GPP type cellular network that can support standards such as LTE and / or NR (5G), which includes an access network 12 (such as a radio access network), and a core network 14. The access network 12 includes a plurality of network nodes 16a, 16b, 16c (collectively referred to as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each of which defines a corresponding coverage area 18a, 18b, 18c (collectively referred to as coverage area 18). Each network node 16a, 16b, 16c can be connected to the core network 14 via a wired or wireless connection 20. A first wireless device (WD) 22a located in the coverage area 18a is configured to be wirelessly connected to the corresponding network node 16a or to be paged by the corresponding network node 16a. A second WD 22b in the coverage area 18b is wirelessly connectable to the corresponding network node 16b. Although multiple WDs 22a, 22b (collectively referred to as wireless devices 22) are shown in this example, the disclosed embodiments are equally applicable to situations where only a single WD is in the coverage area or a single WD is connected to a corresponding network node 16. Note that although only two WDs 22 and three network nodes 16 are shown for convenience, the communication system may include more WDs 22 and network nodes 16.

[0104] Furthermore, it is contemplated that the WD 22 may communicate simultaneously with more than one network node 16 and more than one type of network node 16 and / or be configured to communicate individually with more than one network node 16 and more than one type of network node 16. For example, the WD 22 may have dual connectivity with a network node 16 that supports LTE and the same or different network node 16 that supports NR. As an example, the WD 22 may communicate with an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN.

[0105] The communication network 10 can itself be connected to a host computer 24, which can be implemented in the form of hardware and / or software of a stand-alone server, a cloud-implemented server, a distributed server, or as a processing resource in a server cluster. The host computer 24 can be under the ownership or control of a service provider, or can be operated by or on behalf of a service provider. The connections 26, 28 between the communication system 10 and the host computer 24 can extend directly from the core network 14 to the host computer 24, or can extend via an optional intermediate network 30. The intermediate network 30 can be a combination of one or more of a public network, a private network, or a managed network. The intermediate network 30 (if any) can be a backbone network or the Internet. In some embodiments, the intermediate network 30 can include two or more subnetworks (not shown).

[0106] Figure 4 The communication system as a whole realizes the connection between one of the connected WD 22a, 22b and the host computer 24. The connection can be described as an over-the-top (OTT) connection. The host computer 24 and the connected WD 22a, 22b are configured to use the access network 12, the core network 14, any intermediate network 30 and possible other infrastructure (not shown) as intermediaries to transmit data and / or signaling via the OTT connection. The OTT connection can be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are not aware of the routing of uplink and downlink communications. For example, the network node 16 may not be notified or may not need to be notified of the past routing of the input downlink communication with data originating from the host computer 24 to be forwarded (e.g., handed over) to the connected WD 22a. Similarly, the network node 16 does not need to be aware of the future routing of the output uplink communication originating from the WD 22a to the host computer 24.

[0107] The network node 16 is configured to include a NN resource unit 32, which is configured to perform any steps and / or tasks and / or processes and / or methods and / or features described in the present disclosure, such as: determining a configuration including at least one discard rule, the discard rule being used to discard at least one resource associated with the data unit; causing at least one of the WD and the second network node to be configured with the determined configuration; causing a discard activation request to be sent to the second network node based on the determined configuration, etc. The wireless device 22 is configured to include a WD resource unit 34, which is configured to perform any steps and / or tasks and / or processes and / or methods and / or features described in the present disclosure, such as: receiving a configuration including at least one discard rule, the discard rule being used to discard at least one resource associated with the data unit; causing signaling to be sent based on the received configuration and / or the discard activation request sent to the second network node, etc.

[0108] Now refer to Figure 5 An example implementation of the WD 22, network node 16, and host computer 24 according to the embodiment discussed in the previous paragraphs is described. In the communication system 10, the host computer 24 includes hardware (HW) 38, which includes a communication interface 40, which is configured to establish and maintain a wired or wireless connection with the interface of different communication devices of the communication system 10. The host computer 24 also includes a processing circuit 42, which may have storage and / or processing capabilities. The processing circuit 42 may include a processor 44 and a memory 46. In particular, in addition to or as an alternative to a processor (e.g., a central processing unit) and a memory, the processing circuit 42 may include an integrated circuit for processing and / or control, such as one or more processors and / or processor cores and / or FPGAs (field programmable gate arrays) and / or ASICs (application-specific integrated circuits) suitable for executing instructions. The processor 44 may be configured to access (e.g., write to or read from) a memory 46, which may include any type of volatile and / or non-volatile memory, such as cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read Only Memory).

[0109] Processing circuitry 42 may be configured to control any of the methods and / or processes described herein, and / or cause these methods and / or processes to be performed, for example, by host computer 24. Processor 44 corresponds to one or more processors 44 for performing the functions of host computer 24 described herein. Host computer 24 includes memory 46, which is configured to store data, program software code, and / or other information described herein. In some embodiments, software 48 and / or host application 50 may include instructions that, when executed by processor 44 and / or processing circuitry 42, cause processor 44 and / or processing circuitry 42 to perform the processes described herein with respect to host computer 24. The instructions may be software associated with host computer 24.

[0110] The software 48 may be executed by the processing circuit 42. The software 48 includes a host application 50. The host application 50 may be operable to provide services to a remote user (e.g., WD 22), which is connected via an OTT connection 52 terminated at the WD 22 and the host computer 24. When providing services to the remote user, the host application 50 may provide user data sent using the OTT connection 52. "User data" may be data and information described herein as implementing the described functions. In one embodiment, the host computer 24 may be configured to provide control and functionality to a service provider, and may be operated by or on behalf of the service provider. The processing circuit 42 of the host computer 24 may enable the host computer 24 to observe, monitor, control, send, and / or receive from the network node 16 and / or the wireless device 22 to the network node 16 and / or the wireless device 22. The processing circuitry 42 of the host computer 24 may include a host resource unit 54 configured to perform any of the steps and / or tasks and / or processes and / or methods and / or features described in the present disclosure, for example, to enable a service provider to observe / monitor / control / send to / receive from the network node 16 and / or the wireless device 22.

[0111] The communication system 10 also includes a network node 16 provided in the communication system 10, and the network node 16 includes hardware 58 that enables it to communicate with the host computer 24 and with the WD 22. The hardware 58 may include: a communication interface 60, which is used to establish and maintain a wired or wireless connection with the interface of different communication devices of the communication system 10; and a radio interface 62, which is used to establish and maintain at least a wireless connection 64 with the WD 22 located in the coverage area 18 served by the network node 16. The radio interface 62 can be formed as or can include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The communication interface 60 can be configured to facilitate a connection 66 with the host computer 24. The connection 66 can be direct, or it can pass through the core network 14 of the communication system 10 and / or through one or more intermediate networks 30 outside the communication system 10.

[0112] In the illustrated embodiment, the hardware 58 of the network node 16 also includes a processing circuit 68. The processing circuit 68 may include a processor 70 and a memory 72. In particular, in addition to or in lieu of a processor (such as a central processing unit) and a memory, the processing circuit 68 may also include an integrated circuit for processing and / or control, for example, one or more processors and / or processor cores and / or an FPGA (field programmable gate array) and / or an ASIC (application-specific integrated circuit) adapted to execute instructions. The processor 70 may be configured to access the memory 72 (e.g., write to or read from the memory 72), which may include any type of volatile and / or non-volatile memory, for example, a cache and / or buffer memory and / or a RAM (random access memory) and / or a ROM (read-only memory) and / or an optical memory and / or an EPROM (erasable programmable read-only memory).

[0113] Therefore, the network node 16 also has software 74, which is stored internally, for example, in the memory 72 or stored in an external memory (e.g., a database, a storage array, a network storage device, etc.) accessible by the network node 16 via an external connection. The software 74 can be executed by the processing circuit 68. The processing circuit 68 can be configured to control any method and / or process described herein, and / or cause these methods and / or processes to be performed, for example, by the network node 16. The processor 70 corresponds to one or more processors 70 for performing the network node 16 functions described herein. The memory 72 is configured to store data, program software code, and / or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and / or the processing circuit 68, cause the processor 70 and / or the processing circuit 68 to perform the process described herein with respect to the network node 16. For example, the processing circuit 68 of the network node 16 may include a NN resource unit 32, which is configured to perform any steps and / or tasks and / or processes and / or methods and / or features described in the present disclosure, such as: determining a configuration including at least one discard rule, the discard rule being used to discard at least one resource associated with the data unit; causing at least one of the WD and the second network node to be configured with the determined configuration; causing a discard activation request to be sent to the second network node based on the determined configuration, etc. In addition, the NN resource unit 32 may be configured to perform one or more actions associated with a CU, a DU, a PDCP entity, etc. In some embodiments, the NN resource unit 32 includes one or more of a CU (e.g., a gNB-CU), a DU (e.g., a gNB-DU), and a PDCP entity (or any other entity configured to perform a packet data function such as a packet data convergence protocol function).

[0114] The communication system 10 also includes the already mentioned WD 22. The WD 22 may have hardware 80, which may include a radio interface 82 configured to establish and maintain a wireless connection 64 with a network node 16 serving the coverage area 18 in which the WD 22 is currently located. The radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers.

[0115] The hardware 80 of the WD 22 also includes a processing circuit 84. The processing circuit 84 may include a processor 86 and a memory 88. In particular, as a supplement or alternative to a processor (such as a central processing unit) and a memory, the processing circuit 84 may also include an integrated circuit for processing and / or control, for example, one or more processors and / or processor cores and / or an FPGA (field programmable gate array) and / or an ASIC (application-specific integrated circuit) suitable for executing instructions. The processor 86 may be configured to access the memory 88 (e.g., write to or read from it), which may include any type of volatile and / or non-volatile memory, for example, a cache and / or buffer memory and / or a RAM (random access memory) and / or a ROM (read-only memory) and / or an optical memory and / or an EPROM (erasable programmable read-only memory).

[0116] Therefore, WD 22 may also include software 90, which is stored in a memory 88 at, for example, WD 22, or in an external memory (e.g., a database, a storage array, a network storage device, etc.) accessible by WD 22. The software 90 may be executed by the processing circuit 84. The software 90 may include a client application 92. The client application 92 may be operable to provide services to human or non-human users via WD 22 with the support of the host computer 24. In the host computer 24, the execution host application 50 may communicate with the execution client application 92 via the OTT connection 52 terminated at WD 22 and the host computer 24. When providing services to the user, the client application 92 may receive request data from the host application 50 and provide user data in response to the request data. The OTT connection 52 may transmit both request data and user data. The client application 92 may interact with the user to generate the user data it provides.

[0117] The processing circuit 84 may be configured to control any of the methods and / or processes described herein, and / or to cause these methods and / or processes to be performed, for example, by the WD 22. The processor 86 corresponds to one or more processors 86 for performing the WD 22 functions described herein. The WD 22 includes a memory 88 configured to store data, program software code, and / or other information described herein. In some embodiments, the software 90 and / or the client application 92 may include instructions that, when executed by the processor 86 and / or the processing circuit 84, cause the processor 86 and / or the processing circuit 84 to perform the process described herein with respect to the WD 22. For example, the processing circuit 84 of the wireless device 22 may include a WD resource unit 34, which is configured to perform any of the steps and / or tasks and / or processes and / or methods and / or features described in the present disclosure, such as: receiving a configuration including at least one discard rule, the discard rule being used to discard at least one resource associated with the data unit; causing signaling to be sent based on the received configuration and / or a discard activation request sent to the second network node, and the like.

[0118] In some embodiments, the internal workings of network node 16, WD 22, and host computer 24 are as follows: Figure 5 As shown, and independently, the surrounding network topology can be as Figure 4 shown.

[0119] exist Figure 5 , an OTT connection 52 has been abstractly depicted to illustrate communications between a host computer 24 and a wireless device 22 via a network node 16, without explicitly involving any intermediate devices and the precise routing of messages via these devices. The network infrastructure can determine the routing, which can be configured to be hidden from the WD 22 or from the service provider operating the host computer 24, or from both. The network infrastructure can also make decisions to dynamically change the routing while the OTT connection 52 is active (e.g., based on load balancing considerations or reconfiguration of the network).

[0120] The wireless connection 64 between WD 22 and network node 16 is consistent with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improves the performance of OTT services provided to WD 22 using OTT connection 52, where wireless connection 64 can form the last leg in OTT connection 52. More precisely, the teachings of some of these embodiments can improve data rates, latency, and power consumption, thereby providing benefits such as reduced user waiting time, relaxed file size restrictions, better responsiveness, extended battery life, etc.

[0121] In some embodiments, a measurement process may be provided for the purpose of monitoring the data rate, latency and other factors improved by one or more embodiments. There may also be an optional network function for reconfiguring the OTT connection 52 between the host computer 24 and the WD 22 in response to changes in the measurement results. The measurement process and / or network function for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24 or in the software 90 of the WD 22 or in both. In an embodiment, a sensor (not shown) may be deployed in or associated with a communication device through which the OTT connection 52 passes; the sensor may participate in the measurement process by providing the value of the monitoring quantity exemplified above or providing the value of other physical quantities that the software 48, 90 can use to calculate or estimate the monitoring quantity. Reconfiguration of the OTT connection 52 may include message formats, retransmission settings, preferred routes, etc.; the reconfiguration does not need to affect the network node 16, and it may be unknown or imperceptible to the network node 16. Some such processes and functions may be known and practiced in the art. In certain embodiments, the measurements may involve proprietary WD signaling that facilitates the host computer 24's measurement of throughput, propagation time, latency, etc. In some embodiments, the measurements may be implemented as follows: the software 48, 90 enables the use of the OTT connection 52 to send messages (specifically, empty or "dummy" messages) while it monitors propagation time, errors, etc.

[0122] Thus, in some embodiments, the host computer 24 includes processing circuitry 42 configured to provide user data and a communication interface 40 configured to forward the user data to a cellular network for transmission to the WD 22. In some embodiments, the cellular network also includes a network node 16 having a radio interface 62. In some embodiments, the network node 16 is configured to, and / or the processing circuitry 68 of the network node 16 is configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / terminating transmissions to the WD 22, and / or preparing / terminating / maintaining / supporting / terminating reception of transmissions from the WD 22.

[0123] In some embodiments, host computer 24 includes processing circuitry 42 and communication interface 40 configured to receive user data originating from transmissions from WD 22 to network node 16. In some embodiments, WD 22 is configured to and / or includes a radio interface 82 and / or processing circuitry 84 configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / terminating transmissions to network node 16, and / or preparing / terminating / maintaining / supporting / terminating reception of transmissions from network node 16.

[0124] although Figure 4and Figure 5 Various "units" (e.g., NN resource unit 32 and WD resource unit 34) are shown as being located within respective processors, but it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuit. In other words, these units may be implemented within the processing circuit in hardware or in a combination of hardware and software.

[0125] Figure 6 is a diagram showing a communication system (eg, Figure 4 and Figure 5 Flowchart of an exemplary method implemented in a communication system of FIG. 1 . The communication system may include a host computer 24, a network node 16, and a WD 22, which may be a reference Figure 5 The host computer, network node and WD described in the present disclosure. In a first step of the method, the host computer 24 provides user data (box S100). In an optional sub-step of the first step, the host computer 24 provides user data by executing a host application (e.g., host application 50) (box S102). In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (box S104). In an optional third step, in accordance with the teachings of the embodiments described throughout the present disclosure, the network node 16 sends the user data carried in the transmission initiated by the host computer 24 to the WD 22 (box S106). In an optional fourth step, the WD 22 executes a client application (e.g., client application 92) associated with the host application 50 executed by the host computer 24 (box S108).

[0126] Figure 7 is a diagram showing a communication system (eg, Figure 4 Flowchart of an exemplary method implemented in a communication system of FIG. 1 . The communication system may include a host computer 24, a network node 16, and a WD 22, which may be a reference Figure 4 and Figure 5 The host computer, network node and WD described in the method. In the first step of the method, the host computer 24 provides user data (box S110). In an optional sub-step (not shown), the host computer 24 provides the user data by executing a host application (e.g., the host application 50). In the second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (box S112). According to the teachings of the embodiments described throughout the present disclosure, the transmission can be via the network node 16. In the optional third step, the WD 22 receives the user data carried in the transmission (box S114).

[0127] Figure 8 is a diagram showing a communication system (eg, Figure 4Flowchart of an exemplary method implemented in a communication system of FIG. 1 . The communication system may include a host computer 24, a network node 16, and a WD 22, which may be a reference Figure 4 and Figure 5 The host computer, network node and WD described in the method. In the optional first step of the method, WD 22 receives input data provided by the host computer 24 (box S116). In the optional sub-step of the first step, WD 22 executes the client application 92, which responds to the received input data provided by the host computer 24 to provide user data (box S118). Additionally or alternatively, in the optional second step, WD 22 provides user data (box S120). In the optional sub-step of the second step, WD provides user data by executing a client application (such as client application 92) (box S122). When providing user data, the executed client application 92 can also consider user input received from the user. Regardless of the specific manner of providing user data, WD 22 can initiate the transmission of user data to the host computer 24 in the optional third sub-step (box S124). In the fourth step of the method, according to the teachings of the embodiments described throughout the present disclosure, the host computer 24 receives the user data sent from WD 22 (box S126).

[0128] Fig. 9 is a diagram showing a communication system (eg, Figure 4 Flowchart of an exemplary method implemented in a communication system of FIG. 1 . The communication system may include a host computer 24, a network node 16, and a WD 22, which may be a reference Figure 4 and Figure 5 In an optional first step of the method, the network node 16 receives user data from the WD 22 in accordance with the teachings of the embodiments described throughout the present disclosure (block S128). In an optional second step, the network node 16 initiates a transmission of the received user data to the host computer 24 (block S130). In a third step, the host computer 24 receives the user data carried in the transmission initiated by the network node 16 (block S132).

[0129] Fig.10is a flow chart of an exemplary process in a network node 16 (e.g., a first network node 16a). One or more blocks described herein may be performed by one or more units of the network node 16, for example, by one or more of the processing circuit 68 (including the NN resource unit 32), the processor 70, the radio interface 62, and / or the communication interface 60. The network node 16 is configured, for example, via the processing circuit 68 and / or the processor 70 and / or the radio interface 62 and / or the communication interface 60 to: determine (block S134) a configuration including at least one discard rule for discarding at least one resource associated with a data unit; cause (block S136) at least one of the WD 22 and the second network node 16b to be configured with the determined configuration; send (block S138) a discard activation request to the second network node 16b based on the determined configuration; and receive (block S140) a discard activation response indicating successful activation of the at least one discard rule.

[0130] In some embodiments, the at least one resource is any of a frame and a packet, and the data unit comprises any of a protocol data unit or a service data unit associated with augmented reality signaling.

[0131] In some other embodiments, the sent drop activation request causes at least one of the first network node 16a, the second network node 16b, and the WD 22 to drop at least one resource associated with the data unit.

[0132] In one embodiment, the first network node 16a is one of a centralized unit, a packet data convergence protocol entity, and a distribution unit; when the first network node 16a is a centralized unit or a packet data convergence protocol entity, the second network node 16b is a distribution unit, and when the first network node 16a is a distribution unit, the second network node 16b is a centralized unit.

[0133] Fig.11 is a flow chart of an exemplary process in the wireless device 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more units of the WD 22, for example, by one or more of the processing circuit 84 (including the WD resource unit 34), the processor 86, the radio interface 82, and / or the communication interface 60. The wireless device 22 is configured, for example, via the processing circuit 84 and / or the processor 86 and / or the radio interface 82 to: receive a configuration including at least one discard rule, the discard rule being used to discard at least one resource associated with the data unit; and send signaling based on the received configuration and / or the discard activation request sent to the second network node 16b.

[0134] In some embodiments, the at least one resource is any of a frame and a packet, and the data unit comprises any of a protocol data unit or a service data unit associated with augmented reality signaling.

[0135] In some other embodiments, the sent drop activation request causes at least one of the first network node 16a, the second network node 16b, and the WD 22 to drop at least one resource associated with the data unit.

[0136] In one embodiment, the first network node 16a is one of a centralized unit, a packet data convergence protocol entity, and a distribution unit; when the first network node 16a is a centralized unit or a packet data convergence protocol entity, the second network node 16b is a distribution unit, and when the first network node 16a is a distribution unit, the second network node 16b is a centralized unit.

[0137] Fig.12 1 is a flow chart of an exemplary process in a network node 16 (e.g., a first network node 16a). One or more blocks described herein may be performed by one or more units of the network node 16, for example, by one or more of the processing circuit 68 (including the NN resource unit 32), the processor 70, the radio interface 62, and / or the communication interface 60. The network node 16 is configured, for example, via the processing circuit 68 and / or the processor 70 and / or the radio interface 62 and / or the communication interface 60 to: determine (block S146) a configuration including one or more discard rules for discarding one or more resources associated with the data unit; cause (block S148) one or both of the second network node 16b and the WD 22 to be configured with the determined configuration; and send (block S150) a discard activation request to one or both of the second network node 16b and the WD 22 based on the determined configuration. The discard activation request requests one or both of the second network node 16b and the WD 22 to activate one or more discard rules.

[0138] In some embodiments, the one or more resources include any of frames and packets.

[0139] In some other embodiments, the frame is one of a B frame, a P frame, and an I frame.

[0140] In some embodiments, the frame has a protocol data unit set tag, and at least one of the one or more discard rules is capable of PDU set level discarding based on the protocol data unit set tag. When the at least one rule capable of PDU set level discarding is activated, the frame and at least one other frame having the same protocol data unit set tag are discarded.

[0141] In some other embodiments, the data unit includes any one of a protocol data unit, a service data unit, and a set of protocol data units.

[0142] In some embodiments, the one or more dropping rules are based on an importance level associated with one or both of the resource and the data unit.

[0143] In some other embodiments, the activated one or more drop rules trigger one or both of the second network node 16b and the WD 22 to drop one or more resources associated with the data unit.

[0144] In some embodiments, the method further comprises sending a discard deactivation request to one or both of the second network node 16b and the WD 22. The discard deactivation request requests one or both of the second network node 16b and the WD 22 to deactivate one or more discard rules.

[0145] In some other embodiments, the deactivated one or more drop rules trigger one or both of the second network node 16b and the WD 22 to refrain from dropping one or more resources associated with the data unit.

[0146] In some embodiments, one or more of the first network nodes 16a include one of: a centralized unit, a packet data convergence protocol entity, and a distribution unit; and, when the first network node 16a is one of the centralized unit and the packet data convergence protocol entity, the second network node 16b includes a distribution unit; and when the first network node 16a is a distribution unit, the second network node 16b includes a centralized unit; and, one or both of the one or more resources and data units are associated with extended reality signaling.

[0147] Fig.13 is a flow chart of an exemplary process in the wireless device 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more units of the WD 22, for example, by one or more of the processing circuit 84 (including the WD resource unit 34), the processor 86, the radio interface 82 and / or the communication interface 60. The wireless device 22 is configured, for example, via the processing circuit 84 and / or the processor 86 and / or the radio interface 82 to: receive (block S152) a configuration including one or more discard rules, the discard rules being used to discard one or more resources associated with the data unit; receive (block S154) a discard activation request associated with the received configuration, wherein the discard activation request requests one or both of the second network node 16b and the WD 22 to activate the one or more discard rules; and based on the discard activation request and the received configuration, discard (block S156) one or more resources associated with the data unit.

[0148] In some embodiments, the one or more resources include any of frames and packets.

[0149] In some other embodiments, the frame is one of a B frame, a P frame, and an I frame.

[0150] In some embodiments, the frame has a protocol data unit set tag. At least one of the one or more discard rules can be used for PDU set level discard based on the protocol data unit set tag. The method also includes: when the at least one rule that can be used for PDU set level discard is activated, discarding the frame and at least one other frame having the same protocol data unit set tag.

[0151] In some other embodiments, the data unit includes any one of a protocol data unit, a service data unit, and a set of protocol data units.

[0152] In some embodiments, one or more drop rules are based on an importance level associated with one or both of the resource and the data unit.

[0153] In some other embodiments, the method further includes: activating the one or more drop rules based on the drop activation request, wherein the activated one or more drop rules trigger WD 22 to drop the one or more resources associated with the data unit.

[0154] In some embodiments, the method further comprises receiving a drop deactivation request requesting one or both of the second network node 16b and the WD 22 to deactivate one or more drop rules.

[0155] In some other embodiments, the deactivated one or more drop rules trigger the WD 22 to refrain from dropping the one or more resources associated with the data unit.

[0156] In some embodiments, one or more of the first network nodes 16a include one of: a centralized unit, a packet data convergence protocol entity, and a distribution unit; and, when the first network node 16a is one of the centralized unit and the packet data convergence protocol entity, the second network node 16b includes a distribution unit; and when the first network node 16a is a distribution unit, the second network node 16b includes a centralized unit; and, one or both of the one or more resources and data units are associated with extended reality signaling.

[0157] Having described the general processing flow of the arrangements of the present disclosure, and having provided examples of hardware and software arrangements for implementing the processes and functions of the present disclosure, the following sections provide details and examples of arrangements that signal (e.g., signaled via a control plane) one or more indications that can be used to discard / drop resources (e.g., resources associated with XR business data).

[0158] Some embodiments provide one or more network nodes 16 (e.g., a first network node 16a, a second network node 16b) and a WD 22 (which may be referred to as a UE). Any network node 16 may be / may include at least one of the following: a gNB-CU, a PDCP entity, a gNB-DU, an RLC entity, etc., and may be configured to determine a discard rule for discarding one or more resources (e.g., a PDU set). For example, the first network node 16 may refer to a gNB-DU, and the second network node 16 may refer to a gNB-CU. The PDCP entity may be configured to discard a PDU (e.g., a PDU in an XR PDU set). For discarding, a discard rule may be configured in the network (i.e., the network node 16). The discard rule may be configured using the RRC at the second network node 16 (e.g., the gNB-CU). A request may be sent from the second network node 16 (e.g., gNB-CU) (i.e., the network node 16 hosting the PDCP entity) to the first network node 16 (e.g., gNB-DU) (i.e., the network node 16 hosting the RLC entity) so that the first network node 16 (e.g., gNB-DU) activates the discard rule in the WD 22 (or deactivates it).

[0159] In some other embodiments, the network node 16 (e.g., RLC entity) may be configured to discard the PDU. The discard rule may be configured by the first network node 16 (e.g., gNB-DU), for example, in a lower layer. The configuration may be signaled to the second network node 16 (e.g., gNB-CU), which may send a request to the first network node 16 (e.g., gNB-DU) to activate the discard rule in the WD 22.

[0160] The discard command may be sent from the first network node 16 (e.g., gNB-DU) to the WD 22, which may occur after the second network node 16 (e.g., gNB-CU) signals to the first network node 16 (e.g., gNB-DU). In other words, the gNB-CU may query the first network node 16 (e.g., gNB-DU), and the first network node 16 (e.g., gNB-DU) may activate the rule through downlink control information (DCI) or MAC CE. The WD 22 may be configured to follow (i.e., apply, perform actions based on) the discard rule configured (e.g., configured by RLC / PDCP) and activated by the second network node 16 (e.g., gNB-CU).

[0161] The discard rule may be associated with edge computing and / or XR and / or cloud gaming. Edge computing may be used to help the 5G system achieve predetermined performance to enable XR and cloud gaming. In some embodiments, the discard rule refers to a discard rule.

[0162] In addition, from a capacity perspective, it may be beneficial to use a group PDCP timer to discard all PDUs and PDCP SDUs belonging to a specific PDU set (application data unit). Other methods may be used to predict whether a PDU set meets a predetermined condition (e.g., a requirement). If at least one condition cannot be met, all PDUs and PDCP SDUs corresponding to a given PDU set may be discarded based on different types of XR application information (e.g., the packet size of the PDU set, the number of IP packets belonging to the PDU set, or the type of the PDU set (e.g., posture, one of a set of video frames, or audio)).

[0163] In XR application services, there are several types of video frames, for example, I-frames are independent frames. That is, the decoder can decode I-frames without the help of other previously received frames. However, there are other types of frames, such as B-frames or P-frames, whose decoding depends on the successful reception of independent frames and / or the successful reception of other related frames (such as B-frames or P-frames).

[0164] Discard B and P frames associated with I frames in DU

[0165] B frames and P frames may be marked with their own PDU set tags as well as an I frame PDU set tag. When a subsequent PDCP entity (e.g., a network node 16 including a PDCP entity) indicates to discard a frame (e.g., an I frame with a PDU set tag), all subsequent associated related frames, such as B frames and P frames, may be discarded until a new independent frame (e.g., an I frame based on an I frame PDU set tag) is received. This discarding may be used when the PDCP entity also indicates explicit discarding based on a B frame or P frame PDU set tag.

[0166] If the PDU set transmission time is greater than the maximum PDU set delay requirement, the PDCP layer may discard all packets belonging to the PDU set, including packets that have been delivered to layers below the PDCP layer. In particular, the RLC entity in the first network node 16 (e.g., gNB-DU) may discard the relevant packets according to the configuration (sent, executed) by the second network node 16 (e.g., gNB-CU). The configuration may include any information that can be used to identify and / or discard RLC packets related to the discarded PDCP packets.

[0167] In addition, the receiving PDCP entity in the WD 22 may be configured to be aware of the discard configuration of the transmitting PDCP entity in the second network node 16 (e.g., gNB-CU) and the transmitting RLC entity in the first network node 16 (e.g., gNB-DU). For example, if a portion of the PDU set bits are received in the WD 22, and the remaining bits (i.e., the remaining bits in the PDU set bits) are discarded in the network (i.e., the network node 16, the access network 12, the core network 14, an intermediate network such as a cloud network), the WD 22 may be configured to discard the received packets in the corresponding layer according to a predetermined configuration rule (e.g., a configuration including a discard rule). Therefore, the network provides the configuration rule to the WD 22, for example, via the signaling described above to enable such behavior.

[0168] The PDCP discard solution of the present disclosure may also be applicable to uplink XR traffic of WD 22. The gNB (e.g., network node 16) may communicate explicitly with WD 22 to control uplink traffic signaling. As a non-limiting example, parameters / commands associated with a discard trigger may be included (e.g., in a configuration, a discard rule, etc.), such as a delay requirement, bit rate, delay margin, bit rate margin, flow, service, quality of service flow ID (QFI), etc. to which the mechanism applies, an explicit command to trigger the discard based on the gNB's observation of the uplink transmission, etc. The parameters of the triggering condition may be signaled via an RRC configuration, and the explicit discard request to WD 22 may be RRC and / or MAC-CE to allow flexible and dynamic decisions based on traffic changes.

[0169] Fig.14 and 15 An example of network signaling that may occur between a network node 16 (e.g., gNB-CU, gNB-DU) and a WD 22 is shown.

[0170] The activation of the discard rule is configured by the gNB-CU (e.g. PDCP layer configuration) during modification. For example Fig.14 as shown).

[0171] Step S200: WD 22 is receiving XR PDCP packets from the network (eg, network node 16).

[0172] Step S202: The network node 16a (e.g., gNB-CU), i.e., the entity processing the PDCP layer, decides whether to use (i.e., determine) the discard rule configuration, which may be provided via RRC.

[0173] Step S204: Once the network node 16a (e.g., gNB-CU) configures the WD 22 to discard PDCP packets, the network node 16a (e.g., gNB-CU) will send a discard activation request to the network node 16b (e.g., gNB-DU) to discard these packets. The activation by the network node 16b (e.g., gNB-DU) can be via a new DCI or MAC CE. The activation can also be indicated explicitly or implicitly in the RRC message used to configure the function in the WD 22.

[0174] The activation may also be signaled via the Xn interface to another entity having an RLC layer, for example in the case of an SN terminated bearer.

[0175] Step S206: In case the discard rule is successfully activated, the network node 16b (e.g., gNB-DU) or other entity where the RLC layer is located may reply to the network node 16a (e.g., gNB-CU) or the entity where the PDCP layer is located. The reply may include the result of the operation (i.e., activation and / or deactivation).

[0176] Step S208: WD 22 may follow the indicated discarding rule (ie, perform one or more operations, such as receiving / sending, based on the indicated discarding rule).

[0177] Steps S210-S214: In case of UL transmission, the network node 16a (eg, gNB-CU) configures the WD 22 by including rules to discard PDCP / RLC packets that are too late. Steps S204 and / or S206 for activation or deactivation (and / or any other steps) may be repeated.

[0178] Note 1: The F1 WD Context Setup procedure may be used as an alternative to (and / or in conjunction with) the WD Context Modification procedure. The network node 16a (e.g., gNB-CU) may signal the discarding rules and / or activation status during the setup procedure.

[0179] Note 2: The above steps may be implemented (ie, executed) in the RRC_INACTIVE state (eg, during small data transmission of the WD 22).

[0180] NOTE 3: Step S204 may be repeated to signal a discard deactivation information element (IE) to the network node 16b (e.g., gNB-DU) to deactivate the discard rules and / or update the WD behavior (i.e., configuration).

[0181] Non-limiting example where the discard activation is configured by the gNB-DU (e.g. RLC configuration) Fig.15 shown)

[0182] Step S300: WD 22 is receiving XR PDCP packets from the network.

[0183] Step S302: The node hosting the PDCP entity (i.e., the network node 16b) queries the network node 16a (e.g., the gNB-DU) to configure the discarding rules. This step may also be performed by signaling to another entity having an RLC layer over Xn, such as in the case of SN terminated bearers.

[0184] Step S304: The network node 16a (e.g., gNB-DU) decides whether to use (i.e., determine) the discard rule configuration provided by the MAC / PHY layer.

[0185] Step S306: If the network node 16a (e.g., gNB-DU) has configured the discarding rule, the network node 16a (e.g., gNB-DU) or other entity where the RLC layer is located will reply the discarding configuration to the network node 16a (e.g., gNB-DU) and / or the entity where the PDCP layer is located. In the case of F1, the discarding configuration can be transmitted as an octet string in the DU to CU RRC information.

[0186] Step S308: Once the discard rule configuration is received via F1 or Xn, the PDCP entity will decide (i.e. determine) the action: activate / deactivate. The PDCP entity may send an indication corresponding to the selected action to the network node 16a (gNB-DU).

[0187] Step S310: If the activation is performed by the network node 16a (e.g., gNB-DU), the activation (i.e., activation request) may be sent via a new DCI or MAC CE.

[0188] Step S312: WD 22 may follow the indicated discarding rules.

[0189] Steps S314-S318: In case of UL transmission, the network node 16a (e.g., gNB-DU) configures the WD 22 by including rules for discarding PDCP / RLC packets (e.g., discarding late packets) and / or signals the configuration to the network node 16b (e.g., gNB-CU).

[0190] Note 1: The F1 WD context setup procedure may be used instead of (or in conjunction with) the WD context modification procedure.

[0191] Note 2: The above steps may be implemented (ie, executed) in the RRC_INACTIVE state (eg, during small data transmission of the WD 22).

[0192] In another embodiment, the discard rule configuration information may be signaled between two network nodes and / or entities of the network node 16 (e.g., gNB-CU-UP (user plane) and gNB-CU-CP (control plane)) via an E1P interface.

[0193] The following is a non-limiting list of example embodiments:

[0194] Embodiment A1 A first network node is configured to communicate with a wireless device (WD) and / or a second network node, the second network node is configured to communicate with the WD, the first network node is configured to, and / or includes a radio interface and / or a communication interface and / or includes a processing circuit, the processing circuit is configured to:

[0195] determining a configuration including at least one drop rule for dropping at least one resource associated with the data unit;

[0196] causing at least one of the WD and the second network node to be configured with a determined configuration;

[0197] sending a discard activation request to the second network node based on the determined configuration; and

[0198] A drop activation response is received, the drop activation response indicating successful activation of the at least one drop rule.

[0199] Embodiment A2 includes a first network node according to Embodiment A1, wherein the at least one resource is any one of a frame and a packet, and the data unit includes any one of a protocol data unit or a service data unit associated with extended reality signaling.

[0200] Embodiment A3 comprises a first network node according to any one of embodiments A1 and A2, wherein the sent discard activation request causes at least one of the first network node, the second network node, and the WD to discard at least one resource associated with the data unit.

[0201] Embodiment A4 The first network node according to any one of embodiments A1-A3, wherein:

[0202] The first network node is one of: a centralized unit, a packet data convergence protocol entity, and a distributed unit; and

[0203] When the first network node is one of a centralized unit and a packet data convergence protocol entity, the second network node is a distributed unit; and

[0204] When the first network node is a distributed unit, the second network node is a centralized unit.

[0205] Embodiment B1 A method implemented in a first network node, the first network node being configured to communicate with a wireless device (WD) and / or a second network node, the second network node being configured to communicate with the WD, the method comprising:

[0206] determining a configuration including at least one drop rule for dropping at least one resource associated with the data unit;

[0207] causing at least one of the WD and the second network node to be configured with a determined configuration;

[0208] sending a discard activation request to the second network node according to the determined configuration; and

[0209] A drop activation response is received, the drop activation response indicating successful activation of the at least one drop rule.

[0210] Embodiment B2 The method of embodiment B1, wherein the at least one resource is any one of a frame and a packet, and the data unit comprises any one of a protocol data unit or a service data unit associated with extended reality signaling.

[0211] Embodiment B3 The method of any one of Embodiments B1 and B2, wherein the sent discard activation request causes at least one of the first network node, the second network node, and the WD to discard at least one resource associated with the data unit.

[0212] Embodiment B4 The method according to any one of Embodiments B1-B3, wherein:

[0213] The first network node is one of: a centralized unit, a packet data convergence protocol entity, and a distributed unit; and

[0214] When the first network node is one of a centralized unit and a packet data convergence protocol entity, the second network node is a distributed unit; and

[0215] When the first network node is a distributed unit, the second network node is a centralized unit.

[0216] Embodiment C1 A wireless device WD is configured to communicate with at least one of a first network node and a second network node, the wireless device is configured to, and / or includes a radio interface and / or a processing circuit, the processing circuit is configured to:

[0217] receiving a configuration including at least one drop rule for dropping at least one resource associated with a data unit; and

[0218] Signaling is sent based on the received configuration and / or a discard activation request sent to the second network node.

[0219] Embodiment C2 The WD of embodiment C1, wherein the at least one resource is any one of a frame and a packet, and the data unit comprises any one of a protocol data unit or a service data unit associated with extended reality signaling.

[0220] Embodiment C3 The WD according to any one of embodiments C1 and C2, wherein the sent discard activation request causes at least one of the first network node, the second network node, and the WD to discard at least one resource associated with the data unit.

[0221] Embodiment C4 The WD according to any one of Embodiments C1-C3, wherein:

[0222] The first network node is one of: a centralized unit, a packet data convergence protocol entity, and a distributed unit; and

[0223] When the first network node is one of a centralized unit and a packet data convergence protocol entity, the second network node is a distributed unit; and

[0224] When the first network node is a distributed unit, the second network node is a centralized unit.

[0225] Embodiment D1 A method implemented in a wireless device (WD), the WD configured to communicate with at least one of a first network node and a second network node, the method comprising:

[0226] receiving a configuration including at least one drop rule for dropping at least one resource associated with a data unit; and

[0227] Signaling is sent based on the received configuration and / or a discard activation request sent to the second network node.

[0228] Embodiment D2 The method of embodiment D1, wherein the at least one resource is any one of a frame and a packet, and the data unit comprises any one of a protocol data unit or a service data unit associated with extended reality signaling.

[0229] Embodiment D3 A method according to any one of embodiments D1 and D2, wherein the sent discard activation request causes at least one of the first network node, the second network node, and the WD to discard at least one resource associated with the data unit.

[0230] Embodiment D4 The method according to any one of embodiments D1-D3, wherein:

[0231] The first network node is one of: a centralized unit, a packet data convergence protocol entity, and a distributed unit; and

[0232] When the first network node is one of a centralized unit and a packet data convergence protocol entity, the second network node is a distributed unit; and

[0233] When the first network node is a distributed unit, the second network node is a centralized unit.

[0234] As will be appreciated by those skilled in the art: the concepts described herein may be embodied as methods, data processing systems, computer program products, and / or computer storage media storing executable computer programs. Thus, the concepts described herein may take the form of an all-hardware embodiment, an all-software embodiment, or an embodiment combining hardware and software aspects, all of which are collectively referred to herein as "circuits" or "modules". Any process, step, action, and / or function described herein may be performed by and / or associated with a corresponding module, which may be implemented in software and / or firmware and / or hardware. In addition, the present disclosure may take the form of a computer program product on a tangible computer-usable storage medium having computer program code contained in the medium that can be executed by a computer. Any suitable tangible computer-readable medium may be utilized, including a hard disk, a CD-ROM, an electrical storage device, an optical storage device, or a magnetic storage device.

[0235] Some embodiments are described herein with reference to flowchart illustrations and / or block diagrams of methods, systems, and computer program products. It should be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of multiple blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a general-purpose computer (thereby creating a special-purpose computer), a processor of a special-purpose computer, or other programmable data processing device used to produce a machine, so that the instructions (executed via the processor of the computer or other programmable data processing device) create a program for implementing the flowchart and / or block diagrams. Figure 1 means for performing the functions / actions specified in one or more blocks.

[0236] These computer program instructions may also be stored in a computer-readable memory or storage medium that instructs a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory generate instructions including implementing the flowcharts and / or block diagrams. Figure 1 An article of manufacture that is an instruction means for performing the functions / actions specified in one or more blocks.

[0237] The computer program instructions may also be loaded into a computer or other programmable data processing device to cause a series of operable steps to be executed on the computer or other programmable device to generate a computer-implemented process, so that the instructions executed on the computer or other programmable device provide for implementing the flowchart and / or block diagram. Figure 1 The steps of the functions / actions specified in one or more boxes.

[0238] It should be understood that the functions and / or actions marked in the blocks may not occur in the order marked in the operating instructions. For example, depending on the functions / actions involved, two blocks shown in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in the opposite order. Although some figures include arrows on the communication paths to indicate the primary direction of communication, it will be understood that communication may occur in the opposite direction of the indicated arrows.

[0239] The computer program code for performing the operations of the concepts described herein can be written in an object-oriented programming language such as Python, Java® or C++. However, the computer program code for performing the operations of the present disclosure can also be written in a conventional procedural programming language such as the "C" programming language. The program code can be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer. In the latter scenario, the remote computer can be connected to the user's computer via a local area network (LAN) or a wide area network (WAN), or an external computer can be connected (e.g., using an Internet service provider to connect via the Internet).

[0240] In conjunction with the above description and the accompanying drawings, many different embodiments are disclosed herein. It will be understood that it would be unduly repetitive and confusing to describe and illustrate verbatim every combination and subcombination of these embodiments. Therefore, all embodiments may be combined in any manner and / or combination, and this specification including the accompanying drawings will be construed to construct a complete written description of all combinations and subcombinations of the embodiments described herein and the manner and process of making and using them, and will support the rights and interests claiming any such combination or subcombination.

[0241] Abbreviations that may be used in the preceding description include:

[0242] ADU Application Data Unit

[0243] AR Augmented Reality

[0244] ARP Allocation and Retention Priority

[0245] AS Access Layer

[0246] CQI Channel Quality Indicator

[0247] DL Downlink

[0248] DRB Data Radio Bearer

[0249] eMBB Enhanced Mobile Broadband

[0250] Fps Frames per second

[0251] GTP-U General Packet Radio System Tunneling Protocol User Plane

[0252] IP Internet Protocol

[0253] LCG Logical Channel Group

[0254] LCID Logical Channel Identifier

[0255] MAC Media Access Control

[0256] mMTC massive machine type communication

[0257] MR Mixed Reality

[0258] NAS Non-Access Stratum

[0259] NR New Radio

[0260] PDB Packet Delay Budget

[0261] PDCP Packet Data Convergence Protocol

[0262] PDR Group Detection Rules

[0263] PDU Protocol Data Unit

[0264] PDU Protocol Data Unit

[0265] QFIQoS Flow ID

[0266] QoS Quality of Service

[0267] RAN Radio Access Network

[0268] RLC Radio Link Control

[0269] SDAP Service Data Adaptation Protocol

[0270] SDU Service Data Unit

[0271] SMF session management functions

[0272] TB Transfer Block

[0273] TTI Transmission Time Interval

[0274] UL Uplink

[0275] UPF User Plane Function

[0276] URLLC Ultra-Reliable Low Latency Communications

[0277] VoIP

[0278] VR Virtual Reality

[0279] xR Extended Radio / Reality

[0280] Those skilled in the art will recognize that the embodiments described herein are not limited to what has been specifically shown and described above. In addition, unless otherwise mentioned above, it should be noted that all drawings are not drawn to scale. Various modifications and changes in view of the above teachings are possible without departing from the scope of the appended claims.

Claims

1. A first network node (16a) configured to communicate with a wireless device WD (22) and a second network node (16b), the first network node (16a) comprising a processing circuit (68), the processing circuit (68) being configured to: determining a configuration including one or more drop rules for dropping one or more resources associated with the data unit; causing one or both of the second network node (16b) and the WD (22) to be configured with the determined configuration; and Based on the determined configuration, a discard activation request is sent to one or both of the second network node (16b) and the WD (22), wherein the discard activation request requests one or both of the second network node (16b) and the WD (22) to activate the one or more discard rules.

2. The first network node (16a) according to claim 1, wherein the one or more resources comprise any of frames and packets.

3. The first network node (16a) according to claim 2, wherein the frame is one of a B frame, a P frame and an I frame.

4. The first network node (16a) according to any one of claims 2 and 3, wherein the frame has a protocol data unit set tag, and at least one of the one or more discarding rules can be used for PDU set level discarding based on the protocol data unit set tag, when the at least one rule capable of PDU set level discarding is activated, the frame and at least one other frame having the same protocol data unit set tag are discarded.

5. The first network node (16a) according to any one of claims 1-4, wherein the data unit comprises any one of a protocol data unit, a service data unit, and a protocol data unit set.

6. The first network node (16a) according to any of claims 1-5, wherein the one or more drop rules are based on an importance level associated with one or both of the resource and the data unit.

7. The first network node (16a) according to any of claims 1-6, wherein the activated one or more drop rules trigger one or both of the second network node (16b) and the WD (22) to drop the one or more resources associated with the data unit.

8. The first network node (16a) according to any one of claims 1 to 7, wherein the processing circuit (68) is further configured to: A discard deactivation request is caused to be sent to one or both of the second network node (16b) and the WD (22), the discard deactivation request requesting one or both of the second network node (16b) and the WD (22) to deactivate the one or more discard rules.

9. The first network node (16a) of claim 8, wherein the deactivated one or more drop rules trigger one or both of the second network node (16b) and the WD (22) to refrain from dropping the one or more resources associated with the data unit.

10. The first network node (16a) according to any one of claims 1-9, wherein one or more of the following: The first network node (16a) comprises one of a centralized unit, a packet data convergence protocol entity, and a distributed unit; The second network node (16b) comprises one of the following: a distributed unit when the first network node (16a) is one of the centralized unit and the packet data convergence protocol entity; and a centralized unit when the first network node (16a) is a distributed unit; and One or both of the one or more resources and the data unit are associated with augmented reality signaling.

11. A method in a first network node (16a), the first network node (16a) being configured to communicate with a wireless device WD (22) and a second network node (16b), the method comprising: determining ( S146 ) a configuration including one or more discarding rules for discarding one or more resources associated with the data unit; causing (S148) one or both of the second network node (16b) and the WD (22) to be configured with the determined configuration; and Based on the determined configuration, a discard activation request is sent (S150) to one or both of the second network node (16b) and the WD (22), the discard activation request requesting one or both of the second network node (16b) and the WD (22) to activate the one or more discard rules.

12. The method of claim 11, wherein the one or more resources include any of frames and packets.

13. The method of claim 12, wherein the frame is one of a B frame, a P frame, and an I frame.

14. The method according to any one of claims 12 and 13, wherein the frame has a protocol data unit set tag, and at least one of the one or more discard rules can be used for PDU set level discard based on the protocol data unit set tag, and when the at least one rule that can be used for PDU set level discard is activated, the frame and at least one other frame with the same protocol data unit set tag are discarded.

15. The method according to any one of claims 11-14, wherein the data unit comprises any one of a protocol data unit, a service data unit, and a protocol data unit set.

16. The method of any of claims 11-15, wherein the one or more drop rules are based on an importance level associated with one or both of the resource and the data unit.

17. The method according to any of claims 11-16, wherein the activated one or more drop rules trigger one or both of the second network node (16b) and the WD (22) to drop the one or more resources associated with the data unit.

18. The method according to any one of claims 11 to 17, wherein: The method further comprises: A discard deactivation request is sent to one or both of the second network node (16b) and the WD (22), the discard deactivation request requesting one or both of the second network node (16b) and the WD (22) to deactivate the one or more discard rules.

19. The method of claim 18, wherein the deactivated one or more drop rules trigger one or both of the second network node (16b) and the WD (22) to refrain from dropping the one or more resources associated with the data unit.

20. The method according to any one of claims 11 to 19, wherein one or more of the following: The first network node (16a) comprises one of a centralized unit, a packet data convergence protocol entity, and a distributed unit; The second network node (16b) comprises one of the following: a distributed unit when said first network node (16a) is one of a centralized unit and a packet data convergence protocol entity; and a centralized unit when the first network node (16a) is a distributed unit; and One or both of the one or more resources and the data unit are associated with augmented reality signaling.

21. A wireless device WD (22) configured to communicate with a first network node (16a) and a second network node (16b), the WD (22) comprising a processing circuit (84), the processing circuit (84) being configured to: receiving a configuration including one or more drop rules for dropping one or more resources associated with a data unit; receiving a drop activation request associated with the received configuration, the drop activation request requesting one or both of the second network node (16b) and the WD (22) to activate the one or more drop rules; and Based on the discard activation request and the received configuration, the one or more resources associated with the data unit are discarded.

22. The WD (22) of claim 21, wherein the one or more resources include any of frames and packets.

23. The WD (22) of claim 22, wherein the frame is one of a B-frame, a P-frame, and an I-frame.

24. The WD (22) according to any one of claims 21 and 23, wherein the frame has a protocol data unit set tag, at least one rule of the one or more discard rules can be used for PDU set level discard based on the protocol data unit set tag, and the method further comprises: When the at least one rule enabled for PDU set level discarding is activated, the frame and at least one other frame having the same protocol data unit set tag are discarded.

25. The WD (22) according to any one of claims 21-24, wherein the data unit comprises any one of a protocol data unit, a service data unit, and a set of protocol data units.

26. The WD (22) according to any one of claims 21-25, wherein the one or more drop rules are based on an importance level associated with one or both of the resource and the data unit.

27. The WD (22) according to any one of claims 21 to 26, wherein: The processing circuit (84) is further configured to: The one or more drop rules are activated based on the drop activation request, and the activated one or more drop rules trigger the WD (22) to drop the one or more resources associated with the data unit.

28. The WD (22) according to any one of claims 21-27, wherein The processing circuit (84) is further configured to: A discard deactivation request is received, the discard deactivation request requesting one or both of the second network node (16b) and the WD (22) to deactivate the one or more discard rules.

29. The WD (22) of claim 28, wherein the deactivated one or more drop rules trigger the WD (22) to refrain from dropping the one or more resources associated with the data unit.

30. The WD (22) according to any one of claims 21-29, wherein one or more of the following: The first network node (16a) comprises one of a centralized unit, a packet data convergence protocol entity, and a distributed unit; The second network node (16b) comprises one of the following: a distributed unit when the first network node (16a) is one of a centralized unit and a packet data convergence protocol entity; and a centralized unit when the first network node (16a) is a distributed unit; and One or both of the one or more resources and the data unit are associated with augmented reality signaling.

31. A method in a wireless device WD (22), the WD (22) being configured to communicate with a first network node (16a) and a second network node (16b), the method comprising: receiving ( S152 ) a configuration including one or more discarding rules for discarding one or more resources associated with a data unit; receiving (S154) a discard activation request associated with the received configuration, the discard activation request requesting one or both of the second network node (16b) and the WD (22) to activate the one or more discard rules; and Based on the discard activation request and the received configuration, one or more resources associated with the data unit are discarded (S156).

32. The method of claim 31, wherein the one or more resources comprise any of frames and packets.

33. The method of claim 32, wherein the frame is one of a B frame, a P frame, and an I frame.

34. The method according to any one of claims 31 and 33, wherein the frame has a protocol data unit set tag, at least one of the one or more discard rules can be used for PDU set level discard based on the protocol data unit set tag, and the method further comprises: When the at least one rule enabled for PDU set level discarding is activated, the frame and at least one other frame having the same protocol data unit set tag are discarded.

35. The method according to any one of claims 31-34, wherein the data unit comprises any one of a protocol data unit, a service data unit, and a protocol data unit set.

36. The method of any of claims 31-35, wherein the one or more drop rules are based on an importance level associated with one or both of the resource and the data unit.

37. The method according to any one of claims 31 to 36, wherein: The method further comprises: The one or more drop rules are activated based on the drop activation request, and the activated one or more drop rules trigger the WD (22) to drop the one or more resources associated with the data unit.

38. The method according to any one of claims 31 to 37, wherein: The method further comprises: A discard deactivation request is received, the discard deactivation request requesting one or both of the second network node (16b) and the WD (22) to deactivate the one or more discard rules.

39. The method of claim 38, wherein the deactivated one or more drop rules trigger the WD (22) to refrain from dropping the one or more resources associated with the data unit.

40. The method of any one of claims 31-39, wherein one or more of the following: The first network node (16a) comprises one of a centralized unit, a packet data convergence protocol entity, and a distributed unit; The second network node (16b) comprises one of the following: a distributed unit when the first network node (16a) is one of a centralized unit and a packet data convergence protocol entity; and a centralized unit when the first network node (16a) is a distributed unit; and One or both of the one or more resources and the data unit are associated with augmented reality signaling.

Images