Patent ID: 12225600

DETAILED DESCRIPTION

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 disclosed embodiments will be apparent from the following description.

Exemplary embodiments of the present disclosure are described in terms of an LTE eNB in the role of MN and an NR gNB in the role of SN. Nevertheless, this is merely for the purposes of illustrating features, benefits, and/or underlying principles. As such, a person skilled in the art will readily comprehend that the features, benefits, and/or principles apply equally to other embodiments in which a gNB is MN and the SN is an eNB or another gNB. Furthermore, such features, benefits, and/or principles can also apply to when the SN is a node in a non-3GPP radio access network (RAN).

Furthermore, although the descriptions below are given in terms of specific group identifiers (e.g., SPID), these are merely exemplary and other group identifiers can be utilized in the same or substantially similar manner. Moreover, information related to, or representing, such group identifiers can also be communicated instead of the specifically mentioned group identifiers. For example, rather than communicating an SPID from MN to SN, such information may be conveyed as an RFSP when the SN is connected to the 5GC.

As mentioned above, there are various problems, drawbacks, and/or issues related to identifying groups of users that can prevent and/or inhibit the deployment of EN-DC for networks that employ slicing. These are discussed in more detail below.

Policies for “slicing” in LTE (e.g., E-UTRAN and EPC) can be based on one or a combination of the following identifiers related to user, groups, and/or networks:Public Land Mobile Network ID (PLMN-id) (e.g., “network sharing”);Quality of Service (QoS) Class Identifier (QCI);Subscribers Profile ID for RAT/Frequency Priority (SPID) (e.g., inbound roamers are assigned a certain SPID);Dedicated Core Network ID (DCN-id) (e.g., users belonging to the public safety DCN shall be treated according to a certain policy);MME Group Identity (MMEGI); and/orMembership of a Closed Subscriber Group (CSG).
In LTE, all identifiers and information received from the EPC are available to the eNB and can be used for network resource management (“slicing”) between groups of users.FIG.9illustrates examples of how different “slices” of a RAN (e.g., E-UTRAN) can be identified based on various identifiers, including the ones mentioned above. More specifically, two public land mobile networks (PLMNs) X and Y utilize four different slices of a shared RAN. PLMN X utilizes RAN slice1, which two core network (CN) instances in PLMN Y utilize RAN slices2-4. The RAN slice definition/configuration table shows various exemplary identifiers associated with each of these RAN slices.FIG.10further illustrates how the four RAN slices shown inFIG.9can be associated with various scheduling parameters (e.g., via a flexible QoS feature table) that can be applied to RAN resource scheduling according to particular radio resource policies (RRP) and RAN resource partitioning shares.

It is expected that initial 5G deployments will use EN-DC, with LTE eNB as MN (e.g., MeNB) and with an interface to the 4G EPC. In such case, a NR gNB is SN (e.g., SgNB) and, as such, receives requests to establish resources over X2 from the MeNB. A general principle is that LTE resources are managed by the MeNB, while the SgNB has a large degree of autonomy in managing NR resources. Nevertheless, although there are many possible identifiers could be used as basis for group-level radio resource management according to a policy (“slicing”) in EN-DC, the MN (e.g., MeNB) only sends a subset of these identifiers to the SN (e.g., SgNB), in particular the UE PLMN-id and QCI per bearer. For example, the UE's SPID and DCN-id are not available over the X2 (or Xn) interface. As such, this lack of information prevents the NR RAN (e.g., gNB) from controlling network resources according to the same range of policies available to the LTE RAN (e.g., eNB). In short, the possibilities for slicing of NR resources are limited compared to what is possible for LTE.

In some exemplary embodiments, when the MN (e.g., MeNB) has received or determined an SPID group identifier from the EPC, it forwards it in an SN Setup Request (e.g., X2: SgNB Addition Request message) to the SN (e.g., SgNB). In some exemplary embodiments, when the MN has received or determined a valid DCN-id group identifier for the UE, it forwards it in the SN Setup Request to the SN. In some embodiments, both SPID and DCN-id can be sent in the same SN Setup Request message.

In other exemplary embodiments, the MN can perform an operator-configurable mapping of a group identifier to other information relating to the group identifier (e.g., a new parameter). For example, the MN can map the DCN-id to a “DCN resource index” and send this to the SN. Such a mapping can serve the purpose of abstracting information about the CN connected to the MN, so as not to expose such information to the SN. Rather, mapping the DCN-id to an index can facilitate providing the SN with only the information needed to understand the index values and how they map to a specific policy for the UE.

When the SgNB receives a SN setup request with SPID and/or a DCN-related parameter, it can use this for management of NR resources according to an operator-configured policy. As an example, if the SPID and or DCN-ID identify a policy for which a predefined pool of resources can be used by the UE, the SN can enable such policy and, e.g., prioritize the UE's access to resources of the NR RAN, over access by other UEs that are not associated by the identified policy (e.g., not identified by the SPID and/or DCN-id and/or related parameters).

More generally, the SN can use any combination of SPID, DCN-related information, PLMN-id, QCI, CSG membership, etc. to define groups of users and/or an appropriate resource management policy that relates to the UE's active services and/or services identified with the profile of a subscriber associated with the UE. For example, in the context of NR resource scheduling (e.g., in an NR scheduler), the SN can guarantee that a particular group of users—defined in any of the ways described above—can access a predefined proportion of resources (e.g., radio resources) that can be allocated by the SN. In other words, when there is no congestion in the NR RAN, resources can be assigned to any user regardless of this policy. On the other hand, when congestion occurs in the NR RAN, the defined group of users can receive, upon request, the predetermined proportion of resources in the NR RAN. In other words, the defined group of users is prioritized over other users who are not included in the defined group.

