System and method for HARQ in cloud RAN with large front haul latency

A system is enabled to perform error checking and other HARQ processes at a remote radio unit device in cloud RAN systems that have a large front haul latency. The remote radio unit device performs error checking on transmissions received from a mobile device and sends an acknowledgement (ACK) or negative acknowledgement (NACK) to the mobile device based on whether errors are found.

TECHNICAL FIELD

The subject disclosure relates to a system for enhanced hybrid automatic repeat request to decrease latency in systems with large front haul latency in a mobile communications environment.

BACKGROUND

Hybrid automatic repeat request (HARQ) is a system of error checking where transmissions from mobile devices are checked for errors. If the transmission contains an error, a retransmission request is sent back to the mobile device to resend the transmission. In synchronous uplink systems, there are standards for scheduling so that a certain amount of time is allotted to send the retransmission requirement. The system that performs the HARQ has traditionally been the baseband unit of an eNodeB in an LTE system.

Due to increasing demand, small cell deployments are being developed with cloud radio access network (RAN) systems, where a portion of a base station device (e.g., the baseband unit device of the eNodeB) may support multiple remote radio unit devices. The remote radio unit devices, which are primarily used for transmission and reception of radio signals from mobile devices, may be located at some distance from the baseband units, physical or virtual, and so the increased latency due to the distance between the devices may negatively affect HARQ performance.

DETAILED DESCRIPTION

A system is provided to perform error checking and other HARQ processes at a remote radio unit device in cloud RAN systems that have a large front haul latency. The remote radio unit device performs error checking on transmissions received from a mobile device and sends an acknowledgement (ACK) or negative acknowledgement (NACK) to the mobile device based on whether errors are found. In another embodiment, the remote radio unit device can send an interim ACK to the mobile device, and then send a retransmission request if the baseband unit device determines that there is an error in transmission. Both of these techniques allow for improved uplink throughput even in systems where there may be a high latency fronthaul connection.

In an embodiment, if a remote radio unit device is located at a great enough distance from a baseband unit device that the latency in the connection interferes with scheduling requirements for HARQ processing, a remote radio unit device can be provided that performs error checking at the remote radio unit device, without waiting to hear back from the baseband unit device whether transmissions contain errors. The remote radio unit device can send an ACK or NACK to the mobile device directly. By enabling the remote radio unit device to perform error checking, the ACK and NACK can be sent within the three millisecond time period that is required for synchronous uplink retransmission.

In another embodiment, the remote radio unit device can send an interim or provisional acknowledgement to the mobile device upon reception of a transmission. The interim acknowledgement can be sent to the mobile device within the three millisecond time frame provided by the LTE HARQ standards, even if the remote radio unit device has not already determined whether the transmission contains an error. If the transmission does not contain an error, an additional acknowledgement may not need to be sent, but if the transmission does contain an error, a retransmission request can be sent after the interim acknowledgement was sent. In an embodiment, the interim acknowledgement can be sent if the remote radio unit device is not able to perform the error checking within time, or if a latency between the baseband unit device and the remote radio unit device is above a predetermined threshold.

For these considerations as well as other considerations, in one or more embodiments, a remote radio unit device can comprise a processor and a memory that stores executable instructions that, when executed by the processor, facilitate performance of operations. The operations can include receiving a transmission from a mobile device and determining whether the transmission comprises an error. The operations can also include, in response to the determining indicating that the transmission does not comprise the error, sending an acknowledgement to the mobile device and in response to the determining indicating that the transmission does comprise the error, sending a retransmission request to the mobile device.

In another embodiment, a method can include receiving, by a remote radio unit device comprising a processor, a transmission from a mobile device. The method can also include performing, by the remote radio unit device, error detection on the transmission. The method can also include, in response to not detecting an error, sending, by the remote radio unit device, an acknowledgement to the mobile device, or in response to detecting the error, sending, by the remote radio unit device, a retransmission request to the mobile device.

