Search Images Maps Play YouTube News Gmail Drive More »
Sign in
Screen reader users: click this link for accessible mode. Accessible mode has the same essential features but works better with your reader.

Patents

  1. Advanced Patent Search
Publication numberWO2007018363 A1
Publication typeApplication
Application numberPCT/KR2006/003036
Publication date15 Feb 2007
Filing date2 Aug 2006
Priority date5 Aug 2005
Publication numberPCT/2006/3036, PCT/KR/2006/003036, PCT/KR/2006/03036, PCT/KR/6/003036, PCT/KR/6/03036, PCT/KR2006/003036, PCT/KR2006/03036, PCT/KR2006003036, PCT/KR200603036, PCT/KR6/003036, PCT/KR6/03036, PCT/KR6003036, PCT/KR603036, WO 2007/018363 A1, WO 2007018363 A1, WO 2007018363A1, WO-A1-2007018363, WO2007/018363A1, WO2007018363 A1, WO2007018363A1
InventorsByoung-Young Son
ApplicantUpresto, Inc.
Export CitationBiBTeX, EndNote, RefMan
External Links: Patentscope, Espacenet
System for testifying mobile communication network and method thereof
WO 2007018363 A1
Abstract
Provided is a mobile network verification network system and a method thereof. The mobile network verification system includes: a central controller which controls an overall operation and receives information required for a call simulation; a call generator which automatically generates a call by using a terminal according to an instruction requested from the central controller; an integral call analyzer which collects messages transmitted/received between systems included in a mobile network by using the call generated by the call generator, analyzes the collected messages, and transmits the analyzed information to the central controller; and a service controller which provides a service scenario test environment, and checks or modifies a subscriber service profile in association with external systems related to a specific service. Accordingly, the mobile network and each system can be automatically verified.
Claims  (OCR text may contain errors)
[CLAIMS]
[Claim l]
A mobile network verification system which verifies operations of respective systems included in the mobile network, the verification system comprising: a central controller which controls an overall operation and receives information required for a call simulation; a call generator which automatically generates a call by using a terminal according to an instruction requested from the central controller; and an integral call analyzer which collects messages transmitted/received between systems included in a mobile network by using the call generated by the call generator, analyzes the collected messages, and transmits the analyzed information to the central controller.
[Claim 2]
The verification system according to claim 1, further comprising a service controller, wherein the service controller provides a service scenario test environment, and checks or modifies a subscriber service profile in association with external systems related to a specific service .
[Claim 3] The verification system according to claim 1, further comprising a message collector, wherein the message collector collects a No.7 protocol signal transmitted/received between the systems included in the mobile network, converts the collected signal into an TCP/IP signal, multiplexes the converted signal, and transmits the multiplexed signal to the integral call analyzer.
[Claim 4]
The verification system according to any one of claims 1 to 3, wherein the integral call analyzer detects information on an origination point code, a destination point code, and a transaction ID from the collected messages, and stores the information in a database.
[Claim 5] The verification system according to any one of claims 1 to 3, wherein: the integral call analyzer detects information on an origination point code, a destination point code, and a transaction ID from the collected messages, and stores the information in a database; and the integral call analyzer uses the database so as to analyze transactions for respective nodes, thereby forming a call transaction flow for a specific node.
[Claim 6] The verification system according to any one of claims 1 to 3, wherein: the integral call analyzer detects information on an origination point code, a destination point code, and a transaction ID from the collected messages, and stores the information in a database; and the integral call analyzer uses the database so as to detect a related call transaction of all nodes for a specific call, thereby forming a call transaction flow in a network for the specific call by using the detected transaction information.
[Claim 7]
The verification system according to any one of claims 1 to 3, wherein: the central controller instructs the call generator to create a call by using an origination phone number and a destination phone number which are externally received; the call generator generates a call by using a terminal under the instruction of the central controller; and the integral call analyzer traces all transactions of the mobile network for the generated call from the collected messages, and analyzes the traced transaction.
[Claim 8] A method in which a message transmitted/received between nodes included in a mobile network is collected so as to verify the mobile network, the method comprising steps of:
(a) checking whether the collected message is a call related message;
(b) detecting LinkSet information from the message if the message is the call related message;
(c) recognizing a type of a message protocol, and detecting a specific parameter decided depending on the type of the message protocol by using the message;
(d) checking whether the message is a message desired to be collected, by using the LinkSet information and the specific parameter; and
(e) storing the message in a call information database classified according to the message protocol if the message is a message desired to be collected, wherein, in the method, transactions for a specific call are analyzed.
[Claim 9] The method according to claim 8, wherein the step (c) comprises :
(c-1) recognizing a type of a message protocol; (c-2) detecting a mobile phone number and a transaction ID number from the message if the message protocol is MAP; (c-3) detecting a mobile phone number and a line ID number from the message if the message protocol is ISUP; and
(c-4) detecting a mobile phone number and a local reference number from the message if the message protocol is BSAP, wherein, in the method, transactions for a specific call are analyzed. [Claim lθ]
The method according to any one of claims 8 and 9, further comprising the step of (f) checking whether all transactions stored in the call information database are ended, setting a predetermined ending time, and ending the call after the ending time is over if all of the transactions are ended, when the message is a call ending message.
Description  (OCR text may contain errors)

