Automatically response system using a schedule and method thereof

TECHNICAL FIELD

0001The present invention relates to communication terminals, and more particularly, to a system and a method thereof are provided to automatically responding to incoming calls according to pre-registered schedules.

0002With this invention, a receiver can register at least one or more schedules, can search through schedule information for scheduled messages corresponding to at least one or more schedules, can display schedule notices to the receiver, and can automatically respond to callers accordingly; hence, able to prevent undesired call ringing in public places or during private times, and at the same time, able to avoid any misunderstanding between the caller and the receiver by advising of reason for not being able to receive a call and inform next connectable time. This enables the caller to wait in an efficient manner.

BACKGROUND ART

0003In these days, accelerating development of telecommunication technology and convenience of telecommunication has resulted in a rapid increase in number of people using phones and cellular phones. Cellular phone has an advantage that it can be used at anytime and on anywhere; hence, it is owned by almost one per person.

0004Despite the strength that cellular phone can be used irrespective of time and place, cellular phone's bell ringing sound in public places has become a serious pollution problem in our modern times. Especially, in non-allowed public places, such as school, government building, and library, or even in private times when one does not wish to receive a call, such as while sleeping, rest, studying, or driving. phone ringing sound not only bothers cellular receiver but also people around the receiver.

0005In order to resolve these problems, several techniques such as auto-answering Voice message system and connection disabling system have been developed. Auto-answering system originated from usage in regular wired-phones whereby during receiver's absence, pre-recorded message is played and caller can leave a voice message if needed. Connection disabling system is when a receiver changes cellular phone to non-receiving mode in a public places or where telecommunication signals are fundamentally blocked, calls will not get through to cell phones and hence not cause it to make ringing noise.

0006However, when call signals are fundamentally blocked, there will be a problem of caller not being able to connect even emergency calls. Also, when Auto-answering system is employed, receiver can only check message left by a caller and cannot proactively respond to caller's request.

0007On another invention, patent application number 2000-0037072 that is published in Korea, call connection can be controlled depending on a caller's identity. However, this invention has a complexity of requiring each and every caller to be already registered. Furthermore, the above invention cannot handle calls by non-registered callers. And even for registered callers, if their phone numbers change, those callers' call will not be connected unless registered phone number is changed.

0008On the other hand, aside from techniques to respond to noise pollution, when a receiver determines a schedule for a ringing, there is no means to connect other than receiver's scheduled time.

DISCLOSURE OF THE INVENTION

0009Accordingly, several objects and advantages of this invention are: <ul id="ul8S-d0e23800001" list-style="none"><li id="ul8S-d0e23800002-li00002"><ul id="ul8S-d0e23800002" list-style="none"><li id="ul8S-d0e23800002-p00010" num="00010"> a) to provide a system or method to automatically respond to a call request made by a caller using schedules. </li><li id="ul8S-d0e23800002-p00011" num="00011"> b) to provide a means to enable a call to come through even in a Do-Not-Disturb scheduled time, using a password that was pre-provided to callers by the receiver. </li><li id="ul8S-d0e23800002-p00012" num="00012"> c) to provide a system or method to deliver appropriate message to a caller whether that be a denial of receiving a call and/or to inform next possible time to receive a call. </li><li id="ul8S-d0e23800002-p00013" num="00013"> d) to provide a system or method thereof to communicate notices to receiver relating to schedule information and Do-Not-Disturb state. </li></ul></li></ul>

0014According to a preferred embodiment of this invention, in a call responding system based on schedules, receiver registers one or more schedules, the system searches for schedule information based on one or more registered schedules, schedule the system displays search-resulted schedule notice to receiver, and automatically respond to an incoming call using the schedule.

0015At least more than one schedule could be monthly schedule, weekly schedule, or special time schedule.

0016Registering at least more than one schedule means the system provides an input screen corresponding to the receiver-selected schedule menu, and registering the schedule information into a corresponding database.

