Backhaul Adaptation Protocol Path Identification for Fair Scheduling in Integrated Access Backhaul Nodes

Abstract

A method in which a first network node receives a packet having a path identifier value in a header from a second network node. Based on the path identifier value, a plurality of bearers associated with the path are determined, the plurality of bearers are used to allocate at least one resource to the packet, and the packet is then sent to a third network node based on the at least one resource.

Description

Technical Field

[0001] The present disclosure relates generally to wireless communications and, more particularly, to systems and methods for integrated access backhaul node backhaul adaptation protocol path identification for fair scheduling. Background Art

[0002] The 3rd Generation Partnership Project (3GPP) is currently standardizing Integrated Access and Radio Access Backhaul (IAB) in New Radio (NR) in Rel-16 (RP-192188). The use of short-range mmWave spectrum in NR requires densified deployments using multi-hop backhaul. However, fiber to each base station is too expensive and sometimes not even possible (e.g. historical sites). The main IAB principle is to use wireless links (instead of fiber) for backhaul to enable flexible and very dense cell deployments without densifying the transport network. Use case scenarios for IAB can include coverage extension, deployment of a large number of small cells and fixed wireless access (FWA) (e.g. to residential / office buildings). The larger bandwidth available for NR in mmWave spectrum provides opportunities for self-backhauling without limiting the spectrum to be used for the access link. In addition to this, the inherent multi-beam and multiple-input multiple-output (MIMO) support in NR reduces cross-link interference between the backhaul and the access link, allowing higher densification.

[0003] During the study item phase of the IAB work (a summary of which can be found in the technical report 3GPP TR 38.874 v.16.0.0), it was agreed to adopt a solution that leverages NR’s Central Unit (CU) / Distributed Unit (DU) split architecture, where the IAB nodes will host the DU portion controlled by the Central Unit. The IAB nodes will also have a Mobile Terminating (MT) portion that they use to communicate with their parent node.

[0004] The specifications for IAB strive to reuse existing functions and interfaces defined in NR. Specifically, the Mobile Transport (MT), gNodeB-DU (gNB-DU), gNodeB-CU (gNB-CU), User Plane Function (UPF), Access and Mobility Management Function (AMF), Session Management Function (SMF), and the corresponding NR interfaces Uu (between MT and gNB), F1, NG, X2, and N4 are used as the baseline for the IAB architecture. Modifications or enhancements to these functions and interfaces to support IAB are explained in the context of the architecture discussion. Additional functionality, such as multi-hop forwarding, is included in the architecture discussion because it is essential to understanding IAB operation and because specific aspects may require standardization.

[0005] The MT functionality has been defined as a component of the IAB node. In the context of this study, the MT is referred to as a function residing on the IAB node that terminates the radio interface layer of the backhaul Uu interface towards the IAB donor or other IAB nodes.

[0006] Figure 1 A reference diagram for the IAB in standalone mode is shown, consisting of an IAB donor and multiple IAB nodes. The IAB donor is considered a single logical node that includes a set of functions, such as the gNB-DU, gNB-CU-CP, gNB-CU-UP, and potentially other functions. In a deployment, the IAB donor can be partitioned according to these functions, which can all be co-located or non-co-located, as allowed by the 3GPP NG-RAN architecture. When performing such a partitioning, IAB-related aspects may arise. In addition, some functions currently associated with the IAB donor may eventually be moved outside the donor if they clearly do not perform IAB-specific tasks.

[0007] Figure 2 shows the baseline user plane protocol stack of IAB, and Figure 3A 、 3B Figures 3 and 3C show the baseline control plane protocol stack for IAB. As shown, the chosen protocol stack reuses the current CU-DU separation specification in Rel-15, where the full user plane F1-U (GTP-U / UDP / IP) terminates at the IAB node (just like a normal DU), and the full control plane F1-C (F1-AP / SCTP / IP) also terminates at the IAB node (just like a normal DU). In this case, Network Domain Security (NDS) has been adopted to protect both UP and CP traffic (IPsec in the case of UP and DTLS in the case of CP). IPsec can also be used for CP protection instead of DTLS (in which case the DTLS layer will not be used).

[0008] A new protocol layer called Backhaul Adaptation Protocol (BAP) is introduced in IAB nodes and IAB donors. BAP is used to route packets to appropriate downstream / upstream nodes and is also used to map UE bearer data to appropriate backhaul RLC channels (and between ingress and egress backhaul RLC channels in intermediate IAB nodes) to meet the end-to-end QoS requirements of the bearer.

[0009] At the RAN2 105th meeting, the modeling of the adaptation layer was discussed and the following was agreed upon:

[0010] RAN2 confirms routing and bearer mapping (e.g. mapping of backhaul (BH) radio link control (RLC) channels) is an adaptation layer function

[0011] R2 assumes that the transmit (TX) part of the adaptation layer performs routing and "bearer mapping", and the receive (RX) part of the adaptation layer performs "bearer demapping"

[0012] • R2 assumes that for packets relayed by an IAB node, the SDU is forwarded from the receive part of the adaptation layer to the transmit part of the adaptation layer (for the next hop).

[0013] For further study (FFS): How to model the protocol entities, e.g. whether to model the DU and MT separately; and For further study: How to configure these protocol entities, e.g. using F1-AP or RRC.

[0014] Several other agreements related to the BAP layer were reached in subsequent RAN2 meetings, which are shown below:

[0015] BAP has a DU part configured by F1-AP and an MT part configured by RRC.

[0016] The BAP DU part and the MT part each have a transmitter and a receiver.

[0017] • BAP Routing ID (carried in the BAP header) includes the BAP Address and the BAP Path ID.

[0018] • Each BAP address defines a unique destination (unique to the IAB network of one donor (IAB Access Node or IAB Donor)).

[0019] Each BAP address can have one or more entries in the routing table to enable local routing. Multiple entries are used for load balancing and rerouting in case of RLF. For load balancing, what is decided locally and / or by the IAB donor CU is still for further study.

[0020] • Each BAP routing ID has only one entry in the routing table.

[0021] The BAP address of the IAB node is used to distinguish the traffic to be delivered to the upper layer from the traffic to be delivered to the egress RLC layer (for the donor node, this is for further study).

[0022] For the routing and bearer mapping of packets obtained from the RLC layer, the IAB node needs to be configurable with the following mappings:

[0023] o BAP Routing ID in the BAP header egress link (routing table)

[0024] o Ingress RLC channel Egress RLC channel (bearer mapping)

[0025] For the selection / addition of BAP routing IDs and routing and bearer mapping of packets obtained from upper layers, IAB nodes and IAB donors need to be configurable with the following mappings:

[0026] o (For further study) Upper layer information to be added to the BAP routing ID in the BAP header

[0027] o BAP Routing ID egress link in the BAP header

[0028] o Upper layer information (for further study) egress RLC channel

[0029] Furthermore, when it comes to the BAP header, the following agreement was reached during the second session of RAN2 107th meeting:

[0030] The routing ID is 13 digits.

[0031] There is a C / D position.

[0032] • The length of the BAP address and the BAP routing ID subfield to be fixed / predefined.

[0033] • For DL, the BAP address is 10 bits and the BAP path ID is 3 bits.

[0034] For UL, the number of BAP address bits is for further study, and the number of BAP path ID bits is for further study.

[0035] • R2 expects that there are no restrictions in TS that limit the configuration of Route ID and its components.

[0036] The network must ensure, for example, that there is no path confusion.

[0037] However, the second meeting agreement of RAN2 meeting 107 related to BAP routing ID was overwritten by the following agreement at RAN2 meeting 108:

[0038] For both UL and DL, the BAP header of a data PDU is 3B in length, which contains 1 D / C bit, 3 R bits, 10 BAP address bits and 10 BAP path ID bits (this covers the previous protocol).

[0039] Figure 4 A sample header of a data PDU is shown, where the MSB indicates whether it is a control header or a data header, followed by several reserved bits for flags and future compatibility.

[0040] Intra-donor routing and BH RLC channel configuration

[0041] The second session of RAN3 103rd meeting reached the following agreement related to 1:1 mapping between UE DRBs and BH RLC channels:

[0042] • For 1:1 mapping, confirm that the GTP tunnel ID is used to identify the DRB between the donor CU and the donor DU.

[0043] Solution (WA): Use IPv6 flow labels for 1:1 mapping; whether to also use DSCP is for further study.

[0044] Bearer mapping was further discussed at RAN3 104th meeting, resulting in the following agreement:

[0045] • Use IPv6 flow labels for 1:1 mapping (combined with IAB node IP addresses); does not exclude the use of additional information to differentiate bearers.

[0046] • Solution: For N:1 mapping, both DSCP based mapping and IPv6 flow label based mapping can be used in the donor DU for DL.

[0047] Solution: They can coexist in the same network.

[0048] RAN3 meeting 105 reached additional agreements related to routing and bearer mapping configuration, which are listed below:

[0049] On DL, the IAB donor DU may be configured with information that allows

[0050] C and non-F1 service IP header information derive BAP routing ID.

[0051] On DL, the IAB donor DU may be configured with a mapping that allows

[0052] The IP header information of C and non-F1 services derives the BH RLC channel.

[0053] • On the DL, the IAB donor may be configured with information that allows the BAP address to be derived from the destination IP address.

[0054] • The IAB Donor DU may be configured with a mapping between IPv6 flow label, DS information and destination IP address to BH RLC channel, where any of these three IP header fields is optional in the mapping.

[0055] • The configuration of DL F1-U GTP-U tunnel information on CU-UP is extended to optionally include IPv6 flow label and / or DS information.

[0056] • The extent to which the configuration of DL X2-U and Xn-U GTP-U tunnel information on the MN is extended to optionally include IPv6 flow labels and / or DS information is for further study.

[0057] The second session of RAN3's 105th meeting discussed BAP uplink bearer mapping and intra-BAP donor configuration, and agreed on the following:

[0058] UL mapping is to configure the mapping between GTP-U FTEID (IP address + TEID) and the export backhaul RRC channel

[0059] Solution: We support one-step UL mapping (for F1-U and F1-C)

[0060] Configuration of downlink bearer mapping and routing should be performed by F1-AP

[0061] Path ID is derived from the IP header and mapping provided by the CU

[0062] In DL, for BAP Path ID derivation on donor DU: IP address, IPv6 flow class and / or DS / DSCP can be used; all these fields are optional in F1AP messages used to configure routing

[0063] In summary, RAN3 has agreed that the IP address fields of the F1-AP (e.g., IPv6 flow label, DS / DSCP) can be used to configure the BH RLC channel for the UE bearer in the BAP layer of the IAB donor DU. Similarly, the IP address, IPv6 flow label (optional), and DS / DSCP (optional) of the destination IAB node can be used to derive / configure the BAP path ID for downlink traffic.

[0064] There are certain challenges currently. For example, when scheduling resources for multiple UE bearers, the IAB network should attempt to meet QoS requirements as well as apply appropriate fairness schemes. In cases where a UE bearer must meet strict QoS requirements, it can be mapped 1:1 to a BH RLC channel. Because the BH RLC channel can be configured with the QoS profile of the UE bearer, the scheduler can enforce the necessary QoS requirements. When it comes to N:1 bearer mapping, where multiple UE bearers are mapped to the same BH RLC channel, the scheduler of the intermediate IAB node needs to take into account, among other things, the number of UE bearers carried on each BH RLC channel to fairly share the resources of that channel between the multiple UE bearers carried on their backhaul links. However, the existing 3GPP specifications (i.e., Rel 16) do not provide any mechanism that the IAB node scheduler can use to obtain this information. Summary of the Invention

[0065] Certain aspects of the present disclosure and its embodiments can provide solutions to these and other challenges. For example, a method is proposed herein that uses the BAP Path ID field to convey the number of UE bearers mapped to a given BH RLC channel. This can enable schedulers of intermediate IAB nodes to be informed of the number of UE bearers carried on their backhaul links and, therefore, to apply fair scheduling that takes this into account.

[0066] According to certain embodiments, a method of a network node includes obtaining a number of paths between the network node and at least one IAB node. The network node determines a number of bearers associated with each of the number of paths. For each path, the network node assigns a path identifier value based on at least one of the number of paths and a number of bearers associated with each path.

[0067] According to certain embodiments, a network node includes processing circuitry configured to obtain a number of paths between the network node and at least one IAB node and determine a number of bearers associated with each of the number of paths. For each path, the processing circuitry is configured to assign a path identifier value based on the number of paths and the number of bearers associated with each path.

[0068] According to certain embodiments, a method of a first network node includes: receiving a packet including a header from a second network node. The header includes a path identifier value. Based on the path identifier value, the first network node determines a plurality of bearers associated with the path. Based on the plurality of bearers associated with the path, the first network node allocates at least one resource to the packet. The first network node transmits the packet to a third network node based on the at least one resource.