[DESCRI PTION] [invention Title]

SYSTEM FOR TESTIFYING MOBILE COMMUNICATION NETWORK AND METHOD THEREOF [Technical Field]

The present invention relates to a mobile network verification system and a method thereof, and more particularly, to a mobile network verification system, in which messages transmitted/received between various systems included in a mobile network are collected and analyzed so as to verify the mobile network and operations of the respective systems, and a method thereof. [Background Art]

In general, signaling used in a network is defined as a rule for transferring a series of signals so as to transfer information on a call between systems included in a network and information used for network management and maintenance. As an example of the signaling, No.7 signaling is common channel signaling (CCS) standardized by the International Telecommunication Union's Telecommunication Standardization Sector (ITU-T). In the No.7 signaling, call connection between subscribers and various communication services are provided, or various control signals are transferred so as to manage a network. A protocol employing the No.7 signaling includes: a message transfer part (hereinafter, referred to as MTP) of a network service part which controls signal transfer, corrects errors, and secures a signaling network; a signaling connection control part (hereinafter, referred to SCCP) ; an ISDN user part (hereinafter, referred to as ISUP) which is designed separately depending on an application field such as telephone exchange and data exchange; a transaction capability application part (hereinafter, referred to as TCAP) ; and an application part (hereinafter, referred to AP) .

A No. 7 signaling network, which transfers a signal for controlling a network and performs various communication services, includes a signaling point (SP) for sending, receiving, or transferring a signaling message generated by a user, and a signaling link (SL) that is a logical signal transmission channel for connecting associated signaling points. The signaling point includes a signaling end point

(SEP) that sends or receives a message, and a signaling transfer point (STP) that is formed in pair and transfers the message from one signaling link to another signaling link. The signaling end point includes an origination point (OP) that generates a signaling message and a destination point (DP) that is a destination of the signaling message. A group of signaling links is defined as a signaling LinkSet. A path for transferring a message to the signaling point is defined as a signaling route (SR) . A group of signaling routes, which is a routing path for a signaling destination, is defined as a signaling route set. That is, the No. 7 signaling network includes specification data regarding on the signaling point, the signaling link, the signaling LinkSet, and the signaling route, and transfers a signaling message generated by the originating point through a specific signaling link of a signal LinkSet to be transferred to a destination point, thereby requesting call connection and service.

Meanwhile, a plurality of systems, such as MSC, BSC, HLR, SCP, SMSC, etc, are included in a mobile network. When a new software or hardware package applies to the respective systems, or when a network problem occurs, a network operator verifies the package or tests the network in order to ensure network reliability and stability.

When the network is tested, or a specific package is verified, a conventional method has been used for debugging an internal logic of each system's software, or analyzing a transaction with respect to an adjacent system according to data displayed on an operating terminal by using a system tracing function through a man machine command of the operating terminal. Moreover, in order to analyze a connection relationship between systems included in the overall network, actual calling may be made so that the connection relationship can be decided according to the result thereof. Generally, in the conventional verification method, verification is manually achieved by operators. Therefore, when packages have to be frequently replaced in a system, verification of the packages becomes a problem in terms of long time consumption and high labor costs. In addition, when a problem occurs while a connection relationship is verified between systems included in the overall network, it is very difficult to decide which system erratically operates in the network. In this case, verification consumes human resources and time significantly. Meanwhile, as mobile value added services (for example, pre-paid subscriber, call forwarding, etc) gradually become various, network operators face a lot of troubles in order to verify the services whenever the services are developed, because there is no appropriate method capable of properly verifying the systems and the overall mobile network according to a scenario for each service.

