MXPA97010189A - Transparency of characteristics for wireless microtelphonon between conduit nodes - Google Patents

Abstract

The present invention relates to dividing the wireless handset control function of the telecommunication call control function into a software architecture of a wireless telecommunication system. The function for wireless handset control follows the wireless handset as it is registered and transferred from the switching node to the switching node, the function for telecommunication call control remains in the switching node in which the wireless handset is first active and it remains in that switching node until the wireless handset becomes inactive. When the wireless handset becomes inactive, the wireless telecommunications call control function is transferred to the switching node in which the wireless handset is currently registered.

Description

TRANSPARENCY OF CHARACTERISTICS FOR WIRELESS MICROELPHONUS BETWEEN SWITCHING NODES Field This invention relates to communications switching and in particular to providing features to a wireless handset as the handset is transferred from switching node to switching node. Background of the Invention Highly distributed switching systems are described in U.S. Pat. No. 5,182,751 and the US patent. No. 5,377,262. These distributed systems have an advantage in a wireless telecommunications system because they are easily expandable at low cost. This is important in a wireless telecommunications system that is used in the office, industrial or warehouse environment, where the system initially starts with a minimum number of users and then grows to a large number of users. This distributed system consists of a number of switching nodes, each of which is a separate switching system. An example of this distributed system is illustrated in Figure 1. Each switching node handles a relatively small number of wireless handsets such as one hundred wireless handsets. The manner in which switching nodes REF: 26170 communicate signaling information within the network of switching nodes and direct calls is well described in US Patents. previously referred. The software architecture of the US patents previously referred to is designed with wired telephone equipment in mind. While the distributed switching node architecture has been successfully applied to large wireless telecommunications systems, certain problems have arisen. These problems have resulted from the fact that as an individual user proceeds through the area covered by the distributed telecommunications system, it moves from a switching node to a switching node; therefore, it must be registered in each switching node. This problem has not arisen in cellular switching systems, because the cells or cells within a cellular system are so large that it is difficult for a user, even traveling at high speeds in a car to move between more than two or three cells in the course of a conversation. However, in a PCS system based on an architecture of distributed switching nodes as illustrated in Figure 1, it is quite possible that a user who walks quickly and receives multiple calls at a time, registers at all switching nodes within of the PCS system before becoming inactive. The result is that the information concerning the user and their calls and any call characteristics that have been invoked must be continuously transferred to the different switching nodes. Due to the distributed nature of the switching nodes, each of them does not have an individual communications link to all nodes within the architecture of switching nodes. This results in large amounts of data moved during an active call through multiple switching nodes and improves the possibility of missed calls or mishandling. It is clear that there are problems in the existing software architecture for distributed switching nodes in certain environments of PCS systems. Compendium axis the Invention The previous problems are solved, and a technical advance is achieved by an apparatus and method in a distributed wireless telecommunications system. The software architecture of the wireless telecommunication system divides the wireless handset control function from the telecommunication call control function. The wireless handset control function follows the wireless handset as it is registered and transferred from the switching node to the switching node; Advantageously, the telecommunication call control function remains in the switching node in which the wireless handset first becomes active and remains in that switching node until the wireless handset becomes inactive. When the cordless handset becomes inactive, the wireless telecommunications call control function is transferred to the switching node in which the cordless handset is currently registered. Other and additional aspects of the present invention will be apparent during the course of the following description and by reference to the accompanying drawing. BRIEF DESCRIPTION OF THE DRAWING FIG. 1 illustrates a wireless telecommunications switching system that incorporates the inventive concept; Figure 2 illustrates the software layers of the software architecture implemented in each switching node; Figures 3 and 4 illustrate further details of the wireless telecommunications switching system; Figures 5 to 11 illustrate addressing tables used by the wireless telecommunications switching system; Figures 12 and 13 illustrate the logical structure of a call configuration through the network, software layers for transport, session and application; Figures 14 and 15 illustrate the operations of the transport software layer; Figures 16 and 17 illustrate the operations of the session software layer; Figures 18 to 20 illustrate the operations of an FS application; and Figures 21 to 29 illustrate the operations of an NMM application. Description etall da Figure 1 illustrates a wireless telecommunications system having a plurality of distributed switching nodes. Each switching node is interconnected to a plurality of base stations, with each base station providing service for wireless handsets such as the cordless handsets 141, 142 and 143. In addition, wired telephones can be connected to the switching node via wired links. The switching nodes are interconnected by communication links such as the Primary Rate Interface (PRI) or Basic Rate Interface links (BRI = basic rate interface). Each set of links such as links 111 may consist of a plurality of PRI or BRI links. Unlike the distributed switching nodes systems of US Patents. previously referred to, the wireless telecommunication systems illustrated in Figure 4 does not have a dial plan hierarchy of switching nodes or a hierarchy of switching nodes. When each switching node initializes, it obtains the telephone numbers of the wireless handsets assigned to the initialization switching node when directing a call to the network administrator service (NMS = network manager service) 109. In addition, to obtain the telephone numbers of the wireless handsets assigned to a switching node, each switching node receives the identification of the blocks of the telephone numbers assigned to each of the other switching nodes in the wireless telecommunications system illustrated in Figure 1. way in which a switching node initializes the links that interconnect it with other switching nodes and learns how to direct calls through the architecture of switching nodes, is similar to the US Patents previously referred. Each switching node also receives from the NMS 109, the handset service record (HSR = Handset Service Record) and the feature service register (FSR = Feature Service Record) associated with each assigned handset. The master record service (MSR = Master Service Record) is the combination of the FSR and the HSR. The handset service record defines the type of handset and its configuration. The feature service record defines which features can be used by the handset, the associated buttons on the handset to invoke particular characteristics and features that are active. Figure 5 illustrates the telephone numbers and related node information that are obtained from NMS 109 in table 502. For simplicity, each node is considered to control one hundred telephone numbers, with the hundredth digit reflecting the last digit of the telephone number. node. For example, node 102 controls telephone numbers 8XX indicating all 800 telephone numbers. For simplicity, it is considered that each node only has 5 current telephone numbers assigned to it nevertheless. For example, node 101 has telephone numbers 101 to 105 assigned to it, as illustrated in table 502. Table 503 of Figure 5 indicates how node 101 directs calls to other switching nodes. As will be explained later, the LDC refers to the link left by the switching node 101. As will be described in more detail, each switching node has a network mobility manager (NMM = Network Mobility Manager), feature server application (FS = Feature Server) and handset manager application (HSM = Handset Manager). The NMM application in a switching node is involved in moving the information between switching nodes and adjusting the dial plan. The FS application deals with establishing and performing call control functions required to configure calls and implement telecommunications features.

The HSM application performs the handset control function. Consider the example, where the cordless handsets 141, 142 and 143 are involved in a three-way conference. The wireless handsets are registered and active in base stations illustrated in Figure 1. The example considers that the wireless handsets have been registered in the base stations illustrated at the beginning of the conference call. The call branches of the conference call are merged into a switching node 103. In this case, the HSM and FS applications are together in the switching nodes 103, 106 and 107. For example, in the switching node 106. , the HSM application in the switching node 106 is to control the wireless handset 143, and the FS application in the switching node 106 is to perform all the call control functions with respect to the wireless handset 143. The FS application in the wireless node switching 103 is to perform all call control functions with respect to the conference call. According to the invention, if the wireless handset 141 is now transferred to the base station 122 which is connected to the switching node 101, the HSM application in the switching node 101 now regulates the handset control functions for the wireless handset 141; however, the FS application in the switching node 103 continues to control the call control functions for the wireless handset 141 as well as to control the conference call. In addition, the audio switching function of the conference call continues to be performed by the switching network of the switching node 103. If the wireless handset 141 were to be transferred to another additional base station connected to another node, the HSM application of that node would perform the handset control function; however, the FS application of the switching node 103 will continue to perform the call control function for the wireless handset 141. The invention has the advantage that the call control function remains stationary within a switching node whenever the handset Wireless 141 is continuously active. It should be noted that it is possible for the cordless handset 141 to be active in two calls with one of the calls in the call waiting state. Figure 2 illustrates the software architecture of the switching nodes of Figure 1. This architecture is based on the modified conventional OSI model to implement the ISDN protocol. In accordance with the invention as described herein, certain additional modifications have been made to the standard model in order to include ISDN capabilities.

The main function of the physical layer 201 is to terminate physical links. Specifically, physical layer 201 is responsible for maintaining physical channels and for controlling physical subchannels. The physical layer 201 comprises a portion of software and physical interfaces. In addition, the software portion of the physical layer 201 is responsible for the direct control of the physical interfaces with which the physical links communicating the PRI and BRI information terminate. The physical layer 201 presents the link layer 212, physical sub-channels and physical channels as entities controlled by the link layer 212. The primary function of the link layer 212 is to ensure that the information transmitted on a physical channel is recovered intact and in the correct order. This is achieved by using another protocol layer that allows multiple communication paths - commonly referred to as logical links - to be established in a given physical channel or a physical sub-channel that communicates data in a packet. These logical links are used to identify and process data communicated between the link layer 212 and the physical layer 201. (An example of this type of protocol is the LAPD packet protocol used in ISDN Q.921.link layer 212 terminates the LAPD protocol). The link layer 212 can support multiple protocols, such that the upper layers are rendered ineffective by the different protocols used. In addition, link layer 212 allows higher software layers to control physical layer 201 in an abstract form. As seen in Figure 2, link layer 212 is divided into link interface 202 and link administration 203. The reason for this division is set forth below. It will help at this point to discuss the communication of ISDN signals on a D-channel to assist the readers, for example who has only a rudimentary knowledge of the communication of ISDN signals on a D-channel. At the link layer 212, a plurality of Logical links are established on a D channel. Only one of these logical links communicates the ISDN control signals, and this logical link is referred to here as a logical channel D (LDC). The LDC is identified by a logical channel number D (LDCN). The link interface 202 does most of the functions performed by the link layer 212, including the establishment of the logical links. Link management 213 identifies the various link interfaces for higher layers of software. In addition, link management communicates information between logical links and higher software layers. The network layer 204 processes information communicated in the LDCs, and thus terminates the Q.931 ISDN protocol. Therefore, this layer is responsible for negotiating the use of system resources for terminating or originating external calls to a communication node. The network layer controls the allocation of channels in an interface in which a call is received or configured. For example, if the switching node 101 receives a re-switch call 102 over the links 111, the network layer 204 of the switching node 101 negotiates with its peer layer (the corresponding network layer 204 in the switching node 102). in order to obtain assignment of a link B channel 111 - a procedure layer that will be repeated if a second B channel is desired. This negotiation is carried out using Q.931 standard ISDN messages such as connection and call setup messages by configuring LDC in the channel of links 111. Network layer 204 identifies all D channels of the finished interface with the LDC for that interface. The network layer 204 only tries to establish a call from one point to another point (for example from switching node to switching node). The network layer does not deal with how a call is directed internally to a particular switching node but rather transfers information to higher layers to determine how a call is directed at a switching node. However, the network layer requests an application, referred to herein and below as the connection manager application, add or remove services in a physical interface to a switching connection within a switching node.