In yet another embodiment, a computer-readable storage device storing executable instructions that, in response to execution, cause a system comprising a processor to perform operations. The operations can include receiving a transmission from a mobile device. The operations can also include determining whether the transmission comprises an error, wherein the determining is performed at a remote radio unit. The operations can further include sending an acknowledgement in response to the determining indicating that the transmission does not comprise the error or sending a retransmission request in response to the determining indicating that the transmission does comprise the error.

Turning now toFIG. 1, illustrated is an example, non-limiting embodiment of a block diagram100showing a system showing multiple remote radio unit devices104,106, and108being supported by a baseband unit device102in accordance with various aspects described herein. A fronthaul link110connects the remote radio units104,106, and108, and the latency of the fronthaul link110can vary depending on how far away the remote radio unit devices are from the baseband unit device102.

The uplink connection from a mobile device to the eNodeB, which comprises both the remote radio unit devices104,106, and108and the baseband unit device102is synchronous according to current 3GPP specifications. This reduces the interaction between the mobile device and the eNodeB, and simplifies the operation for mobile device as well. However, to meet the requirement of synchronous uplink retransmission, the eNodeB may need to complete the processing of uplink channel data within a 3 ms time period so that if a retransmission needs to be sent, the eNodeB can alert the mobile device to resend the transmission by the eighth transmission time interval, or 8 ms after the first transmission was sent. If this time requirement is not met, the mobile device cannot resend the data until the sixteenth transmission time interval, or 16 ms after the first transmission is sent, which can slow down the uplink throughput bandwidth.

If there is a large distance between remote radio units104,106, and108and the baseband unit device102, or if baseband unit device102is provided as a cloud service, there can be a large fronthaul delay on connection110such that the 3 ms processing time may not be realized for HARQ error detection at the baseband unit device102. In order to overcome this difficulty, error detection can be implemented at the remote radio unit devices104,106, and108so that the latency caused due to connection110is no longer relevant. In addition, the remote radio unit devices can issue interim acknowledgements so that new data is transmitted every 8 ms, but if an error is detected, then a retransmission request can be sent by the remote radio unit device to the mobile device. This retransmission request can be sent at a later time, and the mobile device can retransmit data that was stored in a buffer on the mobile device.

Turning now toFIG. 2, illustrated is an example, non-limiting embodiment of a block diagram200showing a system for error checking in a cloud RAN in accordance with various aspects described herein.

In an embodiment, if an eNodeB is split with a local remote radio unit device204and a cloud provisioned baseband unit device202such that a latency in the connection interferes with scheduling requirements for HARQ processing, the remote radio unit device can performs error checking at the remote radio unit device204, without waiting to hear back from the baseband unit device202whether transmissions contain errors. The remote radio unit device can send an ACK or NACK to the mobile device206directly. By enabling the remote radio unit device204to perform error checking, the ACK and NACK can be sent within the three millisecond time period that is required for synchronous uplink retransmission.

In an embodiment, the mobile device206can send transmissions that are encoded with an error detecting code such as cyclic redundancy check. The remote radio unit device204can check for errors based on the error detecting code, and if there are errors, request a retransmission. In other embodiments, the mobile device206can send transmissions that are encoded with a forward error correction code and an error detecting code (e.g., Reed-Solomon code). The forward error correction code can be used by the remote radio unit device204to decode the data and/or correct errors in the transmission, and retransmission is only requested in case if the errors in the transmission are uncorrectable.

In a typical eNodeB, the general operational split between the remote radio unit and the baseband unit is that the remote radio unit performs layer1processing, while the baseband unit performs layer2processing and above. In an embodiment of the subject disclosure though, the remote radio unit device204can perform some layer2processing on transmissions received from mobile device204.

In an embodiment, remote radio unit device204can include part of the scheduler of the eNodeB handles retransmission of data, while the part of the scheduler that resides in the baseband unit device202handles new transmissions. Since the HARQ retransmission may need to follow time constraints imposed by the synchronous standards, the retransmission can be handled at the remote radio unit device204without the latency imposed by the connection to the baseband unit device202in the cloud RAN. In an embodiment, the remote radio unit device204can receive scheduling information associated with the new transmission from the baseband unit device202. The scheduling information can provide a schedule for requesting new transmissions from the mobile device206and can include intervals, or breaks between the new transmissions requests to allow for the retransmission requests determined, and generated by remote radio unit device204. The number of intervals, interval rate, or the length of the intervals can be adjusted based on the expected or realized error rate of transmissions received from the mobile device206. For instance, if environmental conditions, or loading, or interference, are such that the error rate is measured or expected to be higher, the baseband unit device202can send scheduling information to the remote radio unit device204that has an increased number of intervals to account for the higher number of retransmission requests.