Therefore, the applicant proposes a method capable of recognizing an organic connection relationship between systems included in a mobile network, and checking whether the systems and the overall network normally operate. [Disclosure] [Technical Problem] The present invention provides a mobile network verification system capable of collecting and analyzing a message transmitted/received between systems included in a mobile network, and verifying an overall operation of the mobile network. The present invention also provides a mobile network verification system capable of verifying an operation of a section included in a mobile network by forming a transaction flow for a call transmitted/received between the section included in the mobile network. The present invention also provides a mobile network verification system capable of verifying a process of handling a call in a mobile network by forming a transaction flow for all transactions related to the call in all sections of the mobile network. The present invention also provides a mobile network verification method capable of verifying an overall operation of a mobile network by collecting and analyzing a message transmitted/received between systems included in the mobile network. [Technical Solution]

According to an aspect of the present invention, there is provided a mobile network verification system which verifies operations of respective systems included in the mobile network, the verification system comprising: a central controller which controls an overall operation and receives information required for a call simulation; a call generator which automatically generates a call by using a terminal according to an instruction requested from the central controller; an integral call analyzer which collects messages transmitted/received between systems included in a mobile network by using the call generated by the call generator, analyzes the collected messages, and transmits the analyzed information to the central controller; a service controller which provides a service scenario test environment, and checks or modifies a subscriber service profile in association with external systems related to a specific service; and a message collector which collects a No.7 protocol signal transmitted/received between the systems included in the mobile network, converts the collected signal into an TCP/IP signal, multiplexes the converted signal, and transmits the multiplexed signal to the integral call analyzer; wherein the verification system verifies operations of respective systems included in the mobile network. In the aforementioned aspect of the present invention, the integral call analyzer may detect information on an origination point code, a destination point code, and a transaction ID from the collected messages, and stores the information in a database. Further, the integral call analyzer may use the database so as to analyze transactions for respective nodes, thereby forming a call transaction flow for a specific node. Further, the integral call analyzer may form a call transaction flow in a network for the specific call by detecting a related call transaction of all nodes for a specific call.

According to another aspect of the present invention, there is provided a method in which a message transmitted/received between nodes included in a mobile network is collected so as to verify the mobile network, the method comprising steps of: (a) checking whether the collected message is a call related message; (b) detecting LinkSet information from the message if the message is the call related message; (c) recognizing a type of a message protocol, and detecting a specific parameter decided depending on the type of the message protocol by using the message; (d) checking whether the message is a message desired to be collected, by using the LinkSet information and the specific parameter; and (e) storing the message in a call information database classified according to the message protocol if the message is a message desired to be collected, wherein, in the method, transactions are analyzed for a specific call. In the aforementioned aspect of the present invention, the step (c) may comprise: (c-1) recognizing a type of a message protocol; (c-2) detecting a mobile phone number and a transaction ID number from the message if the message protocol is MAP; (c-3) detecting a mobile phone number and a line ID number from the message if the message protocol is ISUP; and (c-4) detecting a mobile phone number and a local reference number from the message if the message protocol is BSAP, wherein, in the method, transactions are analyzed for a specific call. [Advantageous Effects]

According to the present invention, when a software or hardware package of systems included in a mobile network is modified, or when a network problem occurs, operations of respective systems can be verified. In addition, according to the present invention, a call can be generated for an overall mobile network on the basis of end-to-end principle so as to control a service. Then, the result thereof is collected, and thus data obtained from integral call analysis can be provided to an operator. Therefore, according to the present invention, reliability on a network and each system can be maximized, and efficiency of human and economic resources required for verification can also be maximized. In particular, a system of the present invention applies to an intelligent network service, thereby providing further accurate and effective analysis data. [Description of Drawings]

FIG. 1 is a block diagram schematically illustrating a structure of a mobile network verification system according to an embodiment of the present invention.

FIG. 2 illustrates an example of a mobile network employing a mobile network verification system according to an embodiment of the present invention. FIG. 3 is a block diagram illustrating a portion of a mobile network in order to form a call transaction flow by a mobile network verification system according to an embodiment of the present invention.

FIG. 4 is a flowchart illustrating an example of a call transaction flow in a specific section of the mobile network of FIG. 3.

FIG. 5 is a flowchart illustrating an example of transactions generated in each section of the mobile network in association with a specific call in the mobile network of FIG. 3.

FIG. 6 is a flowchart sequentially illustrating an operation of an integral call analyzer of a mobile network verification system according to an embodiment of the present invention.

FIG. 7 is a flowchart sequentially illustrating the MAP process of FIG. 6.

FIG. 8 is a flowchart sequentially illustrating the ISUP process of FIG. 6.

FIG. 9 is a flowchart sequentially illustrating the BSAP process of FIG. 6.

FIG. 10 illustrates an example of a call transaction flow formed by an integral call analyzer of a mobile network verification system according to an embodiment of the present invention. [Best Mode]

Hereinafter, exemplary embodiments of the present invention will be descried in detail with reference to the accompanying drawings.

