KR100602024B1 - Method for transmitting radio resource control message in asynchronous mobile communication system - Google Patents

Abstract

The present invention is an asynchronous mobile communication system to facilitate the RRC message transmission between the asynchronous terminal and the asynchronous wireless network irrespective of the type of core network to be connected (asynchronous core network GSM-MAP core network, synchronous core network ANSI-41 core network) The present invention relates to a method for transmitting a radio resource control message in the present invention. When the core network connected to an asynchronous wireless network in an asynchronous mobile communication system is a GSM-MAP network, which is an asynchronous core network, between the asynchronous communication wireless network and the asynchronous terminal. Among the various information elements included in the RRC messages exchanged with each other, the information field included in the core network related information elements uses the RRC message used in the existing asynchronous system as it is, and connects to the asynchronous wireless network in the asynchronous mobile communication system. If the core network is the ANSI-41 network, which is a synchronous core network, the core of the asynchronous RRC message Network-related information elements are converted into new information fields suitable for synchronous transmission, and other information elements are used for the RRC message transmission using the existing asynchronous RRC message.

ANSI-41 Core Network, Synchronous Wireless Network, Asynchronous Wireless Network, Asynchronous Terminal, IMT-2000

Description

Method for transmitting radio resource control message in asynchronous mobile communication system             

1 is a diagram illustrating a network interworking structure of a conventional synchronous / asynchronous mobile communication system, FIG. 1A is a diagram illustrating a network interworking structure of a synchronous mobile communication system, and FIG. 1B is a diagram illustrating a network interworking structure of an asynchronous mobile communication system. ,

FIG. 2 is a diagram illustrating each protocol layer structure in a conventional synchronous / asynchronous mobile communication system. FIG. 2A is a diagram illustrating each protocol layer structure of a synchronous mobile communication system, and FIG. 2b is a diagram illustrating each protocol layer structure of an asynchronous mobile communication system. Is the drawing shown,

3 is a diagram illustrating a core network interworking structure according to a result of an OHG meeting, FIG. 3a is a synchronous ANSI-41 core network interworking structure diagram in a synchronous mobile communication system, and FIG. 3b is asynchronous GSM-MAP core network interworking in a synchronous mobile communication system. 3c is an asynchronous GSM-MAP core network interworking structure diagram in an asynchronous mobile communication system, FIG. 3d is a synchronous ANSI-41 core network interworking structure diagram in an asynchronous mobile communication system,

4 is a protocol hierarchy diagram of a conventional synchronous / asynchronous terminal. FIG. 4A is a protocol hierarchy diagram of a synchronous terminal interworking with an ANSI-41 core network. FIG. 4B is a protocol hierarchy diagram of a synchronous terminal interworking with a GSM-MAP core network. 4C is a protocol layer structure diagram of an asynchronous terminal interworking with the ANSI-41 core network, and FIG. 4D is a protocol layer structure diagram of an asynchronous terminal interworking with the GSM-MAP core network.

5 is a flowchart illustrating a process of transmitting an RRC message by an asynchronous terminal to an asynchronous wireless network in an asynchronous mobile communication system according to the present invention.

6 is an RRC connection request message structure diagram according to the present invention. FIG. 6A is an RRC connection request message structure diagram when the core network is a GSM-MAP core network. FIG. 6B is an RRC connection request when the core network is an ANSI-41 core network. Message structure,

7 is an RRC connection reconfiguration message structure diagram according to the present invention. FIG. 7A is an RRC connection reconfiguration message structure diagram when the core network is a GSM-MAP core network. FIG. 7B is an RRC connection reconfiguration message when the core network is an ANSI-41 core network. Message structure,

8 is an RRC UE capability message structure diagram according to the present invention, FIG. 8A is an RRC UE capability message structure diagram when the core network is a GSM-MAP core network, and FIG. 8B is an RRC UE capability when the core network is an ANSI-41 core network. Message structure,

9 is an RRC Direct Transfer Message structure diagram according to the present invention, FIG. 9A is an RRC Direct Transfer Message structure diagram when the core network is a GSM-MAP core network, and FIG. 9B is an RRC Direct Transfer message when the core network is an ANSI-41 core network. Message structure

FIG. 10 is a structure diagram of a handover failure message between RRC systems according to the present invention, FIG. 10A is a structure diagram of a handover failure message between RRC systems when the core network is a GSM-MAP core network, and FIG. 10B is an ANSI-41 core network. FIG. 10C is a diagram illustrating field contents included in a message field of FIG. 10B. FIG. 10D is a diagram illustrating each information field of FIG. 10C.
11 is a flowchart illustrating a process in which an asynchronous wireless network transmits an RRC message to an asynchronous terminal in an asynchronous mobile communication system according to the present invention.

delete

12 is an RRC connection setup message structure diagram according to the present invention, FIG. 12A is an RRC connection setup message structure diagram when a core network is a GSM-MAP core network, and FIG. 12B is an RRC connection setup when a core network is an ANSI-41 core network. Message structure,

13 is an RRC call message structure diagram according to the present invention, FIG. 13A is an RRC call message structure diagram when the core network is a GSM-MAP core network, and FIG. 13B is an RRC call message structure diagram when the core network is an ANSI-41 core network. ,

14 is an RRC secret mode control message structure diagram according to the present invention, FIG. 14A is an RRC secret mode control message structure diagram when the core network is a GSM-MAP core network, and FIG. 14B is an RRC case when the core network is an ANSI-41 core network. Secret mode control message structure diagram,

FIG. 15 is a diagram illustrating an RRC radio basic setup message structure according to the present invention. FIG. 15A is a diagram illustrating an RRC radio basic setup message structure when a core network is a GSM-MAP core network. FIG. 15B is an RRC diagram when an core network is an ANSI-41 core network. Wireless basic setup message structure

FIG. 16 is a structure diagram of an RRC cell update confirmation message according to the present invention. FIG. 16A is a structure diagram of an RRC cell update confirmation message when the core network is a GSM-MAP core network, and FIG. 16B is an RRC cell when the core network is an ANSI-41 core network. Cell update confirmation message structure diagram.

FIG. 17 is a structure diagram of an RRC URA update confirmation message according to the present invention, FIG. 17A is a structure diagram of an RRC URA update confirmation message when the core network is a GSM-MAP core network, and FIG. URA update confirmation message structure diagram,

18 is an RRC RNTI reassignment message structure diagram according to the present invention, FIG. 18A is an RRC RNTI reassignment message structure diagram when the core network is a GSM-MAP core network, and FIG. 18B is an RRC when the core network is an ANSI-41 core network RNTI reallocation message structure diagram.

19 is an RRC active set update message structure diagram according to the present invention, FIG. 19A is an RRC active set update message structure diagram when the core network is a GSM-MAP core network, and FIG. 19B is an RRC when the core network is an ANSI-41 core network. Active Set Update Message Structure

20 is an RRC handover command message structure diagram according to the present invention, FIG. 20A is an RRC handover command message structure diagram when the core network is a GSM-MAP core network, and FIG. 20B is an RRC when the core network is an ANSI-41 core network. Handover command message structure diagram,

FIG. 21 is a diagram illustrating a structure of a handover command message between RRC systems according to the present invention. FIG. 12A is a diagram of a structure of a handover command message between RRC systems when the core network is a GSM-MAP core network. FIG. 21B is an ANSI-41 core network. FIG. 21C is a diagram showing the contents included in the message field of FIG. 21B.

<Explanation of symbols for the main parts of the drawings>

210: asynchronous terminal 211: synchronous CC

212: synchronous MM 213: asynchronous CC

214: asynchronous MM 220: asynchronous wireless network