In other exemplary embodiments, the SN can also use policies per group of users for other NR resource management tasks. For example, the NR RAN allocates frequency-domain resources based on division into multiple bandwidth parts (BWPs) that cover the available frequency spectrum. Accordingly, the SN can prioritize access to the various BWPs and/or frequency ranges within the various BWPs based on membership in the defined groups.

Various group information for a particular UE can be sent from the MN to the SN in various ways. In one exemplary embodiment, SPID information can be encoded in an SgNB Addition Request message sent by the MN (e.g., MeNB) to request the preparation of resources for EN-DC operation for a specific UE.FIG.11, comprisingFIGS.11A and11B, shows an exemplary format of an SgNB Addition Request message, according to some exemplary embodiments of the present disclosure. In other exemplary embodiments, other messages such as SgNB Modification Request can be used to carry various types of group information for a particular UE.

In other exemplary embodiments, the SN can be arranged in a split configuration comprising a Central Unit (CU) hosting higher layers such as RRC/PDCP and a Distributed Unit (DU) hosting lower layers such as RLC/MAC/PHY, as described briefly above. For example, the SN can be arranged as a gNB-CU and a gNB-DU. In such embodiments, after receiving information relating to one or more group identifier (e.g., SPID, RFSP, DCN-id, etc.) from the MN over an Xn interface, the gNB-CU can forward all, or a portion of, the received information to the gNB-DU over the F1 interface. Such information can be useful for group-based radio resource management (RRM) policies that are implemented by, or involve, a scheduler functionality resident in the gNB-DU. Exemplary F1 messages that could be suitable for providing such information include UE Context Setup Request, UE Context Modification Request, and DL RRC Message Transfer. Although described in terms of NR split architecture, such embodiments can also be utilized in LTE split architectures, in which an eNB SN (e.g., SeNB) is divided into an eNB-CU and an eNB-DU. Messages appropriate for the eNB-CU/eNB-DU interface can be employed in a similar manner as described above for NR split architectures.

These and other exemplary embodiments can provide various advantages related to radio resource management in dual connectivity scenarios that are expected to be important for deployment of NR networks. More specifically, such embodiments facilitate “slicing” of radio resources in dual-connectivity scenarios in which a master node (MN) deploying a first RAT (e.g., LTE) and a secondary node (SN) deploying a different second RAT (e.g., NR). The MN and the SN can be part of different RANs, or different portions of a single RAN that deploys two different RATs.

By providing group-related identifiers associated with a UE when initiating dual-connectivity with the SN, such embodiments facilitate at least the same degree of “slicing” in the RAN (or portion) including the second network node as in the RAN (or portion) including the first network node. This can facilitate the deployment of 5G/NR networks to provide additional data capacity to legacy LTE networks via dual-connectivity techniques. These and other advantages and/or benefits can facilitate more timely design, implementation, and deployment of 5G/NR solutions. Furthermore, these and other advantages and/or benefits can lead to improvements in capacity, throughput, latency, etc. that are envisioned by 5G/NR and are important for the growth of over-the-top (OTT) data applications or services external to the 5G network. Moreover, these and other advantages and/or benefits can also lead to improved user experience associated with OTT data applications or services, particularly with respect to service mobility within the 5G network.

FIG.12illustrates an exemplary method and/or procedure performed by a first network node (e.g., eNB) in a radio access network (RAN), in accordance with various exemplary embodiments of the present disclosure. The first network node can be in communication with a second network node (e.g., gNB) having a different radio access technology (RAT) than the first network node. Although the exemplary method and/or procedure is illustrated inFIG.12by blocks in a particular order, this order is exemplary and the operations corresponding to the blocks can be performed in different orders, and can be combined and/or divided into blocks having different functionality than shown inFIG.12. Furthermore, exemplary method and/or procedure shown inFIG.12can be complimentary to exemplary method and/or procedure illustrated inFIG.13below. In other words, exemplary methods and/or procedures shown inFIGS.12and13are capable of being used cooperatively to provide the benefits, advantages, and/or solutions to problems described hereinabove. Optional operations are indicated by dashed lines.

The exemplary method and/or procedure can include the operations of block1210, where the first network node can determine one or more radio resource management (RRM) identifiers associated with at least one of: a user equipment (UE) served by the first network node; a subscriber associated with the UE; and a group of UEs served by the first network node. In some embodiments, the operations of block1210can include the operations of block1212, where the first network node can receive the one or more RRM identifiers from a core network (e.g., a 5GC or an EPC).

The exemplary method and/or procedure can also include the operations of block1220, where the first network node can send a request for the second network node to establish dual connectivity, as a secondary node (SN), with the UE, wherein the request comprises information relating to the one or more RRM identifiers. In some embodiments, the exemplary method and/or procedure can also include the operations of block1230, where the first network node can manage the UE's access to resources of the RAN based on the one or more RRM identifiers. In some embodiments, the first network node can manage the UE's access to resources of the RAN further based on a profile of the subscriber associated with the UE. In some embodiments, the information relating to the one or more RRM identifiers can map to one or more further policies for managing UE access to resources provided by a RAN that includes the second network node. In some embodiments, the one or more policies can be the same as the one or more further policies.

In some embodiments, each of the one or more RRM identifiers can be related to one or more of the following: Subscribers Profile ID for RAT/Frequency Priority (SPID), Dedicated Core Network ID (DCN-id), Public Land Mobile Network ID (PLMN-id), Mobility Management Entity group identity (MMEGI), QoS Class Indicator (QCI), and Closed Subscriber Group (CSG) membership.

In some embodiments, the first network node can be an eNB configured with an LTE RAT, and the second network node can be a gNB configured with an NR RAT. In other embodiments, the second network node can be an eNB configured with an LTE RAT, and the first network node can be a gNB configured with an NR RAT.

In some embodiments, the one or more RRM identifiers can include a Subscriber Profile ID for RAT/Frequency Priority (SPID), and the information relating to the one or more RRM identifiers can include the SPID. In some embodiments, the one or more RRM identifiers can include a RAT/Frequency Selection Priority (RFSP), and the information relating to the one or more RRM identifiers can include the RFSP. In some embodiments, the one or more RRM identifiers can include an SPID, and the information relating to the one or more RRM identifiers can include a RFSP index.

In some embodiments, the one or more RRM identifiers can include a Dedicated Core Network ID (DCN-id) and/or a Mobility Management Entity group identity (MMEGI). In such embodiments, the information relating to the one or more group identifiers can include an index value that maps to one or more policies for managing UE access to resources of a RAN that includes the second network node.

FIG.13illustrates an exemplary method and/or procedure performed by a second network node (e.g., gNB) in a radio access network (RAN), in accordance with various exemplary embodiments of the present disclosure. The second network node can be in communication with a first network node (e.g., eNB) having a different radio access technology (RAT) than the second network node. Although the exemplary method and/or procedure is illustrated inFIG.13by blocks in a particular order, this order is exemplary and the operations corresponding to the blocks can be performed in different orders, and can be combined and/or divided into blocks having different functionality than shown inFIG.13. Furthermore, exemplary method and/or procedure shown inFIG.13can be complimentary to exemplary method and/or procedure illustrated inFIG.12above. In other words, exemplary methods and/or procedures shown inFIGS.12and13are capable of being used cooperatively to provide the benefits, advantages, and/or solutions to problems described hereinabove. Optional operations are indicated by dashed lines.

The exemplary method and/or procedure can include the operations of block1310, where the second network node can receive a request from a first network node to establish dual connectivity, as a secondary node (SN), with a user equipment (UE) served by the first network node, wherein the request comprises information relating to one or more Radio Resource Management (RRM) identifiers that are associated with at least one of: a user equipment (UE) served by the first network node; a subscriber associated with the UE; and a group of UEs served by the first network node. The exemplary method and/or procedure can also include the operations of block1320, where the second network node may map the information relating to the one or more RRM identifiers to one or more policies for managing the UE's access to resources provided by the second network node. In some embodiments, the one or more RRM identifiers can map to one or more further policies for managing UE access to resources provided by a RAN that includes the first network node. In some embodiments, the one or more policies can be the same as the one or more further policies.

The exemplary method and/or procedure can include the operations of block1330, where the second network node can manage the UE's access to the resources in accordance with the one or more policies. In some embodiments, the second network node can manage the UE's access to the resources further based on a profile of the subscriber associated with the UE. In some embodiments, at least one of the policies can prioritize access by UEs associated with the one or more RRM identifiers over access by UEs that are not associated with all of the one or more identifiers. In some embodiments, such a policy can prioritize access by UEs associated with the one or more group identifiers to particular bandwidth part (BWP) frequency resources that are allocated by the second network node. In some embodiments, at least one of the policies can guarantee that UEs associated with the one or more RRM identifiers can access at least a predefined proportion of resources available from the RAN.

In some embodiments, each of the one or more RRM identifiers can be related to one or more of the following: Subscribers Profile ID for RAT/Frequency Priority (SPID), Dedicated Core Network ID (DCN-id), Public Land Mobile Network ID (PLMN-id), Mobility Management Entity group identity (MMEGI), QoS Class Indicator (QCI), and Closed Subscriber Group (CSG) membership.

In other embodiments, the second network node can be an eNB configured with an LTE RAT, and the first network node can be a gNB configured with an NR RAT. In other embodiments, the first network node can be an eNB configured with an LTE RAT, and the second network node can be a gNB configured with an NR RAT. In such embodiments, the gNB second network node can comprise a central unit (CU) and one or more distributed units (DUs). In such embodiments, the request can be received (in block/operation1310) by the CU, and the exemplary method and/or procedure can also include sending (in block/operation1340) at least one of the following to at least one DU: the information relating to the one or more RRM identifiers; and the one or more policies. This information can be sent, e.g., via an F1 interface between the DU(s) and CU.

In some embodiments, if the information relating to the one or more identifiers is sent to the DU(s), the operation of block1340can be part of block1320. In some embodiments, if the one or more policies are sent to the DU(s), the operation of block1340can be part of block1330. Other combinations and/or arrangements are also possible.

In some embodiments, the one or more RRM identifiers can include a Subscriber Profile ID for RAT/Frequency Priority (SPID), and the information relating to the one or more RRM identifiers can include the SPID. In some embodiments, the one or more RRM identifiers can include a RAT/Frequency Selection Priority (RFSP), and the information relating to the one or more RRM identifiers can include the RFSP. In some embodiments, the one or more RRM identifiers can include an SPID, and the information relating to the one or more RRM identifiers can include a RFSP index.

In some embodiments, the one or more RRM identifiers can include a Dedicated Core Network ID (DCN-id) and/or a Mobility Management Entity group identity (MMEGI). In such embodiments, the information relating to the one or more group identifiers can include an index value that maps to one or more policies for managing UE access to resources of a RAN that includes the second network node.

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 inFIG.14. For simplicity, the wireless network ofFIG.14only depicts network1430, network nodes1460and1460b, and WDs1410,1410b, and1410c. In practice, a wireless network can further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node1460and wireless device (WD)1410are depicted with additional detail. The wireless network can provide communication and other types of services to one or more wireless devices to facilitate the wireless devices' access to and/or use of the services provided by, or via, the wireless network.

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 (WLAN) standards, such as the IEEE 810.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.

Network1430can 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 node1460and WD1410comprise 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 can refer 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, thereby to facilitate, 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, pico 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.

InFIG.14, network node1460includes processing circuitry1470, device readable medium1480, interface1490, auxiliary equipment1484, power source1486, power circuitry1487, and antenna1462. Although network node1460illustrated in the example wireless network ofFIG.14can represent a device that includes the illustrated combination of hardware components, other embodiments can comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods and/or procedures disclosed herein. Moreover, while the components of network node1460are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node can comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium1480can comprise multiple separate hard drives as well as multiple RAM modules).

Similarly, network node1460can 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 node1460comprises 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 node1460can be configured to support multiple radio access technologies (RATs). In such embodiments, some components can be duplicated (e.g., separate device readable medium1480for the different RATs) and some components can be reused (e.g., the same antenna1462can be shared by the RATs). Network node1460can also include multiple sets of the various illustrated components for different wireless technologies integrated into network node1460, 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 node1460.

Processing circuitry1470can 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 circuitry1470can include processing information obtained by processing circuitry1470by, 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 circuitry1470can 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 node1460components, such as device readable medium1480, network node1460functionality. For example, processing circuitry1470can execute instructions stored in device readable medium1480or in memory within processing circuitry1470. Such functionality can include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry1470can include a system on a chip (SOC).

In some embodiments, processing circuitry1470can include one or more of radio frequency (RF) transceiver circuitry1472and baseband processing circuitry1474. In some embodiments, radio frequency (RF) transceiver circuitry1472and baseband processing circuitry1474can 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 circuitry1472and baseband processing circuitry1474can 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 circuitry1470executing instructions stored on device readable medium1480or memory within processing circuitry1470. In alternative embodiments, some or all of the functionality can be provided by processing circuitry1470without 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 circuitry1470can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry1470alone or to other components of network node1460, but are enjoyed by network node1460as a whole, and/or by end users and the wireless network generally.

Device readable medium1480can 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 circuitry1470. Device readable medium1480can 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 circuitry1470and, utilized by network node1460. Device readable medium1480can be used to store any calculations made by processing circuitry1470and/or any data received via interface1490. In some embodiments, processing circuitry1470and device readable medium1480can be considered to be integrated.

Interface1490is used in the wired or wireless communication of signalling and/or data between network node1460, network1430, and/or WDs1410. As illustrated, interface1490comprises port(s)/terminal(s)1494to send and receive data, for example to and from network1430over a wired connection. Interface1490also includes radio front end circuitry1492that can be coupled to, or in certain embodiments a part of, antenna1462. Radio front end circuitry1492comprises filters1498and amplifiers1496. Radio front end circuitry1492can be connected to antenna1462and processing circuitry1470. Radio front end circuitry can be configured to condition signals communicated between antenna1462and processing circuitry1470. Radio front end circuitry1492can receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry1492can convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters1498and/or amplifiers1496. The radio signal can then be transmitted via antenna1462. Similarly, when receiving data, antenna1462can collect radio signals which are then converted into digital data by radio front end circuitry1492. The digital data can be passed to processing circuitry1470. In other embodiments, the interface can comprise different components and/or different combinations of components.

In certain alternative embodiments, network node1460may not include separate radio front end circuitry1492, instead, processing circuitry1470can comprise radio front end circuitry and can be connected to antenna1462without separate radio front end circuitry1492. Similarly, in some embodiments, all or some of RF transceiver circuitry1472can be considered a part of interface1490. In still other embodiments, interface1490can include one or more ports or terminals1494, radio front end circuitry1492, and RF transceiver circuitry1472, as part of a radio unit (not shown), and interface1490can communicate with baseband processing circuitry1474, which is part of a digital unit (not shown).

Antenna1462can include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna1462can be coupled to radio front end circuitry1490and can be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna1462can 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, antenna1462can be separate from network node1460and can be connectable to network node1460through an interface or port.

Antenna1462, interface1490, and/or processing circuitry1470can 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, antenna1462, interface1490, and/or processing circuitry1470can 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 circuitry1487can comprise, or be coupled to, power management circuitry and can be configured to supply the components of network node1460with power for performing the functionality described herein. Power circuitry1487can receive power from power source1486. Power source1486and/or power circuitry1487can be configured to provide power to the various components of network node1460in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source1486can either be included in, or external to, power circuitry1487and/or network node1460. For example, network node1460can 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 circuitry1487. As a further example, power source1486can comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry1487. 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 node1460can include additional components beyond those shown inFIG.14that can be responsible for providing certain aspects of the network node's functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, network node1460can include user interface equipment to allow and/or facilitate input of information into network node1460and to allow and/or facilitate output of information from network node1460. This can allow and/or facilitate a user to perform diagnostic, maintenance, repair, and other administrative functions for network node1460.

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 device1410includes antenna1411, interface1414, processing circuitry1420, device readable medium1430, user interface equipment1432, auxiliary equipment1434, power source1436and power circuitry1437. WD1410can include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD1410, 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 WD1410.

Antenna1411can include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface1414. In certain alternative embodiments, antenna1411can be separate from WD1410and be connectable to WD1410through an interface or port. Antenna1411, interface1414, and/or processing circuitry1420can 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 antenna1411can be considered an interface.

As illustrated, interface1414comprises radio front end circuitry1412and antenna1411. Radio front end circuitry1412comprise one or more filters1418and amplifiers1416. Radio front end circuitry1414is connected to antenna1411and processing circuitry1420, and can be configured to condition signals communicated between antenna1411and processing circuitry1420. Radio front end circuitry1412can be coupled to or a part of antenna1411. In some embodiments, WD1410may not include separate radio front end circuitry1412; rather, processing circuitry1420can comprise radio front end circuitry and can be connected to antenna1411. Similarly, in some embodiments, some or all of RF transceiver circuitry1422can be considered a part of interface1414. Radio front end circuitry1412can receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry1412can convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters1418and/or amplifiers1416. The radio signal can then be transmitted via antenna1411. Similarly, when receiving data, antenna1411can collect radio signals which are then converted into digital data by radio front end circuitry1412. The digital data can be passed to processing circuitry1420. In other embodiments, the interface can comprise different components and/or different combinations of components.