0017Searching for schedule information for schedule notice means the system searches at least more than one schedule register with a selected search criteria, checks whether schedule type is “0” or not, checks the status of Do-Not-Disturb times, and if the schedule type is “0” or if Do-Not-Disturb times is past, deletes schedule information from corresponding schedule register. If Do-Not-Disturb time is not past, it maintains the schedule information from corresponding schedule register, and if searching in more than one schedule register is completed, it performs searching in the order of Special time schedule, weekly schedule, and monthly schedule. And it stores search-resulted schedule information into one or more schedule register.

0018Giving a notice to the Caller means, a) Inquire no. 1 schedule register to check schedule type, b) if that schedule type is not “0”, it checks whether Do-Not-Disturb schedule register is empty, c) if the Do-Not-Disturb schedule register is empty, it stores the schedule register's information into the Do-Not-Disturb register, d) repeat the above steps up to the last schedule register, e) and indicate computed schedule register forms, and if the Do-Not-Disturb schedule register is not empty while repeatedly performing above steps, it compares schedule register's start time to that of the Do-Not-Disturb schedule register.

0019Automatically responding to a caller's call request means, when a call is made, it checks Do-Not-Disturb schedule register and compares it against the present time. If present time is within Do-Not-Disturb scheduled time, it delivers Do-Not-Disturb state to the caller. And if the caller makes an emergency call request while in a Do-Not-Disturb state, it produces an emergency connection call ringing.

0020According to additional embodiment of this invention, in a call responding system based on schedules, it provides a communication terminal that enables a means for a receiver to register one or more schedules, to search for schedule information based on one or more registered schedules, to display search-resulted schedule to receiver, to deny caller's request based on current schedule information, to store one or more of the schedules, to temporarily memorize searched schedule information, and to produce a connection call ringing if a caller makes an emergency call request while in a Do-Not-Disturb state.

0021Stored databases in the communication terminal include Do-Not-Disturb list database, monthly schedule database, weekly schedule database, and special time schedule database.

BRIEF DESCRIPTION OF INVENTION

0022<figref idref="DRAWINGS">FIG. 1</figref> shows an outline of the call responding system according to a preferred operation scenario with a caller terminal and receiver terminal and a Communication Service Center.

0023<figref idref="DRAWINGS">FIG. 2</figref> shows a detailed structure of receiver's Terminal according to the call responding system preferred operation scenario.

0024<figref idref="DRAWINGS">FIG. 3</figref> shows Do-Not-Disturb list database table according to the call responding system preferred operation scenario.

0025<figref idref="DRAWINGS">FIG. 4</figref> shows a monthly schedule database table according to the call responding system preferred operation scenario.

0026<figref idref="DRAWINGS">FIG. 5</figref> shows a weekly schedule database table according to the call responding system preferred operation scenario.

0027<figref idref="DRAWINGS">FIG. 6</figref> shows a special-time schedule database table according to the call responding system preferred operation scenario.

0028<figref idref="DRAWINGS">FIG. 7</figref> shows a data structure in schedule register according to the call responding system preferred operation scenario

0029<figref idref="DRAWINGS">FIG. 8</figref> shows a data structure in Do-Not-Disturb schedule register according to the call responding system preferred operation scenario

0030<figref idref="DRAWINGS">FIG. 9</figref> shows a process flowchart of inputting schedule information according to the call responding system preferred operation scenario

0031<figref idref="DRAWINGS">FIG. 10</figref> shows a process flowchart of searching schedule information according to the call responding system preferred operation scenario

0032<figref idref="DRAWINGS">FIG. 11</figref> shows a process flowchart of displaying schedule information and indicating Do-Not-Disturb state according to the call responding system preferred operation scenario

0033<figref idref="DRAWINGS">FIG. 12</figref> shows a process flowchart of automatically responding to the Caller corresponding to current Do-Not-Disturb state when a caller makes a call request, according to the call responding system preferred operation scenario

BEST MODE CARRYING OUT THE INVENTION

0034The following detailed description will present a preferred embodiment of the invention in reference to the accompanying drawings.

0035<figref idref="DRAWINGS">FIG. 1</figref> shows an outline of call responding system according to a preferred operation scenario. In <figref idref="DRAWINGS">FIG. 1</figref>, the call responding system determines Do-Not-Disturb state based on pre-registered schedule when a caller makes a call request. When a call is made within a Do-Not-Disturb period, the call responding system informs the caller of the Do-Not-Disturb state, but when the call is made outside of Do-Not-Disturb time, it produces a ring and connects the call to the receiver.