Specifically, the network layer performs call configurations by first determining that the request for call establishment is valid and that the resources between the two switching systems are available by handling this call. After this determination, information regarding the call is transferred to higher layers of software. The inverse is real when the network layer receives a request from the higher software layers to establish a connection with another switching node. The network layer 204 receives information from another node concerning another call via LDC. As the information is received in the LDC, a call reference number is used to identify the call associated with this message. The call reference number is chosen by the source network layer during call setup according to the ISDN standard. Details of this identification are given with respect to Figure 14. The transport layer 204 is a key element that allows addressing a call through a complex system having multiple nodes as illustrated in Figure 1. Its primary function is handle the routing of calls externally, ie between switching nodes. The transport layer 205 sees the system of Figure 1 in terms of nodes and deals with directing calls from its own node to other nodes or endpoints. (As explained in the detailed description of the session layer 206, that layer, not the transport layer 205, interprets the logical destination information, such as telephone number, to determine the destination node of a call and establish a intranode path when using the connection manager application). In a total system comprising multiple switching nodes such as a switching node 101, the various transport layers communicate with each other in order to establish a call through the various switching nodes. This communication between transport layers is required because it may be necessary to direct the call through the intervening nodes to reach the destination node. The transport layers communicate with each other using signaling paths (LDCs) established between switching nodes. With respect to addressing between nodes, the transport layer 205 is the first layer that begins to take a global view of the total system illustrated in Figure 1. The transport layer 205 uses information that is provided by the session layer 206, for direct the path between nodes. The transport layer carries out its tasks of directing between different nodes when using tables that define the available trajectories and the options of their trajectories.