Processing circuitry1420can 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 WD1410components, such as device readable medium1430, WD1410functionality. Such functionality can include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry1420can execute instructions stored in device readable medium1430or in memory within processing circuitry1420to provide the functionality disclosed herein.

As illustrated, processing circuitry1420includes one or more of RF transceiver circuitry1422, baseband processing circuitry1424, and application processing circuitry1426. In other embodiments, the processing circuitry can comprise different components and/or different combinations of components. In certain embodiments processing circuitry1420of WD1410can comprise a SOC. In some embodiments, RF transceiver circuitry1422, baseband processing circuitry1424, and application processing circuitry1426can be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry1424and application processing circuitry1426can be combined into one chip or set of chips, and RF transceiver circuitry1422can be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry1422and baseband processing circuitry1424can be on the same chip or set of chips, and application processing circuitry1426can be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry1422, baseband processing circuitry1424, and application processing circuitry1426can be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry1422can be a part of interface1414. RF transceiver circuitry1422can condition RF signals for processing circuitry1420.

In certain embodiments, some or all of the functionality described herein as being performed by a WD can be provided by processing circuitry1420executing instructions stored on device readable medium1430, 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 circuitry1420without 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 circuitry1420can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry1420alone or to other components of WD1410, but are enjoyed by WD1410as a whole, and/or by end users and the wireless network generally.

Processing circuitry1420can 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 circuitry1420, can include processing information obtained by processing circuitry1420by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD1410, 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 medium1430can 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 circuitry1420. Device readable medium1430can 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 circuitry1420. In some embodiments, processing circuitry1420and device readable medium1430can be considered to be integrated.

User interface equipment1432can include components that allow and/or facilitate a human user to interact with WD1410. Such interaction can be of many forms, such as visual, audial, tactile, etc. User interface equipment1432can be operable to produce output to the user and to allow and/or facilitate the user to provide input to WD1410. The type of interaction can vary depending on the type of user interface equipment1432installed in WD1410. For example, if WD1410is a smart phone, the interaction can be via a touch screen; if WD1410is 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 equipment1432can include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment1432can be configured to allow and/or facilitate input of information into WD1410, and is connected to processing circuitry1420to allow and/or facilitate processing circuitry1420to process the input information. User interface equipment1432can 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 equipment1432is also configured to allow and/or facilitate output of information from WD1410, and to allow and/or facilitate processing circuitry1420to output information from WD1410. User interface equipment1432can 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 equipment1432, WD1410can communicate with end users and/or the wireless network, and allow and/or facilitate them to benefit from the functionality described herein.

Auxiliary equipment1434is 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 equipment1434can vary depending on the embodiment and/or scenario.

Power source1436can, 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. WD1410can further comprise power circuitry1437for delivering power from power source1436to the various parts of WD1410which need power from power source1436to carry out any functionality described or indicated herein. Power circuitry1437can in certain embodiments comprise power management circuitry. Power circuitry1437can additionally or alternatively be operable to receive power from an external power source; in which case WD1410can 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 circuitry1437can also in certain embodiments be operable to deliver power from an external power source to power source1436. This can be, for example, for the charging of power source1436. Power circuitry1437can perform any converting or other modification to the power from power source1436to make it suitable for supply to the respective components of WD1410.

FIG.15illustrates one embodiment of a UE in accordance with various aspects described herein. 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 relevant device. Instead, a UE can represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE can represent a device that is not intended for sale to, or operation by, an end user but which can be associated with or operated for the benefit of a user (e.g., a smart power meter). UE15200can be any UE identified by the 3rd Generation Partnership Project (3GPP), including a NB-IoT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE1500, as illustrated inFIG.15, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3rd Generation Partnership Project (3GPP), such as 3GPP's GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, the term WD and UE can be used interchangeable. Accordingly, althoughFIG.15is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.

InFIG.15, UE1500includes processing circuitry1501that is operatively coupled to input/output interface1505, radio frequency (RF) interface1509, network connection interface1511, memory1515including random access memory (RAM)1517, read-only memory (ROM)1519, and storage medium1521or the like, communication subsystem1531, power source1533, and/or any other component, or any combination thereof. Storage medium1521includes operating system1523, application program1525, and data1527. In other embodiments, storage medium1521can include other similar types of information. Certain UEs can utilize all of the components shown inFIG.15, or only a subset of the components. The level of integration between the components can vary from one UE to another UE. Further, certain UEs can contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

InFIG.15, processing circuitry1501can be configured to process computer instructions and data. Processing circuitry1501can be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry1501can include two central processing units (CPUs). Data can be information in a form suitable for use by a computer.

In the depicted embodiment, input/output interface1505can be configured to provide a communication interface to an input device, output device, or input and output device. UE1500can be configured to use an output device via input/output interface1505. 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 UE1500. 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. UE1500can be configured to use an input device via input/output interface1505to allow and/or facilitate a user to capture information into UE1500. 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.

InFIG.15, RF interface1509can be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface1511can be configured to provide a communication interface to network1543a. Network1543acan 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, network1543acan comprise a Wi-Fi network. Network connection interface1511can be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like. Network connection interface1511can implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions can share circuit components, software or firmware, or alternatively can be implemented separately.

RAM1517can be configured to interface via bus1510to processing circuitry1501to 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. ROM1519can be configured to provide computer instructions or data to processing circuitry1501. For example, ROM1519can 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 medium1521can 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 medium1521can be configured to include operating system1523, application program1525such as a web browser application, a widget or gadget engine or another application, and data file1527. Storage medium1521can store, for use by UE1500, any of a variety of various operating systems or combinations of operating systems.

Storage medium1521can 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 medium1521can allow and/or facilitate UE1500to 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 medium1521, which can comprise a device readable medium.

InFIG.15, processing circuitry1501can be configured to communicate with network1543busing communication subsystem1531. Network1543aand network1543bcan be the same network or networks or different network or networks. Communication subsystem1531can be configured to include one or more transceivers used to communicate with network1543b. For example, communication subsystem1531can be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 810.15, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver can include transmitter1533and/or receiver1535to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter1533and receiver1535of each transceiver can share circuit components, software or firmware, or alternatively can be implemented separately.

In the illustrated embodiment, the communication functions of communication subsystem1531can 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 subsystem1531can include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network1543bcan 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, network1543bcan be a cellular network, a Wi-Fi network, and/or a near-field network. Power source1513can be configured to provide alternating current (AC) or direct current (DC) power to components of UE1500. As another example, one of networks1543a-bcan be an LTE RAN and the other of networks1543a-bcan be an NR RAN.

The features, benefits and/or functions described herein can be implemented in one of the components of UE1500or partitioned across multiple components of UE1500. Further, the features, benefits, and/or functions described herein can be implemented in any combination of hardware, software or firmware. In one example, communication subsystem1531can be configured to include any of the components described herein. Further, processing circuitry1501can be configured to communicate with any of such components over bus1510. In another example, any of such components can be represented by program instructions stored in memory that when executed by processing circuitry1501perform the corresponding functions described herein. In another example, the functionality of any of such components can be partitioned between processing circuitry1501and communication subsystem1531. 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.