The present invention relates to radio resource control (hereinafter, abbreviated as "RRC") message transmission in an asynchronous mobile communication system (especially, an asynchronous International Mobile Telecommunications-2000 (IMT-2000) system). Regardless of the type of network (asynchronous core network, GSM-MAP core network and synchronous core network, ANSI-41 core network), RRC message transmission between asynchronous terminal and asynchronous wireless network is smoothly performed. It is about a method.
In more detail, when the core network connected to the asynchronous wireless network in the asynchronous mobile communication system is a GSM-MAP network which is an asynchronous core network, only core type information is inserted into the RRC message used in the existing asynchronous system. If the core network connected to the asynchronous wireless network is an ANSI-41 network which is a synchronous core network, information fields depending on the type of core network among asynchronous RRC messages (core network related information fields, information fields not related to radio resources, Information fields related to radio resources depending on the type of the core network) are changed to new information fields suitable for synchronous operation, and other information fields are generated using the existing asynchronous RRC message. The present invention relates to a method for transmitting a radio resource control message in a mobile communication system.
In a conventional synchronous mobile communication system, a synchronous terminal and a synchronous wireless network (which means "CDMA-2000 wireless network") of a synchronous communication method are connected, and are connected to an ANSI-41 network through a core network (CN).
In addition, in the conventional asynchronous mobile communication system, asynchronous terminal and asynchronous wireless network of asynchronous communication type UTRAN (UMRAN Terrestrial Radio Access Network) is connected, the core network (CN) Global System for Mobile Communication-Mobile Application GSM-MAP Part) Connect to the network.
1 is a diagram illustrating a conventional core network interworking structure of a synchronous / asynchronous mobile communication system as described above.
FIG. 1A is a diagram illustrating a core network interworking structure of a synchronous mobile communication system, in which reference numeral 11 denotes a synchronous terminal, and reference numeral 12 wirelessly interfaces data with the synchronous terminal 11 and includes a base station and a control station. Reference numeral 13 denotes a synchronous wireless network (CDMA-2000 wireless network), and the reference numeral 13 denotes a synchronous core network connected to the synchronous wireless network 12, which is a synchronous mobile communication switch (MSC) 14 and an ANSI-41 network (15). ).
In the core network interworking structure of such a synchronous mobile communication system, the synchronous terminal 11 is connected to the synchronous wireless network 12, as is well known, and the synchronous wireless network 12 is connected to the synchronous core network 13, thereby providing data. Interface.
1B is a diagram illustrating a core network interworking structure of an asynchronous mobile communication system, in which reference numeral 21 denotes an asynchronous terminal, 22 denotes an UTRAN, which is an asynchronous wireless network including a base station and a control station, and 23 denotes an UTRAN 22. An asynchronous core network including an asynchronous mobile communication switch (MSC) 24 to be connected and a GSM-MAP network 25 connected to the asynchronous mobile communication switch 24 is shown.
In the core network interworking structure of the asynchronous mobile communication system, the asynchronous terminal 21 is connected to the UTRAN 22 which is an asynchronous wireless network, and the UTRAN 22 is connected to the asynchronous core network 23 to interface data.
2 is a diagram showing the protocol structure of each part of the synchronous / asynchronous mobile communication system as described above.
2A is a diagram illustrating a protocol structure of each part of a synchronous mobile communication system, in which reference numeral 30 denotes a synchronous terminal, reference numeral 40 denotes a synchronous wireless network, and 50 denotes a synchronous connected to the synchronous wireless network 40. Represents a core network.
The synchronization terminal 30 is divided into a layer 3 (31), a layer 2 (34), a layer 1 (35) and provided with a protocol corresponding to each level, in particular, the layer 3 (31) for call management A call control (CC) 32 and a synchronous mobility management unit (MM) 33 for mobility management are provided.
In addition, the synchronous radio network 40 includes protocols corresponding to the layer 3 (41), the layer 2 (42), and the layer 1 (43), and the same layer as each layer of the sync terminal 30 corresponds.
In addition, the synchronous core network 50 is divided into Layer 3 (51), Layer 2 (54), and Layer 1 (55) and provided with a protocol corresponding to each level. In particular, the layer 3 (51) includes call management. A call control (CC) 52 for synchronization and a mobility management unit (MM) 53 for mobility management are provided.
2B is a diagram showing the protocol structure of each part of an asynchronous mobile communication system, where reference numeral 60 denotes an asynchronous terminal, 70 denotes a UTRAN, and 80 denotes an asynchronous core network.
The asynchronous terminal 60 is divided into a NAS unit 61, a layer 3 (64), a layer 2 (65), a layer 1 (66), and a protocol corresponding to each level is provided. 61 includes an asynchronous call control (CC) 62 for call management and an asynchronous mobility management unit (MM) 63 for mobility management.
Further, the UTRAN 70 corresponds to each layer of the asynchronous terminal 60 and also corresponds to each layer with the asynchronous core network 80. The layer 3 (71), the layer 2 (72), and the layer 1 (73). The corresponding protocol is implemented.
In addition, the asynchronous core network 80 is a NAS unit 81 having an asynchronous call control unit (CC) 82 for connecting to the asynchronous terminal 60, an asynchronous mobility management unit (MM) 83 for mobility management. And a protocol corresponding to Layer 3 (84), Layer 2 (85), and Layer 1 (86) for connecting to each layer in the UTRAN (70).
In the interworking structure as described above, the synchronization terminal 30 receives a synchronization channel message through a synchronization channel from a synchronous wireless network 40 of a synchronous communication method, and connects core network information or synchronization through the synchronization channel message. The synchronous terminal including the wireless network information acquires information necessary for accessing the network.
In addition, the asynchronous terminal 60 receives a system information message (System Information Message) from the UTRAN 70 through a broadcast control channel (BCCH), through which the asynchronous terminal including core network information or UTRAN information Information necessary for access to the network is obtained.
In the case of the synchronous / asynchronous method of the IMT-2000 system, a GSM-MAP network that is used asynchronously or an ANSI-41 network that is used synchronously may be used as a core network according to the May 1999 OHG requirement decision.
That is, the IMT-2000 system may have the following four interworking structures according to the network deployment situation.
Firstly, it is a synchronous terminal, a synchronous communication type wireless network and an ANSI-41 network interworking structure. Secondly, a synchronous terminal, a synchronous communication type wireless network and a GSM-MAP network interworking structure. , Asynchronous communication type wireless network and ANSI-41 network interworking structure. Fourth, asynchronous terminal, asynchronous communication wireless network and GSM-MAP network interworking structure.
3 is a diagram illustrating a core network interworking structure according to the results of an OHG meeting.
First, FIG. 3A is a synchronous ANSI-41 core network interworking structure diagram in a synchronous mobile communication system, where reference numeral 100 denotes a synchronous terminal, 110 denotes a synchronous wireless network, and 120 denotes a synchronous core network.
3B illustrates an interworking structure when a core network connected in a synchronous mobile communication system is an asynchronous core network, reference numeral 100 denotes a synchronous terminal, 110 a synchronous wireless network, and 130 an asynchronous core network. 130 includes a GSM-MAP network.
Next, FIG. 3C is an asynchronous GSM-MAP core network interworking structure diagram in an asynchronous mobile communication system, in which reference numeral 210 is an asynchronous terminal, 220 is UTRAN which is an asynchronous wireless network, and 230 is connected to UTRAN 220 which is the asynchronous wireless network. As the core network, it includes an asynchronous GSM-MAP network.
3D is a synchronous ANSI-41 core network interworking structure diagram in an asynchronous mobile communication system, where reference numeral 210 is the asynchronous terminal, 220 is UTRAN which is an asynchronous wireless network, and 240 is connected to the UTRAN 220 which is the asynchronous wireless network. Core networks include synchronous ANSI-41 networks.
In order to be able to operate adaptively to these four structures, the synchronous terminal and the asynchronous terminal are different from the synchronous terminal and the asynchronous terminal used in the conventional synchronous / asynchronous mobile communication system. It has both CC (Call Control) and MM (Mobility Management) protocol entities for GSM-MAP core network services and CC and MM protocol entities for ANSI-41 core network services.
4 is a protocol hierarchy structure diagram of a conventional synchronous / asynchronous terminal.
First, FIG. 4A is a protocol hierarchy structure diagram of a synchronous terminal interworking with an ANSI-41 core network, where reference numeral 100 is a synchronous terminal, 110 is a synchronous wireless network, and 120 is a synchronous core connected to the synchronous wireless network 110. An ANSI-41 core network.
In this interworking structure, the synchronization terminal 100 is divided into a layer 3 (101), a layer 2 (106), a layer 1 (107), and the layer 3 (101) is a sync CC (102), a sync MM (103), Both asynchronous CC 104 and asynchronous MM 105 are provided, and the protocol of the CC / MM is selectively activated according to the network identifier (a code for identifying the type of network).
For example, since the currently connected network is the ANSI-41 core network 120, the protocols of the synchronous CC 102 and the synchronous MM 103 are activated to interface the message with the ANSI-41 core network 120.
Next, the synchronous wireless network 110 is composed of layer 3 (111), layer 2 (112), layer 1 (113), each layer of the synchronization terminal 100 and each layer of the ANSI-41 core network 120 Corresponds to the message by activating the protocol.
In addition, the ANSI-41 core network 120 is divided into layer 3 (121), layer 2 (124), and layer 1 (125), and layer 3 (121) is a synchronous CC (122) and a synchronous MM (123). ).
On the other hand, when the core network connected to the synchronous mobile communication system is an asynchronous core network as shown in Fig. 3b, it has the protocol structure as shown in Fig. 4b.
Here, reference numeral 100 denotes a synchronous terminal, reference numeral 110 denotes a synchronous radio network, and reference numeral 130 denotes an asynchronous core network.
In this interworking structure, the synchronization terminal 100 is divided into a layer 3 (101), a layer 2 (106), and a layer 1 (107), and the layer 3 (101) is a sync CC (102) and a sync MM (103). And asynchronous CC 104 and asynchronous MM 105, all of which selectively activate the protocol of the CC / MM according to the network identifier (a code for identifying the type of network).
For example, since the currently connected network is the GSM-MAP core network 130, the protocol of the asynchronous CC 104 and the asynchronous MM 105 is activated to interface the message with the GSM-MAP core network 130.
Next, the synchronous wireless network 110 is composed of layer 3 (111), layer 2 (112), layer 1 (113), each layer of the synchronization terminal 100 and each layer of the GSM-MAP core network 130 Corresponds to the message by activating the protocol.
In addition, the GSM-MAP core network 130 is divided into a NAS unit 131, a layer 3 134, a layer 2 135, and a layer 1 136, and the NAS unit 131 is an asynchronous CC ( 132, an asynchronous MM 133.
4C is a protocol hierarchy diagram of an asynchronous terminal interworking with the ANSI-41 core network, where reference numeral 210 is an asynchronous terminal, 220 is an UTRAN which is an asynchronous wireless network, and 230 is connected to the UTRAN 220 which is the asynchronous wireless network. Is an ANSI-41 core network.
In this protocol structure, the asynchronous terminal 210 includes all of the synchronous CC 211, the synchronous MM 212, the asynchronous CC 213, the asynchronous MM 214, and optionally the synchronous CC / MM or asynchronous CC / MM protocol Activate
For example, since the currently connected network is the ANSI-41 core network 230, the protocols of the synchronous CC 211 and the synchronous MM 212 are activated to interface the message with the ANSI-41 core network 230.
Next, FIG. 4D shows a protocol hierarchy diagram of an asynchronous terminal interworking with a GSM-MAP core network.
Here, reference numeral 210 denotes an asynchronous terminal, 220 denotes UTRAN which is an asynchronous wireless network, and 240 denotes a GSM-MAP core network which is connected to the UTRAN 220 which is the asynchronous wireless network.
In this protocol structure, the asynchronous terminal 210 includes all of the synchronous CC 211, the synchronous MM 212, the asynchronous CC 213, and the asynchronous MM 214, and optionally the synchronous CC / MM or the asynchronous CC / MM. Activate the protocol.
For example, since the currently connected network is the GSM-MAP core network 240, the protocols of the asynchronous CC 213 and the asynchronous MM 214 are activated to interface the message with the GSM-MAP core network 240.
As described above, since the IMT-2000 system synchronous / asynchronous system can have four interworking structures, the interface specification should be applied correspondingly.
That is, between the synchronous terminal and the synchronous wireless network is called Air-Interface, uses the same communication protocol as IS-2000, and between the synchronous wireless network and the ANSI-41 network, which is the core network, is called A-Interface, and 3G-IOS (3 Use communication protocols such as Generation Interoperability Specification.
On the other hand, when the IMT-2000 system is a structure in which the asynchronous communication method, that is, the asynchronous terminal and the asynchronous communication wireless network and the GSM-MAP core network interworking, the asynchronous communication wireless network and the asynchronous terminal have an RRC protocol entity. It interoperates with and exchanges messages used by RRC protocol entities. The RRC protocol entity is a protocol entity that manages and controls radio resources between an asynchronous communication wireless network and a terminal. The management and control of radio resources is a message defined in the RRC protocol entity. RRC Message "). If these RRC messages are classified by function, they are as follows.
1) RRC Message related to RRC Connection Management.
That is, it refers to RRC messages that are in charge of connection and release for the RRC protocol entity of the asynchronous communication wireless network and the terminal to be connected to each other, the basic operation used after the RRC connection is connected, and the function broadcasted to the terminal. .
2) RRC Message related to Radio Bearer.
That is, RRC messages that perform functions related to radio resources such as radio resource allocation and reconfiguration of radio resources between asynchronous communication radio networks and terminals.
3) RRC message related to RRC connection mobility.
That is, it refers to RRC messages that perform functions related to mobility information and handover.
4) RRC Message related to Measurement Control.
That is, RRC messages that perform functions related to the current configuration of the radio resources and the current state measurement and management of the radio resources in order to efficiently use the resources.
RRC messages that perform the functions described above include the following information elements according to the function or purpose of each RRC message.
1) Information elements related to core network information
2) UTRAN mobility information-related information elements
3) UE information related information elements
4) Information element related to Radio Bearer information
5) information element related to transport channel information
6) Information element related to physical channel information
7) Information element related to measurement information
Some or all of these information elements are included in each RRC message, and each information element includes many information fields. Among the many information fields in each information element, all or part of the information field is included depending on the function and use, and are interchanged between the wireless network and the terminal of the asynchronous communication method.
The wireless network and the asynchronous terminal of the asynchronous communication method are included in the RRC messages exchanged between the asynchronous wireless network and the terminal. Among the information elements transmitted and transmitted, the information elements related to the radio resource information are stored and used in the RRC protocol entity. Information elements related to core network information or information not related to radio resources are stored and used by CC and MM protocol entities existing in Layer3.
The RRC messages described above, the information elements included in each RRC message, and the information fields included in each information element are defined for asynchronous communication.
As the IMT-2000 system of the asynchronous communication method has a linkage structure between the asynchronous terminal, the wireless network of the asynchronous communication method, and the GSM-MAP core network, according to the network development situation, the asynchronous terminal has an asynchronous CC, MM protocol. The entity operates and the messages exchanged between the asynchronous radio network and the terminal use the RRC messages and other asynchronous messages described above, and the radio resource uses the radio resource used in the asynchronous communication method. Accordingly, in this interworking structure, the asynchronous communication wireless network and the terminal, as described above, among the information elements transmitted and included in the RRC message exchanged between the asynchronous wireless network and the terminal, the information elements related to the radio resource are Store and use in the RRC protocol entity, and information elements related to the core network or information not related to radio resources are stored and used in the CC, MM protocol entity in the upper layer.
In addition, in the case of the IMT-2000 system having such an interworking structure, the CC and MM protocol entities that perform functions such as call control and mobility management are also asynchronous, and asynchronous communication wireless network and terminal Since the RRC messages, information elements, and information fields exchanged between are defined according to the asynchronous communication method, they perform functions such as call control and mobility management without any problems. GSM-MAP core network can be interworked.
On the other hand, according to the results of the OHG requirement, if the asynchronous communication type IMT-2000 system has an interworking structure of the asynchronous terminal, the asynchronous communication type wireless network, and the ANSI-41 core network according to the network development situation, The CC and MM protocol entities operate, and the messages exchanged between the asynchronous radio network and the terminal use the RRC messages and other asynchronous messages described above, and the radio resource uses the radio resource used in the asynchronous communication method. do. In addition, the wireless network and the asynchronous terminal of the asynchronous communication method in such an interworking structure, as is well known, in the interworking structure of the IMT-2000 system having an interworking structure of the asynchronous terminal, the asynchronous communication wireless network and the GSM-MAP core network Interchange and process RRC Messages in the same way as used.
However, such an interlocking structure causes a problem. That is, the information fields included in the RRC messages exchanged between the asynchronous wireless communication network and the asynchronous terminal are not considered such an interworking structure.
In this interworking structure, in order for a synchronous CC and MM protocol entity operating in an asynchronous terminal to normally operate functions such as call control and mobility management, the core network is selected from among information elements included in RRC messages. The dependent information elements shall include the information fields used by the synchronous CC and MM protocol entities.
However, since the RRC messages, information elements included in the RRC messages, and information fields included in the information elements exchanged between the asynchronous communication wireless network and the asynchronous terminal are all defined for the asynchronous communication method, , Synchronous CC, MM protocol entities cannot use it. If the current information elements and information fields are used as it is, in the IMT-2000 system having such an interworking structure, the asynchronous terminal cannot normally interwork with the ANSI-41 core network.

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

