Support for quality-of-service (QOS) monitoring in a dual connectivity or split ng-ran with control plane (CP)—user plane (UP) separation

An apparatus for a Next Generation Node-B (gNB) includes processing circuitry coupled to memory. To configure the gNB for QoS monitoring in an NG-RAN with a control plane (CP)-user plane (UP) separation, the processing circuitry is to decode assistance information data received at a gNB Central Unit (gNB-CU) node of the gNB from a gNB Distributed Unit (gNB-DU) node of the gNB. The gNB-CU node is hosting an NR PDCP. The gNB-DU node is configured as a corresponding node of the gNB. The assistance information data includes delay information of a communication link of the NG-RAN measured by the corresponding node. A delay associated with the communication link is determined at the gNB-CU node of the gNB, based on the delay information measured by the corresponding node.

TECHNICAL FIELD

Aspects pertain to wireless communications. Some aspects relate to wireless networks including 3GPP (Third Generation Partnership Project) networks, 3GPP LTE (Long Term Evolution) networks, 3GPP LTE-A (LTE Advanced) networks, and fifth-generation (5G) networks including 5G new radio (NR) (or 5G-NR) networks and 5G-LTE networks such as 5G NR unlicensed spectrum (NR-U) networks. Other aspects are directed to systems and methods for supporting quality of service (QOS) monitoring in dual connectivity or split NG radio access network (RAN) architecture with control plane (CP)—user plane (UP) separation.

BACKGROUND

Mobile communications have evolved significantly from early voice systems to today's highly sophisticated integrated communication platform. With the increase in different types of devices communicating with various network devices, usage of 3GPP LTE systems has increased. The penetration of mobile devices (user equipment or UEs) in modern society has continued to drive demand for a wide variety of networked devices in many disparate environments. Fifth-generation (5G) wireless systems are forthcoming and are expected to enable even greater speed, connectivity, and usability. Next generation 5G networks (or NR networks) are expected to increase throughput, coverage, and robustness and reduce latency and operational and capital expenditures. 5G-NR networks will continue to evolve based on 3GPP LTE-Advanced with additional potential new radio access technologies (RATs) to enrich people's lives with seamless wireless connectivity solutions delivering fast, rich content and services. As current cellular network frequency is saturated, higher frequencies, such as millimeter wave (mmWave) frequency, can be beneficial due to their high bandwidth.

Potential LTE operation in the unlicensed spectrum includes (and is not limited to) the LTE operation in the unlicensed spectrum via dual connectivity (DC), or DC-based LAA, and the standalone LTE system in the unlicensed spectrum, according to which LTE-based technology solely operates in the unlicensed spectrum without requiring an “anchor” in the licensed spectrum, called MulteFire. MulteFire combines the performance benefits of LTE technology with the simplicity of Wi-Fi-like deployments.

Further enhanced operation of LTE systems in the licensed, as well as unlicensed spectrum, is expected in future releases and 5G systems. Such enhanced operations can include techniques for supporting QOS monitoring in dual connectivity or split NG RAN architecture with CP-UP separation.

DETAILED DESCRIPTION

The following description and the drawings sufficiently illustrate aspects to enable those skilled in the art to practice them. Other aspects may incorporate structural, logical, electrical, process, and other changes. Portions and features of some aspects may be included in or substituted for, those of other aspects. Aspects outlined in the claims encompass all available equivalents of those claims.

FIG.1Aillustrates an architecture of a network in accordance with some aspects. The network140A is shown to include user equipment (UE)101and UE102. The UEs101and102are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) but may also include any mobile or non-mobile computing device, such as Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, drones, or any other computing device including a wired and/or wireless communications interface. The UEs101and102can be collectively referred to herein as UE101, and UE101can be used to perform one or more of the techniques disclosed herein.

Any of the radio links described herein (e.g., as used in the network140A or any other illustrated network) may operate according to any exemplary radio communication technology and/or standard.

LTE and LTE-Advanced are standards for wireless communications of high-speed data for UE such as mobile telephones. In LTE-Advanced and various wireless systems, carrier aggregation is a technology according to which multiple carrier signals operating on different frequencies may be used to cam communications for a single UE, thus increasing the bandwidth available to a single device. In some aspects, carrier aggregation may be used where one or more component carriers operate on unlicensed frequencies.

Aspects described herein can be used in the context of any spectrum management scheme including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as Licensed Shared Access (LSA) in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz, and further frequencies and Spectrum Access System (SAS) in 3.55-3.7 GHz and further frequencies).

