the innovative teachings of the present invention will be described with particular reference to the presently preferred exemplary embodiments . however , it should be understood that this class of embodiments provides only a few examples of the many uses of the innovative teachings herein . in general , statements made in the specification of the present invention do not necessarily delimit any of the claimed invention . fig1 shows the sending of in trigger elements to msc and gmsc . in order to increase intelligibility of fig1 , standardized 3gpp acronyms related to the camel standard are used to indicate the different elements of the figure . these acronyms are known to the person skilled in the art , and include : signal flows between the different elements are indicated in fig1 by arrows . fig2 shows one embodiment of the present invention , which represents the sending of in trigger elements to sgsn . the arrows indicate the data flows from hlr to core network . the hlr uses map ( refer 3gpp ts 29 . 002 [ 4 ]) for the transfer of the in trigger elements to the core network . table 1 provides an overview of in trigger elements serving different purposes . as such , they are sent to different entities in the mobile network . the entities in the mobile network that may receive in trigger elements are : msc , gmsc and sgsn . this is further indicated in table 2 . tables 3a through 3c provide in subscriber profile structures per range of entities . the entities in the mobile network that may receive in trigger elements are msc , gmsc and sgsn . the used terms comprise : msc range 1 : this is an msc number ; it represents a single msc or a group of mscs . if msc range 1 represents a group of mscs , then msc range 1 would contain the leading digits for those msc numbers . example : + 31 516 20456 may represent a single msc ; + 31 516 20 may represent all mscs with leading digits + 31 516 20 . there may , for example , be 3 msc ranges in a particular in subscriber profile : one msc range for vplmn that does not support camel phase 2 default msc range : when subscriber roams in an msc for which no profile is defined , then the default profile applies . sgsn range 1 : this is an sgsn number or sgsn number range . same applies for sgsn range 2 , sgsn range n and default sgsn range . gmsc range 1 : this is a gmsc number or gmsc number range . same applies for gmsc range 2 , gmsc range n and default gmsc range . gmsc range 1 — home : the settings defined for gmsc range 1 — home apply when the subscriber receives a call in that gmsc , whilst the subscriber is registered in an msc in the hplmn . gmsc range 1 — roaming : the settings defined for gmsc range 1 — roaming apply when the subscriber receives a call in that gmsc , whilst the subscriber is registered in an msc not in the hplmn . o - csi , t - csi etc . : the presence of a particular camel trigger element in the profile definition for a particular msc range , sgsn range or gmsc range , means that that camel trigger element applies for that network node ( range ). & lt ; index & gt ;: the & lt ; index & gt ; value indicates which o - csi ( or t - csi , d - csi etc .) definition applies for this msc range , sgsn range or gmsc range . for each camel trigger element type , an array of definitions is configured . the & lt ; index & gt ; value selects one camel trigger element definition from the corresponding array . & lt ; value & gt ;: for oick and tick , a value definition is used . e . g . oick =“ 567 ”. this corresponds with the oick definition in existing products . fallback settings : the fallback settings define the hlr behaviour in the case that the msc where the subscriber registers does not support the required camel phase , as defined by the profile for that msc . there may be a fallback setting per camel trigger element . if the in subscriber profile is defined in accordance with camel roaming agreements , then there should never be a need for the hlr to apply the fallback options . the profile should match the available camel capability in each vplmn . fallback may occur if an msc in a vplmn has ( temporarily ) de - activated camel . the occurrence of fallback action indicates an erroneous situation . hence , a warning should be generated when fallback occurs . the principle described in the present invention may be extended to cover other subscriber settings as well . examples are : packet data protocol ( pdp ) context profile ; by providing different pdp context profiles , depending on the network , the hplmn operator can restrict the destinations that are available for roaming gprs subscribers ; odb settings . according to the present invention , the hlr defines a set of in subscriber profiles . each subscriber may have an index to an instance of an in subscriber profile . each in subscriber profile consists of a set of three lists , comprising msc addresses , sgsn addresses and gmsc addresses . an msc address may be the address of a single msc or may represent a group of mscs . multiple 2g mscs in a plmn ; multiple mscs within a plmn ; multiple mscs in a country , regardless of plmn they belong to . sgsn addresses and gmsc addresses may be grouped in a similar way . per msc address entry , sgsn address entry and / or gmsc address entry , an “ msc in profile ”, “ sgsn in profile ” and / or “ gmsc in profile ” respectively , is defined . in the following we describe an example msc in profile according to the present invention . an msc in profile , associated with an msc address entry , shall reflect an exact in profile that shall be available when a subscriber registers in that msc ( or in one of the mscs belonging to that msc group ). only in trigger elements that are applicable to msc may be included in the msc in profile definition . refer to table 2 . an msc in profile definition shall include adequate fallback settings , which indicate the hlr &# 39 ; s behaviour in the case the msc &# 39 ; s capability do not allow for the sending of the indicated profile . the msc in profile may consist of any valid combination of camel standardised in trigger elements or ericsson - specific in trigger elements . in the following we describe an example sgsn in profile according to the present invention . an sgsn in profile , associated with an sgsn address entry , shall reflect an exact in profile that shall be available when a subscriber attaches to that sgsn ( or to one of the sgsns belonging to that sgsn group ). only in trigger elements that are applicable to sgsn may be included in the sgsn in profile definition , as shown in table 2 . in the following we describe an example gmsc in profile according to the present invention . a gmsc in profile , associated with a gmsc address entry , shall reflect an exact in profile that shall be available when that gmsc ( or a gmsc from that gmsc group ) interrogates the hlr for terminating call handling . only in trigger elements that are applicable to gmsc may be included in the gmsc in profile definition , as shown in table 2 . within a gmsc in profile , a further distinction is made regarding the msc where the subscriber is registered at the moment of receiving a call . when a subscriber receives a call , that subscriber may be in the hplmn or may be roaming abroad . when the subscriber is in hplmn , the hlr may want to send different trigger elements to gmsc than when subscriber is roaming abroad . in the following we describe an example scenario according to the present invention . subscriber in hplmn : hlr sends t - csi to gmsc , whereby t - csi contains a service key that denotes vpn service . the on - line charging for this call is done with vt - csi in vmsc . subscriber in vplmn : hlr sends t - csi to gmsc , whereby t - csi contains a service key that denotes vpn service and on - line charging . in the following we describe an example in subscriber profile according to the present invention . tables 3a through 3c present an example of an in subscriber profile . it is divided in the three main groups : msc - specific in trigger elements ( table 3a ); sgsn - specific in trigger elements ( table 3b ); and gmsc - specific in trigger elements ( table 3c ). each main group is a sequence of address ranges . per address range , there is a profile definition . per subscriber group , a dedicated in subscriber profile is required . within an operator &# 39 ; s network , there are very few subscriber groups , in as far as in differentiation is concerned . examples : within each profile definition ( for msc , sgsn or gmsc ), there are references to individual camel trigger elements and to ericsson - proprietary trigger elements . the actual contents of each camel trigger element are contained in separate lists . for each camel trigger element type , there is a separate list of trigger type definitions . in this way , a single definition of a particular camel trigger type may be used in multiple msc in profiles etc . each o - csi profile definition has the following structure . this definition is in compliance with the etsi / 3gpp defined structure , as shown in table 4 . although preferred embodiments of the system , method , and apparatus of the present invention have been illustrated in the accompanying drawings and described in the foregoing detailed description , it is recognized by those skilled in the art , that the present invention is not limited to the embodiments disclosed , but is capable of numerous rearrangements , modifications , and substitutions without departing from the spirit of the present invention as set forth and defined by the following claims .