Accordingly, the present invention has been proposed in order to solve various problems caused when the synchronous core network is connected and interworked in the conventional asynchronous mobile communication system.
It is an object of the present invention to smoothly transmit an RRC message between an asynchronous terminal and an asynchronous wireless network regardless of the type of core network to be connected (asynchronous core network GSM-MAP core network and synchronous core network ANSI-41 core network). The present invention provides a method for transmitting a radio resource control message in a mobile communication system.
The present invention for achieving the above object,
When the core network connected to the asynchronous wireless network in the asynchronous mobile communication system is the GSM-MAP network, which is an asynchronous core network, the core among several information elements included in the RRC messages exchanged between the asynchronous communication wireless network and the asynchronous terminal Information fields included in network-related information elements and information elements not related to radio resources use the RRC message used in the existing asynchronous system.
In addition, when the core network connected to the asynchronous wireless network in the asynchronous mobile communication system is the ANSI-41 network, which is a synchronous core network, the information related to the core network and the information elements not related to the radio resources in the asynchronous RRC message are synchronous new information. The radio resource related information elements that are changed to the field and do not depend on the core network are used to transmit RRC messages using existing asynchronous RRC messages, and the handoff measurement of asynchronous and synchronous systems and radio link measurement of synchronous systems are performed. For example, the radio resource information elements that depend on the core network generate a new RRC message including information used in the ANSI-41 core network.
In addition, if the IMT-2000 system has an interworking structure between an asynchronous terminal, an asynchronous communication method, and an ANSI-41 core network according to the network deployment situation, among the RRC messages exchanged between the asynchronous system and the asynchronous terminal, the core network RRC messages with related information elements, information elements not related to radio resources, and radio resource related information elements depending on the core network are interleaved by inserting an information field called RTT, which is a field for identifying the type of core network. Make it easy to use and replace.

delete

delete

delete

delete

delete