[0069] According to certain embodiments, a first network node includes processing circuitry configured to: receive a packet including a header from a second network node. The header includes a path identifier value. Based on the path identifier value, the processing circuitry is configured to: determine a plurality of bearers associated with the path. Based on the plurality of bearers associated with the path, the processing circuitry is configured to: allocate at least one resource to the packet. The first network node transmits the packet to a third network node based on the at least one resource.

[0070] Certain embodiments can provide one or more technical advantages. For example, some embodiments can facilitate an IAB node scheduler to improve topology-wide fairness and congestion control. As another example, some embodiments can facilitate an IAB node to remap the BH RLC channels of a BH link with RLF to appropriate BH-RLC channels on an alternative BH link (in terms of their QoS requirements). As another example, some embodiments can use less signaling overhead, or even require no signaling for some network scenarios (i.e., when there is a single path toward each IAB node in the network). BRIEF DESCRIPTION OF THE DRAWINGS

[0071] For a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, in which:

[0072] Figure 1 A reference diagram of IAB in standalone mode is shown, which includes an IAB donor and multiple IAB nodes;

[0073] Figure 2 shows the baseline user plane protocol stack of IAB;

[0074] Figure 3A 、 3B and 3C show the baseline control plane protocol stack of IAB;

[0075] Figure 4 is a sample header of a data PDU;

[0076] Figure 5 is an example of an IAB network according to certain embodiments;

[0077] Figure 6 is another example of an IAB network according to certain embodiments;

[0078] Figure 7 An example wireless network according to certain embodiments is shown;

[0079] Figure 8 shows an example network node according to certain embodiments;

[0080] Figure 9 An example wireless device according to certain embodiments is shown;

[0081] Figure 10 illustrates an example user device according to certain embodiments;

[0082] Figure 11 illustrates a virtualization environment in which functionality implemented by some embodiments may be virtualized according to certain embodiments;

[0083] Figure 12shows a telecommunications network connected to a host computer via an intermediary network according to certain embodiments;

[0084] Figure 13 A general block diagram illustrating a host computer communicating with a user device via a base station over a partially wireless connection in accordance with certain embodiments;

[0085] Figure 14 A method implemented in a communication system according to one embodiment is shown;

[0086] Figure 15 Another method implemented in a communication system according to one embodiment is shown;

[0087] Figure 16 Another method implemented in a communication system according to one embodiment is shown;

[0088] Figure 17 Another method implemented in a communication system according to one embodiment is shown;

[0089] Figure 18 A wireless network including different devices connected directly or indirectly to the wireless network through one or more access network nodes is shown according to certain embodiments;

[0090] Figure 19 An example method of a network node according to certain embodiments is shown;

[0091] Figure 20 Another example method of a network node according to certain embodiments is shown;

[0092] Figure 21 An exemplary virtual computing device according to certain embodiments is shown;

[0093] Figure 22 Another example method of a network node according to certain embodiments is shown; and

[0094] Figure 23 Another exemplary virtual computing device is shown in accordance with certain embodiments. DETAILED DESCRIPTION

[0095] Some embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. However, other embodiments are within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided merely as examples to convey the scope of the subject matter to those skilled in the art. Furthermore, it should be noted that the terms "BAP address" and "BAP routing ID" are used interchangeably. Similarly, the terms "UE bearer" and "UE DRB" are used interchangeably.

[0096] Generally, all terms used in this article will be interpreted according to their ordinary meaning in the relevant technical field, unless clearly given and / or implied different meanings in the context of using the term. Unless explicitly stated, all references to one / an / this element, device, assembly, part, step, etc. should be openly interpreted as referring to at least one instance of this element, device, assembly, part, step, etc. Unless explicitly described as a step after or before another step and / or implicitly a step must be after or before another step, the steps of any method disclosed herein do not have to be performed in the exact order disclosed. Where appropriate, any feature of any embodiment disclosed herein may be applied to any other embodiment. Likewise, any advantage of any embodiment may be applicable to any other embodiment, and vice versa. By the following description, other purposes, features and advantages of the attached embodiments will be apparent.

[0097] BAP Path ID field used to transmit additional information

[0098] Among other things, this document discloses a method at the IAB network level that utilizes the 10-bit BAP Path ID field in the BAP header to convey additional information (besides the path ID), such as the number of UE DRBs mapped to a specific BH RLC channel for N:1 mapping scenarios. Some embodiments divide the BAP Path ID space into different intervals based on the maximum number of paths configured between the IAB donor DU and the IAB node. According to certain specific embodiments, these intervals can be of equal or unequal size, depending on the network implementation.

[0099] According to a specific embodiment, if there are at most K (assuming K=4) paths between the IAB donor DU and the IAB node, the BAP path ID space can be divided into K intervals, where each interval has a value of (2 10 ) / 4=256 address spaces, the first interval has values ​​0 to 255, the second interval has values ​​256 to 511, the third interval has values ​​512 to 767, and the fourth interval has values ​​768 to 1023. That is, for any K, the length of each path space is 2 10 / K (hereinafter denoted as p), and for each path k (k∈{0..K-1}), the possible values ​​range from p*k to p*(k+1)-1.

[0100] According to certain embodiments, within each interval, the path ID may be interpreted in the same manner from a routing perspective (e.g., for the example above, any packet arriving at an intermediate IAB node with a path ID between 0 and 255 and having the same destination BAP address will be routed in the same manner (i.e., according to the routing configuration for the first path)). However, different values ​​may provide additional information regarding how many bearers / UEs are terminated at the destination IAB node or the corresponding ingress backhaul channel on which the packet was received. For example, a path ID of 0 may be used to indicate that only one UE bearer is terminated at the destination IAB node or the associated BH channel, a path ID of 1 may be used to indicate two bearers, and so on. In one implementation, instead of a bearer, a number may represent the number of users, or some combination of the two.

[0101] Figure 5 An example of an IAB network is shown in accordance with certain embodiments. Figure 6 Another example of an IAB network according to certain embodiments is shown. More specifically, Figure 5 and 6 It shows that the UE's DRB is mapped N:1 on the backhaul RLC channel. Figure 5 In , each IAB node can be accessed via a unique physical path, while in Figure 6 In the example, the IAB node 4 can be accessed via two paths, namely, path A (via IAB donor - IAB1 - IAB2 - IAB4) and path B (via IAB donor - IAB1 - IAB3 - IAB4).

[0102] Table 1 shows how the mapping can be performed in the BAP layer of the IAB donor node (for Figure 5 Assume that based on the information in the IP address field (i.e., DS / DSCP) of the F1-AP signaling received from the IAB donor CU (which is based on the QoS requirements of each bearer, since it is reasonable to assume that bearers with similar QoS requirements are mapped to the same BH RLC channel configured to suit the QoS requirements of these bearers), the IAB donor DU maps the DRBs of UE1, UE2, UE8, UE9, and UE12 to BH RLC channel A on its egress BH link with IAB node 1. Similarly, the DRBs of UE3, UE4, and UE5 are mapped to BH RLC channel B, while the DRBs of UE6, UE7, UE10, and UE11 are mapped to BH RLC channel C. Finally, the DRBs of UE12, UE13, UE14 are mapped to BH RLC channel D.

[0103] According to certain embodiments, to indicate information to downstream IAB nodes (i.e., the BH RLC channel shared between UE DRBs), the IAB donor DU increments the BAP Path ID value by the number of DRBs sharing a particular BH RLC channel. For example, BH RLC channel A between the donor node and IAB node 1 is used to transport five bearers (for UE1, UE2, UE8, UE9, and UE12), BH RLC channel A between IAB node 1 and IAB node 2 is used to transport three bearers (for UE8, UE9, and UE12), and so on. Because there is only one path for each IAB node, any value between 0 and 1023 can be used for the Path ID without causing routing issues in intermediate IAB nodes (because the destination BAP address will uniquely determine where the packet should be routed). In the example scenario, the IAB donor assigns a BAP Path ID value of 5 (i.e., equal to the number of bearers multiplexed on that BH RLC channel) to the packet it is mapping to BH RLC channel A, as shown in the table. Similarly, for the other BH RLC channels between the donor and IAB node 1, path ID values ​​3, 4, and 2 correspond to the number of bearers mapped on these channels.

[0104] When an intermediate IAB node acquires a packet, the packet is either destined for those intermediate IAB nodes (i.e., a UE served by those intermediate IAB nodes or traffic destined for the IAB node) or forwarded to another IAB node. Because the intermediate IAB node knows how many bearers it terminates and how many bearers it carries on the ingress backhaul channel, the intermediate IAB node can modify the path ID before forwarding the packet to the next node to account for the number of bearers terminated by the intermediate IAB node. For example, when IAB node 1 acquires a packet destined for IAB4 or IAB5 on backhaul RLC channel A (whose path ID would be 5), IAB node 1 knows that on the next hop (multi-hop), the packet will be carried along with two other bearers (i.e., a total of five bearers on the ingress BH RLC channel, two terminated at IAB node 1, and three that must traverse the next hop associated with the destination BAP address of IAB4 or IAB5). Therefore, IAB node 1 updates the BAP path ID value of the packet it is forwarding to IAB node 3 to 3. However, for packets received via BH RLC channel B (which only carries traffic for bearers terminating at IAB4), since none of them terminate at IAB1, IAB node 1 does not generate a path ID when forwarding the packet. The same is true for packet traffic from BH RLC channels C and D between the donor and IAB node 1. Therefore, packets received on the DU side of IAB node 1 will have the following path IDs (for the link between IAB1 and IAB3): 3 for the first BH RLC channel (corresponding to bearers for UEs 8, 9, and 12); 4 for the next RLC channel (corresponding to bearers for UEs 6, 7, 10, and 11); and 2 for bearers for UEs 13 and 14. Therefore, IAB node 1 can use this information to schedule packets in a fair manner. For example, the QoS setting for BH RLC channel C, which only carries two bearers, can be higher than the QoS setting for BH RLC channel B, which carries four bearers. If only QoS settings were used to prioritize the scheduling of traffic, more users might experience greater delays. Therefore, one example implementation may be to increase / decrease scheduling priorities among different backhaul RLC channels according to the number of bearers (or UEs) multiplexed on these backhaul RLC channels (in addition to the QoS settings of the BH RLC channels).

[0105] According to a specific embodiment, the number of hops may be conveyed using known methods or using a BAP address for the number of hops. The number of hops that a packet must traverse may be made available at an intermediate IAB node, either implicitly or explicitly. Such information may also be used in addition to the number of bearers. For example, even though multiple bearers may be multiplexed on a given BH RLC channel, if most of these bearers terminate at just the next IAB node, then that given BH RLC channel may be assigned a lower scheduling priority than a channel that has fewer bearers multiplexed on it but whose bearers terminate a few hops away. In general, the scheduler at the intermediate IAB node may be described as employing a scheduling algorithm that attempts to achieve fairness when scheduling data belonging to different BH RLC channels by taking into account one or more of the following:

[0106] -The number of UEs mapped on each BH RLC channel

[0107] -The number of bearers mapped on each BH RLC channel

[0108] - How many hops the data belonging to each bearer / BH RLC channel has to go through before it reaches its destination

[0109] Similar path ID updates may be performed at each intermediate IAB node (ie, each IAB node subtracts the number of bearers that the IAB node is terminating from the path ID of the ingress BHRLC channel).

[0110] Table I: For Figure 5 Routing and bearer mapping configuration in the IAB donor node

[0111]

[0112] for Figure 6 In the case of IAB Node 4, IAB Node 5 and IAB Node 6, since there are two possible paths, the path ID space can be divided into multiple partitions, i.e., 0 to 511 for the first path (referred to as path A) and 512 to 1023 for the second path (referred to as path B). Table II shows how the mapping can be performed in the BAP layer of the IAB donor node (for Figure 6Here, the UE8 DRB of IAB node 4 is mapped from the IAB donor node to BH RLC channel A on path A, while the UE9 DRB of IAB node 4 is mapped to BH RLC channel B on path B. Because the UE8 DRB is mapped to BH RLC channel A (on path A), and BH RLC channel A transmits a total of 7 UE DRBs (i.e., UE1, UE2, UE6, UE7, UE8, UE10, and UE11), the path ID of the UE8 DRB is set to 7 (i.e., path ID 0+7). Similarly, for the UE9 DRB, the path ID is set to 519 (i.e., path ID 512+7) because the UE9 DRB is mapped to a BH RLC channel on path B (i.e., BH RLC channel B), and the BH RLC channel transmits a total of 8 UE DRBs (i.e., UE3, UE4, UE5, UE9, UE12, UE13, UE14, and UE15). Similarly, UE10 DRB and UE11 DRB served by IAB node 5 are mapped to BH RLC channel A on path A, while UE12 DRB and UE13 DRB served by the same IAB node (i.e., IAB node 5) are mapped to BH RLC channel B on path B. Therefore, the BAP path ID of the BAP PDU of these DRBs is set according to the path and the number of DRBs sharing the BH RLC channel, as shown in Table II below.

[0113] Table II: For Figure 6 Routing and bearer mapping configuration in the IAB donor node

[0114]

[0115] In some embodiments, the IAB donor DU will increment the BAP path ID by taking into account both the BAP address and the allocated / mapped BH RLC channel. For example, UE1 and UE2 DRBs of IAB node 1 are mapped to BH RLC channel A, therefore, the BAP path ID of the packets carrying traffic for these DRBs will be incremented by 2 (i.e., the BAP path ID will be set to 2 as shown in Table III below). Similarly, the BAP path ID of UE8 and UE9 DRBs of IAB node 4 mapped to BH RLC channel A will be set to 2, while the BAP path ID of UE12 DRB of IAB node 5 mapped to BH RLC channel A will be set to 1. In this sub-case, the intermediate IAB nodes will keep track of the number of UE DRBs mapped to the BH RLC channel by checking the BAP path ID values ​​for different BAP addresses mapped to the BH RLC channel. For example, IAB node 1 (at Figure 5) Upon receiving a packet with BAP address BAP4 (BAP path ID 2) and BAP address BAP5 (BAP path ID 1) on the ingress BH RLC channel A, IAB node 1 will know that its egress BH RLC channel A will be shared by a total of 3 UE DRBs and can therefore provide appropriate QoS treatment when scheduling traffic on its egress BH link.

[0116] Table III: For Figure 5 Routing and bearer mapping configuration in the IAB donor node

[0117]

[0118] Note that in the above method, for a network with a single path to an IAB node, a maximum of 1024 UE DRBs can be mapped to a BH RLC channel, and for a network with two paths to an IAB node, a maximum of 512 UE DRBs can be mapped to a BH RLC channel, and so on. However, if more than 1024 UE DRBs are mapped to a BH RLC channel, then in this case, an increment of 1 in the BAP path ID will indicate that more than one UE DRB (depending on the maximum number of UE DRBs mapped to a BH RLC channel. For example, for 2048 UE DRBs mapped to a BH RLC channel, an increment of 1 in the BAP path ID will indicate that 2 UE DRBs are mapped to a BH RLC channel, and so on) is mapped to a BH RLC channel. The same process also applies to the method described in the sub-embodiments of the present invention.

[0119] In some embodiments, because the mapping will be performed at the IAB donor DU, the DU needs to know the number of available or configured paths in order to adjust the DU's mapping process. The IAB donor CU will provide this information to the DU. In addition, if the IAB donor DU uses an increment of 1 in the BAP Path ID to indicate more than one UE DRB mapped to the BH RLC channel, the intermediate IAB nodes should be notified of this so that the intermediate IAB nodes can reduce the BAP Path ID accordingly for the UE DRBs terminating at the intermediate IAB nodes. The intermediate IAB nodes can be notified via the IAB donor CU or via OAM. These intermediate IAB nodes can be notified only when the increment of 1 in the BAP Path ID indicates more than one UE DRB (rather than for the default case (i.e., when the increment of 1 in the BAP Path ID indicates only one UE DRB)). Alternatively, the intermediate IAB nodes can be notified for all cases.

[0120] Although the subject matter described herein may be implemented in any suitable type of system using any suitable components, the embodiments disclosed herein are directed to wireless networks such as Figure 7 For simplicity, Figure 7 The wireless network shown in FIG. 1 depicts only network 106, network nodes 160 and 160b, and wireless device (WD) 110. In practice, a wireless network may also include any additional elements suitable for supporting communication between wireless devices or between a wireless device and another communication device (e.g., a landline phone, a service provider, or any other network node or terminal device). Of the components shown, network node 160 and WD 110 are depicted in additional detail. A wireless network may provide communication and other types of services to one or more wireless devices to facilitate access and / or use by the wireless device of services provided by or via the wireless network.

[0121] A wireless network can include and / or be connected to any type of communication, telecommunication, data, cellular, and / or radio network or other similar type of system. In some embodiments, a wireless network can be configured to operate according to a particular standard or other type of predefined rules or procedures. Thus, particular embodiments of a wireless network can implement: communication standards such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards such as IEEE 802.11 standards; and / or any other suitable wireless communication standards such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, and / or ZigBee standards.

[0122] The network 106 may include one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks that enable communication between devices.

[0123] The network node 160 and the WD 110 include various components described in more detail below. These components work together to provide network node and / or wireless device functionality, such as providing wireless connectivity in a wireless network. In various embodiments, a wireless network may include any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals (whether via a wired or wireless connection).

[0124] Figure 8An example network node 160 according to a particular embodiment is shown. As used herein, a network node refers to a device that is capable of, configured, arranged, and / or operable to communicate directly or indirectly with a wireless device and / or with other network nodes or devices in a wireless network to enable and / or provide wireless access to the wireless device and / or perform other functions (e.g., management) in the wireless 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)). Base stations can be categorized based on the amount of coverage they provide (or in other words, their transmit power class), and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node 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 also 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. Part of a distributed radio base station may also be referred to as a node in a distributed antenna system (DAS). Other examples of network nodes include MSR devices such as multi-standard radio (MSR) BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), core network nodes (e.g., mobile switching centers (MSCs), mobility management entities (MMEs)), operations and maintenance (O&M) nodes, operations support system (OSS) nodes, self-optimizing networks (SON) nodes, positioning nodes (e.g., evolved serving mobile positioning centers (E-SMLCs)), and / or minimization of drive tests (MDTs). As another example, a network node may be a virtual network node as described in more detail below. However, more generally, a network node may represent any suitable device (or group of devices) capable of, configured, arranged, and / or operable to enable and / or provide access to a wireless network by a wireless device or to provide a service to a wireless device that has accessed the wireless network.

