Abstract:
A method and apparatus for interfacing a synchronous core network with an asynchronous radio network in a next-generation mobile telecommunications system is disclosed. The method includes: a) selecting a function necessary to map a synchronous message to an asynchronous message; b) determining whether the synchronous message is to be transmitted to the mobile station or not; c) storing information necessary to map the synchronous message to the asynchronous message if the synchronous message is to transmitted to the mobile station, d) mapping parameters in the synchronous message to those in the asynchronous message, thereby generating the asynchronous message; e) discarding the message not to be transmitted to the mobile station after storing parameters included in the message not to be transmitted onto a predetermined device; and f) transmitting the asynchronous message to the radio resource controller.

Description:
CROSS-REFERENCE TO RELATED PATENT APPLICATIONS 
       [0001]    This application is a Continuation of U.S. patent application Ser. No. 12/212,118, filed Sep. 17, 2008, which is a continuation of U.S. patent application Ser. No. 11/022,497, filed Dec. 22, 2004 (now U.S. Pat. No. 7,443,881), which is a divisional of U.S. patent application Ser. No. 09/628,316, filed Jul. 28, 2000 (now U.S. Pat. No. 6,853,852), which claims priority to Korean Patent Application No. 1999-30927, filed Jul. 28, 1999, to Korean Patent Application No. 1999-30928, filed Jul. 28, 1999, to Korean Patent Application No. 1999-35876, filed Aug. 27, 1999, and to Korean Patent Application No. 1999-40165, filed Sep. 17, 1999. All of these applications are incorporated herein by reference in their entirety. 
     
    
     FIELD 
       [0002]    The present disclosure relates to a method and apparatus for interfacing a synchronous core network with an asynchronous radio network; and, more particularly to a method and apparatus for interfacing a synchronous core network with an asynchronous radio network in a next-generation mobile telecommunications system. 
       BACKGROUND 
       [0003]    In a conventional synchronous mobile telecommunication system, a synchronous mobile station 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. 
         [0004]    In a conventional asynchronous mobile telecommunication system, an asynchronous mobile station is connected to an asynchronous radio network (for example, a UMTS (universal mobile telecommunications system) Terrestrial Radio Access Network (UTRAN)), and a global system for mobile communications-mobile application part (GSM-MAP) network is connected to a core network. 
         [0005]      FIG. 1  shows core network interface architectures of the conventional synchronous/asynchronous mobile telecommunication systems as mentioned above. 
         [0006]      FIG. 1A  is a view showing the core network interface architecture of the conventional synchronous mobile telecommunications system. In this drawing, the reference numeral  110  denotes a synchronous mobile station,  120  denotes a synchronous radio network (e.g., a code division multiple access-2000 (CDMA-2000) radio network) which performs a data interfacing operation with the synchronous mobile station  110  and includes a synchronous base transceiver station/base station controller (BTS/BSC), and  130  denotes a synchronous core network which is connected to the synchronous radio network  120  and includes a synchronous mobile services switching center (MSC)  131  and an ANSI-41 network  133 . 
         [0007]    In the above core network interface architecture of the conventional synchronous mobile telecommunication system, the synchronous mobile station  110  can be connected to only the synchronous radio network  120  as well known to one skilled in the art, which is in turn connected to the synchronous core network  130 , thereby allowing the synchronous mobile station  110  to be interfaced with only the synchronous core network  130 . 
         [0008]      FIG. 1B  is a view showing the core network interface architecture of the conventional asynchronous mobile telecommunication system. In this drawing, the reference numeral  140  denotes an asynchronous mobile station,  150  denotes an asynchronous radio network (i.e., a UTRAN) which includes a base transceiver station (BTS) and a radio network controller (RNC), and  160  denotes an asynchronous core network which includes an asynchronous mobile services switching center (MSC)  161  connected to the asynchronous radio network  150  and a GMS-MAP network  163  connection to the asynchronous MSC  161 . 
         [0009]    In the above core network interface architecture of the conventional asynchronous mobile telecommunications system, the asynchronous mobile station  140  is connected to the asynchronous radio network  150  (e.g., UTRAN) which is in turn connected to the asynchronous core network  160 , thereby allowing the asynchronous mobile station  140  to perform a data interfacing operation with the asynchronous core network  160 . 
         [0010]      FIG. 2  shows layer protocol structures of the conventional mobile telecommunication systems as mentioned above. 
         [0011]      FIG. 2A  is a view showing the layered protocol structure of the conventional synchronous mobile telecommunications system. In this drawing, the reference numeral  110  denotes a synchronous mobile station,  120  a synchronous radio network and  50  a synchronous core network connected to the synchronous radio network  130 . 
         [0012]    The synchronous mobile station  110  comprises a layer 3   111 , a layer 2   114  and a layer 1   115 . The layer 3   111  includes a synchronous call control (CC) entity  113  for a call management and a synchronous mobility management (MM) entity  112  for a mobility management. 
         [0013]    The layer 1   115  is a physical layer which offers data transport services to higher layers and transfers transport blocks over a radio interface. 
         [0014]    The layer 2   114  is a data link layer which includes the 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. 
         [0015]    The MAC sub layer offers data transfer services on logical channels to a higher layer, the 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. 
         [0016]    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 an error correction, a duplicate detection, a ciphering and a flow control of the data. 
         [0017]    The layer 3   114  is a network layer which includes the following sub layers, a synchronous radio resource (RR) sub layer, a synchronous call control (CC) entity  113  and a mobility management (MM) entity  112 . In the synchronous system, the synchronous RR sub layer is not apparently separated from the others in the layer 3   111 . 
         [0018]    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 3   111  between a mobile station 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 the mobile station/radio network. 
         [0019]    The CC entity  113  handles a call control signaling of layer 3  between the mobile stations and the synchronous radio network. 
         [0020]    The MM entity  112  handles a mobility management signaling of layer  3  between the mobile stations and the synchronous radio network. 
         [0021]    The layers  3  to  1111 ,  114  and  115  in the synchronous mobile station  110  communicate with corresponding layers  121 ,  122  and  123  in the synchronous radio network  120 . 
         [0022]    The synchronous radio network  120  comprises a layer 3   121 , a layer 2   122  and a layer  1   123 . The layers  3  to  1121 ,  122  and  123  in the synchronous radio network  120  correspond respectively to those in the synchronous mobile station  110 . 
         [0023]    The layers  3  to  1 ,  121 ,  122  and  123  in the synchronous radio network  120  communicate with corresponding layers in the synchronous mobile station  110  and the synchronous core network  130 . 
         [0024]    The synchronous core network  130  comprises a layer 3   131 , a layer 2   134  and a layer  1   135 . The layers  3  to  1  in the synchronous radio network  130  correspond respectively to those in the synchronous radio network  120 . 
         [0025]    The layers  3  to  1131 ,  134  and  135  in the synchronous core network  130  communicate with corresponding layers  121 ,  122  and  123  in the synchronous radio network  120 . 
         [0026]    In the conventional synchronous mobile station and radio network as the layered protocol structure, the synchronous mobile station  110  receives a Sync channel message from the synchronous radio network  120  over a Synch channel and acquires information necessary to its connection to the synchronous core network  130 , including information related to the synchronous core network  130  and information about the synchronous radio network  120 , from the received Sync channel message. 
         [0027]    In other words, for interfacing with the synchronous ANSI-41 network via the synchronous radio network, the synchronous mobile station acquires system information (i.e., information related to the radio network and core network) after it is powered on. 
         [0028]    Information elements are written in the Sync channel message received by the synchronous mobile station, as follows: 
         [0029]    a) Protocol Revision Level: 8 bits, 
         [0030]    b) Minimum Protocol Revision Level: 8 bits, 
         [0031]    c) System Identification: 15 bits, 
         [0032]    d) Network Identification: 16 bits, 
         [0033]    e) Pilot Pseudo Noise (PN) sequence offset index: 9 bits, 
         [0034]    f) Long Code State: 42 bits, 
         [0035]    g) System Time: 36 bits, 
         [0036]    h) The number of Leap seconds that have occurred since the start of System Time: 8 bits, 
         [0037]    i) Offset of local time from System Time: 6 bits, 
         [0038]    j) Daylight savings time indicator: 1 bit, 
         [0039]    k) Paging Channel data Rate: 2 bits, 
         [0040]    l) Frequency assignment: 11 bits, 
         [0041]    m) Extended frequency assignment: 11 bits, and 
         [0042]    n) Orthogonal transmit diversity mode: 2 bits. 
         [0043]    The synchronous mobile station stores the following information elements from the received Sync channel message in its memory: 
         [0044]    a) Protocol Revision Level: 8 bits, 
         [0045]    b) Minimum Protocol Revision Level: 8 bits, 
         [0046]    c) System Identification: 15 bits, 
         [0047]    d) Network Identification: 16 bits, 
         [0048]    e) Pilot PN sequence offset index: 9 bits, 
         [0049]    f) Long Code State: 42 bits, 
         [0050]    g) System Time: 36 bits, 
         [0051]    h) Paging Channel Data Rate: 2 bits, and 
         [0052]    i) Orthogonal transmit diversity mode: 2 bits. 
         [0053]      FIG. 2B  is a view showing the layered protocol structure of the conventional asynchronous mobile telecommunications system. In this drawing, the reference numeral  140  denotes an asynchronous mobile station,  150  an asynchronous radio network (e.g., UTRAN) and  160  an asynchronous core network. 
         [0054]    The asynchronous mobile station  140  comprises a non-access stratum (NAS) part, a layer 3   144 , a layer 2   145 , and a layer 1   146 . In particular, the layer 3   144  includes an access stratum (AS) part. The NAS part includes an asynchronous call control (CC) entity  143  for management of a call and an asynchronous mobility management (MM) entity  142  for management of a mobility. The AS part includes an asynchronous radio resource control (RRC) block. 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. 
         [0055]    The asynchronous radio network  150  comprises a layer 3   151 , a layer 2   152 , and a layer 1   153 . The layer 3   151  of the asynchronous radio network  150  has no NAS part having an asynchronous CC entity and an asynchronous MM entity. The layers  3  to  1  of the asynchronous radio network  150  are connected and correspond respectively to those in the asynchronous mobile station  140  and those in the asynchronous core network  160 . However, since the asynchronous radio network  150  does not have the NAS part, i.e., the asynchronous CC entity and the asynchronous MM entity, the NAS parts of the asynchronous mobile station  140  and asynchronous core network  160  are coupled to each other not through the asynchronous radio network  150 . 
         [0056]    The asynchronous core network  160  comprises a NAS part  161  connected to that of the asynchronous mobile station  140 , a layer 3   164  having a AS part (not shown in  FIG. 2B ), a layer 2   165  and a layer  1   166  connected respectively to those in the asynchronous radio network  150 . The NAS part comprises an asynchronous CC entity  163  for management of a call and an asynchronous MM entity  162  for management of mobility. 
         [0057]    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, for convenience, detailed description of the layer  3  to  1  will be skipped. 
         [0058]    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 (MAS Protocol Specification), 3G TS25.322 (RLC Protocol Specification) and 3G TS25.331 (RRC Protocol Specification) in detail. 
         [0059]    In the conventional asynchronous mobile station and radio network having the layered protocol structure, the asynchronous mobile station  140  receives a system information message from the asynchronous radio network  150  over a broadcast control channel (BCCH) and acquires information necessary to its connection to the asynchronous core network  160 , including information related to the asynchronous core network  160  and information about the asynchronous radio network  150 , from the received system information message. 
         [0060]    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 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. 
         [0061]    IMT-2000 system requires new system concept, a high-level adaptation technology, and a novel network technology, as well all conventional technologies which were already adopted in the second digital cellular system. 
         [0062]    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. 
         [0063]    According to network deployment scenarios, the IMT-2000 system can have the following four interface architectures; first: synchronous mobile station—synchronous radio network—synchronous ANS1-41 network, second: synchronous mobile station—synchronous radio network—asynchronous GSM-MAP network, third: asynchronous mobile station—asynchronous radio network—synchronous ANSI-41 network, and fourth: asynchronous mobile station—asynchronous radio network—asynchronous GSM-MAP network. 
         [0064]      FIG. 3  is a view showing a protocol stack structure for interfacing a mobile station and a base station with a core network in a next-generation mobile telecommunications system. 
         [0065]    Referring to  FIG. 3 , it is illustrated a protocol stack structure for interfacing a mobile station and a base station with a core network having the same or a different operating type with/from the mobile station and the base station in a next-generation mobile telecommunications system such as the IMT-2000 system. 
         [0066]    The asynchronous mobile station includes a physical layer, a medium access layer, a radio link layer, a radio resource layer, a mobility management entity and a call control entity. Also, the asynchronous mobile station includes extensions and hooks. 
         [0067]    The extension performs a mapping function between the asynchronous mobile station and the synchronous core network. The hook provides environments for performing a mapping function between the asynchronous mobile station and the synchronous core network. 
         [0068]    The asynchronous base station includes the same elements with those of the asynchronous mobile station. 
         [0069]    Concepts of the protocol stack structure for interfacing a mobile station and a base station and a core network are already defined, however, specific functions the protocol stack structure are not yet defined and proposed. 
         [0070]    The conventional synchronous mobile station and radio network have a disadvantage in that the synchronous mobile station cannot be interfaced with any other networks than a synchronous core network connected thereto because synchronous mobile station cannot recognize an asynchronous message from an asynchronous core network, the conventional synchronous mobile station cannot communicate with the asynchronous core network. 
         [0071]    Similarly, the conventional asynchronous mobile station and radio network have a disadvantage in that the asynchronous mobile station cannot be interfaced with any other networks than an asynchronous core network because asynchronous mobile station cannot recognize a synchronous message from a synchronous core network, the conventional asynchronous mobile station cannot communicate with the synchronous core network. 
       SUMMARY OF THE INVENTION 
       [0072]    Therefore, it is an object of the invention to provide a method and apparatus for interfacing a synchronous core network with an asynchronous mobile station in a next-generation mobile telecommunication system. 
         [0073]    It is another object of the invention to provide a method and apparatus for transmitting a CC/MM entity between a synchronous core network between an asynchronous mobile station in a next-generation mobile telecommunication system. 
         [0074]    It is further another object of the invention to provide a method and apparatus for mapping a message transmitted between a synchronous core network and an asynchronous mobile station in a next-generation mobile telecommunication system. 
         [0075]    It is still further another object of the invention to provide a method and apparatus for transmitting a message between a synchronous core network to an asynchronous mobile station in a next-generation mobile telecommunication system. 
         [0076]    In accordance with an aspect of the preset invention, there is provided a method for mapping a message in order to interface a synchronous core network with an asynchronous radio network a base station (BS), the base station having a radio resource controller, a radio link controller, a medium access controller and a physical controller, the method comprising the steps of: a) selecting a function necessary to map a synchronous message to an asynchronous message; b) determining whether the synchronous message is to be transmitted to the mobile station or not; c) storing information necessary to map the synchronous message to the asynchronous message if the synchronous message it to be transmitted to the mobile station; d) mapping parameters in the synchronous message to those in the asynchronous message, thereby generating the asynchronous message; e) discarding the message not to be transmitted to the mobile station after storing parameters included in the message not to be transmitted onto a predetermined device; and f) transmitting the asynchronous message to the radio resource controller. 
         [0077]    In accordance with another aspect of the present invention, there is provided a method for transmitting a message from a synchronous core network to an asynchronous radio network having a base station (BS), the base station having a radio resource controller, a radio link controller, a medium access controller and a physical controller, the method comprising the steps of: receiving a synchronous message from the synchronous core network; and mapping the synchronous message to an asynchronous message based on information from supporting entities placed in the radio resource controller, the radio link controller, the medium access controller and the physical controller. 
         [0078]    In accordance with further another aspect of the present invention, there is provided a method for transmitting a message from an asynchronous radio network to a synchronous core network, the radio network having a base station (BS), a mobile station and the base station respectively having a radio resource controller, a radio link controller, a medium access controller and a physical controller, the method comprising the steps of: receiving an asynchronous message; and mapping the asynchronous message to a synchronous message based on information from supporting entities placed in the radio resource controller, the radio link controller, the medium access controller and the physical controller. 
         [0079]    In accordance with still further another aspect of the present invention, there is provided a method for transmitting a call control/mobility management (CC/MM) message from a synchronous core network to an asynchronous radio network, the radio network having a mobile station (MS), a base transceiver station (BTS) and a base station controller (BSC), the method comprising the steps of: a) receiving a message received from the synchronous core network, the message having parameters to be bypassed and parameters not to be bypassed; b) determining whether the parameters are to be bypassed or not; c) bypassing the parameters to be bypassed to the mobile station if the parameters are to be bypassed; and d) processing the parameters not be bypassed and generating a processed message if not. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0080]    The above and other objects and features of the instant invention will become apparent from the following description of preferred embodiments taken in conjunction with the accompanying drawings, in which: 
           [0081]      FIG. 1A  is a view showing the core network interface architecture of the conventional synchronous mobile telecommunications system; 
           [0082]      FIG. 1B  is a view showing the core network interface architecture of the conventional asynchronous mobile telecommunications system; 
           [0083]      FIG. 2A  is a diagram of layer protocols of a conventional synchronous mobile telecommunications system; 
           [0084]      FIG. 2B  is a diagram of layer protocols of a conventional asynchronous mobile telecommunications system; 
           [0085]      FIG. 3  is a view showing a protocol stack structure for interfacing a mobile station and a base station with a core network in a next-generation mobile telecommunications system; 
           [0086]      FIG. 4  is a diagram of protocol layers of an asynchronous mobile station and an asynchronous radio network for interfacing with a synchronous core network in accordance with an embodiment of the present invention; 
           [0087]      FIG. 5A to 5D  are block diagrams of supporting entities in accordance with the preset invention; 
           [0088]      FIG. 6  is a block diagram of a mapping entity in accordance with the preset invention; 
           [0089]      FIG. 7  is a flow chart illustrating a method for transmitting a message between an asynchronous radio network and a synchronous core network; 
           [0090]      FIG. 8  is a block diagram of a device for mapping a call control/mobile management (CC/MM) message between an asynchronous radio network and a synchronous core network in accordance with another embodiment of the present invention; 
           [0091]      FIG. 9  is a flow chart illustrating a method for determining whether the CC/MM message is bypassed or not; 
           [0092]      FIG. 10  is a flow chart illustrating a method for mapping a synchronous CC/MM message to an asynchronous CC/MM message; 
           [0093]      FIG. 11  is a flow chart illustrating a method for processing information used for the radio network; and 
           [0094]      FIG. 12  is a diagram showing operations for converting a synchronous authentication request message to an asynchronous message. 
       
    
    
     DETAILED DESCRIPTION 
       [0095]    Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. 
         [0096]      FIG. 4  is a diagram of protocol layers of an asynchronous mobile station and an asynchronous radio network for interfacing the asynchronous radio network with a synchronous core network in accordance with the present invention. 
         [0097]    The reference numeral  400  denotes an asynchronous radio network. The base station  400  includes a synchronous protocol processing block  402 , a mapping entity  404 , a call control/mobility management (CC/MM) entity  406 , a radio resource controller  408 , a radio link controller  410 , a medium access controller  412 , a physical layer  414  and a transport block  416 . 
         [0098]    The radio resource controller  408 , the radio link controller  420 , the medium access controller  412  and the physical layer  414  respectively include a supporting entity  408   a ,  410   a ,  412   a , or  414   a.    
         [0099]    The reference numeral  420  denotes an asynchronous mobile station. The asynchronous mobile station  420  includes a mapping entity  422 , a call control/mobility management (CC/MM) entity  424 , a radio resource controller  426 , a radio link controller  428 , a medium access controller  430  and a physical layer  432 . 
         [0100]    The radio resource controller  426 , the radio link controller  428 , the medium access controller  430  and the physical layer  432  respectively include a supporting entity  426   a ,  428   a ,  430   a  or  432   a.    
         [0101]    The supporting entity interfaces the asynchronous radio network with the synchronous core network. 
         [0102]    If data is received from the synchronous core network, it is determined whether the data is to be transmitted to the mobile station  420  or not. If the data is to be transmitted to the mobile station, a message mapping or parameter mapping of the data is performed in the mapping entity  404 . The mapped data is provided to the radio resource controller  408 . The radio resource controller  408  transmits the mapped data to the CC/MM entity  406  of the mobile station  420  by using the radio resource message. 
         [0103]    The mapping entity  404  transmits an information request primitive requesting information necessary to map or to generate parameters to the supporting entity  408   a  in the radio resource controller  408 . When receiving the information request primitive, the supporting entity transmits the information requested to the mapping entity  404 . 
         [0104]    Referring to  FIG. 5A , the supporting entity  104   a  includes a SE service processing block  502 , a layer link block  504 , and a layer function processing block  506 . 
         [0105]    The SE service processing block  502  provides a communication path for a data communication between the supporting entity and the mapping entity  404 . The SE service processing block  502  transmits the information request primitive to the layer link block  504 . 
         [0106]    The layer link block  504  interfaces the SE service processing block  502  with the layer function processing block  506 . In other words, the layer link block  504  maps information related to upper layers to data having a format used in the layer function processing block  506 . 
         [0107]    The layer function processing block  506  controls a radio resource setting and management based on information for the layer link block  504 . The layer function processing block  506  obtains information requested by the mapping entity  404  radio resource controller. The information obtained from the radio resource controller is transmitted to the mapping entity  404  through the layer function processing block  506 , the layer link block  504  and the SE service processing block  502 . 
         [0108]    Referring to  FIG. 4  again, the radio link controller  410  controls a setting/releasing of a radio link connection based on information from the radio resource controller  408 . If the mapping entity  404  requests the supporting entity  410   a  in the radio link controller  410  to provide information necessary to a parameter mapping or a parameter generation, the supporting entity  410   a  provides requested information to the mapping entity  404 . 
         [0109]    Referring to  FIG. 5B , the supporting entity  410   a  includes a SE service processing block  512 , a layer link block  514 , and a layer function processing block  516 . 
         [0110]    The SE service processing block  502  provides a communication path for data communication between the supporting entity and the mapping entity  404 . The SE service processing block  512  transmits the information request primitive to the layer link block  514 . 
         [0111]    The layer link block  514  interfaces the SE service processing block  512  with the layer function processing block  516 . 
         [0112]    The layer function processing block  516  controls setting/releasing a connection to the radio link controller and data transmission based on information from the layer link block  504 . The radio link controller is responsible for data transmission. The layer function processing block  516  obtains information requested by the mapping entity from the radio link controller. The information obtained from the radio link controller is transmitted to the mapping entity through the layer function processing block  516 , the layer link block  514  and the SE service processing block  512 . 
         [0113]    Referring to  FIG. 4  again, the medium access controller  106  controls access to a physical medium based on the information obtained from the radio link controller  410 . If the mapping entity  404  requests the supporting entity  3412   a  in the medium access controller  412  to provide information necessary to a parameter mapping or a parameter generation, the supporting entity  412   a  provides requested information to the mapping entity  404 . 
         [0114]    Referring to  FIG. 5C , the supporting entity  412   a  includes a SE service processing block  522 , a layer link block  524 , and a layer function processing block  526 . 
         [0115]    The SE service processing block  522  provides a communication path for data communication between the supporting entity and the mapping entity  404 . The SE service processing block  522  transmits the information request primitive to the layer link block  526 . 
         [0116]    The layer link block  524  interfaces the SE service processing block  522  with the layer function processing block  526 . 
         [0117]    The layer function processing block  526  controls reassignment of the radio resource, interfaces the physical layer  414  with the radio resource controller  408 . The layer function processing block  526  obtains information requested by the mapping entity from the medium access controller. The information obtained from the medium access controller is transmitted to the mapping entity through the layer function processing block  526 , the layer link block  524  and the SE service processing block  522 . 
         [0118]    Referring to  FIG. 4  again, the physical layer  414  controls a connection to a physical medium based on the information obtained from the medium access controller  412 . If the mapping entity  404  requests the supporting entity  414   a  in the medium access controller  414  to provide information necessary to a parameter mapping or parameter generation, the supporting entity  414   a  provides requested information to the mapping entity  404 . 
         [0119]    Referring to  FIG. 5D , the supporting entity  414   a  includes a SE service processing block  532 , a layer link block  534 , and a layer function processing block  536 . 
         [0120]    The SE service processing block  532  provides a communication path for data communication between the supporting entity and the mapping entity  404 . The SE service processing block  532  transmits the information request primitive to the layer link block  534 . 
         [0121]    The layer link block  534  interfaces the SE service processing block  532  with the layer function processing block  536 . 
         [0122]    The layer function processing block  536  performs a radio interface. The layer function processing block  536  obtains information requested by the mapping entity from the physical layer. The information obtained from the physical layer is transmitted to the mapping entity through the layer function processing block  536 , the layer link block  534  and the SE service processing block  532 . 
         [0123]    The mapping entity  422  in the mobile station  420  receives information from the synchronous core network and transmits information to be transmitted to the synchronous core network through communications message with the mapping entity  404  in the radio access network  400 . The mapping entity  422  performs the parameter mapping or the parameter generation with is similar to be performed by the mapping entity  404 . Therefore, for convenience, detailed description will be skipped in this specification. 
         [0124]      FIG. 6  is a block diagram of a mapping entity in accordance with an embodiment of the present invention. 
         [0125]    The mapping entity  404  includes a filtering block  602 , a service access point (SAP) block  604 , a data storing/compensating block  606 , a parameter mapping block  608 , a message/parameter generating block  610  and a discarding block  612 . 
         [0126]    The filtering block  602  selects a function necessary to generate or to map messages received from the asynchronous radio network or the asynchronous mobile station. 
         [0127]    The data storing/compensating block  606 , if necessary, stores information necessary to generate or to map the message/parameter and corrects stored message/parameter. 
         [0128]    The parameter mapping block  608  is coupled to the filtering block  602 . The parameter mapping block  608  maps the parameters of the messages received from the filtering block  602  into parameters of messages from the asynchronous radio network, if the message is transmitted from the synchronous core network to the asynchronous mobile station. The parameter mapping block  608  maps the parameters of the messages received from the filtering block  602  into parameters of messages for the synchronous core network, if the message is transmitted from the asynchronous mobile station to the synchronous core network. Then, the mapped data is transmitted to the filtering block  602 . 
         [0129]    The message/parameter generating block  610  generates messages and parameters to be transmitted to the asynchronous radio network or the synchronous core network based on the data stored onto the data storing/compensating block  606 . 
         [0130]    In other words, the message/parameter generating block  610  generates a new message or parameter if there is no related parameter in the message to be transmitted to the asynchronous mobile station or the synchronous core network. In similar, the message/parameter generating block  610  generates a new message or parameter if there is no related parameter in the message to be transmitted to the synchronous core network. 
         [0131]    The discarding block  612  discards the message/parameter not to be transmitted to the asynchronous radio network in the message/parameters received from the filtering block  602 . The discarding block  612  allows information included in the received parameter to be stored on a database  614  and corrects the information stored on the database  614 . The discarding block  612  discards the message/parameter not to be transmitted to the asynchronous mobile station in the message/parameters received from the filtering block  602 . The discarding block  612  allows information included in the received parameters to be stored on a database  614  and corrects the information stored on the database  614 . 
         [0132]    The filtering block  602  transmits the message or parameter which is used for the filtering block  602  or to be transmitted to the asynchronous mobile station  420  to the SAP block  604 . The message or the parameter transmitted to the SAP block  604  is a message or a parameter which is mapped or generated in the parameter mapping block  608 , the message/parameter generating block  610  or the discarding block  612 . 
         [0133]    The SAP block provides a patch for a data transmission between the filtering block  602  and the radio resource controller. The SAP block  604  manages an asynchronous service access point function. 
         [0134]    When transmitting the message/parameter to the lower layers, if possible, the message/parameter is transmitted to the radio resources controller by the RRC SAP block. If there is a function which is not defined in the RRC SAP block, the message/parameter is transmitted to the radio resource controller by a supporting entity (SE) SAP function of the supporting entity  604   a.    
         [0135]    Then, the RRC transfers the received message to its lower layers, or transmits the received message to the CC/MM  424  of the asynchronous mobile station  420  by using a RRC message. 
         [0136]    The mapping entity  422  included in the asynchronous mobile station has elements and functions similar to those of the asynchronous radio network. Therefore, for convenience, detailed description about the mapping entity  422  will be skipped in the specification. 
         [0137]      FIG. 7  is a flow chart illustrating a method for transmitting a message between an asynchronous radio network and a synchronous core network. 
         [0138]    First, a message is received from a synchronous core network in step S 702 . The process goes to step S 704  to select a function necessary to transmit the received message to the asynchronous mobile station. In other words, one of a message mapping function, a message/parameter generating function, a message/parameter storing function, or a message parameter discarding function is selected. 
         [0139]    At step S 706 , it is determined whether there is a message to be transmitted to the asynchronous mobile station. If there is no message to be transmitted to the asynchronous mobile station, the parameters included in the message are stored onto the database  614  and the message is discarded at step S 708 . 
         [0140]    If there is a message to be transmitted to the asynchronous mobile station, it is determined whether there is a related parameter in the received message at step S 710 . 
         [0141]    If there is the related parameter in the received message, the parameter for the synchronous message is mapped to a parameter for the asynchronous message at step  712 . 
         [0142]    If there is no related parameter, a parameter for the asynchronous message is generated by using the stored parameter at step  714 . 
         [0143]    Then, it is determined whether the mapped or generated message can be transmitted by using a conventional RRC SAP function at step S 716 . If possible, the message is transmitted to the RRC by using the conventional RRC SAP function at step S 718 . If not, the message is transmitted to the RRC by using the supporting entity (SE) SAP function at step S 720 . 
         [0144]    The RRC transmits the generated message to the CC/MM entity of the asynchronous mobile station by using the RRC message at step S 722 . 
         [0145]      FIG. 8  is a block diagram of a CC/MM mapper for mapping a call control/mobile management (CC/MM) message between an asynchronous radio network and a synchronous core network. 
         [0146]    Hereinafter, a method and apparatus for interfacing a synchronous core network with a radio network in accordance with another embodiment of the preset invention will be described with reference to  FIGS. 8 to 12 . 
         [0147]    The CC/MM mapper includes a discriminator  842  a bypass parameter processing block (BPP)  844  and an action parameter processing block (APP)  846 . 
         [0148]    The discriminator  840  monitors a CC/MM message and divides the message into parameters to by bypassed and parameters not to be bypassed. 
         [0149]    The BPP  844  encapsulates the parameter to be bypassed or maps the parameter in accordance with a message format used in the radio resource controller of the asynchronous radio network. Then, the BPP  844  transmits encapsulated or mapped parameter to the asynchronous mobile station. 
         [0150]    The APP  846  stores onto the database  848  or transmits information to be processed in the asynchronous radio network to lower protocol layers, i.e., the radio resource controller  850 , the radio link controller  852  and the medium access controller  854 . 
         [0151]      FIG. 9  is a flow chart illustrating a method for determining whether the CC/MM message is bypassed or not. 
         [0152]    First, a message for CC/MM is received from the synchronous core network at step S 902 . The discriminator divides the message into parameters to be bypassed and parameters not to be bypassed at step S 904 . Then, it is determined whether the parameter is to be bypassed or not at step S 906 . If the message is to be bypassed, the message is transmitted to the BPP  844  at step S 908 . If not, the message is transmitted to the APP  846  at step S 910 . 
         [0153]      FIG. 10  is a flow chart illustrating a method for mapping synchronous CC/MM message to asynchronous CC/MM message. 
         [0154]    The BPP  844  receives a message to be bypassed from the discriminator at step S 1002 , and determines whether the message can be converted by a mapping or an encapsulation at step S 1004 . If the message cannot be converted by the mapping method, in other words, if the message can be converted by the encapsulating method, the BPP  844  encapsulates the message in accordance with the data format of the asynchronous radio resource controller and bypasses an encapsulated message to the asynchronous mobile station at step S 1   008 . 
         [0155]    If the message should be converted by the mapping method, the BPP  844  maps the synchronous parameter into an asynchronous parameter and determines whether a size of the mapped parameter is equal to a predetermined size at steps S 1006  and S 1010 . If the size of the mapped parameter is equal to the predetermined size, the BPP  844  arranges the mapped parameters in the order of the synchronous message and transmits the mapped parameter to the asynchronous mobile station at step S 1014 . If not, the BPP  844  adjusts a length of the mapped parameter in accordance with the predetermined size at step S 1012 . Then, the BPP  844  arranges the parameters in the order of the asynchronous message and transmits the parameter having the same length with the predetermined size at steps S 1012  and S 1014 . 
         [0156]      FIG. 11  is a flow chart illustrating a method for processing a parameter not to be bypassed. 
         [0157]    The APP  846  receives a parameter not to be bypassed, i.e., a parameter used in the asynchronous radio network at step S 1102 , and determines whether the parameter of the message is to be processed at step S 1104 . 
         [0158]    If the parameter is to be processed, the APP processes the parameters at step S 1106 . If not, the APP stores the message onto the database at step  1108 . 
         [0159]      FIG. 12  is a diagram showing operations for converting synchronous authentication request message to asynchronous authentication request message. 
         [0160]    If an authentication request message is received at a synchronous CC/MM entity  830   a  included in a synchronous core network, a call processing block  840  of an asynchronous base station determines whether the authentication request message should be bypassed or not in order to be transmitted to an asynchronous CC/MM entity  810   a  in a asynchronous mobile station. 
         [0161]    The discriminator  842  divides the authentication request message into parameters to be bypassed and parameters to be processed in the asynchronous base station. For example, parameters to be processed in the asynchronous base station include a mobility identity, a last paging frame class, etc. the parameters to be bypassed include a message type, an authentication challenge parameter, etc. 
         [0162]    The parameters to be bypassed are transmitted to the BPP  844 . The parameters to be processed in the asynchronous base station are transmitted to the APP  846 . 
         [0163]    The BPP  844  receives the message to be bypassed from the discriminator and determines whether the message can be converted by a mapping or an encapsulating method. If the message cannot be converted by the mapping method, in other words, if the message should be converted by the encapsulating method, the BPP  844  encapsulates the parameter in accordance with the data format of the asynchronous radio resource controller and bypasses the encapsulated parameter to the asynchronous mobile station. 
         [0164]    If the parameter should be converted by the mapping method, the BPP  844  maps the synchronous parameter into an asynchronous parameter and determines whether a size of the mapped parameter is equal to a predetermined size. If the size of the mapped parameter is equal to the predetermined size, the BPP transmits the mapped parameter to the asynchronous mobile station. If not, the BPP  844  adjusts a length of the mapped parameter in accordance with the predetermined size by using padding. The BPP  844  bypasses the parameter having the same length with the predetermined size in order to transmit the parameter. 
         [0165]    If the APP  846  receives a message not to be bypassed, i.e., the parameter used in the asynchronous base station, and determines whether the parameter is to be processed in a lower layer, for example, RRC, RLC or MAC. If the parameter is to be processed in lower layer, the APP  846  allows the parameter to be processed in the lower layer, for example, RRC, RLC or MAC. 
         [0166]    If the parameters of the message are to be reused, the APP  846  stores the message onto the database. When a response message to the authentication request message is received from the asynchronous mobile station, the asynchronous base station transmits the response message to the synchronous core network based on the stored parameters. 
         [0167]    Although the preferred embodiments of the invention have been disclosed for illustrative purpose, those skilled in the art will be appreciate the various modifications, additions and substitutions are possible, without departing from the scope and spirit of the invention as disclosed in the accompanying claims.