Hereinafter, described in detail with reference to the accompanying drawings, preferred embodiments of the present invention according to the technical spirit as described above.
According to the present invention, among information fields included in existing RRC messages used in an asynchronous system, information fields depending on the type of the core network, that is, an information field to be changed by the type of the core network, are assigned to the type of the core network. According to the modification, the normal operation is always performed regardless of the type of the core network to which the CC and MM protocol entities in the layer 3 of the asynchronous terminal are linked.
Among the RRC messages exchanged between the asynchronous communication wireless network and the asynchronous terminal, RRC messages including information fields depending on the type of the core network, and all information elements included in these RRC messages are as follows.
1) RRC Connection Request Message
This message is a message for requesting the RRC connection establishment to the radio network by the UE, and includes information elements such as UE information related information element, Radio Bearer information related information element, and Transport Channel information related information element.
2) RRC Connection Setup Message
This message is a response message of the RRC connection request message transmitted by the terminal to the wireless network, and information for RRC connection exists. For example, information elements such as UE information related information element, Radio Bearer information related information element, Transport Channel information related information element, and Physical Channel related information element are included.
3) RRC Connection Re-establishment Message
This message is a response message of an RRC connection reestablishment request message transmitted by the terminal to the wireless network, and information for RRC connection reestablishment exists. For example, information elements such as a UE information related information element, a transport channel information related information element, a core network information related information element, and a physical channel information related information element are included.
4) UE capability information message
This message is a message for transmitting the capability of the UE to the wireless network, and includes information elements such as core network information related information elements and UE information related information elements.
5) Direct Transfer Message
This message is a message for transmitting CC and MM protocol information through a radio interface, and includes information elements such as information elements related to core network information and information elements related to management information.
6) Paging (Paging Type2) Message
This message is a message for transmitting paging information transmitted to the terminal by the core network, and includes information elements such as core network information related information elements and UE information related information elements.
7) Security Mode Control Message
This message provides information on starting point of ciphering, ciphering key, etc. in relation to ciphering from wireless network to terminal.Information elements such as information element related to core network information, information element related to radio bearer information and information element related to UE Included.
8) Radio Bearer Setup Message
This message is for establishing a new radio bearer, and includes information about a core network information element, a UE information element, a radio bearer information element, a transport channel information element, and a physical channel ( Physical Channel) Information elements such as information-related information elements are included.
9) Cell Update Confirm Message
This message is a response message of a call update message transmitted by the terminal and is a message acknowledging the information of the new call selected by the terminal. The information element of the UE information, the information element of the UTRAN mobility information, and the information of the core network information. Information elements such as elements and information elements related to physical channel information are included.
10) URA Update Confirm Message
This message is a response message of an URA update message transmitted by the terminal, which is a message acknowledging the information of a new UTRAN registration area (URA) selected by the terminal. The information element of the UE information, the information element of the UTRAN mobility information, Information elements such as core network information related information elements are included.
11) RNTI Reallocation Message
This message is a message for assigning a new Radio Network Temporary Identifier (RNTI) to a terminal, which can identify the terminal, and includes information elements such as UE information-related information elements and core network information-related information elements.
12) Active Set Update Message
This message is a message for notifying information update of a radio link belonging to an active set among radio links between a terminal and a wireless network, and includes information elements such as UE information-related information elements and physical channel information-related information elements.
13) Handover Command Message
This message is a message in which the wireless network instructs the UE to start a handover, and includes information elements such as a UE information message, a core network information related information element, and a physical channel information related information element.
14) Inter-system Handover Command Message
This message is a message in which the wireless network commands the handover start from the terminal to a system other than the UTRAN, and includes information elements such as UE information related information elements and other information related information elements.
15) Inter-system Handover Failure Message
This message is a response message of an inter-system handover command message and indicates a failure of handover to another system, and includes information elements such as UE information-related information elements and other information-related information elements. Included.
When the IMT-2000 system of the asynchronous communication method is interworked with the asynchronous terminal, the asynchronous communication method, and the ANSI-41 core network according to the network development situation, the aforementioned RRC messages include information fields related to the ANSI-41 core network. In addition, the RRC message should be interfaced between the asynchronous terminal and the asynchronous radio network by including information fields necessary for proper operation of the synchronous CC and MM protocol entities.
To this end, in an asynchronous terminal, an information element to be changed according to the core network type among the RRC messages transmitted to the asynchronous wireless network should be appropriately changed and transmitted to the asynchronous wireless network, and the RRC message also transmitted to the asynchronous wireless network. The information element to be changed according to the type of the core network must be changed and transmitted to the asynchronous terminal.
In addition, the method of receiving and processing the RRC message should vary according to the type of core network with which the asynchronous terminal and the asynchronous wireless network are interworked.
Hereinafter, the above two transmission methods and two reception and processing methods will be described separately according to an asynchronous terminal and an asynchronous wireless network.
Example 1
5 is a flowchart illustrating a process in which an asynchronous terminal transmits an RRC message to an asynchronous wireless network in an asynchronous mobile communication system according to the present invention.
In step S111, the asynchronous terminal receives a system information message (System Information Message) transmitted from the wireless network of the asynchronous communication method through a broadcast channel (BCCH channel). The master system information block is found in the received message to obtain information on the core network type.
Next, in step S112, information about the acquired core network type is analyzed to determine whether the core network type is a GSM-MAP core network or an ANSI-41 core network.
If the interworking core network is a GSM-MAP core network as a result of this checking, in step S113, the asynchronous terminal operates the asynchronous CC, MM protocol entity in Layer 3.
In step S114, the asynchronous terminal selects an RRC message to be transmitted to the wireless network of the asynchronous communication method.
In addition, in step S115, the information elements of the selected RRC message are generated in a manner defined in the existing 3GPP Specification to generate an RRC message, and then transmitted to an asynchronous communication wireless network. If another RRC message is transmitted after the transmission, step S114 to step S115 are repeated.
When the RRC message selected above is an RRC connection request message and the interworking core network is a GSM-MAP core network, which is an asynchronous core network, the RRC connection request message format shown in FIG. 6A follows. The RRC connection request message format shown in FIG. 6A is the same as the RRC connection request message format used in the existing asynchronous method.
Among the information fields recorded in FIG. 6A, the Initial UE identity information field indicates an ID for identifying the terminal when the terminal requests an RRC connection. In the case of the asynchronous CC and MM protocol entities, the International Mobile Subscriber Identity (IMSI) and the International Mobile (EIEI) are used. Equipment Identity (P-TMSI), Packet Temporary Mobile Subscriber Identity (P-TMSI), Temporary Mobile Subscriber Identity (TMSI), etc. are alternative. RTT represents the type information of the core network.
In addition, when the RRC message selected above is an RRC connection reconfiguration message, and the interworking core network is a GSM-MAP core network, which is an asynchronous core network, the RRC message reconfiguration message format as shown in FIG. 7A follows. The RRC connection reconfiguration message format shown in FIG. 7A is identical to the RRC connection reconfiguration message format used in the existing asynchronous scheme.
The PLMN Identity information field of the information field recorded in FIG. 7A is an ID for identifying a Public Land Mobile Network (PLMN), and is composed of a Mobile Country Code (MCC) and a Mobile Network Code (MNC) information field. ID information for identifying whether the core network domain is IP or PSTN / ISDN is recorded, and the NAS System Info information field indicates information belonging to the NAS, and a location area code (LAC) and routing area code (RAC) information. Included. In addition, RTT represents type classification information of a core network.
In addition, when the RRC message selected above is a new UE capability message, and the interworking core network is a GSM-MAP core network which is an asynchronous core network, the UE capability message format as shown in FIG. 8A follows. The UE capability message format as shown in FIG. 8A is the same as the UE capability message format used in the existing asynchronous scheme.
The CN domain identity information field of the information field recorded in FIG. 8A includes an ID for distinguishing whether the core network domain is IP or PSTN / ISDN. In addition, RTT represents type classification information of a core network.
In addition, when the RRC message selected above is an RRC Direct Transfer message, and the interworking core network is a GSM-MAP core network that is an asynchronous core network, the RRC direct transfer message format shown in FIG. 9A follows. The RRC Direct Transfer message format shown in FIG. 9A is the same as the RRC Direct Transfer message format used in the existing asynchronous method.
The CN domain identity information field of the information field recorded in FIG. 9A includes ID information for distinguishing whether the core network domain is IP or PSTN / ISDN. In addition, RTT represents type classification information of a core network.
In addition, when the RRC message selected above is an inter-system handover failure message, and the interworking core network is a GSM-MAP core network which is an asynchronous core network, the handover failure between RRC systems as shown in FIG. Follow the message format. The RRC inter-system handover failure message format as shown in FIG. 10A is the same as the RRC inter-system handover failure message format used in the existing asynchronous scheme.
The System Type information field of the information field recorded in FIG. 10A includes information indicating the type and version of the corresponding system, and the Message information field records a message corresponding to a specification used in the system specified in the system type. Included information. In addition, RTT represents type classification information of a core network.
On the other hand, when the search results in step S112, if the interlocked core network is the ANSI-41 core network is a synchronous core network, in step S116, the asynchronous terminal operates the synchronous CC, MM protocol entity in Layer3.
In step S117, the asynchronous terminal selects an RRC message to be transmitted to the wireless network of the asynchronous communication method, and extracts unnecessary information elements from the existing RRC message selected in step S118.
Instead of the information element extracted in step S119, a new information element related to the ANSI-41 core network is inserted to generate an RRC message having a new structure, and the generated RRC message is transmitted to the asynchronous communication wireless network. After transmission, in the case of transmitting another RRC message, the operation from step S116 to step S119 is repeated.
In more detail,
If the interworking core network is an ANSI-41 core network and the RRC message selected above is an RRC connection request message, information related to ANSI-41 core network such as Initial UE Identity, synchronous CC and MM protocol entity may be included in the UE information related information element. An information field, etc., depending on the type of the core network is newly defined and included so that it can operate normally, and its message structure is shown in FIG. 6B.
Among the information fields recorded in FIG. 6B, when the UE requests an RRC connection, the Initial UE Identity information field records an ID for identifying the UE. In the case of the synchronous CC and MM protocol entities, the International Mobile Subscriber Identity (IMSI) and TMSI are used. (Temporary Mobile Subscriber Identity) or Electronic Serial Number (ESN). In addition, RTT represents type classification information of a core network. The other information elements are the same as the information elements recorded in the asynchronous RRC connection request message format.
In addition, when the interworking core network is an ANSI-41 core network and the RRC message selected above is an RRC connection reconfiguration message, information related to ANSI-41 core network such as Initial UE Identity, synchronous CC and MM may be included in the UE information related information element. The information field and the like depending on the type of the core network are newly defined and included so that the protocol entity can operate normally. The message structure is shown in FIG. 7B.
Among the information elements recorded in FIG. 7B, the CN information elements information elements include an NID information field for recording an ID for identifying a network within an IMT-2000 system range, an SID information field for recording an ID for distinguishing an IMT-2000 system, and a system level. Information field in which protocol revision level information supported by the system is recorded (the terminal must have P_REV supported by the system communicating with itself), and MIN_P_REV information field in which the minimum protocol revision level information for the terminal to access the system is recorded. (Systems supported by MIN_P_REV enable terminal access), and a Circuit Bearer Identifier information field is recorded in which a Circuit ID of a wired basic between the system and the core network is recorded. In addition, RTT represents type classification information of a core network. The other information elements are identical to those of the existing asynchronous RRC connection reconfiguration message format.
In addition, when the interworking core network is an ANSI-41 core network and the RRC message selected above is an RRC UE capability message, the information related to the ANSI-41 core network such as NID and SID or the synchronous CC and In order to operate the MM protocol entity normally, information fields and the like depending on the type of the core network are newly defined and the message structure thereof is illustrated in FIG. 8B.
Among the information elements recorded in FIG. 8B, the CN information elements information elements include an NID information field for recording an ID for identifying a network within an IMT-2000 system range, an SID information field for recording an ID for distinguishing an IMT-2000 system, and a system level. Information field in which protocol revision level information supported by the system is recorded (the terminal must have P_REV supported by the system communicating with itself), and MIN_P_REV information field in which the minimum protocol revision level information for the terminal to access the system is recorded. (Systems supported by MIN_P_REV enable terminal access), and a Circuit Bearer Identifier information field is recorded in which a Circuit ID of a wired basic between the system and the core network is recorded. In addition, RTT represents type classification information of a core network. The other information elements are the same as the information elements of the existing asynchronous RRC UE capability message format.
In addition, when the interworking core network is an ANSI-41 core network and the RRC message selected above is an RRC Direct Transfer Message, the information related to the ANSI-41 core network such as NID and SID or a synchronous CC and In order to operate the MM protocol entity normally, an information field and the like depending on the type of the core network are newly defined and the message structure thereof is shown in FIG. 9B.
Among the information elements recorded in FIG. 9B, the CN information elements information elements include an NID information field in which an ID for identifying a network within an IMT-2000 system range is recorded, an SID information field in which an ID for identifying an IMT-2000 system is recorded, and a system level. Information field in which protocol revision level information supported by the system is recorded (the terminal must have P_REV supported by the system communicating with itself), and MIN_P_REV information field in which the minimum protocol revision level information for the terminal to access the system is recorded. (Systems supported by MIN_P_REV enable terminal access), and a Circuit Bearer Identifier information field is recorded in which a Circuit ID of a wired basic between the system and the core network is recorded. In addition, RTT represents type classification information of a core network. The other information elements are identical to those of the existing asynchronous RRC Direct Transfer message format.
In addition, when the interworking core network is an ANSI-41 core network and the RRC message selected above is an inter-system handover failure message, the information related to the ANSI-41 core network or the synchronous CC and MM protocol entities may be included in the core network information-related information element. An information field, etc., depending on the type of the core network is newly defined and included so that it can operate normally, and its message structure is shown in FIG. 10B.
Other information elements of the information elements recorded in FIG. 10B include a system type information field and a message information field for intersystem handoff. The other information elements are identical to those of the existing asynchronous RRC inter-system handover failure message format.
Herein, the message s field of FIG. 10B is transmitted to an asynchronous terminal by processing parameters of the General Handoff Direction Message and information for synchronizing the MC system with a coding and formatting method used in the synchronization system. The contents are the same as in FIG. 10C.
Looking at the information recorded in the message field in more detail as follows.
PILOT_PN information field indicating the pilot PN sequence offset index of the target MC system, LC_STATE information field indicating the long code status of the target MC system, SYS_TIME information field indicating the system time of the target MC system, CDMA_FREQ indicating the frequency allocation of the target MC system Information field, a USE_TIME information field indicating whether an explicit operation time is described in this message, an ACTION_TIME information field indicating an operation time, an HDM_SEQ information field indicating a general handoff direction message sequence number, and a SEARCH_INCLUDED information field indicating a pilot search variable. SRCH_WIN_A information field indicating search window sizes for active and non-active sets, SRCH_WIN_N information field indicating search window sizes for neighboring sets, SRCH_WIN_R information field indicating search window sizes for remaining sets, and pilot T_ADD information field indicating detection threshold value, T_DROP information field indicating pilot drop threshold value, T_COMP information field indicating operating set-to-minimum set comparison threshold value, T_TDROP information field indicating drop timer value, adding / operating pilot to running set SOFT_SLOPE information field indicating slope on non-uniform criteria to subtract pilot from active set, ADD_INTERCEPT information field indicating blocking on non-uniform criterion to add pilot to active set, non-uniform to subtract pilot from active set DROP_INTERCEPT information field to indicate blocking in criteria, EXTRA_PARMS information field to indicate included extra variables, P_REV information field to indicate protocol update level, PACKET_ZONE_ID information field to indicate packet data service area identification, F to indicate frame offset RAME_OFFSET information field, PRIVATE_LCM information field indicating individual longcode mask identifier, RESET_L2 information field indicating reset verification procedure command, RESET_FPC information field indicating reset progress traffic channel output control, SERV_NEG_TYPE information field indicating service negotiation type, message sign ENCRYPT_MODE information field indicating notch mode, NOM_PWR_EXT information field indicating extended nominal transmission output, NOM_PWR information field indicating nominal transmission output offset, NUM_PREAMBLE information field indicating traffic channel preamble length, BAND_CLASS information field indicating band class, and allocation frequency A CDMA_FREQ information field indicating, a RETURN_IF_HANDOFF_FAIL information field indicating returning a failure flag, a COMPLETE_SEARCH information field indicating a flag for complete search, and a PERIODI flag indicating a periodic search for non-operating frequencies. C_SEARCH information field, SERVICE_INCLUDED information field indicating included service configuration parameter, SERV_CON_SEQ information field indicating connection sequence number, RECORD_TYPE information field indicating information recording type, RECORD_LEN information field indicating information recording length, Type_specific field information indicating special type field. Field, a SUP_CHAN_PARMS_INCLUDED information field indicating an indication containing supplementary channel parameters, a FOR_INCLUDED information field indicating an indication containing forward allocation information, a FOR_SUP_CONFIG information field indicating a forward supplementary code channel configuration, and NUM_FOR_SUP information indicating the number of forward supplementary code channels Field, a USE_FOR_DURATION information field indicating the use of the forward duration indication, a FOR_DURATION information field indicating the duration of the forward supplemental code channel assignment, and REV_INCLUDED information indicating the indication containing the reverse allocation information For example, a REV_DTX_DURATION information field indicating a reverse discontinuous transmission duration, a CLEAR_RETRY_DELAY information field indicating a retry delay indication deletion, a USE_REV_DURATION information field indicating a reverse duration indication usage, a REV_DURATION information field indicating a duration of a reverse supplemental code channel allocation, and a reverse direction NUM_REV_CODES information field indicating the number of supplementary code channels, USE_T_ADD_ABORT information field indicating the use of reverse T_ADD indications, REV_PARMS_INCLUDED information field indicating an indication with reverse allocation parameters, T_MULCHAN information field indicating supplemental channel request message pilot strength reporting offset, and reverse direction BEGIN_PREAMBLE information field indicating the number of preamble frames on the reverse supplemental code channel at the beginning of transmission on the supplemental code channel, and RESU indicating the number of preamble frames on the reverse supplemental code channel upon transmission return. ME_PREAMBLE information field, USE_PWR_CNTL_STEP information field indicating the power control step size, PWR_CNTL_STEP information field indicating the power control step size, NUM_PILOTS information field indicating the number of pilots included in the message, PILOT_PN information field indicating the pilot PN sequence offset index, and power PWR_COMB_IND information field indicating control signal combining indication, FOR_FUND_CODE_CHAN information field indicating forward basic channel, FOR_SUP_INCLUDED information field indicating forward supplementary code channel included, FOR_SUP_CHAN_REC Record information field indicating forward supplementary code channel record, forward forward information field FPC_SUBCHAN_GAIN information field indicating power control subchannel comparison gain, USE_PC_TIME information field indicating power control operation time usage instruction, and PC_ACTION_TIME information indicating power control subchannel gain operation time Baud field, RLGAIN_TRAFFIC_PILOT information field indicating gain adjustment of reverse traffic channel to gain of reverse pilot channel power for wireless configuration greater than 2, DEFAULT_RLAG information field indicating failure to use reverse link attribute gain, RECORD_TYPE information field indicating information record type, information RECORD_LEN information field indicating record length, Type_specific fields information field indicating special type field, RC_SYNC_ID_INCL information field indicating resource control synchronization identifier included in indicator, RC_SYNC_ID information field indicating resource control synchronization identifier, BLOB_INCL indicating indication contained in BLOB An information field and a BLOB information field indicating a bitized resource control block are included.
FIG. 10D is a view for explaining the content of FIG. 10C.
On the other hand, when the IMT-2000 system of the asynchronous communication method has an interworking structure of the asynchronous terminal, the asynchronous communication method and the GSM-MAP core network or the ANSI-41 core network according to the network development situation, the asynchronous communication method of the wireless network In the RRC messages interoperating between the and asynchronous terminals, a process of receiving and processing the RRC message from the wireless network is illustrated in FIG. 5B.
In step S211, the asynchronous terminal receives a system information message (System Information Message) from the wireless network of the asynchronous communication method. The master system information block is searched in the received message to obtain information on the core network type.
In step S212, it is checked whether the type of core network is a GSM-MAP core network or an ANSI-41 core network. As a result of this check, if the core network is the GSM-MAP core network, in step S213, the asynchronous terminal operates the asynchronous CC, MM protocol entity in Layer 3.
Next, in step S214, the asynchronous terminal receives the RRC message from the wireless network of the asynchronous communication method. The received RRC message includes information fields related to GSM-MAP core network information, information fields necessary for asynchronous CC, MM protocol entity to operate normally, and asynchronous radio resource information field.
Thereafter, in step S215, the RRC message is processed in the manner defined in the existing 3GPP specification.
On the other hand, as a result of confirming the core network type in step S212, if the core network connected to the asynchronous communication wireless network is an ANSI-41 core network, in step S216 the asynchronous terminal operates the synchronous CC, MM protocol entity in Layer 3 Let's do it.
In step S217, the asynchronous terminal receives the RRC message from the wireless network of the asynchronous communication method. The received RRC message includes information fields related to ANSI-41 core network information, information fields necessary for synchronous CC and MM protocol entities to operate normally, and asynchronous radio resource information fields.
Next, in step S218, the RRC message of the new structure is processed in the manner defined in the existing 3GPP Specification.
Example 2
On the other hand, the IMT-2000 system of the asynchronous communication method may have an interworking structure of the asynchronous terminal, the wireless network of the asynchronous communication method and the GSM-MAP core network or the ANSI-41 core network, which is an asynchronous core network, according to the network deployment situation. In the RRC messages interoperating between the wireless network and the asynchronous terminal of the scheme, the wireless network of the asynchronous communication scheme should change the structure of the RRC message transmitted to the asynchronous terminal according to the type of the core network to be interworked.
Hereinafter, a process of transmitting an RRC message or receiving an RRC message transmitted from the asynchronous terminal in an asynchronous communication wireless network will be described.
11A is a flowchart illustrating a process of transmitting an RRC message to an asynchronous terminal by a wireless network of an asynchronous communication method.
First, in step S311, the asynchronous communication wireless network exchanges messages from the interworking core network or receives core network related information through a hardware method (for example, using a dip switch).
In step S312, the type of core network is checked based on the received information. When the interworking core network is a GSM-MAP core network which is an asynchronous core network, the system guide message is transmitted to the asynchronous terminal in step S313.
Next, in step S314, the wireless network selects an RRC message to be transmitted to the asynchronous terminal, and in step S315, generates and transmits an RRC message in a manner defined in the current 3GPP specification.
The interworking core network is a GSM-MAP network, and the process of transmitting an RRC message from the wireless network to the asynchronous terminal will be described in more detail as follows.
If the RRC message selected above is an RRC connection setup message and the interworking core network is a GSM-MAP core network, which is an asynchronous core network, the RRC message follows the RRC connection setup message format as shown in FIG. 12A. The RRC connection setup message format shown in FIG. 12A is the same as the RRC connection setup message format used in the existing asynchronous method.
Among the information fields recorded in FIG. 12A, the Initial UE identity information field indicates an ID for identifying a terminal when the terminal requests an RRC connection. In the case of an asynchronous CC and MM protocol entity, an International Mobile Subscriber Identity (IMSI) and an International Mobile (IMEI) are used. Equipment Identity, P-TMSI (Packet Temporary Mobile Subscriber Identity), TMSI (Temporary Mobile Subscriber Identity) and the like. In addition, RTT represents type classification information of a core network.
Further, when the RRC message selected above is an RRC paging message (Paging Type 2) message, and the interworking core network is a GSM-MAP core network which is an asynchronous core network, the RRC message message format as shown in FIG. 13A follows. The RRC call message format shown in FIG. 13A is the same as the RRC call message format used in the existing asynchronous method.
In FIG. 13A, the CN domain identity information field records ID information identifying whether the core network domain is IP or PSTN / ISDN, and the Paging Record Type Identifier information field records ID information for identifying a calling terminal. The CC or MM protocol entity selects and uses one of IMSI, TMSI, and P-TMSI. In addition, RTT represents type classification information of a core network. In addition, RTT represents type classification information of a core network.
Further, when the RRC message selected above is an RRC secret mode control message, and the interworking core network is a GSM-MAP core network which is an asynchronous core network, the RRC secret mode control message format as shown in FIG. 14A follows. The RRC secret mode control message format shown in FIG. 14A is the same as the RRC secret mode control message format used in the conventional asynchronous method.
In FIG. 14A, an ID for identifying whether the core network domain is IP or PSTN / ISDN is recorded in the CD domain identity information field. In addition, RTT represents type classification information of a core network.
In addition, when the RRC message selected above is an RRC radio basic setup message, and the interworking core network is a GSM-MAP core network which is an asynchronous core network, the RRC radio basic setup message format shown in FIG. 15A follows. The RRC radio basic setup message format shown in FIG. 15A is the same as the RRC radio basic message format used in the existing asynchronous method.
In FIG. 15A, the CN domain identity information field records an ID identifying whether the core network domain is IP or PSTN / ISDN, and the NAS Binding Info information field records connection information between the wired bearer and the wireless bearer. In addition, RTT represents type classification information of a core network. In addition, RTT represents type classification information of a core network. In addition, RTT represents type classification information of a core network.
Further, when the RRC message selected above is an RRC cell update confirmation message, and the interworking core network is a GSM-MAP core network which is an asynchronous core network, the RRC cell update confirmation message format shown in FIG. 16A follows. The RRC cell update confirmation message format shown in FIG. 16A is the same as the RRC cell update confirmation message format used in the existing asynchronous method.
In FIG. 16A, the PLMN Identity information field is a field in which an ID for identifying a Public Land Mobile Network (PLMN) is recorded. The PLMN Identity information field includes a mobile country code (MCC), a mobile network code (MNC), and the like. In addition, the CN domain identity information field records an ID identifying whether the core network domain is IP or PSTN / ISDN, and the NAS System Info information field indicates information belonging to the NAS, and includes a location area code (LAC) and a routing area (RAC). Code). In addition, RTT represents type classification information of a core network.
Further, when the RRC message selected above is an RRC URA update confirmation message, and the interworking core network is a GSM-MAP core network which is an asynchronous core network, the RRC URA update confirmation message format shown in FIG. 17A follows. The RRC URA update confirmation message format shown in FIG. 17A is the same as the RRC URA update confirmation message format used in the existing asynchronous scheme.
In FIG. 17A, the PLMN Identity information field is a field in which an ID for identifying a Public Land Mobile Network (PLMN) is recorded, and includes a mobile country code (MCC), a mobile network code (MCC), and the like. In addition, the CN domain identity information field records an ID identifying whether the core network domain is IP or PSTN / ISDN, and the NAS System Info information field indicates information belonging to the NAS, and includes a location area code (LAC) and a routing area (RAC). Code). In addition, RTT represents type classification information of a core network.
In addition, when the RRC message selected above is an RRC RNTI reassignment message, and the interworking core network is a GSM-MAP core network, which is an asynchronous core network, the RRC RNTI reassignment message format shown in FIG. 18A follows. The RRC RNTI reassignment message format shown in FIG. 18A is the same as the RRC RNTI reassignment message format used in the existing asynchronous scheme.
In FIG. 18A, the PLMN Identity information field is a field in which an ID for identifying a Public Land Mobile Network (PLMN) is recorded. The PLMN Identity information field includes a mobile country code (MCC), a mobile network code (MNC), and the like. In addition, the CN domain identity information field records an ID identifying whether the core network domain is IP or PSTN / ISDN, and the NAS System Info information field indicates information belonging to the NAS, and includes a location area code (LAC) and a routing area (RAC). Code). In addition, RTT represents type classification information of a core network.
In addition, when the RRC message selected above is an RRC active set update message, and the interworking core network is a GSM-MAP core network which is an asynchronous core network, the RRC active set update message format shown in FIG. 19A follows. The RRC active set update message format shown in FIG. 19A is the same as the RRC active set update message format used in the existing asynchronous scheme.
In FIG. 19A, the PLMN Identity information field is a field in which an ID for identifying a Public Land Mobile Network (PLMN) is recorded, and includes a Mobile Country Code (MCC), a Mobile Network Code (MNC), and the like. In addition, the CN domain identity information field records an ID identifying whether the core network domain is IP or PSTN / ISDN, and the NAS System Info information field indicates information belonging to the NAS, and includes a location area code (LAC) and a routing area (RAC). Code). In addition, RTT represents type classification information of a core network.
In addition, when the RRC message selected above is an RRC handover command message and the interworking core network is a GSM-MAP core network which is an asynchronous core network, the RRC handover command message format shown in FIG. 20A follows. The RRC handover command message format shown in FIG. 20A is the same as the RRC handover command message format used in the existing asynchronous method.
In FIG. 20A, the PLMN Identity information field is a field in which an ID for identifying a Public Land Mobile Network (PLMN) is recorded. The PLMN Identity information field includes a mobile country code (MCC), a mobile network code (MNC), and the like. In addition, the CN domain identity information field records an ID identifying whether the core network domain is IP or PSTN / ISDN, and the NAS System Info information field indicates information belonging to the NAS, and includes a location area code (LAC) and a routing area (RAC). Code). In addition, RTT represents type classification information of a core network.
In addition, when the RRC message selected above is a handover command message between RRC systems, and the interworking core network is a GSM-MAP core network, which is an asynchronous core network, the RRC system handover command message format shown in FIG. 21A follows. The RRC inter-system handover command message format shown in FIG. 21A is the same as the RRC inter-system handover command message format used in the existing asynchronous scheme.
In FIG. 21A, the type and version of a corresponding system are recorded in the System Type information field, and a message corresponding to a specification used in a system specified in the system type is recorded in the message information field. In addition, RTT represents type classification information of a core network.
On the other hand, if the core network is determined in step S312 as a result of the core network is an ANSI-41 core network synchronous core network, in step S316 asynchronous wireless network is an asynchronous terminal to inform the system information message that the core network is ANSI-41 core network ( Insert into System Information Message and send to asynchronous terminal.
In step S317, an RRC message to be transmitted to an asynchronous terminal is selected. In step S318, an unnecessary information element is extracted from the selected RRC message. In step S319, new information elements related to the ANSI-41 core network are added to the selected RRC message. Insert and generate a new structure of the RRC message, and transmits the generated RRC message to the asynchronous terminal. After that, when the asynchronous communication wireless network needs to transmit another RRC message to the asynchronous terminal, the process returns to step S317 and repeats the following steps.
When the interworking core network is an ANSI-41 core network, a process of transmitting an RRC message to an asynchronous terminal by an asynchronous communication method will be described in more detail as follows.
First, when the interworking core network is an ANSI-41 core network and the RRC message selected above is an RRC connection setup message, information related to ANSI-41 core network such as Initial UE Identity, synchronous CC and MM may be included in the UE information related information element. The information field and the like depending on the type of the core network are newly defined and included so that the protocol entity can operate normally. The message structure is as shown in FIG. 12B.
Among the information fields recorded in FIG. 12B, when the UE requests an RRC connection, the Initial UE Identity information field records an ID for identifying the UE. In the case of the synchronous CC and MM protocol entities, the International Mobile Subscriber Identity (IMSI) and TMSI are used. (Temporary Mobile Subscriber Identity) or Electronic Serial Number (ESN). In addition, RTT represents type classification information of a core network. The other information elements are the same as the information elements recorded in the asynchronous RRC connection setup message format.
When the interworking core network is an ANSI-41 core network and the RRC message selected above is an RRC call message, NID, SID, and paging record according to the ANSI-41 core network are included in the core network information-related element. The ANSI-41 core network related information or information fields depending on the type of the core network are newly defined so that the synchronous CC and MM protocol entities can operate normally. The message structure is shown in FIG. 13B.
Among the information elements recorded in FIG. 13B, the CN information elements information elements include an NID information field in which an ID for identifying a network within an IMT-2000 system range is recorded, an SID information field in which an ID for identifying an IMT-2000 system is recorded, and a system level. Information field in which protocol revision level information supported by the system is recorded (the terminal must have P_REV supported by the system communicating with itself), and MIN_P_REV information field in which the minimum protocol revision level information for the terminal to access the system is recorded. (Systems supported by MIN_P_REV enable terminal access.) A Paging Record Type Identifier information field is included in which ID information identifying a calling terminal is recorded. In the call record type identification information field, one of IMSI, TMSI, and ESN is selected and used. In addition, RTT represents type classification information of a core network. The other information elements are the same as the information elements of the existing asynchronous RRC call message format.
When the interworking core network is an ANSI-41 core network and the RRC message selected above is an RRC secret mode control message, ANSI-41 core network related information such as NID and SID, or a synchronous CC may be included in the core network information related element. And a newly defined information field depending on the type of the core network so that the MM protocol entity can operate normally. The message structure is shown in FIG. 14B.
Among the information elements recorded in FIG. 14B, the CN information elements information elements include an NID information field in which an ID for identifying a network within an IMT-2000 system range is recorded, an SID information field in which an ID for identifying an IMT-2000 system is recorded, and a system level. Information field in which protocol revision level information supported by the system is recorded (the terminal must have P_REV supported by the system communicating with itself), and MIN_P_REV information field in which the minimum protocol revision level information for the terminal to access the system is recorded. (The system where the MIN_P_REV is supported enables the access of the terminal). In addition, RTT represents type classification information of a core network. The other information elements are the same as the information elements of the existing asynchronous RRC call message format.
In addition, when the interworking core network is an ANSI-41 core network and the RRC message selected above is an RRC radio basic setup message, information related to the ANSI-41 core network such as NID, SID, wired basic ID, etc. may be included in the core network information-related element. Alternatively, information fields depending on the type of the core network are newly defined and included so that the synchronous CC and MM protocol entities can operate normally. The message structure is shown in FIG. 15B.
Among the information elements recorded in FIG. 15B, the CN information elements information elements include an NID information field for recording an ID for identifying a network within an IMT-2000 system range, an SID information field for recording an ID for distinguishing an IMT-2000 system, and a system level. Information field in which protocol revision level information supported by the system is recorded (the terminal must have P_REV supported by the system communicating with itself), and MIN_P_REV information field in which the minimum protocol revision level information for the terminal to access the system is recorded. (Systems supported by MIN_P_REV enable terminal access), and a Circuit bearer Identifier information field in which a wired basic Circuit ID between the system and the core network is recorded. In addition, RTT represents type classification information of a core network. The other information elements are the same as the information elements of the existing asynchronous RRC radio basic setup message format.
In addition, when the interworking core network is an ANSI-41 core network and the RRC message selected above is an RRC cell update confirmation message, the information related to the ANSI-41 core network such as NID, SID, LAI or the like may be included in the core network information-related element. In order to allow the CC and MM protocol entities to operate normally, information fields and the like depending on the type of the core network are newly defined and the message structure thereof is shown in FIG. 16B.
Among the information elements recorded in FIG. 16B, the CN information elements information elements include an NID information field in which an ID for identifying a network within an IMT-2000 system range is recorded, an SID information field in which an ID for identifying an IMT-2000 system is recorded, and a system level. Information field in which protocol revision level information supported by the system is recorded (the terminal must have P_REV supported by the system communicating with itself), and MIN_P_REV information field in which the minimum protocol revision level information for the terminal to access the system is recorded. (Systems supported by MIN_P_REV enable terminal access), and a Circuit bearer Identifier information field in which a wired basic Circuit ID between the system and the core network is recorded. In addition, RTT represents type classification information of a core network. The other information elements are the same as the information elements of the existing asynchronous RRC cell update acknowledgment message format.
In addition, when the interworking core network is an ANSI-41 core network and the RRC message selected above is an RRC URA update confirmation message, the information related to the ANSI-41 core network such as NID, SID, LAI or the like may be included in the core network information related element. In order to allow the CC and MM protocol entities to operate normally, information fields and the like depending on the type of the core network are newly defined and the message structure thereof is illustrated in FIG. 17B.
Among the information elements recorded in FIG. 17B, the CN information elements information elements include an NID information field in which an ID for identifying a network within an IMT-2000 system range is recorded, an SID information field in which an ID for identifying an IMT-2000 system is recorded, and a system level. Information field in which protocol revision level information supported by the system is recorded (the terminal must have P_REV supported by the system communicating with itself), and MIN_P_REV information field in which the minimum protocol revision level information for the terminal to access the system is recorded. (Systems supported by MIN_P_REV enable terminal access), and a Circuit bearer Identifier information field in which a wired basic Circuit ID between the system and the core network is recorded. In addition, RTT represents type classification information of a core network. The other information elements are identical to those of the existing asynchronous RRC URA update confirmation message format.
In addition, when the interworking core network is an ANSI-41 core network and the RRC message selected above is an RRC RNTI reassignment message, the information related to the ANSI-41 core network such as NID, SID, LAI or the like may be included in the core network information-related element. In order to allow the CC and MM protocol entities to operate normally, information fields and the like depending on the type of the core network are newly defined and the message structure thereof is shown in FIG. 18B.
Among the information elements recorded in FIG. 18B, the CN information elements information elements include an NID information field in which an ID for identifying a network within an IMT-2000 system range is recorded, an SID information field in which an ID for identifying an IMT-2000 system is recorded, and a system level. Information field in which protocol revision level information supported by the system is recorded (the terminal must have P_REV supported by the system communicating with itself), and MIN_P_REV information field in which the minimum protocol revision level information for the terminal to access the system is recorded. (Systems supported by MIN_P_REV enable terminal access), and a Circuit bearer Identifier information field in which a wired basic Circuit ID between the system and the core network is recorded. In addition, RTT represents type classification information of a core network. The other information elements are the same as the information elements of the existing asynchronous RRC RNTI reallocation message format.
In addition, when the interworking core network is an ANSI-41 core network and the RRC message selected above is an RRC active set update message, the information related to the ANSI-41 core network such as NID, SID, LAI or the like may be included in the core network information-related element. In order to allow the CC and MM protocol entities to operate normally, information fields and the like depending on the type of the core network are newly defined and the message structure thereof is illustrated in FIG. 19B.
Among the information elements recorded in FIG. 19B, the CN information elements information elements include an NID information field in which an ID for identifying a network within an IMT-2000 system range is recorded, an SID information field in which an ID for identifying an IMT-2000 system is recorded, and a system level. Information field in which protocol revision level information supported by the system is recorded (the terminal must have P_REV supported by the system communicating with itself), and MIN_P_REV information field in which the minimum protocol revision level information for the terminal to access the system is recorded. (Systems supported by MIN_P_REV enable terminal access), and a Circuit bearer Identifier information field in which a wired basic Circuit ID between the system and the core network is recorded. In addition, RTT represents type classification information of a core network. The other information elements are identical to those of the existing asynchronous RRC active set update message format.
In addition, when the interworking core network is an ANSI-41 core network and the RRC message selected above is an RRC handover command message, the information related to the ANSI-41 core network such as NID, SID, LAI or the like may be included in the core network information-related element. In order to allow the CC and MM protocol entities to operate normally, information fields and the like depending on the type of the core network are newly defined and the message structure thereof is illustrated in FIG. 20B.
Among the information elements recorded in FIG. 20B, the CN information elements information elements include an NID information field in which an ID for identifying a network within an IMT-2000 system range is recorded, an SID information field in which an ID for identifying an IMT-2000 system is recorded, and a system level. Information field in which protocol revision level information supported by the system is recorded (the terminal must have P_REV supported by the system communicating with itself), and MIN_P_REV information field in which the minimum protocol revision level information for the terminal to access the system is recorded. (Systems supported by MIN_P_REV enable terminal access), and a Circuit bearer Identifier information field in which a wired basic Circuit ID between the system and the core network is recorded. In addition, RTT represents type classification information of a core network. The other information elements are the same as the information elements of the existing asynchronous RRC handover command message format.
If the interworking core network is an ANSI-41 core network and the RRC message selected above is a handover command message between RRC systems, Candidate Cell ID, Target Cell ID, CDMA Channel ID, and CDMA Frequency may be included in the core network information-related element. An ANSI-41 core network related information or an information field depending on the type of the core network is newly defined so that the synchronous CC and MM protocol entities can operate normally. The message structure is shown in FIG. 21B.
Among the information elements recorded in FIG. 21B, the Other information Elements information element includes a System Type information field in which the type and version of the system are recorded, and a Message information field which is information for synchronizing the parameters of the General Handoff Direction Message with the MC system. Included. Herein, the message information field indicates a PILOT_PN information field indicating a pilot PN sequence offset index of the target MC system, an LC_STATE information field indicating a long code state of the target MC system, and a system time of the target MC system, as shown in FIG. 21C. SYS_TIME information field indicating, CDMA_FREQ information field indicating frequency allocation of the target MC system, USE_TIME information field indicating whether the apparent operation time is described in this message, ACTION_TIME information field indicating the operation time, general handoff direction message sequence number HDM_SEQ information field indicating, SEARCH_INCLUDED information field indicating pilot search variable, SRCH_WIN_A information field indicating search window size for active and non-active sets, SRCH_WIN_N information field indicating search window size for neighboring sets, SRCH_WIN_R information field indicating color window size, T_ADD information field indicating pilot detection threshold, T_DROP information field indicating pilot drop threshold, T_COMP information field indicating operating set to minimum set comparison threshold, T_TDROP information field indicating drop timer value, A SOFT_SLOPE information field indicating the slope on a non-uniform basis to add a pilot to a running set or subtracting a pilot from a running set, an ADD_INTERCEPT information field indicating a block on a non-uniform basis to add a pilot to a running set, DROP_INTERCEPT information field indicating blocking on a non-uniform basis to subtract the pilot from the working set, EXTRA_PARMS information field indicating extra variables included, P_REV information field indicating protocol update level, packet data service area identification PACKET_ZONE_ID information field, FRAME_OFFSET information field indicating frame offset, PRIVATE_LCM information field indicating individual longcode mask identifier, RESET_L2 information field indicating reset check procedure command, RESET_FPC information field indicating reset progress traffic channel output control, service negotiation SERV_NEG_TYPE information field indicating type, ENCRYPT_MODE information field indicating message encoding mode, NOM_PWR_EXT information field indicating extended nominal transmission output, NOM_PWR information field indicating nominal transmission output offset, NUM_PREAMBLE information field indicating traffic channel preamble length, band class A BAND_CLASS information field representing the CDMA_FREQ information field indicating the assigned frequency, a RETURN_IF_HANDOFF_FAIL information field indicating the return of the failure flag, a COMPLETE_SEARCH information field indicating the flag to complete search, and a periodic PERIODIC_SEARCH information field indicating a flag for retrieval of non-operating frequency, SERVICE_INCLUDED information field indicating a contained service configuration parameter, SERV_CON_SEQ information field indicating a connection sequence number, RECORD_TYPE information field indicating an information recording type, RECORD_LEN information indicating an information recording length Field, Type_specific fields information field indicating special type field, SUP_CHAN_PARMS_INCLUDED information field indicating indication with supplementary channel parameters, FOR_INCLUDED information field indicating indication with forward assignment information, FOR_SUP_CONFIG information field indicating forward supplementary code channel configuration, NUM_FOR_SUP information field indicating the number of forward supplementary code channels, USE_FOR_DURATION information field indicating the use of forward duration indications, FOR_DURATION information field indicating the duration of forward supplementary code channel assignments, reverse REV_INCLUDED information field indicating an indication containing allocation information, a REV_DTX_DURATION information field indicating a reverse discontinuous transmission duration, a CLEAR_RETRY_DELAY information field indicating a retry delay indication deletion, a USE_REV_DURATION information field indicating a reverse duration indication usage, a reverse supplemental code channel assignment A REV_DURATION information field indicating the duration of the, a NUM_REV_CODES information field indicating the number of reverse supplemental code channels, a USE_T_ADD_ABORT information field indicating the use of the reverse T_ADD indication, a REV_PARMS_INCLUDED information field indicating the indication with the reverse assignment parameter, and a supplemental channel request message pilot T_MULCHAN information field indicating the strength reporting offset, BEGIN_PREAMBLE information field indicating the number of preamble frames on the reverse supplemental code channel at the beginning of transmission on the reverse supplemental code channel, and the backward complement upon transmission return. RESUME_PREAMBLE information field indicating the number of preamble frames on the full code channel, USE_PWR_CNTL_STEP information field indicating the power control step size, PWR_CNTL_STEP information field indicating the power control step size, NUM_PILOTS information field indicating the number of pilots included in the message, pilot PN A PILOT_PN information field indicating a sequence offset index, a PWR_COMB_IND information field indicating a power control signal combining indication, a FOR_FUND_CODE_CHAN information field indicating a forward basic channel, a FOR_SUP_INCLUDED information field indicating a forward supplementary code channel, and a FOR_SUP_CHAN_REC record indicating a forward supplementary code channel record FOR_SUP_CHAN_REC Record information field indicating information field, FPC_SUBCHAN_GAIN information field indicating forward power control subchannel comparison gain, USE_PC_TIME information field indicating power control operation time usage instruction, power PC_ACTION_TIME information field indicating subchannel gain operation time, RLGAIN_TRAFFIC_PILOT information field indicating gain adjustment of reverse traffic channel to reverse pilot channel power for wireless configuration greater than 2, DEFAULT_RLAG information field indicating that use of reverse link attribute gain has failed. RECORD_TYPE information field indicating record type, RECORD_LEN information field indicating information record length, Type_specific fields information field indicating special type field, RC_SYNC_ID_INCL information field indicating resource control synchronization identifier included in indicator, RC_SYNC_ID information field indicating resource control synchronization identifier , A BLOB_INCL information field indicating an indication included in the BLOB, and a BLOB information field indicating a bitized resource control block.
The other information elements are identical to those of the existing asynchronous RRC intersystem handover command message format.
Meanwhile, the process of receiving the RRC message transmitted from the asynchronous terminal by the asynchronous wireless network according to the type of the interworking core network is as shown in FIG. 11B.
First, in step S411, a message is exchanged from a core network interworking with a wireless network of an asynchronous communication method or the core network related information is received through a hardware method.
Next, in step S412, it is checked whether the type of the core network is a GSM-MAP core network or an ANSI-41 core network. If the core network to be linked is a GSM-MAP core network, the core network is asynchronous terminal in step S413. The GSM-MAP core network information is inserted into a system information message and transmitted to the asynchronous terminal.
In operation S414, the wireless network of the asynchronous communication method receives an RRC message from the asynchronous terminal. The RRC message received here includes information fields related to GSM-MAP core network information, information fields necessary for asynchronous CC and MM protocol entities to operate normally, and asynchronous radio resource information fields.
In addition, in step S415, the RRC message is processed in the manner defined in the existing 3GPP Specification.
In addition, when the core network to be linked as the result of the check in step S412 is an ANSI-41 core network, the asynchronous terminal by inserting the information that the core network ANSI-41 core network into a system information message (System Information Message) in step S416 To send.
In operation S417, the wireless network of the asynchronous communication method receives an RRC message from the asynchronous terminal. The RRC message received here includes information fields related to ANSI-41 core network information, information fields necessary for synchronous CC and MM protocol entities to operate normally, and asynchronous radio resource information fields.
Finally, in step S418, the received new structured RRC message is processed in the manner defined in the existing 3GPP Specification.

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

According to the above-described "method for transmitting a radio resource control message in the asynchronous communication system", the RRC message interface between the asynchronous terminal and the asynchronous radio network is possible even if the core network is connected to any of the GSM-MAP network and the ANSI-41 network. There is an advantage.
In addition, there is an advantage that the asynchronous system subscriber can talk to the subscriber of the synchronous ANSI-41 network or other network by the above effects.

delete

Claims (32)

A method of transmitting a radio resource control (RRC) message between an asynchronous terminal and an asynchronous wireless network in an asynchronous mobile communication system, When the asynchronous terminal transmits an RRC message to the asynchronous wireless network, a) Analyzing the system guide message transmitted from the asynchronous wireless network to recognize the type of core network to be interlocked, b) if the recognized core network is a synchronous core network, generate an RRC message including synchronous core network related information depending on the type of core network; c) a first step of transmitting the generated RRC message to the asynchronous wireless network; When the asynchronous radio network transmits an RRC message to the asynchronous terminal, a) Recognizing the type of core network to be interlocked through message communication with the interlocking core network, b) if the recognized core network is a synchronous core network, generate an RRC message including synchronous core network related information depending on the type of core network; c) a method of transmitting a radio resource control message in an asynchronous mobile communication system, comprising the step of transmitting the generated RRC message to the asynchronous terminal. According to claim 1, The asynchronous terminal, if the interworking core network is an ANSI-41 core network and the RRC message to be transmitted to the asynchronous wireless network is an RRC connection request message, UE information related information elements such as Initial UE Identity, etc. ANSI-41 core network related information, information fields depending on the type of core network such that synchronous CC and MM protocol entities can operate normally (core network related information fields, information fields not related to radio resources, core network) And separately defining information fields related to radio resources depending on the type of the RRC connection request message, and generating the RRC connection request message and transmitting the generated RRC connection request message to the asynchronous wireless network. The method of claim 2, wherein the RRC connection request message is updated with an Initial UE Identity information field in which information corresponding to the UE requests an RRC connection is recorded, and the information field includes an ID for identifying a terminal and a synchronous CC and In the case of the MM protocol entity, one of an International Mobile Subscriber Identity (IMSI), a Temporary Mobile Subscriber Identity (TMSI), an Electronic Serial Number (ESN) is selectively recorded, and RTT information, which is information indicating a type of a core network, is recorded. And other information elements are recorded with the same information elements as those recorded in the asynchronous RRC connection request message format. The method of claim 1, wherein the asynchronous terminal, if the interworking core network is an ANSI-41 core network and the RRC message to be transmitted is an RRC connection reconfiguration message, ANSI-41 such as Initial UE Identity in the UE information related information element. Core field-related information, information fields depending on the type of core network (core network-related information fields, information fields not related to radio resources, type of core network) so that synchronous CC and MM protocol entities can operate normally. And generating information RRC connection reconfiguration messages by separately defining the information fields related to the dependent radio resources and transmitting the generated RRC connection reconfiguration message to the asynchronous wireless network. The system of claim 4, wherein the RRC connection reconfiguration message is supported by an NID information field in which an ID identifying a network within an IMT-2000 system range, an SID information field in which an ID identifying an IMT-2000 system is recorded, and supported at a system level. P_REV information field in which protocol revision level information is recorded (terminal must have P_REV supported by the system communicating with itself), and MIN_P_REV information field (MIN_P_REV) in which the minimum protocol revision level information for accessing the system by the terminal is recorded. Is supported by the terminal), the circuit bearer Identifier information field in which the circuit ID of the wired basic between the system and the core network is recorded is updated, and the RTT distinguishes the type of the core network. Information is recorded, and other information elements are the same as the information elements of the existing asynchronous RRC connection reconfiguration message format. A method for transmitting a radio resource control message in an asynchronous mobile communication system, characterized in that an element is recorded. According to claim 1, wherein the asynchronous terminal, if the interworking core network is an ANSI-41 core network and the RRC message to be transmitted is an RRC UE capability message, the core-network information-related information element ANSI- such as NID, SID 41 Core network related information or information fields depending on the type of core network (core network related information fields, information fields not related to radio resources, type of core network) so that synchronous CC and MM protocol entities can operate normally. And separately defining information fields related to a radio resource depending on the RRC UE capability message, and then transmitting the generated RRC UE capability message to the asynchronous radio network. The RRC UE capability message of claim 6, wherein the RRC UE capability message includes an NID information field for recording an ID for identifying a network within an IMT-2000 system range, an SID information field for recording an ID for distinguishing an IMT-2000 system, and a system level support. P_REV information field in which protocol revision level information is recorded (the terminal must have P_REV supported by the system communicating with itself), and MIN_P_REV information field (MIN_P_REV) in which the minimum protocol revision level information for the terminal to access the system is recorded. Is supported by the terminal), the circuit bearer Identifier information field in which the circuit ID of the wired basic between the system and the core network is recorded is updated, and the RTT information indicating the type of the core network is updated. And other information elements have the same information elements as those of the existing asynchronous RRC UE capability message format. Radio resource control message transmission method in an asynchronous mobile communication system, characterized in that the rock. The method according to claim 1, wherein the asynchronous terminal, when the interworking core network is an ANSI-41 core network and the RRC message to be transmitted is an RRC direct transfer message, includes an NID, ANSI-41 core network related information such as SID or information fields depending on the type of core network for the synchronous CC and MM protocol entities to operate normally (core network related information fields, information fields not related to radio resources). In the asynchronous mobile communication system, a method for transmitting a radio resource control message in asynchronous mobile communication system, characterized by separately defining information fields related to a radio resource depending on the type of the core network, generates an RRC direct transmission message and transmits the generated RRC direct transmission message. . 10. The system of claim 8, wherein the RRC direct transmission message supports an NID information field in which an ID for identifying a network within an IMT-2000 system range is recorded, an SID information field in which an ID for distinguishing an IMT-2000 system is recorded, and supported at a system level. P_REV information field in which protocol revision level information is recorded (the terminal must have P_REV supported by the system communicating with itself), and MIN_P_REV information field (MIN_P_REV) in which the minimum protocol revision level information for the terminal to access the system is recorded. Is supported by the terminal), the circuit bearer Identifier information field in which the circuit ID of the wired basic between the system and the core network is recorded is updated, and information identifying the path of the core network is updated. RTT information is recorded and other information elements are identical to those of the existing asynchronous RRC direct transmission message format. Radio resource control message transmission method in an asynchronous mobile communication system wherein a beam element record. The method of claim 1, wherein when the interworking core network is an ANSI-41 core network and the RRC message to be transmitted is a handover failure message between RRC systems, Candidate Cell ID, Target Cell ID, Target ANSI-41 core network related information such as Cell ID, CDMA Channel ID, CDMA Frequency or information fields depending on the type of core network so that synchronous CC and MM protocol entities can operate normally (core network related information fields, radio Information fields not related to resources and information fields related to radio resources depending on the type of the core network) are separately defined and a handover failure message between RRC systems is generated and transmitted to the asynchronous wireless network. A method for transmitting a radio resource control message in an asynchronous mobile communication system. (Correction) The method according to claim 10, The RRC intersystem handover failure message may be updated with an intersystem message information field including a system type information field indicating a system type and a message information field in which information about intersystem handover is recorded. A method for transmitting a radio resource control message in an asynchronous mobile communication system, wherein the same information element as that of the existing asynchronous system handover failure message format is recorded. According to claim 1, The asynchronous wireless network, if the interworking core network is an ANSI-41 core network and the RRC message to be transmitted is an RRC connection setup message, the UE-related information elements ANSI-41 such as Initial UE Identity. Core field-related information, information fields depending on the type of core network (core network-related information fields, information fields not related to radio resources, type of core network) so that synchronous CC and MM protocol entities can operate normally. Method for transmitting a radio resource control message in an asynchronous mobile communication system, characterized in that the information fields related to the radio resource (dependent on) is separately defined to generate an RRC connection setup message and then transmitted to the asynchronous terminal. The method of claim 12, wherein when the terminal requests an RRC connection, an ID for identifying the terminal is recorded.In the case of a synchronous CC and MM protocol entity, an International Mobile Subscriber Identity (IMSI), a Temporary Mobile Subscriber Identity (TMSI), and an ESN Initial UE Identity information field in which one of the Electronic Serial Numbers) is selected and recorded is updated, and RTT information, which is information for identifying the type of the core network, is recorded, and other information elements are recorded in the asynchronous RRC connection setup message format. A method for transmitting a radio resource control message in an asynchronous mobile communication system, characterized in that the same information element as the information element is recorded. According to claim 1, wherein the asynchronous wireless network, if the interworking core network is an ANSI-41 core network and the RRC message to be transmitted is an RRC call message, NID, SID, ANSI-41 core in the core network information-related elements ANSI-41 core network related information such as paging record according to the network or information fields depending on the type of core network so that synchronous CC and MM protocol entities can operate normally (core network related information fields, wireless In the asynchronous mobile communication system, an RRC call message is generated and transmitted to the asynchronous terminal by separately defining information fields not related to resources and information fields related to radio resources depending on the type of the core network. Radio resource control message transmission method. 15. The system of claim 14, wherein the RRC call message includes an NID information field in which an ID for identifying a network within an IMT-2000 system range is recorded, an SID information field in which an ID for identifying an IMT-2000 system is recorded, and supported at a system level. P_REV information field in which protocol revision level information is recorded (the terminal must have P_REV supported by the system communicating with itself), and MIN_P_REV information field in which the minimum protocol revision level information for accessing the system by the terminal is recorded (MIN_P_REV is Supported system enables the access of the terminal), Paging Record Type Identifier information field in which ID information for calling terminal is recorded is updated, RTT information which is information for identifying the type of core network is recorded, The other information element is characterized in that the same information element as that of the existing asynchronous RRC call message format is recorded. The radio resource control message transmission method in an asynchronous mobile communication system. According to claim 1, wherein the asynchronous wireless network, if the interworking core network is an ANSI-41 core network and the RRC message to be transmitted is an RRC secret mode control message, the core network information-related elements ANSI, such as NID, SID, etc. -41 core network related information, or information fields depending on the type of core network so that synchronous CC and MM protocol entities can operate normally (core network related information fields, information fields not related to radio resources, core network). And separately defining information fields related to a radio resource depending on the type of a radio resource control message, generating an RRC secret mode control message and transmitting the generated RRC secret mode control message to the asynchronous terminal. 17. The system of claim 16, wherein the RRC secret mode control message comprises: an NID information field in which an ID identifying a network within an IMT-2000 system range is recorded, an SID information field in which an ID identifying an IMT-2000 system is recorded, and at a system level. P_REV information field in which supported protocol revision level information is recorded (terminal must have P_REV supported by the system communicating with itself), and MIN_P_REV information field in which minimum protocol revision level information is recorded for the terminal to access the system. The system supporting MIN_P_REV enables access of the terminal), and RTT information, which is information for identifying the type of core network, is recorded, and other information elements are identical to those of the existing asynchronous RRC call message format. Method for transmitting a radio resource control message in an asynchronous mobile communication system, characterized in that the information element is recorded. According to claim 1, wherein the asynchronous wireless network, if the interworking core network is an ANSI-41 core network and the RRC message to be transmitted is an RRC radio basic setup message, NID, SID, wired basic to the element information related to the core network information. ANSI-41 core network-related information such as ID or information fields depending on the type of core network so that synchronous CC and MM protocol entities can operate normally (core network-related information fields, information fields not related to radio resources). In addition, the RRC radio basic setup message is generated by separately defining information fields related to radio resources depending on the type of the core network, and then transmitted to the asynchronous terminal. . 19. The system of claim 18, wherein the RRC radio basic setup message comprises: an NID information field in which an ID identifying a network within an IMT-2000 system range is recorded, an SID information field in which an ID identifying an IMT-2000 system is recorded, and at a system level. P_REV information field in which supported protocol revision level information is recorded (terminal must have P_REV supported by the system communicating with itself), and MIN_P_REV information field in which minimum protocol revision level information is recorded for the terminal to access the system. The system supporting MIN_P_REV enables terminal access), and the Circuit bearer Identifier information field in which the wire ID of the wired base between the system and the core network is recorded is updated, and the RTT information that identifies the type of the core network is updated. The other information elements are the same as the information elements of the existing asynchronous RRC radio basic setup message format. Asynchronous mobile communication system, a radio resource control message transmission method in according to claim is recorded. According to claim 1, The asynchronous wireless network, if the interworking core network is an ANSI-41 core network and the RRC message to be transmitted is an RRC cell update confirmation message, NID, SID, LAI, etc. ANSI-41 core network related information or information fields depending on the type of core network such that synchronous CC and MM protocol entities can operate normally (core network related information fields, information fields not related to radio resources, core And generating information RRC cell update acknowledgment message by separately defining information fields related to radio resources depending on the type of network and transmitting the generated RRC cell update confirmation message to the asynchronous terminal. 21. The system of claim 20, wherein the RRC cell update confirmation message comprises: an NID information field in which an ID identifying a network within an IMT-2000 system range is recorded, an SID information field in which an ID identifying an IMT-2000 system is recorded, and at a system level. P_REV information field in which supported protocol revision level information is recorded (terminal must have P_REV supported by the system communicating with itself), and MIN_P_REV information field in which minimum protocol revision level information is recorded for the terminal to access the system. The system supporting MIN_P_REV enables terminal access), and the Circuit bearer Identifier information field in which the wire ID of the wired base between the system and the core network is recorded is updated, and the RTT information that identifies the type of the core network is updated. The other information elements are identical to those in the existing asynchronous RRC cell update confirmation message format. Method for transmitting a radio resource control message in an asynchronous mobile communication system, characterized in that recorded. According to claim 1, wherein the asynchronous wireless network, if the interworking core network is an ANSI-41 core network and the RRC message to be transmitted is an RRC URA update confirmation message, NID, SID, LAI, etc. ANSI-41 core network related information or information fields depending on the type of core network such that synchronous CC and MM protocol entities can operate normally (core network related information fields, information fields not related to radio resources, core And separately defining information fields related to radio resources depending on the type of network, generating an RRC URA update confirmation message and transmitting the generated RRC URA update confirmation message to the asynchronous terminal. 23. The system of claim 22, wherein the RRC URA update confirmation message comprises: an NID information field in which an ID identifying a network within an IMT-2000 system range is recorded, an SID information field in which an ID identifying an IMT-2000 system is recorded, and at a system level. P_REV information field in which supported protocol revision level information is recorded (the terminal must have P_REV supported by the system communicating with it), and MIN_P_REV information field in which the minimum protocol revision level information is recorded for the terminal to access the system. The system supporting MIN_P_REV enables terminal access), and the Circuit bearer Identifier information field in which the wire ID of the wired base between the system and the core network is recorded is updated, and the RTT information that identifies the type of the core network is updated. And other information elements are identical to those in the existing asynchronous RRC URA update confirmation message format. Method for transmitting a radio resource control message in an asynchronous mobile communication system, characterized in that recorded. According to claim 1, wherein the asynchronous wireless network, if the interworking core network is an ANSI-41 core network and the RRC message to be transmitted is an RRC RNTI reassignment message, NID, SID, LAI, etc. ANSI-41 core network related information or information fields depending on the type of core network such that synchronous CC and MM protocol entities can operate normally (core network related information fields, information fields not related to radio resources, core And generating information RRC RNTI reassignment message by separately defining information fields related to radio resources depending on the type of network and transmitting the generated RRC RNTI reassignment message to the asynchronous terminal. 25. The system of claim 24, wherein the RRC RNTI reassignment message comprises: an NID information field in which an ID for identifying a network within an IMT-2000 system range is recorded; an SID information field in which an ID for identifying an IMT-2000 system is recorded; P_REV information field in which supported protocol revision level information is recorded (terminal must have P_REV supported by the system communicating with itself), and MIN_P_REV information field in which minimum protocol revision level information is recorded for the terminal to access the system. The system supporting MIN_P_REV enables terminal access), and the Circuit bearer Identifier information field in which the wire ID of the wired base between the system and the core network is recorded is updated, and the RTT information that identifies the type of the core network is updated. The other information elements are recorded with the same information elements as those of the existing asynchronous RRC RNTI reassignment message format. Method for transmitting a radio resource control message in an asynchronous mobile communication system, characterized in that the. According to claim 1, The asynchronous wireless network, if the interworking core network is an ANSI-41 core network and the RRC message selected above is an RRC active set update message, NID, SID, LAI in the core network information related elements. ANSI-41 core network related information or information fields depending on the type of core network so that synchronous CC and MM protocol entities can operate normally (core network related information fields, information fields not related to radio resources, And a separate information field related to a radio resource depending on the type of the core network to generate an RRC active set update message and transmit the generated RRC active update message to the asynchronous terminal. 27. The system of claim 26, wherein the RRC active set update message includes: an NID information field in which an ID for identifying a network within an IMT-2000 system range is recorded, an SID information field in which an ID for identifying an IMT-2000 system is recorded, and a system level. Information field in which protocol revision level information supported by the system is recorded (the terminal must have P_REV supported by the system communicating with itself), and MIN_P_REV information field in which the minimum protocol revision level information for the terminal to access the system is recorded. (Systems that support MIN_P_REV enable terminal access.) The Circuit bearer Identifier information field, which records the circuit ID of the wired baseline between the system and the core network, is updated, and the RTT information that identifies the type of the core network. And other information elements are identical to those of the existing asynchronous RRC active set update message format. Asynchronous mobile communication system, a radio resource control message transmission method in according to claim is recorded. According to claim 1, wherein the asynchronous wireless network, if the interworking core network is an ANSI-41 core network and the RRC message to be transmitted is an RRC handover command message, NID, SID, LAI, etc. ANSI-41 core network related information or information fields depending on the type of core network such that synchronous CC and MM protocol entities can operate normally (core network related information fields, information fields not related to radio resources, core And an RRC handover command message generated after separately defining information fields related to radio resources depending on the type of network, and transmitting the generated RRC handover command message to the asynchronous terminal. 29. The system of claim 28, wherein the RRC handover command message includes an NID information field in which an ID for identifying a network within an IMT-2000 system range is recorded, an SID information field in which an ID for identifying an IMT-2000 system is recorded, and a system level. P_REV information field in which supported protocol revision level information is recorded (terminal must have P_REV supported by the system communicating with itself), and MIN_P_REV information field in which minimum protocol revision level information is recorded for the terminal to access the system. The system supporting MIN_P_REV enables terminal access), and the Circuit bearer Identifier information field in which the wire ID is recorded between the system and the core network is updated, and the RTT information that identifies the type of the core network is updated. The other information element is the same information element as that of the existing asynchronous RRC handover command message format. Method of transmitting a radio resource control message in an asynchronous mobile communication system, characterized in that the recording. According to claim 1, The asynchronous wireless network, if the interworking core network is an ANSI-41 core network and the RRC message to be transmitted is an inter-system handover command message, Coredate information related elements Candidate Cell ID, Target ANSI-41 core network related information such as Cell ID, CDMA Channel ID, CDMA Frequency, etc. or information fields depending on the type of core network so that synchronous CC and MM protocol entities can operate normally (core network related information fields, radio Asynchronously characterized by separately defining information fields not related to resources and information fields related to radio resources depending on the type of the core network, to generate a handover command message between RRC systems, and to transmit them to the asynchronous terminal. A method for transmitting a radio resource control message in a mobile communication system. The system of claim 30, wherein the inter-system handover command message includes a system type information field in which the type and version of the corresponding system are recorded, a parameter of a general handoff direction message, and information for synchronizing the MC system with each other. The information field is updated, and RTT information, which is information for identifying the type of core network, is recorded, and other information elements are recorded with the same information element as that of the information format of a handover command message format between existing asynchronous RRC systems. A radio resource control message transmission method in an asynchronous mobile communication system. (Correction) The method according to claim 11 or 31, The message information field includes a PILOT_PN information field indicating a pilot PN sequence offset index of a target MC system, an LC_STATE information field indicating a long code state of a target MC system, a SYS_TIME information field indicating a system time of a target MC system, and a target MC system. CDMA_FREQ information field indicating the frequency allocation of USE, USE_TIME information field indicating whether an explicit operation time is described in this message, ACTION_TIME information field indicating the operation time, HDM_SEQ information field indicating a general handoff direction message sequence number, and pilot search A SEARCH_INCLUDED information field representing the variable, an SRCH_WIN_A information field representing the search window size for active and non-active sets, an SRCH_WIN_N information field representing the search window size for neighboring sets, and a search window size for the remaining sets SRCH_WIN_R information field, T_ADD information field indicating pilot detection threshold, T_DROP information field indicating pilot drop threshold, T_COMP information field indicating working set to minimum set comparison threshold, T_TDROP information field indicating drop timer value, file to working set SOFT_SLOPE information field indicating the slope on a non-uniform criterion for adding the lot or subtracting the pilot from the running set, ADD_INTERCEPT information field indicating the blocking on a non-uniform basis to add the pilot to the running set, the file from the working set DROP_INTERCEPT information field indicating blocking on a non-uniform basis to subtract the lot, EXTRA_PARMS information field indicating extra variables included, P_REV information field indicating protocol update level, PACKET_ZONE_ID information field indicating packet data service area identification, FRAME_OFFSET information field indicating frame offset, PRIVATE_LCM information field indicating individual longcode mask identifier, RESET_L2 information field indicating reset verification procedure command, RESET_FPC information field indicating reset progress traffic channel output control, SERV_NEG_TYPE information indicating service negotiation type Field, ENCRYPT_MODE information field indicating message encoding mode, NOM_PWR_EXT information field indicating extended nominal transmission output, NOM_PWR information field indicating nominal transmission output offset, NUM_PREAMBLE information field indicating traffic channel preamble length, BAND_CLASS information field indicating bandwidth class A CDMA_FREQ information field indicating the assigned frequency, a RETURN_IF_HANDOFF_FAIL information field indicating the return of the failure flag, a COMPLETE_SEARCH information field indicating the flag to complete search, and a periodic search for non-operating frequencies. PERIODIC_SEARCH information field representing a flag, SERVICE_INCLUDED information field representing an included service configuration parameter, SERV_CON_SEQ information field representing a connection sequence number, RECORD_TYPE information field representing an information recording type, RECORD_LEN information field representing an information recording length, and a special type field. Type_specific fields information field, a SUP_CHAN_PARMS_INCLUDED information field indicating an instruction with supplementary channel parameters, a FOR_INCLUDED information field indicating an instruction with forward assignment information, a FOR_SUP_CONFIG information field indicating a forward supplementary code channel configuration, and the number of forward supplementary code channels. NUM_FOR_SUP information field indicating, USE_FOR_DURATION information field indicating the use of forward duration indication, FOR_DURATION information field indicating the duration of forward supplementary code channel allocation, indication containing reverse allocation information REV_INCLUDED information field indicating, REV_DTX_DURATION information field indicating reverse discontinuous transmission duration, CLEAR_RETRY_DELAY information field indicating deleting retry delay indication, USE_REV_DURATION information field indicating using reverse duration indication, REV_DURATION information indicating the duration of reverse supplementary code channel allocation Field, a NUM_REV_CODES information field indicating the number of reverse supplemental code channels, a USE_T_ADD_ABORT information field indicating the use of a reverse T_ADD indication, a REV_PARMS_INCLUDED information field indicating a direction with a reverse assignment parameter, and a T_MULCHAN information indicating the supplemental channel request message pilot strength report offset Field, BEGIN_PREAMBLE information field indicating the number of preamble frames on the reverse supplemental code channel at the beginning of transmission on the reverse supplemental code channel, preamble on the reverse supplemental code channel upon return to transmission. RESUME_PREAMBLE information field indicating the number of frames, USE_PWR_CNTL_STEP information field indicating the power control step size, PWR_CNTL_STEP information field indicating the power control step size, NUM_PILOTS information field indicating the number of pilots included in the message, and pilot PN sequence offset index. FOR_SUP_CHAN_REC indicating a PILOT_PN information field, a PWR_COMB_IND information field indicating a power control signal combining indication, a FOR_FUND_CODE_CHAN information field indicating a forward basic channel, a FOR_SUP_INCLUDED information field indicating a forward supplementary code channel is included, and a FOR_SUP_CHAN_REC Record information field indicating a forward supplementary code channel record Record information field, FPC_SUBCHAN_GAIN information field indicating forward power control subchannel comparison gain, USE_PC_TIME information field indicating power control operation time usage indication, and power control subchannel gain operation PC_ACTION_TIME information field to indicate RLGAIN_TRAFFIC_PILOT information field to indicate gain adjustment of reverse traffic channel to reverse pilot channel power for wireless configuration greater than 2, DEFAULT_RLAG information field to indicate that use of reverse link attribute gain fails, RECORD_TYPE information to indicate information record type Field, RECORD_LEN information field indicating information record length, Type_specific fields information field indicating special type field, RC_SYNC_ID_INCL information field indicating resource control synchronization identifier included in indicator, RC_SYNC_ID information field indicating resource control synchronization identifier, indication contained in BLOB And a BLOB_INCL information field indicating a BLOB_INCL information field and a BLOB information field indicating a bitized resource control block.

Images