[0125] exist Figure 8 In FIG, the network node 160 includes a processing circuit 170, a device readable medium 180, an interface 190, an auxiliary device 184, a power supply 186, a power supply circuit 187, and an antenna 162. Figure 8The network node 160 shown in the example wireless network of FIG. 1 may represent a device that includes the combination of hardware components shown, but other embodiments may include network nodes with different combinations of components. It should be understood that the network node includes any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. Furthermore, although the components of the network node 160 are depicted as a single box within a larger box or nested within multiple boxes, in reality, the network node may include multiple different physical components that make up the single illustrated component (e.g., the device readable medium 180 may include multiple separate hard drives and multiple RAM modules).

[0126] Similarly, network node 160 may include multiple physically separate components (e.g., a Node B component and an RNC component, or a BTS component and a BSC component, etc.), each of which may have its own corresponding components. In some cases where network node 160 includes multiple separate components (e.g., a BTS and a BSC component), one or more of the separate components may be shared among 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 a single, separate network node. In some embodiments, network node 160 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be replicated (e.g., separate device-readable media 180 for different RATs), while some components may be reused (e.g., the same antenna 162 may be shared by all RATs). Network node 160 may also include various sets of exemplary components for different wireless technologies integrated into network node 160 (e.g., GSM, WCDMA, LTE, NR, Wi-Fi, or Bluetooth wireless technologies). These wireless technologies may be integrated into the same or different chips or chipsets as other components within network node 160.

[0127] The processing circuit 170 is configured to perform any determination, calculation, or similar operation (e.g., certain obtaining operations) described herein as provided by the network node. These operations performed by the processing circuit 170 may include: processing information obtained by the processing circuit 170, for example, by converting the obtained information into other information, comparing the obtained information or the converted information with 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.

[0128] The processing circuitry 170 may include a combination of one or more of 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 operable to provide network node 160 functionality, either alone or in conjunction with other network node 160 components (e.g., device-readable medium 180). For example, the processing circuitry 170 may execute instructions stored in the device-readable medium 180 or in a memory within the processing circuitry 170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, the processing circuitry 170 may include a system-on-chip (SOC).

[0129] In some embodiments, processing circuitry 170 may include one or more of radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174. In some embodiments, radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174 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 172 and baseband processing circuitry 174 may be on the same chip or chipset, board, or unit.

[0130] In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB, or other such network device may be performed by processing circuitry 170 executing instructions stored on a device-readable medium 180 or a memory within processing circuitry 170. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 170 without, for example, hard-wired execution of instructions stored on a separate or discrete device-readable medium. In any of these embodiments, processing circuitry 170 can be configured to perform the described functionality regardless of whether or not executing instructions stored on a device-readable storage medium. The benefits provided by such functionality are not limited to processing circuitry 170 or other components of network node 160, but are enjoyed by network node 160 as a whole and / or by end users and the wireless network in general.