These tables do not define all the trajectories if not only those trajectories that the node has already used. Communications and transport layers are used by the network layer 204 using established LDCs. The transport layer 205 communicates information destined for its peers to network layers 204, and the network layer 204 packages this information into the information elements, IEs, of the standard Q.931 ISDN messages. The network layer 204 uses the LDC that has been configured to a particular node to communicate this information to its peer network layer. Similarly, when another network layer receives information of this type, the other network layer unpacks the information and then directs the information to the transport layer. The primary function of session layer 206 is to establish communication between endpoints, with all endpoints considered as applications including for example a BRI station equipment that is considered an application. Significantly, these extreme points can be applications such as the application that performs the call processing features or the dial plan application. Any case, connections between these endpoints are considered a call. A session (call) is configured by session layer 206 whenever two applications require communication with each other. As previously noted, session layer 206 deals only in terms of switching nodes and applications in those switching nodes and relies on transport layer 205 to establish paths to other switching nodes. The session layer 206 identifies the calling application by an address that previously in the telecommunications technique, was considered only a telephone number but has a much broader concept in the Q.931 protocol. From this address, the session layer 206 determines the destination switching node. Session layer 206 configures a call to the destination switching node when communicating with the session layer of the destination switching node. The communication with the other session layer is achieved by having the session layer request its transport layer to place a call to the other switching node, so that a connection can be made for that particular address. The transport layer directs the call based on the node number that is determined by the session layer. These requests are made using the network layer, to generate standard ISDN Q.931 call configuration messages. If the other switching node can not interpret the address, the session layer of that switching node transmits information to its transport layer, requesting that the call be removed. If the session layer can interpret the address, it sends a message to its transport layer requesting that a message be transmitted to the requesting switching node through its network layer. The presentation layer 207 of Figure 2 invokes a complex protocol in order to put in order the information communicated between applications, so that the applications are completely divorced from the protocol used to communicate the information. A presentation-level protocol allows an application to communicate with a peer application through a transport path. Finally, the application layer 208 handles the resources required by the applications that run in the software layer 209. When an application in the software layer 209 communicates with another application similar or even, the application does not perceive that so many other applications exist or where these applications are located. It is the function of the application layer 208 to determine and use these details, consequently allowing the applications to be written in a very abstract manner. The administration information base 211 stores data used by the different software layers. Layer management 210 provides the link management entities required in each software layer. Figure 3 illustrates the switching nodes associated with the previous example. Switching nodes 101, 103, 104, and 106 are illustrated in greater detail. The manner in which the elements 304-310, 314-320, 324-330 and 334-340 work together is described in greater detail in U.S. Pat. No. 5,377,262 and the US patent. No. 5,182,751, which are hereby incorporated by reference. The cordless handset 141 is assigned the number 402. As previously described, the telephone number 402 is assigned to the switching node 104 as illustrated in Figure 7. When the cordless handset 141 is first registered in the base station 126, HSM 311 responds to this registration request. In order to register the wireless handset 141, HSM 311 requires the HSR registration. To obtain this registration, HSM 311 directly requests the HSR from NMM 313. If an application requests or sends data or a message to another application in the same switching node, the data or messages are simply sent between the applications in the software layer 8. If an application requests or sends data or a message to an application in another switching node, a call is configured between the applications. Since the wireless handset 141 is assigned the telephone number of 402, NMM 313 does not have the handset service record. To obtain handset service registration, NMM 313 directs a call to NMM 303 of switching node 104. This call is addressed using the telephone number of MSR 402. In response to this telephone number, session layer 316 examines the level 5 addressing table in the switching node 103. It identifies from the address table 602 of level 5 of Figure 6, the fact that the MSR block 400 of the numbers is assigned to the switching node 104 and requests that the transport layer 317 directs the call to the switching node 104. The transport layer 317 responds to this addressing request to access the addressing table 603 as illustrated in Figure 6 and obtains the information addressed to the node calls of switching 104 over the links 113. As stated in the built-in applications, the lower software layers then direct this call to the switching node 104. The switching node Ion 104 responds to the MSR 402 telephone number to direct this call to NMM 303. The call establishes a signaling path between NMM 313 and NMM 303. NMM 313 requests NMR 303 HSR. NMM 313 responds to the HSR directing this register in MIB 314 and inform HSM 311 of this fact. HSM 311 then validates the wireless handset 141. After the validation is complete, HSM 311 informs NMM 313 of this fact. NMM 313 then sends a termination message to NMM 303. NMM 303 then puts HSM 301 and FS 302 in standby with respect to the wireless handset 402 at switching node 104. At this point, NMM 303 transmits the feature service register. , FSR, to NMM 313 directing FSR in MIB 314. NMM 303 then updates table 702 of Figure 7 to identify the fact that handset 402 is active in switching node 103. NMM 313 responds to the complete record in the insertion line 604 in table 602 of Figure 6, to define that HSM 311 now handles the handset control functions. In addition, NMM 313 inserts in line 606 of table 602, the fact that the wireless handset 141 now registers in the switching node 103. It should be noted that the path 343 of Figure 3 is only to configure the FS 312 link and HSM 311 when the cordless handset 141 is active in a call. Line 608 is inserted into the address table 601 at level 7 of Figure 6, to define the fact that the HS 402 telephone number will have to address HSM 311. Similarly, line 613 is inserted into the table 601 to define the fact that the telephone number 402 will have to be addressed FS 312. The trajectories 341, 342 and 343 have not yet been configured. Now consider when the cordless handset 141 directs a call to the cordless handset 143. Consider that the telephone number for the cordless handset 143 is 601. That means that the cordless handset 143 is not only registered in the switching node 106 but the node 106 is the original or home switching node for the wireless handset 143. HSM 311 receives the digits for the telephone number 601 and directs a call to the telephone number 402. Directs a call to the telephone number 402 because HSM 311 has no mechanism to know or be aware of the application FS serving the cordless handset 141 resides in the switching node 103 at this time. When the HSM-directed call 131 is received by the application layer 320, the last layer examines the addressing table 601 of the level 7, as illustrated in Figure 6 for the switching node 103 and determines from the line 613 that the FS application serving the cordless handset 141 at this time is FS 312. In response to this information, the application layer 320 establishes a call request to FS 312. This configures the path 343 and in the session log table 604 of the level 7, column 609 is inserted indicating that signaling has been established between FS 312 and base station 126 by HSM 311. In this call request is contained the message requesting call configuration of HSM 311. The message of HSM 311 contains as a sub-part address the telephone number of the destination telephone which is the telephone number 601. In response to the sub-part address FS 312 then it requests that a call be set up to the telephone number 601. The application layer 320 responds to the request that a call be configured to the telephone number 601 to examine the addressing table 601 of level 7. The application layer 320 finds no entry for the telephone number 601 in the addressing table 601 of level 7 and transfers the call request to session layer 316. Session layer 316 responds to this request to examine table 602 of Figure 6 and determine from line 607, which the block 600 of the telephone numbers is assigned to the switching node 106. The session layer 316 then requests that the transport layer 317 establish a call to the telephone number 601 by the node 106. The transport layer 317 responds to this request to examine the address table 603 and determine that the node 106 is reached by the links 117. The transport layer 317 then requests that the lower layers transmit this call as a configuration message. The call is then transmitted on the signaling path 341 by the switching node 108 to the switching node 106. When the FS configuration message 312 of the switching node 103 is received by the session layer 336 of the switching node 106, the session layer 336 examines the table 802 of Figure 8 and determines from the line 807 that the wireless handset 143 is currently registered in the switching node 106. The configuration message is then directed to FS 332. FS 332 establishes a call using the number of "hs601", in order to establish communication with the handset manager application serving the cordless handset 143. This call request is communicated to the application layer 340. The application layer 340 responds to the request of call to examine the addressing table 807 of level 7. From line 808, the application layer 340 determines that the telephone number hs601 is it handles by HSM 331. The communication is then established between FS 332 and HSM 331 by path 345. HSM 331 sends the configuration message to wireless handset 143 by adjusting path 346. Wireless handset 143 responds with an alert message. After obtaining the handset alert message 143, HSM 331 transmits an alert message back to FS 332 which in turn communicates the alert message back to FS 312 via the path 341. When the cordless handset 143 responds to the call, HSM 331 communicates a connection message with FS 332, which in turn transmits the connection message to FS 312. The lower software layers of the switching node 103 respond to the connection message to configure the network 318, so that the cordless handsets 141 and 143 connect in an audio connection over the network 318. Now consider that when the cordless handset 141 establishes a conference call by adding the cordless handset 142 to the telephone call present with the cordless handset 143. The telephone number for the cordless handset 142 is considered to be 701. The user of the cordless handset 141 presses the button a propitious to start a conference. A message is sent from the wireless handset 141 to HSM 311. HSM 311 responds to this message to request that FS 312 establish a conference. If the cordless handset 141 is dialed in the service feature record that has the ability to create conferences, FS 312 is requested by HSM 311 that the wireless handset 141 enter the telephone number for the desired third party. When the telephone number 701 for the wireless handset 142 is received by FS 312, FS 312 establishes a call via the switching node 108 with the application FS in the switching node 107 on the path 342. After the application FS in the switching node 107 establishing a connection to the wireless handset 142 by an HSM application in the switching node 107, FS 312 requests that the lower software layers in the switching node 103 establish a conference by the network 318 between the wireless handsets 141, 142 and 143. FS 312 updates FSR in the wireless handset 141 to reflect that there is an active conference call. Now consider in the example that when the cordless handset 141 is transferred to the base station 122 that is connected to the switching node 101. When the cordless handset 141 first contacts the base station 122, it signals HSM 321 of the switching node 101 that an active transfer is going to be made. HSM 321 sends a message to NMM 323 with an active transfer request. Since the wireless handset 141 having the telephone number 402 is not assigned to the switching node 101, NMM 323 places a call to the telephone number NMSR 402. The application layer 330 examines the addressing table 501 of the level 7 of the Figure 7 for a msr entry 402. When not finding an entry, the application layer 330 transfers the call request to the session layer 326. The session layer 326 responds to this call request to examine the table 502 of the Figure 5 and determine that the msr 400 number blocks are assigned to the switching node 104. The session layer 326 then requests that the transport layer 327 direct the call to the switching node 104. The transport layer 327 examines the table 503 and determines which links 111 are to be used to place the calls to the switching node 104. The transport layer 327 then requests that the lower software layers of the switching node 101 direct the call to the switching node 104. When the switching node 104 receives the call, the session layer 306 responds to the dialed telephone number of msr 402 to examine the line 704 of the table 702 and determine that NMM 303 will receive the call. NMM 303 answers the call to determine from line 707 of table 702 that the wireless handset 141 is currently controlled by FS 312 at the switching node 103. NMM 303 directs a call to NMM 313 of the switching node 103 and requests that NMM 303 suspend HSM 311 with respect to the cordless handset 141 and sends the current handset service register for the cordless handset 141 to NMM 303. When NMM 303 receives the handset service register, it transmits this register to NMM 323 of the node 101. NMM 323 responds to the insertion line 901 in Table 503 of Figure 9 to designate that the assignment FS in the switching node 103 is controlling the wireless handset 141. In addition, NMM 323 aggregates the registration data of handset service for the wireless handset 141 to MIB 324 of the switching node 101. NMM 323 then adds the line 902 to the table 502 and adds line 903 to table 501 of Figure 9 to identify the fact that HSM 321 is now handling the wireless handset 141. HSM 321 now calls the telephone number 402. This call is routed through the session layer 326 to the node switching 103 configuring path 401 of Figure 4. Session layer 316 of switching node 103 responds to the call to direct the call to application layer 320 which directs the call to FS 312. FS 312 responds to the request transfer in the call to disable the path 343 to HSM 311 as illustrated in Figure 3 and merge the newly received call of HSM 321 into the currently configured calls with the cordless handsets 142 and 143. This merging operation not only establishes trajectories signaling 401, the path 341 of the path 342 as part of a common conference call but also establishes the audio connection through the network 318 between the wireless handsets 141-142. At this point, the transfer is completed with respect to the user's perception of the wireless handset 141. NMM 323 of the switching node 101 sends a transfer termination message to NMM 303 of the switching node 104. When NMM 303 of the switching node 104 receives the return transfer termination message from NMM 323 from the switching node 101, NMM 303 transmits a transfer termination message to NMM 313 from the switching node 103. Next, NMM 303 disconnects the call to NMM 323 which is has set to transfer the handset service registration information to the switching node 101. NMM 313 of the switching node 103 responds to the termination message of NMM 303 to remove the entry 604 of the table 602 such that the table 602 now appears as in Figure 10. NMM 313 adds line 1001 to table 602 of Figure 10 to indicate that HSM 321 of switching node 101 now e is performing the handset control function. NMM 313 then configures a flag for FS 312. This flag informs FS 312 that when the cordless handset 141 comes to rest that FS 312 will notify NMM 313. This is done in such a way that when the cordless handset 141 is left in At rest, the call control function can be transferred to FS 323 of the switching node 101, considering that the wireless handset 141 is still registered in the switching node 101 at this time. Now consider the operations that are taken when the conference call is at rest. Consider that both cordless phones 143 and 142 come to rest at approximately the same time. In the switching node 106, HSM 331 informs the FS 332 that the wireless handset 601 is now idle. FS 332 sends a disconnect message on the path 341 to FS 312. In response to the disconnect message, FS 312 changes the call records to reflect a bi-directional call between the cordless handset 141 and the cordless handset 142. FS 312 removes the connection network in the network 318 to the switching node 106 for the wireless handset 143 when transmitting an undo merge message to the lower software layers. Path 301 is also removed. Similarly, when the cordless handset 142 engages, the FS application on the switching side 107 also transmits a disconnect message. In response to the second disconnect message, FS 312 on the switching node 103 removes the connection within the network 318 as well as retracts the path 342. Because the flag previously configured when the wireless handset 141 is transferred to the switching node 101 , FS 312 signals to NMM 313 that the wireless handset 141 is now idle. NMM 313 routes a call to NMM 303 and informs NMM 303 that the wireless handset 141 is now idle and transfers FSR to NMM 303. NMM 313 also suspends the operation to FS 312 with respect to the wireless handset 141. In response to FSR, NMM 303 sends this NMM register 323 when first establishing a call to NMM 323. NMM 323 informs FS 322 of receiving the data and stores the data in MIB 324. In addition, NMM 323 removes line 901 from Figure 9 and inserts line 1103 in table 501 and line 1104 in table 502 of Figure 11 to indicate that FS 322 is now performed the call control functions for the wireless handset 141. NMM 323 then sends a termination message to NMM 303 of the switching node 104. In response to the termination message, NMM 303 supports a message to NMM 313 of the switching node 103 designating that the movement of the call control functions to the switching node 101 is complete. NMM 313 removes the feature service registration data from MIB 314. In addition, NMM 313 removes lines 606 and 1001 from table 602 and line 613 from table 601 of Figure 10. Finally, NMM 303 from switching node 104 disconnects the calls it has configured to NMM 313 and NMM 323. Figure 11 illustrates the address tables for switching nodes 101 and 104 after these operations are completed. This section describes call routing from the perspective of the session software layer 206, the transport software layer 205 and the network software layer 204 of Figure 2. Figure 12 illustrates the manner in which the calls are made. identify and process between the network software layer 204, the transport software layer 205 and the session software layer 206. More detail on the logical D-channel numbers for call records (LDCN) and call reference numbers (CRN = Cali Reference Numbers) is given in the US patent No. 5,377,262 previously incorporated. In the network software layer 204, each half of a call is identified by the CRN number, for example CRN 1202. As can be seen in Figure 12, the call record is common across the software layers, and each layer uses additional information along with the call record. The call records are taken from a common table within each switching node, and a call record number is unique within a particular switching node.

The transport software layer 205 identifies each half of a call by the LDCN and the call record number. The LDCN is used because the information illustrated in the level 4 addressing tables is identified by the LDCN number denoting the link (or set of links) of a switching node to another switching node. It should be noted that the call record is identified identically in all three software layers as illustrated in Figure 12, for a particular call. The session software layer 206 is the point within the software architecture where the calls are gathered for purposes of signal information exchange for each call having a single session configuration for it such as session 1206. If a call is simply routed through a switching node, the session register is associated with two call records such as a call register 1201 and call register 1203, with each call record being part of the middle of a call . (Each half of a call is referred to as "half call"). If a call is from or to an application, only one call record is used since the other half of the call ends at the application software layer. Example of a simple application to an application call would be when NMM 313 establishes a call to NMM 303 of Figure 3. For this call, only one path, for example 1208 will leave session log 1207 and will be directed to the application layer for connection to the NMM application. The third type of block structure illustrated in Figure 12 should be considered in light of Figure 13. An example of this type of call is when the cordless handset 141 has established a call to the cordless handset 143 as illustrated in FIG. Figure 3. Consider that CRN 1202 identifies the branch of the call coming from the cordless handset 141 and CRN 1205 identifies the branch of the call that comes from the cordless handset 143 by the path 341. The branching of the call illustrated as 1208 going to the service access point map (SAPM = Service Access Point Map) 1301 of Figure 13, ends at HSM 311. The branch of the call illustrated as 1209 ends by SAPM 1304 in FS 312. The path 343 is illustrated as interconnecting SAPM 1302 and SAPM 1303. Elements 1301-1308 exist at application level 320 for switching node 103. Session log 1308 of level 7 is used for It is used to establish the correspondence between the different portions of the call including the branches 1208 and 1209. The session record 1308 of level 7 is illustrated as table 604 in Figures 6 and 10. The session records of level 7 for the others Switching nodes are illustrated in the appropriate Figures 5 through 11. Messages are communicated directly between FS 312 and NMM 313. The connection manager whose operations are detailed in the US patents Built-in prerequisites respond to a request from the interface administrator running on software layer 3, or a merge request generated by an FS application, to examine the level 7 session log and properly configure the 1207 session log 120 The interface manager responds to reception in the descending call branch of an alert, connection or progress message to request such configuration by the connection manager. The connection manager will establish the audio and data connection through the network 318 equally. From the point of view of the session software layer 206, it simply transfers and receives messages through the branches 1208 and 1209. The operations performed by the software layer 206 in response to these messages are set forth in the following paragraphs. To understand how calls are processed by the three software layers illustrated in Figure 12, consider the examples given in the following paragraphs. For these examples reference should be made to Figure 3 which illustrates the interfaces associated with the call registers 1201 and 1203. For the case where a call is configured through the switching node 108, the call register 1201 is associated with the links 117 and call register 1203 is associated with links 118 in the following example. It should be noted that the branches 1208 and 1209 do not exist.

Consider that a call is received on the links 117 that are destined for the switching node 106 by the links 118. LDCN 1208 is established when the links 117 are activated. When a configuration message associated with a call is received by LDCN 1208, call register 1201 is established and associated with LDCN 1208 as the first call half is initiated. The destination node number is transferred from the network software layer 204 to the transport software layer 205. The transport software layer 205 responds to the number of destination switching nodes to determine that the links 118 are the links suitable for use in order to configure the call through the switching node 108 to the switching node 106. The LDCN 1204 will be the LDCN set when the links 118 are first active. It should be noted that the LDCN number used in Figures 5 to 11 is simply the number of links for simplicity. As stated in previously incorporated patent applications, the fact number will be a different number. The path that is configured with the ascending branch that comes through the call register 1201, then through the session register 1207 and descending through the call register 1202 and CRN 1205. All messages transferred either in the links 117 or links 118, will be transferred up and down these call branches by the session register 1207. The transport software layer 205 transmits the configuration request to the network software layer 204. The last software layer transfers the configuration request to the switching node 106 by the lower software layers and the links 118. Whereas the switching node 106 responds with an alert message, this message is transferred upwards through the second call half which is identifies by the call register 1203 by the network software layer 204 and the transport software layer 205 to the session software layer 2 06. The last software layer uses information in the session register 1206, to identify the first call half that is associated with the call record 1201. The alert message is then communicated by the transport software layer 205, the network software layer 204, the lower software layers and the links 117 to the source switching node. The interface manager in the software layer 3 responds to the alert message to have the connection manager establish a connection through the network of the switching node 108 for this call. For a second example, consider that an application in the switching node 102 transmits a configuration message to establish a logical call with an application in the switching node 103. The configuration message is processed by configuring the first call half in the same way as in the first example. However, after session software layer 206 has established session log 1206, it does not establish a second call half but rather transfers the information to the application in the application software layer. The application responds with a connection request that is transferred in descending order through the software layers 206, 205 and 204, after which it is communicated to the switching node 103 by the links 112. The path 1206 is configured through of level 7 and an SAPM to the application. For a third example, consider the situation where the wireless handset 141 places a call to the wireless handset 143. Now considering Figure 12 that the LDCN 1208 is established when the links 351 become active. Similarly, consider that LDCN 1204 is established when the links are established 117. When a configuration message is received by LDCN 351, call register 1201 is established and associated with LDCN 1208 as the first call half is initiated. The manner in which the transport layer 205 or transport layer 317 of Figure 13 transfers this call and in the manner in which the session software layer 206 responds, has been previously described. The session software layer 206 will direct this call to the application layer 320. The actions taken in the application layer 320 have already been described with respect to Figure 13.

Figure 14 illustrates the information flow received by the transport software layer 205 for half call from the network software application 204. Figure 14 illustrates the actions taken by the routines in the transport software layer 205 to processing each unique combination of LDCN and call record such as LDCN 1208 and call register 1201 defining half call (also referred to as call branch). Each media call is considered capable of having three states in the transport software layer 205: idle state, configuration status and active state. The idle state is the initial condition before the call record is associated with an LDCN. The configuration state occurs after the configuration indication is received from the network software layer 204. The active state is accessed from the configuration state after the first end-to-end message is received from the other half of the configuration. the call, for example received from the session software layer 206. An end-to-end message is an alert, connection or progress message. The software routine illustrated in Figure 14 responds to indications received from the network software layer 204 either to send a request back to the network software layer 204 or to send indications to the session software layer 206. Flow chart of Figure 14 has two main sections. The first section comprises blocks 1402 to 1407 and is related to establishing a new call half in response to a configuration indication from the network software layer. The second section comprises blocks 1408 to 1423 and is related to establishing half call. The decision block 1401 determines whether the indication is received or not from the network software layer 204 is a configuration indication. If it is a configuration indication, decision block 1402 checks to verify if the call is in the idle state. If the call is not in the idle state, the block for error recovery 1403 is executed, since only a configuration indication will be received when this half of the call is in the idle state. If half of the call was in the idle state, block 1404 is executed to place this call half in the configuration state. Decision block 1405 determines whether the node number of switching node 103 equals the destination node number of the configuration indication. If the determination is yes, the node flag is adjusted. The flag is available to both call halves. The node flag is used to pass this determination to the session software layer 206. The blocks 1406 and 1407 are used to properly configure the flag of the node to indicate whether the switching node 103 is the designated node or not. The configuration indication also includes the LDCN and the call record number of the network software layer 204 that specifies that LDCN and call log are being used. (In this half of the call, the LDCN is LDCN 1208 and the call register is the call register 1201). The call record is chosen by the network software layer 204 when the configuration message is received from the physical layer. The LDCN is determined according to the link in which the switching node 103 receives the configuration message. With respect to block 1407, it will be recalled from the previous discussion with respect to Figure 4 that the transport software layer performs all the necessary addressing of a configuration message that is not designated for the receiving switching node. However, it is necessary to transport said configuration message to the session software layer 206, so that a session can be established for this call since the call is routed through the receiving switching node. Block 1407 accomplishes this purpose. With respect to block 1406, it is necessary to pass the configuration location to the session software layer 206, so that the last software layer can perform the necessary actions using the dialed number to determine the destination of the call (either an end point or a subsequent switching node).