FIG. 1 is a block diagram schematically illustrating a structure of a mobile network verification system 10 according to an embodiment of the present invention. Referring to FIG. 1, the verification system 10 includes a central controller 100, a call generator 110, a service controller 120, an integral call analyzer 130, and a message collector 140. Now, the aforementioned elements will be described. First, the central controller 100 controls an overall operation of the verification system 10, receives information required for a call simulation, and instructs the call generator 110 to generate a call according to the received information. That is, when an origination phone number and a destination phone number desired to be found by a user are input to the central controller 100, the verification system 10 traces a call transaction related to a call for the origination and destination phone numbers input by the user from all nodes included in a mobile network. Then, the verification system 10 provides an analysis result thereof.

Further, the central controller 100 provides a user interface of the verification system 10, synchronizes each module of the verification system 10, and performs general control. The call generator 110 automatically generates the call for the origination and destination phone numbers requested from the central controller 100 by using a terminal according to an instruction requested from the central controller 100. The service controller 120 provides a service scenario test environment. Further, the service controller 120 checks or modifies a subscriber service profile in association with external systems related to a specific service. The external systems associated with the service controller 120 are a service network entity within a network. Examples of the external systems include SCP, HLR, and so on.

The message collector 140 collects messages of a No.7 protocol signal transmitted/received between systems included in the mobile network, and multiplexes the collected message by attaching a collected time and a node information tag. Thereafter, the message collector 140 converts the multiplexed message into a TCP/IP signal, and transmits the TCP/IP signal to the integral call analyzer 130. The message collector 140 may be included in the verification system 10. Alternatively, as an independent unit with respect to the verification system 10, the message collector 140 may be disposed outside the verification system 10, and transmit information to the verification system 10. Meanwhile, in a section for transmitting/receiving signals by using a TCP/IP protocol among system sections constituting the mobile network, the integral call analyzer 130 can collect a message without via the message collector 140. The integral call analyzer 130 decodes messages transmitted from the message collector 140 or the like, and stores the decoded messages in a call information database. Further, the integral call analyzer 130 analyses the decoded messages for each node section and each call, and transmits information on the analysis result to the central controller 100. The call information database stores and manages a call ID and call transaction information on the call ID. The call transaction information includes an original point code, a destination point code, an origination phone number, a destination phone number, a message type, a transaction ID (TID) , a call starting time, a call ending time, and the number of messages received and transmitted during entire calls. FIG. 2 illustrates an overall structure of a mobile network installed with the verification system 10 having the aforementioned structure. Referring to FIG. 2, the verification system 10 according to an embodiment of the present invention may apply to a mobile network such as an intelligent network.

As shown in Fig, 2, the mobile network such as the intelligent network includes system nodes such as BTS, BSC, MSC, STP, HLR, SSP, SCP, PDSN, SGSN, IWF, etc. The verification system 10 collects messages transmitted/received between each node through the data collector 140.

The call generator 110 of the verification system 10 automatically generates a call to be simulated using a terminal under the control of the central controller 100.

The integral call analyzer 130 collects the messages transmitted/received between each node of the mobile network by using the call. Then, as shown in FIGS. 4 and 5, the integral call analyzer 130 performs analysis on each section and each call of the system.

FIG. 3 is a block diagram illustrating a portion of a mobile network. FIG. 4 illustrates a call transaction flow for a system section of the SSP 310 and the SCP 320 of FIG. 3. Referring to FIG. 4, the integral call analyzer 130 of the verification system 10 analyzes transactions received/transmitted between the SSP 310 and the SCP 320 with respect to a specific call, and forms a call transaction flow to be transmitted to the central controller 100.

FIG. 5 illustrates a call transaction flow in which related transactions transmitted/received between nodes representing the system over the mobile network of FIG. 3.

Referring to FIG. 5, the integral call analyzer 130 of the verification system 10 analyzes all transactions related to a specific call, and forms a call transaction flow to be transmitted to the central controller 100 .

Now, the operation of the integral call analyzer 130 of the verification system 10 according to an embodiment of the present invention will be described in detail with reference to FIGS. 6 to 9.

FIG. 6 is a flowchart sequentially illustrating an operation of the integral call analyzer 130 according to an embodiment of the present invention. Referring to FIG. 6, a collected message is firstly analyzed (step 600) , and thereafter, it is checked whether the collected message is a call related signaling message (step 610) . If the collected message is the call related signaling message, LinkSet information and mobile ID number (hereinafter, referred to as MIN) are collected, and a specific key value contained in a message is detected (step 620) . The LinkSet information is section information of transaction, and is defined as information on a transmission node and a reception node of transaction. Next, a key value for a specific parameter included in the message is analyzed, and thus a protocol type is recognized (step 630) . If a protocol of the message is a mobile application part (MAP) , the procedure illustrated in FIG. 7 is performed (step 640) . If a protocol of the message is a ISUP, the procedure illustrated in FIG. 8 is performed

