+

WO2018031069A1 - Structure de commande de commande d'accès au support (mac) hiérarchique dans une division fronthauling intra-mac - Google Patents

Structure de commande de commande d'accès au support (mac) hiérarchique dans une division fronthauling intra-mac Download PDF

Info

Publication number
WO2018031069A1
WO2018031069A1 PCT/US2017/020722 US2017020722W WO2018031069A1 WO 2018031069 A1 WO2018031069 A1 WO 2018031069A1 US 2017020722 W US2017020722 W US 2017020722W WO 2018031069 A1 WO2018031069 A1 WO 2018031069A1
Authority
WO
WIPO (PCT)
Prior art keywords
mac layer
central
local
components
scheduling
Prior art date
Application number
PCT/US2017/020722
Other languages
English (en)
Inventor
Jaemin HAN
Sangeetha L. Bangolae
Alexander Sirotkin
Youn Hyoung Heo
Original Assignee
Intel IP Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Intel IP Corporation filed Critical Intel IP Corporation
Publication of WO2018031069A1 publication Critical patent/WO2018031069A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1215—Wireless traffic scheduling for collaboration of different radio technologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/10—Access point devices adapted for operation in multiple networks, e.g. multi-mode access points

Definitions

  • the present disclosure relates to wireless communications, and more specifically, to media access control (MAC) for wireless communications.
  • MAC media access control
  • Wireless mobile communication technology uses various standards and protocols to transmit data between a node (e.g., a transmission station) and a wireless device (e.g., a mobile device), or a user equipment (UE).
  • a node e.g., a transmission station
  • a wireless device e.g., a mobile device
  • UE user equipment
  • Some wireless devices communicate using orthogonal frequency-division multiple access (OFDMA) in a downlink (DL) transmission and single carrier frequency division multiple access (SC- FDMA) in an uplink (UL) transmission.
  • OFDMA orthogonal frequency-division multiple access
  • SC- FDMA single carrier frequency division multiple access
  • OFDM orthogonal frequency-division multiplexing
  • 3GPP third generation partnership project
  • LTE long term evolution
  • IEEE Institute of Electrical and Electronics Engineers
  • 802.16 standard e.g., 802.16e, 802.16m
  • WiMAX Worldwide Interoperability for Microwave Access
  • IEEE 802.1 1 which is commonly known to industry groups as WiFi.
  • the node can be a combination of Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node Bs (also commonly denoted as evolved Node Bs, enhanced Node Bs, eNodeBs, or eNBs), and potentially Radio Network Controllers (RNCs), which communicate with the UE.
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • Node Bs also commonly denoted as evolved Node Bs, enhanced Node Bs, eNodeBs, or eNBs
  • RNCs Radio Network Controllers
  • the downlink (DL) transmission can be a communication from the node (e.g., eNB) to the UE
  • the uplink (UL) transmission can be a communication from the wireless device to the node.
  • data can be transmitted from the eNodeB to the UE via a physical downlink shared channel (PDSCH).
  • PDSCH physical downlink shared channel
  • a physical uplink control channel (PUCCH) can be used to acknowledge
  • the node also called a macro node
  • the cell can be the area in which the wireless devices are operable to communicate with the macro node.
  • HetNets can be used to handle the increased traffic loads on the macro nodes due to increased usage and functionality of wireless devices.
  • HetNets can include a layer of planned high power macro nodes (or macro eNBs) overlaid with layers of lower power nodes (small eNBs, micro-eNBs, pico-eNBs, femto-eNBs, home eNBs (HeNBs) or other network devices) that can be deployed in a less well planned or even entirely uncoordinated manner within the coverage area (cell) of a macro node.
  • FIG. 1 illustrates a block diagram illustrating an example wireless
  • RANs radio access networks
  • RATs radio access technologies
  • FIG. 2 illustrates a block diagram illustrating an example core network to be employed in one or more RATs with radio access networks (RANs) employed with or within a UE or eNB according to various aspects or embodiments.
  • RANs radio access networks
  • FIG. 3 illustrates a protocol aggregation architectures applicable to the network environments, devices and processes according to various aspects or embodiments.
  • FIG. 4 illustrates another wireless communications network system device or system for a UE or eNB according to various aspects.
  • FIG. 5 illustrates a process flow to enable various MAC layer functions of a protocol stack in a distribution architecture according to various aspects or
  • FIG. 6 illustrates another process flow to enable various MAC layer functions of a protocol stack in a distribution architecture according to various aspects or embodiments.
  • FIG. 7 illustrates an example system or network device that can operate various aspects or embodiments.
  • FIG. 8 is an illustration of an example wireless network device or network platform that can implement various aspects or embodiments disclosed.
  • a component can be a processor, a process running on a processor, a controller, a circuit or a circuit element, an object, an executable, a program, a storage device, a computer, a tablet PC and/or a mobile phone with a processing device.
  • an application running on a server and the server can also be a component.
  • One or more components can reside within a process, and a component can be localized on one computer and/or distributed between two or more computers.
  • a set of elements or a set of other components can be described herein, in which the term “set” can be interpreted as "one or more.”
  • these components can execute from various computer readable storage media having various data structures stored thereon such as with a module, for example.
  • the components can communicate via local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network, such as, the Internet, a local area network, a wide area network, or similar network with other systems via the signal).
  • a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network, such as, the Internet, a local area network, a wide area network, or similar network with other systems via the signal).
  • a component can be an apparatus with specific functionality provided by mechanical parts operated by electric or electronic circuitry, in which the electric or electronic circuitry can be operated by a software application or a firmware application executed by one or more processors.
  • the one or more processors can be internal or external to the apparatus and can execute at least a part of the software or firmware application.
  • a component can be an apparatus that provides specific functionality through electronic components or elements without mechanical parts; the electronic components can include one or more processors therein to execute software and/or firmware that confer(s), at least in part, the functionality of the electronic components.
  • MAC layer functions can be delayed as a result of a non-ideal transport network delay, as well as increasing processing complexity among various access nodes and communications of various different radio access technologies (RATs), which can include legacy and new radio access technologies / network devices (e.g., 5G based, internet of things (loT), NextGen components, or other network components).
  • RATs radio access technologies
  • legacy and new radio access technologies / network devices e.g., 5G based, internet of things (loT), NextGen components, or other network components.
  • OSI open system
  • the MAC layer of a network device can be split / partition within the RAN architecture, such as at the eNB, a new radio (NR) base station, a UE or other network device / component. This split can be within the MAC layer among different MAC layer entities / components located within the MAC layer.
  • the MAC layer components can be configured in a hierarchy to enable a division of labor or functional sharing from among the MAC components of the MAC layer.
  • a central MAC component can be configured as the central unit (CU) of the MAC layer that can configured one or multiple local MAC components as distributed unit (DUs) within the MAC layer to operate independently and based on central MAC component of the MAC layer.
  • CU and DU(s) can be communicatively coupled to provide overall MAC layer functions to other protocol layers.
  • the upper layers radio link control (RLC), packet data convergence protocol (PDCP), radio resource control (RRC)
  • RLC radio link control
  • PDCP packet data convergence protocol
  • RRC radio resource control
  • PHY physical layer
  • RF radio frequency
  • FIG. 1 illustrated is an example network configured to enable the operation of legacy network devices, NextGen network devices (network devices based on a 5G network), new radio (NR) network devices, or the like, for example, which can be independent or communicatively coupled in one or more networks.
  • These network devices can be configured to communicate via a communication protocol stack, which can be based on an Open Source Interconnected (OSI) model and defines the networking framework for implementing communication protocols among the various layers. Control can be passed from one layer to the next, starting at an application layer in one station or node, for example, proceeding to a bottom layer, over a channel to a next station and back up the hierarchy.
  • OSI Open Source Interconnected
  • various embodiments and aspects herein are directed to the MAC protocol layer within this hierarchy of the protocol stack, such that the MAC layer itself is configured functionally and structurally in a hierarchy of MAC layer components located within the MAC layer.
  • the network system 1 00 is an example of an interworking architecture for potential interworking between a legacy network (e.g. , the evolved packet core (EPC) 1 04 in the LTE on the left hand side) and the NextGen core 1 06 with the 5G radio (e.g., the RAN 1 1 0 based on 5G RAT on the right hand side), in which each or both can be a component of an eNB or separate eN Bs as RANs 1 08 and 1 1 0, which can be configured to connect to or comprise both the EPC 1 04 and the NextGen core 1 06.
  • a legacy network e.g. , the evolved packet core (EPC) 1 04 in the LTE on the left hand side
  • the NextGen core 1 06 with the 5G radio e.g., the RAN 1 1 0 based on 5G RAT on the right hand side
  • each or both can be a component of an eNB or separate eN Bs as RANs 1 08 and 1 1 0, which can be configured to connect to or comprise
  • the UE signaling treatment or operation can be based on whether the UE is 5G capable or not to determine if the communication flow would be steered either to the EPC core 1 04 or the NextGen core 1 06.
  • UE 1 1 2 can be a legacy UE with bearer based operation handling
  • a UEs 1 1 4 or 1 1 6 can be 5G UEs operable for a bearer based or a flow based operation, in which QoS or other communication parameters are based on a certain communication protocol flow.
  • the protocol structures governing functions and related components to each layer e.g., the PHY layer, MAC layer, or otherwise
  • a legacy UE 1 1 2 and the 5G U E 1 14 can connect to the LTE eNB with RAN based on LTE 1 08, and the legacy U E 1 1 2 has traffic handled over the S1 interface to the EPC 1 04 while the 5G UE 1 14 can have
  • the communication handling can be different for different UEs so that one type of communication handling (e.g., a MAC central-distribution architecture) can be enabled for the 5G UE 1 14.
  • one type of communication handling e.g., a MAC central-distribution architecture
  • the PDCP/ RLC / MAC protocol in LTE can include the information that configures the PDCP layer (or RLC or MAC) to carry resources or one or more parameters related to the communication handling.
  • the eNB can know whether to apply the new or the legacy PDCP/RLC/MAC protocol stack, as well as the appropriate operation protocols (e.g., flow based (bearerless) protocols, bearer based protocols, or the like) along a communication stack architecture.
  • the components of the RAN based on LTE 108 can be employed in or as an eNB of a RAN based LTE or evolved LTE 108 configured to generate and manage cell coverage area / zone 120, while another eNB of a RAN based on 5G RAT or new RAT (NRAT) 1 10 can control the 5G based cell area 122.
  • NRAT new RAT
  • MAC operations of the MAC protocol layer can be centrally controlled with a central MAC layer component that is configured as a central control unit within the MAC layer.
  • the central MAC layer component can govern the central scheduling of resources for communications among various UEs (e.g., UE 1 1 2- 1 1 6) or various different networks 120, 122 of RANs 108, 1 10.
  • UEs e.g., UE 1 1 2- 1 1 6
  • At least a portion of the MAC protocol layer functions can also be delegated by the central MAC layer component to one or more local MAC layer components configured as distribution units.
  • MAC layer operations and physical resource allocation within the MAC layer can be configured by or implemented by the central MAC layer component, as part of the main functionality of the MAC protocol layer.
  • centralized scheduling by the MAC layer can be supported by simultaneously managing two or more independent physical radio resources of DU(s), enabling various features / functionalities such as Coordinated Multi-Point (CoMP) for joint processing and coordinated scheduling, Carrier Aggregation (CA), Dual Connectivity (DC) with a multi-cell view between various RATs of one or more RANs 108, 1 10.
  • CoMP Coordinated Multi-Point
  • CA Carrier Aggregation
  • DC Dual Connectivity
  • DU(s) or local MAC layer components
  • the central MAC layer component as central unit of the MAC layer, which can enable achievement of the stringent 5G performance targets such as a 1 0 Gbps or greater data rate with less than a 1 ms end-to-end latency through densified network nodes (e.g., eNBs, access points or other network device).
  • densified network nodes e.g., eNBs, access points or other network device.
  • FIG. 2 illustrates components of a network in accordance with aspects or embodiments herein.
  • An Evolved Packet Core (EPC) network 200 is shown to include a Home Subscriber Server (HSS) 102, a Mobility Management Entity (MME) 220, a Serving GateWay (SGW) 230, a Packet Data Network (PDN) GateWay (PGW) 240, a Policy and Charging Rules Function (PCRF) 250, which can be included in or as a part of the EPC 104 or the NextGen core 106 of FIG. 1.
  • HSS Home Subscriber Server
  • MME Mobility Management Entity
  • SGW Serving GateWay
  • PDN Packet Data Network
  • PGW Packet Data Network GateWay
  • PCRF Policy and Charging Rules Function
  • the HSS 102 comprises one or more databases for network users, including subscription-related information to support the network entities' handling of
  • the HSS 102 can provide support for
  • the EPC network 200 can comprise one or several HSSs 102, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc.
  • the MME 220 can be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN).
  • GPRS General Packet Radio Service
  • the MMEs 220 can manage mobility aspects in access such as gateway selection and tracking area list management.
  • the EPC network 200 can comprise one or several MMEs 220
  • the SGW 230 terminates the interface toward an Evolved UMTS (Universal Mobile Telecommunications System) Terrestrial Radio Access Network (E-UTRAN), and routes data packets between the E-UTRAN and the EPC network 200.
  • E-UTRAN Universal Mobile Telecommunications System
  • the SGW 230 can be a local mobility anchor point for inter-eNodeB handovers and also can provide an anchor for inter-3GPP mobility for various communication operations such as for Licensed Assisted Access (LAA or eLAA). Other responsibilities can include lawful intercept, charging, and some policy enforcement.
  • LAA Licensed Assisted Access
  • the PGW 240 terminates an SGi interface toward the PDN.
  • the PGW 240 routes data packets between the EPC network 200 and external networks, and can be a node (network device / component) for policy enforcement and charging data collection.
  • the PCRF 250 is the policy and charging control element of the EPC network 200.
  • HPLMN Home Public Land Mobile Network
  • UE User Equipment's
  • IP-CAN Connectivity Access Network
  • HPLMN Home PCRF
  • V-PCRF Visited PCRF
  • VPN Visited Public Land Mobile Network
  • the PCRF 250 can be communicatively coupled to an application server (alternatively referred to as application function (AF)).
  • application server alternatively referred to as application function (AF)
  • the application server is an element offering applications that use Internet Protocol (IP) bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, Long Term Evolution (LTE) PS data services, etc.).
  • IP Internet Protocol
  • PS Packet Services
  • LTE Long Term Evolution
  • the application server can signal the PCRF 250 to indicate a new service flow and selecting the appropriate Quality of Service (QoS) and charging parameters.
  • QoS Quality of Service
  • the PCRF 250 can provision this rule into a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate traffic flow template (TFT) and QoS class of identifier (QCI), which commences the QoS and charging as specified by the application server.
  • PCEF Policy and Charging Enforcement Function
  • the components of the EPC 200 can be implemented in one physical node or separate physical nodes.
  • Network Functions Virtualization can be utilized to virtualize any or all of the above described network node functions via executable instructions stored in one or more computer readable storage mediums.
  • a logical instantiation of the EPC network 200 can be referred to as a network slice 201 .
  • a logical instantiation of a portion of the EPC network 200 can be referred to as a network sub-slice 202 (e.g., the network sub-slice 202 is shown to include the PGW 240 and the PCRF 250).
  • a communication protocol architecture 300 applicable for one or more RAN networks (e.g., 1 08, 1 10, a RAN anchored wireless local area network (WLAN), or other network) or UEs to
  • RAN networks e.g., 1 08, 1 10, a RAN anchored wireless local area network (WLAN), or other network
  • WLAN wireless local area network
  • the TCP/IP layer 302 comprises a Transmission Control Protocol/Internet Protocol layers that is the basic communication language or protocol of the Internet, and can be used as a communications protocol in a private network (either an intranet or an extranet).
  • the TCP/IP layer 302 facilitates communications protocols used to connect network devices on the Internet.
  • the TCP/IP layer 302 can also include a radio resource control (RRC) protocol layer that interacts between the UEs and eNBs at the IP level according to the 3GPP protocol by using RRC messages, for example.
  • RRC radio resource control
  • the Packet Data Convergence Protocol (PDCP) layer 306, below or lower than the TCP / IP / RRC 302, can be one of the layers of the Radio Traffic Stack in LTE, UMTS and performs IP header compression and decompression, transfer of user data and maintenance of sequence numbers for Radio Bearers which are configured for lossless serving radio network subsystem (SRNS) relocation.
  • PDCP Packet Data Convergence Protocol
  • the radio link control (RLC) layer 308, below or lower than the PDCP layer 306, can handle an automatic repeat request fragmentation protocol used over a wireless air interface.
  • the RLC layer 308 can detect packet losses and performs retransmissions to bring packet loss down to a low percentage rate, which is suitable for TCP / IP applications.
  • the media access control (MAC) layer 310 and physical (PHY) layer 31 2 can correspond to separate RATs, respectively, and operate to provide an electrical, mechanical, and procedural interface to the transmission medium.
  • the PHY layer 312 can translate logical communications requests from the data link layer into hardware- specific operations to affect transmission or reception of electronic signals, for example.
  • the MAC layer 310 can provide addressing and channel access control mechanisms that make it possible for several terminals or network nodes to communicate within a multiple access network that incorporates a shared medium, for example.
  • the MAC layer 310 can operate to provide various functions among inter-cell networks 120, 122 and various UEs 1 12-1 16.
  • the MAC protocol layer 310 includes a hierarchical MAC control structure and interface 330 (330') between MAC CU 314 and DU(s) 316, 318 through which the configured MAC layer functionalities within each DU 31 6, 318 can be operated in coordination with MAC CU 314, and can also be operated independently, if configured, with its own localized scheduling decisions without involving CU processing.
  • the central MAC layer component / entity 314 as the CU of the MAC layer 310 is configured to perform scheduling decisions (e.g., resource scheduling) for one or more local MAC layer components in DUs 316, 31 8, while leaving some flexibility for the local MAC entities to perform scheduling decisions in a smaller scale than the MAC CU 314 such as for various PHY layer configurations, associated UEs or networks.
  • the scheduling decisions can include time, frequency, bandwidth, load, power, or other communication related parameter to enable data flow, communication function, or other use, for example
  • the MAC protocol layer 310 within network devices can control various communication functions.
  • a primary function of the MAC protocol layer 310 includes generating transport block (TBs) that include the payload for the PHY layer 31 2, especially for the shared physical channels such as PDSCH and PUSCH, for example.
  • TBs transport block
  • the TB size can be selected based on various parameters (e.g., the number of physical resource blocks (PRBs), the modulation and coding scheme, or other associated parameters), and can be determined / derived by the MAC layer 310 depending on the intended use / communication function with one or more resources, such as for downlink, uplink, a system information (SI) -radio network temporary identifier (RNTI), random access RNTI (RA-RNTI), paging RNTI, a special subframe for a time division duplex (TDD) configuration, or other similar communication resource.
  • SI system information
  • RNTI random access RNTI
  • TDD time division duplex
  • Each TB can be generated for a transmission time interval (TTI).
  • Other functions controlled by the MAC layer 310 can include: frame delimiting and recognition; addressing of destination stations (both as individual stations and as groups of stations); conveyance of source- station addressing information; transparent data transfer of LLC PDUs, or of equivalent information in the Ethernet sublayer; protection against errors, generally by means of generating and checking frame check sequences; or control of access to the physical transmission medium.
  • the channel access control mechanisms provided by the MAC layer can also be known as a multiple access protocol. This makes it possible for several stations connected to the same physical medium to share it. Examples of shared physical media are bus networks, ring networks, hub networks, wireless networks and half-duplex point-to-point links.
  • the multiple access protocol may detect or avoid data packet collisions if a packet mode contention based channel access method is used, or reserve resources to establish a logical channel if a circuit- switched or channelization-based channel access method is used.
  • the channel access control mechanism relies on a physical layer multiplex scheme.
  • the central MAC layer component 314 and the local MAC layer components of DUs 31 6, 318 in conjunction perform the above MAC layer functions together as the MAC layer 310.
  • the central MAC layer component 314 can perform scheduling decisions for multiple local MAC layer components in DUs 31 6, 318, while configuring flexibility for these local MAC entities to perform scheduling decisions in smaller scale independent of the central MAC layer component 314 based on various UEs (e.g., 1 12-1 16 of FIG. 1 ) or the networks (e.g., 120, 122 of FIG. 1 ).
  • the central MAC layer component 314 can configure each DU 31 6, 318 differently to perform one or more of the functions described above with respect to the MAC layer on a local level (e.g., a UE, a network, or particular PHY layer configuration) in order to alleviate processing burdens at the CU 314, or share such processing for MAC layer functions to operate ideally and with lower latency than otherwise.
  • a local level e.g., a UE, a network, or particular PHY layer configuration
  • the MAC layer 310 also includes the MAC interface 330 (330') that communicatively couples the central MAC layer component 314 and the local MAC layer components of DUs 31 6, 318 as part of the communication data transport network.
  • the MAC interface 330 (330') can be nested under the transport network between the CU and DUs, utilizing any type of data or information to interface therebetween.
  • the MAC interface 330 can include any interface connections of a protocol stack or communication interface whether it is an Ethernet, an optical fiber network, or some other kind of network as a transport network that interfaces between the CU as the central MAC layer component 314 and the different DUs with local MAC layer components 316, 31 8, which can operate under the same physical transport network.
  • the central MAC layer component 314 can initiate various messages to establish connection and subsequent configuration of resources to each DU 316, 318, which can include a setup response message, a setup request message, a setup failure message for interface establishment and subsequent communications among these components of the MAC layer 310.
  • the MAC interface 330 (330') can also be a point-to- point communication link, for example, that can comprise either a single link identified by the UE's media access control (MAC) address or other unique identifier, or several links with each link corresponding to a data radio bearer (DRB) of the UE 1 12-1 16, for example.
  • MAC media access control
  • DRB data radio bearer
  • the intended purpose of reducing latency within the MAC layer 310 under more complex scenarios such as heterogeneous networks or various RATs may not be achieved if scheduling is decided entirely and solely from a CU. For example, a follow- up hybrid automatic repeat request (HARQ) retransmission when the negative acknowledgement (NACK) is being received may require further resource scheduling unless pre-configured, such as by a semi-persistent scheduling. If the scheduling requires the CU-level processing, then the non-ideal round-trip transport network delays still persist for every one of the HARQ responses. Thus, such scheduling operations can be delegated by the central MAC layer component 314 to a DU 316 or 318
  • Semi-persistent scheduling can mean that the scheduling is for up to some future point in time.
  • the CU or other component can operate as a central scheduler that therefore does not need to schedule resources or configurations to a DU 316 dynamically up to that time.
  • the local scheduler or DU can be thus be configured up to some persistent time.
  • the CU 314 can operate to configure the DUs dynamically depending on network individual demands.
  • the central MAC layer component 314 can grant these resources to the DUs 316, 31 8 to independently control between one or more different PHY configurations, UEs 1 12-1 16 or networks 1 20, 122.
  • the DU 316 for example, can utilize different resources and manage one or more different UEs / networks from the DU 318.
  • Each DU 316, 31 8 after being configured by the central MAC layer component 314 can then perform operations independent from the central MAC layer component 314.
  • the configurations of the DUs 31 6, 318 by CU 314 can be semi-persistent, re-configured periodically, or dynamic in time based on the network demands.
  • the central MAC layer component 314 and the local MAC layer components of DUs 316, 318 can form this hierarchy structure within the MAC layer 31 0, which means that the DUs 316, 31 8 operate according to the configuration (e.g., resource configuration) granted to each DU 316, 318 by the central MAC layer component 314. Together these components 314-318 can jointly provide all the functionalities of the MAC protocol layer 310.
  • the upper layers (RLC, PDCP, RRC) can interact with the central MAC layer component 314 as the CU, while the local MAC layer components of DUs 316, 318 in each DU interacts with lower layers (e.g., PHY and RF layers) or respective components.
  • Each DU can be configured to have one or more local MAC layer components 31 6, 31 8 and associated resources per PHY configuration, based on, for example, whether a DU supports multiple physical radio interfaces to one or more different UEs / networks, or multiple verticals (e.g., enhanced mobile broadband
  • eMBB ultra-reliable and low latency communication
  • URLLC ultra-reliable and low latency communication
  • mMTC massive machine type communication
  • NG2, NG3, S1 , S6a, or the like a single physical radio interface
  • the central MAC layer component 314 in the CU can control a large number of local MAC layer components 316, 318 in DUs in order to maximize joint scheduling benefits, operate to generate MAC layer functions or operations with the local MAC layer components 31 6, 31 8, or configure each with resources to operate independently of the central MAC layer component 314 and other local MAC layer components as part of the MAC layer 310, for example.
  • This hierarchical structure thus effectively enables dependent configuration of the DUs by the CU, and joint operation between these components as a distribution chain that eases processing burdens from the CU of the MAC layer 310 and can decrease latency.
  • FIG. 4 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
  • FIG. 4 illustrates a diagrammatic representation of hardware resources 400 including one or more processors (or processor cores) 410, one or more memory/storage devices 420, and one or more communication resources 430, each of which are communicatively coupled via a bus 440.
  • node virtualization e.g., NFV
  • a hypervisor 402 can be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 400.
  • the processors 410 e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) such as a baseband processor, an application specific integrated circuit (ASIC), a radio-frequency integrated circuit (RFIC), another processor, or any suitable combination thereof
  • CPU central processing unit
  • RISC reduced instruction set computing
  • CISC complex instruction set computing
  • GPU graphics processing unit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • RFIC radio-frequency integrated circuit
  • the memory/storage devices 420 can include main memory, disk storage, or any suitable combination thereof.
  • the communication resources 430 can include resources or parameters described herein as well as interconnection / network interface components or other suitable devices to communicate with one or more peripheral devices 404 and/or one or more databases 406 via a network 408.
  • the communication resources 430 can include wired communication components (e.g., for coupling via a Universal Serial Bus (USB)), cellular communication components, Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi®
  • Instructions 450 can comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 410 to perform any one or more of the methodologies, functions or component functions discussed herein.
  • the instructions 450 can reside, completely or partially, within at least one of the processors 410 (e.g., within the processor's cache memory), the
  • any portion of the instructions 450 can be transferred to the hardware resources 400 from any combination of the peripheral devices 404 and/or the databases 406.
  • the memory of processors 410, the memory/storage devices 420, the peripheral devices 404, and the databases 406 are examples of computer-readable and machine-readable media.
  • the communication protocol stack 300 or the MAC layer components can be processor components such as the processor 41 2 or 414, or executable components of memory / storage devices 420 with / part of executable instructions 450 for executing these components based on communication resources 430.
  • the central MAC layer component 314 in CU can govern or manage the centralized scheduling with multi-cell PHY configurations across DUs 316, 318, including the support of: UEs (e.g., 1 12-1 16) enabled with coordinated multipoint (CoMP), carrier aggregation (CA), dual connectivity (DC), or other
  • Inter-cell interference management to coordinate functions among DUs to perform inter-cell (inter network (e.g., 120, 122, etc.), or inter-cell 1 12-1 16) operations; Load balancing and performance adaptation between DUs 316, 318.
  • a PHY layer configuration associated to one DU 316 can support CoMP while another DU 318 support carrier aggregation, and associated resources / resource parameters, for example.
  • CoMP can comprise data and channel state information (CSI) being shared among neighboring cellular base stations or eNBs to coordinate their transmissions in the downlink and jointly process the received signals in the uplink.
  • CoMP can utilize a high-speed backhaul network for enabling the exchange of information (e.g., data, control information, and CSI) between the BSs or eNBs, which can be achieved via an optical fiber fronthaul or other interface that can be integrated / interface with the MAC layer 310 or MAC interface 330.
  • Carrier aggregation can include operations to aggregate various component carriers inter-band, intra-band, non-contiguously or contiguously to improve the uplink or downlink frequency spectrum usage more efficiently.
  • Dual connectivity can enable UEs to be connected to one another directly or simultaneously to one another or different eNBs (e.g., RAN 108 and 1 1 0).
  • the central MAC layer component 314 in CU can consider the transport network characteristic (such as available bandwidth (BW) and latency) and the processing capability (or speed) of each DU, when deciding the centralized resource allocation for configuration or function delegation to the various DUs 316, 318, or more.
  • the central MAC layer component 314 can retrieve the scheduling-related information and data from each local MAC layer component 316, 31 8, such as a Buffer status report (BSR) per UE 1 1 2-1 1 6, a power headroom report (PHR) per UE 1 12-1 16 for UL scheduling, load or queue information, or other scheduling related parameter / resource request.
  • BSR Buffer status report
  • PHR power headroom report
  • Scheduling related information can also include data that is common to UE's 1 1 2-1 16 such as common search space parameters like control information, system information, scheduling, or data on a per UE radio channel, as well as signal measurements (power, load, timing, or other UE measurement reporting parameters) from the associated PHY layer for DL / UL scheduling.
  • common search space parameters like control information, system information, scheduling, or data on a per UE radio channel, as well as signal measurements (power, load, timing, or other UE measurement reporting parameters) from the associated PHY layer for DL / UL scheduling.
  • the central MAC layer component 314 can configure each local MAC layer component of DU 316, 318 to perform various MAC operations, separately from other DUs, in conjunction with central MAC layer component 314 processes, or independent of the central MAC layer component 314 including UL or DL HARQ per UE 1 12-1 16, per traffic flow (e.g., based on a QoS associated with a particular communication), or per bearer.
  • the central MAC layer component 314 can also configure each local MAC layer component of DU 316, 318 to perform various MAC operations separately from other DUs, in conjunction with central MAC layer component 314 processes, or independent of the central MAC layer component 314 including cell-specific MAC functionalities such as random access control per PHY configuration (per UE or per network RAT), maintenance on cell radio network temporary identifier (C-RNTI), UL timing alignment per UE, or other similar related network parameters.
  • cell-specific MAC functionalities such as random access control per PHY configuration (per UE or per network RAT), maintenance on cell radio network temporary identifier (C-RNTI), UL timing alignment per UE, or other similar related network parameters.
  • the local MAC layer component 316 or 318 can be configured to perform its own localized resource allocations in order to support the configured MAC operations or UEs that do not require multi-cell PHY configurations across different DUs, which can be assigned or allocated different configurations or resources for scheduling operations for communications (e.g., DL / UL grant, bandwidth, power, for communication through the PHY layer).
  • the local MAC layer component 316 or 31 8 can retrieve the scheduling-related information and data such as queue dynamics from the central MAC layer component 314 for DL scheduling and generating the transport block to the PHY layer 312, for example.
  • the local MAC layer components 316 or 31 8 are configured by the central MAC layer component 314 separately and independently to carry out assigned functions in lieu of or in conjunction with the central MAC layer component 314.
  • These functions can include scheduling operations or other MAC layer functions specific or local to a particular PHY configuration, UE 1 1 2-1 1 6, or network RATs of RANs 108 or 1 1 0, for example. Any control of scheduling resources described herein or particular configurations, which can involve partition configurations for one or more of these functions, can be allocated, assigned or delegated for control /
  • a local MAC layer component 316 or 31 8 processing by a local MAC layer component 316 or 31 8, for example.
  • the functions configured to, or partitioned to a local MAC layer component 316 or 31 8 by the central MAC layer component 314 can be for localized scheduling implementations or scheduling operations to be carried out or shared by the local MAC layer component 31 6 or 318.
  • the localized scheduling implementations / operations can include different resources or parameters in different processes.
  • the local MAC layer component 31 6 or 318 can use the remaining physical resource block (PRB) per each transmission time interval (TTI) from the centralized allocation decision or configuration (resource / partition configuration) allocated by the central MAC layer component 314.
  • the central MAC layer component 314 can allocate what functions, particular resources, or partition configuration for one or more PHY configurations, UEs, or networks via a PRB communication at a TTI. Remainder bits, frames, subframes or PRB resources can be utilized by the local MAC layer component 316 or 318 for scheduling one or more UEs or networks for communication or scheduling requests.
  • subframes can be interlaced for localized / centralized usage.
  • the process by which to interlace can be pre-configured or adaptively managed by the central MAC layer component 314.
  • An interlace can be a sub-carrier mapping operations that enables multiple bits, bit streams or interleaved encoded bits, for example, to be combined with a same level of protection for each sequence, for example.
  • PRBs can be partitioned for localized / centralized usage at every TTI granularity, in which the partition can be pre-configured or adaptively managed by the central MAC layer component 314.
  • the local MAC layer component 316 or 318 can be
  • one or more of these above processes (or options) discussed for localized operations in the local MAC layer component 316 or 318 can be used to configure or re-configure each local MAC layer component 316 or 318 based on periodic reports in a semi-persistent manner, upon request, or initiation by the central MAC layer component 314 itself.
  • the MAC interface 330 or 330' can be further established as the
  • the central MAC layer component 314 can initiate the interface establishment.
  • the MAC interface 330, 330' can support the message exchanges such as MACx SETUP REQUEST, MACx SETUP RESPONSE or MACx SETUP FAILURE for the interface establishment. This way one or more DUs can be integrated, added as well as removed via such messages.
  • a unique local MAC entity identifier for each local MAC layer component 316 or 318 or DU, for example, can be determined through the interface establishment.
  • the information regarding the transport network characteristic can be measured and updated periodically or per request through the MAC interface 330, 330'.
  • the MAC interface 330, 330' can support the message exchanges conveying MAC control-related information, e.g. the local MAC entity configuration, the scheduling-related information / configuration as discussed herein.
  • the MAC interface 330, 330' can support the message exchanges conveying user-plane information such as one or more TBs to the PHY layer, or from the central MAC layer component 314.
  • FIG. 5 illustrates one embodiment of a process flow 500 to generate a MAC layer control structure in a hierarchy within the MAC layer as a fronthauling split, in which the MAC layer distributes or partitions its functions in a hierarchy for fronthauling operations associated with the MAC layer (e.g., scheduling related resources).
  • the method 500 can be considered a distribution hierarchical structure process flow 500 in functional processing within the MAC layer of communication protocol stack models.
  • the operations can be enabled by any network device (e.g., eNB, NRAT, UE or other network device or component).
  • one or more processors can perform operations in a multi-radio heterogeneous network including different RATs comprising: providing, via a central MAC layer component configured to operate as a central unit or CU of the MAC layer, a partition configuration to a local MAC layer component of a plurality of local MAC layer components to configure the local MAC layer component (e.g., 316) as a distribution unit (DU) of the MAC layer with the central MAC layer component.
  • the partition configuration can be a distribution of functionality or resources for governing one or more MAC layer functions, such as scheduling, HARQ operations, random access channel operations or the like.
  • the DU can then be configured to make its own scheduling decisions across one or more UEs, one or more PHY configurations, one or more networks or other network devices based on configuration (partition configuration) enabled by the central MAC layer component (e.g., 314).
  • the method 500 includes communicatively coupling, via a MAC layer interface, communications between the central MAC layer component and the plurality of local MAC layer components in a hierarchal structure to execute operations of the MAC layer.
  • the method 500 can further include performing, via the local MAC layer component, a localized resource scheduling of one or more scheduling resources through one or more lower protocol layers, independent of or in coordination with the central MAC layer component based on the partition configuration.
  • the central MAC layer component e.g., 314 configures the local MAC layer components for localized resource scheduling to one or more PHY configurations.
  • the local MAC layer components can then schedule communications with network devices with or without the central processing unit in CU of the MAC layer of a network device such as an eNB or other network device (e.g., a UE or other network device).
  • the local MAC layer component can retrieve, via the MAC layer interface (e.g., 330), scheduling related information including UE data and the partition configuration associated with one or more higher protocol layers from the central MAC layer component 314, for example.
  • FIG. 6 another process flow 600 that can be a part of the process flow 500 or a separate process flow order to enable localized scheduling in a MAC layer from a CU to one or more DUs therein
  • the method 600 comprises determining, via a central MAC layer component, a resource allocation associated among a plurality of local MAC layer components based on a transport network characteristic of the MAC layer interface and a processing capability of the plurality of local MAC layer components, the transport network characteristic comprising at least one of: an available bandwidth or a latency of a physical medium of the MAC layer interface connecting the central MAC layer component and the plurality of local MAC layer components.
  • the partition configuration designates localized resource allocations among the plurality of local MAC layer components to independently configure the plurality of local MAC layer components to support one or more different PHY protocol layer configurations among network devices for scheduling operations.
  • the method 600 includes controlling a centralized scheduling of the plurality of local MAC layer components according to different physical (“PHY”) protocol layer configurations among at least one of: one or more cell networks or one or more user UEs.
  • PHY physical
  • the local MAC layer components can receive or obtain one or more physical resources related to different PHY protocol layer configurations from the central MAC layer component, and report periodically or as requested by the central MAC layer component any physical resources to the central MAC layer component that it may need to perform for scheduling or other functions or as requested by a UE or network that is beyond what it has been allocated for.
  • the central MAC layer component can opt or not to modify the partition configuration of a local MAC layer component of the plurality of local MAC layer components based on a change of a PHY layer configuration of a UE, a network or a traffic flow of data.
  • circuitry may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality.
  • ASIC Application Specific Integrated Circuit
  • the circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules.
  • circuitry may include logic, at least partially operable in hardware.
  • FIG. 7 illustrates, for one embodiment, example components of a network device such as an eNB, a User Equipment (UE), or other similar network device 700.
  • the network device 700 can include application circuitry 702, baseband circuitry 704, Radio Frequency (RF) circuitry 706, front-end module (FEM) circuitry 708 and one or more antennas 710, coupled together at least as shown.
  • RF Radio Frequency
  • FEM front-end module
  • the application circuitry 702 can include one or more application processors.
  • the application circuitry 702 can include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the processor(s) can include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.).
  • the processors can be coupled with and/or can include memory/storage and can be configured to execute instructions stored in the memory/storage to enable various applications and/or operating systems to run on the system.
  • the baseband circuitry 704 can include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the baseband circuitry 704 can include one or more baseband processors and/or control logic to process baseband signals received from a receive signal path of the RF circuitry 706 and to generate baseband signals for a transmit signal path of the RF circuitry 706.
  • Baseband processing circuity 704 can interface with the application circuitry 702 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 706.
  • the baseband circuitry 704 can include a second generation (2G) baseband processor 704a, third generation (3G) baseband processor 704b, fourth generation (4G) baseband processor 704c, and/or other baseband processor(s) 704d for other existing generations, generations in development or to be developed in the future (e.g., fifth generation (5G), 6G, etc.).
  • the baseband circuitry 704 e.g., one or more of baseband processors 704a-d
  • the radio control functions can include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc.
  • modulation/demodulation circuitry of the baseband circuitry 704 can include Fast-Fourier Transform (FFT), precoding, and/or constellation mapping / demapping functionality.
  • FFT Fast-Fourier Transform
  • encoding/decoding circuitry of the baseband circuitry 704 can include convolution, tail-biting convolution, turbo, Viterbi, and/or Low Density Parity Check (LDPC) encoder/decoder functionality.
  • LDPC Low Density Parity Check
  • the baseband circuitry 704 can include elements of a protocol stack such as, for example, elements of an evolved universal terrestrial radio access network (EUTRAN) protocol including, for example, physical (PHY), media access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), and/or radio resource control (RRC) elements.
  • EUTRAN evolved universal terrestrial radio access network
  • a central processing unit (CPU) 704e of the baseband circuitry 704 can be configured to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP and/or RRC layers.
  • the baseband circuitry can include one or more audio digital signal processor(s) (DSP) 704f.
  • DSP audio digital signal processor
  • the audio DSP(s) 704f can be include elements for compression/decompression and echo cancellation and can include other suitable processing elements in other embodiments.
  • Components of the baseband circuitry can be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments.
  • some or all of the constituent components of the baseband circuitry 704 and the application circuitry 702 can be implemented together such as, for example, on a system on a chip (SOC).
  • SOC system on a chip
  • the baseband circuitry 704 can provide for
  • the baseband circuitry 704 can support communication with an evolved universal terrestrial radio access network (EUTRAN) and/or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN).
  • EUTRAN evolved universal terrestrial radio access network
  • WMAN wireless metropolitan area networks
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • multi-mode baseband circuitry Embodiments in which the baseband circuitry 704 is configured to support radio communications of more than one wireless protocol.
  • RF circuitry 706 can enable communication with wireless networks
  • the RF circuitry 706 can include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • RF circuitry 706 can include a receive signal path which can include circuitry to down-convert RF signals received from the FEM circuitry 708 and provide baseband signals to the baseband circuitry 704.
  • RF circuitry 706 can also include a transmit signal path which can include circuitry to up- convert baseband signals provided by the baseband circuitry 704 and provide RF output signals to the FEM circuitry 708 for transmission.
  • the RF circuitry 706 can include a receive signal path and a transmit signal path.
  • the receive signal path of the RF circuitry 706 can include mixer circuitry 706a, amplifier circuitry 706b and filter circuitry 706c.
  • the transmit signal path of the RF circuitry 706 can include filter circuitry 706c and mixer circuitry 706a.
  • RF circuitry 706 can also include synthesizer circuitry 706d for synthesizing a frequency for use by the mixer circuitry 706a of the receive signal path and the transmit signal path.
  • the mixer circuitry 706a of the receive signal path can be configured to down-convert RF signals received from the FEM circuitry 708 based on the synthesized frequency provided by synthesizer circuitry 706d.
  • the amplifier circuitry 706b can be configured to amplify the down-converted signals and the filter circuitry 706c can be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals.
  • LPF low-pass filter
  • BPF band-pass filter
  • Output baseband signals can be provided to the baseband circuitry 704 for further processing.
  • the output baseband signals can be zero- frequency baseband signals, although this is not a requirement.
  • mixer circuitry 706a of the receive signal path can comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 706a of the transmit signal path can be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 706d to generate RF output signals for the FEM circuitry 708.
  • the baseband signals can be provided by the baseband circuitry 704 and can be filtered by filter circuitry 706c.
  • the filter circuitry 706c can include a low-pass filter (LPF), although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 706a of the receive signal path and the mixer circuitry 706a of the transmit signal path can include two or more mixers and can be arranged for quadrature downconversion and/or upconversion respectively.
  • the mixer circuitry 706a of the receive signal path and the mixer circuitry 706a of the transmit signal path can include two or more mixers and can be arranged for image rejection (e.g., Hartley image rejection).
  • the mixer circuitry 706a of the receive signal path and the mixer circuitry 706a can be arranged for direct downconversion and/or direct upconversion, respectively.
  • the mixer circuitry 706a of the receive signal path and the mixer circuitry 706a of the transmit signal path can be configured for super-heterodyne operation.
  • the output baseband signals and the input baseband signals can be analog baseband signals, although the scope of the embodiments is not limited in this respect.
  • the output baseband signals and the input baseband signals can be digital baseband signals.
  • the RF circuitry 706 can include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 704 can include a digital baseband interface to communicate with the RF circuitry 706.
  • ADC analog-to-digital converter
  • DAC digital-to-analog converter
  • a separate radio IC circuitry can be provided for processing signals for each spectrum, although the scope of the
  • the synthesizer circuitry 706d can be a fractional-N synthesizer or a fractional N/N+1 synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers can be suitable.
  • synthesizer circuitry 706d can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 706d can be configured to synthesize an output frequency for use by the mixer circuitry 706a of the RF circuitry 706 based on a frequency input and a divider control input.
  • the synthesizer circuitry 706d can be a fractional N/N+1 synthesizer.
  • frequency input can be provided by a voltage controlled oscillator (VCO), although that is not a requirement.
  • VCO voltage controlled oscillator
  • Divider control input can be provided by either the baseband circuitry 704 or the applications processor 702 depending on the desired output frequency.
  • a divider control input e.g., N
  • N can be determined from a look-up table based on a channel indicated by the applications processor 702.
  • Synthesizer circuitry 706d of the RF circuitry 706 can include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator.
  • the divider can be a dual modulus divider (DMD) and the phase accumulator can be a digital phase accumulator (DPA).
  • the DMD can be configured to divide the input signal by either N or N+1 (e.g., based on a carry out) to provide a fractional division ratio.
  • the DLL can include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip- flop.
  • the delay elements can be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line.
  • Nd is the number of delay elements in the delay line.
  • synthesizer circuitry 706d can be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other.
  • the output frequency can be a LO frequency (f
  • the RF circuitry 706 can include an IQ/polar converter.
  • FEM circuitry 708 can include a receive signal path which can include circuitry configured to operate on RF signals received from one or more antennas 710, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 706 for further processing.
  • FEM circuitry 708 can also include a transmit signal path which can include circuitry configured to amplify signals for transmission provided by the RF circuitry 706 for transmission by one or more of the one or more antennas 710.
  • the FEM circuitry 708 can include a TX/RX switch to switch between transmit mode and receive mode operation.
  • the FEM circuitry can include a receive signal path and a transmit signal path.
  • the receive signal path of the FEM circuitry can include a low-noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 706).
  • LNA low-noise amplifier
  • the transmit signal path of the FEM circuitry 708 can include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 706), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 71 0.
  • PA power amplifier
  • the device 700 can include additional elements such as, for example, memory/storage, display, camera, sensor, or an input/output (I/O) interface.
  • additional elements such as, for example, memory/storage, display, camera, sensor, or an input/output (I/O) interface.
  • I/O input/output
  • FIG. 8 illustrates a block diagram of an embodiment of access (or user) equipment related to access of a network (e.g., network device, base station, wireless access point, femtocell access point, and so forth) that can enable and/or exploit features or aspects disclosed herein.
  • a network e.g., network device, base station, wireless access point, femtocell access point, and so forth
  • Access equipment e.g., eNB, network entity, or the like
  • UE or software related to access of a network can receive and transmit signal(s) from and to wireless devices, wireless ports, wireless routers, etc. through segments 802 802 B (B is a positive integer).
  • Segments 802 802 B can be internal and/or external to access equipment and/or software related to access of a network, and can be controlled by a monitor component 804 and an antenna component 806.
  • Monitor component 804 and antenna component 806 can couple to communication platform 808, which can include electronic components and associated circuitry that provide for processing and manipulation of received signal(s) and other signal(s) to be transmitted.
  • communication platform 808 includes a receiver/transmitter 810 that can convert analog signals to digital signals upon reception of the analog signals, and can convert digital signals to analog signals upon transmission.
  • receiver/transmitter 810 can divide a single data stream into multiple, parallel data streams, or perform the reciprocal operation.
  • Coupled to receiver/transmitter 810 can be a multiplexer / demultiplexer 812 that can facilitate manipulation of signals in time and frequency space. Multiplexer / demultiplexer 812 can multiplex information
  • multiplexer/ demultiplexer component 812 can scramble and spread information (e.g., codes, according to substantially any code known in the art, such as Hadamard-Walsh codes, Baker codes, Kasami codes, polyphase codes, and so forth).
  • a modulator/demodulator 814 is also a part of communication platform 808, and can modulate information according to multiple modulation techniques, such as frequency modulation, amplitude modulation (e.g., M-ary quadrature amplitude modulation, with M a positive integer); phase-shift keying; and so forth).
  • modulation techniques such as frequency modulation, amplitude modulation (e.g., M-ary quadrature amplitude modulation, with M a positive integer); phase-shift keying; and so forth).
  • Access equipment and/or software related to access of a network also includes a processor 816 configured to confer, at least in part, functionality to substantially any electronic component in access equipment and/or software.
  • processor 816 can facilitate configuration of access equipment and/or software through, for example, monitor component 804, antenna component 806, and one or more components therein.
  • access equipment and/or software can include display interface 818, which can display functions that control functionality of access equipment and/or software or reveal operation conditions thereof.
  • display interface 818 can include a screen to convey information to an end user.
  • display interface 818 can be a liquid crystal display, a plasma panel, a monolithic thin-film based electrochromic display, and so on.
  • display interface 818 can include a component (e.g., speaker) that facilitates communication of aural indicia, which can also be employed in connection with messages that convey operational instructions to an end user.
  • Display interface 818 can also facilitate data entry (e.g., through a linked keypad or through touch gestures), which can cause access equipment and/or software to receive external commands (e.g., restart operation).
  • Broadband network interface 820 facilitates connection of access equipment and/or software to a service provider network (not shown) that can include one or more cellular technologies (e.g., third generation partnership project universal mobile telecommunication system, global system for mobile communication, and so on) through backhaul link(s) (not shown), which enable incoming and outgoing data flow.
  • Broadband network interface 820 can be internal or external to access equipment and/or software and can utilize display interface 818 for end-user interaction and status information delivery.
  • Processor 816 can be functionally connected to communication platform 808 and can facilitate operations on data (e.g., symbols, bits, or chips) for
  • processor 816 can be functionally connected, through data, system, or an address bus 822, to display interface 81 8 and broadband network interface 820, to confer, at least in part, functionality to each of such components.
  • access equipment and/or software memory 824 can retain location and/or coverage area (e.g., macro sector, identifier(s)) access list(s) that authorize access to wireless coverage through access equipment and/or software sector intelligence that can include ranking of coverage areas in the wireless environment of access equipment and/or software, radio link quality and strength associated therewith, or the like.
  • location and/or coverage area e.g., macro sector, identifier(s)
  • access list(s) that authorize access to wireless coverage through access equipment and/or software sector intelligence that can include ranking of coverage areas in the wireless environment of access equipment and/or software, radio link quality and strength associated therewith, or the like.
  • Memory 824 also can store data structures, code instructions and program modules, system or device information, code sequences for scrambling, spreading and pilot transmission, access point configuration, and so on.
  • Processor 81 6 can be coupled (e.g., through a memory bus), to memory 824 in order to store and retrieve information used to operate and/or confer functionality to the components, platform, and interface that reside within access equipment and/or software.
  • the memory 824 can comprise one or more machine-readable medium / media including instructions that, when performed by a machine or component herein cause the machine to perform acts of the method or of an apparatus or system for concurrent communication using multiple communication technologies according to embodiments and examples described herein. It is to be understood that aspects described herein can be implemented by hardware, software, firmware, or any combination thereof. When implemented in software, functions can be stored on or transmitted over as one or more instructions or code on a computer-readable medium (e.g., the memory described herein or other storage device).
  • Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a storage media or a computer readable storage device can be any available media that can be accessed by a general purpose or special purpose computer.
  • Such computer-readable media can comprise RAM, ROM, EEPROM, CD- ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or other tangible and/or non-transitory medium, that can be used to carry or store desired information or executable instructions.
  • any connection can also be termed a computer-readable medium.
  • coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave are included in the definition of medium.
  • processor can refer to substantially any computing processing unit or device including, but not limited to including, single-core processors; single-processors with software multithread execution capability; multi-core processors; multi-core processors with software multithread execution capability; multi-core processors with hardware multithread technology;
  • a processor can refer to an integrated circuit, an application specific integrated circuit, a digital signal processor, a field programmable gate array, a programmable logic controller, a complex programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions and/or processes described herein.
  • Processors can exploit nano-scale architectures such as, but not limited to, molecular and quantum-dot based transistors, switches and gates, in order to optimize space usage or enhance performance of mobile devices.
  • a processor may also be implemented as a combination of computing processing units.
  • memory components or entities embodied in a “memory,” or components including the memory. It is noted that the memory components described herein can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory.
  • nonvolatile memory for example, can be included in a memory, non-volatile memory (see below), disk storage (see below), and memory storage (see below). Further, nonvolatile memory can be included in read only memory, programmable read only memory, electrically programmable read only memory, electrically erasable programmable read only memory, or flash memory.
  • Volatile memory can include random access memory, which acts as external cache memory.
  • random access memory is available in many forms such as synchronous random access memory, dynamic random access memory, synchronous dynamic random access memory, double data rate synchronous dynamic random access memory, enhanced synchronous dynamic random access memory, Synchlink dynamic random access memory, and direct Rambus random access memory.
  • the disclosed memory components of systems or methods herein are intended to include, without being limited to including, these and any other suitable types of memory.
  • Examples can include subject matter such as a method, means for performing acts or blocks of the method, at least one machine-readable medium including instructions that, when performed by a machine cause the machine to perform acts of the method or of an apparatus or system for concurrent communication using multiple communication technologies according to embodiments and examples described herein.
  • Example 1 is an apparatus configured to be employed in an evolved NodeB (eNB), comprising: a central medium access control (MAC) layer component configured, as a central unit (CU) located within a MAC layer, to communicatively interact with one or more upper protocol layers that comprise at least one of: a radio link control (RLC) layer, packet data convergence protocol (PDCP) layer, or a radio resource control (RRC) layer; one or more local MAC layer components as distributed units (DUs) located within the MAC layer and communicatively coupled to the central MAC layer component, configured to interact between one or more lower protocol layers
  • a central medium access control (MAC) layer component configured, as a central unit (CU) located within a MAC layer, to communicatively interact with one or more upper protocol layers that comprise at least one of: a radio link control (RLC) layer, packet data convergence protocol (PDCP) layer, or a radio resource control (RRC) layer
  • RLC radio link control
  • PDCP packet data convergence protocol
  • RRC radio resource
  • MAC layer interface located between the central MAC layer component and the one or more local MAC layer components, configured to communicatively couple the central MAC layer component with the one or more local MAC layer components.
  • Example 2 includes the subject matter of Example 1 , the apparatus of claim 1 , wherein the central MAC layer component is further configured to control a
  • centralized scheduling of the one or more local MAC layer components according to different PHY layer configurations of at least one of: one or more cell networks or one or more user equipments (UEs), based on at least one of: a coordinated multi-point (CoMP) for joint processing and scheduling coordination, a carrier aggregation (CA), or a dual connectivity (DC).
  • CoMP coordinated multi-point
  • CA carrier aggregation
  • DC dual connectivity
  • Example 3 includes the subject matter of any one of Examples 1 -2, including or omitting any elements as optional, wherein the central MAC layer component is further configured to coordinate, through the one or more local MAC layer components, communications related to inter-cell interference between a plurality of cell networks.
  • Example 4 includes the subject matter of any one of Examples 1 -3, including or omitting any elements as optional, wherein the central MAC layer component is further configured to perform at least one of: a load-balancing or a performance adaptation between a plurality of local MAC layer components as the distributed units (DUs) located within the MAC layer and coupled to the central MAC layer component.
  • the central MAC layer component is further configured to perform at least one of: a load-balancing or a performance adaptation between a plurality of local MAC layer components as the distributed units (DUs) located within the MAC layer and coupled to the central MAC layer component.
  • DUs distributed units
  • Example 5 includes the subject matter of any one of Examples 1 -4, including or omitting any elements as optional, wherein the central MAC layer component is further configured to determine a resource allocation among a plurality of local MAC layer components based on a transport network characteristic of the MAC layer interface and a processing capability of the one or more local MAC layer components, the transport network characteristic comprising at least one of: an available bandwidth or a latency of a physical medium of the MAC layer interface connecting the central MAC layer component and the one or more local MAC layer components.
  • Example 6 includes the subject matter of any one of Examples 1 -5, including or omitting any elements as optional, wherein the central MAC layer component is further configured to configure MAC layer operations to the one or more local MAC layer components, the MAC layer operations including one or more of: an uplink
  • HARQ hybrid automatic repeat request
  • a cell specific MAC functionality including a random access control
  • a UE specific functionality including managing a cell radio network temporary identifier (C-RNTI) or an uplink timing alignment between UEs.
  • C-RNTI cell radio network temporary identifier
  • Example 7 includes the subject matter of any one of Examples 1 -6, including or omitting any elements as optional, wherein the one or more local MAC layer components are further configured to coordinate scheduling operations and MAC layer processes with the central MAC layer component, and perform a localized scheduling of data from the one or more lower protocol layers independent of the central MAC layer component based on the scheduling operations with the central MAC layer component.
  • Example 8 includes the subject matter of any one of Examples 1 -7, including or omitting any elements as optional, wherein the one or more local MAC layer components are further configured to retrieve scheduling operation data and queue data from the central MAC layer component, and generate an uplink / downlink scheduling communication and a transport block based on the scheduling operation data and the queue data for the one or more lower or higher protocol layers.
  • Example 9 includes the subject matter of any one of Examples 1 -8, including or omitting any elements as optional, wherein the one or more local MAC layer components are further configured to perform the localized scheduling of data by utilizing a physical resource block (PRB) of a transmission time interval (TTI) that remains from a communication of a scheduling operation, interlacing subframes associated with the scheduling operations, or partitioning the PRB of the TTI.
  • PRB physical resource block
  • TTI transmission time interval
  • Example 10 includes the subject matter of any one of Examples 1 -9, including or omitting any elements as optional, wherein the one or more local MAC layer components are further configured to generate a measurement of at least one of: a scheduling operation, a PRB usage, or a transport network characteristic, and report a measurement report, periodically or as requested, to the central MAC layer component based on the measurement.
  • the one or more local MAC layer components are further configured to generate a measurement of at least one of: a scheduling operation, a PRB usage, or a transport network characteristic, and report a measurement report, periodically or as requested, to the central MAC layer component based on the measurement.
  • Example 1 1 includes the subject matter of any one of Examples 1 -10, including or omitting any elements as optional, wherein the MAC layer interface comprises a hierarchical structure between the central MAC layer component and the one or more local MAC layer components, and is further configured to communicate a scheduling operation partition configuration between the central MAC layer component and the one or more local MAC layer components, wherein the scheduling operation partition configuration designates what scheduling operations are conferred to the one or more MAC layer components to enable joint MAC layer operations of the MAC layer.
  • Example 12 includes the subject matter of any one of Examples 1 -1 1 , including or omitting any elements as optional, wherein the MAC layer interface is further configured to support message exchanges comprising at least one of: a MAC setup request, a MAC setup response, a MAC setup failure corresponding with an interface establishment between the central MAC layer component and the one or more local MAC layer components, or a unique local MAC entity identifier of the one or more local MAC layer components.
  • Example 13 is a computer-readable medium comprising executable instructions that, in response to execution, cause a system of an evolved NodeB (eNB) or a user equipment (UE) comprising one or more processors to perform operations in a multi-radio heterogeneous network including different radio access technologies (RATs), the operations comprising: providing, via a central medium access control (MAC) layer component configured to operate as a central unit (CU) of a MAC layer, a partition configuration to a local MAC layer component of a plurality of local MAC layer components configured to operate as distribution units (DUs) of the MAC layer with the central MAC layer component; and communicatively coupling, via a MAC layer interface, communications between the central MAC layer component and the plurality of local MAC layer components in a hierarchal structure to execute operations of the MAC layer.
  • a central medium access control (MAC) layer component configured to operate as a central unit (CU) of a MAC layer
  • DUs distribution units
  • Example 14 includes the subject matter of Example 13, including or omitting any elements as optional, wherein the operations further comprise: performing, via the local MAC layer component, a localized resource scheduling of one or more scheduling resources through one or more lower protocol layers, independent of or in coordination with the central MAC layer component based on the partition configuration.
  • Example 15 includes the subject matter of any one of Examples 1 3-14, including or omitting any elements as optional, wherein the operations further comprise: retrieving, at the local MAC layer component via the MAC layer interface, scheduling related information including user equipment (UE) data and the partition configuration associated with one or more higher protocol layers from the central MAC layer component; and controlling a centralized scheduling of the plurality of local MAC layer components according to different physical (PHY) protocol layer configurations among at least one of: one or more cell networks.
  • UE user equipment
  • PHY physical
  • Example 16 includes the subject matter of any one of Examples 1 3-15, including or omitting any elements as optional, wherein the operations further comprise: receiving or obtaining, via the plurality of local MAC layer components, one or more physical resources related to different PHY protocol layer configurations; and reporting, periodically or as requested by the central MAC layer component, the one or more physical resources to the central MAC layer component.
  • Example 17 includes the subject matter of any one of Examples 1 3-16, including or omitting any elements as optional, wherein the operations further comprise:
  • Example 18 includes the subject matter of any one of Examples 1 3-17, including or omitting any elements as optional, wherein the partition configuration designates localized resource allocations among the plurality of local MAC layer components to independently configure the plurality of local MAC layer components to support one or more different PHY protocol layer configurations among network devices for scheduling operations.
  • Example 19 includes the subject matter of any one of Examples 1 3-18, including or omitting any elements as optional, wherein the operations further comprise: modifying, via the central MAC layer component, the partition configuration of the local MAC layer component of the plurality of local MAC layer components based on a change in a change of a PHY layer configuration of a network device, a network or a traffic flow.
  • Example 20 is an apparatus employed in a user equipment (UE), comprising:
  • a central medium access control (MAC) layer component configured, as a central unit (CU) located within a first MAC layer of a MAC layer, to communicatively interact with one or more upper protocol layers and a second MAC layer of the MAC layer that is below the first MAC layer in a communication protocol stack; one or more local MAC layer components as distributed units (DUs) located within the second MAC layer and communicatively coupled to the central MAC layer component, configured to be controlled by the central MAC layer component, and communicate with one or more lower protocol layers; and a MAC layer interface, located between the central MAC layer component and the one or more local MAC layer components, configured to communicatively couple the central MAC layer component with the one or more local MAC layer components.
  • DUs distributed units
  • Example 21 includes the subject matter of Example 20, including or omitting any elements as optional, wherein the one or more local MAC layer components are configured to receive a partition configuration that designates one or more scheduling operations or scheduling resources from the central MAC layer component to enable MAC layer operations comprising uplink / downlink communications related to a hybrid automatic repeat request (HARQ), a random access control, a cell radio network temporary identifier (C-RNTI), or an uplink timing alignment between UEs.
  • HARQ hybrid automatic repeat request
  • C-RNTI cell radio network temporary identifier
  • Example 22 includes the subject matter of any one of Examples 20-21 , including or omitting any elements as optional, wherein the partition configuration further designates local scheduling resources to the one or more local MAC layer components to independently configure one or more scheduling resources for a UE, wherein the one or more scheduling resources comprise uplink / downlink scheduling and transport block generation.
  • Example 23 includes the subject matter of any one of Examples 20-22, including or omitting any elements as optional, wherein the one or more local MAC layer components are configured to schedule communication resources based on data provided by the central MAC layer and related to a physical (PHY) layer configuration of the UE, wherein the PHY layer configuration can include at least one of: a coordinated multi-point (CoMP) for joint processing and scheduling coordination, a carrier aggregation (CA), or a dual connectivity (DC).
  • CoMP coordinated multi-point
  • CA carrier aggregation
  • DC dual connectivity
  • Example 24 includes the subject matter of any one of Examples 20-22, including or omitting any elements as optional, wherein the one or more local MAC layer components are configured to perform a localized resource scheduling of resources to support MAC layer operations.
  • Example 25 includes the subject matter of any one of Examples 20-23, including or omitting any elements as optional, wherein the local MAC layer component is configured to generate one or more measurements of an available bandwidth, a latency, or a buffer status, and report, periodically or as requested, the one or more measurements through the MAC layer interface to the central MAC layer component.
  • Example 26 is a system employed in an evolved NodeB (eNB) or a user equipment (UE), comprising: a central medium access control (MAC) layer component configured, as a central unit (CU) located within a first MAC layer of a MAC layer, to communicatively interact with one or more upper protocol layers and a second MAC layer of the MAC layer that is below the first MAC layer in a communication protocol stack; one or more local MAC layer components as distributed units (DUs) located within the second MAC layer and communicatively coupled to the central MAC layer component, configured to be controlled by the central MAC layer component, and communicate with one or more lower protocol layers; and a MAC layer interface, located between the central MAC layer component and the one or more local MAC layer components, configured to communicatively couple the central MAC layer component with the one or more local MAC layer components.
  • a central medium access control (MAC) layer component configured, as a central unit (CU) located within a first MAC layer of a MAC layer, to communic
  • Example 27 includes the subject matter of Example 26, including or omitting any elements as optional, wherein the one or more local MAC layer components are configured to receive a partition configuration that designates one or more scheduling operations or scheduling resources from the central MAC layer component to enable MAC layer operations comprising uplink / downlink communications related to a hybrid automatic repeat request (HARQ), a random access control, a cell radio network temporary identifier (C-RNTI), or an uplink timing alignment between different UEs.
  • HARQ hybrid automatic repeat request
  • C-RNTI cell radio network temporary identifier
  • Example 28 includes the subject matter of any one of Examples 26-27, including or omitting any elements as optional, wherein the partition configuration further designates local scheduling resources to the one or more local MAC layer components to independently configure one or more scheduling resources for a UE, wherein the one or more scheduling resources comprise uplink / downlink scheduling and transport block generation.
  • Example 29 includes the subject matter of any one of Examples 26-28, including or omitting any elements as optional, wherein the one or more local MAC layer components are configured to schedule communication resources for the user equipment (UE) based on data provided by the central MAC layer and related to a physical (PHY) layer configuration of the UE, wherein the PHY layer configuration can include at least one of: a coordinated multi-point (CoMP) for joint processing and scheduling coordination, a carrier aggregation (CA), or a dual connectivity (DC).
  • CoMP coordinated multi-point
  • CA carrier aggregation
  • DC dual connectivity
  • Example 30 includes the subject matter of any one of Examples 26-29, including or omitting any elements as optional, wherein the one or more local MAC layer components are configured to perform a localized resource scheduling of resources to support MAC layer operations or one or more UEs not communicating based on multiple network cell PHY layer configurations.
  • Example 31 includes the subject matter of any one of Examples 26-30, including or omitting any elements as optional, wherein the local MAC layer component is configured to generate one or more measurements of an available bandwidth, a latency, or a buffer status, and report, periodically or as requested, the one or more measurements through the MAC layer interface to the central MAC layer component.
  • Example 32 is an apparatus employed in an evolved NodeB (eNB) or a user equipment (UE) comprising: means for providing a partition configuration to a local MAC layer component of a plurality of local MAC layer components configured to operate as distribution units (DUs) of a central medium access control (MAC) layer component as a central unit (CU) of a MAC layer; and means for communicatively coupling
  • eNB evolved NodeB
  • UE user equipment
  • Example 33 includes the subject matter of Example 32, including or omitting any elements as optional, further comprising: means for performing a localized resource scheduling of one or more scheduling resources through one or more lower protocol layers that are lower than the MAC layer, independent of or in coordination with the central MAC layer component based on the partition configuration.
  • Example 34 includes the subject matter of any one of Examples 32-33, including or omitting any elements as optional, further comprising: means for retrieving at the local MAC layer component scheduling related information including user equipment (UE) data and the partition configuration associated with one or more higher protocol layers from the central MAC layer component; and means for controlling a centralized scheduling of the plurality of local MAC layer components according to different physical (PHY) protocol layer configurations among at least one of: one or more cell networks.
  • UE user equipment
  • PHY physical
  • Example 35 includes the subject matter of any one of Examples 32-34, including or omitting any elements as optional, further comprising: means for receiving or obtaining one or more physical resources related to different PHY protocol layer configurations; and means for reporting, periodically or as requested by the central MAC layer component, the one or more physical resources to the central MAC layer component.
  • Example 36 includes the subject matter of any one of Examples 32-35, including or omitting any elements as optional, further comprising: means for
  • Example 37 includes the subject matter of any one of Examples 32-36, including or omitting any elements as optional, wherein the partition configuration designates localized resource allocations among the plurality of local MAC layer components to independently configure the plurality of local MAC layer components to support one or more different PHY protocol layer configurations corresponding to different network devices for scheduling operations.
  • Example 38 includes the subject matter of any one of Examples 32-37, including or omitting any elements as optional, further comprising: means for modifying the partition configuration of the local MAC layer component of the plurality of local MAC layer components based on a change in a change of a PHY layer configuration of a network device, a network or a traffic flow.
  • Example 39 is an apparatus employed within an evolved NodeB (eNB) or a user equipment (UE) of a multi-radio heterogeneous network including different radio access technologies (RATs), comprising: one or more processors configured to: provide a partition configuration to a local MAC layer component of a plurality of local MAC layer components configured to operate as distribution units (DUs) of a central medium access control (MAC) layer component configured to operate as a central unit (CU) of a MAC layer; and communicatively couple through a MAC layer interface communications between the central MAC layer component and the plurality of local MAC layer components in a hierarchal structure to execute operations of the MAC layer; and a communication interface or a radio frequency interface configured to process or generate communications related to the MAC layer.
  • eNB evolved NodeB
  • UE user equipment
  • UE user equipment
  • Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a storage media or a computer readable storage device can be any available media that can be accessed by a general purpose or special purpose computer.
  • such computer-readable media can comprise RAM, ROM, EEPROM, CD- ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or other tangible and/or non-transitory medium, that can be used to carry or store desired information or executable instructions.
  • any connection is properly termed a computer-readable medium.
  • a computer-readable medium includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • a general-purpose processor can be a microprocessor, but, in the alternative, processor can be any conventional processor, controller, microcontroller, or state machine.
  • a processor can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. Additionally, at least one processor can comprise one or more modules operable to perform one or more of the s and/or actions described herein.
  • modules e.g., procedures, functions, and so on
  • Software codes can be stored in memory units and executed by processors.
  • Memory unit can be implemented within processor or external to processor, in which case memory unit can be communicatively coupled to processor through various means as is known in the art.
  • at least one processor can include one or more modules operable to perform functions described herein.
  • a CDMA system can implement a radio technology such as Universal Terrestrial Radio Access (UTRA), CDMA1800, etc.
  • UTRA includes Wideband-CDMA (W-CDMA) and other variants of CDMA.
  • W-CDMA Wideband-CDMA
  • CDMA1800 covers IS-1800, IS-95 and IS-856 standards.
  • a TDMA system can implement a radio technology such as Global System for Mobile
  • GSM Global System for Mobile Communications
  • An OFDMA system can implement a radio technology such as Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.1 1 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.18, Flash-OFDML , etc.
  • E-UTRA Evolved UTRA
  • UMB Ultra Mobile Broadband
  • Wi-Fi Wi-Fi
  • WiMAX WiMAX
  • IEEE 802.18, Flash-OFDML etc.
  • UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS).
  • 3GPP Long Term Evolution (LTE) is a release of UMTS that uses E-UTRA, which employs OFDMA on downlink and SC-FDMA on uplink.
  • UTRA, E-UTRA, UMTS, LTE and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP).
  • CDMA1 800 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2).
  • 3GPP2 3rd Generation Partnership Project 2
  • such wireless communication systems can additionally include peer-to-peer (e.g., mobile-to-mobile) ad hoc network systems often using unpaired unlicensed spectrums, 802. xx wireless LAN, BLUETOOTH and any other short- or long- range, wireless communication techniques.
  • SC-FDMA Single carrier frequency division multiple access
  • SC-FDMA has similar performance and essentially a similar overall complexity as those of OFDMA system.
  • SC-FDMA signal has lower peak-to-average power ratio (PAPR) because of its inherent single carrier structure.
  • PAPR peak-to-average power ratio
  • SC-FDMA can be utilized in uplink communications where lower PAPR can benefit a mobile terminal in terms of transmit power efficiency.
  • various aspects or features described herein can be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques.
  • the term "article of manufacture” as used herein is intended to encompass a computer program accessible from any computer-readable device, carrier, or media.
  • computer-readable media can include but are not limited to magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips, etc.), optical disks (e.g., compact disk (CD), digital versatile disk (DVD), etc.), smart cards, and flash memory devices (e.g., EPROM, card, stick, key drive, etc.).
  • various storage media described herein can represent one or more devices and/or other machine-readable media for storing information.
  • the term "machine-readable medium" can include, without being limited to, wireless channels and various other media capable of storing, containing, and/or carrying instruction(s) and/or data.
  • a computer program product can include a computer readable medium having one or more instructions or codes operable to cause a computer to perform functions described herein.
  • Communications media embody computer-readable instructions, data structures, program modules or other structured or unstructured data in a data signal such as a modulated data signal, e.g., a carrier wave or other transport mechanism, and includes any information delivery or transport media.
  • modulated data signal or signals refers to a signal that has one or more of its characteristics set or changed in such a manner as to encode information in one or more signals.
  • communication media include wired media, such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.
  • a software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
  • An exemplary storage medium can be coupled to processor, such that processor can read information from, and write information to, storage medium.
  • storage medium can be integral to processor.
  • processor and storage medium can reside in an ASIC.
  • ASIC can reside in a user terminal.
  • processor and storage medium can reside as discrete components in a user terminal.
  • the s and/or actions of a method or algorithm can reside as one or any combination or set of codes and/or instructions on a machine-readable medium and/or computer readable medium, which can be incorporated into a computer program product.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un dispositif de réseau (par exemple, un nœud B évolué (eNB), un équipement utilisateur (UE) ou un autre dispositif) pouvant comprendre un composant de couche de commande d'accès au support central (MAC) configuré en tant qu'unité centrale (CU) d'une couche MAC dans une pile de protocoles d'évolution à long terme (LTE) qui interagit de manière communicative avec une ou plusieurs couches de protocole supérieures de la pile. Des composants de couche de commande d'accès au support local, configurés sous forme d'unités réparties (DUs) situées à l'intérieur de la couche MAC, peuvent être couplés de manière communicative au composant de couche de commande d'accès au support central (MAC) et interagir avec des couches de protocole inférieures de la pile. Une interface de couche MAC couple de manière communicative le composant de couche de commande d'accès au support central aux composants de couche de commande d'accès au support locale afin de distribuer la fonctionnalité à partir de l'unité centrale de la couche MAC parmi les composants de couche de commande d'accès au support local et exécuter les fonctionnalités principales de la couche MAC conjointement.