Returning to decision block 1401, if the indication received from the network software layer is not a configuration indication, session block 1418 is executed to determine whether this call half is in the call configuration state. If this call half is not in the call configuration state, then the decision block 1419 is used to ensure that this call half is not in an idle state. The idle state indicates an error at this point, and error recovery block 1423 will be executed. Considering that this call half is not in the idle state, the indication is checked to check if it is a clear indication. If so, block 1422 executes what returns the state of the call half back to the idle state and releases the call log. In both cases, whether or not a release indication is executed, the indication is sent to the session software layer 206. Returning to decision block 1418, if the call half is in the call configuration state, decision block 1413 checks to see if this is an alert, connection or progress indication, indicating that the call is going to change from the call configuration state to the active state. The ISDN protocol allows any of three of these messages to be given in response to the configuration message under various conditions. If the response to the determination in decision block 1413 is yes, block 1416 is executed to change the call half to the active state. Block 1415 is then executed to use the information contained in the indication addressing vector (which is transferred from the network software layer) to update the level 4 addressing tables. Actually, block 1414 transfers the indication to the session software layer 206. Returning to decision block 1413, if the response fails to the determination made by the last session block, decision block 1412 is executed to determine whether the received message is a release indication or do not. If it is not a release indication, the indication is transferred to the session software layer by blocks 1408 and 1409, since it does not affect this layer. If this is a release indication, this indication is handled in an improved way compared to prior art telecommunications systems. First, the release indication is verified by decision block 1411 to check if it indicates that the call was blocked. If the call was blocked, decision block 1410 is executed to check whether or not there is another path to the destination. This logic is determined by decision blocks 1411 and 1410. If block 1410 is executed, consideration is made that a configuration message sent to a remote switching node has resulted in the remote node sending a release message. In response to the release message, the switching node 103 attempts to find another path to the destination switching node using the level 4 guidance table as previously discussed. If a new path is found by the decision block 1410, the control is transferred to the decision block 1431. This latter block sends a configuration request to the network software layer 204 requesting that this last software layer try to establish the call using a new LDCN number (which is supplied by transport software layer 205), defining the new path used by the original session record and call record. Since the original session record is employed, there is no need for any additional work to be performed by the session support layer 206; therefore, no indication is transferred to the session software layer 206. If either of decision blocks 1411 or 1410 makes a negative determination, block 1409 is executed as previously described. Figure 15 illustrates the actions taken by the transport software layer 205 in response to requests received from the session software layer 206. Figure 15 has two main sections. The first section comprises blocks 1502 to 1512 and is related to the initial step of configuring a new call half. The second section comprises blocks 1515 to 1526 and is related to an established call average. An established media call is either in the configuration or active state. Decision block 1501 checks whether the state of the call half is in the idle state or not. If the call half is in idle state, decision block 1502 checks to check if a configuration request is received from session software layer 206. If it is not a configuration request, then block 1503 is executed to perform error recovery. If it is a configuration request, decision block 1504 is executed to check that the node flag that had previously been set by transport software layer 205 during processing of the other call half, either by block of decision 1406 or 1407 of Figure 14. If the node flag is not adjusted, this indicates that the session software layer is configuring a call originating in this switching node or that this switching node is a point in tandem for a previously addressed call. In this situation, the transport software layer must already direct the call in a forward direction, not to circulate or disconnect the call because there is no available route. To do this, the decision block 1505 determines from the route vector present in the message how it is received from a distant node and the level 4 addressing tables, whether a non-circular route is available. If there is a non-circular route available, block 1506 is executed to send a configuration request together with an LDCN number to network software layer 204. The LDCN identifies the new route. In addition, block 1506 establishes the state equal to the configuration state. If a non-circular route is not available, block 1507 is executed to send a release request to the network software layer 204, to establish the status equal to the idle state, and to inform level 5 that it deregisters the network. session. Returning to decision block 1504, if the node flag indicates that the call is destined for the receiver switching node or originates in this switching node, block 1508 is executed to find the best route to the new destination node. (The best route is determined by the route that has the least interchangeable switching nodes). As will be described with respect to Figure 16, the session software layer 206 responds to the node flag, indicating that the switching node 103 is the entry destination node, to change the node number to a new number of node if the call should be directed to another switching node. In such a case, the switching node 103 is an intermediate node in the route to the other switching node. Decision block 1509 checks to see if a route is found or not. If a route is found, decision block 1510 determines whether the route found is a circular route. (A circular route is identified if any of the new destination switching node is in the list of previously passed switching nodes or if the route reselection will return to a previous switching node). If it is a circular route, the re-address request is transmitted to the network software layer 204, indicating that the node number has been changed and that the route is backup for the call. The result is that a redirection message is sent to the switching node that transmits the additional configuration request to the switching node 103, since it is not necessary to route the call through the switching node 103. The function of the re-address request will be described previously. If the route is not circular as determined by decision block 1510, then block 1511 is executed to send the configuration request to the new route as defined by block terminal LDCN 1508 to a network software layer. 204 and to adjust the state for this half call to the configuration state. Now we return to decision block 1501. If the determination is no, decision block 1515 is executed to determine if this half call is in the configuration state. If the call half is in the configuration state, decision block 1516 determines whether it is a release request or not. If it is a release request, then the state of this half call is set to rest. If it is not a release request, then decision block 1518 is executed to determine whether the request is an end-to-end message. If the answer is yes, then block 1519 adjusts the state of this call average to the active state, block 1520 makes the connection of channel B if in a connection message, and block 1521 sends the request to the software layer of network 204. If the determination in decision block 1518 is no, then block 1521 is executed immediately. Returning to decision block 1515. If the determination was no, decision blocks 1522 and 1524 determine whether the request is a configuration request and the average call is in the active state respectively. If the determination made by decision block 1522 was yes or the determination made by decision block 1524 was no, then error recovery block 1523 is executed. Otherwise decision block 1525 is executed to determine whether the application is a release request or not. If it is a release request, this half call is set to the idle state by 1526 and block 1521 is executed. Figure 16 illustrates the response of the session software layer 206 to indications received from the transport software layer 205. It must be remembered from the discussion of Figure 12 that the session software layer joins the two half calls to form a complete call using a session record. In addition, calls that terminate in an application in the application software layer are communicated by the session software layer a and the designated application. In addition, the session software layer responds to a request that descends from an application to establish a call to an application. In addition, the session software layer performs addressing in the dialed number as previously discussed using the level 5 addressing tables. Figure 16 illustrates the operation of a session software layer 206 in response to indications received from the layer transport software 205. The session software layer 206 responds to these requests to communicate the information to an application or to respond by transmitting additional requests to the transport software layer 205. Requests transmitted to the transport software layer 205 may already be for the two call means illustrated in Figure 12. With respect to certain indications that are received from the transport software layer 205, the session software layer 206 simply communicates these requests to the other called media. The decision block 1601 responds to an indication received from the transport software layer to determine whether the indication is a configuration one or not. If the indication is configuration, decision block 1602 is executed to determine whether the node flag indicates that the receiving node (switching node 103) is the destination node of the indication. It must be remembered that the node flag is adjusted by blocks 1406 and 1407 of Figure 14. If the determination in block 1602 is not, the decision software layer 206 does not require performing any addressing functions since the addressing function will be performed at the node number designating the destination node. However, a call record is obtained by block 1603 for the new call half to be configured. For example, considering that the configuration indication has been received for the first call half dealing with call register 1201 of Figure 12, the call record to be obtained by the second call half will correspond to call register 1203 considering that the call is carried on links 118. After the call record is obtained, block 1604 configures a session record to associate the two half calls. Finally, block 1605 sends the configuration request for the transport software layer 205, so that the last software layer can address the configuration message based on the node number for the second half of the call .

Returning to decision block 1602, if the response to the determination is yes, decision block 1608 is executed to determine whether the call average is intended for an application at switching node 103. If the answer is yes, then the block 1609 is executed to send a connection request back to the other switching node involved with the called half. It should be noted that the second half of the call is not configuration. However, it is necessary to configure a session record if this function is performed by block 1610. Returning to decision block 1608, if the answer to the determination is no, decision block 1613 is executed. If the answer is yes , which means that the configuration message is for a terminal connected to the switching node, blocks 1614 and 1615 are executed to establish a new half call, and a configuration request is sent to the terminal by execution of block 1616. Returning to decision block 1613, if the terminal or application is not present in this node, it is necessary to try to establish a route to the terminal by first using the dialed number to determine a switching node to which that terminal is connected. This action is performed by block 1619 as previously described with respect to Figures 6 to 12. Decision block 1620 determines whether the search was successful for a destination node or not. If the search was unsuccessful, indicating that the switching node 103 can not identify a switching node that hosts the terminal, block 1621 is executed and results in a release request that is sent to the software layer of transport 205. If a destination node is found, blocks 1622 and 1623 are executed to establish a new call half. A configuration request is sent to the transport software layer 205, to establish the second half call with the switching node that was determined per execution of the block 1619. Returning to the decision block 1601 if the indication is not configuration, the Decision block 1627 is executed to determine if it is a release indication. If it is a release indication, block 1628 removes the session record that has the effect of removing the call. In addition, the release indication is sent to the transport software layer 205 in the second call half. For example, if the release indication is received from the average call associated with the call register 1201, the block 1629 will transmit the clear indication to the call half associated with the call register 1203. As can be expected, this operation allows the call is removed through a series of switching nodes. Returning to decision block 1627 if the indication is not a release indication, decision block 1630 checks to see if the indication is associated with an application. This verification is done by simply examining the session record and communicating the information to the destination given in that record. Here, if it is an application, block 2204 is executed. However, if it is not an application, the information is sent to the second call half per execution of block 2205. Figure 17 illustrates the functions performed by the session software layer, in response to requests that are sent from the layer presentation. Decision block 1701 determines whether the request is configuration. If it is a configuration request, then a call half is established in the session software layer when executing blocks 1702 and 1703. Block 1704 interprets the dialed number that is provided by the application to determine the destination node. Block 1709 then sends a configuration request to the transport software layer. Returning to decision block 1701, if the request is not a configuration request, then decision block 1705 determines whether it is a release request. If it is a release request, then block 1706 withdraws the session record and transfers the release request to block 1707 for communication to the transport software layer. Returning to decision block 1705 if the answer is no, then block 1708 simply sends the request of the transport software layer for communication to the terminal or switching node that is coupled in a call with the application. Before describing in more detail the actions taken by the software layers 204, 205 and 206 of Figure 12, when implementing the re-address message, consider how the re-address message is encoded. ISDN signaling is defined by the ISDN Q.931 standard, and it is intended to provide an international standard to control the initiation of calls, call forwarding, call terminations, communication of national use information, local service network information, and specific user information for telecommunications systems and terminals. The re-address message information is encoded as a distributor type message using conventional techniques. For a message of national type or distributor, the first octel (which defines the type of message, is an escape code that causes the switching node to examine the second octel to determine if the message is a message of the distributor or national type. Consider the operation performed by the switching node 102 with respect to Figure 12. As the configuration message is received, it proceeds through the software layers 204, 205 and 206 on the left call branch of the call (data record). call 1201 and LDCN 1208.) When the configuration message is received by the session software layer 206, it interrogates the level 5 addressing tables and determines that the destination switching node is the switching node 103. The session software layer 206 then transmits a configuration request to transport software layer 205 together with the right call branch of Figure 12 (call register 1203 and LDCN 1204). However, when the transport software layer 205 receives the configuration request from the session software layer 206, the transport software layer 205 determines that a circular subpath will be configured between the switching node 102 and 101. Accordingly, the transport software layer 205 transmits a re-address indication back to the session software layer 205. The session software layer 206 responds to the re-address indication to remove the session register 1206 and send a re-address request to the transport software layer 205 in the left call branch of Figure 12. In turn, the transport software layer 205 sends a re-address request to the software layer of network 204. The re-address request causes the network software layer 204 to remove the call register 1201, the LDCN 1208 and CRN 1202, and completely remove all the lower protocols associated with the network. this particular call. Also, the network software layer 204 sends a redirection message to the switching node 103.

