text: the detailed description set forth below in connection with the appended drawings is intended as a description of exemplary embodiments of the present invention and is not intended to represent the only embodiments in which the present invention can be practiced . the term “ exemplary ” used throughout this description means “ serving as an example , instance , or illustration ,” and should not necessarily be construed as preferred or advantageous over other embodiments . the detailed description includes specific details for the purpose of providing a thorough understanding of the present invention . however , it will be apparent to those skilled in the art that the present invention may be practiced without these specific details . in some instances , well - known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the present invention . an exemplary wireless communications device such as a cellular telephone or similar device can be used to communicate with various wireless networks . access to these networks can be managed by the device in a way that is transparent to the user . more specifically , the communications device can automatically designate whether , and in what format , a call can be placed on each one of the various wireless networks , without the user needing to know which network the call is originated on or how the call origination request is handled for originating the call . the manner in which the wireless network is designated may vary from device to device , and those skilled in the art will readily be able to determine the selection criteria best suited for the particular application . in one embodiment of the communications device , an algorithm or similar methodology can be used to determine whether a call is allowed on various wireless networks based on a call origination request by the user or a call origination request by an application such as a browser . the automatic formatting of the call origination request and selection of a compatible wireless network can then be made . determination of whether a call is allowed on a particular network may be made as a function of user preferences . preferences can be programmed into the communications device , such as by programming the device &# 39 ; s communications card or cards , by the user before making the call . alternatively , the user preferences can be set by the manufacturer at the factory or by the carriers , phone service or sales outlet before sale . virtually any algorithm could be implemented to manage access to the various wireless networks . this concept can be extended to other wireless technologies including any satellite or terrestrial application . network access in a wireless communications device can be managed with a software based processor system , or any other configuration known in the art . an exemplary hardware configuration for a software based processor system is shown in fig1 . the processor system has a microprocessor 102 at its core with non - volatile memory 104 . non - volatile memory may comprise memory that is resident on the communications device , or memory on a communications card that may be inserted into the communications device . the microprocessor 102 can provide a platform to run software programs that , among other things , manage call origination on various networks based on ( 1 ) the preferences of the user which can be programmed into the non - volatile memory 104 ; ( 2 ) other information indicative of whether a call is allowed on the various networks ; and ( 3 ) the protocol compatibility of those networks with the call as originated by the user . a digital signal processor ( dsp ) 108 can be implemented with an embedded communications software layer which runs application specific algorithms to reduce the processing demands on the microprocessor 102 . for example , during call origination , the dsp 108 can be used to provide encoding and modulation of text messages from the keypad 106 before those text messages are transmitted to a far end user through an analog front end 112 . the dsp 108 can also provide decoding and demodulation of text messages from the far end user received through the analog front end 112 before presentation to a display 110 . the software layer also interfaces the dsp hardware to the microprocessor 102 and may provide low level services such as allocation of resources to allow the higher level software programs to run . the exemplary processor system supports user entry and editing functions . such functions may be utilized , for example , to program user preferences into the communications device or its memory card ( s ). the user interface can be fully menu driven or implemented in any other fashion . in the menu driven user interface , on - screen options can be presented to display 110 in the form of a main menu for programming the communications device . from the main menu , the user can select an on - screen option for programming user network preferences through various keypad manipulations . once this on - screen option is selected by the user , the microprocessor 102 retrieves a list of networks from the non - volatile memory 104 and presents the list to the display 114 in a sub - menu format . the sub - menu may contain a list of all networks supported by the communications device , or alternatively can display a list of networks for voice services separately from data services . a sub - menu format is shown in fig2 with an exemplary type of information for determining whether a call is allowed on a particular network . the “ fixed dialing list ” comprises all phone numbers allowed by an exemplary communications device or by a card within the communications device . in this example , each phone number is represented by a user - defined code that allows for easy identification and selection by the user when he desires to place a phone call . thus , phone numbers represented by home 202 , office 204 , doctor 206 , school 208 and emergency 210 are allowed in the illustrated example . however , any combination of phone numbers may be allowed according to the user preferences . it is also possible that a user may program a “ block list ,” including numbers that are not allowed on a particular network . in that case , if a user dials a number that is located on the block list , the communications device will reject the call . it is understood that a communications device may contain multiple communications cards , thereby becoming constrained by multiple , different fixed dialing , block , or other such permission - driven lists . it is further understood that any one communications device may , because of multiple cards , be enabled to originate a call on a first network where the dialed phone number is represented on that card &# 39 ; s fixed dialing list , but be restrained from originating the same call on a second network , where the dialed phone number is represented on that card &# 39 ; s block list . thus , for any dialing string input received by the communications device , each card must be tested for its ability to allow the call . an exemplary microprocessor multi - layer software architecture is shown in fig3 . the software architecture includes a user interface 302 , a call manager 304 and a protocol layer 306 running on a microprocessor platform . the dsp 108 and analog front end 112 are shown for completeness , but will not be discussed further . alternatively , each software layer can be run on separate processors or any combination of processors . the processors can be internal to the communications device , or alternatively , one or more processors could be located in an external device such as a laptop computer connected to the communications device . as those skilled in the art will appreciate , the implementation details may vary depending on the particular communications application and the overall design constraints . user interface 302 provides structure to the interaction between the user and the communications device . during the programming of user network preferences , the user interface 302 may be used to generate the menu and sub - menus presented to the display from data stored in the non - volatile memory 104 . the user interface 302 may also be responsible for deleting , adding and reordering user preferred networks within the non - volatile memory 104 in response to menu and sub - menu selections . the user interface 302 may be a software program , or set of programs , that sits as a layer above the call manager 304 . the software programs can be applications such as a phone book , sat ( sim application toolkit ), sat cc ( sat call control ), sms , browser , e - mail or any other software programs . when the user originates a call , or launches an application that initiates a call , the user interface 302 determines the parameters of the call from the keypad entries , including for example service parameters and dialing string input information . the service parameters typically include , among other things , the type of service requested . for example , the requested service can be a voice call , a data call , or any other service provided by the carrier . dialing string input information typically includes data representing the numbers entered by a user who dialed a phone number on the keypad of the communications device . the user interface 302 may also include other service parameters such as the quality of service needed to support the call . for example , if the user initiates a video application , the user interface 202 may determine that the call requires a data rate of 64 kbits / s or higher . the call manager 304 can be used to manage access to various networks in a way that is transparent to the user . based on the parameters derived from the user &# 39 ; s call origination request , the call manager 304 determines whether the call is allowed on each one of the various networks . the call manager 304 may also determine other network selection parameters , such as the service compatibility of all the networks supported by the communications device . then , the determination of whether a call is allowed may be made for only those networks that are first determined to be compatible with the call . for example , if the communications device supports cdma 1x , cdma 1xev - do , gsm , gprs , and umts networks , and the service requested is a video application , the call manager 304 may determine that only the cdma 1xev - do and umts networks can support this application . in that event , the call manager 304 will limit its inquiry regarding whether the call is allowed to just those two compatible networks . the criteria used to determine whether a call is allowed on a particular network managed in a selection algorithm , which is explained in further detail below with reference to fig5 . fig4 is a flow diagram showing the operation of the call manager . when power is first applied to the communications device , the call manager may attempt to register with the user preferred network stored in non - volatile memory in step 402 . once registered , the call manager accepts a call origination request from the user through the user interface in step 404 . the call origination request includes various parameters such as service parameters ( e . g . type of service requested by the user and the quality of service needed to support the call ) and dialing string input information . in step 406 , the call manager may identify the networks supported by the communications device that are service compatible with the call origination request . alternatively , this step may be omitted , such that the determination of whether a call is allowed ( explained below ) may be made for each network , whether it is service compatible or not . in step 408 , the call manager determines whether the call identified in the call origination request is allowed on the network currently registered . this determination is made as a function of the output of an identification algorithm , the details of which are explained below with reference to fig5 . if the identification algorithm output indicates that the call is allowed on the registered network , the call manager attempts to originate a call on that network in step 410 . if the registered network is not among the networks on which the call is allowed , or if the service for the registered network is lost , then the call manager selects one of the other “ allowed ” networks for re - registration in step 412 . in that case , the call manager first determines whether any other networks were identified as “ allowed ” by the identification algorithm output and , if so , determines whether any of those networks are among the service compatible networks . once an alternative network is selected , the call manager will de - register the communications device from the current network and attempt to register with the new selected network in step 414 . if the call manager is unsuccessful in registering the communications device with the new selected network , the call manager will select another network for registration among the service compatible networks in step 412 . finally , the call manager will attempt to originate a call over the registered network in step 416 . fig5 is a flow diagram illustrating an exemplary identification algorithm whose output is utilized by the call manager described above . the identification algorithm implements a method for identifying which of the networks that a communications device is compatible with will be allowed by the communications device to support a dialed call . the identification algorithm also implements a procedure for formatting the call origination request so that the call may be originated on different networks . a communications device may operate on certain networks by means of a communications card adapted to a particular network or group of networks . a communications device may also have multiple such cards , enabling it to operate on multiple networks or groups of networks . for example , a communications device may simultaneously support both a sim ( subscriber identity module ) card enabling it to operate on gsm and gprs networks , a r - uim ( removable user identity module ) card enabling it to operate on a cdma network or hybrid cdma / gsm network , and a usim ( utms sim ) card enabling it to operate on a umts network . of course , it is to be understood that the invention is not limited to any particular type of card or card combination , but is applicable to communications devices that may be adapted to operate on any of a plurality of existing or later - developed wireless networks . when a user &# 39 ; s call origination request is received ( as indicated at block 404 in fig4 ), the identification algorithm illustrated in fig5 accepts the user &# 39 ; s dialing string as an input at block 500 . at block 502 , the algorithm considers whether the dialing string input indicates an emergency number . for example , in certain areas of the united states , a dialing string comprising the digit sequence “ 911 ” indicates an emergency number . if the request is for an emergency call , the call manager marks the call “ allowed ” for all available networks at block 504 , indicating that the call may be originated on any available and service compatible network . a service compatible network is one that is compatible with a communications card within the communications device . the algorithm may skip the remaining usual steps in the case of an emergency call , direct the call manager to originate the emergency call on the currently registered network , and continue to attempt call origination on any available network until the call is successfully placed . if , on the other hand , it is determined at block 502 that the call origination request does not comprise an emergency number , then at block 506 the algorithm selects one card from a plurality of communications cards and proceeds to test and format the call origination request so that the call can be rejected from or placed on the network that is compatible with the selected card . at block 508 , it is determined whether the call request is allowed for the selected card . a call may be allowed , for example , if the dialing string input received with the call origination request is contained in a fixed dialing list that a user has programmed into the communications card . such a situation may occur , for example , when a parent provides a wireless communications device to a child and programs the communications card to only allow the child to dial certain telephone numbers . this has the effect of causing the communications device to operate only for the purpose of dialing those numbers . of course , there are other situations in which such a permissive dialing list might be created . thus , at block 508 , information such as fixed dialing lists , blocked call lists , or other user - defined information is accessed for the purpose of comparing the dialing string input to the information and determining whether the call is allowed . if it is determined at block 508 that the call is not allowed , for example because the dialing string does not represent a number included on a fixed dialing list , or represents a number included on a blocked call list , then at block 510 the call is marked “ not allowed ” for networks compatible with the selected card . at block 512 it is queried whether additional networks , compatible with other communications cards within the communications device , are available to support the call . if not , the call is rejected at block 514 and the call is never originated . otherwise , the algorithm returns to block 506 , where the next card and its compatible networks are selected to test for its availability to support the call . such a situation may occur when a communications device includes two separate communications cards , each having its own fixed dialing list such that a phone number represented by the dialing string input appears on one of the lists but not on the other . in that case , the call would be “ not allowed ” for the networks accessible with one of the cards , but may be allowed on the networks accessible with the other card . returning to block 506 , in the event that the call request is deemed allowed for the first selected card , the algorithm checks at block 516 whether the dialing string must be converted to a new number . for example , if the dialing string input received at block 500 represents a pre - set command programmed by the user into the communications card to represent a frequently - used telephone number , it must be converted to a new dialing string representative of the actual telephone number . or , it may need to be converted so that it includes appropriate digits for being placed as a long distance call . if , for any reason , it is determined that the dialing string must be converted , then it is converted to a new dialing string at block 517 , and at block 518 the new dialing string is checked to determine whether it is an emergency number . if so , the call is marked at block 520 to indicate that it is an “ allowed new emergency number ” for the selected mode . this may occur if the dialing string represents a user - defined code for an emergency number . that user defined - emergency code must then be changed to an actual emergency number , and this number will be recognized at block 518 as an emergency number . otherwise , the call is marked at block 522 to indicate that it is an “ allowed new normal number ” for the selected card , wherein “ normal ” denotes that the call is not an emergency call . returning to block 516 , if it were instead determined that the dialing string input did not need to be converted to a new number , then at block 524 the algorithm queries whether the dialing string input represents a ss ( supplementary service request ) or a ussd ( unstructured ss data request ). for example , certain information within a dialing string may indicate to a carrier associated with the selected network that a service request is being dialed . in that event , the dialing string is converted to an ss or ussd request code and the call is marked at block 526 to indicate that it is an “ allowed ss / ussd ” for the selected network . otherwise , the call is marked at block 528 to indicate that it is an “ allowed original number ” for networks compatible with the selected card . in the exemplary identification algorithm described above , an incoming call request may have resulted in one of at least six different markings to indicate whether and in what form it was allowed on the selected card , as indicated at blocks 504 , 514 , 520 , 522 , 526 and 528 . moreover , in the event that a communications device comprises multiple communications cards , a call request may be marked with any combination of two or more of the markings that represent the conditions indicated at blocks 504 , 514 , 520 , 522 , 526 and 528 . while the identification algorithm input comprises at least one data field , which contains the dialing string input , the output may comprise two or more data fields . one output data field contains a dialing string , which may be identical to the dialing string input or may be altered as a result of the algorithm &# 39 ; s operative steps . a second data field may include one or more bits for indicating the marking conditions representative of the conditions indicated at blocks 504 , 514 , 520 , 522 , 526 and 528 . the bits may be appropriately set according to the determinations of the identification algorithm . a third data field may include the same number of bits for marking the call as the second data field , with the difference between the two fields being the card or networks that the bits are set for . for example , a three - field selection algorithm output may include a dialing string in the first field , a set of bits in the second field set to indicate one of the marking conditions for a first network , and a set of bits in the second field set to indicate one of the marking conditions for a second network . moreover , extra fields may be used to contain alternate dialing strings , which may be different in the algorithm output for each of the different communications cards . alternatively , the selection algorithm may generate two or more separate outputs , one for each network . in that case , each output may comprise two data fields , one for the dialing string ( whether original or changed ) and one for the marking condition . of course , those skilled in the art will recognize that other variations are possible , and that for any particular network , communications card , mobile device or combination thereof , a call origination request may require any of a number of different markings to indicate its ability to be originated on that network . after the dialing string input has been accepted or altered and / or marked for the selected network , the algorithm checks at block 530 whether other networks are available in order to handle the call . if so , the algorithm returns to block 506 where the next network is selected . the same procedure previously described is then followed for the newly selected network , and this process continues until the call has been appropriately marked for each available network that the communications device is compatible with . once each network or card has been considered , it will be determined at block 530 that no further networks are available . at block 531 , the algorithm considers whether any of the calls have been marked as an emergency call . for example , a call marked at block 520 is one that has had its dialing string changed such that the new dialing string indicates an emergency call . if , at block 531 , it is determined that there is an emergency call , then the call is marked at block 533 as allowed on all networks . at block 532 , the various markings generated for each iteration of the algorithm as described above are considered . the algorithm selects an appropriate network on which the call is to be originated as a function of the markings . for example , if a call is marked allowed for a first network and marked allowed for a second network , the algorithm may direct the call manager to originate the call on whichever one of the first or second networks is currently registered . as another example , if a call is marked allowed on a first network and rejected on a second network , but the second network is the currently active one , the algorithm may direct the call manager to disconnect the second network , re - register the first network , and originate the call on the now - active first network . or , if the call has been marked as an emergency , it is allowed on all networks and will therefore be originated on the currently registered network . of course , additional examples regarding how a network may be selected at block 532 , including the consideration of various markings that may have been generated at blocks 520 , 522 , 528 , 526 , 504 and 533 , are also possible . for example , when the dialing input string comprises an emergency number , the algorithm may , at block 532 , direct the call manager to attempt to originate the call on the current active network . if the origination attempt fails after a certain amount of time , which may be set for example by the network carrier , the communications device manufacturer , or some other source , the algorithm may direct the call manager to retain the current network as the active network and repeat the call origination request , or may direct the call manager to disconnect from the current network , switch to a new active network , and attempt to originate the call on the new active network . the call manager may repeat either situation , or any combination of these situations , until the emergency call is successfully originated on a compatible network . in a second possible case , the dialing input string may be changed to a new emergency number for a first communications card , and either changed to a new normal number or retained as the original normal number for a second communications card . in this case , the algorithm may direct the call manager to originate the emergency call on the network compatible with the first communications card . if that is the currently active network , the call may be originated immediately . otherwise , the call manager may disconnect from the active network , register the network compatible with the first call , and then attempt to originate the emergency call on the now - active network . as described above , the emergency call may be originated via a series of origination attempts , each of which may time out after a predetermined length of time . alternatively , if an attempt to originate the emergency call fails , the call manager may switch to the other network , and attempt to originate the call using the normal number , whether it has been changed by the algorithm or retained as the original dialing string input . whichever network is used , and whether the dialing string is a normal or emergency dialing string , the call origination may be made transparent to the user of the communications device . for example , a user interface may display the call origination on either network as an “ emergency call .” at the end of the call , the call manager may either remain on the active network , or switch to another network compatible with the communications device &# 39 ; s other communications card , according to a system selection preference . such preference may be determined by the user , or by default settings made by the communications device manufacturer , or by some other method . in another case , the algorithm may cause the dialing string input to be changed to a new emergency number for a first communications card , and either changed to an ss or ussd , or rejected , for a second communications card . in this case , the algorithm may cause the call manager to originate the emergency number on the network compatible with the first communications card as described above . alternatively , the call manager may alternate between attempts to originate the emergency call on the network compatible with the first communications card , and attempts to originate the ss or ussd call on the network compatible with the second communications card . in yet another case , the dialing string input may be changed by the algorithm to a new emergency number for each of two different cards in the communications device . in this case , the algorithm may direct the call manager to attempt to originate the emergency call on whichever network is currently active . if the call origination attempt fails , the call manager may either re - attempt to originate the call , or switch to the network compatible with the other communications card , and attempt to originate the call using the other emergency number on the now - registered network . subsequent origination attempts , whether sequentially on the same network , alternating between multiple networks , or some combination thereof , may continue until the emergency call is successfully originated . at the end of the call , the call manager may insure registration or re - registration of the originally active network , or may retain the currently active network , according to system selection preference . in a similar case , the dialing string input may be a normal number for each of two communications cards , and may be unchanged by the algorithm . as the above case , where the number was an emergency number for both cards , the call manager may attempt to originate the call on the currently active network , and may make any subsequent origination attempts either on the same network or by alternating between compatible networks . after the call is terminated , the call manager causes the communications device to have either network registered , according to system selection preference . in yet another possible case , the dialing string input may be rejected on a first communications card , but accepted or changed to a new normal number , ss or ussd on a second card . in such a case , the call manager may attempt to originate the ss or ussd on the network compatible with the second card , whether that network is currently active or must be registered first . the call manager may repeat origination attempts until the ss or ussd call is placed , and then cause either of the networks to be registered after termination of the call , according to system selection preference . still another possibility is that the dialing string input is rejected by the algorithm for both communications cards . in this case , the call is simply rejected , and no origination attempt is made for either network . of course , it is to be understood that for a plurality of networks with which a communications device may be compatible ( i . e . multiple communications cards ), and the plurality of possible markings , exemplary ones of which have been described above , a large number of variations and combinations of markings are possible for any received call request . it is also to be understood that while the exemplary scenarios described above involved two communications cards and two networks , the concepts of the present invention are applicable to communications devices that house any other number of communications cards and are compatible with any number of communications networks . while the exemplary algorithm may generally proceed to place emergency calls on any available network immediately , or to select currently active networks for placing allowed calls first , any order of network selection may be implemented . such implementation may be a function of various criteria such as efficiency , user preference , and the like . whichever network is ultimately selected for handling the call , at block 534 ( as also indicated at block 410 in fig4 ), the call is originated on the selected network . the various illustrative logical blocks , modules , and circuits described in connection with the embodiments disclosed herein may be implemented or performed with a general purpose processor , a digital signal processor ( dsp ), an application specific integrated circuit ( asic ), a field programmable gate array ( fpga ) or other programmable logic device , discrete gate or transistor logic , discrete hardware components , or any combination thereof designed to perform the functions described herein . a general - purpose processor may be a microprocessor , but in the alternative , the processor may be any conventional processor , controller , microcontroller , or state machine . a processor may also be implemented as a combination of computing devices , e . g ., a combination of a dsp and a microprocessor , a plurality of microprocessors , one or more microprocessors in conjunction with a dsp core , or any other such configuration . the methods or algorithms described in connection with the embodiments disclosed herein may be embodied directly in hardware , in a software module executed by a processor , or in a combination of the two . a software module may reside in ram memory , flash memory , rom memory , eprom memory , eeprom memory , registers , hard disk , a removable disk , a cd - rom , or any other form of storage medium known in the art . an exemplary storage medium is coupled to the processor such that the processor can read information from , and write information to , the storage medium . in the alternative , the storage medium may be integral to the processor . the processor and the storage medium may reside in an asic . the asic may reside in a user terminal . in the alternative , the processor and the storage medium may reside as discrete components in a user terminal . the previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention . various modifications to these embodiments will be readily apparent to those skilled in the art , and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention . thus , the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein .