Abstract:
A method, apparatus and a computer readable record media storing instructions for executing the same method for interfacing among a hybrid type synchronous or asynchronous terminal to a core network in a next generation mobile telecommunications system. The hybrid type synchronous or asynchronous radio network determines the operating type of the core network when the core network has a connection thereto, and sends the determined core network operating type information and information related to the core network to the hybrid type synchronous or asynchronous terminal, thereby allowing the synchronous or asynchronous terminal to smoothly perform a data interfacing operation with the core network.

Description:
This application is a continuation of Ser. No. 09/564,941 filed May 4, 2000 now U.S. Pat. No. 6,741,868. The entire disclosure of the prior applications are considered as being part of the disclosure of the accompanying application and are hereby incorporated by reference therein by their entireties. 

   FIELD OF THE INVENTION 
   The present invention relates in general to a technique for interfacing among a mobile terminal, .a base station (BS) and a core network in a next-generation mobile telecommunications system, and more particularly to a method, an apparatus and a computer readable record media storing instructions for executing the same method for interfacing among a hybrid type mobile terminal, a hybrid type base transceiver station/base station controller (BTS/BSC) and a core network in a next-generation telecommunication system, e.g., an international mobile telecommunications-2000 (IMT-2000) system and so on, in which a hybrid type synchronous or hybrid type asynchronous radio network determines an operating type of the core network when the core network has a connection thereto, and sends information about the determined core network operating type and information related to the core network to a hybrid type mobile terminal. 
   In more detail, the present invention relates to a method, an apparatus and a computer readable record media storing instructions for executing the same method for interfacing among a hybrid type mobile terminal, a hybrid type base transceiver station/base station controller (BTS/BSC) and a core network in a mobile telecommunications system, wherein a hybrid type synchronous radio network having a hybrid type BTS/BSC determines the operating type of the core network when the core network has a connection thereto, and sends the determined core network operating type and information related to the core network to the hybrid type synchronous terminal over a synchronous channel (Sync channel), and the hybrid type synchronous terminal recognizes the operating type of the core network on the basis of the core network operating type information (hereinafter, refers to “CN type”) and sets a protocol according to the information related to core network. 
   Further, the present invention relates to a method, an apparatus and a computer readable record media for executing the same method for interfacing an asynchronous terminal and a hybrid type asynchronous BTS/BSC with a core network in a mobile telecommunications system, wherein a hybrid type asynchronous radio network having a hybrid type asynchronous BTS/BSC determines an operating type of the core network when the core network has a connection thereto, and sends the determined core network operating type information and information related to the core network to a hybrid type asynchronous terminal over a broadcast control channel (BCCH), and the hybrid type asynchronous terminal recognizes the core network on the basis of the core network operating type information and sets a protocol according to the information related to the core network. 
   DESCRIPTION OF THE PRIOR ART 
   In a conventional synchronous mobile telecommunications system, a synchronous terminal is connected to a synchronous radio network (for example, a CDMA-2000 radio network), and an ANSI-41 network is connected to a core network. 
   In a conventional asynchronous mobile telecommunications system, an asynchronous terminal is connected to an asynchronous radio network (for example, a universal mobile telecommunication system (UMTS) terrestrial radio access network (UTRAN)), and a global system for mobile communications-mobile application part (GSM-MAP) network is connected to a core network. 
     FIG. 1  shows core network interface architectures of the conventional synchronous/asynchronous mobile telecommunication systems as mentioned above. 
     FIG. 1A  is a view showing the core network interface architecture of the conventional synchronous mobile telecommunications system. In this drawing, the reference numeral  11  denotes a synchronous terminal,  12  denotes a synchronous radio network (i.e., a code division multiple access-2000 (CDMA-2000) radio network) which performs a data interfacing operation with the synchronous terminal  11  and includes a synchronous base transceiver station/base station controller (BTS/BSC), and  13  denotes a synchronous core network which is connected to the synchronous radio network  12  and includes a synchronous mobile services switching center (MSC)  14  and an ANSI-41 network  15 . 
   In the above core network interface architecture of the conventional synchronous mobile telecommunications system, the synchronous terminal  11  can be connected to only the synchronous radio network  12  as well known to one skilled in the art, which is in turn connected to the synchronous core network  13 , thereby allowing the synchronous terminal  11  to be interfaced with only the synchronous core network  13 . 
     FIG. 1B  is a view showing the core network interface architecture of the conventional asynchronous mobile telecommunications system. In this drawing, the reference numeral  21  denotes an asynchronous terminal,  22  denotes an asynchronous radio network (i.e., a UTRAN) which includes a base transceiver station (BTS) and a radio network controller (RNC), and  23  denotes an asynchronous core network which includes an asynchronous mobile services switching center (MSC)  24  connected to the UTRAN  22  and a GSM-MAP network  25  connected to the asynchronous MSC  24 . 
   In the above core network interface architecture of the conventional asynchronous mobile telecommunications system, the asynchronous terminal  21  is connected to the asynchronous radio network  22  (i.e., UTRAN) which is in turn connected to the asynchronous core network  23 , thereby allowing the asynchronous terminal  21  to perform a data interfacing operation with the asynchronous core network  23 . 
     FIG. 2  shows layered protocol structures of the conventional synchronous/asynchronous mobile telecommunication systems as mentioned above. 
     FIG. 2A  is a view showing the layered protocol structure of the conventional synchronous mobile telecommunications system. In this drawing, the reference numeral  30  denotes a synchronous terminal,  40  a synchronous radio network and  50  a synchronous core network connected to the synchronous radio network  40 . 
   The synchronous terminal  30  comprises a layer  331 , a layer  235  and a layer  136 . The layer  331  includes a synchronous call control (CC) entity  32  for management of a call and a synchronous mobility management (MM) entity  33  for management of a mobility. 
   The layer  136  is a physical layer which offers data transport services to higher layers and transfers transport blocks over a radio interface. 
   The layer  235  is a data link layer which includes following sub layers, a medium access control (MAC) sub layer and a radio link control (RLC) sub layer. However, the sub layers are not shown in this drawing. 
   The MAC sub layer offers data transfer services on logical channels to a higher layer (RLC sub layer) and on transport channels to a lower layer (the physical layer  36 ). The MAC sub layer is responsible for mapping of the logical channel onto the appropriate transports channel. 
   The RLC sub layer offers data transfer services on primitive to a higher layer and on logical channels to a lower layer (MAC sub layer). Also, the RLC sub layer performs error correction, duplicate detection, ciphering and flow control of the data. 
   The layer  331  is a network layer which includes following sub layers, a synchronous radio resource (RR) sub layer, a synchronous call control (CC) entity  32  and a mobility management (MM) entity  33 . In synchronous system, the synchronous RR sub layer is not apparently separated from the others in the layer  331 . 
   The RR sub layer offers data transfer services on primitive to a lower layer (RLC sub layer) and handles a control plane signaling of the layer  331  between a user equipment (UE) and a synchronous radio network. The RR sub layer manages a radio resource. Also, the RR sub layer assigns/re-configures/releases the radio resource to UE/UTRAN. 
   The CC entity handles a call control signaling of layer  3  between the UEs and the synchronous radio network. 
   The MM entity handles a mobility management signaling of layer  3  between the UEs and the synchronous radio network. 
   The layers  3  to  131 ,  35  and  36  in the synchronous terminal  30  communicate with corresponding layers  41 ,  45  and  46  in the synchronous radio network  40 . 
   The synchronous radio network  40  comprises a layer  341 , a layer  245  and a layer  146 . The layers  3  to  1  in the synchronous radio network  40  correspond respectively to those in the synchronous terminal  30 . 
   The layers  3  to  141 ,  45  and  46  in the synchronous radio. network  40  communicate with corresponding layers  31 ,  35 ,  36 ,  51 ,  55  and  56  in the synchronous terminal and the synchronous core network  50 . 
   The synchronous core network  50  comprises a layer  351 , a layer  255  and a layer  156 . The layers  3  to  1  in the synchronous radio network  50  correspond respectively to those in the synchronous terminal  30 . 
   The layers  3  to  151 ,  55  and  56  in the synchronous core network  50  communicate with corresponding. layers  41 ,  45  and  46  in the synchronous radio network  40 . 
   In the conventional synchronous terminal and radio network as the layered protocol structure, the synchronous terminal  30  receives a Sync channel message from the synchronous radio network  40  over a Sync channel and acquires information necessary to its connection to the synchronous core network  50 , including information related to the synchronous core network  50  and information about the synchronous radio network  40 , from the received Sync channel message. 
   In other words, for interfacing with the synchronous ANSI-41 network via the synchronous radio network, the synchronous terminal acquires system information (i.e., information related to the radio network and core network) through a system determination sub-state, a pilot channel acquisition sub-state, a Sync channel acquisition sub-state and a timing changing sub-state after it is powered on. 
     FIG. 6  is a flowchart illustrating a procedure where the synchronous terminal acquires the system information through the four station transitions as mentioned above. 
   The first state, or the system determination sub-state, S 1 , is a state where the synchronous terminal selects a code division multiple access (CDMA) system with which it should communicate. Before being powered off, the synchronous terminal stores a CDMA channel number that it uses at the present time, a CDMA area list, a system identification (SID) list, a network identification (NID) list and other information in its memory. Thereafter, upon being powered on, the synchronous terminal selects a CDMA system with which it can communicate., on the basis of the above information stored in its memory and a CDMA system selection algorithm, which is provided from a terminal manufacturer. After selecting the CDMA system, the synchronous terminal shifts to the next state, or the pilot channel acquisition sub-state, S 2  to acquire a pilot. 
   The pilot channel acquisition sub-state S 2  is a state where the synchronous terminal obtains a pilot channel and thus selects a base transceiver station. After selecting the CDMA system, the synchronous terminal acquires a pilot with the same CDMA channel number, or CDMA frequency number, as that corresponding to the selected CDMA system. After acquiring the pilot, the synchronous terminal shifts to the next state, or the Sync channel acquisition sub-state, S 3 . 
   The Sync channel acquisition sub-state S 3  is a state where the synchronous terminal acquires information of a system selected through the above pilot channel acquisition and timing information of the selected system. The synchronous terminal receives a Sync channel message from the base transceiver station selected at the above pilot channel acquisition sub-state over a Sync channel and obtains the information of the selected system and the system timing information from the received Sync channel message. Such a Sync channel message is produced by the system and then sent to the synchronous terminal over the Sync channel. 
   Information elements as shown in  FIG. 7A  are written in the Sync channel message received by the synchronous terminal, as follows: 
   a) Protocol Revision Level: 8 bits, 
   b) Minimum Protocol Revision Level: 8 bits, 
   c) System Identification: 15 bits,. 
   d) Network Identification: 16 bits, 
   e) Pilot Pseudo. Noise (PN) sequence offset index: 9 bits, 
   f) Long Code State: 42 bits, 
   g) System Time: 36 bits, 
   h) The number of Leap seconds that have occurred since the start of System Time: 8 bits, 
   i) Offset of local time from System Time: 6 bits, 
   j) Daylight savings time indicator: 1 bit, 
   k) Paging Channel Data Rate: 2 bits, 
   l) Frequency assignment: 11 bits, 
   m) Extended frequency assignment: 11 bits, and 
   n) Orthogonal transmit diversity mode: 2 bits. 
   The synchronous terminal stores the following information elements from the received Sync channel message in its memory: 
   a) Protocol Revision Level: 8 bits, 
   b) Minimum Protocol Revision Level: 8 bits, 
   c) System Identification: 15 bits, 
   d) Network Identification: 16 bits, 
   e) Pilot PN sequence offset index: 9 bits, 
   f) Long Code State: 42 bits, 
   g) System Time: 36 bits, 
   h) Paging Channel Data Rate: 2 bits, and 
   i) Orthogonal transmit diversity mode: 2 bits. 
   After completing the above procedure, the synchronous terminal shifts to the synchronization sub-state S 4 . 
   The synchronization sub-state S 4  is a state where the synchronous terminal synchronizes its timing with that of the selected CDMA system. The synchronous terminal synchronizes its timing with that of the selected CDA system on the basis of the information elements in the Sync channel message, received at the above Sync channel acquisition sub-state and stored in its memory. After being timed with the selected CDMA system, the synchronous terminal enters a standby mode S 5 . 
   At the standby mode S 5 , the synchronous terminal monitors a paging channel of the selected system. Namely, at the standby mode S 5 , the synchronous terminal receives messages (a system parameter message, an access channel message, a registration request message, etc.) sent over the paging channel. 
     FIG. 2B  is a view showing the layered protocol structure of the conventional asynchronous mobile telecommunications system. In this drawing, the reference numeral  60  denotes an asynchronous terminal,  70  a UTRAN and  80  an asynchronous core network. 
   The asynchronous terminal  60  comprises a layer  361 , a layer  265  and a layer  166 . In particular, the layer  361  includes a non-access stratum (NAS) part and an access stratum (AS) part. The NAS part includes an asynchronous call control (CC) part  62  for management of a call and an asynchronous mobility management (MM) part  63  for management of a mobility. The AS part includes an asynchronous radio resource control (RRC) part. In the asynchronous system, the asynchronous RRC sub layer is apparently separated from the NAS part. Functions of the asynchronous RRC sub layer are the same as those of the synchronous RR sub layer. 
   The UTRAN  70  comprises a layer  371 , a layer  273  and a layer  174 . The layer  371  of the UTRAN  70  has no NAS part. having asynchronous CC part and asynchronous MM part. The layers  3  to  1  of the UTRAN  70  are connected and correspond respectively to those in the asynchronous terminal  60  and those in the asynchronous core network  80 . However, since the UTRAN  70  does not have the NAS part, i.e., the asynchronous CC part and the asynchronous MM part, the NAS parts of the asynchronous terminal  60  and the asynchronous core network  80  are coupled to each other not through the UTRAN  70 . 
   The asynchronous core network  80  comprises a layer  3  having a NAS part  81  connected to that of the asynchronous terminal  60  and a AS part, a layer  285  and a layer  186  connected respectively to those in the UTRAN  70 . The NAS part comprises an asynchronous CC part  82  for management of a call and an asynchronous MM part  83  for management of a mobility. 
   Functions of the layer  3  to  1  of the asynchronous system are similar with those of the synchronous system except for an operating type. Therefore, detailed description of the layer  3  to  1  will be skipped. 
   The more detailed descriptions about layered protocol structures are well taught in 3 rd  Generation Partnership Project (3GPP), Technical Specification Group (TSG)—Radio Access Network (RAN): 3G TS25.301 (Radio Interface Protocol Architecture), 3G TS25.302 (Services provided by the physical layer), 3G TS25.321 (MAC Protocol Specification), 3G TS25.322 (RLC Protocol Specification) and 3G TS25.331 (RRC Protocol Specification) in detail. 
   In the conventional asynchronous mobile terminal and radio network having the layered protocol structure, the asynchronous terminal  60  receives a system information message from the UTRAN  70  over a broadcast control channel (BCCH) and acquires information necessary to its connection to the asynchronous core network  80 , including information related to the asynchronous core network  80  and information about the UTRAN  70 , from the received system information message.  FIG. 7B  shows a format of the system information message received by the asynchronous terminal  60 . 
   The system information message, sent from the UTRAN  70  to the asynchronous terminal  60 , contains the following information elements, which are applied in common to all asynchronous terminals connected to the UTRAN of the asynchronous communication system: 
   1) core network (CN) information, 
   2) UTRAN mobility information, and 
   3) other information. 
   The asynchronous terminal analyzes the CN information elements among the above information elements and acquires public land mobile network .(PLMN) identity information, CN domain identity information and non-access stratum (NAS) system information as a result of the analysis. 
   The PLMN identity information is company identification information and includes a mobile country code (MCC) and a mobile network code (MNC). The CN domain identity information is used to determine whether a currently connected core network is of a circuit switching type or a packet switching type. The NAS system information is information desired in an asynchronous call control (CC) part for management of a call and an asynchronous mobility management (MM) part for management of a mobility. 
   IMT-2000 systems are the third generation systems which aim to unify the various mobile communication networks and services into one to provide many mobile communication services. The systems can provide multimedia services under multi-environments through various air-interfaces and high capacity. Also, in the aspect of services, the systems can provide multimedia services of speech, image and data up to the rate of 2 Mbps and an international roaming. And, in the aspect of network, the systems are total systems which are based on ATM networks and combine fixed and wireless systems. 
   IMT-2000 system requires new system concept, high-level adaptation technology, and novel network technology, as well all conventional technologies which were already adopted in the second digital cellular system. 
   As described above, in the next-generation mobile telecommunication system such as the IMT-2000 system, either the GSM-MAP network used in the above conventional asynchronous mobile telecommunications system or the ANSI-41 network used in the above conventional synchronous mobile telecommunications system should be employed as a core. network in order to perform an international roaming in a synchronous or asynchronous mobile telecommunications system of an IMT-2000 system. 
   According to network deployment scenarios, the IMT-2000 system can have the following four interface architectures; first: synchronous terminal—synchronous radio network—synchronous ANSI-41 network, second: synchronous terminal—synchronous radio network—asynchronous GSM-MAP network, third: asynchronous terminal—asynchronous radio network—synchronous ANSI-41 network and fourth: asynchronous terminal—asynchronous radio network—asynchronous GSM-MAP network. 
   The IMT-2000 system has the four interface architectures as mentioned above. Therefore, the hybrid type synchronous terminal must recognize an operating type of a core network currently connected thereto, and the hybrid type synchronous radio network should provide core network operating type information and others information to the hybrid type synchronous terminal. The core network operating type information and the others information must be contained in the Sync channel message that the synchronous terminal, after being powered on, receives through the Sync channel in the above-mentioned conventional interfacing manner. 
   Similarly, the hybrid type asynchronous terminal must recognize an operating type of a core network currently connected thereto, and the hybrid type asynchronous radio network should provide the core network operating type information and others information to the hybrid type asynchronous terminal. The core network operating type information and the others information must be contained in the system information message transmitted to the asynchronous terminal, after being powered on, so that the asynchronous terminal receives through the broadcast control channel (BCCH) in the above-mentioned conventional interfacing manner. 
   However, as shown in  FIG. 7A , the Sync channel message used in the conventional synchronous terminal and radio network contain only information (information regarding a synchronous core network) defined at the Sync channel acquisition sub-state of the synchronous terminal, with neither core network operating type information nor information about an asynchronous core network. 
   Because there is no core network operating type information in the Sync channel message, the synchronous terminal cannot determine which one of the CC/MM protocol for the ANSI-41 core network or the CC/MM protocol for the GSM-MAP core network to use at the layer  3  in its protocol stack structure, and be thus interfaced with any asynchronous core network. Of course, because the synchronous terminal is set to the synchronous CC/MM protocol in the conventional synchronous terminal and radio network, they have no particular problem in interfacing to a core network currently connected thereto, so far as the connected core network is a synchronous core network. 
   Also, as shown in  FIG. 7B , the system information message used in the conventional asynchronous terminal and radio network contain only information (information regarding an asynchronous core network) defined at the BCCH acquisition sub-state of the asynchronous terminal, with neither core network operating type information nor information about a synchronous core network. 
   Because there is no core network operating type information in the system information message, the asynchronous terminal cannot determine which one of the CC/MM protocol for the ANSI-41 core network or the CC/MM protocol for the GSM-MAP core network to use at the layer  3  in its protocol stack structure, and be thus interfaced with any synchronous core network. Of course, because the asynchronous terminal is set to the asynchronous CC/MM protocol in the conventional asynchronous terminal and radio network, they has no particular problem in interfacing with a core network currently connected thereto, so far as the connected core network is an asynchronous core network. 
   In other words, the conventional synchronous terminal and radio network have a disadvantage in that the synchronous terminal cannot be interfaced with any other networks than a synchronous core network connected thereto because it cannot recognize core network operating type information and core network related information. 
   Similarly, the conventional asynchronous terminal and radio network have a disadvantage in that the asynchronous terminal cannot be interfaced with any other networks than an asynchronous core network because they cannot recognize core network operating type information and core network related information. 
   SUMMARY OF THE INVENTION 
   Therefore, the present invention has been made in view of the above problems, and it is an object of the present invention to provide a method, an apparatus and a computer readable record media storing instructions for executing the same method for interfacing among a synchronous or asynchronous terminal, a synchronous or asynchronous radio network and a synchronous or asynchronous core network in a next-generation mobile telecommunications system. 
   It is another object of the present invention to provide a method for interfacing a synchronous terminal with a synchronous or asynchronous core network, wherein a synchronous radio network determines the operating type of the core network when the core network has a connection thereto, and sends the determined core network operating type information and information related to the core network to the synchronous terminal over a Sync channel, and the synchronous terminal recognizes the core network on the basis of the core network operating type information and sets a protocol according to the core network related information, so as to smoothly perform a message interfacing operation with the core network. 
   It is yet another object of the present invention to provide a method for interfacing an asynchronous terminal to a synchronous or asynchronous core network, wherein an asynchronous radio network determines the operating type of the core network when the core network has a connection thereto, and sends the determined core network operating type information and information related to the core network to the asynchronous terminal over a BCCH, and the asynchronous terminal recognizes the core network on the basis of the core network operating type information and sets a protocol according to the core network related information, so as to smoothly perform a message interfacing operation with the core network. 
   In accordance with one aspect of the present invention, there is provided a method for interfacing among a terminal, a radio network and a core network connected to the radio network in a mobile telecommunication system, wherein the radio network has a base station (BS) and each of the terminal and the radio network has a hybrid operating type being possible to be set as either a synchronous operating type or an asynchronous operating type, said method comprising the steps of: a) at the BS, determining an operating type of the core network and generating core network operating type information representing the operating type of the core network; b) at the BS, setting an operating type of the BS to the synchronous operating type or the asynchronous operating type on the basis of the core network operating type information; c) at the BS, providing the terminal with the core network operating type information and information related to the core network through a predetermined channel in a form of a message; d) extracting, at the terminal, the core network operating type information from a received message, the core network operating type information being inserted into a predetermined location of the message; e) recognizing, at the terminal, the operating type of the core network on the basis of the extracted core network operating type information; and f) at the terminal, setting an operating type of the terminal to the synchronous operating type or the asynchronous operating type on the basis of the recognized operating type of the core network. 
   In accordance with another aspect of the present invention, there is provided an apparatus for interfacing among a terminal, a radio network and a core network connected to the radio network in a mobile telecommunication system, wherein the radio network has a base station (BS) and each of the terminal and the radio network has a hybrid operating type being possible to be set as either a synchronous operating type or an asynchronous operating type, said apparatus comprising: determination means, contained in the BS, for determining an operating type of the core network; first setting means, employed in the BS, for setting an operating type of the BS to the synchronous operating type or the asynchronous operating type on the basis of the determined operating type of the core network; message means, included in the BS, for providing the terminal with core network operating type information representing the determined operating type of the core network and information related to the core network through a predetermined channel; receiver means, provided in the terminal, for receiving a channel message having the core network operating type information and the information related to the core network; extraction means, contained in the terminal, for extracting the core network operating type information inserted into a predetermined location of the channel message; detection means, contained in the terminal, for recognizing the operating type of the core network on the basis of the extracted core network operating type information; and second setting means, contained in the terminal, for setting an operating type of the terminal to the synchronous operating type or the asynchronous operating type on the basis of the recognized operating type of the core network. 
   In accordance with a. further aspect of the present invention, there is provided a method for interfacing among a terminal, a radio network and a core network connected to the radio network in a mobile telecommunication system, wherein the radio network has a base station (BS) and the terminal has a hybrid operating type being possible to be set as either a synchronous operating type or an asynchronous operating type, the method comprising the steps of: a) storing core network operating type information and information related to the core network on a storage device; b) reading the core network operating type information and information related to the core network stored on the storage device during a time period of initialization of the BS; c) providing the terminal with the core network operating type information and information related to the core network as a message through a predetermined channel; d) extracting, at the terminal, the core network operating type information from a received message, the core network operating type information being inserted into a predetermined location of the received message; e) recognizing, at the terminal, the operating type of the core network on the basis of the extracted core network operating type information; and f) setting an operating type of the terminal to the synchronous operating type or the asynchronous operating type on the basis of the recognized operating type of the core network. 
   In accordance with further another aspect of the present invention, there is provided an apparatus for interfacing among a terminal, a radio network and a core network connected to the radio network in a mobile telecommunication system, wherein the radio network has a base station (BS) and the terminal has a hybrid operating type being possible to be set as either a synchronous operating type or an asynchronous operating type, comprising: a storage device, contained in the BS, for storing core network operating type information representing operating type of the core network and information related to the core network; first extraction means, contained in the BS, for reading the core network operating type information and information related to the core network stored in the storage device during a time period of initialization of the BS; message means, contained in the BS, for providing the terminal with the core network operating type information and information related to the core network as a message through a predetermined channel; second extraction means, contained in the terminal, for extracting the core network operating type information from a received message, the core network operating type information being inserted into a predetermined location of the received message; detection means, contained in the terminal, for recognizing the operating type of the core network on the basis of the extracted core network operating type information; and setting means, contained in the terminal, for setting an operating type of the terminal to the synchronous operating type or the asynchronous operating type on the basis of the recognized operating type of the core network. 
   In accordance with a further another aspect of the present invention, there is provided a method for interfacing between a radio network and a core network connected to the radio network in a mobile telecommunication system, wherein the radio network has a base station (BS) having a hybrid operating type being possible to be set as either a synchronous operating type or an asynchronous operating type, said method comprising the steps of: a) determining an operating type of the core network; b) setting an operating type of the BS to the synchronous operating type or the asynchronous operating type on the basis of core network operating type information representing the determined operating type of the core network; and c) providing the terminal with the core network operating type information and information related to the core network through a predetermined channel in a form of a message. 
   In accordance with a further aspect of the present invention, there is provided a n apparatus for interfacing between a radio network and a core network connected to the radio network in a mobile telecommunication system, wherein the radio network has a base station (BS) having a hybrid operating type being possible to be set as either a synchronous operating type or an asynchronous operating type, said apparatus comprising: determination means for determining an operating. type of the core network; setting means for setting an operating type of the BS to the synchronous operating type or the asynchronous operating type on the basis of core network operating type information representing the determined operating type of the core network; and message means for providing the terminal with the core network operating type information and information related to the core network through a predetermined channel in a form of a message. 
   In accordance with a further aspect of the present invention, there is provided a computer readable media storing a program instructions, the program instructions disposed on a computer to perform a method for interfacing between a radio network and a core network connected to the radio network in a mobile telecommunication system, wherein the radio network has a base station ABS) having a hybrid operating type being possible to be set as either a synchronous operating type or an asynchronous operating type, said method comprising the steps of: a) determining an operating type of the core network; b) setting an operating type of the BS to the synchronous operating type or the asynchronous operating type on the basis of core network operating type information representing the determined operating type of the core network; and c) providing the terminal with the core network operating type information and information related to the core network through a predetermined channel in a form of a message. 
   In accordance with another. aspect of the present invention, there is provided a method for interfacing among a terminal, a radio network and a core network connected to the radio network in a mobile telecommunication system, wherein the radio network has a base station (BS) and the terminal has a hybrid operating type being possible to be set as either a synchronous operating type or an asynchronous operating type, the method comprising the steps of: a) storing core network operating type information representing operating type of the core network and information related to the core network on a storage device; b) reading the core network operating type information and information related to the core network stored on the storage device during a time period of initialization of the BS; and c) periodically providing the terminal with the core network operating type information and information related to the core network as a message through a predetermined channel. 
   In accordance with still another aspect of the present invention, there is provided an apparatus for interfacing among a terminal, a radio network and a core network connected to the radio network in a mobile, telecommunication system, wherein the radio network has a base station (BS) and the terminal has a hybrid operating type being possible to be set as either a synchronous operating type or an asynchronous operating type, comprising: a storage device, contained in the BS, for storing core network operating type information representing operating type of the core network and information related to the core network; extraction means, contained in the BS, for reading the core network operating type information and information related to the core network stored in the storage device during a time period of initialization of the BS; and message means, contained in the BS, for periodically providing the terminal with the core network operating type information and information related to the core network as a message through a predetermined channel. 
   In accordance with still another aspect of the present invention, there is provided a computer readable media storing a program instructions, the program instructions disposed on a computer to perform a method for interfacing among a terminal, a radio network and a core network connected to the radio network in a mobile telecommunication system, wherein the radio network has a base station (BS) and the terminal has a hybrid operating type being possible to be set as either a synchronous operating type or an asynchronous operating type, the method comprising the steps of: a) storing core network operating type information representing operating type of the core network and information related to the core network on a storage device; b) reading the core network operating type information and information related to the core network stored on the storage device during a time period of initialization of the BS; and c) periodically providing the terminal with the core network operating type information and information related to the core network as a message through a predetermined channel. 

   
     BRIEF DESCRIPTION OF THE DRAWINGS 
     The above and other objects, features and advantages of the present invention will, be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings, in which: 
       FIG. 1  shows core network interface architectures of conventional synchronous/asynchronous mobile telecommunications systems, wherein: 
       FIG. 1A  is a view showing a core network interface architecture of the conventional synchronous mobile telecommunications system; and 
       FIG. 1B  is a view showing a core network interface architecture of the conventional asynchronous mobile telecommunications system; 
       FIG. 2  shows layered protocol structures of the conventional synchronous/asynchronous mobile telecommunications systems, wherein: 
       FIG. 2A  is a view showing a layered protocol structure of the conventional synchronous mobile telecommunications system; and 
       FIG. 2B  is a view showing a layered protocol structure of the conventional asynchronous mobile telecommunications system; 
       FIG. 3  is a view showing a protocol stack structure for interfacing a terminal and a base station with a core network in a next-generation mobile telecommunications system; 
       FIG. 4  shows core network interface architectures of the next-generation mobile telecommunications system, wherein: 
       FIG. 4A  is a view showing a synchronous ANSI-41 core network interface architecture of hybrid type synchronous mobile terminal and radio network; 
       FIG. 4B  is a view showing an asynchronous GSM-MAP core network interface architecture of hybrid type synchronous mobile terminal and radio network; 
       FIG. 4C  is a view showing an asynchronous GSM-MAP core network interface architecture of hybrid type asynchronous mobile terminal and radio network; and 
       FIG. 4D  is a view showing a synchronous ANSI-41 core network interface architecture of hybrid type asynchronous mobile terminal and radio network; 
       FIG. 5  shows layered protocol structures of the next-generation mobile telecommunications system, wherein: 
       FIG. 5A  is a view showing layered protocol structures of hybrid type synchronous mobile terminal and radio network and the synchronous ANSI-41 core network; 
       FIG. 5B  is a view showing layered protocol structures of hybrid type synchronous mobile. terminal and radio network and the asynchronous GSM-MAP core network; 
       FIG. 5C  is a view showing layered protocol structures of hybrid type asynchronous mobile terminal. and radio network and the synchronous ANSI-41 core network; and 
       FIG. 5D  is a view showing layered protocol structures of hybrid type asynchronous mobile terminal and radio network and the asynchronous GSM-MAP core network; 
       FIG. 6  is a flowchart illustrating state transitions of a synchronous terminal in the conventional synchronous mobile telecommunications system; 
       FIG. 7  shows format of a message received by the terminal from the conventional synchronous radio network, wherein: 
       FIG. 7A  is a view showing a format of a Sync channel message received by the synchronous terminal from the conventional synchronous radio network; 
       FIG. 7B  is a view showing a format of a system information message received by an asynchronous terminal from the conventional asynchronous radio network; 
       FIG. 8A  is a block diagram of a base station controller for interfacing among a terminal, a radio network and a core network; 
       FIG. 8B  is a block diagram of a terminal controller for interfacing among a terminal, a radio network and a core network; 
       FIG. 9  shows a Sync channel message received by a hybrid type synchronous terminal from in a hybrid type synchronous radio network in accordance with the present invention, wherein: 
       FIG. 9A  is a view showing a format of the Sync channel message when a core network connected to a hybrid type synchronous radio network is a GSM-MAP network; and 
       FIG. 9B  is a view showing a format of the Sync channel message when the core network connected to the hybrid type synchronous radio network is an ANSI-41 network; 
       FIG. 10  shows a master information block in a system information message received by a hybrid type asynchronous terminal from a hybrid type asynchronous radio network in accordance with the present invention, wherein: 
       FIGS. 10A and 10B  are views showing formats of the master information block when a core network connected to a hybrid type asynchronous radio network, or a UTRAN, is the GSM-MAP network; and 
       FIGS. 10C and 10D  are views showing formats of the master information block when the core network connected to the UTRAN is the ANSI-41 network; 
       FIG. 11  shows flow charts illustrating a method for interfacing a hybrid type synchronous terminal with a core network in accordance with the present invention, wherein: 
       FIG. 11A  is a flowchart illustrating a procedure where a hybrid type synchronous radio network sends core network operating type information and information related to core network to the hybrid type synchronous terminal; and 
       FIG. 11B  is a flowchart illustrating a procedure where the hybrid type synchronous terminal receives the core network operating type information and the information related to core network from the hybrid type synchronous radio network and then is interfaced with the core network on the basis of the received information; and 
       FIG. 12  shows flow charts illustrating a method for interfacing a hybrid type asynchronous terminal to a core network in accordance with the present invention, wherein: 
       FIG. 12A  is a flowchart illustrating a procedure where a hybrid type asynchronous radio network sends core network operating type information and information related to core network to the hybrid type asynchronous terminal; and 
       FIG. 12B  is a flowchart illustrating a procedure where the hybrid type asynchronous terminal receives the core network operating type information and the information related to core network from the hybrid type asynchronous radio network and then is interfaced with the core network on the basis of the received information. 
   

   DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS 
   In the specification, a radio network means a network including a plurality of base transceiver stations (BTS) and at least a base station controller for controlling the plurality of BTSs in a synchronous or an asynchronous mobile telecommunication system. 
   Functions for controlling the base transceiver station can be distributively performed in the plurality of the base transceiver stations, or can be concentrically performed in the base station controller. Therefore, in this specification, a terminology “base station,” which includes the base transceiver station and the base station controller, is used. 
   Referring to  FIG. 3 , it is illustrated a protocol stack structure for interfacing a mobile terminal, a base transceiver station/base station controller (BTS/BSC) and a core network having the same or a different operating type with/from the mobile terminal in a next-generation mobile telecommunications system such as the IMT-2000 system. 
     FIG. 4  shows core network interface architectures of the next-generation mobile telecommunications system such as the IMT-2000 system. 
     FIG. 4A  is a view showing a synchronous ANSI-41 core network interface architecture of a hybrid type synchronous radio network. In this drawing, the reference numeral  100  denotes a hybrid type synchronous terminal,  110  a hybrid type synchronous radio network, and  120  a synchronous core network which includes an ANSI-41 network. 
     FIG. 4B  is a view showing an asynchronous GSM-MAP core network interface architecture of the hybrid type synchronous radio network. In this drawing, the reference numeral  100  denotes a hybrid type synchronous terminal,  110  a hybrid type synchronous radio network, and  130  an asynchronous core network which includes a GSM-MAP network. 
     FIG. 4C  is a view showing an asynchronous GSM-MAP core network interface architecture of a hybrid type asynchronous radio network. In this drawing, the reference numeral  210  denotes a hybrid type asynchronous terminal,  220  denotes a hybrid type UTRAN which is a hybrid type asynchronous radio network, and  240  denotes a core network which is connected to the hybrid type UTRAN  220  and includes an asynchronous GSM-MAP network. 
     FIG. 4D  is a view showing a synchronous ANSI-41 core network interface architecture of the hybrid type asynchronous radio network. In this drawing, the reference numeral  210  denotes a hybrid type asynchronous terminal,  220  denotes a hybrid type UTRAN which is a hybrid type asynchronous radio network, and  230  denotes a core network which is connected to the hybrid type UTRAN  220  and includes a synchronous ANSI-41 network. 
   In order to be operable adaptively to the above four interface architectures, each of the hybrid type synchronous and asynchronous terminals in the next-generation mobile telecommunications system has both asynchronous CC and MM protocol entities serving for the GSM-MAP core network and synchronous CC and MM protocol entities serving for the ANSI-41 core network at the layer  3  in the protocol stack structure, which is a different from each of the conventional synchronous and asynchronous terminals. 
     FIG. 5  shows layered protocol structures of the next-generation mobile telecommunications system. 
     FIG. 5A  is a view showing the layered protocol structure of a hybrid type synchronous terminal, a hybrid type synchronous radio network and the synchronous ANSI-41 core network. In this drawing, the reference numeral  100  denotes a hybrid type synchronous terminal,  110  denotes a hybrid type synchronous radio network, and  120  denotes an ANSI-41 core network which is a synchronous core network connected to the hybrid type synchronous radio network  110 . 
   The hybrid type synchronous terminal  100  comprises a layer  3101 , a layer  2107  and a layer  1108 . The layer  3   101  comprises a synchronous CC part  102 , a synchronous MM part  103 , an asynchronous CC part  104 , an asynchronous MM part  105  and a synchronous radio resource part  106 . The hybrid type synchronous terminal  100  selectively makes a CC/MM protocol active according to a core network operating type. Information for identifying the core network operating type is given to the hybrid type synchronous terminal  100 . 
   For example, if the hybrid type synchronous terminal  100  is currently connected to the ANSI-41 core network  120 , the layer  3101  therein activates protocols of the synchronous CC part  102  and synchronous MM part  103  to perform a message interfacing operation with the ANSI-41 core network  120 . 
   The hybrid type synchronous radio network  110  comprises a layer  3111 , a layer  2115  and a layer  1116 , which activate their protocols corresponding respectively to those in the hybrid type synchronous terminal  100  and those in the ANSI-41 core network  120  to transmit and receive messages. 
   The ANSI-41 core network  120  comprises a layer  3121 , a layer  2125  and a layer  1126 . The layer  3121  comprises a synchronous CC part  122 , a synchronous MM part  123  and a synchronous RR part  124 . 
   On the other hand, a hybrid type synchronous mobile terminal, a hybrid type synchronous radio network and an asynchronous core network have layered protocol structures as shown in  FIG. 5B  when the core network connected thereto is of an asynchronous operating type as shown in  FIG. 4B . 
   In  FIG. 5B , the reference numeral  100  denotes a hybrid type synchronous terminal,  110  denotes a hybrid type synchronous radio network, and  130  denotes a GSM-MAP core network which is an asynchronous core network. 
   The hybrid. type synchronous terminal  100  comprises a layer  3101  having a NAS part and an AS part, a layer  2107  and a layer  1108 . The NAS part includes a synchronous CC part  102 , a synchronous MM part  103 , an asynchronous CC part  104  and an asynchronous MM part  105 . The AS part includes a synchronous RR part  106 . The hybrid type synchronous terminal  100  selectively makes a CC/MM protocol active according to a core network operating type. 
   For example, if the hybrid type synchronous terminal  100  is currently connected to the GSM-MAP core network  130 , the layer  3101  therein activates protocols of the asynchronous CC part  104  and asynchronous MM part  105  to perform a message interfacing. operation with the GSM-MAP core network  130 . 
   The hybrid type synchronous radio network  110  comprises a layer  3111  having a NAS part and an AS part, a layer  2115  and a layer  1116 , which activate their protocols corresponding respectively to those in the hybrid type synchronous terminal  100  and those in the GSM-MAP core network  130  to transmit and receive messages. 
   The GSM-MAP core network  130  comprises a layer  3131  having a NAS part and an AS part, a layer  2135  and a layer  1136 . The NAS part includes an asynchronous CC part  132  and an asynchronous MM part  133 . The AS part includes an asynchronous RRC part  134 . 
   The layers  3  to  1  of the hybrid type synchronous radio network  110  are connected and correspond respectively to those in the hybrid type synchronous terminal  100  and those in the asynchronous core network  130 . However, the NAS parts of the hybrid type asynchronous terminal  100  and the asynchronous core network  130  are coupled to each other not through the hybrid type synchronous radio network  110 . 
     FIG. 5C  is a view showing layered protocol structures of a hybrid type asynchronous mobile terminal, a hybrid type asynchronous radio network and a synchronous ANSI-41 core network. In this drawing, the reference numeral  210  denotes a hybrid type asynchronous terminal,  220  denotes a hybrid type UTRAN which is a hybrid type asynchronous radio network, and  230  denotes an ANSI-41 core network connected to the hybrid type UTRAN  220 . 
   The hybrid type asynchronous terminal  210  comprises a layer  3211 , a layer  2217  and a layer  1218 . The layer  3  includes a synchronous CC part  212 , a synchronous MM part  213 , an asynchronous CC part  214 , an asynchronous MM part  215  and asynchronous RRC part  216  and selectively activates a synchronous CC/MM protocol or an asynchronous CC/MM protocol. 
   For example, if the hybrid type asynchronous terminal  210  is currently connected to the ANSI-41 core network  230 , the layer  3  therein activates a protocol between the synchronous CC part  212  and synchronous MM part  213  to perform a message interfacing operation with the ANSI-41 core network  230 . 
     FIG. 5D  is a view showing layered protocol structures of a hybrid type asynchronous mobile terminal, a hybrid type asynchronous radio network and an asynchronous GSM-MAP core network. In this drawing, the reference numeral  210  denotes a hybrid type asynchronous terminal,  220  denotes hybrid type UTRAN which is a hybrid type asynchronous radio network, and  240  denotes an asynchronous GSM-MAP core network connected to the hybrid type UTRAN  220 . 
   The hybrid type asynchronous terminal  210  comprises a layer  3211  having a NAS part and an AS part, a layer  2217  and a layer  1218 . The NAS part includes a synchronous CC part  212 , a synchronous MM part  213 , an asynchronous CC part  214  and an asynchronous MM part  215  and selectively activates a synchronous CC/MM protocol or an asynchronous CC/MM protocol. The AS part includes an asynchronous RRC part  216 . 
   The hybrid type asynchronous radio network  220  comprises a layer  3221  having a NAS part and an AS part, a layer  2225  and a layer  1226 , which activate their protocols corresponding respectively to those in the hybrid type asynchronous terminal  210  and those in the GSM-MAP core network  240  to transmit and receive messages. 
   The GSM-MAP core network  240  comprises a layer  3241  having a NAS part and an AS part, a layer  2245  and a layer  1246 . The NAS part includes an asynchronous CC part  242  and an asynchronous MM part  243 . The. AS part includes an asynchronous RRC part  244 . 
   For example, if the hybrid type asynchronous terminal  210  is currently connected to the GSM-MAP core network  240 , the NAS part therein activates protocols of the asynchronous CC part  214  and asynchronous MM part  215  to perform a message interfacing operation with the GSM-MAP core network  240 . 
   The layers  3  to  1  of the hybrid type asynchronous radio network  220  are connected and correspond respectively to those in the hybrid type asynchronous terminal  210  and those in the asynchronous core network  240 . However, the NAS parts of the hybrid type asynchronous terminal  210  and the asynchronous core network  240  are coupled to each other not through the hybrid type asynchronous radio network  220 . 
   EMBODIMENT 1 
   In a method for interfacing a hybrid type synchronous terminal to a synchronous core network, the hybrid type synchronous mobile terminal and radio work have core network interface architectures as described above with reference to  FIGS. 4A and 4B  and the associated layered protocol structures as described above with reference to  FIGS. 5A and 5B . 
     FIG. 8A  is a block diagram of a BS controller for interfacing the BS with a core network having the same or a different operating type with/from the BS. 
   The base station (BS) includes a controller  811  which performs control functions of the BS, for example, information transmission, call processing, etc. 
   The BS controller provides a terminal set synchronous or asynchronous with a determined core network operating type information and an information related to the core network to be connected, thereby allowing the terminal to be interfaced with the core. network having the same or a different operating type with/from the terminal. 
   A management/maintenance block  813  determines an operating type of the core network to be connected on the basis of information stored on the BS controller or on the basis of message exchanged with the connected core network. 
   The stored information can be stored on a read only memory (ROM) in the controller  811 , or on a dip switch to which a central processing unit (CPU) of the controller  811  is connected. The message exchanged with the core network is preferably a management/maintenance message or a signaling message. 
   A call processing block  815  provides the terminal with the core network operating type information and the information related to the core network through a channel. In a synchronous operating type, the core network operating type information and the information related to the core network are inserted into a core network operating type information field of a synchronous channel and transmitted to the terminal. The core network operating type information transmitted to the terminal is GSM-MAP information representing an asynchronous core network, or ANSI-41 information representing a synchronous core network. 
     FIG. 8B  is a block diagram of a terminal controller for interfacing the terminal with a core network, wherein the core network is of a synchronous or an asynchronous type. 
   The terminal controller comprises a controlling unit  821 , a call processing unit  823  and a management/maintenance unit  825 . 
   The call processing unit  823  includes a receiving block which receives channel message having core network operating type information, and a determining block which extracts the core network operating type information inserted into a pre-selected location of the channel message and determines whether the core network is of a synchronous or an asynchronous type. The management/maintenance unit  825  includes a setting block which sets the terminal as an operating type corresponding to the core network operating type information. The controlling unit  821  performs general control functions of the terminal, for example, call processing function, management/maintenance function, etc. The terminal controller further includes a memory extracting and storing information related to the core network from the channel message. Here, the information related to the core network corresponds to the core network operating type information. 
   As described above, the method and the apparatus in accordance with the present invention adaptively sets a protocol and interfaces among the terminal, the base station and the core network on the basis of an operating type of the core network. Preferred formats of messages communicated between the terminal and the base station in order to perform setting and interfacing functions are illustrated in  FIGS. 9A and 9B . 
     FIG. 9A  shows a format of a synchronous channel message received by a synchronous terminal when a core network connected to the radio network is GSM-MAP.  FIG. 9B  shows a format of a synchronous channel message received by a synchronous terminal when a core network connected to the radio network is ANSI-41 core network. 
   If the core network operating type information is ANSI-41 information representing a synchronous core network, the information related to core network includes information P_REV representing a revision level of a system protocol, information M_P_REV representing a minimum revision level, system identification SID and network identification NID. If the core network operating type information is GSM-MAP information representing an asynchronous core network, the information related to core network includes public land mobile network identity PLMN_ID, core network domain identity and non-access stratum (NAS) system information. The public land mobile network (PLMN) identity PLMN_ID includes mobile country code (MCC) and mobile network code (MNC). The terminal identifies a provider of a system to which it accesses based on the PLMN identity PLMN_ID. 
     FIG. 11  shows a method for interfacing a hybrid type synchronous terminal with a core network in accordance with the present invention. 
     FIG. 11A  is a flowchart illustrating a procedure where a hybrid type synchronous radio network including a base transceiver station (BTS) and a base station controller (BSC) determines the operating type of the core network and sends information about the core network, for example, core network operating type information and information related to core network, to the hybrid type synchronous terminal. 
   First, the BSC in the hybrid type synchronous radio network detects a core network operating type information of a core network connected thereto at step S 11 . 
   Noticeably, the BSC detects the core network operating type information of the connected core network on the basis of information from a read only memory (ROM) or information from a dip switch which may be manually operated by an operator, upon system initialization. Alternatively, the BSC may detect the operating type of the connected core network through the exchange of a management/maintenance message with the connected core network. 
   Further, the BSC may detect the operating type of the connected core network by conducting the above two methods simultaneously or a simple modification of them. 
   Thereafter, the. BSC determines at step S 12  whether the connected core network is a synchronous ANSI-41 core network. If the connected core network is the synchronous ANSI-41 core network, the BSC sets core network operating type information CN Type corresponding to the detected core network operating type at step S 15 . 
   In the case where it is determined at the above step S 12  that the connected core network is not the synchronous ANSI-41 core network, the BSC determines at step S 13  whether the connected core network is an asynchronous GSM-MAP core network. If the connected core network is the asynchronous GSM-MAP core network, the BSC activates an asynchronous CC part and an asynchronous MM part for a direct spreading (DS) method at step S 14  and then sets the CN Type information corresponding to the detected core network operating type at step S 15 . 
   Herein, the CN Type information is set to “1” when the connected core network is the synchronous ANSI-41 core network, and “0” when the connected core network is the asynchronous GSM-MAP core network. 
   Subsequently, the BSC inserts the set core network operating type information and the information related to core network respectively into specific fields of a Sync channel message at step S 16 . 
   Herein, the Sync channel message has formats as shown in  FIG. 9 . 
     FIG. 9A  is a view showing a format of the Sync channel message when the core network connected to the hybrid type synchronous radio network is the GSM-MAP network. As shown in this drawing, the core network operating type information CN Type of “0” or “1” is written in a first field of the Sync channel message and information elements related to the GSM-MAP network, PLMN identity information PLMN_ID, CN domain identity information and NAS system information, are sequentially written in the subsequent fields of the message. As described above, the same information elements as those in the conventional Sync channel message shown in  FIG. 7A  are sequentially written from the next field of the present Sync channel message. 
     FIG. 9B  is a view showing a format of the Sync channel message when the core network connected to the hybrid type synchronous radio work is the ANSI-41 network. As shown in this drawing, the core network operating type information CN Type of “0” or “1” is written in a first field of the Sync channel message and information elements related to the ANSI-41 network, an 8 bits protocol revision level, an 8 bits minimum protocol revision level, a 15 bits system identification and a 16 bits network identification, are sequentially written in the subsequent fields of the message. The same information elements as those in the conventional Sync channel message shown in  FIG. 7A  are sequentially written from the next field of the present Sync channel message. 
   Herein, the core network operating type information is used to indicate whether the core network connected to the synchronous radio network is the ANSI-41 network or the GSM-MAP network. For example, the core network operating type information is set to “1” when the core network connected to the hybrid type synchronous radio network is the ANSI-41 core network, and “0” when the connected core network is the GSM-MAP core network. 
   Thereafter, the BSC in the hybrid. type synchronous radio network sends the Sync channel message having the CN operating type information to the hybrid type synchronous terminal over a Sync channel at step S 17 . 
   Then, the BSC interfaces the hybrid type synchronous terminal with the core network in a synchronous or asynchronous communication manner according to a set protocol at step S 18 . 
   On the other hand, upon receiving the above Sync channel message, the hybrid type synchronous terminal synchronizes its timing with that of the connected core network according to a flowchart of  FIG. 11B . 
   That is, upon being. powered on, the synchronous terminal selects a CDMA system on the basis of a CDMA channel number, a CDMA area list, an SID list, an NID list and other information stored in its memory and a CDMA system selection algorithm provided from a terminal manufacturer at step S 21 . 
   Then, the hybrid type synchronous terminal acquires a pilot having the same. CDMA channel number as that of the selected CDMA system at step S 22 . In other words, after selecting the CDMA system, the hybrid type synchronous terminal acquires a pilot having the same CDMA channel number as that of the selected CDMA system, or CDMA frequency number as that. corresponding to the selected CDMA system. 
   After acquiring the pilot, the hybrid type. synchronous terminal proceeds to step S 23  to perform a Sync channel acquisition operation and then to step S 24  to receive a Sync channel message over the acquired Sync channel. 
   Subsequently, the hybrid type synchronous terminal analyzes core network operating type information CN Type among information elements in the received Sync channel message at step S 25 . Herein, the CN Type information is set to “1” when the connected core network is the synchronous ANSI-41 core network, and “0” when the connected core network is the asynchronous GSM-MAP core network. 
   Accordingly, the hybrid type synchronous terminal determines at step  526  whether the CN Type information value is “1” and proceeds to step S 27  if the CN Type information value is “1”. At step S 27 , the synchronous terminal analyzes information elements related to the core network as those for the ANSI-41 core network and stores desired ones of them in its memory. At this time, the stored information elements are system identification (SID), network identification (NID), a minimum protocol. revision level (MIN_P_REV) and a protocol revision level (P_REV). 
   Thereafter, at. step S 28 , the hybrid type synchronous terminal selects a synchronous CC part and a synchronous MM part for the ANSI-41 network and sets protocols according to the selected operating type. Subsequently, the hybrid type synchronous terminal synchronizes its timing with that of a base transceiver station in the selected system at step S 29  and then performs a message interfacing operation with the ANSI-41 core network at step S 30 . 
   On the other hand, in the case where it is determined at the above step S 26  that the CN Type information value is not “1”, the synchronous terminal determines at step S 31  whether the CN Type information value is “0” and proceeds to step S 32  if the CN Type information value is “0”. At step S 32 , the synchronous terminal analyzes the information elements related to core network as those for the GSM-MAP core network and stores a desired one, a PLMN identity, of them in its memory. 
   Thereafter, at step S 33 , the hybrid type synchronous terminal selects an asynchronous CC part and an asynchronous MM part for the GSM-MAP network and sets protocols according to the selected operating type. Subsequently, the hybrid type synchronous terminal synchronizes its timing with that of a base transceiver station in the selected system at step S 34  and then performs a message interfacing operation with the GSM-MAP core network at step S 35 . 
   EMBODIMENT 2 
   Architectures of telecommunication system for interfacing a hybrid type asynchronous terminal with a core network are described above with reference to  FIGS. 4C and 4D  and the associated layered protocol structures of the telecommunication system are described above with reference to  FIGS. 5C and 5D . 
   As described above, the method or the apparatus for interfacing in accordance with the present invention adaptively sets a protocol on the basis of an operating type of the core network and smoothly interfaces among the terminal, the base station and the core network. Preferred formats of messages. communicated between the terminal and the base station in order to perform setting and interfacing functions are illustrated in  FIGS. 10A  to and  10 D. 
     FIGS. 10A and 10B  show a format of a master information block in a system information message received by a hybrid type asynchronous terminal when a core network connected to a universal mobile telecommunication system (UMTS) terrestrial radio access. network (UTRAN) is an asynchronous GSM-MAP core network.  FIGS. 10C and 10D  show a format of a master information block in a system information message received by a hybrid type asynchronous terminal when a core network connected to the UTRAN is a synchronous ANSI-41 core network. 
   If the core network operating type information is ANSI-41 information representing a synchronous core network, the information related to core network includes a revision level (P_REV) representing a revision level of a system protocol, a minimum. revision level (M P_REV), a system identification (SID) and network identification (NID). If the core network operating type information is GSM-MAP information representing an asynchronous core network, the information related to core network includes public land mobile network identity (PLMN_ID). 
     FIG. 12A  is a flowchart illustrating a procedure where a hybrid type radio network controller (RNC) in an asynchronous radio network, or UTRAN, determines the operating type of a core network connected thereto and sends the core network operating type information and information related to the core network to a hybrid type asynchronous terminal. 
   First, the hybrid type RNC in the UTRAN detects an operating type of a core network connected thereto at step S 41 . 
   Noticeably, the hybrid type RNC detects the operating type of the connected core network on the basis of information from a read only memory (ROM) or information from a dip switch which may be manually operated by an operator, upon system initialization. Alternatively, the hybrid type RNC may detect the operating type of the connected core network through the exchange of a management/maintenance message with the connected core network. 
   Alternatively, the hybrid type RNC may detect the operating type of the connected core network by conducting the above two methods simultaneously or a simple modification of them. 
   Thereafter, the hybrid type RNC determines at step S 42  whether the connected core network is an asynchronous GSM-MAP core network. 
   If it is determined at the above step S 42  that the connected core network is the asynchronous GSM-MAP core network, the hybrid type RNC sets core network operating type information CN Type corresponding to the detected operating type of the core network at step S 45 . For example, if the connected core network is the asynchronous GSM-MAP core network, the RNC sets the core network operating type information as “GSM-MAP”. 
   Subsequently, the hybrid type RNC inserts the set CN Type information and information related to core network respectively into specific fields of a system information message at step S 46 . 
   Herein, the CN Type. information and information related to core network are inserted into a master information block (MIB) in the system information message. In  FIGS. 10A and 10B , views showing a format of the MIB are shown. The MIB has the CN Type information and the information related to core network in accordance with the present invention. 
   In  FIGS. 10A and 10B , other fields except for CN information elements are the same as those in the conventional system information message shown in  FIG. 7B  and a detailed description thereof will thus be omitted. The core network operating information and the information related to core network are written in the CN information element field. Because it is determined at the above step S 42  that the connected core network is the asynchronous GSM-MAP core network, “GSM-MAP” is written in the CN Type information field and a PLMN identity is written in the core network related information field. 
   Thereafter, the RNC sends the system information message having a master information block (MIB) to the hybrid type asynchronous terminal over a BCCH at step S 47  and then performs a message interfacing operation between the hybrid type asynchronous terminal and the core network at step S 48 . 
   On the other hand, in the case where it is determined at the above step S 42  that the connected core network is not the asynchronous GSM-MAP core network, the RNC determines at step S 43  whether the connected core network is a synchronous ANSI-41 core network. 
   If the connected core network is the synchronous ANSI-41 core network, the RNC activates a synchronous. CC part and a synchronous MM part for MC at step S 44  and then sets the core network operating type information CN Type corresponding to the detected core network operating type at step S 45 . For example, if the connected core network is the synchronous ANSI-41 core network, the RNC sets the CN Type information as “ANSI-41”. 
   Subsequently, the RNC inserts the set CN Type information and the information related to core network respectively into specific fields of a system information message at step S 46 . 
   Herein, the CN Type information and the information related to core network are inserted into the MIB in the system information message.  FIGS. 10C and 10D  are views showing a format of the MIB in which the CN Type information and information related to core network are written in accordance with the present invention. 
   In  FIGS. 10C and 10D , other fields except for fields containing CN information elements are the same as those in the conventional system information message shown in  FIG. 7B  and a detailed description thereof will thus be omitted. The CN Type information and information related to core network are written in the CN information element fields. Because it is determined at the above step S 43  that the connected core network is the synchronous ANSI-41 core network, “ANSI-41” is written in the CN Type information field and ANSI-41 information elements are written in the information related to core network field. Herein, the ANSI-41 information elements are P_REV, MIN_P_REV, SID and NID information. 
   Thereafter, the RNC sends the system information message having the MIB to the asynchronous terminal over the BCCH at step S 47  and then performs a message interfacing operation between the hybrid type asynchronous terminal and the core network at step S 48 . 
   On the other hand, upon receiving the above system information message over the BCCH, the hybrid type asynchronous terminal sets its protocol through a procedure of  FIG. 12B  to perform an interfacing operation with the core network. 
   Namely, upon being powered on, the hybrid type asynchronous terminal selects a PLMN where it is located, on the basis of a PLMN list stored in its memory at step S 51 . Then, the hybrid type asynchronous terminal selects a cell in the selected PLMN with which it can efficiently communicate, at step S 52 , and receives a system information message as shown in  FIGS. 10A and 10B  or  10 C and  10 D over a BCCH at step S 53 . 
   At step S 54 , the hybrid type asynchronous terminal extracts the master information block (MIB) from the received system information message and analyzes CN Type information in the extracted MIB. 
   The hybrid type asynchronous terminal determines at step S 55  whether the CN Type information is “GSM-MAP” and proceeds to step S 56  if the CN Type information is “GSM-MAP”. At step S 56 , the hybrid type asynchronous terminal analyzes the information elements related to core network as those for the GSM-MAP core network and stores a desired one, a PLMN identity, of them in its memory. 
   Thereafter, at step S 57 , the asynchronous terminal selects an asynchronous CC part and an asynchronous MM part for the GSM-MAP network and sets a protocol therebetween. Subsequently, the hybrid type asynchronous terminal carries out its initialization based on the contents of the information elements related to core network at step S 58  and then performs a message interfacing operation with the GSM-MAP core network at step S 59 . 
   On the other hand, in the case where it is determined at the above step S 55  that the CN Type information is not “GSM-MAP”, the hybrid type asynchronous terminal determines at step S 60  whether the CN Type information is “ANSI-41” and proceeds to step S 61  if the CN Type information is “ANSI-41”. 
   At step S 61 , the hybrid type asynchronous terminal analyzes the information elements related to the core network as those for the ANSI-41 core network and stores desired ones of them in its memory. The stored information elements are SID, NID, MIN_P_REV and P_REV information. 
   Thereafter, at step S 62 , the hybrid type asynchronous terminal selects a synchronous CC part and a synchronous MM part for the ANSI-41 network and sets a protocol therebetween. Subsequently, the hybrid type asynchronous terminal carries out its initialization based on the contents of the core network related information elements at step S 63  and then performs a message interfacing operation with the ANSI-41 core network at step S 64 . 
   As apparent from the. above description, according to the present invention, even though a hybrid type synchronous or asynchronous terminal is connected to either a GSM-MAP core network or an ANSI-41 core network, it can smoothly be interfaced with the connected core network because it is able to recognize the operating type of the connected core network and information related to the core network. 
   Further, new information elements (CN Type information and information related to core network) are simply added to a Sync channel message used in an existing synchronous radio network, in other words, changes or modifications of existing information elements in the Sync channel message are minimized. Therefore, the hybrid type synchronous radio network can readily notify a hybrid type synchronous terminal of the operating type of a connected core network, and a synchronous system subscriber can be provided with a service from an asynchronous GSM-MAP core network. 
   Moreover, new information elements, i.e., CN Type information and information related to core network, are added to a system information message used in an asynchronous system having an existing asynchronous radio network, without modifying existing information elements in the system information message. Therefore, the hybrid type asynchronous radio network can readily notify a hybrid type asynchronous terminal of the operating type of a connected core network, and an asynchronous system subscriber can be provided with a service from a synchronous ANSI-41 core network. 
   Although the preferred embodiments of the present invention have been disclosed for illustrative purposes, those skilled in the art will appreciate that various modifications, additions and substitutions are possible, without departing from the scope and spirit of the invention as disclosed in the accompanying claims. Appendix A 3GPP STANDARD DEFINITIONS 
   
     
       
             
             
             
             
             
           
         
             
                 
             
             
               Information 
                 
                 
                 
                 
             
             
               Element/ 
                 
                 
               Type and 
             
             
               Group name 
               Need 
               Multi 
               reference 
               Semantics description 
             
             
                 
             
           
           
             
               Other 
                 
                 
                 
                 
             
             
               information 
             
             
               elements 
             
             
               SIB type 
               MP 
                 
               SIB Type, 
             
             
                 
                 
                 
               10.3.8.21 
             
             
               SIB data fixed 
               MP 
                 
               Bit string 
               The first/leftmost/most 
             
             
                 
                 
                 
               (226) 
               significant bit of the bit string 
             
             
                 
                 
                 
                 
               contains the first bit of the 
             
             
                 
                 
                 
                 
               segment. In case the SIB data 
             
             
                 
                 
                 
                 
               is less than 226 bits, padding 
             
             
                 
                 
                 
                 
               shall be used. The same 
             
             
                 
                 
                 
                 
               padding bits shall be used as 
             
             
                 
                 
                 
                 
               defined in clause 12.1 
             
             
                 
             
           
        
       
     
   
   
     
       
             
             
             
             
             
           
         
             
                 
             
             
               Information Element/Group 
                 
                 
               Type and 
               Semantics 
             
             
               name 
               Need 
               Multi 
               reference 
               description 
             
             
                 
             
           
           
             
               Other information elements 
                 
                 
                 
                 
             
             
               SIB type 
               MP 
                 
               SIB Type, 
             
             
                 
                 
                 
               10.3.8.21 
             
             
               SIB data variable 
               MP 
                 
               SIB data 
             
             
                 
                 
                 
               variable, 
             
             
                 
                 
                 
               10.3.8.20 
             
             
                 
             
           
        
       
     
   
   
     
       
             
             
             
             
             
           
         
             
                 
             
             
               Information Element/Group 
                 
                 
               Type and 
               Semantics 
             
             
               name 
               Need 
               Multi 
               reference 
               description 
             
             
                 
             
           
           
             
               Other Information elements 
                 
                 
                 
                 
             
             
               MIB Value tag 
               MP 
                 
               MIB Value 
             
             
                 
                 
                 
               tag 10.3.8.9 
             
             
               CN information elements 
             
             
               Supported PLMN types 
               MP 
                 
               PLMN Type 
             
             
                 
                 
                 
               10.3.1.12 
             
             
               PLMN Identity 
               CV- 
                 
               PLMN 
             
             
                 
               GSM 
                 
               Identity 
             
             
                 
                 
                 
               10.3.1.11 
             
             
               ANSI-41 information 
             
             
               elements 
             
             
               ANSI-41 Core Network 
               CV- 
                 
               ANSI-41 
             
             
               Information 
               ANSI- 
                 
               Core 
             
             
                 
               41 
                 
               Network 
             
             
                 
                 
                 
               Information 
             
             
                 
                 
                 
               10.3.9.1 
             
             
               References to other system 
               MP 
                 
               References 
             
             
               information blocks and 
                 
                 
               to other 
             
             
               scheduling blocks 
                 
                 
               system 
             
             
                 
                 
                 
               information 
             
             
                 
                 
                 
               blocks and 
             
             
                 
                 
                 
               scheduling 
             
             
                 
                 
                 
               blocks 
             
             
                 
                 
                 
               10.3.8.14 
             
             
                 
             
           
        
       
     
   
   
     
       
             
             
           
         
             
                 
             
             
               Condition 
               Explanation 
             
             
                 
             
           
           
             
               GSM 
               The IE is mandatory present if the IE “Supported 
             
             
                 
               PLMN Types” is set to ‘GSM-MAP’ or ‘GSM-MAP 
             
             
                 
               AND ANSI-41’, and not needed otherwise 
             
             
               ANSI-41 
               The IE is mandatory present if the IE “Supported 
             
             
                 
               PLMN Types” is set to ‘ANSI-41’ or ‘GSM-MAP AND 
             
             
                 
               ANSI-41’, and not needed otherwise 
             
             
                 
             
           
        
       
     
   
   
     
       
             
             
             
             
             
           
         
             
                 
             
             
               Information Element/Group 
                 
                 
               Type and 
               Semantics 
             
             
               name 
               Need 
               Multi 
               reference 
               description 
             
             
                 
             
           
           
             
               References to other system 
               MP 
                 
               References 
                 
             
             
               information blocks 
                 
                 
               to other 
             
             
                 
                 
                 
               system 
             
             
                 
                 
                 
               information 
             
             
                 
                 
                 
               blocks 
             
             
                 
                 
                 
               10.3.8.13 
             
             
                 
             
           
        
       
     
   
   
     
       
             
             
             
             
             
           
         
             
                 
             
             
               Information Element/Group 
                 
                 
               Type and 
               Semantics 
             
             
               name 
               Need 
               Multi 
               reference 
               description 
             
             
                 
             
           
           
             
               References to other system 
               MP 
                 
               References 
                 
             
             
               information blocks 
                 
                 
               to other 
             
             
                 
                 
                 
               system 
             
             
                 
                 
                 
               information 
             
             
                 
                 
                 
               blocks 
             
             
                 
                 
                 
               10.3.8.13 
             
             
                 
             
           
        
       
     
   
   
     
       
             
             
             
             
             
           
         
             
                 
             
             
               Information Element/Group 
                 
                 
               Type and 
               Semantics 
             
             
               name 
               Need 
               Multi 
               reference 
               description 
             
             
                 
             
           
           
             
               Message Type 
               MP 
                 
               Message 
                 
             
             
                 
                 
                 
               Type 
             
             
               UE information elements 
             
             
               RRC transaction identifier 
               MP 
                 
               RRC 
             
             
                 
                 
                 
               transaction 
             
             
                 
                 
                 
               identifier 
             
             
                 
                 
                 
               10.3.3.36 
             
             
               Integrity check info 
               CH 
                 
               Integrity 
             
             
                 
                 
                 
               check info 
             
             
                 
                 
                 
               10.3.3.16 
             
             
               Failure cause 
               MP 
                 
               Failure 
             
             
                 
                 
                 
               cause and 
             
             
                 
                 
                 
               error 
             
             
                 
                 
                 
               information 
             
             
                 
                 
                 
               10.3.3.14 
             
             
                 
             
           
        
       
     
   
   
     
       
             
             
             
             
             
           
         
             
                 
             
             
               Information Element/Group 
                 
                 
               Type and 
               Semantics 
             
             
               name 
               Need 
               Multi 
               reference 
               description 
             
             
                 
             
           
           
             
               CN domain identity 
               MP 
                 
               Enumerated 
                 
             
             
                 
                 
                 
               (CS domain, 
             
             
                 
                 
                 
               PS domain) 
             
             
                 
             
           
        
       
     
   
   
     
       
             
             
             
             
             
           
         
             
                 
             
             
               Information Element/Group 
                 
                 
               Type and 
               Semantics 
             
             
               name 
               Need 
               Multi 
               reference 
               description 
             
             
                 
             
           
           
             
               CN domain identity 
               MP 
                 
               CN domain 
                 
             
             
                 
                 
                 
               identity 
             
             
                 
                 
                 
               10.3.1.1 
             
             
               CHOICE CN Type 
               MP 
             
             
               &gt;GSM-MAP 
             
             
               &gt;&gt;CN domain specific NAS 
               MP 
                 
               NAS system 
             
             
               system information 
                 
                 
               information 
             
             
                 
                 
                 
               (GSM-MAP) 
             
             
                 
                 
                 
               10.3.1.9 
             
             
               &gt;ANSI-41 
             
             
               &gt;&gt;CN domain specific NAS 
               MP 
                 
               ANSI-41 
             
             
               system information 
                 
                 
               NAS system 
             
             
                 
                 
                 
               information, 
             
             
                 
                 
                 
               10.3.9.4 
             
             
               CN domain specific DRX 
               MP 
                 
               CN domain. 
             
             
               cycle length coefficient 
                 
                 
               specific 
             
             
                 
                 
                 
               DRX cycle 
             
             
                 
                 
                 
               length 
             
             
                 
                 
                 
               coefficient, 
             
             
                 
                 
                 
               10.3.3.6 
             
             
                 
             
           
        
       
     
   
   
     
       
             
             
             
             
             
           
         
             
                 
             
             
               Information Element/Group 
                 
                 
               Type and 
               Semantics 
             
             
               name 
               Need 
               Multi 
               reference 
               description 
             
             
                 
             
           
           
             
               PLMN identity 
               OP 
                 
               PLMN 
                 
             
             
                 
                 
                 
               identity 
             
             
                 
                 
                 
               10.3.1.11 
             
             
               CN common GSM-MAP NAS 
               OP 
                 
               NAS system 
             
             
               system information 
                 
                 
               information 
             
             
                 
                 
                 
               (GSM-MAP) 
             
             
                 
                 
                 
               10.3.1.9 
             
             
               CN domain related information 
               OP 
               1 to 
             
             
                 
                 
               &lt;maxCNdomains&gt; 
             
             
               &gt;CN domain identity 
               MP 
                 
               CN domain 
             
             
                 
                 
                 
               identity 
             
             
                 
                 
                 
               10.3.1.1 
             
             
               &gt;CN domain specific GSM-MAP 
               MP 
                 
               NAS system 
             
             
               NAS system info 
                 
                 
               information 
             
             
                 
                 
                 
               (GSM-MAP) 
             
             
                 
                 
                 
               10.3.1.9 
             
             
                 
             
           
        
       
     
   
   
     
       
             
             
             
             
             
           
         
             
                 
             
             
               Information Element/Group 
                 
                 
               Type and 
               Semantics 
             
             
               name 
               Need 
               Multi 
               reference 
               description 
             
             
                 
             
           
           
             
               PLMN identity 
               OP 
                 
               PLMN 
                 
             
             
                 
                 
                 
               identity 
             
             
                 
                 
                 
               10.3.1.11 
             
             
               CN common GSM-MAP NAS 
               OP 
                 
               NAS system 
             
             
               system information 
                 
                 
               information 
             
             
                 
                 
                 
               (GSM-MAP) 
             
             
                 
                 
                 
               10.3.1.9 
             
             
               CN domain related information 
               OP 
               1 to 
             
             
                 
                 
               &lt;maxCNdomains&gt; 
             
             
               &gt;CN domain identity 
               MP 
                 
               CN domain 
             
             
                 
                 
                 
               identity 
             
             
                 
                 
                 
               10.3.1.1 
             
             
               &gt;CN domain specific GSM-MAP 
               MP 
                 
               NAS system 
             
             
               NAS system info 
                 
                 
               information 
             
             
                 
                 
                 
               (GSM-MAP) 
             
             
                 
                 
                 
               10.3.1.9 
             
             
               &gt;CN domain specific DRX cycle 
               MP 
                 
               CN domain 
             
             
               length coefficient 
                 
                 
               specific DRX 
             
             
                 
                 
                 
               cycle length 
             
             
                 
                 
                 
               coefficient, 
             
             
                 
                 
                 
               10.3.3.6 
             
             
                 
             
           
        
       
     
   
   
     
       
             
             
             
             
             
           
         
             
                 
             
             
               Information 
                 
                 
                 
                 
             
             
               Element/Group 
                 
                 
               Type and 
               Semantics 
             
             
               name 
               Need 
               Multi 
               reference 
               description 
             
             
                 
             
           
           
             
               IMEI 
               MP 
               15 
                 
               The first element 
             
             
                 
                 
                 
                 
               contains the first IMEI 
             
             
                 
                 
                 
                 
               digit, the second 
             
             
                 
                 
                 
                 
               element the second 
             
             
                 
                 
                 
                 
               IMEI digit and so on. 
             
             
               &gt;IMEI digit 
               MP 
                 
               INTEGER(0..15) 
             
             
                 
             
           
        
       
     
   
   
     
       
             
             
             
             
             
           
         
             
                 
             
             
               Information 
                 
                 
                 
                 
             
             
               Element/Group 
                 
                 
               Type and 
               Semantics 
             
             
               name 
               Need 
               Multi 
               reference 
               description 
             
             
                 
             
           
           
             
               PLMN identity 
               MP 
                 
               PLMN 
                 
             
             
                 
                 
                 
               identity 
             
             
                 
                 
                 
               10.3.1.11 
             
             
               LAC 
               MP 
                 
               Bit string (16) 
               The first/leftmost bit of 
             
             
                 
                 
                 
                 
               the bit string contains the 
             
             
                 
                 
                 
                 
               most significant bit of 
             
             
                 
                 
                 
                 
               the LAC. 
             
             
                 
             
           
        
       
     
   
   
     
       
             
             
             
             
             
           
         
             
                 
             
             
               Information 
                 
                 
                 
                 
             
             
               Element/Group 
                 
                 
               Type and 
               Semantics 
             
             
               name 
               Need 
               Multi 
               reference 
               description 
             
             
                 
             
           
           
             
               NAS message 
               MP 
                 
               Octet string 
               The first octet contains 
             
             
                 
                 
                 
               (1..4095) 
               octet 1 [17] of the NAS 
             
             
                 
                 
                 
                 
               message, the second octet 
             
             
                 
                 
                 
                 
               contains octet 2 of the NAS 
             
             
                 
                 
                 
                 
               message and so 
             
             
                 
                 
                 
                 
               on. 
             
             
                 
             
           
        
       
     
   
   
     
       
             
             
             
             
             
           
         
             
                 
             
             
               Information 
                 
                 
                 
                 
             
             
               Element/Group 
                 
                 
               Type and 
               Semantics 
             
             
               name 
               Need 
               Multi 
               reference 
               description 
             
             
                 
             
           
           
             
               GSM-MAP 
               MP 
                 
               Octet 
               The first octet contains 
             
             
               NAS system 
                 
                 
               string(1..8) 
               octet 1 [17] of the NAS 
             
             
               information 
                 
                 
                 
               system information 
             
             
                 
                 
                 
                 
               element, the second octet 
             
             
                 
                 
                 
                 
               contains octet 2 of the NAS 
             
             
                 
                 
                 
                 
               system information 
             
             
                 
                 
                 
                 
               element and so on. 
             
             
                 
             
           
        
       
     
   
   
     
       
             
             
             
             
             
           
         
             
                 
             
             
               Information Element/Group 
                 
                 
               Type and 
               Semantics 
             
             
               name 
               Need 
               Multi 
               reference 
               description 
             
             
                 
             
           
           
             
               Paging record type 
               MP 
                 
               Enumerated 
                 
             
             
               identifier 
                 
                 
               (IMSI (GSM- 
             
             
                 
                 
                 
               MAP), TMSI 
             
             
                 
                 
                 
               (GSM-MAP)/ 
             
             
                 
                 
                 
               P-TMSI, 
             
             
                 
                 
                 
               IMSI (DS- 
             
             
                 
                 
                 
               41), TMSI 
             
             
                 
                 
                 
               (DS-41)) 
             
             
                 
             
           
        
       
     
   
   
     
       
             
             
             
             
             
           
             
             
             
             
             
           
         
             
                 
             
             
               Information 
                 
                 
                 
                 
             
             
               Element/Group 
                 
                 
               Type and 
               Semantics 
             
             
               name 
               Need 
               Multi 
               reference 
               description 
             
             
                 
             
           
           
             
                 
             
           
        
         
             
               MCC 
               MP 
               3 
                 
               The first element contains the 
             
             
                 
                 
                 
                 
               first MCC digit, the second 
             
             
                 
                 
                 
                 
               element the second MCC digit 
             
             
                 
                 
                 
                 
               and so on. 
             
             
                 
             
           
        
       
     
   
   
     
       
             
             
             
             
           
         
             
                 
             
             
               Parameters 
               REFERENCE 
               TYPE 
               NOTE 
             
             
                 
             
           
           
             
               MCC, Mobile Count Code 
                 
               M 
                 
             
             
               MNC, Mobile Network Code 
                 
               M 
             
             
                 
             
           
        
       
     
   
   
     
       
             
             
             
             
           
         
             
                 
             
             
               Parameters 
               REFERENCE 
               TYPE 
               NOTE 
             
             
                 
             
           
           
             
               Standby allowed reception level 
                 
               M 
               The usage of 
             
             
               (dBm) 
                 
                 
               these 
             
             
                 
                 
                 
               parameters 
             
             
                 
                 
                 
               needs 
             
             
                 
                 
                 
               clarification 
             
             
                 
                 
                 
               FFS. 
             
             
               Standby prohibited reception 
                 
               M 
             
             
               level (dBm) 
             
             
               Threshold for Cell Re-selection 
                 
               M 
             
             
               (dB) 
             
             
               Allowed reception SIR (dB) 
                 
               M 
             
             
               Radio link timeout