FIG.16is a schematic block diagram illustrating a virtualization environment1600in which functions implemented by some embodiments can be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which can include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).

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 environments1600hosted by one or more of hardware nodes1630. 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 applications1620(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. Applications1620are run in virtualization environment1600which provides hardware1630comprising processing circuitry1660and memory1690. Memory1690contains instructions1695executable by processing circuitry1660whereby application1620is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

Virtualization environment1600, comprises general-purpose or special-purpose network hardware devices1630comprising a set of one or more processors or processing circuitry1660, 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 memory1690-1which can be non-persistent memory for temporarily storing instructions1695or software executed by processing circuitry1660. Each hardware device can comprise one or more network interface controllers (NICs)1670, also known as network interface cards, which include physical network interface1680. Each hardware device can also include non-transitory, persistent, machine-readable storage media1690-2having stored therein software1695and/or instructions executable by processing circuitry1660. Software1695can include any type of software including software for instantiating one or more virtualization layers1650(also referred to as hypervisors), software to execute virtual machines1640as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

Virtual machines1640, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and can be run by a corresponding virtualization layer1650or hypervisor. Different embodiments of the instance of virtual appliance1620can be implemented on one or more of virtual machines1640, and the implementations can be made in different ways.

During operation, processing circuitry1660executes software1695to instantiate the hypervisor or virtualization layer1650, which can sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer1650can present a virtual operating platform that appears like networking hardware to virtual machine1640.

As shown inFIG.16, hardware1630can be a standalone network node with generic or specific components. Hardware1630can comprise antenna16225and can implement some functions via virtualization. Alternatively, hardware1630can be part of a larger cluster of hardware (e.g., such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO)16100, which, among others, oversees lifecycle management of applications1620.

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 machine1640can 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 machines1640, and that part of hardware1630that 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 machines1640, 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 machines1640on top of hardware networking infrastructure1630and corresponds to application1620inFIG.16.

In some embodiments, one or more radio units16200that each include one or more transmitters16220and one or more receivers16210can be coupled to one or more antennas16225. Radio units16200can communicate directly with hardware nodes1630via 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 signalling can be effected with the use of control system16230which can alternatively be used for communication between the hardware nodes1630and radio units16200.

With reference toFIG.17, in accordance with an embodiment, a communication system includes telecommunication network1710, such as a 3GPP-type cellular network, which comprises access network1711, such as a radio access network, and core network1714. Access network1711comprises a plurality of base stations1712a,1712b,1712c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area1713a,1713b,1713c. Each base station1712a,1712b,1712cis connectable to core network1714over a wired or wireless connection1715. A first UE1791located in coverage area1713ccan be configured to wirelessly connect to, or be paged by, the corresponding base station1712c. A second UE1792in coverage area1713ais wirelessly connectable to the corresponding base station1712a. While a plurality of UEs1791,1792are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station1712.

Telecommunication network1710is itself connected to host computer1730, 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 computer1730can 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. Connections1721and1722between telecommunication network1710and host computer1730can extend directly from core network1714to host computer1730or can go via an optional intermediate network1720. Intermediate network1720can be one of, or a combination of more than one of, a public, private or hosted network; intermediate network1720, if any, can be a backbone network or the Internet; in particular, intermediate network1720can comprise two or more sub-networks (not shown).

The communication system ofFIG.17as a whole enables connectivity between the connected UEs1791,1792and host computer1730. The connectivity can be described as an over-the-top (OTT) connection1750. Host computer1730and the connected UEs1791,1792are configured to communicate data and/or signaling via OTT connection1750, using access network1711, core network1714, any intermediate network1720and possible further infrastructure (not shown) as intermediaries. OTT connection1750can be transparent in the sense that the participating communication devices through which OTT connection1750passes are unaware of routing of uplink and downlink communications. For example, base station1712may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer1730to be forwarded (e.g., handed over) to a connected UE1791. Similarly, base station1712need not be aware of the future routing of an outgoing uplink communication originating from the UE1791towards the host computer1730.

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 toFIG.18. In communication system1800, host computer1810comprises hardware1815including communication interface1816configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system1800. Host computer1810further comprises processing circuitry1818, which can have storage and/or processing capabilities. In particular, processing circuitry1818can comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer1810further comprises software1811, which is stored in or accessible by host computer1810and executable by processing circuitry1818. Software1811includes host application1812. Host application1812can be operable to provide a service to a remote user, such as UE1830connecting via OTT connection1850terminating at UE1830and host computer1810. In providing the service to the remote user, host application1812can provide user data which is transmitted using OTT connection1850.

Communication system1800can also include base station1820provided in a telecommunication system and comprising hardware1825enabling it to communicate with host computer1810and with UE1830. Hardware1825can include communication interface1826for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system1800, as well as radio interface1827for setting up and maintaining at least wireless connection1870with UE1830located in a coverage area (not shown inFIG.18) served by base station1820. Communication interface1826can be configured to facilitate connection1860to host computer1810. Connection1860can be direct or it can pass through a core network (not shown inFIG.18) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware1825of base station1820can also include processing circuitry1828, 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. Base station1820further has software1821stored internally or accessible via an external connection.

Communication system1800can also include UE1830already referred to. The UE's hardware1835can include radio interface1837configured to set up and maintain wireless connection1870with a base station serving a coverage area in which UE1830is currently located. Hardware1835of UE1830can also include processing circuitry1838, 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. UE1830further comprises software1831, which is stored in or accessible by UE1830and executable by processing circuitry1838. Software1831includes client application1832. Client application1832can be operable to provide a service to a human or non-human user via UE1830, with the support of host computer1810. In host computer1810, an executing host application1812can communicate with the executing client application1832via OTT connection1850terminating at UE1830and host computer1810. In providing the service to the user, client application1832can receive request data from host application1812and provide user data in response to the request data. OTT connection1850can transfer both the request data and the user data. Client application1832can interact with the user to generate the user data that it provides.

It is noted that host computer1810, base station1820and UE1830illustrated inFIG.18can be similar or identical to host computer1730, one of base stations1712a,1712b,1712cand one of UEs1791,1792ofFIG.17, respectively. This is to say, the inner workings of these entities can be as shown inFIG.18and independently, the surrounding network topology can be that ofFIG.17.

InFIG.18, OTT connection1850has been drawn abstractly to illustrate the communication between host computer1810and UE1830via base station1820, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure can determine the routing, which it can be configured to hide from UE1830or from the service provider operating host computer1810, or both. While OTT connection1850is active, the network infrastructure can further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

Wireless connection1870between UE1830and base station1820is 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 UE1830using OTT connection1850, in which wireless connection1870forms the last segment. More precisely, the exemplary embodiments disclosed herein can improve flexibility for the network to monitor end-to-end quality-of-service (QoS) of data flows, including their corresponding radio bearers, associated with data sessions between a user equipment (UE) and another entity, such as an OTT data application or service external to the 5G network. 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 connection1850between host computer1810and UE1830, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection1850can be implemented in software1811and hardware1815of host computer1810or in software1831and hardware1835of UE1830, or both. In embodiments, sensors (not shown) can be deployed in or in association with communication devices through which OTT connection1850passes; 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 software1811,1831can compute or estimate the monitored quantities. The reconfiguring of OTT connection1850can include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station1820, and it can be unknown or imperceptible to base station1820. Such procedures and functionalities can be known and practiced in the art. In certain embodiments, measurements can involve proprietary UE signaling facilitating host computer1810's measurements of throughput, propagation times, latency and the like. The measurements can be implemented in that software1811and1831causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection1850while it monitors propagation times, errors etc.

FIG.19is a flowchart illustrating an exemplary method and/or procedure implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which, in some exemplary embodiments, can be those described with reference toFIGS.17and18. For simplicity of the present disclosure, only drawing references toFIG.19will be included in this section. In step1910, the host computer provides user data. In substep1911(which can be optional) of step1910, the host computer provides the user data by executing a host application. In step1920, the host computer initiates a transmission carrying the user data to the UE. In step1930(which can be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step1940(which can also be optional), the UE executes a client application associated with the host application executed by the host computer.

FIG.20is a flowchart illustrating an exemplary method and/or procedure implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which can be those described with reference toFIGS.17and18. For simplicity of the present disclosure, only drawing references toFIG.20will be included in this section. In step2010of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application. In step2100, the host computer initiates a transmission carrying the user data to the UE. The transmission can pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step2030(which can be optional), the UE receives the user data carried in the transmission.

FIG.21is a flowchart illustrating an exemplary method and/or procedure implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which can be those described with reference toFIGS.17and18. For simplicity of the present disclosure, only drawing references toFIG.21will be included in this section. In step2110(which can be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step2120, the UE provides user data. In substep2121(which can be optional) of step2120, the UE provides the user data by executing a client application. In substep2111(which can be optional) of step2110, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application can further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep2130(which can be optional), transmission of the user data to the host computer. In step2140of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.FIG.22is a flowchart illustrating an exemplary method and/or procedure implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which can be those described with reference toFIGS.17and18. For simplicity of the present disclosure, only drawing references toFIG.22will be included in this section. In step2210(which can be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step2220(which can be optional), the base station initiates transmission of the received user data to the host computer. In step2230(which can be optional), the host computer receives the user data carried in the transmission initiated by the base station.

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.

Exemplary embodiments of the present disclosure include the following enumerated examples.1. A method performed by a first network node in a first radio access network (RAN), the first network node in communication with a second network node in a second RAN, the method comprising:determining one or more group identifiers associated with at least one of:i. a user equipment (UE) served by the first network node; andii. a subscriber associated with the UE;sending a request for the second network node to establish dual connectivity, as a secondary node (SN), with the UE, wherein the request comprises information relating to the one or more group identifiers; andmanaging the UE's access to resources of the first RAN based on the one or more group identifiers.2. The method of embodiment 1, wherein the information relating to the one or more group identifiers is usable by the second network node to manage the UE's access to resources of the second RAN.3. The method of any of embodiments 1-2, wherein:The first network node is an eNB in an LTE RAN; andThe second network node is a gNB in an NR RAN.4. The method of any of embodiments 1-3, wherein the one or more group identifiers comprise at least one of a Subscriber Profile ID for RAT/Frequency Priority (SPID) and a Dedicated Core Network ID (DCN-id).5. The method of any of embodiments 1-4, wherein the information relating to the SPID comprises a RAT/Frequency Selection Priority (RFSP).6. The method of any of embodiments 1-3, wherein the information relating to the DCN-id comprises an index value that maps to one or more policies for managing UE access to resources of the second RAN.7. The method of any of embodiments 1-3, wherein each of the one or more group identifiers is determined based on one or more of Subscribers Profile ID for RAT/Frequency Priority (SPID), Dedicated Core Network ID (DCN-id), Public Land Mobile Network ID (PLMN-id), QoS Class Indicator (QCI), and Closed Subscriber Group (CSG) membership.8. The method of any of embodiments 1-7, wherein managing the UE's access to resources of the first RAN is further based on a profile of the subscriber associated with the UE.9. A method performed by a second network node in a second radio access network (RAN), the second network node in communication with a first network node in a first RAN, the method comprising:receiving a request from the first network node to establish dual connectivity, as a secondary node (SN), with a user equipment (UE) served by the first network node, wherein the request comprises information relating to one or more group identifiers that are associated with at least one of:i. the UE; andii. a subscriber associated with the UE;managing the UE's access to resources of the second RAN based on the one or more group identifiers.10. The method of embodiment 9, wherein request is received by central unit (CU) comprising the second network node, and the method further comprises sending the information relating to the one or more group identifiers to at least one distributed unit (DU) comprising the second network node.11. The method of any of embodiments 9-10, wherein:The first network node is an eNB in an LTE RAN; andThe second network node is a gNB in an NR RAN.12. The method of any of embodiments 9-11, wherein the one or more group identifiers comprise at least one of a Subscriber Profile ID for RAT/Frequency Priority (SPID) and a Dedicated Core Network ID (DCN-id).13. The method of any of embodiments 9-12, wherein the information relating to the SPID comprises a RAT/Frequency Selection Priority (RFSP).14. The method of any of embodiments 9-12, wherein the information relating to the DCN-id comprises an index value that maps to one or more policies for managing UE access to resources of the second RAN.15. The method of any of embodiments 9-11, wherein each of the one or more group identifiers is determined based on one or more of Subscribers Profile ID for RAT/Frequency Priority (SPID), Dedicated Core Network ID (DCN-id), Public Land Mobile Network ID (PLMN-id), QoS Class Indicator (QCI), and Closed Subscriber Group (CSG) membership.16. The method of any of embodiments 9-15, wherein managing the UE's access to resources of the second RAN is further based on a profile of the subscriber associated with the UE.17. The method of any of embodiments 9-15, wherein managing the UE's access to resources of the second RAN is based on a policy that prioritizes access by UEs associated with the one or more group identifiers over access by UEs that are not associated with all of the one or more identifiers.18. The method of embodiment 17, wherein the policy prioritizes access by UEs associated with the one or more group identifiers to particular bandwidth part (BWP) frequency resources that are allocated by the second RAN.19. The method of any of embodiments 9-15, wherein managing the UE's access to resources of the second RAN comprises guaranteeing that UEs associated with the one or more group identifiers can access at least a predefined proportion of resources available in the second RAN.20. A first network node in a first radio access network (RAN), the first network node in communication with a second network node in a second RAN, the first network node comprising:processing circuitry configured to perform operations corresponding to any of the methods of embodiments 1-8; andpower supply circuitry configured to supply power to the first network node.21. A second network node in a second radio access network (RAN), the second network node in communication with a first network node in a first RAN, the second network node comprising:processing circuitry configured to perform operations corresponding to any of the methods of embodiments 9-19; andpower supply circuitry configured to supply power to the second network node.22. A communication system including a host computer comprising:processing circuitry configured to provide user data; anda 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 first radio access network (RAN) comprising a first network node and a second RAN comprising a second network node, each of the first and second network nodes having a radio interface and processing circuitry;the first network node's processing circuitry is configured to perform operations corresponding to any of the methods of embodiments 1-8; andthe second network node's processing circuitry is configured to perform operations corresponding to any of the methods of embodiments 9-19.23. The communication system of embodiment 22, further including a user equipment configured to communicate with at least one of the first and second DUs.24. The communication system of any of embodiments 22-23, wherein:the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; andthe UE comprises processing circuitry configured to execute a client application associated with the host application.25. A method implemented in a communication system including a host computer, first and second network nodes, and a user equipment (UE), the method comprising:at the host computer, providing user data;at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the first and second network nodes; andoperations, performed by the first network node, corresponding to any of the methods of embodiments 1-8; andoperations, performed by the second network node, corresponding to any of the methods of embodiments 9-19.26. The method of embodiment 25, further comprising, transmitting the user data by at least one of the first and second network nodes.27. The method of any of embodiments 25-26, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application.28. A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to at least one of a first network node comprising a first radio access network (RAN) and a second network node comprising a second RAN, wherein the second network node comprises a radio interface and processing circuitry configured to perform operations corresponding to any of the methods of embodiments 9-19, and wherein the first network node comprises processing circuitry configured to perform operations corresponding to any of the methods of embodiments 1-8.29. The communication system of the previous embodiment further including the first and second network nodes.30. The communication system of any of embodiments 28-29, further including the UE, wherein the UE is configured to communicate with at least one of the first and second network nodes.31. The communication system of any of embodiments 28-30, wherein:the processing circuitry of the host computer is configured to execute a host application;the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.