0036To achieve this, the call responding system must have a caller's terminal <b>100</b> and a receiver's terminal <b>140</b> that can request a call and receive a call respectively. In here, the terminals <b>100</b> and <b>140</b> means either wired or wireless terminals. The wired terminal means a normal house phone. The wireless terminal means PCS, Cellular phone, or a PDA. Also, the call responding system includes a communication service center (CSC) <b>120</b> that provides services of registering personal information from the caller or the receiver, connecting a communication channel between the caller and the receiver, and enabling a voice exchange between the caller and the receiver. The CSC <b>120</b> in a case of normal house phones means public switched telephone network (PSTN), such as Verizon and AT&amp;T firms. The CSC <b>120</b> in a case of wireless network service means wireless service firms, such as Verizon Wireless and Nextel.

0037The receiver's terminal <b>140</b> is explained using <figref idref="DRAWINGS">FIG. 2</figref>. In here, it should be noted that the caller's terminal <b>100</b> can be structured the same way as the receiver's terminal <b>140</b>. The reason to differentiate the caller's terminal <b>100</b> and the receiver's terminal <b>140</b> is to differentiate a caller and a receiver, and the terminals that caller and receiver carry would have the same functionality and the same structure.

0038<figref idref="DRAWINGS">FIG. 2</figref> shows a detailed structure of receiver's Terminal according to the call responding system preferred operation scenario. In <figref idref="DRAWINGS">FIG. 2</figref>, the receiver's terminal <b>140</b> encompasses an input unit <b>151</b> which is used by receiver to input schedules, and a display unit <b>157</b> to show input screen according to receiver's schedule register request. The input unit <b>151</b> can be buttons on outside surface of the receiver's terminal <b>140</b>. The display unit <b>157</b> can be a Liquid Crystal Display (LCD) screen to show or any displayable information. Also, the receiver's terminal <b>140</b> can include a controller <b>153</b>, a memory <b>155</b>, schedule register <b>159</b> a receive signal detector <b>161</b>, a receive signal generator <b>163</b>, and an input/output interface <b>165</b>.

0039The receiver can make a schedule input request using the input unit <b>151</b>. The controller <b>153</b> provides an appropriate input screen to the receiver corresponding to receiver's register request. Hence, the receiver can input desired schedule and have it registered in receiver's terminal <b>140</b>.

0040In the memory <b>155</b>, a procedure for replying a caller's call is stored in a software program format. The memory <b>155</b> is also stored with receiver-input schedule; such as Do-Not-Disturb list of database, monthly schedule database, weekly schedule database, and special-time schedule database. Now each database is explained using FIGS. <b>3</b> to <figref idref="DRAWINGS">FIG. 6</figref>.

0041<figref idref="DRAWINGS">FIG. 3</figref> shows a Do-Not-Disturb list database table <b>200</b> according to the call responding system preferred operation scenario. In <figref idref="DRAWINGS">FIG. 3</figref>, the table <b>200</b> consists of a Do-Not-Disturb list field <b>201</b>, a password field <b>203</b>, and a default code field <b>205</b>. The Do-Not-Disturb list field <b>201</b> contains receiver's list of Do-Not-Disturb events, such as driving, conference, meeting, interview, lecture, show, sleeping, private time, planning time, etc. The password field <b>203</b> is filled indivisually with respect to each Do-Not-Disturb event. That means for each Do-Not-Disturb event, a distinct password can be registered. The password field <b>203</b> is required for the call responding system to connect a caller with password when the caller requests an emergency call during a Do-Not-Disturb period. In here, the password must be distributed in advance to approved callers corresponding to each Do-Not-Disturb event.

