GB2338871A - Integrated information communications system - Google Patents

Integrated information communications system Download PDF

Info

Publication number
GB2338871A
GB2338871A GB9920041A GB9920041A GB2338871A GB 2338871 A GB2338871 A GB 2338871A GB 9920041 A GB9920041 A GB 9920041A GB 9920041 A GB9920041 A GB 9920041A GB 2338871 A GB2338871 A GB 2338871A
Authority
GB
United Kingdom
Prior art keywords
ics
address
packet
corporation
network
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
GB9920041A
Other versions
GB2338871B (en
GB9920041D0 (en
Inventor
Hisao Furukawa
Shoji Miyaguchi
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
DISTRIB SYST RES INST
Distribution Systems Research Institute
Miyaguchi Research Co Ltd
Original Assignee
DISTRIB SYST RES INST
Distribution Systems Research Institute
Miyaguchi Research Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from JP35022497A external-priority patent/JP3084681B2/en
Priority claimed from JP3900798A external-priority patent/JP3000051B2/en
Application filed by DISTRIB SYST RES INST, Distribution Systems Research Institute, Miyaguchi Research Co Ltd filed Critical DISTRIB SYST RES INST
Priority claimed from GB9821661A external-priority patent/GB2332837B/en
Publication of GB9920041D0 publication Critical patent/GB9920041D0/en
Publication of GB2338871A publication Critical patent/GB2338871A/en
Application granted granted Critical
Publication of GB2338871B publication Critical patent/GB2338871B/en
Anticipated expiration legal-status Critical
Expired - Fee Related legal-status Critical Current

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/14Charging, metering or billing arrangements for data wireline or wireless communications
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46Interconnection of networks
    • H04L12/4604LAN interconnection over a backbone network, e.g. Internet, Frame Relay
    • H04L12/4608LAN interconnection over ATM networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46Interconnection of networks
    • H04L12/4604LAN interconnection over a backbone network, e.g. Internet, Frame Relay
    • H04L12/462LAN interconnection over a bridge based backbone
    • H04L12/4625Single bridge functionality, e.g. connection of two networks over a single bridge
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/66Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/74Address processing for routing
    • H04L45/742Route cache; Operation thereof
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/09Mapping addresses
    • H04L61/25Mapping addresses of the same type
    • H04L61/2503Translation of Internet protocol [IP] addresses
    • H04L61/2514Translation of Internet protocol [IP] addresses between local and global IP addresses
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/09Mapping addresses
    • H04L61/25Mapping addresses of the same type
    • H04L61/2503Translation of Internet protocol [IP] addresses
    • H04L61/2521Translation architectures other than single NAT servers
    • H04L61/2535Multiple local networks, e.g. resolving potential IP address conflicts
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/45Network directories; Name-to-address mapping
    • H04L61/4505Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/45Network directories; Name-to-address mapping
    • H04L61/4557Directories for hybrid networks, e.g. including telephone numbers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/02Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
    • H04L63/0272Virtual private networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/04Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • H04L63/0435Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload wherein the sending and receiving network entities apply symmetric encryption, i.e. same key used for encryption and decryption
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/12Applying verification of the received information
    • H04L63/123Applying verification of the received information received data contents, e.g. message integrity
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22Parsing or analysis of headers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/54Store-and-forward switching systems 
    • H04L12/56Packet switching systems
    • H04L12/5601Transfer mode dependent, e.g. ATM
    • H04L2012/5638Services, e.g. multimedia, GOS, QOS
    • H04L2012/5646Cell characteristics, e.g. loss, delay, jitter, sequence integrity
    • H04L2012/5652Cell construction, e.g. including header, packetisation, depacketisation, assembly, reassembly
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/54Store-and-forward switching systems 
    • H04L12/56Packet switching systems
    • H04L12/5601Transfer mode dependent, e.g. ATM
    • H04L2012/5685Addressing issues
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2212/00Encapsulation of packets
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/08Protocols for interworking; Protocol conversion
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/18Multiprotocol handlers, e.g. single devices capable of handling multiple protocols

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Radio Relay Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

To provide an integrated information communications system (ICS) 20000-1 without using dedicated lines or the Internet, ensuring communication speed, communication quality, communication trouble countermeasures in a unified manner, wherein security and reliability in communication is ensured, the system is comprised of an access control apparatus for connecting a plurality of computer communication networks or information communication equipment (e.g. LANs) to each, and a relay device for networking the aforementioned access control apparatus, the system having functions for performing routing by transferring information by a unified address system ADS), and is configured such that the aforementioned plurality of computer communication networks or information communication equipment can perform communications in an interactive manner. The ICS user address 4520 and ICS network address 7920 of the other party to the communication are obtained as an ICS domain name which is a telephone number, and said ICS network address is held in a conversion table 20013-1 within access control apparatus 20010-1 at a call side. For example, the telephone number 81-3-1234-5678 becomes domain name "5678. 32. 12. 3.81."

Description

2338871 INTEGRATED INMIMTION CUMMUNICATION SYSTEM
BAC2921QUM OF THE INVENTI 1. Field of the Invention
The present invention relates to an integrated information camunication system connecting information camunication equipments or information ceimunication system such as and/or for personal carputer, LAN (Local Area Network), telephone (including cellular phone), FAX (Facsimile), CATV (Cable Television), Internet and the like, not only via dedicated lines, but also via ISDN (Integrated Services Digital Network), FR (Frame Relay), ATM (Asynchronous Transfer Mode), IPX (Integrated Packet Exchange), satellite, wireless and public lines. Here, integrated information mmunication equipments perform mmuni-cation provided with an address (for information cenTminication) for distinguishing the integrated information ccnym=cation equipment with other equipment. Particularly, the present invention relates to an integrated information communication system which integrates data transfer services based on connection-less networks (e.g., RFC791 or RFC1883 IP (Internet Protocol) technology) and irrprx)ves the overall economics of the information cammucation system by employing a unified address system, and ensuring security to realize interactive ccmainications between connected terminals or system. 2. Description of the Prior Art
In accordance with =inputer and information mmunication 1 technology, cmWter cammnication networks have in recent years cam to be widely used in universities, research institutes, gave=mbent organizations, and intra-corporation/inter-corporation situations. LANs are used for intra-corporation conTminication networks, and in the event that the geographic locale is on a national basis. the form thereof beccms such as sown in FIG.1. In the exarrple described in FIGA, each local LAN uses a ccemon protocol, with each being connected by dedicated lines. Here, e.g., a corporation X has LAN-X 1, LAWX2 and LAN-M as LANs, a corporation Y has LAWY1, LAWY2 and LAWY3 as LANs, and both corporations X and Y use c=unication address systems ADX and ADY for performing cter ccmmnlcations. Since it is necessary to lay a separate dedicated line for each corporation with such a LAN network, system architecture becemes costly, and in the event that connection is to be made to a LAN network of another corporation, interfacing mast be matched such as the communication address system, making interconnection very difficult and very costly.
On the other hand, the Internet has recently become, widespread as a global-scale computer cenymmication network. On the Internet, networks are connected using a router of a provider, a ocnTmmicatim protocol called TCP/IP (Transmission Control Protocol/Internet Protocol) is employed, dedicated lines or FR networks are used for connecting remote areas, and Ethernets which are 10 Mbps LANs or FDDIs (Fiber Distributed Data Interface) which are 10 Mbps LANs are used as cenmriication paths within st-ructures. FIG.2 shows an e"Tle of an 2 Internet connection, in which the routers in the providers maintain mutual connection by exchanging routing table connection information. Each router is connected to a plurality of networks, and judgment is made based on the routing table regard-ing to which router connected to which provider' s network received data should go next. Thus, on the Internet, the IP address attached to each IP packet (IP datagram) is checked, judt is made to which router the IP packet should be sent, and that IP packet is sent accordingly. Thus, IP packets are transferred one after another and delivered to the destination cter, by weans of all routers performing the abave-described operation.
FIG.3 illustrates the information contents of an RFC791 IP packet used by the Internet, divided into a control field and a data field. FIG.4 illustrates the information contents of a similar RM1883, divided into a control field and a data field. In either figure, the parentheses () indicate the number of bits.
However, with the Internet, the path control is restricted by IP, so that one cannot tell whether the other party with which communication is being made is the authorized party, and the system is such that the =runication path is not administrated in an integrated manner, meaning that there are problem regarding security in that information may be eavesdropped. Also, in reality, addresses within the LANs are being separately decided by the LAN users, so there is the necessity to replace the LAN user addresses when connecting the LAN to the Internet. Also, conmmication quality such as 3 cemameation speed and ceunmication error rate for the trunk lines making up the Internet camunicatlon path differ fram one line to another for each LAN, and are practically non-uniform. Also, there are problems such as an atteffpt to send a 10 Mbps TV signal for videoconferencing not ach- ieving the desired cemm=cation speed. Further, there is no administrator for performing maintenance of the network such as in the case of failure, of for integrating the overall network for future planning for the network and so forth. Also, with LAN networks and the Internet, the terminals are personal camputers (ccirputer,s), and it has been difficult to use telephones, FAX and CATV in an integrated manner therein.
SZJV OF THE-INVENTION The present embodiment has been made in accordance with the above- described situations, and it is an object of the present invention to provide an integrated information communication systern capable of containing a plurality of VANs which perform IP packet transfer of which security and reliability in ccmmnications has been ensured, by means of not using dedicated lines or the Internet so as to improve econamic considerations of the information can=ication systern architecture, and ensuring ccnmmcation speed, ceunmucation quality and cenTm=cation trouble countermeasure in a unIfied manner. Also, it is another object of the present invention to provide an integrated information c=unication system which uses a single information transfer which is not dependent on the type of service, 4 such as sound, image (motion and still), text, etc., so as to interconnect services which have conventionally been provided separately, such as total camunication services, analog/digital telephone line services, Internet provider services, FAX services, camputer data exchange services, CATV services and so forth. Further, it is another object of the present invention to provide an integrated information cemmunication system which enables inter-corporation conTainication with very little change to the cmWter canmnication address system which have been independently and separately created within each separate corporation (including universities, research institutes, goverrt organizations, etc.).
The present invention relates to an integrated information communication system, and the above objects of the present invention are realized as follows: the present invention is configured by providing an access control apparatus for connecting a plurality of computer cunication networks or information ccnnuucation equipment to each, and a relay device for networking the aforementioned access control apparatus, the system having functions for performing routing by transferring information by a unified address system, and is configures such that the aforementioned plurality of camputer c=unication networks or information communication equipments can perform ccffnmications in an interactive manner. In FIG.1 which is given as an example of a conventional arrangement, the range of dedicated lines used for intra-corporation and inter-corporation czemunications is indicated by solid lines, and F this is replaced with the equivalent of a cter ccnmmications network according to IP as a cwmn c=unication network indicated by broken lines.
The abave-described objects of the present invention are achieved by an ICS user packet having a unique ICS user address systern ADx being converted into an ICS network packet having an address systern ADS, based on the administration of a conversion table provided within an access control apparatus, and by being arranged such that in the case that transmission is made over at least one VAN contained therein following rules of the aforemmtioned address system ADS, and the destination other access control apparatus is reached, conversion is made to the aforementioned ICS user address systern ADX based on the administration of the aforementioned conversion table, and another external information ccnTminication apparatus is reached. Also, the above-described objects of the present invention are achieved by an ICS user packet having a unique ICS user address systern ADX being converted into an ICS network packet corresponding with a reception ICS network address registered beforehand to the conversion table in accordance with a user logic cominication line, rather than using an ICS user address within the aforementioned ICS user packet based m the administration of a conversion table provided within the access control apparatus, and by being arranged such that in the case that transmission of the aforementioned ICS network packet is rnade to another access control apparatus via at least one VAN following rules of the ICS address systern ADS, the transfer destination of the 6 aforementioned ICS network packet being either 1 or N, this is returned to the aforementioned ICS network packet based on the administration of a conversion table provided within the aforementioned access control apparatus, and another external informtion communication apparatus is reached.
BRIEF DESCRIPTION OF THE DRANIMR
In the accompanying drawings:
FIG.1 is a block diagram to explain a conventional LAN network; FIG.2 is a diagram illustrating a form of Internet; FIG.3 is a diagram illustrating an IP packet according to RFC791 stipulation; FIG.4 is a diagram illustrating an IP packet according to RFC1883 stipulation; FIG.5 is a block diagram systematically illustrating the basic principle of the present invention; FIG.6 is a block diagram illustrating an example of a network wherein an ICS according to the present invention is constructed of plurality of VANs; FIG.7 is a block diagram illustrating an example of configuring the access control apparatus; FIG.8 is a block diagram illustrating an example of configuring the relay apparatus; FIG.9 is a block diagram illustrating an example of configuring the inter- VAN gateway; 7 FIG.10 is a block diagram L1lustrating an example of configuring the ICS network server; FIG.11 is an array diagram illustrating an example of the ICS user address used in the present invention; FIG. 12 is a wiring diagram illustrating the connection relation between the ICS logic terminal and user ccnyminication line; FIG.13 is a diagram L1lustrating the relation between the ICS user packet and the ICS network packet, used in the present invention; FIG.14 is a portion of a constructional block drawing illustrating a first ent)odt (intra-corporation ccnmriicatim, inter-corporation canTunication) according to the present invention..
FIG.15 is a portion of a constructional block drawing illustrating a first entxxUmnt according to the present invention; FIG.16 is a diagram to show an exarrple of a conversion table; FIG.17 is a diagram to show an example of a temporary conversion table; FIG.18 is a flowchart illustrating an example of operation of the access control apparatus; FIG.19 is a flowchart illustrating an example of operation of the access control apparatus in inter-corporation c=unication; FIG.20 is a constructional block drawing illustrating a second embodiment (virtual dedicated lme) according to the present invention; FIG.21 is a diagram to show an example of the conversion table; 8 FIG.22 is a flowchart illustrating an example of operation of the access control apparatus in virtual dedicated line connection; FIG.23 is a diagram to show an example of formiat of NSAP type ATM address; FIG.24 is a diagram to show an information unit of ATM cell type; FIG.25 is a diagram to explain convexsion/restoring operation between ICS network packet and CKS packet; FIG.26 is a diagrain to explain dissolution/assernbly between CKS frame and cell; FIG.27 is a portion of a constructional block showing a 3rd embodiment (embodiment using ATM network) according to the present invention; FIG.28 is a portion of a constructional block shg a 3rd embodiment according to the present invention; FIG.29 is a diagrarn to show an example of an ATM address conversion table and a VC address conversion table; FIG.30 is a diagram to show an example of an ATM address conversion table and a VC address conversion table; FIG. 31 is a flowchart to show a flow of packet using SVC and PVC; FIG.32 is a flowchart to show a flow of packet using SVC and PVC; FIGs.33 and 34 are block diagrams to show 1:N ccumunication or N: 1 c=mication using PVC; 9 FIGs.35 and 36 are block diagrams to show N:N cenrunication using PVC; FIG.37 is a diagram to shaw an example of FR frame address port-ion; FIG.38 is a diagram to shaw a variation between ICS network packet and FR frame; FIG.39 is a portion of a constructional block showing a fourth embodiment (enbodiment using FR network) according to the present invention; FIG.40 is a portion of a constructional block showing a fourth effbodiment according to the present invention..
FIG.41 is a diagram to shaw an example of an FR address conversion table and a MC address conversion table; FIG.42 is a diagram to show an example of an FR address conversion table and a MC address conversion table; FIG. 43 is a flowchart to show a flaw of packet using SVC and PVC; FIG. 44 is a flowchart to shaw a flow of using SVC and PVC; FIGs.45 and 46 are block diagrams to show l:N carnunication or N:1 c=nunication using PVC; FIGs.47 and 48 are block diagrams to show N:N ceninLinication using PVC; FIG.49 is a portion of a constructional block shawing a fifth embodimnt(acczfftion of telephone line, ISDN line, CATV line, satellite line, M line, cellular phone line) according to the present invention; FIG. 50 is a portion of a constructional block showing a fifth entxxhrent according to the present invention; FIG.51 is a portion of a constructional block showing a fifth ewbodinv-. nt according to the present invention; FIG.52 is a portion of a constructional block showing a fifth ewbodiment according to the present invention; FIG.53 shows an example of the conversion table; FIG. 54 is a flowchart to show an operation of a fifth embodiment; FIG.55 is a portion of a constructional block showing a sixth entxxbzent according to the present invention; FIG.56 is a portion of a constructional block showing a sixth ewbodiment according to the present invention; FIG. 57 is a portion of a constructional block showing a sixth entxxbnmt according to the present invention; FIG.58 is a diagram to show an example of description of router table in a dial-up router;
FIG. 59 is a flowchart to show an operation of a sixth entxxlirrv-.nt; FIG.60 is a constructional block showing a seventh embodinmt (ICS address administration server) according to the present invention; FIG. 61 is constructional block showing an eighth embodiment(fill 1 - duplex czmnunication including a satellite communication 11 path) according to the present invention; FIG.62 is a timing chart to show an example of operation of a full-duplex cenTnLmication by TCP; FIG.63 is a timing chart to explain an eighth entx)diment; FIG.64 is a timing chart to explain an eighth embodiment; FIG.65 is a timing chart to explain an eighth embodinimt; FIG.66 is a constructional block showing a variation of an eighth embodiment; FIG.67 is a timing chart to show an operation of a ninth embodiment (fi 111 -duplex cammanication including a satellite cenvun-ication path) according to the present invention; FIG.68 is a timing chart to explain a ninth embodiment; FIG.69 is a timing chart to explain a ninth embodiment; FIG.70 is a timing chart to explain a tenth ewbodiment; FIG.71 is a timing chart to explain a tenth embodiment; FIG.72 is a timing chart to explain an eleventh embodiment; FIG.73 s a constructional block showing a twelfth embodiment (full-duplex cermunication path) according to the present invention; FIG.74 is a timing chart to show an operation of a twelfth embodiment; FIG.75 is a constructional block to show a variation of a twelfth embodiment; FIG.76 is a diagram to show an example of TCP fr ame FIG.77 is a diagram to show an example of UDP frame; FIG.78 is a portion of a constructional block showing a 12 thirteenth effbodiweent(control of receiving priority degree) according to the present invention; FIG.79 is a portion of a constructional block showing a thixteenth embodiment according to the present invention; FIG.80 is a portion of a diagram, to explain a thirteenth entxxlt; FIG.81 is a portion of a diagram to explain a thirteenth embodiment; FIG.82 is a flowchart to show an operation to decide a degree of priority; FIG.83 is a constructional block showing a 14t" embodiment (control of transmitting priority degree) according to the present invention; FIGs.84and 85 are diagrams to show an example of a conversion table using in a 14th embodinmt; FIG.86 is a flowchart to show an operation of priority decision in a 14th adxxbzp-nt; FIG.87 is a constructional block showing a 15t1' embodimnt (multiplex communication) according to the present invention; FIG.88 is a diagram to show an example of a conversion table using in a 15th embodiment; FIG.89 is a diagram to show an example of a conversion table using in a 15th embodimmt; FIG.90 is a constructional block to show a variation of a 15th entxxbirent; 13 a constructional block showing a 16' according to the present invention; a constructional block showing a W" present invention.. explain a 16th ent)odiment; FIG.91 is a portion of embodimant(operation of ICS) FIG. 92 is a portion of embodiment according to the FIG.93 is a diagram to FIG.94 is a diagram to explain a 16th embodiment FIG.95 is a diagram to explain a 16th embodiment; FIG.96 is a diagram to explain a 16t' embodiment; FIG.97 is a diagram to explain a 16'd' embodiment FIG.98 is a diagram to explain a 16th embodiment; FIG.99 is a diagram to explain a 16th entx)dinmt; FIG.100 is a diagram to show an exarrple of an ICS network address appropriation record table using in a 16th enbodinv-.nt; FIG.101 is a diagram to show an example of an ICS user address appropriation record table using in a 16th embodiment; FIG.102 is a diagram to show an example of a conversion table using in a At" enbodiment; FIG.103 is a diagram to show an example of a conversion table using in a 16th embodiment; FIG.104 is a diagram to show an example of a conversion table using in a 16th embodiment; FIG. 105 is a procedure chart to explain a 16th embodiment; FIG.106 is a diagram to show an example of a conversion table using in a 16'd' embodiment; FIG. 107 is a procedure chart to explain a 16th embodiment; 14 FIG. 108 is a diagram to show an example of a conversion table using in a 16t" embodiment; FIG.109 is a diagram to explain a demain name server; FIG.110 is a diagram to explain a damain name server; FIG.111 is a diagram to explain a damain name server; FIG.112 is a diagram to explain a damain name server; FIG.113 is a diagram to explain a call of a damain name server; FIG.114 is a diagram to explain re-writing of a conversion table from an IP texminal; FIG.115 is a diagram to explain re-writing of a conversion table from an IP terminal; FIG.116 is a constructional block showing a lld' embodiment (calling of a ccorm-inicator by telephone narber) according to the present invention; FIG.117 is a diagram to show an example of a conversion table; FIG.116 is a diagram to explain an 17t" ffdxxlt; FIG.118 is a diagram to show an example of an inner table using in a 17t" aTbodirnent; FIG.119 is a diagram to show an example of an inner table using in a 17th embodiment; FIG.120 is a diagram to show an example of an inner table using in a 17"' anbodiment; FIG.121 is a diagram to explain a call of a damain name server; FIG.123 is a portion of a constructional block showing a 18th embodiment (IP te=dnal to be connected with plural access control apparatuses) according to the present invention; FIG. 124 is a portion of a constructional block showing a At" embodiment according to the present invention; FIG.125 is a diagram to show an example of a verifying server; FIG.126 is a diagram, to show an example of a conversion table; FIG.127 is a timing chart to explain register procedure fran a hem IP terminal; FIG.128 is a diagram to explain an accessing method of an verifying server; FIG.129 is a diagram to show an example of an inner table using in a 18t1' entxxlt, FIG.130 is a diagram to show an example of an inner table using in a 18th wt)odt; FIG.131 is a diagram to show an example of an inner table using in a 18t" embodiment; FIG.132 is a block diagram to show a call of an verifying server; FIG.133 a portion of a constructional block diagrarn illustrating a 10' entxxUment (closed-zone network conTnanication and open-zone ixncation used network discriminator) according to the present invention; FIG.134 is a portion of a constructional block diagram, illustrating a 19th embodirrent according to the present invention FIG.135 is a portion of a constructional block diagram illustrating a 19t" effbodiment according to the present invention; 16 FIG. 136 illustrating FIG.137 used in a 19th FIG.138 in a 19th FIG.139 used in a 19th FIG.140 is a portion of a constructional block diagram a 19t1' embodiment according to the present invention; is a diagram to show an example of a conversion table entxxlt; is a diagram to show an example of a conversion table embodiment; is a diagram to show an example of a conversion table embodiment; is a diagram to show an example of a conversion table used in a 19th embodiment; FIG-141 is a flowchart to show an example of an operation of a 19th embodiment; FIG.142 is a flowchart to show an example of an operation of a 19th embodiment; FIG.143 is a portion of a constructional block diagram:illustrating a 20th wbodimnt (IP terminal to be connected with Plural access control apparatus having network identifier) according to the present invention; FIG.144 is a portion of a constructional block diagram illustrating a 20th ent)odinmt according to the present invention; FIG.145 is a diagram to show an example of a verifying server used in a 20'h embodiment; FIG.146 is a diagram to show an example of a conversion table used in a 20th embodiment; FIG.147 is a signal flowchart to explain an operation of a 20th 1 7 embodiment; FIG.148 is a diagram to explain a 20th embodiment; FIG. 149 is a diagram to explain a 20th entxxliment; FIG.150 is a diagram to explain a 20':" embodiment; FIG.151 is a diagram to explain a 20th embodiment; FIG.152 is a diagram to explain a 20th embodiment; and FIG. 153 is a diagram to explain a 20'l' embodiment.
DE=PTION OF = PRE11EM- EMBODIMENTS FIG.5 systematically illustrates the basic principle of the present invention, wherein the integrated information communication system (hereafter referred to as 44 ICS") 1 according to the present invention has self-appointed address providing rules as a cter information/conm.mication address. i.e., the system has a unique address system ADS, and has access control apparatuses (2 through 7 in the present exarrple) which serve as access points for connecting a plurality of =rputer cenTm=cation networks or information communication equipments, e.g., a great number of LANs (in the present example, corporation X ' s LAN-Xl, LAN-X2 and LAN-M, and corporation Y' s LAWY1, LAWY2 and LAWY3). Here, corporation X' s LAN-Xl, LAWX2 and LAN-M have the same address system ADX, and corporation Y ' s LAWY1, LAWY2 and LAN-Y3 have the same address system ADY. The access control apparatuses 2, 3 and 4 have conversion tables for administrating mutual conversion between the address system ADS and the address system ADX. The access control apparatuses 5, 6 and 7 18 have conversion tables for administrating mutual conversion between the address system ADS and the address system ADY. The ccoputer communication data (ICS packet) within the ICS 1 uses addresses according to the address system ADS of the ICS 1, and performs IP communication such as is used on the Internet.
Now, description will be made regarding the operation in the case of conTaziication within a single corporation. The mrputer cenTmrdcation data (ICS packet) 80 transmitted from the LAN-Xl of the corporation X is provided with addressing following the address system ADX, but ls subjected to address conversion following the address system ADS under administration of the conversion table of the access control apparatus within the ICS 1, and becomes ICS packet 81. This is then sent within the ICS 1 following the rules of the address system ADS, and upon reaching the destination access control apparatus 4, is restored to the ccuputer ccmTunication data 80 of the address system ADX under the administration of the conversion table thereof, and is sent to the LAN-M within the same corporation X. Here, the ICS frame being sent and received within the ICS 1 is referred to as an ICS network packet, and the ICS packet being sent and received outside of the ICS 1 is referred to as an ICS user packet. The ICS user packet is such as stipulated by the Internet protocol RFC791 or RFC1883 as a rule, but dealing with ICS packets which do not follow this rule will be described later in conjunction with description of another entxxbjrv-.nt.
The ICS network packet 81 is cemprised. of a network control 19 field 81-1 and a network data field 81-2, with the network control field 81-1 storing the addresses (address system ADS) of the access control apparatuses 2 and 4 therein. The ICS user packet ls either used as the network data field 81-2 with no change to the data value thereof, or is subjected to data format conversion following stipulations determined within the ICS 1 and is used as network data field 81-2. An exarrple of the data format conversion stipulations might be conversion to ciphertext or data cwpressim, and the access control apparatus 2 may be provided with ciphering mans, deciphering means for returning the ciphertext to the original plain-text, data cmpression n, and data decompression means for returning the compressed data to the original data. In the access control apparatus 2, the ICS user packet 80 is used as the ICS network packet 81-2, and each of the operations of adding the network control field 81-1 to the ICS network packet 81-2 are referred to as "ICS encapsulation". Also, in the access control appar-atus 4, the operations of removing the network control field 81-1 from the ICS network packet 81 are referred to as nICS reverse encapsulation".
Now, description will be made regarding the operation in the case of c=mication between corporations. The carnputer communication data (ICS user packet) 82 transmitted from the LAWY2 of the corporation Y is provided with addressing following the address system ADY, but is subjected to address conversion following the address system ADS under administration of the conversion table of the access control apparatus 6 within the ICS 1, and becames ICS packet 83.
This is then sent within the ICS 1 following the rules of the address system ADS, and upon reaching the destination access control apparatus 3, is converted to the ccniputer a=imication data 82 of the address system ADX under the administration of the conversion table thereof, and is sent to the LAN-X2 within the corporation X. e address lengths of 32 bits and 128 bits are used in the present invention, the present invention is by no me= restricted to these. Even If the length of the addresses are changed to such other than 32-bit or 128bit, this does not change the principle of address conversion which is the principle idea of the present invention.
Thus, according to the present invention, both intra-corporation and inter-corporation uter ceffinunications are enabled by unified address administration by the ICS 1. Generally used user terminals for ccrnputer ccnm=cations are incorporated within the LAN within the structure of the user, and incorporated within the VAN (Value Added Network) via accessline, and user data packets are sent which have differing data formats and differing address system for each type of service. For example, an IP address is used for Internet services, a telephone nmtw/ISDN nurber (E. 164 address) for telephone services, and an X.121 address is used for X. 25 packet services. Conversely, according to the ICS 1 of the present invention, address conversion is perfoimed with the conversion table of the access control apparatus based on the input ICS user packet, thus realizing sending of information frames of data of varied structures unified under a single data formut and address system, i.e., converted to ICS packets.
2 1 FIG.6 schematically illustrates an example whexein the ICS 1 of the present invention is cenprised of a plurality of VANs (VAN-1, VAN2, VAN3), with each VAN being administered by a VAN operator. An ICS 1 user applies to the VAN operator for a user conmnication line, and the VAN operator decides the ICS address and ICS network address for the user and registers this informtion with the circuit type in a conversion table 12 within the access control apparatus 10 such as shown in FIG.7. The ICS 1 has as access points serving as external connection elements with the LANs (or terminals) of the corporations X and Y the access control apparatuses 10-1, 10-2, 10-3, 10-4 and 10-5, as shown in FIG.7., and further has relay apparatuses 20-1, 20-2, 20-3 and 204, and also ICS network servers 40-1, 40-2, 40-3, 40-4 and 40-5, as well as ICS address adad-nistration servers 50-1 and 50-2. A relay apparatus 20 such as shown in FIG.8 is provided to the ceffnunication path within each of the VANs, and an inter-VAN gateway 30 such as illustrated in FIG.9 is provided as the connection element of VAN-2 and VAN-3. The LANs 1-1, 1-2, 1-3 and 1-4 are respectively connected to the access control apparatuses 10-1, 10-5, 104 and 10-2, via the user communication lines 36-1, 36-2, 36-3 and 36-4.
The access control apparatus 10 (10-1, 10-2, 10-3, 10-4 and 105) are devices containing the user comamication lines from the user (corporations X and Y) to the ICS 1, and as shown in FIG.7. is comprised of a processing device 11 comprised of a CPU or the like, conversion table 12 serving as a database for performing address conversion and the like. an input/output interface line portion 13, 22 and a temporary conversion table 14. Also, the relay apparatus 20 has network packet transfer = g functions and path specification routing functions, and as shown in FIG.8 has a processing device 21 ccoprised of a CPU or the Like and a conversion table 22, the conversion table 22 being used for determining the cenTrunication destination when the ICS network frarne is transferred within the ICS 1. The inter-VAN gateway 30 has a processing device 31 ccrrprised of a CPU or the like and a relay table 32 for determining where to send ICS network packets between VANs, as shown in FIG.S.
As shown in FIG.10, the ICS server 40 is camprised of a processing device 41 and an ICS network database 42, the usage of the ICS network database 42 not being restricted. Examples of thiLs usage include: user-specific data corresponding with the ICS address (such as the narne or address of the user), data not corresponding with the ICS address, such as data indicating the state of cemninication trouble within the VAN, or data not directly related to the VAN, such as an electronic library which maintains and discloses digital documents, public keys for a public encryption systern using encryption technology employed in verifying the authenticity of the sender and receiver, and maintaining data such as public proof data and related data or secret keys for a secret encryption systern and related data. The processing device 41 refers to the ICS network database 42, and obtains corresponding data and sends the data to the access control apparatus 10. Further, not only does the ICS network database 42 operate in stand-alone manner, but also is capable of =Tainicating 23 with other ICS network servers and obtaining data therefran. by weans of sending and receiving ICS network frames based m IP ccnmniication technology. Within the ICS, the ICS network server is the only mrponent provided with an ICS network address.
According to the present invention, the address used to identify miputers, terminals and the like used with-in the ICS network packet is referred to as an ICS network address, and the address used to identify the =rputer's, terminals and the like used within the ICS user packet Is referred to as an ICS user address. The ICS network address is used only within the ICS, one or both of the two types being used; 32-bit and/or 128-bit. Similarly, the ICS user address also uses one or both of the two types; 32-bit and/or 128-bit. The access control apparatus 10, the relay apparatus 20, the VAN gateway 30 and the ICS network server are arranged so as to be provided each with an ICS network address so as to be uniquely identified. Also, the ICS user address is fo of a VAN upper code and VAN internal code. With the length of the VAN upper code being represented as Cl bits and the length of the VAN internal code being represented as C2 bits, the ICS user address is used such that the total of Cl + C2 equals either 32 bits or 128 bits.
In the present invention, no particular rnethod for deciding the VAN upper code and VAN internal code is stipulated, but in the case of Cl + C2 = 32 bits, the follawing example can be given for a method for deciding such:
24 VAN upper address = district administration code(4-bit) Hcountry code(4- bit) 11VAN code(8-bit) VAN internal code = VAN district code(4-bit) 11VAN access point code(8- bit) lluser logic code(4-bit) FIG.11 makes description thereof using an example of an ICS user address. Here, the symbol nalib" indicates linkage of data "an and "bw, i.e., data obtained by means of arrayed data "an and "b in this order. The ICS network address can be provided with locality in the same manner as with the user network address. That is,
ICS network address = district administration code 11 country code 11VAN code MVAN district codeliuser logic communications line code Thus, the relay apparatus can efficiently find the transfer destination by mans of deciding the transferring destination with consideration to the district. The address can be determined in the same way in the case of Cl + C2 = 128 bits, as well. Incidentally, with the present invention, the ICS frame can be constructed as described later, as long as Cl + C2 = 32 bits or Cl + C2 = 128 bits ls kept, regardless of haw the field sections for the VAN upper code and VAN internal code are made, or the length of each of the sections.
Also, when deciding the VAN upper code and VAN internal code, Palt- of these codes may be made to be unique to the user. That is, the user can make a user-specific address system. The address values within a 32 bit address value are from address 0 to address (2-32 -1), the present invention is carried out by providing an address decided uniquely to the user within the range of address 10 x 224 to address (10 x 224 + 2 24 _1) ' i.e., address (172 x 2 24 + 16 x 2 16) to address (172 x 2 24 + 32 x 2 16 _1) or address (192 x 2 24 + 168 x 2 16) to address (192 x 2 24 + 169 x 2 16 _1).
A physical camimcation line can be separated into a plurality of canrunication lines and used, this being realized in conventional art as frame relay (FR) multiplex commtmication method, for example. According to the present invention, the user s ccrffmmication line is separated into a user physical conTrunication line and one or more user logic comninication lines. FIG.12 illustrates an example of the above, wherein a user physical conTnmication line 60 is separated into two user logic c=unication lines 61-1 and 61-2 of the ccomunication rate 50 Mps. Also, separate =rputer =minication apparatuses 621, 62-2, 62-3, and 62-4 are each connected to respective user logic comm.mication lines, and the ICS user addresses "4123,0025,0026,4124" are provided to each of the computer communication apparatuses 62-1 through 62-4. The user physical =minication Line 60 is connected to the access control apparatus 63, and the point of contact between the two is called "ICS logic terminal". The ICS logic terminal is provided with an only ICS network address within the ICS. In the example shown in FIG.12 user logic communication lines 61- 1 and 61-2 26 are connected to the access control apparatus 63, and ICS network addresses "8710n and "8711" are provided to the contact point ICS logic terminals 64-1 and 64-2, respectively.
As described above, the ICS network server 40 is also provided with an only ICS network address, so that the ICS network address can determine that the ICS logic terminal or the ICS network server is the only one within the ICS. The ICS network server is capable of exchanging information with other ICS servers by mans of sending and receiving ICS network packets provided with each other' s ICS network addresses, using the IP conTamication technology. This function is referred to as "ICS network server conTminication functionn. The access control apparatus is also provided with an only ICS network address within the ICS, and is capable of exchanging information with other ICS servers by means of the ICS network server ccnTmmication function. The ICS network server cinication function is realized by using conventional TCP or UDP(User Datagram Protocol) technology.
There are two types of ICS packets in the present invention, as described earlier, the ICS network packet which is sent and received with-in the ICS, and the ICS user packet which is sent and received outside of the ICS. Each packet is cmprised of a control field and a data field, and, as shown in FIG.13, the packets are c"ri-sed of a network control field, a user control field, a network data field and a user data field, so as to allow usage by ICS encapsulation and ICS reverse encapsulation. That is, when the ICS user packet enters the ICS fram the access control apparatus, the ICS user packet becomes
27 part of the data of the ICS network packet, and the control field of the ICS network packet (network control field) is added thexeto (ICS encapsulation). The network control field is divided into a basic field and an external- field. The basic field is used as a header of RFC791 or RFC1833 stipulation and the external field is used for ciphering or the like.
Inside the network control field of the ICS packet is placed a range for storing the sender' s address and the intended reoeiver' s address. There are two types of ICS packets, those with a 32-bit address length and those with a 128-bit address length, with a packet format being employed according to the RFC791 stipulation shown in FIG.3, for example. In the event that 32 bits is insufficient for the ICS network address, for example, in the event that a 64-bit address is to be used, following the RFC791 stipulation, the lacking 32 bits (64 bits - 32 bits) are written into the option portion of the ICS network packet control field, thus making the network address usable at 64 bits. Now, supplemental description will be made regarding the aforementioned user-specific address. In the event that a great number of users have a private address (a type of ICS address) in the section between (10 x 224) and (10 x 224 + 2 24 _1) for example, in the case that the length of the ICS user address is 32 bits, the 32 bits is insufficient for the ICS network address, since the ICS network address is provided corresponding to the ICS user address, and 64 bits is required, for exanple. In this case, as described above, the lacking 32 bits are written into the option portion of the ICS network
28 packet control field, thus making the network address usable at 64 bits.
The fact that ccm=cation between the same user (called "intracorporation cmcation") is possible using a private address will be described in the first embodiment. Also, in the event that the address length is 128 bits, the present embodiment is c=ied out following packet format according to the RFIC1883 stipulation such as shown in FIGA, for example. The transmitting address range within the network control field, and the address stored in the destination address are made to be ICS network addresses, each respectively being the transmitting ICS network address and the receiving ICS network address. Further, the transmitting address range within the user control field, and the address stored in the destination address are made to be ICS user addresses, each respectively being the sender ICS user address and the receiver ICS user address.
Incidentally, there is no need to following the RFC791 or RFC1883 stipulation for the ICS packet format in carrying out the present invention; the present:invention can be carried out as long as the packet format is such that uses addresses of 32 bits or 128 bits in length. Generally, ICSs receives ICS user packets stipulated by RFC791 or WC1883, but other packet formats can be handles within the ICS network by converting to ICS user packets with conversion means.
Embodinient-1 (Basic ICS, intra-corporation ccm-mication and intracorporation conTnanication):
A first entxxlimeiit of the present invention will be described with reference to FIGs.14 and 15, regarding basic cannmication wherein the transfer destination within the ICS is determined from the receiver' s ICS user address, based on administration by a conversion table. In the figures, 170-1, 170-2, 170-3 and 170-4 respectively denote gateways provided within the LANs 100-1, 100-2, 100-3 and 100-4, and the ICS packets can pass through these gateways 170-1 through 1704.
First, description will be made regarding c=unication between a terminal which is connected to LAN 100-1 of a corporation X which has a unique address system ADX, and a ternd-nal which is connected to LAN 100-2 of the same corporation X. That is, this is communication between a terminal which has an ICS user address "0012" on the LAN 100-1, and a terminal which has an ICS user address "003C m the LAN 100-2. This cenTnanication is typical of c=unication nude between terminals which have set addresses based on a unique address system within a single corporation (ADX in this exanple), the communication being made via the ICS 100 in an interactive manner. This type of conm=ication is referred to as intra-corporation communication service (or intra-corporation cannziication). Next, description will be made regarding communication between a texminal which is connected to LAN 100-1 of a corporation X which has a unique address system ADX, and a texminal which is connected to LAN 100-3 of a corporation Y which has a unique address system ADY. That is, this is ccmenication between a terminal which has an ICS user address "0012" on the LAN
100-1, and a terminal which has an ICS user address "115C on the LAN 1003. This ccffmmication is typical of ccmmunication made between terminals which have different address system within different corporations, the ccnmxmcation being made using an ICS address system which can be shared between the two. This type of conTmnication is referred to as intercorporation ccmmunication service (or intercorporation communication). <<Cammon preparation>> In describing the present embodiment, the address format and so forth is determined as described below, but the specific numeric values and formats are all but an exaffple, and the present invention is by no means limited to these. The ICS network address is represented by a 4-digit number, and the sender ICS user address and the receiver ICS user address are both represented by a 4-digit number. Of the sender ICS user address and the receiver ICS user address, addresses of which the upper two digits are not 110011 are used as inter-corporation ccnTminicatim addresses, and these inter-corporation comm=cation addresses are an only value within the ICS 100. Of the sender ICS user address and the receiver ICS user address, addresses of which the upper two digits are "00" are used as intra-corporation communication addresses, and these intra- corporation communication addresses my be duplicate of other intracorporation ccffmlnication addresses within the ICS 100. The ICS address administration server 150-1 is capable of uniquely identifying the intercorporation communication addresses. Also, the conversion table 113-1 provided to 31 the access control apparatus 110-1 contains the following: originating ICS network addresses, receiving ICS network addresses# sender ICS network addresses, receiver ICS network addresses, request identification, speed segments and so forth. The request identification registered to the conversion table 113-1 is such that, e.g., "V' represents intra- corporation c=nunication service, ', 2m represents inter-corporation conmmication service, and ', 3" represents virtual dedicated line connection. The speed segment is the line speed that the cnication fran the ICS network address requires, including throughput (e.g., the number of ICS packets sent within a certain amount of time). <<Preparation for intra-corporation ccnTmxiication>> The users of LAN 100-1 and LAN 100-2 specify the te=dx.Lal and apply to a VAN operator in order that the intra-corporation ccnnm,Licatim of the terminals connected to the LANs can perform communication via the VAN-1 and VAN-3. The VAN operator responds to the application and sets the aforementioned ICS network address, ICS user address, request identificatim number, etc. to the conversion tables of the access control apparatuses 110-1 and 110-5 connected to the LAN 100-1 and LAN 100-2.
The items to be set for the VAN- 1 are as follows. The ICS network address is decided by the ICS logic terminal of the access control apparatus 110-1 to which the LAN 100-1 is connected, with the ICS network address of the ICS logic terminal in this case being set as "77110. The intra-corporation ccmnlnication address of the 32 terminal connected to the LAN 100-1 frcm which the application was made is set as ', 0012u, and this is used as the sender ICS user address. The intra-corporation c=unication address used by the terminal of the address is set as ', 2212", and this is used as the sender ICS user address. Next, the intra-corpor-ation cenyminication address of the terminal connected to the LAN 100-2 fram which the application was made is decided by the ICS logic terminal of the access control apparatus 110-5 to which the LAN 100-2 is connected, in this case the ICS network address being set as ', 9922", and this is used as the receiving ICS network address. Further, the ICS user address used by the terminal connected to the LAN 100-2 is set as "0034", and this is used as the receiver ICS user address. The nu "ln is set as the request identification, indicating the intracorporation ccmmunication service that was applied for, and the above is registered to the conversion table 113-1.
The items to be set for the VAN- 3 are as follows. Values necessary for reverse cemmunication (canTnunication frem LAN 100-2 to LAN- 1) are set to the conversion table of the access control apparatus 110-5 connecting the LAN 100-2 frcin which application was made. That is, data is set reverse to the transmitting ICS network address and the receiving ICS network address, and at the same time, data is set reverse to the sender ICS user address and the receiver ICS user address. The ICS network address of the LAN 100-2 is set as ', 9922", and this is used as the transmitting ICS network address. NaTeral "0034n is set as the sender ICS user address for the intra-corporation 33 ICS user address of the terminal connected to the LAN 100-2, and the ICS user address ', 0012" of the terminal of the other party is used as the receiver ICS user address. Also, the Ics user address "7711" of the LAN 100-1 is used as the receiving ICS network address and the value 11' is set as the request identification, indicating intracorporation cenTaxiication services. The above is written to the conversion table of the access control apparatus 110-5 and registered. <<Operation of intra- corporation communication>> Regarding ccunmication between a terminal connected to LAN 100- 1 and having a sender ICS user address ', 0012", and a terminal connected to LAN 100-2 and having a receiver ICS user address ', 003C the sender ', 0012n sends an ICS user packet to the receiver "003C. This ICS user packet has set as the sender ICS user address ', 0012", and as the receiver ICS user address has set "003C. and the terminal with the ICS user address ', 0012" perform sending thereof.
The operation will be explained with reference to a flowchart in FIG.18. The conversion table 113-1 is shown in FIG.16 and the trary conversion table 114-2 is shown in FIG.17.
The ICS user packet PI is sent via the user logic ccuramication line 1801, and transferred to the access control apparatus 110-1 as the ICS user packet Pl. The access control apparatus 110-1 refers to the conversion table 113-1 frat the transmitting ICS network address 41 7711"(Steps S100 and S101) and the receiver ICS user address "003C of the received ICS user packet, and knows that the cenTmmication is an intra-corporation caffrunication fran the request identification 34 value ', 1" obtained at the same time(Step S102). Then, the receiving ICS network address "9922w corresponding to the sender ICS user address "0034w is obtained (Step S103) and is ICS-encapsulated (Step S106). The above procedures illustrated in a flowchart are as shown in FIG.18, with the intra-corporation being flaw (1) therein. The sender ICS user address may be used to specify a source of the ICS packet.
The access control apparatus 110-1 performs the ICS encapsulation, fonrdng the ICS network packet P2 which is sent to the relay apparatus 120-1. Since the ICS network address of the network field is ensured of its uniqueness within the ICS, there is no conflict with other ICS packets. The ICS network packet P2 passes through the relay apparatus 120-1 and 120-2 based on the receiving ICS network address, and reaches the access control apparatus 110-5 of the VAN-3. The acx>--ss control apparatus 1105 remves the network control field frem the ICS network packet P4 and performs ICS reverse encapsulation, and re-creates a user data packet P5 which is the same as the ICS user Packet P1 from the network data field of the ICS packet, and sends it to the LAN 100-2. The ICS user packet is routed through the LAN lOO2, and is transferred to the tenninal which has the ICS user address "0034". <<Preparation for inter-corporation convunication>>
As an example of performiing inter-corporation =Tunication, the ccffumlcation between a temanal which has an ICS user address "0012" and is connected to a LAN 100-1 following address system ADX, and a te=inal which has an ICS user address 115C and is connected to a LAN 100- 3 following address system ADY, will be described. The users of the LAN 100-1 and LAN 100-3 specify the terminal to the VAN each is connected to so as to be able to perform the c=unication via VAN1 and VAN-2, and make application to the VAN operator. The VAN operator sets the necessary items in the conversion table of the access control apparatus which is connected to the LAN 100-1 and LAN 100-3, in accordance with the application.
The items to be set regarding VAN- 1 are as follows. The ICS network address of the LAN 100-1 is made to be 7711", the intra- corporation cenmmication address held by the terminal connected to the LAN 100-1 fran which there was application is made to be "0012", and this is made to be the sender ICS user address. The inter corporation cenyminication address provided to the terminal of the above ICS user address made to be "2212", and this is made to be the sender user address (inter-corporation). The ICS network address is determined by the ICS logic terminal of the access control apparatus 110-4 connected to the ICS network address of the LAN 100-3 from which there was application, the ICS network address here being ', 8822", and this is made to be the receiving ICS network address. Also, the ICS user address of a terminal connected to the LAN 100-3 is made to be 64 1156', and this is made to be the receiver ICS user address.
Further, a value "2" is set as the request identification, indicating the inter-corporation cenmrdeation service that was applied for, and the above is registered to the conversion table 1131.
36 The items to be set regarding VAN-2 are as follows. As a conversion table for the access control apparatus 110-4 to which the LAN 100-3 is connected, a trary conversion table 114-2 which holds reverse data for a certain time, e.g., 24 hours, is set. That is, regarding the ICS network address ', 8822" to which is connected the LAN 100-3 which uses the inter-corporation conTnunication service. the following are provided within the access control apparatus 110-4: a transmitting ICS network address, a sender ICS user address, a receiver ICS user address, a receiving ICS network address and trary conversion table 114-2 which includes a request identification and so forth. <<Operation of intercorporation ccrmiunicatim>> A terminal having an ICS user address ', 0012m sends an ICS user packet Fl wherein the sender ICS user address is set as ', 0012" and the receiver ICS user address is set as ', 115C as. The ICS user packet F1 is transferred to the access control apparatus 110-1 via the user logic c=amications line 180-1.
The access control apparatus 110-1 refers to the conversion table 113-1 fran the originating ICS network address ', 7711" of the LAN 100-l(Steps S100 and S101) and the receiver ICS user address '115C, and knows that the request identification value is ', 2u, i.e., this cawunication is an inter-corporation cenTmnication (Step S102). The receiving ICS network address corresponding to the receiver ICS user address "1156" is known as "8822(Step S104), and then the sender ICS user address ', 0012n is converted into an inter-corporation 37 ccmmmication address.2212"(Step S105). The access control apparatus 110-1 adds a network control field, from the obtained transmitting ICS network address ', 7711", the sender ICS user address "2212", the receiver ICS user address '115C and the receiving ICS network address 8822n, and PexfOnns the ICS encapsulation, forming the ICS network packet F2 which is sent to the relay apparatus 120-l(Step S106). The above procedures are illustrated in a flow (2) in FIG.18.
In the above inter-corporation ccnTmmication, in the event that the sender ICS user address within the ICS user packet Fl is mde to be the inter-corporation ccm=cation address "2212", the sender and the receiver perform the intercorporation cmcation using an inter-corporation cenim=iication address(Steps S102 and S104). In this case, the access control apparatus 110-1 does not perforim the process of converting the sender ICS user address "2212" into the intercorporation caTnunication address "2212 as such is not necessary. The above procedures are illustrated in a flow (3) in FIG.18. The sender ICS user address may be used to specify a source of the ICS packet.
The relay apparatus 120-1 transfers the ICS network packet to the access control apparatus 110-4 within the VAN-2 via the relay apparatus 120-2 within the VAN-1, the inter-VAN gateway 130 and the relay appar-atus 1203 within the VAN-2, based on the receiving ICS network address. The operation will be explained with reference to FIG.19. The access control apparatus 110-4 receives the ICS network packet(Step S110), creates an ICS user packet F5 fram the network data 38 field(Step S111: ICS reverse encapsulation), and decides fram the receiving ICS network address the logic terminal for sending((1) of Step S112) and sends it to the LAN 100-3(Step S113). At the same time, in the event that the relation among the transmitting ICS network address ', 8822", the sender ICS user address 115C, the receiver ICS user address ', 2212" and the receiving ICS network address.7711n is not registered in the conversion table within the access control apparatus 110-4, a value "2w of the request identification, i.e., a designation of the inter- corporation c=unication is set to the trary conversion table 114-2((2) of Step S112). The registration contents of thetenWrary conversion table 114-2 are updated according to processes such as the contents being deleted if there is no usage thereof for 24 hours. The ICS user packet is routed through the LAN 1003, and is transferred to the terminal having the ICS user address
115C. In a case that the coluffin of the sender ICS user address in the conversion table 114-2 is separated as "intra-corporation and "intercorporation' of the conversion table 113-1, e.g., in the case that "1159" is described in the conversion table as the sender ICS user address w1159w which is described at the address colurrin of user control field of ICS user packet just after the ICS reverse encapsulation is processed. Then, the process in which the address of the user control field is rewritten to "002Y' is added to the process of the Step S112(1). As described above, although the ICS user address "0023" for the intra- corporation czffrminicatim is used within LAN, the ICS "1159" for the corporations outside LAN. In another entxxbirbents,
39 the values are not set in the temporary conversion table. Ftr-ther, in another embodi ts, the conversion table 113-1 does not include the sender ICS address (intra-corporation) and the sender ICS user address (intercorporation) and does not include the flow (2) in FIG.18, i.e., Step S105. At the Step S104, the sender ICS user address is not referred. An effect of this embodiment is that register number of the conversion table is to be reduced to one of the sender ICS user address when there are many the sender ICS user addresses.
Effibodin-ent-2 (Virtual dedicated line):
Now, descriptlon of the operation of virtual dedicated line connection according to the present invention will be made with reference to FIG.20. Here, the virtual dedicated line connection refer's to c=runication wherein ICS user packets are transferred in a fixed manner to a receiving ICS network address already registered in the convexsion table, regardless of the ICS user address within the user control field of the ICS user packet, in which the format taken is one-on-one or one-on-N. While the components of FIG.20 are the same as those of Embodiment-1 shown in FIGs.14 and 152 what is different is the contents of registration in the conversion table. In the conversion table of the access control apparatus, the receiving ICS network address is dete=nined from the transmitting ICS network address in a fixed manner, so that either the sender ICS user address (intra-corporation), the sender ICS user address (inter-corporation) and the receiver ICS user address are either not registered, or ignored if registered.
Description will now be given regarding a case in which a corporation X uses virtual dedicated line connection, and the comninication is conducted between LAN 200-1 of the corporation X which is connected to the access control apparatus 210-1, and LAN 2002 of the corporation X which is connected to the access control apparatus 210-5. The conversion table 213-1 is shown in FIG.21. <<Preparation>>
The user applies to a VAN operator for virtual dedicated line connection. The VAN operator determines the ICS network address "7711- of the ICS logic terminal at the connection point between the access control apparatus 210-1 for connecting the LAN 200-1 of the corporation X and the user logic =nunications line 240-1, and similarly determines the ICS network address ', 9922" of the ICS logic texminal at the connection point between the access control apparatus 210-5 for connecting the LAN 200-2 of the corporation X and the user logic comminications line 240-2. Next, the VAN operator performs setting to the conversion table 213-1 of the access control apparatus 210-1 of the following: the transmitting ICS network address "7711", the receiving ICS network address ', 9922" and the request type. Illustrated in FIG.20 is an example wherein the request type ', Y' has been made to serve as the virtual dedicated line connection. Similarly, the VAN operator performs setting to the conversion table of the access control apparatus 210-5 of the following: the transmitting ICS network address ', 9922", the receiving ICS network address "7711" and 41 the request type. <<Procedures>> The operation will be explained with reference to FIG. 22. The LAN 200-1 of the corporation X sends a user packet F10 to the ICS 200 via the user logic ccmrunication line 240. The access control apparatus 210-1 which has received the ICS user packet F10 from the logic terminal of the ICS network address "7711n makes reference to the request type of the transmitting ICS network address ', 7711"(Steps S200 and S201) and identifies this as a virtual dedicated line connection by referring the request identification "3m(Step S202), and reads the receiving ICS network address ', 9922"(Step S203). Next, the access control apparatus 210-1 adds a network control field to the ICS user packet F10 in which the receiving ICS network address is set to "9922" and the transmitting ICS network address is set to "7711n, thus forming an ICS network packet Fll(Step S204: ICS encapsulation), and sends this to the relay apparatus 220-l(Step S205). The relay apparatus 200-1 which receives the ICS network packet F11 determines the destination based on the receiving ICS network address of the ICS network packet F11, and sends an ICS network packet F12 to the relay apparatus 220-2. The ICS network packet F12 is transferred to the access control apparatus 210-5 via the relay apparatus 220-4 within the VAN-3.
The access control apparatus 210-5 rennoves the network control field fran the ICS network packet F13 (ICS reverse encapsulation), and sends the ICS network packet F14 fran the logic terminal of the ICS
42 network address ', 9922" to the user logic communications line 240-2. Then, the LAN 200-2 of the corporation X receives the ICS user packet F14. Transmission can be made in the same say as described fram the LAN 200-2 to the LAN 200-1, and thus, interactive communication is available. Using the same method, ICS user packets can be transferred from the LAN 200-1 of the corporation X to a LAN 200-3 of another corporation Y.
Also, while the above description has been made with reference to a case of one-on-one communication, one-on-N ccmTunication can also be performed. For example, a plurality of ICS network addresses may be set to the conversion table 213-1 of the access control apparatus 210-1 shown in FIG.20, as indicated by the transmitting ICS network address ', 7712". In the present example, two ICS network addresses are set, "6611" and "8822". The access control apparatus 210-1, upon receiving the ICS user packet from the ICS logic terminal with an ICS network address ', 7712y', creates a first ICS network packet wherein a network control field set with 6611" for the receiving ICS network address is added thereto, and a second ICS network packet wherein a network control field set with 8822" for the receiving ICS network address is added thereto, these being sent to the relay apparatus 220 1. Consequently, one-on-two communication can be pexformed.
Subsequently, one-on-N c=unication can be performed by transferring each ICS network packet in the same manner as described above.
43 Embodiment-3 (Embodiment using an ATM network):
An embodiment will be described wherein the network inside the ICS according to the present invention is configured using an ATM network. The present enbodiment will be described in the following order: (1) supplementary explanation of ATM-related conventional art, (2) description of cemponents, (3) flow of packets using-SW, (4) flaw of packets using PVC, (5) one-on-N or Won-one communication using PVC, and (6) N-on-N camTunication using PVC. Incidentally, since the present embodiment mainly discloses art regarding address conversion between ICS network packets and ATM networks, so any of the following can be applied to the present embodiment: intra-corporation ccnnwucation service and intercorporation carym=cation service described in Embodiment-1 and virtual dedicated line service described in Embodiment-2. (1) Supplementary explanation of ATM-related conventional art:
First, supplementary explanation will be made regarding ATMrelated conventional art to the extent that is necessary to describe the present embodiment. With an ATM network, a plurality of non-fixed logic channels which can flexibly deal with ccunionication speed and so forth can be set on a plWsical line. these logic channels being referred to as Ws (Virtual Channel). There are two types of virtual channels stipulated according to the way of setting, SVC (Switched Virtual Channel) and PVC (Permanent Virtual Channel). The SW performs call setting of a virtual channel whenever necessary, and can establish a logic line having the necessary speed for a necessary 44 duration with an arbitrary ATM terminal (a general term for ccmm=cation devices which are connected to the ATM network and perform cenTmmications using the ATM network). Call setting of the virtual channel is performed by the AIM terminal which is attempting to initiate ccmnunication, and the signaling method" is standardized in ITU-T regarding this method. An address for identifying the destination ATM texminal to which call setting is to be performed (this address hereafter referred to as nATM address") is necessary for call setting, and the ATM addresses are systematized so that each ATM terminal has a unique ATM address within the ATM network, in order to enable identification of the ATM texminals. There are the following address systems: E.164 format stipulated in the ITU-T Recamrendations Q.2931, and the three types of NSAP method ATM addresses such as shown in FIG. 23 following the ATM Forum UNI 3.1 Specifications. Now, regarding ICS, which of the above ATM address systems is used is decided by the specific construction of the ATM network, so description of the present enbodiment will proceed using the term "ATM address".
The PVC performs call setting in a semi-permanent manner, and can be considered to be a virtual line as viewed frern the ATM terminal. IDs for identifying virtual channels (hereafter referred to as "vi-rtual channel IDO) are appropriated to established virtual channels for both the VC and PVC. A virtual channel ID is emprised. of the VPI (Virtual Path Identifier) and the WI (Virtual Channel Identifier) of the cell header portion of the ATM cell format (63 bytes) shown in FIG. 24.
Information ccmmunication within the ATM network is performed in information units of the ATM cell format shown in FIG.24, so there is the necessity to convert the ICS network packets into the ATM cells in order to send over an ATM network. This conversion is performed in two steps: conversion to CPCS (Common Part Convergence Sublayer) shown in FIG.25, and degradation of the CPCS frames to the ATM frames as shown in FIG.26. Dividing a communication packet into ATM cells results in a plurality of the ATM cells in most circumstances, so the series of ATM cells related to the since cenTmmication packet is referred to as an ATM cell sequence. Reception of an ATM cell sequence results in reverse conversion, which is performed in two steps: assembling a CPCS frame frat the ATM cell sequence shown in FIG.26, and extracting and reproducing the caminiication packet (ICS network packet) from the CPCS frame shown in FIG.25. Conversion to the CPCS frame and degradation/assembly of the ATM cells constitute known art, which has been standardized following the ITU- T Reccmmendations. Also, protocol headers within the CPCS frame user information have been standardized in RFC1483 of IEW. (2) Description of components:
FIGs.27 and 28 focus on the ATM network 1042, in which the internal construction of the conversion unit 1033-1 within the ATM exchange 101331 and of the conversion unit 1033-2 within the ATM exchange 10133-2 is described, and also the access control apparatus 1010-2 and 1010-1 are described in a simplified manner. Contents of 46 an ATM address conversion table 1533-5 and a VC address conversion table 1433-5 are shown in FIG.29, and contents of an ATM address conversion table 1533-6 and a VC address conversion table 1433-6 are shown in FIG. 30. In the present entx>dinmt, the internal configuration of the access control apparatus and the operation of the processing device within the access control apparatus are basically the same in principle as the description given in Embodiment-l.
Appropriated to the access control apparatus 1010-5 shown in FIG.27 are ICS network addresses "7711" and "7722", serving as connection points (ICS logic terminals) for corporations X and A which are the users of the ICS 905. Also appropriated to the access control apparatus 1010-7 are ICS network addresses "7733w and "774C, serving as connection points for corporations W and C, similarly. In FIG. 28, appropriated to the access control apparatus 1010-6 are ICS network addresses n9922n and "9933", serving as connection points for corporations Y and B, and similarly appropriated to the access control apparatus 1010-8 are ICS network addresses "9944n and n9955", serving as connection points for corporations Z and D. Here, in the ATM network embodiment, the corporations X, Y and so forth, which are given as examples of users, may be differing locations within a single corporation which perform intra- corporation conTa=cation, or may be different corporations which perform inter-corporation cnication.
An interface unit 1133-5 is provided in the conversion unit 1033-5 within the ATM exchange 10133-5, this interface unit 1133-5 handling the processing of rectifying interfacing (physical layers, 47 data link layer protocol) of the cemmunication lines connecting the access control apparatus 1010-5 and the ATM exchange 10133-5. The conversion unit 1033-5 is comprised of a processing device 1233-5, and also an ATM address conversion table 1533-5 for call setting with the SW, and a VC address conversion table 1433-5 for converting addresses frcxn ICS network addresses used by both SVC and PVC to vixtual channel. Also, the ATM exchange 10133-5 connects the ATM address administration server 1633-5 serving as an information processing device for storing the ATM address conversion table with, in the case of using PVC, the PVC address administration server 1733-5 serving as an information processing device for storing the VC address conversion table, thereby performing the information processing relating to address conversion. The cnents making up the ATM exchange 10133-6 are the same as the description given regarding the ATM exchange 10133-5. In FIGs.27 and 28, the access control apparatus 1010-5 and the access control apparatus 1010-7 are connected to the ATM exchange 10133-5 via the conminicatlon line 1810-5 and cemmunication line 1810-7, respectively, and also, the access control apparatus 1010-6 and the access control apparatus 1010-8 are connected to the ATM exchange 10133-6 via the connunication line 1810-6 and communication line 1810-8, respectively. An ATM address "3977" unique to the network is set to the conversion unit 1033-5 within the ATM exchange 10133-5, and an ATM address "399T' unique to the network is set to the conversion unit 1033-6 within the ATM exchange 10133-6. The ATM exchange 10133-5 and the ATM exchange 10133-6 are connected via the ATM exchange 10133-7 in the present
48 Z:
entx)diment. (3) Flow of packets using SW:
An embod=mt wherein SVC is applied as a cemm=cation path within the ATM network will be described with an example of an ICS user packet sent from a terminal of a corporation X toward a terminal of a corporation Y, with reference to FIGs.27 and 28. <<Preparation>> A receiving ICS network address indicating the destination of the ICS network packet, a receiving ATM address for indicating the other party for call setting of the virtual channel on the ATM network, and channel capabilities such as =minication speed requested by the virtual channel, are registered in the ATM address conversion table 1533-5. Also, similar registration is rnade to the ATM address conversion table 1533-6. In the entxxbirv-.nt, the values set in the ATM address conversion table 1533-5 are as follows: "9922" which is the ICS network address appropriated to the ICS logic terminal of the access control apparatus 1010-6 is set as the conmnication address of the corporation Y, and the ATM address "399T' which is uniquely appropriated to the conversion unit 1033-6 within the ATM network is registexed as the receiving ATM address. In the present ent)odiment, a canymmication speed of 64 Kbps is set as the channel capabilities. The contents registered to the AIM address conversion table 1533-5 are also written to the ATM address administration server 1633-5.
The values set in the ATM address conversion table 1533-6 are as follows: "7711n which is the ICS network address appropriated to the ICS logic terminal of the access control apparatus 1010-5 is set as the ccnuwiication address of the corporation X, and the ATM address "3977u which is uniquely appropriated in the ATM network to the conversion unit 1033-5 within the ATM exchange 10133-5 to which the access control apparatus 1010-5 is connected is registered as the receiving ATM address. In the present effbodiment, a cam-unication s of 64 Kbps is set as the channel capabilities. The contents registered to the ATM address conversion table 1533-6 are also written to the ATM address administration server 1633-6. <<Transferring ICS network packets fran the access control apparatus>> As described in Embodirrient-1, the ICS user packets sent fra, a terminal of the corporation X toward the terminal of the corporation Y connected to the access control apparatus 1010-6 via the access control apparatus 1010-5 is encapsulated upon passing through the access control apparatus 1010-5, and becemes an ICS network packet Fl having the transmitting ICS network address "7711" and the receiving ICS network address "9922" as an ICS packet header. The ICS network packet Fl is sent frcrn the access control apparatus 1010-5 to the ATM exchange 10133-5, and reaches the conversion unit 1033-5. The following is a description thereof made with reference to FIG.31. <<Obtaining a virtual channel ID>>
Once the conversion unit 1033-5 receives the ICS network packet Fl(Step S1601), there is the need to request a virtual channel ID of the SVC virtual channel determined by the relation of the transmitting ICS network address "7711" and the receiving ICS network address -9922" in the ICS packet header, in order to correctly transfer the received packet Fl to the ATM exchange 10133-5. In the case that the ccuminication is based on the WC, there are cases that the virtual channel corresponding with the cammunication path is established at the time of the receiving the ICS network packet, and cases in which the virtual channel has not yet been established. In order to find out whether or not the virtual charmel has been established, the processing device 1233-5 first searches whether or not a virtual channel corresponding with the pair of a transmitting ICS network address m7711" and a receiving ICS network address "9922" is registered in the VC address conversion table 1433-5 (Step S1602), and in the event that there is registration here, establishment of the virtual channel can be thus confirmed. That is, the fact that the virtual channel corresponding with the pair of transmitting ICS network address "7711" and receiving ICS network address "9922" is n33n is obtained, and further, it can be found that this virtual channel is carminicating based on the SW, fran the value "ll" of the channel type obtained at the same time. In the event that there is no such registration on the VC address conversion table 1433-5, the requested virtual channel is established with the latter- described <<call setting>>, and the virtual channel ID is obtained fram the information registered to the VC address conversion table 1433-5 at that point (Step S1603). <<Call setting>> Regarding the above-mentioned case wherein "there is no regist- 51 ration of a virtual channel ID corresponding with a c=unication path determined by correspondence between a transmitting ICS network address and a receiving ICS network address on the VC address conversion table 1433-5n, i.e., in the case that there is no virtual channel ID corresponding w-Lth the o=mication path established yet, it beccoes necessary to perform the following call setting, to establish a virtual channel within the AIM network ccffprising ICS 905. An example of operation of the call setting will now be described.
The processing device 1233-5 of the conversion unit 1033-5, upon making reference to the VC address conversion table 1433-5 and finding that there Is no registration -of a virtual channel ID corresponding with the pair of transmitting ICS network address "7711" and receiving ICS network address "9922" (Step S1602), the processing device 1233-5 of the conversion unit 10335 refers to the VC address conversion table 1533-5, finds the receiving ICS network address "9922" registered in the VC address conversion table 1533-5 matching the receiving ICS network address H9922", and obtains transmitting ATM address "399C corresponding thereto and channel capabilities n64K" corresponding thereto, and so forth. The processing device 1233-5 uses the obtained transmitting ATM address "3999n to perform a request for call setting to the ATM exchange 10133-5, and also requested at this time is channel capabilities such as conTainication speed of the virtual channel simultaneously obtained fran the VC address conversion table 1533-5 and so forth. The ATM exchange 10133-5, upon receiving the call setting request. uses a signal method which is provided 52 standard to ATM exchanges proper as known technique to establish a virtual channel within the ATM network which reaches the ATM exchange 10133-6 (Step S1606). The virtual channel ID appropriated for identification of the virtual channel is notified fran the ATM exchanges to conversion units 1033-5 and 1033-6 therein, but in the event that this is based on stipulations of a signal method according to known technique, the value notified fram the calling party ATM exchange 10133-5(e.g., "33n) and the value noti-fied from the receiving party ATM exchange 101333(e.g., "44n) may not be the same value. At the conversion unit 1033-5, the virtual channel ID u33" which is notified frcm the ATM exchange 101335 is registered in the VC address conversion table 1433-5 along with the transmitting ICS network address M11" and the receiving ICS network address R9922" (Step S1607), and stores these on the VC address conversion table 1433-5 while the connection of this virtual channel is established. When the virtual channel connection is no longer necessary, the conversion unit 1033-5 requests call release of the virtual channel to the ATM exchange 10133-5, and at the same time deletes the registration co=esponding with virtual channel ID "33" on the VC address conversion table 1433-5. Registration to the VC address conversion table 1433-6 in the conversion unit 1033-6 will be described later. << Packet transfer>> The processing device 1233-5 of the conversion unit 1033-5 converts the ICS network packet Fl received frern the access control apparatus 1010-5 into a CPCS frame shown in FIG.25 according to the 53 virtual channel (virtual channel ID "33") established according the above description, and further performs degradation into ATM cells as shown in FIG.26 and transfers to the relay ATM exchange 10133-7(Step S1604). <<Transfer of ATM cells>>
According to the above-described method, the ATM cell series Si cerrprised of a plurality of cells obtained by converting the ICS network packet Fl is transferred from the ATM exchange 10133-5 to the relay ATM exchange 10133-5, and further is transferred to the ATM exchange 10133-6 as ATM cell series S2. The following is a description thereof with reference to the flowchart in FIG.32. <<Operation following arrival of packet>>
Once the ATM cell series S2 reaches the ATM exchange 10133-6 (Step S1610), this ATM cell series S2 is transferred frem the ATM exchange 10133-6 to the conversion unit 1033-6. At the conversion unit 1033-6 as shown in FIG. 26, the received ATM cells are assembled into a CKS frame, and further, as shown in FIG.25, an ICS network packet is restored from the CKS frame (Step S1611). In FIG.28, the restored ICS network packet is shown as ICS network packet F2, but the contents thereof are identical to that of the ICS network packet Fl. The ICS network packet F2 is transferred to an access control apparatus dete=ned by the receiving ICS network address "9922" in the header thereof, i.e., to access control apparatus 1010-6 which has an ICS logic terminal appropriated with ICS network address n9922" (Step S1612).
54 At this time, at the conversion unit 1033-6, the transmitting ICS network address "7711", the receiving ICS network address "9922" the channel type "ll" indicating the fact this is SVC identified at the point of receiving the call, and the virtual channel ID "4C appropriated at the time of call setting of the SVC virtual channel are registered in the VC address conversion table 1433-6 (Step S1614), and at this time, the transmitting ICS network address "7711" of the ICS network packet F2 is written to the receiving ICS network address of the VC address conversion table 1433-6, and the receiving ICS network address "9922n is written to the transmitting ICS network address of the VC address conversion table 1433- 6, i.e., these are written in reverse positions. However, if at the point of registration an item already exists within the VC address conversion table 1433-6 identical to that regarding which registration is being attempted, no registration is made. The address conversion information registered in the VC address conversion table 1433-6 is stored m the VC address conversion table 1433-5 while the connection of the virtual channel having a corresponding virtual channel (in this example, virtual channel ID "4411) is established (Step S1613). <<Reverse packet flaw>> Now, description of the case of reverse flow of the ICS packet, i.e., flow ficr a corporation Y to a corporation X, will be made with reference to FIGs.27 and 28, under the presumption that call setting of the SVC virtual channel has been made according to the above description. An ICS user packet sent out fran the corporation Y to p the corporation X is converted into an ICS network packet F3 having the transmitting ICS network address "9922" and the receiving ICS network address M11" in the header portion thereof, and the processing following the flaw shown in FIG.31 as described above ls performed by the processing device 1233-6 of the conversion unit 10336 within the ATM exchange 10133-6.
In this case, the VC address conversion table 1433-5 in the conversion unit 1033-6 has registered therein a virtual channel ID "4C with a channel type "ll" which means SW, corresponding with the transmitting ICS network address "9922" and receiving ICS network address "7711n, so the system operates following the flaw(l) shown in FIG.31, thereby converting the ICS network packet F3 into a plurality of ATM cells (ATM series S3) and transferring, with regard to the virtual channel ID n4C. The ICS network packet F3 is reLa and transferred by the relay ATM exchange 10133- 5, beccm ATM series S4 and reach the ATM exchange 10133-5, are received via the virtual channel having virtual channel ID "33n in the conversion unit 1033-6 thereof, and restored into an ICS network packet F4 having identical contents with the ICS network packet F3. In the conversion unit 10335, the pair of the transmitting ICS network address "9922" and the receiving ICS network address "7711" in the header of the ICS network packet F4 is already registered in the VC address conversion table 1433-5 in reverse fashion, so registration to the VC address conversion table is not performed, and the ICS network packet F4 is transferred to the access control apparatus 1010-5.
56 <<E)le of application to half-duplex ccmTunication>> The abave description has been made with reference to cases wherein an ICS packet is transferred fran the corporation X to the corporation Y, and reverse fromthe corporation Y to the corporation X, with an network within the ICS 905 having been configured of an ATM network, being carried out with a single SVC virtual channel. For example, applying this transfer and reverse transfer to a request packet to a server terminal of the corporation Y to be connected to the ICS frcrn a client terminal of the corporation X to be connected to the ICS (transfer), and a response packet to this request packet f.Lat the client terminal of the corporation X to server terminal of the corporation Y (reverse transfer) results in an application example of half -duplex =minication in which one-way ccrmiunication is performed at times, and both-way cenTainication is realized by switching the ccnmniication direction by time frames. <<Example of application to fill] -duplex comnziication>>
The virtual channel set m the ATM network is capable of fi duplex c=unication, i.e., sinataneous both-way cenTminication, due to the ATM stipulations. For example, applying the transfer and reverse transfer to request packets to a plurality of server terminals of the corporation Y to be connected to the ICS from a plurality of client terminals of the corporation X to be connected to the ICS (transfer), and response packets to the request packets frem the plurality of client terminals of the corporation X to the plurality of server terminals of the corporation Y (reverse transfer) results in 57 asynchrx)nous transfer of packets between the client texminals and the server terminals, so simultaneous both-way cnication is conducted on the single SVC virtual channel serving as the ccmmmicatim path, thereby making for an application example of fill 1 -duplex cennunication. (4) Flaw of packets using PVC An enbodiment wherein the network within the ICS 906 is configured with an ATM network and PVC is applied as a cennxmicatim path within the ATM network wi-ll be described with an example of an ICS user packet sent frcin a terminal of a corporation W toward a terminal of a corporation Z, with reference to FIGs.27 and 28. <<Preparation>> A transmitting ICS network address, a receiving ICS address, the virtual channel ID of the PVC fixed on the ATM network (indicating the cemunication path between the ATM exchange 10133-5 and the ATM exchange 10133-6), and the channel type indicating that the virtual channel ID is PVC, are registered in the VC address conversion table 1433-5. This registration is different fran the case of SW, in that registration is made in the VC address conversion table 14335 at the same time that the PVC v:i-rtual channel is set in the ATM exchanges (10133-5, 10133-7, 101336) serving as the ccmn-mication path, and is saved in a fixed manner whIle the communication path is necessary, i.e., until the setting of the PVC virtual channel is canceled. Also, the registration is made to the VC address conversion table 1433-6 in the same manner. Incidentally, the PVC virtual channel ID is appropriated to the respective ATM exchanges at the tim that PVC is 58 fixedly connected between the ATM exchanges.
The values set in the VC address conversion table 1433-5 are as follows: value "7733" which is the transmitting ICS network address appropriated to the ICS logic terminal of the access control apparatus 1010-7 is set as the canTminication address of the corporation W, and value "994C which is the receiving ICS network address appropriated to the ICS logic terminal of the access control apparatus 1010-8 is set as the ccmminication address of the corporation Z. Further, the PVC virtual channel ID "55" which is appropriated to the ATM exchange 10133-5 is set as the virtual channel ID, and value "22" is set as the channel type, indicating the PVC. Also, settings for registering to the VC address conversion table 1433-5 are written to the PVC address administration server 1733-5, and stored.
In the same way, similar settings are rnade in the VC address conversion table 1433-6 in the conversion unit 1033-6 in the ATM exchange 10133-6, with the transmitting ICS network address and the receiving ICS network address reversed. in this case, even If the same PVC is being implied, the virtual channel ID rnay be of a different value to the VC address conversion table 1433-5. When the registering to VC address conversion table 1433-6 in this instance, this is also written to and stored in the PVC address administration server 1733-6.
The values set in the VC address conversion table 1433-6 are as follows: value "994C which is the transmitting ICS network address appropriated to the ICS logic texudnal of the access control apparatus 59 1010-8 is set as the camiinication address of the corporation Z, and value "7733" which is the receiving ICS network address appropriated to the ICS logic terminal of the access control apparatus 1010-7 is set as the caminication address of the corporation W. Further, the PVC virtual channel ID u6C which is appropriated to the ATM exchange 10133-6 is set as the virtual channel ID, and value "22" is set as the channel type, indicating PVC. <<Transferring ICS network packets frem access control apparatus>> The ICS user packet sent toward the terminal of the corporation Z connected to the access control apparatus 1010-5 via the access control apparatus 1010-7 is ICS-encapsulated. upon passing through the access control apparatus 1010-7, and becems an ICS network packet F5 having the transmitting ICS network address "7733" and the receiving ICS network address "994C as an ICS packet header. The ICS network packet F5 is sent frcin the access control apparatus 1010-7 to the ATM exchange 10133-5, and reaches the conversion unit 1033-5 via the interface unit 1133-5. <<Obtaining a virtual channel ID>> The processing device 1233-5 refers to the VC address conversion table 1433-5 using the transmitting ICS network address n7733n and the receiving ICS network address "994C in the header of the received ICS network packet F5, and obtalns the fact that the virtual channel ID identifying the virtual channel set between the conversion units 10335 and 1033-6 inside the ATM exchange 10133-6 connected to the access control apparatus 1010-8 with the ICS logic terminal provided with a qv reviving ICS network address "994C is "55. At the same time, it can be fOUnd that the virtual channel is PVC, from the value "22 A' of the channel type obtained. <<Transfer of packets>> The processing device 1233-5 converts the ICS network packet PS received from the access control apparatus 1010-7 into an ATM cell series, and transfers this to the ATM exchange 10133-7, with regard to the PVC virtual channel nW' obtained as described above. The method of ATM cell conversion is the same as that described above in the embodiment of SW. The above processing procedures of the conversion unit 1033-5 are as shown in FIG.31, and PVC always follows the flow (1). <<Transfer of ATM cells>> The ATM cell series S1 comprised of a plurality of cells obtained by converting the ICS network packet Fl is transferred from the ATM exchange 10133-5 to the relay ATM exchange 10133-7, and further is transferred to the ATM exchange 10133-6 as ATM cell series S2. This operation is the same as with WC. <<Operation following arrival of packet>> Once the ATM cell series S2 reaches the ATM exchange 10133-6, this ATM cell series S2 is transferred fran the ATM exchange 10133-6 to the conversion unit 1033-6 within the ATM exchange 10133-6. The conversion unit 1033-6 assembles the received ATM cells into a CKS frame, which is the same as with WC. In FIG. 28, the restored ICS network packet is shown as an ICS network packet F6, but the contents 61 thereof are identical to that of the ICS network packet F5. The ICS network packet F6 is transferred to an access control apparatus determined by the receiving ICS network address "994C in the header thereof, i.e., to access control device 1010-8 which has an ICS logic terminal appropriated with ICS network address "994C. The above processing procedures of the conversion unit 1033-6 are as shown in FIG. 32, and PVC always follows the flow (1). <<Reverse packet flaw>> Next, description of the case of reverse flow of the ICS packet, i.e., flow fran the corporation Z to the corporation W, will be made with reference to FIGs. 27 and 28, in the same manner as above. An ICS user packet sent out fran the corporation Z to the corporation W is ICS- encapsulated into an ICS network packet F7 having the transmitting ICS network address "994C and the receiving ICS network address "7733" in the header portion thereof, and the processing following the flow shown in FIG.31 as described above is performed by the processing device 1233-6 of the conversion unit 1033-6 within the ATM exchange 10133-6. In this case, the VC address conversion table 14336 in the conversion unit 1033-6 has registered therein a virtual channel ID %C corresponding with a transmitting ICS network address "994C and a receiving ICS network address "7733, so the system converts the ICS network packet F7 into a plurality of ATM cell series and transfers, with regard to the virtual channel ID "66".
The ATM cell series transferred through the ATM network reach the converting unit 1033-5 of the ATM exchange 10133-5, are received 62 .M via the virtual channel having virtual channel ID "55", and restored into an ICS network packet F8 having identical contents with the ICS network frame F7. However, in the conversion unit 1033-5, the pair of the transmitting ICS network address "9944m and the receiving ICS network address M33u in the header of the ICS network packet F4 is already registered in the VC address conversion table 1433-5 in reverse fashion, and information that the virtual channel ID "55" as to this transmitting/receiving address pair is channel type "22" Is obtained, so registration to the VC address conversion table is not performed, and the ICS network packet F8 is transferred to the access control apparatus 1010- 7. <<Ele of application to half-duplex ccnmmication>> The above description has been made with reference to an entxdlmnt of transferring an ICS packet using PVC with a network within ICS 905 having been configured of an ATm network, but the difference between the PVC and the SVC is whether the virtual channel is fixed or called and set as necessary, so there is no difference in the operation itself of transferring packets aver the set virtual channel. Accordingly, regarding the ICS according to the present invention, an example of application to half-duplex canrunication using an ATM network PVC virtual channel is the same as an example of application to half-duplex c=unication using a SVC network PVC virtual channel. <<Exarnple of application to full-duplex ccrffmmication>>
The example of application of PVC full-duplex ccffu=cation is 63 equivalent to the exarrple of application of full-duplex ccnTmxdcation in SW, due to the same reason as the exarrple of application to halfduplex =nunication.
(5) One-on-N or Won-one ccnmmication using PVC In the above exauple. an enbodiment was described wherein one virtual channel was described as a c=urLication path connecting one corporation (location) with one corporation (location), i.e., a ccnTmziication path connecting one ICS logic tern-anal with one ICS logic terminal, but one PVC virtual channel can be used as a conTm-nication path connecting one ICS logic terminal with a plurality of ICS logic terminals. Such One-on-N or Won-one ccnTm-inication will be described with reference to FIGs.33 and 34. <<Description of ceniponents>>
In FIGs.33 and 34, regarding the access control apparatus 101010, the corporation X is connected to an ATM exchange 10133-10 with an ICS logic terminal within the access control apparatus 1010-10 provided with the ICS network address "7711". With the parties to be reached from the corporation X as the corporations A through D, the corporation A is connected to an ICS logic terminal within the access control apparatus 1010-20 provided with the ICS network address "9922 and the corporation B is connected to an ICS logic terminal within the access control apparatus 1010-20 provided with the ICS network address n9923R. In the same manner, the corporation C is connected to an ICS logic terminal within the access control apparatus 1010-40 provided with the ICS network address "9944", and the corporation D is 64 connected to an ICS logic terminal within the access control apparatus 1010-40 provided with the ICS network address n9955". The access control apparatuses 1010-20 and 1010-40 are connected to the ATM exchange 10133- 20, and the ATM exchanges 10133-10 and 10133-20 are connected via a relay network. <<Preparation>> With regard to the ATM exchanges 10133-10 and ATM 10133-20, a single PVC virtual channel connecting the conversion unit 1033-10 within the ATM exchange 10133-10 and the conversion unit 1033-20 within the ATM exchange 10133-20, setting "33" as the virtual channel ID provided to the conversion unit 1033-10 of the virtual Channel, and "44n as the virtual channel ID provided to the conversion unit 1033-20 of the virtual channel. Registration such as shown in FIGs.33 and 34 is pexfo regarding the VC address conversion table 1433-1 within the conversion unit 1033-10 and the VC address conversion table 143320 within the conversion unit 1033-20. <<Packet flow for one-on-N ccmnunicatim>> The flow of packets for one-on-N conTrunication will be described concerning packets sent from the corporation X to each of the corporations A through D. An ICS network packet sent frcin the corporation X toward the corporation A, having a transmitting ICS network address "7711n and a receiving network address "9922", is transferred to the PVC virtual channel with a virtual channel ID "33", by means of making reference to the VC address conversion table 1433-20 in the conversion unit 1033-10. An ICS network packet sent fran the corporation X toward the corporation B, having a transmitting ICS network address "7711n and a receiving network address n9933", is also transferred to the PVC virtual channel with a virtual channel ID "33". An ICS network packet sent from the corporation X toward the corporation C, having a transmitting ICS network address n7711" and a receiving network address "9944n, and An ICS network packet sent frern the corporation X toward the corporation D, having a transmitting ICS network address n7711" and a receiving network address "9955" are transferred to the PVC virtual channel with a virtual channel ID "33n in the same manner. This indicates that one-on-N (corporation X to corporations A through D) ccnwunicatim is being performed while sharing a single PVC virtual channel. Reverse packet flow, i.e., transfer from the corporations A through D to the corporation X, will be described in the next section. <<Packet flow for N- on-one cenTainication>> The flow of packets for N-on-one cenTamication will be described concerning packets sent to the corporation X frem each of the corporations A through D. An ICS network packet sent toward the corporation X fran the corporation A. having a transmitting ICS network address n9922n and a receiving network address n7711", is transferred to the PVC virtual channel with a virtual channel ID "4C, by mans of making reference to the VC address conversion table 143320 in the conversion unit 1033-20. An ICS network packet sent toward the corporation X from the corporation B, having a transmitting ICS network address "9933" and a receiving network address "7711n, is also transferred to the PVC virtual channel with a virtual channel ID "4C An ICS network packet sent toward the corporation X from the corporation C, having a transmitting ICS network address "994C and a receiving network address "7711", and An ICS network packet sent toward the corporation X from the corporation D, having a transmitting ICS network address "9955" and a receiving network address n 7711" are transferred to the PVC virtual channel with a virtual channel ID "4C in the same manner. This indicates that Won-one (corporations A through D to corporation X) canminication is being perfonred while sharing a single PVC virtual channel. (6) Won-N ccffniunication using PVC Using the same method as one-on-N =munication, one PVC virtual channel can be used as a c=mication path connecting a plurality of ICS logic terminals with a plurality of ICS logic terminals. Such Non-N =minication will be described with reference to FIGs.35 and 36. <<Description of cnents>>
The corporation X has ICS logic terminal address n7711" of the access control apparatus 1010-11 as the contact point thereof, the corporation Y has ICS logic terminal address "7722u of the access control apparatus 1010-11 as the contact point thereof, and the access control apparatus 1010-11 is connected to the ATM exchange 10133-11. With the other party which the corporation X or corporation Y is atterrpting to reach as the corporation A or corporation C. The corporation A has ICS logic terminal address R9922" of the access control apparatus 1010-21 as the contact point thereof, the corpo- 67 ration Y has ICS logic temninal address "994C of the access control apparatus 1010-41 as the contact point thereof. The access control apparatuses 1010-21 and 1010-4 are connected to the ATM exchange 10133-21, and the ATM exchanges 10133-11 and 10133-21 are connected via a relay network. <<Preparation>> With regard to the ATM exchanges 1013311 and 10133-21, a single PVC virtual channel connects the conversion unit 1033-11 within the ATM exchange 10133-11 and the conversion unit 1033-21 within the ATM exchange 10133-21, setting R3319 as the virtual channel ID provided to the conversion unit 1033-11 of the virtual Channel, and "4C as the virtual channel ID provided to the conversion unit 1033-21 of the virtual channel. Registration such as shown in FIGs.35 and 36 is performed regarding the VC address conversion table 1433-11 within the conversion unit 1033-11 and the VC address conversion table 1433-21 within the conversion unit 1033-21. <<Packet flow for N-on-N cenTminication>> The flaw of packets for N-on-N cannnication will first be described concerning packets sent frern the corporation X to each of the corporations A and C. An ICS network packet sent frern the corporation X toward the corporation A, having a transmitting ICS network address "7711" and a receiving network address "99220, is transferred to the PVC virtual channel with a virtual channel ID "33" by ffeans of nkiking reference to the VC address conversion table 1433- 11 in the conversion unit 1033-1.An ICS network packet sent frcin the corporation X toward the corporation C, having a transmitting ICS network address M11" and a receiving network address H994C, is also transferred to the PVC virtual channel with a virtual channel ID "3311. Next, the flow of packets will be described concerning packets sent frcm the corporation Y to each of the corporations A and C. An ICS network packet sent frm the corporation Y to the corporation A, having a transmitting ICS network address "7722" and a receiving network address n9922n, is transferred to the PVC virtual channel with a virtual channel ID "33", by means of making reference to the VC address conversion table 1433-11 in the conversion unit 1033-11. An ICS network packet sent fran the corporation Y taward the corporation C, having a transmitting ICS network address M22n and a receiving network address "994C, is also transferred to the PVC virtual channel with a virtual channel ID "33".
Next, reverse packet flaw will be described concerning packets sent to each of the corporations X and Y fram the corporation A. An ICS network packet sent toward the corporation X fram the corporation A, having a transmitting ICS network address "9922" and a receiving network address M11", is transferred to the PVC virtual channel with a virtual channel ID "4C, by means; of making reference to the VC address conversion table 1433-21 in the conversion unit 1033-2. An ICS network packet sent toward the corporation Y frem the corporation A, having a transmitting ICS network address "9922" and a receiving network address "7722", is also transferred to the PVC virtual channel with a virtual channel ID "44", by means of making reference to the VC address conversion table 1433-2 in the conversion unit 1033-2. An ICS network packet sent toward the corporation X fran the corpor-ation C, having a transmitting ICS network address "9944" and a receiving network address "7711", is transferred to the PVC virtual channel with a virtual channel ID n4C. An ICS network packet sent toward the corporation Y frem the corporation C, having a transmtting ICS network address "994C and a receiving network address "7722", is also transferred to the PVC virtual channel with a virtual channel ID n44R. Thus, N-on-N cinication is performed while sharing a single PVC virtual channel.
Embodwrent-4 (Embodiment using an FR network):
An embodiment wt-U be described wherein the network inside the ICS according to the present invention is configured using an FR network. The present embodiment will be described in the following order: (1) supplementary explanation of FR-related conventional art, (2) description of cenWnents, (3) flow of packets using SW, (4) flow of packets using PVC, (5) one-on-N or Won-one cennionication using PVC, and (6) N-on-N cenminication using PVC. With the present entxxliment, two types of methods using SVC or PVC way be used separately, or these may be used in conjunction. Description will be given regarding each of the cases of using SVC and PVC. Also, intra-corporation ccnTmzucatim service and intercorporation cenTnanication service described in Embodiment-1, and virtual dedicated line service described in Effibodiment-2, can both be realized with the access control apparatus according to the present invention, so there is no need to consider these separately regarding network packet conminication with the network within the ICS. Rather, in the present embodiment, these c=unication services will be described integrally. (1) Supplementary explanation of FR-related conventional art:
First, supplementary explanation will be made regarding FRrelated conventional art to the extent that is necessary to describe the present embodiment.
A frame relay consists of using canminication information units called packets with variable lengths to perform cenTrunication and to specify the communication path for each packet. This is a conventional art which has been standardized in the ITU.TI.233 Reccmmendations and so forth which have realized accumlated exchange of packets within a circuit network, and also logic ffultiplexing (a technIque for multiplexing a single physical line into a plurality of logic lines). The service using the above technique is referred to as Frame Mode Bearer Service (hereafter referred to as "FMBS"), and stipulated for FMBS are: the Frame Switch Bearer Service (hereafter referred to as -FSBS") wherein the other party to which connection is to be made is selected (SVC); and the Frame Relay Bearer Service (hereafter referred to as wFRBSn) wherein the other party to which connection is to be made is fixed (PVC). The term nFrame Relayn generally only indicates FRBS ("Frame Relayn in the narrow sense) at times, but with the present invention, "Frame Relayn is used as a term indicating all FMBS including MS and FRBS. In the event that only MS is to be specifically indicated, the term 'Trame relay using SVCR will be used, and in the event that only FRBS is to be specifically indicated, the term 'Trame relay using PVC' will be used. Hereafter, the above- defined "frame relay in the wide sense (FM3S)" will be referred to as FR, and packets transferred over an FR network will be called "FR packetsn in order to distinguish these frem ICS packets.
As described earlier, with an FR network, a plurality of logic lines can be set on a physical line, these logic lines being referred to as logic channels. Identifiers appropriated to FR terminals connecting to both ends of the logic channels (an overall reference to cenTnunication equipment connected to the FR network and comninicating using the FR network) in order to identify the logic channels are called Data Link Connection Identifiers (hereafter referred to as "DLCIR). SVC and PVC are stipulated to logic channels, depending on the way of setting. SVC performs call setting of the logic channel when necessary, and is capable of obtaining a logic line with any FR terminal for a necessary duration, at a necessary speed. Call setting of the logic channel is performed by the FR terminal attempting to initiate ccm=cation, the method thereof being standardized in ITU-T. Call setting requires an address for identifying the FR terminal of the other party to which the call is to be set (hereafter referred to as "FR address"), the FR addresses being systematized so as to be unique in the FR network, thereby enabling identification of each FR terminal. PVC is for fixedly setting a call setting to the FR exchange, and can be viewed as a virtual dedicated line frum the point of the FR terminal.
Regarding the established logic channels, MCIs for identifying logic channels are appropriate for both SVC and PVC, and in the event of transferring an FR packet, the DWI is set at the MCI bit portion m the FR packet address portion shown in FIG.37. There are three formats stipulated for the FR packet address portion, FIG.37 showing the 2-byte foimt which is one of these. Logic channel capabilities (channel capabilities) of the FR network include: Ctted Information Rate (hereafter referred to as "CIR") which is the infonration transfer speed guaranteed at a norml state (a state wherein there is no congestion) of the FR network.
There is the necessity to convert ICS network packets into FR packets in order to send such canTainication packets over an FR network, as shown in FIG.38. Reception of an FR packet results in reverse conver,sion, consisting of extracting and reproducing the ccrnmaication packet (ICS network packet) fram the FR packet as shown in FIG.38. Conversion of this FR packet has been standardized following the ITU-T Recemrendations. Also, protocol headers within the FR packet user information have been standardized in RFC1490 of IEW. (2) Description of ccnWnents:
FIGs.39 and 40 show a forth embodiment of the present invention. In the present embodiment, the internal configuration of the access control apparatus and the operation of the processing device within the access control apparatus are basically the same in principle as the description given in Ent)odiment-l.
73 Appropriated to the access control apparatus 1010-5 are ICS network addresses "7711" and "7722n, serving as connection points (ICS logic terminals) for the corporations X and A which are the users of the ICS 925. Also appropriated to the access control apparatus 1010-7 are ICS network addresses "7733" and "7744", serving as connection points for the corporations W and C, similarly. Appropriated to the access control apparatus 1010-6 are ICS network addresses "992T' and n9933", serving as connection points for the corporations Y and B, and similarly appropriated to the access control apparatus 1010-8 are ICS network addresses "994C and n9955R, serving as connection points for the corporations Z and D. Here, in the entx)dmrent shown in FIGs.39 and 40, etc., the corporations X, Y and so forth, which are given as exarrples of users, may be differing locations within a single corporation which perform the intra-corporation =Trunication, or may be different corporations which perform the inter-corporation canrunication.
An interface unit 1132-5 is provided in the conversion unit 1032-5 within the FR exchange 101325, this interface unit 1132-5 handling the processing of rectifying inter-facing of the communication line 1812-5 connecting the access control apparatus 1010-5 and the FR exchange 10132- 5, and the conamication line 1812-5 connecting the access control apparatus 1010-7 and the FR exchange 10132-5 (physical layers, data link layer protocol). The conversion unit 1032-5 Is cised of a processing device 1232-5, and also an FR address conversion table 1532-5 for call setting with SW, and a MC address 74 conversion table 1432-5 for converting addresses from ICS network addresses used by both SVC and PVC to logic channel. Also, the FR exchange 10132-5 connects the FR address administration server 1632-5serving as an information processing device for storing the FR address conversion table with, in the case of using PVC, the MC address administration server 1732-5 serving as an information processing device for storing the MC address conversion table, thereby performing an information processing relating to address conversion. The carponents making up the FR exchange 10132-6 are the same as the description given regarding the FR exchange 10132-5. In the present ewbodiment, the access control apparatuses 1010-5 and 1010-7 are connected to the FR exchange 10132-5 via the ccnTmnication lines 18105 and 1810-7, respectively, and also, the access control apparatuses 1010-6 and 1010-8 are connected to the FR exchange 10132-6 via the ccxt,Liunicatim lines 1810-6 and 1810-8, respectively. An FR address "2977" unique to the network is set to the conversion unit 1032-5 within the FR exchange 10132-5, and an FR address n2999n unique to the network Is set to the conversion unit 1032-6 within the FR exchange 10132-6. The FR exchanges 10132-5 and 10132-6 are connected via the FR relay network, but in the present entxxUnbent, connecting is made via the FR exchange 10132-7 representing the FR relay network. (3) Flaw of packets using SW:
An embodiment wherein the network within an ICS is configured of an FR network, and SVC is applied as a c=unication path within the FR network, will be described with an example of an ICS user packet sent from a terminal of the corporation X toward a terminal of the corporation Y, with reference to FIGs.39 and 40. <<Preparation>> A receiving ICS network address indicating the destination of the ICS network packet to be transferred from the conversion unit 1032-5 to the FR network, a receiving FR address for indicating the other party for call setting of the logic channel on the FR network, and channel capabilities such as connunication speed requested by the logic channel, are registered in the FR address conversion table 15325 within the conversion unit 1032-5 inside the FR exchange 10132. Also, similar registration is made to the FR address conversion table 1532-6.
In the entxxlurbent, the values set in the FR address conversion table 1532-5 are as follows: "9922" which is the ICS network address appropriated to the ICS logic terminal of the access control apparatus 1010-6 is set as the coninxdcation address of the corporation Y, and the FR address '299C which is uniquely appropriated to the conversion unit 1032-6 within the FR network is registered as the receiving FR address. In the present embodiment, a ceffnunication speed of 64 ICbps is set as the channel capabil-ities. The contents registered to the FR address conversion table 1532-5 are also written to the FR address administration server 1632-5.
The values set in the FR address conversion table 1532-6 are as fol-lows: value "7711n which is the ICS network address appropriated to the ICS logic terminal of the access control apparatus 1010-5 i-s set 76 as the c=nunication address of the corporation X, and the FR address "2977" which is uniquely appropriated in the FR network to the conversion unit 1032-5 within the FR exchange 10132-5 to which the access control apparatus 1010-5 is connected is registered as the receiving FR address. In the present entx)dimnt, a ccamunication speed of 64 Kbps is set as the channel capabilities. The contents registered to the FR address conversion table 1532-6 are also written to the FR address adniinistration server 1632-6. <<Transferring ICS network packets frcrn access control apparatus>> The ICS user packet sent toward the texminal of the corporation Y connected to the access control apparatus 1010-6 via the access control apparatus 1010-5 is ICS-encapsulated upon passing through the access control apparatus 1010-5, and becemes an ICS network packet Fl having the transmitting ICS network address "7711n and the receiving ICS network address "9922" as an ICS packet header. The ICS network packet F1 is sent frarn the access control apparatus 1010-5 to the FR exchange 10132-5, and reaches the conversion unit 1032-5 via an interface unit 1132-5 which processes convers:lon/rectify-ing of electric signals in the ccmnzdcation path. The following is a description thereof made with reference to the flowchart in FIG.43. <<Obtaining a MCI>>
Once the conversion unit 1032-5 receives the ICS network packet Fl(Step S1701), there is the need to request a MCI of the SVC logic channel determined by the relation of the transmitting ICS network address "77W' and the receiving ICS network address n9922n in the ICS 77 packet header, in order to correctly transfer the received packet Fl to the FR exchange 10132-5. In the case that the cenmLinication is based on SW, there are cases that the logic channel corresponding with the ccmninication path is established at the tirre of receiving the ICS network packet, and cases in which the logic channel has not yet been established. In order to find out whether or not the logic channel has been established, the processing device 1232-5 first searches whether or not a logic channel corresponding with the pair of a transmitting ICS network address "7711" and a receiving ICS network address "9922" is registered in the MC address conversion table 14325(Step S1702), and in the event that there is registration here, establishment of the logic channel can be thus confirmed. That is, the fact that the logic channel corresponding with the pair of transmitting ICS network address n7711" and receiving ICS network address "9922" is "1C is obtained, and further, it can be found that this logic channel is ccnTmmicating based on SW, frum the value "10" of the channel type obtained at the same time. In the event that there is no such registration on the MC address conversion table 1432-5, the requested logic channel is established with the latterdescribed <<call setting>>, and MCI is obtained fran the information registered to the MC address conversion table 1432-5 at that point (Step S1703). <<Ca-U setting>> Regarding the above-mentioned Case wherein "there is no registration of a MCI corresponding with a cammications path 78 determined by correspondence between a transmitting ICS network address and a receiving ICS network address on the MC address conversion table 1432-5", i.e., in the case that there is no MCI co=esponding with this conmmications path established yet, it beccoes necessary to perform the following call setting, to establish a logic channel within the FR network coaprising ICS 925. An exarnple of operation of the call setting will now be described.
The processing device 1232-5 of the conversion unit 1032-5, upon making reference to the MC address conversion table 1432-5 and finding that there is no registration of a DWI corresponding with the pair of transmitting ICS network address n7711n and receiving ICS network address "9922" (Step S1702), the processing device 1232-5 of the conversion unit 1032-5 refers to the MC address conversion table 1532-5, finds the receiving ICS network address R9922" registered in the MC address conversion table 1532-5 matching the receiving ICS network address "9922", and obtains transmitting FR address n2999n corresponding thereto and channel capabilities "6W corresponding thereto, and so forth (Step S1705). As described in the above <<Preparation>> section, this transmitting FR address "2999n is an address which is uniquely appropriated within the FR network to the conversion unit 1032-6 in the FR exchange 10132-6 to which the access control apparatus 1010-6 is connected, this access control apparatus 1010-6 having the ICS logic terminal provided with a receiving ICS network address "9922n.
The processing device 1232-5 uses the obtained transmitting FR 79 address "2999" to perform a request for call setting to the FR exchange 10132-5, and also requested at this time is channel capabilities such as c=unication speed of the logic channel Sifflultaneously obtained from the FR address conversion table 1532-5 and so forth(Step S1706). The FR exchange 10132-5, upon receiving the call setting request, uses a signal method which is provided standard to FR exchanges proper as known technique to establish a logic channel within the FR network which reaches the FR exchange 101326. The MCI appropriated for identification of the logic channel is notified frem the FR exchanges to conversion units 1032-5 and 1032-6 therein, but in the event that this is based on stipulations of a signal method according to known technique, the value notified from the calling party FR exchange 10132-5 (e.g., "IC) and the value notified from the receiving party FR exchange 10132-3 (e.g., "26") may not be the same value. At the conversion unit 1032-5, the MCI "1C which is notified frcm the FR exchange 10132-5 is registered in the FR address conversion table 1432-5 along with the transmitting ICS network address "7711" and the receiving ICS network address "9922" (Step S1707), and stores these on the FR address conversion table 1432-5 whUe the connection of the above logic channel is established. When the logic channel connection is no longer necessary, the conversion unit 1032-5 requests call release of the logic channel to the FR exchange 10132-5, and at the same time deletes the registration corresponding with MCI uW m the FR address conversion table 1432-5. Registration to the FR address conversion table 1432-6 in the conversion unit 1032-6 will be described later. <<Packet transfer>> The processing device 1232-5 of the conversion unit 1032-5 converts the ICS network packet F1 received frcin the access control apparatus 1010-5 into a FR packet shown in FIG.38 according to the logic channel(DLCI n1C) established according the above description, and further performs the conversion into FR packets and transfers to the relay FR exchange 101327(Step S1704). <<Transfer of FR packets>>
According to the above-described method, the FR packet S1 obtained by converting the ICS network packet Fl is transferred from the FR exchange 10132-5 to the relay FR exchange 10132-5, and further is transferred to the FR exchange 10132-6 as FR packet S2. The following is a description thereof with reference to the flowchart in FIG.44. <<Operation following arrival of packet>>
Once the FR packet S2 reaches the FR exchange 10132-6(Step S1710), this PR packet S2 is transferred from the FR exchange 10132-6 to the conversion unit 1032-6. At the conversion unit 1032-6, as shown in FIG.38, an ICS network packet is restored fran the received FR packet (Step S1711). In FIG.40, the restored ICS network packet is shown as an ICS network packet F2, but the contents thereof are identical to that of the ICS network packet Fl. The ICS network packet F2 is transferred to an access control apparatus determined by the receiving ICS network address "9922" in the header thereof, i.e., 81 to access control apparatus 1010-6 which has an ICS logic terminal appropriated with ICS network address "9922n(Step S1712).
At this time, at the conversion unit 1032-6, the transmitting ICS network address "7711n, the receiving ICS network address "9922", the channel type "10n indicating the fact this is SM identified at the point of receiving the call, and MCI "2C appropriated at the time of call setting of the SVC logic channel are registered in the FR address conversion table 1432-6(Step S1714), and at this time, the transmitting ICS network address "7711" of the ICS network packet F2 is written to the receiving ICS network address of the FR address conversion table 1432-6, and the receiving ICS network address "9922n is written to the transmitting ICS network address of the FR address conversion table 1432-6, i.e., these are written in reverse positions. However, if at the point of registration an item already exists within the FR address conversion table 1432-6 identical to that regarding which registration is being attempted, no registration is made. The address conversion information registered in the FR address conversion table 1432-6 is stored on the MC address conversion table 1432-6 while the connection of the logic channel having a corresponding logic channel (in this example, MCI "26") is established. <<Reverse packet flow>> Now, description of the case of reverse flaw of the ICS packet, i.e., flaw frcrn the corporation Y to the corporation X, will be made with reference to FIGs.39 and 40, under the presumption that call setting of the SVC logic channel has been made according to the above
82 description.
An ICS user packet sent out fran the corporation Y to the corporation X is ICS-encapsulated upon passing through the access control apparatus 1010-6 and is converted into an ICS network packet F3 having the transmitting ICS network address "9922" and the receiving ICS network address "7711" in the header portion thereof, and is transferred to the conversion unit 1032-6 within the FR exchange 10132-6. The processing following the flow shown in FIG. 43 as described above is performed by the processing device 1232-6 of the conversion unit 1032-6, but the FR address conversion table 1432-5 in the conversion unit 1032-6 has registered therein a MCI "2C with a channel type n1C which means SW, corresponding with transmitting ICS network address "9922" and receiving ICS network address "7711", so the system operates following the flaw (1) shown in FIG.43, thereby converting the ICS network packets F3 into an FR packet (FR packet S3) and transferring, with regard to MCI "26n.
The FR packet S3 is relayed and transferred by the relay FR exchange 10132-5, beccrm FR packet S4 and reach the FR exchange 101325, are received via the logic channel having MCI n 16 u in the conversion unit 10326 thereof, and restored into an ICS network packet F4 having identical contents with the ICS network packet F3. In the conversion unit 1032-5, the pair of the transmitting ICS network address "9922n and the receiving ICS network address "7711" in the header of the ICS network packet F4 is already registered in the FR address conversion table 1432-5 in reverse fashion, so registration 83 to the FR address conversion table is not performed, and the ICS network packet F4 is transferred to the access control apparatus 10105. <<Example of application to half -duplex cenmmication>> The above description has been made with reference to cases wherein an ICS packet is transferred from the corporation X to the corporation Y, and reverse fran the corporation Y to the corporation X, with an network within ICS 925 having been configured of an FR network, being carried out with a single SVC logic channel. For example, applying the transfer and reverse transfer to a request packet to a server terminal of the corporation Y to be connected to the ICS frorn a client te=dnal of the corporation X to be connected to the ICS (transfer), and a response packet to the request packet fraL the client terminal of the corporation X to server terminal of the corporation Y (reverse transfer) results in an application example of half -duplex conm=cation in which one-way c=unication is performed at times, and both-way canmaication is realized by sw-itch-ing the cmication direction by time frames. <<Exarrple of application to full-duplex communication>>
The logic channel set on the FR network is capable of fullduplex cannmication, i.e., simltaneous both-way canmnication, due to the FR stipulations. For example, applying the transfer and reverse transfer to request packets to a plurality of server tern-dnals of the corporation Y to be connected to the ICS frem a plurality of client terminals of the corporation X to be connected to the ICS 84 (transfer), and response packets to the request packets fram the plurality of client terminals of the corporation X to the plurality of server terminals of the corporation Y (reverse transfer) results in asynchronous transfer of packets between the client terminals and the server terminals, so simultaneous both-way cammunication is conducted on the single SVC logic channel serving as the camunication path, thereby making for an application example of full-duplex camunication. (4) Flow of packets using PVC:
An embodknent wherein the network within the ICS 925 is configured with an FR network and PVC is applied as a c=mcation path within the FR network will be described with an example of an ICS user packet sent frcm a terminal of the corporation W toward a terminal of the corporation Z. <<Preparation>> A transmitting ICS network address of an ICS network packet to be transferred to the FR network frem the conversion unit 1032-5, a receiving ICS address, the MCI of the PVC fixed on the FR network (indicating the comn=cation path between the FR exchange 10132-5 and the FR exchange 10132-6), and the channel type indicating that the MCI is PVC, are registered in the FR address conversion table 1432-5. This registration is different frxxn the case of SW, in that registration is made in the FR address conversion table 1432-5 at the same tirre that the PVC logic channel is set in the FR exchanges (10132-5, 10132-5, 10132-6) serving as the ccmxinication path, and is saved in a fixed manner while the ccnm=cation path is necessary, i.e., until the setting of the PVC logic channel is canceled. Also, the registration is made to the MC address conversion table 14326 in the same manner. Incidentally, the MCI of PVC is appropriated to the respective FR exchanges at the time that PVC is fixedly connected between the FR exchanges.
The values set in the MC address conversion table 1432-5 are as follows: value "7733" which is the transmitting ICS network address appropriated to the ICS logic terminal of the access control apparatus 1010-7 is set as the =ninication address of the corporation W, and value n994C which is the receiving ICS network address appropriated to the ICS logic terminal of the access control apparatus 1010-8 is set as the conmniication address of the corporation Z. Further, PVC logic channel ID n18n which is appropriated to the FR exchange 10132-5 is set as the MCI, and value "2C is set for the channel type, indicating PVC. Also, settings for registering to the MC address conversion table 1432-5 are written to the MC address administration server 1732-5, and stored. In the same way, similar settings are made in the MC address conversion table 1432-6 in the conversion unit 1032-6 in the FR exchange 10132-6, with the transmitting ICS network address and the receiving ICS network address reversed. In this case, even if the same PVC is being implied, the MCI may be of a different value to the MC address conversion table 14325.
The values set in the MC address conversion table 1432-6 are as follows: value "994C which is the transmitting ICS network address appropriated to the ICS logic terminal of the access control apparatus 86 1010-8 is set as the camiunication address of the corporation Z, and value "7733" which is the receiving ICS network address appropriated to the ICS logic terminal of the access control apparatus 1010-7 is set as the cemiLmication address of the corporation W. Further, PVC logic channel ID "2V which is appropriated to the FR exchange 10132-6 is set as the MCI, and value "20" is set as the channel type, Indicating PVC. Also, settings registered to the MC address conversion table 1432-6 are alsowritten to and store in the MC address administration server 1732-6. <<Transferring ICS network packets frarn the access control device>> As described in Embodiment-1, the ICS user packet sent toward the terminal of the corporation Z connected to the access control apparatus 1010-8 via the access control apparatus 1010-7 is ICSencapsulated upon passing through the access control apparatus 1010-7, and becomes an ICS network packet F5 having the transmitting ICS network address "7733w and the receiving ICS network address "994C as an ICS packet header. The ICS network packet F5 is sent frcin the access control apparatus 1010-7 to the FR exchange 10132-5, and reaches the conversion unit 1032-5. <<Obtaining a DLCI>> The processing device 1232-5 refers to the MC address conversion table 1432-5 using the transmitting ICS network address "7733" and the receiving ICS network address n994C in the header of the received network packet F5, and obtains the fact that the MCI identifying the logic channel set as a cemninication path for this ICS network address pair is n 18n. At the same time, it can be found that this logic channel is PVC, frcrn the value w20n of the channel type obtained. <<Transfer of packet>> The processing device 1232-5 Converts the ICS network packet F5 received frcn the access control apparatus 1010-7 into an FR frame, and transfers it to FR exchange 10132-7, with regard to the PVC logic channel " 18 0 obtained as described above. The method of FR packet conversion is the same as that described above in the embodiment of SW. The above processing procedures of the conversion unit 1032-5 are as shown in FIG. 43, and PVC always follows the flaw (1). <<Transfer of FR packet>> The FR packet S1 carprised of a plurality of cells obtained by converting the ICS network packet F5 is transferred frem the FR exchange 10132-5 to the relay FR exchange 10132-5, and further is transferred to the FR exchange 10132-6 as FR packet S2. This operation is the same as with SW. <<Operation following arrival of packet>> Once the FR packet S2 reaches the FR exchange 10132-6, this FR packet S2 is transferred fiat the FR exchange 10132-6 to the conversion unit 1032-6 with-in the FR exchange 10132-6. The conversion unit 1032-6 restored the received FR packet into an ICS network packet, which is the same as with SW. In FIG.40, the restored ICS network packet is shown as ICS network packet F6, but the contents thereof are identical to that of the ICS network packet F5. The ICS network 88 packet F6 is transferred to an access control apparatus determined by the receiving ICS network address "994C in the header thereof, i.e., to access control apparatus 1010-8 which has an ICS logic terminal appropriated with the ICS network address "994C. The above processing procedures of the conversion unit 1032-6 are as shown in FIG.44, and PVC always follows the flow (1). <<Reverse packet flow>> Next, description of the case of reverse flaw of the ICS packet, i.e., flow from the corporation Z to the corporation W, will be made, with an PVC logic channel as the canm=cation path. An ICS user packet sent out fran the corporation Z to the corporation W is ICSencapsulated into an ICS network packet F7 having the transmitting ICS network address "994C and the receiving ICS network address "7733" in the header portion thereof when passing through the access control apparatus 1010-8, and is transferred to the conversion unit 1032-6 within the FR exchange 10132-6. The processing following the flow shown in FIG.43 is performed by the processing device 1232-6 of the conversion unit 1032-6. In this case, the MC address conversion table 1432-5 in the conversion unit 1032-6 has registered therein a MCI "2V corresponding with the transmitting ICS network address n9944n and the receiving ICS network address "7733n, so the system converts the ICS network packets F7 into an FR packet and transfers, with regard to MCI "28".
The FR packet transferred through the FR network reach the convension unit 1032-5 of the FR exchange 10132-5, are received via the logic channel having MCI "18n, and restored into an ICS network packet F8 having identical contents with the ICS network packet F7. However, in the conversion unit 1032-5, the pair of the transmitting ICS network address "994C and the receiving ICS network address n7733n in the header of the ICS network packet F8 is already registered in the MC address conversion table 1432-5 in reverse fashion, and an inforrnation that the MCI "18" as to this transinitting/receiving address pair is channel type n2C is obtained, so the registration to the FR address conversion table is not performed, and the ICS network packet F8 is transferred to the access control apparatus 1010-7. <<Example of application to half-duplex caamn-Lication>> The above description has been rnade with reference to an embodiumt of transferring an ICS packet using PVC with a network within ICS 925 having been configured of an FR network, but the difference between PVC and the earlier-described SVC is whether the logic channel is fixed or called and set as necessary, so there Is no difference in the operation itself of transferring packets aver the set logic channel. Accordingly, regarding the ICS according to the present invention, an example of application to half-duplex conmmication using an FR network with a PVC logic channel is the sanie as an example of application to half-duplex ccnTm=cation using a SVC logic Channel. <<Eyle of application to full-duplex camunication>>
Due to the same reason as that regarding the example of application to full-duplex camunication, an example of application to PVC fill'-duplex cammication is the same as an example of application to SVC full-duplex conmiunication. (5) One-on-N or N-on-one ccnm2nication using PVC:
In the above example, an embodimient was described wherein one logic channel was described as a cemmunication path connecting one corporation (location) with one corporation (location), i.e., a ccffm-inication path connecting one ICS logic terminal with one ICS logic terminal, but one PVC logic channel can be used as a cammication path connecting me ICS logic terminal with a plurality of ICS logic terminals. Such One-on-N or N-on-one communication will be described with reference to FIGs.45 and 46. <<Description of cnents>>
The corporation X is connected with an ICS logic texminal within the access control apparatus 1010-10 provided with the ICS network address "7711", and the access control apparatus 1010-52 is connected to the FR exchange 10132-52. With the parties to be reached fram the corporation X as the corporations A through D, the corporation A is connected to an ICS logic terminal within the access control apparatus 1010-62 provided with the ICS network address 09922", and the corporation B is connected to an ICS logic terminal within the access control apparatus 1010-62 provided with the ICS network address "9923". In the saw manner, the corporation C is connected to an ICS logic teaminal within the access control apparatus 1010-82 provided with the ICS network address "994C, and the corporation D is connected to an 91 ICS logic tenninal within the access control apparatus 1010-82 provided with the ICS network address "9955". The access control apparatuses 1010- 62 and 1010-82 are connected to the FR exchange 10132-62, and the FR exchange 10132-52 and FR exchange 10132-62 are connected via a relay network. <<Preparation>> With regard to the FR exchanges 10132-52 and 10132-62, a single PVC logic channel connecting the conversion unit 1032-52 within the FR exchange 10132-52 and the conversion unit 103262 within the FR exchange 10132-62, setting "1C as the MCI provided to the conversion unit 1032-52 of the logic channel, and "2C as the MCI provided to the conversion unit 1032-62 of the logic channel. Registration such as shown in FIGs.45 and 46 is performed regarding the DLC address conversion table 1432-52 within the conversion unit 1032-52 and the MC address conversion table 1432-62 within the conversion unit 103262. <<Fram flow for one-on-N camnmication>> The flaw of packet for one-on-N camnnication will be described concerning packet sent frxxn the corporation X to each of the corporations A through D. An ICS network packet sent fran the corporation X toward the corporation A, having a transinitting ICS network address "7711n and a receiving network address "9922", is transferred to the PVC logic channel with a MCI "lC, by means of making reference to the DLC address conversion table 1432-62 in the conversion unit 103252. An ICS network packet sent fran the corporation X toward the 92 corporation B, having a transmitting ICS network address "7711n and a receiving network address "9933", is also transferred to the PVC logic channel with a MCI "16". An ICS network packet sent frem the corpor-ation X toward the corporation C, having a transmitting ICS network address "7711" and a receiving network address "994C, and an ICS network packet sent frem the corporation X toward the corporation D, having a transmitting ICS network address "7711" and a receiving network addressR9955" are transferred to the PVC logic channel with a MCI "1C in the same manner. This indicates that one-on-N (the corporation X to the corporations A through D) cam-unication is being performed e sharing a single PVC logic channel. Reverse packet flow, i.e., transfer frem the corporations A through D to the corporation X, will be described next. <<Packet flow for N-on-one ccnTminication>> The flow of packet for N-on-one cemmnication will be described concerning packet sent to the corporation X frcin each of the corporations A through D. An ICS network packet sent to the corporation X frem the corporation A, having a transmitting ICS network address "9922R and a receiving network address "7711n, is transferred to the PVC logic channel with a MCI "2C, by means of making reference to the MC address conversion table 1432-62 in the conversion unit 1032-62. An ICS network packet sent toward the corporation X frcin the corporation B, having a transmitting ICS network address R9933" and a receiving network address "7711", is also transferred to the PVC logic channel with a MCI "2C. An ICS network 93 packet sent toward the corporation X frem. the corporation C, having a transmitting ICS network address "994C and a receiving network address "7711", and An ICS network packet sent toward the corporation X fran the corporation D, having a transmitting ICS network address n9955" and a receiving network address "7711" are transferred to the PVC logic channel with a MCI "2C in the same manner. This indicates that N-on-one (the corporations A through D to the corporation X) conTrunication is being performed while sharing a single PVC logic channel. (6) N-on-N ccraTunication using PVC:
* Using the same method as one-on-N comn=cation, one PVC logic channel can be used as a c=unication path connecting a plurality of ICS logic terminals with a plurality of ICS logic texminals. Such Non-N camninication will be described with reference to FIGs.47 and 48. <<Description of cnents>>
The corporation X has ICS logic terminal address "7711" of the access control apparatus 1010-13 as the contact point thereof, the corporation Y has ICS logic terminal address M22" of the access control apparatus 101013 as the contact point thereof, and the access control apparatus 1010-13 is connected to the FR exchange 10132-13. With the other party which the corporation X or corporation Y is attempting to reach as the corporation A or corporation C, the corporation A has ICS logic te=inal address "9922n of the access control apparatus 1010-23 as the contact point thereof, the corporation Y has ICS logic terminal address R994C of the access 94 control apparatus 1010-43 as the contact point thereof. The access control apparatuses 1010-23 and 1010-43 are connected to the FR exchange 10132-23, and the FR exchanges 10132-13 and 10132-23 are connected via a relay network. <<Preparation>> With regard to the FR exchanges 10132-13 and 10132-23, a single PVC logic channel connects the conversion unit 1032-13 within the FR exchange 10132- 13 and the conversion unit 1032-23 within the FR exchange 10132-23, setting "1611 as the MCI provided to the conversion unit 1032-13 of the logic channel, and "2C as the MCI provided to the conversion unit 1032-23 of the logic channel. The registration such as shown in FIGs.47 and 48 is perforn-ed regarding the MC address conversion table 1432-13 within the conversion unit 1032-13 and the MC address conversion table 1432-23 within the conversion unit 103223. <<Packet flaw for N-on-N cenTrunication>> The flow of packets for N-on-N a=unication will first be described concerning packets sent from the corporation X to each of the corporations A and C. An ICS network packet sent fram the corporation X toward the corporation A, having a transmitting ICS network address "7711" and a receiving network address n9922", is transferred to the PVC logic channel with a MCI "16", by mans of nk-Ocing reference to the MC address conversion table 1432-13 in the conversion unit 1032-13. An ICS network packet sent frern the corporation X toward the corporation C, having a transmitting ICS network address "7711" and a receiving network address "9944", is also transferred to the PVC logic channel with a MCI "1C. Next, the flow of packet wiIII be described concexning packets sent fran the corporation Y to each of the corporations A and C. An ICS network packet sent frcxn the corporation Y toward the corporation A, having a transmitting ICS network address n7722n and a receiving network address "9922", is transferred to the PVC logic channel with a MCI n1611, by means of making reference to the MC address conversion table 1432-13 in the conversion unit 1032-13. An ICS network packet sent fran the corporation Y toward the corporation C, having a transmitting ICS network address "7722" and a receiving network address "994C, is also transferred to the PVC logic channel with a MCI "1C.
Next, reverse packet flaw will be described concerning packets sent to each of the corporations X and Y from the corporation A. An ICS network packet sent toward the corporation X frcin the corporation A, having a transmitting ICS network address u9922" and a receiving network address "7711", Is transferred to the PVC logic channel with a MCI "26n, by nveans of making reference to the MC address conversion table 1432-23 in the conversion unit 1032-2. An ICS network packet sent toward the corporation Y fram the corporation A, having a transmitting ICS network address n9922" and a receiving network address "7722", is also transferred to the PVC logic channel with a MCI 112C. An ICS network packet sent toward the corporation X frem the corporation C, having a transmitting ICS network address "994C and a receiving network address "7711", is transferred to the PVC 96 logic channel with a MCI n2C. An ICS network packet sent toward the corporation Y fram the corporation C, having a transmitting ICS network address H9944n and a receiving network address "7722n, is also transferred to the PVC logic channel with a MCI "26n. Thus, N-on-N cen=mication is performed while sharing a single PVC logic channel.
Embodiment-S (Containment of telephone line, ISDN line, CATV line, satellite line, IM line, cellular phone line):
As described in Rrbodiment-l and Embodiment-2, connection to access control apparatuses which serve as access points is not limited to communication lines to LANs (dedicated lines, etc.), but rather, telephone lines, ISDN lines, CATV lines, satellite lines, M lines and cellular phone lines may also be contained. The following is a description of an embodiment.
FIG.49 through FIG.52 illustrate an example of a system containing telephone lines, ISDN lines, CATV lines, satellite lines, M lines and cellular phone lines, according to the ICS 6000. The line por-tions 60111 and 6011-2 are made up of telephone line conversion units 6030-1 and 6030-2, ISDN line conversion units 6029-1 and 6029-2, CATV line conversion units 6028-1 and 6028-2, satel-lite line conversion units 6027- 1 and 6027-2, M line conversion units 6026-1 and 6026-2, and cellular phone line conversion units 6025-1 and 6025-2. The telephone line conversion units 6030-1 and 6030-2 have capabilities for conversion and reverse-conversion equivalent to physical layers and data link layers (first layer and second layer of 97 OSI (open Systems Interconnection) ccnTrmication protocol) between the telephone lines 6160-1 and 6160-2 and the access control apparatuses 6010- 1 and 6010-2. Also, the ISDN line conversion units 6029-1 and 6029-2 have capabilities for conversion and reverse-conversion equivalent to physical layers and data Link layers between the ISDN lines 6161-1 and 6161-2 and the access control apparatuses 6010-1 and 6010-2, and the CATV line conversion units 6028-1 and 6028-2 have capabilities for conversion and reverse-conversion equivalent to physical layers and data Lu& layers between the CATV lines 6162-1 and 6162-2 and the access control apparatuses 6010-1 and 6010-2. Further, the satellite line conversion units 6027-1 and 6027-2 have capabilities for conversion and reverseconversion equivalent to physical layers and data link layers between the satellite lines 61631 and 6163-2 and the access control apparatuses 60101 and 6010-2, and the M conversion units 6026-1 and 6026-2 have capabilities for conversion and reverse-conversion equivalent to physical layers and data link layers between the M lines 6164-1 and 6164-2 and the access control apparatuses 6010-1 and 6010-2. The cellular phone conversion units 6025-1 and 6025-2 have capabilities for conversion and reverse-conversion equivalent to physical layers and data link layers between the cellular phone wireless lines 6165-1 and 6165-2 and the access control apparatuses 6010-1 and 6010-2. An exarrple of the conversion table 6013-1 is shown in FIG.53.
The ICS packet interface network 6050 transfers ICS network packets following the RFC791 or RFC1883 stipulations, without change 98 In the ICS network packet format. The X. 25 network 6040 accepts ICS network packets and converts these to X.25 format and transfers, and at the end reverse-converts these into ICS network packet format and outputs. The FR network 6041 accepts ICS network packets and converts these to FR format and transfers, and at the end reverse-converts these into ICS network packet format and outputs. The ATM network 6042 accepts ICS network packets and converts these to ATM format and transfers, and at the end reverse-converts these into ICS network packet format and outputs. The satellite ccmmunication network 6043 accepts ICS network packets and transfers the information using the satellite, and at the end reverseconverts these into ICS network packet format and outputs. Also, the CATV line network 6044 accepts ICS network packets and converts into CATV format packets and transfers the contents thereof, and at the end reverseconverts these into ICS network packet format and outputs. <<Ccnmn preparation>> The conversion table 6013-1 within the access control apparatus 6010-1 contains the transmitting ICS network address, the sender ICS user address, the receiver ICS user address, the receiving ICS network address, the request identification and the speed as shown in FIG.53. The request identification represents services and connections, e.g. as follows: value "1" indicates intra-corporation service, value R2" indicates inter- corporation service, value n3n indicates virtual dedicated line connection, and value n4n indicates ICS server connection. The conversion table 6013-1 contains addresses registered 99 therein with the same rrbp-thod as that described in Embodiment-l and Rrbodiment-2. The ICS network server 670 has an ICS user address of "200C and an ICS network address of "7821n, and is connected to the access control apparatus 6010-1 via ICS ccmmnications line 6081-1. The conversion table 6013-1 contains the receiver ICS user address "2000n of the ICS network server 670, receiving ICS network address of "7821n and request identification of "C'.
The operation thereof is described with reference to FIG.54. <<Ccnman:Lcatim frcm a telephone line to an ISDN line>> The user 6060-1 sends out the ICS user frame F110 with a sender ICS user address "3400" and a receiver ICS user address n2500m to the access control apparatus 6010-1 via the telephone line 6160-1. The access control apparatus 6010-1 receives the ICS user packet F110 frorn the telephone line conversion unit 6030-1 with the ICS network address "7721"(Step S1800), and checks whether or not the ICS network address H7721" is registered on the conversion table 6013-1 with the request identification as virtual dedicated line connection "3n(Step S1801). In this case, the registration has not been made, so next, the access control apparatus 6010-1 checks that the receiver ICS user address n250C is registered on the conversion table 6013-1(Step S1803) and that the request identification has been registered as intercorporation camiunication "2"(Step, S1804). In this case, the registration has been made, so the receiving ICS network address 1155220 is obtained fram the conversion table 6013-1, processing such as billing related to the inter- corporation m=mication is performed (Step S1805), the ICS user packet F110 is ICS-encapsulated (step S1820), converted into an ICS network packet F120, and sent to the ICS packet transfer network 6030 via ICS network ccnTrunicatim line 6080-1 (Step S1825). <<Caffrmication fran an ISDN line to a CATV 1-ine>> The user 6061-1 sends out the ICS user packet F111 with a sender ICS user address "3500" and a receiver ICS user address "260C to the access control apparatus 6010-1 via the ISDN line 6161-1. The access control apparatus 6010-1 receives the ICS user packet F111 frorn the ISDN line conversion unit 6031-1 with the ICS network address "7722" (Step S1800), and checks whether or not the ICS network address M22" is registered on the conversion table 6013-1 with the request identification as virtual dedicated line connection "3"(Step S1801). In this case, the registration has been made, so the receiving ICS network address "552Y' is obtained frem the conversion table 6013-1, processing such as billing related to dedicated line connection ls performed(Step S1802), the ICS user packet F111 is ICS-encapsulated (Step S1820), converted into an ICS network packet F121, and sent to the ICS packet transfer network 6030 via ICS network cenTrunication line 6080-l(Step S1825).
Incidentally, regarding the virtual dedicated line connection, the sender ICS user address and receiver ICS user address written within the ICS network packet F111 do not have to be used in the access control apparatus. Next, the ICS network packet F121 reaches the access control apparatus 6010-2 via the FR network 6041 and the 101 ICS network camunication line 6080-2 for example, is reversely ICSencapsulated and restored into the ICS user packet F111, and reaches the user 6062-2 connected to the CATV line 6162-2 via the CATV line unit 6028-2 which is provided with the transmitting ICS network address "5523n. <<Ccm,mmication from a CATV line to a satellite line>> The user 6062-1 sends out the ICS user packet F112 with a sender ICS user address "360C and a receiver ICS user address "2700" to the access control apparatus 6010-1 via the CATV line 6162-1. The access control apparatus 6010-1 receives the ICS user packet F112 frcin the CATV line conversion unit 6032-1 with the ICS network address "7723u (Step S1800), and checks whether or not the ICS network address "7723" is registered on the conversion table 6013-1 with the request identification as virtual dedicated line connection RY'(Step S1801). In this case, the registration has not been rnade, so next, the access control apparatus 6010-1 checks that the receiver ICS user address 112700n is registered on the conversion table 6013-l(Step S1803) and that the request identification has been registered as intercorporation conTrunicatlon R2"(Step S1804). In this case, the registration has been rnade as inter-corporation coffnunication "2", so the receiving ICS network address "5524n is obtained fram the conversion table 6013-1, processing such as billing related to intercorporation cionTanicatim is performed(Step S1805), the ICS user packet F112 is ICS-encapsulated(Step S1820), converted into an ICS network packet F122, and sent to the ICS packet transfer network 630 102 via ICS network cem-mmication line 6080-l(Step S1825). The ICS network packet F122 reaches the access control apparatus 6010-2 via the ATM network 6042 and the ICS network cam-unication line 6080-2 for example, is reversely ICS-encapsulated and restored into the ICS user packet F112, and reaches the user 6063-2 with the receiving ICS network address "2700". <<CcnTaunication frcin a satellite line to an M line>> The user 6063-1 sends out the ICS user packet F113 with a sender ICS user address "370OR and a receiver ICS user address "280C to the access control apparatus 6010-1 via the telephone line 6163-1. The access control apparatus 6010-1 receives the ICS user packet F113 fran the satellite line conversion unit 6027-1 with the ICS network address "772C(Step S1800), and checks whether or not the ICS network address R7724n is registered on the conversion table 6013-1 with the request identification as virtual dedicated line connection "3"(Step S1801). In this case, the registration has not been made, so next, the access control apparatus 6010-1 checks that the receiver ICS user address "2800" is registered on the conversion table 6013-l(Step S1803) and that the request identification has been registered as intercorporation commmication "2"(Step S1804). In this case, the registration has been made as inter-corporation camirdcation "2n, so the receiving ICS network address "5525" is obtained frcm the conversion table 6013-1, processing such as billing related to intercorporation caminication is performed(Step S1805), the ICS user packet F113 is ICS-encapsulated(Step S1820), converted into an ICS 103 network packet F123, and sent to the ICS fram transfer network 6030 via ICS network comenication line 6080-l(Step S1825). The ICS network packet F123 reaches the access control apparatus 6010-2 via the ICS packet interface 6050 and ICS network c=unication line 60802 for example, is reversely ICS-encapsulated and restored into the ICS user packet F113, and reaches the user 6064-2 with the receiving ICS network address "2800". <<Ccmainication fran an M line to a cellular telephone line>> The user 6064-1 sends out the ICS user packet F114 with a sender ICS user address "0012" and a receiver ICS user address n2900m to the access control apparatus 6010-1 via the M line 6164-1. The access control apparatus 6010-1 receives the ICS user packet F114 frem the M line conversion unit 6026-1 with the ICS network address "7725n (Step S1800), and checks whether or not the ICS network address "7725" is registered on the cormersion table 6013-1 with the request identification as virtual dedicated line connection u3"(Step S1801). In this case, the registration has not been made, so next, the access control apparatus 6010-1 checks that the receiver ICS user address "290C written in the ICS user packet F114 is registered on the conversion table 6013-l(Step S1803) and that the request identification has been registered as inter-corporation conTrunication "2" (Step S1804). In this case, the registration has not been rnade as inter-corporation cenminication "2u, so the access control apparatus 6010-1 checks whether the registration has been rnade as intracorporation coffnimication ul"(Step S1810). In this case, the 104 registration has been made as intra-corporation communication "1n, so the receiving ICS network address "552C is obtained fran the conversion table 6013-1, processing such as billing related to intracorporation communication is performed(Step S1811), the ICS user packet F113 is ICSencapsulated(Step S1820), converted into an ICS network packet F124, and sent to the ICS packet transfer network 6030 via ICS network communication line 6080-1 (Step S1825). The ICS network packet F124 reaches the access control apparatus 6010-2 via the CATV Line network 6044 and ICS network ccunimication line 6080-2 for example, is reversely ICS-encapsulated and restored into the ICS user packet F114, and reaches the user 6065-2 with the receiving ICS network address "290OR. <<CcnTmziication frorn a cellular telephone line to a telephone line>> The user 6065-1 sends out the ICS user packet F115 with a sender ICS user address n380C and a receiver ICS user address "2400n to the access control apparatus 6010-1 via the cellular telephone line 6165-1. The access control apparatus 6010-1 receives the ICS user packet F115 fran the cellular telephone line conversion unit 6035-1 with the ICS network address "772C(Step S1800), and checks whether or not the ICS network address "772C is registered on the conversion table 6013-1 with the request identification as virtual dedicated line connection "X' (Step S1801). In this case, the registration has not been rnade, so next, the access control apparatus 6010-1 checks that the receiver ICS user address "240Ou written in the ICS user packet F115 is registered on the conversion table 6013-l(Step S1803) and that the request identification has been registered as inter-corporation camunication "2" (Step S1804). In this case, the registration has been made as inter- corporation cammnication "2", so the receiving ICS network address n5521" is obtained fran the conversion table 6013-1, processing such as billing related to intra-corporation camunication is performed(Step S1811), the ICS user packet F115 is ICS-encapsulated (Step S1820), converted into an ICS network packet F125. and sent to the ICS packet transfer network 6030 via ICS network cenTrunication line 6080-l(Step S1825). The ICS network packet F124 reaches the access control apparatus 6010-2 via the satellite line network 6043 and ICS network comninication. line 6080-2 for example, is reversely ICS-encapsulated and restored into the ICS user packet F115, and reaches the user 6060-2 with the receiving ICS network address "2400". <<Ccnnunication frcin a cellular telephone line to an ICS network server> > The user 6066-1 sends out the ICS user packet F116 w:th a sender ICS user address n3980" and a receiver ICS user address "2000" to the access control apparatus 6010-1 via the cellular telephone line 6166-1. The access control apparatus 6010-1 receives the ICS user packet F116 frem the cellular telephone line conversion unit 6025-1 with the ICS network address "772C(Step S1800), and checks whether or not the ICS network address "772C is registered on the conversion table 6013-1 with the request identification as virtual dedicated line connection "3R(Step S1801). In this case, the registration has not been made, so next, the access control apparatus 6010-1 checks that the receiver ICS 106 user address "2000n written in the ICS user packet F116 is registered on the conversion table 6013-l(Step S1803) and that the request identification has been registered as inter-corporation camninication "2n (Step S1804). In this case, the registration has not been made so the access control apparatus 6010-1 checks whether or not the request identification is registered as intra-corporation cenmmicatim R1n (Step S1810). In this case, the registration has not been made, so the access control apparatus 6010-1 checks whether or not the request identification is registered as ICS network server OC(Step S1812). In this case, the registration has been made as inter-corporation cenTnunication "2", so the receiving ICS network address "8721' is obtained fran the conversion table 6013-1, processing such as billing related to intra-corporation canmnication is performed(Step S1813), the ICS user packet F115 is ICS- encapsulated(Step S1820), converted into an ICS network packet, and sent to the ICS network server 670 (Step S1825).
According to the above-described transferring methods, changing the ICS user address written into the ICS user packet allows for the sending side to select any of the following on the receiving side: telephone li-ne, ISM line, CATV line, satellite line, IPX lime, or cellula phone line; regardless of whether the sending side is any of the following: telephone line, ISDN line, CATV line, satellite line, IPX line, or cellular phone line.
Embodiment-6 (Dial-up router):
107 An example of using a dial-up router will be described with reference to FIG. 55 through FIG. 57. A user 7400-1 within a LAN 7400 has an ICS user address "2500", and similarly, a user 7410-1 within a LAN 7410 has an ICS user address "3601". The administrator of the dial-up router 7110 enters in the router table 7113-1 of the dial-up router 7110 the telephone number specified frem the receiver ICS user address and the order or priority thereof frem the router table input unit 7018-1.
Now, registration to the router table 7113-1 will be described with reference to FIG.58. In the event that the receiver ICS user address "3601" has been specified, the highest on the priority list is telephone number "03-1111-1111", No.2 on the priority list is telephone number "0322222222", and No.3 on the priority list is telephone number "03-33333333n. The receiver ICS user addresses "3602" and n370C are also registered in the same imnner. Here, reference will be made to the flawchart shawn in FIG.59 as an example of c=unication from the sender ICS user address "2500" to the receiver ICS user address "3601".
The user 7400-1 sends the ICS user packet F200 to the dial-up router 7110 via the gateway 7400-2 and the user logic cenTwnication line 7204. The dial-up router 7110 operates under the processing device 7112-1, and receives the ICS user packet F20O(Step S1901), reads the receiver ICS user address "3601" included in the ICS user packet F200, searches the router table 7113-1 with the address n3601" included in the ICS user packet F200 as the search keyword(Step S1902), 108 and finds the telephone number with high priority. In this case, the telephone number highest on the priority list is "03-1111-1111", as shown in the router table in FIG.58, so the dial-up router 7110 dials the telephone number "03-1111-1111" via the telephone network as the first attempt(Step S1910). As a result, a telephone communication path 7201 with the line portion 7011-1 of the access control apparatus 7010-1 which is called by the telephone number "03-1111-1111" is established, i.e., the dial-up router 7110 and the line portion 7011-1 are connected by a telephone line. In the event that the dial-up router 7110 and the line portion 7011-1 are not connected by a telephone line, dial-up router 7110 finds the telephone number "032222-2222" that is second in priority, and dials the telephone number "03-2222-2222" via the telephone network as the first attempt(Step S1911). As a result, a telephone =runication path 7202 with the line portion 7011-1 of the access control apparatus 7010-1 which is called by the telephone number "03-2222-2222" is established. Also, in the event that the dial-up router 7110 and the line unit 7011-1 are not connected by a telephone line, the dialup router 7110 finds the telephone number "033333-3333" that is third in priority, and dials the telephone number "03-3333-3333" via the telephone network as the third attempt(Step S1911). As a result, a telephone communication path 7203 with the line portion 7011-3 of the access control apparatus 7010-3 which is called by the telephone number "03-3333-3333" is established. In the event that the dial-up router and the access control apparatus are not connected by a telephone line regardless of 109 the above multiple attempts, the dial-up router 7110 stores the received ICS packet F200 in a memory 7117-l(Step S1913), makes reference again to the router table(Step S1902) after a certain amunt of time(Step S1914), and attempts establishment of telephone catinsMiCation Path 7201, 7202 or 7203.
Next, description will be made regarding the operations following the connection of the aforementioned dial-up router 7110 and the Line portion 7011-1. The dial-up router 7110 enters verification procedures for determining whether this is an authorized user registered in the access control apparatus 7010-1 as a user(Step S1920). Any arrangement which achieves the object of verification is agreeable for the verification procedures, but for example, an ID and password for identifying the dialup router are sent frcin the dial-up router 7110 to the line portion 7011 via the telephone line 7201 the verifying unit 7016-1 of the access control apparatus 7010-1 checks whether or not the received ID and password are correct, and in the event that the user is correct, the fact that the user is correct, i.e., cenniunication data notifying "affirmative confirmation" is sent to the dial-up router 7110 via the telephone ccomunication path 7210, thus campleting the verification procedures. In the event that either one of the ID or password is incorrect. communication via the telephone cermunication path 7210 is terminated.
Upon receiving notification of "affiiTative confirmation" from the telephone line 7201 in user verification, the dial-up router 7110 sends the ICS user packet F200 to the telephone communication path 7201 (Step S1930), and when the confirmation has been made that the access controlapparatus 7010-1 has received the ICS user packet F200, releases the telephone ccnTmziicatim path 7201 and hangs up(Step S1931), thus completing the above-described series of processes for the dial-up router.
Upon receiving the ICS user packet F200, the access control apparatus 7010-1 uses the conversion table 7013-1 under administration of the processing device 7012-1, generating an ICS network packet F301, which is sent out into the ICS network cemmunication line 7301 within the ICS 7100. In the present embodiment, the transmitting ICS network address for the ICS network packet F301 is "7501" which is a network address appropriated to the ICS logic terminal within the line portion 7011-1, and the receiving ICS network address is R8601" appropriated to the ICS logic terminal within the access control apparatus 7010-2. The ICS network packet F301 is transferred a = ss the ICS 7100 and reaches the access control apparatus 7010-2, where it is reversely ICS-encapsulated and reaches the user 7410-1 with the ICS user address "3601" via the user logic c=nunication line 7601.
In the above description, in the event that a telephone =ffminication path 7202 called by the telephone number R03-2222-2222" is established between the dial-up router 7110 and the line portion 7011-1 of the access control apparatus 7010-1, the ICS user packet F200 is transferred from the dial-up router 7110 to the line portion 7011-1 via the telephone ccuniziication path 7202. In this case also, upon receiving the ICS user packet F200, the access control apparatus
7010-1 performs the ICS encapsulation to generate an ICS network packet F302, which is sent out into the ICS network cmication line 7301 within the ICS 7100. Now, the transmitting user address for the ICS user packet F302 is R7502", and the receiving ICS user address, "8601".
Also, in the event that a telephone c=unication path 7203 called by the telephone number "03-3333-3333" is established between the dial-up router 7110 and the line portion 7011-3 of the access control apparatus 7010-3, the ICS user packet F200 is transferred from the dial-up router 7110 to the line portion 7011-3 via the telephone communication path 7203. In this case, upon receiving the ICS user packet F200, the access control apparatus 7010-3 performs the ICS encapsulation to generate an ICS network packet F303, which is sent out into the ICS network c=unication line 7303 within the ICS 7100. In this case, the transmitting user address for the ICS user packet F303 is "7800" which is a network address provided to an ICS logic terminal within the line portion 7011-3, and the receiving ICS user address is u8601", which is a network address provided to an ICS logic terminal within the line portion 7010-2. The ICS network packet F303 is transferred across the ICS 7100 and reaches the access control apparatus 7010-2, where it is reversely ICS-encapsulated and reaches the user 74101 with the ICS user address "3601" via the user logic conrunication line 7601.
112 Drbodinmt-7 (ICS address name administration server):
In the present embodiment shown in FIG.60. ICS address name administration servers 13000-1, 13000-2, 13000-3 and 13000-4 within the ICS 13000-1 are respectively connected to access control apparatuses 13010-1, 13010-2, 13010-3 and 13010-4. The ICS address name administration server 13000-1 has a processing device 130001-1, a co=elation table 13002-1 and an ICS name converting table 13003-1, and fur-ther is appropriated an ICS network address "9801" which can be uniquely distinguished within the ICS.
The other ICS address name administration servers 13000-2, 13000-3 and 13000-4 also have the same capabilities as the ICS address name administration server 13000-1, each containing a processing device, a correlation table and an ICS name conversion table, each having the respective ICS network addresses "9802n, "9803n and n980C, each ccm=cating one with another using ICS network =nunication functions, and each capable of exchanging the info = tion that another ICS address name administration server has. The ICS address namp- VAN representative administration server 13020-1 has an ICS network address "9805", and another ICS address narne VAN representative administration server 13020- 2 has an ICS network address n9806n, these communicating with a great inany ICS address name administration servers and other ICS address narne VAN representative adndnistration servers using ICS network conr=cation functions, and each capable of exchanging the inforrnation that each other has. The ICS address name VAN representative administration server 13020-1 has a processing 113 device 13031-1 and a database 13032-1, performs exchange of the information such as ICS addresses and ICS names with all ICS address name administration servers within the VAN 13000-1, the collected data relating to the ICS addresses and ICS names is stored in the database 13032-1. Hence the ICS address name VAN representative administration server 13020-1 represents the VAN 13030-1 by means of performing the above procedures.
The above ICS address name VAN administration server 13020-1 includes a processing device, a correlation table and an ICS name conversion table, and another embodiment may be formed by grouping the correlation table and the ICS name conversion table into a single table, in which case one of the ICS user addresses contained in both of these two types of tables is used.
Entxxhment-8 (Full-duplex ccnynmicatim including satellite conminication path: Part l): <<Configuration of user, data providing corporation, communication satellite, etc. >> The present embodiment perform a type of ful 1 -duplex communication by ining a satellite's transmitting functions and IP cemumication functions. In the present entodiment, RIP terminaln indicates a terminal or =iputer which has functions of sending and receiving IP packets.
Description will be made with reference to FIG. 61. The present embodiment is rised of: ICS 16000-1; access control apparatuses
114 16100-1, 16110-1 and 16120-1; data prxyviding corporation 16200-1; IP terminal 16210-1 of the data providing corporation; satellite transmission corporation 16300-1; IP terminal 16310-1 of the satellite transrnission corporation; database 16320-1 of the satellite transmission corporation; satellite transinission equipment 16330-1 of the satellite transmission corporation; conTmmication satellite 164001; users 16500-1, 16510-1 and 16520-1; IP texffdnals 16501-1, 16511-1 and 16521-1 of each user; satellite receivers 16502-1, 16512-1 and 16522-1 of each user; satellite electric wave ccnTnmication lines 16600-1, 16610-1, 16620-1 and 16630-1; and user logic cenTrunication lines 16710-1, 16720-1, 16730-1 and 16740-1. The IP terminals 16210-1, 16501-1, 16511-1 and 16521-1 each have ICS user addresses n3000", "2300n, "240C and "2500", and are respectively connected to the access control apparatuses 16100-1, 16120-1, 16120-1 and 16110-1, via user logic camiunication lines. The IP terminal 16310-1 can be classified as an ICS network server, having an ICS special nurber "4300", and connected to the access control apparatus 16100-1 via the ICS network communication line within the ICS 16000-1. Electric wave transrnitted fran the satellite transmitter 16330-1 transfer information via the satellite electric wave cannanication path 16600-1, the electric wave is received by satellite receivers 16502-1, 16512-1 and 16522-1, the received data being delivered to the IP terminals 16501-1, 16511-1 and 16521-1. The present embodirrent is characterized by the satellite transrnission corporation 16300-1 having satellite conTrunication functions.
<<Preparation: Description of conventional art>>
In order to describe the present entx)diment, first, known TCP and UDP camt=cation technology will be explained. FIG. 62 is an example of fullduplex communication using TCP, wherein a communicating party 1 sends a synchronous packet #1, and a convunicating party 2 returns a confirming packet #2 upon receiving the first packet. C=nunication procedures wherein such packets #1 and #2 are sent and received is referred to as TCP connection establishment phase. Next, both communicating parties send and receive packets #31, #3-2, #3-3 and #3-4, and communication procedures wherein such sending and receiving of packets is performed is referred to as TCP data transfer phase. Finally, a f i nal packet #4 is sent and a confinning packet #5 is returned to conf:dn the reception of the packet. CenTm-mication procedures wherein such packets #4 and #5 are sent and received is referred to as TCP connection ending phase. Besides the above TCP cemm=cation procedures, there are cormi=cation procedures called UDP, comprised of data transfer alone. An example is shown in FIG. 62, UDP is characterized in comparison with TCP by the absence of the TCP connection establishment and connection ending phases.
The ccnn=iication procedures according to the present entxKliment will be made with reference to FIGs. 61 and 63. In the following procedures, the aforewmtioned TCP technology full-duplex canmaication is enployed except for the cases of transmission instruction to satellite transion equipment (#6 and #14 in FIG.63) and "data transmission" using electric wave frem the satellite transmission 116 equipment (#7 and #15 in FIG.63), however, only the TCP data transfer phase is shown in FIG.63, and the TCP connection establist phase and TCP connection ending phase are emitted fran the drawing and from description thereof.
The IP terminal 16210-1 of the data providing corporation 162001 obtains "data to be provided" frem the database 16220-1 thexeof and sends it to the IP terminal 16310-1 of the satellite transmission corporation 16300-1 which can be identified by the ICS special number "4300", using the IP frame transmission functions of the ICS (#1 in FIG.63, the same hereafter). The satellite transmission corporation 16300-1 stores the received Mata to be provide& in its database 16320-1. The IP terniinal 16501-1 of the user 16500-1 sends an "inquiry packet" to the IP texminal 16210-1 which can be identified with the ICS user address "3000"(#2). The IP terminal 16210-1 returns a "reply packet"(#3), the IP terminal 16501-1 receives this "reply packeC, and then sends a "request packeC to the IP terminal 162101(#4). When the IP tenninal 16210-1 receives the "request packeC, it sends a "transmission instruction packet" to the IP terminal 16310-1 (#5). When the IP terminal 16310-1 receives the ninstruction packetn, it instructs transmission of the ndata to be provide& saved in the database 16220-1(#6). The satellite transmission equipment 16330-1 emits the "data to be provide& as electric wave toward the cenTnunication satellite 16400-1 (first half of #7), the canrunication satellite 16400-1 amplifies the received "data to be provided" and emits it (latter half of V), the satellite receiving equipment 16502- 117 1 receives the "data to be provide& as electric wave, and hands it to the IP terminal 16501-1. Thus, the IP terminal 16501-1 obtains the "data to be providedn via the conTwriication satellite 16400-1, and sends a "reception confirmation packet" to the IP terminal 16210-1 of the corporation 16200-1 providing the Mata to be providedn(#8). Next, the IP terminal 16210-1 sends a "reception confirmation packet" to the IP terminal 16310-1 of the satellite transmission corporation 16300-1 (#9). In the above procedures, #1, #2, C, #4, #5, #8 and #9 use the above-descr. ibed TCP caam=cation technology, and the TCP data transfer phase alone is shown and described.
Next, the procedures #10, #11, #12, #13, #14, #15, #16 and #17 shown in FIG.63 are almost the same as the above procedures, the difference in this exle being that instead of the user 16500-1, the IP terminal 16501-1 and the satellite receiving equipment 16502-1, another user 16510-1, IP terminal 16511-1 and satellite receiving equipment 16512-1 are used, and the present embodiment is capable of transferring Mata to be provide& to a plurality of users.
The above-described cenminication procedures shall be described with reference to FIG.64. The sending of an "inquiry packet"(#2), returning a "reply packet"(#3), sending of a urequest packeC(#4), ndata transmissionn by satellite cammnicatim(#7), and sending "reception confirmation packet"(#8) in FIG.64 corresponds with the sending of an ninquiry packeC(#2), returning a "reply packetn(C), sending of a "request packetn(#4), "data transmission" by satellite conrunication(V), and sending "reception confirmation packet"(#8) in 118 FIG. 63. From the above description, in the event that the satellite camiLmication corporation 16300-1 and the data providing corporation 16200-1 are viewed as an integrated communication function unit (hereafter referred to as an integrated ccrnaziication entity"). The user in FIG. 64 can be considered to be performing full-duplex ccnTm=catim with the aforementioned integrated c=unication entity. <<Variation on above embodimp-nt>>
Next, a variation of the above embodiment wherein only a portion of the ccmmcation procedures has been changed shall be described with reference to FIGs.61 and 65.
First, the IP terminal 16501-1 of the user 16500-1 sends an "inquiry packeC to the IP terminal 16210-1 which can be identified with the ICS user address n3000" (#1 in FIG.65: the same hereafter). The IP terminal 16210-1 returns a "reply packetu(#2), the IP terminal 16510-1 receives the "reply packeC, and then sends a "request packeC to the IP terminal 16210-1(0). When the IP terminal 16210-1 receives the "request packeC, it sends "data to be provided" frcm the database 16220-1 thereof to the IP terminal 16310-1 which can be identified by the ICS special number "4300"(#4), and also sends a "transmission instruction packetn to the IP terminal 16310-1(#5).
The satellite transmission corporation 16300-1 stores the received Mata to be provide& in its database 16320-1, and instructs transmission of the saved "data to be providedn(#6). The satellite transmission equipt 163301 emits the ndata to be provided" as electric wave toward the ccmnLmication satellite 16400-1 (first half 119 of #7), the camiunication satellite 16400-1 amplifies the received "data to be provide& and emits it (latter half of #7), the satellite receiving equipment 16502-1 receives the "data to be provided" as electric wave, and hands it to the IP terminal 16501-1. Thus, the IP terminal 165011 obtains the Mata to be provideW via the conrunication satellite 16400-1, and sends a nreception confirmation packetn to the IP terminal 16210-1 of the corporation 16200-1 providing the "data to be provided"(#8). Next, the IP terminal 16210-1 sends a nreception confirmation packeC to the IP tenninal 16310-1 of the satellite transmission corporation 16300-1(#9). Next, the procedures #10, #11. #12, #13, #14, #15, #16, #17 and #18 are almost the same as the above procedures, the difference in this example being that instead of the user 16500-1, the IP terminal 16501-1 and satellite receiving equipment 16502-1, another user 16510-1, IP terminal 16511-1 and satellite receiving equipment 16512-1 are used. <<Another variation on above entxxlirnent>> In the above two embodlments, TCP technology full-duplex caffnmication is employed, and only the TCP data transfer phase is shown in the figures, with the TCP connection establishment phase and TCP connection ending phase being omitted from the drawings and from description thereof. In the embodiment to be described now, UDP ccffnunicatim technology described in FIG.62 is applied to a part or to all, and part or all of the packet sending and receiving using the TCP data transfer phase technique is replaced with packet sending and receiving using the UDP data transfer phase technique.
<<Another variation on above embodiment>> Another version will be described with reference to FIG.66. In FIG.61, the satellite transmission corporation 16300-1, the IP terminal 16310-1 of the satellite transmission corporation, the database 16320-1 of the satellite transmission corporation, and satellite transmission equipffwt 16330-1 of the satellite transmission corporation are each within the ICS 16000-1, the IP terminal 16310-1 being provided with an ICS special number n4300'. As ca%5ared to this, in the exanple shawn in FIG.66, the satellite transmission corporation 16300-2, the IP terminal 16310-2 of the satellite transmission corporation, the database 16320-2 of the sate M te transmission corporation, and the satellite transmission equipment 16330-2 of the satellite transmission corporation are each outside of the ICS 16000-2 the IP terminal 16310-2 being provided with an ICS user address "3900" The data providing corporation 16200-1 and users 16500-1, 16510-1, 16520-1 are capable of sending and receiving of IP packets can be performed ccinpletely regardless of whether the other party has an ICS user address or an ICS special number, so sending and receiving of IP frames can be performed in cambination with satellite ccffninucation with the example in FIG.66 just as with that in FIG.61.
Embodiment-9 (FuLl-duplex ccmn-mication including satellite ccmTunication path: Part 2):
The present entxxUmmt is another variation of Embodiment-8, with description being made with reference to FIGs.61 and 66. The
121 data providing corporation 16200-1, the satellite transmission corporation 16300-1, the user 16500-1, etc. are the same; only the communication procedures are different. Also, TCP technology fullduplex =munication will be effployed, but FIG.67 only illustrates TCP data transfer phase.
The IP terminal 16210-1 of the data providing corporation 162001 obtains "data to be provided" from the database 16220-1 thereof and sends this to the IP terminal 16310-1 of the satellite transmission corporation 16300-1 which can be identified by the ICS special nuTber "4300", using the IP frc-xm transmission functions of the ICS (#1 in FIG.67, the sarne hereafter). The satellite transmission corporation 16300-1 stores the received Mata to be provided" in its database 16320-1. Next, the IP terminal 16210-1 of the data providing corporation 16200-1 sends a "transmission notification frarne" to the IP terminal 16501-1 of the user 16500-1(#2). Upon receiving the n transmission notification packeC, the IP terminal 16501-1 returns a u transmission consent packeC to the IP terminal 16210-1(#3). When the IP terminal 16210-1 receives the ntransmission consent packeC, i sends a "transmission instruction packetn to the IP terminal 163101(#4). When the IP terminal 16310-1 of the satellite transmission corporation 16300-1 receives the ntransmission instruction packetn, i instructs transmission of the "data to be provided" saved in the database 16220-1(#5). The satellite transmission equipment 16330-1 emits the Mata to be provideT as electric wave toward the comrunication satellite 16400-1(fi-rst half of #6), the cannunication 122 satellite 16400-1 amplifies the received ndata to be providedn and emits it(latter half of #6), the satellite receiving equipment 16502-1 receives the "data to be provide& as electric wave, and hands it to the IP terminal 16501-1. Thus, the IP terminal 16501-1 obtains the ndata to be provide& via the cmcation satellite 16400-1, and sends a nreception confixmtion packet" to the IP terminal 16210-1 of the data providing corporation 16200-1 providing the "data to be providedn(V).
The above-described ccmnLmicatim procedures shall be described with reference to FIG.68. The sending of an ntransmission notification packet"(#2), the returning of a "transmission consent packet"(#3), ndata transmission" by satellite cannunication (#6), and the sending of "reception confirrnation packet-(#7) in FIG.68 correspond with the sending of an "transmission notification frame"(#2), the returning of a "transmission consent packet"(#3), "data transmissionn by satellite ccnrunication(#6), and the sending of "reception confirmation packet"(#7) in FIG.67, respectively. Frern the above description, in the event that the satellite conTnunication corporation 16300-1 and the data providing corporation 16200-1 are viewed as an integrated ccmn=cation function unit (hereafter referred to as an "integrated conrunication entity"), the user 16500-1 in FIG.68 can be considered to be performing full-duplex =Tamication with the aforementioned integrated conTnmication entity. <<Another variation on above effbodiment>>
Next, a variation of the above embodiment wherein only a portion 123 of the ccnTmrilcation procedures has been changed shall be described with reference to FIGs.61 and 69. The IP terminal 16210-1 of the data providing corporation 16200-1 sends a "transmission notification packet" to the IP terminal 16501-1 of the user 16500-1 (#1 in FIG.69: the same hereafter). Upon receiving the "transmission notification packeC, the IP terminal 165011 returns a "transmission consent packeC to the IP terminal 16210-1(#2). When the IP terminal 16210-1 receives the ntransmission consent packet", it obtains "data to be providedn frern the database 16220-1 thereof and sends this to the IP terminal 16310-1 of the satellite transmission corporation 16300-1 which can be identified by the ICS special nuTber I'430On(#3) and further sends a "transinission instruction packet" to the IP terminal 16310-1(#4). When the IP terminal 16310-1 of the satellite transmission corporation 16300-1 receives the "transmission instruction packet", it instructs transmission of the ndata to be prx)vided" saved in the database 16220-1(#5). The subsequent cemn=cation procedures are the same as those described above. <<Another variation on above embodimnt>> In the above two effbodiments, TCP technology full-duplex coffnmication is "loyed, and only the TCP data transfer phase is shown in the figures, with the TCP connection establishment phase and the TCP connection ending phase being anitted frem the drawings and fran the description thereof. In the enbodinmt to be described now, UDP caffnunication technology described in FIG.62 is applied to a part or to all, and part or all of the packet sending and receiving using
124 the TCP data transfer phase technique is replaced with packet sending and receiving using the UDP data transfer phase technique. < <Another variation m above ewbodiment > > Another version will be described with reference to FIG.66. In FIG.61, the satellite transmission corporation 16300-1, the IP terminal 16310-1 of the satellite transmission corporation, the database 16320-1 of the satellite transmission corporation, and the satellite transmission equipment 16330-1 of the satellite transmission corporation are each within the ICS 16000-1, the IP terminal 16310-1 being provided with an ICS special nu "430On. As caT to this in the example shown in FIG.66, the satellite transmission corporation 16300-2, the IP terminal 16310-2 of the satellite transmission corporation, the database 16320-2 of the satellite transmission corporation, and the satellite transmission equipment 16330-2 of the satellite transmission corporation are each outside of the ICS 16000-2 the IP terminal 16310-2 being provided with an ICS user address "390ON Entod-unent-10 (Full-duplex ccnm=cation including satellite ccmTunication path: Part 3):
The present embodiment is another variation of Embodwrent-8, and will be described with reference to FIGs. 61 and 70. The data providing corporation 16200-1, the satellite transmitting corporation 16300-1, the user 16500-1 are the same, with only the cann-mication procedures being different. The present effibod=hent perform the fi 111 duplex cann=cation of WP technology, but only the TCP data transfer phase is shown in FIG.70.
The IP terminal 16210-1 of the data providing corporation 162001 sends a "Plan notification packet" to each of the following: the IP terminal 16501-1 having an ICS user address "2300", ICS user address -2400- (165111), and ICS user address n250OR (16521-1) (#1 in FIG.70: the san-e hereafter). Next, the IP terminal. 16210-1 of the data providing corporation 16200-1 obtains Mata to be provide& fran the database 16220-1 thereof and sends this to the IP terminal 16310-1 of the satellite transrnission corporation 16300-1 which can be identified by the ICS special nmter "4300", using the IP frarne transfer functions of the ICS(#2). The satellite transmission corporation 16300-1 stores the received Mata to be provided" in its database 16320-1, and also instructs transmission of the "data to be provide& (#3). The satellite transmission equipmmt 16330-1 emits the "data to be providedn as electric wave toward the cenTnanication satellite 16400-1(first half of #4), the caffumnication satellite 16400-1 arnpLifies the received ndata to be providedn and emits it(latter half of #4), the satellite receiving equipment 16502-1 receives the "data to be provided" as electric wave, and hands it to the IP terminal 16501-1.
Thus, the IP temainal. 16501-1 obtains the "data to be provideffl via the =aninication satellite 16400-1, and sends an "individual report packeC to the IP terminal 16210-1(#5-1). Using the saw canninication procedures, the IP terminal 16511-1 obtains the "data to be provideT, and sends an nindividual report packetn to the IP 126 terminal 16210-1(#5-2). The iP terminal 16521-1 also obtains the "data to be provided", and sends an "individual report Packet- to the IP terminal 16210-1(#5-3). The IP terminal 16210-1 sends an "individual inquiry packet" to the IP terminal 16511-1 of the user 16510-1(#6), and the IP teaminal 16511-1 returns an nindividual reply packet" to the IP terminal 16210-1(V).
The above-described cemm=catim procedures will be described with reference to FIG.71. The sending of the "plan notification frameu(#1), "data transmission" by sateMte ccnTminication(#4), the sending of "individual report packetn(#5-2), the sending of "individual inquiry packeC(#6), and the returning of "individua]L reply packet"(#7) in FIG.71 correspond with the sending of the nplan notification packetn(#1), "data transmissionn by satellite ccnTmziication(#4), the sending of "individual report frame"(#5-2), the sending of "individual inquiry fran-e"(#6), and the returning of -individua_l reply frame"(#7) in FIG.70, respectively. Frxxn the above description, in the event that the satellite canminication corporation 16300-1 and the data providing corporation 16200-1 are viewed as an integrated c=runication entity, the user 16500-1 in FIG.67 can be considered to be performing ful]-duplex cammmication with the aforementioned integrated ccnTmmication entity. <<Another variation on above effbodinent>>
In each of the above effbodiments, the full-duplex caffmmicatim of TCP technology is employed, and only the WP data transfer phase is shown in the figures, with the TCP connection establishmmt phase and 127 TCP connection ending phase being emitted from the drawings and frem the description thereof. In the embodirrent to be described now, UDP ccxtaiuniCation technology described in FIG.62 is applied to a part or to all, and part or all of the packet sending and receiving using the TCP data transfer phase technique is replaced with packet sending and receiving using the UDP data transfer phase technique. <<Another variation on above ent)odiment>>
Another version will be described with reference to FIG.66. In FIG.61, the satellite transmission corporation 16300-1, the IP texndxial 16310-1 of the satellite transmission corporation, the database 16320-1 of the satellite transmission corporation, and the satellite transmission equit 16330-1 of the satellite transmission corporation are each within the ICS 16000-1, the IP terminal 16310-1 being provided with an ICS special nurber n4300". As caq:) to this, in the example shown in FIG.66, the satellite transmission corporation 16300-2, the IP terminal 16310-2 of the sate M te transmission corporation, the database 16320-2 of the satellite transmission corporation, and the satellite transmission equipment 16330-2 of the satellite transmission corporation are each outside of the ICS 16000-2 the IP terminal 16310-2 being provided with an ICS user address n390OR Embodirrbent-11 (Full-duplex comnniication including satellite conTnunication path: Part 4):
The present ewbodiment is another variation of Embodiment-8, and will bedescribed with reference to FIGs.61 and 72. The data 128 providing corporation 16200-1, the satellite transmission corporation 16300-1, the user 16500-1 are the same, with only the communication procedures being different. The present embodiment performs the fl 111 duplex camiunication of TCP technology, but only the TCP data transfer phase is shown in FIG.72.
The IP terminal 16210-1 of the data providing corporation 162001 obtains "data to be provideffl from the database 16220-1 thereof and sends this to the IP terndnal 16310-1 of the satellite transmission corporation 16300-1 which can be identified by the ICS special nu "4300", using the IP frame transfer functions of the ICS (#1 in FIG.72: the same hereafter). The satellite transmission corporation 16300-1 stores the received "data to be provided" in its database 16320-1.
Next, the IP terminal 16501-1 of the user 16500-1 sends an "inquiry packet" to the IP terminal 163101 which can be identified with the ICS user address R4300"(#2). The IP terminal 16310-1 retums a nreply packet"(#3), the IP terminal 16510-1 receives the "reply packetR, and then sends a "request packet" to the IP terminal 163101(#4). When the IP terminal 16310-1 receives the nrequest packeC, it instructs satellite transmission equipment of the Mata to be providedn saved in the database 16300-1(#5). The satellite transmission equipment 16330-1 emits the Mata to be provided" as electric wave toward the ccaniunication satellite 16400-1 (first half of #6), the cenrunication satellite 16400-1 amplifies the received Mata to be provideW and emits it (latter half of #6), the satellite receiving equipment 16502-1 receives the Mata to be providedl' as electric wave, and hands it to the IP terminal 16501-1. Thus, the IP terminal 16501-1 obtains the Mata to be pruvided" via the conminication sate M te 16400-1, and sends a nreception confirmation packeC to the IP terminal 16310-1 of the data providing corporation 16200-1 providing the Mata to be provided" (V). In the above procedures, #1, #2, #3, #4 and #7 use the abavedescribed TCP cenTm-mication technology, and the TCP data transfer phases alone are shown and described. Next, the procedures #8, #9, #10, #11, #12 and #13 shown in FIG.72 are almost the same as the above procedures, the difference in this example being that instead of the user 16500-1, the IP terminal 165011, and the satellite receiving equipment 16502-1, another corporation 16510-1, IP terminal 16511-1, and satellite receiving equipment 165121 are used.
The above-described camninication procedures shal 1 be described with reference to FIG.64. The sending of an ninquiry packetn(#2), the returning of a "reply packet"(#3), the sending of a "request packet"(#4), "data transmission" by satellite cenm-mication(#7), and the sending of nreception confirmation packet"(#8) in FIG.64 correspond with the sending of an ninquiry packetn(#2), the returning of a "reply packet"(#3), the sending of a "request packet"(#4), ndata transmissionn by satellite cammunication(V), and the sending "reception confirmation packet"(#8) in FIG.72, respectively. From the above description, in the event that the satellite conmnication corporation 16300-1 and the data providing corporation 16200-1 are viewed as an integrated communication entity, the user 16500-1 in FIG. 64 can be considered to be performing full-duplex caffmmication with the aforementioned integrated camiLmication entity. <<Another variation on above entx)diment>> In the above two embodiments, the full-duplex Lmication of TCP technology is employed, and only the TCP data transfer phase is shown in the figures, with the TCP connection establishment phase and TCP connection ending phase being omitted fram the drawings and frum the description thereof. In the embodiment to be described now, UDP communication technology described in FIG.62 is applied to a part or to all, and part or all of the packet sending and receiving using the TCP data transfer phase technique is replaced with packet sending and receiving using the UDP data transfer phase technique. <<Another variation on above embodiment>>
Another version will be described with reference to FIG.66. In FIG.61, the satellite transmission corporation 16300-1, the IP terminal 16310-1 of the satellite transmission corporation, the database 16320-1 of the satellite transmission corporation, and the satellite transmission equipment 16330-1 of the satellite transmission corporation are each within the ICS 16000-1, the IP terminal 16310-1 being provided with an ICS special number "4300". As cam to this, in the example shown in FIG.66, the satellite transmission corporation 16300-2, the IP terminal 16310-2 of the satellite transmission corporation, the database 16320-2 of the satellite transmission corporation, and the satellite transmission equit 16330-2 of the satellite transmission corporation are each outside of the ICS 16000-2 the IP terminal 16310-2 being provided with an ICS user address "390C Embodiment-12 (Full-duplex comffunication including satellite cenTM. Mication path: Part 5):
The present embodiment performs a type of full-duplex caffnmication by combining a satellite transmission f=tion and an IP coffinunication function. A major difference between the present embodiment and Ent)odinmt-8 is the fact that the satellite receiving equipment is within the access control apparatus in the present enbodirrent.
Description will be made with reference to FIG.73. The present embodiment is emprised of: an ICS 16000-3; access control apparatuses 16100-3, 161103 and 16120-3; satellite reception equipments 16102-3, 16112-3 and 161223; a data providing corporation 16200-3; an IP terminal 16210-3 of the data providing corporation; a satellite transmission corporation 163003; an IP terminal 16310-3 of the satellite transmission corporation; a database 16320-3 of the satellite transmission corporation; a satellite transmission equit 16330-3 of the satellite transmission corporation; a cenrunication satellite 16400-3; users 16500-3, 16510-3 and 16520-3; IP terminals 16501-3, 16511-3 and 16521-3 of each user; satellite airwaves ccnymxiication lines 16600-3, 16610-3, 16620-3 and 16630-3; and user logic conminication lines 16710-3, 16720-3, 16730-3 and 16740-3. The IP terminals 16210-3, 16501-3, 165113 and 16521-3 each have ICS user
132 addresses "3000", "2300", n240T' and "2500", and are respectively connected to the access control apparatuses 16100-3, 16120-3, 16120-3 and 16110-3, via user logic communication lines. The IP tenninal 16310-3 can be classified as an ICS network server, having an ICS special number "4300", and connected to the access control apparatus 16100-3 via the ICS network communications line within the ICS 16000-3. Electric wave transmitted from the satellite transmitter 16330-3 transfers information via the satellite electric wave cammnication path 16600-3, the electric wave is received by satellite receivers 16112-3 and 16122-3. << Example of c=mication procedures >> The ccffm=cation procedures according to the present embodiment will be made with reference to FIG.73and 74. In the following procedures, the aforementioned full-duplex c=unication of TCP technology is emp loyed except for the cases of transmission instruction to satellite transmission equipment (#5 and #12 in FIG.74) and "data transmissionn using electric wave from the satellite transmission equipment (#6 and #13 in FIG.74), however, only the WP data transfer phase is shown in FIG.74.
The IP terminal 16210-3 of the data praviding corporation 162003 obtains Rdata to be prDvided" frcm the database 16220-3 thereof and sends this to the IP terminal 16310-3 of the satellite transmission corporation 16300-3 which can be identified by the ICS special number "4300", using the IP packet transfer function of the ICS (#1 in FIG.74, the same hereafter). The satellite transmission corporation 16300-3 133 stores the received "data to be provideC in its database 16320-3. The IP terminal 16501-3 of the user 16500-3 sends an "inquiry packeC to the IP terminal 16310-3 which can be identified with the ICS user address "4300" (#2). The IP terminal 16310-3 returns a "reply packeC(#3), the IP terminal 16501-3 receives the "reply packeC, and then sends a "request packeC to the IP terminal 16310-3 (#4). When the IP terminal 163103 receives the "request packetR, it converts the Mata to be provide& saved in the database 16320-3 into ICS packet fonnat and instructs transmission thereof (#5). Here, the data portion of the ICS packet is the "data to be provided", and the destination ICS user address is address "230C of the IP terminal 16501-3. The satellite transmission equiprrent 16330-3 emits the ICS packet including "data to be provided n as electric wave toward the c=nunication. satellite 16400-3 (first half of #6), the caffninication satellite 16400-3 awplifies the received "data to be providedn and emits it (latter half of #6), the satellite receiving equits 16502-3, 16112-3 and 16122-3 each receive the ICS frarne including the "data to be provide& as electric wave, each check the destination of the ndata to be provided", and since the destination of the ndata to be provide& is IP terndnal 16501-3, the access control apparatus 16122-3 returns the Mata to be provided", to the ICS user frame format, and sends it to the IP terminal 16501-3(#7). Upon receiving the Mata to be provided", the IP terminal 16501-3 sends a "reception confirmation packet" to the IP terminal 16310-3(#8). In the above procedures, #1, #2, C, #4, #7 and #8 use the above-described TCP 134 ccffm-inicatim technology, and the TCP data transfer phase alone is shown and described.
Next, the procedures #9, #10, #11, #12, #13, #14 and #15 shown in FIG.74 are almost the same as the above procedures, the difference 1n this exarrple being that instead of the user 16500-3, the IP terminal 16501-3, and the satellite receiving equipment 16502-3, another canpany 16510-3, IP terminal 16511-3, and satellite receiving equipment 16512-3 are used, and the present ent)odt is capable of transferring "data to be provide& to a plurality of users.
The above-described can=mication procedures shall be described with reference to FIG.64. The sending of an "inquiry packet"(#2), the returning of a "reply packetw(#3), the sending of a nrequest packet"(#4), "data transmission" by satellite ccmmmication(#7), and the sending of "reception confirmation packet" in FIG.64 correspond with the sending of an ninquiry packetu(#2), the returning of a "reply packet"(#3), the sending of a "request packet"(#4), ndata transmission" by satellite ccnrunication(#7), and the sending of Rreception confirmation packet"(#8) in FIG.74, respectively. Frcxn the above description, in the event that the satellite cannunication corporation 16300-3 and the data providing corporation 16200-3 are viewed as an nintegrated camunication entity, the user in FIG.64 can be considered to be perforn-dng full-duplex commnication with the aforementioned integrated conTamication entity. <<Another variation on above embodiment>>
In the above two entxxbirkents, the flill-duplex cemminication of TCP technology is employed, and only the TCP data transfer phase is shown in the figures, with the TCP connection establishment phase and TCP connection ending phase being emitted frem the drawings and frem the description thereof. In the embodiment to be described now, UDP caummication technology described in FIG. 62 is applied to a part or to all, and part or all of the packet sending and receiving using the TCP data transfer phase technique is replaced with packet sending and receiving using the UDP data transfer phase technique. <<Another variation m above enbodimnt>>
Another version will be described with reference to FIG.75. In FIG.73, the satellite transmission corporation 16300-3, the IP terminal 16310-3 of the satellite transmission corporation, the database 16320-1 of the satellite transmission corporation, and the satellite transmission equipnmt 16330-3 of the satellite transmission corporation are each Inside the ICS 16000-3, the IP terminal 16310-3 being provided with an ICS special number "4300". As ccny to this, in the example shown in FIG. 75, the satellite transmission corporation 16300-4, the IP terminal 16310- 4 of the satellite transmission corporation, the database 16320-2 of the satellite transmission corporation, and the satellite transmission equipment 16330-4 of the satellite transmission corporation are each outside of the ICS 16000-4, the IP tentnal 16310-4 being provided with an ICS user address "390T' Embodiment - 13 (Control of receiving priority degree):
In the control field of the IP packet shown in FIG.3, there is a
136 transmitting IP address and a destination IP address in addition to the "protocol type", and in the TCP packet shown in FIG.76 and the UDP frame shown in FIG.77 there are defined a sender's port number and an intended receiver's port number, respectively. The 48 bits of data consisting of the IP address (32 bits) and the port number (16 bits) laid out is called a socket number. That is, socket number = IP address 11port number. In the present effbodiment, the follg terms shall be used: sender's socket number = sender's IP address 11 sender's port nwkber; intended receiver's socket nu = intended receiver's IP address 11 intended receiver's port number. The present embodiment is an example of controlling the degree of priority of the ICS user frarne which is obtained by reaching the access control apparatus frcm the ICS network conTrmication line and being reversely ICSencapsulated here, this controlling the degree of priority being performed using the "protocol type" which is displayed in the ICS user frame, and the socket number thereof.
As shown in FIGs.78 and 79, an ICS 17000-1 includes access control apparatuses 17100-1, 17110-1, 17120-1, 17130-1, 17140-1, 17150-1 and 17160-1, and the access control apparatus 17100-1 includes a line unit 17111-1, a processing device 17112-1 and a conversion table 17113-1. Blocks 17200-1, 17210-1, 17220-1, 17230-1, 17240-1, 17250-1, 17260-1, 17270-1 and 17280-1 are each corporation LANs, and are each connected to the ICS 17000-1 via the respective gateways 17201-1, 17211-1, 17221-1, 17231-1, 17241-1, 17251-1, 17261-1, 17271-1 and 17281-1. Each LAN has 2 to 3 texminals having functions for sending IP user packet, wherein the ICS user addresses are: for within LAN 17200-1. "260OR and "2610"; for within LAN 17200-1, "2600- and "2610"; for within LAN 17210-1, "123C and "1240"; for within LAN 17220-1, "2700n, w2710-, and -272C; for within LAN 17230-1, "2800" and R28100; for within LAN 17240-1, "1200" and "121C; for within LAN 17250-1, -120C and "1210"; for within LAN 17260-1, "2200n and "22100; for within LAN 17270-1, "2300" and n231C; and for within LAN 17280-1, "2400" and "2410". Further, blocks 17291-1 and 17292-1 are each terminals which have functions of sending and receiving IP user packets, respectively having ICS user addresses n250C and n1250n, being connected to ICS 17000-1. <<Conversion table>> The conversion table 17113-1 within the access control apparatus 17100-1 shall be described with reference to FIGs.80 and 81. The function of the conversion table as the same as those in the other ent)odurents, and the present invention is characterized in that the portion table, named ndegree of priority of reception" code, degree of priority of protocol, degree of priority of TCP socket, and degree of priority of UDP socket, which am cnents of the conversion table 17113-1 are used for controlling the degree of priority. In the event that the transmitting ICS network address of the conversion table is "7821", the "degree of priority of reception" code is stipulated to be it qv pr-7821. That is, the "degree of priority of reception" code is made to be a parameter which is dependent on the ICS network address provided to the ICS user logic terminal sent from the access control apparatus after the ICS reverse encapsulation. Looking at the other portion table of the conversion table 17113-1, e.g., in regard to "pr7821", the degree of priority of protocol is described as being "p-l", the degree of priority of Tep socket as "t-l", and the degree of priority of UDP socket as %ULL". Here, MLW' indicates "unspecified". The degree of priority of protocol "p-l" dictates that the degree of priority of is, in descending order, "TCP99, RMPR, "WPMu and "IGPM".
Looking at even other portion table with regard to the degree of priority of TCP socket "t-l", the dictated order of degree of priority of is, in descending order, "sk-l" and "sk-7n. Looking at even other portion table with regard to the degree of priority of UDP socket "u1", the dictated order of degree of priority is, in descending order, "sk-Y' and "sk-8". Fbxther, in the contents of the socket code "sk-l" wh-ich is written in another portion table, "To" indicates the intended receiver's socket number, and indicates that the intended receiver's IP address is "2100" and that the intended receiver's port number is "30n, and in the same manner, in the contents of the socket code nsk2", "Fran" indicates the sender's socket number, and indicates that the sender's IP address is "1240" and that the sender's port number is 1%32n.
<<Individual description of ICS packet>>
The ICS network frame NFO1 is sent out fran the terminal 17291-1 with the ICS user address R250C, and then is ICS-encapsulated. at the access control apparatus 17110-1 with a transmitting ICS network 139 address "720C and a receiving ICS network address "7821", then is transferred within the ICS 17000-1 and reaches the access control apparatus 17100-1, where it is reversely ICS-encapsulated to become an ICS user frame UFOl, and reaches the temninal with the ICS user address "2100" via the user logic convunication Line 17821-1. The nprotocol type" of the control field of the user packet UFO1 which is within the ICS network packet NFO1 is TCP, and the "intended receiver's port number" of the TCP packet is "3C in the example.
In the following, beginning with a packet NF02, brief description will be made in the o of NF03, NF04, NFOS, NF06, NF07, NFOS, NF09, NFlO and NF11, as shown in FIG.78.
A frame NF02 is sent out from a terminal with the ICS user address "2600", and then is ICS-encapsulated at with a transmitting ICS network address "7300" and a receiving ICS network address n7821", then is transferred within the ICS and is reversely ICS-encapsulated to become a frame UF02, and reaches the terminal with the ICS user address "2110" via the user logic comnanication line 17821-1. The "protocol type" of the packet UF02 is TCP, and the nintended receiver p s port number" of the TCP packet is "30n, in this example.
A frame NF03 is sent out from a terminal with the ICS user address "12300, and then is ICS-encapsulated at with a transmitting ICS network address "7400" and a receiving ICS network address "7822", then is transferred within the ICS and is reversely ICS-encapsulated to become a packet UF03, and reaches the terminal with the ICS user address "1200" via the user logic c=unication line 17822-1. The 91protocol type" of the packet UP03 is TCP, and the "intended receiver's port number" of the TCP packet is "3C, in this example.
A frame NF02 is sent out frcrn a terminal with the ICS user address R124C, and then is ICS-encapsulated at with a transmitting ICS network address "7400" and a receiving ICS network address R7822n then is transferred within the ICS and is reversely ICS-encapsulated to beccime a packet UF04, and reaches the terminal with the ICS user address "1210" via the user logic c=amication line 17822-1. The nprotocol typeu of the packet UF04 is TCP, and the "intended receiver's port number" of the TCP packet is n32u, in this example.
A frame NF05 is sent out f-reit a terminal with the ICS user address n1250R, and then is ICS-encapsulated at with a transmitting ICS network address "7500" and a receiving ICS network address "7822u then is transferred within the ICS and is reversely ICS-encapsulated to beccime a packet UP05, and reaches the terminal with the ICS user address "1220" via the user logic cencation line 17822-2. The Elprotocol type" of the packet UF05 is TCP, and the "intended receiver's port number" thereof is n32", in this example.
A frc-m NF06 is sent out frern a terminal with the ICS user address "2610n, and then is ICS-encapsulated at with a transmitting ICS network address "7300" and a receiving ICS network address "7823n, then is transferred within the ICS and is reversely ICS-encapsulated to became a packet UF06, and reaches the terndnal with the ICS user address "2200" via the user logic ccmmmicatim line 17823-1. The "protocol type" of the packet UF06 is UDP, and the "intended 141 receiver's port number" of the TCP packet is "40", in this example.
A frame NF07 is sent out fram a terminal with the ICS user address "2700", and then is ICS-encapsulated, at with a transmitting ICS network address "7600" and a receiving ICS network address n7823' then is transferred within the ICS and is reversely ICS-encapsulated to became a packet UF07, and reaches the terminal with the ICS user address "2210" via the user logic cmication line 17823-1. The 11pratocol typen of the packet UF07 is UDP, and the "intended receiver's port number" thereof is "40n, in this example.
A packet NFO8 is sent out fram a terminal with the ICS user address "2710", and then is ICS-encapsulated at with a transmitting ICS network address "7600" and a receiving ICS network address "7824n then is transferred within the ICS and is reversely ICS-encapsulated to beccm a packet UFO8, and reaches the terminal with the ICS user address n2300" via the user logic canTamication line 17824-1. The 11pratocal type" of the packet UFO8 is UDP, and the "intended receiver's port number" thereof is "40", in this example.
A packet NFO9 is sent out fram a terminal with the ICS user address "2800", and then is ICS-encapsulated, at with a transmitting ICS network address "7700" and a receiving ICS network address "782C then is transferred within the ICS and is reversely ICS-encapsulated to became a packet UF09, and reaches the terminal with the ICS user address "2310n via the user logic communication line 17824-1. The n protocol type" of the packet UF09 is UDP, and the "intended receiver's port numbern thereof is "42", in this example.
142 3 A packet NFlO is sent out from a terminal with the ICS user address "2720", and then is ICS-encapsulated at with a transmitting ICS network address "7600" and a receiving ICS network address "78250 then is transferred within the ICS and is reversely ICS-encapsulated to became a packet W10, and reaches the terndnal with the ICS user address n2400" via the user logic comTunication line 17825-1. The "protocol type" of the packet UFlO is TCP, and the nintended receiver's port numbern thereof is "60", in this exmple.
A frame NF11 is sent out frcin a terminal with the ICS user address "2810", and then is ICS-encapsulated at with a transmitting ICS network address R770C and a receiving ICS network address n7825n, then is transferred within the ICS and is reversely ICS-encapsulated to became a packet UM, and reaches the terniinal with the ICS user address "2410" via the user logic communication line 17825-1. The "protocol typen of the packet UF11 is UDP, and the "intended receiver's port number" thereof is "70", in this example. <<Example 1 for determining the degree of priority> > The manner in which the degree of priority is determined will be described with reference to the flowchart in FIG.82. The access control apparatus 17100-1 receives the ICS network packets NFO1 and NF02 from the ICS network camninication line almost at the same time (Step S1000), and reversely ICS-encapsulates each to obtain ICS user packets UFO1 and W02(Step S1010). From the conversion table 17113-1 it can be known that the receiving ICS network address of the ICS logic terminal sending these ICS user packets is "7821n for both, i.e., p 143 that there is a match(Step S1020). The "de of priority of receptionn code for both ICS network packets NFO1 and NF02 is "pr7821", and then according to portion table of the conversion table 17113-1, the degree of priority of protocol for "pr-7821" is specified as being np-l", the degree of priority of TCP socket as "t-l", and the degree of priority of UDP socket as nNULLn. Further, looking at even other portion table ccinprising the conversion table 17113-1, the degree of priority of protocol "p-ln dictates that the degree of priority of is, in descending orclw, Tep, UDP, WPM and IGPM, and with regard to the degree of priority of TCP socket "t-l", the dictated order of degree of priority of is, in descending order, "sk-ln and "sk-7", and the contents of the socket code nsk-l" indicate that the IP address comprising the intended receiver's socket number is n210OR and that the intended receiver's port number thereof is "30g%. rThe protocol type indicated within the ICS network packet NFO1 is RTW", the intended receiver's ID address is "2100", and the intended receiver's port number is n3C. On the other hand, the protocol type indicated within the ICS network packet NF02 is "TCP", the intended receiverts ID address is n2110", and the intended receiver's port number is "3C. In the present embodinmt. it can be understood that it is the ICS network packet NFO1 that has the protocol type and intended receiver's socket number that matches with the of the aforementioned socket code "sk-l". Based m the speci. above procedures, it is determined that the ICS network packet to be sent out with higher priority is NFOl(Step S1030). Next, this ICS 144 network packet NFO1 is sent out to the user logic terminal via the ICS logic te=ninal (Step S1040). <<Ex&rple 2 for determining the degree of priority>> The access control apparatus 17100-1 receives the ICS network frames NF03, NF04 and NF05 frem the ICS network ccnTnmicatim line almost at the same time(Step S1000), and reversely ICS-encapsulates each to obtain ICS user packets UF03, NF04 and W05(Step S1010). Frarn the conversion table 17113- 1 it can be known that the receiving ICS network address of the ICS logic terminal sending these ICS user packets is "7822u for all, i.e., that there is a match (Step S1020). The Rdegree of priority of reception" code for all of the ICS network packets NF03, NF04 and NF05 is "pr-7822", the degree of priority of protocol thereof is specified as being nP-1", the degree of priority of TCP socket as "t-2", and the degree of priority of UDP socket as %ULL". The contents of the degree of priority of protocol np-l" dictates that TCP has the highest degree of priority, and with regard to the degree of priority of TCP socket "t-2n, "sk-2" has the highest degree of priority, and the contents of the socket code "sk-2" indicate that the IP address ccrnprising the sender's socket nunt)er is "2100n and that the sender's port nunter thereof is n3C. The protocol type indicated within the ICS network packet NF03 is "TCP", the sender's ID address is "1230", and the sender's port nanber is "30n. The protocol type indicated within the ICS network packet NF04 is RTepn, the sender's ID address is n1240n, and the sender's port nurt),--r is n32". Also, the protocol type indicated within the ICS network packet NF05 ls RTCP', the sender's ID address is n125C, and the sender's port number is "32". In the present embodiment, it can be understood that it is the ICS network packet NF04 that has the protocol type and the intended receiver's socket number that matches with the specifications of the aforementioned socket code "sk-2n. Based on the above procedures, lt is determined that the ICS network packet to be sent out with hi priority is NF04 (Step S1030). Next, this ICS network packet NF04 is sent out to the user logic terminal via the ICS logic terminal (Step S1040). <<Example 3 for determining the degree of priority>>
The access control apparatus 17100-1 receives the ICS network packets NF06 and NF07 fran the ICS network cenuunication line almost at the same time (Step S1000), and reversely ICS-encapsulates each to obtain ICS user packets UF06 and UF07 (Step S1010). From the conversion table 17113-1 it can be known that the receiving ICS network address of the ICS logicterminal sending these ICS user packets is "7823" for both, i.e., that there is a match (Step S1020). The "degree of priority of reception" code for both ICS network packets NF06 and NF07 is npr-7823n, and the degree of priority of protocol is specified as being "p-2", the degree of priority of TCP socket as nNULLn, and the degree of priority of UDP socket as "u-l". Further, looking at even other portion table =prising the conversion table 17113-1, the degree of priority of protocol np-2" dictates that the degree of priority is, in descending order, UDP, TCP, WPM and IGPM, and with regard to the degree of priority of UDP socket "ul", 146 the dictated order of degree of priority is, in descending order, "sk3" and "sk-8", and the contents of the socket code usk-3" indicate that the IP address cernprising the intended receiver's socket number is "2200n and that the intended receiver's port number thereof is 040The protocol type indicated within the ICS network packet NF06 is "UDPn, the intended receiver's ID address is "2200", and the intended receiver's port number is "40n. On the other hand, the protocol type indicated within the ICS network packet NF07 is nUDP", the intended receiver's ID address is "2110", and the intended receiver's port number is "40n. In the present embodiment, it can be understood that it is the ICS network packet NF06 that has the protocol type and the intended receiver's socket number that matches with the specifications of the aforementioned socket code "sk-3". Based on the above procedures, it is determined that the ICS network packet to be sent out with higher priority is NF06 (Step S1030). Next, this ICS network packet NF06 is sent out to the user logic temninal via the ICS logic terminal (Step S1040). <<Ele 4 for determining the degree of priority>>
The access control apparatus 17100-1 receives the ICS network packets NF08 and NF09 fram the ICS network =Tamication line almst at the same time (Step S1000), and reversely ICS-encapsulates each to obtain ICS user packets UF08 and UF09 (Step S1010). From the conversion table 17113-1 it can be knawn that the receiving ICS network address of the ICS logic terminal sending these ICS user packets is "782C for both, i.e., that there is a match (Step S1020).
147 The Rdegree of priority of reception" code for both ICS network packets NFO8 and NF09 ls "pr-7824n, and the degree of priority of protocol is specified as being "p-2", the degree of priority of TCP socket as %ULL", and the degree of Priority of UDP socket as "u-2" The degree of priority of protocol "p-2n dictates that socket code "sk-40 has the highest priority, and the contents of the socket signal "sk-C indicate that the IP address ccffprising the sender's socket number is "2710" and that the sender's port number thereof is "40n. The protocol type indicated within the ICS network packet NF08 is "UDPn, the sender's ID address is "2710n, and the sender's port number ls "40". On the other hand, the protocol type indicated within the ICS network packet NF09 is nUDP", the sender's ID address is "2800", and the sender's port number is n42n. In the present embodiment, it can be understood that it is the ICS network packet NF08 that has the protocol type and the sender's socket number that matches with the specifications of the aforunentioned socket code "sk-C. Based m the above procedures, it is determined that the ICS network packet to be sent out with higher priority is NF08 (Step S1030). Next, this ICS network packet NFO8 is sent out to the user logic terminal via the ICS logic terminal (Step S1040). <<Example 5 for detexndxLing the degree of priority>>
The access control apparatus 17100-1 receives the ICS network frames NFlO and NF11 fran the ICS network caniunication line almost at the same time (Step S1000), and reversely ICS-encapsulates: each to obtain ICS user packets UFlO and UF11 (Step S1010). From the 148 conversion table 17113-1 it can be known that the receiving ICS network address of the ICS logic terminal sending these ICS user packets is R7825" for both, i.e., that there is a match (Step S1020). The Rdegree of priority of reception" code for both ICS network packets NFlO and NF11 is npr-7825n, and the degree of priority of protocol is specified as being "p-l", the degree of priority of TCP socket as "t-3", and the degree of priority of UDP socket as nu-3u. The degree of priority of protocol "p-l" dictates that the degree of priority of TCP is higher than that of UDP. The protocol type indicated in the ICS network packet NFlO is "TCP", and the protocol type indicated in the ICS network packet NFlO is "UDP Based on the above procedures, it is determined that the ICS network packet to be sent out with higher priority is NFlO (Step S1030). Next, this ICS network packet NFlO is sent out to the user logic terminal via the ICS logic terminal (Step S1040).
Embodiment-14 (Control of transmitting priority degree):
Description will now be made regarding and effbodiment wherein user IP packets arriving from outside the ICS are ICS-encapsulated with the access control apparatus, and then the order of sending out onto the ICS network camunication line is decided. <<Configuration>>
As shown in FIG.83, an CS 17000-2 includes access control apparatuses 17100-2 through 17190-2, and the access control apparatus 17100-2 includes a line unit 17111-2, a processing device 17112-2 and 149 a conversion table 17113-2. Blocks 17240-2 through 17280-2 are corporate LANs which are each connected to the ICS 17000-2 via the ICS user logic cnication line. Bach of the LANs includes a plurality of IP terminals and blocks 17401-2 and 17411-2 are both IP terminals. <<Conversion table>> The functions of the conversion table 17113-2 shown in FIGs.84 and 85 are the same as those in the other embodiments, and the present invention is characterized in that the portion table, named "degree of priority of reception" code, degree of priority of protocol, degree of priority of TCP socket, and degree of priority of UDP socket, which are camponents of the conversion table 17113-2 are used for controlling the degree of priority. In the event that the transmitting ICS network address of the conversion table is "7821", the ntransmitting priority degree" code is stipulated to be nps-7821". That is, the Rreceiving priority degree" code is made to be a parameter which is dependent on the ICS network address provided to the ICS user logic terminal sent fran the access control apparatus after the ICS reverse encapsulation. Looking at the other portion table of the conversion table 17113-1, e.g., in regard to "ps- 7821", the degree of priority of protocol is described as being np-21", the degree of priority of TCP socket as Ot-21", and the degree of priority of UDP socket as 'SULW. The method of describing the degree of priority of protocol, the degree of priority of TCP socket, and the degree of priority of UDP socket, etc. is the same as that of Embodiment- 13.
<<Exarnple 1 for determining the degree of priority>> The manner in which the degree of priority is determined will be described with reference to the flowchart in FIG.86. The access control apparatus 17100-2 receives the ICS user packets F01 and F02 fran the ICS network cammication line almost at the same time, and obtains the ICS network address appropriated to the ICS logic terminal (Step S2700). Next, the procedures for control of transmitting priority degree are as follows. The "transmitting priority degreew code for both ICS user packets F01 and F02 is wps-78210, and then according to portion table of the conversion table 17113-2, the degree of priority of protocol for nps-7821" is specified as being "p-21", the degree of priority of TCP socket as "t-21", and the degree of priority of UDP socket as nNULL'. Further, looking at other portion table carprising the conversion table 17113-2, the degree of priority of protocol np-21n dictates that the degree of priority is, in descending order, TCP, UDP, WPM, and IGPM, and with regard to the degree of priority of TCP socket Ot-21n, the dictated order of degree of priority of is, in descending order, "sk-21" and Usk-27n, and the contents of the socket signal usk-21" indicate that the IP address c " rising the sender's socket number is 0210OR and that the sender's port number thereof is n30 The protocol type indicated within the ICS user packet F01 is nTCPn, the sender's ID address is "2100", and the sender's port number is R3C. On the other hand, the protocol type indicated within the ICS network packet F02 is "TCPn, the sender's ID address is "21100, and the sender's port number is n30n 151 In the present embodiment, it can be understood that it is the ICS network packet F01 that has the protocol type and the intended receiver's socket number that matches with the specifications of the aforementioned socket code "sk-21". Based on the above procedures, it is determined that the ICS user packet to be sent out with higher priority is F01 (Step S2710).
Next, the system checks whether or not the ICS network address "7721R provided to the logic terminal which received the ICS user packet F01 is registered on the conversion table 17113-2 with the request identification as virtual dedicated line connection n3" (Step S2720). The subsequent steps are the same as the steps S2730 through S2770 described with the other embodiments, and at the end ICS encapsulation is performed (Step S2780), and the ICS network packet NFO1 is sent into the ICS 17000- 2 with priority (Step S2790). << Another example for determining the degree of priority >> Regarding example 2 for determining the degree of priority wherein the access control apparatus 17100-2 receives the ICS user packets F03, F04 and F05 frcm the ICS logic terminal of the line portion 17111-2 provided with ICS network address "7822" almost at the same time; ele 3 for determining the degree of priority wherein the access control apparatus 17100-2 receives the ICS user packets F06 and F07 from the ICS logic terminal of the line portion 17111-2 provided with ICS network address R782Y' almost at the same tirre; example 4 for determining the degree of priority wherein the access control apparatus 17100-2 receives the ICS user packets F08 and F09 152 from the ICS logic terminal of the line portion 17111-2 provided with ICS network address "782C almost at the same time; and exarrple 5 for determining the degree of priority wherein the access control apparatus 17100-2 receives the ICS user packets F10 and F11 from the ICS logic terminal of the Line portion 17111-2 provided with ICS network address "7823" almost at the same time: the method for determining the degree of priority is the same as example 1 for determining the degree of priority, as shown in the portion table rising the conversion table 17113-2, and description thereof will be emitted.
Effbodiment-15 (Multiple connunication):
The description of the present embodiment will be made with reference to FIG.85 through FIG.87. An ICS 18000-1 includes access control apparatuses 18140-1, 18141-1, 18142-1, 18143-1 and 18144-1, a conversion table within the access control apparatus 18140-1 being 18195-1 and the conversion table within the access control apparatus 18141-1 being 18196-1. The conversion table 18195-1, as with the conversion table 6013-1. contains specified values "V', ff2#%, nY' and mC for request identification, and correspondingly, intra-corporation c=unication, inter-corporation cannunication, virtual dedicated line connection, and ICS network server connection can be made within a single access control apparatus. The conversion table 18196-1, contains only the specified value "3n for request identification, enabling virtual dedicated line connection. The ICS network server
153 18160-1 is connected to the access control apparatus 18140-1 via an ICS network conTmudeation line. A block 18184-1 is an FR network or an ATM network; in the event that 18184-1 is an FR network.
LANs 18110-1 and 18130-1 are each connected with access control apparatuses 18140-1 and 18142-1 via an ICS user logic cammication line. The gateways 18171-1 and 18172-1 are connected to the access control apparatus 18140-1 or 18141-1, via an ICS user logic cenTmxiicatim line. LAN 18120-1 includes a plurality of IP terminals, 18121-1, 18122-1 and 18123-1. Now, the term "IP terminal" refers to a ternunal which has the functions of sending and receiving IP user packets. The IP terminals 18150-1 and 18151-1 are each via access control apparatuses 18143-1, 18144-1, and an ICS user logic c=unication line. The ICS network ccffmmcation line 18191-1 connects the conversion unit 18181-1 with the access control apparatus 18141-1, and the ICS network cenTainication line 18192-1 connects the conversion unit 18182-1 with the access control apparatus 18141-2.
ICS user packet sent fran the LAN 18120-1 or LAN 18110-1 is, upon arrival to the access control apparatus 18140-1, ICS-encapsulated in order to receive one of the ceminication services of intracorporation canumnication, inter-corporation commication, virtual dedicated line connection, or ICS network server connection, following control of the request identification values "1", n2Y1, n3n or 914n listed in the conversion table 18195-1. Also, an ICS user packet sent frorn the gateway 18172-1, upon arrival to the access control apparatus 18140-1, is ICSencapsulated. in order to receive virtual dedicated 154 line cammnication service filling the control of the request identification "3" listed on the conversion table 18196-1, passes through the conversion unit 18181-1 via the ICS network =Trunication line 18191-1, further passes through the FR network or ATM network 18184-1, passes through the conversion unit 18182-1, passes through the ICS network ccmmmication line 18192-1, and is delivered to the access control apparatus 18142-1. For the FR network or ATM network 18184-1 here, fixed connection with the other party (PVC) which is a known art is used as the function of the FR network or ATM network. Thus, according to the above- described procedures, transfer of ICS user packets is realized. <<Partial change to above embodiment: variation>> Description will be made with reference to FIG.90. As with ICS 18000-1, ICS 18000-2 also include multiple access control apparatuses, and are connected with LANs and IP terminals through the access control apparatuses. The FR network or ATM network 18184-1 in FIG.87 is replaced with FR network or ATM network 18200-1; the access control apparatus 181411, the conversion unit 18181-1, and the ICS network ccmTo-mication line 18191-1 are replaced with PVC inter-face conversion unit 18210-2; the access control apparatus 18142-1, the conversion unit 18182-1, and the ICS network ccffnunication line 18192-1 are replaced with PVC interface conversion unit 18220-2; and further, the gateways 18171-1 and 18172-1 are replaced with a gateway 182302. Now, in the event that a block 18200-2 is an FR network, the PVC interface conversion units 18210- 2 and 18220-2 are functions for converting the
ICS user packet into the FR packet format, and reverseconverting thereof. In the event that 18200-2 is an ATM network, the PVC interface conversion units 18210-2 and 18220-2 are functions for converting the ICS user packet into the ATM frame format, and reverseconverting thereof. Transfer of ICS use packet according to this variation is realized by using the functions of f connection with the other party (PVC) by the FR network or ATM network.
Embodiment-16 (Operation of ICS):
Description will be made with reference to FIGs.91 and 92. The ICS 190001 includes: VAN 19010-1, VAN 19020-1, access control apparatuses 19300-1, 19310-1, 193201 and 19330-1, relay devices 19400-1, 19410-1, 19420-1 and 19430-1, inter-VAN gateway 19490-1, and server devices 19500-1, 19510-1, 19520-1, 19530-1 and 19540-1. Each server is provided with an ICS network address, and has a plurality of ICS network servers therein. These plurality of ICS network servers are distinguished by port numbers used with TCP ccrrrrii=cation protocol or UDP ccrmt=cation protocol. The access control apparatuses 19300-1, 19310-1, 19320-1 and 19330-1 each include conversion tables 19301-1, 19311-1, 19311-1 and 19311-1, each includes conversion table servers 19731-1, 19732-1, 19733-1 and 19734-1, and also includes dcmain name servers 19741-1, 19742-1, 19743-1 and 19744- 1, and also includes resource administration servers 19751-1, 19752-1, 19753-1 and 19754-1, the relay device 19400-1 includes a path information server 19761-1 and resource administration server 19755-1, the relay device 19410-1
156 includes a path information server 19762-1, the relay device 19420-1 includes a path information server 19763-1, the relay device 19430-1 includes a path information server 19764-1, the server device 19500-1 includes a user service server 19711-1 and ICS authority server 197211, the server device 19510-1 includes a governing resource administration server 19750-1 and gaveniing resource administration server 19760-1, the server device 19520-1 includes a user service server 19712-1 and ICS authority server 19722-1, the server device 19530-1 includes an ICS network server 19980-1 which has an ICS user address "1200" and perform electronic library services, and an ICS network server 19981-1 which has an ICS user address "1300" and performs travel information services, the server device 19540-1 includes a governing resource administration server 19720-1, gavexning darain name server 19740-1, governing conversion table server 19730-1, and goveming user service server 19710-1.
The abave-described access control apparatuses, relay device, server devices, and VAN gateways are connected by the ICS network ccmTunication lines 19040-1, 19041-1, 19042-1 and 19043-1, so as to be able to exchange information one with another using ICS network conTnanication functions. The server devices are formed by, e. g., giving the ICS network =nymnication function to a camputer, with program running therein for realizing server functions.
A block 19110-1 is an FR network, and the conversion units 19111-1 and 19112-1 are for performing interface conversion with the conT=n-lcatim lines of the FR exchange network and the ICS 157 commication lines transferring ICS network packets. Also, a block 19900-1 is an ATM network, and the conversion units 19901-1 and 199021 are for performing interface conversion with the cenvunication lines of the ATM exchange network and the ICS cmmmcation lines transferring ICS network packets.
In the entxxlit, connected outside of the IcS 190oO are LANS 19600-1, 19601-1, 19602-1, 19603-1, 19604-1 and 19605-1, and IP terminals 19606-1 and 19607-1 having functions for sending and receiving ICS network packets. <<Hierarchical structure of the ICS network server>> Description will be rmde with FIGs.93 through 98. The governing user server 19710-1 has superior controlling authority in instructing the user service servers 19711-1 and 19712-1 or requesting individual information reports, the meaning of superior controlling authorlty being illustrated in a tree-structure diagram in FIG.93. A block 19811-1 is a cenmmication path for information exchange between the governing user service server 19710-1 and the user service server 19711-1, and is ccoprised of ICS cenrnxiication lines and relay device, among others. The governing resource administration server 19720-1, the governing conversion table server 19730-1, the governing dcmain name server 19740-1, the governing resource administration server 19750-1, and the governing resource administration server 19760-1 are also the same, each being shown in FIGs. 94 through 98. Now, in the present effbodiment, there are two layers in the tree-structure hlerarchy, but this can be increased to three or more layers by
158 increasing the name of access control apparatuses, relay devices, servers devices, etc., places within the ICS. The path information service is provided with the functions of sending and receiving inside the ICS, a path table used by the relay devices and access control apparatuses. The resource administration server is provided with administration functions of keeping up on mounting information or obstruction information of the relay devices, access control apparatuses and server devices. <<Operation of ICS 19000-1 by ICS operator>> The ICS operators 19960-1 and 19961-1 provide instructions such as operation start-up to, or request reports of individual information frcrn, the governing user service server 19710-1, the governing conversion table server 19730-1, the governing resource administration server 19750- 1, and the governing resourre administration server 19760-1, thereby facilitating operation of the ICS 19000-1. <<Operation of ICS 19000-1 by ICS authority>> The ICS authority 19950-1 provides instructions such as the operation start-up to, or request reports of individual information from, the governing resource administration server 19720-1 and the governing domain name server 19740-1, thereby facilitating administration of addresses and the like used in the ICS 19000-1. <<Socket number and server>> The ICS servers each have ICS user addresses and ICS network addresses, but an addition to the other embodiments is that the above servers have, in addition to ICS network addresses, port numbers 159 stipulated by TCP or UDP communication protocol. That is, each of the aforementioned servers is identified by a 32-bit ICS network address and a 16-bit port number, waking for a value with a total of 48 bits (this being referred to as "socket number"). Each server includes programs which have peculiar functions operating within the ICS 190001, and further, there are servers among these which have noperating interface", as described later. Now, the "operating interface" is a function which performs exchange of information, and sends and receives instructions such as operation of the various server functions or start-up or operation, with the operator via a keyboard or the like. Each server provides access control apparatuses or relay devices, for example, with ICS network addresses, applies differing port numbers to the plurality of programs with-in these devices (i.e., servers), distinguishing by the socket number. As described in the embodiments, each server has ICS network czrmlunicatim functions, and can exchange information one with another using the ICS network address and the port numbers. <<Registration 1 to ICS of user: Inter- corporation communication and ICS network server>> Description will be made with reference to FIG.91, FIG.92 and FIG.99. An applicant 19200-1 to the ICS 19000-1 applies to the ICS receptionist 19940-1 for ICS membership (procedure P100). The. Application reception data" is a usage itern of ICS wherein the ICS user address, the ICS network address, and the ICS name has been deleted, and is coffprised of, e.g., request identification (classification of intra-corporation ccnTm-mication, inter-corporation ccuminication, virtual dedicated line connection, or ICS network server connection), ccnTmmication band conditions such as speed class and priority, billing conditions, open-zone connection conditions, payment method, name and address of user (personal ID data), signing conditions, encryption conditions and so on.
The ICS receptionist 19940-1 enters the above "application reception datan to the user service server 19711-1 via the "operating interface", and stores the napplication reception data" in the user database 19611-1 (procedure P110). Next, the user service se=jer 19711-1 requests of the ICS authority server 19721-1 the ICS user address, ICS network address and ICS name, using the ICS network CMMMiCatim functions (procedures P120). The ICS authority server 19721-1 appropriates the requested aforementioned ICS address and ICS name using the ICS network address appropriation record table 19622-1 (FIG.100) and the ICS user address appropriation record table 19623-1 (FIG.101) stored within the database 19621-1 (procedure P130), stores the appropriation results in the aforementioned appropriation tables, and further returns the appropriation results to the user service server 19711-1 (procedure P140). The user service server 19711-1 stores the appropriation results obtained fram the ICS authority server 19721-1 in the user database 19611- 1 (procedure P150).
FIG.100 is an example of the ICS network address appropriation record table 19622-1, and in the first line of this table there is an example which states beforehand that an ICS network address "7700" has 161 been appropriated to ICS logic teminal identifying code LT-001 of the node identifying code ACU-1, that the appropriate identifying code is user-1, that the date of appropriation is April 1, 1998, and that the node identifying code ACU-1 points to the access control apparatus 19300- 1. Also, in the third line of this table there is an example which states beforehand that an ICS network address "6930" has been appropriated to port number 620" of the node identifying code SW-1, that the appropriate identifying code is Sc-001, that the date of appropriation is February 1, 1998, and that the node identifying code SW-1 points to the server device 19530-1.
FIG.101 is an example of an ICS user address appropriation record table, and in the first line of this table there is an example which states that the ICS name address "461C has been appropriated with an ICS name (also called an ICS dcak-dn name) of "ddl.ocl.bbl.aal.jp", that the request identification value is "2", that the appropriate identifying code is user-1, and that the date of appropriation is April 1, 1998. Further, in the fourth line of this table there is an example which states that the ICS name address "1200" has been appropriated with an ICS name of "rrl.qq. pp.jp", that the request identification value is 'W', that the appropriate identifying code is Sv-001, and that the date of appropriation is February 1, 1998.
The user service server 19711-1 provides inforrnation to the conversion table server 19731-1 via the ICS network c=amication function so as to write the application contents of the usage 162 applicant 19200-1 and the obtained ICS network address into the conversion table 19301-1 in the access control apparatus 19300-1 (procedure P160). The contents to be provided are: transmitting ICS network address, sender ICS user address, request identification, speed class, priority, signing conditions, encryption conditions, open-zone class and so on. Also, in the event that the aforementioned ICS network address and ICS user address have a request value of "2", i.e., inter- corporation comumication, registration is made as transmitting ICS network address and sender ICS user address. In the event that the request value is "C, i.e., ICS network server, registration is made as receiving ICS network address and receiver ICS user address. The conversion table server 19731-1 adds the above contents to the conversion table 19301-1 (procedures P170). The receiving ICS network address and the receiver ICS user address are not registered in the conversion table 19301-1 at this time, but are registered in the conversion table 19301-1 at the time of nregistration of other party of cemmnication", later described in the present embodiment.
Next, the conversion table server 19731-1 notifies the ICS domain name server 19641-1 of the ICS network address, the ICS user address and the ICS name (procedure P180). The ICS domain name server 19641-1 writes the above received ICS network address, ICS user address and ICS name in the database therein and stores them (procedure P190), and reports completion of writing to the conversion table server 19731-1 (procedure P200). The conversion table server 163 19731-1 confirm this report (procedure P210), reports completion of the series of Procedures to the user service server 19711-1 (procedure P220), the user service server 19711-1 confirms this report (procedure_ P230), and informs the usage applicant of the appropriation results, namely, the ICS user address and ICS name (procedure P240). Incidentally, the ICS network address is used only within the ICS, so the usage applicant is not notified of this. In the event that the request value is "4n, i.e., ICS network server, the user service server 19711-1 notifies all conversion table servers within theICS 19000-1 at the time of the procedure P160, and requests registration to the conversion table of all access control apparatuses. <<Re-writing adffdnistration of conversion table by governing conversion table server>> Description will be made with reference to procedures 800 through 960 to the bottom of FIG.99 and FIG.91, FIG.92, FIG.95. The governing conversion table server 19730-1 instructs the conversion table server 19731-1 to rewrite the contents of the conversion table 19301-1, e.g., speed class priority, transmitting ICS network address, a part or all of other item in the conversion table (procedure P800), and the conversion table server 19731-1 changes the contents of the conversion table 19301-1 according to the instructions (procedure P810). Also, the domain name server 19741-1 is instructed to re-write the ICS network address and the Like (procedure P820), the domain narne server 19741-1 follows the instructions and updates the internal table (procedure P830), reports the results to the conversion table server
164 19731-1 (procedure P840), the conversion table server 19731-1 confirms (procedure P850), and reports to the governing conversion table server 19730-1 (procedure P860). Also, the governing conversion table server 19730-1 instructs the user service sexver 19711-1 to re-write the contents of the user database 19611-1, such as speed class, ICS network address, etc. (procedure P900), and the user service server 19711-1 follows the instructions and updates the contents of the user database 19611-1 (procedure P910). Also, the ICS network addresses, ICS user address, and ICS names which have become unnecessary to the ICS authority server 19721-1 are returned, or new requests are made (Procedure P920), the ICS authority server 19721-1 follows these instructions and updates the ICS network address appropriation record table 19622-1 and the ICS user address appropriation record table 19623-1 (procedure P930), reports the results thereof to the user service server 19711-1 (procedure P940), the user service server 19711-1 confirms the report (procedure P950), and reports to the governing conversion table server (procedure P960).
In the above description, an arrangement may be used wherein first, the governing conversion table server 19730-1 calls up the user service server 19711-1 and performs the aforementioned procedures P900 through P960, and then secondly calls up the conversion table server 19731-1 and perform the aforementioned procedures P800 through P860. With such an arrangement, the ICS operator 19960-1 instructing rewriting of the contents of the access control table to the governing conversion table server 19730-1 enables exchanging of the conversion, table within the access control apparatus and the address infon-ation related thereto with domain name servers and ICS authority servers which have administration, thexeby facilitating ease of re-writing management of the contents of a conversion table with consistency, i.e., ease of updating managenmt of all conversion tables within the access control apparatuses within the ICS 19000-1. <<Registration of other party of czmminication>> FIG.105 will be described. A usage applicant for the ICS 19000-1 applies for registration of other party of ccffnTinication to the ICS receptionist 19940-1 along with the darain narne of the other party of camunication (procedure P300). The ICS receptionist 19940-1 receives the domain name of the other party of conTnunication (procedure P310), and sends it to the conversion table server 19731-1 (procedure P320). The conversion table server 19731-1 exchanges information with the do name servers 19740-1, 19742-1, etc. (procedures P330 and P331), obtains the ICS network address and the ICS user address corresponding with the damin name of the other party of commnication regarding which there was inquiry, updates the contents of the conversion table 19301-1 (procedure P340), and reports the results (procedures P350 and P360). The updated results are shown to the conversion table 19301-2. The ICS network address obtained here is registered in a conversion table such as shown in FIG. 106 as a receiving ICS network address. and the ICS user address obtained here is registered as a receiver ICS user address. Incidentally, in the case of an ICS network server, the spaces for the ICS network address and the ICS user address reni&m 166 blank. <<Registration 2 to ICS of user: Intra-corporation communication and virtual dedicated line>> Description will be made with reference to FIG. 107. The difference with intra-corporation camynication as con to the above inter-corporation camunication is that an ICS user address is handed in and an ICS name cannot be used, accordmgly, there is no appropriation of the ICS names, and there are no procedures for using ICS names (procedures P180, P190 and P200). First, an applicant 19200-1 to the ICS 19000-1 applies to the ICS receptionist 19940-1 for ICS membership (procedure P400). The "Application reception data" is a usage item of ICS wherein the ICS network address and the ICS name has been deleted, and is comprised of, e. g., ICS user address, request identification (classification of intra- corporation communication, inter-corporation communication, virtual dedicated line connection, or ICS network server connection), speed class and priority, etc., the sarre as with the previous inter-corporation communication. The ICS user address further shows a plurality of pairs for both sender ICS user address and receiver ICS user address. Also, in the case of a virtual dedicated line connection, the sender ICS user address and the receiver ICS user address are not shown; this is what is different as compared to the intra-corporation communication.
The ICS applicant 19940-1 enters the above "application reception data" to the user service server 19711-1 via the "operating interface", and stores the "application reception data" in the user database 19611-1 (procedure P410). Next, the user service server 19711-1 requests of the ICS authority server 197231-1 the ICS user address, the ICS network address and the ICS name, using the ICS network c=unication function (procedures P420). The ICS authority server 19721-1 appropriates only the ICS network address as with the abave procedure P130 (procedure P430), records the appropriation results in the aforementioned appropriation tables, and further returns the appropriation results to the user service server 19711-1 (procedure P440). The user service server 19711-1 stores the appropriation results obtained fran the ICS authority server 19721-1 in the user database 19611-1 (procedure P450).
The user service server 19711-1 notifies the conversion table server 19731-1 of the application contents and the obtained ICS network address (procedure P460), the conversion table server 19731-1 adds the above contents to the conversion table 19301-1 (procedure P370), and reports letion of registration (procedures P480 and P495). FIG.108 shaws and example of registration to the conversion table 19301 of the intracorporation cmainication and the virtual dedicated line. <<Description of demain name server>>
An example of 4-layer hierarchy will be described with reference to FIG. 109 and FIGs.110 to 112, regarding the procedures P330 and P331 regarding the demain name server in the description of FIG.105. The ICS network address of the internal table 19600-1 of the danain narne server which is the object of the daT= narne "root" is "9500n, and m.. m 168 d(:uk-Li-n names rvalwy, 59a21@, RaY' and so forth exist below, indicating, e.g., that the ICS network address of the domain name server which handles the domain name "al" is R96lon, and the port number is "440ry The ICS network address of the internal table 19610-1 of the domain name server which is the object of the domain name "aln is "96lon, and domain names "blu, "b2", "b3" and so forth exist below, indicating, e. g., that the ICS network address of the domain name server which handles the demain name "b2" is "9720", and the port number is "440n The ICS network address of the internal table 19620-1 of the domain name server which is the object of the demain name "bln is "9720". and domain names "c4n, 91c5", "cC and so forth exist below, indicating, e.g., that the terminal space for the domain name nc5" is YES, weaning that there are no more demain names below, and that in this exarrple, the ICS network address of the ICS name "c5.b2.al." is n9720", and that the ICS user address is n451On. Also, the record of the internal table 19620-1 of the damain name server. i.e., the ICS name (ICS domain name), the ICS network address and the ICS user address "4610n are considered to be one group of data and referred to particularly as a nresource recordn of the dcmain name server. <<Calling damain name servers>> With reference to FIG.113, description will be made regarding the procedures in which the conversion table server 19630-1 calls the damain name servers 19640-1, 19650-1 and 19660-1, and searches for the ICS network address and the ICS user address corresponding with the dcma:Ln name "c5.b2.al. ". The conversion table server 19630-1 enters
169 the daTain name "c5.b2.al.n in the resolver 19635-1 in the conversion table. The resolver 19635-1 sends the ICS packet 196411 including Wall' to the ICS dmiain nc-ue server 19640-1, and an ICS packet 19642-1 including an ICS network address n961OR of the ICS darain name server for Waln is returned. Next, The resolver 19635-1 sends an ICS packet 19651-1 including "b2u to the ICS dcmain name server 19650-1, and an ICS packet 19652-1 including an ICS network address n972C of the ICS darain name server for "b2" is returned.
Next, the resolver 19635-1 sends an ICS packet 19661-1 including n c5" to the ICS do name server 19660-1, and an ICS packet 19662-1 including an ICS network address R982W for nc5" and an ICS user address "4520" is returned. According to the above procedures, the conversion table server 19630-1 obtains an ICS network address 0982C and an ICS user address R452C corresponding with the demain nam Hc5.W.al.". <<Re-writing of conversion table from an IP terminal>> Description will be made with reference to FIGs.114 and 115. An ICS user packet including the domain nam "c5.b2.al." is sent from the IP terminal 19608-1 to the conversion table server 19731-1 (procedure P500). The conversion table server 19731-1 makes inquiry to the do name server (procedure P510), the dcmain name server searches and obtains the ICS network address "9820" and the ICS user address "4520" corresponding with the daTain name "c5.b2.al." (procedure P520), and returns this to the conversion table server 19731-1 (procedure P530), the conversion table server writes this to the conversion table
19301-1 (procedure P540), and reports to the IP terminal 19608-1 (procedure P550). In these procedures, the ICS network address R982C is written into the conversion table as a receiving network address, and the ICS user address "452C as a receiver ICS user address, the re-written conversion table being shown in FIG.103. Incidentally, FIG.103 cmits the items listed in the conversion table corresponding with the request identification included in FIG.102.
Next, the IP terminal 19608-1 sends an ICS user packet to the conversion table server 19731-1, including specification for changing the speed class to n2", with regard to the registered contents of the conversion table 19301-1X (procedure P600). The conversion table server 19731-1 re- writes the registration contents of the conversion table 19301-1X so that the speed class is "2u, according to the specification (procedure P610), and reports to the IP terminal 19608-1 (procedure P620). The conversion table re-written by these procedures is shown as 19301-Y (FIG.104). <<Moving a terminal between access control apparatuses>>
As can be seen from the entxxlurbent of the ICS user address appropriation record table 19623-1, the first line of this table appropriates ICS nam "ddl.ccl.bbl.aal.jp" to the ICS user address R4610n, and holds the ICS user address and the ICS name. For example, in the event that a terminal 19608-1 (FIG.91) having an ICS user address R461C is moved from the access control apparatus 19300-1 to the access control apparatus 19320-1 (FIG.92), and in the event that this terminal is appropriated a new ICS network address "7821w for 171 example, the conversion table has registered therein a transmitting ICS network address u7821" and a sender ICS user address "46101' as a paix. In this case, the ICS name "ddl.ccl.bbl.aal.jp" is paired with the ICS user address "4610n as stipulated by the ICS user address appropriation record table 19623-1, and the ICS name is not changed. The resource record camprised of the ICS name "ddl.ccl.bbl.aal.jp" within the dc name server. the ICS network address "7700", and the ICS user address "4610", is changed to that having the ICS name "ddl.ccl.bbl.aal.jp", the ICS network address "7821n and the ICS user address "4610". That is, the ICS network address "7700" is re-written to another address "7821", but the ICS name "ddl.ccl.bbl.aal.jpu and the ICS user address "4610" are not re- wr-itten. Sunirerizing this, the resource record of the dcwam narae server and ICS user address appropriation record table of the ICS authority server hold the ICS user address and the ICS name, and there is no case in which only one is changed. Accordingly, in the event that a terminal is n-oved between access control apparatuses, there is no need to change the ICS user address and ICS name of the terminal. (Other embodiment: determination of ICS user address by the user) This is an arrangerent wherein the abave enbodiment has been changed so that the user determines the ICS user address. That is, when the user (usage applicant 19200-1) applies to the ICS 19000-1, an ICS user address is added. The ICS receptionist 19940-1 includes the ICS user address in the application reception data. Also. the ICS authority server 19711-1 stores the ICS user address that the user has 172 applied for in the ICS user address appropriation record table 19623-1. According to the above method, the user can determine his/her own ICS user address, thus increasing freedom of usage.
Embodiment-17 (calling other party of canrunication by telephone nunber):
The present embodiment shows an example wherein using the telephone number as the ICS domain name allows sending and receiving of ICS user IP packet with the other party of c=lunication, in which digitized voice is stored within the user IP packet, thereby facilitating public communication using a telephone. In the present entx)diment, description will be made with reference to the example wherein the telephone number 81-3-1234-5678 in Tokyo, Japan, is viewed as being domain name I'5678.34. 12.3.8l." Here, "3" indicates Tokyo, and "W' indicates Japan.
Description will be made with reference to FIG.116. An ICS 20000-1 includes access control apparatuses 20010-1, 20020-1 and 20030-1, relay devices 20080-1 and 20090-1, domain name servers 201101, 20120-1, 20130-1, 20140-1 and 20150-1, and the access control apparatus 20010-1 includes line portion 20011-1, a processing device 20012-1, a conversion table 20013-1 and a conversion table server 20040-1. The conversion table server 20040-1 is within the access control apparatus 20010-1, and an ICS network address of "7800" and port number of "600n are appropriated. The conversion table server 20040-1 is provided with an ICS user address "4600" from outside of
173 the ICS 20000-1, and appears to be an ICS server having the functions of converting an entered danain name into an ICS user address and returning, and also registering the ICS network address in the conversion table 200131 within the access control apparatus 20010-1.
A block 20210-1 is a LAN, blocks 20211-1 and 20300-1 are both IP terminals having the functions of sending and receiving ICS user frames, each having ICS user addresses "4520" and "1200n, and are connected to the ICS 20000-1 via the ICS user logic conTminication line. IP texniinal 20300-1 can be used as a telephone and thus is referred to as an "IP telephonen. The IP telephone 20300-1 includes a telephone nu input unit 20310-1, IP address accumulating unit 20320-1, voice data sending/receiving unit 20330-1, input buttons 20340-1, and voice inputloutput unit 20350-1. <<Obtaining ICS user address by telephone nurber>> The telephone nurber "1234-5678" Is entered into the telephone nmber input unit 20310-1 by the input buttons 20340-1. The telephone narber input unit 20310-1 generates the ICS user packet P1201, and delivers this to the access control apparatus 20010-1 via the ICS user logic cenTminication line. Here, the ICS user packet is the sender ICS user address "120C and the receiver ICS user address "4600n, and the telephone nuTber "1234-5678" entered by the input buttons 20340-1 is included in the data. The processing device 20010-1 looks at the conversion table 20013-1, and sends the ICS user packet P1201 to the conversion table server 20040-1 indicated by the ICS user address "4600". Also, in the present embodiment, the conversion table server 174 20040-1 is within the access control apparatus 20010-1, so there is no need to user ICS network camirdcation functions. Based m the telephone narber "1234-5678" included in the data field of the ICS user packet, the conversion table server 20040-1 sequentially contacts denkiin name servers 20130-1, 20140-1 and 20150-1, and obtains the ICS network address "792C and the ICS user address "452C of the terminal 20211-1 of the other party of communication in the event that the telephone number R1234-567C is viewed as a demain narrke-
Next, the conversion table server 20040-1 creates a conversion table new item 20030-1 using the two addresses "79200 and "4520" obtained here, generates an ICS user packet P1202 for the ICS user address "4520n and writes the ICS user address "4520R therein and sends it to the IP telephone 20300-1. The IP telephone 20300-1 cernbines the ICS user address n4520" contained in the received ICS user packet P1202 with the telephone nuTiber "1234-5678" regarding which inquiry has already been made, and stores these in the IP address storage unit 20320-1, and uses it at a later day at the point that the ICS user address "452C corresponding with the telephone number "1234-5678" beccrrp-s necessary. The aforewmtioned conversion table new item 20030-1 correlates the IP telephone 20300-1 having the ICS network address "7820" and the ICS user address "120W' with the destination terminal 20211-1 specified by the telephone nariber "1234567C. The conversion table new item 20030-1 is used as a new cmWnent of the corivexsim table 20013-1. <<Ccffmmication using ICS user address>> Voice is inputted fram the voice irput/OutPut unit 20350-1, the voice is converted into digital data at the voice data sending/receiving unit 20330-1, stored in the ICS user packet P1210, and sent to the destination specified by the telephone nurber "12345678n, i.e., to the terminal 202111 determined by the ICS user address "4520". After this, telephone ccrmxuiication is perfo by sending and receiving ICS user packet between the two terminals 202111 and 20211-1. <<Detailed description of dank-dn name server>>
Regarding the above description, the method of the conversion table server presenting the telephone nu "1234-5678" to the dmkiin name server and obtaining the ICS network address "7920" and the ICS user address n4520w will be described in detail.
FIG.116 is diagram illustrating an embodiment of a 6-layer hierarchy ndcnuin name treen, with root domain name "root-tel" being provided on Level 1 of the tree, dcnk-dn names uln - "44'... n81n... "90" - existing on Level 2 which Is lower on the tree, and dcmain names - "391... R615... for example existing on Level 3 beneath domain name nW, and demain nams... "ll", n12P, 0131%7... for example existing on Level 4 beneath dcwain name 03", and further dcmain narnes... R#33n, R34n, R35",... for exarrple existing on Level 5 beneath dcmain narre "12n, and darain names - "5677w, n5678", R567C existing on Level 6 beneath demain name "3C.
FIG.119 illustrates the internal table 20131-1 of the damain name server 20130-1 handling the damain name "Y, and indicates that, 176 e.g., under domain name "Y' the domain sexver 20140-1 which handles domain name "12" has an ICS network address of "8720" and a port number of "440". FIG.120 illustrates the internal table 20141-1 of the domain name server 20140-1 handling the domain name "12", and indicates that, e. g., under domain name "12n the domain server 20150-1 which handles domain name "3C has an ICS network address of "882C and a port number of "440". Also, FIG.121 illustrates the internal table 20151-1 of the domain name server 20150-1 handling the domain name "12", and indicates that the endpoint for the domain name "5678n in the internal table 20151-1 is YES, meaning that there are no more domain names below, and in this example, the ICS network address corresponding to the domain name "5678.34.12.3.18. n is "8920n, and the ICS user address thereof is "4520". <<Calling domain name server>> With reference to FIG.122, description will be made of the procedures for the conversion table server 20040-1 calling the do name servers 20130-1, 20140-1 and 20150-1, and searching for the ICS network address and the ICS user address corresponding with the do name "5678.34.12.3.8l.". Now, the resolver 20041-1 has therein the ICS network address of a domain name server handling the Level 1 domain "root-teln shown in FIG.119. Also, in the event that there is a great deal of comm=cation with the domain name server which handle the Level 2 and Level 3 domains, the ICS network addresses of the upper domain name servers thereof are stored in the resolver 20041-1.
The conversion table server 20040-1 inputs domain name 177 "5678.34.12." into the internal resolver 20041-1. The resolver 200411 has the ICS network address "861C of the server handling the dcmain nam "3.8l. " which indicates "81" for Japan and "3" for Tokyo, and sends an ICS packet 20135-1:Including the damain name "120 which is under the daTain name nY' to the ICS dcmain name server 20130-1 using the ICS network camiunication function, in response to which an Ics frame 20136-1 including the ICS network address "8720n of the ICS damain name server 20140-1 which handles the damain name 1'12" is returned. Next, the resolver 20041-1 sends an ICS packet 20145-1 including the dcmain name "W' to the ICS darain name server 20140-1, in response to which an ICS packet 20146-1 including the ICS network address n882W' of the ICS danain name server 20146-1 which handles the darain name "3C is returned.
Next, the resolver 20041-1 sends an ICS packet 20155-1 including the dc name "5678" to the ICS dc name server 20150-1, in response to which an ICS packet 20156-1 including the ICS network address "7920" and "ICS user address 452C of the ICS damain name server 20156-1 corresponding with the damain name "567C is returned. According to the above procedures, the converslon table 20040-1 obtains the ICS network address "792C and the ICS user address n4520n corresponding to the darain nane "5678.34.12.3.8l. ". << Telephone line connection >> There is a telephone line conversion unit 20510-1 within the line portion 200011-1, and the telephone 20520-1 is connected to the telephone Iine conversion unit 20510-1 via the telephone line 20530-1.
178 The telephone line conversion unit 20510-1 has the same function as those described in the other embodwrents, and generates an ICS user packet sorted in the data field, as will as converting voice sent fran the telephone line 20530-1 into digitized voice. Also, ICS user packet which is sent in reverse, i.e., frem the ICS network to pass through the access control line portion, have the digitized voice stored therein converted into analog voice in the telephone line conversion unit 20510-1, or in the event of an ISDN line, converted into digitized voice. According to such an arrangement, the IP terminal 20300-1 provided with an ICS demain name and the telephone 20520-1 can perform ccnTaLmication by telephone voice. (Connecting to a public telephone network)
Further, the telephone line conversion unit 20510-1 and the private exchange 20600-1 are connected by a telephone line 20530-2. Telephones 20520-2 and 20520-3 are connected with a private telephone line 20540-1 extending frctn the private exchange 20600-1, and a telephone cemmunication can be carried out between the telephone 20520-2 and the telephone 20300-1. Also, connection can be made via the private exchange 20600-1 to public telephone networks/ international telephone network 20680-1. Such an arrangement enables the telephone ccmmunication between the telephones 20520-4 and 20300-1.
* Embodiment-18 (IP terminal capable of connecting to plural access control apparatuses):
The present embodiment does not fix the IP terminal having the 179 functions for sending and receiving ICS user IP packets to a specific access control apparatus; rather, it realizes an IP terminal which can be rwved and connected to other access control apparatuses and used, i.e., capable of roaming. Roaming is realized based on the ICS demain name provided to the IP terminal. <<Password transmission technique using cipher>> The present embodiment includes procedures for ciphering a secret password PW and sending it from the sender (encoding (ciphering) side) to the receiver (decoding side). First, a ciphering function E1 and a decoding function Di will be described. The ciphering function Ei is represented by y Ei(kl, x), and the decoding function Di is represented by x Di(k2, y). Here, "y" denotes the ciphertext, x" denotes plain-text, "klw and "k20 are keys, and "i" represents cipher nuTbers (i = 1, 2, --)determining the secret key code and the public key code, including haw the value of the cipher key is to be used. In the above, an arrangement may be used wherein plain-text x' is ciphered instead of plain-text x with x' = X ii r (wherein "r" is a randam number), and discarding the random number r fram the plain-text x' upon decoding, thus obtaining the plain-text x. Such an arrangement generates a different ciphertext each time the same plain-text is ciphered, owing to the random number, and it is said that such is less susceptible to code cracking. (Ele of cipher nu i <<Preparation>> The sender m discloses the damain name thereof (DUn) to the public including the receiver. The receiver calculates Km = Hash-1 (DNm) using the secret data campression function Hash-1, and hands aver only the cipher key Km using a safe method so as to be unnoticed by a third party. This example is an example of using DES ciphering, and the sender holds an nciphering module DES-e" for realizing the ciphering function Ei, and a cipher key Km. The cipher key Km is a secret value which the sender and receiver share. The receiver has the "decoding module DES-& for realizing the decoding function Di, and the data ccrrpression function Hash-1. What is used for the data compression function Hash-1 is determined separately for each cipher number. A data compression function is also referred to as a "hash functionn. <<Ciphering by sender>> The sender sets the secret password PW as x = PW, and ciphers as y - DES- eWm, x) with the ciphering module DES-e and the cipher key Km being held, thereby sending the ciphertext y and daTain name DNm. <<Decoding by receiver>> The receiver receives the ciphertext y and the denain name DUn, calculates the secret cipher key Km as Km = Hash-l(DNm) using the receiver's secret data ccinpression function Hash-1, and the obtains the plaintext x as x = DES-d(Km, y) using the decoding module. The plain-text x is password PW, and the receiver can obtain the secret password PW. A third party does not know the data ression function Hash-1 and thus cannot calculate the cipher key Km, and accordingly, cannot calculate the secret password PW. In the above 181 embodiment, as stipulation of the cipher number i =3, the ciphering functions and the decoding functions can be replaced with ciphering functions and decoding functions other than DES code. (Rle of cipher nunber i = 2) <<Preparation>> The present example is an example of employing RSA encoding, wherein the sender generatesciphering function y = -e mod n and decoding function y = xd mod n. Here, e #-- d holds, the key d being a secret value. The sender hands to the receiver the disclosable ciphering keys e and n, and ciphering ne RSA-e for realizing y 'emod n. The sender holds the ciphering keys and the ciphering module RSA-e. The sender does holds neither the secret ciphering module nor secret data. On the other hand, the receiver holds n and the secret key d, and the ciphering module RSA-e for realIzing y =)e mod n. <<Ciphering by sender>> The sender encodes the secret password PW, awn domain name DNm, and time of sending (year/month/day/hour/minute/second) as x = PW 11 xl 11 x2 (wherein xl: domain name DNim, and x2: year/month/day/hour/ minute/second) and ciphers as y = ie mod n using the ciphering module RSA- e, thus sending the ciphertext y. <<Decoding by receiver>> The receiver receives the ciphertext y and calculates x = yd mod n using the decoding ne RSA-d held beforehand and the dwg key. The result is x = W 11 xl, 11 x2, so the data which is at a certain position fram the head of x is used as the password PW. In the above 182 ciphering, daram name xl. and ye-ar/month/day/hour/minute/second x2 are used as randcm numbers. A third par-ty does not know the secret key d and thus cannot calculate the secret password Pw. In the above ffnbOdt, as stipulations Of the cipher number i = 4, the values of the cipher keys e, d and n can be changed. Also, as stipulations of the cipher number i = 5, the RSA ciphering technique can be replaced with a different public key ciphering teque. <<Terminal verification technique using password and randam. number>> Description will be made regarding verification technique for determining whether Or not the password PW used by a roaming terminal agrees with the password registered in the verifying server. As prerequisite conditions, the verifying server of the verifying entity and the terminal of the user to receive verification have a password PW that ls secret to a third party, with a ciphering function E (wherein y = E(k, x), y represents ciphertext, k represents ciphering key, and x represents plain-text). Specific procedures for te=rdnal verification will now be described. The terminal of the user to receive verification decides upon a randam number R using appropriate means, calculates Yl = F(PW, R) using the password PW and function y F(M R) and sends both the randam number R and the function Yl to the verifying entity. The verifying entity receives the randam number R and the function Y1, and calculates Y2 = F(FW, R) using the received randcm number R, the password PW held within. and the function F, and checks whether or not Yl = Y2 holds. In the event that there is a match, verification can be made that the owner of the terminal which is being verified is using the correct password PW, i.e., verification of the tenninal can be made. In the abave technique, an arrangenmt in which the user to be verified cannot freely select the random n=ter R but rather the randam nuffber R is restricted to depending on tirm (called a tim randam number) further increases difficulty of a third party calculating the password. Instead of the ciphering function used above, the secret data cempression function Hj niay be used instead, for Y1, Y2 = (PW, R). <<Overa-11 configuration>> FIGs.123 and 124 illustrate an overview of the roaming technique according to the present effbodiment, wherein the ICS 21000-1 includes access control apparatuses 21010-1, 21020-1, 21030-1, 21040-1, 21050-1 and 21060-1, relay devices 21080-1, 21080-2 and 21080-3, verifying servers 21100-1, 21101-1, 21102-1 and 21103-1, d^in name servers 21130-1, 21131-1, 21132-1 and 21133-1, a user service server 21250-1 and an ICS authority server 21260-1. The access control apparatus 21010-1 is provided with a conversion table 21013-1, a conversion table server 21016- 1, a registration server 21017-1 and a connection server 21018-1. The access control apparatus 21020-1 is provided with a conversion table 21023-1, a conversion table server 21026-1, a registration server 21027-1 and a connection server 21028-1. The connection servers 21018-1 and 21028- 1 are provided with an ICS user address "6310", and has the function to register access control apparatuses deterrrdned as necessary to the IP terminal, or to connect thereto.
184 The conversion table server 21016-1 has a function for rewriting the contents of the conversion table 21013-1, and the conversion table server 21026-1 has a function for re-writing the contents of the conversion table 21023-1. Also, the LAN 21150-1 has an IP terminal 21151-1, the LAN 21160-1 has an IP terminal 21161-1, and a block 21171-1 is an IP terminal. A block 21200-1 is a portable roaming terminal, and is identified by ICS dcmain name "cl.bl.al." provided uniquely within the ICS 21000-1. <<Application for use of roaming terminal>> The er of a roaming terminal 21200-1 indicates as an ICS usage applicant 21270-1 a payment method for the roaming terminal 21200-1, and applies to the ICS authority server 21260-1 via user service server 21250-1 for an ICS demain name and an ICS user address. The payment method represented by billing class "MNY", e.g., in the event that MNY = 1, the charges are billed to the hame IP (i.e., an IP terminal which is connected to the access control apparatus in a fixed manner), in the event that MNY = 2, the charges are paid according to the record of the verifying server. The ICS authority server 21260-1 sets an ICS daTain name "cl.bl.al." for using the roaming terminal 21200-1, and an ICS user address n1200". Further, in order to be connected to the access control apparatus 21010-1 in a fixed manner and use it, the awner of the IP terminal 21200-1 applies for an ICS network address to the ICS authority server 21260-1 via the user service server 21250-1. The user service server 21250-1, upon obtaining the ICS network address, makes a request to the conversion table server 21016-1 to set the ICS network address "8115" and the ICS user address "1200" in the conversion table 21013-1.
The ICS receptionist 21271-1 embeds inside the interior 21201-1 of the roaming terminal 21200-1 the following: ICS demain name Ocl.bl.al.", ICS user address "1200", special ICS address for roaming terminals (called "roaming special number") '100C, ICS user address "6300" for registration server, and ICS user address "6310" for connecting server, and further embeds inside the interior 21202-1 of the roaming terminal 21200-1 the ciphering function Ei and decoding related data RP1. Now, RP1 = Hj (demain name 11 RPO) 11 RPO (wherein RPO NKY 11 i R j) holds, and the domain name is "cl.bl. al.". MNY is the abave-described billing class, "i" is a cipher number for typifying the cipher Ei, and "j" determines the type of Hash function Hj. Data carpression function Hj is a secret dedicated function used only by the verifying server and the user service server. The user does not hold the data cmpression function Hj, and does not even know Hj, and thus is incapable of generating code related data RP1. <<Registration procedure frcm home IP texminal>> Description will be made with reference to FIG.127. The roaming terminal user connects the roaming texminal 21200-1 to the position of the hcme IP terminal 21151-1. Next, the rDg temninal user decides m a password (PW) and enters this frern the input unit 21204-1, and also generates an ICS user packet PKO1 using the ciphering function and the coding-related data stored within the inner portion 21202-1, and sends it to the access control apparatus 21010-1 via the ICS user
186 logic camiunication line 21152-1 (procedures T10). The destination of the ICS user packet M01 is "6300" which points to the roaming registration server, and includes own ICS domain name "cl.bl.al.", cipher parameter PR1, ICS user address "1200", expiration data "98-1231", ciphertext "y" which is the password that has been ciphered, ntgu (wherein tg = 1 in order to display registration procedures), and "Yes" or nNo" for roaming connection specification. The generation method employed for the ciphertext "y" is the coding technique described earlier. For example, in the event that the cipher number 2, ciphertext "y" is generated with y =. e mod n (wherein x = PW 11 cl.bl.al. llyear/rnonth/day/hour/niinute/second). The access control apparatus 21010-1 looks at the conversion table 21013-1 and transfers the ICS user packet PKO1 to the registration server 21017-1 with the destination "6300" (procedure T15). The registration server 21017-1 uses the demain name "cl.bl.al." to call the verifying server 21100-1 (procedure T20). Also, the method by which the registration server 21017-1 calls the verifying server 21100-1 using the dmk-iin name is the same as the method by which the connection server 21028-1 calls the verifying server 21100-1 using the damain name, the details thereof being described in detail later. The verifying server 21100-1 checks the contents of the received ICS user packet W01, and decodes the ciphertext "yu using the earlier- described technique, thereby calculating the password PW. For exarrple, in the event that the cipher number = 2, the ciphertext "y" is decoded with x = yd mod n. This yields x = PWIlcl.bl.al. llyear/rwnth/day/hourlrninute/second, so the password PW can be obtained.
Next, the contents of the cipher parameter PP1 is RP1 = Hj (dcnk-dn name 11 RPO) 11 RPO (wherein RPO = MNY li i 11 j), so the verifying server 21100-1 uses the secret Hash function Hj held within the verifying server 21100-1 and the obtained darain name ncl.bl.al.n to calculate t = Hj (danain name 11 RPO) 11 RPO), and ch whether or not t = RP1 holds for the received RP1. If it holds, judgment is passed that the damain name "cl.bl. al.", the billing class MW, and the cipher numbers nin and "j" have not been tampered with. The verifying server 21100-1 checks for excessive or insufficient registration contents, and in the event that the contents are normal, the registration results are registered in the verification table 21100-2; registration is not made in the event there are insufficient registration contents.
This is illustrated in the verifying table 21100-2 in the line with the administration number 1, with the damain name as "cl.bl.al." cipher number "2", billing class (MNY) "1", value of calculated password PW "22469111, expiration date "98-1231n, roaming connection of "Yes", i.e., acceptance of a roaming connection. At the time of generating the PKO1 in procedure T10, the aforementioned value of tg may be set to tg = 2 and roaming connection set to nNon. The password will not leak to a third party, due to application of the abovedescribed ciphering method. Roaming registration is reported by passing through the registration server 210171 (procedure T30), then the access control apparatus 21010-1 (procedure T35), and reported to 188 the roaming jp terminal (procedure T40). Further, an ICS user packet for changing the value of the password PW with tg = 3 or changing the date of expiration with tg = 4 can be sent from the terminal 21200-1 via the ICS user logic comnnication line 21152-1, after the above procedure T40 has been completed. Incidentally, a rmthod which can be employed for changing the password involves specifying the prior password. <<Sending and receiving user IP packet while traveling>> An example will be described regarding connecting a roaming terminal 21200-1 to the access control apparatus 21020-1 and sending and receiving of user IP packet between domain name "cl.bl.al." of the roaming terminal 21200-1 and the other party of conrunication with a domain name "c2.b2.a2. ". The user inputs the following from the input unit 21204-1: the domain name "c2.b2.a2.w of other party of communication, "tg" which has been set to tg = 5 for specifying sending and receiving of user IP packet, own password PW, and "5" which specifies the roaming connection period in days (represented by TTL). The inside 21201-1 and 21202-1 of the roaming terminal 21200-1 is used to this end. Also, the IP frame field 21203-1 is used for generating, and sending and receiving ICS user IP packets W01, PK02, PK03, PK04 and so forth.
Next, the roaming terminal 21200-1 generates a user IP packet PK02, and sends it to the access control apparatus 21020-1 via the ICS user logic cunication line 21210-1 (procedure T50). The user IP packet PK02 includes the sender domain name "cl.bl.al.", receiver daTein name " c2. W. a2. ", cipher parameter RP2 and connection period (represented by TTL). The cipher parameter RP2 is data calculated with the password PW and the inside 21202-2. That is, year/month/dayl second "yy-randd-sssss" is generated and used as a time random number TR (TR = yy-rrm-dd-sssss), and the clock of inside 21202-2 and the cipher function Ei is used to calculate RP2 = Ei(PW, TR) UTR.
The access control apparatus 21020-1 receives the user IP packet M02, obtains the ICS network address "7800" provided to the ICS logic terminal, and since the request identification from the conversion table 21023-1 is "C and further the sender ICS user address written to the user IP packet M02 is "10000 (i.e., roaming special nint)ex), the above ICS network address "780C is held, and is delivered with the ICS user packet PM2 to the connection server 21028-1 pointed to by the receiver ICS user address "631C (procedure T60). The ICS netmork address "780C obtained in this procedure will be used after the laterdescribed process T130. <<Function of connection server>> Next, the connection server 21028-1 calls the verifying server 21100-1 using the dcmain name "cl.bl.al.u, and transfers the dcmain name n cl.bl. al." and the cipher parameter RP2 to the verifying server (procedure T70). The verifying server 21100-1 reads the values of the password PW and cipher nmter written to the verifying table 21100-2, and selects cipher function Ei and reads the password PW. Next, the cipher parameter RP is RP2 = Ei(PW, TR) 1PIR, so the time randem number which Is to the latter half of the RP2 is used to calculate t = Ei(PW, TR). In the event that the value of this temporary variable t calculated here matches the first half Ei(PW, T) of the received RP2, confirmation can be made that the password PW entered into the terminal 21200-1 is correct. The time function TR includes the year/rnonth/day (i.e., TR = yy- rrin-dd-sssss), so unauthorized access can be discovered In the case that the received year/month/day does not match that time of processing.
Next, the verifying server 21100-1 reports the following items written in the verifying table 21100-2 to the connection server 210281 (procedure T80): ccrrpletion of roaming registration, billing class, and verifying server calling information (procedure T80). In the present entxxliment, the bill-ing class is MNY = 1, and the verifying server calling information is the ICS network address "7981n of the verifying server 21100-1, port number "710" and administration number "V' of the verifying administration table. The connection server 21028-1 presents the dcmain name "cl.bl.al." to the dcmain name server, requests the ICS user address and the ICS network address associated with the domain name (procedure T90), and obtains the ICS user address "120C and the ICS network address "8115" (procedure T100). In the same way, the connection server presents the dcnk-dn name "c2.b2.a2." to the dcmain name server, requests the ICS user address and the ICS network address associated with the dcmain name (procedure T110), and obtains the ICS user address "2500" and the ICS network address 0820C (procedure T120).
Next, the connection server 21028-1 informs the conversion table 191 server 21026-1 of the following (procedure T130): the ICS network address "7800n of the ICS logic terminal which has input the ICS user packet (held in procedure T60); the ICS user address "1200", ICS user address "2500", and ICS network address "8200", just obtained from the domain name server; and also the completion of roaming registration, billing class, and verifying server calling information received from the verifying server 21100-1.
The conversion table server 21026-1 writes the four address to the conversion table 21023-1 as received. The value of the request identification is n1C, meaning inter-corporation communication by roaming. In the event that the bi.1ling class is MNY = 1, the ICS network address "8115" and the ICS user address R120W' just obtained frem the donain name server are forwarded to the billing notification destination of the conversion table 21023-1. Also, in the event that the billing class is MNY = 2, verifying server calling information is forwarded to the billing notification destination of the conversion table 21013-1. Further, "5n which specifies the roaming connection period in days is also written to the conversion table 21013-1. When the writing to the conversion table 21023-1 is completed, the conversion table server 21026-1 reports the results to the connection server 21028-1 (procedure T140). This completion report is sent via the access control apparatus 21020-1 (procedure T150) to the roaming terminal 21200-1 with the ICS user packet PK03 (procedure T160).
Now, the ICS user packet PK03 includes the ICS user address "1200" associated with the domain name n cl.bl.al.n of the roaming terminal 21200-1, and the CS user address "2500" associated with the domain name " c2. W. a2. " of the other party of c=ninication. The corporation operating the access control apparatus can charge the owner of the roaming terminal 21200-1 for the above usage of the connection server 21028-1, i.e., the procedures for receiving the ICS user packet PK02 up to returning the ICS user packet PK03, and "5" which specifies the roaming connection period in days. <<Using the roaming terminal>> The roaming terminal 21200-1 can use the conversion table 210231 created following the above-described procedures, to perform intercorporation cormanication (procedures T170 through T220). In the event that "S" which specifies the roaming connection period in days elapses, the conversion table server 21026-1 can delete the above roaming connection written in the inside of conversion table 21023-1. <<Notification of billing>> The access control apparatus 21020-1 notifies the billing notification destination registered in the conversion table 21023-1 of the conminication charges (procedure T300 or T310). <<Method for accessing the verifying server>> On the above description, detailed description will be made regarding the method for judging whether or not the verification request contained in the ICS network packet PK02 generated by the roaming terminal 21200-1 due to the connection server 21028-1 presenting the domain name Ocl.bl.al." to a plurality of verifying servers including verifying server 21100-1 is correct, i.e., whether
193 or not the domain name "cl.bl.al." of the roaming terminal 21200-1 is registered with the verifying server.
An eyle of 4 -layer hierarchy will be described with reference to FIG. 128. A domain name "root" is provided on Level 1 of the tree, and domain names "al", "a2", "a3" and so forth exist on Level 2 below, domain names "bl", nb2". "b3", and so forth exist on Level 3 below "al" for example, and domain names "cl". l@c211, "c3"... and so forth exist on Level 4 below "bl" for example.
FIG.129 illustrates the internal table 21102-2 of the verifying server 21102-1 handling the domain "root", indicating,,e.g., that the ICS network address of the domain name server 21101-1 which handles the domain name "aln below the dmuin name "root" is "7971", and the port number is "710". Also, FIG.130 illustrates the internal table 21101-2 of the verifying server 21101-1 handling the domain "al", indicating, e.g., that the ICS network address of the domain name server 21100-1 which handles the damin name "bl" below the domain name teal" is "7981n, and the port number is n710u.
FIG.131 illustrates the internal table 21100-2 of the verifying server 21100-1 handling the domain "bl", indicating, e.g., that the domain name ncl" below the domain name nbl" shows "YES" in the endpoint in the internal table 21100-2, meaning that there are no more domain names below, and that in this example, the domain name n cl.bl.al" has been registered with the verifying server, and facts such that the password PW is "224691", that the date of expiration is "98-12-31n, etc., are recorded therein.
194 <<CaLling verifying server>> With reference to FIG.132, description will be made regarding the procedures in which the connection server 21028-1 calls the verifying server 21100-1 using the damain name "cl.bl.al.", and checks whether or not the dcmain name "cl.bl.al." has been registered in the verifying server. Now, the connection server 21028-1 has therein the ICS network address of the verifying server handling the daTain nroot" on Level 1 shown in FIG. 128. Also, in the event that there is a great deal of camunication with the verifying servers which handle the Level 2 and Level 3 danains, the ICS network addresses of the verifying servers thereof are held therein.
The connection server 21028-1 enters the demain name "cl.bl.al." in the interrial resolver 21029-1. The resolver 21029-1 sends the ICS frame 21335-1 including "al" under the dcmain name uroot" and the cipher parameter RP2 to the verifying server 21102-1, and an ICS packet 21336-1 including an ICS network address "7971n of the ICS damain name server for "aln is returned. Next, the resolver 21029-1 sends an ICS packet 21345-1 including "bl" to the verifying server 21101-1, and an ICS packet 21346-1 including an ICS network address "7981n of the verifying server for "bV' is returned. Next, the resolver 21029-1 sends an ICS packet 21355-1 including ncl" to the verifying server 21100-1, and regarding the damain name ncln, the space for the endpoint of 21100-1 is "Yes" this time, so it can be judged that verification information has been registered. In this way, nroot", Raln and nbl" have been followed in order, so it can be understood that the verification information for the reversed domain name ncl.bl.al." is registered in the internal table 21100-2.
The verifying server 21100-1 checks the received cipher parameter RP, and checks that the expiration date "98-12-31" has not expired. Next, the verifying server 21100-1 reads the password PW and the value of the cipher number written in the verifying table, and selects cipher function Ei. The cipher parameter RP is RR2 = Ei(PW, TR) 11 TR, so the tirne random nwk)k--r TR to the latter half of RP2 is used to calculate t = Ei (M TR). In the event that the value of this trary variable t calculated here matches the first half Ei(PW, TR) of the received RP2, confirmation can be made that the password PW entered into the terminal 21200-1 is correct. The above results are reported to the connection server 21028-1. Consequently, the connection server 21028-1 can know the verification results (authorized or denied) and the billing class MNY. <<Other ent)odiment of roaming without a home IP terminal>> In the above entxKlurent, in the event that the ICS receptionist does not set a home IP terndnal, the earlier-described nRegistration procedures fra, ham IP terminal" are performed via the user service server 21250-1. In this case, the billing record "120' within the verifying table 21100-2 within the verifying server 21100-1, and the information "7981-710-1" of the verifying server presented to the billing notification destination within the conversion table 21023-1, are used. <<Another enbodirrent of roaming wherein the verifying server is 196 included in the domain name server>> The structure of the domain name tree shown in FIG.128 that is the object of verifying server 21110-1 is the same as the domain name trees that are the object of domain name servers in other embodiments. Accordingly, each darain server is capable of storing the data of the verifying server described in the present embodt, and include the function of a verifying server. That is, this other method of carTying out roaming is realized by integrating the verifying server described in the present embodiment with the domain name server described in other entxxbffents. <<Access control apparatus and IP terminal connecting with wireless transceiver>> A wireless transceiver 21620-1 is provided within the ICS 21000-1, and the wireless transceiver 21620-1 and a wireless transceiver 21640-1 can exchange information one with another via a wireless ccmxniication path 21625-1. The terminal 21630-1 includes the less transceiver 21640-1, and as with the case of the earlierdescribed IP terminal 21200-1, the terminal 21200-2 has functions for inter-corporation cennurilcation using an ICS domain name. There is an information cotumnication path 21620-1 between the access control apparatus 21020-1 and the wireless transceiver 21620-1. The information communication path 21610-1 is Like the ICS user logic comenication line in that it has functions for sending and receiving ICS user packet, and these are different in that the information cenTnanication path 21610-1 is within the ICS 21000-1. The wireless transceiver 21620-1 and the wireless transceiver 21640-1 both have functions for receiving the ICS user packet, converting the information within the ICS user packet into ICS user packet information in waveform format and transmitting them, and also reverse function, i.e., receiving ICS user packet information in waveform format and reverse -converting into ICS packet format and transmitting these. Accordingly, the ICS user packet sent out fran the IP terndxial 21200-2 passes through the wireless transceiver 21640-1, wireless cenuunication path 21625-1, wireless transceiver 21620-1, and information camunication path 21610-1, and is provided to the access control apparatus. Also, an ICS packet sent out in the reverse direction, i.e., sent from the access control apparatus 210201 passes through the information cannxiication path 21610-1, the wireless transceiver 21620-1, the wireless cenTminication path 21625-2, the wireless transceiver 21640-1, and is delivered to the IP terminal 21200-2.
Ernbodiment-19 (Closed-zone network communication using network identifier, and open-zone communication):
A method for using a network identifier to restrict virtual dedicated line service, intra-corporation communication service and inter- corporation communication service to within the closed-zone. and a method for non-specifying the closedzone specification of the network identifier, i.e., specifying open-zone, will be described. Here, the network identifier is
198 appropriated corresponding with the ICS user address. <<Configuration>> As shown in FIGs.133 to 136, an ICS 22000-1 includes access control apparatuses 22010-1, 22020-1, 22030-1 and 220401, and the access control apparatus 22010-1 includes a line portion 220111, a processing device 22012-1 and a conversion table 22013-1, the access control apparatus 22020-1 includes a line portion 22021-1, a processing device 22022-1 and a conversion table 22023-1, the access control appartus 22030-1 includes a line portion 22031-1, a processing device 22032-1 and a conversion table 22033-1, the access control apparatus 22040-1 includes a line portion 22041-1, a processing device 22042-1 and a conversion table 22043- 1, and blocks 22060-1, 22061-1, 22062-1, 22063-1 and 22064-1 are each relay devices, and are interconnected and also connected to one of the access control apparatuses, via the ICS network communication line. Blocks 22101-1, 22102-1, 22103-1, 22104-1, 22105-1, 22106-1, 22107-1, 22108-1, 22109-1, 22110-1, 22111-1 and 22112-1 are each corporation LANs, and are each connected to the line portions of one of the access control apparatuses via the respective gateways and the ICS user logic communication line. Here, a block 22120-1 is a gateway for LAN 22101-1, a block 22121-1 is an ICS user logic communications line, and the other gateways and ICS user logic communication lines are also in similar positions, as shown in FIGs.133 through 136.
199 Each LAN has 2 to 3 IP terminals having function for sending an IP user packet, wherein the ICS user addresses are: for within LAN 22101-1, "150W' and "1510"; for within LAN 22102-1, "5200", "5210", and n5250"; for within LAN 22103-1, "190W' and "1910"; for within LAN 22104-1, "1100" and"111V; for within LAN 22105-1, "4200" and n4210"; for within LAN 22106-1, "18OW' and "1810"; for within LAN 22107-1, n1920" and n1930"; for within LAN 22108-1, "5410" and "5420"; for within LAN 22109-1, "143W' and "1440n; for within LAN 22110-1, "65000 and "196V; for within LAN 22111-1, n1820w' and "1830n; and for within LAN 22112-1, n4410" and "1420".
In the above description, values n10OW' through "1999" for the ICS user address indicate the ICS user addresses for the intra-corporation communication, values "20OW' through "6999" for the ICS user address indicate the ICS user addresses for the inter-corporation communication, and values "7000" through n9999" for the ICS network address indicate the ICS network addresses. The ICS network server uses the ICS user address range ("10OW' through u1999") when performing the intra-corporation communication, and the ICS user address range C'20OW' through "6999") when performing the inter-corporation communication. Also, the ICS user addresses used for the intra-corporation communication can also be used for the intercorporation communication. <<Conversion table line and network identifier>>
Description will be made regarding "lines" in the conversion table. For example, in conversion table 22013-1, the example is that wherein: in the first line, the value of request identification is nln, the value of transmitting ICS network address is "8100", the value of sender ICS user address (intra-corporation) is "1500n, sender ICS user address (intercorporation) is blank, the value of receiver ICS user address is "1100n, the value of receiving ICS network address is "7100", the value of the network identifier is nAOW', and other items are unfilled. Here, a blank space may mean "Nulln. The "line" in the conversion table is also referred to as a Wrecord" of the conversion table. The network identifier is a symbol provided for sectoring off a section of the ICS network and making that portion a net, and distinguishing the net, and may be a numeral or a code. The network identifiers are provided per line in the conversion table. Incidentally, in the event that the network is not to be a closed-zone network, this is indicated in each line in the conversion table with "Open", as shown in conversion table 22033-1.
The operation will be described with reference to the flowcharts in FIGs. 141 and 142. <<Closed-zone/intra-corporation communication>> An ICS user frame S01 is sent out from an IP terminal having an address "1100" within the LAN 22104-1, and reaches the access control apparatus 22020-1 via the ICS user logic 201 comunication line. At the time of receiving the ICS user packet S01 from the ICS logic terminal with the address "710C of the line portion 22021-1, the access control apparatus 22020-1 obtains the transmitting ICS network address R71000, and further obtains the sender ICS user address "110C and the receiver ICS user address "1500" from the ICS user packet S01 (Step SP100), and checks whether the transmitting ICS network address "7100" is registered on the conversion table 22023-1 with the request identification as "3" (Step SP110). In this case, it is not registered, so next the access control apparatus 22020-1 checks whether or not there is a record in the conversion table 22023-1 that contains all of the ICS network address "7100", the sender ICS user address nllooye, and the receiver ICS user address "1500", these having been obtained as described above (Step SP120). In this case, the existence of such is confirmed (Step SP130), and next, the sender ICS user address (intra-corporation) of this record alone is recorded as n1100", confirmation is made that the space for the sender ICS user address (inter-corporation) is blank, following which receiving ICS network address "810C is obtained (Step SP160).
Next, an ICS encapsulation is performed using the transmitting ICS network address "710C thus obtained and the receiving ICS network address "8100n (Step SP180), and the ICS network packet TO1 thus obtained is sent out onto the ICS 202 network communication line (Step SP190). The ICS network packet TO1 passes through the relay devices 22062-1, 22061-1 and 22060-1, and reaches the access control apparatus 22010-1. The access control apparatus 22010-1, upon receiving the ICS network packet TO1 (Step ST100), confirms that the receiving ICS network address n8100" written within the network control field (ICS capsule) of the ICS network packet TO1 is registered as the transmitting ICS network address "8100" within the conversion table 22013-1 (Step ST110), and then performs the ICS reverse encapsulation (Step ST120), and sends the obtained ICS user packet S01 to the ICS logic communication line 12121-1 connected to the address "8100" within the line portion 22011-1 (Step ST130). Incidentally, in the event that the receiving ICS network address n8100" is not registered within the conversion table 22013-1, the ICS network packet TO1 is discarded (Step ST115). <<Closed-zone/intra-corporation communication/access to network server>>
An ICS user packet S02 is sent out from an IP terminal having an address "1100" within the LAN 22104-1. At the time of receiving the ICS user packet S02 from the ICS logic terminal with the address "7100" of the line portion 22021-1, the access control apparatus 22020-1 obtains the transmitting ICS network address n7100", and further obtains the sender ICS user address "110C and the receiver ICS user address "6100" 203 from the ICS user packet S02 (Step SP100), and checks whether the ICS network address "7100" is registered on the conversion table 22023-1 with the request identification as "30 (Step SP110). In this case, it is not registered, so next the access control apparatus 22020-1 checks whether or not there is a record in the conversion table 22023-1 that contains all of the ICS network address "7100", the sender ICS user address "110C and the receiver ICS user address "6100", these having been obtained as described above (Step SP120). In this case, the non-existence of such is confirmed (Step SP130) Next, search is made for a record identical to the above receiver ICS user address "610C from one or more records in the conversion table with a network identifier the same as the network identifier "A001" having the request identification value "C' in the conversion table 22023-1 with the aforementioned ICS network address of "710C and the sender ICS user address of "1100n (in this case, the third record from the top in the conversion table 22023-1), and the receiving network address n9100" written to the record is found (Step SP170). Next, the ICS encapsulation is performed using the transmitting ICS network address "710C and the receiving ICS network address "910C thus obtained (Step SP180), and the ICS network frame T02 thus obtained is sent out onto the network communication line (Step SP190). The ICS network packet T02 passes through the relay devices 22062-1 and 22061-1, and 204 reaches the ICS network server 22081-1. The same is true for the ICS user packet S03 sent out from the IP terminal having the address "1110" within the LAN 22104-1, the network identifier is uA002", and is ICS- encapsulated to become the ICS network packet T03, and passes through the relay devices 220621 and 22061-1, and reaches the ICS network server 22082-1. <<Closed-zone/inter-corporation communication>> An ICS user packet S04 is sent out from an IP terminal having an address "4200" within the LAN 22105-1. At the time of receiving the ICS user frame S04 from the ICS logic terminal with the address n7200n of the line portion 22021-1, the access control apparatus 22020-1 obtains the transmitting ICS network address "7200", and further obtains the sender ICS user address "420C and the receiver ICS user address "5200" from the ICS user packet S04 (Step SP100), and checks whether the address "720C is registered on the conversion table 22023-1 with the request identification as "Y' (Step SP110). In this case, it is not registered, so next the access control apparatus 22020-1 checks whether or not there is a record in the conversion table 22023-1 that contains all of the transmitting ICS network address "7200n, the sender ICS user address n4200w and the receiver ICS user address n5200", these having been obtained as described above (Step SP120). In this case, the existence of such is confirmed (Step SP130), and next, the sender ICS user address (intracorporation) of this record is blank, 205 confirmation is made that the sender ICS user address (inter corporation) alone is recorded as "4200" (Step SP160).
Next, the ICS encapsulation is performed using the transmitting ICS network address "7200" thus obtained and the receiving ICS network address "820C (Step SP180), and the ICS network packet T04 thus obtained is sent out onto the network communication line (Step SP190). The ICS network packet T04 passes through the relay devices 22062-1, 22061-1 and 22060-1, and reaches the access control apparatus 22010-1. The access control apparatus 22010-1, upon receiving the ICS network packet T04 (Step ST100), confirms that the receiving ICS network address "8200" written within the network control field (ICS encapsule) of the ICS network frame T04 is registered as the transmitting ICS network address "820C within the conversion table 22013-1 (Step ST110), and then performs the ICS reverse encapsulation (Step ST120), and sends the obtained ICS user packet S04 to the ICS logic communication line connected to the address "8200" (Step ST130). <<Closed-zone/inter-corporation communication/access to network server>>
An ICS user packet S05 is sent out from an IP terminal having an address "4200" within the LAN 22105-1. At the time of receiving the ICS user packet SOS from the ICS logic terminal with the address "7200" of the line portion 22021-1, the access control apparatus 22020-1 obtains the transmitting 206 ICS network address "7200", and further obtains the sender ICS user address "420C and the receiver ICS user address "620C from the ICS user packet SOS (Step SP100), and checks whether the ICS network address "7200" is registered on the conversion table 22023-1 with the request identification as "3" (Step SP110). In this case, it is not registered, so next the access control apparatus 22020-1 checks whether or not there is a record in the conversion table 22023-1 that contains all of the transmitting ICS network address "7200", the sender ICS user address "420C and the receiver ICS user address "6200", these having been obtained as described above (Step SP120). In this case, the non-existence of such is confirmed (Step SP130), and next, search is made for a record identical to the above receiver ICS user address "610C from one or more records in the conversion table with a network identifier the same as the network identifier nBO01" having the request identification value "4n (ICS network server specification) in the conversion table 22023-1 with the aforementioned receiver ICS network address of "7200" and the sender ICS user address of "420On (in this case, the seventh record from the top in the conversion table 22023-1), and the receiving network address "920On written to the record is found (Step SP170).
Next, the ICS encapsulation is performed using the transmitting ICS network address w720On and the receiving ICS network address n9200" thus obtained (Step SP180), and the ICS 207 network packet TO5 thus obtained is sent out onto the ICS network communication line (Step SP190). The ICS network packet TOS passes through the relay device 22062-1 and reaches the ICS network server 22083- 1. The same is true for the ICS user packet S06 sent out from the IP terminal having the address n421OR within the LAN 22105-1, the network identifier is "BO02", and is ICS-encapsulated to become the ICS network frame T06, and passes through the relay device 22062-1 and reaches the ICS network server 22084-1. <<Communication from network server within ICS to network server outside of ICS>> The IP terminal 22092-1 within the LAN 22102-1 is an wICS external server", comprised of an IP terminal placed outside the ICS 22000-1 and so forth. The ICS external server 22092-1 has an ICS user address "5250'm, and is registered in the conversion table 22013-1 (ninth record from the top in the in the conversion table 22013-1). However, the receiver ICS user address and the receiving ICS network address spaces are blank, and are registered as being "Null". At the time that the ICS internal server 22084-1 sends out an ICS network packet T22, the ICS network packet T22 passes through the relay devices 22062-1, 22061-1 and 22060-1, and reaches the access control apparatus 22010-1 (Step SP100), confirmation is made that the transmitting IC network address is not registered within the conversion table 22013-1 as "8200", the ICS reverse 208 encapsulation is performed (Step SP120) in order to form the ICS user packet S22, which is sent toward the ICS external server 22092-1 (Step SP130). For reverse direction communication, the ICS encapsulation is performed using the conversion table 22013-1, and delivery is made to the ICS internal server 22084-1. <<Closed-zone/virtual dedicated line>> An ICS user packet S07 is sent out from an IP terminal having an address n180C within the LAN 22106-1. At the time of receiving the ICS user packet S07 from the ICS logic terminal with the address "730C of the line portion 22021-1, the access control apparatus 22020-1 obtains the transmitting ICS network address "7300", and further obtains the sender ICS user address n180C and the receiver ICS user address '190C from the ICS user packet S07 (Step SP100), and checks whether the ICS network address 0730C is registered on the conversion table 22023-1 with the request identification as "3", i.e., as a virtual dedicated line connection (Step SP110). In this case, it is registered. Next the access control apparatus 22020-1 checks whether or not there is a record in the conversion table 22023-1 that contains the transmitting ICS network address "730C and the receiver ICS user address n1900u, these having been obtained as described above (Step SP140). In this case, such does not exist, so the receiver ICS network address "830C of the record wherein the receiver ICS 209 s 1 user address space is blank (or "Null") with the ICS network address "7300" in the conversion table 220231 is found (Step SP145), the ICS encapsulation is performed using the transmitting ICS network address n730C thus obtained and the receiving ICS network address "8300" (Step SP180), and the ICS network packet T07 thus obtained is sent out onto the network communication line (Step SP190). The ICS network packet T07 passes through the relay devices 22062-1, 22061-1 and 22060-1, and reaches the access control apparatus 22010-1. The access control apparatus 22010-1, upon receiving the ICS network packet T07 (Step ST100), confirms that the receiving ICS network address "8300n written within the network control field (ICS capsule) of the ICS network packet T07 is registered as the transmitting ICS network address "8300" within the conversion table 22013-1 (Step ST110), and then performs the ICS reverse encapsulation (Step ST120), and sends the obtained ICS user packet S07 to the ICS logic communication line 12121-1 connected to the address "8300" within the line portion 22011-1 (Step ST130).
This is the same for ICS user packet S09 sent out from the IP terminal having the ICS user address "1820" within the LAN 22111-1, the network identifier is "CO02", the ICS encapsulation is performed and transferred through the ICS 22000-1, the ICS reverse encapsulation is performed at the access control apparatus 22030 to form an ICS user packet S09, 210 which reaches the IP terminal having the ICS user address "1920" within the LAN 22107-1. <<Closed-zone/virtual dedicated line/access to network server>> An ICS user packet S08 is sent out from an IP terminal having an address "1810" within the LAN 22106-1. At the time of receiving the ICS user packet S08 from the ICS logic terminal with the address "7300n of the line portion 22021-1, the access control apparatus 22020-1 obtains the ICS network address "7300n, and further obtains the sender ICS user address "1810" and the receiver ICS user address n6300n from the transmitting ICS user packet S08 (Step SP100), and checks whether "7300n is registered on the conversion table 22023-1 with the request identification as "3" (virtual dedicated line) (Step SP110). In this case, it is registered. Next the access control apparatus 22020-1 checks whether or not there is a record in the conversion table 22023-1 that contains the transmitting ICS network address "7300" and the receiver ICS user address "6300", these having been obtained as described above (Step SP140). In this case, such does exist, and the receiving network address n930C written to the record is found (Step SP145). Next, the ICS encapsulation is performed using the transmitting ICS network address "7300" and the receiving ICS network address "930C thus obtained (Step SP180), the transmitting ICS network address n730C thus obtained and the receiving ICS network are used to perform the ICS encapsulation 2 11 (Step SP180), and the ICS network packet T08 thus obtained is sent out onto the ICS network communication line (Step SP190). The ICS network packet T08 passes through the relay devices 22062-1 and 22064-1, and reaches the ICS network server 220871.
The same is true for the ICS user packet S10 sent out from the IP terminal having the address n183C within the LAN 22111-1, the network identifier is nCO02", and is ICSencapsulated to become the ICS network packet T10, and passes through the relay device 22064-1 and reaches the ICS network server 220891. <<Open-zone/inter-corporation comunication>> Open-zone/inter-corporation communication is almost the same as the aforementioned closed-zone/inter-corporation communication; the difference is that checking has been added for registration of both the sender ICS user address (intracorporation) and the sender ICS user address (intercorporation) in searching the records in conversion tables 22013-1 and 22043-1, as described below.
An ICS user packet S13 is sent out from an IP terminal having a user address "142C within the LAN 22112-1. At the time of receiving the ICS user packet S13 from the ICS logic terminal with the address R7405" of the line portion 22041-1, the access control apparatus 22040-1 obtains the transmitting ICS network address "7405n, and further obtains the sender ICS 212 user address "142C and the receiver ICS user address R542C from the ICS user packet S13 (Step SP100), and checks whether the ICS network address "7405" is registered on the conversion table 22023-1 with the request identification as "Y' (Step SP110). In this case, it is not registered, so next the access control apparatus 22040-1 cheeks whether or not there is a record in the conversion table 22043-1 that contains all of the transmitting ICS network address "7405", the sender ICS network address "1420" and receiver ICS user address "5420", these having been obtained as described above (Step SP120), the existence of such is confirmed (Step SP130), and next, a record is found recorded in the conversion table 22043-1 wherein the sender ICS user address (intra-corporation) is "1420n and the sender ICS user address (inter-corporation) is "5420" (in this case, the fifth record from the top on conversion table 220431). Next, the received sender ICS user address (intracorporation) R142C is re- written to a inter-corporation address "4420", and the receiving ICS network addres S n 840C registered to this record is obtained (Step SP160). Next, the ICS encapsulation is performed using the transmitting ICS network address "7405n and the receiving ICS network address "840C thus obtained (Step SP180), and the ICS network packet thus obtained is sent out onto the ICS network communication line (Step SP190). The ICS network packet passes through the relay devices 22064-1 and 22063-1, and reaches the access 213 control apparatus 22030-1. The access control apparatus 220301, upon receiving the ICS network packet (Step ST100), confirms that the receiving ICS network address "840Ou written within the network control field (ICS capsule) of the ICS network packet is registered as the transmitting ICS network address "8400n within the conversion table 22033- 1 (Step ST110), and then performs the ICS reverse encapsulation (Step ST120), and sends the obtained ICS user packet S130 to the ICS logic communication line connected to the address "8400" (Step ST130).
An ICS user packet S11 sent out from an IP terminal having an ICS user address "44100 within the LAN 22112-1 is ICS-encapsulated by the access control apparatus 22040-1 by same procedures as described above with regard to closedzone/inter-corporation communication, transferred through the ICS 22000-1, reversely ICS-encapsulated in the access control apparatus 22030-1, and delivered to an IP terminal having an ICS user address "541C within the LAN 22108-1. As another example, an ICS user packet S12 sent out from an IP terminal having an ICS user address R4410n within the LAN 22112-1 is ICS-encapsulated by the access control apparatus 22040-1 by the same procedures as described above, transferred through the ICS 22000-1, delivered to the access control apparatus 22030- 1, and at the time of the ICS reverse encapsulation, reference to the record in conversion table 22033-1 (in this case, the fifth 214 record from the top on the conversion table) reveals that the address "5430" written within the ICS user packet S12 is an ICS user address (inter-corporation), the address value "5430" is re-written to an ICS user address (intra-corporation) "1430" (Step ST120), an ICS user packet S120 is generated, and delivered to the IP terminal having the ICS user address "143W' within the LAN 22109-1. As another example, an ICS user packet S14 sent out from an IP terminal having an ICS user address "1420" within the LAN 22112-1 has a sender ICS user address "1420" and a receiver ICS user address n5440n, is transferred through the ICS 22000-1 and is delivered to the IP terminal within the LAN 22109 with an ICS user address of "1440" and a sender ICS user address "4420", having been converted to an ICS user packet S140 with a receiver ICS user address "1440". <<Open-zone/inter-corporation communication/access to network server>> ICS user packets S15 and S16 sent out from within the LAN 221121 are delivered to the ICS network server 22085-1 that is the destination of each, following the same procedures as that described above. <<Communication from network server within ICS to network server outside of ICS>> A block 22086-1 is an ICS network server is an within the ICS 22000-1, and is an "ICS external server", comprised of a database placed outside the ICS 22000-1, and so forth. The 215 ICS external servers 22090-1 and 22091 have ICS user addresses "650C and "1960", and are registered in the conversion table 22033-1 (in this case. the eighth and ninth records from the top in the in the conversion table 22033-1). However, the receiver ICS user address and the receiving ICS network address spaces are blank, and are registered as being "Null". The ICS external server 22091-1 has sender ICS user address (intracorporation) "1960", and further, is provided with a sender ICS user address (intercorporation) "6960". Also, the ICS internal server 22086-1 has ICS user address "6600", ICS network address "9500", these being registered in the conversion table 22033-1 (in this case, the tenth record from the top in the in the conversion table 22033-1).
At the time that the ICS internal server 22086-1 sends out the ICS network packet T20, the ICS network packet T20 passes through the relay devices 22063-1 and reaches the access control apparatus 22030-1, the ICS reverse encapsulation is performed using the conversion table 22033-1 in order to form the ICS user packet S20, which is delivered to the ICS external server 22090-1. For reverse direction communication, the ICS reverse encapsulation is performed in the access control apparatus 22030- 1 to form the ICS user packet S21, and delivery is made to the ICS external server 22086-1. Summarizing the above, an ICS external server is placed outside of the ICS 22000-1, and communication between internal servers within the 216 ICS 22000-1 and external servers outside the ICS 22000 is enabled.
An arrangement may be used wherein all or a plurality of records in the conversion table 22013-1 within the access control apparatus 22013-1 are selected as necessary, stored within a conversion table record file 220141, and extracting as necessary for performing the ICS encapsulation and the ICS reverse encapsulation. This also is true for the conversion table 22020-1 within the access control apparatus 22023-1 and so forth. In the access control apparatus, the portion of the conversion table 21033-1 in which specification of the network identifier is that for open-zone connection ("Open") is usually not held within the access control apparatus, and instead an arrangement may be used in which address information to be registered to the conversion table is obtained from the domain name server 22095-1 and temporarily used as a conversion table 22030-1. Also, the network server 22081-1 for closedzone/intracorporation communication may be used as a domain name server for closedzone/intra-corporation communication which can be commanded by the network identifier nMOV'. Incidentally, the hierarchical structure of the domain name in the example is shown to be a single-layer structure specifying, e.g., domain name "al", but this may be made to be 2- or 3layer hierarchy such as "bl.al." or ncl.bl.al.". Further, the network server 22083-1 for closed-zone/inter-corporation
217 communication may be used as a domain name server for closedzone/inter- corporation communication which can be commanded by the network identifier "BO01". The network server 22087-1 for closed-zonelvirtual dedicated line may be used as a domain name server for closed- zone/virtual dedicated line which can be commanded by the network identifier "CO01m. Incidentally, in the present embodiment, the hierarchical structure of the domain name in the example is shown to be a single-layer structure specifying, e.g., domain name "aln, but this may be made to be 2- or 3-layer hierarchy such as "bl.al." or ncl.bl.al.".
Embodiment-20 (IP terminal capable of connecting to plural access control apparatuses with identifiers):
The present embodiment does not fix the IP terminal having the functions for sending and receiving ICS user IP packet to a specific access control device; rather, it realizing usage of an IP terminal which can be moved and connected to other access control apparatuses and used, i.e., capable of roaming, using identifiers. Roaming is realized based on the ICS domain name provided to the IP terminal. <<Password transmission technique using cipher>> The present embodiment includes procedures for ciphering a secret password PW and sending this from the sender (ciphering side) to the receiver (decoding side). First, the 218 ciphering function Ei and the decoding function Di will be described. The ciphering function Ei is represented by y Ei(kl, x), and the decoding function Di is represented by x Di(k2, y). Here, y denotes the ciphertext, x denotes plaintext, kl and U are keys, and "i" represents cipher numbers (i = 1, 2,---) determining the secret key code and public key code, including how the value of the cipher key is to be used. In the above, an arrangement may be used wherein plain-text x' is ciphered instead of the plain-text x with x' = xilr (wherein r is a random number), and discarding the random number r from the plain-text x' upon decoding, thus obtaining the plain-text x. Such an arrangement generates a different ciphertext each time the same plain-text is ciphered, owing to the random number, and it is said that such is less susceptible to cipher cracking. (Example of cipher number i = 1) <<Preparation>> The sender m discloses the domain name thereof (DNm) to the public including the receiver. The receiver calculates Km = Hash-l(DNm) using the secret data compression function Hash1, and hands over only the cipher key Km using a safe method so as to be unnoticed by athird party. This example is an example of using DES ciphering, and the sender holds an]m ciphering module DES-e" for realizing the ciphering function E!, and a cipher key Km. The cipher key Km is a secret value 219 which the sender and receiver share. The receiver has the nciphering module DES-W for realizing the decoding function Di and the data compression function Hash-1. What is used for the data compression function Hash-1 is determined separately for each cipher number. A data compression function is also referred to as a "hash function". <<Ciphering by sender>> The sender sets the secret password PW as x = PW, and ciphers as y = DES- e(Km,x) with the ciphering module DES-e and the cipher key Km being held, thereby sending the ciphertext and domain name DNm. <<Decoding by receiver>> The receiver receives the ciphertext y and the domain name DNffi, calculates the secret cipher key Km as Km = Hashl(DNffi) using the receiver's secret data compression function Hash-1, and the obtains the plain-text x as x = DES - d(Km,y) using the decoding module. The plain- text x is password PW, and the receiver can obtain the secret password PW. A third party does not know the data compression function Hash-1 and thus cannot calculate the cipher key Km, and accordingly, cannot calculate the secret password PW. In the above embodiment, as stipulation of the cipher number i = 3, the ciphering function and the decoding function can be replaced with coding function and decoding function other than DES code. (Example of cipher number i = 2) 220 <<Preparation>> The present example is an example of employing RSA ciphering, wherein the sender generates a ciphering function y = x%od n and a decoding function y = xSod n. Here, e g d holds, the key d being a secret value. The sender hands to the receiver the discloseable ciphering keys e and n, and the ciphering module RSA-e for realizing y = x%od n. The sender holds the ciphering keys and the ciphering module RSA-e. The sender does holds neither the secret ciphering module nor secret data. On the other hand, the receiver holds n and the secret key d and the ciphering module RSA-e for realizing y x'mod n. <<Ciphering by sender>> The sender ciphers the secret password PW, own domain name DNm, and time of sending (year/month/day/hour/minute /second) as x = PW 1 xl 11 x2 (wherein Xl: domain name DNm, and x2 year/month/day/hour/minute /second) and encodes as y = x%od n using the ciphering module RSA-e, thus sending the ciphertext Y. <<Decoding by receiver>> The receiver receives the ciphertext y and calculates y X%od n using the decoding module RSA-d held beforehand and the decoding key. The result is x = PW 11 xl 11 x2, so the data which is at a certain position from the head of x is used as PW. In the above ciphering, domain name xl and year/month/day/ 221 hour/minute/second x2 are used as random numbers. A third party does not know the secret key d and thus cannot calculate the secret password PW. In the above embodiment, as stipulations of the cipher number i = 4, the values of the cipher keys e, d and n can be changed. Also, as stipulations of the cipher number i = 5, the RSA ciphering technique can be replaced with a different public key ciphering technique. <<Terminal verification technique using password and random number>> Description will be made regarding verification technique for determining whether or not the password PW used by a roaming terminal agrees with the password registered in the verifying server. As prerequisite conditions, the verifying server of the verifying entity and the terminal of the user to receive verification have a password PW that is secret to a third party, with a ciphering function E (wherein y = E(k,x), y represents ciphertext, k represents ciphering key, and x represents plain-text). Specific procedures for terminal verification will now be described. The terminal of the user to receive verification decides upon a random number R using appropriate means, calculates Yl = F(PW, R) using the password PW and the function y = F(PW, R) and sends both the random number R and Yl to the verifying entity. The verifying entity receives the random numbers R and Y1, and calculates Y2 = F(FW, R) using the received random number R, the password PW held
222 within, and function F, and checks whether or not Y1 - Y2 holds. In the event that there is a match, the verification can be made that the owner of the terminal which is being verified is using the correct password PW, i.e., verification of the terminal can be made. In the above technique, an arrangement in which the user to be verified cannot freely select the random number R but rather the random number R is restricted to depending on time (called a time random number) further increases difficulty of a third party calculating the password. Instead of the ciphering function used above, the secret data compression function Hj may be used instead, for Y1, Y2 = Hj(W, R). <<Overall configuration>> FIGs.143 and 144 illustrate an overview of the roaming technique according to the present embodiment, wherein an ICS 21000-1 includes access control apparatuses 21010-1, 21020-1, 21030-1, 21040-1, 21050-1 and 21060-1, relay devices 21080-1, 21081-1, 21082-1 and 21083-1, verification servers 21100-1, 21101-1, 21102-1 and 21103-1, domain name servers 21130-1, 21131-1, 21132-1 and 21133-1, user service server 21250- 1 and an ICS authority server 21260-1. The access control apparatus 21010- 1 is provided with a conversion table 21013-1, a conversion table server 21016-1, a registration server 21017-1 and a connection server 21018-1. The access control apparatus 21020-1 is provided with a conversion table 21023-1, a conversion table server 21026-1, a registration server 21027-1 and a connection server 21028-1. The connection servers 210181 and 21028-1 are provided with an ICS user address "6310", and has the function to register access control apparatuses determined as necessary to the IP terminal, or to connect thereto. The verifying server 21100-2 is shown in FIG.145 and the conversion table 21023-1 is shown in FIG.146.
The conversion table server 21016-1 has a function for re-writing the contents of the conversion table 21013-1, and the conversion table server 21026-1 has a function for rewriting the contents of the conversion table 21023-1, which is the same as described in other embodiments. Also, the LAN 21150-1 has an IP terminal 21151-1, the LAN 21160-1 has an IP terminal 21161-1, and a block 21171-1 is an IP terminal. A block 21200-1 is a portable roaming terminal, and is identified by the ICS domain name "cl.bl.al." ICS 21000-1. <<Application for use of roaming terminal>> The owner of a roaming terminal 21200-1 indicates as an ICS usage applicant 21270-1 the payment method for the roaming terminal 21200-1, and applies to the ICS authority server 21260-1 via user service server 21250-1 for an ICS domain name and an ICS user address. The payment method is represented by billing class "MNY", e.g., in the event that MNY = 1, the charges are billed to the home IP (i.e., an IP terminal which provided uniquely ithin the 224 is connected to the access control apparatus in a fixed manner), in the event that MNY = 2, the charges are paid according to the record of the verifying server. The ICS authority server 21260-1 sets an ICS domain name: "cl.bl.al. for using the roaming terminal 21200-1, and an ICS user address "1200". Further, in order to be connected to the access control apparatus in a fixed manner and use it, the owner of the IP terminal 21200-1 applies for an ICS network address to the ICS authority server 21260-1 via the user service server 21250-1. The user service server 21250-1, upon obtaining the ICS network address, makes a request to the conversion table server 21016-1 to set the ICS network address "8115" and the ICS user address "1200n in the conversion table 21013-1.
The ICS receptionist 21271-1 embeds inside the interior 21201-1 of the roaming terminal 21200-1 the following: ICS domain name "cl.bl.al.", ICS user address "1200", special ICS address for roaming terminals (called Hroaming special number "1000", ICS user address "6300" for registration server, and ICS user address "6310" for connecting server, and further embeds inside the interior 21201-1 of the roaming terminal 21200-1 the ciphering function Ei and the decoding related data RP1. Now, RP1 = Hj (domain 11 name RPO) 11 RPO (wherein RPO = NMY 11 i JI j 11 NID) holds, and the domain name is "cl. bl. al. ". MW is the above- described billing class, ni" is a cipher number for the cipher Ei, and nin determines the type of Hash function Hj, and 92) %ID" is a network identifier nBOOV'. Network identifies are named to distinguish between closed-zone networks and open-zone networks. Data compression function Hj is a secret dedicated function used only by the verifying server and the user service server. The user does not hold the data compression function Hj, and does not even known Hj, and thus is incapable of generating cipher related data RP1. <<Registration procedures from home IP terminal>> Description will be made with reference to FIG.147. roaming terminal user connects the roaming terminal 21200-1 to the position of the home IP terminal 21151-1. Next, the roaming terminal user decides on a password (PW) and enters this from the input unit 21204-1, and also generates an ICS user packet PKO1 using the ciphering function and the codingrelated data stored within 21202-1, and sends it to the access control apparatus 21010-1 via the ICS user logic comunication line 21152-1 (procedures T10). The destination of the ICS user packet PKO1 is "6300n which points to the roaming registration server, and includes own ICS domain name "cl.bl. al.", cipher parameter PR1, ICS user address n1200n, expiration data n98- 1231 ciphertext "y" which is the password that has been ciphered, mtgo (wherein tg = 1 in order to display registration procedures), and "Yes" or 'Son for roaming connection specification. The generation method employed for the ciphertext "yn is the ciphering technique described earlier.
For example, in the event that the cipher number = 2, ciphertext "y" is generated with y = x%od n (wherein x = PW cl.bl.al. 1I year /month/day/hour /minute/ second). The access control apparatus 21010-1 looks at the conversion table 21013-1 and transfers the ICS user packet PKO1 to the registration server 31017-1 with the destination n6300" (procedure T15). The registration server 21017-1 uses the domain name Wcl. bl.al.n to call the verifying server 21100-1 (procedure T20). Also, the method by which the registration server 210171 calls the verifying server 21100-1 using the domain name is the same as the method by which the connection server 21028-1 calls the verifying server 21100-1 using the domain name, the details thereof being described in detail later. The verifying server 21100-1 checks the contents of the received ICS user packet PK01, and decodes the ciphertext "y" using the earlierdescribed technique. thereby calculating the password PW. For example, in the event that the code number = 2, the ciphertext n yn is decoded with x = ydmod n. This yields x = PW 111. bl. al. year/month/day/hour/minute/second, so the password PW can be obtained.
Next, the contents of the cipher parameter PP1 is RP1 Hj (domain name 11 RPO) 11 RPO (wherein RPO = MNY 11 i Ii j 11 NID), so the verifying server 21100-1 uses the secret Hash function Hj held within the verifying server 21100-1 and the obtained domain name m cl. bl. al. " to calculate t = Hj (domain name 11 RPO) 11 RPO), 227 and checks whether or not t = RP1 holds for the received RP1. If it holds, judgment is passed that the domain name n cl.bl.al.", billing class MNT, cipher numbers ni" and "j", and the network identifier "NID" have not been tampered with. The verifying server 21100-1 checks for excessive or insufficient registration contents, and in the event that the contents are normal, the registration results are registered in the verifying table 21100-2; registration is not made in the event there are insufficient registration contents.
This is illustrated in the verifying table 21100-2 in the line with the administration number 1, with the domain name as "cl.bl.al.", cipher number "2", billing class (MNY) "1", value of calculated password PW "224691", expiration date "9812-31", roaming connection of RYeC, i.e., acceptance of a roaming connection. At the time of generating the PKO1 in procedure T10, the aforementioned value of tg may be set to tg 2 and roaming connection set to 'So The password will not leak to a third party. due to application of the abovedescribed ciphering method. Roaming registration is reported by passing through the registration server (procedure T30), then the access control apparatus 21010-1 (procedure T35), and reported to the roaming IP terminal (procedure T40). Further, an ICS user packet for changing the value of the password PW with tg = 3 or changing the date of expiration with tg = 4 can be sent from the terminal 21200-1 via the ICS user logic 228 communication line 21152-1, after the above procedure T40 has been completed. Incidentally, a method which can be employed for changing the password involves specifying the prior password. <<Sending and receiving user IP packet while traveling>> An example will be described regarding connecting a roaming terminal 21200-1 to the access control apparatus 210201 and sending and receiving of the user IP packet between domain name "cl.bl.al.n of the roaming terminal 21200-1 and the other party of communication with a domain name "c2.b2.a2.u The user inputs the following from the input unit 21204-1: the domain name nc2.b2.a2.' of other party of communication, ntgn which has been set to tg = 5 for specifying sending and receiving of user IP packet, own password PW, and "5n which specifies the roaming connection period in days (represented by TTL). The cipher parameter RP2 is data calculated with the password PW and the inside 21202-2. That is, year/month/day/second "yy-mm-dd-sssss" is generated and used as a time random number TR (TR = yy-mm-dd-sssss), and the clock of inside 21202-2 and the cipher function Ei is used to calculate RP2 = Ei (PW, TR) 11 TR.
The access control apparatus 21020-1 receives the user IP packet PK02, obtains the ICS network address "7800n provided to the ICS logic terminal, and since the request identification from the conversion table is "4n and further the sender ICS 229 user address written to the user IP packet PK02 is I'100011 (i.e., roaming special number), the above ICS network address n780C is held, and is delivered with the ICS user packet PM2 to the connection server 21028- 1 pointed to by the receiver ICS user address "631C (procedure T60). The ICS network address "7800" obtained in this procedure will be used after the laterdescribed process T130. <<Function of connection server>> Next, the connection server 21028-1 calls the verifying server 21100-1 using the domain name "cl.bl.aln, and transfers the domain name "cl.bl. al" and the parameter RP2 to the verifying server (procedure T70). The verifying server 21100-1 reads the values of the password PW and the cipher number written to the verifying table 21100-2, and selects cipher function Ei and reads the password PW. Next, the cipher parameter RP is RP2 = Ei(PW, TR) 11 TR, so the time random number which is to the latter half of the RP2 is used to calculate t Ei(PW, TR). In the event that the value of this temporary variable t calculated here matches the first half Ei(PW, T) of the received RP2, confirmation can be made that the password PW entered into the terminal 212001 is correct. The time function TR includes the year/month/day (i.e., TR = yy-mm-ddsssss), so unauthorized access can be discovered in the case that the received year/month/day does not match that time of processing.
Next, the verifying server 21100-1 reports the following items written in the verifying table 21100-2 to the connection server 21028-1 (procedure T80): completion of roaming registration, billing class, and verifying server calling information (procedure T80). In the present embodiment, the billing class is MNY = 1, and the verifying server calling information is the ICS network address "7981" of the verifying server 21100-1, port number "71C and administration number "1R of the verifying administration table. The connection server 21028-1 presents the domain name Ocl.bl.al." to the domain name server, requests the ICS user address and ICS network address associated with the domain name (procedure T90), and obtains the ICS user address "1200" and ICS network address '8115n (procedure T100). In the same way, the connection server presents the domain name "c2.b2.a2." to the domain name server, requests the ICS user address and the ICS network address associated with the domain name (procedure T110), and obtains the ICS user address "2500n and the ICS network address n820C (procedure T120).
Next, the connection server 21028-1 informs the conversion table server 21026-1 of the following (procedure T130): the ICS network address "780C of the ICS logic terminal which has input the ICS user packet (held in procedure T60); the ICS user address "1200", ICS user address "2500", and ICS network address "8200", just obtained from the domain name 231 server; and also the completion of roaming registration, billing class, and verifying server calling information received from the verifying server 21100-1. The conversion table server 2120-6 writes the four address to the conversion table 21023-1 as received. The value of the request identification is "lo", meaning the Inter-corporation communication by roaming. The network identifier (NID) is nBO01n. In the event that the billing class is MNY = 1, the ICS network address "8115" and the ICS user address n120W' just obtained from the domain name server are forwarded to the billing notification destination of the conversion table 210231. Also, in the event that the billing class is MNY = 2, verifying server calling information is forwarded to the billing notification destination of the conversion table 210131. Further, "5" which specifies the roaming connection period in days is also written to the conversion table 21013-1. When the writing to the conversion table 21023-1 is completed, the conversion table server 21026-1 reports the results to the connection server 21028-1 (procedure T140). This completion report is sent via the access control apparatus 21020-1 (procedure T150) to the roaming terminal 21200-1 with the ICS user packet PM3 (procedure T160).
Now, the ICS user packet PK03 includes the ICS user address n1200n associated with the domain name "cl.bl.al." of the roaming terminal 212001, and the CS user address "2500" 232 associated with the domain name "c2.b2.a2." of the other party of communication. The corporation operating the access control apparatus can charge the owner of the roaming terminal 21200-1 for the above usage of the connection server 21028-1, i.e., the procedures for receiving the ICS user packet PK02 up to returning the ICS user packet PK03, and "5n which specifies the roaming connection period in days. The above embodiment is an example of the network identifier (NID) RBOW', and is applied to closed-zone networks described in other embodiments. Also, as another embodiment, the network identifier (NID) may be set as nOpen" and applied to an open-zone network. In this case, the roaming technique is the same as that of the aforementioned closed-zone network "BO01n. <<Using the roaming terminal>> The roaming terminal 21200-1 can use the conversion table 21023-1 created following the above-described procedures, to perform the inter- corporation conymmication the same as with that described in other embodiments (procedures T170 through T220). In the event that n5n which specifies the roaming connection period in days elapses, the conversion table server 21026-1 can delete the above roaming connection written in the inside of conversion table 21023-1. <<Notification of billing>> The access control apparatus 21020-1 notifies the billing notification destination registered in the conversion 233 table 21023-1 of the communication charges (procedure T300 or T310). <<Method for accessing the verifying server>> Of the above description, detailed description will be made regarding the method for judging whether or not the verification request contained in the ICS network packet PK02 generated by the roaming terminal 21200-1 due to the connection server 21028-1 presenting the domain name "cl.bl.al." to a plurality of verifying servers including verifying server 21100-1 is correct, i.e., whether or not the domain name n cl.bl.al." of the roaming terminal 21200-1 is registered with the verifying server.
An example of 4-layer hierarchy will be described with reference to FIG. 173. A domain name "rooC is provided on Level 1 of the tree, and domain names "al", "a2g', "aYe... and so forth exist on Level 2 below, domain names nbl", 'b2", 0b391... and so forth exist on Level 3 below "aln for example, and domain names "cl", 91c2", below "bl" for example.
19 c3u - and so forth exist on Level 4 FIG.149 illustrates the internal table 21102-2 of the verifying server 21102-1 handling the domain RrooC, indicating, e.g., that the ICS network address of the domain name server 21101-1 which handles the domain name "al" below the domain name "rooC is "7971", and the port number is "710" Also, FIG.150 illustrates the internal table 21101-2 of the 234 verifying server 21101-1 handling the domain 11a1H, indicating, e.g., that the ICS network address of the domain name server 21100-1 which handles the domain name "bl" below the domain name nalw is n7981n, and the port number is "71On. FIG.151 illustrates the internal table 21100-2 of the verifying server 21100-1 handling the domain "bl", indicating, e.g. , that the domain name "cl" below the domain name "bl" shows "YESn in the terminal space in the internal table 21100-2, meaning that there are no more domain names below, and that in this example, the domain name Rcl.bl. al" has been registered with the verifying server, and facts such that the password PW is "224691", that the date of expiration is "98-12-31n, etc., are recorded therein <<Calling verifying server>> With reference to FIG.152, description will be made regarding the procedures in which the connection server 21028-1 calls the verifying server 21100-1 using the domain name Rcl.bl.al.", and checks whether or not the domain name Rcl.bl.al." has been registered in the verifying server. Now, the connection server 21028-1 has therein the ICS network address of the verifying server handling the domain "rootn on Level 1 shown in FIG.153. Also, in the event that there is a great deal of communication with the verifying servers which handle the Level 2 and Level 3 domains, the ICS network addresses of the verifying servers thereof are held therein.
235 The connection server 21028-1 enters the domain name Wcl.bl.al." in the internal resolver 21029-1. The resolver 21029-1 sends the ICS packet 21335-1 including "al" under the domain name "root" and the cipher parameter RP2 to the verifying server 21102-1, and an ICS packet 21336-1 including an ICS network address "7971" of the ICS domain name server for naln is ret = ed. Next, the resolver 21029-1 sends an ICS packet 21345-1 including nbl" to the verifying server 21101-1, and an ICS packet 21346-1 including an ICS network address "7981n of the verifying server for nbln is ret=ed. Next, the resolver 21029-1 sends an ICS packet 21355-1 including ncln to the verifying server 21100-1, and regarding the domain name Oclu, the space for the endpoint of 21100-1 is "Yes" this time, so it can be judged that verifying information has been registered. In this way, "rootn, "al", and "bl'm have been followed in order, so it can be understood that the verification information for the reversed domain name cl.bl.al." is registered in the internal table 21100-2.
The verifying server 21100-1 checks the received cipher parameter RP2, and checks that the expiration date "98-12-31" has not expired. Next, the verifying server 211001 reads the password PW and the value of the cipher number written in the verification table, and selects cipher function Ei. The cipher parameter RP is RR2 = Ei (PW, TR) 11 TR, so the time random number TR to the latter half of RP2 is used to calculate t = Ei(PW, 236 TR). In the event that the value of this temporary variable calculated here matches the first half Ei(PW, TR) of the received RP2, confirmation can be made that the password PW entered into the terminal 21200-1 is correct. The above results are reported to the connection server 21028-1. Consequently, the connection server 21028-1 can know the verification results (authorized or denied) and billing class MNY. <<Other embodiment of roaming without a home IP terminal>> In the above embodiment, in the event that the ICS receptionist 21271-1 does not set a home IP terminal, the earlier-described "Registration procedures from home IP terminal" are performed via the user service server 21250-1. In this case, the billing record "120" within the verifying table 21100-2 within the verifying server 21100-1, and the information "7981-710-lu of the verifying server presented to the billing notification destination within the conversion table 21023-1, are used. <<Another embodiment of roaming wherein the verifying server is included in the domain name server>> The structure of the domain name tree shown in FIG.153 that is the object of verifying server 21110-1 is the same as the domain name trees that are the object of domain name servers in other embodiments. Accordingly, each domain server is capable of storing the data of the verifying server 237 described in the present embodiment, and include the functions of a verifying server. That is, this other method of carrying out roaming is realized by integrating the verifying server described in the present embodiment with the domain name server described in other embodiments. <<Access control apparatus and IP terminal connecting with wireless transceiver>> A wireless transceiver 21620-1 is provided within the ICS 21000-1, and the wireless transceiver 21620-1 and a wireless transceiver 21640-1 can exchange information one with another via a wireless ccmminication path 21625-1. The terminal 21630-1 includes the wireless transceiver 216401, and as with the case of the earlierdescribed IP terminal 21200-1, the terminal 21200-2 has a function for the inter-corporation communication using an ICS domain name. There is an information communication path 21620-1 between the access control apparatus 21020-1 and the wireless transceiver 21620-1. The information camiLmication path 21610-1 is Like the ICS user logic cammication line in that It has a function for sending and receiving ICS user packets, and these are different in that the information ccnTmnication path 21610-1 is within the ICS 21000-1. The wireless transceiver 21620-1 and the wireless transceiver 21640-1 both have a function for receiving ICS user packets, converting the information within the ICS user frame into ICS user packet information in waveform format and transmitting them, and also reverse functions, i.e., receiving ICS user packet information in waveform format and reverse- 238 converting into ICS packet format and transmitting these. Accordingly, the ICS user packet sent out from the IP terminal 21200-2 passes through the wireless transceiver 21640-1, wireless caminication path 21625-1, wireless transceiver 21620-1, and information camninication path 21610-1, and is provided to the access control apparatus. Also, ICS frame sent out in the reverse direction, i.e., sent from the access control apparatus 21020-1 passes through the information conTmziication path 21610-1, wireless transceiver 21620-1, wireless canTunication path 21625-2, wireless transceiver 21640-1, and is delivered to the IP terminal 21200-2.
Thus, according to the present invention, administration of information cenTminication is performed with a unified address system, and various services can be provided, without using dedicated lines or the Internet, thus enabling structuring a large-scale ccimunication system with high security and with relatively low costs. Also, intercorporation camn=cation can be performed between individual corporations (including governmentorganizations, universities, and so forth) which had conventionally been servIces separately with practically no change to the address system for computer coffnunicatlons. Further, since the network administrator holds the network control authority, the overall administration of the network becemes clear, increasing ease of se=ing reliability and also markedly mpro=g security.
239 CLAM 1. In an integrated information communications system; wherein an ICS user packet having a unique ICS user address system ADX is converted into an ICS network packet having an address system ADS, based on the administration of a conversion table provided within an access control apparatus; and wherein in the case that transmission is made over at least one VAN contained therein following rules of said address system ADS, and the destination other access control apparatus is reached, conversion is made to said ICS user address system ADX based on the administration of said conversion table, and another external information communications apparatus is reached, characterized Mi that ICS user address and ICS network address of communication other party are obtained as ICS domain name which is telephone number, and said ICS network address is held in a conversion table within access control apparatus at a call side.
1 W -1 2-4 D
GB9920041A 1997-12-05 1998-10-05 Integrated information communication system Expired - Fee Related GB2338871B (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
JP35022497A JP3084681B2 (en) 1996-12-06 1997-12-05 Integrated information and communication system
JP3900798A JP3000051B2 (en) 1998-02-20 1998-02-20 Integrated information and communication system
GB9821661A GB2332837B (en) 1997-12-05 1998-10-05 Integrated information communication system

Publications (3)

Publication Number Publication Date
GB9920041D0 GB9920041D0 (en) 1999-10-27
GB2338871A true GB2338871A (en) 1999-12-29
GB2338871B GB2338871B (en) 2000-08-30

Family

ID=27269500

Family Applications (7)

Application Number Title Priority Date Filing Date
GB9920041A Expired - Fee Related GB2338871B (en) 1997-12-05 1998-10-05 Integrated information communication system
GB0019276A Expired - Fee Related GB2356327B (en) 1997-12-05 1998-10-05 Integrated information communication system
GB9920086A Expired - Fee Related GB2338876B (en) 1997-12-05 1998-10-05 Integrated information communication system
GB9920042A Expired - Fee Related GB2338872B (en) 1997-12-05 1998-10-05 Integrated information communication system
GB9920076A Expired - Fee Related GB2338873B (en) 1997-12-05 1998-10-05 Intergrated information communication system
GB9920084A Expired - Fee Related GB2338875B (en) 1997-12-05 1998-10-05 Integrated information communication system
GB9920079A Expired - Fee Related GB2338874B (en) 1997-12-05 1998-10-05 Integrated information communication system

Family Applications After (6)

Application Number Title Priority Date Filing Date
GB0019276A Expired - Fee Related GB2356327B (en) 1997-12-05 1998-10-05 Integrated information communication system
GB9920086A Expired - Fee Related GB2338876B (en) 1997-12-05 1998-10-05 Integrated information communication system
GB9920042A Expired - Fee Related GB2338872B (en) 1997-12-05 1998-10-05 Integrated information communication system
GB9920076A Expired - Fee Related GB2338873B (en) 1997-12-05 1998-10-05 Intergrated information communication system
GB9920084A Expired - Fee Related GB2338875B (en) 1997-12-05 1998-10-05 Integrated information communication system
GB9920079A Expired - Fee Related GB2338874B (en) 1997-12-05 1998-10-05 Integrated information communication system

Country Status (1)

Country Link
GB (7) GB2338871B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
RU2679962C1 (en) * 2018-02-20 2019-02-14 Акционерное общество "Российская корпорация ракетно-космического приборостроения и информационных систем" (АО "Российские космические системы") Method of assigning ip addresses in a personal satellite communication network on low-orbit satellites repeaters with zone registration of subscriber terminals

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1997023977A1 (en) * 1995-12-26 1997-07-03 Ntt Mobile Communications Network Inc. Mobile radio data communication system
WO1997031490A2 (en) * 1996-02-20 1997-08-28 Hewlett-Packard Company Method of accessing a target entity over a communications network
GB2320167A (en) * 1996-12-06 1998-06-10 Distrib Syst Res Inst Integrated information communications system

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR2737372B1 (en) * 1995-07-27 1997-09-12 Alexandre Serge DEVICE AND METHOD FOR INTERCONNECTING NETWORKS, IP ROUTER COMPRISING SUCH A DEVICE
US6172972B1 (en) * 1996-05-28 2001-01-09 Microsoft Corporation Multi-packet transport structure and method for sending network data over satellite network
CA2217838C (en) * 1996-11-07 2003-07-29 At&T Corp. Wan-based voice gateway

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1997023977A1 (en) * 1995-12-26 1997-07-03 Ntt Mobile Communications Network Inc. Mobile radio data communication system
WO1997031490A2 (en) * 1996-02-20 1997-08-28 Hewlett-Packard Company Method of accessing a target entity over a communications network
GB2320167A (en) * 1996-12-06 1998-06-10 Distrib Syst Res Inst Integrated information communications system

Also Published As

Publication number Publication date
GB2356327A (en) 2001-05-16
GB9920086D0 (en) 1999-10-27
GB0019276D0 (en) 2000-09-27
GB2338876B (en) 2000-08-30
GB9920084D0 (en) 1999-10-27
GB2338872B (en) 2000-08-30
GB2338874A (en) 1999-12-29
GB2338871B (en) 2000-08-30
GB9920079D0 (en) 1999-10-27
GB2338873B (en) 2000-08-30
GB2338875A (en) 1999-12-29
GB2338876A (en) 1999-12-29
GB2356327B (en) 2002-06-26
GB2338872A (en) 1999-12-29
GB2338873A (en) 1999-12-29
GB2338874B (en) 2000-08-30
GB2338875B (en) 2000-08-30
GB9920076D0 (en) 1999-10-27
GB9920042D0 (en) 1999-10-27
GB9920041D0 (en) 1999-10-27

Similar Documents

Publication Publication Date Title
CA2254045C (en) Integrated information communication system
US7869437B2 (en) Controlled transmissions across packet networks
US7433362B2 (en) System and method for SONET NSAP addressing
US8072979B2 (en) Terminal-to-terminal communication control system for IP full service
US5134610A (en) Network transit prevention
ES2285242T3 (en) CARRIER CONNECTION SIGNALING IN A DISTRIBUTED ARCHITECTURE.
GB2338871A (en) Integrated information communications system
GB2364491A (en) Integrated information communications (ICS) system
KR100204046B1 (en) Method for setting the field arameter of broadband bearer capability information factor in atm exchange system
JP3932269B2 (en) Integrated information communication system
JP3261459B2 (en) Integrated information and communication system
JP2002158717A (en) Integrated information communication system
JP2004048744A (en) Integrated information communication system

Legal Events

Date Code Title Description
732E Amendments to the register in respect of changes of name or changes affecting rights (sect. 32/1977)

Free format text: REGISTERED BETWEEN 20160915 AND 20160921

PCNP Patent ceased through non-payment of renewal fee

Effective date: 20171005