Patent application number | Description | Published |
20130121159 | DATA BREAKOUT AT THE EDGE OF A MOBILE DATA NETWORK - Mobile network services are performed in a mobile data network in a way that is transparent to most of the existing equipment in the mobile data network. The mobile data network includes a radio access network and a core network. A first service mechanism in the radio access network breaks out data coming from a basestation, and performs one or more mobile network services at the edge of the mobile data network based on the broken out data. These services may include caching of data, data or video compression techniques, push-based services, charging, application serving, analytics, security, data filtering, and new revenue-producing services, as well as others. This architecture allows performing new mobile network services at the edge of a mobile data network within the infrastructure of an existing mobile data network. | 05-16-2013 |
20130121250 | DATA BREAKOUT AT THE EDGE OF A MOBILE DATA NETWORK - Mobile network services are performed in a mobile data network in a way that is transparent to most of the existing equipment in the mobile data network. The mobile data network includes a radio access network and a core network. A first service mechanism in the radio access network breaks out data coming from a basestation, and performs one or more mobile network services at the edge of the mobile data network based on the broken out data. These services may include caching of data, data or video compression techniques, push-based services, charging, application serving, analytics, security, data filtering, and new revenue-producing services, as well as others. This architecture allows performing new mobile network services at the edge of a mobile data network within the infrastructure of an existing mobile data network. | 05-16-2013 |
20130156020 | KEY STORAGE AND RETRIEVAL IN A BREAKOUT COMPONENT AT THE EDGE OF A MOBILE DATA NETWORK - Mobile network services are performed in a mobile data network in a way that is transparent to most of the existing equipment in the mobile data network. The mobile data network includes a radio access network and a core network. A breakout component in the radio access network breaks out data coming from a basestation, and performs one or more mobile network services at the edge of the mobile data network based on the broken out data. These services may require the use of keys. Keys are stored and retrieved from a non-volatile key storage in a way that assures subsystems that need the keys have access to the keys. The keys retrieved from the non-volatile key storage are stored in a shared memory in the requesting subsystem, which allows any applications that requires access to the keys to directly access the keys in the shared memory. | 06-20-2013 |
20130157618 | KEY STORAGE AND RETRIEVAL IN A BREAKOUT COMPONENT AT THE EDGE OF A MOBILE DATA NETWORK - Mobile network services are performed in a mobile data network in a way that is transparent to most of the existing equipment in the mobile data network. The mobile data network includes a radio access network and a core network. A breakout component in the radio access network breaks out data coming from a basestation, and performs one or more mobile network services at the edge of the mobile data network based on the broken out data. These services may require the use of keys. Keys are stored and retrieved from a non-volatile key storage in a way that assures subsystems that need the keys have access to the keys. The keys retrieved from the non-volatile key storage are stored in a shared memory in the requesting subsystem, which allows any applications that requires access to the keys to directly access the keys in the shared memory. | 06-20-2013 |
20130157619 | STATES FOR BREAKOUT APPLIANCE IN A MOBILE DATA NETWORK - Mobile network services are performed in a mobile data network in a way that is transparent to most of the existing equipment in the mobile data network. The mobile data network includes a radio access network and a core network. A breakout appliance in the radio access network breaks out data coming from a basestation, and performs one or more mobile network services at the edge of the mobile data network based on the broken out data. The breakout appliance includes multiple states that support manufacturing, testing, production, tamper detection and end of life, and the functions of the breakout appliance vary according to its state. | 06-20-2013 |
20130157702 | STATES FOR BREAKOUT APPLIANCE IN A MOBILE DATA NETWORK - Mobile network services are performed in a mobile data network in a way that is transparent to most of the existing equipment in the mobile data network. The mobile data network includes a radio access network and a core network. A breakout appliance in the radio access network breaks out data coming from a basestation, and performs one or more mobile network services at the edge of the mobile data network based on the broken out data. The breakout appliance includes multiple states that support manufacturing, testing, production, tamper detection and end of life, and the functions of the breakout appliance vary according to its state. | 06-20-2013 |
20130173898 | SECURE BOOT OF A DATA BREAKOUT APPLIANCE WITH MULTIPLE SUBSYSTEMS AT THE EDGE OF A MOBILE DATA NETWORK - A secure boot is provided for a breakout system having multiple subsystems at the edge of a mobile data network. The secure boot utilizes two trusted platform modules (TPM) to secure multiple subsystems. Further described is utilizing a first TPM to boot a service processor and then utilizing a second TPM to secure boot two additional subsystems. Booting of the final subsystem is accomplished in a two step process which first loads a boot loader and verifies the boot loader, and then second loads an operating system load image and verifies the operating system code. | 07-04-2013 |
20130174220 | SECURE BOOT OF A DATA BREAKOUT APPLIANCE WITH MULTIPLE SUBSYSTEMS AT THE EDGE OF A MOBILE DATA NETWORK - A secure boot is provided for a breakout system having multiple subsystems at the edge of a mobile data network. The secure boot utilizes two trusted platform modules (TPM) to secure multiple subsystems. Further described is utilizing a first TPM to boot a service processor and then utilizing a second TPM to secure boot two additional subsystems. Booting of the final subsystem is accomplished in a two step process which first loads a boot loader and verifies the boot loader, and then second loads an operating system load image and verifies the operating system code. | 07-04-2013 |
20130218915 | VALlDATING A SYSTEM WITH MULTIPLE SUBSYSTEMS USING TRUSTED PLATFORM MODULES AND VIRTUAL PLATFORM MODULES - Software validation is provided for a breakout system having multiple subsystems at the edge of a mobile data network. The software validation utilizes one or more trusted platform modules (TPM) to secure multiple subsystems including virtual machines in the breakout system. Hash values for the software in the various subsystems are placed in Platform Configuration Registers (PCRs) of the TPM. The TPM cryptographically signs quotes, which are a collection of hash values from the PCRs. The breakout system produces an extensible markup language (XML) file with the signed quotes related to the subsystems and sends them to a network management system for verification. The network management system validates the software configured on the breakout system using a public key to access the quotes and compares the values to known good values stored in an inventory record associated with the specific breakout system being validated. | 08-22-2013 |
20130219183 | VALlDATING A SYSTEM WITH MULTIPLE SUBSYSTEMS USING TRUSTED PLATFORM MODULES AND VIRTUAL PLATFORM MODULES - Software validation is provided for a breakout system having multiple subsystems at the edge of a mobile data network. The software validation utilizes one or more trusted platform modules (TPM) to secure multiple subsystems including virtual machines in the breakout system. Hash values for the software in the various subsystems are placed in Platform Configuration Registers (PCRs) of the TPM. The TPM cryptographically signs quotes, which are a collection of hash values from the PCRs. The breakout system produces an extensible markup language (XML) file with the signed quotes related to the subsystems and sends them to a network management system for verification. The network management system validates the software configured on the breakout system using a public key to access the quotes and compares the values to known good values stored in an inventory record associated with the specific breakout system being validated. | 08-22-2013 |
20130336114 | USING THE MAINTENANCE CHANNEL IN A MOBILE DATA NETWORK TO PROVIDE SUBSCRIBER DATA WHEN A CACHE MISS OCCURS - A mobile data network includes a radio access network and a core network. A first service mechanism in the radio access network breaks out data coming from a basestation. When data is broken out by the first service mechanism, the data is delivered at the edge, which means the true activity of the channel is not visible to the core network. In order to maintain the high-speed channel, channel maintenance data packets are sent to and from the radio network controller on the network tunnel. The maintenance channel is also used to send cache miss data to a subscriber when a cache miss occurs at the edge of the mobile data network, without regard to a need for channel maintenance data packets. | 12-19-2013 |
20130336207 | REDUCING PACKET LOSS IN A MOBILE DATA NETWORK WITH DATA BREAKOUT AT THE EDGE - A breakout system initiates RLC resets to resynchronize data communication to improve quality of experience for the user. Synchronization of radio traffic is monitored and maintained by the breakout system. When data is broken out, the RLC function is split into two different flows, between the UE and the breakout system and between the breakout system and the RNC. When the sequence numbers of the two flows become out of sync the ciphering context will become out of synchronization resulting in errors. The breakout system can initiate an RLC reset into both of these flows to resynchronize the data communication to improve user's quality of experience. | 12-19-2013 |
20130336208 | REDUCING PACKET LOSS IN A MOBILE DATA NETWORK WITH DATA BREAKOUT AT THE EDGE - A breakout system initiates radio link control (RLC) resets to resynchronize data communication to improve quality of experience for the user. Synchronization of radio traffic is monitored and maintained by the breakout system. When data is broken out, the RLC function is split into two different flows, between the user equipment (UE) and the breakout system and between the breakout system and the radio network controller (RNC). When the sequence numbers of the two flows become out of sync the ciphering context will become out of synchronization resulting in errors. The breakout system can initiate an RLC reset into both of these flows to resynchronize the data communication to improve user's quality of experience. | 12-19-2013 |
20140010087 | IP FLOW BASED OFFLOAD FOR SUBSCRIBER DATA OPTIMIZATION AND SCHEDULING AT THE BASESTATION IN A MOBILE DATA NETWORK - Mobile network services are performed at the edge in a flat mobile data network in a way that is transparent to most of the existing equipment in the mobile data network to reduce the load and increase efficiency on the mobile data network by breaking out data at the edge based on specific IP data flows. The mobile data network includes a radio access network and a core network. A first service mechanism in the radio access network breaks out data coming from a basestation based on breakout conditions, and performs one or more mobile network services. The second service mechanism determines what traffic satisfies breakout authorization criteria and informs the first service mechanism. The message from the second service mechanism triggers the first service mechanism to perform IP flow based breakout. An overlay network allows the first and second mechanisms to communicate with each other. | 01-09-2014 |
20140026064 | VIRTUAL WORLD TELEPORTATION - The present invention is directed to teleporting avatars between disparate virtual worlds. A system is disclosed that includes a facility for creating a persona profile for an avatar in a first virtual world when the avatar wants to be teleported out of the first virtual world; a facility for transferring persona profiles to and from a disparate virtual world; and a facility for instantiating an inbound avatar based on a received persona profile. Persona profiles may include, e.g., rendering information, trait information, and inventory information. | 01-23-2014 |
20140026077 | VIRTUAL WORLD TELEPORTATION - The present invention is directed to teleporting avatars between disparate virtual worlds. A system is disclosed that includes a facility for creating a persona profile for an avatar in a first virtual world when the avatar wants to be teleported out of the first virtual world; a facility for transferring persona profiles to and from a disparate virtual world; and a facility for instantiating an inbound avatar based on a received persona profile. Persona profiles may include, e.g., rendering information, trait information, and inventory information. | 01-23-2014 |
20140026078 | VIRTUAL WORLD TELEPORTATION - The present invention is directed to teleporting avatars between disparate virtual worlds. A system is disclosed that includes a facility for creating a persona profile for an avatar in a first virtual world when the avatar wants to be teleported out of the first virtual world; a facility for transferring persona profiles to and from a disparate virtual world; and a facility for instantiating an inbound avatar based on a received persona profile. Persona profiles may include, e.g., rendering information, trait information, and inventory information. | 01-23-2014 |
20140043980 | LAWFUL INTERCEPTION IN A MOBILE DATA NETWORK WITH DATA OFFLOAD AT THE BASESTATION - Lawful interception (LI) is supported on a flat mobile data network with breakout services at the basestation. A first service mechanism at the basestation is prevented from breaking out services for subscribers that are part of LI. A second service mechanism in the core network maintains a subscriber list of subscribers that are subject to LI. In response to a PDP context activation by a subscriber on the list, the second service mechanism does not supply PDP context information to the first service mechanism for data breakout thus preventing breakout for the subscriber subject to lawful interception. | 02-13-2014 |
20140044019 | LAWFUL INTERCEPTION IN A MOBILE DATA NETWORK WITH DATA OFFLOAD AT THE BASESTATION - Lawful interception (LI) is supported on a flat mobile data network with breakout services at the basestation. A first service mechanism at the basestation is prevented from breaking out services for subscribers that are part of LI. A second service mechanism in the core network maintains a subscriber list of subscribers that are subject to LI. In response to a PDP context activation by a subscriber on the list, the second service mechanism does not supply PDP context information to the first service mechanism for data breakout thus preventing breakout for the subscriber subject to lawful interception. | 02-13-2014 |
20140071804 | UTILIZING STORED DATA TO REDUCE PACKET DATA LOSS IN A MOBILE DATA NETWORK WITH DATA BREAKOUT AT THE EDGE - In a mobile data network with a breakout system, when data is broken out, the RLC function is split into two different flows, between the UE and the breakout system and between the breakout system and the RNC. These two flows are processed by different RLC functions that may drift apart and become out of synchronization resulting in errors that diminish the user's quality of experience. Other errors may also occur in communication on these two different flows. The breakout system attempts to correct these errors using data stored locally in communication data structures for the two data flows. If the errors cannot be corrected, the breakout system can initiate an RLC reset into both of these flows to resynchronize the data communication. | 03-13-2014 |
20140071805 | UTILIZING STORED DATA TO REDUCE PACKET DATA LOSS IN A MOBILE DATA NETWORK WITH DATA BREAKOUT AT THE EDGE - In a mobile data network with a breakout system, when data is broken out, the RLC function is split into two different flows, between the UE and the breakout system and between the breakout system and the RNC. These two flows are processed by different RLC functions that may drift apart and become out of synchronization resulting in errors that diminish the user's quality of experience. Other errors may also occur in communication on these two different flows. The breakout system attempts to correct these errors using data stored locally in communication data structures for the two data flows. If the errors cannot be corrected, the breakout system can initiate an RLC reset into both of these flows to resynchronize the data communication. | 03-13-2014 |
20140098680 | MOBILITY SUPPORT IN A MOBILE DATA NETWORK - A mobility event is supported on a flat or next generation mobile data networks with data breakout or offload at the edge of the mobile data network. Packet data is buffered while a complete set of the PDP context information is transferred from the source eNodeB to the target eNodeB and the mobile core network is updated with the information about the handover in a timely manner to prevent packet loss and thus provide a seamless user experience. The breakout system supports the PDP context transfer by shifting the end point of the TCP communication from the local breakout entity (MIOP@eNodeB) to the core breakout entity (MIOP@GW), transferring the TCP connection to the core breakout entity, and supporting the network initiated control flows in a way that is seamless from the perspective of the UE and the core network. | 04-10-2014 |
20140098687 | MOBILITY SUPPORT IN A MOBILE DATA NETWORK - A mobility event is supported on a flat or next generation mobile data networks with data breakout or offload at the edge of the mobile data network. Packet data is buffered while a complete set of the PDP context information is transferred from the source eNodeB to the target eNodeB and the mobile core network is updated with the information about the handover in a timely manner to prevent packet loss and thus provide a seamless user experience. The breakout system supports the PDP context transfer by shifting the end point of the TCP communication from the local breakout entity (MIOP@eNodeB) to the core breakout entity (MIOP@GW), transferring the TCP connection to the core breakout entity, and supporting the network initiated control flows in a way that is seamless from the perspective of the UE and the core network. | 04-10-2014 |
20140132763 | Distributed Control of a Heterogeneous Video Surveillance Network - A surveillance video broker arbitrates access by multiple clients to multiple surveillance video sources. Both clients and sources register with the broker. Each source independently specifies respective clients permitted real-time access to its video and conditions of access, if any. Preferably, the video source is a local surveillance domain having one or more cameras, one or more sensors, and a local controller, the source specifying clients or client groups permitted access, and independently specifying conditions of access for each client or client group, where conditions may include scheduled events, non-scheduled events, such as alarms or emergencies, and/or physical proximity. The broker automatically authorizes real-time access according to pre-specified conditions. Preferably, the broker can also arbitrate alert notifications to the clients based on pre-specified notification criteria. | 05-15-2014 |
20140132764 | Providing Emergency Access to Surveillance Video - Real-time access by a public authority emergency responder to surveillance video of a privately-controlled source is conditionally pre-authorized dependent on the existence of at least one pre-specified emergency condition, and recorded in a data processing system. A public authority emergency responder subsequently requests real-time access to the surveillance video (e.g., during an emergency), and if the pre-specified emergency condition is met, access is automatically granted, i.e., without the need for manual intervention. A pre-specified emergency condition could, e.g., be an alarm condition detected by a sensor at the site of the video surveillance, or a declared state of emergency, properly declared by an appropriate public official. | 05-15-2014 |
20140132765 | Automated Authorization to Access Surveillance Video Based on Pre-Specified Events - Real-time access by a requestor to surveillance video is conditionally pre-authorized dependent on the existence of at least one pre-specified automatically detectable condition, and recorded in a data processing system. A requestor subsequently requests real-time access to the surveillance video (e.g., as a result of an alarm), and if the pre-specified automatically detectable condition is met, access is automatically granted, i.e., without the need for manual intervention. An automatically detectable condition could, e.g., be an alarm condition detected by a sensor at the site of the video surveillance. Alternatively, it could be a locational proximity of the requestor to the site of the video surveillance. Alternatively, it could be a previously defined time interval. | 05-15-2014 |
20140132772 | Automated Authorization to Access Surveillance Video Based on Pre-Specified Events - Real-time access by a requestor to surveillance video is conditionally pre-authorized dependent on the existence of at least one pre-specified automatically detectable condition, and recorded in a data processing system. A requestor subsequently requests real-time access to the surveillance video (e.g., as a result of an alarm), and if the pre-specified automatically detectable condition is met, access is automatically granted, i.e., without the need for manual intervention. An automatically detectable condition could, e.g., be an alarm condition detected by a sensor at the site of the video surveillance. Alternatively, it could be a locational proximity of the requestor to the site of the video surveillance. Alternatively, it could be a previously defined time interval. | 05-15-2014 |
20140133831 | Providing Emergency Access to Surveillance Video - Real-time access by a public authority emergency responder to surveillance video of a privately-controlled source is conditionally pre-authorized dependent on the existence of at least one pre-specified emergency condition, and recorded in a data processing system. A public authority emergency responder subsequently requests real-time access to the surveillance video (e.g., during an emergency), and if the pre-specified emergency condition is met, access is automatically granted, i.e., without the need for manual intervention. A pre-specified emergency condition could, e.g., be an alarm condition detected by a sensor at the site of the video surveillance, or a declared state of emergency, properly declared by an appropriate public official. | 05-15-2014 |
20140136701 | Distributed Control of a Heterogeneous Video Surveillance Network - A surveillance video broker arbitrates access by multiple clients to multiple surveillance video sources. Both clients and sources register with the broker. Each source independently specifies respective clients permitted real-time access to its video and conditions of access, if any. Preferably, the video source is a local surveillance domain having one or more cameras, one or more sensors, and a local controller, the source specifying clients or client groups permitted access, and independently specifying conditions of access for each client or client group, where conditions may include scheduled events, non-scheduled events, such as alarms or emergencies, and/or physical proximity. The broker automatically authorizes real-time access according to pre-specified conditions. Preferably, the broker can also arbitrate alert notifications to the clients based on pre-specified notification criteria. | 05-15-2014 |
20140241152 | COLLECTION OF SUBSCRIBER INFORMATION FOR DATA BREAKOUT IN A MOBILE DATA NETWORK - A method and system supports subscriber based IP data breakout at the edge of a mobile data network without monitoring the use of security keys or breaking into ciphered message exchanges. The system employs a first service mechanism operating at the edge of the mobile data network a second service mechanism operating at the core on the S11 interface. The second service mechanism at the core collects subscriber related data, subscriber identifiers and tunnel identifiers and sends this data to the first service mechanism. The second service mechanism at the core collects subscriber related data, subscriber identifiers and tunnel identifiers and sends this data to the first service mechanism. The first service mechanism uses the tunnel identifiers received from the second service mechanism to identify sessions and tunnels carrying subscriber dependent data packets (S1-U packets) in order to perform subscriber-based IP data breakout, offloading and optimization. | 08-28-2014 |
20140241158 | COLLECTION OF SUBSCRIBER INFORMATION FOR DATA BREAKOUT IN A MOBILE DATA NETWORK - A method and system supports subscriber based IP data breakout at the edge of a mobile data network without monitoring the use of security keys or breaking into ciphered message exchanges. The system employs a first service mechanism operating at the edge of the mobile data network a second service mechanism operating at the core on the S11 interface. The second service mechanism at the core collects subscriber related data, subscriber identifiers and tunnel identifiers and sends this data to the first service mechanism. The second service mechanism at the core collects subscriber related data, subscriber identifiers and tunnel identifiers and sends this data to the first service mechanism. The first service mechanism uses the tunnel identifiers received from the second service mechanism to identify sessions and tunnels carrying subscriber dependent data packets (S1-U packets) in order to perform subscriber-based IP data breakout, offloading and optimization. | 08-28-2014 |
20150026695 | SYSTEM AND METHOD TO CONTROL HEAT DISSIPATION THROUGH SERVICE LEVEL ANALYSIS - The system and method generally relate to reducing heat dissipated within a data center, and more particularly, to a system and method for reducing heat dissipated within a data center through service level agreement analysis, and resultant reprioritization of jobs to maximize energy efficiency. A computer implemented method includes performing a service level agreement (SLA) analysis for one or more currently processing or scheduled processing jobs of a data center using a processor of a computer device. Additionally, the method includes identifying one or more candidate processing jobs for a schedule modification from amongst the one or more currently processing or scheduled processing jobs using the processor of the computer device. Further, the method includes performing the schedule modification for at least one of the one or more candidate processing jobs using the processor of the computer device. | 01-22-2015 |