0042<figref idref="DRAWINGS">FIG. 4</figref> shows a monthly schedule database table <b>206</b> according to the call responding system preferred operation scenario. In <figref idref="DRAWINGS">FIG. 4</figref>, the monthly schedule database table <b>206</b> consists of a date field <b>207</b>, a start time field <b>209</b>, a finish time field <b>211</b>, a receiver state field <b>213</b>, a location field <b>215</b>, a moving time field <b>217</b>, a password request code field <b>219</b>, and a load check field <b>221</b>. The table <b>206</b> may have monthly repeating schedules registered. In here, the receiver state <b>213</b> is coded numerically in order to link its relation to the Do-Not-Disturb table database <b>200</b>. For example, when a receiver's state is ‘conference’, a number ‘2’ is registered, and the number ‘2’ corresponds to ‘conference’ in <figref idref="DRAWINGS">FIG. 3</figref>. When the receiver's state is ‘conference’, password and default code in <figref idref="DRAWINGS">FIG. 3</figref> corresponding to ‘conference’ are determined. The password request code is used to check whether to allow a caller to make an emergency call ringing or not. For example, if code is ‘Y’, the caller needs to have a password to make an emergency connection. However, if code is ‘N’, the caller does not need a password to make an emergency connection if the caller wishes to. The load-check field <b>221</b> is created for a use later on to avoiding duplicating search for information that is already stored in the schedule register <b>159</b> when schedules are searched. Furthermore, the load-check field <b>221</b> is automatically set to ‘N’ in the beginning. If after a search, schedule information gets to be stored in the schedule register <b>159</b>, corresponding schedule's load-check field <b>221</b> is changed to ‘Y’.

0043Thereby, the receiver inputs all corresponding fields in the receiver's own monthly schedule, and the monthly schedule is registered in the monthly schedule database <b>206</b>.

0044<figref idref="DRAWINGS">FIG. 5</figref> shows a weekly schedule database table <b>222</b> according to the call responding system preferred operation scenario. In <figref idref="DRAWINGS">FIG. 5</figref>, the weekly schedule database table <b>222</b> consists of a day-of-the-week field <b>223</b>, a start time field <b>225</b>, a finish time field <b>227</b>, a receiver state field <b>229</b>, a location field <b>231</b>, a moving time field <b>233</b>, a password request code field <b>235</b>, and a load check field <b>237</b>. The table <b>222</b> may have weekly repeating schedules registered.

0045<figref idref="DRAWINGS">FIG. 6</figref> shows a special-time schedule database table <b>238</b> according to the call responding system preferred operation scenario. In <figref idref="DRAWINGS">FIG. 6</figref>, the special time schedule database table <b>238</b> consists of a date field <b>239</b>, a start time field <b>241</b>, a finish time field <b>243</b>, a receiver state field <b>245</b>, a location field <b>247</b>, a moving time field <b>249</b>, a password request code field <b>251</b>, and a load check field <b>253</b>. The table <b>238</b> may have non-repeating one-time schedules registered.

0046Going back to <figref idref="DRAWINGS">FIG. 2</figref>, the controller <b>153</b> executes store program in the memory <b>155</b>. The controller <b>153</b> regularly checks registered schedules in the memory <b>155</b>, and stores schedule information that is needed for schedule notice in the schedule register <b>159</b>. The controller <b>153</b> stores schedule information corresponding to current Do-Not-Disturb schedule separately into the DND schedule register while providing schedule notice information that was stored in the schedule register <b>159</b>. The controller <b>153</b> gives schedule notice based on search result to terminal owner, and provides Do-Not-Disturb status to the caller. The controller <b>153</b> searches schedules, and if searched time coincides with schedule notice time, it displays schedule information on the display unit <b>157</b>, and at the same time, generate schedule notice signals in the receive signal generator <b>163</b> in a preprogrammed signal manner. The controller <b>153</b> receives a caller's connection request, determines if called time is within a Do-Not-Disturb time period or not, and subsequently sends Do-Not-Disturb state and next connectable time to the caller. The controller <b>153</b> could generate connection signal even during a Do-Not-Disturb period when the caller uses a password to request an emergency call.

0047The schedule register <b>159</b> is a temporary memory device to store searched schedule notice from the schedules. The schedule register <b>159</b> may include Do-Not-Disturb schedule register that stores separately current Do-Not-Disturb status schedule. Although the call responding system in this invention uses 10 schedule registers and one Do-Not-Disturb register, depending on this invention's alternatives, it can use more than 10 schedule registers.

