# US 8,151,321 B2 · Modular network-assisted policy resolution > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 8,151,321 B2 - Document ID: US8151321B2 - Status: Granted - Kind: B2 - Application number: 11/333,928 - Filed: 2006-01-17 - Published: 2007-04-19 - Granted: 2012-04-03 - Earliest claimed: 2005-10-13 - Assignees: Nokia Corporation - Inventors: Heikki Waris - Web page: https://patentgrep.com/patent/US8151321B2 ## CPC - H04L 12/28: characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks] (wireless communication networks H04W {; arrangements for dividing the transmission path H04W40/00}) - H04L 41/0894: Policy-based network configuration management - H04L 47/10: Flow control; Congestion control - H04L 47/20: Traffic policing - H04W 8/04: Registration at HLR or HSS [Home Subscriber Server] - H04W 28/02: Traffic management, e.g. flow control or congestion control - H04W 48/18: Selecting a network or a communication service - H04W 36/14: Reselecting a network or an air interface - H04W 88/06: adapted for operation in multiple networks {or having at least two operational modes}, e.g. multi-mode terminals - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract The present invention relates to a policy resolution method and system, access network and terminal device for enabling modular network-assisted policy resolution, wherein the policy resolution is divided into separate stages each handling specific types of trigger events and performing specific types of policy actions. The separate stages are processed in a chronological order during a policy resolution round, and trigger events which occur during a policy resolution round are frozen until the start of the next policy resolution round. Thereby, modular policy resolution with reduced delays and oscillations can be achieved. Moreover, policy processing can be divided into a policy decision point functions in the network and a policy enforcement point function in the network or terminal device, so that terminal resources used for policy resolution can be saved. ## Claims ### Claim 1 A method of policy resolution with interdependent trigger events and policy actions, comprising: dividing a policy resolution into separate stages each handling specific types of trigger events and performing specific types of policy actions; processing in a terminal device, at least one of the separate stages in a chronological order during a policy resolution round; and freezing trigger events which occur during a policy resolution round until the start of the next policy resolution round, wherein an access is selected from a plurality of accesses available to the terminal device. ### Claim 2 (depends on 1) A method according to claim 1, wherein the policy resolution round comprises a first stage of network availability detection, a second stage of listing of accessible networks, a third stage of updating of associations between traffic flows and their parent domains and selection and joining of preferred networks for domains, a fourth stage of updating of associations between flows and access networks and deciding on handovers, a fifth stage of disconnection from networks or deactivation of interfaces, and a sixth stage of execution of policy resolution. ### Claim 3 (depends on 1) A method according to claim 1, wherein the trigger events comprise configuration events and connectivity events. ### Claim 4 (depends on 3) A method according to claim 3, further comprising sending the configuration events by a configuration application in one set. ### Claim 5 (depends on 3) A method according to claim 3, further comprising buffering the configuration events over time periods longer than those of other trigger events. ### Claim 6 (depends on 2) A method according to claim 2, wherein the first stage is performed based on knowledge about the need for the first or estimation about when the first stage could result in new information. ### Claim 7 (depends on 2) A method according to claim 2, wherein the second stage is started from a list of networks that were detected as available, and wherein those networks which are blocked by current policies are removed from the list. ### Claim 8 (depends on 2) A method according to claim 2, wherein the third stage is performed by checking flows of a first domain with respect to the need to move to a second domain. ### Claim 9 (depends on 2) A method according to claim 2, wherein the disconnection and deactivation in the fifth stage is performed for any access network that no longer has any active flows. ### Claim 10 (depends on 2) A method according to claim 2, wherein the first stage is performed based on context information indicating at least one of a timer event and a location detection, configuration information indicating at least one of a user interface access event and a user interface configuration event, and network state information indicating at least one of a flow initiation and a flow termination. ### Claim 11 (depends on 2) A method according to claim 2, wherein the second stage is performed based on configuration information indicating at least one of a change of profile preference and an access point change, and network state information indicating at least one of an available access point and a unavailable access point. ### Claim 12 (depends on 2) A method according to claim 2, wherein the third stage is performed based on configuration information indicating at least one of a change of domain preference and an change of domain definition, and network state information indicating at least one of a flow initiation and a flow termination. ### Claim 13 (depends on 2) A method according to claim 2, wherein the fourth stage is performed based on network state information indicating at least one of an unavailable access point and an initiated flow. ### Claim 14 (depends on 2) A method according to claim 2, wherein the fifth stage is performed based on network state information indicating at least one of a flow initiation and a flow termination. ### Claim 15 (depends on 2) A method according to claim 2, wherein the processing of the first and fifth stages is performed at the terminal device of a respective user. ### Claim 16 (depends on 2) A method according to claim 2, wherein processing of each of the first, third and fourth stages and at least a partial processing of the second stage is performed at a gateway device, wherein the gateway device comprises an access gateway device. ### Claim 17 (depends on 2) A method according to claim 2, wherein at least a partial processing of the second stage is performed at a service gateway device. ### Claim 18 A policy resolution system including computer-executable instructions embodied on a non-transitory computer-readable medium for execution by a processor for performing policy resolution with interdependent trigger events and policy actions, comprising: a resolution and enforcement mechanism configured to: process separate stages of policy resolution in a chronological order during a policy resolution round, each of the stages handling specific types of trigger events and performing specific types of policy actions, and freeze trigger events which occur during a policy resolution round until the start of the next policy resolution round, wherein an access is selected from a plurality of accesses available to a terminal device. ### Claim 19 An access network apparatus for performing policy resolution with interdependent trigger events and policy actions, the access network comprising: a processor; and a memory unit operatively connected to the processor and including computer-executable instructions configured to perform a process of policy resolution with interdependent trigger events and policy actions, comprising: dividing a policy resolution into separate stages each handling specific types of trigger events and performing specific types of policy actions; processing in a terminal device, at least one of the separate stages in a chronological order during a policy resolution round; and freezing trigger events which occur during a policy resolution round until the start of the next policy resolution round, wherein an access is selected from a plurality of accesses available to the terminal device. ### Claim 20 (depends on 19) An access network apparatus according to claim 19, wherein the access network apparatus is configured to enforce policies transparently. ### Claim 21 (depends on 20) An access network apparatus according to claim 20, wherein the access network apparatus is configured to have policies at least partially enforced at the terminal device by initiating an enforcement signaling with the terminal device. ### Claim 22 (depends on 19) An access network apparatus according to claim 19, wherein the access network apparatus is configured to create access definitions for matching against preference information of users maintained by the access network apparatus. ### Claim 23 (depends on 19) An access network apparatus according to claim 19, wherein the computer-executable instructions are further configured to identify user flows including identifying an end user based on the end user's Internet Protocol address. ### Claim 24 (depends on 19) An access network apparatus according to claim 19, wherein the computer-executable instructions are further configured to identify user flows including code identifying a remote end point based on one of a Uniform Resource Identifier (URI) detected by a Session Initiation Protocol (SIP) proxy, a Domain Name Server (DNS) name detected by a DNS server, and at least one of an Internet Protocol (IP) address and port detected by a border router and a mobility gateway.