Aspects described herein can also be applied to different Single Carrier or OFDM flavors (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, etc.) and in particular 3GPP NR (New Radio) by allocating the OFDM carrier data bit vectors to the corresponding symbol resources.

In some aspects, any of the UEs101and102can include enhanced MTC (eMTC) UEs or further enhanced MTC (FeMTC) UEs.

The UEs101and102may be configured to connect, e.g., communicatively couple, with a radio access network (RAN)110. The RAN110may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN. The UEs101and102utilize connections103and104, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections103and104are illustrated as an air interface to enable communicative coupling and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth-generation (5G) protocol, a New Radio (NR) protocol, and the like.

In an aspect, the UEs101and102may further directly exchange communication data via a ProSe interface105. The ProSe interface105may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).

Any of the RAN nodes111and112can terminate the air interface protocol and can be the first point of contact for the UEs101and102. In some aspects, any of the RAN nodes111and112can fulfill various logical functions for the RAN110including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling, and mobility management. In an example, any of the nodes111and/or112can be a new generation Node-B (gNB), an evolved node-B (eNB), or another type of RAN node.

The S-GW122may terminate the S1 interface113towards the RAN110, and routes data packets between the RAN110and the CN120. In addition, the S-GW122may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities of the S-GW122may include a lawful intercept, charging, and some policy enforcement.

The P-GW123may further be a node for policy enforcement and charging data collection. Policy and Charging Rules Function (PCRF)126is the policy and charging control element of the CN120. In a non-roaming scenario, in some aspects, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with a UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with a local breakout of traffic, there may be two PCRFs associated with a UE's IP-CAN session: a Home PCRF (H-PCRF) within an HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF126may be communicatively coupled to the application server184via the P-GW123.

In some aspects, the communication network140A can be an IoT network or a 5G network, including a 5G new radio network using communications in the licensed (5G NR) and the unlicensed (5G NR-U) spectrum. One of the current enablers of IoT is the narrowband-IoT (NB-IoT).

An NG system architecture can include the RAN110and a 5G network core (5GC)120. The NG-RAN110can include a plurality of nodes, such as gNBs and NG-eNBs. The core network120(e.g., a 5G core network or 5GC) can include an access and mobility function (AMF) and/or a user plane function (UPF). The AMF and the UPF can be communicatively coupled to the gNBs and the NG-eNBs via NG interfaces. More specifically, in some aspects, the gNBs and the NG-eNBs can be connected to the AMF by NG-C interfaces, and to the UPF by NG-U interfaces. The gNBs and the NG-eNBs can be coupled to each other via Xn interfaces.

In some aspects, the NG system architecture can use reference points between various nodes as provided by 3GPP Technical Specification (TS) 23.501 (e.g., V15.4.0, 2018-12). In some aspects, each of the gNBs and the NG-eNBs can be implemented as a base station, a mobile edge server, a small cell, a home eNB, and so forth. In some aspects, a gNB can be a master node (MN) and NG-eNB can be a secondary node (SN) in a 5G architecture.

FIG.1Billustrates a non-roaming 5G system architecture in accordance with some aspects. Referring toFIG.1B, there is illustrated a 5G system architecture140B in a reference point representation. More specifically. UE102can be in communication with RAN110as well as one or more other 5G core (5GC) network entities. The 5G system architecture140B includes a plurality of network functions (NFs), such as access and mobility management function (AMF)132, session management function (SMF)136, policy control function (PCF)148, application function (AF)150, user plane function (UPF)134, network slice selection function (NSSF)142, authentication server function (AUSF)144, and unified data management (UDM)/home subscriber server (HSS)146. The UPF134can provide a connection to a data network (DN)152, which can include, for example, operator services, Internet access, or third-party services. The AMF132can be used to manage access control and mobility and can also include network slice selection functionality. The SMF136can be configured to set up and manage various sessions according to network policy. The UPF134can be deployed in one or more configurations according to the desired service type. The PCF148can be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to PCRF in a 4G communication system). The UDM can be configured to store subscriber profiles and data (similar to an HSS in a 4G communication system).