[0131] Device-readable medium 180 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., a hard disk), removable storage media (e.g., a flash drive, a compact disk (CD), or a digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory, device-readable and / or computer-executable storage device that stores information, data, and / or instructions that may be used by processing circuit 170. Device-readable medium 180 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 are executable by processing circuit 170 and utilized by network node 160. Device-readable medium 180 may be used to store any computations performed by processing circuit 170 and / or any data received via interface 190. In some embodiments, processing circuit 170 and device-readable medium 180 may be considered integrated.

[0132] Interface 190 is used for wired or wireless communication of signaling and / or data between network node 160, network 106, and / or WD 110. As shown, interface 190 includes ports / terminals 194 for sending and receiving data to and from network 106, for example, via a wired connection. Interface 190 also includes radio front-end circuitry 192, which can be coupled to antenna 162 or, in some embodiments, form part of antenna 162. Radio front-end circuitry 192 includes filters 198 and amplifiers 196. Radio front-end circuitry 192 can be connected to antenna 162 and processing circuitry 170. Radio front-end circuitry 192 can be configured to condition signals transmitted between antenna 162 and processing circuitry 170. Radio front-end circuitry 192 can receive digital data to be transmitted to other network nodes or WDs via wireless connections. Radio front-end circuitry 192 can use a combination of filters 198 and / or amplifiers 196 to convert the digital data into a radio signal with appropriate channel and bandwidth parameters. The radio signal can then be transmitted via antenna 162. Similarly, when receiving data, antenna 162 may collect radio signals, which may then be converted into digital data by radio front-end circuitry 192. The digital data may be passed to processing circuitry 170. In other embodiments, the interface may include different components and / or different combinations of components.

[0133] In certain alternative embodiments, the network node 160 may not include a separate radio front end circuitry 192, and instead, the processing circuitry 170 may include the radio front end circuitry and may be connected to the antenna 162 without the separate radio front end circuitry 192. Similarly, in some embodiments, all or a portion of the RF transceiver circuitry 172 may be considered part of the interface 190. In other embodiments, the interface 190 may include one or more ports or terminals 194, the radio front end circuitry 192, and the RF transceiver circuitry 172 as part of a radio unit (not shown), and the interface 190 may communicate with the baseband processing circuitry 174 that is part of a digital unit (not shown).

[0134] Antenna 162 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals. Antenna 162 may be coupled to radio front-end circuitry 190 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna 162 may include one or more omnidirectional, sectored, or flat panel antennas operable to transmit / receive radio signals between, for example, 2 GHz and 66 GHz. Omnidirectional antennas can be used to transmit / receive radio signals in any direction, sectored antennas can be used to transmit / receive radio signals from devices within a specific area, and flat panel antennas can be line-of-sight antennas for transmitting / receiving radio signals in relatively straight lines. In some cases, the use of more than one antenna may be referred to as MIMO. In some embodiments, antenna 162 may be separate from network node 160 and may be connected to network node 160 via an interface or port.

[0135] Antenna 162, interface 190 and / or processing circuit 170 can be configured to perform any receive operation and / or certain obtain operations described herein as being performed by a network node. Any information, data and / or signal can be received from a wireless device, another network node and / or any other network device. Similarly, antenna 162, interface 190 and / or processing circuit 170 can be configured to perform any transmit operation described herein as being performed by a network node. Any information, data and / or signal can be sent to a wireless device, another network node and / or any other network device.

[0136] Power circuit 187 may include or be coupled to power management circuitry and is configured to provide power to the components of network node 160 for performing the functions described herein. Power circuit 187 may receive power from power source 186. Power source 186 and / or power circuit 187 may be configured to provide power to the various components of network node 160 in a form appropriate for the respective components (e.g., at the voltage and current levels required by each respective component). Power source 186 may be included in power circuit 187 and / or network node 160 or external thereto. For example, network node 160 may be connected to an external power source (e.g., a power outlet) via an input circuit or interface (e.g., a cable), whereby the external power source provides power to power circuit 187. As another example, power circuit 186 may include a power source in the form of a battery or battery pack connected to or integrated into power circuit 187. The battery may provide backup power if the external power source fails. Other types of power sources, such as photovoltaic devices, may also be used.

[0137] Alternative embodiments of network node 160 may include Figure 8 Additional components beyond those shown may be responsible for providing 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, network node 160 may include a user interface device to allow information to be input into network node 160 and to allow information to be output from network node 160. This may allow a user to perform diagnostic, maintenance, repair, and other management functions with respect to network node 160.

[0138] Figure 9An example wireless device (WD) according to a specific embodiment is shown. As used herein, a wireless device (WD) refers to a device that is capable of, configured, arranged and / or operable to wirelessly communicate with a network node and / or other wireless devices. Unless otherwise specified, the term WD may be used interchangeably with user equipment (UE) herein. Wireless communication may involve sending and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves and / or other types of signals suitable for transmitting information over the air. In some embodiments, a WD may be configured to send and / or receive information without direct human interaction. For example, a WD may be designed to send information to a network on a predetermined schedule when triggered by an internal or external event or in response to a request from the network. Examples of WDs include, but are not limited to, smartphones, 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 equipment (LEE), laptop mounted equipment (LME), smart devices, wireless customer premises equipment (CPE), vehicle-mounted wireless terminal devices, etc. WDs can support device-to-device (D2D) communication, for example, by implementing 3GPP standards for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and vehicle-to-everything (V2X), and in this case can be referred to as D2D communication devices. As another specific example, in an Internet of Things (IoT) scenario, a WD can represent a machine or other device that performs monitoring and / or measurement and transmits the results of such monitoring and / or measurement to another WD and / or network node. In this case, the WD can be a machine-to-machine (M2M) device, which can be referred to as an MTC device in the 3GPP context. As a specific example, a WD may be a UE that implements the 3GPP Narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering equipment such as power meters, industrial machinery, or household or personal appliances (e.g., refrigerators, televisions, etc.), personal wearable devices (e.g., watches, fitness trackers, etc.). In other cases, a WD may represent a vehicle or other device that is capable of monitoring and / or reporting its operating status or other functions associated with its operation. A WD as described above may represent an endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or mobile terminal.

[0139] As shown, wireless device 110 includes antenna 111, interface 114, processing circuitry 120, device-readable medium 130, user interface device 132, auxiliary device 134, power supply 136, and power supply circuitry 137. WD 110 may include multiple groups of one or more of the components shown for the different wireless technologies supported by WD 110 (e.g., GSM, WCDMA, LTE, NR, Wi-Fi, WiMAX, or Bluetooth wireless technologies, to name a few). These wireless technologies may be integrated into the same or different chips or chipsets as other components in WD 110.

[0140] Antenna 111 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals and is connected to interface 114. In some alternative embodiments, antenna 111 may be separate from WD 110 and may be connected to WD 110 via an interface or port. Antenna 111, interface 114, and / or processing circuit 120 may be configured to perform any receive or transmit operation described herein as being performed by a WD. Any information, data, and / or signal may be received from a network node and / or another WD. In some embodiments, the radio front-end circuit and / or antenna 111 may be considered an interface.

[0141] As shown, interface 114 includes radio front-end circuitry 112 and antenna 111. Radio front-end circuitry 112 includes one or more filters 118 and amplifier 116. Radio front-end circuitry 114 is connected to antenna 111 and processing circuitry 120 and is configured to condition signals transmitted between antenna 111 and processing circuitry 120. Radio front-end circuitry 112 may be coupled to antenna 111 or may be part of antenna 111. In some embodiments, WD 110 may not include a separate radio front-end circuitry 112; instead, processing circuitry 120 may include radio front-end circuitry and may be connected to antenna 111. Similarly, in some embodiments, part or all of RF transceiver circuitry 122 may be considered part of interface 114. Radio front-end circuitry 112 may receive digital data transmitted via a wireless connection to other network nodes or WDs. Radio front-end circuitry 112 may use a combination of filters 118 and / or amplifiers 116 to convert the digital data into a radio signal with appropriate channel and bandwidth parameters. The radio signal may then be transmitted via antenna 111. Similarly, when receiving data, antenna 111 may collect radio signals, which are then converted into digital data by radio front-end circuitry 112. The digital data may be passed to processing circuitry 120. In other embodiments, the interface may include different components and / or different combinations of components.

[0142] The processing circuit 120 may include a combination of one or more of 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 operable to provide WD 110 functionality, either alone or in combination with other WD 110 components (e.g., device readable medium 130). Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, the processing circuit 120 may execute instructions stored in the device readable medium 130 or in a memory within the processing circuit 120 to provide the functionality disclosed herein.

[0143] As shown, processing circuitry 120 includes one or more of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126. In other embodiments, the processing circuitry may include different components and / or different combinations of components. In some embodiments, processing circuitry 120 of WD 110 may include a system-on-chip (SoC). In some embodiments, RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 may be on separate chips or chipsets. In alternative embodiments, part or all of baseband processing circuitry 124 and application processing circuitry 126 may be combined into a single chip or chipset, while RF transceiver circuitry 122 may be on a separate chip or chipset. In other alternative embodiments, part or all of RF transceiver circuitry 122 and baseband processing circuitry 124 may be on the same chip or chipset, while application processing circuitry 126 may be on a separate chip or chipset. In other alternative embodiments, part or all of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 may be combined into the same chip or chipset. In some embodiments, RF transceiver circuitry 122 may be part of interface 114. RF transceiver circuitry 122 may condition RF signals for processing circuitry 120.

[0144] In some embodiments, some or all of the functions described herein as being performed by the WD may be provided by processing circuitry 120 executing instructions stored on a device-readable medium 130 (which may be a computer-readable storage medium in some embodiments). In alternative embodiments, some or all of the functions may be provided by processing circuitry 120 without, for example, hard-wiring instructions stored on a separate or separate device-readable medium. In any of these specific embodiments, processing circuitry 120 may be configured to perform the described functions regardless of whether instructions stored on a device-readable storage medium are executed. The benefits provided by such functions are not limited to processing circuitry 120 or other components of WD 110, but are enjoyed by WD 110 as a whole and / or by end users and wireless networks in general.

[0145] Processing circuitry 120 may be configured to perform any determinations, calculations, or similar operations (e.g., certain acquisition operations) described herein as being performed by the WD. These operations performed by processing circuitry 120 may include: processing information obtained by processing circuitry 120, for example, by converting the obtained information into other information, comparing the obtained information or the converted information with information stored by WD 110, and / or performing one or more operations based on the obtained information or the converted information; and making determinations as a result of the processing.

[0146] Device-readable medium 130 is operable to store computer programs, software, applications (including one or more of logic, rules, code, tables, etc.), and / or other instructions executable by processing circuitry 120. Device-readable medium 130 may include computer memory (e.g., random access memory (RAM) or read-only memory (ROM), mass storage media (e.g., a hard disk), removable storage media (e.g., a 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 usable by processing circuitry 120. In some embodiments, processing circuitry 120 and device-readable medium 130 may be considered integrated.

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

[0148] Auxiliary devices 134 can be operated to provide more specialized functions that may not typically be performed by a WD. This can include specialized sensors for measuring for various purposes, interfaces for other communication types such as wired communication, etc. The inclusion and types of components of auxiliary devices 134 can vary depending on the embodiment and / or scenario.

[0149] In some embodiments, power source 136 may take the form of a battery or battery pack. Other types of power sources may also be used, such as an external power source (e.g., an electrical outlet), a photovoltaic device, or a battery. WD 110 may also include a power circuit 137 for delivering power from power source 136 to various components of WD 110 that require power from power source 136 to perform any functions described or indicated herein. In some embodiments, power circuit 137 may include power management circuitry. Power circuit 137 may additionally or alternatively be operable to receive power from an external power source. In this case, WD 110 may be connected to an external power source (e.g., an electrical outlet) via an input circuit or interface (e.g., a power cord). In some embodiments, power circuit 137 may also be operable to deliver power from the external power source to power source 136. This may be used, for example, to charge power source 136. Power circuit 137 may perform any formatting, conversion, or other modification of the power from power source 136 to make it suitable for the respective components of WD 110 to which it is being supplied.

[0150] Figure 10 One embodiment of a UE according to various aspects described herein is shown. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and / or operates the associated equipment. 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 specific 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). UE 200 may be any UE identified by the Third Generation Partnership Project (3GPP), including NB-IoT UE, Machine Type Communication (MTC) UE, and / or Enhanced MTC (eMTC) UE. As Figure 10 As shown, UE 200 is an example of a WD that is configured to communicate in accordance with one or more communication standards promulgated by the Third Generation Partnership Project (3GPP), such as 3GPP's GSM, UMTS, LTE, and / or 5G standards. As previously mentioned, the terms WD and UE may be used interchangeably. Figure 10 It is UE, but the components discussed in this article are also applicable to WD and vice versa.

[0151] exist Figure 10In the embodiment, UE 200 includes a processing circuit 201, which is operatively coupled to an input / output interface 205, a radio frequency (RF) interface 209, a network connection interface 211, a memory 215 (including a random access memory (RAM) 217, a read-only memory (ROM) 219, and a storage medium 221, etc.), a communication subsystem 231, a power supply 233 and / or any other components or any combination thereof. The storage medium 221 includes an operating system 223, an application 225, and data 227. In other embodiments, the storage medium 221 may include other similar types of information. Some UEs may utilize Figure 10 All components shown may be used, or only a subset of these components may be used. The level of integration between components may vary from one UE to another. In addition, some UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0152] exist Figure 10 In the embodiment of the present invention, processing circuit 201 can be configured to process computer instructions and data. Processing circuit 201 can be configured to implement any sequential state machine operable to execute machine instructions stored as a machine-readable computer program in memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic and appropriate firmware; one or more stored programs, general-purpose processors (e.g., microprocessors or digital signal processors (DSPs)) and appropriate software; or any combination thereof. For example, processing circuit 201 can include two central processing units (CPUs). Data can be information in a form suitable for use by a computer.

[0153] In the depicted embodiment, the input / output interface 205 may be configured to provide a communication interface to an input device, an output device, or both. The UE 200 may be configured to use an output device via the input / output interface 205. The output device may use the same type of interface port as the input device. For example, a USB port may be used to provide input to or output from the UE 200. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, a transmitter, a smart card, another output device, or any combination thereof. The UE 200 may be configured to use an input device via the input / output interface 205 to allow a user to capture information into the UE 200. The input device may include a touch-sensitive display or a presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a webcam, etc.), a microphone, a sensor, a mouse, a trackball, a steering wheel, a trackpad, a scroll wheel, a smart card, etc. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from the 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, another similar sensor, or any combination thereof. For example, the input device can be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

[0154] exist Figure 10 In the embodiment of the present invention, the RF interface 209 can be configured to provide a communication interface to RF components such as transmitters, receivers and antennas. The network connection interface 211 can be configured to provide a communication interface to the network 243a. The network 243a can include a wired and / or wireless network, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a telecommunications network, another similar network or any combination thereof. For example, the network 243a can include a Wi-Fi network. The network connection interface 211 can be configured to include a receiver and a transmitter interface, which are used to communicate with one or more other devices through the communication network according to one or more communication protocols (such as Ethernet, TCP / IP, SONET, ATM, or Ethernet, etc.). The network connection interface 211 can implement receiver and transmitter functions suitable for a communication network link (such as optical, electrical, etc.). The transmitter and receiver functions can share circuit components, software or firmware, or alternatively can be implemented separately.

[0155] RAM 217 can be configured to be connected to processing circuit 201 via bus 202 to provide storage or caching of data or computer instructions during the execution of software programs such as operating systems, applications, and device drivers. ROM 219 can be configured to provide computer instructions or data to processing circuit 201. For example, ROM 219 can be configured to store unchanging low-level system code or data for basic system functions (e.g., basic input and output (I / O), booting, receiving keystrokes stored in non-volatile memory from a keyboard). Storage medium 221 can be configured to include memories such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cassettes, or flash drives. In one example, storage medium 221 can be configured to include an operating system 223, applications 225 such as a web browser application, a widget or gadget engine, or another application, and data files 227. The storage medium 221 may store any one of various operating systems or a combination of operating systems for use by the UE 200 .

[0156] Storage medium 221 can be configured to include multiple physical drive units, such as a redundant array of independent disks (RAID), a floppy disk drive, a flash memory, a USB flash drive, an external hard 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 disc drive, a holographic digital data storage (HDDS) optical drive, an external mini dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), an external micro-DIMM SDRAM, smart card memory (e.g., a subscriber identity module or a removable user identity (SIM / RUIM) module), other memory, or any combination thereof. Storage medium 221 can allow UE 200 to access computer-executable instructions, applications, etc. stored on a transient or non-transitory storage medium to download or upload data. An article of manufacture, such as one utilizing a communication system, can be tangibly embodied in storage medium 221, which can include device-readable media.