The session software layer 206 of switching node 102 processes the configuration indication as illustrated in Figure 16, by executing decision blocks 1601 and 1602. Since the node flag is set to indicate that the node number present equal to the destination node number, decision blocks 1608 and 1613 are executed with the determination that is "no" in both cases, resulting in block 1619 being executed. When block 1619 is executed, the software layer session 206 of the switching node 102 determines that the block of numbers containing the telephone number of the BRI station set 123, have been given to the switching node 103. The decision block 1620 determines that a designation node was found in block 1619 and causes blocks 1622, 1623 and 1624 to be executed, which results in a call log and a configuration session record being obtained and a configuration request transmitted in the call branch on the right side of Figure 12 to the transport software layer 205 of the switching node 102. This configuration request is processed by the transport software layer 205 according to Figure 15. The decision blocks 1501, 1502 and 1504 are executed with resultants of "yes" terminations. Since the response to the determination presented by decision block 1504 is "yes", block 1508 is executed resulting in a path that is determined at switching node 103 per link 117. Consequently, the response to decision block 1509 is "yes", and the response to decision block 1510 is "yes" since the route is circular resulting in block 1512 being executed. Execution of block 1512 results in a redirection indication communicated to the software layer of session 206 on the right-hand branch of Figure 12 and the node flag that matches the destination number that does not equal the present node number. In this situation, that a redirection indication is communicated to the session software layer 206 on the right call branch, the node flag is used to indicate to the decision software layer 206 that the transport software layer 205 has determined a circular sub-trajectory. In the session software layer 206, the redirection indication is processed as illustrated in Figure 16. Decision blocks 1601, 1627 and 1630 produce "no" determinations resulting in decision block 2206 being executed. Decision block 2206 determines whether the indication from the transport software layer is a redirection indication. Therefore, the determination made by decision block 2206 is "yes". In response to this determination "yes" decision block 1641 is executed resulting in the execution of block 1642 since the node flag is adjusted to indicate that the destination node number is not equal to the present node number. Execution of block 1642 results in a redirect request communicated to the transport software layer 205 for the left call branch in Figure 12. The session software layer 206 withdraws session log 1206, and the redirect request specifies that the destination number should be the switching node number 103. As will be briefly described, this results in a redirect message sent back to the switching node 103. The transport software layer 205 responds to the redirection request to process this request as illustrated in Figure 15. The determination made by decision block 1501 is "no", resulting in the execution of decision block 1523. Since it is a redirection request, decision block 1528 transfers control to block 1529 that transmits a redirection request to network software layer 204 on the left call branch of Figure 12 The network software layer then transmits a redirection message to the switching node 103. As the redirection request is processed by the network software layer 204 and the lower software layers, these software layers respond to the request of the network software layer. redirection to release the call with the switching node 103 as if the redirection request was a release request.

Figures 18 to 20 illustrate, in flowchart form, the steps performed by an FS application. Decision block 1801 responds to a message or request to determine if it is a configuration request that is received from application level 7. If the answer is yes, decision block 1802 determines whether it is a configuration call from an HSM to establish a call or make a transfer. If the answer is Yes, in decision block 1802, decision block 1805 determines whether it is a transfer request. If the answer is No the control is transferred to block 1803. Block 1803 obtains the destination telephone number of the wireless handset to which the HSM application attempts to establish a call. This destination telephone number is in a field sub-part of the configuration request. Once the destination telephone number is obtained, a new configuration request is transmitted to the lower software layers for the processing block 1804. The action of block 1804 results in a call being directed to the wireless handset or telephone link. destination. Returning to decision block 1802, if the answer is No, this means that a call is received from an entity other than the HSM application. The configuration message is considered to be from a wireless handset or other telecommunications terminal. if the answer in decision block 1802 is No, the control is transferred to decision block 1806. Decision block 1806 determines whether the send all calls feature is active since the call is from another wireless handset or other call terminal. telecommunications if the answer is No in block 1806, the letters "hs" are added to the receiving destination telephone number which causes the call to be directed to the HSM application serving the cordless telephone. After execution of block 1809, the control is transferred to block 1808 using the new number created in block 1809 or 1807, to generate a new configuration request which is then sent to the lower software layers for processing. Returning to decision block 1806, if the answer is Yes, block 1807 changes the destination number to the call coverage system number and transfers control to block 1808 whose operations have already been described. Returning to decision block 1801, if the request is not a configuration request, the control is transferred to decision block 1811. Decision block 1811 determines whether the request is an alert, connection or progress request. Any of these requests indicates that if the bandwidth is required for the call, it will have to be added at that moment. The FS request does not add the bandwidth. As previously discussed, the messages retransmitted in descending order, to the other branch of the call where lower levels, ie the interface manager in level three, request that the connection administrator application establish the appropriate bandwidth through of the network of the switching node. If the answer in decision block 1811 is No, decision block 1813 determines whether the request is a release request. If the answer is No in decision block 1813, the control is transferred to decision block 1816. Decision block 1816 determines whether the request is a request from the HSM requesting a drive for a particular feature. If the answer in decision block 1816 is No, block 1817 retransmits the message by the other branch of the call. Returned to decision block 1913, if the answer is Yes, control is transferred to decision block 1901 of Figure 19. Decision block 1901, determines whether the call associated with the release request has more than two call branches as is illustrated in Figure 12, leaving the session record 1207. For example, a three-way conference call, has three call branches. If the answer in decision block 1901 is No, block 1906 retransmits the release request to the lower software layers. The lower software layers release the entire call, so that the call is no longer established through the switching node. Decision blocks 1907 and 1909 determine whether the handset processor that handles the cordless handset is located in another switching node and the handset is idle. If the answer in both decision blocks 1907 and 1908 is Yes, block 1909 transmits the idle message to the NMM application. In response to this sleep message, the NMM application will transfer the call control functions performed by the FS application to the FS application on the switching node running the HSM application. It should be noted that if the decision in decision blocks 1907 and 1909 is No, control is also returned to decision block 1801 of Figure 18. Returning to decision block 1901, if the answer is Yes, block 1902 sends a request undo merger to the software layers of the lower layers to disconnect just this branching call to multiple branching call. Decision block 1903 then determines if there are more than two active call branches. If the answer is No, block 1904 resets the call flag with multiple branches. If the response of decision block 1903 is Yes, the control is returned back to decision block 1801 of Figure 18. Returning to decision block 1805 of Figure 18, if the answer is Yes, it is a transfer request and the control is transferred to block 1911 of Figure 19. Block 1911 sends an undo merge request to disconnect the branch of the call connected to the HSM application on the current communication node. Block 1912 then sends a merge request to the lower software layers to add the new call branch from the new HSM that just transmitted the transfer request. After execution of block 1912, control is transferred back to decision block 1801 of Figure 18. Returning to decision block 1816 of Figure 18, if the request is a characteristic drive request from the HSM application, control is transferred to the decision block 2001 of Figure 20. In the current implementation, only two features are illustrated as possible. These two features are to send all calls in a three-way conference. A person with skill in the specialty can easily determine how to provide other features. The decision block 2001 determines whether the feature drive is characteristic to send all calls. If the answer is Yes, decision block 2002 determines whether to send all calls is fully active. It is considered in the cordless handset that there is only one button for the feature to send all calls. This button is either used to activate or deactivate the send all calls feature. If the answer in decision block 2002 is No, sending all calls is not currently active, block 2004 marks send all calls as active, before returning control to decision block 1801 of Figure 18. If the answer in decision block 2002 is Yes, block 2003 marks the characteristic to change all calls as inactive before returning control to decision block 1801 of Figure 18. If the answer in decision block 2001 is no, the control is transfers to decision block 2006 that determines whether a conference call is triggered. If the answer in decision block 2006 is no, block 2007 will process any other characteristic drive in a normal way before returning control to decision block 1801. In response to a decision yes, in decision block 2006, the Decision block 2008 determines whether the conference call flag is set. If the conference call flag is set, this means that the cordless handset has completed the call to the third telecommunication terminal and does not want to create the three-way conference. If the response to the decision block 2008, block 209 sends the merge request to the lower software layers, to cause the three branch calls to connect in conjunction with the bandwidth. Block 2011 adjusts the call flag of multiple branches before transferring control back to decision block 1801 of Figure 18. Returning to decision block 2008, if the conference call flag is not adjusted, block 2012 adjusts the conference call and multi-branch call flags, and block 2013 requests the telephone number of the third telecommunications terminal to be added to the current call from the HSM application. After this destination telephone number is received, block 2014 sends a configuration request to the lower software layers with the telephone number, before transferring control back to decision block 1801 of Figure 18. Figures 21 to 29 illustrate the steps performed by an NMM application. Decision block 2101 determines whether a registration request has been received from an HSM application. If the answer is yes, decision block 2102 determines whether the telephone number is owned by the switching node executing the present NMM request. If the answer is yes, block 2103 performs normal processing since it is not necessary to transfer any data from the other switching nodes. if the answer in decision block 2102 is no, block 2104 sends a request to the NMM that owns the telephone number requesting the HSR data. The HSR data is received by block 2106 and block 2107 stores the HSR data and informs the HSM application of this fact. Decision block 2108 waits for a complete log message from the HSM application. If such a complete registration message is not received, block 2109 does error recovery. If a complete log message is received from the HSM, the control is transferred to block 2111 which manages the number "HS" and the telephone number (identifying the control FS) in the present switching node for the HSM application. Finally, block 2112 sends a registration completion message to the proprietary NMM application before returning control to decision block 2101. Returning to decision block 2101, if a registration request has not been received from an HSM application, it is transferred control to decision block 2201 of Figure 22. Decision block 2201 determines whether a request for registration of another NMM application has been received. This occurs if the present NMM application owns the telephone number for a handset attempting to register at the switching node running the other NMM application. Block 2104 of Figure 21 generates said request. If the answer in decision block 2201 is yes, decision block 2202 suspends the HSM application and sends a copy of the HSR data to the other NMM application. If the HSM is in a third switching node, a message will be sent to the NMM application of the third switching node requesting the HSR data. The third NMM application will suspend the HSM and transfer the HSR data again. Decision block 2202 then waits for the record termination message of the other NMM application. If said message is not received, block 2204 performs error recovery. If the record termination message is received, the control is transferred to block 2206 which disconnects the call to the other NMM application and transfers control to block 2207. The last block withdraws the number "HS". Finally, control is transferred to decision block 2101 of Figure 21. Returning to decision block 2201 of Figure 22, if the answer is no, the control is transferred to decision block 2301 of Figure 23. The decision block 2301 determines if an active transfer request is being received. If the answer is yes, decision block 2302 determines whether the telephone number of the wireless handset requesting the transfer is owned by the present NMM application. If the answer is no, block 2304 sends a transfer request to the proprietary NMM request requesting the HSR data. Decision block 2307 tests to check whether the HSR data is received from the NMM application that owns the telephone number. If the answer is no, error recovery is performed by block 2308. If the answer in decision block 2307 is yes, block 2309 stores the HSR data. Then, block 2310 manages the table such that the telephone number points to the switching node executing the FS application. Block 2311 sends a message to the HSM application in the same switching node as the NMM application. Decision block 2312 determines whether an HSM acknowledgment is received. If the answer is no, block 2313 performs error recovery. If the response in decision block 2312 is yes, block 2314 manages the tables such that the number hs points to the HSM application on the current switching node running the NMM application performing blocks 2301 to 2316. Finally , a transfer completion message is sent to the NMM application that owns the telephone number before control is transferred to decision block 2101 of Figure 21. Returning to decision block 2302, if the NMM application possesses the telephone number , block 2303 performs normal processing. This normal processing consists of executing operations similar to those of blocks 2310 to 2314. Returning to decision block 2301, if an active transfer request is not detected, control is transferred to decision block 2401 of Figure 24. The last block The decision determines whether a transfer request that requests HSR data is received. This request is generated by an NMM application executing block 2304 of Figure 23.