In an embodiment, an interim acknowledgement can be sent from the remote radio unit device204to the mobile device206regardless of whether an error has been detected or not. If the fronthaul delay in overall processing at both the remote radio unit device204and the baseband unit device202is greater than 3 ms, then the interim acknowledgment can be sent on a physical HARQ indicator channel (PHICH). The remote radio unit device204can either ask for a retransmission of data or a new data transmission using a toggled new data indicator bit on a Physical Downlink Control Channel (PDCCH) after the data received in the transmission on the Physical Uplink Shared Channel (PUSCH) is received.

In an embodiment, the remote radio unit device204can initiate checking for errors, and if the processing is finished within 3 ms, the remote radio unit device204can send the ACK/NACK on PHICH. If the processing, either at the baseband unit device202or at remote radio unit device204, has not been performed within the time frame, the remote radio unit device204can send a temporary or interim ACK on PHICH. The interim acknowledgement prevents unnecessary retransmissions, since the mobile device206will retransmit unless an ACK is received. When the ACK is received, interim or not, the mobile device206can buffer the transmission for a short time, and if a NACK or a retransmission request related to the first transmission is received, the mobile device206can retransmit the buffered data.

In the case when a NACK is supposed to be sent, the dummy ACK halts the process of non-adaptive retransmission but it gives more control for later retransmission, requested on PDCCH with possibly different resource blocks and MCS, while using less number of retransmissions.

In another embodiment, the remote radio unit device204can check for HARQ transmission errors in transmissions from the mobile device206at the remote radio unit device204. If data is received without errors, then an ACK can be sent on PHICH to the mobile device206, and if a retransmission is required by the baseband unit device202, the remote radio unit device204can send a indicator to 0 on downlink control information (DCI format 0) on PDCCH. If an error is detected however at the remote radio unit204, then the remote radio unit device204can itself send a NACK on PHICH.

Turning now toFIG. 3, illustrated is an example, non-limiting embodiment of a block diagram300showing a remote radio unit device302in accordance with various aspects described herein.

In an embodiment, if an eNodeB is split with a local remote radio unit device302and a cloud provisioned baseband unit device312such that a latency in the connection interferes with scheduling requirements for HARQ processing, the remote radio unit device302can performs error checking at the remote radio unit device302, without waiting to hear back from the baseband unit device312whether a transmission from a mobile device314contains an error. The remote radio unit device302can send an ACK or NACK to the mobile device314directly. By enabling the remote radio unit device302to perform error checking, the ACK and NACK can be sent within the three millisecond time period that is required for synchronous uplink retransmission.

In an embodiment, an RF component310can receive a transmission from mobile device314via a radio frequency (RF) connection. An error checking component304can begin to check the transmission for errors. The error checking component304can check for errors based on an error detecting code that was encoded with the data in the transmission, and if there are errors, request a retransmission. In other embodiments, the error checking component304can try to correct the errors using a forward error correcting code that was encoded with the data and request a retransmission if the data is uncorrectable.

In an embodiment, a fronthaul component308can transmit the received data to the baseband unit device312via a fronthaul link. The baseband unit device312can also perform HARQ processing, and initiate a retransmission or new data transmission via the fronthaul component308. A scheduler component306can monitor the length of time between receiving the transmission at the RF component310the error checking processing by the error checking component304. If the scheduler component306determines that the 3 ms time period for sending an ACK/NACK will not be met, the scheduler component306can initiate sending of an ACK to the mobile device314via the RF component310. The ACK can be an interim ACK, and if the error checking component304determines that there is an error, a retransmission request can be sent to the mobile device314.