[0157] exist Figure 10In the embodiment of the present invention, the processing circuit 201 can be configured to communicate with the network 243b using the communication subsystem 231. The network 243a and the network 243b can be the same network or different networks. The communication subsystem 231 can be configured to include one or more transceivers for communicating with the network 243b. For example, the communication subsystem 231 can be configured to include one or more transceivers for communicating with one or more remote transceivers of another device (e.g., another WD, UE, or a base station of a radio access network (RAN)) capable of wireless communication according to one or more communication protocols (e.g., IEEE 802.11, code division multiple access (CDMA), wideband code division multiple access (WCDMA), GSM, LTE, universal terrestrial radio access network (UTRAN), WiMax, etc.). Each transceiver can include a transmitter 233 and / or a receiver 235 to respectively implement transmitter or receiver functions (e.g., frequency allocation, etc.) suitable for the RAN link. Furthermore, the transmitter 233 and receiver 235 of each transceiver may share circuit components, software, or firmware, or alternatively may be implemented separately.

[0158] In the illustrated embodiment, the communication functions of the communication subsystem 231 may include 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 to determine location (GPS), another similar communication function, or any combination thereof. For example, the communication subsystem 231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. The network 243b may include a wired and / or wireless network, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a telecommunications network, another similar network, or any combination thereof. For example, the network 243b may be a cellular network, a Wi-Fi network, and / or a near-field network. The power supply 213 may be configured to provide alternating current (AC) or direct current (DC) power to the components of the UE 200.

[0159] The features, benefits, and / or functions described herein may be implemented in one of the components of the UE 200, or may be divided among multiple components of the UE 200. Furthermore, the features, benefits, and / or functions described herein may be implemented in any combination of hardware, software, or firmware. In one example, the communication subsystem 231 may be configured to include any of the components described herein. Furthermore, the processing circuit 201 may be configured to communicate with any such component over the bus 202. In another example, any such component may be represented by program instructions stored in a memory that, when executed by the processing circuit 201, perform the corresponding functions described herein. In another example, the functions of any such component may be divided between the processing circuit 201 and the communication subsystem 231. 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.

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

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

[0162] These functions may be implemented by one or more applications 320 (which may alternatively be referred to as software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operable to implement certain features, functionality, and / or benefits of some embodiments disclosed herein. The applications 320 run in a virtualized environment 300, which provides hardware 330 including processing circuitry 360 and memory 390. The memory 390 contains instructions 395 executable by the processing circuitry 360, whereby the applications 320 are operable to provide one or more features, benefits, and / or functionality disclosed herein.

[0163] The virtualization environment 300 includes general-purpose or specialized network hardware devices 330, which include a set of one or more processors or processing circuits 360, which may be commercial off-the-shelf (COTS) processors, application-specific integrated circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or specialized processors. Each hardware device may include memory 390-1, which may be non-persistent memory for temporarily storing instructions 395 or software executed by the processing circuits 360. Each hardware device may include one or more network interface controllers (NICs) 370 (also known as network interface cards), which include physical network interfaces 380. Each hardware device may also include non-transitory, persistent, machine-readable storage media 390-2 in which software 395 and / or instructions executable by the processing circuits 360 are stored. The software 395 may include any type of software, including software for instantiating one or more virtualization layers 350 (also known as hypervisors), software for executing virtual machines 340, and software that enables them to perform the functions, features, and / or benefits associated with some embodiments described herein.

[0164] The virtual machine 340 includes virtual processing, virtual memory, virtual network or interface, and virtual storage, and can be run by a corresponding virtualization layer 350 or hypervisor. Different embodiments of instances of the virtual device 320 can be implemented on one or more virtual machines 340 and can be implemented in different ways.

[0165] During operation, processing circuitry 360 executes software 395 to instantiate a hypervisor or virtualization layer 350, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 350 may present a virtual operating platform to virtual machines 340 that appears to be networked hardware.

[0166] like Figure 11 As shown, hardware 330 can be a standalone network node with common or specialized components. Hardware 330 can include antenna 3225 and can implement some functions via virtualization. Alternatively, hardware 330 can be part of a larger hardware cluster (e.g., such as in a data center or customer premises equipment (CPE)), where many hardware nodes work together and are managed by management and orchestration (MANO) 3100, which, among other things, oversees the lifecycle management of application 320.

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

[0168] In the context of NFV, a virtual machine 340 can be a software implementation of a physical machine that runs programs as if they were executed on a physical, non-virtual machine. Each virtual machine 340 and the portion of hardware 330 that executes the virtual machine (hardware dedicated to the virtual machine and / or hardware shared by the virtual machine with other virtual machines 340) form a separate virtual network element (VNE).

[0169] Still in the context of NFV, a virtual network function (VNF) is responsible for handling specific network functions running in one or more virtual machines 340 on top of the hardware networking infrastructure 330 and corresponds to Figure 11 Application 320.

[0170] In some embodiments, one or more radio units 3200, each including one or more transmitters 3220 and one or more receivers 3210, may be coupled to one or more antennas 3225. The radio units 3200 may communicate directly with the hardware nodes 330 via one or more appropriate network interfaces, and may be used in combination with virtual components to provide a virtual node with radio capabilities, such as a radio access node or base station.

[0171] In some embodiments, some signaling may be implemented using a control system 3230 , which may alternatively be used for communications between the hardware node 330 and the radio unit 3200 .

[0172] Figure 12 A telecommunications network is shown connected to a host computer via an intermediary network in accordance with certain embodiments.

[0173] refer to Figure 12According to an embodiment, a communications system includes a telecommunications network 410, such as a 3GPP-type cellular network, including an access network 411, such as a radio access network, and a core network 414. Access network 411 includes multiple base stations 412a, 412b, 412c (e.g., NBs, eNBs, gNBs) or other types of wireless access points, each defining a corresponding coverage area 413a, 413b, 413c. Each base station 412a, 412b, 412c can be connected to core network 414 via a wired or wireless connection 415. A first UE 491 located in coverage area 413c is configured to wirelessly connect to or be paged by the corresponding base station 412c. A second UE 492 in coverage area 413a can wirelessly connect to the corresponding base station 412a. Although multiple UEs 491, 492 are shown in this example, the disclosed embodiments are equally applicable to situations where only one UE is in the coverage area or is connected to the corresponding base station 412.

[0174] Telecommunications network 410 itself is connected to a host computer 430, which can be embodied in the hardware and / or software of a standalone server, a cloud-enabled server, a distributed server, or as processing resources in a server farm. Host computer 430 can be under the ownership or control of a service provider, or can be operated by or on behalf of the service provider. Connections 421 and 422 between telecommunications network 410 and host computer 430 can extend directly from core network 414 to host computer 430, or can be via an optional intermediary network 420. Intermediary network 420 can be one of a public, private, or managed network, or a combination of more than one of these; intermediary network 420, if present, can be a backbone network or the Internet; in particular, intermediary network 420 can include two or more subnetworks (not shown).

[0175] Overall, Figure 12The communication system enables connectivity between connected UEs 491, 492 and a host computer 430. This connectivity can be described as an over-the-top (OTT) connection 450. The host computer 430 and the connected UEs 491, 492 are configured to communicate data and / or signaling via the OTT connection 450, using the access network 411, the core network 414, any intermediate networks 420, and possibly other infrastructure (not shown) as intermediaries. The OTT connection 450 can be transparent in the sense that the participating communication devices through which the OTT connection 450 passes are unaware of the routing of uplink and downlink communications. For example, the base station 412 may not be informed or need not be informed of the past routing of incoming downlink communications with data originating from the host computer 430 to be forwarded (e.g., handed over) to the connected UE 491. Similarly, the base station 412 does not need to be aware of the future routing of outgoing uplink communications from the UE 491 to the host computer 430.

[0176] Figure 13 A host computer is shown communicating with a user device via a base station over a partially wireless connection in accordance with certain embodiments.

[0177] According to one embodiment, reference will now be made to Figure 13 Describe an example implementation of the UE, base station, and host computer discussed in the previous paragraphs. In the communication system 500, the host computer 510 includes hardware 515, which includes a communication interface 516 configured to establish and maintain a wired or wireless connection with the different communication devices of the communication system 500. The host computer 510 also includes processing circuitry 518, which may have storage and / or processing capabilities. In particular, the processing circuitry 518 may include one or more programmable processors, application-specific integrated circuits, field programmable gate arrays, or a combination of these items suitable for executing instructions (not shown). The host computer 510 also includes software 511, which is stored in the host computer 510 or accessible by the host computer 510 and executable by the processing circuitry 518. The software 511 includes a host application 512. The host application 512 is operable to provide services to a remote user of a UE 530, such as a user connected via an OTT connection 550 that terminates at the UE 530 and the host computer 510. In providing services to remote users, the host application 512 may provide user data sent using the OTT connection 550 .

[0178] The communication system 500 also includes a base station 520 provided in the telecommunication system, and the base station 520 includes hardware 525 that enables it to communicate with the host computer 510 and the UE 530. The hardware 525 may include a communication interface 526 for establishing and maintaining wired or wireless connections with different communication devices of the communication system 500, and for establishing and maintaining connections with the network devices located in the coverage area ( Figure 13 The communication interface 526 may be configured to facilitate a connection 560 with the host computer 510. The connection 560 may be direct, or the connection 560 may be through a core network (e.g., a telecommunications system) of the telecommunications system. Figure 13 (not shown) and / or through one or more intermediate networks external to the telecommunications system. In the illustrated embodiment, the hardware 525 of the base station 520 also includes processing circuitry 528, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or a combination of these suitable for executing instructions (not shown). The base station 520 also has software 521 stored internally or accessible via an external connection.

[0179] The communication system 500 also includes the previously mentioned UE 530. The hardware 535 of the UE 530 may include a radio interface 537 configured to establish and maintain a wireless connection 570 with a base station serving the coverage area in which the UE 530 is currently located. The hardware 535 of the UE 530 also includes processing circuitry 538, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or a combination of these items suitable for executing instructions (not shown). The UE 530 also includes software 531 stored in or accessible by the UE 530 and executable by the processing circuitry 538. The software 531 includes a client application 532. The client application 532 is operable to provide services to human or non-human users via the UE 530 with the support of the host computer 510. In the host computer 510, the executing host application 512 can communicate with the executing client application 532 via an OTT connection 550 that terminates between the UE 530 and the host computer 510. In providing services to users, client application 532 can receive request data from host application 512 and provide user data in response to the request data. OTT connection 550 can transmit both the request data and the user data. Client application 532 can interact with the user to generate the user data it provides.

[0180] Notice, Figure 13 The host computer 510, base station 520 and UE 530 shown can be respectively Figure 12The host computer 430, one of the base stations 412a, 412b, 412c, and one of the UEs 491, 492 are similar or identical. That is, the internal working principles of these entities can be as follows Figure 13 shown, and independently, the surrounding network topology can be Figure 12 The surrounding network topology.

[0181] exist Figure 13 In FIG, OTT connection 550 has been abstractly drawn to illustrate communication between host computer 510 and UE 530 via base station 520, without explicitly referencing any intermediate devices and the precise routing of messages through these devices. The network infrastructure can determine the routing, and the network infrastructure can be configured to hide the routing from UE 530 or from the service provider operating host computer 510, or both. While OTT connection 550 is active, the network infrastructure can further make decisions based on which it dynamically changes the routing (e.g., based on load balancing considerations or network reconfiguration).

[0182] The wireless connection 570 between UE 530 and base station 520 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE 530 using OTT connection 550 (where wireless connection 570 forms the final segment). More specifically, the teachings of these embodiments can improve the network's ability to allocate resources, thereby providing benefits such as providing more bandwidth when it is more needed. This can allow more bandwidth to be allocated to UEs that need it.

[0183] A measurement process may be provided for the purpose of monitoring data rate, latency, and other factors that one or more embodiments improve upon. In response to changes in measurement results, an optional network function may also be provided for reconfiguring the OTT connection 550 between the host computer 510 and the UE 530. The measurement process and / or network function for reconfiguring the OTT connection 550 may be implemented in the software 511 and hardware 515 of the host computer 510, or in the software 531 and hardware 535 of the UE 530, or in both. In an embodiment, a sensor (not shown) may be deployed in or associated with the communication device through which the OTT connection 550 passes; the sensor may participate in the measurement process by providing values ​​of the monitored quantities exemplified above, or other physical quantities from which the software 511, 531 can calculate or estimate the monitored quantities. Reconfiguration of the OTT connection 550 may include message formats, retransmission settings, preferred routing, and the like. The reconfiguration need not affect the base station 520 and may be unknown or imperceptible to the base station 520. Such processes and functions may be known and practiced in the art. In certain embodiments, the measurements may involve proprietary UE signaling that facilitates host computer 510 measurements of throughput, propagation time, latency, etc. The measurements may be achieved because software 511 and 531 causes messages, particularly empty or "dummy" messages, to be sent using OTT connection 550 during its monitoring of propagation time, errors, etc.

[0184] Figure 14 is a flow chart showing a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station and a UE, which may be a reference Figure 12 and Figure 13 To simplify the present disclosure, only the host computers, base stations and UEs described in this section are included. Figure 14 Reference is made to the accompanying drawings of FIG. In step 610, the host computer provides user data. In sub-step 611 of step 610 (which may be optional), the host computer provides the user data by executing a host application. In step 620, the host computer initiates a transmission carrying the user data to the UE. In step 630 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station sends the user data carried in the transmission initiated by the host computer to the UE. In step 640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0185] Figure 15 is a flow chart showing a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station and a UE, which may be a reference Figure 12 and Figure 13To simplify the present disclosure, only the host computers, base stations and UEs described in this section are included. Figure 15 Reference is made to the accompanying drawings of the present invention. In step 710 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides the user data by executing a host application. In step 720, the host computer initiates a transmission carrying the user data to the UE. According to the teachings of the embodiments described throughout this disclosure, this transmission may be through a base station. In step 730 (which may be optional), the UE receives the user data carried in the transmission.

[0186] Figure 16 is a flow chart showing a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station and a UE, which may be a reference Figure 12 and Figure 13 To simplify the present disclosure, only the host computers, base stations and UEs described in this section are included. Figure 16 Reference is made to the accompanying drawings of . In step 810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 820, the UE provides user data. In sub-step 821 (which may be optional) of step 820, the UE provides user data by executing a client application. In sub-step 811 (which may be optional) of step 810, the UE executes a client application, which provides user data in response to the received input data provided by the host computer. When providing user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data is provided, the UE initiates the transmission of the user data to the host computer in sub-step 830 (which may be optional). In step 840 of the method, in accordance with the teachings of the embodiments described throughout this disclosure, the host computer receives user data sent from the UE.

[0187] Figure 17 is a flow chart showing a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station and a UE, which may be a reference Figure 12 and Figure 13 To simplify the present disclosure, only the host computers, base stations and UEs described in this section are included. Figure 17 Reference is made to the accompanying drawings. In step 910 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 920 (which may be optional), the base station initiates a transmission of the received user data to the host computer. In step 930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0188] Figure 18 A wireless network is shown that includes different devices that are directly or indirectly connected to the wireless network through one or more access network nodes (e.g., gNBs 1060a and 1060b). In particular, the wireless network includes access network nodes (e.g., gNBs 1060a and 1060b), UE 1010a, hub 1010b, remote devices 1015a and 1015b, and server 1009. UE 1010a and hub 1010b can be any of a variety of devices capable of wirelessly communicating with gNB 1060. Although hub 1010b is referred to as a hub, it can also be considered a UE (with hub functionality) because it is capable of wirelessly communicating with gNB 1060b using standard protocols (e.g., wireless standards provided by 3GPP). In practice, Figure 18 Each device shown represents a variety of different devices that can be used in different scenarios, as discussed in more detail below. Any of these devices capable of wirelessly communicating with a gNB, eNB, or any other similar 3GPP access node can be considered a wireless device or UE.