In some aspects, the 5G system architecture140B includes an IP multimedia subsystem (IMS)168B as well as a plurality of IP multimedia core network subsystem entities, such as call session control functions (CSCFs). More specifically, the IMS168B includes a CSCF, which can act as a proxy CSCF (P-CSCF)162BE, a serving CSCF (S-CSCF)164B, an emergency CSCF (E-CSCF) (not illustrated inFIG.1B), or interrogating CSCF (I-CSCF)166B. The P-CSCF162B can be configured to be the first contact point for the UE102within the IM subsystem (IMS)168B. The S-CSCF164B can be configured to handle the session states in the network, and the E-CSCF can be configured to handle certain aspects of emergency sessions such as routing an emergency request to the correct emergency center or PSAP. The I-CSCF166B can be configured to function as the contact point within an operator's network for all IMS connections destined to a subscriber of that network operator, or a roaming subscriber currently located within that network operator's service area. In some aspects, the I-CSCF166B can be connected to another IP multimedia network170E, e.g. an IMS operated by a different network operator.

In some aspects, the UDM/HSS146can be coupled to an application server160E, which can include a telephony application server (TAS) or another application server (AS). The AS160B can be coupled to the IMS168B via the S-CSCF164B or the I-CSCF166B.

A reference point representation shows that interaction can exist between corresponding NF services. For example,FIG.1Billustrates the following reference points: N1(between the UE102and the AMF132), N2(between the RAN110and the AMF132), N3(between the RAN110and the UPF134), N4(between the SMF136and the UPF134), N5(between the PCF148and the AF150, not shown), N6(between the UPF134and the DN152). N7(between the SMF136and the PCF148, not shown), N8(between the UDM146and the AMF132, not shown), N9(between two UPFs134, not shown), N10(between the UDM146and the SMF136, not shown), N11(between the AMF132and the SMF136, not shown), N12(between the AUSF144and the AMF132, not shown), N13(between the AUSF144and the UDM146, not shown), N14(between two AMFs132, not shown), N15(between the PCF148and the AMF132in case of a non-roaming scenario, or between the PCF148and a visited network and AMF132in case of a roaming scenario, not shown), N16(between two SMFs, not shown), and N22(between AMF132and NSSF142, not shown). Other reference point representations not shown inFIG.1Bcan also be used.

FIG.1Cillustrates a 5G system architecture140C and a service-based representation. In addition to the network entities illustrated inFIG.1B, system architecture140C can also include a network exposure function (NEF)154and a network repository function (NRF)156. In some aspects, 5G system architectures can be service-based and interaction between network functions can be represented by corresponding point-to-point reference points Ni or as service-based interfaces.

In some aspects, as illustrated inFIG.1C, service-based representations can be used to represent network functions within the control plane that enable other authorized network functions to access their services. In this regard, 5G system architecture140C can include the following service-based interfaces: Namf158H (a service-based interface exhibited by the AMF132), Nsmf158I (aservice-based interface exhibited by the SMF136), Nnef158B (a service-based interface exhibited by the NEF154), Npcf158D (a service-based interface exhibited by the PCF148), a Nudm158E (a service-based interface exhibited by the UDM146), Naf158F (a service-based interface exhibited by the AF150), Nnrf158C (a service-based interface exhibited by the NRF156), Nnssf158A (a service-based interface exhibited by the NSSF142), Nausf158G (a service-based interface exhibited by the AUSF144). Other service-based interfaces (e.g., Nudr, N5g-eir, and Nudsf) not shown inFIG.1Ccan also be used.

In example embodiments, any of the UEs or base stations discussed in connection withFIG.1A-FIG.1Ccan be configured to operate using the techniques discussed in connection withFIG.2andFIG.3. The term “base station” is interchangeable with the term “RAN network node.”

Disclosed aspects include performance measurements related to UL/DL packet delay for 5G networks under the Rel-16 WI Enhancement of performance assurance for 5G networks including network slicing. The UL/DL packet delay may be measured for QoS flows between UPF and UE, based on mechanisms for QoS Monitoring per QoS Flow per UE to assist URLLC service.

In some aspects, for the UPF to report the end-to-end (between UPF and UE) delay result to the SMF, the NG-RAN may provide the RAN part of the delay between the NG-RAN and the UE (e.g., over the Uu interface) to the UPF. In a split base station (e.g., gNB) architecture with CP/UP separation, such RAN part delay consists of delays that are measured separately across DU, CU-UP, and/or CU-CP as follows:

(a) A DL delay is a sum of delays incurred at CU-UP, on F1-U, at DU, and on the air interface; and

