Sprint Communications Comapny L.p.

Sprint Communication Cômpany L.p.

Dora Potluri

Wing K Lee

James D Barnes

Shrikant D Jannu

Ivan K Chow

Denis Tsai

Dan O'Connor

Ratna K Daggubati

Robin Dale Katzer

M Jeffrey Stone

Sanjay Kumar Sharma

Devon L Biere

Lavanya Srinivasan

Kenneth Charles Boydstun

Bharath N Kuruvalli

Jiangxiang Yang

Yiqun Ye

Jianxiang Yang

Yiquin Ye

Omar Dewan

A method and system are disclosed for behavioral analysis for profiling wireless subscribers. The method includes loading carrier reference data comprising a set of common categories and loading a plurality of behavior records of at least two types, wherein each behavior record is generated by a mobile device activity of a subscriber. The method proceeds by associating each behavior record with one or more of the categories, thereby generating categorized data records. Finally each category associated with a behavior record is added to a subscriber profile for the subscriber whose activity generated the behavior record.

Behavioral analysis engine for profiling wireless subscribers

A system is provided for a mobile device search optimizer. The system includes a storage device, a processor, and an optimizer engine. The optimizer engine, when executed by the processor, stores user input for a mobile device to the storage device. The optimizer engine also identifies a pattern of multiple user inputs entered to select a presentation view of an application on the mobile device during multiple occasions. Additionally, the optimizer engine configures the application to offer a user input option to display the presentation view in response to a selection of the user input option.

Mobile device search optimizer

A system for personalizing new mobile devices based on previous mobile device usage is provided. The system includes a storage device, a processor, and a personalizing engine. The personalizing engine, when executed by the processor, stores user input for a first mobile device to the storage device, and builds a profile based on the user input. The personalizing engine also configures a user interface on a second mobile device to provide a user interface link based on the profile to enable a user to access the user interface link via the second mobile device.

Mobile device personalization based on previous mobile device usage

Computer implemented methods and systems are provided for web log filtering. A uniform resource locator (URL) is identified for a resource requested by an identified device. The URL is stored unless the URL has at a reference to an advertisement or an extension that matches any of a list of extensions specified for storage exclusion. The stored URL is categorized based on either the stored URL or an included domain name, depending on whether the included domain name matches any of the list of domain names that are associated with multiple categories. A count is incremented in a web log category associated with the identified device based on the categorized stored URL.

Web log filtering

Computer implemented methods and systems are provided for web log category analysis of website usage. A communication service provider computer system identifies a uniform resource locator (URL) for a resource requested by a mobile device. The communication service provider computer system categorizes the URL. The communication service provider computer system increments a count in a web log category based on categorizing the URL and customer data associated with the mobile device. The communication service provider computer system analyzes a usage of a plurality of websites associated with the web log category based on the count in the web log category.

Audience measurement of wireless web subscribers

A system and method for accessing a business logic module is provided. The system comprises a client that calls an interface to send a stateful message. The system also comprises a stateless session bean which receives the stateful message from the interface and calls the business logic module to perform a function.

Web services enterprise integration with service oriented architecture

A system for demonstrating proof of concept of a project, such as a computer application, for an organization is provided. The system includes a requirements component, a use case component, a log component, and a reporting component. The requirements component maintains requirements of the organization for the project or computer application. The use case component maintains a plurality of use cases, each of the plurality of use cases are associated with at least one of the requirements. The log component track the results of the project or computer application's execution of at least some of the plurality of use cases. The log component is also operable to track at least some defects of the project identified based on executing some of the plurality of use cases. The reporting component is operable to report results for at least some of the use cases.

Demonstrating proof of concept of a project with requirements component providing weights on importance and tracking with use cases

A naming service for locating a service in an enterprise is provided. The naming service comprising a binding module to associate a first service with a location of an interface maintaining a reference to the first service, the binding module further operable to associate a second service with a location of the second service. The naming service further comprising a look-up module operative to provide the location of the interface in response to a request by an application for the first service, the look-up module further operable to provide the location of the second service in response to a request by a second application. A method for locating a service in an enterprise is also provided.