[0189] Now looking at some of the possibilities, UE 1010a can be any of a variety of different devices capable of wirelessly communicating with gNB 1060a. Figure 18 Some examples listed in the include virtual reality (VR) headsets, sensors, actuators, surveillance equipment, vehicles, or remote controls. These examples are not exhaustive and include various more specific devices, including various Internet of Things (IoT) devices. For example, in an embodiment where UE 1010a is a VR headset, UE 1010a may be a cellular phone used with the headset, or it may be a standalone or dedicated VR headset. In some embodiments, UE 1010a may be an augmented reality (AR) headset. As an AR or VR headset, UE 1010a may be used for entertainment (e.g., gaming, videos, etc.), education / business (e.g., remote conferencing, virtual lectures, etc.), healthcare (e.g., remote diagnosis, patient consultations, etc.), or any other purpose that can provide virtual or augmented content to remote users. In any of these cases, UE 1010a may receive content via wireless connection 1070a with gNB 1060a.

[0190] As another example, in an embodiment where UE 1010a is a sensor or monitoring device, UE 1010a may be a device capable of detecting or measuring one or more conditions, such as motion, gravity, humidity, temperature, biometrics, speed, door / window opening, smoke, fire, volume, flow, or any other type of device. As a sensor, UE 1010a may also be capable of capturing conditions. For example, if UE 1010a includes a camera, it may capture images, or if it includes a microphone, it may capture sound. Regardless of the sensor type, UE 1010a may provide an output to gNB 1060a via wireless connection 1070a. The output may be periodic (e.g., every 15 minutes if it reports a sensed temperature), random (e.g., to balance reports from multiple sensors), in response to a trigger event (e.g., sending an alert when moisture 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).

[0191] As another example, in an embodiment where the UE 1010a is an actuator, the UE 1010a can be a motor, a switch, or any other device that can change state in response to input received via the wireless connection 1070a. For example, the UE 1010a can be a vibrator that generates vibrations to provide tactile feedback to a user. As another example, the UE 1010a can be a small motor that adjusts the control surface of a drone in flight or a robotic arm performing a medical procedure. As another example, the UE 1010a can be a switch that remotely turns on another device (e.g., a light).

[0192] As another example, in an embodiment where UE 1010a is a vehicle, UE 1010a may be a drone, car, airplane, ship, train, tractor, robot, or any other type of device including one or more sensors and / or actuators (one or more sensors and / or actuators may change the position of the device autonomously or at the instruction of a user). In such an embodiment where UE 1010a is a remotely controlled vehicle (e.g., a drone), UE 1010a may receive instructions about movement, actuation, or sensing from a user via wireless connection 1070a, and return position, sensor, or video information to the user via wireless connection 1070a. In such an embodiment where UE 1010a is an autonomous vehicle, UE 1010a may receive alerts and other messages from other vehicles and / or infrastructure sensors via wireless connection 1070a, and provide its own telemetry data to other devices via wireless connection 1070a.

[0193] As another example, in an embodiment where UE 1010a is a remote control device, UE 1010a may be a device dedicated to controlling other devices or a general-purpose computer with a program or application that provides control over other devices. UE 1010a may send commands to the remote device via wireless connection 1070a. UE 1010a may also receive feedback, telemetry, or other information from the remote device via wireless connection 1070a. UE 1010a may present this received information to a user, who may then issue commands to the remote device. For example, UE 1010a may receive a video signal from a remote operating room via wireless connection 1070a and then issue commands to a remote surgical machine via wireless connection 1070a, which may execute the commands.

[0194] Despite Figure 18 Only a single UE 1010a is shown in the figure, but in fact any number of UEs can be used together for a single use case. For example, the first UE 1010a can be a speed sensor used in a drone, which provides the speed information of the drone to the second UE 1010a, which is a remote control device for operating the drone. When the user makes changes from the remote control device, the third UE 1010a, which is an actuator, can adjust the throttle on the drone to increase or decrease the speed. Similarly, in the above example, the first (sensor) and third (actuator) UEs 1010a can be a single UE that handles the communication of both the speed sensor and the actuator, or the UE 1010a can include one or more of the above. Similarly, in the above example, a hub (e.g., hub 1010b) can be used to handle the communication between the sensors and actuators and the controller.

[0195] The hub 1010b can be any of a variety of different devices that provide wireless access to the gNB 1060b for one or more remote devices 1015a. Some examples of different types of hubs are described in Figure 181015a, b and the like. The hub 1010b may include a memory to store data (e.g., video, audio, image, buffer, sensor data, file sharing) collected from the remote device 1015a or to be provided to the remote device 1015a. The hub 1010b may include a processor, an operating system, and server functions. The hub 1010b may include components for wireless communication to achieve wireless connection 1071 with the remote device 1015a and / or components for fixed connection with the remote device 1015b. The hub 1010b may also include routing capabilities, firewall capabilities, a VPN server, or a VPN client. The hub 1010b may also allow different communication schemes and / or scheduling between the hub 1010b and the remote devices 1015a, b and between the hub 1010b and the network 1006.

[0196] As an example, hub 1010b can be a broadband router that enables remote device 1015a to directly or indirectly access network 1006. In certain embodiments, hub 1010b can facilitate communication between remote devices 1015a and 1015b. This can be done with or without communication through network 1006. In some embodiments, hub 1010b can simply forward data from remote device 1015a or 1015b to network 1006. In some embodiments, hub 1010b can first filter, buffer, store, analyze, or verify the data from remote device 1015a or 1015b before sending the data to network 1006 or another remote device. Similarly, data from network 1006 can pass directly through hub 1010b, or it can be first processed by hub 1010b on its way to remote device 1015a or 1015b.

[0197] As another example, the hub 1010b can be a controller that sends commands or instructions to one or more actuators in the remote device 1015a. These commands or instructions can be received from a second remote device 1015b, the gNB 1060b, or through executable code, scripts, or processing instructions in the hub 1010b.

[0198] As another example, hub 1010b can be a collection location for data from one or more remote devices 1015a and / or 1015b. For example, remote devices 1015a and / or 1015b can be sensors, cameras, measurement devices, or any other type of device discussed herein that can provide output or receive input. Hub 1010b can serve as a temporary storage device for data from, for example, remote device 1015b and, in some embodiments, can perform analytics or other processing on the data. Hub 1010b can have a constant / persistent or intermittent connection with gNB 1060b.

[0199] As another example, the hub 1010b can be a content source. For example, when the remote device 1015a is a VR headset, display, speaker, or other media delivery device, the hub 1010b can retrieve VR assets, video, audio, or other media via the gNB 1060b, and then provide them directly to the remote device 1015a after some local processing and / or after adding additional local content.

[0200] Remote device 1015a can be any of a variety of different devices, for example, a device that includes one or more of a sensor, an actuator, and / or a screen. Remote device 1015a can alternatively be a VR (or AR) headset, a machine-to-machine (M2M) device, an IoT device, an Internet of Everything (IoE) device, or any other type of device capable of wirelessly accessing a communications network via a hub, or capable of acting as a hub (which, in the present context, includes providing network access to devices that cannot communicate directly with communications network 1006 via gNB 1060a or 1060b). In some scenarios, remote device 1015a can establish a wireless connection with gNB 1060a or 1060b, but still connects via hub 1010b. Remote device 1015b can be similar to remote device 1015a in most respects, except that it has a wired connection to hub 1010b rather than a wireless connection (e.g., wireless connection 1071).

[0201] gNBs 1060a and 1060b can provide wireless access to network 1006 to various wireless devices, such as UE 1010a and hub 1010b. Network 1006 can connect Figure 18The various devices shown include a server 1009, which can host various applications (e.g., real-time and pre-recorded content), data collection services (e.g., obtaining and compiling data about various environmental conditions detected by multiple remote devices 1015a, 1015b or UE 1010a), analytical functions, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and monitoring center, or any other such functions performed by a server. For example, plant status information can be collected and analyzed by the server 1009. As another example, the server 1009 can process audio and video data that may have been obtained from the UE 1010a for use in creating a map. As another example, the server 1009 can collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the server 1009 can store surveillance video uploaded by the remote device 1015b via the hub 1010b. As another example, the server 1009 may store media content such as video, audio, VR, or AR, and the server 1009 may broadcast, multicast, or unicast the media content to a remote device such as the UE 1010a or the remote device 1015a. As other examples, the server 1009 may be used for energy pricing, remote control of non-time-critical electrical loads to balance power generation demand, location services, presentation services (e.g., compiling maps from data collected from remote devices), or any other function that collects, retrieves, stores, analyzes, and / or transmits data.

[0202] Figure 19 An example method 1100 according to certain embodiments is shown. The method begins at step 1102, where a network node 160, 1060 obtains a first number of paths between the network node and one or more IAB nodes. The first number of paths can be based on the network topology, feedback or other information provided by one or more other network nodes, one or more policies of a network operator, or any other relevant factors in the network implementation. In some embodiments, the first number can be a maximum number of paths. For example, a network operator can specify that a maximum of 10 paths can be used from the network node. In some embodiments, the network node can determine the first number of paths based on the network topology.

[0203] At step 1104, the network node 160, 1060 divides the value range into a first number of intervals. Each interval is associated with a path from the network node to another IAB node. In some embodiments, each interval may have the same number of values. The value range may be a value range associated with the BAP Path ID subfield. For example, if the BAP Path ID subfield is 10 bits, there is a range of values ​​from 0 to 1023 (or 2 for 1024 values). 10). If the first number of intervals is 8, each interval can include 128 values ​​(1024 / 8=128). More specifically, the first interval can have values ​​0-127, the second interval can have values ​​128-255, and so on.