0048<figref idref="DRAWINGS">FIG. 7</figref> and <figref idref="DRAWINGS">FIG. 8</figref> illustrates data structure of the schedule information in the schedule register <b>159</b>.

0049<figref idref="DRAWINGS">FIG. 7</figref> shows a data structure <b>260</b> in the schedule register <b>159</b> according to the call responding system preferred operation scenario. In <figref idref="DRAWINGS">FIG. 7</figref>, the data structure <b>260</b> consists of a start time field <b>261</b>, a finish time field <b>263</b>, a receiver state field <b>265</b>, a location field <b>267</b>, a moving time field <b>269</b>, a password field <b>271</b>, and a schedule type field <b>273</b>. In here, the start time field <b>261</b>, a finish time field <b>263</b>, a receiver state field <b>265</b>, a location field <b>267</b>, and a moving time field <b>269</b> can be copied directly from the memory <b>155</b> and be stored. The password field <b>271</b> is set to ‘0000’ if password request field in database is ‘N’. If password request field in database is ‘Y’, a password corresponding to the password request field may be copied and be stored in the password field <b>271</b>. The schedule type field <b>273</b> contains a number depending on simple schedule notice or Do-Not-Disturb status indicating mode; namely, ‘0’ for simple schedule notice, ‘1’ for Do-Not-Disturb state indication, and ‘2’ for schedule notice and Do-Not-Disturb state indication. For example, if Do-Not-Disturb state indication is selected, ‘1’ will be stored in the schedule type field <b>273</b>.

0050<figref idref="DRAWINGS">FIG. 8</figref> shows a data structure <b>274</b> in Do-Not-Disturb schedule register according to the call responding system preferred operation scenario. The Do-Not-Disturb schedule register is included in the schedule register <b>159</b> in <figref idref="DRAWINGS">FIG. 2</figref>. In <figref idref="DRAWINGS">FIG. 8</figref>, the data structure <b>274</b> consists of a start time field <b>275</b>, a finish time field <b>277</b>, a receiver state field <b>279</b>, a password field <b>281</b>, and a schedule type field <b>283</b>. In here, data input storage method for each category is the same as the storage method of the above schedule register; except in the Do-Not-Disturb schedule register, only fields that are required for connection denial are stored; the start time field <b>275</b>, the finish time field <b>277</b>, the receiver state field <b>279</b>, the password field <b>281</b>, and the schedule type field <b>283</b>. Hence, only current Do-Not-Disturb schedule information is stored. Hence, when there is a call request, only Do-Not-Disturb schedule register need to be checked to respond appropriately and promptly. Without this register, the system must search all schedule registers every time a call request is received.

0051In order to either display Do-Not-Disturb state status on the display unit <b>157</b>, or effect “one-touch Do-Not-Disturb selection”, the Do-Not-Disturb schedule register is required. The data that “one-touch Do-Not-Disturb selection” process requires is the data in the Do-Not-Disturb schedule register in <figref idref="DRAWINGS">FIG. 8</figref>. In a preferred scenario, ‘*’ button is for disabling Do-Not-Disturb schedule, ‘#’ button is for enabling Do-Not-Disturb schedule with a set of default values (current time to start time, ‘start time+increase time’ to finish time, default to receiver's state, ‘0000’ to password, ‘1’ [Do-Not-Disturb selection] to schedule type) . Additionally, ‘Δ’ and ‘←’ buttons are for moving Do-Not-Disturb schedule items, and ‘↑’ and ‘↓’ buttons are for changing each item's values. If a schedule already exists for the time that a user wishes to change, then only finish time, receiver state, and password can be modified. Now the only additionally required data is Do-Not-Disturb Increase time, and this value shall be determined by a value in the password <b>203</b> field under category ‘planning (9)’ in Do-Not-Disturb list <b>201</b> from the <figref idref="DRAWINGS">FIG. 3</figref>. That is because ‘planning’ is for schedule notice and does not need to use a password.

