Methods, apparatus, and computer readable media related to low latency services in wireless networks
By deploying congestion detection algorithm and marking probability function in the gNB (CU/DU) separation architecture of the radio network, the congestion indicator is transmitted using the F1 interface, the problem of missing uplink L4S design in the radio network is solved, and delay sensitivity is achieved Low latency and high reliability of service.
Patent Information
- Application Number
- CN202411238474.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2021-09-24
- Filing Date
- 2022-09-23
- Publication Date
- 2024-11-26
AI Technical Summary
There is a lack of effective rate adaptation methods in existing radio access networks, especially in high-level separation architectures, where the design of uplink L4S lacks a clear solution, resulting in low latency peak and congestion control efficiency.
In the gNB (CU/DU) separation architecture, by deploying congestion detection algorithm and marking probability function in the DU or CU, the congestion indicator is transmitted using the F1 interface to realize congestion detection and marking of the uplink, ensuring that the packet rate is appropriate , reduce delay and delay jitter.
Effective congestion control of the uplink in the radio network is realized, and the service quality is improved, especially under the high-level separation architecture, ensuring low latency and high reliability for latency-sensitive services.
Smart Images

Figure CN119030927A_ABST
Abstract
Description
[0001] This application is a divisional application of the Chinese patent application "Methods, devices and computer-readable media related to low-latency services in wireless networks" with application number 202280064248.7 (filing date September 23, 2022). Technical Field
[0002] Embodiments of the present disclosure relate to wireless networks, and in particular, to methods, apparatus, and computer-readable media related to congestion in wireless networks. Background Art
[0003] Today, typical wireless networks supporting 4G and earlier versions are optimized primarily for mobile broadband (MBB) and voice services. MBB services can be very throughput demanding, but are generally insensitive to latency. For example, non-real-time streaming services handle long delays by using large buffers, which effectively hides delay jitter in the network, still resulting in a good end-user experience. In later versions of 4G, but especially in 5G, other types of services have come into focus. Examples of these new services are Ultra-Reliable Low Latency Communication (URLLC) services (typically targeted at industrial applications) and gaming services. Within 3GPP standardization, features are being developed to support these new URLLC services and use cases.
[0004] Remote driving is a latency-sensitive use case, but gaming is probably a more common example of an application, including multi-user gaming, augmented reality (AR), virtual reality (VR), games with and without rendering, etc. In order to meet the end-user quality of experience for these applications, the end-to-end (E2E) latency must be considered, that is, in addition to providing low latency through the radio access network (RAN), the latency through the core network (CN) and all the way to the application server and / or client needs to be considered. With edge cloud deployment of applications, the impact of latency from the CN and between the network and the application can be reduced.
[0005] Another quality of service (QoS) aspect to consider for delay-sensitive services is reliability, which is measured as the probability of delivering the traffic within a specified duration (i.e., meeting the delay requirement). Reliability is closely related to the delay requirement, because in the absence of a delay requirement, the traffic can always be delivered by using enough retransmissions. Therefore, reliability is a very important criterion when tuning the network for delay-sensitive traffic.
[0006] When a specific QoS level is to be ensured for a given service, an additional parameter to consider is the availability of resources. Ensuring that resources are available when the service requires them will ensure timely data exchange and reduce the number of failures for a given bearer communication process.
[0007] E2E congestion control and active queue management
[0008] E2E congestion control allows nodes involved in a traffic path to signal congestion to the source. Signaling can be explicit or implicit, for example by dropping packets. The source detects congestion signaling and then adapts its rate to the weakest link. Active queue management (AQM) is often used in combination with E2E rate adaptation to reduce delay jitter in long-term transmissions caused by bursty sources. An example of E2E congestion control and AQM is low latency, low loss, scalable throughput (L4S) described in the next section. L4S uses explicit congestion notification signaling together with an active queue management algorithm and is used within the present disclosure to illustrate the solution. Those skilled in the art will appreciate that the concepts described herein are equally applicable to other congestion notification mechanisms.
[0009] Low latency, low loss, scalable throughput (L4S)
[0010] One way to manage latency (particularly queuing latency) in E2E data flows is to use L4S (see Internet Draft: Low Latency, Low Loss, Scalable Throughput (L4S) Internet Service: Architecture, https: / / tools.ietf.org / id / draft-ietf-tsvwg-l4s-arch-06.html). If congestion is experienced, any node serving a data flow with L4S capabilities can set an explicit congestion notification (ECN) bit in the IP header of the flow. The receiving client collects congestion / ECN statistics and feeds them back to the corresponding server. Based on the reported congestion information, the server application adapts its data rate to maintain low queuing latency and short E2E latency. Therefore, congestion indications are set in the forward direction, collected by the client and sent to the server in the feedback protocol.
[0011] When queue delays are very low, packets are marked as "congested", which reacts quickly to even the slightest sign of congestion, allowing end hosts to implement scalable congestion control, where the transmission rate (or congestion window) changes in proportion to the fraction of packets that are marked as congested. See also Figure 1 , which shows the overall principle.
[0012] L4S enables real-time critical data applications to adapt their rate to the weakest link, minimizing the latency impact due to queue build up. The latest L4S is typically triggered by a threshold in the input queue of a transmission node and can be used to signal congestion situations. Given that most transmission nodes have fairly stable or slowly varying output rates, it provides good results. However, for radio networks, the output rate changes on wireless links may be more frequent than traditional wired solutions, which can lead to sudden latency spikes, even when using L4S.
[0013] High-Level Partitioning in RAN
[0014] In the 5G standard, a gNB may be divided into a central unit (CU) and one or more distributed units (DUs), which are communicatively coupled to each other via an F1 interface, such as Figure 2 As shown in (extracted from 3GPP TS 38.401v16.6.0).
[0015] The F1 interface means that the PDCP function is located in the CU, while the RLC and lower layer functions (eg, MAC and PHY layers) are located in the DU.
[0016] Figure 3 The user plane protocol stack between RAN and UE is shown. In the gNB CU-DU split architecture, the responsibilities of the RAN-UE protocol stack are divided between CU and DU, where the high layers (SDAP and PDCP) terminate in the CU and the remaining low layers (RLC, MAC, PHY) terminate in the DU. Figure 4 The UE is not aware of the intra-gNB CU-DU split, which means that the RAN-UE procedures are the same regardless of the gNB internal architecture.
[0017] Distributed termination of the RAN-UE protocol layer is implemented by the F1 interface, which provides a method for transferring NR PDCP PDUs between the CU and DU for the user plane. Depending on the distance between the CU and DU placement, the transmission delay can be added to the gNB processing delay.
[0018] User plane protocol used on F1-U, Xn-U, and X2-U
[0019] In 3GPP TS 38.425 v16.3.0, the UP protocol for F1-U, Xn-U and X2-U interfaces is described. In this specification, the following two types of PDUs are shown: Downlink Data Delivery Status (DDDS) (PDU Type 1) and Assistance Information (PDU Type 2).
[0020] PDU type 1 has been defined to enable a node hosting a lower layer (e.g. RLC) to convey information about DL traffic flows to a node hosting PDCP. In addition, this PDU type can be used to signal a radio link outage or radio link recovery of the associated data radio bearer to a node hosting PDCP.
[0021] PDU Type 2 has been introduced to allow nodes hosting lower layers (e.g. RLC) to transmit information that can help nodes hosting PDCP to better manage the configuration of radio bearers. As an example, the assistance information can have different types, as described below with the help of the value range of the assistance information type field. It can be seen that the assistance information provides information about the radio channel used for the DRB.
[0022] The value range of the auxiliary information type is as follows: {0=Unknown, 1=Average CQI, 2=Average HARQ failure, 3=Average HARQ retransmission, 4=DL Radio Quality Index, 5=UL Radio Quality Index, 6=Power Headroom Report, 7-228=Reserved for future value extension, 229-255=Reserved for testing purposes}.
[0023] The remainder of this section is copied from 3GPP TS 38.425v16.3.0.
[0024] ++++++++Start of text from 3GPP TS 38.425v16.3.0++++++++++
[0025] 5.5.2.2DL data transmission status (PDU type 1)
[0026] This frame format is defined to transmit feedback to allow a receiving node (ie, a node hosting an NRPDCP entity) to control downlink user data flow via a sending node (ie, a corresponding node).
[0027] The corresponding DL data transfer status frame is shown below. Table 1 shows an example of how the frame is constructed when all optional IEs (ie IEs whose presence is indicated by an associated flag) are present.
[0028] The absence of such an IE changes the position of all subsequent IEs on the octet level.
[0029]
[0030]
[0031] Table 1: DL data transfer status (PDU type 1) format
[0032] 5.5.2.3 Auxiliary Information Data (PDU Type 2)
[0033] This frame format is defined to allow a node hosting an NR PDCP entity to receive assistance information.
[0034] The following table shows the corresponding auxiliary information data frame.
[0035]
[0036] ++++++++End of text from 3GPP TS 38.425v16.3.0++++++++++
[0037] There are certain challenges currently. When used in a radio access network such as NR, efficient rate adaptation for high-rate time-critical services is required, which is essential to achieve a good quality of experience. Existing and earlier RAN technologies do not include this possibility.
[0038] The major part of gNB processing latency comes from the radio interface and the related scheduling. However, in a gNB split architecture, the functionality and responsibilities need to be distributed between the nodes and the necessary interface modifications need to be defined. Furthermore, depending on the distance between the CU and DU placement, additional CU-DU transmission latency may have to be considered. An integrated gNB L4S solution (with co-located CU-DU functionality or co-located hosted PDCP and correspondence nodes) enables a low complexity design due to the possibility of sharing data between congestion detection and congestion marking functionality. The problem is that there is currently no defined solution / design that addresses uplink L4S using a high-level split architecture.
[0039] L4S is based on the addition of information at the IP level and has been proven to be an effective way to provide network-supported rate adaptation (see Ericsson white paper "Enabling time-critical applications over 5G with rate adaptation", May 2021). In the UL direction, the IP packets are generated at the UE, and in theory the UE can be the node responsible for setting the L4S information in the IP packets sent in the UL. However, such an approach will have an impact on the availability of the L4S solution, for example, which depends on the UE's ability to support L4S. A better and more operator-controllable approach would be to enable the L4S information to be set by the network so that L4S support is independent of UE type and capabilities. Summary of the invention
[0040] Therefore, one problem addressed by embodiments of the present disclosure is how to support L4S for UL traffic in the network. Such a problem is even more pronounced in a split RAN architecture where the gNB-DU can see resource conditions (and therefore congestion) through the radio interface, while the UL IP packets are only visible at the gNB-CU-UP.
[0041] Certain aspects of the present disclosure and its embodiments can provide solutions to these or other challenges. One objective of the embodiments disclosed herein is to enable support for rate adaptation applications in a gNB (CU / DU) split architecture. Several methods are proposed on how to distribute the required functionality for uplink congestion control and the necessary interface updates in a gNB (CU / DU) split architecture. The congestion detection algorithm and the marking probability function can be deployed together in the DU or CU. There is also the option of having DU-deployed congestion detection and CU-deployed marking probability function. Note that embodiments of the present disclosure are also applicable to scenarios other than split base station architectures, such as dual-connection or multi-connection configurations (e.g., where the bearer is divided between the primary node and the secondary node).
[0042] Embodiments of the present disclosure enable UEs using specific services and / or specific subscriptions to follow instructions from the RAN to limit the impact of delays due to queue growth. Specific services may be characterized by a need for low latency and the ability to perform service rate adaptation based on notifications from the RAN.
[0043] A first aspect of the present disclosure provides a method for uplink congestion control in a radio network performed by a first network node. The first network node processes one or more first layers of a protocol stack for an uplink connection between a wireless device and the radio network, and is communicatively coupled to a second network node, which processes one or more second layers of the protocol stack for the uplink connection. The one or more second layers are lower than the one or more first layers. The method includes: obtaining an indication of a proportion of packets to be marked with a congestion indicator within an uplink user plane flow on the uplink connection, wherein the proportion is based on a delay experienced by packets of the uplink user plane flow sent by the wireless device to the second network node; marking the proportion of packets with the congestion indicator; and sending packets of the uplink user plane flow toward a core network of the radio network.
[0044] An apparatus for performing the method set forth above is also provided. For example, another aspect provides a first network node for uplink congestion control in a radio network. The first network node processes one or more first layers of a protocol stack for an uplink connection between a wireless device and the radio network, and is communicatively coupled to a second network node, which processes one or more second layers of the protocol stack for the uplink connection. The one or more second layers are lower than the one or more first layers. The first network node includes a processing circuit configured to cause the first network node to: obtain an indication of a proportion of packets within an uplink user plane flow on the uplink connection to be marked with a congestion indicator, wherein the proportion is based on a delay experienced by packets of the uplink user plane flow sent by the wireless device to the second network node; mark the proportion of packets with the congestion indicator; and send packets of the uplink user plane flow toward a core network of the radio network.
[0045] In a second aspect, the present disclosure provides a method for uplink congestion control in a radio network performed by a second network node. The second network node processes one or more second layers of a protocol stack for an uplink connection between a wireless device and the radio network, and is communicatively coupled to a first network node, the first network node processing one or more first layers of the protocol stack for the uplink connection. The one or more second layers are lower than the one or more first layers. The method includes: sending packets for an uplink user plane flow on the uplink connection to the first network node for onward transmission toward a core network node of the radio network; and sending one or more of the following to the first network node: an indication of a proportion of packets within the uplink user plane flow on the uplink connection to be marked with a congestion indicator, wherein the proportion is based on a delay experienced by packets of the uplink user plane flow sent by the wireless device to the second network node; and an indication of a delay experienced by packets of the uplink user plane flow sent by the wireless device to the second network node.
[0046] An apparatus for performing the method set forth above is also provided. For example, another aspect provides a second network node for uplink congestion control in a radio network. The second network node processes one or more second layers of a protocol stack for an uplink connection between a wireless device and the radio network, and is communicatively coupled to a first network node, the first network node processing one or more first layers of the protocol stack for the uplink connection. The one or more second layers are lower than the one or more first layers. The second network node includes a processing circuit configured to cause the second network node to: send packets for an uplink user plane flow on the uplink connection to the first network node for onward transmission toward a core network node of the radio network; and send one or more of the following to the first network node: an indication of a proportion of packets within the uplink user plane flow on the uplink connection to be marked with a congestion indicator, wherein the proportion is based on a delay experienced by packets of the uplink user plane flow sent by the wireless device to the second network node; and an indication of a delay experienced by packets of the uplink user plane flow sent by the wireless device to the second network node.
[0047] Certain embodiments can provide one or more of the following technical advantages. One advantage of the embodiments disclosed herein is that it ensures an efficient way to deploy uplink congestion detection for network-supported rate adaptation (e.g., L4S) in a high-layer split architecture defined in NR. This will achieve good QoE for high-rate, rate-adaptive services that require short latency. BRIEF DESCRIPTION OF THE DRAWINGS
[0048] For a better understanding of the embodiments of the present disclosure, and in order to show how the invention may be implemented, reference will now be made, by way of example only, to the accompanying drawings, in which:
[0049] Figure 1 An overview diagram showing the functionality of low latency, low loss, scalable throughput (L4S);
[0050] Figure 2 shows a high-level partitioning in the Next Generation Radio Access Network (NG-RAN);
[0051] Figure 3 The user plane protocol stack for user equipment (UE) and gNodeB (gNB) is shown;
[0052] Figure 4 shows the distribution of protocol layers for gNB;
[0053] Figure 5 The implementation of L4S functions in a network node or base station is shown;
[0054] Figure 6 shows characteristics of a marking probability function pMark according to some embodiments;
[0055] Figure 7 illustrates an implementation of L4S within a radio access network (RAN) according to some embodiments;
[0056] Figure 8-10 A gNB according to some embodiments is shown;
[0057] Fig.11 is a timeline illustrating the principles of delay measurement for a distributed unit (DU) according to some embodiments;
[0058] Fig.12 A method according to a particular embodiment is shown;
[0059] Fig.13 A method according to a particular embodiment is shown;
[0060] Fig.14 An example of a communication system according to some embodiments is shown;
[0061] Fig.15 A UE according to some embodiments is shown;
[0062] Fig.16 illustrates a network node according to some embodiments;
[0063] Fig.17 is a block diagram of a host according to some embodiments;
[0064] Fig.18 is a block diagram illustrating a virtualized environment according to some embodiments; and
[0065] Fig.19 A communication diagram of a host according to some embodiments is shown. DETAILED DESCRIPTION
[0066] Some embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. The embodiments are provided as examples to convey the scope of the subject matter to those skilled in the art. Although described in the context of a distributed base station, for example, where the base station is divided into a centralized unit (CU) (the CU itself can be divided into a control plane (CP) unit and a user plane (UP) unit) and one or more distributed units (DUs), the present disclosure provides methods and apparatus that can be applied to any use case in which the user plane protocol described in TS38.425v16.3.0 is used. That is, the use cases covered are use cases in which nodes hosting low layers and nodes hosting PDCP protocols communicate with each other by means of Xn-U, X2-U, and F1-U interfaces or via any other interface after TS38.425v16.3.0.
[0067] For example, this may occur when the wireless device is configured with dual or multiple connections. In these cases, the wireless device is configured with connections to multiple base stations (primary nodes (e.g., MeNB, MgNB, etc.) and one or more secondary nodes (e.g., SeNB, SgNB, etc.)). The radio bearer can be divided between the primary node and the secondary node so that the lower layer (e.g., RLC, MAC and / or PHY) of the protocol stack for the connection / bearer is hosted at the secondary node, while the higher layer (e.g., PDCP, IP, etc.) is hosted at the primary node. Therefore, the embodiments of the present disclosure are also applicable to these scenarios. In the present disclosure, unless otherwise specified, the term "first network node" refers to a network node or base station that hosts the upper layer of the protocol stack for the connection between the wireless device (e.g., UE) and the radio network. Examples of the first network node include a centralized unit (e.g., CU-UP) of a distributed base station, and a primary node for a wireless device configured with dual or multiple connections. The term "second network node" refers to a network node or base station that hosts the lower layer of the protocol stack for the connection between the wireless device (e.g., UE) and the radio network. Examples of the second network node include a distributed unit (DU) of a distributed base station, and a secondary node for a wireless device configured with dual connectivity or multiple connectivity.
[0068] Figure 5 The implementation of L4S functions within a network node or base station (e.g., gNB or eNB) is shown. The core functions of L4S functions are listed below:
[0069] Packet Marking marks IP packets as Congestion Experienced (CE) as specified in the L4S Internet-Draft (described above). It uses the output from PMark to identify the proportion of packets to be marked. This function has deployment constraints, namely, to be located at a location in the IP packet header that can access the application data flow, which implies allocation at the PDCP entity.
[0070] The Congestion Detection Algorithm (CDA) detects congestion and congestion levels in the data flow, and estimates whether the (queue) delay target cannot be met, and whether there is a deviation and to what extent.
[0071] PMark, marking, computes the score of packets to be marked as CE based on information from CDA.
[0072]
[0073] Figure 6 The characteristics of the pMark function according to one embodiment of the present disclosure are shown. Those skilled in the art will understand that Figure 6 Only one possible implementation of the pMark function is shown, and other pMark functions are possible within the scope of the appended claims and / or embodiments. For example, Figure 6 The values of Th are shown for the low and high thresholds (respectively Th low and Th high ), the pMark function varies linearly between low and high values (e.g., 0 and 1, respectively) for delay times between the low threshold and the high threshold. At delay times below the low threshold, the pMark function may have a low value; at delay times above the high threshold, the pMark function may have a high value. Alternatively, the pMark function may vary nonlinearly; for example, the pMark function may vary in quantized steps as the time delay varies; the pMark function may vary as a curve or other function of the time delay experienced by the connected data packets. Other examples will naturally occur to those skilled in the art, and the embodiments of the present disclosure are not limited in this respect.
[0074] Figure 7 The implementation of L4S within the RAN according to an embodiment of the present disclosure is shown. The gNB (which is responsible for scheduling the UE) can estimate the UE output queue based on the buffer status report (BSR) sent by the UE. The UE output queue and other metrics (such as channel quality, cell load, etc.) can be used to calculate the level of IP packet congestion marking to be injected into the data flow towards the application client.
[0075] In a split gNB architecture (or split bearer in dual or multi-connectivity), Figure 5 The core functions in the PDCP are distributed between DUs and / or CUs (secondary network nodes and / or primary network nodes). The packet marking function can be located in the CU together with the PDCP function, but there are different options for how to distribute the CDA and PMark functions.
[0076] Figure 8An embodiment according to the present disclosure is shown, wherein the CDA and pMark functions are located in the DU, while the packet marking function is located in the CU. Thus, the DU sends an indication of the proportion of packets to be marked with a congestion indicator to the CU over the F1 interface.
[0077] Fig. 9 An embodiment according to the present disclosure is shown, where the CDA is located in the DU, while the pMark and packet marking function are located in the CU. Thus, the DU sends information about the delay experienced by packets of the uplink user plane flow to the CU over the F1 interface. The PMark function uses this information to calculate the proportion of packets to be marked with a congestion indicator, and this proportion of packets is marked by the packet marking function in the PDCP entity.
[0078] Fig.10 An embodiment according to the present disclosure is shown, in which the CDA, pMark and packet marking function are located in the CU. Therefore, the DU sends information about the CU data flow and / or the performance metrics monitored by the DU to the CU via the F1 interface. The CDA uses this information to calculate or estimate the delay experienced by, for example, packets of an uplink user plane flow. The PMark function uses this delay to calculate the proportion of packets to be marked with a congestion indicator, and this proportion of packets is marked by the packet marking function in the PDCP entity.
[0079] Above for Figure 8 , 9 The embodiments described in and 10 are respectively labeled as Cases A, B, and C. Further details about these embodiments are set forth below.
[0080] Situations A and B: CDA in DU
[0081] In both cases A and B, the gNB-DU may host a function (e.g., CDA) that determines whether the UL resources are congested. This is possible because the gNB-DU receives buffer status reports (BSRs) and also collects UL measurements that reveal the radio quality of the UL channels. The gNB-DU also knows the rate at which RLC traffic from the UE is acknowledged, and therefore it can infer whether the congestion is due to a bad radio link or due to a lack of radio resources (or both). In addition, the gNB-DU is aware of the resource utilization, such as information signaled to the gNB-CU over the F1-C interface via the RESOURCE STATUS UPDATE procedure. This information provides insight into whether potential congestion is occurring in the UL and can be used by the gNB-DU to provide instructions to the gNB-CU-UP on how to perform ECN marking.
[0082] Case A: CDA and PMark in DU, sending marking probability through F1
[0083] As described above, in case A, the CDA and PMark functions are hosted in the DU (or secondary network node). In one embodiment of the present disclosure, information providing the marking probability may be added to the 3GPP TS 34.425 Assistance Information PDU as shown below (underlined paragraphs show additions to the relevant standards).
[0084] Extract from 3GPP TS 38.425v16.3.0 Section 5.5.2.3 Auxiliary Information Data (PDU Type 2)
[0085] This frame format is defined to allow a node hosting an NR PDCP entity to receive assistance information.
[0086] Table 2 shows the corresponding ASSISTANCE INFORMATION DATA frame.
[0087]
[0088]
[0089] Table 2: Auxiliary information data (PDU type 2) format
[0090] L4S marking probability indication
[0091] Description: This field indicates the presence of L4S marking probability.
[0092] Value range: {0=L4S marking probability does not exist, 1=PDCP L4S marking probability exists}.
[0093] Field length: 1 bit.
[0094] L4S marking probability
[0095] Description: This field indicates the probability that UL IP packets should be marked with the L4S flag (i.e., ECN marking). For example, if the L4S marking probability is set to 50, the node hosting PDCP should interpret this information as a suggestion to mark 50% of the UL IP packets in egress with the L4S flag.
[0096] Value range: {0…100}.
[0097] Field length: 1 octet.
[0098] The number n of octets used for the L4S marking probability may reflect the desired marking probability resolution. In the above example, 1 octet is used to represent the L4S marking probability. However, if higher precision is desired, more octets may be allocated. Based on the L4S marking probability information received in the auxiliary information, the CU-UP determines when to start including the ECN marking in the IP header based on the received L4S marking probability value. When the CU-UP receives auxiliary information whose L4S marking probability value is different from the previously received L4S marking probability value, it may change the ECN marking accordingly. The lack of the L4S marking probability in subsequent auxiliary information may be interpreted by the CU-UP as an indication that the L4S marking probability is no longer applicable, and therefore the ECN marking should no longer be included in the IP header.
[0099] In another embodiment of the present disclosure, the information added to the above-mentioned PDU Type 2 (i.e., L4S marking probability indication and L4S marking probability) may be added to the PDU Type 1 PDU (i.e., DDDS). One advantage of this approach may be that PDU Type 1 may be received more frequently by a node hosting PDCP than PDU Type 2. Therefore, by adding L4S assistance information to this PDU type, the gNB-CU-UP may receive guidance on how to set up L4S more frequently.
[0100] In another embodiment of the present disclosure, L4S congestion indication may be included as a new event in the cause value IE included in the PDU type 1 defined in TS38.425. An example of how this new value may be included is reported below:
[0101] Extract from 3GPP TS 38.425v16.3.0 Section 5.5.3.23 Cause Values
[0102] Description: This parameter indicates the specific event reported by the corresponding node.
[0103] Value range: {0=Unknown, 1=Radio link outage, 2=Radio link recovery, 3=UL radio link outage, 4=DL radio link outage, 5=UL radio link recovery, 6=DL radio link recovery, 7=L4S congestion indication, 8-228=Reserved for future value extension, 229-255=Reserved for testing purposes}.
[0104] As an alternative solution, a congestion marking (referred to herein as L4S congestion notification) may be added to the PDU signaled from the gNB-DU to the gNB-CU, or generally to the PDU signaled from the node hosting the lower layers to the node hosting the PDCP (e.g., in the GTP-U extended header of the UL GTP-U PDU). This L4S congestion indication may be provided with each uplink PDU containing an IP packet that is determined by the implementation-specific congestion control algorithm to carry a congestion indication (e.g., in the ECN field of the IP packet). If the uplink PDU contains more than one IP packet or it contains fragments of IP packets, and if the L4S congestion notification is added to the uplink PDU (e.g., in the GTP-U extended header), the node hosting the PDCP that receives the UL PDU shall mark all corresponding IP packets with a field indicating congestion (e.g., the ECN field).
[0105] Case B: CDA in DU and PMark in CU, sending DU delay information via F1
[0106] In this embodiment of the present disclosure, the gNB-DU provides DU delay information to the gNB-CU-UP, e.g., an indication of the delay experienced by packets of uplink user plane flows. In one embodiment, the DU delay information reflects the time to "flush" the UE outgoing buffer and send data to the gNB-CU-UP, i.e., the time measured in DU from BSR reception until data is sent on F1.
[0107] use Fig.11 The timeline in Figure 1 illustrates the principle of DU delay measurement. The left side (Example A) can be described as:
[0108] 1. When the UE has data to send, the UE sends a BSR (including the data size).
[0109] 2. The gNB-DU responds with a grant indicating the data size and resources to be used in the upcoming transmission.
[0110] 3. The UE uses the granted resources to send uplink data.
[0111] 4. The gNB-DU processes the reception and sends the data to the gNB-CU via F1.
[0112] DU delay corresponds to the time from (1) to (4). Fig.11 As shown in , the UE data message may also include an updated BSR. In example (A), all data is granted and no new data arrives in the UE outgoing buffer. In example (B), multiple BSRs and UE data transmissions are required to clear the UE buffer, which means longer DU delay.
[0113] The DU Delay measurement may be included (piggybacked) with the F1 data. Alternatively, it may be sent in a separate message, for example as a new information element in the auxiliary information (i.e., PDU Type 2). The DU Delay may also be averaged and sent less frequently than the F1 data transmission. Yet another option is to use existing information elements in existing messages, but with a new interpretation, for example the UL Delay DU result in the auxiliary information (i.e., PDU Type 2) may be redefined for this purpose.
[0114] As mentioned above, the gNB-DU is aware of the cell / traffic load, resource situation and radio channel quality, and based on this information, the Congestion Detection Algorithm (CDA) can adjust the DU delay according to the current and predicted situation, which is then sent to the gNB-CU.
[0115] The PMark function in the gNB-CU uses the received DU delay information as input for the L4S marking probability calculation, e.g., as above for Figure 6 described.
[0116] Case C: CDA and PMark in CU, monitoring / analyzing CU data flow through F1 and / or F1 performance monitored by DU quantity
[0117] As mentioned above, in case C, the CDA and PMark functions are hosted in the CU (or master network node). For example, based on the channel conditions monitored in the UL, the DU sends auxiliary information to the gNB-CU signaling, which guides the UP how to set the L4S information in the UL service.
[0118] In this embodiment, the node hosting PDCP (e.g., gNB-CU-UP) may rely on information contained in PDU Type 1 and / or PDU Type 2 to infer whether the ECN marking should be set in the UL IP packet in egress. The information that the node hosting PDCP may use for this purpose may be one or more of the following:
[0119] The actual UL data flow received via the F1-U interface into the gNB-CU can be monitored and used to estimate the congestion-related delays that occur when the number of bits to be transmitted is limited by the capacity of the air / radio interface. (The reason for the limitation may be shadow fading, interference, scheduling of other users or the purpose of the application to temporarily send a large amount of data.)
[0120] UL Delay DU result included in PDU Type 2. This information may indicate to the node hosting PDCP that the delay on the Uu interface in the UL is too large and this may indicate that congestion is occurring.
[0121] Note that the gNB-CU-UP may also utilize the UL D1 Result received from the gNB-CU-CP over the F1 interface, which represents the UL delay experienced by the UE for traffic relative to a specific DRB. Such a delay measurement includes the time between the entry of a PDU into the PDCP buffer and the exit of the PDU over the air interface or radio interface. The gNB-CU-UP receives the UL D1 Result IE in the E1AP information structure shown in Appendix 1:
[0122] Assistance Information Type and Radio Quality Assistance Information included in PDU Type 2: This information may provide information about the UL channel conditions to the gNB-CU-UP. An example of such information is the UL Radio Quality Index.
[0123] Cause value included in PDU Type 1: This IE may include events that help the gNB-CU-UP determine the UL channel status, such as a UL Radio Link Outage Event Indication, which indicates that the radio link is not available for transmission in the UL, and may indicate the presence of UL congestion.
[0124] Additionally, the gNB-CU-UP may use measurements of the F1-U round trip time transmission delay to infer whether the congestion is due to F1-U resource limitations. Such RTT measurements may be obtained in different ways, such as by using a GTP-U echo function that generates a GTP-U UL PDU when a GTP-U DL PDU is received, or by using a report polling flag or an auxiliary information report polling flag that may be included in (DL) PDU type 0 and trigger immediate reporting of gNB-DUs from PDU type 1 and PDU type 2 packets. Thus, the gNB-CU-UP may calculate the RTT between sending a PDU including a polling flag and receiving the associated report, and infer the F1-U delay from this RTT.
[0125] For the use case of a split RAN architecture (where the node hosting the lower layers is the gNB-DU and the node hosting the PDCP includes the gNB-CU), i.e., where the gNB-CU-UP and gNB-CU-CP are not separated, another piece of information that the gNB-CU can use to infer whether the UL channel is congested is information received via the F1-C interface by means of a Resource Status Update message. This message contains per-cell resource information, which includes, for example, information related to the utilization of PRBs, the availability of resources in the cell, the number of active UEs in the cell, the number of RRC connections in the cell, a transport level traffic load indication, etc. The Resource Status Update message is shown in Appendix 2.
[0126] By receiving one or more of the information listed above, the node hosting the PDCP can infer the presence of a congestion situation on the UL communication channel for a particular DRB. Therefore, the node hosting the PDCP can decide to apply an ECN mark to some / all UL IP packets in the egress of the corresponding DRB service.
[0127] In one embodiment of the present disclosure, a node hosting lower layers (e.g., gNB-DU) may host functionality intended to influence how a node hosting PDCP (e.g., gNB-CU) should apply ECN marking. In such a case, the node hosting lower layers may set, adapt, or configure some of the parameters listed above to generate specific ECN markings at the node hosting PDCP. For example, some parameters may be set to values that will trigger ECN marking at the node hosting PDCP. Some of the parameters that the node hosting lower layers may set are:
[0128] Cause value in PDU Type 1: In this case, an event such as UL radio link outage may be declared for the purpose of triggering ECN marking.
[0129] Resource status update information: In this case, information such as composite available capacity and radio resource status may be set to values that allow the node hosting PDCP to determine that congestion has occurred and therefore a specific ECN marking policy needs to be applied.
[0130] Appendix 1: E1AP Information Structure
[0131] Extract from 3GPP TS 38.473v16.6.0 (F1 application protocol) Section 9.2.2.19 GNB-CU-CP Measurement Result Information This message is sent to the gNB-CU-UP to provide the measurement results received by the gNB-CU-CP.
[0132] Direction: gNB-CU-CP → gNB-CU-UP
[0133]
[0134] Appendix 2: Resource status update message:
[0135] Extract from 3GPP TS 38.473v16.6.0 (F1 Application Protocol) Section 9.2.1.23 Resource Status Update
[0136] This message is sent by the gNB-DU to the gNB-CU to report the results of the requested measurements.
[0137] Direction: gNB-DU → gNB-CU
[0138]
[0139]
[0140] Fig.12 The method 12 may be performed by a first network node in the radio network (e.g., a centralized unit (CU, CU-UP, etc.) in a distributed base station, a master node, a MeNB, a MgNB, etc., respectively, as will be described later. Fig.14 and 16 The network node 1460 or 1600 described in the example) is executed. Figures 5 to 11 In particular, for Fig.12 The described methods may correspond to the actions of the CU or master network node described above with respect to these figures.
[0141] The first network node processes one or more first layers of a protocol stack for an uplink connection between a wireless device and a radio network. For example, the first network node may host one or more of a PDCP layer and an IP layer of the protocol stack. The first network node is communicatively coupled to a second network node (e.g., a DU, a secondary node, a SeNB, a SgNB, etc.), and the second network node processes one or more second layers of a protocol stack for an uplink connection. The one or more second layers are lower than the one or more first layers. For example, the second network node may host one or more of: an RLC, a MAC, and a PHY layer of the protocol stack.
[0142] The method starts at step 1202, where a first network node receives packets from a second network node for an uplink user plane flow on an uplink connection between a wireless device and a radio network.Data Radio Bearers (DRBs) may be used to control and / or organize UL user plane flows.
[0143] In step 1204, the first network node obtains an indication of a proportion of packets within the uplink user plane flow to be marked with a congestion indicator. Note that the packets to be marked with a congestion indicator may be located at a different layer of the protocol stack than the packets received from the second network node. For example, the packets received from the second network node may be RLC PDUs. The packets to be marked with a congestion indicator may be PDCP PDUs or IP packets. The proportion is based on a delay experienced by packets of the uplink user plane flow sent (e.g., by a wireless device) to the second network node.
[0144] In step 1206, the first network node marks the proportion of packets with a congestion indicator (eg, an L4S indicator, such as an ECN field). This step may be performed within the PDCP layer in the first network node.
[0145] The packets may be marked using probabilistic techniques.For example, the indication of the proportion of packets to be marked with a congestion indicator may comprise an indication of a probability according to which the first network node marks the packets.
[0146] In step 1208, the first network node sends packets of the uplink user plane flow, including the proportion of packets marked with the congestion indicator, towards the core network of the radio network. For example, the packets may be sent to the core network over a backhaul network.
[0147] Those skilled in the art will appreciate that step 1204 may vary according to, for example, the different scenarios A, B, and C described above.
[0148] In case A, e.g., where the CDA and PMark functions are hosted in the second network node, step 1204 may include receiving an indication of a proportion of packets to be marked with a congestion indicator (e.g., in the form of a probability) from the second network node, e.g., via an F1, X2, or Xn interface. For example, as described above, the indication may be included in an assistance information (type 2) PDU or a downlink data transfer status (type 1) PDU.
[0149] In case B, for example where the CDA function is hosted in the second network node and the PMark function is hosted in the first network node, step 1204 may include calculating a proportion of packets based on the delay experienced by packets of the uplink user plane flow sent to the second network node. In this example, the first network node may receive from the second network node an indication of the delay experienced by the packets in their transmission from a wireless device (e.g., UE) to the first network node via the second network node. For example, the delay may include a delay between sending a buffer status report by the wireless device to the second network node and sending data corresponding to the buffer status report by the second network node to the first network node. Additionally or alternatively, the delay may include a delay between sending a buffer status report by the wireless device to the second network node and sending all data indicated in the buffer status report by the second network node to the first network node. The above with respect to Fig.11 Further details can be found in the description.
[0150] The indication of the delay may be piggybacked within the data of the uplink user plane flow (e.g., within the packet received in step 1202), or received in a PDU (e.g., an assistance information PDU) from the second network node. In either case, the delay value reported to the first network node may be averaged by the second network node over multiple measurement instances of the delay.
[0151] In case C, where the CDA and PMark functions are hosted in the first network node, step 1204 may also include calculating a proportion of packets based on the delay experienced by packets of the uplink user plane flow sent to the second network node. In this embodiment, instead of receiving the delay directly from the first network node, the first network node may receive information from the second network node or a third network node (e.g., a CU-CP node) so that the first network node can calculate, estimate, or infer the delay experienced by packets of the uplink user plane flow. The information received from the second network node may include one or more of the following: an uplink data flow; an uplink delay on a radio interface; one or more radio quality metrics for a connection between the wireless device and the second network node; an indication of the state of one or more uplink channels between the wireless device and the second network node; an indication of the round trip time of a transmission between the first network node and the second network node. The information received from the third network node (which may relate to resources utilized in a cell served by the second network node) may include one or more of: an indication of utilization of physical resource blocks; an indication of availability of resources in the cell; the number of active wireless devices in the cell; the number of RRC connections in the cell; and one or more transmission level traffic load indications.
[0152] In other embodiments, the first congestion indicator may be added to the PDU signaled from the second network node to the first network node. A first congestion marking (which may be provided, for example, in a GTP-U extension header of a UL GTP-U PDU) may be provided with each uplink PDU containing an IP packet determined by a congestion control algorithm (in the second network node) to carry a second congestion indicator (e.g., in an ECN field of the IP packet). If the uplink PDU contains more than one IP packet or it contains fragments of IP packets, and if the first congestion indicator is added to the uplink PDU (e.g., in a GTP-U extension header), the node hosting the PDCP that receives the UL PDU will mark all corresponding IP packets within the uplink PDU with the second congestion indicator (e.g., ECN field).
[0153] Fig.13 Method 13 may be performed by a second network node (e.g., a distributed unit (CU, CU-UP, etc.) in a distributed base station, a secondary node, a SeNB, a SgNB, etc., as will be described later. Fig.14 and 16 The network node 1460 or 1600 described in the example) is executed. Figures 5 to 11 In particular, for Fig.13The described methods may correspond to the actions of the DU or secondary network node described above with respect to these figures.
[0154] The second network node processes one or more second layers of a protocol stack for an uplink connection between the wireless device and the radio network. For example, the second network node may host one or more of the following: RLC, MAC, and PHY layers of the protocol stack. The second network node is communicatively coupled to a first network node (e.g., a CU, a master node, a MeNB, a MgNB, etc.), and the first network node processes one or more first layers of a protocol stack for an uplink connection. The one or more second layers are lower than the one or more first layers. For example, the first network node may host one or more of a PDCP layer and an IP layer of the protocol stack.
[0155] The method starts at step 1302, where a second network node sends packets for an uplink user plane flow on an uplink connection between a wireless device and a radio network to a first network node.
[0156] In step 1304, the second network node sends to the first network node one or more of: an indication of a proportion of packets within an uplink user plane flow on the uplink connection to be marked with a congestion indicator, wherein the proportion is based on a delay experienced by packets of the uplink user plane flow sent by the wireless device to the second network node; an indication of the delay experienced by packets of the uplink user plane flow sent by the wireless device to the second network node; and information enabling the first network node to calculate or estimate the delay experienced by packets of the uplink user plane flow sent by the wireless device to the second network node.
[0157] Those skilled in the art will appreciate that step 1304 may vary according to, for example, the different scenarios A, B, and C described above.
[0158] In case A, e.g., where the CDA and PMark functions are hosted in the second network node, step 1304 may include sending an indication of the proportion of packets to be marked with a congestion indicator (e.g., in the form of a probability) to the first network node, e.g., via an F1, X2, or Xn interface. For example, as described above, the indication may be included in an assistance information (type 2) PDU or a downlink data transfer status (type 1) PDU.
[0159] In case B, e.g., where the CDA function is hosted in the second network node and the PMark function is hosted in the first network node, step 1304 may include sending to the first network node an indication of the delay experienced by the packets in their transmission from the wireless device (e.g., UE) to the first network node via the second network node. For example, the delay may include a delay between sending a buffer status report by the wireless device to the second network node and sending data corresponding to the buffer status report by the second network node to the first network node. Additionally or alternatively, the delay may include a delay between sending a buffer status report by the wireless device to the second network node and sending all data indicated in the buffer status report by the second network node to the first network node. The above with respect to Fig.11 Further details can be found in the description.
[0160] The indication of the delay may be piggybacked within the data of the uplink user plane flow (e.g., within the packet sent in step 1302), or sent in a PDU (e.g., an assistance information PDU) from the second network node. In either case, the delay value reported to the first network node may be averaged over multiple measurement instances of the delay.
[0161] In case C, where the CDA and PMark functions are hosted in the first network node, step 1304 may include sending information to the first network node, thereby enabling the first network node to calculate, estimate or infer the delay experienced by packets of the uplink user plane flow. The information sent to the first network node may include one or more of the following: uplink data flow; uplink delay on the radio interface; one or more radio quality metrics for the connection between the wireless device and the second network node; an indication of the state of one or more uplink channels between the wireless device and the second network node; an indication of the round trip time of a transmission between the first network node and the second network node.
[0162] In other embodiments, the first congestion indicator may be added to the PDU signaled from the second network node to the first network node. A first congestion marking (which may be provided, for example, in a GTP-U extension header of a UL GTP-U PDU) may be provided with each uplink PDU containing an IP packet determined by a congestion control algorithm (in the second network node) to carry a second congestion indicator (e.g., in an ECN field of the IP packet). If the uplink PDU contains more than one IP packet or it contains fragments of IP packets, and if the first congestion indicator is added to the uplink PDU (e.g., in a GTP-U extension header), the node hosting the PDCP that receives the UL PDU will mark all corresponding IP packets within the uplink PDU with the second congestion indicator (e.g., ECN field).
[0163] Fig.14 An example of a communication system 1400 is shown in accordance with some embodiments.
[0164] In this example, the communication system 1400 includes a telecommunications network 1402, which includes an access network 1404 (e.g., a radio access network (RAN)) and a core network 1406 (which includes one or more core network nodes 1408). The access network 1404 includes one or more access network nodes, such as network nodes 1410a and 1410b (one or more of which may be collectively referred to as network nodes 1410), or any other similar third generation partnership project (3GPP) access nodes or non-3GPP access points. The network nodes 1410 facilitate direct or indirect connection of user equipment (UE), such as connecting UEs 1412a, 1412b, 1412c, and 1412d (one or more of which may be collectively referred to as UEs 1412) to the core network 1406 via one or more wireless connections.
[0165] Example wireless communications over wireless connections include sending and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information without the use of wires, cables, or other material conductors. In addition, in different embodiments, the communication system 1400 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that can facilitate or participate in the communication of data and / or signals (whether via a wired connection or a wireless connection). The communication system 1400 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar types of systems.
[0166] UE 1412 may be any of a variety of communication devices, including wireless devices that are arranged, configured and / or operable to communicate wirelessly with network node 1410 and other communication devices. Similarly, network node 1410 is arranged, capable, configured and / or operable to communicate directly or indirectly with UE 1412 and / or other network nodes or devices in telecommunication network 1402 to enable and / or provide network access (e.g., wireless network access) and / or perform other functions (e.g., management) in telecommunication network 1402.
[0167] In the depicted example, the core network 1406 connects the network node 1410 to one or more hosts, such as the host 1416. These connections may be direct connections, or indirect connections via one or more intermediate networks or devices. In other examples, the network node may be directly coupled to the host. The core network 1406 includes one or more core network nodes (e.g., core network node 1408) composed of hardware and software components. The features of these components may be substantially similar to those described for the UE, network node, and / or host, so that their description is generally applicable to the corresponding components of the core network node 1408. The example core network node includes one or more functions of: a mobile switching center (MSC), a mobility management entity (MME), a home subscriber server (HSS), an access and mobility management function (AMF), a session management function (SMF), an authentication server function (AUSF), a subscription identifier de-hiding function (SIDF), a unified data management (UDM), a security edge protection agent (SEPP), a network open function (NEF), and / or a user plane function (UPF).
[0168] The host 1416 may be under the ownership or control of a service provider other than the operator or provider of the access network 1404 and / or the telecommunications network 1402, and may be operated by or on behalf of the service provider. The host 1416 may host various applications to provide one or more services. Examples of such applications include providing real-time and / or pre-recorded audio / video content, data collection services (e.g., obtaining and compiling data about various environmental conditions detected by multiple UEs), analysis functions, social media, functions for controlling or otherwise interacting with remote devices, functions for alarm and monitoring centers, or any other such functions performed by a server.
[0169] Overall, Fig.14The communication system 1400 enables connections between UEs, network nodes, and hosts. In this sense, the communication system can be configured to operate according to predefined rules or procedures, such as specific standards, including but not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standards (e.g., 6G); Wireless Local Area Network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard (WiFi); and / or any other suitable wireless communication standards, such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-wave, Near Field Communication (NFC), ZigBee, LiFi, and / or any Low Power Wide Area Network (LPWAN) standards, such as LoRa and Sigfox.
[0170] In some examples, telecommunication network 1402 is a cellular network implementing 3GPP standardized features. Thus, telecommunication network 1402 can support network slicing to provide different logical networks to different devices connected to telecommunication network 1402. For example, telecommunication network 1402 can provide ultra-reliable low-latency communication (URLLC) services to some UEs while providing enhanced mobile broadband (eMBB) services to other UEs, and / or provide massive machine type communication (mMTC) / massive IoT services to other UEs.
[0171] In some examples, UE 1412 is configured to send and / or receive information without direct human interaction. For example, the UE may be designed to send information to access network 1404 on a predetermined schedule when triggered by an internal or external event or in response to a request from access network 1404. Additionally, the UE may be configured to operate in a single RAT or multi-RAT or multi-standard mode. For example, the UE may operate using any one or a combination of Wi-Fi, NR (New Radio), and LTE, i.e., configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) New Radio-Dual Connectivity (EN-DC).
[0172] exist Fig.14In the example shown in , the hub 1414 communicates with the access network 1404 to facilitate indirect communication between one or more UEs (e.g., UE 1412c and / or 1412d) and a network node (e.g., network node 1410b). In some examples, the hub 1414 can be a controller, a router, a content source and analysis, or any other communication device described herein about the UE. For example, the hub 1414 can be a broadband router that enables the UE to access the core network 1406. As another example, the hub 1414 can be a controller that sends commands or instructions to one or more actuators in the UE. The command or instruction can be received from the UE, the network node 1410, or received by an executable code, script, process or other instruction in the hub 1414. As another example, the hub 1414 can be a data collector that acts as a temporary storage device for UE data, and in some embodiments, analysis or other processing of the data can be performed. As another example, the hub 1414 can be a content source. For example, for a UE that is a VR headset, display, speaker, or other media delivery device, the hub 1414 can obtain VR assets, video, audio, or other media or data related to the sensory information via the network node, and then the hub 1414 provides it to the UE directly, after performing local processing, and / or after adding additional local content. In another example, the hub 1414 acts as a proxy server or orchestrator for the UE, especially when one or more UEs are low-energy IoT devices.
[0173] Hub 1414 can have constant / persistent or intermittent connection with network node 1410b. Hub 1414 can also allow different communication schemes and / or scheduling between hub 1414 and UE (e.g., UE 1412c and / or 1412d) and hub 1414 and core network 1406. In other examples, hub 1414 is connected to core network 1406 and / or one or more UE via wired connection. In addition, hub 1414 can be configured to be connected to M2M service provider and / or connected to another UE via direct connection through access network 1404. In some scenarios, UE can establish wireless connection with network node 1410, while still connected via hub 1414 by wired or wireless connection. In some embodiments, hub 1414 can be a dedicated hub, that is, its main function is to route communication from network node 1410b to UE / from UE to network node 1410b. In other embodiments, the hub 1414 may be a non-dedicated hub, that is, a device that is operable to route communications between UEs and the network node 1410b, but is also capable of operating as a communications origin and / or endpoint for a particular data channel.
[0174] Fig.15 UE 1500 according to some embodiments is shown. As used herein, UE refers to a device capable of, configured, arranged and / or operable to wirelessly communicate with a network node and / or other UEs. Examples of UEs include, but are not limited to, smart phones, mobile phones, cellular phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablet computers, laptop computers, laptop embedded devices (LEEs), laptop mounted devices (LMEs), smart devices, wireless client equipment (CPEs), vehicle-mounted or vehicle-mounted embedded / integrated wireless devices, etc. Other examples include any UE identified by the Third Generation Partnership Project (3GPP), including narrowband Internet of Things (NB-IoT) UEs, machine type communications (MTC) UEs, and / or enhanced MTC (eMTC) UEs.
[0175] The UE may support device-to-device (D2D) communications, for example, by implementing 3GPP standards for sidelink communications, dedicated short-range communications (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the associated device. Rather, a UE may represent a device that is intended to be sold to or operated by a human user but may not be, or may not initially be, associated with a particular human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended to be sold to or operated by an end user but may be associated with or operated for the benefit of a user (e.g., a smart power meter).
[0176] UE 1500 includes a processing circuit 1502, which is operatively coupled to an input / output interface 1506, a power supply 1508, a memory 1510, a communication interface 1512, and / or any other components or any combination thereof via a bus 1504. Some UEs may utilize Fig.15 All or a subset of the components shown in . The level of integration between components may vary depending on the UE. In addition, some UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
[0177] The processing circuit 1502 is configured to process instructions and data, and may be configured to implement any sequential state machine operable to execute instructions stored as a machine-readable computer program in the memory 1510. The processing circuit 1502 may be implemented as one or more hardware-implemented state machines (e.g., using discrete logic, field programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), etc.); programmable logic and appropriate firmware; one or more stored computer programs, general-purpose processors (e.g., microprocessors or digital signal processors (DSPs)) and appropriate software; or any combination of the above. For example, the processing circuit 1502 may include multiple central processing units (CPUs). The processing circuit 1502 may be operated to provide UE 1500 functionality alone or in combination with other UE 1500 components (e.g., memory 1510).
[0178] In this example, the input / output interface 1506 can be configured to provide one or more interfaces to an input device, an output device, or one or more input and / or output devices. Examples of output devices include speakers, sound cards, video cards, displays, monitors, printers, actuators, transmitters, smart cards, another output device, or any combination thereof. An input device can allow a user to capture information into the UE 1500. Examples of input devices include touch-sensitive displays or presence-sensitive displays, cameras (e.g., digital cameras, digital video cameras, web cameras, etc.), microphones, sensors, mice, trackballs, direction pads, trackpads, rollers, smart cards, etc. The presence-sensitive display can include a capacitive or resistive touch sensor to sense input from a user. The sensor can be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device can use an interface port of the same type as an input device. For example, a universal serial bus (USB) port can be used to provide input devices and output devices.
[0179] In some embodiments, the power supply 1508 is configured as a battery or a battery pack. Other types of power supplies may be used, such as an external power supply (e.g., a power outlet), a photovoltaic device, or a battery. The power supply 1508 may also include a power supply circuit for transmitting power from the power supply 1508 itself and / or an external power supply to various parts of the UE 1500 via an input circuit or interface (e.g., a power cord). The transmitted power may be used, for example, to charge the power supply 1508. The power supply circuit may perform any formatting, conversion, or other modification of the power from the power supply 1508 to make the power suitable for the corresponding components of the UE 1500 to which the power is provided.
[0180] The memory 1510 may be or be configured to include a memory such as a random access memory (RAM), a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic disk, an optical disk, a hard disk, a removable cassette, a flash drive, etc. In one example, the memory 1510 includes one or more application programs 1514 (e.g., an operating system, a web browser application, a widget, a widget engine, or other application) and corresponding data 1516. The memory 1510 may store any one of a variety of operating systems or a combination of operating systems for use by the UE 1500.
[0181] The memory 1510 may be configured to include a plurality of physical drive units, such as a redundant array of independent disks (RAID), a flash memory, a USB flash drive, an external hard drive, a thumb drive, a pen drive, a key drive, a high-density digital versatile disc (HD-DVD) optical drive, an internal hard drive, a Blu-ray optical drive, a holographic digital data storage (HDDS) optical drive, an external mini dual in-line memory module (DIMM), a synchronous dynamic random access memory (SDRAM), an external micro-DIMM SDRAM, a smart card memory (e.g., a tamper-proof module in the form of a universal integrated circuit card (UICC), including one or more subscriber identity modules (SIMs), such as USIM and / or ISIM), other memories, or any combination thereof. The UICC may be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC, commonly referred to as a “SIM card”. The memory 1510 may allow the UE 1500 to access instructions, applications, etc. stored on a temporary or non-temporary storage medium to offload data or upload data. An article of manufacture, such as utilizing a communication system, may be tangibly embodied as or in memory 1510, which may be or include a device-readable storage medium.
[0182] The processing circuit 1502 may be configured to communicate with an access network or other network using a communication interface 1512. The communication interface 1512 may include one or more communication subsystems and may include an antenna 1522 or be communicatively coupled to the antenna 1522. The communication interface 1512 may include one or more transceivers for communication (e.g., by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network)). Each transceiver may include a transmitter 1518 and / or a receiver 1520 suitable for providing network communications (e.g., optical, electrical, frequency allocation, etc.). In addition, the transmitter 1518 and the receiver 1520 may be coupled to one or more antennas (e.g., antenna 1522), and may share circuit components, software, or firmware, or may be implemented separately instead.
[0183] In some embodiments, the communication functionality of the communication interface 1512 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near field communication, location-based communication such as using a global positioning system (GPS) to determine location, another similar communication functionality, or any combination thereof. Communication may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, code division multiple access (CDMA), wideband code division multiple access (WCDMA), GSM, LTE, new radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / Internet protocol (TCP / IP), synchronous optical network (SONET), asynchronous transfer mode (ATM), QUIC, hypertext transfer protocol (HTTP), etc.
[0184] Regardless of the type of sensor, the UE may provide an output of the data captured by its sensor via a wireless connection to a network node through its communication interface 1512. The data captured by the UE's sensor may be transmitted via another UE via a wireless connection to a network node. The output may be periodic (e.g., every 15 minutes if it reports the sensed temperature), random (e.g., to balance the reporting load from multiple sensors), in response to a trigger event (e.g., sending an alarm when humidity is detected), in response to a request (e.g., a user-initiated request), or a continuous stream (e.g., a live video feed of a patient).
[0185] As another example, the UE includes an actuator, motor, or switch associated with a communication interface that is configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input, the state of the actuator, motor, or switch can change. For example, the UE can include a motor that adjusts a control surface or rotor of a drone in flight based on the received input, or controls a robotic arm performing a medical procedure based on the received input.
[0186] When in the form of an Internet of Things (IoT) device, a UE may be a device for one or more application areas including, but not limited to, urban wearable technology, extended industry applications, and healthcare. Non-limiting examples of such IoT devices are devices that are or are embedded in: a connected refrigerator or freezer, a television, connected lighting, an electric meter, a robotic vacuum cleaner, a voice-controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / humidity sensor, an electric door lock, a connected doorbell, an air conditioning system such as a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for augmented reality (AR) or virtual reality (VR), a wearable device for tactile enhancement or sensory enhancement, a sprinkler, an animal or item tracking device, a sensor for monitoring plants or animals, an industrial robot, an unmanned aerial vehicle (UAV), and any kind of medical device such as a heart rate monitor or a teleoperated surgical robot. A UE in the form of an IoT device includes circuits and / or software related to the intended application of the IoT device and, for example, software for Fig.15 Other components of UE 1500 are described as shown in FIG.
[0187] As yet another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements and sends the results of such monitoring and / or measurements to another UE and / or a network node. In this case, the UE may be an M2M device, which may be referred to as an MTC device in the 3GPP context. As a specific example, a UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle (e.g., a car, bus, truck), a ship, and an airplane, or other device that is capable of monitoring and / or reporting its operating status or other functions associated with its operation.
[0188] In practice, any number of UEs may be used together for a single use case. For example, a first UE may be or be integrated into a drone and provide the drone's speed information (obtained via a speed sensor) to a second UE that is a remote controller for operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the speed of the drone. The first UE and / or the second UE may also include multiple of the functions described above. For example, a UE may include a sensor and an actuator and handle data communications for both the speed sensor and the actuator.
[0189] Fig.16 A network node 1600 according to some embodiments is shown. As used herein, a network node refers to a device capable of, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or other network nodes or devices in a telecommunications network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs), and NR Node Bs (gNBs)).
[0190] Base stations may be classified based on the amount of coverage they provide (or in other words, their transmit power class), and may therefore be referred to as femto base stations, pico base stations, micro base stations, or macro base stations, depending on the amount of coverage provided. A base station may be a relay node or a relay donor node that controls a relay. A network node may also include one or more (or all) parts of a distributed radio base station (e.g., a centralized digital unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio head (RRH)). Such a remote radio unit may or may not be integrated with an antenna as an antenna-integrated radio. Portions of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
[0191] Other examples of network nodes include a multi-transmission point (multi-TRP) 5G access node, a multi-standard radio MSR device (such as an MSRBS), a network controller such as a radio network controller (RNC) or a base station controller (BSC), a base transceiver station (BTS), a transmission point, a transmission node, a multi-cell / multicast coordination entity (MCE), an operation and maintenance (O&M) node, an operation support system (OSS) node, a self-organizing network (SON) node, a positioning node (e.g., an evolved serving mobile positioning center (E-SMLC)), and / or a minimization of drive tests (MDT).
[0192] The network node 1600 includes a processing circuit 1602, a memory 1604, a communication interface 1606 and a power supply 1608 and / or any other components or any combination thereof. The network node 1600 may include multiple physically separated components (e.g., a node B component and an RNC component, or a BTS component and a BSC component, etc.), each of which may have its own corresponding components. In certain scenarios where the network node 1600 includes multiple separate components (e.g., BTS and BSC components), one or more separate components may be shared between multiple network nodes. For example, a single RNC may control multiple node Bs. In such a scenario, in some cases, each unique node B and RNC pair may be considered as a single separate network node. In some embodiments, the network node 1600 may be configured to support multiple radio access technologies (RATs). In such an embodiment, some components may be repeated (e.g., separate memories 1604 for different RATs), while some components may be reused (e.g., the same antenna 1610 may be shared by different RATs). The network node 1600 may also include various sets of example components for different wireless technologies (e.g., GSM, WCDMA, LTE, NR, Wi-Fi, Zigbee, Z-wave, LoRaWAN, radio frequency identification (RFID), or Bluetooth wireless technologies) integrated into the network node 1600. These wireless technologies may be integrated into the same or different chips or chipsets and other components within the network node 1600.
[0193] The processing circuit 1602 may include a combination of one or more of the following operable to provide the functionality of the network node 1600 alone or in combination with other network node 1600 components (e.g., memory 1604): a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and / or encoded logic. For example, the processing circuit 1602 may be configured to cause the network node to perform as described in reference Fig.12 That is, the processing circuit 1602 may be configured to act as the first network node and execute the method described above for Fig.12 Additionally or alternatively, the processing circuit 1602 may be configured to act as the second network node described above and perform the above-mentioned Fig.13 Describes one or more actions.
[0194] In some embodiments, processing circuitry 1602 includes a system on a chip (SOC). In some embodiments, processing circuitry 1602 includes one or more of radio frequency (RF) transceiver circuitry 1612 and baseband processing circuitry 1614. In some embodiments, radio frequency (RF) transceiver circuitry 1612 and baseband processing circuitry 1614 may be on separate chips (or chipsets), boards, or units (e.g., a radio unit and a digital unit). In alternative embodiments, some or all of RF transceiver circuitry 1612 and baseband processing circuitry 1614 may be on the same chip or chipset, board, or unit.
[0195] Memory 1604 may include any form of volatile or non-volatile computer-readable memory, including, but not limited to, permanent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disk (CD) or digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable storage device that stores information, data and / or instructions that can be used by processing circuit 1602. Memory 1604 may store any suitable instructions, data or information, including computer programs, software, applications (including one or more of logic, rules, code, tables, etc.) and / or other instructions that can be executed by processing circuit 1602 and utilized by network node 1600. Memory 1604 may be used to store any calculations performed by processing circuit 1602 and / or any data received via communication interface 1606. In some embodiments, processing circuit 1602 and memory 1604 are integrated.
[0196] The communication interface 1606 is used for the wired or wireless communication of signaling and / or data between network nodes, access networks and / or UEs. As shown, the communication interface 1606 includes a port / terminal 1616 to send and receive data from the network, for example, via a wired connection. The communication interface 1606 also includes a radio front-end circuit 1618 that can be coupled to an antenna 1610 or as a part of an antenna 1610 in some embodiments. The radio front-end circuit 1618 includes a filter 1620 and an amplifier 1622. The radio front-end circuit 1618 can be connected to the antenna 1610 and the processing circuit 1602. The radio front-end circuit 1618 can be configured to adjust the signal transmitted between the antenna 1610 and the processing circuit 1602. The radio front-end circuit 1618 can receive digital data that will be sent to other network nodes or UEs via a wireless connection. The radio front-end circuit 1618 can use a combination of a filter 1620 and / or an amplifier 1622 to convert digital data into a radio signal with appropriate channel and bandwidth parameters. The radio signal can then be transmitted via the antenna 1610. Similarly, when receiving data, antenna 1610 may collect radio signals, which may then be converted into digital data by radio front end circuitry 1618. The digital data may be passed to processing circuitry 1602. In other embodiments, the communication interface may include different components and / or different combinations of components.
[0197] In some alternative embodiments, the network node 1600 does not include a separate radio front end circuit 1618, but rather, the processing circuit 1602 includes the radio front end circuit and is connected to the antenna 1610. Similarly, in some embodiments, all or part of the RF transceiver circuit 1612 is part of the communication interface 1606. In other embodiments, the communication interface 1606 includes one or more ports or terminals 1616, the radio front end circuit 1618, and the RF transceiver circuit 1612 as part of a radio unit (not shown), and the communication interface 1606 communicates with the baseband processing circuit 1614, which is part of the digital unit (not shown).
[0198] Antenna 1610 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna 1610 may be coupled to radio front end circuit 1618 and may be any type of antenna capable of wirelessly sending and receiving data and / or signals. In some embodiments, antenna 1610 is separate from network node 1600 and may be connected to network node 1600 via an interface or port.
[0199] Antenna 1610, communication interface 1606 and / or processing circuit 1602 may be configured to perform any receiving operation and / or certain obtaining operations described herein as being performed by a network node. Any information, data and / or signal may be received from a UE, another network node and / or any other network device. Similarly, antenna 1610, communication interface 1606 and / or processing circuit 1602 may be configured to perform any sending operation described herein as being performed by a network node. Any information, data and / or signal may be sent to a UE, another network node and / or any other network device.
[0200] The power supply 1608 provides power to the various components of the network node 1600 in a form suitable for the respective components (e.g., at the voltage and current levels required by each respective component). The power supply 1608 may also include or be coupled to a power management circuit to provide power to the components of the network node 1600 for performing the functions described herein. For example, the network node 1600 may be connected to an external power source (e.g., a power grid, a power outlet) via an input circuit or interface (e.g., a cable), whereby the external power source provides power to the power circuit of the power supply 1608. As yet another example, the power supply 1608 may include a power source in the form of a battery or battery pack connected to or integrated into the power circuit. If the external power source fails, the battery may provide backup power.
[0201] An embodiment of the network node 1600 may include Fig.16 Additional components beyond those shown that are used to provide certain aspects of the functionality of the network node, including any functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 1600 may include a user interface device to allow information to be input into the network node 1600 and to allow information to be output from the network node 1600. This may allow a user to perform diagnostics, maintenance, repair, and other management functions for the network node 1600.
[0202] Fig.17 is a block diagram of a host 1700 according to various aspects described herein, and the host 1700 may be Fig.14 1416 of the embodiment of the host. As used herein, the host 1700 can be or include various combinations of hardware and / or software, including processing resources in a stand-alone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, a container, or a server farm. The host 1700 can provide one or more services to one or more UEs.
[0203] Host 1700 includes processing circuitry 1702, which is operatively coupled to input / output interface 1706, network interface 1708, power supply 1710, and memory 1712 via bus 1704. Other components may be included in other embodiments. The features of these components may be substantially similar to those described with respect to previous figures (e.g., Fig.15 and 16 ) so that its description is generally applicable to corresponding components of host 1700.
[0204] The memory 1712 may include one or more computer programs, including one or more host applications 1714 and data 1716, which may include user data, such as data generated by the UE for the host 1700 or data generated by the host 1700 for the UE. An embodiment of the host 1700 may use only a subset or all of the components shown. The host application 1714 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding of multiple different classes, types or implementations of UEs (e.g., mobile phones, desktop computers, wearable display systems, head-up display systems). The host application 1714 may also provide user authentication and authorization checks, and may periodically report health status, routing, and content availability to a central node (e.g., a device in a core network or on the edge). Thus, the host 1700 can select and / or indicate to the UE a different host for the over-the-top service. The host application 1714 can support various protocols, such as HTTP Live Streaming (HLS) protocol, Real-time Messaging Protocol (RTMP), Real-time Streaming Protocol (RTSP), HTTP Dynamic Adaptive Streaming (MPEG-DASH), etc.
[0205] Fig.18It is a block diagram showing a virtualized environment 1800 in which the functions implemented by some embodiments can be virtualized. In the current context, virtualization means creating a virtual version of a device or equipment, which may include a virtualized hardware platform, storage device, and networking resources. As used herein, virtualization can be applied to any device or component thereof described herein, and relates to an implementation in which at least a portion of the functions are implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components performed by one or more virtual machines (VMs), which are implemented in one or more virtual environments 1800 hosted by one or more hardware nodes (e.g., hardware computing devices operated as network nodes, UEs, core network nodes, or hosts). In addition, in embodiments in which a virtual node does not require a radio connection (e.g., a core network node or host), the node may be fully virtualized.
[0206] Application 1802 (which may alternatively be referred to as a software instance, a virtual appliance, a network function, a virtual node, a virtual network function, etc.) runs in a virtualized environment 1800 to implement certain features, functions and / or benefits of some embodiments disclosed herein.
[0207] The hardware 1804 includes processing circuitry, memory storing software and / or instructions executable by the hardware processing circuitry, and / or other hardware devices as described herein, such as network interfaces, input / output interfaces, etc. The software may be executed by the processing circuitry to instantiate one or more virtualization layers 1806 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide virtual machines 1808a and 1808b (one or more of which may be generally referred to as virtual machines 1808), and / or perform any of the functions, features, and / or benefits described for some embodiments described herein. The virtualization layer 1806 may present a virtual operating platform that appears to be networked hardware to the virtual machines 1808.
[0208] The virtual machine 1808 includes virtual processing, virtual memory, virtual network or interface, and virtual storage, and can be run by a corresponding virtualization layer 1806. Different embodiments of instances of virtual devices 1802 can be implemented on one or more virtual machines 1808 and can be implemented in different ways. In some contexts, the virtualization of hardware is referred to as network function virtualization (NFV). NFV can be used to integrate many network device types onto industry-standard high-volume server hardware, physical switches, and physical storage that can be located in data centers and customer premises equipment.
[0209] In the context of NFV, a virtual machine 1808 may be a software implementation of a physical machine that runs a program as if the program were executed on a physical, non-virtualized machine. Each virtual machine 1808 and the portion of the hardware 1804 that executes the virtual machine (hardware dedicated to the virtual machine and / or hardware shared by the virtual machine with other virtual machines) form a separate virtual network element. Still in the context of NFV, a virtual network function is responsible for handling a specific network function running in one or more virtual machines 1808 on the hardware 1804 and corresponds to an application 1802.
[0210] Hardware 1804 can be implemented in a stand-alone network node with general or specific components. Hardware 1804 can implement some functions via virtualization. Alternatively, hardware 1804 can be part of a larger hardware cluster (e.g., such as in a data center or CPE), where many hardware nodes work together and are managed via management and orchestration 1810, which, among other items, oversees the life cycle management of application 1802. In some embodiments, hardware 1804 is coupled to one or more radio units, each of which includes one or more transmitters and one or more receivers that can be coupled to one or more antennas. The radio unit can communicate directly with other hardware nodes via one or more appropriate network interfaces, and can be used in combination with virtual components to provide a virtual node with radio capabilities, such as a radio access node or base station. In some embodiments, a control system 1812 can be used to provide some signaling, which can be used alternatively for communication between hardware nodes and radio units.
[0211] Fig.19 A communication diagram is shown in which a host 1902 communicates with a UE 1906 via a network node 1904 over a partially wireless connection according to some embodiments. Fig.19 To describe the UE (eg, Fig.14 UE 1412a and / or Fig.15 UE 1500), network node (e.g. Fig.14 The network node 1410a and / or Fig.16 network nodes 1600) and hosts (e.g. Fig.14 Host 1416 and / or Fig.17 An example implementation of host 1700).
[0212] Similar to the host 1700, an embodiment of the host 1902 includes hardware, such as a communication interface, a processing circuit, and a memory. The host 1902 also includes software that is stored in the host 1902 or accessible by the host 1902 and can be executed by the processing circuit. The software includes a host application that can operate to provide services to a remote user (e.g., a UE 1906 connected via an over-the-top (OTT) connection 1950 extending between the UE 1906 and the host 1902). When providing services to the remote user, the host application can provide user data sent using the OTT connection 1950.
[0213] The network node 1904 includes hardware that enables it to communicate with the host 1902 and the UE 1906. The connection 1960 can be direct or through a core network (such as Fig.14 The core network 1406 of the present invention) and / or one or more other intermediate networks, such as one or more public, private or managed networks. For example, the intermediate network can be a backbone network or the Internet.
[0214] UE 1906 includes hardware and software, which is stored in UE 1906 or accessible by UE 1906 and can be executed by the processing circuit of UE. The software includes a client application, such as a web browser or an operator-specific "application", which is operable to provide services to human or non-human users via UE 1906 with the support of host 1902. In host 1902, the executing host application can communicate with the executing client application via an OTT connection 1950 terminated at UE 1906 and host 1902. When providing services to users, the client application of UE can receive request data from the host application of the host and provide user data in response to the request data. OTT connection 1950 can transmit both request data and user data. The client application of UE can interact with the user to generate user data provided to the host application via OTT connection 1950.
[0215] The OTT connection 1950 may extend via a connection 1960 between the host 1902 and the network node 1904 and via a wireless connection 1970 between the network node 1904 and the UE 1906 to provide connectivity between the host 1902 and the UE 1906. The connection 1960 and the wireless connection 1970 through which the OTT connection 1950 may be provided have been drawn abstractly to illustrate communications between the host 1902 and the UE 1906 via the network node 1904 without explicit reference to any intermediate devices and the precise routing of messages via those devices.
[0216] As an example of sending data via the OTT connection 1950, in step 1908, the host 1902 provides user data, which can be performed by executing a host application. In some embodiments, the user data is associated with a specific human user who interacts with the UE 1906. In other embodiments, the user data is associated with the UE 1906, and the UE 1906 shares the data with the host 1902 without explicit human interaction. In step 1910, the host 1902 initiates a transmission carrying the user data toward the UE 1906. The host 1902 may initiate the transmission in response to a request sent by the UE 1906. The request may be caused by human interaction with the UE 1906 or by the operation of a client application executed on the UE 1906. According to the teachings of the embodiments described throughout the present disclosure, the transmission may be through the network node 1904. Therefore, in step 1912, according to the teachings of the embodiments described throughout the present disclosure, the network node 1904 sends the user data carried in the transmission initiated by the host 1902 to the UE 1906. In step 1914 , UE 1906 receives user data carried in the transmission, which may be performed by a client application executing on UE 1906 that is associated with a host application executed by host 1902 .
[0217] In some examples, UE 1906 executes a client application that provides user data to host 1902. The user data may be provided in response to data received from host 1902. Thus, in step 1916, UE 1906 may provide user data, which may be performed by executing a client application. In providing the user data, the client application may further consider user input received from a user via an input / output interface of UE 1906. Regardless of the specific manner in which the user data is provided, UE 1906 initiates transmission of the user data toward host 1902 via network node 1904 in step 1918. In step 1920, in accordance with the teachings of the embodiments described throughout the present disclosure, network node 1904 receives user data from UE 1906 and initiates transmission of the received user data toward host 1902. In step 1922, host 1902 receives the user data carried in the transmission initiated by UE 1906.
[0218] One or more of the various embodiments improve the performance of OTT services provided to UE 1906 using OTT connection 1950 (where wireless connection 1970 forms the final segment). More specifically, the teachings of these embodiments can improve the latency and reliability of uplink transmissions, thereby providing benefits such as better responsiveness.
[0219] In an example scenario, host 1902 may collect and analyze plant status information. As another example, host 1902 may process audio and video data that may have been obtained from UE for creating a map. As another example, host 1902 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, host 1902 may store surveillance videos uploaded by UE. As another example, host 1902 may store or control access to media content such as video, audio, VR, or AR, and host 1902 may broadcast, multicast, or unicast the media content to UE. As other examples, host 1902 may be used for energy pricing, remote control of non-time-critical power loads to balance power generation demand, positioning services, presentation services (e.g., compiling a map based on data collected from a remote device, etc.), or any other function of collecting, obtaining, storing, analyzing, and / or sending data.
[0220] In some examples, a measurement process may be provided for the purpose of monitoring data rates, delays, and other factors on which one or more embodiments are improved. In response to changes in the measurement results, there may also be an optional network function for reconfiguring the OTT connection 1950 between the host 1902 and the UE 1906. The measurement process and / or network function for reconfiguring the OTT connection may be implemented in the software and hardware of the host 1902 and / or the UE 1906. In some embodiments, sensors (not shown) may be deployed in other devices through which the OTT connection 1950 passes or associated with such other devices; the sensors may participate in the measurement process by providing the values of the monitored quantities of the above examples or providing the values of other physical quantities from which the software can calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 1950 may include message formats, retransmission settings, preferred routes, etc.; the reconfiguration does not require direct changes to the operation of the network node 1904. Such processes and functions may be known and practiced in the art. In some embodiments, the measurement may involve proprietary UE signaling, which facilitates the host 1902 to measure throughput, propagation time, delay, etc. The measurement can be achieved because the software causes the OTT connection 1950 to be used to send messages, particularly empty or "dummy" messages, during which it monitors propagation times, errors, etc.
[0221] Although the computing devices (e.g., UE, network node, host) described herein may include a combination of the hardware components shown, other embodiments may include computing devices with different combinations of components. It will be understood that these computing devices may include any suitable combination of hardware and / or software required to perform the tasks, features, functions and methods disclosed herein. The determination, calculation, acquisition or similar operations described herein may be performed by a processing circuit, which may process information in the following manner: converting the obtained information into other information, comparing the obtained information or the converted information with the information stored in the network node, and / or performing one or more operations based on the obtained information or the converted information, and making a determination as a result of the processing. In addition, although the components are depicted as a single box located within a larger box or nested within multiple boxes, in fact, the computing device may include multiple different physical components constituting a single shown component, and the functions may be divided between separate components. For example, a communication interface may be configured to include any component described herein, and / or the functions of the components may be divided between the processing circuit and the communication interface. In another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, while the computationally intensive functions may be implemented in hardware.
[0222] In some embodiments, some or all of the functionality described herein may be provided by a processing circuit executing instructions stored on a memory, which in some embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by a processing circuit without the need to execute instructions stored on a separate or separate device-readable storage medium, such as in a hardwired manner. In any of these specific embodiments, the processing circuit may be configured to perform the described functionality, regardless of whether instructions stored on a non-transitory computer-readable storage medium are executed. The benefits provided by such functionality are not limited to processing circuits or other components of a computing device, but are enjoyed by the computing device as a whole and / or generally by end users and wireless networks.
[0223] The following numbered statements set forth embodiments of the present disclosure:
[0224] Group B Example
[0225] 1. A method for uplink congestion control in a radio network, performed by a first network node, the first network node processing one or more first layers of a protocol stack for an uplink connection between a wireless device and the radio network, the first network node being communicatively coupled to a second network node, the second network node processing one or more second layers of the protocol stack for the uplink connection, wherein the one or more second layers are lower than the one or more first layers, the method comprising:
[0226] obtaining an indication of a proportion of packets within an uplink user plane flow on the uplink connection to be marked with a congestion indicator, wherein the proportion is based on a delay experienced by packets of the uplink user plane flow sent to the second network node;
[0227] marking the proportion of packets with a congestion indicator; and
[0228] Packets of the uplink user plane flow are sent towards the core network of the radio network.
[0229] 2. The method of embodiment 1, wherein the proportion of packets is marked in a Packet Data Convergence Protocol (PDCP) entity of the first network node.
[0230] 3. A method according to embodiment 1 or 2, wherein the indication of the proportion of packets to be marked includes an indication of a probability, and wherein marking the proportion of packets with a congestion indicator includes: marking packets of an uplink user plane flow with a congestion indicator based on the probability.
[0231] 4. The method of any preceding embodiment, wherein obtaining an indication of the proportion of packets to be marked comprises: receiving an indication of the proportion of packets to be marked from the second network node.
[0232] 5. The method of embodiment 4, wherein the indication of the proportion of packets to be marked is received in an assistance information protocol data unit (PDU) sent by the second network node.
[0233] 6. The method of embodiment 4, wherein the indication of the proportion of packets to be marked is received in a downlink data delivery status PDU sent by the second network node.
[0234] 7. The method of any one of embodiments 1 to 3, wherein obtaining an indication of a proportion of packets to be marked comprises calculating the proportion of packets based on a delay experienced by packets of an uplink user plane flow sent to the second network node.
[0235] 8. The method of embodiment 7, further comprising receiving, from the second network node, an indication of delay experienced by packets of the uplink user plane flow sent to the second network node.
[0236] 9. The method of embodiment 8, wherein the delay experienced by packets of the uplink user plane flow comprises a delay between sending a buffer status report by the wireless device to the second network node and sending data corresponding to the buffer status report by the second network node to the first network node.
[0237] 10. A method according to embodiment 8 or 9, wherein the delay experienced by the packets of the uplink user plane flow includes the delay between the wireless device sending the buffer status report to the second network node and the second network node sending all data indicated in the buffer status report to the first network node.
[0238] 11. The method of any one of embodiments 8 to 10, wherein the indication of the delay experienced by the packets of the uplink user plane flow sent to the second network node is piggybacked within the data for the uplink user plane flow.
[0239] 12. The method of any one of embodiments 8 to 10, wherein the indication of the delay experienced by packets of the uplink user plane flow sent to the second network node is received in an assistance information PDU from the second network node.
[0240] 13. A method according to any one of embodiments 8 to 12, wherein the indication of the delay experienced by packets of the uplink user plane flow sent to the second network node includes an indication of the average delay experienced by packets of the uplink user plane flow sent to the second network node.
[0241] 14. The method of embodiment 7, further comprising calculating or estimating a delay experienced by packets of the uplink user plane flow sent to the second network node.
[0242] 15. The method of embodiment 14, wherein the delay experienced by packets of the uplink user plane flow sent to the second network node is estimated or calculated based on information received from the second network node.
[0243] 16. A method according to embodiment 15, wherein the information received from the second network node includes one or more of the following: an uplink data flow; an uplink delay on a radio interface; one or more radio quality metrics for a connection between the wireless device and the second network node; an indication of the state of one or more uplink channels between the wireless device and the second network node; an indication of a round-trip time for transmission between the first network node and the second network node.
[0244] 17. A method according to any one of embodiments 14 to 16, wherein the delay experienced by packets of an uplink user plane flow sent to a second network node is estimated or calculated based on information received from a third network node (e.g., a control plane node, such as a control plane centralized unit) about resources utilized in a cell served by the second network node.
[0245] 18. A method according to embodiment 17, wherein the information received from the third network node includes one or more of the following: an indication of utilization of physical resource blocks; an indication of availability of resources in the cell; the number of active wireless devices in the cell; the number of RRC connections in the cell; and one or more transmission level traffic load indications.
[0246] 19. The method according to embodiment 1 or 2 further includes: receiving data packets for an uplink user plane flow from a second network node, wherein obtaining an indication of the proportion of packets to be marked with a congestion indicator includes: a subset of data packets received from the second network node marked with a first congestion indicator, and wherein marking packets for the uplink user plane flow with a congestion indicator includes: marking Internet Protocol packets within the subset of data packets received from the second network node with a second congestion indicator.
[0247] 20. A method for uplink congestion control in a radio network, performed by a second network node, the second network node processing one or more second layers of a protocol stack for an uplink connection between a wireless device and the radio network, the second network node being communicatively coupled to a first network node, the first network node processing one or more first layers of a protocol stack for the uplink connection, wherein the one or more second layers are lower than the one or more first layers, the method comprising:
[0248] sending packets for an uplink user plane flow on the uplink connection to the first network node for onward transmission towards a core network node of the radio network; and
[0249] Sending one or more of the following to the first network node:
[0250] An indication of a proportion of packets within an uplink user plane flow on the uplink connection to be marked with a congestion indicator, wherein the proportion is based on packets of the uplink user plane flow sent by the wireless device to the second network node
[0251] the delays experienced;
[0252] an indication of a delay experienced by packets of an uplink user plane flow sent by the wireless device to the second network node;
[0253] as well as
[0254] Information enabling the first network node to calculate or estimate a delay experienced by packets of an uplink user plane flow sent by a wireless device to a second network node.
[0255] 21. A method according to embodiment 20, wherein the indication of the proportion of packets to be marked with a congestion indicator includes a subset of data packets marked with a first congestion indicator sent to the first network node, thereby enabling the first network node to mark Internet Protocol packets within the subset of data packets with a second congestion indicator.
[0256] 22. A method according to embodiment 20, wherein the method includes: sending information to a first network node enabling the first network node to calculate or estimate the delay experienced by packets of an uplink user plane flow sent by a wireless device to a second network node, and wherein the information includes one or more of the following: an uplink data flow; an uplink delay on a radio interface; one or more radio quality metrics for a connection between the wireless device and the second network node; an indication of the state of one or more uplink channels between the wireless device and the second network node; an indication of the round-trip time of a transmission between the first network node and the second network node.
[0257] 23. A method according to embodiment 20, wherein the method includes: sending an indication of the proportion of packets in an uplink user plane flow on an uplink connection to a first network node to be marked with a congestion indicator, and wherein the indication of the proportion of packets to be marked includes an indication of the probability that the first network node is to mark packets of the uplink user plane flow with a congestion indicator.
[0258] 24. A method according to embodiment 20, wherein the method includes: sending an indication of the delay experienced by packets of an uplink user plane flow sent by a wireless device to a second network node to a first network node, and wherein the delay experienced by packets of the uplink user plane flow includes a delay between sending a buffer status report by the wireless device to the second network node and sending data corresponding to the buffer status report by the second network node to the first network node.
[0259] 25. The method of embodiment 24, wherein the delay experienced by packets of the uplink user plane flow comprises a delay between sending a buffer status report by the wireless device to the second network node and sending all data indicated in the buffer status report by the second network node to the first network node.
[0260] 26. The method of embodiment 24 or 25, wherein the indication of the delay experienced by the packets of the uplink user plane flow sent to the second network node is piggybacked within the data of the uplink user plane flow.
[0261] 27. The method of any one of embodiments 24 to 26, wherein the indication of delay experienced by packets of the uplink user plane flow sent to the second network node is received in an assistance information PDU from the second network node.
[0262] 28. A method according to any one of embodiments 24 to 27, wherein the indication of the delay experienced by packets of the uplink user plane flow sent to the second network node includes an indication of the average delay experienced by packets of the uplink user plane flow sent to the second network node.
[0263] 29. The method according to any of the preceding embodiments, wherein the one or more first layers include a Packet Data Convergence Protocol (PDCP) layer.
[0264] 30. The method according to any one of the preceding embodiments, wherein the one or more second layers include one or more of the following: a radio link control (RLC) layer; a medium access control (MAC) layer; and a physical (PHY) layer.
[0265] 31. The method of any preceding embodiment, wherein the first network node comprises a first, such as a centralized unit, of a base station, and the second network node comprises a second, such as a distributed unit, of a base station.
[0266] 32. A method according to any of the preceding embodiments, wherein the congestion indicator comprises a low-latency, low-loss, scalable throughput (L4S) congestion indicator.
[0267] 33. The method according to any one of the preceding embodiments, further comprising:
[0268] obtain user data; and
[0269] Forwards user data to the host.
[0270] Group C Example
[0271] 34. A network node for uplink congestion control in a radio network, the network node comprising:
[0272] A processing circuit configured to cause a network node to perform any of the steps of any one of Group B embodiments;
[0273] A power supply circuit is configured to supply power to the processing circuit.
[0274] 35. A first network node for uplink congestion control in a radio network, the first network node comprising:
[0275] A processing circuit configured to cause the first network node to perform the method of any one of embodiments 1 to 19 and 29 to 33 (dependent on embodiments 1 to 19);
[0276] A power supply circuit is configured to supply power to the processing circuit.
[0277] 36. A second network node for uplink congestion control in a radio network, the second network node comprising:
[0278] A processing circuit configured to cause the second network node to perform the method of any one of embodiments 20 to 28 and 29 to 33 (dependent on embodiments 20 to 28);
[0279] A power supply circuit is configured to supply power to the processing circuit.
[0280] 37. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising:
[0281] processing circuitry configured to provide user data; and
[0282] A network interface, which is configured to initiate transmission of user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and a processing circuit, the processing circuit of the network node being configured to perform any operation of any of the Group B embodiments to send user data from a host to a UE.
[0283] 38. The host according to the preceding embodiment, wherein:
[0284] The processing circuitry of the host is configured to execute a host application that provides user data; and
[0285] The UE includes processing circuitry configured to execute a client application associated with a host application to receive a transmission of user data from the host.
[0286] 39. A method implemented in a host, the host being configured to operate in a communication system further comprising a network node and a user equipment (UE), the method comprising:
[0287] Providing user data to the UE; and
[0288] A transmission carrying user data is initiated to a UE via a cellular network including a network node, wherein the network node performs any operation of any of Group B embodiments to send user data from a host to a UE.
[0289] 40. The method according to the previous embodiment further includes: sending, at the network node, user data provided by the host for the UE.
[0290] 41. A method according to any of the first two embodiments, wherein the user data is provided at the host by executing a host application, the host application interacts with a client application executed on the UE, and the client application is associated with the host application.
[0291] 42. A communication system configured to provide an over-the-top service, the communication system comprising:
[0292] A host computer, which includes:
[0293] a processing circuit configured to provide user data to a user equipment (UE), the user data being associated with an over-the-top service; and
[0294] A network interface configured to initiate transmission of user data to a cellular network node for transmission to a UE, the network node having a communication interface and a processing circuit, the processing circuit of the network node being configured to perform any operation of any of the Group B embodiments to send user data from a host to a UE.
[0295] 43. The communication system according to the previous embodiment, further comprising:
[0296] Network nodes; and / or
[0297] User equipment.
[0298] 44. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising:
[0299] processing circuitry configured to initiate receipt of user data; and
[0300] A network interface configured to receive user data from a network node in a cellular network, the network node having a communication interface and a processing circuit, the processing circuit of the network node being configured to perform any operation of any of the Group B embodiments to receive user data from a host user equipment (UE).
[0301] 45. The host according to the preceding embodiment, wherein:
[0302] The processing circuitry of the host is configured to execute a host application to provide user data; and
[0303] The host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.
[0304] 46. The host of any one of the first two embodiments, wherein initiating reception of user data comprises: requesting user data.
[0305] 47. A method implemented by a host, the host being configured to operate in a communication system further comprising a network node and a user equipment (UE), the method comprising:
[0306] At the host, reception of user data from the UE is initiated, the user data originating from a transmission that the network node has received from the UE, wherein the network node performs any steps of any of Group B embodiments to receive user data from the UE of the host.
[0307] 48. The method according to the previous embodiment also includes: at the network node, sending the received user data to the host.
[0308] abbreviation
[0309] At least some of the following abbreviations may be used in the present disclosure. If there is an inconsistency between abbreviations, the above usage shall take precedence. If listed multiple times below, the first listing shall take precedence over any subsequent listings.
[0310] 5GC 5G Core Network
[0311] AQM Active Queue Management
[0312] AR Augmented Reality
[0313] BSR Buffer Status Report
[0314] CDA Congestion Detection Algorithm
[0315] CE experiences congestion
[0316] CN Core Network
[0317] CQI Channel Quality Indicator
[0318] CU Central Unit
[0319] DDDS Downlink data transmission status
[0320] DL Downlink
[0321] DRB Data Radio Bearer
[0322] DU Distributed Unit
[0323] E1AP E1 Application Protocol
[0324] E2E End to End
[0325] ECN Explicit Congestion Notification
[0326] GTP GPRS Tunneling Protocol
[0327] HARQ Hybrid Automatic Repeat Request
[0328] L4S low latency, low loss, scalable throughput
[0329] MAC Media Access Control
[0330] MBB Mobile Broadband
[0331] NG Next Generation
[0332] PDCP Packet Data Convergence Protocol
[0333] PDU Protocol Data Unit
[0334] PHY Physical Layer
[0335] QoE Quality of Experience
[0336] QoS Quality of Service
[0337] RAN Radio Access Network
[0338] RLC Radio Link Control
[0339] RTT Round Trip Time
[0340] SDAP Service Data Adaptation Protocol
[0341] UE User Equipment
[0342] UL Uplink
[0343] UP User Plane
[0344] URLLC Ultra-Reliable Low Latency Communications
[0345] VR Virtual Reality
[0346] 1x RTT CDMA2000 1x Radio Transmission Technology
[0347] 3GPP Third Generation Partnership Project
[0348] 5G Fifth Generation
[0349] 6G Sixth Generation
[0350] ABS Almost Blank Subframe
[0351] ARQ Automatic Repeat Request
[0352] AWGN Additive White Gaussian Noise
[0353] BCCH Broadcast Control Channel
[0354] BCH Broadcast Channel
[0355] CA Carrier Aggregation
[0356] CC Carrier Component
[0357] CCCH SDU Common Control Channel SDU
[0358] CDMA Code Division Multiple Access
[0359] CGI Cell Global Identifier
[0360] CIR Channel Impulse Response
[0361] CP Cyclic Prefix
[0362] CPICH Common Pilot Channel
[0363] CPICH Ec / No CPICH received energy per chip divided by the power density in the frequency band
[0364] CQI Channel Quality Information
[0365] C-RNTI Cell RNTI
[0366] CSI Channel State Information
[0367] DCCH Dedicated Control Channel
[0368] DL Downlink
[0369] DM Demodulation
[0370] DMRS Demodulation Reference Signal
[0371] DRX Discontinuous Reception
[0372] DTX Discontinuous Transmission
[0373] DTCH Dedicated Traffic Channel
[0374] DUT Device Under Test
[0375] E-CID Enhanced Cell ID (positioning method)
[0376] eMBMS Evolved Multimedia Broadcast Multicast Service
[0377] E-SMLC Evolved Serving Mobile Location Center
[0378] ECGI Evolved CGI
[0379] eNB E-UTRAN Node B
[0380] ePDCCH Enhanced Physical Downlink Control Channel
[0381] E-SMLC Evolved Serving Mobile Location Center
[0382] E-UTRA Evolved UTRA
[0383] E-UTRAN Evolved UTRAN
[0384] FDD Frequency Division Duplex
[0385] FFS needs further study
[0386] Base stations in gNB NR
[0387] GNSS Global Navigation Satellite System
[0388] HARQ Hybrid Automatic Repeat Request
[0389] HO Switchover
[0390] HSPA High Speed Packet Access
[0391] HRPD High Rate Packet Data
[0392] LOS Line of Sight
[0393] LPP LTE Positioning Protocol
[0394] LTE Long Term Evolution
[0395] MAC Media Access Control
[0396] MAC Message Authentication Code
[0397] MBSFN Multimedia Broadcast Multicast Service Single Frequency Network
[0398] MBSFN ABS MBSFN Almost Blank Subframe
[0399] MDT Minimized Drive Test
[0400] MIB Master Information Block
[0401] MME Mobility Management Entity
[0402] MSC Mobile Switching Center
[0403] NPDCCH Narrowband Physical Downlink Control Channel
[0404] NR New Radio
[0405] OCNG OFDMA Channel Noise Generator
[0406] OFDM Orthogonal Frequency Division Multiplexing
[0407] OFDMA Orthogonal Frequency Division Multiple Access
[0408] OSS Operation Support System
[0409] OTDOA observed time difference of arrival
[0410] O&M Operation and Maintenance
[0411] PBCH Physical Broadcast Channel
[0412] P-CCPCH Primary Common Control Physical Channel
[0413] PCell Primary Cell
[0414] PCFICH Physical Control Format Indicator Channel
[0415] PDCCH Physical Downlink Control Channel
[0416] PDCP Packet Data Convergence Protocol
[0417] PDP Profile Delay Profile
[0418] PDSCH Physical Downlink Shared Channel
[0419] PGW Packet Gateway
[0420] PHICH Physical Hybrid ARQ Indicator Channel
[0421] PLMN Public Land Mobile Network
[0422] PMI Precoder Matrix Indicator
[0423] PRACH Physical Random Access Channel
[0424] PRS Positioning Reference Signal
[0425] PSS Primary Synchronization Signal
[0426] PUCCH Physical Uplink Control Channel
[0427] PUSCH Physical Uplink Shared Channel
[0428] RACH Random Access Channel
[0429] QAM Quadrature Amplitude Modulation
[0430] RAN Radio Access Network
[0431] RAT Radio Access Technology
[0432] RLC Radio Link Control
[0433] RLM Radio Link Management
[0434] RNC Radio Network Controller
[0435] RNTI Radio Network Temporary Identifier
[0436] RRC Radio Resource Control
[0437] RRM Radio Resource Management
[0438] RS reference signal
[0439] RSCP Received Signal Code Power
[0440] RSRP Reference Symbol Received Power or Reference Signal Received Power
[0441] RSRQ Reference Signal Received Quality or Reference Symbol Received Quality
[0442] RSSI Received Signal Strength Indicator
[0443] RSTD Reference Signal Time Difference
[0444] SCH Synchronization Channel
[0445] SCell Secondary Cell
[0446] SDAP Service Data Adaptation Protocol
[0447] SDU Service Data Unit
[0448] SFN System Frame Number
[0449] SGW Service Gateway
[0450] SI System Information
[0451] SIB System Information Block
[0452] SNR Signal to Noise Ratio
[0453] SON Self-Optimizing Network
[0454] SS Sync Signal
[0455] SSS Secondary synchronization signal
[0456] TDD Time Division Duplex
[0457] TDOA Time Difference of Arrival
[0458] TOA Time of Arrival
[0459] TSS three-level synchronization signal
[0460] TTI Transmission Time Interval
[0461] UE User Equipment
[0462] UL Uplink
[0463] USIM Universal Subscriber Identity Module
[0464] UTDOA Uplink Time Difference of Arrival
[0465] WCDMA Wideband CDMA
[0466] WLAN broadband local area network
Claims
1. A method for uplink congestion control in a radio network, performed by a first network node, the first network node processing one or more first layers of a protocol stack for an uplink connection between a wireless device and the radio network, the one or more first layers comprising a Packet Data Convergence Protocol (PDCP) layer, the first network node being communicatively coupled to a second network node, the second network node processing one or more second layers of the protocol stack for the uplink connection, wherein The one or more second layers are lower than the one or more first layers, and the method comprises: receiving (1204) an assistance information protocol data unit (PDU) from the second network node, the assistance information PDU comprising an indication of a proportion of packets within an uplink user plane flow on the uplink connection to be marked with a congestion indicator, wherein the proportion is based on a delay experienced by packets of the uplink user plane flow sent by the wireless device to the second network node; marking (1206) the proportion of packets with the congestion indicator; and Packets of the uplink user plane flow are sent (1208) towards a core network of the radio network.
2. The method according to claim 1, wherein: Marking (1206) the proportion of packets with the congestion indicator is performed by setting an Explicit Congestion Notification (ECN) bit in an IP header of the packets.
3. A method according to any one of the preceding claims, wherein: The indication explicitly states the proportion of packets to be marked.
4. A method for uplink congestion control in a radio network, performed by a second network node, the second network node processing one or more second layers of a protocol stack for an uplink connection between a wireless device and the radio network, the second network node being communicatively coupled to a first network node, the first network node processing one or more first layers of the protocol stack for the uplink connection, the one or more first layers comprising a Packet Data Convergence Protocol (PDCP) layer, wherein The one or more second layers are lower than the one or more first layers, and the method comprises: sending (1302) packets for an uplink user plane flow on the uplink connection to the first network node for onward transmission towards a core network node of the radio network; and Sending (1304) an auxiliary information protocol data unit (PDU) to the first network node, the auxiliary information PDU comprising: An indication of a proportion of packets within the uplink user plane flow on the uplink connection to be marked with a congestion indicator, wherein the proportion is based on a delay experienced by packets of the uplink user plane flow sent by the wireless device to the second network node.
5. The method according to claim 4, wherein: The indication explicitly states the proportion of packets to be marked.
6. The method according to claim 4, wherein: The indication of the proportion of packets to be marked comprises an indication of a probability that the first network node is to mark packets of the uplink user plane flow with the congestion indicator.
7. A method according to any one of the preceding claims, wherein: The first network node comprises a centralized unit of a base station and the second network node comprises a distributed unit of the base station.
8. A network node (1600) for uplink congestion control in a radio network, the network node being configured to perform the method according to any one of claims 1 to 3.
9. A network node (1600) for uplink congestion control in a radio network, the network node being configured to perform the method according to any of claims 4 to 6.
10. A first network node for uplink congestion control in a radio network, the first network node processing one or more first layers of a protocol stack for an uplink connection between a wireless device and the radio network, the one or more first layers comprising a Packet Data Convergence Protocol (PDCP) layer, the first network node being communicatively coupled to a second network node, the second network node processing one or more second layers of the protocol stack for the uplink connection, wherein The one or more second layers are lower than the one or more first layers, and the first network node comprises: The processing circuit (1602) is configured to cause the first network node to: receiving an assistance information protocol data unit (PDU) from the second network node, the assistance information PDU comprising an indication of a proportion of packets within an uplink user plane flow on the uplink connection to be marked with a congestion indicator, wherein the proportion is based on a delay experienced by packets of the uplink user plane flow sent by the wireless device to the second network node; marking the proportion of packets with the congestion indicator; and Packets of the uplink user plane flow are sent towards a core network of the radio network.
11. The first network node according to claim 10, wherein: The marking with the congestion indicator in the proportion of packets is by means of an Explicit Congestion Notification (ECN) bit in an IP header of the packets.
12. The first network node according to any one of claims 10 to 11, wherein: The indication explicitly states the proportion of packets to be marked.
13. A second network node (1600) for uplink congestion control in a radio network, the second network node processing one or more second layers of a protocol stack for an uplink connection between a wireless device and the radio network, the second network node being communicatively coupled to a first network node, the first network node processing one or more first layers of the protocol stack for the uplink connection, the one or more first layers comprising a Packet Data Convergence Protocol (PDCP) layer, wherein The one or more second layers are lower than the one or more first layers, and the second network node comprises: The processing circuit (1602) is configured to cause the second network node to: sending packets for an uplink user plane flow on the uplink connection to the first network node for onward transmission towards a core network node of the radio network; and Send an auxiliary information protocol data unit (PDU) to the first network node, where the auxiliary information PDU includes: An indication of a proportion of packets within the uplink user plane flow on the uplink connection to be marked with a congestion indicator, wherein the proportion is based on a delay experienced by packets of the uplink user plane flow sent by the wireless device to the second network node.
14. The second network node according to claim 13, wherein: The indication explicitly states the proportion of packets to be marked with a congestion indicator.
15. The second network node according to claim 13, wherein: The indication of the proportion of packets to be marked comprises an indication of a probability that the first network node is to mark packets of the uplink user plane flow with the congestion indicator.
Citation Information
Cited By
Control information sending method and device, equipment, storage medium and program product
CN120979600A
RAN and UE driven L4S marking and processing for congestion management in an O-RAN based network architecture
US12684410B2
RAN and UE Driven L4S Marking and Processing for Congestion Management in an O-RAN Based Network Architecture
US20240334244A1