Here, blocks 2401-2414 are executed by the NMM application which owns the telephone number of the handset requesting the active transfer. If the answer in decision block 2401 is yes, decision block 2402 determines whether the handset is registered in the switching node running the NMM application. If the answer is yes, the control is transferred to decision block 2901 of Figure 29. Returning to decision block 2402, if the handset is not registered in this switching node, block 2403 sends a request for HSR data to the NMM application in the switching node in which the handset is registered. Decision block 2404 determines whether the HSR data is received. If the answer is no, block 2406 performs error recovery. If the HSR data is received, block 2407 sends the HSR data to the requesting NMM application. Finally, a termination message is sent to the NMM application running on the switching node in which the handset is registered, and block 2409 disconnects the call to the NMM application requesting the HSR data before returning control to the block of decision 2101 of Figure 21. Returning to decision block 2402, if the handset registers in this switching node, the control is transferred to decision block 2902 of Figure 25. Blocks 2902 to 2916 are made by the application Proprietary NMM running on the switching node running the HSM application in control of the handset requesting the transfer. Decision block 2902 determines whether the FS application controlling the handset runs in this switching node. If the answer is yes, block 2908 suspends the FS application, and block 2909 suspends the HSM application. Block 2911 sends the HSR data to the requesting NMM application. Block 2912 manages the table such that the HS number indicates the new HS application that controls the handset after transfer. Block 2913 adjusts the HSM flag. Block 2916 stops suspending the FS application before returning control back to decision block 2101 of FIGURE 21. Returning to decision block 2401, if a transfer request for HSR data is not received, the control is transferred to decision block 2501 of Figure 25. Blocks 2501 to 2516 are made by the NMM application running on the switching node executing the HSM application which controlled the handset requesting the transfer. This is only true if this switching node does not execute the proprietary NMM application. If the answer is yes in decision block 2501, decision block 2502 determines whether the FS application controlling the handset is executed in this switching node. If the answer is yes, decision block 2508 suspends the FS application and block 2509 suspends the HSM application. Block 2511 sends the HSR data to the proprietary NMM application. Block 2512 manages the table, such that the HS number signals the new HS application that controls the handset after transfer. Block 2513 adjusts the HSM flag. Block 2514 disconnects the call from the proprietary NMM and block 2516 stops suspending the FS application before returning control back to decision block 2101 of Figure 21. Returning to decision block 2502 if the FS application does not execute on this switching node, block 2503 suspends the HSM application and block 2504 sends the HSR data to the property NMM application. Finally, block 2506 manages the table to remove the HS number, and block 2507 disconnects the call from the proprietary NMM application, before transferring control back to decision block 2101 of Figure 21. Returning to decision block 2501, if it is not a request for HSR data from the proprietary NMM application, the control is transferred to decision block 2601 of Figure 26. Blocks 2601-2609 are executed by an NMM application that has received a rest message from an FS application that runs on the same switching node. The idle message is generated when the FS application determines that the cordless handset is not active on any call.

The purposes of blocks 2601-2609 are to withdraw the FS application from this switching node with respect to the wireless handset and inform the proprietary NMM application. If the answer in decision block 2601 is yes, decision block 2602 determines whether the current NMM application has the telephone number; therefore, it is the proprietary NMM application. If the answer is yes, block 2603 sends a message to the NMM application in the switching node in which the handset is now registered informing this NMM application that the handset is idle. The message also includes FSR data. Next, block 2604 disconnects the call with the NMM application at the switching node in which the handset is registered before returning control to decision block 2101 of Figure 21. Returning to decision block 2602, if the application NMM does not have the telephone number, the control is transferred to block 2606 that sends a message to the proprietary NMM application that the handset is idle. This message also includes the FSR data. Decision block 2607 waits until a movement of the complete FS application message is returned by the proprietary NMM application. When the message is received, block 2608 removes the FSR data from the switching node, and block 2609 manages the table to retrieve the telephone number before returning control to decision block 2101 of Figure 21. Returning to the block. decision 2601 if the answer is no, control is transferred to decision block 2701. Decision block 2701 determines whether there is a message at rest from another NMM application. This idle message will be transmitted by block 2603 or block 2606 of Figure 26. If the answer is yes in decision block 2701, block 1702 determines whether the NMM application has the telephone number of the handset that has just been left. Resting. if it is the proprietary NMM application, blocks 2703 to 2713 perform the operations of moving the FSR data received in the idle message and activating an FS application in the switching node in which the handset is now registered. If the NMM application does not have this telephone number, then blocks 2101 to 2804 are made by an NMM application in which the handset is active but does not own the telephone number. If the answer in decision block 2702 is yes, decision block 2703 determines whether the handset is registered in this switching node. If the answer is yes, block 2704 stores the FS data and activates the FS application. Finally, block 2606 sends a complete message to move back to the NMM application it sends before transferring the control back to decision block 2101 of Figure 21.

Returning to decision block 2703, if the handset is not registered in this switching node, the control is transferred to block 2707. This latter block sends a message to the NMM application in the switching node executing the FS application for the handset . The message defines that the handset is at rest and that a movement is occurring. After executing block 2707, block 2708 sends the FSR data to the NMM application in the switching node in which the handset is registered. Decision block 2709 waits for a move termination message to be received from the NMM application at the node where the handset is registered. If this message is not received, error recovery is performed by block 2711. If the termination message is received, block 2712 sends a complete message to move to the NMM application on the switching node running the FS application. Finally, block 2713 disconnects the calls with the other two NMM applications before returning control to decision block 2101 of Figure 21. Returning to decision block 2702, if the NMM application does not have the telephone number of the handset that is now Resting, the control is transferred to block 2801 of Figure 28. Block 2801 suspends the HSM application, and block 2802 stores the FSR data. Block 2803 manages the table, such that the FS application in this switching node is active and serves the handset. After executing block 2803, block 2804 sends a complete message to move to the other NMM application. Finally, block 2806 activates the HSM application. It is noted that in relation to this date, the best method known to the applicant to carry out the aforementioned invention, is that which is clear from the present description of the invention. Having described the invention as above, property is claimed as contained in the following:

Claims (22)