[0204] At step 1106, the network node 160, 1060 determines a second number of bearers associated with each path. This can be based on information collected directly or indirectly at the network node. For example, the network node can receive information from multiple downstream network nodes regarding the number of bearers they support. Based on this information, the network node can determine how many bearers are associated with a particular path.

[0205] At step 1108, network nodes 160, 1060 assign a path ID value to each path. The path ID value is based on the interval associated with the path and the number of bearers associated with the path. More specifically, each value within the interval represents a different number of bearers associated with the corresponding path. For example, in the scenario above, if each path has 128 or fewer bearers, each subsequent value in the interval (except the first) may indicate the presence of one additional bearer. For example, in the first interval (0-127) associated with the first path, 5 may indicate the presence of 6 bearers, and 6 may indicate the presence of 7 bearers. Similarly, in the second interval (128-255) associated with the second path, 132 may indicate the presence of 6 bearers, and 133 may indicate the presence of 7 bearers associated with the second path. If there are more than 128 bearers, each value in the interval may represent multiple bearers. For example, if the path has 475 bearers, each value in the interval may indicate 4 more bearers than the subsequent value. For example, 2 may indicate the presence of 9 to 12 bearers associated with the path.

[0206] In step 1110, the number of bearers per path is used to allocate resources among different paths. That is, the number of bearers per path can be used for load balancing, fairness, etc.

[0207] At step 1112 , the user data is provided using the resources associated with the corresponding path, and then at step 1114 , the user data is forwarded to the host computer.

[0208] Any appropriate steps, methods, features, functions or benefits disclosed herein may be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include a plurality of these functional units. These functional units may be implemented via processing circuits that may include one or more microprocessors or microcontrollers and other digital hardware that may include digital signal processors (DSPs), dedicated digital logic, etc. The processing circuit may be configured to execute program code stored in a memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory device, optical storage device, etc. The program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols and instructions for executing one or more technologies described herein. In some implementations, the processing circuit may be used to cause the corresponding functional units to perform the corresponding functions according to one or more embodiments of the present disclosure.

[0209] Figure 20 Another example method 1200 for a network node 160, 1060 according to certain embodiments is shown. The method begins at step 1202, where the network node 160, 1060 obtains a number of paths between the network node and at least one IAB node. At step 1204, the network node 160, 1060 determines a number of bearers associated with each of the number of paths. At step 1206, for each path, the network node 160, 1060 assigns a path identifier value based on at least one of the number of paths and the number of bearers associated with each path.

[0210] In one particular embodiment, network node 160 places the path identifier value in a BAP header of the packet and sends the packet to at least one IAB node.

[0211] In a particular embodiment, the network node 160 allocates at least one resource to the packet based on at least one of a path identifier value and a number of bearers.

[0212] In another specific embodiment, the number of paths is a maximum number of paths.

[0213] In another specific embodiment, the maximum number of paths is based on the network topology.

[0214] In a particular embodiment, network node 160 divides the range of path identifier values ​​into a plurality of intervals, where each interval is associated with one of the number of paths.

[0215] In another particular embodiment, each interval of the plurality of intervals includes a unique portion of the range of path identifier values.

[0216] In another specific embodiment, each interval is associated with at least one of: the number of bearers; the number of users; the number of hops to the destination; and a Differentiated Services Code Point (DSCP) value.

[0217] In another particular embodiment, each interval within the plurality of intervals includes a same number of path identifier values ​​within the range of path identifier values.

[0218] In another specific embodiment, a first interval in the plurality of intervals includes a first number of path identifier values ​​within the range of path identifier values, a second interval in the plurality of intervals includes a second number of path identifier values ​​within the range of path identifier values, and the first number and the second number are different.

[0219] In another particular embodiment, each path identifier value within each interval of the plurality of intervals is associated with a different number of bearers.

[0220] In a specific embodiment, the number of bearers includes the number of UE bearers.

[0221] In a particular embodiment, the network node comprises a DU.

[0222] In one particular embodiment, the network node comprises an IAB node.

[0223] Figure 21 shows that in wireless networks (such as Figure 7 18) in a wireless network). The apparatus may be in a wireless device or a network node (e.g. Figure 7 and / or wireless devices 110, 1010 or network nodes 160, 1060 as shown in FIG. 18. The apparatus 1300 is operable to perform the reference Figure 20 The example methods described herein and any other processes or methods that may be disclosed herein. It should also be understood that Figure 20 The method does not have to be performed only by the apparatus 1300. At least some operations of the method may be performed by one or more other entities.

[0224] The virtual device 1300 may include processing circuitry that may include one or more microprocessors or microcontrollers, as well as other digital hardware that may include a digital signal processor (DSP), dedicated digital logic, and the like. The processing circuitry may be configured to execute program code stored in a memory that may include one or more types of memory, such as read-only memory (ROM), random access memory, cache memory, flash memory devices, optical storage devices, and the like. In various embodiments, the program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols, as well as instructions for executing one or more techniques described herein. In some implementations, the processing circuitry may be configured to cause the obtaining module 1310, the determining module 1320, the allocating module 1330, and any other suitable units of the device 1300 to perform corresponding functions according to one or more embodiments of the present disclosure.

[0225] According to certain embodiments, the obtaining module 1310 may perform certain obtaining functions of the apparatus 1300. For example, the obtaining module 1310 may obtain the number of paths between the network node and at least one IAB node.

[0226] According to certain embodiments, the determination module 1320 may perform certain determination functions of the apparatus 1300. For example, the determination module 1320 may determine the number of bearers associated with each of the number of paths.

[0227] According to certain embodiments, the allocation module 1330 may perform certain allocation functions of the apparatus 1300. For example, the allocation module 1330 may allocate path identifier values ​​based on at least one of the number of paths and the number of bearers associated with each path.

[0228] As used herein, the term "module" or "unit" may have the conventional meaning in the field of electronics, electrical devices and / or electronic equipment, and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, logical solid-state and / or discrete devices, computer programs or instructions for performing corresponding tasks, processes, calculations, output and / or display functions, etc. as described herein.

[0229] Figure 22Another example method 1400 for a first network node 160, 1060 according to certain embodiments is shown. The method begins at step 1402, where the first network node 160, 1060 receives a packet from a second network node 160, 1060, including a header that includes a path identifier value. At step 1404, based on the path identifier value, the first network node 160, 1060 determines a number of bearers associated with the path. At step 1406, based on the number of bearers associated with the path, the first network node 160, 1060 allocates at least one resource to the packet. At step 1408, the first network node 160, 1060 sends the packet to a third network node based on the at least one resource.

[0230] In one particular embodiment, based on the path identifier value, the first network node 160, 1060 determines that the first network node is not the destination node for the packet.

[0231] In one particular embodiment, the first network node 160, 1060 determines the path associated with the packet based on a path identifier value in a header of the packet.

[0232] In one specific embodiment, the first network node 160, 1060 determines that at least one of the plurality of bearers terminates at the first network node. Before sending the packet to the third network node, the first network node 160, 1060 modifies the path identifier value to delete the at least one of the plurality of bearers that terminates at the first network node 160, 1060.

[0233] In one particular embodiment, the header is a BAP header.

[0234] In a particular embodiment, the range of path identifier values ​​is divided into a plurality of intervals, each interval being associated with a path within the plurality of paths.The first network node 160, 1060 determines the path of the packet based on the path identifier value in the header of the packet.

[0235] In another specific embodiment, the number of paths is a maximum number of paths.

[0236] In another specific embodiment, the maximum number of paths is based on the network topology.

[0237] In another specific embodiment, each interval is associated with at least one of: the number of bearers; the number of users; the number of hops to the destination; and a Differentiated Services Code Point (DSCP) value.

[0238] In another particular embodiment, each interval within the plurality of intervals includes a same number of path identifier values ​​within the range of path identifier values.

[0239] In another specific embodiment, a first interval in the plurality of intervals includes a first number of path identifier values ​​within the range of path identifier values, and a second interval in the plurality of intervals includes a second number of path identifier values ​​within the range of path identifier values. The first number and the second number are different.

[0240] In another particular embodiment, each path identifier value within each interval of the plurality of intervals is associated with a different number of bearers.

[0241] In another specific embodiment, the number of bearers includes the number of UE bearers.

[0242] In a particular embodiment, the first network node comprises an IAB node.

[0243] In a particular embodiment, the second network node comprises a DU or an IAB node.

[0244] In a particular embodiment, the third network node comprises an IAB node.

[0245] Figure 23 A wireless network (e.g. Figure 7 18) in a wireless network). The apparatus may be in a wireless device or network node (e.g. Figure 7 and / or wireless devices 110, 1010 or network nodes 160, 1060 as shown in FIG. 18. The apparatus 1500 is operable to perform the reference Figure 22 The example methods described herein and any other processes or methods that may be disclosed herein. It should also be understood that Figure 22 The method does not have to be performed only by the apparatus 1500. At least some operations of the method may be performed by one or more other entities.

[0246] Virtual device 1500 may include processing circuitry, which may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include a digital signal processor (DSP), dedicated digital logic, etc. The processing circuitry may be configured to execute program code stored in a memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory, cache memory, flash memory devices, optical storage devices, etc. In various embodiments, the program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols, as well as instructions for executing one or more techniques described herein. In some implementations, the processing circuitry may be configured to cause receiving module 1510, determining module 1520, allocating module 1530, sending module 1540, and any other suitable units of device 1500 to perform corresponding functions according to one or more embodiments of the present disclosure.

[0247] According to certain embodiments, the receiving module 1510 may perform certain receiving functions of the apparatus 1500. For example, the receiving module 1510 may receive a packet from the second network node 160, 1060 including a header, the header including a path identifier value.

[0248] According to certain embodiments, the determination module 1520 may perform certain determination functions of the apparatus 1500. For example, the determination module 1520 may determine a plurality of bearers associated with a path based on the path identifier value.

[0249] According to certain embodiments, the allocation module 1530 may perform certain allocation functions of the apparatus 1500. For example, the allocation module 1530 may allocate at least one resource to the packet based on a plurality of bearers associated with the path.

[0250] According to certain embodiments, the sending module 1540 may perform certain sending functions of the apparatus 1500. For example, the sending module 1540 may send the packet to the third network node based on the at least one resource.

[0251] Example Embodiments

[0252] Example embodiment 1. A method for employing a BAP path ID performed by a network node, the method comprising: obtaining a first number of paths between the network node and at least one IAB node; dividing a value range into a first number of intervals, wherein each interval includes the same number of values, and wherein each interval is associated with one path in the first number of paths; determining a second number of bearers associated with each path in the first number of paths; and assigning a path ID value to each path based on the determined number of bearers associated with the path and the interval associated with the path.

[0253] Example Embodiment 2. The method of Example Embodiment 1, wherein the first number of paths is a maximum number of paths.

[0254] Example Embodiment 3. The method of Example Embodiment 2, wherein the maximum number of paths is based on a network implementation, including at least a network topology.

[0255] Example embodiment 4. The method of any one or more of example embodiments 1-3, wherein each value within the interval is associated with a different number of bearers.

[0256] Example Embodiment 5. The method of any one or more of Example Embodiments 1-4, wherein the path ID may be used to facilitate resource allocation based on the determined number of bearers associated with each path.

[0257] Example Embodiment 6. The method of any preceding embodiment, further comprising: providing user data; and forwarding the user data to a host computer via transmission to a base station.

[0258] Example embodiment 7. A base station for employing a BAP path ID, the base station comprising: a processing circuit configured to perform any of the steps of any of example embodiments 1 to 6; and a power supply circuit configured to supply power to the base station.

[0259] Example embodiment 8. A communication system comprising a host computer, the host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE), wherein the cellular network comprises a base station having a radio interface and processing circuitry, the processing circuitry of the base station being configured to perform any of the steps of any one of example embodiments 1 to 6.

[0260] Example embodiment 9. The communication system according to the previous example embodiment, further comprising: a base station.

[0261] Example embodiment 10. The communication system according to the first two example embodiments, further comprising: a UE, wherein the UE is configured to communicate with a base station.

[0262] Example embodiment 11. The communication system according to the first three example embodiments, wherein: the processing circuit of the host computer is configured to execute a host application to provide user data; and the UE includes a processing circuit configured to execute a client application associated with the host application.

[0263] Example embodiment 12. A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network including the base station, wherein the base station performs any steps of any one of example embodiments 1 to 6.

[0264] Example embodiment 13. The method according to the previous example embodiment, further comprising: at the base station, sending user data.

[0265] Example embodiment 14. The method of the two preceding example embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising: executing, at the UE, a client application associated with the host application.

[0266] Example embodiment 15. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and a processing circuit configured to perform the method according to the first three example embodiments.