(step 642) . If the protocol of the message is BASP, the procedure illustrated in FIG. 9 is performed (step 644) . The procedures will be described later. After the aforementioned steps 640, 642, and 644 are performed, returning back to step

600, the process of analyzing collected messages is repeated.

FIG. 7 is a flowchart illustrating the procedure performed when a protocol is MAP. Referring to FIG. 7, it is checked whether a LinkSet, a MIN, and a transaction ID (hereinafter, referred to as TID) are accurate information

(step 700) . If they are accurate, the presence of a call ID is checked (step 710) . If the call ID does not exist, the call ID is generated (step 712) . A message is stored in a memory allocated to the call ID (step 720) , and thereafter, it is checked whether the message is a call ending message or a transaction ending message (step 722) . If the message is not the call ending message nor the transaction ending message, the process returns back to a flow indicated by 4 in FIG. 6. When an operation type of the message is checked, and the check result shows that the message is the call ending message or the transaction ending message, transaction information on an associated call ID is determined to be an ending state (step 724). Thereafter, it is checked whether the message is the call ending message (step 726) . The end of call is determined according to an ISUP RLC (Release Complete) message or a SCCP RLC message. In the MAP protocol, a call starting message is confirmed if an Origination Request' message or an 'Analyzed Information' message exists. The end of transaction is determined according to a message type tag of a transaction portion and a component type tag of a component portion of a TCAP parameter contained in a MAP message. If the result of step 726 shows that the message is not the call ending message, the process returns back to the flow indicated by 4 in FIG. 6

If the message is the call ending message, it is checked whether all transactions contained in the call ID are ended

(step 728) . If all of the transactions contained in the call ID are not ended, the process indicated by 4 in FIG. 6 is performed.

If all of the transactions contained in the call ID are ended, an ending time is determined for a call (step 730) , and the call is ended after the ending time is over (step 740) . Next, information stored in the memory allocated to the call ID is stored in a database, thereby completing the procedure (step 742) .

FIG. 8 is a flowchart performed when a message protocol is ISUP. All steps of FIG. 8 are the same as those of FIG. 7 except for a process (step 800) for checking whether a LinkSet, a MIN, and a circuit ID code (hereinafter, referred to as CIC) are accurate.

In addition, FIG. 9 is a flowchart performed when a message protocol is base station application part (BSAP) . All steps of FIG. 9 are the same as those of FIG. 7 except for a process (step 900) for checking whether a LinkSet, a MIN, and a local reference number (hereinafter, referred to as LRN) are accurate. The mobile network verification system of the present invention forms a call transaction flow by using transaction information on an call ID stored in a database according to the aforementioned processes.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present invention as defined by the appended claims. [industrial Applicability]

A mobile network verification system of the present invention analyzes systems included in a mobile network such as an intelligent network, and provides an analysis result thereof to an operator. The present invention can be widely used in a mobile network field.