PCT/US2017/020722 2016-08-11 2017-03-03 Structure de commande de commande d'accès au support (mac) hiérarchique dans une division fronthauling intra-mac WO2018031069A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201662373753P 2016-08-11 2016-08-11
US62/373,753 2016-08-11

Publications (1)

Publication Number Publication Date
WO2018031069A1 true WO2018031069A1 (fr) 2018-02-15

Family

ID=58361104

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2017/020722 WO2018031069A1 (fr) 2016-08-11 2017-03-03 Structure de commande de commande d'accès au support (mac) hiérarchique dans une division fronthauling intra-mac

Country Status (1)

Country Link
WO (1) WO2018031069A1 (fr)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111182486A (zh) * 2019-12-17 2020-05-19 三维通信股份有限公司 移动终端定位系统和方法
CN111526581A (zh) * 2019-02-03 2020-08-11 华为技术有限公司 一种用户定位的方法、网元、系统及存储介质
US10980043B2 (en) * 2016-11-02 2021-04-13 Zte Corporation Data transmission method and device, and base station
WO2022076996A1 (fr) 2020-10-05 2022-04-14 Cohere Technologies, Inc. Ordonnancement et retransmission dans des unités centrales et des unités distribuées
US20220141670A1 (en) * 2015-09-06 2022-05-05 Mariana Goldhamer Virtualized base station and its controller
US20220361041A1 (en) * 2020-05-28 2022-11-10 At&T Intellectual Property I, L.P. Pooling of baseband units for 5g or other next generation networks

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2996422A1 (fr) * 2014-09-10 2016-03-16 Cisco Technology, Inc. Système et procédé pour découpler le lte mac planificiation de procédures a sous-trame vitesse

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2996422A1 (fr) * 2014-09-10 2016-03-16 Cisco Technology, Inc. Système et procédé pour découpler le lte mac planificiation de procédures a sous-trame vitesse

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
INTEL CORPORATION: "RAN functional split: intra MAC split description and benefits", vol. RAN WG3, no. Sophia Antipolis, France; 20161010 - 20161014, 6 October 2016 (2016-10-06), XP051151889, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN3/Docs/> [retrieved on 20161006] *
INTERDIGITAL COMMUNICATIONS: "Architecture-related Aspects for Interworking between NR and LTE", vol. RAN WG2, no. Dubrovnik, Croatia; 20160411 - 20160415, 2 April 2016 (2016-04-02), XP051082554, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG2_RL2/TSGR2_93bis/Docs/> [retrieved on 20160402] *

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220141670A1 (en) * 2015-09-06 2022-05-05 Mariana Goldhamer Virtualized base station and its controller
US12069482B2 (en) * 2015-09-06 2024-08-20 Mariana Goldhamer Virtualized base station and its controller
US10980043B2 (en) * 2016-11-02 2021-04-13 Zte Corporation Data transmission method and device, and base station
CN111526581A (zh) * 2019-02-03 2020-08-11 华为技术有限公司 一种用户定位的方法、网元、系统及存储介质
CN111182486A (zh) * 2019-12-17 2020-05-19 三维通信股份有限公司 移动终端定位系统和方法
WO2021121284A1 (fr) * 2019-12-17 2021-06-24 三维通信股份有限公司 Système et procédé de positionnement de terminal mobile
US20220361041A1 (en) * 2020-05-28 2022-11-10 At&T Intellectual Property I, L.P. Pooling of baseband units for 5g or other next generation networks
WO2022076996A1 (fr) 2020-10-05 2022-04-14 Cohere Technologies, Inc. Ordonnancement et retransmission dans des unités centrales et des unités distribuées
EP4226673A4 (fr) * 2020-10-05 2024-11-13 Cohere Technologies, Inc. Ordonnancement et retransmission dans des unités centrales et des unités distribuées