[0267] Example embodiment 16. A communication system comprising a host computer, the host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a radio interface and the processing circuitry.

[0268] Example embodiment 17. The communication system according to the previous embodiment, wherein the cellular network further comprises a base station configured to communicate with the UE.

[0269] Example embodiment 18. The communication system of the two preceding embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application to provide user data; and the processing circuitry of the UE is configured to execute a client application associated with the host application.

[0270] Example embodiment 19. A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network including the base station.

[0271] Example embodiment 20. The method according to the previous example embodiment, further comprising: receiving, at the UE, user data from the base station.

[0272] Example embodiment 21. A communication system comprising a host computer, the host computer comprising: a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the UE comprises a radio interface and processing circuitry.

[0273] Example embodiment 22. The communication system according to the previous example embodiment, further comprising: a UE.

[0274] Example embodiment 23. The communication system according to the first two example embodiments further includes: a base station, wherein the base station includes a radio interface configured to communicate with the UE and a communication interface configured to forward user data carried by the transmission from the UE to the base station to the host computer.

[0275] Example embodiment 24. The communication system of the first three example embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; and the processing circuitry of the UE is configured to execute a client application associated with the host application, thereby providing user data.

[0276] Example embodiment 25. A communication system according to the first four embodiments, wherein: the processing circuit of the host computer is configured to execute a host application to provide request data; and the processing circuit of the UE is configured to execute a client application associated with the host application to provide user data in response to the request data.

[0277] Example embodiment 26. A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising: at the host computer, receiving user data sent from the UE to the base station, wherein the base station performs any steps of any one of example embodiments 1 to 6.

[0278] Example embodiment 27. The method of the previous example embodiment, further comprising: at the UE, providing user data to the base station.

[0279] Example embodiment 28. The method of the first two example embodiments, further comprising: executing, at the UE, a client application to provide user data to be transmitted; and executing, at the host computer, a host application associated with the client application.

[0280] Example embodiment 29. The method according to the first three example embodiments further includes: executing a client application at the UE; and receiving input data to the client application at the UE, the input data being provided at the host computer by executing a host application associated with the client application, wherein the user data to be sent is provided by the client application in response to the input data.

[0281] Example embodiment 30. A communication system comprising a host computer, the host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the processing circuitry of the base station being configured to perform any of the steps of any of example embodiments 1 to 6.

[0282] Example embodiment 31. The communication system according to the previous embodiment, further comprising: a base station.

[0283] Example embodiment 32. The communication system according to the two previous example embodiments, further comprising: a UE, wherein the UE is configured to communicate with the base station.

[0284] Example embodiment 33. The communication system of the first three embodiments, wherein: the processing circuit of the host computer is configured to execute a host application; and the UE is configured to execute a client application associated with the host application, thereby providing user data to be received by the host computer.

[0285] Example embodiment 34. A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising: at the host computer, receiving from the base station user data originating from a transmission that the base station has received from the UE, wherein the base station performs any steps of any of example embodiments 1 to 6.

[0286] Example embodiment 35. The method according to the previous embodiment, further comprising: receiving, at the base station, user data from the UE.

[0287] Example embodiment 36. The method of the two preceding example embodiments, further comprising: at the base station, initiating transmission of the received user data to a host computer.

[0288] The systems and devices described herein may be modified, added to, or omitted without departing from the scope of this disclosure. Components of the systems and devices may be integrated or separated. Moreover, the operations of the systems and devices may be performed by more, fewer, or other components. In addition, any suitable logic, including software, hardware, and / or other logic, may be used to perform the operations of the systems and devices. As used in this document, "each" refers to each member of a set or each member of a subset of a set.

[0289] Without departing from the scope of the present disclosure, the methods described herein may be modified, added to, or omitted. The methods may include more, fewer, or other steps. Additionally, the steps may be performed in any suitable order.

[0290] Although the present disclosure has been described in terms of specific embodiments, it will be apparent to those skilled in the art that the changes and substitutions of the embodiments will be apparent. Therefore, the above description of the embodiments does not limit the present disclosure. Other changes, substitutions, and variations are possible without departing from the spirit and scope of the present disclosure.

Claims

1. A method performed by a network node, the method comprising: Obtaining the number of paths between the network node and at least one integrated access backhaul IAB node; determining a number of bearers associated with each of the number of paths; For each path, assigning a path identifier value based on at least one of a number of the paths and a number of bearers associated with each path; placing the path identifier value in a Backhaul Adaptation Protocol (BAP) header of the packet; allocating at least one resource to the packet based on at least one of the path identifier value and the number of the bearers; as well as The packet is sent to the at least one IAB node.

2. The method according to claim 1, wherein: The number of paths is the maximum number of paths.

3. The method according to claim 2, wherein: The maximum number of paths is based on the network topology.

4. The method according to any one of claims 1 to 3, further comprising: The range of path identifier values ​​is divided into a plurality of intervals, wherein each interval is associated with a path among the number of paths.

5. The method according to claim 4, wherein: Each interval of the plurality of intervals includes a unique portion of the range of path identifier values.

6. The method according to claim 4, wherein: Each interval is associated with at least one of the following: The number of loads; The number of users; The number of hops to the destination; and Differentiated Services Code Point (DSCP) value.

7. The method according to claim 4, wherein: Each interval within the plurality of intervals includes a same number of path identifier values ​​within the range of path identifier values.

8. The method according to claim 4, wherein: a first interval within the plurality of intervals includes a first number of path identifier values ​​within the range of path identifier values, a second interval within the plurality of intervals includes a second number of path identifier values ​​within the range of path identifier values, and The first number and the second number are different.

9. The method according to claim 4, wherein: Each path identifier value within each interval of the plurality of intervals is associated with a different number of bearers.

10. The method according to any one of claims 1 to 3, wherein: The number of bearers includes the number of UE bearers.

11. The method according to any one of claims 1 to 3, wherein: The network node comprises a distributed unit DU.

12. The method according to any one of claims 1 to 3, wherein: The network node comprises an IAB node.

13. A network node, comprising: A processing circuit configured to: Obtaining the number of paths between the network node and at least one integrated access backhaul IAB node; determining a number of bearers associated with each of the number of paths; For each path, assigning a path identifier value based on the number of paths and the number of bearers associated with each path; placing the path identifier value in a Backhaul Adaptation Protocol (BAP) header of the packet; allocating at least one resource to the packet based on at least one of the path identifier value and the number of the bearers; as well as The packet is sent to the at least one IAB node.

14. The network node according to claim 13, wherein: The number of paths is the maximum number of paths.

15. The network node according to claim 14, wherein: The maximum number of paths is based on the network topology.

16. The network node according to any one of claims 13 to 15, wherein: The processing circuit is configured to divide the range of path identifier values ​​into a plurality of intervals, wherein each interval is associated with a path among the number of paths.

17. The network node according to claim 16, wherein: Each interval of the plurality of intervals includes a unique portion of the range of path identifier values.

18. The network node according to claim 16, wherein: Each interval is associated with at least one of the following: The number of loads; The number of users; The number of hops to the destination; and Differentiated Services Code Point (DSCP) value.

19. The network node according to claim 16, wherein: Each interval within the plurality of intervals includes a same number of path identifier values ​​within the range of path identifier values.

20. The network node of claim 16, wherein: a first interval within the plurality of intervals includes a first number of path identifier values ​​within the range of path identifier values, a second interval within the plurality of intervals includes a second number of path identifier values ​​within the range of path identifier values, and The first number and the second number are different.

21. The network node according to claim 16, wherein: Each path identifier value within each interval of the plurality of intervals is associated with a different number of bearers.

22. The network node according to any one of claims 13 to 15, wherein: The number of bearers includes the number of UE bearers.

23. The network node according to any one of claims 13 to 15, wherein: The network node comprises a distributed unit DU.

24. The network node according to any one of claims 13 to 15, wherein: The network node comprises an IAB node.

25. A method performed by a first network node, the method comprising: receiving, from a second network node, a packet including a header, the header including a path identifier value; determining a plurality of bearers associated with the path based on the path identifier value; allocating at least one resource to the packet based on the plurality of bearers associated with the path; as well as The packet is sent to a third network node based on the at least one resource.

26. The method according to claim 25, further comprising: Based on the path identifier value, it is determined that the first network node is not a destination node for the packet.

27. The method according to any one of claims 25 to 26, further comprising: A path associated with the packet is determined based on the path identifier value in the header of the packet.

28. The method according to any one of claims 25 to 26, further comprising: determining that at least one of the plurality of bearers is terminated at the first network node; as well as Prior to sending the packet to the third network node, the path identifier value is modified to delete the at least one bearer of the plurality of bearers that terminates at the first network node.

29. The method according to any one of claims 25 to 26, wherein: The header is a Backhaul Adaptation Protocol (BAP) header.

30. The method according to any one of claims 25 to 26, wherein: A range of path identifier values ​​is divided into a plurality of intervals, each interval being associated with a path within a plurality of paths, and the method further comprises determining the path of the packet based on the path identifier value in the header of the packet.

31. The method according to claim 30, wherein: The number of paths is the maximum number of paths.

32. The method according to claim 31, wherein: The maximum number of paths is based on the network topology.

33. The method of claim 30, wherein: Each interval is associated with at least one of the following: The number of loads; The number of users; The number of hops to the destination; and Differentiated Services Code Point (DSCP) value.

34. The method of claim 30, wherein: Each interval within the plurality of intervals includes a same number of path identifier values ​​within the range of path identifier values.

35. The method of claim 34, wherein: a first interval within the plurality of intervals includes a first number of path identifier values ​​within the range of path identifier values, a second interval within the plurality of intervals includes a second number of path identifier values ​​within the range of path identifier values, and The first number and the second number are different.

36. The method according to any one of claims 32 to 35, wherein: Each path identifier value within each interval of the plurality of intervals is associated with a different number of bearers.

37. The method of claim 36, wherein: The number of bearers includes the number of UE bearers.

38. The method according to any one of claims 25 to 26, wherein: The first network node comprises an integrated access backhaul IAB node.

39. The method according to any one of claims 25 to 26, wherein: The second network node includes a distributed unit DU or an IAB node.

40. The method according to any one of claims 25 to 26, wherein: The third network node includes an IAB node.

41. A first network node, comprising: A processing circuit configured to: receiving, from a second network node, a packet including a header, the header including a path identifier value; determining a plurality of bearers associated with the path based on the path identifier value; allocating at least one resource to the packet based on the plurality of bearers associated with the path; as well as The packet is sent to a third network node based on the at least one resource.

42. The first network node according to claim 41, wherein: The processing circuit is configured to: Based on the path identifier value, it is determined that the first network node is not a destination node for the packet.

43. The first network node according to any one of claims 41 to 42, wherein: The processing circuit is configured to: A path associated with the packet is determined based on the path identifier value in the header of the packet.

44. The first network node according to any one of claims 41 to 42, wherein: The processing circuit is configured to: determining that at least one of the plurality of bearers is terminated at the first network node; as well as Prior to sending the packet to the third network node, the path identifier value is modified to delete the at least one bearer of the plurality of bearers that terminates at the first network node.

45. The first network node according to any one of claims 41 to 42, wherein: The header is a Backhaul Adaptation Protocol (BAP) header.

46. ​​The first network node according to any one of claims 41 to 42, wherein: A range of path identifier values ​​is divided into a plurality of intervals, each interval being associated with a path within a plurality of paths, and the processing circuit is further configured to determine the path of the packet based on the path identifier value in the header of the packet.

47. The first network node according to claim 46, wherein: The number of paths is the maximum number of paths.

48. The first network node according to claim 47, wherein: The maximum number of paths is based on the network topology.

49. The first network node according to claim 46, wherein: Each interval is associated with at least one of the following: The number of loads; The number of users; The number of hops to the destination; and Differentiated Services Code Point (DSCP) value.

50. The first network node of claim 46, wherein: Each interval within the plurality of intervals includes a same number of path identifier values ​​within the range of path identifier values.

51. The first network node of claim 50, wherein: a first interval within the plurality of intervals includes a first number of path identifier values ​​within the range of path identifier values, a second interval within the plurality of intervals includes a second number of path identifier values ​​within the range of path identifier values, and The first number and the second number are different.

52. The first network node of claim 46, wherein: Each path identifier value within each interval of the plurality of intervals is associated with a different number of bearers.

53. The first network node according to any one of claims 41 to 42, wherein: The number of bearers includes the number of UE bearers.

54. The first network node according to any one of claims 41 to 42, wherein: The first network node comprises an integrated access backhaul IAB node.

55. The first network node according to any one of claims 41 to 42, wherein: The second network node includes a distributed unit DU or an IAB node.

56. The first network node according to any one of claims 41 to 42, wherein: The third network node includes an IAB node.

Images