Patent Citations
Cited PatentFiling datePublication dateApplicantTitle
KR20010054212A * Title not available
KR20010083960A * Title not available
KR20040032560A * Title not available
US6765990 *19 Dec 200220 Jul 2004TekelecDatabase driven methods and systems for real time call tracing
Referenced by
Citing PatentFiling datePublication dateApplicantTitle
US835189820 Dec 20118 Jan 2013Headwater Partners I LlcVerifiable device assisted service usage billing with integrated accounting, mediation accounting, and multi-account
US838591626 Apr 201226 Feb 2013Headwater Partners I LlcAutomated device provisioning and activation
US839645826 Apr 201212 Mar 2013Headwater Partners I LlcAutomated device provisioning and activation
US84067331 May 201226 Mar 2013Headwater Partners I LlcAutomated device provisioning and activation
US84372719 Apr 20127 May 2013Headwater Partners I LlcVerifiable and accurate service usage monitoring for intermediate networking devices
US844198920 Jul 201214 May 2013Headwater Partners I LlcOpen transaction central billing system
US846731212 Apr 201218 Jun 2013Headwater Partners I LlcVerifiable and accurate service usage monitoring for intermediate networking devices
US847866725 Apr 20122 Jul 2013Headwater Partners I LlcAutomated device provisioning and activation
US85165524 Apr 201220 Aug 2013Headwater Partners I LlcVerifiable service policy implementation for intermediate networking devices
US852763023 Aug 20123 Sep 2013Headwater Partners I LlcAdaptive ambient services
US853198610 Apr 201210 Sep 2013Headwater Partners I LlcNetwork tools for analysis, design, testing, and production of services
US854787212 Apr 20121 Oct 2013Headwater Partners I LlcVerifiable and accurate service usage monitoring for intermediate networking devices
US857090825 Apr 201329 Oct 2013Headwater Partners I LlcAutomated device provisioning and activation
US858811013 Sep 201219 Nov 2013Headwater Partners I LlcVerifiable device assisted service usage billing with integrated accounting, mediation accounting, and multi-account
US858954125 May 201119 Nov 2013Headwater Partners I LlcDevice-assisted services for protecting network capacity
US860691124 Jan 201210 Dec 2013Headwater Partners I LlcFlow tagging for service policy implementation
US86261159 Sep 20117 Jan 2014Headwater Partners I LlcWireless network service interfaces
US863061115 Nov 201214 Jan 2014Headwater Partners I LlcAutomated device provisioning and activation
US863061719 Oct 201214 Jan 2014Headwater Partners I LlcDevice group partitions and settlement platform
US863063018 Dec 201214 Jan 2014Headwater Partners I LlcEnhanced roaming services and converged carrier networks with device assisted services and a proxy
US863110215 Nov 201214 Jan 2014Headwater Partners I LlcAutomated device provisioning and activation
US86348052 Aug 201221 Jan 2014Headwater Partners I LlcDevice assisted CDR creation aggregation, mediation and billing
US863482112 Nov 201221 Jan 2014Headwater Partners I LlcDevice assisted services install
US863533525 May 201121 Jan 2014Headwater Partners I LlcSystem and method for wireless network offloading
US863567828 Mar 201321 Jan 2014Headwater Partners I LlcAutomated device provisioning and activation
US863981115 Jan 201328 Jan 2014Headwater Partners I LlcAutomated device provisioning and activation
US863993512 Dec 201228 Jan 2014Headwater Partners I LlcAutomated device provisioning and activation
US864019815 Jan 201328 Jan 2014Headwater Partners I LlcAutomated device provisioning and activation
US866636413 Sep 20124 Mar 2014Headwater Partners I LlcVerifiable device assisted service usage billing with integrated accounting, mediation accounting, and multi-account
US86675714 Dec 20124 Mar 2014Headwater Partners I LlcAutomated device provisioning and activation
US868809913 Sep 20121 Apr 2014Headwater Partners I LlcOpen development system for access service providers
US869507319 Apr 20138 Apr 2014Headwater Partners I LlcAutomated device provisioning and activation
US871363012 Apr 201229 Apr 2014Headwater Partners I LlcVerifiable service policy implementation for intermediate networking devices
US872455419 Mar 201313 May 2014Headwater Partners I LlcOpen transaction central billing system
US872512328 Sep 201113 May 2014Headwater Partners I LlcCommunications device with secure data path processing agents
US873795722 Apr 201327 May 2014Headwater Partners I LlcAutomated device provisioning and activation
US87451914 Oct 20113 Jun 2014Headwater Partners I LlcSystem and method for providing user notifications
US874522012 Jul 20133 Jun 2014Headwater Partners I LlcSystem and method for providing user notifications
US878866120 Jan 201422 Jul 2014Headwater Partners I LlcDevice assisted CDR creation, aggregation, mediation and billing
US87937581 Dec 201129 Jul 2014Headwater Partners I LlcSecurity, fraud detection, and fraud mitigation in device-assisted services systems
US879790816 May 20135 Aug 2014Headwater Partners I LlcAutomated device provisioning and activation
US883277720 Sep 20119 Sep 2014Headwater Partners I LlcAdapting network policies based on device service processor configuration
US88393872 Mar 200916 Sep 2014Headwater Partners I LlcRoaming services network and overlay networks
US88393882 Mar 200916 Sep 2014Headwater Partners I LlcAutomated device provisioning and activation
US886845517 Aug 201221 Oct 2014Headwater Partners I LlcAdaptive ambient services
US88861629 Jan 201411 Nov 2014Headwater Partners I LlcRestricting end-user device communications over a wireless access network associated with a cost
US88930091 Dec 201118 Nov 2014Headwater Partners I LlcEnd user device that secures an association of application to service policy with an application certificate check
US889774320 Dec 201125 Nov 2014Headwater Partners I LlcVerifiable device assisted service usage billing with integrated accounting, mediation accounting, and multi-account
US88977442 Oct 201225 Nov 2014Headwater Partners I LlcDevice assisted ambient services
US889807913 Sep 201225 Nov 2014Headwater Partners I LlcNetwork based ambient services
US889829321 Sep 201125 Nov 2014Headwater Partners I LlcService offer set publishing to device agent with on-device service selection
US89034522 Oct 20122 Dec 2014Headwater Partners I LlcDevice assisted ambient services
US892446928 Sep 201130 Dec 2014Headwater Partners I LlcEnterprise access control and accounting allocation for access networks
US892454328 Sep 201130 Dec 2014Headwater Partners I LlcService design center for device assisted services
US892454920 Aug 201230 Dec 2014Headwater Partners I LlcNetwork based ambient services
US894802518 Apr 20143 Feb 2015Headwater Partners I LlcRemotely configurable device agent for packet routing
US90140267 Feb 201221 Apr 2015Headwater Partners I LlcNetwork based service profile management with user preference, adaptive policy, network neutrality, and user privacy
US90260793 Jan 20145 May 2015Headwater Partners I LlcWireless network service interfaces
US903712728 Apr 201419 May 2015Headwater Partners I LlcDevice agent for remote user configuration of wireless network access
US909431123 Jul 201428 Jul 2015Headwater Partners I, LlcTechniques for attribution of mobile device data traffic to initiating end-user application
US913770131 Mar 201515 Sep 2015Headwater Partners I LlcWireless end-user device with differentiated network access for background and foreground device applications
US91377392 Mar 200915 Sep 2015Headwater Partners I LlcNetwork based service policy implementation with network neutrality and user privacy
US91439761 Apr 201522 Sep 2015Headwater Partners I LlcWireless end-user device with differentiated network access and access status for background and foreground device applications
US91544282 Apr 20156 Oct 2015Headwater Partners I LlcWireless end-user device with differentiated network access selectively applied to different applications
US91548266 Apr 20126 Oct 2015Headwater Partners Ii LlcDistributing content and service launch objects to mobile devices
US917310425 Mar 201527 Oct 2015Headwater Partners I LlcMobile device with device agents to detect a disallowed access to a requested mobile data service and guide a multi-carrier selection and activation sequence
US917930819 Apr 20123 Nov 2015Headwater Partners I LlcNetwork tools for analysis, design, testing, and production of services
US917931519 Mar 20153 Nov 2015Headwater Partners I LlcMobile device with data service monitoring, categorization, and display for different applications and networks
US917931623 Mar 20153 Nov 2015Headwater Partners I LlcMobile device with user controls and policy agent to control application access to device location data
US917935930 Mar 20153 Nov 2015Headwater Partners I LlcWireless end-user device with differentiated network access status for different device applications
US91980429 Jan 201324 Nov 2015Headwater Partners I LlcSecurity techniques for device assisted services
US919807410 Apr 201524 Nov 2015Headwater Partners I LlcWireless end-user device with differential traffic control policy list and applying foreground classification to roaming wireless data service
US919807515 Apr 201524 Nov 2015Headwater Partners I LlcWireless end-user device with differential traffic control policy list applicable to one of several wireless modems
US919807616 Apr 201524 Nov 2015Headwater Partners I LlcWireless end-user device with power-control-state-based wireless network access policy for background applications
US919811724 Mar 201524 Nov 2015Headwater Partners I LlcNetwork system with common secure wireless message service serving multiple applications on multiple wireless devices
US920428218 Dec 20121 Dec 2015Headwater Partners I LlcEnhanced roaming services and converged carrier networks with device assisted services and a proxy
US92043743 Apr 20151 Dec 2015Headwater Partners I LlcMulticarrier over-the-air cellular network activation server
US921515926 Mar 201515 Dec 2015Headwater Partners I LlcData usage monitoring for media data services used by applications
US921561313 Apr 201515 Dec 2015Headwater Partners I LlcWireless end-user device with differential traffic control policy list having limited user control
US922002728 Aug 201522 Dec 2015Headwater Partners I LlcWireless end-user device with policy-based controls for WWAN network usage and modem state changes requested by specific applications
US92257979 Apr 201529 Dec 2015Headwater Partners I LlcSystem for providing an adaptive wireless ambient service to a mobile device
US923240324 Mar 20155 Jan 2016Headwater Partners I LlcMobile device with common secure wireless message service serving multiple applications
US924745018 Dec 201226 Jan 2016Headwater Partners I LlcQuality of service for device assisted services
US925366310 Dec 20132 Feb 2016Headwater Partners I LlcControlling mobile device communications on a roaming network based on device state
US925873517 Apr 20159 Feb 2016Headwater Partners I LlcDevice-assisted services for protecting network capacity
US92705595 Dec 201323 Feb 2016Headwater Partners I LlcService policy implementation for an end-user device having a control application or a proxy agent for routing an application traffic flow
US927118416 Apr 201523 Feb 2016Headwater Partners I LlcWireless end-user device with per-application data limit and traffic control policy list limiting background application traffic
US927743316 Apr 20151 Mar 2016Headwater Partners I LlcWireless end-user device with policy-based aggregation of network activity requested by applications
US927744510 Apr 20151 Mar 2016Headwater Partners I LlcWireless end-user device with differential traffic control policy list and applying foreground classification to wireless data service
US931991313 Apr 201519 Apr 2016Headwater Partners I LlcWireless end-user device with secure network-provided differential traffic control policy list
US93511935 Dec 201324 May 2016Headwater Partners I LlcIntermediate networking devices
US93861217 Apr 20155 Jul 2016Headwater Partners I LlcMethod for providing an adaptive wireless ambient service to a mobile device
US938616530 May 20145 Jul 2016Headwater Partners I LlcSystem and method for providing user notifications
US939246214 Nov 201412 Jul 2016Headwater Partners I LlcMobile end-user device with agent limiting wireless data communication for specified background applications based on a stored policy
US949119924 Jul 20148 Nov 2016Headwater Partners I LlcSecurity, fraud detection, and fraud mitigation in device-assisted services systems
US949156422 Jul 20168 Nov 2016Headwater Partners I LlcMobile device and method with secure network messaging for authorized components
US952157817 Apr 201513 Dec 2016Headwater Partners I LlcWireless end-user device with application program interface to allow applications to access application-specific aspects of a wireless network access policy
US953216122 Dec 201527 Dec 2016Headwater Partners I LlcWireless device with application data flow tagging and network stack-implemented network access policy
US953226115 Jan 201427 Dec 2016Headwater Partners I LlcSystem and method for wireless network offloading
US95443972 Feb 201510 Jan 2017Headwater Partners I LlcProxy server for providing an adaptive wireless ambient service to a mobile device
US955788923 Jan 201331 Jan 2017Headwater Partners I LlcService plan design, user interfaces, application programming interfaces, and device management
US956554325 Sep 20137 Feb 2017Headwater Partners I LlcDevice group partitions and settlement platform
US956570719 Dec 20147 Feb 2017Headwater Partners I LlcWireless end-user device with wireless data attribution to multiple personas
US957155917 Feb 201414 Feb 2017Headwater Partners I LlcEnhanced curfew and protection associated with a device group
US957201924 Nov 201414 Feb 2017Headwater Partners LLCService selection set published to device agent with on-device service selection
US957818212 May 201421 Feb 2017Headwater Partners I LlcMobile device and service management
US959147429 Aug 20147 Mar 2017Headwater Partners I LlcAdapting network policies based on device service processor configuration
US960945910 Dec 201428 Mar 2017Headwater Research LlcNetwork tools for analysis, design, testing, and production of services
US960951013 Mar 201428 Mar 2017Headwater Research LlcAutomated credential porting for mobile devices
US960954415 Nov 201328 Mar 2017Headwater Research LlcDevice-assisted services for protecting network capacity
US961519215 Jul 20164 Apr 2017Headwater Research LlcMessage link server with plural message delivery triggers
US964195717 Aug 20162 May 2017Headwater Research LlcAutomated device provisioning and activation
US96479183 Aug 20169 May 2017Headwater Research LlcMobile device and method attributing media services network usage to requesting application
US967473126 Jul 20166 Jun 2017Headwater Research LlcWireless device applying different background data traffic policies to different device applications
US970577123 Jul 201411 Jul 2017Headwater Partners I LlcAttribution of mobile device data traffic to end-user application based on socket flows
US970606114 Nov 201411 Jul 2017Headwater Partners I LlcService design center for device assisted services
US974989815 Apr 201529 Aug 2017Headwater Research LlcWireless end-user device with differential traffic control policy list applicable to one of several wireless modems
US974989915 Apr 201529 Aug 2017Headwater Research LlcWireless end-user device with network traffic API to indicate unavailability of roaming wireless connection to background applications
US97558426 Apr 20125 Sep 2017Headwater Research LlcManaging service user discovery and service launch object placement on a device
Classifications
International ClassificationH04W24/00
Cooperative ClassificationH04W24/00
European ClassificationH04W24/00
Legal Events
DateCodeEventDescription
25 Apr 2007121Ep: the epo has been informed by wipo that ep was designated in this application
6 Feb 2008NENPNon-entry into the national phase in:
Ref country code: DE
3 Sep 2008122Ep: pct app. not ent. europ. phase
Ref document number: 06783492
Country of ref document: EP
Kind code of ref document: A1