Similar Documents

Publication Publication Date Title
US11031982B2 (en) Filter coefficient configuration in New Radio systems
US11291080B2 (en) Link quality reporting enhancements for new radio
US10257753B2 (en) WLAN mobility for LTE/WLAN aggregation
US20180206282A1 (en) Bearer splitting
US10841910B2 (en) Physical downlink control channel for fifth-generation networks
WO2018031069A1 (fr) Structure de commande de commande d&#39;accès au support (mac) hiérarchique dans une division fronthauling intra-mac
US20240364487A1 (en) Physical Resource Block Indexing for Coexistence of Narrow Band, Carrier Aggregation, and Wide Band User Equipment in New Radio
EP3414933B1 (fr) Signalisation pour intervalle de mesure amélioré pour réseau synchrone
EP3923607A1 (fr) Fourniture de services pour dispositifs d&#39;internet des objets dans des réseaux cellulaires
US10812169B2 (en) User equipment measurements for new radio
EP3603150B1 (fr) Dispositifs pour internet de choses, iot, communication, iot, sur un spectre sans licence
WO2018106911A2 (fr) Équipement d&#39;utilisateur multefire pour une transmission de liaison montante sans octroi
WO2017196386A1 (fr) Mécanismes pour éviter la qualité explicite de signalisation de service sur une interface radio
EP3437254B1 (fr) Dispositif et procédé pour une gestion de cycle de vie de nfv à l&#39;aide de fonctions de gestion de configuration
WO2017135986A1 (fr) Transmission de support multiple dans la liaison montante pour une intégration d&#39;évolution à long terme et wifi
WO2017171898A1 (fr) Équipement utilisateur (ue), nœud b évolué (enb) et procédés de suspension et de reprise de liaisons de communication d&#39;un support radio
WO2024097420A1 (fr) Procédés et agencements pour indication de port d&#39;antenne
WO2024063979A1 (fr) Association d&#39;état tci unifié pour une communication basée sur un point de réception multi-transmission
WO2017197248A1 (fr) Mappage de canal de transport sur canal physique à intervalles de temps de transmission extensibles
EP3437381A1 (fr) Échelonnement d&#39;un trafic sans surveillance dans un système d&#39;évolution à long terme (lte) après une interdiction

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17712300

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17712300

Country of ref document: EP

Kind code of ref document: A1

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载