0052The usage of the schedule registers and the Do-Not-Disturb schedule register <b>159</b> define a class structure of memory <b>155</b>. That is, the schedule registers resides in the memory <b>155</b>'s upper structure, and the Do-Not-Disturb schedule register resides in the schedule register's upper structure. This is to minimize a time required to quickly determine a status of Do-Not-Disturb state when a call request is received. If the schedule register does not exist, all schedule information in memory <b>155</b> must be searched. And if Do-Not-Disturb schedule register does not exist, not only all schedule registers must be searched but also “one-touch Do-Not-Disturb selection” will be difficult to achieve.

0053Referring back to <figref idref="DRAWINGS">FIG. 2</figref>, the receive signal detector <b>161</b> searches for caller's connect request ring signal through input/output interface <b>165</b>. When a ring signal is detected, the receive signal detector <b>161</b> conveys this information to the controller <b>153</b>.

0054When a caller uses a password to request an emergency call, the receive signal generator <b>163</b> produces an emergency call receive ring signal after receiving a control signal from the controller <b>153</b>. The emergency call receive signal could be quieter than a normal receive signal as not to disturb public atmosphere in a Do-Not-Disturb state. It could also be a Silent-mode ring. The volume of the connect call signal can be preset in the program and can be controlled by the controller <b>153</b>.

0055One should note that the call responding system could be embodied within the CSC <b>120</b> instead of within the receiver's terminal <b>140</b>. That means the organization and the functionalities of the controller <b>153</b>, the memory <b>155</b>, and the schedule register <b>159</b> can be achieved within the CSC <b>120</b> to effect the call responding system. In this case, call responding system can be provided to more callers with a better service. For example, one can use Internet or PDA to directly schedule CSC <b>120</b>'s computer system database, and better additional functionalities can be added.

0056<figref idref="DRAWINGS">FIG. 9</figref> shows a process flowchart of inputting schedule information according to the call responding system preferred operation scenario. A receiver who has purchased the call responding system needs to register monthly, weekly, special time schedules into receiver's terminal. But before registering monthly, weekly, special time schedules, the receiver must register Do-Not-Disturb list items. In <figref idref="DRAWINGS">FIG. 9</figref>, the receiver first selects a schedule menu (step <b>301</b>). Then, the receiver's terminal displays an input screen to the receiver corresponding to the selected menu (step <b>303</b>). The receiver inputs schedule information through the input screen (step <b>305</b>). In this step, schedule information would include day-of-the-week, date, start time, finish time, receiver state, location, moving time, password, etc. Then the receiver terminal registers the schedule information to corresponding databases (step <b>307</b>). If the schedule information is for monthly schedule, the receiver's terminal registers the schedule information into the monthly schedule database, and if the schedule information is for weekly schedule, the receiver's terminal registers the schedule information into the weekly schedule database. Also the receiver can input Do-Not-Disturb state, password, and default type; hence registering into the Do-Not-Disturb list database.

0057<figref idref="DRAWINGS">FIG. 10</figref> shows a process flowchart of searching through schedule information according to the call responding system preferred operation scenario. Assuming that all schedules in the receiver terminal are registered, auto-responding process is automatically executed from the moment that the receiver terminal's power is turned on.

0058<figref idref="DRAWINGS">FIG. 10</figref> shows that when the receiver terminal's power is turned on, the receiver terminal starts the schedule searching process. Firstly, the receiver terminal monitors whether current time is within a preset searching cycle time (step <b>311</b>). In here, the searching cycle time is modifiable, and it is preferred that it be set in 1-minute unit; thereby, the receiver terminal executes schedule searching process. Secondly, the receiver terminal searches through the schedule register (step <b>313</b>). In here, the schedule information includes start time, finish time, receiver state, location, moving time, password, and schedule type of which all are illustrated in <figref idref="DRAWINGS">FIG. 7</figref>. This schedule searching process is for deleting schedule information that is stored in the schedule register if current time is past its finish time. For example, if current time is 11:33AM and the schedule register's stored schedule information's finish time is 11:30AM, then the schedule information does not need to be stored in the schedule register anymore; hence, it may be deleted. The receiver terminal checks whether the schedule type is ‘0’ (step <b>315</b>), and if it is not ‘0’ , it checks whether current time is past finish time. (step <b>317</b>). If the schedule type is ‘0’ or if current time is past finish time , the receiver terminal deletes schedule information from the schedule register (step <b>321</b>). If current time is not past finish time, the receiver terminal maintains the schedule register's schedule information (step <b>319</b>). The steps from <b>313</b> to <b>321</b> are repeated for all schedule registers.

0059When searching in schedule registers is completed, the receiver terminal searches special-time schedule (step <b>323</b>). In here, the special-time searching can be executed using schedule information that is registered in the special-time schedule database. The receiver terminal checks whether current date is the same as the scheduled date (step <b>325</b>). If these are the same, the receiver terminal executes ‘schedule information treatment’ on corresponding schedule information (step <b>335</b>). If these are different, the receiver terminal executes ‘schedule information maintain’ step (step <b>337</b>).

0060After special-time schedule searching is completed, the receiver terminal searches weekly schedules (step <b>227</b>). It compares current day against a scheduled day (step <b>329</b>). If these are the same, it executes the step <b>335</b>; but if these are different, it executes the step <b>337</b>.

0061After weekly schedule searching is completed, the receiver terminal searches monthly schedules (step <b>331</b>). It compares current day against a scheduled day (step <b>333</b>). If these are the same, it executes the step <b>335</b>; and if these are different, it executes the step <b>337</b>.

0062These steps are executed for all information in all types of schedule databases.

0063In “schedule Information Treatment” process (step <b>335</b>), for items with load-check is ‘N’, it searches through schedules that have current time within the schedule's start and finish time. Therefore, the number of schedule registers is determined by the number of schedules that could be planned to have the same times. In our system's case, it would be possible to have 10 schedule registers that could have the same time (in minute unit). For loaded schedule information, load-check is set to ‘Y’, and schedule type is set. Schedule type is set to 0 if receiver state is ‘planning’ (in <figref idref="DRAWINGS">FIG. 3</figref> receiver state is ‘9’) as this is for ‘simply schedule notice’. If moving time is ‘0:00’ and place requires privacy, this situation is Do-Not-Disturb and schedule type is set to 1. Finally, the schedule type is set to 2 if there exists moving time and place is private as this situation is Do-Not-Disturb and is in a schedule notice mode.

0064In ‘schedule information maintain’ step <b>337</b>, all schedule information's load-check value is set to ‘N’. This has a meaning of initializing next schedule search towards once-loaded schedule register's information on a special day.

0065<figref idref="DRAWINGS">FIG. 11</figref> shows a process flowchart of displaying schedule information and indicating Do-Not-Disturb state according to the call responding system preferred operation scenario. Updated schedule information that resulted from the schedule searching process can be notified to the receiver as well as displayed of its Do-Not-Disturb state. As mentioned earlier, this invention consists of 10 schedule registers and one Do-Not-Disturb register. In <figref idref="DRAWINGS">FIG. 11</figref>, one can see that the receiver terminal checks updated schedule registers sequentially (step <b>341</b>). The receiver terminal checks if 10^thschedule register is checked yet (step <b>343</b>), and if not, it checks if the first schedule register's schedule type is ‘0’ (simple schedule notify) (step <b>345</b>).

0066If the schedule type is not ‘0’, it checks whether Do-Not-Disturb schedule register is empty (step <b>349</b>). If the Do-Not-Disturb schedule register is empty, the receiver terminal copies schedule information from the first schedule register to the Do-Not-Disturb schedule register (step <b>353</b>). In a case that the Do-Not-Disturb schedule register is not empty, the receiver terminal compares first register's start time against the Do-Not-Disturb schedule register (step <b>351</b>).

0067If the Do-Not-Disturb register's start time is later than that of the schedule register, the Do-Not-Disturb schedule register's information is copied from that of schedule register (step <b>353</b>). If the Do-Not-Disturb register's start time is not later than that of the schedule register, the receiver terminal goes on to check if the schedule type is ‘1’ or not (step <b>355</b>). If it is ‘1’, the receiver terminal sets itself to the Do-Not-Disturb state (step <b>357</b>), and if it is not ‘1’, the receiver terminal sets itself to the schedule notice and a Do-Not-Disturb state (step <b>359</b>).