(b) An UL delay consists of a PDCP queuing delay in the UE that is reported to CU-CP via RRC, and the rest of the delays are measured by CU-UP and DU.

In general, the communications between the core network a base station, and a UE are illustrated as shown inFIG.2.FIG.2illustrates diagram200of delay measurement between the NG-RAN and the UE (for downlink (DL) and uplink (UL)) in a split NG-RAN with CP/UP separation, in accordance with some embodiments.

In some aspects, when CU-UP receives a monitoring request packet, it may report either UL or DL or both delays between the NG-RAN and the UE based on the monitoring configuration for the concerned QoS flow. This means that either CU-UP may be given the delay value to be reported, or at least component delay results which are measured by the DU (for both DL and UL) or by the UE (for UL) may be gathered at the CU-UP. The disclosed techniques support the RAN part of the delay measurement and reporting in a split NG-RAN with CP/UP separation. The disclosed techniques are focused on signaling support for the RAN part delay measurement within an NG-RAN node consisting of DU, CU-UP, and CU-CP, including the UL delay reported from the UE.

In some embodiments, a CU-CP centric approach may be used where all the component results are first gathered at CU-CP and then CU-CP calculates/sends the delay value to be reported (either DL or UL or both) to the CU-UP. Such CU-CP centric approach, however, may not be optimal for the following reasons:

(a) An DL delay is not measured anywhere in the CU-CP nor the UE. Reporting the DU part of DL delay via CU-CP (and eventually to CU-UP) is not necessary; and

(b) Such approach unnecessarily involves multi-hop in the case of MR-DC with 5GC. In the example of an MN terminated SCG bearer, the DU part of DL delay should be sent to the SN's CU-CP (over F1-C), then to the MN's CU-CP (over Xn-C), to be aggregated as the delay value to be reported, which is then forwarded to the MN's CU-UP (over E1), which is complicated compared to sending the DU part of DL delay directly to the MN's CU-UP via the already established Xn-U between MN and SN.

The following embodiments are discussed herein:

(a) Embodiment 1: DU reports the DU part of DL/UL delay measurement directly to CU-UP via F1-U or Xn-U. This is an approach letting DU directly report what it has measured (i.e. DU part of DL delay or UL delay) over the already established F1-U or Xn-U to the CU-UP.

(b) Embodiment 2: CU-CP reports the UE part of UL delay measurement directly to CU-UP via E1. This is an approach letting CU-CP directly report what it has (i.e. UE part of UL delay) over E1 to the CU-UP.

(c) Embodiment 3: CU-UP polls delay measurement reporting from DU (DU part of DL/UL delay) via F1-U or Xn-U. Since delays per DRB are measured across different entities, CU-UP may be able to trigger the reporting in case some component result is missing or needs to be updated.

(d) Embodiment 4: CU-UP polls delay measurement reporting from CU-CP (UE part of UL delay) via E1. This is Embodiment 3 applied to CU-CP over E1.

The above embodiments of the present disclosure provide several mechanisms that support the RAN part of the delay measurement and reporting in dual connectivity or a split NG-RAN architecture with CP-UP separation.

Embodiment 1: DU Reports the DU Part of DL/UL Delay Measurement Directly to CU-UP Via F1-U or Xn-U

Some example implementation for the stage-3 TS 38.425 is as provided below.

Transfer of MEASUREMENT RESULT frame: The purpose of the Measurement Result procedure is to provide delay measurement information available at the corresponding node to the node hosting the NR PDCP entity. Such information may be taken into consideration by the node hosting the NR PDCP entity for QoS monitoring, as specified in TS 23.501. An NR user plane protocol instance making use of the Transfer of Measurement Result procedure is associated with a single data radio bearer only. The Transfer of Measurement Result procedure may be invoked if the corresponding node decides to send the delay measurement information to the node hosting the NR PDCP entity for the concerned data radio bearer.

The MEASUREMENT RESULT frame may be sent when the corresponding node receives a DL USER DATA PDU including the Measurement Result Polling Flag set to 1. In some aspects, the measurement result may be sent from the corresponding node to the node hosting NR PDCP.

The frame format for the NR user plane protocol—MEASUREMENT RESULT (PDU Type 3): This frame format may be defined to allow the node hosting the NR PDCP entity to receive delay measurement information available at the corresponding node for QoS monitoring. The following TABLE 1 shows the respective MEASUREMENT RESULT frame which can be used in the disclosed techniques.

The coding of information elements in a Measurement Result frame is as follows:

UL Measurement Indication (“Ind.”)—Description: This parameter indicates the presence of UL Delay DU Result: Value range: {0=UL Delay DU Result not present, 1=UL Delay DU Result present}; Field length: 1 bit.

UL Delay DU Result—Description: This field indicates the UL delay measured at the corresponding node in milliseconds for the concerned DRB over the Uu interface. It is encoded as an Unsigned32 binary integer value. The node hosting PDCP entity shall, if supported, use this information to calculate the total UL delay over the Uu interface for the concerned DRB and report to the UPF for QoS monitoring; Value range: {0..232-1}; Field length: 4 octets.

DL Measurement Ind.—Description: This parameter indicates the presence of DL Delay DU Result; Value range: {0=DL Delay DU Result not present, 1=DL Delay DU Result present}; Field length: 1 bit.

DL Delay DU Result.—Description: This field indicates DL delay measured at the corresponding node in milliseconds for the concerned DRB over the Uu interface. It is encoded as an Unsigned32 binary integer value. The node hosting PDCP entity shall, if supported, use this information to calculate the total DL delay over the Uu interface for the concerned DRB and report to the UPF for QoS monitoring; Value range: {0..232-1}; Field length: 4 octets.

Embodiment 2: CU-CP Reports the UE Part of UL Delay Measurement Directly to CU-UP Via the E1 Interface

An example implementation for the stage-3 TS 38.463 is as provided below.

The Measurement Result procedure: This procedure may be initiated the gNB-CU-CP to report the UL delay measurement result calculated by the UE for the concerned DRBs. The procedure uses UE-associated signaling. The gNB-CU-CP initiates the procedure by sending the MEASUREMENT RESULT message to the gNB-CU-UP.

An example MEASUREMENT RESULT message is illustrated in TABLE 2, which is sent by the gNB-CU-CP to the gNB-CU-UP to provide UL delay measurement calculated by the UE for the concerned DRBs.

Embodiment 3: CU-Up Polls Delay Measurement Reporting from DU (DU Part of DL/UL Delay) Via F1-U or Xn-U Interfaces

Some example implementation for the stage-3 TS 38.425 is as provided below.

Transfer of DOWNLINK USER DATA. If the Measurement Result Polling Flag is equal to 1, the corresponding node shall if supported, send the MEASUREMENT RESULT to the node hosting the NR PDCP entity.

The frame format for the NR user plane protocol—DL USER DATA (PDU Type 0): The following TABLE 3 shows the respective DL USER DATA frame.

Coding of Information Elements in Frames.

Measurement Result Polling Flag—Description: This parameter indicates that the node hosting the NR PDCP entity requests the corresponding node to send a MEASUREMENT RESULT PDU; Value range: {0=Measurement Result not requested, 1=Measurement Result requested}; Field length: 1 bit.

Embodiment 4: CU-UP Polls Delay Measurement Reporting from CU-CP (UE Part of UL Delay) Via the E1 Interface

Some example implementation for the stage-3 TS 38.463 is as provided below.

The Measurement Result Request procedure: This procedure is initiated by the gNB-CU-UP to request the gNB-CU-CP to provide the UL delay measurement result calculated by the UE for the concerned data resource blocks (DRBs). The procedure uses UE-associated signaling. In some aspects, the gNB-CU-UP initiates the procedure by sending the MEASUREMENT RESULT REQUEST message (e.g., a format of such message is provided in TABLE 4 below) in the gNB-CU-CP.

FIG.3illustrates a block diagram of a communication device such as an evolved Node-B (eNB), a next generation Node-B (gNB), an access point (AP), a wireless station (STA), a mobile station (MS), or a user equipment (UE), in accordance with some aspects and to perform one or more of the techniques disclosed herein. In alternative aspects, the communication device300may operate as a standalone device or may be connected (e.g., networked) to other communication devices.

Circuitry (e.g., processing circuitry) is a collection of circuits implemented in tangible entities of the device300that include hardware (e.g., simple circuits, gates, logic, etc.). Circuitry membership may be flexible over time. Circuitries include members that may, alone or in combination, perform specified operations when operating. In an example, the hardware of the circuitry may be immutably designed to carry out a specific operation (e.g., hardwired). In an example, the hardware of the circuitry may include variably connected physical components (e.g., execution units, transistors, simple circuits, etc.) including a machine-readable medium physically modified (e.g., magnetically, electrically, moveable placement of invariant massed particles, etc.) to encode instructions of the specific operation.

