Patent Application
20070202870
1. Field of the Invention
The invention is related to the field of communication networks and, in particular, to providing a child call log service in wireless networks that allows a parent to access call information of a child using a mobile device.
2. Statement of the Problem
With the popularity of cellular phones, many families are signing up for service and have multiple cell phones. A family may sign up for a sharing plan where two or more lines share a common monthly usage. A family may also sign up for individual plans for the family members. With family usage increasing, many children have their own cell phones. One concern for parents giving their children cell phones is misusage of the phone. For instance, a child may place calls to people that are not authorized by the parents, or may place long-duration calls to their friends. A child may also access the internet on internet-capable phones which may cause the parents to incur higher rates.
Presently, parents may track the phone usage of their children by viewing the monthly statements provided by the service provider. These monthly statements are typically included with the monthly bills. Some service providers also provide the monthly statements online, which allows the parents to view the last-month's statement and previous-monthly statements through a web site of the service provider.
Some problems presently exist for allowing parents to view the cell phone usage of their children. For one, the parents have to wait for the service provider to send a monthly statement or post the monthly statement online before it can be viewed. This does not allow a parent to view recent usage, such as in the last day, the last week, etc. Another problem is that to view the statements provided online, the parents need to have internet access. Not all parents have internet access and do not have the ability to view cell phone usage of their children online.
Some service providers of VoIP service provide a web site that allows a parent to view current call information of a child using a VoIP phone. Once again, it may be a problem to view a web site as a parent may not have internet access. The VoIP service providers do not provide a mechanism that allows a parent to view the call information for the child over his/her VoIP phone.
The invention solves the above and other problems by providing a child call log service in wireless networks. According to the child call log service, the wireless network tracks the usage of a child placing or receiving calls in the wireless network, and stores call information for the child in a call log. A parent may then access the call information in the call log through the wireless network and his/her mobile device to determine with whom the child has been conversing, the duration of the calls of the child, the type of the calls, etc. The wireless network updates the call log of the child based on the usage of the child so that the parent may advantageously access recent call information for the child, such as within the last hour, the last day, the last week, etc. The parent does not need to wait to receive a monthly statement in order to view the child's call information. The parent may advantageously access the child's call information from the wireless network through their mobile device (e.g., a cell phone). The parent does not need to have internet access to acquire the child's call information.
In one embodiment of the invention, a wireless network for providing the child call log service comprises a network node and a child call log system. To provide the child call log service, the network node serves calls for a mobile device of a child. In addition to serving the calls for the child, the network node also records call information for the calls of the child, and transmits the call information to the child call log system. The child call log system stores the call information for the child in a call log for the child. At this point, the child call log system has a call log that includes recent call information for the child, such as call information for calls at least within the last week.
According to the child call log service, a parent of the child is able to access the call information for the child through the wireless network. To access the call information for the child, the parent transmits a request for the call information to the wireless network through a mobile device. The network node receives the request from the parent, and transmits a request for the call information to the child call log system. Responsive to the request from the network node, the child call log system accesses the call log for the child to identify the call information for the child. The child call log system then provides the call information for the child to the mobile device of the parent. The child call log system may provide the call information to the parent in many desired ways, such as in a text message, a multimedia message, an email message, a voice message, etc.
The invention may include other exemplary embodiments described below.
The same reference number represents the same element on all drawings.
Network node 102 includes any system, server, or other device that serves mobile devices for wireless communication, such as a Mobile Switching Center (MSC). In particular, network node 102 is adapted to serve a mobile device 110 of a child 112 and a mobile device 120 of a parent 122. Mobile devices 110 and 120 comprise any devices adapted to communicate via wireless signals, such as a cell phone, a PDA, or another type of mobile communication device. Those skilled in the art understand that mobile devices 110 and 120 may be served by different network nodes, but a single network node 102 is shown merely for illustrative purposes.
Network node 102 and child call log system 104 may each comprise instructions executable by a processing system to operate as described below to provide the child call log service. Some examples of instructions are software, program code, and firmware. The instructions are operational when executed by the processing system to direct the processing system to operate in accordance with the invention. The term “processing system” refers to a single processing device or a group of inter-operational processing devices. Some examples of processors are computers, integrated circuits, and logic circuitry.
In step 202, network node 102 serves calls for mobile device 110 of child 112. To serve calls for mobile device 110, network node 102 may connect calls from mobile device 110 directed to other parties (not shown) through wireless network 100. Network node 102 may also connect calls from other parties to mobile device 110 through wireless network 100. As part of serving calls, network node 102 sets up, maintains, and tears down calls in wireless network 100.
In step 204, network node 102 records call information for the calls served for mobile device 110 of child 112. The call information may include directory numbers of the parties of the call, the duration of the call, the type of call, etc. Network node 102 then transmits the call information to child call log system 104. Network node 102 may transmit call information for a call to child call log system 104 responsive to the call being completed.
Child call log system 104 receives the call information for the calls for child 112, and stores the call information for child 112 in a call log for child 112 in step 206. If a call log does not already exist for child 112, then child call log system 104 creates a call log for child 112 and stores the call information for child 112 in the call log. If a call log already exists, then child call log system 104 stores the call information for child 112 in the call log. At this point, child call log system 104 has a call log that includes recent call information for child 112. Recent call information refers to call information for calls for child 112 within at least the last week. The call log may also include older call information. According to the child call log service, parent 122 is able to access the call information for child 112 through wireless network 100.
To access the call information for child 112, parent 122 transmits a request for the call information to wireless network 100 through mobile device 120 that is received by network node 102. Parent 122 may initiate the request for the call information by dialing a feature code (e.g., *61) in mobile device 120. Parent 122 may alternatively initiate the request for the call information by dialing a particular directory number assigned for the child call log service. The request from parent 122 may request particular call information, such as call information for calls for child 112 within at least the last week or for another specified time period (e.g., the last hour or the last day). The request from parent 122 may further request call information for the last call of child 112, call information on calls to a particular party, etc. Responsive to the request from parent 122, network node 102 transmits a request for the call information to child call log system 104. Network node 102 may authenticate parent 122 before transmitting the request for the call information to child call log system 104.
Responsive to the request from network node 102, child call log system 104 accesses the call log for child 112 to identify the call information for child 112 in step 208. In step 210, child call log system 104 provides the call information for child 112 to mobile device 120 of parent 122. Child call log system 104 may provide the call information to parent 122 in many desired ways. For instance, child call log system 104 may transmit the call information to parent 122 in the form of a text message or a multimedia message transmitted to mobile device 120. Child call log system 104 may transmit the call information to parent 122 in the form of an email message transmitted to mobile device 120. Child call log system 104 may transmit the call information to parent 122 in audible form, such as in a voice message or an announcement transmitted to mobile device 120.
Child call log system 104 is not intended to provide the call information to parent 122 in the form of a web page. Mobile device 120 of parent 122 may not be internet-enabled or may not have a web browser. Also, parent 122 may not have internet access through a home computer or a work computer. Thus, child call log system 104 is configured to provide the call information in another manner so that parent 122 may access the call information for child 112 through mobile device 120.
Wireless network 100 advantageously records call information for child 112 in a call log that can subsequently be accessed by parent 122 through mobile device 120. Because wireless network 100 continually updates the call log of child 112, parent 122 may advantageously access recent call information for the child, such as within the last hour, the last day, the last week, etc. Parent 122 does not need to wait to receive a monthly statement in order to view call information for child 112. Also, parent 122 may advantageously access call information for child 112 through mobile device 120 without requiring parent 122 to have internet and web-browsing capability through mobile device 120 or another system.
MSC 302 is adapted to serve a mobile device 310 of a child 312 and a mobile device 320 of a parent 322. Those skilled in the art understand that mobile devices 310 and 320 may be served by different MSCs, but a single MSC 302 is shown merely for illustrative purposes.
Parent 322 and child 312 have both subscribed to the child call log service through the service provider operating wireless network 300. To subscribe to the service, parent 322 establishes a user name and password that is subsequently used to authenticate parent 322 when parent 322 seeks to view the call information for child 312. The service provider also defines a network address for child call log system 304 that will be used to store the call log for child 312. Mobile devices 310 and 320 then register with wireless network 300 at some point, such as upon power up.
If the user does not subscribe to the child call log service, then method 400 ends. If the user subscribes to the child call log service, then MSC 302 determines whether the user is identified as child 312 or parent 322 in step 410. If the user is identified as child 312, then MSC 302 creates/updates the Visitor Location Register (VLR) for the user with a child call log service indicator, the directory number of parent 322, and a network address of child call log system 304 in step 412. If the user is identified as parent 322, then MSC 302 creates/updates the VLR for the user with a child call log service indicator, a password for parent 322, and a network address of child call log system 304 in step 414. Method 400 is performed for both mobile device 310 and mobile device 320 to register these devices.
If the user is identified as child 312, then MSC 302 records call information for the call in step 508. The call information may include an identifier for child 312 (e.g., a directory number), an identifier for parent 322, an identifier of the other party to the call, a duration for the call, a call type, and possibly other information. When the call has been completed, MSC 302 generates a call record for the call based on the call information. One example of a call record is a Call Detail Record (CDR) traditionally generated by an MSC. MSC 302 then transmits the call record for the call to child call log system 304 in step 510 over IP network 309 for storage of the call record. MSC 302 may transmit the call record to child call log system 304 responsive to the call being completed so that child call log system. 304 has the most recent call information for call of child 312. Those skilled in the art understand that MSC 302 may also transmit a copy of the call record to a billing system (not shown).
According to the child call log service, parent 322 is able to access call information for child 312 that is stored in the call log in child call log system 304.
If the user is identified as parent 322, then MSC 302 prompts parent 322 for a password in step 706. MSC 302 receives a password from parent 322 through mobile device 320 and determines if the password is valid in step 708. If the password is not valid, then MSC 302 denies the request in step 705. If the password is valid, then parent 322 is authenticated as an authorized parent of child 312 that is allowed to access the call information for child 312.
In step 710, MSC 302 transmits a request for the call information for child 312 to child call log system 304 over IP network 309. MSC 302 is able to identify the network address for child call log system 304 in the VLR for parent 322. In step 712, MSC 302 then establishes a data path between mobile device 320 of parent 322 and child call log system 304.
Responsive to receiving the request for the call information from MSC 302, child call log system 304 retrieves the call log for child 312 in step 714. Child call log system 304 then identifies the call information in the call log that was requested by parent 322 in step 716. As previously stated, the request from parent 322 may request particular call information, such as call information for calls for child 312 within at least the last week or for another specified time period (e.g., the last hour or the last day). The request from parent 322 may further request call information for the last call of child 312, call information on calls to a particular party, etc. Child call log system 304 then provides the call information for child 312 to parent 322 in step 718.
Child call log system 304 may provide the call information to parent 322 in many desired ways. For instance, child call log system 304 may transmit the call information to text/multimedia message server 306 over IP network 309. Text/multimedia message server 306 then generates a text message (e.g., SMS message) or multimedia message (e.g., MMS message) that includes the call information for child 312, and transmits the message to mobile device 320 of parent 322 through MSC 302. Parent 322 may then view the call information provided in the text message through his/her mobile device 320.
Similarly, child call log system 304 may alternatively transmit the call information to email server 308 over IP network 309. Email server 308 then generates an email message that includes the call information for child 312, and transmits the email message to mobile device 320 of parent 322 through MSC 302. Parent 322 may then view the call information provided in the email message through his/her mobile device 320.
Child call log system 304 may alternatively transmit the call information to parent 322 in audible form. For instance, child call log system 304 may include text-to-speech hardware and/or software that convert the call information for child 312 to an audible format. Child call log system 304 may then provide the call information to parent 322 as a voice message or an announcement. Once again, child call log system 304 is not intended to provide the call information to parent 322 in the form of a web page.
The above embodiments of the child call log service describe the relationship of a parent and a child. In the above and other embodiments, the child call log service may also be extended to relationships other than the parent/child relationship. For instance, the child call log service (which may be generally referred to as a call log service) may be used for an employer/employee relationship or another relationship where one mobile user desires to access recent call information for another mobile user. The “child” in the above embodiments may be generally referred to as a target user. The “parent” in the above embodiments may be generally referred to as a requesting user that is requesting the call information for the target user. One assumption that is made is that the requesting user is authorized to access the call information for the target user due to the relationship between the requesting user and the target user, due to consent by the target user, etc. As an example, an employee (target user) may consent to the employer (requesting user) accessing call information for calls placed with a company mobile phone.
Although specific embodiments were described herein, the scope of the invention is not limited to those specific embodiments. The scope of the invention is defined by the following claims and any equivalents thereof.