0068After the first schedule register's schedule notice Do-Not-Disturb state setting is completed, second schedule register is checked (step <b>361</b>). And the above steps from <b>343</b> to <b>361</b> are repeated until the last schedule register is checked.

0069When schedule type is ‘0’ in the step <b>345</b>, the receiver terminal sets itself to schedule notice only (step <b>347</b>).

0070The result from checking first schedule register to last schedule register can be displayed to the receiver, and at the same time, receiver signal be generated. In here, the schedule notice means communicating corresponding schedule information. The Do-Not-Disturb status displayed items include receiver state, Do-Not-Disturb time, password request status on corresponding schedule information. The Do-Not-Disturb time is calculated by subtracting current time from finish time.

0071<figref idref="DRAWINGS">FIG. 12</figref> shows a process flowchart of automatically responding to a Caller corresponding to current Do-Not-Disturb state when a caller makes the call request, according to the call responding system preferred operation scenario. <figref idref="DRAWINGS">FIG. 12</figref> shows that this process starts with receiver terminal checking to see if there is any call request (step <b>371</b>); this check for call request is done using ring signal. When there is a call request, the receiver terminal checks the Do-Not-Disturb schedule register (step <b>373</b>), and determines if current time is between start time and finish time (step <b>375</b>). After the comparison, if current time has past the finish time, the receiver terminal generates a receive signal and alerts the receiver via either a ring sound or a vibration (step <b>377</b>). If current time is within start and finish time, it communicates to the caller its current Do-Not-Disturb status (receiver state and call possible time, etc.) via either text message or voice message (step <b>379</b>).

0072The caller may still wish to connect and make an emergency call request even after learning of Do-Not-Disturb state. At this time, an emergency call connection can still be achieved. The receiver terminal checks to see if the caller is making an emergency call request (step <b>381</b>). If there is an emergency call request, the receiver terminal checks if the caller's selected password matches with that of Do-Not-Disturb schedule register (step <b>383</b>). The step <b>383</b> also applies to cases when password is not setup or password is ‘0000’. After checking, if the password is correct or if password is not setup or password is ‘0000’, the receiver terminal generates an emergency call receive signal (step <b>385</b>), if password is required but is not correct, it communicates to the caller to re-input a password and provide a helpful guide information (step <b>387</b>). Thereby, the receiver learns of an emergency call request in the step <b>385</b>, and answer the call. Through the step <b>387</b> the caller can re-input a correct password to make an emergency call request.

0073On an alternative embodiment of this invention, by receiver registering schedule information ahead of time, if the receiver does not wish to answer any call, the receiver does not have to answer calls using this Do-Not-Disturb functionality.

0074This invention can be applied such that by receiver register certain undesired people's phone numbers in advance, a system can be used such as to block any calls coming from these people.

0075Industrial Applicability

0076From the description above, a number of advantages of Auto Responding System by Schedule (call responding system) become evident: <ul id="ul6S-d0e41700001" list-style="none"><li id="ul6S-d0e41700002-li00002"><ul id="ul6S-d0e41700002" list-style="none"><li id="ul6S-d0e41700002-p00077" num="00077"> (a) By automatically answering calls using schedules, undesired call ringing can be prevented while in a public place or during a private time. </li><li id="ul6S-d0e41700002-p00078" num="00078"> (b) By informing the caller as to the exact reason for not answering the call as well as informing the next possible call receive time, any misunderstanding between the caller and the receiver can be prevented. </li><li id="ul6S-d0e41700002-p00079" num="00079"> (c) By enabling to have selective emergency calls to be received even during a Do-Not-Disturb time, absolutely imperative calls can reach the receiver regardless of Do-Not-Disturb settings. </li><li id="ul6S-d0e41700002-p00080" num="00080"> (d) By notifying the receiver of current schedule or current Do-Not-Disturb state, communication system's usage is maximized. </li></ul></li></ul>

0081This invention is applicable for both wire and wireless terminals.

0082The call responding system can be supplied either by a communication service provider or by a terminal manufacturer.

0083Although the description above contains many specificities, these should not be construed as limiting the scope of this invention. Also, on the above technical field, any person with some communications knowledge can change or modify this invention without going outside of the scope limits of this invention.