Dave's Patent Content Factory
Applications
Terms
Paragraphs
Claims
Docket
Logout
About
New Paragraph
Paragraphs
Search Content
Para #
Notes
Any Field
Search
Clear
Actions
Matter
Content
Para #
Notes
Modified
View
Edit
Delete
KBR-1 1400.2.623
The method of claim 12, wherein the trigger event comprises a change in one or more factors that define the context.
163
Added by DJM 2 2022
2/25/22, 12:00 AM
View
Edit
Delete
KBR-1 1400.2.623
The method of claim 12, wherein the trigger event comprises the route changing to an alternative route.
162
Added by DJM 2 2022
2/25/22, 12:00 AM
View
Edit
Delete
KBR-1 1400.2.623
The method of claim 12, wherein the trigger event comprises the navigation module leaving a waypoint along the route.
161
Added by DJM 2 2022
2/25/22, 12:00 AM
View
Edit
Delete
KBR-1 1400.2.623
To manage the orientation mode, the system 500 may use the context module 520. The context module 520 determines a context 400 for a route to be navigated by a user. As discussed above, the context module 520 may reference one or more factors (e.g., example factors 502-524) to determine the context 400. Determining a particular context 400 and/or orientation mode may include evaluating certain weights or priorities for the factors. Alternatively, or in addition, a user may indicate a preference or set a parameter that identifies a particular context 400 for a given set of one or more factors or as a default context.
109
Added by DJM 2 2022
2/25/22, 12:00 AM
View
Edit
Delete
KBR-1 1400.2.623
In still another example, an internal trigger event 506a may be created, or triggered, when user input is received relating to orientation mode. For example, referring to Figure 1A, a user may provide user input by activating drop-down list 116 and selecting a different orientation mode than a current orientation mode. In this example, a user may select a Heading Up orientation as their desired orientation mode rather than a North Up orientation mode. Such use input may trigger an internal trigger event 506a and the trigger module 508 may coordinate with the context module 520, orientation mode module 530, and/or change orientation mode module 550 to effectuate the change.
119
Added by DJM 2 2022
2/25/22, 12:00 AM
View
Edit
Delete
KBR-1 1400.2.623
In another example, an internal trigger event 506a may be created, or triggered, when there is a change in one or more factors that were used to define the context 400. For example, a change in the weather, a change in the role of the user, a change in the route, a revised route, a change in the mode of transportation, or the like.
118
Added by DJM 2 2022
2/25/22, 12:00 AM
View
Edit
Delete
KBR-1 1400.2.623
Those of skill in the art will appreciate that various examples of internal trigger events 506a and/or external trigger events 506b may exist each of which is within the scope of the present disclosure. In one example, an internal trigger event 506a may be created, or triggered, when a user approaches a particular waypoint or type of waypoint (e.g., within x feet of the waypoint). In another example, an internal trigger event 506a may be created, or triggered, when a user leaves a particular waypoint or type of waypoint (e.g., beyond x feet of the waypoint).
117
Added by DJM 2 2022
2/25/22, 12:00 AM
View
Edit
Delete
KBR-1 1400.2.623
In the illustrated embodiment, the trigger events 506 can be internal trigger events 506a or internal trigger events 506a. Internal trigger events 506a may be trigger events that are caused by factors, attributes, parameters, or characteristics that can be monitored, tracked, and/or sensed by the navigation module 510. External trigger events 506b may be trigger events that are not caused by factors, attributes, parameters, or characteristics that can be monitored, tracked, and/or sensed by the navigation module 510.
116
Added by DJM 2 2022
2/25/22, 12:00 AM
View
Edit
Delete
KBR-1 1400.2.623
In the illustrated embodiment, the change orientation mode module 550 may include a trigger module 508 that awaits trigger events. In certain embodiments, the trigger module 508 listens for trigger events. The trigger module 508 may monitor one or more factors, aspects, sensors, and/or other parameters to determine when a trigger event 506 happens. The trigger module 508 is configured to detect the trigger event 506 and initiate a response to the trigger event 506. In certain embodiments, the trigger module 508 may activate the context module 520 to determine a new context 400 and/or the trigger module 508 may activate the orientation mode module 530 to determine a new orientation mode in response to one or more trigger events 506.
115
Added by DJM 2 2022
2/25/22, 12:00 AM
View
Edit
Delete
KBR-1 1400.2.623
A "trigger" or "trigger event" may refer to any suitable event, condition, circumstance, and/or set of circumstances or change therein for which a monitor, listener, or receiver is configured to respond to based on such event, change, and/or set of circumstances. Examples trigger events include, but are not limited to, internal trigger events, external trigger events, milestone trigger events, and the like among other events and/or circumstances that are possible and contemplated herein.
114
Added by DJM 2 2022
2/25/22, 12:00 AM
View
Edit
Delete
KBR-1 1400.2.623
When the navigation module 510 is operating to assist a user with navigation, the navigation module 510 may use the change orientation mode module 550 to change the orientation mode for navigation module 510 from a current, or first, orientation mode to another, or second, orientation mode provided by the orientation mode module 530. The change orientation mode module 550 may operate in response to various inputs, prompts, states, and/or conditions as a user navigates a route. In one embodiment, the change orientation mode module 550 may operate in response to a change in one of the factors that influenced the context 400. In another embodiment, the change orientation mode module 550 may operate in response to a trigger event 506.
113
Added by DJM 2 2022
2/25/22, 12:00 AM
View
Edit
Delete
KBR-1 1400.2.623
The orientation mode module 530 may coordinate with one of the set orientation mode module 540 and the change orientation mode module 550 to set an orientation mode for the navigation module 510. When the navigation module 510 is first initiated to assist a user with navigation, the navigation module 510 may use the set orientation mode module 540 to set the orientation mode for navigation module 510 to a determined orientation mode (e.g., a first orientation mode) provided by the orientation mode module 530. The set orientation mode module 540 may provide a selected orientation mode 504 to an I/O interface 210 or I/O interface 360. The I/O interface 360 may provide map data on a display device 216 according to the selected orientation mode 504.
112
Added by DJM 2 2022
2/25/22, 12:00 AM
View
Edit
Delete
KBR-1 1400.2.623
The context module 520 may coordinate with the orientation mode module 530 to determine an orientation mode for particular context 400. In certain embodiments, the context module 520 may determine an orientation mode from a set of orientation modes 502. Examples of orientation modes that may be part of the set of orientation modes 502 include a north up orientation mode, heading up orientation mode, course up orientation mode, and the like. In certain embodiments, the context 400 determined may be associated with a particular orientation mode. Alternatively, or in addition, one or more sets of contexts 400 may be associated with one or more orientation modes. The relationship between a context 400 and an orientation mode may be determined algorithmically or by way of retrieving an orientation mode associated with a context 400 using a repository.
110
Added by DJM 2 2022
2/25/22, 12:00 AM
View
Edit
Delete
KBR-1 1400.2.623
In certain embodiments, certain internal trigger events 506a such as receiving user input indicating a different desired orientation mode may lead to other changes in the behavior of the navigation module 510. In one example, a single internal trigger event 506a that is user input indicating a different desired orientation mode may cause the navigation module 510 to change an orientation mode associated with a current context 400 to change the orientation mode to the orientation mode indicated by the user input.
120
Added by DJM 2 2022
2/25/22, 12:00 AM
View
Edit
Delete
KBR-1 1400.2.623
Among one or more of its other features, functions, aspects and attributes, the navigation module 510 manages an orientation mode for the system 500. In other words, the navigation module 510 manages a contextual navigation direction orientation used in presenting information to a user. "Contextual navigation direction orientation" refers generally to features, functions, methods, apparatuses, devices, circuits, modules, components, firmware, and/or software configured to manage an orientation for navigational direction information based on a context for the navigation.
108
Added by DJM 2 2022
2/25/22, 12:00 AM
View
Edit
Delete
KBR-1 1400.2.623
Figure 5 depicts a system 500 for setting an orientation mode, according to one or more examples of the present disclosure. Figure 5 may include similar modules, code, components, parts, devices, apparatus, features, and aspects as those disclosed and described in relation to Figures 3 and 4, however the members of the system 500 may include additional and/or alternative modules, code, components, parts, devices, apparatus, features, and aspects. Accordingly, the system 500 includes a navigation module 510, a context module 520, an orientation mode module 530, and a set orientation mode module 540. Alternatively, or in addition, the system 500 may also include a change orientation mode module 550 and/or a prediction module 560.
107
Added by DJM 2 2022
2/25/22, 12:00 AM
View
Edit
Delete
KBR-1 1400.2.623
Specifically, if a user has navigated through a particular five-points intersection 106k over five hundred times, the history factor 424 may have a first weight and/or preference for a certain orientation mode. Alternatively, or in addition, if a user navigates to a particular locale for the first time, for example, the history factor 424 may have a second weight and/or preference for a certain orientation mode. As with the other factors, the degree to which the history factor 424 defines or influences the context 400 can be predefined based on a set of default settings. Alternatively, or in addition, the degree to which the history factor 424 defines or influences the context 400 can be set, determined, or adjusted by a user.
106
Added by DJM 2 2022
2/25/22, 12:00 AM
View
Edit
Delete
KBR-1 1400.2.623
In one example, the context 400 may be influenced by a history factor 424. The history factor 424 is a factor that is based on how often a user has taken a particular route, included a particular waypoint along the route, visited a particular destination, and/or been to a locale that includes the route. The history factor 424 may be referred to as a navigation history or visit history. "Navigation history" or “visit history” refers to a set of data that identifies one or more places, waypoints, or locations, a person or user has visited and/or navigated through or to, in the past. "Locale" refers to a specific location and the areas immediately surrounding the specific location. Often a locale has a particular set of attributes that may relate to its geography, scenery, climate, or the like. Data for the history factor 424 may be stored by a navigation apparatus 220 in storage 214. The history factor 424 can include whether or not a user has visited a locale and/or how often a user has visited a locale, waypoint, or taken a particular route.
105
Added by DJM 2 2022
2/25/22, 12:00 AM
View
Edit
Delete
KBR-1 1400.2.623
Specifically, if a user defines a route for the navigation that is the shortest and most efficient, the route factor 422 may have a first weight and/or preference for a certain orientation mode. Alternatively, or in addition, if a user defines a route for the navigation that is the longest and most time consuming, for example, the route factor 422 may have a second weight and/or preference for a certain orientation mode. As with the other factors, the degree to which the route factor 422 defines or influences the context 400 can be predefined based on a set of default settings. Alternatively, or in addition, the degree to which the route factor 422 defines or influences the context 400 can be set, determined, or adjusted by a user.
104
Added by DJM 2 2022
2/25/22, 12:00 AM
View
Edit
Delete
KBR-1 1400.2.623
In one example, the context 400 may be influenced by a route factor 422. The route factor 422 is a factor that is based on a particular route for the navigation. Certain routes may take the fastest most efficient route from the point of origin to the destination. Other routes may include multiple waypoints, travel to points that increase the length of time or distance for the route, and the like.
103
Added by DJM 2 2022
2/25/22, 12:00 AM
<< first
< previous
198
199
200
201
202
203
204
205
206
next >
last >>
Page 202 of 438, showing 20 record(s) out of 8,747 total