US20020085577A1 - Technique for configuring network interface circuit in integrated services digital network keyphone system - Google Patents
Technique for configuring network interface circuit in integrated services digital network keyphone system Download PDFInfo
- Publication number
- US20020085577A1 US20020085577A1 US09/033,531 US3353198A US2002085577A1 US 20020085577 A1 US20020085577 A1 US 20020085577A1 US 3353198 A US3353198 A US 3353198A US 2002085577 A1 US2002085577 A1 US 2002085577A1
- Authority
- US
- United States
- Prior art keywords
- network
- entity
- country
- code
- configuration
- 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
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q11/00—Selecting arrangements for multiplex systems
- H04Q11/04—Selecting arrangements for multiplex systems for time-division multiplexing
- H04Q11/0428—Integrated services digital network, i.e. systems for transmission of different types of digitised signals, e.g. speech, data, telecentral, television signals
- H04Q11/0435—Details
- H04Q11/0457—Connection protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q11/00—Selecting arrangements for multiplex systems
- H04Q11/04—Selecting arrangements for multiplex systems for time-division multiplexing
- H04Q11/0428—Integrated services digital network, i.e. systems for transmission of different types of digitised signals, e.g. speech, data, telecentral, television signals
- H04Q11/0435—Details
- H04Q11/0471—Terminal access circuits
Definitions
- the present invention relates to a keyphone system and, in particular, to a technique for configuring a network interface circuit for interfacing an analog keyphone system to an integrated services digital network (hereinafter, referred to as an “ISDN”).
- ISDN integrated services digital network
- the ISDN keyphone system includes a basic rate interface (hereinafter, referred to as a “BRI”) of the ISDN and a network interface circuit. Therefore, the network interface circuit is generally considered as the BRI trunk.
- BRI basic rate interface
- the BRI trunk used as a device for interfacing the analog keyphone system with the BRI performs the ISDN protocol.
- the BRI is used as an S/T interface of the basic rate interface regulated in the ISDN, that is, an interface line between the ISDN and a terminal, including 2B+D channels comprised of two B channels and one D channel.
- the B channel is used for transmission of voice and data information with the transmission rate of 64 Kbps and the D channels are used for transmission of a control signal with the transmission rate of 16 Kbps.
- a function program for supporting the ISDN protocol is installed within a read only memory (hereinafter, referred to as a ROM) located in the BRI trunk.
- a ROM read only memory
- the ISDN protocol depends upon the country or network in most cases. Therefore, when different countries or the networks operate with the ISDN keyphone system, the function program for performing the ISDN protocol by the BRI trunk of the corresponding ISDN keyphone system has to be varied accordingly, too. Consequently, it is necessary for the ROM included in the BRI trunk to contain the function program in conformity with the corresponding country or network.
- the present invention comprises a technique for configuring a network interface circuit in an integrated services digital network keyphone system, comprising the steps of: first storing beforehand in a read only memory(ROM) of the network interface circuit all function programs for supporting an integrated services digital network protocol for a country and a network which will be used by the keyphone system, selecting a function program from among the function programs stored in the ROM corresponding to the country and kind of network to be operated upon initialization, and setting the selected program, as the function program to be executed.
- ROM read only memory
- FIG. 1 is a block diagram showing the construction of a BRI trunk of an ISDN keyphone system
- FIG. 2 is a block diagram showing the construction of software for performing an ISDN protocol in the BRI trunk of an ISDN keyphone system
- FIG. 3 is a diagram showing processes of transceiving the configuration message between software modules according to an embodiment of the present invention
- FIGS. 4A and 4B are flowcharts showing processes for processing a layer management entity according to an embodiment of the present invention.
- FIGS. 5A and 5B are flowcharts showing processes for processing an application entity according to an embodiment of the present invention.
- FIG. 6 is a flowchart showing processes for processing a call control entity according to an embodiment of the present invention.
- FIG. 7 is a flowchart showing processes for processing a network signaling entity according to an embodiment of the present invention.
- FIG. 8 is a flowchart showing processes for processing a data link entity according to an embodiment of the present invention.
- FIG. 9 is a flowchart showing processes for processing a physical entity according to an embodiment of the present invention.
- FIG. 10 is a flowchart showing processes for processing a main device of a keyphone system according to an embodiment of the present invention.
- FIG. 1 is a block diagram showing the construction of a BRI trunk 100 of an ISDN keyphone system, where the BRI trunk 100 is connected between a main device 102 of the ISDN keyphone system and 4 lines BRI of the ISDN.
- the BRI trunk 100 includes a CPU (central processing unit) 104 , a ROM 106 , a random access memory (hereinafter, referred to as RAM 108 , a dual port RAM 110 , an IDEC (ISDN D-channel exchange controller) 112 , an EPIC (extended PCM interface controller) 114 , and a QUAT-S (quadruple transceiver for user/network interface-S) 116 , which is connected to the main device 102 of the keyphone system.
- a CPU central processing unit
- ROM read-only memory
- RAM 108 random access memory
- RAM 108 dual port RAM 110
- IDEC ISDN D-channel exchange controller
- EPIC extended PCM interface controller
- QUAT-S quadrature-S
- the main device 102 generally provides the overall function having the exchange service for central office and extension calls in the ISDN keyphone system.
- the CPU 104 , the ROM 106 , the RAM 108 , the dual port RAM 110 , and the IDEC 12 are connected with one another via a CPU bus 118 , and the IDEC 112 , the EPIC 114 , and the QUAT-S 116 are connected with one another via an IOM2 (ISDN-oriented modular 2) interface 120 .
- the CPU bus 118 is comprised of an address bus, a data bus, and a control bus.
- the IOM2 interface 120 used as a 4 wire serial interface is constructed with two clock lines for synchronization and two data lines.
- the data lines are composed of two B channels B 1 and B 2 , a D channel, a monitor channel of 64 Kbps, a command/indication channel of 32 Kbps, and MR and MX channels of 8 Kbps for controlling the monitor channel, for each BRI.
- the CPU 104 performs an operation depending upon the program stored in the ROM 106 .
- the CPU 104 communicates with the main device 102 of the keyphone system, performs the ISDN protocol, and provides the interface between the main device 102 of the keyphone system and the BRI of the ISDN.
- the ROM 106 stores the function program and the reference data for performance of the ISDN protocol.
- the RAM 108 temporarily stores the data in accordance with performance of the program of the CPU 104 .
- the dual port RAM 110 provides a path for communication with the main device 102 , that is, the communication between the CPU 104 and the keyphone system.
- the IDEC 112 used as the component for controlling four D channels at the same time can be for example, a PEB-2075 of the SIEMENS Ltd. company.
- the EPIC 114 used as the component for switching 32 64 Kbps channels can be a PEB-2055 of the SIEMENS Ltd. company, and connects the channel of the main device 102 with the B channel of the BRI connected to the QUAT-S 116 .
- the QUAT-S 116 used as four BRI interface component can be a PEB-2084 of the SIEMENS Ltd. company, and connects the BRI trunk 100 to the BRI as four wire ISDN physical lines.
- the BRI trunk 100 performs all of protocols related to the ISDN as mentioned previously and transceives the message necessary for performance of the ISDN protocol with the main device 102 of the keyphone system through the dual port RAM 110 .
- the software for performing the ISDN protocol by the CPU 104 includes an initial entity 200 , a layer management entity 202 , an application entity 204 , a call control entity 206 , a network signaling entity 208 , a data link entity 210 , and a physical entity 212 , as shown in FIG. 2.
- FIG. 2 is a block diagram showing the construction of a software for performing the ISDN protocol in the BRI trunk of an ISDN keyphone system. Also, in FIG. 2, the program is divided by the software modules according to the nature of the job and each module is called an entity. The entities are performed by the CPU 104 and the arrows connecting entities comprise the message flow between entities.
- the initialization entity 200 among these entities is the module which is firstly performed after resetting the BRI trunk 100 or power on resetting the keyphone system.
- the initialization entity 200 sets all kinds of initial values of the system and transmits the configuration start message to perform the configuration for each layer, to the layer management entity 202 .
- the layer management entity 202 is the module for managing all of the entities, namely, the application entity 204 , the call control entity 206 , the network signaling entity 208 , the data link entity 210 , and the physical entity 212 .
- the layer management entity 202 performs the configuration for each layer and manages the significant event influenced by the other entities among the events generated at each entity. As an example of the event, there is often generated line damage at the physical entity 212 .
- the application entity 204 is the module for transceiving the message with the main device 102 of the keyphone system as shown in FIG. 1.
- the application entity 204 changes the message received from the main device 102 of the keyphone system into the message format processed by the call control entity 206 , transmits the changed message, changes the message received from the call control entity 206 into the message format processed by the main device 102 of the keyphone system and transmits the changed message.
- the call control entity 206 is the module for managing the call and interfacing with the application entity 204 .
- the call control entity 206 receives the message related to the performance of the user from the application entity 204 , makes the message conform with the currently-selected ISDN protocol, and transmits the message to the network signaling entity 208 .
- the call control entity 206 checks whether or not the received message conforms with the selected message, and transmits the checked result to the application entity 204 .
- the call control entity 206 When a response for transmitting the message to the network is required, the call control entity 206 generates the response message and transmits the generated message to the network signaling entity 208 .
- the network signaling entity 208 is the module for performing the D channel signaling protocol.
- the network signaling entity 208 checks whether or not the message received from the data link entity 210 conforms with the selected message, and transmits the checked result to the call control entity 206 .
- the network signaling network 208 generates the message requiring the transmission from the call control entity 206 to the network, in accordance with the currently-selected ISDN protocol and transmits the generated message to the data link entity 210 .
- the data link entity 210 is the module for performing an LAPD (link access procedure on D channel) protocol or an LAPB (link access procedure on B channel) protocol, and selects the LAPD or the LAPB depending upon its configuration.
- the data link entity 210 receives the message for transmission from the network signaling entity 208 , generates the message in conformity with the format of the currently-selected ISDN protocol, and transmits the generated message to the physical entity 212 .
- the data link entity 210 checks whether or not the message received from the physical entity 212 conforms with the selected ISDN protocol and transmits the checked result to the network signaling entity 208 .
- the physical entity 212 is the module being directly connected hardwarely to the ISDN physical line, and manages the deactivation and the activation of the physical line.
- the physical entity 212 receives the message for transmission from the data link entity 210 and transmits the received message through the ISDN physical line to the HDLC (high-level data link control) frame.
- the physical entity 212 transmits the HDLC frames received from the ISDN physical line to the data link entity 210 .
- the present invention can commonly use the ISDN protocol for all countries or networks with only one BRI trunk.
- the present invention previously stores the function program for supporting the ISDN protocol for the expected country or network which will be used by the ISDN keyphone system, in the ROM 106 of the BRI trunk 100 .
- the present invention beforehand makes the list for the start addresses for each function program as an all function list table and stores the all function list table in the ROM 106 .
- the function program stored in the ROM 106 is equal to the conventional function program for supporting the corresponding ISDN protocol.
- the present invention beforehand makes the kind of countries and networks applicable to the ISDN protocol by the function program stored in the ROM 106 , namely, the list of the country codes and the network codes form the country-network list table and the table is stored in the ROM 106 .
- the CPU 104 of the BRI trunk 100 performs the configuration operation according to the configuration message transceiving procedure of FIG. 3 according to an embodiment of the present invention, receives the information for the countries and kinds of networks to be currently operated from the main device 102 of the keyphone system and forms the execution function table.
- the main device 102 of the keyphone system transmits the information for the countries and kinds of networks to be currently operated, to the BRI trunk 100 .
- the execution function table is comprised of the start address list of the function program corresponding to the countries and the networks to be currently operated by the function program belonging to the all function list table.
- the countries and kinds of networks to be currently operated means the kind of ISDN installed and connected currently to the ISDN keyphone system.
- the BRI trunk 110 can provide normal services by performing the ISDN protocol according to the countries and kinds of networks to be currently operated by the execution function program depending upon the execution function table formed as stated above. Accordingly, even in the case that the country and the network are varied by making the execution function table with selecting the function program according to the countries and the networks to be currently operated, from the all configuration function list upon initialization, the present invention has no need to replace the ROM 106 of the BRI trunk 100 with a new ROM.
- FIG. 3 is a diagram showing processes of transceiving the configuration message between software modules according to an embodiment of the present invention, which shows the kind and the transmission direction of the message transmitted according to an embodiment of the present invention between the main device 102 of the keyphone system and the entities as depicted in FIG. 2 performed in the CPU 104 of the BRI trunk 100 as illustrated in FIG. 1.
- the arrows connected between the entities indicate the transmission direction of the message, and reference numerals MSG 1 to MSG 16 at each arrow indicate message generation order.
- the procedure of processing the message generation orders MSG 1 to MSG 16 is called a “configuration procedure”.
- each message transmitted between the entities is for convenience of explanation, explained by referring to the corresponding order of the message generation orders MSG 1 to MSG 16 . Furthermore, the transmission of the message between the entities is performed for itself by the CPU 104 and the transmission of the message between the application entity 302 and the main device 102 of the keyphone system is performed by the dual port RAM 110 .
- FIGS. 4 A- 4 B and 9 are flowcharts showing processes for processing entities for performance of the configuration procedure according to an embodiment of the present invention
- FIG. 10 is a flowchart showing processes for processing the main device 102 of the keyphone system according to an embodiment of the present invention.
- FIG. 4 is divided into FIGS. 4A and 4B and FIG. 5 is divided into FIGS. 5A and 5B.
- FIG. 4A is followed by FIG. 4B and FIG. 5A is followed by FIG. 5B.
- FIGS. 4A and 4B are flowcharts showing processes for processing the layer management entity according to an embodiment of the present invention
- FIGS. 5A and 5B are flowcharts showing processes for processing the application entity according to an embodiment of the present invention.
- the CPU 104 starts the configuration procedure from the layer management entity 300 , that is, checks at step 400 of FIG. 4A whether or not the configuration start message has been received from the main device 102 of the keyphone system.
- the layer management entity 300 starts the configuration procedure according to an embodiment of the present invention by receiving the configuration start message to perform the configuration for each layer from the initial entity 100 as shown in FIG. 2 where the initial values necessary for the system are set to general initialization. Firstly, when the configuration start message is received, the layer management entity 300 performs step 402 . However, when other messages except for the configuration start message have been received at step 400 , the layer management entity 300 performs a corresponding routine.
- the layer management entity 300 transmits the configuration request message MSG 1 including the application configuration data to the application entity 302 .
- the application configuration data indicates ID(identification) representing the specific countries and kinds of networks preset as the default value, that is, the country codes and the network codes.
- the configuration request message MSG 1 is the message requesting the application entity 302 to perform the configuration procedure.
- the layer management entity 300 at step 404 checks whether or not the configuration checking message MSG 6 has been received from the application entity 302 .
- the application entity 302 checks at step 500 of FIG. 5A whether or not the configuration request message MSG 1 has been received from the layer management entity 300 and, when the configuration request message MSG 1 has been received therefrom, starts the configuration procedure at step 502 .
- the application entity 302 performs the corresponding routine, conventionally.
- the application entity 302 receiving the configuration request message MSG 1 at step 500 transmits the restart request message MSG 2 to the main device 102 of the keyphone system at step 502 .
- the restart request message MSG 2 is the message requesting the main device 102 of the keyphone system to start the new configuration procedure.
- the application entity 302 checks at step 504 , whether or not a parameter setting request message MSG 3 has been received from the main device 102 of the keyphone system.
- the main device 102 of the keyphone system starts the configuration procedure by receiving the restart request message MSG 2 from the application entity 302 of the BRI trunk 100 at step 1000 of FIG. 10.
- the main device 102 of the keyphone system performs the corresponding routine, conventionally.
- the main device 102 of the keyphone system which receives the restart request message MSG 2 at step 1000 , transmits the parameter setting request message MSG 3 included in the parameter values as the country code and the network code set at the keyphone system by the operator of the keyphone system, to the BRI trunk 100 at step 1002 .
- the parameter setting request message MSG 3 is the message which requests the BRI trunk 100 to set the parameters set at the keyphone system by the operator.
- the main device 102 of the keyphone system checks at step 1004 , whether or not a parameter setting check message MSG 4 is received from the BRI trunk 100 .
- the application entity 302 Upon the application entity 302 receiving the parameter setting request message MSG 3 from the main device 102 of the keyphone system at step 504 , the application entity 302 checks whether or not the country code and the network code of the parameter values included in the parameter setting request message MSG 3 exist in the country-network list table stored in the ROM 106 . At this point, when other messages except for the parameter setting request message have been received at step 504 , the application entity 302 ignores the received message. Also, the application entity 302 transmits the parameter setting check message MSG 4 to the main device 102 of the keyphone system according to the checked result at step 506 , and at steps 508 and 510 .
- the application entity 302 indicates the result value as being “OK”, includes the values in the parameter setting check message MSG 4 , and transmits it to the main device 102 of the keyphone system at step 510 .
- the parameter setting check message MSG 4 is the message for informing the checked result for the parameter setting request, and “OK” indicates that the country code and the network code set in the keyphone system by the operator are correctly set.
- the application entity 302 When the country code and the network code of the parameter values included in the parameter setting request message MSG 3 do not exist in the country-network list table, the application entity 302 indicates the result value as being “NOK”, includes all of the country codes and the network codes existing in the country-network list table stored in the ROM 106 , in the parameter setting check message MSG 4 , and transmits it to the main device 102 of the keyphone system.
- the “NOK” indicates that the country code and the network code set in the keyphone system by the operator are incorrectly set.
- the application entity 302 includes all of the country codes and the network codes in the parameter setting check message MSG 4 existing in the country-network list table so as to set the message correctly and transmit it.
- the application entity 302 checks at step 512 , whether or not an initialization request message MSG 5 has been received from the main device 102 of the keyphone system. Unlike this, when the result value transmitted by being included in the parameter setting check message MSG 4 is “NOK”, the application entity 302 proceeds to step 504 , thereby checking whether or not the parameter setting request message MSG 3 has again been received from the main device 102 of the keyphone system.
- the main device 102 of the keyphone system When the main device 102 of the keyphone system receives the parameter setting check message MSG 4 from the BRI trunk 100 in step 1004 of FIG. 10, the main device 102 of the keyphone system checks at step 1006 whether or not the result value included in the parameter setting check message MSG 4 is “OK” at step 1006 . At this event, once other messages except for the parameter setting check message MSG 4 have been received in step 1004 , the main device 102 of the keyphone system ignores the received message.
- the main device 102 of the keyphone system displays the country code and the network code included in the content of the parameter setting check message MSG 4 to be seen by the operator and again sets the country code and the network code selected by the operator of the keyphone system at step 1008 .
- the operator of the keyphone system checks all of the country codes and the network codes applicable at the BRI trunk 100 , again selects and sets the right country code and the right network code. After setting the country code and the network code, the main device 102 of the keyphone system performs step 1002 once more.
- the main device 102 of the keyphone system again transmits the parameter setting request message MSG 3 including the newly-set country code and network code to the BRI trunk 100 and the application entity 302 of the BRI trunk 100 again performs steps 504 to 506 in response to the transmitted message.
- the main device 102 of the keyphone system transmit the initialization request message MSG 5 including the country code and the network code included in the parameter setting request message MSG 3 to the BRI trunk 100 at step 1010 .
- the initialization request message MSG 5 is for the message requesting initialization of the BRI trunk 100 so as to perform the ISDN protocol corresponding to the country code and the network code included in the parameter setting request message MSG 3 .
- the main device 102 of the keyphone system checks at step 1012 whether or not an initialization check message MSG 16 has been received from the BRI trunk 100 .
- step 514 of FIG. 5B When the application entity 302 received the initialization request message MSG 5 from the main device 102 of the keyphone system at step 512 , the application entity 302 performs step 514 of FIG. 5B. In this case, when other messages except for the initialization request message MSG 5 have been received at step 512 , the application entity 302 ignores the received message. Also, the application entity 302 changes the country code and the network code of the application configuration data into the country code and the network code included in the initialization request message MSG 5 and stores the changed message in step 514 .
- the application entity 302 includes the changed country code and network code in the configuration check message MSG 6 with the application state value indicated as “OK” and transmits the included country code and network code to the layer management entity 300 at step 516 .
- the configuration check message MSG 6 is the message which informs the layer management entity 300 of the completion of the configuration procedure by the application entity 302 .
- the transmission of the application state value as “OK”, means that the configuration procedure of the application entity 302 has been normally completed.
- the application entity 302 checks at step 518 whether or not an all configuration check message MSG 15 has been received from the layer management entity 300 .
- the layer management entity 300 Upon the layer management entity 300 receiving the configuration check message MSG 6 from the application entity 302 at step 404 , the layer management entity 302 stores the application state value included in the configuration check message MSG 6 , and the country code and the network code of the application configuration data at step 406 . At this point, when other messages except for the configuration check message MSG 6 have been received, the layer management entity 300 ignores the received message. Hereinafter, the layer management entity 300 performs steps 408 to 430 , thereby enabling the call control entity 304 , the network signaling entity 306 , the data link entity 308 , and the physical entity 310 to perform the configuration procedure sequentially.
- the layer management entity 300 transmits the configuration request message MSG 7 including the country code and the network code of the application configuration data included in the configuration check message MSG 6 to the call control entity 304 .
- the configuration request message MSG 7 requests the configuration procedure performance to the call control entity 304 .
- the layer management entity 300 checks at step 410 whether or not a configuration check message MSG 8 has been received from the call control entity 304 .
- the call control entity 304 starts the configuration procedure from step 602 by receiving the configuration request message MSG 7 from the layer management entity 300 at step 600 of FIG. 6. In this instance, in the case that other messages except for the configuration request message MSG 7 have been received in step 600 , the call control entity 304 performs the corresponding routine. However, at step 602 , the call control entity 304 which receives the configuration request message MSG 7 , performs the configuration by forming the execution function table using the country code and the network code in the content of the configuration request message MSG 7 .
- the call control entity 304 forms the country code and the network code included in the configuration request message MSG 7 among the function programs existing in the all function list table stored in the ROM 106 , that is, the start address list of the function program corresponding to the country and the network to be currently operated, as the execution function table.
- the call control entity 304 selects the function program corresponding to the country and the network to be currently operated among the function program stored at the ROM 106 and sets the execution function program. Accordingly, the call control entity 304 can perform the ISDN protocol according to the country and the network to be currently operated by the function program depending upon the execution function table formed as stated above.
- the call control entity 304 sets the call control state value to “OK” and transmits the configuration check message MSG 8 to the layer management entity 300 , so that the configuration procedure can be completed.
- the configuration check message MSG 8 is the message for informing the layer management entity 300 of the completion of the configuration procedure. Also, the transmission of the call control value as “OK” represents that the configuration procedure of the call control entity 304 has been completed.
- the layer management entity 300 When the layer management entity 300 receives the configuration check message MSG 8 from the call control entity 304 at step 410 , the layer management entity 300 performs step 414 after storing the call control state value included in the configuration check message MSG 8 at step 412 . At this point, in the event that other messages except for the configuration check message MSG 8 have been received therefrom, the layer management entity 302 ignores the received message. Thus, at step 414 , the layer management entity 300 transmits the configuration request message MSG 9 including the country code and the network code of the application configuration data included in the configuration check message MSG 6 to the network signaling entity 306 . The configuration request message MSG 9 is the message requesting the configuration procedure performance to the network signaling entity 306 . Thereafter, the layer management entity 300 checks at step 416 , whether or not the configuration check message MSG 10 has been received from the network signaling entity 306 .
- the network signaling entity 306 starts the configuration procedure from step 702 by receiving the configuration request message MSG 9 from the layer management entity 300 at step 700 of FIG. 7.
- the network signaling entity 306 performs the corresponding routine.
- the network signaling entity 304 receiving the configuration request message MSG 9 in the above step 700 , performs the configuration by forming the execution function table using the country code and the network code in the content of the configuration request message MSG.
- the network signaling entity 306 forms the country code and the network code included in the configuration request message MSG 9 among the function programs existing in the all function list table stored in the ROM 106 , that is, the start address list of the function program corresponding to the country and the network to be currently operated by the network signaling entity 306 , as the execution function table.
- the network signaling entity 306 selects the function program corresponding to the country and the network to be currently operated from among the function programs stored in the ROM 106 and sets the execution function program. Accordingly, the network signaling entity 306 can perform the ISDN protocol according to the country and the network to be currently operated by the function program depending upon the execution function table formed as stated above.
- the network signaling entity 306 sets the network signaling state value to “OK” and transmits the configuration check message MSG 10 to the layer management entity 300 , so that the configuration procedure can be completed.
- the configuration check message MSG 10 is the message for informing the layer management entity 300 of the completion of the configuration procedure by the network signaling entity 306 . Also, the transmission of the network signaling “OK” value represents that the configuration procedure of the network signaling entity 306 has been completed.
- the layer management entity 300 When the layer management entity 300 receives the configuration check message MSG 10 from the network signaling entity 306 , the layer management entity 300 performs step 420 after storing the network signaling state value included in the configuration check message MSG 10 at step 418 of FIG. 4B. At this point, in the event that other messages except for the configuration check message MSG 10 have been received therefrom, the layer management entity 300 ignores the received message. Thus, at step 420 , the layer management entity 300 transmits the configuration request message MSG 11 including the country code and the network code of the application configuration data included in the configuration check message MSG 6 to the data link entity 308 . The configuration request message MSG 11 is the message requesting the configuration procedure performance to the data link entity 308 . Thereafter, the layer management entity 300 checks at step 422 , whether or not the configuration check message MSG 12 has been received from the data link entity 308 .
- the data link entity 308 starts the configuration procedure from step 802 by receiving the configuration request message MSG 11 from the layer management entity 300 at step 800 of FIG. 8.
- the data link entity 308 performs the corresponding routine.
- the data link entity 308 receiving the configuration request message MSG 11 at step 800 performs the configuration by forming the execution function table using the country code and the network code in the content of the configuration request message MSG 11 .
- the data link entity 308 forms the country code and the network code included in the configuration request message MSG 11 from among the function programs existing in the all function list table stored in the ROM 106 , that is, the start address list of the function program corresponding to the country and the network to be currently operated, as the execution function table.
- the data link entity 308 selects the function program corresponding to the country and the network to be currently operated from among the function programs stored in the ROM 106 and sets the execution function program. Accordingly, the data link entity 308 can perform the ISDN protocol according to the country and the network to be currently operated by the function program depending upon the execution function table formed as stated above.
- the network signaling entity 306 sets the data link state value to “OK” and transmits the configuration check message MSG 12 to the layer management entity 300 , so that the configuration procedure can be completed.
- the configuration check message MSG 12 is the message for informing the layer management entity 300 of the completion of the configuration procedure by the data link entity 308 . Also, the transmission of the data link value as “OK” represents that the configuration procedure of the data link entity 308 has been completed.
- the layer management entity 300 Upon the layer management entity 300 receiving the configuration check message MSG 12 from the data link entity 308 at step 422 , the layer management entity 300 performs step 426 after storing the data link state value included in the configuration check message MSG 12 at step 424 . At this point, in the event that other messages except for the configuration check message MSG 12 have been received therefrom, the layer management entity 300 ignores the received message. Thus, at step 426 , the layer management entity 300 transmits the configuration request message MSG 13 including the country code and the network code of the application configuration data included in the configuration check message MSG 6 , to the physical entity 310 . The configuration request message MSG 13 is the message requesting the configuration procedure performance to the physical entity 310 . Thereafter, the layer management entity 300 checks at step 428 , whether or not the configuration check message MSG 14 has been received from the physical entity 310 .
- the physical entity 310 starts the configuration procedure from step 902 by receiving the configuration request message MSG 13 from the layer management entity 300 at step 900 of FIG. 9.
- the physical entity 310 performs the corresponding routine.
- the physical entity 310 receiving the configuration request message MSG 13 at step 900 performs the configuration by forming the execution function table using the country code and the network code in the content of the configuration request message MSG 13 .
- the physical entity 310 forms the country code and the network code included in the configuration request message MSG 13 from among the function programs existing in the all function list table stored in the ROM 106 , that is, the start address list of the function program corresponding to the country and the network to be currently operated, as the execution function table.
- the physical entity 310 selects the function program corresponding to the country and the network to be currently operated from among the function programs stored in the ROM 106 and sets the execution function program. Accordingly, the physical entity 310 can perform the ISDN protocol according to the country and the network to be currently operated by the function program depending upon the execution function table formed as stated above.
- the physical entity 310 sets the data link state value to “OK” and transmits the configuration check message MSG 14 to the layer management entity 300 , so that the configuration procedure can be completed.
- the configuration check message MSG 14 is the message for informing the layer management entity 300 of the completion of the configuration procedure by the physical entity 310 . Also, the transmission of the data link value as “OK” represents that the configuration procedure of the physical entity 310 has been completed.
- the layer management entity 300 Upon the layer management entity 300 receiving the configuration check message MSG 14 from the physical entity 310 at step 428 , the layer management entity 300 performs step 432 after storing the physical state value included in the configuration check message MSG 14 at step 430 . At this point, in the event that other messages except for the configuration check message MSG 14 have been received therefrom, the layer management entity 300 ignores the received message. Thus, at the above step 432 , the layer management entity 300 ends the configuration procedure by transmitting the all configuration check message MSG 15 having the configuration state of all entities, that is, the information such as the application state value, the call control state value, the network signaling state value, the data fink state value, and the physical state value, to the application entity 302 .
- the all configuration check message MSG 15 is the message informing the completion of the configuration state of all entities.
- the application entity 302 completes the configuration procedure by transmitting the initialization check message MSG 16 having the configuration state of all entities included in the all configuration check message MSG 15 , to the main device 102 of the keyphone system at step 520 .
- the application entity 302 ignores the received message.
- the initialization check message MSG 16 represents the completion of the configuration operation in order to perform the ISDN protocol for the country and the network to be currently operated by the BRI trunk 100 , that is, to perform all of entities for the ISDN protocol.
- the BRI trunk 100 performs the normal operation. That is, the BRI trunk 100 can provides normal service by performing the ISDN protocol according to the country and the network to be currently operated by the function program as the execution function table formed by the configuration procedure as stated above.
- the main device 102 of the keyphone system upon the main device 102 of the keyphone system receiving the initialization check message MSG 16 at step 1012 , the main device 102 of the keyphone system completes the configuration procedure after storing the country code and the network code set by the operator at step 1014 . Namely, the main device 102 of the keyphone system stores the country code and the network code as the currently-operated country code and network code with the above configuration order.
- the main device 102 of the keyphone system ignores the received message.
- the present invention has no need to replace the ROM storing the program for performance of the ISDN protocol with the new ROM whenever the country and the network are varied by commonly using one BRI trunk for all countries and networks which have ISDN protocols different from one another.
Abstract
Description
- This application makes reference to, incorporates the same herein, and claims all benefits accruing under 35 U.S.C. §119 from an application for METHOD FOR CONFIGURING NETWORK INTERFACE CIRCUIT IN INTEGRATED SERVICES DIGITAL NETWORK KEYPHONE SYSTEM earlier filed in the Korean Industrial Property Office on the Feb. 28, 1997 and there duly assigned Serial No. 6551/1997.
- 1. Field of the Invention
- The present invention relates to a keyphone system and, in particular, to a technique for configuring a network interface circuit for interfacing an analog keyphone system to an integrated services digital network (hereinafter, referred to as an “ISDN”).
- 2. Description of the Related Art
- While a typical keyphone system has been used by being interfaced with a public switched telephone network (hereinafter, referred to as a PSTN), it has also been recently used with an ISDN. Herein, the keyphone system being interfaced with the ISDN is conventionally called an ISDN keyphone system. The ISDN keyphone system includes a basic rate interface (hereinafter, referred to as a “BRI”) of the ISDN and a network interface circuit. Therefore, the network interface circuit is generally considered as the BRI trunk.
- The BRI trunk used as a device for interfacing the analog keyphone system with the BRI, performs the ISDN protocol. Also, the BRI is used as an S/T interface of the basic rate interface regulated in the ISDN, that is, an interface line between the ISDN and a terminal, including 2B+D channels comprised of two B channels and one D channel. The B channel is used for transmission of voice and data information with the transmission rate of 64 Kbps and the D channels are used for transmission of a control signal with the transmission rate of 16 Kbps. In this BRI trunk, a function program for supporting the ISDN protocol is installed within a read only memory (hereinafter, referred to as a ROM) located in the BRI trunk.
- Meanwhile, the ISDN protocol depends upon the country or network in most cases. Therefore, when different countries or the networks operate with the ISDN keyphone system, the function program for performing the ISDN protocol by the BRI trunk of the corresponding ISDN keyphone system has to be varied accordingly, too. Consequently, it is necessary for the ROM included in the BRI trunk to contain the function program in conformity with the corresponding country or network.
- As stated hereinafter, since the function program for performing the ISDN protocol for a specific country or a specific network is included in the ROM of the BRI trunk, there is a problem in that the ROM included in the BRI trunk must be replaced with a new ROM in conformity with the corresponding country or network whenever the country or network used by the keyphone system is changed.
- The following patents each disclose features in common with the present invention but do not teach or suggest the specifically recited technique for configuring a network interface circuit in an integrated services digital network keyphone system of the present invention: U.S. Pat. No. 5,666,349 to Petri entitled Method For Controlling Components Of A Communication System, U.S. Pat. No. 5,442,630 to Gagliardi et al., entitled ISDN Interfacing Of Local Area Networks, U.S. Pat. No. 5,574,861 to Lorvig et al., entitled Dynamic Allocation Of B-Channels In ISDN, U.S. Pat. No. 5,481,598 to Bergler et al., entitled Subscriber Terminal For ISDN Network, U.S. Pat. No. 5,070,524 to Mano, entitled Telephone System, U.S. Pat. No. 5,617,630 to Feinberg et al., entitled Interface For A Data Telephone And Data Terminal In A Digital Telephone System, U.S. Pat. No. 5,655,001 to Cline et al, entitled Wireless Telecommunication System Using Protocol Conversion For Signaling Between Base Stations And Land Based Switches, U.S. Pat. No. 5,062,108 to Bales et al., entitled ISDN Codeset Conversion, U.S. Pat. No. 5,239,542 to Breidenstein et al, entitled Time Division Multiplex Switching System For Interconnecting Telephone Circuits Which Operate In Accordance With Different Signaling Systems And Call Formats, U.S. Pat. No. 5,278,972 to Baker et al., entitled Communication System For Converting ISDN Signaling Protocol Between Local And Public Network Having First Group Of Mandatory Elements And Second Group Of Non-Mandatory Elements, U.S. Pat. No.5,412,660 to Chen et al., entitled ISDN-To ISDN Communication Via Satellite Microwave Radio Frequency Communications Link, and U.S. Pat. No. 5,652,782 to Hughes-Hartogs, entitled Digital Telephone Overcoming International Incompatibilities.
- It is an object of the present invention to provide a technique for configuring a network interface circuit capable of being commonly used in all countries or networks which have different ISDN protocols, with only one BRI trunk.
- In order to achieve the above object, the present invention comprises a technique for configuring a network interface circuit in an integrated services digital network keyphone system, comprising the steps of: first storing beforehand in a read only memory(ROM) of the network interface circuit all function programs for supporting an integrated services digital network protocol for a country and a network which will be used by the keyphone system, selecting a function program from among the function programs stored in the ROM corresponding to the country and kind of network to be operated upon initialization, and setting the selected program, as the function program to be executed.
- A more complete appreciation of this invention, and many of the attendant advantages thereof, will be readily apparent as the same becomes better understood by reference to the following detailed description when considered in conjunction with the accompanying drawings, in which like reference symbols indicate the same or similar components, wherein:
- FIG. 1 is a block diagram showing the construction of a BRI trunk of an ISDN keyphone system;
- FIG. 2 is a block diagram showing the construction of software for performing an ISDN protocol in the BRI trunk of an ISDN keyphone system;
- FIG. 3 is a diagram showing processes of transceiving the configuration message between software modules according to an embodiment of the present invention;
- FIGS. 4A and 4B are flowcharts showing processes for processing a layer management entity according to an embodiment of the present invention;
- FIGS. 5A and 5B are flowcharts showing processes for processing an application entity according to an embodiment of the present invention;
- FIG. 6 is a flowchart showing processes for processing a call control entity according to an embodiment of the present invention;
- FIG. 7 is a flowchart showing processes for processing a network signaling entity according to an embodiment of the present invention;
- FIG. 8 is a flowchart showing processes for processing a data link entity according to an embodiment of the present invention;
- FIG. 9 is a flowchart showing processes for processing a physical entity according to an embodiment of the present invention; and
- FIG. 10 is a flowchart showing processes for processing a main device of a keyphone system according to an embodiment of the present invention.
- Hereinafter, a preferred embodiment of the present invention will be concretely explained with reference with accompanying drawings. Most of all, throughout the drawings, it is noted that the same reference numerals or letters will be used to designate like or equivalent elements having the same function. Further, in the following description, numerous specific details such as concrete components composing the circuitry and the frequencies, are set forth to provide a more thorough understanding of the present invention. It will be apparent, however, to one skilled in the art that the present invention may be practiced without these specific details. A detailed description of known functions and constructions unnecessarily obscuring the subject matter of the present invention has been omitted in the following description.
- FIG. 1 is a block diagram showing the construction of a
BRI trunk 100 of an ISDN keyphone system, where the BRItrunk 100 is connected between amain device 102 of the ISDN keyphone system and 4 lines BRI of the ISDN. The BRItrunk 100 includes a CPU (central processing unit) 104, aROM 106, a random access memory (hereinafter, referred to asRAM 108, adual port RAM 110, an IDEC (ISDN D-channel exchange controller) 112, an EPIC (extended PCM interface controller) 114, and a QUAT-S (quadruple transceiver for user/network interface-S) 116, which is connected to themain device 102 of the keyphone system. Therein, themain device 102 generally provides the overall function having the exchange service for central office and extension calls in the ISDN keyphone system. TheCPU 104, theROM 106, theRAM 108, thedual port RAM 110, and the IDEC 12 are connected with one another via aCPU bus 118, and the IDEC 112, the EPIC 114, and the QUAT-S 116 are connected with one another via an IOM2 (ISDN-oriented modular 2)interface 120. TheCPU bus 118 is comprised of an address bus, a data bus, and a control bus. TheIOM2 interface 120 used as a 4 wire serial interface is constructed with two clock lines for synchronization and two data lines. The data lines are composed of two B channels B1 and B2, a D channel, a monitor channel of 64 Kbps, a command/indication channel of 32 Kbps, and MR and MX channels of 8 Kbps for controlling the monitor channel, for each BRI. - The
CPU 104 performs an operation depending upon the program stored in theROM 106. TheCPU 104 communicates with themain device 102 of the keyphone system, performs the ISDN protocol, and provides the interface between themain device 102 of the keyphone system and the BRI of the ISDN. TheROM 106 stores the function program and the reference data for performance of the ISDN protocol. TheRAM 108 temporarily stores the data in accordance with performance of the program of theCPU 104. Thedual port RAM 110 provides a path for communication with themain device 102, that is, the communication between theCPU 104 and the keyphone system. TheIDEC 112 used as the component for controlling four D channels at the same time, can be for example, a PEB-2075 of the SIEMENS Ltd. company. TheEPIC 114 used as the component for switching 32 64 Kbps channels, for example, can be a PEB-2055 of the SIEMENS Ltd. company, and connects the channel of themain device 102 with the B channel of the BRI connected to the QUAT-S 116. The QUAT-S 116 used as four BRI interface component, can be a PEB-2084 of the SIEMENS Ltd. company, and connects theBRI trunk 100 to the BRI as four wire ISDN physical lines. TheBRI trunk 100 performs all of protocols related to the ISDN as mentioned previously and transceives the message necessary for performance of the ISDN protocol with themain device 102 of the keyphone system through thedual port RAM 110. - In the
BRI trunk 100, the software for performing the ISDN protocol by theCPU 104 includes aninitial entity 200, alayer management entity 202, anapplication entity 204, acall control entity 206, anetwork signaling entity 208, adata link entity 210, and aphysical entity 212, as shown in FIG. 2. FIG. 2 is a block diagram showing the construction of a software for performing the ISDN protocol in the BRI trunk of an ISDN keyphone system. Also, in FIG. 2, the program is divided by the software modules according to the nature of the job and each module is called an entity. The entities are performed by theCPU 104 and the arrows connecting entities comprise the message flow between entities. - The
initialization entity 200 among these entities is the module which is firstly performed after resetting theBRI trunk 100 or power on resetting the keyphone system. Theinitialization entity 200 sets all kinds of initial values of the system and transmits the configuration start message to perform the configuration for each layer, to thelayer management entity 202. - The
layer management entity 202 is the module for managing all of the entities, namely, theapplication entity 204, thecall control entity 206, thenetwork signaling entity 208, thedata link entity 210, and thephysical entity 212. Thelayer management entity 202 performs the configuration for each layer and manages the significant event influenced by the other entities among the events generated at each entity. As an example of the event, there is often generated line damage at thephysical entity 212. - The
application entity 204 is the module for transceiving the message with themain device 102 of the keyphone system as shown in FIG. 1. Theapplication entity 204 changes the message received from themain device 102 of the keyphone system into the message format processed by thecall control entity 206, transmits the changed message, changes the message received from thecall control entity 206 into the message format processed by themain device 102 of the keyphone system and transmits the changed message. - The
call control entity 206 is the module for managing the call and interfacing with theapplication entity 204. Thecall control entity 206 receives the message related to the performance of the user from theapplication entity 204, makes the message conform with the currently-selected ISDN protocol, and transmits the message to thenetwork signaling entity 208. When receiving the message from thenetwork signaling entity 208, thecall control entity 206 checks whether or not the received message conforms with the selected message, and transmits the checked result to theapplication entity 204. When a response for transmitting the message to the network is required, thecall control entity 206 generates the response message and transmits the generated message to thenetwork signaling entity 208. - The
network signaling entity 208 is the module for performing the D channel signaling protocol. Thenetwork signaling entity 208 checks whether or not the message received from thedata link entity 210 conforms with the selected message, and transmits the checked result to thecall control entity 206. Thenetwork signaling network 208 generates the message requiring the transmission from thecall control entity 206 to the network, in accordance with the currently-selected ISDN protocol and transmits the generated message to thedata link entity 210. - The
data link entity 210 is the module for performing an LAPD (link access procedure on D channel) protocol or an LAPB (link access procedure on B channel) protocol, and selects the LAPD or the LAPB depending upon its configuration. Thedata link entity 210 receives the message for transmission from thenetwork signaling entity 208, generates the message in conformity with the format of the currently-selected ISDN protocol, and transmits the generated message to thephysical entity 212. Thedata link entity 210 checks whether or not the message received from thephysical entity 212 conforms with the selected ISDN protocol and transmits the checked result to thenetwork signaling entity 208. - The
physical entity 212 is the module being directly connected hardwarely to the ISDN physical line, and manages the deactivation and the activation of the physical line. Thephysical entity 212 receives the message for transmission from thedata link entity 210 and transmits the received message through the ISDN physical line to the HDLC (high-level data link control) frame. Thephysical entity 212 transmits the HDLC frames received from the ISDN physical line to thedata link entity 210. - In the BRI trunk as described above, the present invention can commonly use the ISDN protocol for all countries or networks with only one BRI trunk. To meet it, the present invention previously stores the function program for supporting the ISDN protocol for the expected country or network which will be used by the ISDN keyphone system, in the
ROM 106 of theBRI trunk 100. At this point, the present invention beforehand makes the list for the start addresses for each function program as an all function list table and stores the all function list table in theROM 106. The function program stored in theROM 106 is equal to the conventional function program for supporting the corresponding ISDN protocol. Also, the present invention beforehand makes the kind of countries and networks applicable to the ISDN protocol by the function program stored in theROM 106, namely, the list of the country codes and the network codes form the country-network list table and the table is stored in theROM 106. - Herein, the program of the country-network list table will be given hereinafter.
construct network COUNTRY_NETWORK[]= {{EUROPE, ETSI}, {FRANCE, FT_VN3}, {UK, BT_ISDN2}, {GERMANY,DT_1TR6}, {SWEDEN, SWD_TVKT}, {BELGIUM, BG_V1),}; - In this state, during the initial operation, the
CPU 104 of theBRI trunk 100 performs the configuration operation according to the configuration message transceiving procedure of FIG. 3 according to an embodiment of the present invention, receives the information for the countries and kinds of networks to be currently operated from themain device 102 of the keyphone system and forms the execution function table. In this instance, themain device 102 of the keyphone system transmits the information for the countries and kinds of networks to be currently operated, to theBRI trunk 100. The execution function table is comprised of the start address list of the function program corresponding to the countries and the networks to be currently operated by the function program belonging to the all function list table. The countries and kinds of networks to be currently operated means the kind of ISDN installed and connected currently to the ISDN keyphone system. Thereafter, theBRI trunk 110 can provide normal services by performing the ISDN protocol according to the countries and kinds of networks to be currently operated by the execution function program depending upon the execution function table formed as stated above. Accordingly, even in the case that the country and the network are varied by making the execution function table with selecting the function program according to the countries and the networks to be currently operated, from the all configuration function list upon initialization, the present invention has no need to replace theROM 106 of theBRI trunk 100 with a new ROM. - Now, the present invention will be more concretely explained below with reference to FIGS.3 to 10.
- FIG. 3 is a diagram showing processes of transceiving the configuration message between software modules according to an embodiment of the present invention, which shows the kind and the transmission direction of the message transmitted according to an embodiment of the present invention between the
main device 102 of the keyphone system and the entities as depicted in FIG. 2 performed in theCPU 104 of theBRI trunk 100 as illustrated in FIG. 1. The arrows connected between the entities indicate the transmission direction of the message, and reference numerals MSG1 to MSG16 at each arrow indicate message generation order. The procedure of processing the message generation orders MSG1 to MSG16 is called a “configuration procedure”. Further, in following description, each message transmitted between the entities is for convenience of explanation, explained by referring to the corresponding order of the message generation orders MSG1 to MSG16. Furthermore, the transmission of the message between the entities is performed for itself by theCPU 104 and the transmission of the message between theapplication entity 302 and themain device 102 of the keyphone system is performed by thedual port RAM 110. - FIGS.4A-4B and 9 are flowcharts showing processes for processing entities for performance of the configuration procedure according to an embodiment of the present invention, and FIG. 10 is a flowchart showing processes for processing the
main device 102 of the keyphone system according to an embodiment of the present invention. Herein, for convenience, FIG. 4 is divided into FIGS. 4A and 4B and FIG. 5 is divided into FIGS. 5A and 5B. Also, FIG. 4A is followed by FIG. 4B and FIG. 5A is followed by FIG. 5B. - Therefore, FIGS. 4A and 4B are flowcharts showing processes for processing the layer management entity according to an embodiment of the present invention, and FIGS. 5A and 5B are flowcharts showing processes for processing the application entity according to an embodiment of the present invention.
- When power is applied to the keyphone system or the
BRI trunk 100 is reset, theCPU 104 starts the configuration procedure from thelayer management entity 300, that is, checks atstep 400 of FIG. 4A whether or not the configuration start message has been received from themain device 102 of the keyphone system. At this moment, thelayer management entity 300 starts the configuration procedure according to an embodiment of the present invention by receiving the configuration start message to perform the configuration for each layer from theinitial entity 100 as shown in FIG. 2 where the initial values necessary for the system are set to general initialization. Firstly, when the configuration start message is received, thelayer management entity 300 performsstep 402. However, when other messages except for the configuration start message have been received atstep 400, thelayer management entity 300 performs a corresponding routine. Thus, atstep 402, thelayer management entity 300 transmits the configuration request message MSG1 including the application configuration data to theapplication entity 302. The application configuration data indicates ID(identification) representing the specific countries and kinds of networks preset as the default value, that is, the country codes and the network codes. Also, the configuration request message MSG1 is the message requesting theapplication entity 302 to perform the configuration procedure. After that, thelayer management entity 300 atstep 404 checks whether or not the configuration checking message MSG6 has been received from theapplication entity 302. - The
application entity 302 checks atstep 500 of FIG. 5A whether or not the configuration request message MSG1 has been received from thelayer management entity 300 and, when the configuration request message MSG1 has been received therefrom, starts the configuration procedure atstep 502. When other messages except for the configuration request message MSG1 have been received atstep 500, theapplication entity 302 performs the corresponding routine, conventionally. Theapplication entity 302 receiving the configuration request message MSG1 atstep 500, transmits the restart request message MSG2 to themain device 102 of the keyphone system atstep 502. The restart request message MSG2 is the message requesting themain device 102 of the keyphone system to start the new configuration procedure. Following that, theapplication entity 302 checks atstep 504, whether or not a parameter setting request message MSG3 has been received from themain device 102 of the keyphone system. - Then, the
main device 102 of the keyphone system starts the configuration procedure by receiving the restart request message MSG2 from theapplication entity 302 of theBRI trunk 100 atstep 1000 of FIG. 10. At this time, when other messages except for the restart request message MSG2 have been received therefrom atstep 1000, themain device 102 of the keyphone system performs the corresponding routine, conventionally. Themain device 102 of the keyphone system which receives the restart request message MSG2 atstep 1000, transmits the parameter setting request message MSG3 included in the parameter values as the country code and the network code set at the keyphone system by the operator of the keyphone system, to theBRI trunk 100 atstep 1002. The parameter setting request message MSG3 is the message which requests theBRI trunk 100 to set the parameters set at the keyphone system by the operator. Hereinafter, themain device 102 of the keyphone system checks atstep 1004, whether or not a parameter setting check message MSG4 is received from theBRI trunk 100. - Upon the
application entity 302 receiving the parameter setting request message MSG3 from themain device 102 of the keyphone system atstep 504, theapplication entity 302 checks whether or not the country code and the network code of the parameter values included in the parameter setting request message MSG3 exist in the country-network list table stored in theROM 106. At this point, when other messages except for the parameter setting request message have been received atstep 504, theapplication entity 302 ignores the received message. Also, theapplication entity 302 transmits the parameter setting check message MSG4 to themain device 102 of the keyphone system according to the checked result atstep 506, and atsteps ROM 106, it means that the country code and the network code have been correctly set by the operator. However, when the country code and the network code of the parameter values included in the parameter setting request message MSG3 do not exist in the country-network list table stored at theROM 106, it means that the country code and the network code have been incorrectly set. - Moreover, when the country code and the network code of the parameter values included in the parameter setting request message MSG3 exist in the country-network list table, the
application entity 302 indicates the result value as being “OK”, includes the values in the parameter setting check message MSG4, and transmits it to themain device 102 of the keyphone system atstep 510. The parameter setting check message MSG4 is the message for informing the checked result for the parameter setting request, and “OK” indicates that the country code and the network code set in the keyphone system by the operator are correctly set. When the country code and the network code of the parameter values included in the parameter setting request message MSG3 do not exist in the country-network list table, theapplication entity 302 indicates the result value as being “NOK”, includes all of the country codes and the network codes existing in the country-network list table stored in theROM 106, in the parameter setting check message MSG4, and transmits it to themain device 102 of the keyphone system. The “NOK” indicates that the country code and the network code set in the keyphone system by the operator are incorrectly set. When the country code and the network code of the parameter values included in the parameter setting request message MSG3 do not exist at the country-network list table, it means that the codes have been incorrectly set. Accordingly, theapplication entity 302 includes all of the country codes and the network codes in the parameter setting check message MSG4 existing in the country-network list table so as to set the message correctly and transmit it. - After that, upon the result value transmitted by being included in the parameter setting check message MSG4 being “OK”, the
application entity 302 checks atstep 512, whether or not an initialization request message MSG5 has been received from themain device 102 of the keyphone system. Unlike this, when the result value transmitted by being included in the parameter setting check message MSG4 is “NOK”, theapplication entity 302 proceeds to step 504, thereby checking whether or not the parameter setting request message MSG3 has again been received from themain device 102 of the keyphone system. - When the
main device 102 of the keyphone system receives the parameter setting check message MSG4 from theBRI trunk 100 instep 1004 of FIG. 10, themain device 102 of the keyphone system checks atstep 1006 whether or not the result value included in the parameter setting check message MSG4 is “OK” atstep 1006. At this event, once other messages except for the parameter setting check message MSG4 have been received instep 1004, themain device 102 of the keyphone system ignores the received message. However, when the result value included in the parameter setting check message MSG4 is “NOK”, themain device 102 of the keyphone system displays the country code and the network code included in the content of the parameter setting check message MSG4 to be seen by the operator and again sets the country code and the network code selected by the operator of the keyphone system atstep 1008. Here, the operator of the keyphone system checks all of the country codes and the network codes applicable at theBRI trunk 100, again selects and sets the right country code and the right network code. After setting the country code and the network code, themain device 102 of the keyphone system performsstep 1002 once more. As a result, themain device 102 of the keyphone system again transmits the parameter setting request message MSG3 including the newly-set country code and network code to theBRI trunk 100 and theapplication entity 302 of theBRI trunk 100 again performssteps 504 to 506 in response to the transmitted message. - To the contrary, when the result value included in the parameter setting check message MSG4 is “OK” in
step 1006, themain device 102 of the keyphone system transmit the initialization request message MSG5 including the country code and the network code included in the parameter setting request message MSG3 to theBRI trunk 100 atstep 1010. The initialization request message MSG5 is for the message requesting initialization of theBRI trunk 100 so as to perform the ISDN protocol corresponding to the country code and the network code included in the parameter setting request message MSG3. Next, themain device 102 of the keyphone system checks atstep 1012 whether or not an initialization check message MSG16 has been received from theBRI trunk 100. - When the
application entity 302 received the initialization request message MSG5 from themain device 102 of the keyphone system atstep 512, theapplication entity 302 performsstep 514 of FIG. 5B. In this case, when other messages except for the initialization request message MSG5 have been received atstep 512, theapplication entity 302 ignores the received message. Also, theapplication entity 302 changes the country code and the network code of the application configuration data into the country code and the network code included in the initialization request message MSG5 and stores the changed message instep 514. Thereafter, theapplication entity 302 includes the changed country code and network code in the configuration check message MSG6 with the application state value indicated as “OK” and transmits the included country code and network code to thelayer management entity 300 atstep 516. The configuration check message MSG6 is the message which informs thelayer management entity 300 of the completion of the configuration procedure by theapplication entity 302. The transmission of the application state value as “OK”, means that the configuration procedure of theapplication entity 302 has been normally completed. Hereinafter, theapplication entity 302 checks atstep 518 whether or not an all configuration check message MSG15 has been received from thelayer management entity 300. - Upon the
layer management entity 300 receiving the configuration check message MSG6 from theapplication entity 302 atstep 404, thelayer management entity 302 stores the application state value included in the configuration check message MSG6, and the country code and the network code of the application configuration data atstep 406. At this point, when other messages except for the configuration check message MSG6 have been received, thelayer management entity 300 ignores the received message. Hereinafter, thelayer management entity 300 performssteps 408 to 430, thereby enabling thecall control entity 304, thenetwork signaling entity 306, thedata link entity 308, and thephysical entity 310 to perform the configuration procedure sequentially. Atstep 408, thelayer management entity 300 transmits the configuration request message MSG7 including the country code and the network code of the application configuration data included in the configuration check message MSG6 to thecall control entity 304. The configuration request message MSG7 requests the configuration procedure performance to thecall control entity 304. After that, thelayer management entity 300 checks atstep 410 whether or not a configuration check message MSG8 has been received from thecall control entity 304. - Thus, the
call control entity 304 starts the configuration procedure fromstep 602 by receiving the configuration request message MSG7 from thelayer management entity 300 atstep 600 of FIG. 6. In this instance, in the case that other messages except for the configuration request message MSG7 have been received instep 600, thecall control entity 304 performs the corresponding routine. However, atstep 602, thecall control entity 304 which receives the configuration request message MSG7, performs the configuration by forming the execution function table using the country code and the network code in the content of the configuration request message MSG7. At this case, thecall control entity 304 forms the country code and the network code included in the configuration request message MSG7 among the function programs existing in the all function list table stored in theROM 106, that is, the start address list of the function program corresponding to the country and the network to be currently operated, as the execution function table. In other words, thecall control entity 304 selects the function program corresponding to the country and the network to be currently operated among the function program stored at theROM 106 and sets the execution function program. Accordingly, thecall control entity 304 can perform the ISDN protocol according to the country and the network to be currently operated by the function program depending upon the execution function table formed as stated above. After that, thecall control entity 304 sets the call control state value to “OK” and transmits the configuration check message MSG8 to thelayer management entity 300, so that the configuration procedure can be completed. Here, the configuration check message MSG8 is the message for informing thelayer management entity 300 of the completion of the configuration procedure. Also, the transmission of the call control value as “OK” represents that the configuration procedure of thecall control entity 304 has been completed. - When the
layer management entity 300 receives the configuration check message MSG8 from thecall control entity 304 atstep 410, thelayer management entity 300 performsstep 414 after storing the call control state value included in the configuration check message MSG8 atstep 412. At this point, in the event that other messages except for the configuration check message MSG8 have been received therefrom, thelayer management entity 302 ignores the received message. Thus, atstep 414, thelayer management entity 300 transmits the configuration request message MSG9 including the country code and the network code of the application configuration data included in the configuration check message MSG6 to thenetwork signaling entity 306. The configuration request message MSG9 is the message requesting the configuration procedure performance to thenetwork signaling entity 306. Thereafter, thelayer management entity 300 checks atstep 416, whether or not the configuration check message MSG10 has been received from thenetwork signaling entity 306. - Then, the
network signaling entity 306 starts the configuration procedure fromstep 702 by receiving the configuration request message MSG9 from thelayer management entity 300 atstep 700 of FIG. 7. In this instance, in the case that other messages except for the configuration request message MSG9 have been received atstep 700, thenetwork signaling entity 306 performs the corresponding routine. However, atstep 702, thenetwork signaling entity 304 receiving the configuration request message MSG9 in theabove step 700, performs the configuration by forming the execution function table using the country code and the network code in the content of the configuration request message MSG. In this case, thenetwork signaling entity 306 forms the country code and the network code included in the configuration request message MSG9 among the function programs existing in the all function list table stored in theROM 106, that is, the start address list of the function program corresponding to the country and the network to be currently operated by thenetwork signaling entity 306, as the execution function table. In other words, thenetwork signaling entity 306 selects the function program corresponding to the country and the network to be currently operated from among the function programs stored in theROM 106 and sets the execution function program. Accordingly, thenetwork signaling entity 306 can perform the ISDN protocol according to the country and the network to be currently operated by the function program depending upon the execution function table formed as stated above. After that, atstep 704, thenetwork signaling entity 306 sets the network signaling state value to “OK” and transmits the configuration check message MSG10 to thelayer management entity 300, so that the configuration procedure can be completed. The configuration check message MSG10 is the message for informing thelayer management entity 300 of the completion of the configuration procedure by thenetwork signaling entity 306. Also, the transmission of the network signaling “OK” value represents that the configuration procedure of thenetwork signaling entity 306 has been completed. - When the
layer management entity 300 receives the configuration check message MSG10 from thenetwork signaling entity 306, thelayer management entity 300 performsstep 420 after storing the network signaling state value included in the configuration check message MSG10 atstep 418 of FIG. 4B. At this point, in the event that other messages except for the configuration check message MSG10 have been received therefrom, thelayer management entity 300 ignores the received message. Thus, atstep 420, thelayer management entity 300 transmits the configuration request message MSG11 including the country code and the network code of the application configuration data included in the configuration check message MSG6 to thedata link entity 308. The configuration request message MSG11 is the message requesting the configuration procedure performance to thedata link entity 308. Thereafter, thelayer management entity 300 checks atstep 422, whether or not the configuration check message MSG12 has been received from thedata link entity 308. - Then, the
data link entity 308 starts the configuration procedure fromstep 802 by receiving the configuration request message MSG11 from thelayer management entity 300 atstep 800 of FIG. 8. In this instance, in the case that other messages except for the configuration request message MSG11 have been received atstep 800, thedata link entity 308 performs the corresponding routine. However, atstep 802, thedata link entity 308 receiving the configuration request message MSG11 atstep 800, performs the configuration by forming the execution function table using the country code and the network code in the content of the configuration request message MSG11. In this case, thedata link entity 308 forms the country code and the network code included in the configuration request message MSG11 from among the function programs existing in the all function list table stored in theROM 106, that is, the start address list of the function program corresponding to the country and the network to be currently operated, as the execution function table. In other words, thedata link entity 308 selects the function program corresponding to the country and the network to be currently operated from among the function programs stored in theROM 106 and sets the execution function program. Accordingly, thedata link entity 308 can perform the ISDN protocol according to the country and the network to be currently operated by the function program depending upon the execution function table formed as stated above. After that, atstep 804, thenetwork signaling entity 306 sets the data link state value to “OK” and transmits the configuration check message MSG12 to thelayer management entity 300, so that the configuration procedure can be completed. The configuration check message MSG12 is the message for informing thelayer management entity 300 of the completion of the configuration procedure by thedata link entity 308. Also, the transmission of the data link value as “OK” represents that the configuration procedure of thedata link entity 308 has been completed. - Upon the
layer management entity 300 receiving the configuration check message MSG12 from thedata link entity 308 atstep 422, thelayer management entity 300 performsstep 426 after storing the data link state value included in the configuration check message MSG12 atstep 424. At this point, in the event that other messages except for the configuration check message MSG12 have been received therefrom, thelayer management entity 300 ignores the received message. Thus, atstep 426, thelayer management entity 300 transmits the configuration request message MSG13 including the country code and the network code of the application configuration data included in the configuration check message MSG6, to thephysical entity 310. The configuration request message MSG13 is the message requesting the configuration procedure performance to thephysical entity 310. Thereafter, thelayer management entity 300 checks atstep 428, whether or not the configuration check message MSG14 has been received from thephysical entity 310. - Then, the
physical entity 310 starts the configuration procedure fromstep 902 by receiving the configuration request message MSG13 from thelayer management entity 300 atstep 900 of FIG. 9. In this instance, in the case that other messages except for the configuration request message MSG13 have been received instep 900, thephysical entity 310 performs the corresponding routine. However, atstep 902, thephysical entity 310 receiving the configuration request message MSG13 atstep 900, performs the configuration by forming the execution function table using the country code and the network code in the content of the configuration request message MSG13. In this case, thephysical entity 310 forms the country code and the network code included in the configuration request message MSG13 from among the function programs existing in the all function list table stored in theROM 106, that is, the start address list of the function program corresponding to the country and the network to be currently operated, as the execution function table. In other words, thephysical entity 310 selects the function program corresponding to the country and the network to be currently operated from among the function programs stored in theROM 106 and sets the execution function program. Accordingly, thephysical entity 310 can perform the ISDN protocol according to the country and the network to be currently operated by the function program depending upon the execution function table formed as stated above. After that, atstep 904, thephysical entity 310 sets the data link state value to “OK” and transmits the configuration check message MSG14 to thelayer management entity 300, so that the configuration procedure can be completed. The configuration check message MSG14 is the message for informing thelayer management entity 300 of the completion of the configuration procedure by thephysical entity 310. Also, the transmission of the data link value as “OK” represents that the configuration procedure of thephysical entity 310 has been completed. - Upon the
layer management entity 300 receiving the configuration check message MSG14 from thephysical entity 310 atstep 428, thelayer management entity 300 performsstep 432 after storing the physical state value included in the configuration check message MSG14 atstep 430. At this point, in the event that other messages except for the configuration check message MSG14 have been received therefrom, thelayer management entity 300 ignores the received message. Thus, at theabove step 432, thelayer management entity 300 ends the configuration procedure by transmitting the all configuration check message MSG15 having the configuration state of all entities, that is, the information such as the application state value, the call control state value, the network signaling state value, the data fink state value, and the physical state value, to theapplication entity 302. The all configuration check message MSG15 is the message informing the completion of the configuration state of all entities. - Once the
application entity 302 receives the all configuration check message MSG15 atstep 518, theapplication entity 302 completes the configuration procedure by transmitting the initialization check message MSG16 having the configuration state of all entities included in the all configuration check message MSG15, to themain device 102 of the keyphone system atstep 520. At this time, when other messages except for the all configuration check message MSG15 have been received, theapplication entity 302 ignores the received message. The initialization check message MSG16 represents the completion of the configuration operation in order to perform the ISDN protocol for the country and the network to be currently operated by theBRI trunk 100, that is, to perform all of entities for the ISDN protocol. - When all configuration procedure of the
BRI trunk 100 is completed by the above operation, theBRI trunk 100 performs the normal operation. That is, theBRI trunk 100 can provides normal service by performing the ISDN protocol according to the country and the network to be currently operated by the function program as the execution function table formed by the configuration procedure as stated above. - Meanwhile, upon the
main device 102 of the keyphone system receiving the initialization check message MSG16 atstep 1012, themain device 102 of the keyphone system completes the configuration procedure after storing the country code and the network code set by the operator atstep 1014. Namely, themain device 102 of the keyphone system stores the country code and the network code as the currently-operated country code and network code with the above configuration order. Here, when other messages except for the initialization check message MSG16 have been received, themain device 102 of the keyphone system ignores the received message. - Accordingly, it is unnecessary to replace the
ROM 106 of theBRI trunk 100 with a new ROM even when the country and the network are varied by making the execution function table with selecting the function program according to the country and the network to be currently operated, from the all configuration function list table. That is to say, oneBRI trunk 100 can be commonly used in all countries and networks which have protocols different from one another. - As apparent form the foregoing, the present invention has no need to replace the ROM storing the program for performance of the ISDN protocol with the new ROM whenever the country and the network are varied by commonly using one BRI trunk for all countries and networks which have ISDN protocols different from one another.
- While there has been illustrated and described what are considered to be preferred embodiments of the present invention, it will be understood be those skilled in the art that various changes and modifications may be made, and equivalents may be substituted for elements thereof without departing from the true scope of the present invention. In addition, many modifications may be made to adapt a particular situation to the teaching of the present invention without departing from the central scope thereof. Therefore, it is intended that the present invention not be limited to the particular embodiments disclosed as the best modes contemplated for carrying out the present invention, but that the present invention includes all embodiments falling within the scope of the appended claims.
Claims (15)
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR97/6551 | 1997-02-28 | ||
KR6551/1997 | 1997-02-28 | ||
KR1019970006551A KR100222433B1 (en) | 1997-02-28 | 1997-02-28 | Configuration method of network interfacing circuits in isdn key telephone system |
Publications (2)
Publication Number | Publication Date |
---|---|
US20020085577A1 true US20020085577A1 (en) | 2002-07-04 |
US6426963B1 US6426963B1 (en) | 2002-07-30 |
Family
ID=19498363
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/033,531 Expired - Lifetime US6426963B1 (en) | 1997-02-28 | 1998-03-02 | Technique for configuring network interface circuit in integrated services digital network keyphone system |
Country Status (5)
Country | Link |
---|---|
US (1) | US6426963B1 (en) |
KR (1) | KR100222433B1 (en) |
AU (1) | AU706106B2 (en) |
DE (1) | DE19807537B4 (en) |
GB (1) | GB2324930B (en) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060030306A1 (en) * | 2000-12-07 | 2006-02-09 | Kuhn Brian G | Generic activation and registration framework for wireless devices |
US7072356B1 (en) * | 2000-06-19 | 2006-07-04 | Cisco Technology, Inc. | System and method for configuring a communications protocol |
US20070203844A1 (en) * | 2001-05-08 | 2007-08-30 | Palm, Inc. | Activation key for a wireless-enabled device |
US20100022240A1 (en) * | 2001-01-05 | 2010-01-28 | Palm, Inc. | Requesting a user account for services |
US20100091762A1 (en) * | 2008-10-13 | 2010-04-15 | Embarq Holdings Company, Llc | System, method, and apparatus for user-initiated provisioning of a communication device |
Families Citing this family (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7126713B1 (en) * | 1998-03-17 | 2006-10-24 | Brother Kogyo Kabushiki Kaisha | Communication terminal apparatus and method |
KR100322272B1 (en) * | 1999-08-19 | 2002-02-06 | 윤종용 | Method for automatically seclecting calling line identification presentation in a mobile terminal |
DE10062762A1 (en) * | 2000-12-13 | 2002-08-22 | Siemens Ag | Arrangement and method for data transmission of digital transmission data |
US6622044B2 (en) * | 2001-01-04 | 2003-09-16 | Cardiac Pacemakers Inc. | System and method for removing narrowband noise |
KR100475187B1 (en) * | 2002-12-13 | 2005-03-10 | 삼성전자주식회사 | key phone system for enable session initiation protocol and method for call setup |
CN101969395B (en) * | 2009-07-28 | 2013-02-27 | 华为技术有限公司 | Method for configuring code, method and system for detecting path and network equipment |
Family Cites Families (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH0657075B2 (en) * | 1984-05-29 | 1994-07-27 | 富士通株式会社 | Digital channel device |
US5062108A (en) | 1989-09-29 | 1991-10-29 | At&T Bell Laboratories | ISDN codeset conversion |
JP3085676B2 (en) | 1989-10-30 | 2000-09-11 | 株式会社東芝 | Telephone equipment |
FR2661300B1 (en) * | 1990-04-23 | 1994-06-17 | Bull Sa | MULTIPROTOCOL CONVERTER FOR CONNECTING A PLURALITY OF ASYNCHRONOUS TERMINALS TO A TELECOMMUNICATIONS NETWORK. |
US5317630A (en) | 1990-09-10 | 1994-05-31 | At&T Bell Laboratories | Interface for a data telephone and data terminal in a digital telephone system |
US5278972A (en) | 1990-11-21 | 1994-01-11 | At&T Bell Laboratories | Communication system for converting ISDN signaling protocol between local and public network having first group of mandatory elements and second group of non-mandatory elements |
DE4107742A1 (en) | 1991-03-11 | 1992-09-17 | Standard Elektrik Lorenz Ag | PROTOCOL ADJUSTMENT |
DE4115242A1 (en) * | 1991-05-10 | 1992-11-12 | Standard Elektrik Lorenz Ag | PROTOCOL ADAPTER |
US5442630A (en) | 1991-05-24 | 1995-08-15 | Gagliardi; Ugo O. | ISDN interfacing of local area networks |
US5239542A (en) | 1991-08-23 | 1993-08-24 | Redcom Laboratories, Inc. | Time division multiplex switching system for interconnecting telephone circuits which operate in accordance with different signalling systems and call formats |
DE4228801A1 (en) | 1991-10-03 | 1993-04-08 | Standard Elektrik Lorenz Ag | SUBSCRIBER TERMINAL FOR ISDN NETWORKS |
CA2099738C (en) | 1992-09-25 | 1999-01-12 | William Keith Cline | Architecture for a wireless telecommunication system |
DE69229793T2 (en) * | 1992-12-17 | 2000-04-20 | Ibm | Method for initializing a group of ISDN adapter cards which are plugged into a workstation functioning as the main ISDN gateway and device |
US5412660A (en) | 1993-09-10 | 1995-05-02 | Trimble Navigation Limited | ISDN-to-ISDN communication via satellite microwave radio frequency communications link |
JPH07193619A (en) | 1993-10-27 | 1995-07-28 | Canon Inc | Digital telephone set and its operating method |
DE4341888C1 (en) | 1993-12-08 | 1995-04-06 | Siemens Ag | Method for controlling components of a communications system |
US5574861A (en) | 1993-12-21 | 1996-11-12 | Lorvig; Don | Dynamic allocation of B-channels in ISDN |
DE69421512T2 (en) * | 1994-01-14 | 2000-05-18 | Ibm | Procedure for automatic adaptation and automatic configuration of the bit rate of an ISDN terminal adaptation device to 56 kbps or 64 kbps |
DE59510279D1 (en) * | 1994-03-16 | 2002-08-22 | Siemens Ag | Method for commissioning an interface to be assigned to different transmission paths in a program-controlled communication system |
US5949762A (en) * | 1996-01-24 | 1999-09-07 | Telebit Corporation | Apparatus and method for processing multiple telephone calls |
US5784558A (en) * | 1996-04-26 | 1998-07-21 | Integrated Network Corporation | Method and apparatus for testing of extended ISDN BRI service |
-
1997
- 1997-02-28 KR KR1019970006551A patent/KR100222433B1/en not_active IP Right Cessation
-
1998
- 1998-02-11 AU AU53875/98A patent/AU706106B2/en not_active Ceased
- 1998-02-23 DE DE19807537A patent/DE19807537B4/en not_active Expired - Fee Related
- 1998-03-02 GB GB9804300A patent/GB2324930B/en not_active Expired - Fee Related
- 1998-03-02 US US09/033,531 patent/US6426963B1/en not_active Expired - Lifetime
Cited By (25)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7072356B1 (en) * | 2000-06-19 | 2006-07-04 | Cisco Technology, Inc. | System and method for configuring a communications protocol |
US20060030306A1 (en) * | 2000-12-07 | 2006-02-09 | Kuhn Brian G | Generic activation and registration framework for wireless devices |
US20070178899A1 (en) * | 2000-12-07 | 2007-08-02 | Palm, Inc. | Mobile device capable of registering with multiple servers |
US9332079B2 (en) | 2000-12-07 | 2016-05-03 | Qualcomm Incorporated | Generic activation and registration framework for wireless devices |
US20080003994A1 (en) * | 2000-12-07 | 2008-01-03 | Palm, Inc. | Generic Activation and Registration Framework for Wireless Devices |
US20090005039A1 (en) * | 2000-12-07 | 2009-01-01 | Palm, Inc. | Providing user interface data on a mobile computing device |
US8918100B2 (en) * | 2000-12-07 | 2014-12-23 | Qualcomm Incorporated | Providing user interface data on a mobile computing device |
US8744441B2 (en) | 2000-12-07 | 2014-06-03 | Qualcomm Incorporated | Wireless services over different carrier networks |
US20100120407A1 (en) * | 2000-12-07 | 2010-05-13 | Palm, Inc. | User registration for wireless service on mobile computing device |
US20100120428A1 (en) * | 2000-12-07 | 2010-05-13 | Palm, Inc. | Wireless services over different carrier networks |
US7894847B2 (en) | 2000-12-07 | 2011-02-22 | Palm, Inc. | Activation of mobile computing device |
US7861009B2 (en) | 2001-01-05 | 2010-12-28 | Palm, Inc. | Requesting a user account for services |
US8131888B2 (en) | 2001-01-05 | 2012-03-06 | Hewlett-Packard Development Company, L.P. | Activation of mobile computing device on a cellular network |
US20100022240A1 (en) * | 2001-01-05 | 2010-01-28 | Palm, Inc. | Requesting a user account for services |
US20110149861A1 (en) * | 2001-01-05 | 2011-06-23 | Palm, Inc. | Activation of mobile computing device on a cellular network |
US8812398B2 (en) | 2001-05-08 | 2014-08-19 | Qualcomm Incorporated | Key for a wireless-enabled device |
US8036991B2 (en) | 2001-05-08 | 2011-10-11 | Hewlett-Packard Development Company, L.P. | Registration of a mobile computing device for a service on a wireless network |
US20100169217A1 (en) * | 2001-05-08 | 2010-07-01 | Palm, Inc. | Registration of a mobile computing device for a service on a wireless network |
US20100165938A1 (en) * | 2001-05-08 | 2010-07-01 | Palm, Inc. | Registration of a mobile computing device for a data service on a wireless network |
US20070203844A1 (en) * | 2001-05-08 | 2007-08-30 | Palm, Inc. | Activation key for a wireless-enabled device |
US9524497B2 (en) | 2001-05-08 | 2016-12-20 | Qualcomm Incorporated | Registration of a mobile computing device for a data service on a wireless network |
US20100091762A1 (en) * | 2008-10-13 | 2010-04-15 | Embarq Holdings Company, Llc | System, method, and apparatus for user-initiated provisioning of a communication device |
US8917718B2 (en) * | 2008-10-13 | 2014-12-23 | Centurylink Intellectual Property Llc | System, method, and apparatus for user-initiated provisioning of a communication device |
US9584562B2 (en) | 2008-10-13 | 2017-02-28 | Centurylink Intellectual Property Llc | System, method, and apparatus for user-initiated provisioning of a communication device |
US10348780B2 (en) | 2008-10-13 | 2019-07-09 | Centurylink Intellectual Property Llc | System, method, and apparatus for user-initiated provisioning of a communication device |
Also Published As
Publication number | Publication date |
---|---|
KR19980069480A (en) | 1998-10-26 |
DE19807537A1 (en) | 1998-10-01 |
GB9804300D0 (en) | 1998-04-22 |
AU5387598A (en) | 1998-09-03 |
US6426963B1 (en) | 2002-07-30 |
KR100222433B1 (en) | 1999-10-01 |
GB2324930B (en) | 1999-05-12 |
GB2324930A (en) | 1998-11-04 |
AU706106B2 (en) | 1999-06-10 |
DE19807537B4 (en) | 2005-12-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6185412B1 (en) | Procedure and system for ensuring emergency communication in a wireless local loop environment | |
US5774460A (en) | Local ISDN radio transmission system | |
CA2268981C (en) | Call management in a wireless telecommunications system | |
US6426963B1 (en) | Technique for configuring network interface circuit in integrated services digital network keyphone system | |
US5450396A (en) | Communication system and a private branch exchange to be used in such a communication system | |
US6301475B1 (en) | Procedure for limiting the mobility area of a terminal device in a wireless local loop | |
WO1997017790A1 (en) | Adapting the fixed network protocols to a mobile communications network | |
US5910980A (en) | Calling subscriber information notification | |
US20020126696A1 (en) | Communication system and circuit controller | |
US6034949A (en) | Evaluation means for a message-oriented layer-3 communication | |
US6711175B1 (en) | Procedure for scanning or disconnecting a module line in a V5.2 access node | |
RU2198478C2 (en) | Method for controlling set-up and use of transmission channels in radio communication systems, especially in rll/wll system of dect standard inserted as local message transmission stub in digital-network complex-service system | |
US6088438A (en) | Method of and apparatus for networking a plurality of private branch exchange systems using ISDN lines | |
EP1040675B1 (en) | Transmission of signalling information between a central terminal and a subscriber terminal of a telecommunications system | |
WO1998008352A1 (en) | Procedure to improve the capacity of a v5 interface in a wireless local loop environment | |
KR100275074B1 (en) | Electronic exchanger capable of expropriating of v5.2 interface using an external host | |
KR100584339B1 (en) | Automatic Call Retry Method in Private Switching System | |
KR100226877B1 (en) | Method for managing information of base station | |
KR100258148B1 (en) | Method of, inter-cell bearer handover in dect wireless pabx | |
KR100394728B1 (en) | Method of Controlling Transmission of Subscriber Information in the Wireless Local Loop | |
KR19990062280A (en) | V5.2 link receiving device using internal bus in electronic switchboard | |
JP2003032378A (en) | Bulk communication device and channel bulk communication system | |
KR19990062283A (en) | V5.2 Statistical Information Management System using External Host in Electronic Switching System | |
KR20000045806A (en) | Isdn primary group speed interface in switching system | |
CA2244570A1 (en) | Implementing minet on layers 1 and 2 of the isdn protocol stack |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: SAMSUNG ELECTRONICS CO., LTD., KOREA, REPUBLIC OF Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:KIM, JONG-IL;REEL/FRAME:009127/0870 Effective date: 19980328 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
FEPP | Fee payment procedure |
Free format text: PAYER NUMBER DE-ASSIGNED (ORIGINAL EVENT CODE: RMPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
FPAY | Fee payment |
Year of fee payment: 12 |