In an embodiment, the error checking component304can determine whether or not the transmission contains an error within 3 ms, and an ACK can be sent if no error is found, or an NACK can be sent if an error is found.

In an embodiment, the scheduler component306can determine the latency between the baseband unit device312and the remote radio unit device302. If the latency is small/low enough that the baseband unit device312can perform HARQ processing on data within the time constraints imposed by synchronous uplink standards, then the remote radio unit device302will just perform layer1processing on the transmissions received from mobile device314and forward the transmissions to the baseband unit device312for all layer2and above processing. If scheduler component306determines that the latency is high enough that the HARQ processing at the baseband unit device312will not meet the time requirements, then the scheduler component306can initiate error checking at the remote radio unit device302by error checking component304.

Turning now toFIG. 4, illustrated is an example, non-limiting embodiment of a block diagram showing a timeline400for error checking in accordance with various aspects described herein. The timeline400shown inFIG. 4illustrates an embodiment where the remote radio unit performs error checking and sends a NACK indicating that an error has been found.

In an embodiment, each of the time period divisions in the timeline400indicate a transmission time interval of 1 ms. There are 8 TTIs, or 8 ms between when the UE, or the mobile device, can send packets of data to the remote radio unit. At402, the eNodeB, or more specifically, the RRU, sends an uplink grant to the mobile device where it is received shortly thereafter. At404, the UE transmits the data on PUSCH and it is received by the RRU shortly thereafter. At406, after the PUSCH data is received, the remote radio unit can begin processing the transmission to check for errors. At410, after the RRU determines that there is an error, the NACK can be sent to the mobile device where it is received at412which gives time for the mobile device to resend the transmission at414.

If the RRU did not check for errors, the time period408denotes the length of time for processing by the BBU, which may not give enough time for the mobile device to resend the data414. If the mobile device misses the414time period, it may have to wait another 8 TTIs to resend the data, thus causing a 16 ms delay in case of transmission errors, versus an 8 ms delay if the RRU is performing error checking.

Turning now toFIG. 5, illustrated is an example, non-limiting embodiment of a block diagram showing a timeline500for error checking in accordance with various aspects described herein. The timeline500shown inFIG. 5illustrates an embodiment where the remote radio unit sends an interim acknowledgement.

In an embodiment, each of the time period divisions in the timeline500indicate a transmission time interval of 1 ms. There are 8 TTIs, or 8 ms between when the UE, or the mobile device, can send packets of data to the remote radio unit. At502, the eNodeB, or more specifically, the RRU, sends an uplink grant to the mobile device where it is received shortly thereafter. At504, the UE transmits the data on PUSCH and it is received by the RRU shortly thereafter. At508, after the PUSCH data is received, the remote radio unit sends a dummy, or interim acknowledgement, even though the HARQ processing by the eNodeB is still being performed as shown at506. At512, after the eNodeB processing finished, the RRU can send a retransmission request on PDCCH and the mobile device can resend the transmission at514.

FIGS. 6-8illustrates a process in connection with the aforementioned systems. The processes inFIGS. 6-8can be implemented for example by systems100-300as illustrated inFIGS. 1-3respectively. While for purposes of simplicity of explanation, the methods are shown and described as a series of blocks, it is to be understood and appreciated that the claimed subject matter is not limited by the order of the blocks, as some blocks may occur in different orders and/or concurrently with other blocks from what is depicted and described herein. Moreover, not all illustrated blocks may be required to implement the methods described hereinafter.

FIG. 6illustrates a flow diagram of an example, non-limiting embodiment of a method for error checking at a remote radio unit device as described herein. The method600can begin at602where the method includes receiving, by a remote radio unit device comprising a processor, a transmission from a mobile device. At604, the method includes performing, by the remote radio unit device, error detection on the transmission. An error checking component can begin to check the transmission for errors at the remote radio unit device. The error checking component can check for errors based on an error detecting code that was encoded with the data in the transmission, and if there are errors, request a retransmission. In other embodiments, the error checking component can try to correct the errors using a forward error correcting code that was encoded with the data and request a retransmission if the data is uncorrectable.