Enterprise naming service system and method

The present invention, known as the Middleware Brokering System, brokers messages between middleware computing products. Each middleware service can send data to the Middleware Brokering System in its native data format and programming syntax. The Middleware Brokering System converts the data transmitted from the different platforms into a standard format known as a structured event. Messages are then transmitted to and stored in an underlying, commercially available publish/subscribe engine. The Middleware Brokering System contains internal logic that determines whether any subscribers are interested in the messages. If an interested subscriber is found, the Middleware Brokering System retrieves the message from the publish/subscribe engine, converts the data from the structured event into the native format of the receiving application, and sends the message to the appropriate application.

Middleware brokering system

The present invention, known as the Middleware Brokering System Adapter, is a component useful with a Middleware Brokering System, which brokers messages between middleware computing products. Each middleware service can send data to and receive data from the Middleware Brokering System in its native data format and programming syntax. The Middleware Brokering System Adapter is a component of the Middleware Brokering System that transforms data messages from the native format of a middleware computing product or a mainframe computing system into a format known as a structured event and from a structured event into the native format of the middleware product or the mainframe system. In an embodiment of the invention, the Middleware Brokering System Adapter maps the fields of a Cobol copybook onto the fields of a structured event and the fields of a structured event onto the fields of a copybook. In an alternative embodiment, the Middleware Brokering System Adapter maps the fields of a Java Messaging Service MapMessage onto the fields of a structured event and the fields of a structured event onto the fields of a MapMessage.

Middleware brokering system adapter

The invention comprises methods and apparatus for implementing a trader service. The present invention involves creating a trader service, preferably compliant with the CORBA CosTrader Specification, where the trader service is arranged to store persistent information using a directory service. This aspect involves creating a storage mechanism comprising a directory service, preferably a directory service compliant with LDAP version 2, which is arranged to store the persistent information for the trader service. An additional embodiment may be implemented by creating a data store interface for interacting with the directory service, wherein such interaction comprises the use of protocol compliant with LDAP version 2.

Method and apparatus for implementing persistence in trader services associated with a computer system

A CORBA-compliant computer network includes a registration server on which an AAR service resides, a registry database and an ORB which couples the registry server to the registry database. A CORBA-compliant interceptor residing on the ORB intercepts each message, generated by the AAR service, invoking the registry database and each message, generated by the registry database, responding to the invocation message generated by the service of the client server. The interceptor selects information useful in determining the cause of a failed usage of the service residing in the client server from each intercepted invocation and response messages, writes the selected information to a data store residing in the client server and then re-invokes the intercepted invocation and response messages. In the event of a network failure, the data written to the data store may be reviewed to obtain useful information regarding the network failure.

Computer system having an authentication and/or authorization routing service and a CORBA-compliant interceptor for monitoring the same

The invention comprises methods and apparatus for implementing a name service. In the present invention, a name service compliant with the CORBA CosNaming specification may be implemented which incorporates load balancing. This invention involves a name service having a data store and a data store interface which are not necessarily configured for the persistent storage of information. This invention further involves creating a load balancing index within the data store interface and using name-overloading to create names containing a load balancing name identifier which may be used for referencing in the load balancing index. The data store interface of this embodiment could also include a specific bind operation, a specific resolve operation, or both.

Method and apparatus for implementing CORBA compliant name services incorporating load balancing features

A naming service implementation method and apparatus. The method involves creating a name service, preferably compliant with the CORBA CosNaming Specification, where the name service is arranged to store persistent information using a directory service. This aspect involves creating a storage mechanism comprising a directory service, preferably a directory service compliant with LDAP version 2, which is arranged to store the persistent information for the name service. An additional embodiment may be implemented by creating a data store interface for interacting with the directory service, wherein such interaction comprises the use of protocol compliant with LDAP version 2.

Growing community of inventors

Plano, TX, United States of America

Dora Potluri