Patent application number | Description | Published |
20080301692 | FACILITATING ACCESS TO INPUT/OUTPUT RESOURCES VIA AN I/O PARTITION SHARED BY MULTIPLE CONSUMER PARTITIONS - At least one input/output (I/O) firmware partition is provided in a partitioned environment to facilitate access to I/O resources owned by the at least one I/O firmware partition. The I/O resources of an I/O firmware partition are shared by one or more other partitions of the environment, referred to as consumer partitions. The consumer partitions use the I/O firmware partition to access the I/O resources. Since the I/O firmware partitions are responsible for providing access to the I/O resources owned by those partitions, the consumer partitions are relieved of this task, reducing complexity and costs in the consumer partitions. | 12-04-2008 |
20090063894 | Autonomic PCI Express Hardware Detection and Failover Mechanism - A system with an autonomic PCI Express hardware detection and failover mechanism includes a plurality of combination root complex capable and endpoint capable devices. A combination root complex capable and endpoint capable device may be selectively configured to operate in either a root complex mode or an endpoint mode. One of the devices assumes the root complex mode and the remaining devices each assume the endpoint mode. Each of the endpoint mode devices is adapted to detect a failure of the root complex mode device. In response to detection of the failure of the root complex mode device, one of the endpoint mode devices assumes root complex mode. An endpoint device may include a timer with a timeout value. Whenever, an endpoint device receives a communication from the root complex device, the endpoint device restarts its timer. If the timer times out with the endpoint device receiving a communication from the root complex device, the endpoint device issues a read request to the root complex device. If the root complex device does not respond to the read request, the endpoint device assumes root complex mode. Different endpoint devices may be assigned different timeout values. Accordingly, the endpoint device that is assigned the shortest time out value will assume root complex mode upon detection of a root complex device failure. | 03-05-2009 |
20130070618 | MOBILE NETWORK SERVICES 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 first service mechanism in the radio access network breaks out data coming from a basestation, and performs one or more mobile network services based on the broken out data. A second service mechanism in the core network performs one or more mobile network services based on the network traffic remaining after the first service mechanism performs its breakout. An optional third service mechanism coupled to the core network provides one or more mobile network services in the mobile data network. An overlay network allows the first, second and third service mechanisms to communicate with each other. The overlay network is preferably a private virtual network. | 03-21-2013 |
20130070619 | MAINTENANCE OF HIGH-SPEED CHANNELS BY INSERTING CHANNEL MAINTENANCE DATA IN A MOBILE DATA NETWORK TO AVOID CHANNEL TYPE SWITCHING - 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. The reduction of data in the core network due to serving data at the edge risks causing a switch from a high-speed channel to a low-speed channel by the mechanism in the core network that monitors and assigns channel speeds. In order to maintain the high-speed channel, the on-going data rate for a subscriber session is monitored and channel maintenance traffic is injected towards and from the radio network controller (in both directions). The amount of channel maintenance traffic depends on thresholds that determine a desired data rate. | 03-21-2013 |
20130070687 | MACRO DIVERSITY IN A MOBILE DATA NETWORK WITH EDGE BREAKOUT - Macro diversity is managed at the edge in a mobile data network with edge data Macro diversity is managed at the edge in a mobile data network with edge data breakout with a component in a Mobile Internet Optimization Platform (MIOP) referred to as MIOP@NodeB. A set of NodeBs that are in simultaneous communication with user equipment are defined as an active set. One of the MIOP@NodeBs of the active set is selected as a master, with the remaining MIOP@NodeBs in the active set being designated slaves. During uplink of signaling data, the signaling data is sent from the UE to all the NodeBs in the active set, which send the signaling data to each of their corresponding MIOP@NodeBs. Each slave MIOP@NodeB sends its data to the master MIOP@NodeB, which combines the data from all into a best packet. | 03-21-2013 |
20130070712 | MACRO DIVERSITY IN A MOBILE DATA NETWORK WITH EDGE BREAKOUT - Macro diversity is managed at the edge in a mobile data network with edge data Macro diversity is managed at the edge in a mobile data network with edge data breakout with a component in a Mobile Internet Optimization Platform (MIOP) referred to as MIOP@NodeB. A set of NodeBs that are in simultaneous communication with user equipment are defined as an active set. One of the MIOP@NodeBs of the active set is selected as a master, with the remaining MIOP@NodeBs in the active set being designated slaves. During uplink of signaling data, the signaling data is sent from the UE to all the NodeBs in the active set, which send the signaling data to each of their corresponding MIOP@NodeBs. Each slave MIOP@NodeB sends its data to the master MIOP@NodeB, which combines the data from all into a best packet. | 03-21-2013 |
20130094394 | MAINTENANCE OF HIGH-SPEED CHANNELS BY INSERTING CHANNEL MAINTENANCE DATA IN A MOBILE DATA NETWORK TO AVOID CHANNEL TYPE SWITCHING - 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. The reduction of data in the core network due to serving data at the edge risks causing a switch from a high-speed channel to a low-speed channel by the mechanism in the core network that monitors and assigns channel speeds. In order to maintain the high-speed channel, the on-going data rate for a subscriber session is monitored and channel maintenance traffic is injected towards and from the radio network controller (in both directions). The amount of channel maintenance traffic depends on thresholds that determine a desired data rate. | 04-18-2013 |
20130094400 | MOBILE NETWORK SERVICES 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 first service mechanism in the radio access network breaks out data coming from a basestation, and performs one or more mobile network services based on the broken out data. A second service mechanism in the core network performs one or more mobile network services based on the network traffic remaining after the first service mechanism performs its breakout. An optional third service mechanism coupled to the core network provides one or more mobile network services in the mobile data network. An overlay network allows the first, second and third service mechanisms to communicate with each other. The overlay network is preferably a private virtual network. | 04-18-2013 |
20130121134 | FAIL TO WIRE REMOVABLE MODULE FOR NETWORK COMMUNICATION LINK - A fail-to-wire (FTW) module that preserves a primary data path connection from an upstream computer to a downstream computer if there is any kind of failure in a breakout data path to a breakout system. The FTW module provides switches between the incoming data network data and the breakout system such that when the breakout system encounters a failure, the switches are de-activated to bypass the breakout system. The switches in the FTW module are activated by a system health signal from the breakout system. The breakout system can be serviced without interrupting the data network connections since the FTW module can be extracted from the failed breakout system with data network connections intact. The FTW module is preferably a compact modular element that fits within the breakout chassis and is easily inserted and removed from the breakout system during servicing operations. | 05-16-2013 |
20130121139 | FAIL TO WIRE REMOVABLE MODULE FOR NETWORK COMMUNICATION LINK - A fail-to-wire (FTW) module that preserves a primary data path connection from an upstream computer to a downstream computer if there is any kind of failure in a breakout data path to a breakout system. The FTW module provides switches between the incoming data network data and the breakout system such that when the breakout system encounters a failure, the switches are de-activated to bypass the breakout system. The switches in the FTW module are activated by a system health signal from the breakout system. The breakout system can be serviced without interrupting the data network connections since the FTW module can be extracted from the failed breakout system with data network connections intact. The FTW module is preferably a compact modular element that fits within the breakout chassis and is easily inserted and removed from the breakout system during servicing operations. | 05-16-2013 |
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 |
20130170472 | MOBILITY MANAGEMENT OF OSI CONNECTIONS BETWEEN CELL TOWERS - A processor-implemented method, apparatus, and/or computer program product move Open Systems Interconnection (OSI) layer 4 connections between wirelessly-connected user equipment to a series of cell-towers, wherein an OSI layer 4 connection is extracted out of the underlying cellular protocols at the series of cell-towers. A detection is made that user equipment, which has a broken-out layer 4 connection, has moved from a first cell-tower to a second cell-tower. Traffic for an existing layer 4 connection from the user equipment is tunnelled between the first cell-tower and the second cell-tower. A predetermined trigger event is identified. In response to the predetermined trigger event occurring, an ongoing bidirectional flow of data packets is migrated from the user equipment over to layer 4 connections maintained at the second cell-tower. | 07-04-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 |
20140043042 | Snoop Detection on Calibrated Bus - An electronic system having a high speed signaling bus requiring training (calibration) of a calibrated item in a driver circuitry or a receiver circuitry for reliable operation. At manufacturing or in a secure location, secure calibration coefficients are determined for the electronic system and are stored in a non-volatile storage. During operation, the high speed signaling bus may be re-calibrated, resulting in a new currently active calibration coefficient for the calibrated item. A coefficient watchdog checks a new coefficient value selected by the re-calibration at present environmental conditions such as voltage and temperature against the secure calibration coefficients. If the new calibration coefficient value is the same as a calibration coefficient value in an acceptably close secure calibration coefficient, the new calibration coefficient is accepted; if not, a potentially probed warning is created by the coefficient watchdog. | 02-13-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 |
20140043984 | CHARGING AND POLICY FOR SERVICES AT THE EDGE OF A MOBILE DATA NETWORK - Mobile network services are performed at the edge of 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. A second service mechanism in the core network receives data monitored during attach and Packet Data Protocol (PDP) context activation, and establishes sessions with components in the mobile data network that support charging and policy control for sessions broken out by the first service mechanism. | 02-13-2014 |
20140044018 | CHARGING AND POLICY FOR SERVICES AT THE EDGE OF A MOBILE DATA NETWORK - Mobile network services are performed at the edge of 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. A second service mechanism in the core network receives data monitored during attach and Packet Data Protocol (PDP) context activation, and establishes sessions with components in the mobile data network that support charging and policy control for sessions broken out by the first service mechanism. | 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 |
20140044039 | COOPERATIVE MOBILITY MANAGEMENT IN A MOBILE DATA NETWORK WITH DATA BREAKOUT AT THE EDGE - A TCP context is transferred to a Gi Optimizer to provide cooperative mobility management in a mobile data network with a breakout system. The breakout system includes an Iub Optimizer at the MIOP@NodeB, and the Gi Optimizer at the MIOP@Core. When a MIOP@NodeB detects a mobility event for a broken out user equipment (UE), the Iub optimizer in the MIOP@NodeB coordinates with the Gi optimizer to transfer the TCP/UDP connection established between the UE and the IuB Optimizer to the Gi Optimizer. After the transfer, the UE is served by the Gi Optimizer. The transfer of the TCP/UDP connection to the Gi optimizer may require tunnel stitching at the MIOP@RNC depending on the PDP context state and the RRC state of the UE. | 02-13-2014 |
20140045486 | COOPERATIVE MOBILITY MANAGEMENT IN A MOBILE DATA NETWORK WITH DATA BREAKOUT AT THE EDGE - A TCP context is transferred to a Gi Optimizer to provide cooperative mobility management in a mobile data network with a breakout system. The breakout system includes an Iub Optimizer at the MIOP@NodeB, and the Gi Optimizer at the MIOP@Core. When a MIOP@NodeB detects a mobility event for a broken out user equipment (UE), the Iub optimizer in the MIOP@NodeB coordinates with the Gi optimizer to transfer the TCP/UDP connection established between the UE and the IuB Optimizer to the Gi Optimizer. After the transfer, the UE is served by the Gi Optimizer. The transfer of the TCP/UDP connection to the Gi optimizer may require tunnel stitching at the MIOP@RNC depending on the PDP context state and the RRC state of the UE. | 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 |
20140120978 | NETWORK MANAGEMENT FOR WIRELESS APPLIANCES IN A MOBILE DATA NETWORK - A network management system utilizes an element manager at the RNC level to reduce the workload and efficiently manage multiple wireless appliances in a mobile data network. Management communications from the network management system flow through the element manager to all devices under the RNC level appliance hosting the element manager. The element manager provides for fault management, performance monitoring and configuration of the many breakout appliances and reports necessary information back to the network management system. | 05-01-2014 |
20140122946 | NETWORK MANAGEMENT FOR WIRELESS APPLIANCES IN A MOBILE DATA NETWORK - A network management system utilizes an element manager at the RNC level to reduce the workload and efficiently manage multiple wireless appliances in a mobile data network. Management communications from the network management system flow through the element manager to all devices under the RNC level appliance hosting the element manager. The element manager provides for fault management, performance monitoring and configuration of the many breakout appliances and reports necessary information back to the network management system. | 05-01-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 |
20140198650 | AVOIDING NETWORK ADDRESS TRANSLATON IN A MOBILE DATA NETWORK - A flow setup table in a basestation breakout component allows for servicing non-cacheable IP data flows at the breakout component without the need for network address translation. For each broken out IP flow at the breakout component, the flow setup table holds a mapping between tunnel IDs and the IP related information. The flow setup table data is sent to the breakout component at the gateway. The gateway breakout component uses the flow setup table to forward non-cacheable data requests to the internet and return data received from the internet back to the basestation breakout component. The basestation component then sends the non-cacheable data in the correct tunnel to the user equipment requesting the data. | 07-17-2014 |
20140198718 | AVOIDING NETWORK ADDRESS TRANSLATON IN A MOBILE DATA NETWORK - A flow setup table in a basestation breakout component allows for servicing non-cacheable IP data flows at the breakout component without the need for network address translation. For each broken out IP flow at the breakout component, the flow setup table holds a mapping between tunnel IDs and the IP related information. The flow setup table data is sent to the breakout component at the gateway. The gateway breakout component uses the flow setup table to forward non-cacheable data requests to the internet and return data received from the internet back to the basestation breakout component. The basestation component then sends the non-cacheable data in the correct tunnel to the user equipment requesting the data. | 07-17-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 |