Abstract:
A communication method by which a first device and a second device each having a wireless interface perform communications, includes a step of making the first device transmit a communication element ensuring request containing a predetermined communication pattern, a step of making the second device judge from a relationship with a self-allocated resource quantity whether a communication having the predetermined communication pattern contained in the communication element ensuring request is acceptable or not, if judged acceptable, generate and transmit a new address, and retain an associated relationship between the new address and the predetermined communication pattern, a step of making the first device transmit predetermined information by use of the new address, and a step of making the second device transfer the predetermined information transmitted by use of the new address with the predetermined communication pattern associated with the new address.

Description:
BACKGROUND OF THE INVENTION  
       [0001]     The invention relates to a technology for communications performed by a first device and a second device that have wireless interfaces.  
         [0002]     A wireless LAN based on IEEE802.11, etc. involves using a common wireless medium for exchanging control information and connection information of a real-time traffic (which hereinafter be abbreviated to RTT) between a station (STA) and an access point (AP).  
         [0003]     In the AP defined as the wireless medium, however, a conflict occurs in the wireless medium because of the same medium similarly receiving the information with respect to a non-real-time traffic (which will hereinafter be abbreviated to NRTT) as well, and hence there arises a problem that it is difficult to ensure a quality of the RTT.  
         [0004]     A scheme (refer to patent document 1) for solving the problem about ensuring the quality of the RTT is that the RTT and the NRTT are distributed by restricting a wireless area with time. This scheme involves employing a system that manages bands utilizable on the AP side after accepting a QoS (Quality of Service) request, checks the conflict and gives a response to the STA. The STA performs a time-based transmission according to the response information.  
         [0005]     Further, the following scheme (refer to patent document 2) is proposed. The STA side classifies the applications according to the RTT and the NRTT, and requests a resource each time in the wireless area with respect to the RTT. The AP side, if possible of allocating the resources, allocates the bands and, if there exist a plurality of requests, allocates an optimum resource to the band in away that adjusts balance between a necessary capacity required for unit time and a capacity on the whole.  
         [0006]     In the former scheme, however, the wireless area is restricted by the time restriction system, and, as a concomitant of this, if no information exists for the time when ensured as the QoS request demands, there occurs a condition that these bands can not be efficiently utilized. Moreover, generally a plurality of terminals reside in the wireless bands, and, in the case of adopting the system that gives the time restriction to the wireless bands, there are affected by an intensity of radio waves, a data loss, etc., resulting in a difficulty of adjustment of timing. Further, the synchronization must be done, and therefore the time coincidence itself requires a complicated function.  
         [0007]     While in the latter scheme, there is a problem of causing a necessity that a resource count be ensure each time. Moreover, a terminal side requesting the utility resource must have traffic occurrence information about the RTT that is used for making a request. Hence, the request is made after monitoring the occurrence information given from the application, and this is not said to be advantageous in terms of the time. Furthermore, there is a possibility that the requests might occur in burst from the plurality of terminals, and, if occurred, a conflict processing algorithm becomes complicated.  
         [0008]     Still further, in both of those schemes, the access from the STA side is the same with the RTT and the NRTT, and hence there still remains a possibility that the RTT might not be ensured due to an encounter with unlawful accessing.  
         [0009]     [Patent Document 1]
        Japanese Patent Application Laid-Open Publication No. 2003-209554        
 
         [0011]     [Patent Document 2]
        Japanese Patent Application Laid-Open Publication No. 2003-169363        
 
       SUMMARY OF THE INVENTION  
       [0013]     It is an object of the invention to provide a technology for ensuring a quality of a specified communication such as RTT, etc.  
         [0014]     The invention was devised to solve the problems and takes the following constructions.  
         [0015]     A first aspect of the present invention is a communication method by which a first device and a second device each having a wireless interface perform communications. In the first aspect of the invention, the first device transmits a communication element ensuring request containing a predetermined communication pattern. The second device judges from a relationship with a self-allocated resource quantity whether a communication having the predetermined communication pattern contained in the communication element ensuring request is acceptable or not, if judged acceptable, generates and transmits a new address, and retains an associated relationship between the new address and the predetermined communication pattern. The first device transmits predetermined information by use of the new address. And the second device transfers the predetermined information transmitted by use of the new address with the predetermined communication pattern associated with the new address.  
         [0016]     According to the invention, only when judging that the quality can be ensured, the new address is generated and transmitted to the first device. Then, only the predetermined information transmitted by using the new address is transferred. Accordingly, even in the case where the first device performs the specified communication such as the RTT, etc., its quality (QoS) can be ensured.  
         [0017]     The communication method of the first aspect of the invention may further comprises, for example, a step of storing the predetermined information transmitted by use of the new address in a memory, and the second device reads the predetermined information from the memory and transfers the predetermined information in accordance with the predetermined communication pattern associated with the new address.  
         [0018]     With this first aspect of the invention, even when the first device performs the specified communication such as the RTT, etc., the quality (QoS) thereof can be ensured. Further, the security can be improved.  
         [0019]     In the communication method, for instance, a single or a plurality of different devices are assigned at least one of a data retaining function, a data collecting function based on the communication element ensuring request and a function of transmitting the information to a network among functions implemented on the second device.  
         [0020]     This exemplifies a distributed example of the functions implemented on the second device.  
         [0021]     In the communication method of the first aspect of the invention, for example, the second device may transmit a transmission permissible period information for accepting the first device. The first device may transmit the transmission permissible period information. And the second device may transfer the retained information in accordance with the transmission permissible period information.  
         [0022]     In the communication method of the first aspect of the invention, for instance, the first device is a mobile communication device, and the second device is a wireless base station.  
         [0023]     This exemplifies the first device and the second device. Therefore, the first device and the second device are not limited to these types of devices. For example, the first device may be a mobile communication device, and the second device may be a mobile support device (Home Agent).  
         [0024]     In the communication method of the first aspect of the invention, for example, the wireless interface possessed by the first device is a normal interface.  
         [0025]     This exemplifies the wireless interface possessed by the first device. Hence, the wireless interface possessed by the first device is not limited to this type of interface.  
         [0026]     Further, the invention can be specified as the invention of the device as follows.  
         [0027]     A second aspect of the present invention is a communication device comprises a creating unit creating a communication element ensuring request, an associating unit associating with an application for making the communication element ensuring request, for a transmitting unit transmitting the communication element ensuring request, and for a performing unit performing the communication by use of the new address with respect to the application that has done the associating, when receiving a new address from a device which received the communication element ensuring request.  
         [0028]     The communication device of the second aspect of the invention may further comprises, for instance, a performing unit performing the communication without using the new address with respect to the application making none of the communication element ensuring request.  
         [0029]     Moreover, the invention can be specified as the invention of the device as follows.  
         [0030]     A third aspect of the present invention is a communication device makes a communication element ensuring request for a plurality of second devices in a network in which there exist the plurality of devices each implementing a function possessed by the second device.  
         [0031]     In the communication device of the third aspect of the invention, for example, the communication element ensuring request is further made for the second device belonging to the neighborhood of a communication destination terminal.  
         [0032]     Further, in the communication device of the third aspect of the invention, for instance, the transmitting unit may further transmit a new communication element ensuring request, thereby changing allocation of resources with respect to a new piece of address information.  
         [0033]     Moreover, in the communication device of the third aspect of the invention, for example, the transmitting unit may further transmit a new communication element ensuring request, thereby requesting, as additional information, an address created afresh by dividing allocation information in the address information.  
         [0034]     The invention can be specified as the invention of the device as below.  
         [0035]     A fourth aspect of the invention is a communication control device comprises a receiving unit receiving a communication element ensuring request containing a predetermined communication pattern from a first device, a creating unit creating a new address associated with the predetermined communication pattern, and a transmitting unit transmitting the new address information to the first device.  
         [0036]     In the communication control device of the fourth aspect of the invention, for instance, the creating unit may generate a random address.  
         [0037]     Moreover, in the communication control device of the fourth aspect of the invention, e.g., a restriction of a predetermined period of time is set in the new address.  
         [0038]     Moreover, the communication control device of the fourth aspect of the invention may further comprises, for instance, a retaining unit retaining, for a fixed period of time, predetermined information transmitted by using the new address from the first device, and a collecting unit collecting and transferring the predetermined information on the basis of a predetermined communication pattern from the retaining unit.  
         [0039]     Still further, in the communication control device of the fourth aspect of the invention, for example, when the first device transmits the new address, period indicating information used by the second device to effect the collection is given to the first device.  
         [0040]     The invention can be specified as the invention of a system as follows.  
         [0041]     A fifth aspect of the invention is a communication system in which a first device and a second device each having a wireless interface perform communications, comprises a first device transmitting a communication element ensuring request containing a predetermined communication pattern, a second device judging from a relationship with a self-allocated resource quantity whether a communication having the predetermined communication pattern contained in the communication element ensuring request is acceptable or not, if judged acceptable, generating a new address, and retaining an associated relationship between the new address and the predetermined communication pattern, and a transmitting unit transmitting the new address from the second device to the first device, wherein the first device transmits the predetermined information by use of the new address, and the second device transfers the predetermined information transmitted by use of the new address, with the predetermined communication pattern associated with the new address.  
         [0042]     Moreover, the invention can be also specified as the invention as a communication control device.  
         [0043]     A sixth aspect of the invention is a communication control device for performing communications with a device for transmitting predetermined information, comprises a receiving unit receiving the predetermined information transmitted from the device, a judging unit judging from a relationship with a self-allocated resource quantity whether a communication having the predetermined communication pattern is acceptable or not, when receiving the predetermined information containing a predetermined communication pattern, a generating unit generating a new address, if judged acceptable, a retaining unit retaining an associated relationship between the new address and the predetermined communication pattern, a providing unit providing the new address to the device, and a transferring unit transferring the predetermined information with the predetermined communication pattern associated with the new address, when receiving the predetermined information transmitted by use of the new address.  
         [0044]     Yet further, the invention can be also specified as the invention of the communication device as below.  
         [0045]     A seventh aspect of the invention is a communication device comprises a first transmitting unit transmitting a communication element ensuring request containing a predetermined communication pattern by use of a first address, a receiving unit receiving a second address transmitted from a device judging from a relationship with a self-allocated resource quantity that a communication having the predetermined communication pattern contained in the communication element ensuring request is acceptable, and a second transmitting unit transmitting the predetermined information by use of the second address.  
         [0046]     The principle of the invention will be explained with reference to the drawings.  
         [0047]      FIG. 1  shows a view of the principle of the invention. As shown in  FIG. 1 , a network system in which the communication method, etc. of the invention is actualized includes a first device m 1 , a second device m 2  connected to a network n 2 , and a wireless communication network n 1  extending between the first device and the second device. The network n 2  is defined as a general type of network such as the Internet, a closed network and so on.  
         [0048]     The first device m 1  has a function of performing communications with the second device m 2  via the wireless communication network n 1 . The first device m 1  makes a communication element ensuring request (containing the predetermined communication pattern according to the invention) for the second device m 2  (S 10 ). For example, when a real-time communication application is started up on the first device m 1 , the first device m 1  makes the communication element ensuring request for the second device m 2 .  
         [0049]     The second device m 2 , after receiving the communication element ensuring request from the first device m 1 , judges based on resource information of a resource allocated to the second device m 2  on the basis of this request within the network whether the requested resource can be provided or not, and, if providable, generates an address for the communication element ensuring request (S 11 ). An associated relationship between the generated address and the communication element ensuring request (containing the predetermined communication pattern according to the invention) received a short while ago, is retained in a request-pattern-to-assigned-address associating (mapping) list.  
         [0050]     The second device m 2  transmits the generated address to the first device m 1  (S 12 ).  
         [0051]     The first device m 1  switches over the real-time communication application to the address given from the second device m 2  (S 13 ).  
         [0052]     The real-time communication application on the first device m 1  sends the predetermined information to the second device m 2  by use of the switched-over new address (S 14 ). The second device m 2  receives and retains a content transmitted from the first device m 1  (S 15 ). The second device m 2  collects the retained information on the basis of the communication element ensuring request (the predetermined communication pattern according to the invention) associated with the address generated in S 11  (S 16 ), and transmits the thus-collected information to the network (S 17 ). Namely, the second device m 2  transfers the predetermined information transmitted by use of the new address from the first device m 1  with the predetermined communication pattern associated with the new address.  
         [0053]     As explained above, the system illustrated in  FIG. 1  includes the first device m 1  that transmits the communication element ensuring request containing the predetermined communication pattern (S 10 ), and the second device m 2  judging from the relation with the self-allocated resource quantity whether the communication having the predetermined communication pattern contained in the communication element ensuring request is acceptable or not, the generating, if judged acceptable, the new address (S 11 ), and retaining the associated relationship between the new address and the predetermined communication pattern. The new address is sent to the first device m 1  from the second device m 2  (S 12 ).  
         [0054]     The first device m 1  transmits the predetermined information by use of the new address given from the second device m 2  (S 14 ). The second device retains the predetermined information sent by use of the new address (S 15 ), and transfers the thus-retained predetermined information with the predetermined communication pattern associated with the new address (S 16 , S 17 ).  
         [0055]     It is therefore possible to ensure the communication quality requested by the first device m 1  (the real-time communication application). Further, the first device m 1  can be utilized by use of the address based on the communication element ensuring request (the predetermined communication pattern according to the invention).  
         [0056]      FIG. 2  shows a second mode of the principle view of the invention. As shown in  FIG. 2 , a different point from  FIG. 1  is that a third device m 3  is assigned part of the functions possessed by the second device m 2 .  
         [0057]     The first device m 1  makes the communication element ensuring request (containing the predetermined communication pattern according to the invention) for the third device m 3  (S 20 ). For example, when the real-time communication application is started up on the first device m 1 , the first device m 1  makes the communication element ensuring request for the third device m 3 . The third device m 3  retains the communication element ensuring request given from the first device m 1  (showing an example of being retained in Hold a in  FIG. 2 ).  
         [0058]     The second device m 2  periodically reads the information (the communication element ensuring request given from the first device m 1 ) retained by the third device m 3 , then judges based on the resource information of the resource allocated to the second device m 2  on the basis of the request within the network whether the requested resource can be provided or not, and, if providable, generates an address for the communication element ensuring request (S 21 ). The associated relationship between the generated address and the communication element ensuring request (containing the predetermined communication pattern according to the invention) received a short while ago, is retained in the request-pattern-to-assigned-address associating (mapping) list.  
         [0059]     The second device m 2  transmits the generated address to the third device m 3  (S 22 ).  
         [0060]     The third device m 3  creates the management information (such as permitting acceptance of a packet, and configuring a retaining target and a function of Hold b) with respect to the address given from the second device m 2  (S 23 ). Thereafter, the third device m 3  transmits to the first device m 1  the address given from the second device m 2  (S 24 ).  
         [0061]     The first device m 1  switches over the real-time communication application to the address given from the third device m 3  (S 25 ).  
         [0062]     The real-time communication application on the first device m 1  sends the predetermined information to the third device m 3  by use of the switched-over new address (S 26 ). The third device m 3  receives the content transmitted from the first device m 1  and retains this content in Hold b (S 27 ) The second device m 2  collects the retained information from Hold b on the basis of the communication element ensuring request (the predetermined communication pattern according to the invention) associated with the address generated in S 21  (S 28 ), and transmits the collected information to the network (S 19 ). Namely, the second device m 2  transfers the predetermined information sent by using the new address from the first device m 1  with the predetermined communication pattern associated with the new address.  
         [0063]     Thus, the third device m 3  (Hold b) is retained with the predetermined information transmitted by use of the new address from the first device m 1 , and the second device m 2  collects the information. With this configuration, it is feasible to restrain the traffic from the terminal m 1 , etc. from directly affecting the second device m 2  in the core-sided network.  
         [0064]     Next, a modified example of the second mode of the principle view of the invention will be explained.  
         [0065]     In  FIG. 2 , the third device m 3  is provided at an anterior sage, while the second device m 2  is provided at a posterior stage, however, the third device m 3  and the second device m 2  may be in such a relationship that these devices serve as terminal points of the network. For example, it can be presumed that the third device m 3  is provided in the vicinity of the first device m 1 , and the second device m 2  is provided in the vicinity of a new device performing communications with the first device m 1 . In this case, it is easy to ensure an interval (gap) size suited to not executing the communication process in the vicinity of the first device m 1  but performing the communications with the new terminal.  
         [0066]     Moreover, if the third device m 3  and the second device m 2  are constructed together, namely, if the second device m 2  is constructed with a multi-stage configuration, the anterior-stage m 2  side provides a selection filtering function in terms of the network resources, while the posterior-stage m 2  side can be made to assure the quality in terms of the interval (gap).  
         [0067]     Further, as for the address generated in S 11  in  FIG. 1  and in S 21  in  FIG. 2 , for instance, as shown in  FIG. 3 , the second device m 2  is provided with a random address generating module and generates an address ( 2 - a ) by use of a random number generated by this random address generating module, and this address may also be associated with the management address. With this scheme, a fluctuation address can be swept out, thereby making it possible to build up a solid architecture in terms of security.  
         [0068]     Moreover, as shown in  FIG. 4 , in addition to the configuration shown in  FIG. 2  or  3 , the third device m 3  (Hold c) may retain (S 31 ) the predetermined information transmitted (S 30 ) from a non-real-time application (or an application that does not use the communication element ensuring request) on the first device m 1  (by use of an address other than the new address), and the second device m 2  may collect, when there is a space area in the resources, the information (S 32 ) and may transmit the collected information to the network (S 33 ).  
         [0069]     Note that the processes in S 30  through S 33  can be, it is considered, operated in parallel with the processes in S 20  through S 29  shown in  FIG. 2  or  3 .  
         [0070]      FIG. 5  shows a third mode of the principle view of the invention. As shown in  FIG. 5 , an example of the construction is that there are one or more devices having the function of the third device m 3 , and the address provided by the second device m 2  is processed in division by a fourth device m 4 .  
         [0071]     The first device m 1  makes the communication element ensuring request (containing the predetermined communication pattern according to the invention) for the third device m 3  (S 40 ). For instance, when the real-time communication application is started up on the first device m 1 , the first device m 1  makes the communication element ensuring request for the third device m 3 . The third device m 3  retains the communication element ensuring request given from the first device m 1  (showing an example of being retained in Hold a in  FIG. 5 ).  
         [0072]     The second device m 2  periodically reads the information (the communication element ensuring request given from the first device m 1 ) retained by the third device m 3 , then judges based on the resource information of the resource allocated to the second device m 2  on the basis of the request within the network whether the requested resource can be provided or not, and, if providable, generates an address for the communication element ensuring request (S 41 ). The associated relationship between the generated address and the communication element ensuring request (containing the predetermined communication pattern according to the invention) received a short while ago, is retained in the request-pattern-to-assigned-address associating (mapping) list.  
         [0073]     The second device m 2  transmits the address generated in S 41  to the fourth device m 4  (S 42 ).  
         [0074]     The fourth device m 4  creates the management information (such as permitting acceptance of a packet, and configuring a retaining target and a function of Hold d) with respect to the address given from the second device m 2  (S 43 ). At this time, the address is sent with a request for no notification of the address.  
         [0075]     The second device m 2  notifies (indication) the third device m 3  of no generation of the address (S 44 ). The third device m 3  transmits the address given from the second device m 2  to the first device m 1  (S 45 ).  
         [0076]     The first device m 1  switches the real-time application to the address given from the third device m 3  (S 46 ).  
         [0077]     The real-time communication application on the first device m 1  sends the predetermined information to the fourth device m 4  by use of the switched-over new address (S 47 ). The fourth device m 4  receives the content transmitted from the first device m 1  and retains this content in Hold d (S 48 ).  
         [0078]     The second device m 2  collects the retained information from Hold don the basis of the communication element ensuring request (the predetermined communication pattern according to the invention) associated with the address generated in S 41  (S 49 ), and transmits the collected information to the network (S 50 ).  
         [0079]     It is to be noted that the third device m 3  (Hold c) may retain (S 52 ) the predetermined information transmitted (S 51 ) from a non-real-time application (or an application that does not use the communication element ensuring request) on the first device m 1  (by use of an address other than the new address), and the second device m 2  may collect, when there is a space area in the resources, the information (S 53 ) and may transmit the collected information to the network (S 54 ).  
         [0080]     Note that the processes in S 51  through S 54  can be, it is considered, operated in parallel with the processes in S 40  through S 49 .  
         [0081]     As discussed above, in the system shown in  FIG. 5 , the process with the communication element ensuring request can be separated by utilizing the network side where there is explicitly the space area, and hence, even when an unlawful load is applied on the third device m 3 , the fourth device m 4  operates independently, thereby enabling the wireless communications of which the quality is ensured.  
         [0082]     An example of the construction of the first device m 1  will be explained with reference to  FIG. 6 .  FIG. 6  is a functional block diagram of the first device m 1 .  
         [0083]     As shown in  FIG. 6 , the first device m 1  includes, for performing the communications, a receiving function c 1 , a transmitting function c 2 , a receipt information identifying function c 3 , an address generating function c 4 , an application management table c 5 , a timer function c 6 , a real-time application c 7 , a non-real-time application c 8  and so on.  
         [0084]     The first device m 1  identifies via the receipt information identifying function c 3  as to whether the signal is a signal for control or not. Then, the first device m 1 , in the case of the signal for the control, generates an address (CoA: Care-of-Address) in the address generating function c 4  when receiving a router advertisement (RA). As for this address generation, there may be available a function of receiving the address based on DHCP (Dynamic Host Configuration Protocol), etc., however, herein the router advertisement is given on the assumption of the mobile IP.  
         [0085]     Further, concerning the application management table c 5  (see  FIG. 8 ), the transfer is conducted when receiving the information, etc. as a result of effecting the transmission as the communication ensuring request demands. The application management table c 5  serves to monitor the timer if there is timer information when making the communication element ensuring request. Further, when receiving the address (RCoA: Rental Care-of-Address) due to the communication element ensuring request, the address generating function c 4  generates the address, and this address is retained in a RCoA field in the application management table c 5 .  
         [0086]     Further, in the case of the normal communication application data, a routing function is applied (executed) to the real-time application c 7  and the non-real-time application c 8  that are related to the address information.  
         [0087]     As to the transmission process from the real-time application c 7  and the non-real-time application c 8 , the communications are performed by using the address associated in the application management table c 5 .  
         [0088]     Moreover, when a period transmission request process is given from the second device m 2  via the receipt information identifying function c 3 , the period transmission request is retained, and the information thereof is sent when transmitting the data from the terminal.  
         [0089]     An example of the construction of the second device m 2  will be explained with reference to  FIG. 7 .  FIG. 7  is a functional block diagram of the second device m 2 .  
         [0090]     As shown in  FIG. 7 , the second device m 2  includes, for performing the communications, a receiving function b 1 , a transmitting function b 2 , buffer management information b 3 , a resource management function b 4 , a timer function b 5 , an address management function b 6 , a request-pattern-to-assigned-address associating (mapping) list b 7 , a filtering management function b 8 , etc.  
         [0091]     The second device m 2  retains the information from the receiving function b 1  on the basis of the buffer management information b 3 . Herein, the buffer is constructed of a common control buffer for retaining the communication element ensuring request, a common data buffer for retaining the information that does not use the communication element ensuring request, and an individual buffer for dynamic management on an individual-address-basis.  
         [0092]     The resource management function b 4  periodically monitors the buffer and collects the storage information thereof.  
         [0093]     The timer function b 5  takes various types of timing depending on a variety of time periods and the content of the communication element ensuring request given from the first device m 1 .  
         [0094]     The address management function b 6  generates the address upon receiving the request from the resource management function b 4 , and transmits the generated address to the source management module b 4 .  
         [0095]     The request-pattern-to-assigned-address associating (mapping) list b 7  is a list used for the resource management function b 4  to manage the request pattern requested by the first device m 1  and the assigned address with respect to this request pattern.  
         [0096]     The resource management function b 4  is capable of providing a restriction to a providing period. Effective time is managed by utilizing the timer function b 5 . Further, the address is registered in the filtering management function for its being stored on the individual buffer by permitting the acceptance about the address. Thereafter, with respect to the buffer management information, an individual buffer generation request is made, and the address is transmitted by using the transmitting function b 2 .  
         [0097]     According to the invention, it is possible to ensure the quality of the specified communication such as RTT, etc. Further, the flexible protocol can be utilized for the core configuration of the network. Still further, the security can be improved and the policies requested can be clearly classified by providing the point capable of controlling by use of only the address desired on the network side. Yet further, the information retained on the routing process side is utilized by way of the open gate, thereby enabling the transmission side to conduct the conscious time management. Moreover, it is feasible to restrain the invalid request from being transmitted in futility across the wireless area. Furthermore, the network linking method and the load-sharing management are facilitated. Still furthermore, when the communication involves using the present system, the information that should be assured just anterior to the communication partner terminal can be provided, and hence the present system becomes superior to other systems in terms of a gap size.  
     
    
     DESCRIPTION OF THE DRAWINGS  
       [0098]      FIG. 1  is a view of the principle of the invention (a first mode);  
         [0099]      FIG. 2  is a view of the principle of the invention (a second mode);  
         [0100]      FIG. 3  is an explanatory view of a modified example of the invention;  
         [0101]      FIG. 4  is an explanatory view of a modified example of the invention;  
         [0102]      FIG. 5  is a view of the principle of the invention (a third mode);  
         [0103]      FIG. 6  is a functional block diagram of a first device m 1 ;  
         [0104]      FIG. 7  is a functional block diagram of a second device m 2 ;  
         [0105]      FIG. 8  is an example of an application management table;  
         [0106]      FIG. 9  is an explanatory view of an outline or architecture of a network system as an embodiment of the invention;  
         [0107]      FIG. 10  is an explanatory view of a communication request allocation process;  
         [0108]      FIG. 11  is an explanatory view of a process of judging whether acceptable or not by analyzing an acceptance pattern on the basis of resources;  
         [0109]      FIG. 12  is an explanatory view of the process of judging whether acceptable or not by analyzing the acceptance pattern on the basis of the resources;  
         [0110]      FIG. 13  is an example of a resource management table;  
         [0111]      FIG. 14  is a buffer management table;  
         [0112]      FIG. 15  is an explanatory view of generating a random address;  
         [0113]      FIG. 16  is an explanatory view of setting effective time;  
         [0114]      FIG. 17  is an explanatory view of a resource updating process;  
         [0115]      FIG. 18  is an explanatory view of a plural communication element ensuring process;  
         [0116]      FIG. 19  is an explanatory view of a buffer management device replay process;  
         [0117]      FIG. 20  is an explanatory view of a period Look-in enable process (a period Look-in gate enable request process);  
         [0118]      FIG. 21  is an explanatory view of the period Look-in enable process (the period Look-in gate enable request process);  
         [0119]      FIG. 22  is an explanatory flowchart of the communication element ensuring request in MN m 1 ;  
         [0120]      FIG. 23  is an explanatory flowchart of a process for the communication element ensuring request in RMA m 2 ;  
         [0121]      FIG. 24  is an explanatory flowchart of a post-acquisition process of an address in the MN m 1 ;  
         [0122]      FIG. 25  is an explanatory flowchart of a reading process from an individual buffer in the RMA m 2 ;  
         [0123]      FIG. 26  is an explanatory flowchart of a transmissible period information registering process in the RMA m 2 ;  
         [0124]      FIG. 27  is an explanatory flowchart of the transmissible period information registering process in the RMA m 2 ; and  
         [0125]      FIG. 28  is an explanatory flowchart of a reading process from a common buffer in the RMA m 2 . 
     
    
     DETAILED DESCRIPTION OF THE INVENTION  
       [0126]     A network system will hereinafter be described by way of an embodiment of the invention with reference to the drawings.  FIG. 9  is an explanatory view of an outline of architecture of the network system as the embodiment of the invention.  
         [0127]     As shown in  FIG. 9 , the network system includes a mobile communication terminal m 1 , a resource management agent (RMA) m 2 , a filter function-implemented router m 3  for buffering, an access point (AP) m 3 - 1 , a bugger m 3 - 2 , a buffer m 3 - 3 , a buffer m 3 - 4 , networks n 1  through n 3 , and so on.  
         [0128]     The mobile communication terminal (which will hereinafter be also abbreviated to MN) m 1  is a Mobile Node (which will hereinafter be abbreviated to MN) or a station (which will hereinafter be abbreviated to STA), and has a function capable of separately utilizing a usage address according to RTT and NRTT.  
         [0129]     The resource management agent (which will hereinafter be also abbreviated to RMA) m 2  has a function of grasping a transmission resource quantity to the mobile communication terminal m 1 , and comprises a process for acquiring information for a self-managed area with respect to each router m 3  and an address management function for transferring the information.  
         [0130]     The buffering filter function-implemented router (which will hereinafter be also termed BFR) m 3  is constructed of the buffers (m 3 - 2 , m 3 - 3 , m 3 - 4 ) having three functions.  
         [0131]     The access point (AP) m 3 - 1  has a function of transferring data from the mobile communication terminal m 1  to the network n 3 . In the following discussion, it is assumed that the BFR m 3  includes this function.  
         [0132]     The buffer m 3 - 2  is a buffer that accepts common QoS (Quality of Service) (which will hereinafter be also referred to as a common acceptance buffer). The buffer m 3 - 3  is a buffer that manages the individual address and conducts the management for every address (which will hereinafter be also called an individual buffer). The buffer m 3 - 4  is a common data transmission buffer (which will hereinafter be also termed a common data transmission buffer).  
         [0133]     The network n 1  is a network to which the mobile communication terminal m 1  belongs when gaining an access. The network N 2  is defined as a wireless communication area. The network n 3  is defined as a backbone for the network.  
         [0134]     (Communication Request Allocation Process)  
         [0135]     A communication request allocation process will be explained with reference to  FIG. 10 .  
         [0136]     In the following discussion, it is assumed that the BFR m 3  is incorporated into the RMA m 2 , thus attaining an integral construction (corresponding to  FIG. 1 ).  
         [0137]     The RMA m 2  having also a function of the access router together sends a router-advertisement at predetermined timing (S 100 ).  
         [0138]     The MN m 1  creates a care-of-address CoA by use of this (S 101 ). The MN m 1  generates a communication element ensuring request (a characteristic requirement of a real-time application). The MN m 1  sends to the RMA m 2  the communication element ensuring request by use of the address CoA created in S 101  (S 102 ).  
         [0139]     The communication element ensuring request includes at least one of a period, time and a pattern (corresponding to a predetermined communication pattern according to the invention) shown in  FIG. 8 . For instance,  FIG. 11  shows, by way of the communication element ensuring request, an example of transmitting Period=ON, Time=0 (instantaneously) and Pattern= 0103 ,  0812 ,  1821 ,  2427 ,  0000  to the RMA m 2  from the MN m 1 . This pattern represents that thirty resources (one box in  FIG. 12  indicates one resource) exist as the resources between the MN m 1  and the RMA m 2  as shown in  FIG. 12 . Among 30 resources,  0103  in the pattern represents a request for three resources from a 01th resource up to a 03th resource,  0812  represents a request for five resources from a 08th resource to a 12th resource,  1821  indicates a request for four resources from an 18th resource to a 21th resource, and  2427  indicates a request for four resources from a 24th resource to a 27th resource, respectively. Note that 0000 represents an end of the request. Incidentally, the pattern shown herein is a numerically-valued (digitized) example with respect to want-to-utilize positions. Further, the time shown herein may be either the normal time or counter information of numerical values digitized.  
         [0140]     The RMA m 2  includes the CoA address with respect to the communication element ensuring request (request condition) given from the MN m 1  and also a control signal (a period, etc.), and therefore stores the communication element ensuring request on a common control buffer (S 103 ) The RMA m 2  periodically reads the communication element ensuring request from the common control buffer (S 104 ).  
         [0141]     The RMA m 2  refers to a resource management table retained by the RMA m 2  itself, and judges based on a self-allocated resource whether it is acceptable or not by analyzing an acceptance pattern. Then, the RMA m 2 , when judging that it is acceptable, generates an access address and sweeps it out.  
         [0142]     An example of this operation will be explained with reference to  FIGS. 11 and 12 . Note that the communication element ensuring requests indicated by the numerals are used as those in common throughout  FIGS. 11 and 12 . In (1) (which is indicated by a circled numeral in  FIGS. 11 and 12 , and the same representation is likewise used hereinafter), the RMA m 2  shows a band quantity allocated to the network, and in this case it follows that 30 resources are given. In (2), a resource request (a predetermined communication pattern) from the MN m 1  is a process requested with this pattern, and the RMA m 2 , the allocation being possible, retains this request pattern and sends an address (RCoA that will be described later on) associated with this pattern to the MN m 1 .  
         [0143]     (3) indicates a residual band of the resources possessed by the RMA m 2 . (4) shows a case in which a new resource request is sent from the MN m 1 , and, the RMA m 2  being unable to assign the process as it is, (5) a location to which the pattern is allocated is searched for by shifting a time-base. In this case, a representation is that a backward shift is done by one. This request pattern is retained as will be explained later on, and the address (RCoA that will hereinafter be described) is sent to the MN m 1 . (6) indicates a residual band of the resources possessed by the RMA m 2 .  
         [0144]     (7) shows a case in which a new resource request is transmitted from the MN m 1 , however, the RMA m 2 , there being no band that meets the request, rejects the acceptance by sending back no address.  
         [0145]     Further, a resource allocation management process in  FIG. 11  involves associating the process with the address.  
         [0146]     Incidentally, though supplementary, the request from the MN m 1  is given a width of request time when making the pattern request, thereby facilitating execution of allocating the resources managed by the RMA m 2 . Then, frequent occurrences of the resource request may be prevented by sending back the time till the resource pattern is started. The address swept out is to be created as an addition on the side of the MN m 1 . It follows that the MN m 1  uses the swept-out address for the application data related to the real-time application. Further, as for the swept-out address, on the side of the RMA, a buffer is generated, and an operation of transmitting the data the network is performed at timing determined inside, thereby actualizing the real-time communications. Moreover, non-real-time information can be utilized by use of the previous address without any change. Each of these points will be explained later on.  
         [0147]     It is judged as described above whether acceptable or not.  
         [0148]     The resource management table (see  FIG. 13 ) retains, as shown in  FIG. 11 , the pattern  0130 ,  0000 . This pattern represents that 30 resources are, as shown in  FIG. 11 , allocated to the RMA m 2 .  
         [0149]     The RMA m 2 , if acceptable, generates a unique rental care-of-address (RCoA) for processing the pattern on the network side (S 105 ).  
         [0150]     Note that with respect to the address (RCoA) generated in S 105 , as shown in  FIG. 15 , a random address is generated (S 105 ) and may be retained in a way that associates this random address with the self-managed address (S 105 ). With this scheme, the fixed address is not always utilized, and hence the security can be strengthened.  
         [0151]     Moreover, when generating the address in S 105 , an effective period of time of this address may also be set (see  FIG. 16 ).  
         [0152]     The RMA m 2  registers the generated address RCoA and the communication element ensuring request (including also, if set, the effective time. See  FIG. 16 ) received a short while ago in the buffer management table shown in  FIG. 14 . The buffer management table (see  FIG. 14 ) retains, as shown in  FIG. 14 , for instance, [ON/ 0 / 0103 ,  0812 ,  1821 ,  2427 ,  0000 /RCoA- 1 / 0 ]. In  FIG. 14 , [RCoA- 1 ] indicates the generated address RCoA, and [ON/ 0 / 0103 ,  0812 ,  1821 ,  2427 ,  0000 ] represents the received communication element ensuring request.  
         [0153]     Further, the RMA m 2 , after retaining the assigned address RCoA for management RCoA information (S 106 ), generates an individual buffer for accepting (retaining) the transmission from RCoA, and, sends RCoA (together with, if set, the effective time. See  FIG. 16 ) to the MN m 1  (S 107 ). It is to be noted that when setting the effective time, for instance, as shown in  FIG. 14 , the individual buffer (refer to B 1   k ) is stored with this effective time, and the request from the address concerned is accepted for only this effective time. If the effective time elapses, the management information is released.  
         [0154]     The MN m 1 , after receiving the address RCoA from the RMA m 2 , (creates and) registers RCoA in its own application management table (S 108 ). Through this process, an address relationship with the real-time application used in the communication element ensuring request is changed from CoA to RCoA.  
         [0155]     Namely, hereafter, the real-time application transmits the data (corresponding to predetermined information according to the invention) to the RMA m 2  by use of RCoA (S 109 ). Note that when receiving together with the effective time, for example, as shown in  FIG. 17 , an update request can be made before the elapse of this effective time.  
         [0156]     The RMA m 2  temporarily stores (buffers) the data, the address RCoA being contained therein, given from the MN m 1  (the real-time application) in the individual buffer individually generated a short while ago for RCoA (S 110 )  FIG. 13  shows a storage example of the individual buffer. The data from the MN m 1  are retained as in the case of m 1  transmission messages  1  through n 1  (data from m 1 ).  
         [0157]     The RMA m 2  reads the information from the individual buffer with a specified period on the basis of the condition information when generating the address RCoA. For example, as shown in  FIG. 11 , when the buffer management table is registered with [RCoA- 1 ] as RCoA and [ON/ 0 / 0103 ,  0812 ,  1821 ,  2427 ,  0000 ] as the pattern, the m 1  transmission message is read from the individual buffer (refer to Blk) of RCoA- 1  with the specified period [ON/ 0 / 0103 ,  0812 ,  1821 ,  2427 ,  0000 ] (S 111 ).  
         [0158]     The RMA m 2  transmits the data read with this specified period to the destination network (S 112 ).  
         [0159]     Next, the processing of the non-real-time application will be explained.  
         [0160]     The non-real-time application transmits the data to the RMA m 2  by using not RCoA but CoA (S 113 ). This is a communication process that does not employ the communication element ensuring request.  
         [0161]     The RMA m 2 , since the data from the MN m 1  (the non-real-time application) contains the address CoA but does not contain the control signal (the communication element ensuring request such as the period, etc.), stores this piece of data on the common buffer (S 114 ).  
         [0162]     The RMA m 2 , if it proves by referring to the self-retained resource management table that there is a space area in the communication resources, reads the storage data from the common buffer and transmits the readout data to the destination network (S 115 ).  
         [0163]     Note that the processes in S 102  through S 112  and the processes in S 113  through S 115  can be, it is considered, executed simultaneously.  
         [0164]     As discussed above, the system shown in  FIG. 9  includes the MN m 1  transmitting the communication element ensuring request containing the predetermined communication pattern (S 102 ), and includes the RMA m 2  for judging whether or not the communication having the predetermined communication pattern contained in the communication element ensuring request is acceptable in the relation with the self-allocated resource quantity, generating the new address if judged acceptable (S 105 ), and retaining the associated relation between this new address and the predetermined communication pattern. The new address is sent to the MN m 1  from the RMA m 2  (S 107 ).  
         [0165]     The MN m 1  transmits the predetermined information by utilizing the new address given from the RMA m 2  (S 109 ). The RMA M 2  retains the predetermined information sent by use of the new address (S 110 ), and transfers the thus-retained predetermined information with the predetermined communication pattern associated with the new address (S 111 , S 112 ).  
         [0166]     It is therefore possible to ensure the communication quality requested by the MN m 1  (the real-time communication application. Further, the MN m 1  can be utilized with the address based on the communication element ensuring request (the predetermined communication pattern according to the invention).  
         [0167]     Moreover, the designation is explicitly given to what executes the resource control about RTT on the network side, and, therefor, the unit time is acquired by using the buffering function and further the gate function with respect to the information stored by the buffering function, whereby the processes based on NRTT and RTT are explicitly separated and the management is conducted on the network side. Accordingly, it follows that the single user can be avoided from falling into a monopolizing status, the information subjected to the transmitting process by the user can not be sent to the network through an initiative operation of the MN m 1 , and the control of transmitting this information to the network is done by the initiative operation of the MN m 1 .  
         [0168]     Further, the RTT of the MN m 1  can be supported on the network side. Namely, when sweeping out the specified address (RCoA in  FIG. 10 ) on the network side, address prefix data possessed by the access point AP (RMA m 2  in  FIG. 10 ) that is different from the control request is transmitted (S 107 ) whereby the RTT process can be clearly separated in the different network by the control process. Moreover, even when the plurality of mobile nodes MN m 1  exist, these can be efficiently managed.  
         [0169]     (Resource Update Request)  
         [0170]     In the case where the MN m 1  creates RCoA in S 108 , if making a new communication element ensuring request (or continuance) with respect to this address RCoA, the address acquisition is conducted by utilizing again the same route as in S 102  through S 107 . This process will be described with reference to  FIG. 17 .  
         [0171]     The MN m 1  generates the communication element ensuring request (a characteristic requirement of the real-time application). The MN m 1  transmits this communication element ensuring request (illustrated as a communication element ensuring request- 2  in  FIG. 17 ) to the RMA m 2  by using the address CoA created in S 101  (S 102 - 1 ).  
         [0172]     The RMA m 2 , since the communication element ensuring requires (request condition) from the MN m 1  contains both the address CoA and the control signal (the period, etc.), stores this communication element ensuring request on the common buffer (S 103 - 1 ).  
         [0173]     The RMA m 2  periodically reads the communication element enduring request from the common control buffer (S 104 - 1 ). The RMA m 2  refers to the self-retained resource management table, then analyzes the acceptance pattern on the basis of the self-allocated resources, and thus judges whether acceptable or not.  
         [0174]     The RMA m 2 , if judged acceptable, generates a unique rental care-of-address (which is the same as RCoA) for processing the pattern on the network side (S 105 - 1 ).  
         [0175]     The RMA m 2  registers the thus-generated address RCoA and the communication element ensuring request (together with, if the effective time is set, this effective time. See  FIG. 16 ) received a short while ago in the buffer management table shown in  FIG. 14 .  
         [0176]     Further, the RMA m 2 , after retaining the assigned address RCoA for the management CoA information (S 106 - 1 ) generates the individual buffer for accepting (retaining) the transmission from RCoA, and transmits RCoA (together with, if the effective time is set, this effective time. See  FIG. 16 ) to the MN m 1  (S 107 - 1 ).  
         [0177]     The MN m 1 , after receiving RCoA from the RMA m 2 , (creates and) registers this address RCoA in its own application management table (S 108 - 1 ). With this scheme, an address relationship with the real-time application utilized in the communication element ensuring request is changed (overwritten) from CoA to RCoA.  
         [0178]     Namely, the real-time application hereafter transmits data to RMAm 2  using RCoA.  
         [0179]     (Plural Communication Element Ensuring Process)  
         [0180]     As described above, there has been discussed the example of generating one address RCoA as the rental address (S 105 ). The scheme is not, however, limited to this and may also be done as follows. For example, as shown in  FIG. 18 , a plurality (two addresses are exemplified in  FIG. 18 ) of rental addresses RCoA and RCoA- 2  are generated (S 105 ) and registered in the buffer management table. Then, after retaining the assigned RCoA for the management CoA information (S 106 ), the individual buffer for accepting (retaining) the transmission from the RCoA may be generated, and RCoA (together with, if the effective time is set, this effective time. See  FIG. 16 ) may be transmitted to the MN m 1  (S 107 ).  
         [0181]     Thus, in the case of performing the real-time communications with the different terminal via the network, when the conditions enabling the communication for requesting the network for the plurality of addresses and the band are settled through negotiation with the destination terminal for communications, the address can be swept out. With this function, the network side can provide the assured communication with the communication partner (terminal).  
         [0182]     (Buffer Management Device Relay Process)  
         [0183]     Next, a buffer management device relay process will be explained with reference to  FIG. 19 .  
         [0184]     In the following discussion, it is assumed that a BFR m 3  and the RMA m 2  are constructed separately (corresponding to  FIG. 2 ).  
         [0185]     The BFR m 3  sends a router advertisement at predetermined timing (S 200 ). The MN m 1  creates a care-of-address CoA by using this (S 201 ).  
         [0186]     The MN m 1  generates the communication element ensuring request (a characteristic requirement of the real-time application). The MN m 1  transmits this communication element ensuring request to the BFR m 3  by using the address CoA created in S 201  (S 202 ).  
         [0187]     The BFR m 3 , as the communication element ensuring request (the request condition) from the MN m 1  contains both the address CoA and the control signal (the period, etc.), stores this communication element ensuring request on the common control buffer (S 203 ).  
         [0188]     The RMA m 2  periodically reads the communication element ensuring request from the common control buffer (S 204 ).  
         [0189]     The RMA m 2  refers to the resource management table, then analyzes the acceptance pattern on the basis of the resource assigned to the m 3 , and thus judges whether acceptable or not.  
         [0190]     The RMA m 2 , if judged acceptable, generates a unique rental care-of-address (RCoA) for processing the pattern on the network side (S 205 ). The RMA m 2  registers the thus-generated address RCoA and the communication element ensuring request received a short while ago in the buffer management table shown in  FIG. 14 . Further, the RMA m 2 , after retaining the assigned RCoA for the management CoA information (S 206 ), notifies the BFR M 3  of the address (S 207 ) The BFR m 3  generates the individual buffer for accepting (retaining) the transmission from RCoA, and transmits RCoA to the MN m 1  (S 208 ).  
         [0191]     The MN m 1 , after receiving the address RCoA from the RMA m 2 , registers this RCoA in its own application management table (S 209 ). With this scheme, the address relationship with the real-time application used in the communication element ensuring request is changed from CoA to RCoA.  
         [0192]     Namely, hereafter, the real-time application transmits the data (corresponding to the predetermined information according to the invention) to the RMA m 2  by use of RCoA (S 210 ).  
         [0193]     The RMA m 2  temporarily stores (buffers), as the data from the MN m 1  (the real-time application) contains the address RCoA, this data in the individual buffer individually generated for RCoA (S 211 ).  FIG. 13  shows a storage example of the individual buffer. The data from the MN m 1  are retained as in the case of m 1  transmission messages  1  through n (data from m 1 ).  
         [0194]     The RMA m 2  reads the information from the individual buffer with a specified period on the basis of the condition information when generating the address RCoA. For example, as shown in  FIG. 11 , when the buffer management table is registered with [RCoA- 1 ] as RCoA and [ON/ 0 / 0103 ,  0812 ,  1821 ,  2427 ,  0000 ] as the pattern, the m 1  transmission message is read from the individual buffer (refer to Blk) of RCoA- 1  with the specified period [ON/ 0 / 0103 ,  0812 ,  1821 ,  2427 ,  0000 ] (S 212 ).  
         [0195]     The RMA m 2  transmits the data read with this specified period to the destination network (S 213 ).  
         [0196]     Next, the processing of the non-real-time application will be explained.  
         [0197]     The non-real-time application transmits the data to the BFR m 3  by using not RCoA but CoA (S 214 ). This is a communication process that does not employ the communication element ensuring request.  
         [0198]     The BFR m 3 , since the data from the MN m 1  (the non-real-time application) contains the address CoA but does not contain the control signal (the communication element ensuring request such as the period, etc.), stores this piece of data on the common buffer (S 215 ).  
         [0199]     The RMA m 2 , if it proves by referring to the self-retained resource management table that there is a space area in the communication resources, reads the storage data from the common buffer and transmits the readout data to the destination network.  
         [0200]     (Period Look-In Enable Request Process)  
         [0201]     Next, a period Look-in enable request process will be described with reference to  FIG. 20 . This process is a process executed after S 200  through S 207  in  FIG. 19  and is a process from S 300  onward in  FIG. 20 .  
         [0202]     The RMA m 2  sends back the RCoA and simultaneously transmits Look-in-Cycle information defined as control information with respect to the transmission data from the side of the MN m 1  (S 300 ). For instance, the MN m 2  creates the Look-in-Cycle information by setting “1” in a data-transmissible resource location and “0” in locations other than this location in a way that refers to the resource management table (refer to a bit string shown in  FIG. 20 ).  
         [0203]     The MN m 1 , after receiving the RCoA from the RMA m 2 , registers this RCoA in its own application management table (S 301 ). With this scheme, the address relationship with the real-time application used in the communication element ensuring request is changed from CoA to RCoA.  
         [0204]     Namely, hereafter, the real-time application transmits the data to the RMA m 2  by use of RCoA (S 302 ).  
         [0205]     The RMA m 2  temporarily stores (buffers), as the data from the MN m 1  (the real-time application) contains the address RCoA, this data in the individual buffer individually generated for RCoA (S 303 ).  FIG. 13  shows a storage example of the individual buffer. The data from the MN m 1  are retained as in the case of m 1  transmission messages  1  through n (data from m 1 ).  
         [0206]     The MN m 1  requests the BFR m 3  for the timing for transmitting the data by sending the Look-in-Cycle information to the BFR m 3  (S 304 ). The BFR m 3  reads the storage data from the individual buffer at the timing in the Look-in-Cycle information and sends the data to the RMA m 2  (S 305 ). The RMA m 2  transmits the data from the BFR m 3  to the destination network (S 306 ).  
         [0207]     Next, the processing of the non-real-time application will be explained.  
         [0208]     The non-real-time application transmits the data to the RMA m 2  by using not RCoA but CoA (S 306 ). This is a communication process that does not employ the communication element ensuring request.  
         [0209]     The RMA m 2 , since the data from the MN m 1  (the non-real-time application) contains the address CoA but does not contain the control signal (the communication element ensuring request such as the period, etc.), stores this piece of data on the common buffer (S 307 ).  
         [0210]     The RMA m 2 , if it proves by referring to the self-retained resource management table that there is a space area in the communication resources, reads the storage data from the common buffer and transmits the readout data to the destination network (S 308 ).  
         [0211]     Note that the processes in S 300  through S 305  and the processes in S 306  through S 308  can be, it is considered, executed simultaneously.  
         [0212]     In this example, the data have already been transmitted, and the pattern for transporting the stored information is transmitted, thereby effecting the transmission based on this pattern.  
         [0213]     Further, the buffering filter-function-implemented router m 3  (or AP) capable of buffering is disposed anterior to the RMA m 2 , thereby retaining the information for a fixed period of time. With this router employed, when a sequence number is assigned to the RTT information, if the radio waves are unstable enough to reach with difficulty, pieces of storage information can be organized (arranged) more surely by transmitting the RTT information a plural number of times.  
         [0214]     (Period Look-in Enable Reservation Process)  
         [0215]     Next, a period Look-in enable reservation process will be described referring to  FIG. 21 . This process is a process executed after S 200  through S 207  in  FIG. 19  and S 300  through S 303  in  FIG. 20 , and is a process from S 309  onward in  FIG. 21 .  
         [0216]     The MN m 1  transmits the Look-in-Cycle information (S 309 ), however, the BFR m 3  performs an operation of retaining the cycle information for a fixed period of time and periodically opening the gate (S 310 ).  
         [0217]     As shown in  FIG. 21 , a different point from in  FIG. 20  is that the process in S 310  is executed earlier and thereafter the process in S 303  can be executed.  
         [0218]     The processes in S 311  through S 314  are the same as the processes in S 305  through S 308  in  FIG. 20 , and hence their explanations are omitted.  
         [0219]     In this example, the gate is periodically started up, and the data coincident with the target time are flowed into the network by transmitting the data with that period. Further, there can be carried out a method of effecting, with the data arrival serving as a trigger, the timing transmission with this pattern.  
         [0220]     (Details of Operation)  
         [0221]     (Communication Element Ensuring Request in MN m 1 )  
         [0222]     The communication element ensuring request in the MN m 1  will be explained referring to  FIG. 22 .  
         [0223]     The MN m 1 , if the received data is a router advertisement (S 400 : Yes) and there is a change in the prefix of the router advertisement (S 401 : Yes), updates the communication address based on this router advertisement (creates the care-of-address CoA) (S 402 ). This is a known mobile IP function.  
         [0224]     Then, the MN m 1 , if it proves by referring to the its own application management table shown in  FIG. 8  that the application for assuring the communication is registered therein (S 403 : Yes), generates the communication element ensuring request information (a characteristic requirement of the real-time application) (S 404 ). The MN m 1  transmits the communication element ensuring request to the RMA m 2  by use of the CoA generated in S 402  a short while ago (S 405 ).  
         [0225]     Whereas if there is no change in the prefix of the router advertisement (S 401 : No) while the application for assuring the communication is registered (S 406 : Yes), and if the RCoA is not ensured for the application for assuring the communication (S 407 : No), in the same way as described above, the communication element ensuring request information is generated (S 404 ) and is transmitted as a message to the RMA m 2  (S 405 ).  
         [0226]     As explained above, the MN m 1 , when the application for assuring the communication is registered, makes the communication element ensuring request.  
         [0227]     (Process for Communication Element Ensuring Request in RMA m 2 )  
         [0228]     The RMA m 2 , as the communication element ensuring request (request condition) from the MN m 1  contains the address CoA and also the control signal (the period, etc.), stores this communication element ensuring request on the common control buffer (S 103 ). This operation has already been explained (see  FIG. 10 ).  
         [0229]     A processing sequence in  FIG. 23  is executed each time (periodic) reading timing given by the timer of the RMA m 2  is reached.  
         [0230]     The RMA m 2 , when the timer gives the reading timing, reads the communication element ensuring request from the common control buffer if stored with this communication element ensuring request (described as an intermediate acceptance message in  FIG. 23 ) (S 500 : Yes). If the CoA associated with the readout communication element ensuring request is not coincident with the already-managed CoA (S 501 : No), the RMA m 2  judges whether or not the communication element ensuring request can be provided on the management resources (S 502 ). To be specific, the RMA m 2  refers to the self-retained resource management table, then analyzes the acceptance pattern based on the self-allocated resources, and thus judges whether acceptable or not. Then, the RMA m 2 , if judged providable (acceptable) (S 502 : Yes), updates an address assigning resource management table (S 503 ). Namely, the RMA m 2  generates a unique rental care-of-address (RCoA) for processing the pattern on the network side (S 105 ), and registers the thus-generated address RCoA and the communication element ensuring request (together with, if the effective time is set, this effective time. See  FIG. 16 ) received a short while ago in the resource management table shown in  FIG. 13 . The RMA m 2  shifts the acceptance message by one and again repeats the processes from S 500  onward.  
         [0231]     While on the other hand, if the CoA associated with the communication element ensuring request read out in S 500  is coincident with the already-managed CoA (S 501 : Yes), the RMA m 2  judges whether or not the communication element ensuring request information has a difference from present one (S 505 ). Then, the RMA M 2 , if not different (S 505 : No), updates the effective time (S 506 ), and sends the address information and the timer information (S 507 ). This operation has already been explained (see  FIG. 8 ).  
         [0232]     Whereas if judged different (S 505 : Yes), the RMA m 2  further judges whether the communication element ensuring request is a dividable request or not (S 508 ). Then, the RMA m 2 , if judged to be the dividable request (S 508 : Yes) and if the division can be properly conducted (S 509 : Yes), generates a new address by effecting the division (S 510 ) then updates the buffer address information management (S 511 ) and sends back the address information (S 512 ). This operation has already been described (see  FIG. 10 ). Note that the judgment as to whether the division can be properly conducted or not (S 509 ) can be, it is considered, made by, for example, the RMA m 2  in a way that refers to its own resource management table.  
         [0233]     Whereas if not the dividable request (S 508 : No), the RMA m 2  further judges whether the request is a communication element change request or not (S 513 ). Then, if judged to be the communication element change request (S 513 : Yes), the RMA m 2  executes the processes in S 502  through S 504 .  
         [0234]     (Post-Acquisition Process of Address in MN m 1 )  
         [0235]     As shown in  FIG. 24 , the MN m 1 , if the received address (RCoA) is neither a new address nor plural addresses (S 600 : No), updates the information as a concomitant of the communication element ensuring request (S 601 ). This operation has already been explained (see  FIG. 17 ).  
         [0236]     While on the other hand, if the received address is the new address or the plural addresses (S 600 : Yes), the MN m 1  further judges whether the request is the dividable request or not (S 602 ). Then, if the request is not the dividable request (S 602 : No), the MN m 1  changes a usage address with respect to the application related to the communication element ensuring request (S 603 ). This operation has already been described (see  FIG. 10 , etc.)  
         [0237]     Whereas if the request is the dividable request (S 602 : Yes), the MN m 1  updates the information as the concomitant of the communication element ensuring request about the old address (S 604 ), and updates also the registration in the management information table about the new address (S 605 ) This operation has already been explained (see  FIG. 10 ).  
         [0238]     (Reading Process from Individual Buffer in RMA m 2 )  
         [0239]     The RMA m 2 , as the data from the MN m 1  (the real-time application) contains the address RCoA, temporarily stores (buffers) this data in the individual buffer individually generated for the RCoA (S 110 ). This operation has already been described (see  FIG. 10 ).  
         [0240]     A processing sequence in  FIG. 25  is executed each time the (periodic) reading timing given by the timer of the RMA m 2  is reached.  
         [0241]     The RMA m 2 , when the timer gives the reading timing, if a registration count in the individual buffer does not show a null status (S 700 : No), executes a process related to the registration (a process related to the individual buffer information in a block shown in  FIG. 14 ), for instance, a process of monitoring the reference Blk for the registration count by referring to the registration count (S 701 ). Then, if data of Blk information for reading exists (S 702 : Yes), the RMA m 2  collects pieces of information from the buffer (S 703 ), and executes a message transmission process (S 704 ). This operation has already been explained (see  FIG. 10 ).  
         [0242]     (Transmittable Period Information Registration Process in RMA m 2 )  
         [0243]     The RMA m 2 , as the data from the MN m 1  (the real-time application) contains the address RCoA, temporarily stores (buffers) this data in the individual buffer individually generated for the RCoA (S 110 ). This operation has already been described (see  FIG. 10 ).  
         [0244]     A processing sequence in  FIG. 26  is executed each time the (periodic) reading timing given by the timer of the RMA m 2  is reached.  
         [0245]     The RMA m 2 , when the timer gives the reading timing, if a registration count in the individual buffer does not show a null status (S 800 : No), executes a process related to the registration (a process related to the individual buffer information in a block shown in  FIG. 14 ), for example, a process of monitoring the reference Blk for the registration count by referring to the registration count (S 801 ). Then, if not finished all about the registration count in the individual buffer (S 802 : No), the RMA m 2  registers transmittable period information (intermediate assigned pattern information in  FIG. 14 , which corresponds, i.e., Look-in-Cycle) to the Blk (S 803 ), and moves the information to Blk next time (S 804 ). The process in S 802  through S 804  is executed for all the registered individual buffers. This operation has already been described (see  FIG. 21 ).  
         [0246]     When the transmittable period information is thus registered in every individual buffer, as shown in  FIG. 27 , the RMA m 2 , if there exists the information that should be transmitted (S 805 : Yes), executes the message transmission process (S 806 ).  
         [0247]     (Reading Process from Common Buffer in RMA m 2 )  
         [0248]     The RMA m 2 , since the data from the MN  1  (the non-real-time application) contains the address CoA but does not contain the control signal (the communication element ensuring request such as the period, etc.), stores the data on the common buffer (S 114 ). This operation has already been described (see  FIG. 10 ).  
         [0249]     A processing sequence in  FIG. 28  is executed each time (periodic) reading timing given by the timer of the RMA m 2  is reached.  
         [0250]     The RMA m 2 , when the timer gives the reading timing, if it proves by referring to its own resource management table that there is a space area in the management resources (S 900 : Yes), further judges whether or not some remaining acceptance messages still exist in the common buffer (S 901 ) Then, if the remaining acceptance messages exist (S 901 : Yes) the RMA m 2  reads the remaining acceptance messages from the common buffer, and executes the message transmission process till the management resources come to a null capacity (S 901 : Yes, S 902 , S 903 : No).  
         [0251]     While on the other hand, if no space area exists in the management resources (S 901 : No), or if transmitted up to the null capacity of the management resources (S 903 : Yes) the RMA m 2  further judges whether or not the acceptance message is left and whether or not the acceptance message is in excess of the retaining effective time (S 904 ). Then, if judged No (S 904 : No), the RMA m 2  returns to S 900 , and repeats the processes once again. Whereas if judged Yes (S 904 : Yes), the RMA m 2  discards the acceptance message (S 905 ), then makes judgment about the next message (S 906 ), and executes the processes from S 904  onward.  
         [0252]     The invention can be carried out in a variety of forms without deviating from the spirit or the principal features thereof. Hence, the embodiment is nothing but a simple exemplification in every aspect. The invention should not be limitedly construed by these descriptions.  
         [0253]     According to the invention, it is possible to ensure the quality of the specified communication such as RTT, etc. Further, the flexible protocol can be utilized for the core configuration of the network. Still further, the security can be improved and the policies requested can be clearly classified by providing the point capable of controlling by use of only the address desired on the network side. Yet further, the information retained on the routing process side is utilized by way of the open gate, thereby enabling the transmission side to conduct the conscious time management. Moreover, it is feasible to restrain the invalid request from being transmitted in futility across the wireless area. Furthermore, the network linking method and the load-sharing management are facilitated. Still furthermore, when the communication involves using the present system, the information that should be assured just anterior to the communication partner terminal can be provided, and hence the present system becomes superior to other systems in terms.