# US 2014/0155109 A1 · Subscriber-aware paging > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2014/0155109 A1 - Document ID: US20140155109A1 - Status: Published application - Kind: A1 - Application number: 13/690,365 - Filed: 2012-11-30 - Published: 2014-06-05 - Earliest claimed: 2012-11-30 - Assignees: Cisco Technology, Inc. - Applicants: Cisco Technology, Inc. - Inventors: Maulik VAIDYA; Lingesh MUNAGALA; Arun C. ALEX; Gibson Soon Teck ANG; Sailakshmi MAHALINGAM; Adi Raja MURUGAN; Gaurav VAID - Web page: https://patentgrep.com/patent/US20140155109A1 ## CPC - H04W 68/04: multi-step notification using statistical or historical mobility data - H04W 8/06: Registration at serving network Location Register, VLR or user mobility server - H04W 60/00: Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract This disclosure relates to systems and methods for paging devices in a communication network. A network device providing mobility management through control messaging can be assigned a number of cell sites in multiple tracking areas. The network device such as a mobility management entity (MME) can use a subscriber-aware implementation to provide a hierarchy for contacting a mobile device with a page. The subscriber-aware implementation can be tailored to analyze subscriber activity such as frequency and timing, to page a subset of the total number of cell sites in multiple tracking areas based on the subscriber activity, and to expand the subset after unsuccessful attempts to page the mobile device. ## Claims ### Claim 1 A method comprising: maintaining, at a mobility management entity (MME) in a communication network, a list of eNodeBs from which a user equipment (UE) was actively communicating with the communication network, the communication network including a plurality of eNodeBs arranged into at least one tracking area; receiving a page request for the UE at the MME; sending a first page request to a first set of the eNodeBs in the tracking area at least in part based on the eNodeBs with which the UE was last actively communicating; identifying a second set of eNodeBs to receive a paging request at least in part based on subscriber location activity of the UE, the subscriber location activity including one or more location identifiers associated with the UE, one or more system time stamps of the MME, and a subscriber identifier associated with the UE, and the second set having at least some different eNodeBs than the first set; and sending a second page request to the second set of eNodeBs, if a response is not received after the first page request. ### Claim 2 (depends on 1) The method of claim 1, wherein the location identifiers include at least one of a Tracking Area Code (TAC) or an eNodeB identifier. ### Claim 3 (depends on 1) The method of claim 1, wherein the subscriber location activity further includes a count of the number of times the UE has responded to page requests at eNodeBs associated with the plurality of location identifiers. ### Claim 4 (depends on 1) The method of claim 1, wherein the second set of eNodeBs includes a first subset of eNodeBs from which the UE most frequently responds to paging requests. ### Claim 5 (depends on 4) The method of claim 4, wherein the second set of eNodeBs includes a second subset of eNodeBs from which the UE responded to paging requests most recently, the second subset including at least some different eNodeBs than the first subset. ### Claim 6 (depends on 4) The method of claim 4, wherein the second set of eNodeBs includes eNodeBs from which the UE most frequently responds to paging requests during a window of time, the window of time determined at least in part based on time stamps during which the UE previously responded to paging requests. ### Claim 7 (depends on 1) The method of claim 1, wherein the second set of eNodeBs includes eNodeBs identified at least in part based on a probability that the UE will be associated with a particular location identifier at the current time, based on previous time stamps and previous subscriber location activity. ### Claim 8 (depends on 1) The method of claim 1, wherein the identifying the second set of eNodeBs further comprises sending the subscriber location activity via an interface to a remote analytics node so as to offload analysis of the subscriber location activity; and receiving, from the analytics node, the second set of eNodeBs identified at least in part based on patterns analyzed from the subscriber location activity. ### Claim 9 A mobility management entity (MME) that communicates with at least one eNodeB in a communication network to page a user equipment (UE), and where the communication network includes a plurality of eNodeBs that are arranged into at least one tracking area, the MME comprising: a storage medium configured to store a list of eNodeBs from which the UE was actively communicating with the communication network and a list of eNodeBs identified based on subscriber location activity of the UE within the communication network; a physical interface configured to receive a page request for the UE where the page request includes the tracking area where the UE was last registered, and to send page requests to at least one eNodeB; and a processing unit configured to send page requests selectively to some eNodeBs of the plurality of eNodeBs including initiating a sending of a first page request to at least one eNodeB at least in part based on the list of eNodeBs from which the UE was last actively communicating and initiating a sending of a second page request to a second set of eNodeBs at least in part based on subscriber location activity of the UE, the subscriber location activity including one or more location identifiers associated with the UE, one or more system time stamps of the MME, and a subscriber identifier associated with the UE, and the second set having at least some different eNodeBs than the first set. ### Claim 10 (depends on 9) The MME of claim 9, wherein the location identifiers include at least one of a Tracking Area Code (TAC) or an eNodeB identifier. ### Claim 11 (depends on 9) The MME of claim 9, wherein the subscriber location activity further includes a count of the number of times the UE has responded to page requests at eNodeBs associated with the plurality of location identifiers. ### Claim 12 (depends on 9) The MME of claim 9, wherein the processing unit is further configured to send the subscriber location activity to an analytics node so as to offload analysis of the subscriber location activity; and to receive, from the analytics node, the second set of eNodeBs identified at least in part based on patterns analyzed from the subscriber location activity. ### Claim 13 (depends on 9) The MME of claim 9, wherein the processing unit is configured to process packets received on the physical interface in response to subscriber events, the subscriber events including the UE attaching to the communications network, the UE detaching from the communications network, the UE sending a tracking area update (TAU), a handover of the UE, or processing packets at periodic time intervals. ### Claim 14 (depends on 9) The MME of claim 9, wherein the second set of eNodeBs includes eNodeBs from which the UE most frequently responds to paging requests or eNodeBs from which the UE responded to paging requests most recently. ### Claim 15 An analytics node comprising: a storage medium configured to store a list of eNodeBs from which a user equipment (UE) was actively communicating with a communication network, where the communication network includes a plurality of eNodeBs that are arranged into at least one tracking area; a physical interface configured to receive, from a remote mobility management entity (MME), a subscriber location activity update, so as to offload analysis of subscriber location activity from the remote MME, where the MME communicates with at least one eNodeB in the communication network to page the UE, and where the subscriber location activity includes one or more location identifiers associated with the UE, one or more system time stamps of the MME, and a subscriber identifier associated with the UE; and a processing unit configured to identify a first set of eNodeBs to receive a paging request from the remote MME at least in part based on the list of eNodeBs from which the UE was last actively communicating; identify a second set of eNodeBs to receive a paging request from the remote MME at least in part based on the subscriber location activity, the second set having at least some different eNodeBs than the first set; and send the first and second sets of eNodeBs over the physical interface to the remote MME. ### Claim 16 (depends on 15) The analytics node of claim 15, wherein processing unit is further configured to aggregate subscriber location activity from a plurality of UEs, and to identify the second set of eNodeBs based on the aggregated subscriber location activity. ### Claim 17 (depends on 15) The analytics node of claim 15, wherein the subscriber location activity further includes a count of the number of times the UE has responded to page requests at eNodeBs associated with the plurality of location identifiers. ### Claim 18 (depends on 15) The analytics node of claim 15, wherein the second set of eNodeBs includes eNodeBs from which the UE most frequently responds to paging requests or eNodeBs from which the UE responded to paging requests most recently. ### Claim 19 (depends on 15) The analytics node of claim 15, wherein the second set of eNodeBs includes eNodeBs from which the UE most frequently responds to paging requests during a window of time, the window of time determined at least in part based on time stamps during which the UE previously responded to paging requests. ### Claim 20 (depends on 15) The analytics node of claim 15, wherein the second set of eNodeBs includes eNodeBs identified at least in part based on a probability that the UE will be associated with a particular location identifier at the current time, based on previous time stamps and previous subscriber location activity.