Patent Grant
11064417
The present disclosure is generally related to wireless communication networks and is more particularly related to configuring and operating an adaptation layer in a relay node, for communicating with a central unit of a donor base station through a distributed unit of the donor base station.
The NG RAN logical nodes shown in
Furthermore, the F1 interface between the gNB-CU and gNB-DU is specified, or based on, the following general principles:
As noted above, the CU can host protocols such as RRC and PDCP, while a DU can host protocols such as RLC, MAC and PHY. Other variants of protocol distributions between CU and DU can exist, however, such as hosting the RRC, PDCP and part of the RLC protocol in the CU (e.g., Automatic Retransmission Request (ARQ) function), while hosting the remaining parts of the RLC protocol in the DU, together with MAC and PHY. In some exemplary embodiments, the CU can host RRC and PDCP, where PDCP is assumed to handle both UP traffic and CP traffic. Nevertheless, other exemplary embodiments may utilize other protocol splits that by hosting certain protocols in the CU and certain others in the DU. Exemplary embodiments can also locate centralized control plane protocols (e.g., PDCP-C and RRC) in a different CU with respect to the centralized user plane protocols (e.g., PDCP-U).
It has also been agreed in 3GPP RAN3 Working Group (WG) to support a separation of the gNB-CU into a CU-CP (control plane) function (including RRC and PDCP for signaling radio bearers) and CU-UP (user plane) function (including PDCP for user plane). The CU-CP and CU-UP parts communicate with each other using the E1-AP protocol over the E1 interface. The CU-CP/UP separation is illustrated in
The NG-RAN is layered into a Radio Network Layer (RNL) and a Transport Network Layer (TNL). The NG-RAN architecture, i.e., the NG-RAN logical nodes and interfaces between them, is defined as part of the RNL. For each NG-RAN interface (NG, Xn, F1) the related TNL protocol and the functionality are specified. The TNL provides services for user plane transport and signaling transport. In NG-Flex configuration, each gNB is connected to all 5GC nodes within a pool area. The pool area is defined in 3GPP TS 23.501. If security protection for control plane and user plane data on TNL of NG-RAN interfaces has to be supported, NDS/IP (3GPP TS 33.401) shall be applied.
In the context of RAN 5G architectures, 3GPP has agreed that dual connectivity is supported. Such mechanism consists of establishing master and secondary nodes and it consists of distributing user plane (UP) traffic to the master node (MN) and secondary nodes (SNs) according to the best possible traffic and radio resource management. CP traffic is assumed to terminate in one node only, i.e., the MN.
In the architecture identified by CUs and DUs, dual connectivity (DC) can be achieved by means of allowing a UE to connect to multiple DUs served by the same CU or by allowing a UE to connect to multiple DUs served by different CUs. As illustrated in
Furthermore, in the context of 5G standardization, multi-RAT dual connectivity (MR-DC) is being specified. When MR-DC is applied, a RAN node (the master node, MN) anchors the control plane towards the CN, while another RAN node (the secondary node, SN) provides control and user plane resources to the UE via coordination with the MN. This is shown in
Within the scope of MR-DC, various user plane/bearer type solutions are possible, as seen in
For 3GPP Rel-15, it has been agreed to support so-called non-standalone NR deployments. In these deployments, the NR RAT does not support stand-alone operation, i.e., it cannot serve UEs by itself. Instead, dual connectivity (EN-DC type) is used to serve end users. This means that UEs first connect to the LTE MeNB, which later sets up the NR leg in the SgNB (secondary gNB).
In the procedure shown in
In addition to non-standalone operation, NR will also support standalone (SA) operation. In this case, the UEs that support SA NR will camp on NR cells and perform access directly to the NR system (i.e., no connection to LTE first is required to access the NR). An SA-capable NR gNB will broadcast System Information (SI) in the cell that is used to access the NR cell, in a way similar to LTE operation, though the contents of the SI, as well as the manner in which it is broadcasted (e.g. periodicity) could be different from LTE.
Densification via the deployment of more and more base stations (e.g., macro or micro base stations) is one of the mechanisms that can be employed to satisfy the increasing demand for bandwidth and/or capacity in mobile networks, which is mainly driven by the increasing use of video streaming services. Due to the availability of more spectrum in the millimeter wave (mmw) band, deploying small cells that operate in this band is an attractive deployment option for these purposes. However, the normal approach of connecting the small cells to an operator's backhaul network with optical fiber can end up being very expensive and impractical. Employing wireless links for connecting the small cells to the operator's network is a cheaper and more practical alternative. One such approach is an integrated access backhaul (IAB) network, where the operator can utilize part of the available radio resources for the backhaul link.
IAB has been studied earlier in 3GPP in the scope of Long Term Evolution (LTE) Rel-10. In that work, an architecture was adopted where a Relay Node (RN) has the functionality of an LTE eNB and UE modem. The RN is connected to a donor eNB which has a S1/X2 proxy functionality hiding the RN from the rest of the network. That architecture enables the Donor eNB to also be aware of the UEs behind the RN and hide any UE mobility between Donor eNB and Relay Node on the same Donor eNB from the CN. During the Rel-10 study, other architectures were also considered including, e.g., where the RNs are more transparent to the Donor gNB and allocated a separate stand-alone P/S-GW node.
For 5G/NR, similar options utilizing IAB can also be considered. One difference compared to LTE is the gNB-CU/DU split described above, which separates time-critical RLC/MAC/PHY protocols from less time-critical RRC/PDCP protocols. It is anticipated that a similar split could also be applied for the IAB case. Other IAB-related differences anticipated in NR as compared to LTE are the support of multiple hops and the support of redundant paths.
During the RAN3 #99 meeting in Athens (February 2018), several IAB multi-hop designs were proposed, and summarized under five architecture reference diagrams (available at 35w.3gpp.org/ftp/tsg_ran/wg3_iu/TSGR3_99/Docs/R3-181502.zip). These reference diagrams differ with respect to the modification needed on interfaces or additional functionality needed, e.g., to accomplish multi-hop forwarding. These five architectures are divided into two architecture groups. The main features of these architectures can be summarized as follows:
Architecture group 1: Consists of architectures 1a and 1b. Both architectures leverage CU/DU split architecture.
Architecture 1a:
Architecture 1b:
Architecture group 2: Consists of architectures 2a, 2b and 2c
Architecture 2a:
Architecture 2b:
Architecture 2c:
Architecture 1a leverages CU/DU-split architecture.
The donor also holds a DU to support UEs and MTs of downstream IAB-nodes. The IAB-donor holds a CU for the DUs of all IAB-nodes and for its own DU. Each DU on an IAB-node connects to the CU in the IAB-donor using a modified form of F1, which is referred to as F1*. F1*-U runs over RLC channels on the wireless backhaul between the MT on the serving IAB-node and the DU on the donor. F1*-U provides transport between MT and DU on the serving IAB-node as well as between DU and CU on the donor. An adaptation layer is added, which holds routing information, enabling hop-by-hop forwarding. It replaces the IP functionality of the standard F1-stack. F1*-U may carry a GTP-U header for the end-to-end association between CU and DU. In a further enhancement, information carried inside the GTP-U header may be included in the adaption layer. Further, optimizations to RLC may be considered such as applying ARQ only on the end-to-end connection opposed to hop-by-hop. The right side of
Architecture 1b also leverages CU/DU-split architecture.
In this architecture, each IAB-node and the IAB-donor hold the same functions as in architecture 1a. Also, as in architecture 1a, every backhaul link establishes an RLC-channel, and an adaptation layer is inserted to enable hop-by-hop forwarding of F1*.
As opposed to architecture 1a, the MT on each IAB-node establishes a PDU-session with a UPF residing on the donor. The MT's PDU-session carries F1* for the collocated DU. In this manner, the PDU-session provides a point-to-point link between CU and DU. On intermediate hops, the PDCP-PDUs of F1* are forwarded via adaptation layer in the same manner as described for architecture 1a. The right side of
In architecture 2a, the IAB-node holds an MT to establish an NR Uu link with a gNB on the parent IAB-node or IAB-donor. Via this NR-Uu link, the MT sustains a PDU-session with a UPF that is collocated with the gNB. In this manner, an independent PDU-session is created on every backhaul link. Each IAB-node further supports a routing function to forward data between PDU-sessions of adjacent links. This creates a forwarding plane across the wireless backhaul. Based on PDU-session type, this forwarding plane supports IP or Ethernet. In case PDU-session type is Ethernet, an IP layer can be established on top. In this manner, each IAB-node obtains IP-connectivity to the wireline backhaul network.
All IP-based interfaces such as NG, Xn, F1, N4, etc. are carried over this forwarding plane. In the case of F1, the UE-serving IAB-Node would contain a DU rather than a full gNB, and the CU would be in or beyond the IAB Donor. The right side of
In case the IAB-node holds a DU for UE-access, it may not be required to support PDCP-based protection on each hop since the end user data will already be protected using end to end PDCP between the UE and the CU.
In architecture 2b, the IAB-node holds an MT to establish an NR Uu link with a gNB on the parent IAB-node or IAB-donor. Via this NR-Uu link, the MT sustains a PDU-session with a UPF. Opposed to architecture 2a, this UPF is located at the IAB-donor. Also, forwarding of PDUs across upstream IAB-nodes is accomplished via tunneling. The forwarding across multiple hops, therefore, creates a stack of nested tunnels. As in architecture 2a, each IAB-node obtains IP-connectivity to the wireline backhaul network. All IP-based interfaces such as NG, Xn, F1, N4, etc. are carried over this forwarding IP plane. The right side of
Architecture 2c leverages DU-CU split. The IAB-node holds an MT which sustains an RLC-channel with a DU on the parent IAB-node or IAB-donor. The IAB donor holds a CU and a UPF for each IAB-node's DU. The MT on each IAB-node sustains an NR-Uu link with a CU and a PDU session with a UPF on the donor. Forwarding on intermediate nodes is accomplished via tunneling. The forwarding across multiple hops creates a stack of nested tunnels. As in architecture 2a and 2b, each IAB-node obtains IP-connectivity to the wireline backhaul network. Opposed to architecture 2b, however, each tunnel includes an SDAP/PDCP layer. All IP-based interfaces such as NG, Xn, F1, N4, etc. are carried over this forwarding plane. The right side of
Given an architecture as in the architecture 1 examples described above, there are advantages of performing ARQ functions of the RLC layer on a hop-by-hop basis, rather than end-to-end, between the UE and IAB donor. If hop-by-hop ARQ is assumed, the adaptation layer discussed above can be above RLC or below it.
Embodiments of the presently disclosed techniques and apparatus place the adaptation layer above the RLC, allowing reuse of the NR lower layers (RLC, MAC, PHY) in the IAB nodes, reducing standardization and implementation impacts, while providing bearer-level QoS-based service quality guarantees. More particularly, disclosed herein are mechanisms for the proper configuration of the backhaul bearer mappings of the adaptation layer in IAB networks, so that the QoS level of the bearers as well as the hop depth is considered.
Embodiments disclosed herein include methods, in a relay node, for mapping end-user bearers to backhaul bearers in an adaptation layer of a donor base station or a relay node connected to the donor base station, directly or through one or more additional relay nodes. An example method comprises the step of mapping a plurality of end-user bearers to backhaul bearers in consideration of QoS classes for the end-user bearers and a distance from the relay node to a destination node for each of the plurality of end-user bearers, such that at least one of the backhaul bearers carries end-user bearers with different QoS classes and different distances to the destination node. In some embodiments, this mapping considers the distance from the relay node to the destination node for at least one of the end-user bearers in terms of a number of remaining hops from the relay node to the destination node. In some of these and in some other embodiments, the mapping considers the distance from the relay node to the destination node for at least one of the end-user bearers in terms of an estimated end-to-end delay from the relay node to the destination node.
In some embodiments, the method comprises mapping an end-user bearer having a highest-priority traffic, as indicated by the QoS class of the end-user bearer, and having a largest distance, as indicated by the distance from the relay node to the destination node for the end-user bearer, to a separate, unshared, backhaul bearer. In some embodiments, mapping end-user bearers to backhaul bearers in consideration of QoS classes for the end-user bearers and the distance from the relay node to the destination node for each end-user bearer comprises mapping at least one end-user bearer having low-priority traffic and a distant destination node, as indicated by the QoS class and the distance from the relay node to the destination node for the at least one end-user bearer, to a same backhaul bearer as at least one additional end-user bearer having high-priority traffic and a nearby destination, as indicated by the QoS class and the distance from the relay node to the destination node for the at least one additional end-user bearer.
In some embodiments, a method according to any of the above embodiments further comprises the steps of detecting, in adaptation headers for each packet of at least one end-user bearer, a time-to-live value indicating a packet-delay requirement for the packet; and, upon forwarding the packet to a next node, modifying the time-to-live value to reflect time spent by the packet in the relay node.
Further aspects of the present invention are directed to an apparatus, an IAB/relay node, computer program products or computer readable storage medium corresponding to the methods summarized above and functional implementations of the above-summarized apparatus and wireless device.
Of course, the present invention is not limited to the above features and advantages. Those of ordinary skill in the art will recognize additional features and advantages upon reading the following detailed description, and upon viewing the accompanying drawings.
Exemplary embodiments briefly summarized above will now be described more fully with reference to the accompanying drawings. These descriptions are provided by way of example to explain the subject matter to those skilled in the art and should not be construed as limiting the scope of the subject matter to only the embodiments described herein. More specifically, examples are provided below that illustrate the operation of various embodiments according to the advantages discussed above.
Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods and/or procedures disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein can be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments can apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description.
Of the various architectures described above, the architecture group 1 has been prioritized to be studied in 3GPP, and currently the different possibilities for the placement of the adaptation layer and its functionality are being discussed (R2-1806456).
Thus, the following discussion focuses only on the case of hop-by-hop ARQ (
Having the adaptation layer below the RLC, as in
However, with the adaptation layer placed above the RLC, some granularity for QoS management may be not available, because several bearers can be mapped over the same backhaul bearer. Even if only bearers with the same QoS are mapped over the same backhaul bearer, fairness may not be achieved, because some packets may have yet to traverse several hops before they reach the destination (e.g., final IAB node) as compared to packets belonging to other bearers (UEs) that may be located in a different IAB node located closer (fewer hops).
Detailed herein are mechanisms for the proper configuration of the backhaul bearer mappings of the adaptation layer in IAB networks, so that the QoS level of the bearers as well as the hop depth is considered. By utilizing an adaptation layer above the RLC, the NR lower layers (RLC, MAC, PHY) can be reused, “as is,” in the IAB nodes, reducing standardization and implementation impacts. Further, service quality of bearers may be guaranteed via:
In this description, focus is placed on the case where the IAB nodes are connected towards the network (to the next IAB node on the chain or the Donor DU/gNB in case the last IAB node on the right on the chain) using the NR air interface. Accordingly, the NR RRC protocol is assumed. However, the techniques described herein are equally applicable to the case where these links are using the LTE air interface (e.g., in an EN-DC setting). In this case, RRC refers to the LTE RRC protocol.
In the following description, the focus is on architecture 1a, as described above. However, the techniques are equally applicable for architecture 1b and architecture 2 variants.
As discussed above, placing the adaptation layer above the RLC minimizes the standardization impact. Also, multiplexing/aggregation of end-user bearers over the backhaul bearers should be carried via the adaptation layer in that case. The main role of the adaptation layer should be the forwarding of the packets to the intended IAB node while fulfilling the QoS requirements. In other words, the intermediate IAB nodes need to know only about the intended IAB node for the packets. It is the destination/last IAB node that has the UE context information for routing the packets to the exact UE.
However, this does not mean that intermediate IAB nodes are unaware of QoS requirements of the end-user bearers. In fact, QoS requirements are considered during mapping configuration at the intermediate IAB nodes. The adaptation layer at IAB nodes should know how to multiplex/de-multiplex packets, while employing the configured mapping rules.
Having each intermediate IAB node become fully aware of each individual UE context, and that each UE bearer having a separate logical channel in each IAB node is not a scalable solution. Besides, for this extreme level of granularity, we need to increase enormously the number of logical channel IDs (LCIDs), which currently can be a maximum of 29 for DRBs (32 LCIDs, for which 3 are reserved for SRBs). Furthermore, merely placing the adaptation layer below RLC does not provide any gain in granularity unless modifications are made to the MAC scheduling and buffer status reporting mechanisms.
Several observations can be made. First, it is not scalable to have a separate backhaul bearer in each hop corresponding to each UE bearer being served via that hop. Second, by properly configuring the adaptation layer, the intermediate IAB nodes can forward the packets according to QoS requirements of end-user bearers without knowing the full UE context. Third, to achieve fine granularity via putting the adaptation layer below RLC, the MAC scheduler as well as buffer status reporting must be modified.
In a multi-hop IAB system, UEs can access the network via IAB nodes that can be any of a number of different hops away from the donor DU. Furthermore, UEs attached to the same IAB node may need to establish DRBs with different QCIs. In such situation, where some UEs are more hops away from the donor DU than other UEs, a mechanism may be needed to ensure fairness among the UEs. A baseline solution could be that the adaptation layer only provides routing information, without considering QoS or fairness aspect. The mapping rules configured at the adaptation layer of DUs forward the ingress backhaul bearer to egress backhaul bearer irrespective of the QoS requirements of the end-user traffic aggregated at these backhaul (IAB) bearers.
A simple approach to include the QoS and fairness aspects in routing can be to have a separate (dedicated) backhaul bearer for each QoS class per subsequent IAB nodes. Consequently, the first DU (donor DU) must support a relatively large number of backhaul bearers, that is, the number of hops/links times the number of QoS classes as shown in
A simple but un-scalable approach which does not require any changes to the scheduler is to assign a separate backhaul bearer to each QoS class per subsequent IAB node. A more scalable, yet still simple (no modifications are needed to the scheduler) solution for supporting fairness/QoS, is to share, in an intelligent way, the backhaul bearers among QoS classes of IAB nodes that are different hops away from donor DU. For example, traffic belonging to a distant IAB node with high priority can have a dedicated bearer at all the links/hops, while relatively low priority traffic belonging to the same IAB node can share backhaul bearer with high priority traffic for nearby (to donor DU) IAB node.
The multi-hop IAB system should strive to fulfil the latency requirements of bearers with strict delay requirements, irrespective of the number of hops involved. This might require over-dimensioning, i.e., dedicated backhaul bearers (for delay intolerant traffic) in certain links of the system and is up to network operators how to implement the mapping rules.
Existing numbers of logical channels can be enough for multi-hop relaying system if shared intelligently among end-user bearers. To ensure fairness, high priority traffic belonging to distant IAB nodes can be assigned separate IAB bearer at all the intermediate hops/links. To compensate the farness factor, low-priority traffic for distant IAB nodes can share IAB bearers with high priority traffic for nearby IAB nodes. For services with strict delay tolerance, the mapping rules at the IAB nodes could consider the end-to-end delay as a QoS parameter rather than the number of hops. Thus, a multi-hop IAB system can adopt a less complex solution, such as smart sharing of existing backhaul bearers among end-user traffic.
To summarize, some of the factors to consider in configuring the mapping of the adaptation layer are:
For bearers with strict packet delay requirements, a flag can be included in the adaptation header corresponding to a “time to live” value for the packets of this bearer (initially by the donor DU for the DL traffic and by the destination IAB node for UL traffic), and each intermediate IAB node can consider this to prioritize the packet. On forwarding the packet to the next node, the time to live value can be modified by the IAB node to reflect the time spent from the reception of the packet at one end and the transmission to the other end.
The mapping of the adaptation layers on all the intermediate nodes can be performed statically when a UE bearer is setup, or/and it can be done dynamically, based on some rules. For example, the IAB nodes can be given rules on how to change the mapping when more and more UEs and bearers are added into the network. One possible scenario is to start with a one-to-one mapping between the QoS class and the hop count used in the mapping, as in
The configuration of the mapping rules, etc., can be performed by a control controller unit (e.g., CU or operation and maintenance function). The protocols used to configure the mapping rule can be F1-AP, RRC, MAC or any other control plane protocol. It is also possible to signal configuration information in the adaptation layer header.
Although the subject matter described herein can be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in
The wireless network can comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system. In some embodiments, the wireless network can be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the 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 (ALAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.
Network 2106 can comprise 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 to enable communication between devices.
Network node 2160 and WD 2110 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, the wireless network can comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that can facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). Base stations can be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and can then also be referred to as femto base stations, pica base stations, micro base stations, or macro base stations. A base station can be a relay node or a relay donor node controlling a relay. A network node can also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station can also be referred to as nodes in a distributed antenna system (DAS).
Further examples of network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. As another example, a network node can be a virtual network node as described in more detail below. More generally, however, network nodes can represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.
In
Similarly, network node 2160 can be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which can each have their own respective components. In certain scenarios in which network node 2160 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components can be shared among several network nodes. For example, a single RNC can control multiple NodeB's. In such a scenario, each unique NodeB and RNC pair, can in some instances be considered a single separate network node. In some embodiments, network node 2160 can be configured to support multiple radio access technologies (RATs). In such embodiments, some components can be duplicated (e.g., separate device readable medium 2180 for the different RATs) and some components can be reused (e.g., the same antenna 2162 can be shared by the RATs). Network node 2160 can also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 2160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies can be integrated into the same or different chip or set of chips and other components within network node 2160.
Processing circuitry 2170 can be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry 2170 can include processing information obtained by processing circuitry 2170 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
Processing circuitry 2170 can comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 2160 components, such as device readable medium 2180, network node 2160 functionality. For example, processing circuitry 2170 can execute instructions stored in device readable medium 2180 or in memory within processing circuitry 2170. Such functionality can include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 2170 can include a system on a chip (SOC).
In some embodiments, processing circuitry 2170 can include one or more of radio frequency (RF) transceiver circuitry 2172 and baseband processing circuitry 2174. In some embodiments, radio frequency (RF) transceiver circuitry 2172 and baseband processing circuitry 2174 can be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 2172 and baseband processing circuitry 2174 can be on the same chip or set of chips, boards, or units
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 can be performed by processing circuitry 2170 executing instructions stored on device readable medium 2180 or memory within processing circuitry 2170. In alternative embodiments, some or all of the functionality can be provided by processing circuitry 2170 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 2170 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 2170 alone or to other components of network node 2160, but are enjoyed by network node 2160 as a whole, and/or by end users and the wireless network generally.
Device readable medium 2180 can comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that can be used by processing circuitry 2170. Device readable medium 2180 can store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 2170 and, utilized by network node 2160. Device readable medium 2180 can be used to store any calculations made by processing circuitry 2170 and/or any data received via interface 2190. In some embodiments, processing circuitry 2170 and device readable medium 2180 can be considered to be integrated.
Interface 2190 is used in the wired or wireless communication of signaling and/or data between network node 2160, network 2106, and/or WDs 2110. As illustrated, interface 2190 comprises port(s)/terminal(s) 2194 to send and receive data, for example to and from network 2106 over a wired connection. Interface 2190 also includes radio front end circuitry 2192 that can be coupled to, or in certain embodiments a part of, antenna 2162. Radio front end circuitry 2192 comprises filters 2198 and amplifiers 2196. Radio front end circuitry 2192 can be connected to antenna 2162 and processing circuitry 2170. Radio front end circuitry can be configured to condition signals communicated between antenna 2162 and processing circuitry 2170. Radio front end circuitry 2192 can receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 2192 can convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 2198 and/or amplifiers 2196. The radio signal can then be transmitted via antenna 2162. Similarly, when receiving data, antenna 2162 can collect radio signals which are then converted into digital data by radio front end circuitry 2192. The digital data can be passed to processing circuitry 2170. In other embodiments, the interface can comprise different components and/or different combinations of components.
In certain alternative embodiments, network node 2160 may not include separate radio front end circuitry 2192, instead, processing circuitry 2170 can comprise radio front end circuitry and can be connected to antenna 2162 without separate radio front end circuitry 2192. Similarly, in some embodiments, all or some of RF transceiver circuitry 2172 can be considered a part of interface 2190. In still other embodiments, interface 2190 can include one or more ports or terminals 2194, radio front end circuitry 2192, and RF transceiver circuitry 2172, as part of a radio unit (not shown), and interface 2190 can communicate with baseband processing circuitry 2174, which is part of a digital unit (not shown).
Antenna 2162 can include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 2162 can be coupled to radio front end circuitry 2190 and can be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 2162 can comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni-directional antenna can be used to transmit/receive radio signals in any direction, a sector antenna can be used to transmit/receive radio signals from devices within a particular area, and a panel antenna can be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna can be referred to as MIMO. In certain embodiments, antenna 2162 can be separate from network node 2160 and can be connectable to network node 2160 through an interface or port.
Antenna 2162, interface 2190, and/or processing circuitry 2170 can be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals can be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna 2162, interface 2190, and/or processing circuitry 2170 can be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals can be transmitted to a wireless device, another network node and/or any other network equipment.
Power circuitry 2187 can comprise, or be coupled to, power management circuitry and can be configured to supply the components of network node 2160 with power for performing the functionality described herein. Power circuitry 2187 can receive power from power source 2186. Power source 2186 and/or power circuitry 2187 can be configured to provide power to the various components of network node 2160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 2186 can either be included in, or external to, power circuitry 2187 and/or network node 2160. For example, network node 2160 can be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 2187. As a further example, power source 2186 can comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 2187. The battery can provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, can also be used.
Alternative embodiments of network node 2160 can include additional components beyond those shown in
As used herein, wireless device (WD) refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term WD can be used interchangeably herein with user equipment (UE). Communicating wirelessly can involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. In some embodiments, a WD can be configured to transmit and/or receive information without direct human interaction. For instance, a WD can be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE). a vehicle-mounted wireless terminal device, etc.
A WD can support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and can in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (IoT) scenario, a WD can represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another WD and/or a network node. The WD can in this case be a machine-to-machine (M2M) device, which can in a 3GPP context be referred to as an MTC device. As one particular example, the WD can be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a WD can represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above can represent the endpoint of a wireless connection, in which case the device can be referred to as a wireless terminal. Furthermore, a WD as described above can be mobile, in which case it can also be referred to as a mobile device or a mobile terminal.
As illustrated, wireless device 2110 includes antenna 2111, interface 2114, processing circuitry 2120, device readable medium 2130, user interface equipment 2132, auxiliary equipment 2134, power source 2136 and power circuitry 2137. WD 2110 can include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 2110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies can be integrated into the same or different chips or set of chips as other components within WD 2110.
Antenna 2111 can include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 2114. In certain alternative embodiments, antenna 2111 can be separate from WD 2110 and be connectable to WD 2110 through an interface or port. Antenna 2111, interface 2114, and/or processing circuitry 2120 can be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals can be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna 2111 can be considered an interface.
As illustrated, interface 2114 comprises radio front end circuitry 2112 and antenna 2111. Radio front end circuitry 2112 comprise one or more filters 2118 and amplifiers 2116. Radio front end circuitry 2114 is connected to antenna 2111 and processing circuitry 2120 and can be configured to condition signals communicated between antenna 2111 and processing circuitry 2120. Radio front end circuitry 2112 can be coupled to or a part of antenna 2111. In some embodiments, WD 2110 may not include separate radio front end circuitry 2112; rather, processing circuitry 2120 can comprise radio front end circuitry and can be connected to antenna 2111. Similarly, in some embodiments, some or all of RF transceiver circuitry 2122 can be considered a part of interface 2114. Radio front end circuitry 2112 can receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 2112 can convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 2118 and/or amplifiers 2116. The radio signal can then be transmitted via antenna 2111. Similarly, when receiving data, antenna 2111 can collect radio signals which are then converted into digital data by radio front end circuitry 2112. The digital data can be passed to processing circuitry 2120. In other embodiments, the interface can comprise different components and/or different combinations of components.
Processing circuitry 2120 can comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD 2110 components, such as device readable medium 2130, WD 2110 functionality. Such functionality can include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 2120 can execute instructions stored in device readable medium 2130 or in memory within processing circuitry 2120 to provide the functionality disclosed herein.
As illustrated, processing circuitry 2120 includes one or more of RF transceiver circuitry 2122, baseband processing circuitry 2124, and application processing circuitry 2126. In other embodiments, the processing circuitry can comprise different components and/or different combinations of components. In certain embodiments processing circuitry 2120 of WD 2110 can comprise a SOC. In some embodiments, RF transceiver circuitry 2122, baseband processing circuitry 2124, and application processing circuitry 2126 can be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry 2124 and application processing circuitry 2126 can be combined into one chip or set of chips, and RF transceiver circuitry 2122 can be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry 2122 and baseband processing circuitry 2124 can be on the same chip or set of chips, and application processing circuitry 2126 can be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry 2122, baseband processing circuitry 2124, and application processing circuitry 2126 can be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry 2122 can be a part of interface 2114. RF transceiver circuitry 2122 can condition RF signals for processing circuitry 2120.
In certain embodiments, some or all of the functionality described herein as being performed by a WD can be provided by processing circuitry 2120 executing instructions stored on device readable medium 2130, which in certain embodiments can be a computer-readable storage medium. In alternative embodiments, some or all of the functionality can be provided by processing circuitry 2120 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 2120 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 2120 alone or to other components of WD 2110, but are enjoyed by WD 2110 as a whole, and/or by end users and the wireless network generally.
Processing circuitry 2120 can be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry 2120, can include processing information obtained by processing circuitry 2120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 2110, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
Device readable medium 2130 can be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 2120. Device readable medium 2130 can 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 a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that can be used by processing circuitry 2120. In some embodiments, processing circuitry 2120 and device readable medium 2130 can be considered to be integrated.
User interface equipment 2132 can include components that allow and/or facilitate a human user to interact with WD 2110. Such interaction can be of many forms, such as visual, audial, tactile, etc. User interface equipment 2132 can be operable to produce output to the user and to allow and/or facilitate the user to provide input to WD 2110. The type of interaction can vary depending on the type of user interface equipment 2132 installed in WD 2110. For example, if WD 2110 is a smart phone, the interaction can be via a touch screen; if WD 2110 is a smart meter, the interaction can be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface equipment 2132 can include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 2132 can be configured to allow and/or facilitate input of information into WD 2110 and is connected to processing circuitry 2120 to allow and/or facilitate processing circuitry 2120 to process the input information. User interface equipment 2132 can include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment 2132 is also configured to allow and/or facilitate output of information from WD 2110, and to allow and/or facilitate processing circuitry 2120 to output information from WD 2110. User interface equipment 2132 can include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment 2132, WD 2110 can communicate with end users and/or the wireless network and allow and/or facilitate them to benefit from the functionality described herein.
Auxiliary equipment 2134 is operable to provide more specific functionality which may not be generally performed by WDs. This can comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment 2134 can vary depending on the embodiment and/or scenario.
Power source 2136 can, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, can also be used. WD 2110 can further comprise power circuitry 2137 for delivering power from power source 2136 to the various parts of WD 2110 which need power from power source 2136 to carry out any functionality described or indicated herein. Power circuitry 2137 can in certain embodiments comprise power management circuitry. Power circuitry 2137 can additionally or alternatively be operable to receive power from an external power source; in which case WD 2110 can be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry 2137 can also in certain embodiments be operable to deliver power from an external power source to power source 2136. This can be, for example, for the charging of power source 2136. Power circuitry 2137 can perform any converting or other modification to the power from power source 2136 to make it suitable for supply to the respective components of WD 2110.
In
In
In the depicted embodiment, input/output interface 2205 can be configured to provide a communication interface to an input device, output device, or input and output device. UE 2200 can be configured to use an output device via input/output interface 2205. An output device can use the same type of interface port as an input device. For example, a USB port can be used to provide input to and output from UE 2200. The output device can be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. UE 2200 can be configured to use an input device via input/output interface 2205 to allow and/or facilitate a user to capture information into UE 2200. The input device can include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display can include a capacitive or resistive touch sensor to sense input from a user. A sensor can be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like 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.
In
RAM 2217 can be configured to interface via bus 2202 to processing circuitry 2201 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM 2219 can be configured to provide computer instructions or data to processing circuitry 2201. For example, ROM 2219 can be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory. Storage medium 2221 can be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium 2221 can be configured to include operating system 2223, application program 2225 such as a web browser application, a widget or gadget engine or another application, and data file 2227. Storage medium 2221 can store, for use by UE 2200, any of a variety of various operating systems or combinations of operating systems.
Storage medium 2221 can be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof. Storage medium 2221 can allow and/or facilitate UE 2200 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system can be tangibly embodied in storage medium 2221, which can comprise a device readable medium.
In
In the illustrated embodiment, the communication functions of communication subsystem 2231 can include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. For example, communication subsystem 2231 can include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network 2243b can encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 2243b can be a cellular network, a Wi-Fi network, and/or a near-field network. Power source 2213 can be configured to provide alternating current (AC) or direct current (DC) power to components of UE 2200.
The features, benefits and/or functions described herein can be implemented in one of the components of UE 2200 or partitioned across multiple components of UE 2200. Further, the features, benefits, and/or functions described herein can be implemented in any combination of hardware, software or firmware. In one example, communication subsystem 2231 can be configured to include any of the components described herein. Further, processing circuitry 2201 can be configured to communicate with any of such components over bus 2202. In another example, any of such components can be represented by program instructions stored in memory that when executed by processing circuitry 2201 perform the corresponding functions described herein. In another example, the functionality of any of such components can be partitioned between processing circuitry 2201 and communication subsystem 2231. In another example, the non-computationally intensive functions of any of such components can be implemented in software or firmware and the computationally intensive functions can be implemented in hardware.
In some embodiments, some or all of the functions described herein can be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 2300 hosted by one or more of hardware nodes 2330. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node can be entirely virtualized.
The functions can be implemented by one or more applications 2320 (which can alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Applications 2320 are run in virtualization environment 2300 which provides hardware 2330 comprising processing circuitry 2360 and memory 2390. Memory 2390 contains instructions 2395 executable by processing circuitry 2360 whereby application 2320 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.
Virtualization environment 2300, comprises general-purpose or special-purpose network hardware devices 2330 comprising a set of one or more processors or processing circuitry 2360, which can be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device can comprise memory 2390-1 which can be non-persistent memory for temporarily storing instructions 2395 or software executed by processing circuitry 2360. Each hardware device can comprise one or more network interface controllers (NICs) 2370, also known as network interface cards, which include physical network interface 2380. Each hardware device can also include non-transitory, persistent, machine-readable storage media 2390-2 having stored therein software 2395 and/or instructions executable by processing circuitry 2360. Software 2395 can include any type of software including software for instantiating one or more virtualization layers 2350 (also referred to as hypervisors), software to execute virtual machines 2340 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.
Virtual machines 2340, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and can be run by a corresponding virtualization layer 2350 or hypervisor. Different embodiments of the instance of virtual appliance 2320 can be implemented on one or more of virtual machines 2340, and the implementations can be made in different ways.
During operation, processing circuitry 2360 executes software 2395 to instantiate the hypervisor or virtualization layer 2350, which can sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 2350 can present a virtual operating platform that appears like networking hardware to virtual machine 2340.
As shown in
Virtualization of the hardware is in some contexts 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, which can be located in data centers, and customer premise equipment.
In the context of NFV, virtual machine 2340 can be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of virtual machines 2340, and that part of hardware 2330 that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines 2340, forms a separate virtual network elements (VNE).
Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines 2340 on top of hardware networking infrastructure 2330 and corresponds to application 2320 in
In some embodiments, one or more radio units 23200 that each include one or more transmitters 23220 and one or more receivers 23210 can be coupled to one or more antennas 23225. Radio units 23200 can communicate directly with hardware nodes 2330 via one or more appropriate network interfaces and can be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.
In some embodiments, some signaling can be effected with the use of control system 23230 which can alternatively be used for communication between the hardware nodes 2330 and radio units 23200.
With reference to
Telecommunication network 2410 is itself connected to host computer 2430, which can be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. Host computer 2430 can be under the ownership or control of a service provider or can be operated by the service provider or on behalf of the service provider. Connections 2421 and 2422 between telecommunication network 2410 and host computer 2430 can extend directly from core network 2414 to host computer 2430 or can go via an optional intermediate network 2420. Intermediate network 2420 can be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 2420, if any, can be a backbone network or the Internet; in particular, intermediate network 2420 can comprise two or more sub-networks (not shown).
The communication system of
Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to
Communication system 2500 can also include base station 2520 provided in a telecommunication system and comprising hardware 2525 enabling it to communicate with host computer 2510 and with UE 2530. Hardware 2525 can include communication interface 2526 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 2500, as well as radio interface 2527 for setting up and maintaining at least wireless connection 2570 with UE 2530 located in a coverage area (not shown in
Communication system 2500 can also include UE 2530 already referred to. Its hardware 2535 can include radio interface 2537 configured to set up and maintain wireless connection 2570 with a base station serving a coverage area in which UE 2530 is currently located. Hardware 2535 of UE 2530 can also include processing circuitry 2538, which can comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE 2530 further comprises software 2531, which is stored in or accessible by UE 2530 and executable by processing circuitry 2538. Software 2531 includes client application 2532. Client application 2532 can be operable to provide a service to a human or non-human user via UE 2530, with the support of host computer 2510. In host computer 2510, an executing host application 2512 can communicate with the executing client application 2532 via OTT connection 2550 terminating at UE 2530 and host computer 2510. In providing the service to the user, client application 2532 can receive request data from host application 2512 and provide user data in response to the request data. OTT connection 2550 can transfer both the request data and the user data. Client application 2532 can interact with the user to generate the user data that it provides.
It is noted that host computer 2510, base station 2520 and UE 2530 illustrated in
In
Wireless connection 2570 between UE 2530 and base station 2520 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 2530 using OTT connection 2550, in which wireless connection 2570 forms the last segment. More precisely, the exemplary embodiments disclosed herein enable proper routing of the incoming packets to the proper path (i.e., a next IAB node or the destination UE), as well as the mapping to the proper bearer in that path by enhancing the F1-AP and RRC protocols. The techniques described herein take advantage of existing RRC and F1-AP protocols, or even existing procedures, to realize the setup and reconfiguration of adaptation layers that are needed for routing packets to the right path (i.e., next node) and mapping them to the right bearer within the correct path. These and other advantages can facilitate more timely design, implementation, and deployment of 5G/NR solutions. Furthermore, such embodiments can facilitate flexible and timely control of data session QoS, which can lead to improvements in capacity, throughput, latency, etc. that are envisioned by 5G/NR and important for the growth of OTT services.
A measurement procedure can be provided for the purpose of monitoring data rate, latency and other network operational aspects on which the one or more embodiments improve. There can further be an optional network functionality for reconfiguring OTT connection 2550 between host computer 2510 and UE 2530, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection 2550 can be implemented in software 2511 and hardware 2515 of host computer 2510 or in software 2531 and hardware 2535 of UE 2530, or both. In embodiments, sensors (not shown) can be deployed in or in association with communication devices through which OTT connection 2550 passes; the sensors can participate in the measurement procedure by supplying values of the monitored quantities exemplified above or supplying values of other physical quantities from which software 2511, 2531 can compute or estimate the monitored quantities. The reconfiguring of OTT connection 2550 can include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 2520, and it can be unknown or imperceptible to base station 2520. Such procedures and functionalities can be known and practiced in the art. In certain embodiments, measurements can involve proprietary UE signaling facilitating host computer 2510's measurements of throughput, propagation times, latency and the like. The measurements can be implemented in that software 2511 and 2531 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 2550 while it monitors propagation times, errors etc.
In some exemplary embodiments, the base station 2520 in
The base station 2520 may be a donor gNB in some exemplary embodiments, with an F1 interface defined between the central unit 2610 and each of the distributed units 2630, for configuring an adaptation layer for communicating with a relay node through a distributed unit 2630 of the donor base station. The central unit 2610 may have processing circuitry configured, for example, to use RRC signaling to establish a packet data unit (PDU) session for a mobile terminal (MT) part of the relay node and, after establishing the PDU session, configure an F1 adaptation layer in a protocol stack for the MT part of the relay node, the F1 adaptation layer providing for F1 signaling between the central unit of the donor base station and the relay node. The processing circuitry may also be configured to, after configuring the F1 adaptation layer for the MT part of the relay node, set up an F1 adaptation layer for a distributed unit part of the relay node, for communication with a first further relay node downstream of the relay node, using F1 signaling with the relay node, the F1 adaptation layer for the distributed unit part of the relay node being configured to forward packets exchanged between the central unit of the donor base station and the first further relay node.
The central unit 2610 may include processing circuitry 2612 that is operatively associated with the communication circuitry 2618. In an example embodiment, the processing circuitry 2612 comprises one or more digital processors 2614, e.g., one or more microprocessors, microcontrollers, Digital Signal Processors (DSPs), Field Programmable Gate Arrays (FPGAs), Complex Programmable Logic Devices (CPLDs), Application Specific Integrated Circuits (ASICs), or any mix thereof. More generally, the processing circuitry 2612 may comprise fixed circuitry, or programmable circuitry that is specially configured via the execution of program instructions implementing the functionality taught herein.
The processing circuitry 2612 also includes or is associated with storage 2616. The storage 2616, in some embodiments, stores one or more computer programs and, optionally, configuration data. The storage 2616 provides non-transitory storage for the computer program and it may comprise one or more types of computer-readable media, such as disk storage, solid-state memory storage, or any mix thereof. By way of non-limiting example, the storage 2616 comprises any one or more of SRAM, DRAM, EEPROM, and FLASH memory.
In general, the storage 2616 comprises one or more types of computer-readable storage media providing non-transitory storage of the computer program and any configuration data used by the base station. Here, “non-transitory” means permanent, semi-permanent, or at least temporarily persistent storage and encompasses both long-term storage in non-volatile memory and storage in working memory, e.g., for program execution.
In some embodiments, the processing circuitry 2612 is configured to perform the method shown in
As explained earlier, a gNB-CU may be split into multiple entities. This includes gNB-CU-UPs, which serve the user plane and host the PDCP protocol, and one gNB-CU-CP, which serves the control plane and hosts the PDCP and RRC protocol. These two entities are shown as separate control units in
The IAB/relay node 2900 may include processing circuitry 2930 that is operatively associated with or controls the radio circuitry 2912, 2922. In an example embodiment, the processing circuitry 2930 comprises one or more digital processors, e.g., one or more microprocessors, microcontrollers, Digital Signal Processors (DSPs), Field Programmable Gate Arrays (FPGAs), Complex Programmable Logic Devices (CPLDs), Application Specific Integrated Circuits (ASICs), or any mix thereof. More generally, the processing circuitry 2930 may comprise fixed circuitry, or programmable circuitry that is specially configured via the execution of program instructions implementing the functionality taught herein.
The processing circuitry 2930 also includes or is associated with storage. The storage, in some embodiments, stores one or more computer programs and, optionally, configuration data. The storage provides non-transitory storage for the computer program and it may comprise one or more types of computer-readable media, such as disk storage, solid-state memory storage, or any mix thereof. By way of non-limiting example, the storage comprises any one or more of SRAM, DRAM, EEPROM, and FLASH memory.
In general, the storage comprises one or more types of computer-readable storage media providing non-transitory storage of the computer program and any configuration data used by the base station. Here, “non-transitory” means permanent, semi-permanent, or at least temporarily persistent storage and encompasses both long-term storage in non-volatile memory and storage in working memory, e.g., for program execution.
According to some embodiments, the processing circuitry 2930 of the IAB/relay node 2900 is configured to map end-user bearers to backhaul bearers in an adaptation layer. The processing circuitry 2930 is configured to map a plurality of end-user bearers to backhaul bearers in consideration of QoS classes for the end-user bearers and a distance from the relay node to a destination node for each of the plurality of end-user bearers, such that at least one of the backhaul bearers carries end-user bearers with different QoS classes and different distances to the destination node. In some embodiments the processing circuitry 2930 considers the distance from the relay node to the destination node for at least one of the end-user bearers in terms of a number of remaining hops from the relay node to the destination node, when performing the mapping. In some of these and in some other embodiments, the processing circuitry 2930 considers the distance from the relay node to the destination node for at least one of the end-user bearers in terms of an estimated end-to-end delay from the relay node to the destination node, when performing the mapping.
In some embodiments, the processing circuit 2930 maps an end-user bearer having a highest-priority traffic, as indicated by the QoS class of the end-user bearer, and having a largest distance, as indicated by the distance from the relay node to the destination node for the end-user bearer, to a separate, unshared, backhaul bearer. In some embodiments, the processing circuit 2930 maps end-user bearers to backhaul bearers in consideration of QoS classes for the end-user bearers and the distance from the relay node to the destination node for each end-user bearer comprises mapping at least one end-user bearer having low-priority traffic and a distant destination node, as indicated by the QoS class and the distance from the relay node to the destination node for the at least one end-user bearer, to a same backhaul bearer as at least one additional end-user bearer having high-priority traffic and a nearby destination, as indicated by the QoS class and the distance from the relay node to the destination ode for the at least one additional end-user bearer.
In some embodiments, the processing circuit 2930 is further configured to detect, in adaptation headers for each packet of at least one end-user bearer, a time-to-live value indicating a packet-delay requirement for the packet, and, upon forwarding the packet to a next node, to modify the time-to-live value to reflect time spent by the packet in the relay node.
In some embodiments, the processing circuitry 2930 is configured to perform the method shown in
As shown at block 3402, the example method comprises the step of mapping a plurality of end-user bearers to backhaul bearers in consideration of QoS classes for the end-user bearers and a distance from the node to a destination node for each of the plurality of end-user bearers, such that at least one of the backhaul bearers carries end-user bearers with different QoS classes and different distances to the destination node. In some embodiments, this mapping considers the distance from the node to the destination node for at least one of the end-user bearers in terms of a number of remaining hops from the node to the destination node. In some of these and in some other embodiments, the mapping considers the distance from the node to the destination node for at least one of the end-user bearers in terms of an estimated end-to-end delay from the node to the destination node.
In some embodiments, the method comprises mapping an end-user bearer having a highest-priority traffic, as indicated by the QoS class of the end-user bearer, and having a largest distance, as indicated by the distance from the node to the destination node for the end-user bearer, to a separate, unshared, backhaul bearer. In some embodiments, mapping end-user bearers to backhaul bearers in consideration of QoS classes for the end-user bearers and the distance from the node to the destination node for each end-user bearer comprises mapping at least one end-user bearer having low-priority traffic and a distant destination node, as indicated by the QoS class and the distance from the node to the destination node for the at least one end-user bearer, to a same backhaul bearer as at least one additional end-user bearer having high-priority traffic and a nearby destination, as indicated by the QoS class and the distance from the node to the destination node for the at least one additional end-user bearer.
In some embodiments, the method further includes, as shown at blocks 3404 and 3406, the steps of detecting, in adaptation headers for each packet of at least one end-user bearer, a time-to-live value indicating a packet-delay requirement for the packet, and, upon forwarding the packet to a next node, modifying the time-to-live value to reflect time spent by the packet in the node.
The term unit can have conventional meaning in the field of electronics, electrical devices and/or electronic devices and can include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
Example embodiments of the techniques and apparatus described herein include, but are not limited to, the following enumerated examples:
| Number | Name | Date | Kind |
|---|---|---|---|
| 8724472 | Huang et al. | May 2014 | B2 |
| 9860786 | Wang et al. | Jan 2018 | B1 |
| 10045356 | Gerkis | Aug 2018 | B2 |
| 10158555 | Ghosh | Dec 2018 | B2 |
| 10206138 | Cao | Feb 2019 | B2 |
| 10341898 | Mehta | Jul 2019 | B2 |
| 20080298251 | Khuu | Dec 2008 | A1 |
| 20100014444 | Ghanadan | Jan 2010 | A1 |
| 20100272007 | Shen | Oct 2010 | A1 |
| 20110194483 | Ji | Aug 2011 | A1 |
| 20110206094 | Zhang et al. | Aug 2011 | A1 |
| 20110235514 | Huang et al. | Sep 2011 | A1 |
| 20120002594 | Racz | Jan 2012 | A1 |
| 20120294226 | Racz | Nov 2012 | A1 |
| 20120300648 | Yang | Nov 2012 | A1 |
| 20120307668 | Wiemann | Dec 2012 | A1 |
| 20130039185 | Teyeb | Feb 2013 | A1 |
| 20130143574 | Teyeb | Jun 2013 | A1 |
| 20130336199 | Schwartz | Dec 2013 | A1 |
| 20150063122 | Chiang | Mar 2015 | A1 |
| 20150138977 | Dacosta | May 2015 | A1 |
| 20160029403 | Roy | Jan 2016 | A1 |
| 20160112896 | Karampatsis | Apr 2016 | A1 |
| 20170171837 | Chen | Jun 2017 | A1 |
| 20170245171 | Jung | Aug 2017 | A1 |
| 20170331670 | Parkvall | Nov 2017 | A1 |
| 20180092139 | Novlan et al. | Mar 2018 | A1 |
| 20180124633 | Hwang | May 2018 | A1 |
| 20190044754 | Hampel | Feb 2019 | A1 |
| 20190215055 | Majmundar | Jul 2019 | A1 |
| 20190289492 | Hampel | Sep 2019 | A1 |
| 20200007223 | Zhu | Jan 2020 | A1 |
| 20200029384 | Hong | Jan 2020 | A1 |
| Number | Date | Country |
|---|---|---|
| 2437564 | Apr 2012 | EP |
| 2010107357 | Sep 2010 | WO |
| 2012125095 | Sep 2012 | WO |
| 2019139524 | Jul 2019 | WO |
| Entry |
|---|
| Hussain et al., “A QoS-aware dynamic bandwidth allocation scheme for multi-hop WiFi-based long distance networks”, 2015, Eurasip J. Wireless Commun. Netw., No. 1, pp. 1-18 (Year: 2015). |
| Lee et al., “QoS-guaranteed Transmission Scheme Selection for OFDMA Multi-hop Cellular Networks”, Jun. 2007, IEEE International Conference on Communications, pp. 4587-4591 (Year: 2007). |
| Draves et al., “Routing in Multi-Radio, Multi-Hop Wireless Mesh Networks”, 2004, ACM Annual International Conference on Mobile Computing and Networking (MOBICOM), 2004, pp. 114-128 (Year: 2004). |
| 3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Stage 2 (Release 15)”, 3GPP TS 37.340 V15.1.0, Mar. 2018, 1-52. |
| 3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; F1 application protocol (F1AP) (Release 15)”, 3GPP TS 38.473 V15.1.1, Apr. 2018, 1-106. |
| 3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2 (Release 15) The present”, 3GPP TS 38.300 V0.6.0, Aug. 2018, 1-58. |
| 3GPP, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3GPP System Architecture Evolution (SAE); Security architecture (Release 15)”, 3GPP TS 33.401 V15.3.0, Mach 2018, 1-163. |
| 3GPP, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 15)”, 3GPP TS 23.501 V15.1.0, Mar. 2018, 1-201. |
| 3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on new radio access technology: Radio access architecture and interfaces (Release 14)”, 3GPP TR 38.801 V14.0.0 (Mar. 2017), Mar. 2017, 1-91. |
| 3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Architecture description (Release 15)”, 3GPP TS 38.401 V15.1.0 (Mar. 2018), Mar. 2018, 1-23. |
| Unknown, Author , “IAB U-plane considerations for architecture group 1”, Qualcomm Incorporated (Rapporteur), 3GPP TSG-RAN WG2 Meeting #101bis, R2-1806456, Sanya, China, Apr. 16-20, 2018, 1-5. |
| Unknown, Author , “pCR for TR 38.874”, Qualcomm Inc. et al., 3GPP TSG-RAN WG3 Meeting #99bis, R3-182458, Sanya, China, Apr. 16-20, 2018, 1-6. |
| Unknown Author, “Way Forward—IAB Architecture for L2/3 relaying”, 3GPP TSG-RAN WG3 Meeting #99; R3-181502; Athens, Greece, Jan. 26-Mar. 2, 2018, 1-6. |
| “3GPP TS 38.300 V15.1.0”; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2 (Release 15), Mar. 2018, pp. 1-71. |
| 3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; F1 application protocol (F1AP) (Release 15)”, 3GPP TS 38.473 V15.2.0, May 2018, 1-161. |
| 3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; F1 data transport (Release 15)”, 3GPP TS 38.474 V15.1.0, May 2018, 1-8. |
| 3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on Integrated Access and Backhaul; (Release 15)”, 3GPP TR 38.874 V0.3.2, May 2018, 1-39. |
| Unknown, Author , “IAB—C-plane transport in L2-relaying architecture”, 3GPP TSG-RAN WG3 Meeting #99bis, R3-181946, Sanya, China, Apr. 16-20, 2018, 1-5. |
| 3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; F1 data transport (Release 15)”, 3GPP TS 38.474 V15.0.0, Jan. 2018, 1-8. |
| 3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Architecture description (Release 15)”, 3GPP TS 38.401 V15.2.0, Jun. 2018, 1-39. |
| 3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; F1 application protocol (F1AP) (Release 15)”, 3GPP TS 38.473 V15.2.1, Jul. 2018, 1-161. |
| 3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; F1 general aspects and principles (Release 15)”, 3GPP TS 38.470 V15.2.0, Jun. 2018, 1-12. |
| 3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2 (Release 15)”, 3GPP TS 38.300 V15.2.0, Jun. 2018, 1-87. |
| 3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on Integrated Access and Backhaul; (Release 15) the present”, 3GPP TR 38.874 V0.2.1, May 2018, 1-19. |
| AT&T, “L2-based multi-hop architecture to support IAB architecture requirements”, 3GPP TSG-RAN WG3 #99, R3-181345, Athens, Greece, Feb. 26-Mar. 2, 2018, 1-8. |
| Babiarz, J., et al., “Configuration Guidelines for DiffServ Service Classes”, IETF Network Working Group, RFC 4594, Aug. 2006, 1-57. |
| Ericsson, “Protection of internal gNB interfaces”, 3GPP TSG-SA WG3 Meeting #91Bis, S3-181838, La Jolla (US), May 21-25, 2018, 1-2. |
| Ericsson, “Protection of internal gNB interfaces”, 3GPP TSG-SA WG3 Meeting #91Bis, S3-182047, revision of S3-181838, La Jolla (US), May 21-25, 2018, 1-3. |
| Huawei, “Overview of RAN2 IAB Impacts”, 3GPP TSG-RAN WG2#101bis, R2-1806178, Sanya, China, Apr. 16-20, 2018, 1-7. |
| Intel Corporation, “IAB Topology management and route management”, 3GPP TSG-RAN WG2 Meeting #102, R2-1807340, Busan, Korea, May 21-25, 2018, 1-4. |
| Tuexen, M., et al., “Datagram Transport Layer Security (DTLS) for Stream Control Transmission Protocol (SCTP)”, Internet Engineering Task Force (IETF); Request for Comments: 6083; Category: Standards Track; ISSN: 2070-1721, Jan. 2011, 1-9. |
| Zte, “Consideration on RLC ARQ in IAB”, 3GPP TSG-RAN WG2 Meeting #102, R2-1807396, Busan, Korea, May 21-25, 2018, 1-6. |
| Number | Date | Country | |
|---|---|---|---|
| 20190349834 A1 | Nov 2019 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62669550 | May 2018 | US |