1. EIVINICATIONS 1. A method for providing wireless service for a plurality of wireless handsets by a wireless switching system having a plurality of switching nodes, with each of the plurality of switching nodes being connected to an individual set of a plurality of base stations, comprising the steps of: executing a first application for controlling call functions at a first of the plurality of switching nodes, whereby the first application for controlling call functions provides continuous control of wireless calls which originate in the first of the plurality of switching nodes; executing a first application for controlling handset functions in the first of the plurality of switching nodes and the first application for controlling handset functions provides direct control of one of the plurality of wireless handsets connected by one of the first individual set of the plurality of handset functions. base stations to the first of the plurality of switching nodes and one of the plurality of wireless handsets participating in a wireless call, which originates in the first of the plurality of switching nodes; characterized by: transferring control of one of the plurality of wireless handsets to a second application for controlling handset functions that are executed in a second of the plurality of switching nodes before a transfer from one of the plurality of wireless handsets to one of a second individual set of the plurality of base stations, connected to a second of the plurality of switching nodes; and establishing a telecommunications call between the second application to control handset functions and the first application to control call functions, thereby making the first application to control continuous call functions to control the wireless call.
2. 2. The method according to claim 1, characterized in that it further comprises the step of providing control of all call characteristics for wireless calls originating in the first of the plurality of switching nodes by the first application to control Call functions.
3. 3. The method according to claim 2, characterized in that it further comprises the step of transferring the call control for wireless calls involving one of a plurality of wireless handsets, to a second application for controlling call functions that are executing on the second of the plurality of switching nodes on a first of the plurality of wireless handsets that remain inactive on all wireless calls, while the second application for controlling the handset functions of one of the plurality of wireless handsets.
4. 4. The method according to claim 3, characterized in that each of the plurality of wireless handsets has a handset service record that has information defining attributes to each of the plurality of wireless handsets, with each of the handset service records maintained by the application to control handset functions that are executed in a first of the plurality of switching nodes in which each of the plurality of associated handsets, with each of the service registers The handset is connected and the step of transferring control of a first of the plurality of wireless handsets comprises the step of transferring a handset service register from one of the plurality of wireless handsets from the first of the plurality of switching nodes. to the second of the plurality of switching nodes.
5. 5. The method according to claim 4, characterized in that each of the plurality of wireless handsets is assigned for administration functions to an individual of the plurality of switching nodes and each of the plurality of switching nodes executes an application for controlling network management functions, with that each of the applications for controlling functions for network administration controls the management functions in a first of the plurality of switching nodes, in which each of the applications for controlling the network management functions is executed and the stage of transferring the handset service record of one of the plurality of wireless handsets comprises the steps of requesting the handset service registration from a second application to control the network management functions, which are executed in the second of the plurality of handset services. switching nodes for the second application for control the functions of the handset that transmits a first message; requesting in response to the first message, the handset service record from a third application for controlling network management functions running on a third party of the plurality of switching nodes to which a first of the plurality of wireless handsets is allocated per the second application for controlling the network administration functions that transmit a second message; requesting in response to the second message, the handset service record from a first application to control network management functions that are executed in the first of the plurality of switching nodes by the third application to control the network administration functions that they transmit that third message; and communicating in response to the third message the handset service record by the first application to control the network administration functions to the second application to control the network management functions by the third application to control the network administration functions.
6. 6. The method according to claim 5, characterized in that each of the plurality of wireless handsets is assigned an individual addressing number and an application for controlling functions of the handset to control the handset functions of each of the plurality of handsets. wireless handsets, is identified for call routing by forming a first type of addressing numbers, which is the addressing number of each of the plurality of cordless handsets patented with a first pre-defined set of characters so that the type of first addressing number is used by applications to control call functions to establish calls to applications to control handset functions.
7. 7. The method according to claim 6, characterized in that an application for controlling network management functions for each of the plurality of switching nodes is identified by call routing by forming a group of numbers of a second type of network. address numbers which is the addressing number of each of the plurality of wireless handsets assigned to each of the plurality of caching nodes with a second pre-defined set of characters.
8. 8. The method according to claim 4, characterized in that each of the plurality of wireless handsets has a feature service record that has information defining call state and call feature status for each of the plurality of wireless handsets, with each of the feature service registers maintained by the application to control call functions that run on one of the plurality of switching nodes where the wireless handset associated with each of the service registers of feature originates a present wireless call and the step of transferring call control comprises the step of transferring a feature service record of one of the plurality of wireless handsets from the first of the plurality of switching nodes to the second of the plurality of switching nodes.
9. 9. The method according to claim 8, characterized in that each of the plurality of wireless handsets is assigned for management functions to an individual of the plurality of switching nodes and each of the plurality of switching nodes executes a application for controlling the network management functions, whereby each of the applications for controlling the network management functions, controls the management functions in a first of the plurality of switching nodes wherein each of the applications for controlling network management functions are executed and the step of transferring the feature service register of one of the plurality of wireless handsets comprises the steps of sending a first message to a first application to control the network management functions which are executed in the first of the plurality of switching nodes by the first application to control call functions in response to termination of the first wireless call; transmitting the feature service record by the first application to control the network administration functions to a third application to control the network management functions that are executed in a third of the plurality of switching nodes to which a first of the plurality of wireless handsets is assigned; and transmitting the feature service record by the third application, to control the network administration functions to a second application to control the network management functions that are executed in the second of the plurality of switching nodes.
10. 10.- The method according to the claim 9, characterized in that each of the plurality of wireless handsets is assigned an individual addressing number and an application for controlling functions of the handset, to control the handset functions of each of the plurality of wireless handsets, is identified for call routing. by forming a first type of addressing numbers which is the addressing number of each of the plurality of wireless handsets being searched with a first pre-defined set of characters, whereby the type of first addressing number is used by applications for control call functions to establish calls to applications to control handset functions.
11. 11. The method according to the claim 10, characterized in that an application for controlling the network management functions for each of the plurality of switching nodes is identified for call routing by forming a group of numbers of a second type of addressing numbers, which is the number of addressing each of the plurality of wireless handsets assigned to each of the plurality of cached switching nodes with a second pre-defined set of characters.
12. 12.- Wireless switching system for providing wireless service for a plurality of wireless handsets and the wireless switching system has a plurality of switching nodes, with each of the plurality of switching nodes being connected to an individual set of a plurality of base stations, comprising: means for executing a first application for controlling call functions at a first of the plurality of switching nodes whereby the first application for controlling call functions provides continuous control of wireless calls originating in the first of the plurality of switching nodes; means for executing a first application for controlling handset functions in the first of the plurality of switching nodes and the first application for controlling handset functions provides direct control of one of the plurality of connected wireless handsets by means of one of a first individual set of telephones. the plurality of base stations to the first of the plurality of switching nodes and a first of the plurality of wireless handsets participating in a wireless call originating in the first of the plurality of switching nodes; characterized by: means for transferring control of one of the plurality of wireless handsets to a second application for controlling handset functions that are executed in one second of the plurality of switching nodes before a transfer of one of the plurality of wireless handsets to one of a second individual set of the plurality of base stations, connected to a second of the plurality of switching nodes; and means for establishing a telecommunications call between the second application for controlling the handset functions and the first application for controlling call functions thereby making the first application to control continuous call functions to control the wireless call.
13. 13. The wireless switching system according to claim 12, characterized in that it further comprises means for providing control of all call characteristics for the wireless calls originating in the first of the plurality of switching nodes by the first application to control the call functions.
14. 14. The wireless switching system according to claim 13, characterized in that it also comprises means for transferring the call control for wireless calls involved by one of the plurality of wireless handsets to a second application for controlling call functions., which are executed in the second of the plurality of switching nodes when the first of the plurality of wireless handsets becomes inactive in all wireless calls while the second application for controlling the handset functions controls the handset functions of the first of the plurality of wireless handsets.
15. 15. The wireless switching system according to claim 14, characterized in that each of the plurality of wireless handsets has a handset service record that has information defining attributes to each of the plurality of wireless handsets with each one. of the handset service records maintained by the application to control the handset functions that are executed in the first of the plurality of switching nodes, wherein each of the plurality of wireless handsets associated with each of the Handset service records are connected and the means for transferring control of one of the plurality of wireless handsets comprises means for transferring a handset service register of the first of the plurality of wireless handsets from the first of the plurality of switching nodes to the second of the plu of switching nodes.
16. 16. - The wireless switching system according to claim 15, characterized in that each of the plurality of wireless handsets is assigned for administration functions to an individual one of the plurality of switching nodes and each of the plurality of switching nodes executes an application for controlling the network management functions, whereby each of the applications for controlling the network management functions controls the management functions in the first of the plurality of switching nodes in which each of the applications to control the network management functions is executed and the means for transferring the handset service register of the first of the plurality of wireless handsets comprises means for requesting handset service registration from a second application to control the network management functions that is executed an in the second of the plurality of switching nodes by the second application for controlling the functions of the handset that transmit a first message; means for requesting in response the first message, the handset service registration from a third application for controlling the network management functions running on a third of the plurality of switching nodes to which the first of the plurality of wireless handsets it is assigned by the second application to control the network administration functions that transmit a second message; means for requesting in response to the second message, the handset service registration from a first application to control network management functions that are executed in the first of the plurality of switching nodes by the third application to control the functions for administration of network that transmit a third message; and means for communicating in response to the third message, the handset service registration by the first application to control the network administration functions to the second application to control the network administration functions by the third application to control the functions for administration of network.
17. 17. The wireless switching system according to claim 16, characterized in that each of the plurality of wireless handsets is assigned to an individual addressing number and an application to control functions of the handset to control the functions of the handset of each one. of the plurality of wireless handsets is identified for call routing by forming a first type of addressing numbers which is the addressing number of each of the plurality of cordless handsets patented with a first pre-defined set of characters, thereby the first address number type is used by applications to control call functions to establish calls to applications to control handset functions.
18. 18. The wireless switching system according to claim 17, characterized in that an application for controlling the network administration functions for each of the plurality of switching nodes is identified by call routing by forming a group of numbers of a second type of addressing numbers which is the addressing number of each of the plurality of wireless handsets assigned to each of the plurality of caching nodes with a second pre-defined set of characters.
19. 19. The wireless switching system according to claim 15, characterized in that each of the plurality of wireless handsets has a feature service record that has information defining call status and call feature status for each of the plurality of wireless handsets with each of the feature service registers maintained by the application to control call functions executing on the first of the plurality of switching nodes, wherein the wireless handset associated with each of the feature service records originates a present wireless call and the means for transferring call control comprises means for transferring a feature service record of the first of the plurality of wireless handsets from the first of the plurality of switching nodes to the second of the plurality of switching nodes.
20. 20. The wireless switching system according to claim 19, characterized in that each of the plurality of wireless handsets is assigned for administration functions to an individual of the plurality of switching nodes and each of the plurality of nodes of switching executes an application for controlling the network management functions whereby each of the applications for controlling the network management functions controls the management functions in the first of the plurality of switching nodes, in which each of the applications for controlling the network management functions are executed and the means for transferring the feature service register of the first of the plurality of wireless handsets comprises means for sending a first message to a first application for controlling the network management functions that run on the first of the pl urality of switching nodes by the first application to control call functions in response to termination of the first wireless call; means for transmitting the feature service record by the first application for controlling network management functions to a third application for controlling network management functions running on a third of the plurality of switching nodes to which the first of the plurality of cordless handsets is assigned; and means for transmitting the feature service register by the third application for controlling the network management functions to a second application for controlling the network management functions in the second of the plurality of switching nodes.
21. 21. The wireless switching system according to claim 20, characterized in that each of the plurality of cordless handsets is assigned to an individual addressing number and an application for controlling the handset functions of each of the plurality of handsets. wireless, is identified by call routing by forming a first type of addressing numbers which is the addressing number of each of the plurality of wireless handsets catenated with a first pre-defined set of characters thereby making the first number type Addressing is used by applications to control call functions, to establish calls to applications to control handset functions.
22. 22. The wireless switching system according to claim 21, characterized in that an application for controlling the network management functions for each of the plurality of switching nodes is identified by call routing by forming a group of numbers of a second type of addressing numbers which is the addressing number of each of the plurality of wireless handsets assigned to each of the plurality of caching nodes with a second pre-defined set of characters.