At606, the method includes in response to not detecting an error, sending, by the remote radio unit device, an acknowledgement to the mobile device, or in response to detecting the error, sending, by the remote radio unit device, a retransmission request to the mobile device.

FIG. 7illustrates a flow diagram of an example, non-limiting embodiment of a method700for error checking at a remote radio unit device as described herein. The method700can begin at702where the method includes sending, by the remote radio unit device, an interim acknowledgement to the mobile device. At704, the method can include determining, by the remote radio unit device, that the transmission comprises an error based on receiving an indication of the error from a baseband unit device. At706, the method can include sending, by the remote radio unit device, the retransmission request after sending the interim acknowledgement.

FIG. 8illustrates a flow diagram of an example, non-limiting embodiment of a method800for error checking at a remote radio unit device as described herein.

At802the method can begin with the remote radio unit device receiving a transmission from a mobile device, and at804the remote radio unit device can initiate error checking. An error checking component on the remote radio unit device can begin to check the transmission for errors at the remote radio unit device. The error checking component can check for errors based on an error detecting code that was encoded with the data in the transmission, and if there are errors, request a retransmission. In other embodiments, the error checking component can try to correct the errors using a forward error correcting code that was encoded with the data and request a retransmission if the data is uncorrectable.

At806, a scheduling function of the remote radio unit device can determine whether the error checking is going to take longer than 3 milliseconds. The length can be based on the type and/or complexity of the error checking. The duration of the error checking can also be based on a fronthaul latency between the remote radio unit device and the baseband unit device.

If the scheduler determines that the error checking will take less than 3 milliseconds, then the error checking is completed at the RRU at808and then it is determined whether there is an error at810. If there is an error, a NACK is transmitted to the mobile device at814, and a retransmission is then received a short time later at816. If there is no error, then an ACK is sent at812.

If the scheduler determines that the error checking will take longer than 3 seconds, then an interim acknowledgement can be sent at818. Once the error checking is completed it is determined whether an error is present at820. If there is an error, than a NACK can be sent, but if there is no error, than nothing needs to be done, and a new transmission can be received at822.

Referring now toFIG. 9, there is illustrated a block diagram of a computing environment in accordance with various aspects described herein. For example, in some embodiments, the computer can be or be included within the remote radio unit device104,106,108,204, or302or within the baseband unit device102,202, or312.

Computing devices typically include a variety of media, which can include computer-readable storage media and/or communications media, which two terms are used herein differently from one another as follows. Computer-readable storage media can be any available storage media that can be accessed by the computer and includes both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer-readable storage media can be implemented in connection with any method or technology for storage of information such as computer-readable instructions, program modules, structured data or unstructured data.

With reference again toFIG. 9, the example environment900for implementing various embodiments of the aspects described herein includes a computer902, the computer902including a processing unit904, a system memory906and a system bus908. The system bus908couples system components including, but not limited to, the system memory906to the processing unit904. The processing unit904can be any of various commercially available processors. Dual microprocessors and other multi-processor architectures can also be employed as the processing unit904.

The system bus908can be any of several types of bus structure that can further interconnect to a memory bus (with or without a memory controller), a peripheral bus, and a local bus using any of a variety of commercially available bus architectures. The system memory906includes ROM910and RAM912. A basic input/output system (BIOS) can be stored in a non-volatile memory such as ROM, erasable programmable read only memory (EPROM), EEPROM, which BIOS contains the basic routines that help to transfer information between elements within the computer902, such as during startup. The RAM912can also include a high-speed RAM such as static RAM for caching data.

The computer902further includes an internal hard disk drive (HDD)914(e.g., EIDE, SATA), which internal hard disk drive914can also be configured for external use in a suitable chassis (not shown), a magnetic floppy disk drive (FDD)916, (e.g., to read from or write to a removable diskette918) and an optical disk drive920, (e.g., reading a CD-ROM disk922or, to read from or write to other high capacity optical media such as the DVD). The hard disk drive914, magnetic disk drive916and optical disk drive920can be connected to the system bus908by a hard disk drive interface924, a magnetic disk drive interface926and an optical drive interface928, respectively. The interface924for external drive implementations includes at least one or both of Universal Serial Bus (USB) and Institute of Electrical and Electronics Engineers (IEEE)994interface technologies. Other external drive connection technologies are within contemplation of the embodiments described herein.