In connecting the physical components, the underlying electrical properties of a hardware constituent are changed, for example, from an insulator to a conductor or vice versa. The instructions enable embedded hardware (e.g., the execution units or a loading mechanism) to create members of the circuitry in hardware via the variable connections to carry out portions of the specific operation when in operation. Accordingly, in an example, the machine-readable medium elements are part of the circuitry or are communicatively coupled to the other components of the circuitry when the device is operating. In an example, any of the physical components may be used in more than one member of more than one circuitry. For example, under operation, execution units may be used in a first circuit of a first circuitry at one point in time and reused by a second circuit in the first circuitry, or by a third circuit in a second circuitry at a different time. Additional examples of these components with respect to the device300follow.

In some aspects, the device300may operate as a standalone device or may be connected (e.g., networked) to other devices. In a networked deployment, the communication device300may operate in the capacity of a server communication device, a client communication device, or both in server-client network environments. In an example, the communication device300may act as a peer communication device in a peer-to-peer (P2P) (or other distributed) network environment. The communication device300may be a UE, eNB, PC, a tablet PC, an STB, a PDA, a mobile telephone, a smartphone, a web appliance, a network router, switch or bridge, or any communication device capable of executing instructions (sequential or otherwise) that specify actions to be taken by that communication device. Further, while only a single communication device is illustrated, the term “communication device” shall also be taken to include any collection of communication devices that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a service (SaaS), and other computer cluster configurations.

The communication device (e.g., UE)300may include a hardware processor302(e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory304, a static memory306, and mass storage307(e.g., hard drive, tape drive, flash storage, or other block or storage devices), some or all of which may communicate with each other via an interlink (e.g., bus)308.

The communication device300may further include a display device310, an alphanumeric input device312(e.g., a keyboard), and a user interface (UI) navigation device314(e.g., a mouse). In an example, the display device310, input device312, and UI navigation device314may be a touchscreen display. The communication device30may additionally include a signal generation device318(e.g., a speaker), a network interface device320, and one or more sensors321, such as a global positioning system (GPS) sensor, compass, accelerometer, or another sensor. The communication device300may include an output controller328, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).

The storage device307may include a communication device-readable medium322, on which is stored one or more sets of data structures or instructions324(e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. In some aspects, registers of the processor302, the main memory304, the static memory306, and/or the mass storage307may be, or include (completely or at least partially), the device-readable medium322, on which is stored the one or more sets of data structures or instructions324, embodying or utilized by any one or more of the techniques or functions described herein. In an example, one or any combination of the hardware processor302, the main memory304, the static memory306, or the mass storage316may constitute the device-readable medium322.

As used herein, the term “device-readable medium” is interchangeable with “computer-readable medium” or “machine-readable medium”. While the communication device-readable medium322is illustrated as a single medium, the term “communication device-readable medium” may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions324. The term “communication device-readable medium” is inclusive of the terms “machine-readable medium” or “computer-readable medium” and may include any medium that is capable of storing, encoding, or carrying instructions (e.g., instructions324) for execution by the communication device300and that cause the communication device300to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions. Non-limiting communication device-readable medium examples may include solid-state memories and optical and magnetic media. Specific examples of communication device-readable media may include non-volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; Random Access Memory (RAM); and CD-ROM and DVD-ROM disks. In some examples, communication device-readable media may include non-transitory communication device-readable media. In some examples, communication device-readable media may include communication device-readable media that is not a transitory propagating signal.

The instructions324may further be transmitted or received over a communications network326using a transmission medium via the network interface device320utilizing anyone of a number of transfer protocols. In an example, the network interface device320may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the communications network326. In an example, the network interface device320may include a plurality of antennas to wirelessly communicate using at least one of single-input-multiple-output (SIMO), MIMO, or multiple-input-single-output (MISO) techniques. In some examples, the network interface device320may wirelessly communicate using Multiple User MIMO techniques.

The term “transmission medium” shall be taken to include any intangible medium that is capable of storing, encoding, or carrying instructions for execution by the communication device300, and includes digital or analog communications signals or another intangible medium to facilitate communication of such software. In this regard, a transmission medium in the context of this disclosure is a device-readable medium.

Although an aspect has been described with reference to specific exemplary aspects, it will be evident that various modifications and changes may be made to these aspects without departing from the broader scope of the present disclosure. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. This Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various aspects is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.