The present invention relates to a game system utilizing wireless communication. More specifically, the present invention relates to a wireless communication game system having a “child” device capable of storing information of a parent device existing within a communicable range between the child device, and a mobile game apparatus and a game system used therefor.
One example of a conventional wireless communication game system is disclosed, for example, in Japanese Patent Laying-open No. 2000-135380 (International Classification: A63F13/00, H04L12/28) laid-open on May 16, 2000.
In this prior art reference, people such as friends, and others, promise among themselves, for example, that they will bring a game apparatus that executes the same game, establish communication via the game apparatus, and execute a wireless communication game. In the prior art, users have no choice but to confirm verbally identification information of the game apparatus of others and information on a game name, etc., in order to know such information. Therefore, in a case where a game apparatus of unknown persons exists within a communicable range, it is realistically difficult to play the wireless communication game with that person. Therefore, in the prior art, the user cannot freely and dynamically select the game apparatus of a communicating partner.
Therefore, it is a feature of the exemplary embodiments of the present invention to provide a novel wireless communication game system, a mobile game apparatus, a child device connecting method, and a game program in a wireless communication game system.
It is another feature of an exemplary embodiment of the present invention to provide a wireless communication game system, a mobile game apparatus, a child device connecting method, a game program in a wireless communication game system capable of arbitrarily selecting a parent device which a child device intends to select.
It is still another feature of an exemplary embodiment of the present invention to provide a wireless communication game system, a mobile game apparatus, a child device connecting method and a game program in a wireless communication game system capable of freely playing a wireless communication game with the game apparatus existing within a communicable range.
A wireless communication game system according to of an exemplary embodiment of the present invention uses a plurality of mobile game apparatuses, which function as a parent device or a child device and are capable of wireless communication with each other. The parent device includes broadcasting circuitry for broadcasting a parent device packet including user's own apparatus identifying information for allowing a user's own apparatus to be identified and game identifying information for allowing a game executed by the user's own apparatus to be identified. The child device includes a receiver, a display, a selector, and a connection request transmitter. The receiver receives the parent device packet from the parent device existing within a communicable range. The display displays a parent device list of the parent device existing within a communicable range, based on the parent device packet received by the receiver. The selector allows a player to select any one of the parent devices included in the parent device list. The connection request transmitter transmits a connection request toward the parent device selected by the selector.
More specifically, the wireless communication game system is formed using at least two mobile game apparatuses (10: corresponding reference numeral in the detailed description of the preferred embodiments described below in this embodiment. A mobile game apparatus (10) in the embodiment includes a mobile game machine (12), and a wireless communication unit (14) attached to the mobile game machine. In a case of the parent device, the mobile game apparatus uses this mobile communication unit (14) so as to broadcast a parent device packet in a first time slot, and receives a child device packet in a second time slot. In a case of the child device, the mobile game apparatus receives the parent device packet in the first time slot, and transmits the child device packet toward the parent device in the second time slot.
The broadcasting circuitry corresponds to steps S2003 and S2009 of a transmission/reception process of the parent device shown in
In addition, the child device receives the above-described parent device packet by the receiver shown in a step S4001 in
A user of the child device looks at a game name in the parent device list, for example, and operates a cross key of an operation key (38) forming a selector in steps of S79 and S151 in
Therefore, this allows the child device to arbitrarily determine whether to connect to any one of the parent devices displayed in the parent device list created from the parent device packet.
In a certain embodiment, the broadcasting circuitry broadcasts the parent device packet even during a time that a communication game is being executed with another child device. This, more specifically, corresponds to
In another embodiment, the parent device and the child device are apparatus for making a wireless communication in a predetermined communication cycle. The communication cycle includes a first time slot used by the parent device, and a second time slot used by the child device. The broadcasting circuitry transmits the parent device packet including game data in the first time slot. That is, the first time slot is a parent device slot, and the second time slot is a child device slot. Furthermore, the broadcasting circuitry broadcasts the parent device packet including payload data shown in
In a certain embodiment, the display displays in the parent device list only the parent device that executes a game communicable with the game executed by the user's own apparatus, based on the game identifying information received by the receiver. In a case that the game apparatus is an apparatus to which a game cartridge storing a game program is detachably attached, for example, the display displays in the parent device list the parent device only when the game of the game cartridge attached to the parent device is communicable with the game of the game cartridge attached to the child device. More specifically, as shown in
In another embodiment, the child device is an apparatus to which a game cartridge storing a game program is detachably attached. The display displays in the parent device list a parent device that executes a game not communicable with the game of the game cartridge currently attached thereto. More specifically, the game cartridge corresponds to a cartridge 16 shown in
In still another embodiment, the parent device packet further includes entry reception data showing whether or not to receive a new entry of the child device. The display displays in the parent device list only the parent device that receives the new entry of the child device, based on the entry reception data received by the receiver. More specifically, the entry reception data corresponds to data other than “ffh” of the E slot, and therefore, the child device displays the parent device that sets the data other than “ffh” in the E slot of the parent device packet as shown in
In yet another embodiment, the parent device further comprises a child device-use program storage locations for storing a child device-use program, and a child device-use program transmitter for transmitting, in response to a connection request from the child device (the child device is an apparatus to which the game cartridge is detachably attached, for example, and in response to a request from the child device to which the game cartridge is not attached), the child device-use program to the child device. The parent device packet further includes child device-use program holding data showing whether or not it is being provided with the child device-use program storage locations. In a case of showing that the child device-use program holding data is provided with the child device-use program, the display displays in the parent device list the parent device irrespective of the game, which is executed by the user's own apparatus, based on the child device-use program holding data received by the receiver. More specifically, the child device-use program storage locations corresponds to an area 76 in
In addition, in accordance with an exemplary embodiment, the parent device stores both a first program not requiring the child device to transmit the child device-use program, and a second program requiring the child device to transmit the child device-use program. The parent device packet further includes execution type data showing which program, the first program or the second program, the parent device executes. Regarding the parent device executing the first program, the display displays in the parent device list only the parent device that executes a game communicable with the game executed by the user's own apparatus, based on the execution type data received by the receiver, and regarding the parent device executing the second program, displays in the parent device list irrespective of the game, which is executed by the user's own apparatus. More specifically, a cartridge 16 shown in
In an exemplary embodiment, the child device is an apparatus to which a game cartridge storing a game program is detachably attached. The display displays, in a case where the game cartridge is not attached, in the parent device list only the parent device provided with the child device-use program storage locations, based on the child device-use program holding data received by the receiver. Similar to an above-described embodiment, only the parent device holding the OC-mode-use game program is displayed. Therefore, in a case where the game cartridge is not attached, the child device displays only the information on the parent device capable of transmitting the child device-use program. This allows a player using the child device to easily select the parent device.
In still another embodiment, the present invention further comprises: parent device list storage locations for storing a parent device list of the parent device existing within a communicable range, based on the parent device packet received by the receiver; and a parent device list clearing mechanism for regularly clearing the parent device list stored in the parent device list storage locations. The display displays based in the parent device list stored in the parent device list storage locations. More specifically, the parent device list is displayed based on the parent device list storage locations (which corresponds to a parent device list area 80 in
A child device connecting method in a wireless communication game system according to an exemplary embodiment of the present invention is a child device connecting method in the wireless communication game system using a plurality of mobile game apparatuses that function as a parent device or a child device capable of communicating with each other, and includes following steps of (a) broadcasting from the parent device a parent device packet including user's own apparatus identifying information for allowing the user's own apparatus to be identified, and game identifying information for allowing a game executed by the user's own apparatus to be identified, (b) receiving in the child device the parent device packet from the parent device existing within a communicable range, (c) displaying in the child device a parent device list of the parent device existing within a communicable range, based on the parent device packet received by the receiving step, (d) allowing in the child device a player to select any one of the parent devices included in the parent device list, and (e) transmitting in the child device a connection request toward the selected parent device.
A program of a wireless communication game system according to an exemplary embodiment of the present invention is a program of a wireless communication game system using a plurality of mobile game apparatuses that function as a parent device or a child device capable of communicating with each other, and allows a processor of the mobile game apparatus to execute following steps: (a) allowing the processor of the parent device to broadcast a parent device packet including user's own apparatus identifying information for identifying the user's own apparatus, and game identifying information for allowing a game executed by the user's own apparatus to be identified, (b) allowing the processor of the child device to receive the parent device packet from the parent device existing within a communicable range, (c) allowing the processor of the child device to display a parent device list of the parent device existing within a communicable range, based on the parent device packet received by the step (b), (d) allowing the processor of the child device to make a player select any one of the parent devices included in the parent device list, and (e) allowing the processor of the child device to transmit a connection request toward the selected parent device.
A mobile game apparatus according to an exemplary embodiment of the present invention uses a plurality of mobile game apparatuses, any one of which functions as a parent device, and the other of which functions as a child device, both capable of playing a wireless communication game. This mobile game apparatus comprises: broadcasting circuitry, for the parent device (for functioning as the parent device), for broadcasting a parent device packet including user's own apparatus identifying information for allowing the user's own apparatus to be identified, and game identifying information for allowing a game executed by the user's own apparatus to be identified; a receiver; a display; a selector; and a transmitter, for the child device (for functioning as the child device). The receiver receives the parent device packet from the parent device existing within a communicable range. The display displays a parent device list of the parent device existing within a communicable range, based on the parent device packet received by the receiver. The selector allows a player to select any one of the parent devices included in the parent device list. The transmitter transmits a connection request toward the selected parent device.
In the child device connecting method, the program, the mobile game apparatus, similar to the wireless communication game system, it has an advantage that the child device is capable of knowing the parent device existing within a communicable range, and easily selecting and connecting a desired parent device.
According to an exemplary embodiment of the present invention, since the parent device broadcasts the parent device information, it is possible that the child device knows what kind of parent devices exist within a communicable range (that is, it is possible to know the parent device capable of playing a communication game). In addition, the child device is capable of arbitrarily determining which parent device to connect.
In a case of a wireless communication game, the mobile game apparatus is freely carried, and therefore, the mobile game apparatus existing within a communicable range progressively changes. According to an exemplary embodiment of the present invention, however, it is possible to know information on the mobile game apparatus existing within a communicable range. This makes it possible to freely determine an intended partner with whom to play the wireless communication game.
In addition, there is a case that an apparatus of a unknown stranger comes into a communicable range. In this case, too, it is possible to know the information, thus making it possible to play the wireless communication game with the unknown stranger.
The above described objects and other objects, features, aspects and advantages of the exemplary embodiments of the present invention will become more apparent from the following detailed description of the present invention when taken in conjunction with the accompanying drawings.
A wireless communication game system to which an exemplary embodiment of the present invention is adapted uses a mobile game apparatus 10 as shown in
The mobile game machine 12 shown in
The mobile game machine 12 has the cartridge connector 40, and the cartridge 16 is connected or inserted into this cartridge connector 40. The cartridge 16 contains a ROM 42 and a backup RAM 44, and a game program for a game to be executed in the mobile game machine 12, in addition to its game name, is set in the ROM 42 in advance. The backup RAM 44 stores progressive data of the game and resultant data of the game.
The mobile game machine 12 is further provided with a communication connector 46, and a connector 48 of the wireless communication unit 14 is connected to the communication connector 46. It is noted that the mobile game machine 12 used in this embodiment is GameBoy Advance (Trademark) as an example. GameBoy Advance is a commercially available hand-held video game platform, which in copending application Ser. No. 09/863,866 (published on Nov. 29, 2001 as US 2001/0047452) which is hereby incorporated herein by reference. In this case, the above-described cartridge connector 40 is a 32-pin connector provided at a far side on an upper surface when the LCD 18 is rendered a front surface (front face), and the communication connector 46 is a 6-pin connector provided at a near side on an upper side.
The wireless communication unit 14 includes a base band IC 50, and the base band IC 50 includes a ROM 52. The ROM 52 contains an OCD (One-Cartridge Download) program, and other programs, for example, and the base band IC 50 is operated according to these programs. It is noted that the One-Cartridge Download program is a program for downloading a program into the child device in an OC mode (one-cartridge mode: a mode in which a game cartridge is attached to the parent device only, and the child device is operated in response to a download of a child device-use program from the parent device cartridge).
The wireless communication unit 14 is further provided with an EEPROM 54, and a user's name, for example, is uniquely set to the EEPROM 54. The base band (Base Band) IC 50 transmits data including the user's name to an RF (Radio Frequency)—IC56, the RF—IC 56 modulates the data, and transmits a radio wave from an antenna 58. However, in an exemplary embodiment, the an intensity of the radio wave is extremely weak, and is set to so small a value that this wave radio is not subject to legal regulation. In addition, this wireless communication unit 14 is provided with a power circuit 60. Typically, the power circuit 60 is a battery, and supplies a DC (direct-current) power source to each component of the wireless communication unit 14.
In addition, in the wireless communication unit 14, the radio wave transmitted from another mobile game apparatus is received by the antenna 58, demodulated by the RF-IC 56, and a demodulated signal is input into the base band IC 50. Therefore, the base band IC 50 decodes the demodulated signal, decodes the data, and transmits the data to the mobile game machine 12, that is, the WRAM 28 via the connectors 48 and 46.
In the wireless communication game system of an embodiment according to the present invention, a plurality of mobile game units 10 as shown in
In addition, in a case that the user's own apparatus 62 participates in a game, the apparatus 62 needs to become the parent device or the child device. In a case that the user's own apparatus becomes the child device, it is necessary to find a parent device capable of participating. When finding the parent device, it is necessary to find a different parent device depending on a case that the user's own apparatus has the cartridge 16.
First, in a case that the user's own apparatus 62 is the mobile game apparatus to which the cartridge 16 is attached shown in
However, in a case that it is intended to use the user's own apparatus as the parent device, the user may simply depress a B button included in the operation key 38.
The reason why only the three parent devices are displayed in the parent device list 18A in
In addition, in the parent device list 18A in
Furthermore, when the all-display flag is turned-off, the parent device list 18A shown in
In the above-described example, the cartridge of Mario Kart-1 (Trademark) is attached to the user's own apparatus (child device). However, in a case of intending to play the game in the OC mode without the cartridge 16 being attached to the user's own apparatus, a parent device list 18A shown in
Next, referring to
Subsequently, when the parent device having the user name “Shiroh” enters the range, a parent device list 18A shown in
Furthermore, when the parent device having the user name “Ichiroh” comes outside the range 64, a parent device list 18A in
In addition, in a case that the user's own apparatus is the parent device, and waits for a new participation of the child device, a child device list 18B shown in
Next, referring to
The parent device packet, as shown in
The parent device packet further includes a flag OC, and this flag OC is a flag showing whether or not possible to be applied to the above-described one cartridge (OC) mode. More specifically, when this flag OC is reset, that is, when OC=0, this means that the game cartridge of the parent device at that time is not applicable to the OC mode, or applicable to the OC mode, however, it is currently played in the normal mode. When the flag OC is set, that is, when OC=1, this means that it is possible to be applicable to the OC mode, and it is currently played in the OC mode. Therefore, a user who does not have the cartridge needs to find the parent device having this flag OC “1”.
Subsequent to the flag OC, the parent device packet includes fields ESlot, USlot, and Payload in this order. The E slot field Eslot is stored with the number of the child device slots available for entry (participation). That is, the slot number that a newly participated child device can use is stored. In the U slot field USlot, a usage situation of the child device slot is stored. More specifically, this is shown in
The payload field Payload is a field for transmitting the game data necessary in a game process, and a field for storing the game data transmitted from the parent device to the child device.
A child device packet transmitted from the child device at the child device slot assigned to the child device is displayed in
In a case that a new child device attempts to connect (Entry) to the parent device under such the situation, the child device number is determined by issuing the child device number CID other than “16” or “130” such as a random number, for example, because, by referring to the U slot field USLot of the parent device, “16” and “130” are used as the child device CID. As one example, it is provided that “86” is determined as the CID of the child device. Therefore, the child device transmits CID=86 to the child device slot (child device slot 2) designated by the ESlot.
Then, the parent device knows, by receiving “86” in the child device slot 2, that the child device having the child device number CID “86” intends to apply for entry. Next, the parent device determines whether or not to accept that entry. In a case of accepting the entry, the parent device broadcasts the parent device packet having “86” set to the area corresponding to the child device slot 2 of the Uslot, which is shown in the lowest column in
In the
In an embodiment in
The memory map of the EEPROM 54 of the wireless communication unit 14 shown in
Referring to the memory map shown in
The parent device list area 80 is an area for temporarily storing/holding the data for displaying the parent device list 18A described earlier in
The parent device list clear timer 82 is a timer for measuring a time period until clearing the data of this parent device list area 80, and as described later, if a time set to this timer 82 is up, the parent device list area 80 is automatically cleared.
The child device list area 84 is an area for temporarily storing/holding the data for displaying the child device list 18B described earlier in
The WRAM 28 further includes the parent device variable area 86 for storing a variable used when the user's own apparatus is operated (behaves) as the parent device, and the child device variable area 88 for storing a variable used when the user's own apparatus is operated (behaves) as the child device.
In the parent device variable area 86, data for the respective fields PID, USlot, and ESlot and the child device number (CID) of the child device subject to connection, and in addition, variables n and m are set. Herein, the variable n indicates the number of slots currently and actually assigned to one child device, and its maximum number is applied by the above-described variable N. In addition, the variable m indicates the number of the child devices currently, actually and simultaneously connected to one parent device, and its maximum number is applied by the above-described variable M.
In the child device variable area 88, data for the field CID shown in
The game variable area 90 is an area for storing game variables of the game being executed such as variables showing the number of cleared stages, an acquired item, and etc, for example. In addition, a transmission buffer 92 and a reception buffer 94 are areas for temporarily storing transmitting data and receiving data, respectively.
More than one mobile game apparatuses 10 each of which has such the structure constructs the game system, and descriptions regarding an operation of each mobile game apparatus 10 in the game system are made below by referring to flow charts.
Prior to the detailed descriptions, in a case that the cartridge not applicable to the OC mode is attached to the user's own apparatus, and the user's own apparatus becomes the parent device, a series of steps S29 (
Furthermore, in a case that although the cartridge applicable to the OC mode is attached to the user's own apparatus, the game is played in the normal mode (not OC mode), when the user's own apparatus becomes the parent device, a series of the steps S29 (
Moreover, in a case that the cartridge applicable to the OC mode is attached to the user's own apparatus, and the game is played in the OC mode, the user's own apparatus cannot function other than the parent device. In this case, via steps S75 and S77 (
In addition, in a case that the cartridge is not attached to the user's own apparatus, the user's own apparatus can only become the child device in the OC mode, and therefore, in this case, a series of steps S111 (
In a case that “NO” is determined in the step S5, that is, in a case that although the cartridge is attached to the user's own apparatus, the cartridge is a cartridge not applicable to the OC mode, the process advances to a step S7 in
Subsequently, in a step S9, it is attempted to receive the parent device packet as shown in
When “NO” is determined in the preceding step S11, or when after finishing registration in the step S15, in a succeeding step S17, it is determined whether or not a value of the parent device list clear timer 82 reset in the preceding step S7 becomes equal to or longer than two seconds. If “YES”, the parent device list 80 is cleared in a step S19, and the parent device list clear timer 82 is reset. Herein, the reason why the parent device list clear timer 82 is reset is that as described above, by referring to
Subsequently, the process advances to a step S27 in
Herein, referring to
In a succeeding step S1003, the processor 20 writes a pseudo random value into the area PID for setting the parent device PID of the parent device variable area 86 (
Subsequently, in a succeeding step S1011, the processor 20 examines the signal from the operation key 38 (
Then, if “NO” is determined in the step S1011, that is, the user of the parent device did not depress the A button, or after executing the step S1015, the processor 20 determines whether or not the start key (not shown) is operated based on the signal from the operation key 38 in a step S1017. If “YES”, the process directly returns. However, if “NO”, in a succeeding step S1021, a transmission/reception process of the parent device shown in detail in
The transmission/reception process of the parent device shown in a step S1019 in
If “NO” is determined in the preceding step S2001, in a succeeding step S2007, the processor 20 determines whether or not no data transmission is made during the past 64 miliseconds. It is noted that a time period of this “64 miliseconds” is an example of a numerical value capable of dissolving a timer deviation, and needless to say, other numerical values may be possible.
If “YES” is determined in the step S2007, using the parent device slot, each data excluding the payload such as the PID, the user name, the game name, the OC flag, the E slot, and the U slot, for example, is transmitted in a step S2009. This step S2009 is a step necessary for enabling the entry from the child device, and even without the payload (data to be transmitted), the data necessary for the entry process (the PID, the user name, the game name, the OC flag, the E slot, and the U slot) is regularly transmitted, thus the child device is always capable of making the entry process. In this step S2009, the payload data is not transmitted. Next, after the step S2009 is ended, or when “NO” is determined in the step S2007, the process returns via the preceding step S2005.
Returning to
When “NO” in the preceding step S1023, or after ending the step S1025, the processor 20 determines whether or not the received CID is the same as the subject to connection CID (that is, it is determined whether or not the received CID is the CID of the child device currently under connection process) in a step S1027. If “NO”, the process returns to the preceding step S1011. If “YES”, that CID is stored in a portion showing the entry slot of the U slot area USlot within the area 86 in
When the actual number of allotted slots n reaches the maximum number of allottable slots N, the entry process toward the child device is ended, and the process advances to a step S1035 in
Subsequently, the processor 20 of the parent device, in a step S1041, increments (+1) the actual number of child devices m, and in a step S1043, determines whether or not the actual number of child devices m becomes equal to the maximum number of child devices to be connected M (varies depending on each game). If “YES” is determined in the step S1043, that is, it is determined that it is not possible to connect more child devices, the process directly returns.
On the contrary, in a case that it is still possible to connect more than one child devices, that is, “NO” is determined in the step S1043, the process returns to the step S1007 in
Thus, the connection process is executed in the step S29 in
Subsequently, it is determined whether or not the game is started in the step S33, that is, the start button (not shown) included in the operation key 38 is depressed. When the start button is depressed, in the succeeding step S35, the processor 20 refers to the U slot area USlot of the parent device variable area 86 shown in
Next, in the step S41, by the transmission/reception process of the parent device described by referring to
Subsequently, in the step S43, the processor 20 determines whether or not the data of a certain child device is not successfully received for more than a predetermined time period t1. Being determined “YES” in this step S43 means that it is probable that the child device has already departed from the communicable range 64 (
When “NO” is determined in the step S43, or after the step S45 is ended, in the succeeding step S47, the processor 20 determines whether or not “ffh” is set to the E slot area ESlot of the parent device variable area 86. If “YES”, in the succeeding step S49, the processor 20 executes the game process according to the game program 62 (
When “NO” is determined in the step S47 in
When “NO” in the preceding step S53, or when the step S55 is ended, the processor 20 determines whether or not the received child device number CID is the same as the subject to connection CID in the step S57. If “YES”, in the succeeding step S59, the child device CID is stored in a portion showing the entry slot of the U slot area USlot of the area 86 in
Subsequently, the processor 20 of the parent device, in the step S67, determines whether or not the actual number of connecting child devices m becomes equal to the maximum number of connectable child devices M. If “YES” is determined in this step S67, that is, it is determined that it is not possible to connect more child device, in the step S69, “ffh” is written into the E slot area ESlot.
It is noted that after the step S69, or when “NO” is determined in the steps S51, S57, S63 or S67, respectively, the process stops the mid-course participation process of the child device in each case, and returns (returns to the step S49 in
The above-described is a case that the cartridge not applicable to the OC mode is attached to the user's own apparatus, and a process of the mobile game apparatus of a case that the user's own apparatus becomes the parent device.
Next, descriptions will be made regarding a process of the mobile game apparatus of a case that the cartridge applicable to the OC mode is attached to the user's own apparatus.
When “YES” is determined in the step S5 in
In a case that the cartridge applicable to the OC mode is attached to the user's own apparatus, and the game of the OC mode is played, the user's own apparatus can only become the parent device. Described in detail, If “NO” in a step S73, that is, in a case that the OC mode is selected, in the succeeding step S75, similar to the preceding step S29 (
The above-described is the process of the mobile game apparatus in a case that the cartridge applicable to the OC mode is attached to the user's own apparatus.
Next, descriptions will be made regarding a case that the cartridge not applicable to the OC mode is attached, and a process of the mobile game apparatus in a case that the user's own apparatus becomes the child device.
When “NO” is determined in the step S27 in
In a step S301, which is a first step in
When “NO” is determined in the step S3003, that is, in a case that the parent device packet of the selected parent device is not successfully received, in a step S3005, it is determined whether or not it is time-out (time is run out), and if “NO” in this step S3005, the process returns to the preceding step S3001. However, if “YES”, the process writes “failure” into a connection result variable (within the area 88 in
When “YES” is determined in the step S3003, that is, when the synchronizing signal of the subject parent device is successfully received, in a step S3009, the processor 20 of the child device resets a synchronizing timer (area 88), and advances to a succeeding step S3011. In this step S3011, the processor 20 renders the pseudo random value the ID number of the child device CID. Next, in a step S3011, it is determined whether or not the child device having the CID at this time is already present. That is, referring to the U slot of the received parent device packet, it is determined whether or not the same CID is already present. In a case that “YES” in the step S3013, it is necessary to change the number once allotted, and therefore, in this case, the step S3011 is once again executed, and by allotting a new number CID, the examination in the step S3013 is once again executed.
The steps S3011 and S3013 are repeated until “NO” is obtained in the step S3013, and when “NO” is obtained, the process advances to a succeeding step S3015. In the step S3015, the number of actually allotted slots n is rendered zero (0), and furthermore, in a succeeding step S3017, the parent device packet is received, and in a step S3019, the synchronizing timer is once again reset. Next, in a step S3021, the processor 20 determines whether or not the E slot ESlot of the received parent device packet (see
When “NO” is determined in the step S3021, the process advances to a step S3023 in
Next, in a succeeding step S3029, the processor 20 of the child device confirms whether or not its own number (CID) is present in an entry slot position of the U slot field of the received parent device packet. Next, if “NO” is determined in this step S3029, in a succeeding step S3031, the processor 20 determines whether or not it is the time-out. In a case that it is not the time-out, the process returns to the preceding step S3017 (
When “YES” is determined in the step S3029, that is, its own number (CID) is present in the entry slot position of the U slot of the received parent device packet, after incrementing (+1) the actual number of allotted slots n in a succeeding step S3033, in a step S3035, it is determined whether or not the actual number of allotted slots n becomes equal to the maximum number of slots N to be allotted to one child device (that is, this N changes depending on a game. A value of 1-4, for example). When “NO” is determined in this step S3035, that is, when it is still possible to allotted the slot, the process returns to the preceding step S3025 so as to receive the parent device packet.
However, if “YES” is determined in the step S3025, assuming that as many slots as possible are assigned, in a succeeding step S3037, “success” is registered in the connection result variable, and the process advances to a succeeding step S3039. In this step S3039, the parent device number PID of the connected parent device and the acquired slot number are stored in the area 88 of the internal RAM 28 of the user's own apparatus (
In the step S85, it is determined whether or not the connection result is “success” by referring to the connection result variable of the area 88. Then, in a case of “NO”, in a succeeding step S87, a message such as “not connected”, for example, is displayed on the LCD 18 of the parent device (
In a case that the connection to the parent device is successful, in a succeeding step S89, the processor 20 of the child device, toward the parent device, uses the parent device slot allotted to the user's own apparatus so as to transmit the user name and the game name of the user's own apparatus. Next, in a step S91, it is determined whether or not to start the game, that is, it is determined whether or not the start button included in the operation key 38 is depressed. If it is detected that the start button is turned-on in this step S91, in a succeeding step S93, the transmission/reception process of the child device is executed.
The transmission/reception process of the child device shown in the step S93 in
Returning to
When “YES” is determined in the preceding step S95, that is, no data has been successfully received from the parent device for more than the predetermined time period t2, in a step S103, a message such as “not communicable with the parent device. Try to restore”, for example, is displayed, and after this, in a step S105, a restoring process is executed.
This restoring process is displayed in detail in
When “NO” is determined in the step S5003, that is, when it is not successful to receive the data of the parent device packet which the user's own apparatus is to be restored, in a succeeding step S5005, it is determined whether or not it is time-out. Then, if “NO”, the process returns to the preceding step S5003, and however, if it is time-out, in a succeeding step S5007, the process writes “failure” in the restoring result variable included in the area 88 shown in
When “YES” is determined in the preceding step S5003, that is, when it is successful to receive the parent device packet from the subject parent device, the synchronizing timer is reset in a succeeding step S5009, and furthermore, in a step S5011, the parent device packet is received. Then, in a step S5013, it is determined whether or not its own number CID is present in the U slot field of the parent device packet. That the number of the user's own apparatus is present in the received parent device packet means that the reason of a state of the communication failure for more than the time period t2 is not an intentional cutting-off by the parent device, and therefore, in a succeeding step S5015, the process registers “success” in the restoring result variable of the area 88 (
It is noted that even if “YES” is determined in the step S5003, if “NO” is determined in the step S5013, the process returns via the preceding step S5007, assuming that the communication cuffing-off results from an intentions of the parent device.
Returning from a subroutine in
The above-described is a case that the cartridge not applicable to the OC mode is attached to the user's own apparatus, and the process of the mobile game apparatus in a case that the user's own apparatus becomes the child device.
Next, descriptions will be made regarding a process of the mobile game apparatus in a case that the cartridge is not attached to the user's own apparatus. However, in this case, the user's own apparatus can merely operate as the child device of the game corresponding to the OC mode.
Returning to
Subsequently, in a step S115 in
In the step S125, it is determined whether or not a value of the parent device clear timer 82 reset in the step S115 becomes equal to or more than “2 seconds”. If “YES”, the parent device list, that is, the parent device list area 80, is cleared in a step S127, and the parent device list clear timer 82 is reset. Subsequently, the process advances to a step S127 similar to a case that “NO” is determined in the step S125.
In the step S127, of the parent device list, the parent device having the E slot not “ffh” and the OC flag “1”, that is, information (user name, game name) of the parent device capable of playing the game in the OC mode, and that does not refuse a participation (entry) of the child device is displayed. This creates, to the user of the child device, a parent device list 18A as shown in
If “YES” is determined in the step S131, the process advances to a step S139 so as to execute a connection process of the child device (
In a step S137, according to the method already described in detail, the connection process of the child device is executed, and in the succeeding step S139, by referring to the connection result variable of the area 88 in
If “YES” is determined in the step S139, the processor 20 transmits toward the parent device that successfully made the connection with the child device the user name of the parent device, and the game name. Subsequently, the process advances to a step S145 in
The above is a process of the mobile game apparatus in a case that the cartridge is not attached to the user's own apparatus.
It is noted that if “NO” is determined in the step S81 in
In addition, if “NO” is determined in the step S79 in
It is noted that in the above embodiment, it is selected whether the user's own apparatus is rendered the parent device or the child device, in tune with progress of the program. However, it may be possible that such the selection is immediately made. In this case, as shown in
Although the present invention has been described and illustrated in detail, it is clearly understood that the same is by way of illustration and example only and is not to be taken by way of limitation, the spirit and scope of the present invention being limited only by the terms of the appended claims.
Number | Date | Country | Kind |
---|---|---|---|
2002-305523 | Oct 2002 | JP | national |
This application is a continuation of U.S. patent application Ser. No. 15/354,246 filed Nov. 17, 2016, which is a continuation of U.S. patent application Ser. No. 15/092,741 filed Apr. 7, 2016, which is a continuation of U.S. patent application Ser. No. 13/830,762 filed Mar. 14, 2013, which is a continuation of U.S. patent application Ser. No. 12/926,381 filed Nov. 15, 2010, which is a continuation of Ser. No. 10/689,073 filed Oct. 21, 2003, which claims priority to Japanese Patent Application No. 2002-305523 filed Oct. 21, 2002. The entire contents of these are incorporated herein in their entirety by reference.
Number | Name | Date | Kind |
---|---|---|---|
4546351 | Nambu | Oct 1985 | A |
5048831 | Sides | Sep 1991 | A |
5428528 | Takenouchi et al. | Jun 1995 | A |
5461608 | Yoshiyama | Oct 1995 | A |
5738583 | Comas et al. | Apr 1998 | A |
5987376 | Olson et al. | Nov 1999 | A |
6045447 | Yoshizawa et al. | Apr 2000 | A |
6175854 | Bretscher | Jan 2001 | B1 |
6183367 | Kaji et al. | Feb 2001 | B1 |
6322451 | Miura | Nov 2001 | B1 |
6354946 | Finn | Mar 2002 | B1 |
6383075 | Jeong et al. | May 2002 | B1 |
6524189 | Rautila | Feb 2003 | B1 |
6699125 | Kirmse et al. | Mar 2004 | B2 |
6733382 | Oe et al. | May 2004 | B2 |
6736727 | Doi et al. | May 2004 | B1 |
6769915 | Murgia et al. | Aug 2004 | B2 |
6785561 | Kim | Aug 2004 | B1 |
6804542 | Haartsen | Oct 2004 | B1 |
6842460 | Olkkonen | Jan 2005 | B1 |
6862737 | Iwamura et al. | Mar 2005 | B1 |
6879570 | Choi | Apr 2005 | B1 |
7177911 | Decarmo | Feb 2007 | B2 |
7491124 | Tanaka et al. | Feb 2009 | B2 |
7729661 | Tanaka et al. | Jun 2010 | B2 |
7756129 | Donaghey | Jul 2010 | B2 |
7780526 | Nguyen et al. | Aug 2010 | B2 |
7929911 | Tanaka et al. | Apr 2011 | B2 |
8073923 | Sasaki et al. | Dec 2011 | B2 |
8296439 | Tanaka et al. | Oct 2012 | B2 |
8442436 | Tanaka et al. | May 2013 | B2 |
8469818 | Tanaka et al. | Jun 2013 | B2 |
8582570 | Donaghey | Nov 2013 | B2 |
8582571 | Donaghey | Nov 2013 | B2 |
8588196 | Donaghey | Nov 2013 | B2 |
8588231 | Donaghey | Nov 2013 | B2 |
8589599 | Donaghey | Nov 2013 | B1 |
8628419 | Tanaka et al. | Jan 2014 | B2 |
8632404 | Tanaka et al. | Jan 2014 | B2 |
8636595 | Tanaka et al. | Jan 2014 | B2 |
8641527 | Tanaka et al. | Feb 2014 | B2 |
8647205 | Tanaka et al. | Feb 2014 | B2 |
8675590 | Donaghey | Mar 2014 | B2 |
8683092 | Donaghey | Mar 2014 | B1 |
8700815 | Donaghey | Apr 2014 | B2 |
8732347 | Donaghey | May 2014 | B2 |
8732361 | Donaghey | May 2014 | B2 |
8734253 | Tanaka et al. | May 2014 | B2 |
8768255 | Tanaka et al. | Jul 2014 | B2 |
8851997 | Tanaka et al. | Oct 2014 | B2 |
8858337 | Tanaka et al. | Oct 2014 | B2 |
8951122 | Tanaka et al. | Feb 2015 | B2 |
8956233 | Tanaka et al. | Feb 2015 | B2 |
8968101 | Tanaka et al. | Mar 2015 | B2 |
9174126 | Tanaka et al. | Nov 2015 | B2 |
9174129 | Tanaka et al. | Nov 2015 | B2 |
9180376 | Tanaka et al. | Nov 2015 | B2 |
9320972 | Tanaka et al. | Apr 2016 | B2 |
9345968 | Tanaka et al. | May 2016 | B2 |
9370715 | Tanaka et al. | Jun 2016 | B2 |
9387404 | Tanaka et al. | Jul 2016 | B2 |
9457267 | Tanaka et al. | Oct 2016 | B2 |
9457268 | Tanaka et al. | Oct 2016 | B2 |
9504915 | Tanaka et al. | Nov 2016 | B2 |
9526986 | Tanaka et al. | Dec 2016 | B2 |
9550117 | Tanaka et al. | Jan 2017 | B2 |
20010008852 | Izumi | Jul 2001 | A1 |
20010012757 | Boyle | Aug 2001 | A1 |
20010029166 | Rune et al. | Oct 2001 | A1 |
20010039212 | Sawano et al. | Nov 2001 | A1 |
20010047452 | Okada et al. | Nov 2001 | A1 |
20020002074 | White et al. | Jan 2002 | A1 |
20020061743 | Hutcheson et al. | May 2002 | A1 |
20020119821 | Sen et al. | Aug 2002 | A1 |
20020160838 | Kim | Oct 2002 | A1 |
20030003994 | Washio | Jan 2003 | A1 |
20030008714 | Tajiri et al. | Jan 2003 | A1 |
20030040347 | Roach et al. | Feb 2003 | A1 |
20030045356 | Thomas | Mar 2003 | A1 |
20030060168 | Teibel | Mar 2003 | A1 |
20030079003 | Burr et al. | Apr 2003 | A1 |
20030114224 | Anttila et al. | Jun 2003 | A1 |
20030124979 | Tanada et al. | Jul 2003 | A1 |
20040063498 | Oakes et al. | Apr 2004 | A1 |
20040082383 | Muncaster et al. | Apr 2004 | A1 |
20040087369 | Tanaka et al. | May 2004 | A1 |
20040128319 | Davis et al. | Jul 2004 | A1 |
20040203354 | Yue | Oct 2004 | A1 |
20050073522 | Aholainen et al. | Apr 2005 | A1 |
20050080896 | Wu | Apr 2005 | A1 |
20050192099 | Nguyen et al. | Sep 2005 | A1 |
20050282639 | Tanaka et al. | Dec 2005 | A1 |
20070197298 | Rowe | Aug 2007 | A1 |
20080171601 | Kirmse et al. | Jul 2008 | A1 |
20090093310 | Tanaka et al. | Apr 2009 | A1 |
20110070950 | Tanaka et al. | Mar 2011 | A1 |
20110281655 | Nguyen et al. | Nov 2011 | A1 |
20130203505 | Tanaka et al. | Aug 2013 | A1 |
20160008719 | Tanaka et al. | Jan 2016 | A1 |
20160220900 | Tanaka et al. | Apr 2016 | A1 |
20170065883 | Tanaka et al. | Mar 2017 | A1 |
20170100663 | Tanaka et al. | Apr 2017 | A1 |
20170113130 | Tanaka et al. | Apr 2017 | A1 |
Number | Date | Country |
---|---|---|
1 145 748 | Oct 2001 | EP |
07-056497 | Mar 1995 | JP |
07-095321 | Apr 1995 | JP |
08-307544 | Nov 1996 | JP |
09-006753 | Jan 1997 | JP |
10-015245 | Jan 1998 | JP |
10-056417 | Feb 1998 | JP |
10-151274 | Jun 1998 | JP |
2867980 | Dec 1998 | JP |
11-033230 | Feb 1999 | JP |
2924828 | May 1999 | JP |
11-207031 | Aug 1999 | JP |
11-308653 | Nov 1999 | JP |
11-355867 | Dec 1999 | JP |
2000-126455 | May 2000 | JP |
2000-135380 | May 2000 | JP |
2000-151641 | May 2000 | JP |
2000-181822 | Jun 2000 | JP |
2000-305885 | Nov 2000 | JP |
2001-038042 | Feb 2001 | JP |
2001-087561 | Apr 2001 | JP |
2001-167036 | Jun 2001 | JP |
2001-168873 | Jun 2001 | JP |
2001-197150 | Jul 2001 | JP |
2001-212365 | Aug 2001 | JP |
2001-298460 | Oct 2001 | JP |
2002-052253 | Feb 2002 | JP |
2002-066143 | Mar 2002 | JP |
2002-111860 | Apr 2002 | JP |
2002-165009 | Jun 2002 | JP |
2002-175234 | Jun 2002 | JP |
2002-189663 | Jul 2002 | JP |
2002-224449 | Aug 2002 | JP |
2002-245269 | Aug 2002 | JP |
2002-280955 | Sep 2002 | JP |
2002-281041 | Sep 2002 | JP |
2003-023661 | Jan 2003 | JP |
2003-024643 | Jan 2003 | JP |
2003-092575 | Mar 2003 | JP |
3421017 | Apr 2003 | JP |
2003-309486 | Oct 2003 | JP |
2004-080400 | Mar 2004 | JP |
2004-136009 | May 2004 | JP |
9323125 | Nov 1993 | WO |
Entry |
---|
V Jumpbooks Game Series for GBA YUU*GI*OU Duel Monsters International World-wide edition, Shueisha Inc., Apr. 23, 2003, first version, lower port of p. 20, 1 page. |
Japanese Office Action for Japanese Serial No. 2004-096954. |
Office Action issued in corresponding Japanese Patent Application No. 2010-200497 dated Oct. 18, 2011. |
Claudia V. Goldman et al., “E-Play,” Multimedia and Expo, 2002, ICME '02, Proceedings, 2002 IEEE International Conference, vol. 2, pp. 321-324. |
Robert N. Smith et al., “An Adaptive Mobile Wireless Handover,” Computer Software and Applications Conference, 1997, COMPSAC '97, Proceedings, The Twenty-First Annual International, pp. 486-492, Aug. 11, 1997. |
Ricky A. Bangun et al., “A Network Architecture for Multiuser Networked Games on Demand,” Information, Communications and Signal Processing, 1997 ICICS, Proceedings of 1997 International Conference, vol. 3, pp. 1815-1819, Sep. 9, 1997. |
Ricky A. Bangun et al., “An Analysis of Multi-Player Network Games Traffic,” Multimedia Signal Processing, 1999 IEEE 3rd Workshop, pp. 3-8, 1999. |
Bluetooth Specification v1.OB, Dec. 1, 1999, pp. 104-107. |
“Master Table of Contents & Compliance Requirements,” Specification of the Bluetooth System Wireless Connections Made Easy, Specification vol. 0, Covered Core Package Version: 1.2, Nov. 5, 2003, pp. 1-1200. |
“Master Table of Contents & Compliance Requirements,” Specification of the Bluetooth System Wireless Connections Made Easy, Specification vol. 0, Covered Core Package Version: 2.0 + EDR, Nov. 4, 2004, pp. 1-1230. |
“Master Table of Contents & Compliance Requirements,” Specification of the Bluetooth System Wireless Connections Made Easy, Specification vol. 0, Covered Core Package Version: 2.1 + EDR, Jul. 26, 2007, pp. 1-1420. |
Specification of the Bluetooth System Wireless Connections Made Easy, Specification vol. 1, Covered Core Package Version: 1.0 B, Dec. 1, 1999, pp. 1-1082. |
Specification of the Bluetooth System, The Ad Hoc Scatternet for Affordable and Highly Functional Wireless Connectivity, Specification vol. 1, Covered Core Package Version: 1.0, Jul. 5, 1999, pp. 1-1082. |
Specification of the Bluetooth System, Specification vol. 1, Version 1.1, Feb. 22, 2001, pp. 1-1084. |
Summons to Attend Oral Proceedings issued on Jul. 8, 2014 in European Application No. 4 252 428, pp. 1-13. |
Sharp Electronics: “Sharp Model YO-500/YO-530—Electronic Organizer Operation Manual,” Jan. 15, 2003, pp. 1-136, XP-002635507. |
Wikipedia—ALOHAnet, retrieved Jun. 20, 2019, 10 pages. https://en.wikipedia.org/wiki/ALOHAnet. |
Raphael Rom et al., “Multiple Access Protocols”, Jun. 1, 1989, XP055595968, pp. 47-62. |
Number | Date | Country | |
---|---|---|---|
20180008892 A1 | Jan 2018 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 15354246 | Nov 2016 | US |
Child | 15709778 | US | |
Parent | 15092741 | Apr 2016 | US |
Child | 15354246 | US | |
Parent | 13830762 | Mar 2013 | US |
Child | 15092741 | US | |
Parent | 12926381 | Nov 2010 | US |
Child | 13830762 | US | |
Parent | 10689073 | Oct 2003 | US |
Child | 12926381 | US |