A number of program modules can be stored in the drives and RAM912, including an operating system930, one or more application programs932, other program modules934and program data936. All or portions of the operating system, applications, modules, and/or data can also be cached in the RAM912. The systems and methods described herein can be implemented utilizing various commercially available operating systems or combinations of operating systems.

A user can enter commands and information into the computer902through one or more wired/wireless input devices, e.g., a keyboard938and a pointing device, such as a mouse940. Other input devices (not shown) can include a microphone, an infrared (IR) remote control, a joystick, a game pad, a stylus pen, touch screen or the like. These and other input devices are often connected to the processing unit904through an input device interface942that can be coupled to the system bus908, but can be connected by other interfaces, such as a parallel port, an IEEE 1394 serial port, a game port, a universal serial bus (USB) port, an IR interface, etc.

A monitor944or other type of display device can be also connected to the system bus908via an interface, such as a video adapter946. In addition to the monitor944, a computer typically includes other peripheral output devices (not shown), such as speakers, printers, etc.

The computer902can operate in a networked environment using logical connections via wired and/or wireless communications to one or more remote computers, such as a remote computer(s)948. The remote computer(s)948can be a workstation, a server computer, a router, a personal computer, portable computer, microprocessor-based entertainment appliance, a peer device or other common network node, and typically includes many or all of the elements described relative to the computer902, although, for purposes of brevity, only a memory/storage device950is illustrated. The logical connections depicted include wired/wireless connectivity to a local area network (LAN)952and/or larger networks, e.g., a wide area network (WAN)954. Such LAN and WAN networking environments are commonplace in offices and companies, and facilitate enterprise-wide computer networks, such as intranets, all of which can connect to a global communications network, e.g., the Internet.

When used in a LAN networking environment, the computer902can be connected to the local network952through a wired and/or wireless communication network interface or adapter956. The adapter956can facilitate wired or wireless communication to the LAN952, which can also include a wireless AP disposed thereon for communicating with the wireless adapter956.

When used in a WAN networking environment, the computer902can include a modem958or can be connected to a communications server on the WAN954or has other means for establishing communications over the WAN954, such as by way of the Internet. The modem958, which can be internal or external and a wired or wireless device, can be connected to the system bus908via the input device interface942. In a networked environment, program modules depicted relative to the computer902or portions thereof, can be stored in the remote memory/storage device950. It will be appreciated that the network connections shown are example and other means of establishing a communications link between the computers can be used.

FIG. 10presents an example embodiment1000of a mobile network platform1010that can implement and exploit one or more aspects of the disclosed subject matter described herein. Generally, wireless network platform1010can include components, e.g., nodes, gateways, interfaces, servers, or disparate platforms, that facilitate both packet-switched (PS) (e.g., internet protocol (IP), frame relay, asynchronous transfer mode (ATM)) and circuit-switched (CS) traffic (e.g., voice and data), as well as control generation for networked wireless telecommunication. As a non-limiting example, wireless network platform1010can be included in telecommunications carrier networks, and can be considered carrier-side components as discussed elsewhere herein. Mobile network platform1010includes CS gateway node(s)1012which can interface CS traffic received from legacy networks like telephony network(s)1040(e.g., public switched telephone network (PSTN), or public land mobile network (PLMN)) or a signaling system #7(SS7) network1070. Circuit switched gateway node(s)1012can authorize and authenticate traffic (e.g., voice) arising from such networks. Additionally, CS gateway node(s)1012can access mobility, or roaming, data generated through SS7network1070; for instance, mobility data stored in a visited location register (VLR), which can reside in memory1030. Moreover, CS gateway node(s)1012interfaces CS-based traffic and signaling and PS gateway node(s)1018. As an example, in a 3GPP UMTS network, CS gateway node(s)1012can be realized at least in part in gateway GPRS support node(s) (GGSN). It should be appreciated that functionality and specific operation of CS gateway node(s)1012, PS gateway node(s)1018, and serving node(s)1016, is provided and dictated by radio technology(ies) utilized by mobile network platform1010for telecommunication.

