DETAILED ACTION
Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
NOTICE for all US Patent Applications filed on or after March 16, 2013
In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the
rationale supporting the rejection, would be the same under either status.
Claim Rejections - 35 USC § 102
The following is a quotation of the appropriate paragraphs of AIA 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless -
(a)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale or otherwise available to the public before the effective filing date of the claimed invention.
Claims 1-4, 6-8, 10-11, 13-18 and 20 are rejected under 35 U.S.C. 102 (a)(1) as anticipated by Mackenzie et al. (US 20210258244 A1, hereinafter ‘MACKENZIE’).
Regarding claim 1, MACKENZIE teaches a system for user device handoff within a telecommunications network (
Fig. 2, Network 200 with UE 106,
[0035] FIG. 2 shows a network 200 similar to that of network 100. Coverage in network 200 is provided by 3 macrocells 202, 204 and 206, two picocells 210 and 212, and a home eNodeB (HeNB) 220. The ovals, give an approximation of the coverage of each cell. There is an access point or gateway 220a associated with the HeNB 220, though the base stations corresponding to the other cells have been omitted for simplicity.
[0036] ….. The UE 106 starts at location A. This is a common location for this UE to be at, and may be the user's office for example.), the system comprising:
at least one processor (
Figs. 2A, macrocells 202, 204 and 206, two picocells 210 and 212, home eNodeB (HeNB) 220, and UE 106,
See also Fig. 3 UE 106 with processor 302);
at least one memory coupled to the at least one processor, the memory having computer-executable instructions stored thereon that, when executed by the at least one processor (
Figs. 2A, macrocells 202, 204 and 206, two picocells 210 and 212, home eNodeB (HeNB) 220, and UE 106,
See also Fig. 3, UE 106 with processor 302, program module 310 and Data Store 320,
[0030] FIG. 3 shows a block diagram of the UE 106 comprising a processor 302, program module 310 and a data store 320. The program module 310 comprises various programs for running on the processor 302, which include a control module 312, an additional action module 314, and a connection module 316. The data store 320 is used to store various data including measurements and statistics, and can take the form of memory such as solid state memory. For example, data such as the UE's cell connection history, cell signal strength, predicted UE route, historical route data, and so on can be stored in the data store 320.
[0071] Exemplary embodiments of the disclosure are realized, at least in part, by executable computer program code which may be embodied in an application program data representing the program modules in FIG. 3. When such computer program code is loaded into the memory of the processor 302 for execution, it provides a computer program code structure which is capable of performing at least part of the methods ), cause the system to:
identify a user device connected to the telecommunications network via a cell of a set of cells (
Fig. 2, [0035] Coverage in network 200 is provided by 3 macrocells 202, 204 and 206, two picocells 210 and 212, and a home eNodeB (HeNB) 220. The ovals, give an approximation of the coverage of each cell. There is an access point or gateway 220a associated with the HeNB 220, though the base stations corresponding to the other cells have been omitted for simplicity.
[0036] In this example the HeNB 220 is the preferred cell for the UE 106. The UE 106 starts at location A. This is a common location for this UE to be at, and may be the user's office for example.
[0038] The UE 106 starts its journey from location A. The control module 312 is aware that the UE 106 is in the area of location A, based on triangulation of neighboring cell measurements. The UE 106 now moves along route C which will end in location B, a location with HeNB 220. The UE 106 may switch between connected and idle states along this route.
See also [0041] When the UE 106 arrives at point 3, the UE 312 moves out of coverage of macrocell 206, which was the serving cell.
(Construed while in Cell Coverage 206a which include location A, UE 106 connects with corresponding serving macrocell 206 cell in Cell Coverage 206a and control module 312 identify connection to the telecommunications network via the macrocell 206));
detect a present location of the user device (
[0038] The UE 106 starts its journey from location A. The control module 312 is aware that the UE 106 is in the area of location A, based on triangulation of neighboring cell measurements. The UE 106 now moves along route C…..);
access historical data indicating one or more past locations of the user device (
[0037] Three routes that the UE 106 has taken when leaving location A are also shown as lines 225, 226 and 227. Route A 225 is represented by a dot dash line, route B 226 is represented by a dashed line, and route C 227 a dotted line. These routes are all routes associated with location A learned over time by the control module 312 using measurements available to the UE 106. They are likely to be the most commonly taken routes from location A. These routes are stored in the data store 320 and can be updated over time.
[0038] The UE 106 starts its journey from location A. The control module 312 is aware that the UE 106 is in the area of location A, based on triangulation of neighboring cell measurements. The UE 106 now moves along route C which will end in location B, a location with HeNB 220.);
predict a future location of the user device based on the historical data and the present location of the user device (
See [0037] cited above.
[0038] The UE 106 starts its journey from location A. The control module 312 is aware that the UE 106 is in the area of location A, based on triangulation of neighboring cell measurements. The UE 106 now moves along route C which will end in location B, a location with HeNB 220. The UE 106 may switch between connected and idle states along this route. When in connected mode, the serving cell will configure measurements to be made by the UE 106. ….. These measurements are stored in the data store 320 of the UE 106. The control module 312 analyses these measurements to determine how likely the UE 106 is to be within range of the HeNB 220. Based on the probability of being within range, the control module 312 can coordinate further measurements or actions to be made (by the additional action module 314) to locate the HeNB. As such, any additional measurements or actions are only made when necessary.
[0040] If measurements are made between point 1 and point 2, then the control unit 312 can deduce that the UE 106 is either on route B or route C, but is not on route A. The control unit 312 thus determines that the probability of being with range of the preferred cell, the HeNB 220, is still very low, and so decides that no additional measurements or actions are required.
[0047] The control unit 312 can use signal strength measurements associated with connected cells to predict which path the UE 106 is on, and progress along that path. Whilst this alone cannot be used for triangulation, it can be used to indicate progress along potential routes. For example, as the UE 106 moves along route C, the UE 106 will have a strong signal from the serving cell, macrocell 206, which eventually becomes weak. The UE 106 is then served by picocell 212. The signal from picocell 212 will initially be strong, then become weak again before the UE 106 nears the end of the route. The timing of these changes in signal strength can be used to determine the likelihood of being on a particular route (as well as for estimating a speed along a route), and subsequently to determine the probability of the UE being within range of the preferred cell.);
identify at least one cell of the set of cells based on the predicted future location (
[0038] The UE 106 now moves along route C which will end in location B, a location with HeNB 220.); and
cause the user device to connect to the at least one cell (
[0036] In this example the HeNB 220 is the preferred cell for the UE 106. The UE 106 starts at location A. This is a common location for this UE to be at, and may be the user's office for example.
[0046] Once the control unit 312 determines that the UE 106 is in the coverage area of the HeNB 220, it instructs the connection module 316 to start handover to the HeNB 220.
[0069] …. If the UE 106 is in connected mode, then the connection module 316 can inform the network that the preferred cell is in range, so that the network can arrange for handover to the preferred cell to take place.).
Regarding claim 2, MACKENZIE teaches the system of claim 1, wherein to predict the future location of the user device, the computer-executable instructions, when executed by the at least one processor, further cause the system to:
determine at least one of a speed of the user device and a direction of travel of the user device (
See [0036, 0037] cited above for claim 1.
[0047] The control unit 312 can use signal strength measurements associated with connected cells to predict which path the UE 106 is on, and progress along that path. Whilst this alone cannot be used for triangulation, it can be used to indicate progress along potential routes. For example, as the UE 106 moves along route C, the UE 106 will have a strong signal from the serving cell, macrocell 206, which eventually becomes weak. The UE 106 is then served by picocell 212. The signal from picocell 212 will initially be strong, then become weak again before the UE 106 nears the end of the route. The timing of these changes in signal strength can be used to determine the likelihood of being on a particular route (as well as for estimating a speed along a route), and subsequently to determine the probability of the UE being within range of the preferred cell.), and
predict the future location of the user device based on the historical data, the present location of the user device, and at least one of the speed and the direction of travel (
See [0036, 0037, 0047] cited above).
Regarding claim 3, MACKENZIE teaches the system of claim 1, wherein to predict the future location of the user device, the computer-executable instructions, when executed by the at least one processor, further cause the system to:
identify, based on the historical data one or more of:
at least one location at which the user device was located two or more times (
Fig. 2, Point 1, Point 2,
[0037] Three routes that the UE 106 has taken when leaving location A are also shown as lines 225, 226 and 227. Route A 225 is represented by a dot dash line, route B 226 is represented by a dashed line, and route C 227 a dotted line. These routes are all routes associated with location A learned over time by the control module 312 using measurements available to the UE 106.
See also [0038-0040] Location A, Point 1 …. Point 2);
at least one amount of time during which the user device was located at one or more locations (
[0035] home eNodeB (HeNB) 220
[0036] Location A … office
[0038] Location A …. Location B, a location with HeNB 220); and
at least one travel path of the user device (
See [0037] route A 225 … route B 226… Route C 227);
detect a current time (
[0047] …. The timing of these changes in signal strength can be used to determine the likelihood of being on a particular route (as well as for estimating a speed along a route) …); and
predict the future location of the user device based on the current time, the historical data, and the present location of the user device (
See [0037, 0038, 0047] cited above for claim 1, disclosing location, timing and speed gets monitored to predict route/path and corresponding future location along the predicted path which is one of the stored route).
Regarding claim 4, MACKENZIE teaches the system of claim 1, wherein to identify at least one cell of the set of cells, the computer-executable instructions, when executed by the at least one processor, further cause the system to:
predict a path of the user device based on the predicted future location, the historical data, and the present location of the user device (
See [0037, 0038, 0047] cited above for claim 1 );
identify a plurality of cells based on the predicted path, the plurality of cells including the at least one cell (
See [0035, 0037, 0047] cited for claim 1); and
determine one or more times at which the user device is to connect to the at least one cell (
See [0035] Coverage in network 200 is provided by 3 macrocells 202, 204 and 206, two picocells 210 and 212, and a home eNodeB (HeNB) 220. The ovals, give an approximation of the coverage of each cell. …
[0038] The UE 106 now moves along route C which will end in location B, a location with HeNB 220. The UE 106 may switch between connected and idle states along this route. When in connected mode, the serving cell will configure measurements to be made by the UE 106.
[0041] When the UE 106 arrives at point 3, the UE 312 moves out of coverage of macrocell 206, which was the serving cell.).
Regarding claim 6, MACKENZIE teaches the system of claim 1, wherein to cause the user device to connect to the at least one cell, the computer-executable instructions, when executed by the at least one processor, further cause the system to:
determine a time at which the user device is to connect to the at least one cell based on the historical data and the present location of the user device (
Fig. 4, [0060] In 400, the preferred cells list is stored in the data store 320. As described above, the preferred cells list is a list of preferred cells associated with the UE 106, and in this example contains the identity of the HeNB 220. In 402, the control unit 312 starts a timer.
[0062] The data store 320 also stores a shortlist of learned routes. In 406, the control unit 312 processes the measurements from 404 to determine whether the UE 106 might be on one or more of the shortlisted routes.
[0063] The control unit 312 then evaluates the routes the UE is likely to be on, and uses that to determine the probability of the UE 106 being in range of the preferred cell in 408.
[0064] In 410, the control unit 312 then checks to see if the UE 106 is within range of the preferred cell based on the determined probability from 408. If the UE 106 is in range, then the control unit 312 instructs the connection module 316 to either select or connect to the preferred cell in 411.
[0065] If in 410 the control unit 312 finds that the UE 106 is not within range of the preferred cell, processing passes to 412. …. configuring additional network measurements, activating WiFi, activating GPS, and changing the duration of the timer for the next evaluation (typically reducing the timer or interval between evaluations as the probability of being within range of the preferred cell increases)
[0067] As described, the timer value can be adjusted according to the probability of the UE 106 being within range of the preferred cell, with the timer being reduced if the probability is high. Thus, the process is repeated with increasing frequency as the probability of being within range of the preferred cell increases. Furthermore, the timer value can be adjusted depending on where the UE 106 is on the determined route, and further on a predicted velocity along that route. Thus, if the UE 106 is moving quickly (e.g. in a car), then the timer can be set for a short duration (e.g. 10 seconds) to ensure the process is repeated at shorter intervals, whereas if the UE 106 is moving very slowly (e.g. walking on foot), then the timer can be set for a long duration (e.g. 5 minutes), especially if the UE 106 is still far away from the preferred cell. Put another way, the predicted route and speed along that route taken by the UE can be predicted, and used to determine the timer value (and thus interval between actions).).
Regarding claim 7, MACKENZIE teaches the system of claim 1, wherein to predict the future location, the computer-executable instructions, when executed by the at least one processor, further cause the system to:
identify one or more measures of the quality of networking services provided to the user device (
[0047] The control unit 312 can use signal strength measurements associated with connected cells to predict which path the UE 106 is on, and progress along that path. Whilst this alone cannot be used for triangulation, it can be used to indicate progress along potential routes. For example, as the UE 106 moves along route C, the UE 106 will have a strong signal from the serving cell, macrocell 206, which eventually becomes weak. The UE 106 is then served by picocell 212. The signal from picocell 212 will initially be strong, then become weak again before the UE 106 nears the end of the route. The timing of these changes in signal strength can be used to determine the likelihood of being on a particular route (as well as for estimating a speed along a route), and subsequently to determine the probability of the UE being within range of the preferred cell.
(Cell signal strength is one metric for network service quality as known in the art));
determine whether the user device is to connect to a different cell than the cell to which the user device is currently connected based on the one or more measures of the quality of networking services provided to the user device (
See [0047] as the UE 106 moves along route C, the UE 106 will have a strong signal from the serving cell, macrocell 206, which eventually becomes weak. The UE 106 is then served by picocell 212.); and
in response to a determination that the user device is to connect to a different cell, predict the future location of the user device based on the historical data and the present location of the user device (
[0037] route A …. route B …. route C ….. learned over time by the control module 312 using measurements available to the UE 106 …
[0038] The UE 106 starts its journey from location A. The control module 312 is aware that the UE 106 is in the area of location A, based on triangulation of neighboring cell measurements. The UE 106 now moves along route C which will end in location B, a location with HeNB 220. The UE 106 may switch between connected and idle states along this route.
[0047] as the UE 106 moves along route C, the UE 106 will have a strong signal from the serving cell, macrocell 206, which eventually becomes weak. The UE 106 is then served by picocell 212.).
Regarding claim 8, MACKENZIE teaches the system of claim 1, wherein to identify the at least one cell, the computer-executable instructions, when executed by the at least one processor, further cause the system to:
identify one or more measures of the quality of networking services provided to the user device (
[0047] The control unit 312 can use signal strength measurements associated with connected cells to predict which path the UE 106 is on, and progress along that path. Whilst this alone cannot be used for triangulation, it can be used to indicate progress along potential routes. For example, as the UE 106 moves along route C, the UE 106 will have a strong signal from the serving cell, macrocell 206, which eventually becomes weak. The UE 106 is then served by picocell 212. The signal from picocell 212 will initially be strong, then become weak again before the UE 106 nears the end of the route.);
determine whether the user device is to connect to an identified cell based on the one or more measures of the quality of networking services provided to the user device and the predicted future location of the user device (
[0033] the control module 312 monitors measurements that have been made by the UE 106, including the attachment history of the UE 106 (i.e. the cells previously connected to and the associated times) stored in the data store 320. The control module 312 determines the probability of the UE 106 being within range (for a connection) of a preferred cell. This can be done by predicting the path or route the UE 106 is on …
[0037] route A …. route B …. route C ….. learned over time by the control module 312 using measurements available to the UE 106 …
[0038] The UE 106 starts its journey from location A. The control module 312 is aware that the UE 106 is in the area of location A, based on triangulation of neighboring cell measurements. The UE 106 now moves along route C which will end in location B, a location with HeNB 220.
[0046] Once the control unit 312 determines that the UE 106 is in the coverage area of the HeNB 220, it instructs the connection module 316 to start handover to the HeNB 220.
[0047] as the UE 106 moves along route C, the UE 106 will have a strong signal from the serving cell, macrocell 206, which eventually becomes weak. The UE 106 is then served by picocell 212. The signal from picocell 212 will initially be strong, then become weak again before the UE 106 nears the end of the route); and
based on a determination that the device is not to connect to the identified cell, prevent the user device from connecting to the identified cell until it is determined that the user device is to connect to the identified cell (
[0046] Once the control unit 312 determines that the UE 106 is in the coverage area of the HeNB 220, it instructs the connection module 316 to start handover to the HeNB 220.
[0047] as the UE 106 moves along route C, the UE 106 will have a strong signal from the serving cell, macrocell 206, which eventually becomes weak. The UE 106 is then served by picocell 212. The signal from picocell 212 will initially be strong, then become weak again before the UE 106 nears the end of the route).
Regarding claim 10, the claim is interpreted mutatis mutandis of claim 1, and rejected for the same reason as set forth for claim 1.
Regarding claim 11, the claim is interpreted and rejected for the same reason as set forth for claim 4.
Regarding claim 13, the claim is interpreted and rejected for the same reason as set forth for claim 7.
Regarding claim 14, the claim is interpreted and rejected for the same reason as set forth for claim 3.
Regarding claim 15, the claim is interpreted mutatis mutandis of claim 1, and rejected for the same reason as set forth for claim 1.
Regarding claim 16, the claim is interpreted and rejected for the same reason as set forth for claim 2.
Regarding claim 17, the claim is interpreted and rejected for the same reason as set forth for claim 3.
Regarding claim 18, the claim is interpreted and rejected for the same reason as set forth for claim 4.
Regarding claim 20, the claim is interpreted and rejected for the same reason as set forth for claim 7.
Claim Rejections - 35 USC § 103
The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action:
A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made.
This application currently names joint inventors. In considering patentability of the claims the examiner presumes that the subject matter of the various claims was commonly owned as of the effective filing date of the claimed invention(s) absent any evidence to the contrary. Applicant is advised of the obligation under 37 CFR 1.56 to point out the inventor and effective filing dates of each claim that was not commonly owned as of the effective filing date of the later invention in order for the examiner to consider the applicability of 35 U.S.C. 102(b)(2)(C) for any potential 35 U.S.C. 102(a)(2) prior art against the later invention.
Claims 5, 12 and 19 are rejected under 35 U.S.C. 103 being unpatentable over Mackenzie et al. (US 20210258244 A1, hereinafter ‘MACKENZIE’) in view of Noh et al. (KR 100753845 B1, hereinafter ‘NOH’).
Regarding claim 5, MACKENZIE teaches the system of claim 4.
MACKENZIE does not explicitly disclose wherein to cause the user device to connect to the at least one cell, the computer-executable instructions, when executed by the at least one processor, further cause the system to:
for each respective cell of the at least one cell:
cause the respective cell to reserve networking resources for the user device before a time at which the user device is to connect to the respective cell.
In an analogous art, NOH teaches wherein to cause the user device to connect to the at least one cell, the computer-executable instructions, when executed by the at least one processor, further cause the system to:
for each respective cell of the at least one cell:
cause the respective cell to reserve networking resources for the user device before a time at which the user device is to connect to the respective cell (
Page 19 Paragraph 2- Page 20 Paragraph 1:
After the procedure (P300) in which the access network control unit and CNMC collect the relevant information in advance as described above, a mobile terminal with multiple interfaces detects that a handover will occur through signal strength, etc. (P301) and transmits terminal information, including its own location information using GPS, to the access network control unit (S305 to S306). At this time, the access network control unit that has received information about the mobile terminal uses the location information {Vector) of the terminal and the information stored in the location management control unit {401} of the access network control unit (see Fig. 6} to predict which direction the mobile terminal will move to and determine whether it is an intra-network handover or an inter-network handover {P302}. If it is a network handover, the access network control unit performs preliminary work (resource reservation and pre-authentication) for the router and access point {P303} and informs the mobile terminal of the information of the router and access point, thereby enabling a seamless handover.
Page 21 Paragraph 1:
At this time, the new access network performs pre-authentication for mobile terminals and resource reservation work to support QoS for existing mobile terminals (P305). This not only allows mobile terminals to naturally receive the real-time services they received from the previous network even after the handover when moving to a new network ...).
Therefore, it would have been obvious to one of ordinary skill in the art, before the effective filing date of the claimed invention, to take the technique of advance resource reservation for predicted UE handover of NOH to the method of predicting location along mobility routes based on historical data of a UE of MACKENZIE in order to take the advantage of a technique for seamless handover and extending battery life of UE (NOH: Page 20 Paragraph 1).
Regarding claim 12, the claim is interpreted and rejected for the same reason as set forth for claim 5.
Regarding claim 19, the claim is interpreted and rejected for the same reason as set forth for claim 5.
Claim 9 is rejected under 35 U.S.C. 103 being unpatentable over Mackenzie et al. (US 20210258244 A1, hereinafter ‘MACKENZIE’) in view of Ali Parichehrehteroujeni et al. (US 20250267538 A1 with priority of us-provisional-application US 63270429, hereinafter ‘ALI’).
Regarding claim 9, MACKENZIE teaches the system of claim 1.
MACKENZIE does not explicitly disclose wherein to detect the present location of the user device, the computer-executable instructions, when executed by the at least one processor, further cause the system to:
determine an altitude of the user device.
In an analogous art, ALI teaches wherein to detect the present location of the user device, the computer-executable instructions, when executed by the at least one processor, further cause the system to:
determine an altitude of the user device (
[0244] Predicting UE's location is a part for mobility optimisation, as many radio resource management (RRM) actions related to mobility (e.g. selecting handover target cells) can benefit from the predicted UE location/trajectory.
[0255] Step 2. Model Inference. Required measurements are leveraged into Model Inference to output the prediction, e.g. UE trajectory prediction, target cell prediction, target NG-RAN node prediction, etc.
[0256] Step 3. According to the prediction, recommended actions or configuration are executed for Mobility Optimization.
[0257] In some embodiments, the following data is required as input data for mobility optimization.
[0258] Input Information from UE: (i) UE historical location information from MDT, e.g., Latitude, longitude, altitude, cell ID; (ii) Radio measurements related to serving cell and neighbouring cells associated with UE location information, e.g., RSRP, RSRQ, SINR; (iii) UE Mobility history information; (iv) Moving velocity; (v) predicted traffic; (vi) Trajectory information; (vii) RAN visible QoE metrics e.g., buffer level.).
Therefore, it would have been obvious to one of ordinary skill in the art, before the effective filing date of the claimed invention, to take the technique of using UE historical location information for location prediction of ALI to the method of predicting location along mobility routes based on historical data of a UE of MACKENZIE in order to take the advantage of a technique for UE for mobility optimization determining which is the best mobility target for maximisation of efficiency and performance (ALI: [0244, 0257]).
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure:
Nair et al. (US 20240406831 A1), describing First Node, Device And Methods Performed Thereby For Managing One, More Indications
Conceicao et al. (US 20240381222 A1), describing METHODS AND APPARATUSES FOR DATA FORWARDING IN WIRELESS COMMUNICATIONS
Svennebring et al. (US 20230308199 A1), describing LINK PERFORMANCE PREDICTION USING SPATIAL LINK PERFORMANCE MAPPING
Albasheir et al. (US 20220312293 A1), describing METHODS AND SYSTEMS FOR SELECTING A GATEWAY NODE TO SUPPORT HANDOVER IN A WIRELESS COMMUNICATION NETWORK
Kozhaya et al. (US 20220150666 A1), describing INTELLIGENT DYNAMIC COMMUNICATION HANDOFF FOR MOBILE APPLICATIONS
Szilagyi et al. (US 20200396658 A1), describing TERMINAL DEVICE SPECIFIC HANDOVER PARAMETERS
Lin et al. (US 20200169935 A1), describing CELLULAR NETWORK HANDOFF PLANNING
Meredith et al. (US 20190200267 A1), describing CONTROL OF WIRELESS FIDELITY ACCESS FOR 5G OR OTHER NEXT GENERATION NETWORK
Mythri Hunukumbure et al. (US 20170311216 A1), describing GROUP HANDOVER WITH MOVING CELLS
Hamilton et al., (US 20160014648 A1), describing TECHNIQUES FOR IMPROVED ALLOCATION OF NETWORK RESOURCES USING GEOLOCATION AND HANDOVER MANAGEMENT
Quick, JR et al. (US 20150038180 A1), describing PAGING AREA REDUCTION BASED PREDICTIVE MOBILITY
Ahmed et al., describing Efficient Handover in LTE-A by Using Mobility Pattern History and User Trajectory Prediction
Any inquiry concerning this communication or earlier communications from the examiner should be directed to SHAH M RAHMAN whose telephone number is (571)272-8951. The examiner can normally be reached 9:30AM-5:30PM PST.
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, UN C CHO can be reached at 571-272-7919. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/SHAH M RAHMAN/Primary Examiner, Art Unit 2413