In addition to receiving and processing CS-switched traffic and signaling, PS gateway node(s)1018can authorize and authenticate PS-based data sessions with served mobile devices. Data sessions can include traffic, or content(s), exchanged with networks external to the wireless network platform1010, like wide area network(s) (WANs)1050, enterprise network(s)1070, and service network(s)1080, which can be embodied in local area network(s) (LANs), can also be interfaced with mobile network platform1010through PS gateway node(s)1018. It is to be noted that WANs1050and enterprise network(s)1060can embody, at least in part, a service network(s) like IP multimedia subsystem (IMS). Based on radio technology layer(s) available in technology resource(s)1017, packet-switched gateway node(s)1018can generate packet data protocol contexts when a data session is established; other data structures that facilitate routing of packetized data also can be generated. To that end, in an aspect, PS gateway node(s)1018can include a tunnel interface (e.g., tunnel termination gateway (TTG) in 3GPP UMTS network(s) (not shown)) which can facilitate packetized communication with disparate wireless network(s), such as Wi-Fi networks.

In embodiment1000, wireless network platform1010also includes serving node(s)1016that, based upon available radio technology layer(s) within technology resource(s)1017, convey the various packetized flows of data streams received through PS gateway node(s)1018. It is to be noted that for technology resource(s)1017that rely primarily on CS communication, server node(s) can deliver traffic without reliance on PS gateway node(s)1018; for example, server node(s) can embody at least in part a mobile switching center. As an example, in a 3GPP UMTS network, serving node(s)1016can be embodied in serving GPRS support node(s) (SGSN).

For radio technologies that exploit packetized communication, server(s)1014in wireless network platform1010can execute numerous applications that can generate multiple disparate packetized data streams or flows, and manage (e.g., schedule, queue, format . . . ) such flows. Such application(s) can include add-on features to standard services (for example, provisioning, billing, customer support . . . ) provided by wireless network platform1010. Data streams (e.g., content(s) that are part of a voice call or data session) can be conveyed to PS gateway node(s)1018for authorization/authentication and initiation of a data session, and to serving node(s)1016for communication thereafter. In addition to application server, server(s)1014can include utility server(s), a utility server can include a provisioning server, an operations and maintenance server, a security server that can implement at least in part a certificate authority and firewalls as well as other security mechanisms, and the like. In an aspect, security server(s) secure communication served through wireless network platform1010to ensure network's operation and data integrity in addition to authorization and authentication procedures that CS gateway node(s)1012and PS gateway node(s)1018can enact. Moreover, provisioning server(s) can provision services from external network(s) like networks operated by a disparate service provider; for instance, WAN1050or Global Positioning System (GPS) network(s) (not shown). Provisioning server(s) can also provision coverage through networks associated to wireless network platform1010(e.g., deployed and operated by the same service provider), such as femto-cell network(s) (not shown) that enhance wireless service coverage within indoor confined spaces and offload RAN resources in order to enhance subscriber service experience within a home or business environment by way of UE1075.

It is to be noted that server(s)1014can include one or more processors configured to confer at least in part the functionality of macro network platform1010. To that end, the one or more processor can execute code instructions stored in memory1030, for example. It is should be appreciated that server(s)1014can include a content manager1015, which operates in substantially the same manner as described hereinbefore.

In example embodiment1000, memory1030can store information related to operation of wireless network platform1010. Other operational information can include provisioning information of mobile devices served through wireless platform network1010, subscriber databases; application intelligence, pricing schemes, e.g., promotional rates, flat-rate programs, couponing campaigns; technical specification(s) consistent with telecommunication protocols for operation of disparate radio, or wireless, technology layers; and so forth. Memory1030can also store information from at least one of telephony network(s)1040, WAN1050, enterprise network(s)1060, or SS7network1070. In an aspect, memory1030can be, for example, accessed as part of a data store component or as a remotely connected memory store.