JP2006020339A - Mobile communication method and mobile communication system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide the mobile communication method and the mobile communication system which are applicable to a multimedia environment and suitable for transmission of various types of data. <P>SOLUTION: In the mobile communication method for communicating between a plurality of mobile terminals and a network, a personal identifier for identification is preliminarily assigned to the mobile terminals and the network tentatively assigns a tentative identifier as the identifier to the mobile terminals in the network. The network and the mobile terminals keep the personal identifier and the tentative identifier. The network detects discordance between the tentative identifier kept by oneself and the tentative identifier kept by the mobile terminal, and re-assigns the tentative identifier to the mobile terminal for which the discordance is detected. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a mobile communication method and a mobile communication system suitable for mobile communication, and more particularly to a mobile communication method and a mobile communication system suitable for multimedia and suitable for transmission of various data.

  Conventionally, mobile phones have been widely used, and TDMA (Time Division Multiple Access), FDMA (Frequency Division Multiple Access), etc. have been adopted as access methods, but in recent years, the frequency utilization efficiency is good and the transmission speed is high. CDMA (Code Division Multiple Access) having advantages such as being easy to change and being hard to be wiretapped is being adopted.

  However, since the conventional CDMA is constructed mainly for the purpose of voice transmission, there is a problem that its access method is not suitable for data communication. On the other hand, in the recent multimediaization, data to be transmitted is not limited to voice, but includes various data handled by a computer or the like.

  For this reason, in the next generation communication system, it is desired that the access between the mobile device and the network is suitable for transmission of various data.

  The present invention has been made in view of the above-described circumstances, and an object thereof is to provide a mobile communication method and a mobile communication system that are compatible with multimedia and suitable for transmission of various data.

According to the present invention, in a mobile communication method for performing communication between a plurality of mobile devices and a network, a personal identifier for identification is assigned in advance to each mobile device, and the network is temporarily connected to the mobile device in the area. An identifier is assigned as a temporary identifier, and the network and the mobile device hold the personal identifier and the temporary identifier, respectively, and the network holds the temporary identifier held by itself and the temporary device held by the mobile device. The mobile communication method is characterized in that it detects that the local identifiers do not match and reassigns the temporary identifier to the mobile devices that do not match.
According to the above-described invention, it is possible to provide a CDMA wireless communication method and a wireless communication system suitable for transmission of various data compatible with multimedia.

  The present invention provides a base station controller that communicates with a mobile station capable of diversity combining under the control of an exchange station via a plurality of radio base stations, and transmission information to be transmitted to the mobile station received from the exchange station The present invention provides a base station controller characterized by comprising a concealment processing means for performing concealment processing and generating concealment transmission information.

  Further, the present invention provides a base station controller that performs communication via a plurality of radio base stations with a mobile device capable of diversity combining under the control of a switching center, and transmits the confidential transmission information that has been concealed in the switching center. A base comprising: retransmission control information adding means for adding retransmission control information; and distribution means for distributing the confidential transmission information to which the retransmission control information is added to the plurality of radio base stations. A station control apparatus is provided.

  In addition, the present invention performs a concealment process on transmission information to be transmitted to a mobile station in an exchange that communicates with a mobile station capable of diversity combining via a plurality of radio base stations and a base station controller. The present invention provides an exchange station comprising a secret processing means for generating the secret transmission information.

  The present invention also provides a mobile communication system comprising a mobile device capable of diversity combining, a plurality of radio base stations, and a base station control device that performs communication via the radio base stations under the control of an exchange. The base station controller distributes the information to the plurality of radio base stations and conceals the information before distributing it when the information is transmitted from the exchange side to the mobile station side. The present invention provides a mobile communication system characterized by performing processing.

  The present invention also provides a mobile communication system comprising a mobile device capable of diversity combining, a plurality of radio base stations, and a base station control device that performs communication via the radio base stations under the control of an exchange. When the information is transmitted from the switching station side to the mobile station side, the switching station performs a concealment process on the information before distributing the information to the base station controller. A mobile communication system is provided.

  The present invention also provides a mobile communication system comprising a mobile device capable of diversity combining, a plurality of radio base stations, and a base station control device that performs communication via the radio base stations under the control of an exchange. And providing a second layer concealment processing means for performing concealment processing on information handled only in layers corresponding to the second layer and higher layers in the OSI reference model. is there.

  The present invention also provides a mobile communication system comprising a mobile device capable of diversity combining, a plurality of radio base stations, and a base station control device that performs communication via the radio base stations under the control of an exchange. In the OSI reference model, a third layer concealment processing means for performing concealment processing on information handled only in a layer corresponding to the third layer or higher in the OSI reference model, and concealment in a layer corresponding to the second layer in the OSI reference model The present invention provides a mobile communication system comprising a second layer mutual notification means for performing mutual notification of start.

  Furthermore, the present invention provides a mobile communication system comprising a mobile device capable of diversity combining, a plurality of radio base stations, and a base station control device that performs communication via the radio base stations under the control of an exchange. In the OSI reference model, in the layer corresponding to the second layer in the OSI reference model, the third layer concealment processing means for performing the concealment processing on the information handled only in the layer corresponding to the third layer or higher in the OSI reference model Retransmission control information adding means for adding retransmission control information to the information subjected to the confidential processing by the third layer confidential processing means, and the confidential transmission information with the retransmission control information added to the plurality of radio base stations The present invention provides a mobile communication system characterized by comprising distribution means for distributing data.

  According to another aspect of the present invention, there is provided a control method for a base station controller that performs communication via a plurality of radio base stations with a mobile station capable of diversity combining under the control of the switching center. The present invention provides a mobile communication system characterized by including a concealment processing step for performing concealment processing on transmission information to be transmitted and generating concealment transmission information.

  Furthermore, the present invention provides a control method for a base station control apparatus that performs communication via a plurality of radio base stations with a mobile station capable of diversity combining under the control of the switching center. A retransmission control information adding step for adding retransmission control information to the transmission information; and a distribution step for distributing the secret transmission information to which the retransmission control information is added to the plurality of radio base stations. A control method for the base station control apparatus is provided.

  Furthermore, the present invention provides a method for controlling an exchange that communicates with a mobile station capable of diversity combining via a plurality of radio base stations and a base station controller, and conceals transmission information to be transmitted to the mobile station. It is an object of the present invention to provide a control method for a switching center characterized by including a concealment processing step for performing processing to generate the concealment transmission information.

  The present invention also provides a mobile communication system comprising a mobile device capable of diversity combining, a plurality of radio base stations, and a base station control device that performs communication via the radio base stations under the control of an exchange. In the control method, when transmitting information from the exchange side to the mobile station side, the base station control device distributes the information to the plurality of radio base stations and converts the information into the information before distribution. The present invention provides a method for controlling a mobile communication system, characterized by comprising a step of performing a concealment process.

  Furthermore, the present invention provides a mobile communication system comprising a mobile device capable of diversity combining, a plurality of radio base stations, and a base station control device that performs communication via the radio base stations under the control of an exchange. In this control method, when information is transmitted from the exchange side to the mobile station side, the information is concealed before the information is delivered to the base station controller in the exchange. The present invention provides a control method for a mobile communication system characterized by being applied.

  The present invention also provides a mobile communication system comprising a mobile device capable of diversity combining, a plurality of radio base stations, and a base station control device that performs communication via the radio base stations under the control of an exchange. And a second layer concealment processing step for performing concealment processing on information handled only in layers corresponding to the second and higher layers in the OSI reference model. A method is provided.

  The present invention also provides a mobile communication system comprising a mobile device capable of diversity combining, a plurality of radio base stations, and a base station control device that performs communication via the radio base stations under the control of an exchange. In the control method, the third layer concealment processing step of performing concealment processing on information handled only in the layer corresponding to the third layer or higher in the OSI reference model, and the second layer in the OSI reference model And a second layer mutual notification step of performing mutual notification of the start of concealment in a layer. A method for controlling a mobile communication system is provided.

  The present invention controls a mobile communication system comprising a mobile device capable of diversity combining, a plurality of radio base stations, and a base station controller that performs communication via the radio base station under the control of an exchange. In the method, in a layer corresponding to the second layer in the OSI reference model, a third layer concealment processing step for performing a concealment process on information handled only in a layer corresponding to the third layer or higher layer in the OSI reference model A retransmission control information adding step for adding retransmission control information to the information subjected to the confidential processing by the third layer confidential processing step, and the confidential transmission information with the retransmission control information added to the plurality of radio base stations The present invention provides a method for controlling a mobile communication system, characterized by comprising a distribution step of distributing to a mobile communication system.

  According to each of the above inventions, it is possible to reliably perform diversity combining even in a mobile device that cannot simultaneously process a secret transmission signal and an unsecret transmission signal.

  Further, the present invention provides a mobile device that communicates with a network via a wireless line, wherein the decryption processing start timing for starting the decryption processing of the confidential reception signal is independent of the confidential processing start timing of the transmission signal. It is an object of the present invention to provide a mobile device including a decryption processing start timing setting means for setting a transmission signal in accordance with a confidential processing start timing of a network.

  In addition, the present invention further comprises decryption processing means for performing a secret decryption process on a secret received signal received from the network via the wireless line, and the decryption process start timing setting means sends a reception confidentiality start request from the network. Concealment request determination means for determining whether or not it has been received, and decryption processing instruction means for causing the decryption processing means to start decryption processing based on the timing of receiving the reception confidentiality start request based on the determination, The present invention provides a mobile device characterized by this.

  In addition, the present invention sets the start timing of the concealment process for performing concealment processing on the transmission signal, independently of the decryption start timing of the concealment reception signal, in a mobile device that communicates with the network via a wireless line. The present invention provides a mobile device characterized by comprising a secret processing start timing setting means.

  In addition, the present invention provides a transmission concealment start request unit that transmits a transmission concealment start request to the network via the wireless line, and a concealment processing unit that performs concealment processing on the transmission signal to generate a concealment transmission signal. And the concealment process start timing setting means includes a concealment process instruction means for starting concealment processing in the concealment processing means based on the timing at which the transmission concealment start request is transmitted. Is to provide.

  Further, the present invention provides a network-side control device that communicates with a mobile device via a wireless line, and the decryption processing start timing for starting the decryption processing of the confidential reception signal is independent of the confidential processing start timing of the transmission signal. Then, a network control apparatus is provided, characterized by comprising decoding processing start timing setting means for setting in correspondence with the transmission signal concealment processing start timing in the mobile device.

  In addition, the present invention further comprises decryption processing means for performing a secret decryption process on the secret received signal received from the mobile station via the radio line, and the decryption process start timing setting means receives a reception concealment start request from the network. And a decryption processing instruction means for causing the decryption processing means to start decryption processing based on the timing of receiving the reception confidentiality start request based on the determination. A network control device characterized by the above is provided.

  The present invention relates to a network-side control apparatus that performs communication with a mobile device via a wireless line, and the start timing of the concealment process for performing concealment processing on the transmission signal is independent of the start timing of decryption of the concealment reception signal. It is an object of the present invention to provide a network control device including a secret processing start timing setting means for setting.

  In addition, the present invention provides a transmission concealment start request means for transmitting a transmission concealment start request to the mobile device via the radio line, and a concealment process for concealing the transmission signal to generate a concealment transmission signal. And the concealment process start timing setting means includes a concealment processing instruction means for starting concealment processing in the concealment processing means based on the timing at which the transmission concealment start request is transmitted. A control device is provided.

  According to another aspect of the present invention, there is provided a mobile communication system that performs communication between a mobile device and a network via a wireless line, wherein the network transmits a confidentiality start request to the mobile device via the wireless line. A start request means, a first secret transmission signal generation means for generating a first secret transmission signal by performing a concealment process on a first transmission signal that is a transmission signal from the network to the mobile device after transmission of the secret start request; First secret transmission signal transmitting means for transmitting a first secret transmission signal to the mobile device, response determination means for determining whether or not a secret start response indicating acceptance of the secret start request from the mobile device is received, First decoding processing means for starting decoding of a second confidential transmission signal transmitted from the mobile device when the mobile device accepts the confidentiality start request based on the determination of the response determination means, and Transfer A request determination unit that determines whether or not the concealment start request has been received, and a concealment start response unit that transmits the concealment start response when accepting the concealment start request based on the determination of the request determination unit And a second decryption processing means for starting the decryption of the first secret transmission signal transmitted by the network when accepting the concealment start request, and a transmission signal from the mobile unit to the network after transmitting the concealment start response A second secret transmission signal generating means for generating a second secret transmission signal by performing a secret process on the second transmission signal, and a second secret transmission signal transmitting means for transmitting the second secret transmission signal to the network. The present invention provides a mobile communication system including the above-described features.

  Further, the present invention provides a method for controlling a mobile device that communicates with a network via a wireless line, wherein the decryption processing start timing for starting the decryption processing of the confidential reception signal is independent of the confidential processing start timing of the transmission signal. Thus, the present invention provides a mobile device control method comprising a decryption processing start timing setting step for setting the transmission signal in correspondence with the confidential processing start timing of the transmission signal.

  In addition, the present invention further includes a decryption processing step for performing a secret decryption process on a confidential reception signal received from the network via the wireless line, and the decryption processing start timing setting step receives a reception confidentiality start request from the network. A concealment request determination step for determining whether or not the received concealment request, and a decryption processing instruction step for starting the decryption processing in the decryption processing step based on the timing of receiving the reception concealment start request based on the determination, The present invention provides a control method for a mobile device.

  Further, the present invention provides a control method for a mobile device that communicates with a network via a wireless line, wherein the start timing of the concealment processing for concealing the transmission signal is independent of the start processing of the decryption processing of the concealment reception signal. Accordingly, the present invention provides a method for controlling a mobile device, comprising a concealment processing start timing setting step to be set.

  In addition, the present invention provides a transmission concealment start request step for transmitting a transmission concealment start request to the network via the wireless line, and a concealment processing step for generating a concealment transmission signal by performing concealment processing on the transmission signal. And the concealment processing start timing setting step includes a concealment processing instruction step for starting concealment processing in the concealment processing step based on the timing at which the transmission concealment start request is transmitted. The control method is provided.

  According to the present invention, in the control method of the network-side control device that performs communication with the mobile device via a wireless line, the decryption process start timing for starting the decryption process of the secret reception signal is set as the secret process start timing of the transmission signal. The present invention provides a control method for a network-side control device, comprising a decoding process start timing setting step that is set in correspondence with the transmission signal concealment process start timing in the mobile device.

  In addition, the present invention further includes a decryption processing step for performing a secret decryption process on the secret received signal received from the mobile station via the wireless line, and the decryption processing start timing setting step includes a request to start reception confidentiality from the network. And a decryption processing instruction step for starting decryption processing in the decryption processing step based on the timing at which the reception confidentiality start request is received based on the determination. The present invention provides a control method for a network-side control device characterized by the above.

  According to the present invention, in the control method of the network-side control device that performs communication with the mobile device via a wireless line, the start timing of the concealment process for performing the concealment process on the transmission signal is the start timing of the decryption process of the concealment reception signal. A network-side control device is provided that includes a concealment processing start timing setting step that is independently set.

  In addition, the present invention provides a transmission concealment start request step for transmitting a transmission concealment start request to the mobile device via the radio line, and a concealment process for concealing the transmission signal to generate a concealment transmission signal. And the concealment processing start timing setting step includes a concealment processing instruction step for starting concealment processing in the concealment processing step based on the timing at which the transmission concealment start request is transmitted. A control method for the side control device is provided.

  According to another aspect of the present invention, there is provided a control method for a mobile communication system that performs communication between a mobile device and a network via a wireless line. A transmission start request step for transmitting, and a first transmission transmission signal generation step for generating a first transmission transmission signal by performing a concealment process on a first transmission signal that is a transmission signal from the network to the mobile device after transmission of the connection start request. Determining whether the network has received a first secret transmission signal transmitting step for transmitting the first secret transmission signal to the mobile device and a secret start response for accepting the secret start request from the mobile device. And a first decryption for starting to decrypt the second confidential transmission signal transmitted from the mobile device when the mobile device accepts the confidentiality start request based on the determination in the response determination step. And when the mobile station accepts the concealment start request on the basis of the determination in the request determination step and whether or not the mobile station has received the concealment start request. A concealment start response step for transmitting a start response to the network side; and a second decryption processing step for starting decryption of the first concealment transmission signal transmitted by the network when the mobile device accepts the concealment start request; A second secret transmission signal generating step of generating a second secret transmission signal by subjecting a second transmission signal, which is a transmission signal to the network, from the mobile device after transmitting the secret start response; and the second secret transmission A control method for a mobile communication system, comprising: a second secret transmission signal transmission step of transmitting a signal from the mobile device side to the network.

  According to each of the above inventions, for simplification of the system, even when the network side does not have the function of simultaneously decoding both the secret signal and the unconfidential signal, the secret start timing is set on the mobile device side and the network side. There is no deviation, and communication can be reliably and smoothly performed between the mobile device and the network side.

  Further, the present invention provides a confidential processing notification means for notifying the network side of confidential processing specifying information for specifying one or a plurality of confidential processing that can be performed in a mobile device that communicates with a network via a wireless line. The present invention provides a mobile device characterized by comprising:

  In addition, according to the present invention, the concealment processing notifying unit notifies the network side of concealment key generation processing specific information for specifying concealment key generation processing that can be processed together with the concealment processing specification information. The present invention provides a mobile device characterized by comprising a key generation process notifying means.

  Further, the present invention provides a secret communication means for performing a concealment process corresponding to a concealment execution request notified from the network side and communicating with the network in a mobile device that communicates with the network via a wireless line. The present invention provides a mobile device characterized by being provided.

  In addition to this, the secret communication means generates the secret key generation means for generating the corresponding secret key based on the secret key generation specification notification for specifying the secret key generation processing notified from the network side, There is provided a mobile device comprising: a concealment processing means for performing the concealment process using the concealment key.

  Further, the present invention provides a network-side control device that communicates with a mobile device via a wireless line to specify one or a plurality of concealment processes that can be performed in the mobile device notified from the mobile device. Based on the process identification information, a concealment process determining means for determining a concealment process for actual communication, and a concealment execution request for requesting the mobile device to perform concealment using the determined concealment process The present invention provides a network-side control device comprising a confidential processing execution requesting means for notifying.

  In addition, the present invention is used when actually communicating based on secret key generation process specifying information specifying one or more secret key generation processes that can be processed by the mobile station notified from the mobile station. A secret key generation process selecting means for selecting a secret key generation process; and a secret key generation notification means for performing a secret key generation process notification for notifying the mobile device of the selected secret key generation process. A network-side control device characterized by the above is provided.

  According to each of the above inventions, it is possible to select a concealment process according to the degree of security requested by the mobile device side (mobile device or user) and perform concealment. Further, it is possible to select a concealment process in accordance with a multimedia service (voice, moving image) provided by the communication service on the mobile device side or the network side, and perform the concealment. Furthermore, when the mobile communication system is expanded in the future, it becomes easy to introduce a new concealment process even when it becomes necessary to enhance the concealment in consideration of new services. Furthermore, if a minimum common concealment process is supported between multiple networks, it is possible to perform concealed communication without having to consolidate all the concealment processes when roaming and In addition to the confidential processing, it is possible to execute an original confidential processing within the network.

  In the present invention, when a call originates or an incoming call occurs in a mobile station, when the mobile station can communicate by diversity handover, the call is triggered by the main branch and the mobile station by diversity handover. An access characterized in that a plurality of branches consisting of both sub-branches to be added for communication are set between the network and the mobile station, and the mobile station starts a diversity handover using the plurality of branches. A link control method is provided.

  Further, in the present invention, when a message including a setting request for a plurality of branches is received from the network when an access link is not set with the network, the plurality of branches are set with the network. A mobile station characterized by starting a diversity handover is provided.

  In addition, the present invention provides that when a mobile station is capable of performing communication by diversity handover when a call is made or an incoming call occurs, the main branch and the mobile station are triggered by the call. The present invention provides a base station control apparatus characterized in that a plurality of branches, which are both sub-branches to be added for communication by handover, are set between a network and the mobile station.

  In addition, the present invention performs a main branch and intra-base station handover when a call is generated for a mobile station and the mobile station can perform communication by intra-base station diversity handover using one base station. The present invention provides a base station controller characterized by transmitting a message including a setting request for a plurality of branches consisting of both sub-branches to be added to the base station and the mobile station.

  In addition, the present invention provides an inter-base station inter-base station communication when the mobile station is capable of performing communication by diversity handover between base stations using a plurality of base stations when an outgoing call or incoming call occurs in the mobile station. It is an object of the present invention to provide a base station controller characterized by transmitting a message including a request to set a plurality of branches with the mobile station to each base station related to diversity handover.

  In addition, the present invention provides a base station control apparatus that can perform communication by intra-base station diversity handover when a mobile station makes a call or an incoming call. A base station characterized in that both a main branch and a sub-branch to be added to the main branch to perform diversity handover are set between the mobile station and the intra-base station diversity handover is started. It is to provide.

  According to each of the above inventions, when a call originates or an incoming call occurs in a mobile station, the mobile station can perform communication by diversity handover within a base station using one base station. Since the setting and the addition of sub-branches proceed as a series of procedures, and unnecessary signals are not transmitted / received, the transition to diversity handover can be performed efficiently, and other radio access links can be transferred. Interference can be reduced.

  In the present invention, when it is recognized that the mobile station is in a state where the branch should be switched and communication by diversity handover can be started after the branch is switched, the branch between the network and the mobile station is changed from the current one. The present invention provides a branch switching control method characterized by switching to a plurality of branches necessary for communication by the diversity handover and causing a mobile station to start diversity handover.

  Further, the present invention sets a branch between the network and the network in accordance with a command from the network when the branch is to be switched and communication using the diversity handover branch can be started after the branch is switched. The mobile station is characterized by switching from one to a plurality of branches for performing communication by the diversity handover and starting the diversity handover.

  In addition, the present invention allows the network and the branch between the mobile stations to be connected when the mobile station is in a state to switch branches and when it is recognized that communication by diversity handover can be started after branch switching. The present invention provides a base station controller characterized by switching from one to a plurality of branches for performing communication by diversity handover, and causing a mobile station to start diversity handover.

  In addition, the present invention is applicable when the mobile station is in a state in which branch switching is to be performed and it is recognized that communication by diversity handover within a base station using one base station can be started after branch switching. The present invention provides a base station controller characterized by transmitting a message including a branch switching command and a command indicating that a sub-branch should be added to perform diversity handover to a station and the mobile station.

  In addition, the present invention, when it is recognized that the mobile station is in a state where the branch should be switched, and communication by diversity handover between base stations using a plurality of base stations can be started after branch switching, A command indicating that a branch necessary for communication by diversity handover should be set is transmitted to each base station, and a message including a command for branch switching and a command indicating that a sub-branch should be added to perform diversity handover is transmitted to the mobile station. The present invention provides a base station control device characterized by transmitting to the base station.

  In addition, when the present invention receives a message from the base station controller that includes a branch switching command to the mobile station and a command indicating that a sub-branch should be added to perform diversity handover, according to each command in the message. The present invention provides a base station characterized in that a branch set for the mobile station is switched and a sub-branch is added to the mobile station to start an intra-base station diversity handover.

  According to each of the above inventions, when there is an opportunity for branch switching in the mobile station and it is recognized that a shift to the diversity handover is possible after the branch switching, the branch directly from the current branch to the branch corresponding to the communication by the diversity handover is performed. Since switching is made and useless signal transmission / reception is not performed, the transition to the diversity handover can be efficiently performed, and interference with other radio access links can be reduced.

  In the present invention, when a new call is generated when a mobile station capable of simultaneous communication with a plurality of calls is communicating, each communication between the new call and the existing call generated in the mobile station is performed. The branch control method is characterized in that the branch or the communication frequency band is controlled so that the branch configuration and the communication frequency band are the same.

  Further, the present invention provides a branch configuration for communication of an existing call generated in a mobile station when a new call is generated when a mobile station capable of simultaneous communication of a plurality of calls is communicating. A branch control method characterized by allocating the same branch configuration and communication frequency band as the communication frequency band to communication for a new call is provided.

  Further, according to the present invention, in a mobile station capable of simultaneous communication of a plurality of calls, when a new call is generated during communication, the existing call generated in the mobile station is instructed by a command from the network. The present invention provides a mobile station characterized by performing communication for a new call using the same branch configuration and communication frequency band as the branch configuration and communication frequency band for communication.

  In addition, the present invention can provide a new call and an existing call generated in the mobile station when a new call is generated when a mobile station capable of communicating with a plurality of calls is communicating. The present invention provides a base station control apparatus that controls a branch or a communication frequency band so that the branch configuration for communication and the communication frequency band are the same.

  Further, the present invention provides a branch configuration for communication of an existing call generated in a mobile station when a new call is generated when a mobile station capable of simultaneous communication of a plurality of calls is communicating. The present invention provides a base station controller characterized by assigning the same branch configuration and communication frequency band as the communication frequency band to communication for a new call.

  According to each of the above-described inventions, the same brachiinch configuration and communication band can be assigned to a plurality of calls including an existing call and a new call, so that the control burden for communication corresponding to each call can be reduced.

  The present invention relates to a branch configuration or communication frequency for communication of an existing call generated in a mobile station when a new call is generated when a mobile station capable of simultaneous communication of multiple calls is communicating. If the same branch configuration and communication frequency band as the band cannot be allocated for communication for a new call, another branch configuration or frequency band that can maintain the existing call and the new call is selected, and the existing call and new A branch control method is characterized in that a branch configuration or a communication frequency band for call communication is the selected branch configuration or communication frequency band.

  The present invention relates to a branch configuration and a communication frequency that are the same as a branch configuration or a communication frequency band for communication of an existing call when a new call is generated when a mobile station capable of simultaneous communication of multiple calls is communicating. If a bandwidth cannot be allocated for communication for a new call, other branch configurations or frequency bands that can maintain the existing call and the new call can be assigned to the communication of the existing call and the new call by a command from the network. A mobile station characterized by having a branch configuration or a communication frequency band is provided.

  The present invention relates to a branch configuration or communication frequency for communication of an existing call generated in a mobile station when a new call is generated when a mobile station capable of simultaneous communication of multiple calls is communicating. If the same branch configuration and communication frequency band as the band cannot be allocated for communication for a new call, another branch configuration or frequency band that can maintain the existing call and the new call is selected, and the existing call and new The present invention provides a base station control device characterized in that a branch configuration or communication frequency band for call communication is the selected branch configuration or communication frequency band.

  According to each of the above-described inventions, the same brachiinch configuration and communication band can be assigned to a plurality of calls including an existing call and a new call, so that the control burden for communication corresponding to each call can be reduced.

  The present invention selects a common branch configuration or communication frequency band for all calls that can maintain all calls in a mobile station when a handover trigger occurs in a mobile station that performs communication for multiple calls. The present invention provides a branch control method characterized by changing the branch configuration or communication frequency band for all calls to the selected branch configuration or communication frequency band.

  The present invention provides a new branch common to all calls in accordance with a command from the network, in accordance with a command from the network, when a handover trigger occurs during communication of a plurality of calls. A mobile station characterized by changing to a configuration or a communication frequency band is provided.

  The present invention selects a common branch configuration or communication frequency band for all calls that can maintain all calls in a mobile station when a handover trigger occurs in a mobile station that performs communication for multiple calls. The present invention provides a base station controller characterized by changing the branch configuration or communication frequency band for all calls to the selected branch configuration or communication frequency band.

  According to each of the above inventions, even when a handover is performed, the same Brachinchi configuration and communication band can be assigned to a plurality of calls in communication, so the control burden for communication corresponding to each call can be reduced. Can do.

  The present invention provides a case where there is no other branch configuration or communication frequency band capable of maintaining all calls in the mobile station when a handover trigger occurs in a mobile station performing communication of a plurality of calls. Select other branch configurations or communication frequency bands that can maintain multiple high-priority calls in the mobile station, disconnect all calls other than high-priority calls, and all branches of high-priority multiple calls The present invention provides a branch control method characterized in that the configuration or frequency band is changed to the selected branch configuration or frequency band.

  In addition, according to the present invention, when there is no branch configuration or communication frequency band capable of maintaining all calls in the case where an opportunity for handover occurs when performing communication of a plurality of calls, according to a command from the network, Calls other than a plurality of high priority calls among the plurality of calls are disconnected, and a branch configuration or frequency band of the plurality of high priority calls is changed to a branch configuration or frequency band selected by the network. A mobile station is provided.

  Further, the present invention provides a case where there is no other branch configuration or communication frequency band capable of maintaining all calls in the mobile station when a handover trigger occurs in a mobile station performing communication of multiple calls. And selecting other branch configurations or communication frequency bands capable of maintaining a plurality of high priority calls in the mobile station, and disconnecting all calls other than the plurality of high priority calls. The base station control apparatus is characterized in that the branch configuration or frequency band is changed to the selected branch configuration or frequency band.

  According to each of the above inventions, when a trigger for handover occurs, even if there is no branch configuration or communication frequency band that can maintain all calls in communication, high-priority calls Since communication can be maintained, communication with high priority can be maintained even in a situation where there is little available radio resource.

  The present invention also provides a method for setting a control channel in a mobile communication system in which a mobile station can perform a plurality of communications using a plurality of sets of radio resources, and the plurality of sets of radios used by the mobile station for a plurality of communications. The present invention provides a control channel setting method characterized by setting a control channel for transmission / reception of control information between a mobile station and a network for one of resources.

  According to the present invention, it is possible to reduce hardware related to transmission / reception of control information as compared with the case where all of a plurality of control channels are set in correspondence with a plurality of communications, and the control information transmission order is further reduced. Complex control such as adjustment between a plurality of control channels can be omitted.

  In addition, according to the present invention, a mobile station performs a plurality of communications using a plurality of sets of radio resources and transmits / receives control information to / from a network through a control channel set in one of the plurality of sets of radio resources. When the last communication using the radio resource with which the control channel is set is released, and there is still communication to be maintained by another set of radio resources at the time, The control channel set in the set of radio resources from which the last communication is released is switched to the control channel newly set in the set of other radio resources, and the control of the communication is continued. A control channel switching control method is provided.

  In addition, according to the present invention, a mobile station performs a plurality of communications using a plurality of sets of radio resources and transmits / receives control information to / from a network through a control channel set in one of the plurality of sets of radio resources. When the last communication using the radio resource with which the control channel is set is released, and there is still communication to be maintained by another set of radio resources at the time, The control channel set in the set of radio resources from which the last communication is released is switched to the control channel newly set in the set of other radio resources, and the control of the communication is continued. A base station control apparatus is provided.

According to each of the above inventions, when the control information is exchanged using a common control channel for a plurality of communications, the last communication using the radio resource in which the control channel is set is released, and When there remains communication to be maintained by another set of radio resources at that time, the control channel is switched. Therefore, after the switching time, it is possible to continue to exchange control information for communication using a new control channel.
In the present invention, a base station transmits broadcast information including a perch channel transmission power value and an uplink interference amount via a perch channel, and a mobile station receives the broadcast information from each neighboring base station and Detecting the reception level of the perch channel for each station, calculating the propagation loss between the mobile station and the base station from the reception level and the perch channel transmission power value in the broadcast information for each base station; Calculate the required uplink transmission power for each base station by calculation using the propagation loss calculated for each base station, the amount of uplink interference included in the broadcast information from each base station, and the base station required reception SIR, and wait When selecting the radio zone to be handed over or the radio zone to be handed over while passing, select the radio zone with the minimum required uplink transmission power and select the required uplink transmission. There is provided a method of controlling a radio zone and an uplink transmission power, characterized in that for controlling the uplink transmission power based on the power.

  The present invention also provides a base station comprising means for transmitting broadcast information including a perch channel transmission power value and an uplink interference amount via a perch channel.

  In addition, the present invention receives broadcast information including a perch channel transmission power value and an uplink interference amount from each neighboring base station via a perch channel, and sets the reception level of the perch channel for each base station. Detecting and calculating the propagation loss between the mobile station and the base station from the reception level and the perch channel transmission power value in the broadcast information for each base station, and calculating the propagation loss calculated for each base station The required uplink transmission power is calculated for each base station by calculation using the amount of uplink interference included in the broadcast information from each base station and the required base station reception SIR, and should be handed over during the radio zone to be awaited or while passing In selecting a radio zone, a radio zone with a minimum required uplink transmission power is selected, and an uplink transmission power is selected based on the required uplink transmission power. There is provided a mobile station, characterized in that for controlling the.

  According to each of the above inventions, it is possible to optimize the uplink transmission output in the mobile station even when the perch channel transmission power value differs between the base stations.

  In the present invention, when an additional branch is set between a mobile station and a network, the mobile station can start communication without waiting for confirmation of establishment of synchronization for all branches between the mobile station and the network. Therefore, the present invention provides a handover control method characterized in that a branch addition procedure is terminated when a new state is reached.

  In addition, the present invention provides a handover control method characterized in that the branch addition procedure is terminated by confirming synchronization establishment for only one of the branches set in the mobile station. It is.

  Further, according to the present invention, when a request to add a new branch to a branch set with the network is received from the network, the branch is added via the branch after the additional setting of the branch. When a signal is received, diversity combining using the branch and another branch is started, and a mobile station is provided.

  Further, in the present invention, when a request to add a new branch for performing a diversity handover within the base station is received from the base station controller for the branch set with the mobile station In addition, after the additional setting of the branch, when the signal is received through the branch, the base station diversity combining using the branch and another branch is started. is there. In addition, the present invention has received a request from the base station control device to add a new branch to the branch set up with the mobile station to perform diversity handover between base stations. In this case, after the additional setting of the branch, when the signal is received through the branch, the signal received through the branch is sent to a base station controller that performs inter-base station diversity combining. To provide a base station.

  Further, in the present invention, when a new branch is additionally set between the mobile station and the network, after a new branch addition setting request is output, confirmation of synchronization establishment for all branches between the mobile station and the network is confirmed. The base station control apparatus is characterized in that the branch addition procedure is terminated without waiting.

  In addition, in the present invention, when the branch additional setting request is output in order to perform inter-base station diversity handover, a signal is received via each branch necessary for inter-base station diversity handover. The present invention provides a base station controller characterized by starting inter-base station diversity combining.

  According to each of the above inventions, the branch addition procedure ends when the mobile station becomes communicable, so that the branch addition procedure can be quickly completed.

  The present invention relates to a mobile radio communication system capable of coexisting a plurality of lines in one carrier by a code multiplexing method, and at least an allocatable code resource having a predetermined bandwidth according to a required transmission rate. The present invention provides a mobile radio communication system comprising code resource allocating means for allocating a part to each line.

  In addition, the present invention is characterized by comprising a line allocating means for allocating, to the mobile station, the line to which at least a part of the allocable code resource is allocated according to the transmission rate capability of the mobile station. A wireless communication system is provided.

  Further, the present invention provides a mobile radio communication system capable of coexisting a plurality of lines in one carrier by a code multiplexing method, and a plurality of allocatable code resources having a predetermined bandwidth and independent from each other. There is an unused code resource having a bandwidth corresponding to the required transmission rate when allocating at least a part of the allocatable code resource to each line according to the required transmission rate. If not, a re-assignment means is provided for reassigning at least a part of the other allocatable code resources to the line to which at least a part of the one allocatable code resource is assigned. A mobile radio communication system is provided.

  In addition, the present invention provides an unused code having a bandwidth corresponding to the required transmission rate when allocating at least a part of the code resource to each line according to the required transmission rate. It is an object of the present invention to provide a mobile radio communication system characterized by comprising unused code resource discrimination means for discriminating whether or not a resource exists.

  In addition, the present invention assumes a reference code resource having a preset reference bandwidth at every preset predetermined timing, and is necessary for assigning one or more preset reference code resources to the line. And a re-allocation unit having a bandwidth necessary for allocating the reference code resource to the line based on the determination by the allocation determination unit. When there is no unused code resource, an unused code resource necessary for assigning the reference code resource to the line is secured for the line to which the one assignable code resource is assigned. The mobile radio communication is characterized in that another allocatable code resource is reassigned to the line until It is intended to provide a system.

  The present invention also provides an allocatable code having a predetermined bandwidth according to a required transmission rate in a radio base station apparatus capable of coexisting a plurality of lines in one radio carrier by a code multiplexing method. It is an object of the present invention to provide a radio base station apparatus comprising code resource allocation availability determination means for determining whether at least a part of resources can be allocated to each line.

  Furthermore, the present invention comprises a base station characterized by comprising a line allocating means for allocating to the mobile station the line to which at least a part of the allocatable code resource according to the transmission rate capability of the mobile station is allocated. A control device is provided.

  The present invention also provides an allocation method having a predetermined bandwidth according to a required transmission rate in a control method of a mobile radio communication system capable of coexisting a plurality of lines in one carrier by code multiplexing. The present invention provides a control method for a mobile radio communication system, comprising a code resource allocation step for allocating at least a part of possible code resources to each line.

  The present invention also provides a mobile radio communication that has a plurality of allocatable code resources that are independent from each other and have a predetermined bandwidth, and that allows a plurality of lines to coexist in one carrier by a code multiplexing scheme. In the system control method, there is a code resource having a code resource length corresponding to the required transmission rate when allocating at least a part of the code resource to each line according to the required transmission rate. A determination step for determining whether or not there is an unused code resource having a bandwidth corresponding to the required transmission rate based on the determination; A reassigning step of reassigning at least a part of the other allocatable code resources to the line that is assigned; Control method for a mobile radio communication system comprising the there is provided a.

  Also, the present invention provides a control method for a radio base station apparatus that allows a plurality of lines to coexist in one radio carrier by a code multiplexing method, and has a predetermined bandwidth according to a required transmission rate The present invention provides a control method for a radio base station apparatus, comprising a code resource assignability determination step for determining whether or not at least a part of an assignable code resource can be allocated to each line. .

  According to another aspect of the present invention, there is provided a control method for a base station control apparatus for controlling a radio base station apparatus. The present invention provides a control method for a base station control device, characterized in that it comprises a line assignment step for assigning to a base station.

  According to each of the above-described inventions, the frequency of code resource reassignment (relocation) to the line is minimized, and the connection delay is suppressed because the code resource is not relocated when a call occurs. Can do.

(1): Outline of the system (1.1): Introduction This system aims to improve the frequency utilization efficiency, flexibly handle multiple and high-speed signals, and realize high quality equivalent to a fixed network, etc. The present invention relates to a mobile communication system in which Wideband-Code Divison Multiple Access (W-CDMA) is applied to a radio access scheme.

(1.2): Overall Configuration of System First, the overall configuration of a W-CDMA mobile communication system according to an embodiment of the present invention will be described with reference to FIG. As shown in the figure, this system includes a mobile station apparatus (MS) and a radio base station system apparatus (BSS). The base station system device (BSS) is composed of a radio base station device (BTS) and an exchange (MCC), and is connected by a wired transmission path (HW).

On the other hand, as a mobile station apparatus (MS), there are a general-purpose mobile device, a small form device 1 connected to a personal computer, a small portable device 2 which is a so-called mobile phone, and the like.
The exchange (MCC) is connected to a personal computer via a fixed network PSTN, ISDN, telephone, or LAN.
With such a configuration, high quality voice, N-ISDN, packet, or modem signal can be transmitted.

(1.3): Abbreviations Next, explanation of abbreviations used in this specification is shown in FIG. Note that terms not specifically defined in this specification are ITU-T recommendation Q.3. It describes in conformity with 65.

(2.1): Overview of access interface Chapter 2 defines the access interface of the W-CDMA mobile communication system. As shown in FIG. 2, the access interface in this system includes a radio interface between a mobile station apparatus (MS) and a radio base station apparatus (BTS), and a radio base station apparatus (BTS) and an exchange ( BTS-MCC interface between MCC). Of course, the access method described below may be applied not only to W-CDMA but also to other devices.

This chapter includes the following items for the above interface specifications.
1) System provision service required for protocol specification, system capability specification 2) Service provision, system function configuration and control method for system capability support 3) Reference configuration for protocol specification, interface specification point 4) Radio interface Physical configuration, physical conditions 5) Signal transfer protocol in the radio interface (layer 2)
6) Control protocol in the radio interface (Layer 3)
7) Physical configuration of interface between base station and MCC, electrical condition 8) Information transmission protocol of interface between base station and MCC
(ATM layer, AAL type 2)
9) Signal transfer protocol (AAL) between base station and MCC interface
10) Base station-MCC interface control protocol (layer 3)
The control method and protocol specifications in this chapter are drafts of Recommendation Draft Q. FNA, Q. FIF, Q.E. FSA, Q. Complies with FSR.

(2.2): Features of the access interface Next, the features of the access interface will be described.
(2.2.1): Handover In a mobile communication network, a plurality of radio zones are provided, and a base station is provided in each radio zone. A radio channel called a perch channel is used for communication between each base station and a mobile station apparatus (MS), and a radio channel used for communication is selected from a plurality of perch channels having different frequency bands. Each perch channel is configured with a traffic channel TCH for transmitting communication contents. By the way, in mobile communication, when a mobile station apparatus (MS) moves across radio zones, the reception level of radio waves from the base station is lowered and communication quality is deteriorated. For this reason, it is necessary to change the communication partner so as to perform communication with a base station having a high reception level. In this case, the traffic channel TCH used by the mobile station apparatus (MS) is switched, which is called handover.

  By the way, when the mobile station apparatus (MS) performs handover, it is desirable to perform handover with the traffic channel TCH in the same frequency band during communication. For this reason, in the conventional mobile communication, the mobile station apparatus (MS) measures the reception level of radio waves from the surrounding zone for the perch channel having the same frequency band as the communication frequency band, and according to the reception level. A candidate for handover was selected. The handover candidate is notified to the network as a handover request.

  However, if a traffic channel TCH having the same frequency band as the communication frequency band is not set in the cell that is a candidate for handover in the surrounding zone, this is used for the mobile station apparatus (MS) that requested the handover. Cannot be assigned. For this reason, the network side needs to delete a handover candidate cell in which the traffic channel TCH is not set in the same frequency band as the frequency band in communication.

  Therefore, in this system, when the mobile station apparatus (MS) notifies the network of a handover request, a request is made by deleting in advance a cell in which a traffic channel TCH in the same frequency band as the communication frequency band is not set. I am doing so. Hereinafter, this point will be described.

  FIG. 259 shows an example of handover in this system. In the figure, the mobile station apparatus (MS) is located in zone 1 and is communicating in the frequency band f2. It is assumed that this mobile station apparatus (MS) has moved from zone 1 to zone 2. In this case, if the reception level of the frequency band f2 measured by the mobile station apparatus (MS) is higher in the order of zones 2, 3, and 4, the candidate indicated by the conventional handover request is the first candidate: zone 2, second. Candidate: zone 3, third candidate: zone 4. On the other hand, in this system, the setting status of the traffic channel TCH in the peripheral zone is broadcast as broadcast information (see 2.5.2.4.2.6), and using this, the mobile station apparatus (MS) detects a zone in which the traffic channel TCH is not set in the same frequency band as the communication frequency band and excludes it from the handover candidates. Therefore, the mobile station apparatus (MS) in this example notifies the network of a handover request with the first candidate: zone 3 and the second candidate: zone 4.

  As a mode of handover of this system, there are an additional handover, a switched handover, and a deletion handover as shown in Chapter 2.3.2.2.4, but the handover considering the traffic channel setting situation described above is an additional handover, Implemented with switched handover.

  Here, an example of operation until the mobile station apparatus (MS) makes a handover request will be described with reference to FIG. In the figure, MRRC, MRTR, RFTR and RRC are all functional entities provided in the mobile station apparatus (MS). The MRCR controls radio resources. MRTR performs concealment and output control, and measures the wireless environment, that is, the reception level from each zone. RFTR performs concealment and output control, and RRC controls radio resources.

  As shown in FIG. 37, MRRC indicates that CELL CONDITION MEASUREMENT req. Ind is output to MRTR at regular intervals. Upon receiving this, the MRTR measures the reception level from each zone, and the measurement result is sent to CELL CONDITION MEASUREMENT resq. Return to MRRC as conf. Next, the MRRC compares the reception level of the radio channel being communicated with the reception level of the radio channel from the surrounding zone. If the latter exceeds the former, the MRRC performs the following processing in order to perform handover.

  MRRC specifies zones in descending order of reception level for the frequency band being communicated, and excludes those for which no traffic channel TCH is set based on broadcast information. Thereafter, the MRRC identifies the remaining zone as a handover candidate, and instructs the NON SOFT HANDOVER EXECUTION TRIGER req. An ind is generated and notified to the TACF on the network side via the RRC.

  When a handover trigger is made by this notification to the TACF, the network side selects a handover destination from the handover candidates, notifies this to the mobile station apparatus (MS) side, and establishes a communication channel. ing. Thereby, on the network side, the mobile station apparatus (MS) recognizes the frequency band in communication, and performs complicated processing such as determining whether the traffic channel TCH is set in the handover candidate zone for the frequency band. Can be omitted. The operation after the handover trigger is shown in FIG.

(2.2.2): Switching of ACCH An associated control channel (ACCH) is a control channel that uses the same radio resources as the traffic channel TCH used for voice and data communication. By using this ACCH, control information can be exchanged between the mobile station (MS) and the base station (BS).

  By the way, there is a system that allows one mobile station apparatus (MS) to simultaneously communicate a plurality of calls, or a system that supports one communication using a plurality of radio physical channels. These systems are suitable for radio bearer service.

Even in this type of system, it is necessary to exchange control information between a mobile station (MS) and a base station (BS) that are communicating a plurality of calls.
In this case, an ACCH is set for each radio resource corresponding to a plurality of calls (that is, a radio resource used for each traffic channel TCH), and control information is exchanged via each ACCH. A method is also conceivable.

  However, when such a method is adopted, a lot of hardware is required for transmission / reception of control information, and complicated control is required for adjustment of transmission / reception of control signals between a plurality of ACCHs. is there.

  Therefore, in this system, when a mobile station performs a plurality of communications simultaneously using a plurality of sets of radio resources (a radio resource in which a plurality of traffic channels TCH are set), one radio among the plurality of sets of radio resources is used. A resource is selected, and a control channel for transmitting / receiving control information between the mobile station and the base station is set for the radio resource.

The ACCH setting method in this system will be described below.
First, FIG. 260 shows an example of a system in which a mobile station can perform a plurality of communications simultaneously. As shown in FIG. 260, communication corresponding to each call is performed between the mobile station apparatus (MS) and the base station (BS) via each traffic channel TCH corresponding to a plurality of calls.

  In such a case, in this system, an arbitrary one (for example, ACCH1 in the figure) is selected from a plurality of ACCHs corresponding to a plurality of traffic channels TCH, and is related to the mobile station apparatus (MS). All control signals can be transmitted and received on the ACCH.

  Therefore, according to the present system, it is possible to reduce hardware related to transmission / reception as compared with the case where all of a plurality of ACCHs corresponding to a plurality of traffic channels TCH are supported, and a plurality of control signal transmission orders. It is possible to omit complicated control such as adjustment between the ACCHs.

  By the way, in the case of the system as described above, when the radio resources using the ACCH are released as the individual communication is terminated and the traffic channel TCH is released, the ACCH is used for another call. There arises a problem that it is difficult to secure continuously. Alternatively, the same problem occurs when changing the transmission rate required for the ACCH.

  Therefore, in this system, a single mobile station apparatus (MS) allows communication of a plurality of calls simultaneously, shares the ACCH associated with each traffic channel TCH, and releases radio resources using the ACCH. Then, the ACCH is switched to another radio channel.

  FIG. 261 shows a configuration related to ACCH switching of this system as a functional entity. In this example, the mobile station apparatus (MS) performs two communications (hereinafter referred to as the first call communication and the second call communication) simultaneously using the traffic channels TCH1 and TCH2, and initially uses the ACCH1. It is assumed that control information is transmitted between the network and the mobile station apparatus (MS).

As shown in the figure, the mobile station apparatus (MS) is provided with TACAF, BCAF1, and BCAF2. Here, TACAF is a function entity for controlling access and instructing release, setting, etc. of ACCH. BCAF1 is a function entity that controls the radio bearer for communication of the first call, and BCAF2 is a function entity that controls the radio bearer for communication of the second call, both of which release and set the ACCH. Is.
Further, BCFr1 and BCFr2 are provided in the base station (BS), and TACF is provided in the network as the BSC function.

  Here, BCFr1 and BCFr2 are functional entities that control radio bearers for communication of the first call and the second call, respectively, and activate and release the ACCH. TACF is a functional entity that controls access and instructs activation, release, etc. of ACCH.

  Here, it is assumed that the communication of the first call using the traffic channel TCH1 ends and the communication of the second call using the traffic channel TCH2 is continued. The ACCH switching operation in this case will be described with reference to the sequence diagram shown in FIG.

  First, when communication of the first call using the traffic channel TCH1 is completed, the traffic channel TCH1 is released. When the TACF detects the release opportunity of the traffic channel TCH1, the ACCH continues to use the ACCH1 on the same physical channel as the traffic channel TCH1 and to continue using the traffic channel TCH2 after releasing the traffic channel TCH1. Detect that is needed.

  In this case, the TACF notifies the BCFr2 corresponding to the communication of the second call of an ACCH2 activation request accompanying the traffic channel TCH2. Thereby, BCFr2 activates ACCH2. Then, the BCFr2 returns a completion notification reporting that the activation of ACCH2 is completed to the TACF.

When the TACF receives the completion notification, the TACF notifies the TACAF of a request for switching to ACCH2.
Upon receipt of this switching request, TACAF notifies ACCF2 setting request to BCAF2, and BCAF2 sets ACCH2.

Next, TACAF notifies BCAF1 of a request to release ACCH1, and BCAF1 releases ACCH1.
After this, TACAF sends a switch completion notification reporting that the ACCH has been switched to the TACF.
Next, when the TACF issues a request for releasing ACCH1 to BCFr1, BCFr1 releases ACCH1. As a result, switching of the ACCH is completed, and control information is exchanged between the mobile station apparatus (MS) and the network side via the ACCH 2 that uses the same radio resource as the traffic channel TCH2.
The ACCH switching procedure will be described in detail in Chapter 2.4.3.5.7.

(2.2.3): Setting of Concealment In mobile communication, since communication is performed by an air interface, a signal is encrypted to prevent unauthorized interception and data tampering. Concealing (encrypting) a signal is called ciphering, and deciphering (decrypting) is called deciphering.

  By the way, when performing transmission / reception of a concealed signal (control signal), it is not possible to properly cancel concealment unless it is known from which timing concealment is started. In this case, if the secret release timing is incorrect, an unknown signal is acquired.

  Here, with reference to FIG. 751 and FIG. 752, the malfunction resulting from the timing of a secrecy start and secrecy cancellation is demonstrated.

FIG. 751 is an explanatory diagram showing an example of a secret execution state in the mobile communication system.
For example, when the mobile station MS is capable of diversity handover control, the base station controller RNC transmits the same transmission signal to the plurality of radio base stations BS1 to BS3 as shown in FIG. A case is assumed in which a (non-confidential signal) is distributed, a concealment process is executed in each of the radio base stations BS1 to BS3, and a concealed transmission signal (confidential signal) is transmitted to the mobile station MS.

  In this mobile communication system, as shown in FIG. 752, since the concealment process is executed in each radio base station BS, there is a possibility that the secrecy execution timing is shifted between the radio base stations BS1 to BS3.

  In this case, the secret start timing may be matched between the radio base stations BS, but it is actually difficult. More specifically, it is necessary for the base station controller RNC that controls the radio base stations BS1 to BS3 to negotiate with the radio base stations BS1 to BS3, respectively, and to completely match the start timing of the secrecy. However, it is difficult to match the start timing of the secrecy between the radio base stations BS.

  For this reason, as will be described later, the third layer of the OSI reference model terminates between the mobile station MS and the base station controller RNC or between the mobile station MS and the switching center MSC. When concealment is performed at the terminal MS and each radio base station BS), the transmission signals transmitted from the radio base stations BS1 to BS3 are the same transmission signal (secret transmission signal or unconfidential transmission). The transmission signal (confidential signal) that has been concealed by the radio base station BS2 and the radio base station BS3 and the radio base station BS1 are concealed as shown in FIG. Unprocessed transmission signals (unconfidential signals) are transmitted at the same time, and the confidential transmission signals and unconfidential transmission signals are processed in parallel from the standpoints of simplifying the device configuration and reducing manufacturing costs. So that the problem that it becomes impossible to perform the diversity combining occurs in the mobile station MS can not Rukoto.

  Therefore, this system is intended to enable diversity combining even in a mobile device that cannot process a confidential transmission signal and an unconfidential transmission signal at the same time. The timing is mutually notified between the mobile station apparatus (MS) and the exchange (MCC), so that deciphering is performed accurately and normal communication can be performed.

FIG. 64 shows a functional model for explaining the start of concealment.
As shown in FIG. 64, a mobile station MS (Mobile Station) is provided with UIMF, MCF, and TACAF. The UIMF holds information about mobile users and provides user authentication and confidentiality calculations. The MCF is an interface with a network for non-call related services. TACAF controls access to the mobile terminal such as call origination and paging detection.

  On the other hand, SACF, TACF, LRCF, and LRDF are provided on the network side. The SACF is an interface with a mobile terminal for non-call related services, and is connected to the MCF. Further, the TACF controls access to the mobile terminal such as execution of transmission and paging, and is connected to the TACAF. The LRCF performs mobility control and is connected to the TACF and the SACF. The LRDF stores various data related to mobility.

  In such a configuration, prior to mutual notification of ciphering start, user authentication (see 2.4.5.1) is performed according to the procedure shown in FIG. At this time, the network and the mobile terminal hold the authenticated secret keys in the UIMF and the LRDF, respectively, and deliver them to the TACAF / MCF and the TACF / SACF, respectively.

Thereafter, mutual notification of ciphering start timing is performed according to the sequence shown in FIG.
More specifically, first, from the LRCF on the network side, Start Ciphering req. ind is notified to TACAF / MCF on the mobile terminal side via TACF / SACF.

Thereby, the mobile terminal can detect that ciphering is applied to the signal transmitted from the network thereafter. For this reason, the TACF / SACF on the network side starts Start Ciphering req. When ind is transmitted, a signal to be transmitted thereafter is controlled to be concealed using a concealment execution type and a concealment key for specifying a predetermined concealment process.
When the mobile terminal receives a signal that has been concealed, the concealment release control of the received signal is performed by TACAF / MCF. The secret key is obtained from the UIMF prior to this process.
Thereby, concealment is ensured about the transmission signal (downlink signal) transmitted from the network side.

Next, the TACAF / MCF on the mobile terminal side starts Start Ciphering resq. Which instructs to conceal the signal transmitted from the mobile terminal side. conf is notified to the TACF / SACF on the network side.
Thereby, the network side can detect that ciphering is applied to the received signal thereafter. For this reason, the TACAF / MCF on the mobile terminal side starts Start Ciphering req. When conf is transmitted, a signal to be transmitted thereafter is concealed using a concealment execution type and a concealment key for specifying a predetermined concealment process. When the concealed signal is received on the network side, the concealment cancellation of the received signal is controlled by the TACF / SACF. Thereby, concealment is ensured for the transmission signal (uplink signal) transmitted from the mobile terminal side.

By the way, in the said description, although the outline of control of the secrecy start timing was demonstrated, it did not mention to which information a secrecy process is performed.
Therefore, in the following description, it will be examined which information is effective for the concealment process. This process can be performed independently of the control of the concealment start timing.

  An OSI reference model shown in FIG. 263 is known as an open system communication protocol. In this model, the standard from the physical connection to the standard necessary for business processing is divided into seven layers. Here, the first layer is called a physical layer and defines mechanical and electrical procedures and means for data transmission. For example, the shape of the socket is defined by this layer. The second layer is called a data link layer, in which data links are set, held, and released, and errors occurring in the physical layer are detected and recovered.

  The third layer is called a network layer, and connection between different networks is achieved by this layer. As a result, the upper layer can perform communication without worrying about what kind of network is being used. The fourth layer is called a transport layer and controls a transparent data flow between session entities. The fifth layer is called a session layer, and session connection is set and released by this layer. The sixth layer is called a presentation layer, and the data syntax is selected by this layer. The seventh layer is an application layer, and this layer identifies a communication partner and determines service quality. In the ITU, the subscriber line interface is defined in the third layer, and these correspond to the third to seventh layers of the OSI reference model.

Here, this system will be examined in more detail.
FIG. 753 shows a schematic configuration diagram of this system.
As shown in FIG. 753, the present system includes a mobile station MS, a plurality of radio base stations BS connected to the mobile station MS via radio lines, and a base station control for controlling the plurality of radio base stations BS. It comprises a device RNC and a switching center MSC for connecting the base station control device RNC to a fixed network.

In this case, it is assumed that the following conditions are satisfied.
(1) The mobile station MS and the base station controller RNC have a function of performing diversity combining / distribution.
(2) The first layer of the OSI reference model on the radio line side terminates between the mobile station MS and each radio base station BS.
(3) The second layer of the OSI reference model on the radio line side terminates between the mobile station MS and the base station controller RNC.
(4) The third layer of the OSI reference model in this system terminates between the mobile station MS and the base station controller RNC or between the mobile station MS and the switching center MSC.

Furthermore, the functional conditions of the second layer satisfy the following conditions.
(1) It has a second layer frame retransmission function.
(2) The third layer frame has a function of configuring the third layer frame so that the original order is obtained when the third layer frame extends over a plurality of second layer frames.
(3) When a secret signal and an unconfidential signal corresponding to the same information are received at the same time, there is no function capable of decoding both.

  Under the above conditions, concealment is performed in the second layer, and as shown in FIG. 754, the application of the switching center MSC issues a concealment start request (step S1), and the third layer (step S2) in this system, A case is assumed where a confidentiality start request is notified to the mobile station MS side via the second layer control unit (step S3) and the second layer concealment execution / cancellation unit of the base station controller RNC (step S4).

  Then, the network-side application notifies the mobile station MS side of the confidentiality start request (step S4), and then the second-layer confidentiality of the mobile station MS via the second-layer confidentiality implementation / cancellation unit of the base station controller RNC. A request for starting concealment is made to the implementation / cancellation unit (step S5), and thereafter, the application of the switching center MSC causes the second layer concealment implementation / cancellation unit of the base station controller RNC to perform concealment. Thereafter, a signal sent via the second layer concealment execution / cancellation unit becomes a concealment signal.

On the other hand, on the mobile station MS side, the application receives a concealment start request via the second layer concealment execution / cancellation unit, the second layer control unit, and the third layer (steps S6 to S8).
As a result, the application sets the second layer concealment execution / cancellation unit to cancel the concealment of the signal from the network side (step S9).

  Under the above conditions, when concealment is performed in the second layer, concealment is performed before the diversity handover (DHO) distribution to the radio base station BS on the network side. Even if the mobile station MS cannot process the secret transmission signal and the non-secret transmission signal at the same time without causing the impossible state, diversity combining can be surely performed.

  By the way, in the above-described embodiment, the second layer control unit sets the network side to the network side before the timing (step S9) for completing the secrecy release for the second layer concealment execution / release unit by the application of the mobile device MS is completed. When a retransmission request is made (steps S10 and S12) and the timing of signal retransmission (steps S13 and S14) corresponding to the retransmission request is advanced, the second layer concealment execution / cancellation unit releases the concealment In other words, the secret signal is transferred to the second layer as it is (step S15), and the second layer frame sequence number may be unknown.

  In other words, this is because the second layer (data link layer) executes the concealment in the second layer in spite of the detection and retransmission of errors occurring in the first layer (physical layer). This is due to the fact that Note that error detection is performed by adding a CRC to a signal.

As a result,
(1) The second layer frame retransmission function, which is the function of the second layer, cannot be used.
(2) The function constituting the third layer frame cannot be used so that the original order is obtained when the third layer frame extends over a plurality of frames.
This will cause a malfunction.

Therefore, in such an OSI reference model, the above-described mutual start notification (Start Ciphering req. Conf, Start Ciphering resq. Conf) is performed in the third and higher layers and not in the second layer. Is preferable.
For this reason, in this system, the information to be concealed is set to the third layer or higher, the second layer is not concealed, and the second layer performs mutual notification of the concealment start.

  Therefore, even if an error occurs in the first layer (physical layer) and the signal cannot be received correctly, the second layer retransmission control becomes independent even after concealment due to error detection and retransmission performed in the second layer. Done. By this retransmission, signals that have not arrived at the receiving side are received in the order of transmission, and therefore the receiving side can accurately recognize the timing of the start of secrecy.

  It should be noted that concealment can be executed in the second layer as long as the reliability of the first layer and the second layer can be ensured so that retransmission control is not performed in the second layer.

(2.2.4): Reassignment of TMUI In this system, an individual identifier (IMUI) for identifying each mobile station device (MS) is assigned in advance and held by each mobile station device (MS) and the network side. To do. Although it is possible to perform communication using this personal identifier (IMUI), in mobile communication, since communication is performed by an air interface, the personal identifier (IMUI) may be intercepted. In this case, there is a possibility that unauthorized communication using another person's personal identifier (IMUI) may be performed by the intercepted third party.

  Therefore, in this system, the network assigns a temporary mobile user identifier (TMUI) to the mobile station device (MS) in the area, separately from the personal identifier (IMUI), and assigns this to the mobile station device (MS). ). Note that the notification in this case is performed after concealment on the air interface so that the contents are not intercepted illegally.

  Here, the temporary mobile user identifier (TMUI) is assigned during the location registration procedure. If the location registration fails due to an air interface malfunction or the like, the location registration is performed again. Accordingly, there is no theoretical mismatch between the temporary mobile user identifier (TMUI) and the personal identifier (IMUI). However, when the mobile station device (MS) or the device storing the temporary mobile user identifier (TMUI) on the network side malfunctions, the temporary mobile user identifier (TMUI) and the personal identifier (IMUI) do not match. May occur.

  When such a contradiction occurs, it is necessary to avoid the contradiction and perform normal processing. Therefore, in this system, the following procedure is adopted between the network and the mobile station apparatus (MS).

  FIG. 264 shows a sequence between the network and the mobile station apparatus (MS) at the time of an incoming call. First, when receiving an incoming call, the network (in this case, the exchange) performs paging based on the other party's temporary mobile user identifier (TMUI). Paging is performed by reporting a temporary mobile user identifier (TMUI) and making a general call in the full control range of the exchange (MCC).

  As described above, the temporary mobile user identifier (TMUI) is assigned to each mobile station device (MS) in the area, and each mobile station device (MS) holds the temporary mobile user identifier (TMUI) by itself. ing. Therefore, when each mobile station apparatus (MS) receives the notified temporary mobile user identifier (TMUI), each mobile station apparatus (MS) is notified of the temporary mobile user identifier (TMUI) held by itself. It is determined whether or not. And, each mobile station apparatus (MS) is connected to Paging. The resp is returned to the exchange (MCC) (step S2).

  Next, the network performs user authentication (see 2.3.3.2.4.1). In this case, the network generates authentication information (random number) necessary for executing authentication of the mobile station apparatus (MS) that has accessed, and notifies the mobile station apparatus (MS) of this (step S3). When the mobile station apparatus (MS) receives the authentication information, the mobile station apparatus (MS) performs an operation using the authentication information (random number), and returns the authentication operation result obtained as a result (step S4). ). In this case, the authentication calculation is performed using an authentication key stored in advance in each mobile station apparatus (MS). The network side stores each authentication key in a predetermined storage device (for example, SDF) in association with the personal identifier (IMUI) and the temporary mobile user identifier (TMUI).

  Thereafter, the network reads the authentication key corresponding to the temporary mobile user identifier (TMUI) used in step S1 from the storage device. Then, an authentication calculation is performed using the read authentication key and the authentication information (random number) transmitted in step S3, and it is determined whether or not the calculation result matches the calculation result of the mobile station apparatus (MS) ( Step S5). If they match, the determination result is YES, the mobile station apparatus (MS) is authenticated as valid, and normal incoming call processing is performed.

  On the other hand, if the calculation results do not match, the determination result in step S5 is NO. In this case, the temporary mobile user identifier (TMUI) is not regular. The cause of the mismatch is that the responding mobile station apparatus (MS) is invalid, and the temporary mobile user identifier (TMUI) that is a legitimate user but managed by the network and the mobile station apparatus (MS) are The temporary mobile user identifier (TMUI) to be managed may not match. For this reason, in this system, it is confirmed whether or not the user is a legitimate user by using the personal identifier (IMUI).

  Specifically, first, a network (in this case, an exchange) makes an IMUI transmission request for instructing a transmission request for an individual identifier (IMUI) to the mobile station apparatus (MS) (step S6). Thereafter, the mobile station apparatus (MS) notifies the personal identifier (IMUI) held by itself (step S7).

  Next, when the network generates a random number again and notifies the mobile station apparatus (MS) as authentication information, the mobile station apparatus (MS) uses the authentication information and an authentication key held by itself to perform an authentication operation. The authentication calculation result obtained as a result is returned to the network as an authentication response (step S9).

  Thereafter, the network accesses the storage device based on the personal identifier (IMUI) acquired in step S7, and reads the authentication key corresponding to the personal identifier (IMUI). Then, an authentication calculation is performed using the read authentication key and the authentication information (random number) transmitted in step S8, and it is determined whether or not the calculation result matches the calculation result of the mobile station apparatus (MS) ( Step S10). If they do not match, the mobile station device (MS) is illegal, so the radio channel is disconnected and communication is terminated (step S12).

  On the other hand, if they match, the mobile station device (MS) is a legitimate user, so the exchange (MCC) reassigns the temporary mobile user identifier (TMUI). Therefore, the legitimate mobile station device (MS) can acquire the temporary mobile user identifier (TMUI) again. Thereby, the mobile station apparatus (MS) can perform normal communication in the future using the newly assigned temporary mobile user identifier (TMUI). Since the mobile station apparatus (MS) in this case is not a call target, the radio channel is disconnected and communication is terminated (step S12).

  As described above, according to the TMUI reassignment described above, when the temporary mobile user identifier (TMUI) held by the network and the temporary mobile user identifier (TMUI) held by the mobile station apparatus (MS) are different, the personal identifier When the network side recognizes that the user is a legitimate user based on (IMUI), the temporary mobile user identifier (TMUI) is reassigned, which causes a contradiction in the temporary mobile user identifier (TMUI). Even if it is a case, it can return to a normal state promptly. Note that the temporary mobile user identifier (TMUI) is also reassigned at the time of location registration and transmission as in the case of the incoming call described above. The temporary mobile user identifier (TMUI) is managed by SDF, which will be described later. This SDF can be provided, for example, in a location register arranged in the network and managing subscriber information.

(2.3): System Overview Next, an overview of this system will be described.
(2.3.1): Provided Service This system comprehensively provides communication of various information such as voice and data, and provides a plurality of bearer services simultaneously on one mobile terminal. For example, there are 64 kbit / s unrestricted digital bearer × 2. Also, instead of the conventional PDC mobile communication system, the wired section is converted to ATM and the wireless section is converted to CDMA. Thereby, high-quality and high-speed transmission can be performed.
FIG. 266 shown below shows the contents of the service. This system can be interconnected with PSTN, N-ISDN, PLML, B-ISDN, and IMT-2000.

(2.3.1.1): Bearer service This system provides the following bearer services: (1) Circuit switching mode a) 8 kbit / s voice bearer service This bearer service is intended to support voice services . The digital signal at point Um is standard G. 729. However, bit transparency is not guaranteed. In addition, this bearer service is not intended to support voice band data communication. FIG. 267 shows the contents of the 8 kbit / s voice bearer service.

b) 64 kbit / s unrestricted bearer service This bearer service provides information transfer of subrate multiplexed to 64 kbit / s without changing information between Um points. FIG. 267 shows the contents of the 64 kbit / s unrestricted bearer service.

c) Multiple rate unrestricted bearer service (64 kbit × n: n = 6, for example)
This bearer service provides information transfer of sub-rates multiplexed to 384 kbit / s without changing information between Um points. The contents of the multiple rate unrestricted bearer service are shown in FIG.

(2) Packet switching mode (FFS)
In this system, the bearer service can be provided in the packet line mode in addition to the above-described line mode bearer service.

(2.3.1.2): Mobility Service As a mobility portability service in this system, an personal identifier (IMUI: International Mobile User Identity) is adopted. The personal identifier (IMUI) is assigned in advance to identify each mobile terminal, and is held by the mobile station apparatus (MS) and the exchange (MCC). When the mobile station device (MS) moves across the wireless area, location registration, handover, etc. are performed using this personal identifier (IMUI). As a result, communication can be performed at an arbitrary place.

(2.3.1.3): Quality requirements This system has an error correction code and a retransmission function. This guarantees an average bit error rate of 10-3 in the network (including air) for voice calls, while the average bit error rate of 10-6 is similarly applied to information such as data communication and control information other than voice. Guarantee.

(2.3.2): System capability (2.3.2.1): System capability related to communication service (2.3.2.1.1.1): Origination Origination is based on an origination request from a user. This refers to a series of control procedures in which an MS accesses a network and sets up an access link between the network and the MS, a connection to the partner user, and the like necessary for communication with the partner user. This procedure is realized by a procedure such as SDCCH control, user ID Retrieval, authentication, start of secrecy, access link setting, etc. and mutual information transfer with the calling user, analysis procedure, and the like.

  In order to handle outgoing calls, the system has the following capabilities: First, it has the ability to establish SDCCH for notifying the network of the transmission of a mobile station apparatus (MS). This point will be described in detail in this chapter, SDCCH control.

The system also has the capability of establishing an association (Terminal Association) between the MS and the network. Specifically, the following capabilities are included.
a) Notifying the network of the transmission of the MS using the temporary mobile user identifier (TMUI), and starting the terminal association. In addition, the MS capability is notified from the MS to the network, and the network retains the MS capability and controls to accept a new call to the MS in the network when a new call is subsequently generated.
b) Ability to recognize a call request MS and transfer the information of the MS from the network database to the analysis and control functions in the network. (If the TMUI of the originating MS cannot be recognized on the network, the MS is queried for the mobile user identifier (IMUI) unique to the MS and the MS is recognized.)
c) User authentication control for confirming the validity of the MS based on the MS information is performed. This point will be described in detail in this chapter, user authentication.
d) Concealment control is performed to prevent interception and falsification of the control channel and information channel between the MS and the network. This point will be explained in detail in this chapter, secrecy.
e) Notifying the MS of success or failure of the above sequence of procedures.

In addition, the present system has a capability of notifying the network side of the request service of the calling user after the establishment of the terminal association, and notifying that the network has accepted the call request of the user.
In addition, the present system has a capability of notifying the outgoing call control function of the above-mentioned instance of the terminal association control function and associating the two.
In addition, the present system includes notifying the network of the wireless state around the MS when a service is requested from the MS, and recognizing the network.
The system also has the ability to collect and analyze user profiles and determine service provision based on service requests from MSs.
In addition, the present system has a capability of capturing, starting, and setting in-network resources (voice codec, data trunk, in-network wired line, etc.) for providing services based on the analysis of the requested service of the MS.

  The system also has the ability to set up access links for traffic channels and associated control channels in response to service requests from MSs. (Refer to this chapter, access link setting) Also, with the setting of the associated control channel, it has the ability to release the SDCCH that has been used to transfer control signals. This point will be described in detail in this chapter, SDCCH control.

In addition, the system makes a service request to the other user, and has the ability to perform call control such as the other user call notification and response notification in accordance with the incoming call control on the other user side, and the independent call of the communicating user. Has the ability to provide outgoing (additional calls). However, user authentication is not performed for the additional call because user authentication of the MS that is already in communication is performed.
The system also has the ability to provide outgoing calls from new users while a call is in progress on the terminal.

(2.3.3.2.1.2): Incoming Incoming is an incoming call based on a service request from a third party user to this system user, the network calls the user MS, accepts the response, and communicates with the incoming user. A series of control procedures for setting an access link in the network and between the network and the MS and a connection to the other user. This procedure is implemented by procedures such as paging, SDCCH control, user ID retry, authentication, confidentiality start, in-network routing, access link setting, etc., and mutual information transfer and analysis procedures with the receiving user.

  In order to handle incoming calls, the system has the following capabilities. First, the system accepts service requests from third parties (from the system user and the user at the interconnection destination), collects profiles by the mobile user identifier of the incoming user, analyzes the service of the incoming user, It has the ability to perform paging activation to the paging execution function by analyzing the status of the MS, necessity of paging execution, acquisition of the paging area, and acquisition of information necessary for establishing the terminal association from the network. However, Pagig is not performed for additional incoming calls.

The system also has the ability to call the MS with a mobile user identifier that identifies the terminating MS and recognize the response MS on the network side. Normally, TMUI is used. If the network knows that the TMUI is abnormal, it uses an MS-specific mobile user identifier (IMUI). The Paging procedure is implemented with the following capabilities.
a) The network recognizes the Paging area corresponding to the MS, and specifies the Paging-CH for paging. Thereafter, a signal is distributed to a node (BTS) in the network that performs paging on the paging-CH, and paging is performed in a necessary area (sector unit) in the BTS.
b) Establishing an SDCCH for notifying the network of a response to the MS Paging. This point will be described in detail in this chapter, SDCCH control.
c) When the MS responds to the call from the network, the terminal association is activated with the terminal MS. Further, the correspondence between the response signal and the calling signal is taken using the Paging ID. Further, the MS capability is notified from the MS to the network, and the network retains the MS capability and controls to accept a new call to the MS in the network when a new call occurs thereafter.
In addition, this system has a capability of notifying the network of the wireless state around the MS at the time of the Paging response, and recognizing it on the network.

In addition, this system has a capability for the network to establish a terminal association based on the response from the MS. The establishment of the terminal association is performed as follows.
a) User authentication control for confirming the validity of the MS is performed. This point will be explained in detail in this chapter and the user authentication chapter.
b) Concealment control is performed to prevent interception and falsification of the control channel and information channel between the MS and the network. This point will be explained in detail in this chapter and the secrecy chapter.
c) The MS is notified of the success or failure of the above sequence.

  In addition, after establishing the terminal association, this system performs routing to the in-network control node that performed the control, notifies the setting of the in-network line and the request service of the calling user, and activates incoming call control. Is provided. In addition, this terminal association control function instance is notified to the incoming call control function to associate them.

  The system also has the ability to collect and analyze user profiles based on incoming service requests and determine service provision to incoming users.

  In addition, the system has the capability of capturing, starting, and setting in-network resources (voice codec, data trunk, in-network wired line, etc.) for providing services based on the analysis of the incoming request service.

  The system also has the ability to set up access links for traffic channels and associated control channels corresponding to incoming service requests. This point will be explained in detail in this chapter, access link setting. In addition, with the setting of the associated control channel, the SDCCH for which control signal transfer has been performed is released. This point will be described in detail in this chapter, SDCCH control.

In addition, the system has a capability of making a service request to an incoming user and performing call control such as notification of a called user being called to the other party's outgoing user and notification of a response accompanying the incoming call control.
The system also has the ability to provide outgoing calls from new users while a call is in progress on the terminal.
The system also has the ability to provide an independent call termination (additional call) to the communicating user. However, user authentication is not performed for the additional call because user authentication of the MS that is already in communication is performed.

  In addition, this system is for the case where there is a response from a plurality of MSs when receiving a call, and the procedure after the response fails, and the correspondence between TMUI and IMUI between the network side and the mobile device is inconsistent. Provides the ability to reassign TMUI during the incoming procedure.

(2.3.3.2.1.3): Call Release Call release refers to a call release request from a user, a call release request from a partner user during communication, or detection of deterioration of a wireless line. A series of procedures for releasing a link in the network used for communication, an access link between the network and the MS, and a connection with the other user. This procedure is realized by the procedure of user disconnection (user status update) and access link release.

  In the final call release procedure on the MS, a procedure for releasing the association between the MS and the network is activated. This procedure is realized by a procedure for updating the mobile device status.

To handle call release, the system has the following capabilities: First, this system has a capability of notifying a user of a call release request from the user and notifying the user that the network has accepted.
In addition, this system has a capability of notifying a user of a call release request from a communication partner user from the network.
The system also has the ability to update the user profile for user status update due to call release.

  The system also has the ability to release the access link corresponding to the call being released. This point is described in detail in Release of access link [Chapter 3.2.2.3]. If an associated channel is set for the access link, the ACCH switching procedure is activated. This point will be described in detail in Handover [Chapter 3.2.2.4].

In addition, the present system has the capability of identifying whether the call to be released is the final call on the MS, and in the case of the final call, has the ability to change the status of the mobile device managed by the network.
In addition, this system has a capability of releasing a call triggered by an access link release procedure (see access link release [Chapter 3.2.2.3]) based on detection of loss of synchronization.
In addition, this system has a capability of releasing a call in response to an access link release request from the MS.
In addition, the present system has a capability of releasing a call from the MS due to abandonment during call origination.

(2.3.2.2): System capability related to access link control (2.3.2.2.2.1): SDCCH control SDCCH control refers to SDCCH for MS to access the network and send / receive control messages. (Stand-alone Dedicated Control Channel) and procedures for establishing an access wired link for transfer of control messages within the network, and when this SDCCH and the intra-network access wired link become unnecessary The procedure to do. This procedure is executed along with all procedures that require MS-network interaction including MS transmission, MS termination, and MS location registration.

  In order to execute SDCCH control, the system has the following capabilities. First, the present system has a capability that an MS requests an SDCCH setting to the network using a random access procedure on the RACH, and the network allocates radio resources (upper and lower short codes) for the SDCCH to the MS using the FACH. The correspondence between this request and allocation is performed based on a random number (PID) set by the MS in the request message.

  In addition, this system has a capability for the network to select radio resources (upper and lower short codes) for the SDCCH for each sector. As the upper and lower long codes for the SDCCH, those unique to the base station and having different phases for each sector are used. Therefore, the MS obtains a downlink long code from the cell search procedure or broadcast information (BCCH1) and an uplink long code from the broadcast information (BCCH1).

  In addition, this system has a capability of establishing an access wired link for transferring a control message within the network in response to an SDCCH setting request from the MS.

The system also has the ability to identify MS location information when requesting establishment of an access wired link in the network. Note that the RACH, FACH, and SDCCH transmission power settings in this procedure are described in detail in section 2.3.2.2.2.6.
In addition, this system recognizes that the SDCCH is no longer necessary for the network and the MS (end of non-call related procedures such as location registration, transition to ACCH, etc.), and has the ability to execute the release locally. Prepare.

(2.3.3.2.2.2): Access link setting The access link setting refers to a communication channel for user information transfer and a control channel for control signal transfer between the network and the MS when an MS originates / receives an MS. The procedure for setting in. This procedure includes a procedure for setting up an access wired link in the network and a procedure for setting up an access wireless link between the network and the MS.

In order to perform access link setup, the system has the following capabilities. First, the network has an ability to determine an information transfer capability, a quality class, and the like required for an access link of each connection based on a call / connection control request, and to allocate an appropriate resource.
In addition, the present system has an ability for the MS to designate an access wired link and an access wireless link setting candidate sector for the network based on the perch channel measurement result and broadcast information from the network. Call admission control will be described in detail in Chapter 2.3.2.2.7.

In addition, the present system has a capability for the network to set an access wired link in an access wired link and an access wireless link setting sector designated by the MS. Here, the access wired link setting includes a communication channel for transferring user information and, if necessary, a control channel for transferring a control signal.

  In addition, the present system has a capability for the network to store an uplink long code applied to the access radio link in the in-network database in correspondence with the MS identifier (TMUI / IMUI). Furthermore, it has the ability to obtain this information from the database when setting the access link.

  The system also has the ability for the network to select a radio resource for an access radio link within the designated sector and assign it to the MS. The radio resource selection is described in detail in Chapter 2.3.2.2.5.

  In addition, the present system has an ability for the MS to send information (perch transmission power, perch reception SIR) for determining the initial transmission power of the downlink access radio link to the network based on the perch channel measurement result.

  In addition, this system has a capability for the network to determine the initial transmission power of the downlink access radio link based on information for determining the downlink transmission radio link initial transmission power from the MS. The transmission power control will be described in detail in Section 2.3.2.2.2.6.

  In addition, the present system has a capability for the BSC to start diversity handover simultaneously with access link setting based on access wired link and access radio link setting sector information from the MS. Handover will be described in detail in Chapter 2.3.2.2.4.

  In addition, the present system has the capability of the MS notifying the network of the uplink long code phase difference between the sector where the SDCCH is set and each candidate sector based on broadcast information (20 msec periodic report information).

In addition, the present system has a capability of establishing synchronization of the uplink access radio link based on the uplink long code phase difference information notified from the MS.
(2.3.2.2.2.3): Access link release

  The access link release refers to a procedure for releasing all communication channels for network-MS user information transfer and control channels for control signal transfer at the end of communication. This procedure includes a procedure for releasing the access wired link in the network and a procedure for releasing the access wireless link between the network and the MS.

  In order to perform access link release, the system has the following capabilities. First, the present system has a capability of releasing a corresponding access link when the network releases each connection or releases a corresponding connection accompanying a call release. In this case, release of the access radio link is requested from the network to the MS.

In addition, when this system detects loss of synchronization in all handover branches of an access link, if this system does not detect resynchronization before a certain time (squelch hold timer expires), it will release this access link. With the ability to
In addition, when the MS detects out-of-synchronization in all the handover branches of the access link, it has the ability to stop radio channel transmission of this access link and to detect out-of-synchronization in the network. Note that the MS may notify the network of this event.
The system also has the capability of releasing all handover branches of the access link as the access link is released during a diversity handover.

(2.3.2.2.4): Handover Handover is a procedure for changing the access point to the MS network while continuing communication due to MS movement, communication quality degradation, traffic distribution, and other reasons. Say. This procedure includes access radio link switching and, in some cases, access wired link switching procedures.

In order to execute a handover, the system has the following capabilities.
First, the system has the ability to support the next handover.
a) In intra-cell inter-sector branch addition handover, handover is performed in which a handover branch is added in a different sector in the same cell as the used handover branch. The access wired link is not added with this handover.

  b) In the inter-cell branch additional handover, a handover for adding a handover branch in a different cell from the handover branch in use is performed. An access wired link to an additional cell is also added along with this handover.

  c) In the inter-cell sector branch deletion handover, in a handover handover, that is, in an intra-cell sector diversity handover state after execution of an intra-cell sector branch addition handover, a handover for deleting one sector of the handover branch is performed. Done. The access wired link is not deleted along with this handover.

  d) In the inter-cell branch deletion handover, in the inter-cell diversity handover state after the inter-cell branch addition handover is executed, a handover for deleting one cell's handover branch is performed. The access wired link for the deleted cell is also deleted along with this handover.

  e) In intra-cell branch switching handover, handover is performed in which all handover branches in communication are released and an access link is newly set in the handover destination cell. If there is no change in service attributes before and after handover, the access wired link is maintained. Note that this includes inter-cell sectors.

  f) In the inter-cell branch switching handover, a handover is performed in which all handover branches in communication are released and an access link is newly set in the handover destination cell. With this handover execution, switching of the access wired link is also executed.

  g) In intra-sector frequency switching handover, handover is performed for switching to a different radio frequency channel in the same sector for all handover branches in communication. The access wired link is not added / deleted with this handover.

  h) Code switching is handover for switching a downlink short code to a different code of the same code type in the same sector for a certain handover branch in communication. The access wired link is not switched with this handover.

  i) In user speed switching, all handover branches for the connection are released to change connection attributes between users (speed change, voice-voice band data switching, etc.), and newly changed connections are supported. Possible access links are set up.

  j) ACCH switching is a case where the radio resources in use of ACCH are released with the release of each connection or the corresponding connection with the release of the call, and the ACCH is continuously used for other calls. When securing is required or when changing the transmission rate required for the ACCH, the ACCH is switched to an access wired link or an access wireless link for another connection.

  k) The code type may be switched. In this case, the short code can be switched to a code of a different code type within the same sector for all handover branches in communication. The access wired link is not switched with this handover. Note that the maximum number of handover branches that can be simultaneously connected by the above-described branch addition handover is N.

  In addition, the present system has a capability for the MS to activate branch addition handover, branch deletion handover, and branch switching handover for the network based on the perch channel measurement result and call acceptance information from the network. The activation information includes designation information of candidate sectors for which handover is executed. Call admission control is described in detail in section 2.3.2.2.2.7.

In addition, the present system has a capability for a network to execute a handover by determining a handover execution sector from the candidate sectors based on the handover activation from the MS.
In addition, in the case of branch addition handover, the system has a capability for the network to allocate radio resources for the access radio link on the radio frequency channel having the same radio frequency as the existing branch for the additional branch. In addition, the same uplink code resource is assigned to all branches of one connection. The radio resource selection is described in detail in Chapter 2.3.2.2.5.

  In addition, the system has a capability of ignoring handover activation from the MS when the network cannot execute a handover due to a lack of required radio resources or other in-network resources. In addition, when the MS does not receive a handover execution instruction from the network in response to its own handover activation request, it has a capability of performing a handover activation analysis again after a certain time, and reactivating the handover if necessary. In addition, the system has a capability for the MS to transmit information for determining the initial transmission power of the downlink access radio link of the additional branch to the network based on the perch channel measurement result.

In addition, the present system has a capability that the network determines the initial transmission power of the downlink access radio link of each additional branch based on the above-mentioned initial transmission power determination information from the MS. The transmission power control will be described in detail in Section 2.3.2.2.2.6.
In addition, in this system, in the branch addition handover, the MS uses the uplink long code phase difference between itself and each branch addition candidate sector based on broadcast information (20 msec periodic report information), and the frame offset group used by itself. , With the ability to notify the network of slot offset groups.

  In addition, this system has a capability of establishing synchronization of the uplink access radio link in the branch added sector based on the uplink long code phase difference information, the frame offset group, and the slot offset group notified from the MS.

  Further, in this system, one or both of the addition of an intra-sector branch and the addition of an inter-cell branch can be started and executed simultaneously with each branch switching, intra-sector different frequency, and user speed switching handover. The number of branches added by intra-sector sector branch addition and inter-cell branch addition handover is a maximum of N−1 in total.

Further, in this system, branch addition and branch deletion handover can be activated and executed simultaneously. Note that the maximum number of branches after execution of these combinations is N.
In the present system, branch addition handover, branch switching handover of other connections, ACCH switching, and code type switching of other connections can be executed simultaneously with access link setting.

In addition, the present system has a capability for the network to request code switching from the MS for effective use of short code resources.
Further, in this system, ACCH switching can be performed simultaneously with the release of the access link. Note that SDCCH handover is not performed.

(2.3.3.2.5): Radio resource selection Radio resource selection is an appropriate radio resource (wireless) based on information sent from the MS for each procedure of SDCCH setup, access link setup, and handover. Frequency channel, short code, offset value, etc.).

For radio resource selection, the system has the following capabilities. First, this system is provided with the ability for the MS to notify the network of its radio functional capabilities (corresponding radio frequency channel, corresponding multi-code number, etc.).
In addition, the present system is provided with the capability of the network to obtain the uplink long code specific to each MS from the in-network database.

In addition, this system has a capability for the network to manage the usage status of the uplink short code of each MS and select the uplink short code for each connection. In addition, the present system has a capability that the network determines execution / rejection of the requested radio resource selection based on the amount of uplink interference for each sector and the requested communication speed and quality.
In addition, this system has a capability that the network manages the usage status of the downlink short code for each sector and selects the downlink short code for each connection according to the request.
In addition, this system has a capability for the network to select a radio frame offset group and a slot offset group in radio resource selection for the SDCCH setup procedure and the access link setup procedure.

(2.3.2.2.6): Transmission power control Transmission power control is the initial transmission power determination of the radio access link in each procedure of signal transmission on RACH / FACH, SDCCH setting, access link setting, handover, Moreover, it means performing downlink transmission power control of each handover branch during diversity handover. Note that this procedure does not include transmission power control executed by layer 1.

(1) Uplink initial transmission power value setting Transmission power when transmitting from the mobile station to the base station via the uplink radio channel saves the capacity of the uplink radio channel and has an adverse effect on other radio access links. To prevent it, it should be minimized as much as possible. In order to minimize the uplink transmission power, for example, when selecting a radio zone to be awaited or a radio zone to be handed over during communication, a radio zone capable of performing communication with the minimum transmission power should be selected. And some means is needed to make that choice.

  However, the mobile station in the conventional system can detect only the reception level or SIR (signal-to-interference power ratio) from each base station as a decision material for selecting such a radio zone. In addition, the transmission power value of each base station may be different for each base station. For this reason, in the conventional system, it has been impossible for the mobile station to autonomously optimize the uplink transmission power from the mobile station to the network.

Therefore, the present system has the following capabilities to solve this problem and to set an optimal upstream initial transmission power value.
First, in this system, a corrected perch CH transmission corrected by the network in consideration of transmission loss (cable loss etc.) in the base station using periodic report information (broadcast information transmitted every 20 msec) in the perch CH. It has the ability to report power values.

In addition, the present system has a capability for the network to notify the amount of uplink interference using periodic report information (every 20 msec) in the perch CH.
In addition, this system sets the initial transmission power value based on the perch CH transmission power value after correction, the amount of uplink interference, the perch CH reception power value measured by the MS, and the base station required reception SIR held as operation data. Has the ability to set.

Here, with reference to FIG. 792, optimization of the uplink transmission power value performed based on the above-described capability will be described.
First, as shown in FIG. 792, base stations A and B exist, and broadcast information is transmitted through respective perch channels, and each perch channel transmission power value (after the above correction) is Pa and Let it be Pb. Also, Ra and Rb are reception levels when the mobile station receives broadcast information from both base stations via the perch channel.

In this case, the mobile station transmits the perch channel transmission power values Pa and Pb of the base stations A and B included in the broadcast information, and the perch channel reception levels Ra and Rb from the base stations A and B in the mobile station. Based on the above, it is possible to obtain the propagation loss Lpa = Pa−Ra between the base station A and the mobile station and the propagation loss Lpb between the base station B and the mobile station.
In the mobile station, for example, when selecting a radio zone to be awaited or when selecting a radio zone as a handover destination, the propagation loss obtained for each base station as described above, the uplink interference amount of each base station, Calculates the required uplink transmission power for each base station from the station required reception SIR, selects the base station (radio zone) with the minimum required uplink transmission power, and optimizes the uplink transmission power according to the base station Can be (minimized).
As described above, according to the present system, it is possible to optimize the uplink transmission output in the mobile station even when the perch channel transmission power value differs among the base stations.

(2) Downlink initial transmission power value setting 1) FACH, downlink SDCCH
The MS notifies the network (BTS) of the perch CH reception SIR value by the RACH. Further, the network (BTS) transmits the initial transmission from the perch CH reception SIR value of the mobile station perch, the perch CH transmission power value of the operation information within the network (BTS), the FACH (SDCCH) required reception SIR value in the MS, and the rate correction value. Set the power value.

2) Downstream TCH
The network (BTS) broadcasts the perch CH transmission power value (without correction) using broadcast information (BCCH1) in the perch CH. The MS notifies the network (BSC function) of the perch CH received SIR value of the mobile station through the SDCCH. The MS notifies the network (BSC function) of the perch CH transmission power value (without correction) using the SDCCH.

Also, the network (BSC function) is based on the mobile station perch CH reception SIR value, perch CH transmission power value (no correction), and the TCH required reception SIR value and rate correction value in the MS of the network (BSC function) operation information. It has the ability to calculate the downlink initial transmission power value. When there are a plurality of TCH setting candidate zones, the value of the zone (main branch) with the smallest calculated value is set as the set value.
The network (BSC function) has a capability of notifying the base station of the initial downlink transmission power.

Further, since the reliability of a certain radio branch becomes low during the diversity handover, and the high-speed transmission power control may not operate normally, the MS has the ability to perform the low-speed downlink transmission power control by layer 3.
The MS periodically notifies the network (BSC) of the perch CH transmission power value (without correction) and the perch CH reception SIR value in the zone in communication.
In addition, this system has a capability of increasing or decreasing the required reception SIR in the MS so that the MS reception quality during communication is the same as the reference quality.
The network has the ability to calculate and set the transmission power control value of the base station based on the above values.

(2.3.2.2.2.7): Call admission control Call admission control refers to the amount of uplink interference, downlink transmission power, equipment resources in use that can be measured and determined in the base station, and each allowable limit. By comparison, it refers to control for generating idle / busy information and restricting call acceptance at the time of outgoing / incoming calls, at the time of bearer change, and at the time of handover based on the information. This control procedure is implemented in the MS and network, and the implementation of the control in the MS is optional. By implementing with MS, it becomes possible to suppress useless call request, TCH setting at the time of incoming call, bearer change request, and handover request, which contributes to reduction of control load in the network. This control in the network is indispensable because there are situations in which the network has to make a judgment based on the update frequency of call admission control and traffic concentration.

(1) In case of implementation by MS With respect to implementation by MS, the system has the following capabilities.
First, the present system has a capability for the network to notify the call acceptance information in the broadcast information (BCCH2).
This system also allows the MS to start random access at the time of the first call transmission, at the time of SETUP transmission at the time of the second call transmission, at the time of SETUP reception at the time of incoming call (TCH is not set), at the time of handover trigger transmission, and bearer change Immediately before the SETUP transmission at that time, it has the ability to refer to the broadcast information (BCCH2) in the base station that is a TCH setting candidate.
In addition, the present system has an ability for the MS to determine whether the assignment is possible or not in comparison with call acceptance information.

(2) When implemented in the network With respect to the implementation in the MS, the present system has a capability for the network to determine whether or not to allocate the TCH activation request in comparison with the call acceptance information.

(2.3.2.2.8): Standby control Standby control is to control the MS to make a transition to a state where outgoing / incoming calls can be made when the power is turned on or when the MS moves from outside the service area. That's it. A procedure for changing the standby zone due to the movement of the MS is referred to as standby zone shift control.

(1) Standby control In order to execute standby control, this system has the following capabilities. First, in the present system, the network uses the periodic report information (every 20 msec) in the perch CH, and reports the corrected perch CH transmission power value corrected in consideration of the transmission loss (cable loss etc.) in the base station. Have the ability.

In addition, this system selects the minimum value based on the perch CH transmission power value after correction of the zone holding the searched downlink long code and the perch CH reception power value measured by the MS, and broadcasts the zone. Ability to reference information (BCCH1).
In addition, the present system has a capability that the network uses the broadcast information (BCCH1) in the perch CH to broadcast the standby permission level, the standby deterioration level, the network number, the regulation information, and the like.
In addition, the present system is provided with an ability for the MS to make a standby permission determination based on the broadcast information (BCCH1) referred to.

In addition, this system has a capability for the network to broadcast control channel structure information using broadcast information (BCCH1) in the perch CH.
In addition, the present system has an ability for the MS to determine a PCH to be awaited from the broadcast information (BCCH1) referred to.
In addition, the present system is provided with the ability for the MS to determine the RACH to be used from the broadcast information (BCCH1) referred to.

In addition, the present system has a capability that the network broadcasts the uplink long code of the zone using broadcast information (BCCH1) in the perch CH.
In addition, the present system has an ability for the MS to determine an uplink long code to be used in the RACH and SDCCH based on the broadcast information (BCCH1) referred to.

(2) Standby zone shift control Further, in order to execute the standby zone shift control, the present system has the capability of broadcasting the downlink long code of the surrounding zone using the broadcast information (BCCH1) in the perch CH. . In addition, the present system has a capability for the MS to search the downlink long code of the surrounding zone from the broadcast information (BCCH1) referred to and shift to the zone.

(2.3.2.3): System Capability regarding Mobility Service The system capability regarding mobility service will be described.
(2.3.3.2.3.1): Terminal Location Registration / Update The network manages the terminal location in order to guarantee the mobility of the mobile terminal. Therefore, the terminal location registration is performed when the user is first recognized in the network (when the power is first turned on or when another network user roams to the network). On the other hand, the terminal location update is automatically performed when the location area changes in the same network. Thereby, the terminal position information in the network is rewritten.

In order to execute terminal location registration / update, this system has the following capabilities.
First, this system. The network has the ability to broadcast location information to the MS so that the MS can recognize the location information.
In addition, when the MS moves in the network, the system recognizes that the MS has moved from the location area managed in the network, and has an ability to request an update of the location information managed in the MS.
In addition, this system has an ability to establish an SDCCH in order to transmit and receive a control signal for a location registration procedure with a network and an MS (see SDCCH control).

In addition, this system has a capability of performing terminal authentication in order to prevent an unauthorized mobile device from accessing the network and updating location information in the network only when it succeeds.
The system also has the ability for the network to assign a new TMUI to the MS.
In addition, the present system has a capability of starting authentication using the IMUI for the MS when the authentication using the TMUI fails.
The system also has the ability to notify the MS from the network that the location registration procedure has been completed.
In addition, the present system has a capability for the MS to activate the location registration / update procedure again when the MS cannot receive the location registration / update result notification.

(2.3.2.4): System capabilities related to security services Next, system capabilities related to security services will be described.
(2.3.2.2.4.1): User Authentication User authentication refers to confirming whether each mobile device user making a service request to the network is valid. As a result, it is possible to prevent an unauthorized mobile device from accessing an unauthorized network. This procedure is executed at the time of MS transmission (first call), incoming call, and location registration.

  In order to perform user authentication, the system has the following capabilities. First, when the MS accesses the network, this system generates information (authentication calculation result, random number) necessary for executing authentication of the MS in the network, and requests the MS to perform the authentication calculation. Is provided. Moreover, it has the capability to generate a secret key used in a secret calculation performed after authentication.

In addition, the present system has a capability that the MS generates an authentication calculation result based on the random number notified from the network and notifies the network.
In addition, this system has a capability of collating the authentication calculation result generated by the network with the authentication calculation result from the MS.
In addition, the present system has the ability to allow the network to query the MS for the IMUI when the authentication performed using the TMUI fails, acquire authentication-related data based on the IMUI, and execute the authentication procedure again.
In addition, this system has a capability of canceling an outgoing call, incoming call, and location registration procedure when an authentication operation fails due to in-network data by IMUI.

(2.3.4.2.2): Concealment Concealment is illegal in the control signal (SDCCH, ACCH) and user information (TCH) between the network and the MS based on the service request from the user of this system user. A series of controls that encrypt signals to prevent eavesdropping and data tampering. This control procedure is performed in the outgoing call, incoming call and location registration procedures.

  In order to execute concealment, the system manages control signals on the wireless interface, information necessary for ciphering and deciphering user information (secret information, related information for generating secret keys, etc.) It has the ability to deliver to the network and to the MS.

In addition, the present system has a capability of performing data calculation and transmitting / receiving data on a wireless interface based on the delivered information.
In addition, the present system has a capability of instructing the start timing of ciphering and deciphering between the network and the MS.

(2.3.3.2.4.3): TMUI Management TMUI determines (1) the purpose of ensuring confidentiality on the air interface (IMUI concealment), and (2) the amount of terminal identifier information on the air interface. For the purpose of reduction, it is used as a temporary terminal identifier (= user identifier) on the air interface.

  The network assigns a TMUI to the MS that is in the area, notifies the TMUI assigned to the MS, and manages the TMUI in the network while the MS is in the area. TMUI management is performed by location registration, outgoing call, and incoming call procedures. However, in this system, TMUI allocation at the time of outgoing / incoming calls is optional.

  In order to perform TMUI management, the system has the following capabilities. First, this system has a capability to generate and secure a TMUI for the MS when the network accesses the MS (location registration, update procedure, outgoing / incoming call procedure (optional)).

The system also has the ability to notify the MS of the TMUI generated by the network and confirm that the MS has stored the TMUI. At the time of location registration, the mobile device is notified together with information specifying the node to which the TMUI is assigned. At the time of outgoing / incoming call, only the TMUI is notified to the mobile device.
In addition, this system has the ability to activate TMUI notification after concealment on the air interface so that the contents are not intercepted illegally when the TMUI is notified from the network to the MS.
In addition, this system has a capability of managing the usage state of the TMUI so that the TMUI double assignment is not performed.

(2.3.2.5): System Capability Related to System Management Next, system capability related to system management will be described.
(2.3.2.5.1): System synchronization condition The system synchronization condition refers to a synchronization condition in the system necessary for performing diversity handover without significant buffering delay in the network and the mobile device. Specifically, for example, the cycle is 640 ms.

  In order to satisfy the above-mentioned system synchronization condition, the present system takes subordinate synchronization between the MSC (MCC) function and the subordinate BTS with respect to the reference clock having a period of 640 ms, and maintains the clock timing. Note that the phase synchronization error of the 640 ms period clock between the MSC function and the subordinate BTS is within 5 ms.

(2.4): Control Method Next, the control method will be described.
(2.4.1): Functional network architecture FIG. 3 shows the functional network architecture of this system. Each function conforms to the ITU-T recommendation.
In the figure, CCAF is an interface between a user and a network side call control function (CCF) that is provided on a mobile terminal and provides service access to the user. TACAF is configured on the mobile terminal, and controls access to the mobile terminal such as paging detection.

  Next, BCAF is configured on the mobile terminal and controls the radio bearer of the mobile terminal. The BCF controls bearers. The BCFr is provided on the network side and controls the radio bearer.

  Next, the TACF is provided on the network side and controls access to the mobile terminal for execution of paging or the like. The CCF performs call / connection control. The SCF performs service control. The SDF accumulates various service-related data. The LRCF performs mobility control. The LRDF stores various data related to mobility. SSF is an interface between CCF and SCF. It also detects service control triggers. The SRF controls access to special devices such as information storage devices.

  Next, the MCF is provided on the mobile terminal and is an interface with a network in a non-call related service. On the other hand, the SACF is provided on the network side and is an interface with a mobile terminal for non-call related services.

  Next, MRRC is provided in the mobile terminal and controls radio resources. On the other hand, the RRC is provided on the network side and controls radio resources. The MRTR is provided in the mobile terminal and performs secrecy and output control. On the other hand, the RFTR is provided on the network side, and performs secrecy and output control.

  The UIMF then holds information about the mobile user and provides user authentication and secrecy. In the following description, UIMF may be described as UTMF.

  FIG. 4 shows the functional network architecture divided into a communication control plane and a radio resource control plane. In this figure, the number (FE Number) of each functional entity is associated with the functional entity name shown in FIG.

The relationship between each functional entity is as follows.
Between FE01 and FE06 (CCAF-CCF) is Relationship ra, between FE02 and FE05 (TACAF-TACF) is Relationship rb, between E07 and FE09 (LRCF-SSF) is between Relationship rc, and between FE07 and FE08. (LRCF-LRDF) is Relationship rd, FE09 and FE10 (SSF-SRF) is Relationship re, FE07 and FE10 (LRCF-SRF) is Relationship rf, FE05 and FE07 (TACF-LRCF) Is Relationship rg, between FE05 and FE12 (TACF-SACF) is Relationship rh, and between FE05 and FE06 (TACF-CCF) is R relationship ri, between FE05 and FE04 (TACF-BCF) is Relationship rj, rja between FE05 and FE04a, rjb between FE05 and FE04b, and Relationship kr between FE07 and FE12 (LRCF-SACF). Between FE11 and FE12 (MCF-SACF) is Relationship rl, Between FE01 and FE02 (CCAF-TACAF) is Relationship rm, Between FE02 and FE03 (TACAF-BCAF) is Relationship rn, FE13 and FE14. (MRRC-MRTR) is between Relationship ro and FE13 and FE15 (MRRC-RRC) is between Relationship rp, FE15 and FE. Between 6 (RRC-RFTR) is Relationship rq, Between FE03 and FE04 (BCAF-BCF) is Relationship rr, Between FE04 and FE06 (BCF-CCF) is between Relationships rs, FE05 and FE15 (TACF). -RRC) is Relationship rt, FE02 and FE13 (TACAF-MRRC) is Relationship ru, FE02 and FE17 (TACAF-TIMF) is Relationship rv, and FE11 and FE17 (MCF-TIMF) is Relations. The relationship between rw and FE01 and FE18 (CCAF-UIMF) is Relationship rx, and between FE11 and FE18 (MCF-UIMF) is Relatio. Shipry, between FE04a and FE04b (BCFr-BCF) is Relationship r44, between FE06 and FE06 (CCF-CCF) is Relationship r66, between FE07 and FE07 (LRCF-LRCF) is Err77, Between FE05 and FE05 (TACF-TACF) is called Relationship r55, and between FE08 and FE08 (LRDF-LRDF) is called Relationship r88. FIG. 271 summarizes the relationship between the functional entities.

(2.4.2): Basic communication service information flow (2.4.2.1): Originating (first call, additional call)
a) Functional model
a-1) First call (Initial outgoing call)
FIG. 5 shows a function model of the first outgoing call. The radio resource is selected by the BCFr under the control of the same TCAF that has received the setup request call. A scenario composite FEs network is formed by selecting radio resources.
a-2) Additional call (Outgoing call additional)
FIG. 6 shows a function model of the outgoing additional call. The radio resource is selected by the BCFr under the control of the same TCAF that has received the setup request call. A scenario composite FEs network is formed by selecting radio resources.

b) Information flows
b-1) Initial call (Initial outgoing call)
7 and 8 show information diagrams of the first call.
b-2) Additional call FIG. 9 shows an information diagram of an additional call.

c) Definition of Information Flows, Information Elements, Functional Entity Operations (Definitions of Information Flows, Information Elements, and Functional Entity Actions)
The information flow and the like will be described below, and the corresponding information elements and the like are shown together in a table. However, the table may be omitted if there is no corresponding element.
When the CCAF issues a setup request call for terminal access to the network by the mobile station and a setup request call for connection between the CCAF and TACAF, the TA SETUP req. ind. (TA setup req.ind.) Is used (see FIG. 272).
TA SETUP req. ind. (TA setup req.ind.) Is transmitted from TACAF for a request for establishment of terminal access, such as, for example, invoking connection between TACAF and TACF (see FIG. 273).
The TMUI is used to establish IMUI trust, and the user ID does not include the TMUI allocation source ID for shortening the data.

TACF is a TA SETUP PERMISSION req. ind. (TA setup permission req.ind.) Requests authentication of access from the mobile device to the network (see FIG. 274).
Reverse Long Code Retrieval req. ind. (Uplink long code search req.ind.) Is used to search for an uplink long code (see FIG. 275).
Reverse Long Code Retrieval req. ind. (Uplink long code search req.ind.) Is used for searching for an uplink long code (see FIG. 276).
Reverse Long Code Retrieval resp. conf. (Uplink long code search resp.conf.) Is used for searching for an uplink long code (see FIG. 277).

TERMINAL STATUS UPDATE req. ind. (Terminal state update req.ind.) Is used to update the terminal state (see FIG. 278).
TERMINAL STATUS UPDATE resp. conf. (Terminal state update resp.conf) responds to the request (see FIG. 279).

ADD ROUTING INFO req. ind. (Add routing information req.ind.) Is sent to the LRDF to add a routing address to the subscriber's profile. This information flow is transmitted only when an authenticated mobile device is found and the related information is obtained (see FIG. 280).
ADD ROUTING INFO resp. conf. (Routing information addition resp.conf.) Responds to the request (see FIG. 281).

The LRCF notifies the TACF of TA SETUP PERMISSION resp. conf. (TA setup permission resp.conf.) Is activated (see FIG. 282).
Reverse Long Code Retrieval resp. conf. (Uplink long code search resp.conf.
) Is used for uplink long code search (see FIG. 283).

TA SETUP resp. conf. (TA setup resp.conf.) Notifies the completion of establishment of terminal access (see FIG. 284).
TA SETUP resp. conf. (TA setup resp.conf.) Is used for confirmation of setup of terminal access, connection completion between CCAF and TACAF (see FIG. 285).

SETUP req. ind. (Setup req.ind.) Is used for connection establishment request (see FIG. 286).
TACF Instance ID Indication req. ind. (TACF instance ID instruction req.ind.) Is used for searching for an uplink long code (see FIG. 287).

  MMRC is a CELL CONDITION MEASUREMENT req. ind. (Cell state detection req.ind.) Search for cell selection information is started. This flow is an information flow for requesting confirmation, and the confirmation (that is, CELL CONDITION MEASUREMENT resp. Conf.) Provides a detection result (see FIG. 288).

  CELL CONDITION MEASUREMENT resp. conf. (Cell state detection resp. Conf.) Is a CELL CONDITION MEASUREMENT req. ind. In response to a request from (cell state detection req. Ind.), A detection result of cell selection information is provided (see FIG. 289).

In order to report cell selection information, the mobile terminal transmits a CELL CONDITION REPORT req. ind. (Cell status report req. Ind.). The network uses this information for radio channel selection. This information flow does not require confirmation (see FIG. 290).
The SSF sends a CALL SETUP PERMISSION req. ind. (Call setup permission req. Ind.) Is activated (see FIG. 291).

USER PROFILE RETRIEVAL req. ind. (User profile search req.ind.) Is used for a user profile search request (see FIG. 292).
USER PROFILE RETRIVAL rep. conf. (User profile search resp.conf.) Responds to the request (see FIG. 293).

The LRCF is a CALL SETUP PERMISION resp. conf. (Call setup permission resp.conf.) Is activated (see FIG. 294).
SETUP req. ind. (Setup req.ind.) Is used for connection establishment request (see FIG. 295).
PROCEEDING req. ind. (Procedure req.ind.) Reports the validity of the receiver's connection setup, authentication, routing and continuation of call progress as desired. This information flow does not require confirmation (see FIG. 296).

In the TACF-RRC (= rt), the network uses Measurement Condition Notification req. ind. (Status detection req.ind.) Indicates the status of detection and reporting of cell selection information in the mobile device. When the mobile device is in the idle mode, the network periodically performs the Measurement Condition Notification req. ind. (State detection req.ind.) Is instructed. When the mobile station is communicating, the network changes the Measurement Condition Notification req. ind. (State detection req.ind.) Is instructed. This information flow does not require confirmation (see FIG. 297).
Between MRRC and RRC (= rp), the network uses Measurement Condition Notification req. ind. (Status detection req.ind.) Indicates the status of detection and reporting of cell selection information in the mobile device. When the mobile device is in the idle mode, the network periodically performs the Measurement Condition Notification req. ind. (State detection req.ind.) Is instructed. When the mobile station is communicating, the network changes the Measurement Condition Notification req. ind. (State detection req.ind.) Is instructed. This information flow does not require confirmation (see FIG. 298).

REPORT req. Between CCF ′ and CCF ′ (= r66). ind. (Report req. Ind.) Is used for reporting the report status and / or other types of information related to the network (eg, attention, hold, hold, release, etc.). This information flow does not require confirmation (see FIG. 299).
REPORT req. Between CCAF ′ and CCF ′ (= ra). ind. (Report req. Ind.) Is used for reporting the report status and / or other types of information related to the network (eg, attention, hold, hold, release, etc.). This information flow does not require confirmation (see FIG. 300).

SETUP resp. conf. (Setup resp.conf.) Is used to confirm connection establishment (see FIG. 301).
SETUP resp. conf. (Setup resp.conf.) Is used to confirm connection establishment (see FIG. 302).

(2.4.2.2): Incoming call (first call, additional call)
a) Functional model
a-1) Initial calling call
FIG. 10 shows a function model of the incoming first call.
a-2) Incoming additional call (Incoming additional call)
FIG. 11 shows a function model of the incoming additional call.

b) Information flows
b-1) Initial call (initial calling call)
FIG. 12 is an information flow diagram of the incoming first call.
FIG. 13 is an information flow diagram of the incoming first call.
FIG. 14 is an information flow diagram of the incoming first call.
b-2) Incoming additional call (Incoming additional call)
FIG. 15 is an information flow diagram of an incoming call addition.
FIG. 16 is an information flow diagram of an incoming additional call.
b-3) Incoming additional call (Incoming additional call)

c) Definition of Information Flow, Information Element, and Functional Entity Operation Hereinafter, the information flow etc. will be described, and the corresponding information element etc. will be shown together in a table. However, the table may be omitted if there is no corresponding element. SETUP req. ind. (Setup req.ind) is used for connection establishment request (see FIG. 303).

ROUTING INFO. QUERY req. ind. (Routing information search req.ind.) Is used for routing search (see FIG. 304).
The receiving user number or roaming number is used as an identifier of the receiving user. In this case, a roaming number is used.
TERMINAL ID RETRIEVAL req. ind. (Terminal ID search req.ind.) Is used for a user profile search request (see FIG. 305).
The roaming number is used in this information flow for specifying a search target user instead of the receiving side user ID.
In the selection process, data to be searched is specified. This information element in this information flow specifies the user ID.
TERMINAL ID RETRIEVAL resp. conf. (Terminal ID search resp.conf.) Is a terminal ID search req. ind. (See FIG. 306).

TERMINAL STATUS QUERY req. ind. (Terminal state search req.ind.) Is used for searching the terminal state when the terminal is accessing, for example (see FIG. 307).
In the selection process, data to be searched is specified. This information element in this information flow specifies the communication state of the user.
TERMINAL STATUS QUERY resp. conf. (Terminal state search resp.conf.) Is a terminal state search req. ind. It responds to the request from (see FIG. 308).
TERMINAL STATUS UPDATE req. ind. (Terminal state update req.ind.) Is used to update the terminal state (see FIG. 309).
TERMINAL STATUS UPDATE resp. conf. (Terminal state update resp.conf.) Is a terminal state update req. ind. It responds to the request from (see FIG. 310).

PAGING AREA QUERY req. ind. (Paging area search req.ind.) Is used for searching for a paging area including TACF when it is recognized that the terminal is not accessing (see FIG. 311).
In the selection process, data to be searched is specified. This information element in this information flow specifies a paging area.
PAGING AREA QUERY resp. conf. (Paging area search resp.conf.) Is a paging area search req. ind. Responds to the request from (see FIG. 312).

PAGE req. ind. (Page req.ind.) Is used to start paging of TACF (see FIG. 313).
The LRCF creates a paging relationship ID. The paging relationship ID is used to correlate requests and responses.
PAGING req. ind. (Paging req.ind.) Is used to encode the mobile device in order to determine the communication path by positioning the mobile device in the network. This element is an information flow for requesting confirmation (see FIG. 314).
TACF creates a paging ID. Paging is used for response identification.

PAGING resp. conf. (Paging resp.conf.) Is used as a response to the request (see FIG. 315).
PAGE resp. conf. (Page resp.conf.) Notifies the LRCF of the paging result as a response. Upon receiving this information flow, the LRCF forcibly initializes the SLP for user authentication as a response to the user (see FIG. 316).
This information flow is also used when there is no response from the terminal. When the information element to be selected becomes unknown, it is assumed that there is no response from the terminal in response to a paging request from the network. .

Reverse Long Code Retrieval req. ind. (Uplink long code search req.ind.) Is used for uplink long code search (see FIG. 317).
Reverse Long Code Retrieval req. ind. (Uplink long code search req.ind.) Is used to search for an uplink long code (see FIG. 318).
Reverse Long Code Retrieval resp. conf. (Uplink long code search resp.conf.
) Is used to search for an upstream long code (see FIG. 319).

MRRC is a Cell Condition Measurement req. ind. Detection of cell selection information is started by (cell state detection req.ind.). This information element is an information flow for requesting confirmation, and the confirmation (that is, Cell Condition Measurement resp. Conf. (Cell state detection resp. Conf.)) Provides the detection result (see FIG. 320).
Cell Condition Measurement resp. conf. (Cell state detection resp.conf.) Is a Cell Condition Measurement req. ind. In response to a request from (cell state detection req.ind.), The detection result of the cell selection information is provided (see FIG. 321).

  In the mobile device, the cell Condition Report req. ind. (Cell state report req.ind.) Reports cell selection information. This information is used to select a radio channel. This information element is an information flow that does not require confirmation (see FIG. 322).

ADD ROUTING INFO. req. ind. (Routing information addition req.ind.) Is transmitted to LRDFp to add routing information to the subscriber profile. Sent only when an authenticated mobile device is found and the relevant information is obtained (see FIG. 323).
ADD ROUTING INFO. resp. conf. (Routing information addition resp.conf.) Is the ADD ROUTING INFO. req. ind. This is a response to (routing information addition req.ind.) (See FIG. 324).

PAGE AUTHORIZED req. ind. (Page authentication req.ind.) Is used to notify the authentication result of the terminal to TACF (see FIG. 325).
Reverse Long Code Retrieval resp. conf. (Uplink long code search resp.conf.) Is used for uplink long code search (see FIG. 326).
PAGE AUTHORIZED req. ind. (Page authentication req.ind.) Is used to notify the authentication result of the terminal to TACAF.
ROUTING INFO QUERY resp. conf. (Routing information search resp.conf.) Responds to the request (see FIG. 327).
The Routing address and TACF instance ID (address routing and TACF instance ID) are used in this case for specifying routing information. Address routing is used for routing in the base network.

SETUP req. ind. (Setup req.ind.) Is used to establish a connection (see FIG. 328).
TERMINATION ATTEMPT req. ind. (Termination trial req.ind.) Is used to request a user profile when communication continuation is required (see FIG. 329).
USER PROFILE RETRIEVAL req. ind. (User profile search req.ind.) Is used for profile search of the called user from the LRDF (see FIG. 330).
USER PROFILE RETRIVAL rep. conf. (User profile search resp.conf.) Responds to a request from the LRCF (see FIG. 331).
TERMINATION ATTEMPT resp. conf. (Termination trial resp.conf.) Responds to the request from the SSF (see FIG. 332).
SETUP req. ind. (Setup resp.conf.) Is used to establish a connection (see FIG. 333).
Proceeding req. ind. (Continue req.ind.) Reports the connection setup validity and authentication on the called side as desired, and further reports that the routing and call status is ongoing. This information flow does not require confirmation (see FIG. 334).

  The network is Measurement Condition Notification req. ind. (Status detection req.ind.) Indicates the status of detection and reporting of cell selection information in the mobile device. When the mobile device is in the idle mode, the network periodically performs the Measurement Condition Notification req. ind. (State detection req.ind.) Is instructed. When the mobile station is communicating, the network changes the Measurement Condition Notification req. ind. (State detection req.ind.) Is instructed. This information flow does not require confirmation (see FIG. 335).

REPORT req. ind. (Report req.ind) is used for reporting the status of reporting on the network and / or other types of information. Other types of information include, for example, attention, hold, hold, and release. This information flow is an information flow that does not require confirmation (see FIG. 336).
SETUP resp. conf. (Setup req.ind) is used to confirm connection establishment (see FIG. 337).
CONNECTED req. ind. (Connection req.ind) is the transmitted SETUP resp. conf. (Setup resp.conf.) Used to guarantee receipt and receipt. This information flow is an information flow that does not require confirmation (see FIG. 338).

(2.4.2.3): Call release (2.4.4.2.3.1): User-side disconnection (a) Basic model FIG. 17 shows a basic model of user-side disconnection.
(B) Information Flow FIG. 18 shows an information flow for user-side disconnection.

(C) Information flow definition RELEASE req. ind. (Release req.ind.) Is used to release resources built into call connections such as call IDs and channels. This information flow is an information flow for requesting confirmation (see FIG. 339).
RELEASE resp. conf. (Release resp.conf.) Is used for instructing the release of all the resources incorporated in the connection so far (see FIG. 340).
The TACF informs the SCF of the detection of the call release attempt using the TA RELEASE req. ind. (Release req.ind.) Is activated. This information flow is activated when the final call is released and the terminal's relationship (relationship) integration is canceled (see FIG. 341).
TERMINAL STATUS MAKE IDLE req. ind. (Terminal availability state req.ind.) Is used to make the terminal call state idle (see FIG. 342).
TERMINAL STATUS MAKE IDLE resp. conf. (Terminal free state resq.ind.) Is the TERMINAL STATUS MAKE IDLE req. ind. It responds to the request for (free terminal status req.ind.) (See FIG. 343).
TA RELEASE resp. conf. (TA release resp.conf.) Is the TA RELEASE req. ind. Used to confirm (TA release req.ind.) (See FIG. 344).

(2.4.3.2.3.2): Network-side disconnection (a) Basic model FIG. 19 is a diagram showing a basic model of network-side disconnection.
(B) Information flow FIG. 20 shows an information flow diagram of network-side disconnection.

(C) Information flow definition The information flow and the like will be described below, and the corresponding information elements and the like are shown together in a table. However, the table may be omitted if there is no corresponding element.
RELEASE req. ind. (Release req.ind.) Is used to release resources built into the call connection such as call number and channel. This flow is a flow for requesting confirmation (see FIG. 345).
RELEASE resp. conf. (Release resp.conf.) Is used to instruct the release of all resources that have been incorporated in the connection so far (see FIG. 346).
The TACF informs the LRCF of the detection of the call release attempt using the TA RELEASE req. ind. (Release req.ind.) Is activated. This information flow is activated when the final call is released and the terminal's relationship (relationship) integration is canceled (see FIG. 347).

TERMINAL STATUS MAKE IDLE req. ind. (Terminal availability state req.ind.) Is used to make the terminal call state idle (see FIG. 348).
TERMINAL STATUS MAKE IDLE resp. conf. (Terminal free state resq.ind.) Is the TERMINAL STATUS MAKE IDLE req. ind. It responds to the request for (free terminal status req.ind.) (See FIG. 349).
TA RELEASE resp. conf. (TA release resp.conf.) Is the TA RELEASE req. ind. Used to confirm (TA release req.ind.) (See FIG. 350).

(2.4.3.2.3.3): Abnormal release
(2.4.2.3.3.1): Radio link failure due to mobile station detection (Radio)
link failure-mobile detected)
(2.4.2.3.3.3.1.1): Normal Procedure Using Module (Common Procedure Modules Used)
A normal procedure using the module includes a user disconnect.

(2.4.2.3.3.3.1.2): Information Flow Diagram (Information Flow Diagram)
a) Functional model
A functional model of squelch release detected by the network is shown in FIG.
The model shown in FIG. 21 is a function model of emergency release, that is, a radio link failure detected by a mobile device.
b) Information flows
A diagram of the CC-Plane information flow in case of emergency release, that is, a radio link failure detected by the mobile station is shown in FIG.
c) Definition of information flows and information elements (Definitions of Information Flows, Information Elements)

Hereinafter, the information flow, information elements, and the like will be described in the same manner as in the rules in FIG. However, the table may be omitted if there is no corresponding element.
RADIO LINK FAILURE req. ind. (Radio link failure req.ind.) Is used for notification of a radio link failure detected by BCAF or BCFr. In this procedure, BCAF activates this information flow (see FIG. 351).
RELEASE NOTIFICATION req. ind. (Release notification req.ind.) Is used to report connection release between the network and the terminal. This information flow is an information flow that does not require confirmation (see FIG. 352).

RADIO LINK FAILURE req. ind. (Radio link failure req.ind.) Is used for notification of detection of a radio link failure (see FIG. 353).
RADIO LINK FAILURE req. ind. (Radio link failure req.ind.) Is used for notification of detection of a radio link failure (see FIG. 354).
RADIO LINK FAILURE resp. conf. (Radio link failure resp.conf.) Is RADIO LINK FAILURE req. ind. This is a confirmation information flow for (radio link failure req.ind.) (See FIG. 355).

RADIO BEARER RELEASE req. ind. (Radio bear release req.ind.) Is used for a radio bearer release request. This information flow is created by the network (see FIG. 356).
TACF is a TA RELEASE req. ind. Request release of terminal access by (radio bearer release req.ind.). This information flow is activated only when the final call is released.
TACF is BEARER RELEASE req. ind. (Bearer release req.ind.) Is activated to cause the BCF to release the bearer (see FIG. 357).
BEARER RELEASE resp. conf. (Bearer release resp.conf.) Is a confirmation information flow for the request (see FIG. 358).

Anchor TACF is BEARER RELEASE req. ind. By transmitting (Bearer Release req.ind.), The TACF in operation is requested to release the bearer that is releasing the call (see FIG. 359).
TACF is BEARER RELEASE req. ind. (Bearer release req.ind.) Is activated to release the radio bearer (see FIG. 360).
BEARER RELEASE resp. conf. (Bearer release resp.conf.) Is a confirmation information flow for the request (see FIG. 361).
TACF is BEARER & RADIO BEARER RELEASE req. ind. (Bearer and radio bearer release req.ind.) Is activated to release the bearer and radio bearer (see FIG. 362).
BEARER & RADIO BEARER RELEASE resp. conf. (Bearer and radio bearer release resp. Conf.) Is BEARER & RADIO BEARER RELEASE req. ind. It is used for confirming the release of the bearer and the radio bearer according to the request (bearer and radio bearer release req.ind.) (See FIG. 363).
BEARER RELEASE resp. conf. (Bearer release resp.conf.) Is a confirmation information flow for notifying the TACF of the completion of the radio bearer release by the previous request (see FIG. 364).
The TACF informs the LRCF of the detection of the call release attempt by using TA RELEASE req. ind. (TA release req.ind.) Is activated (see FIG. 365).

TERMINAL STATUS MAKE IDLE req. ind. (Terminal availability state req.ind.) Is used for requesting an updated user profile. In order to release the call, this information flow is used to make the call state of the user idle (see FIG. 366).
TERMINAL STATUS MAKE IDLE resp. conf. (Terminal state vacation resq.ind.) Is the TERMINAL STATUS MAKE IDLE req. ind. It responds to the request for (free terminal req.ind.) (See FIG. 367).

TA RELEASE resp. conf. (TA release resp.conf.) Is the TA RELEASE req. ind. Used for confirmation against (TA release req.ind.) (See FIG. 368).
(2.4.2.3.3.2): Radio link failure-network detected
(2.4.2.3.3.3.2.1): Normal Procedure Using Module (Common Procedure Modules Used)
A normal procedure using the module includes a user disconnect.
(2.4.2.3.3.3.2.2): Information Flow Diagram (Information Flow Diagram)

a) Functional model
FIG. 23 shows a functional model of squelch release detected by the terminal.
FIG. 23 shows a functional model in case of emergency release, that is, detection of a radio link failure by the network.

b) Information flows
FIG. 24 shows a diagram of the CC-Plane information flow in case of mobile call release, ie emergency release due to radio link failure detected by the network.

C) Definition of information flows and information elements (Definitions of Information Flows, Information Elements)
Hereinafter, the information flow and information elements will be described in the same manner as in the rules in FIG.
RADIO LINK FAILURE req. ind. (Radio link failure req.ind.) Is BCFr or BCFA. Used for radio link failure detection and report notification (see FIG. 369).
RADIO LINK FAILURE req. ind. (Radio link failure req.ind.) Is used for notification of detection of a geolink failure (see FIG. 370).
RADIO LINK FAILURE resp. conf. (Radio link failure resp.conf.) Is RADIO LINK FAILURE req. ind. This is a confirmation information flow for (radio link failure req.ind.) (See FIG. 371).

RADIO BEARER RELEASE req. ind. (Radio bearer release req.ind.) Is used for a radio bearer release request. This information flow is created by the network (see FIG. 372).
RELEASE NOTIFICATION req. ind. (Release notification req.ind.) Is used to instruct the connection release between the network and the terminal. This flow is an information flow that does not require confirmation (see FIG. 373).
RADIO BEARER RELEASE resp. conf. (Radio bearer release resp.conf.) Is a confirmation information flow for the request (see FIG. 374).

TACF is a TA RELEASE req. ind. (TA release req.ind.) Requests release of terminal access. This information flow is activated only when the final call is released.
TA RELEASE resp. conf. (TA release resp.conf.) Is a confirmation information flow for the request.
TACF is BEARER RELEASE req. ind. (Bearer release req.ind.) Is activated to release the radio bearer (see FIG. 375).
BEARER RELEASE resp. conf. (Bearer release resp.conf.) Is a confirmation information flow for the request (see FIG. 376).
Anchor TACF is BEARER RELEASE req. ind. (The bearer release req.ind.) Is transmitted to request the TACF in operation to release the bearer that is releasing the call (see FIG. 377).
TACF is BEARER RELEASE req. ind. (Bearer release req.ind.) Is activated to release the radio bearer (see FIG. 378).

BEARER RELEASE resp. conf. (Bearer release resp.conf.) Is a confirmation information flow for the request (see FIG. 379).
TACF is BEARER & RADIO BEARER RELEASE req. ind. (Bearer and radio bearer release req.ind.) Is activated to release the bearer and radio bearer (see FIG. 380).
BEARER & RADIO BEARER RELEASE resp. conf. (Bearer and radio bearer release resp. Conf.) Is BEARER & RADIO BEARER RELEASE req. ind. It is used for confirming the release of the bearer and the radio bearer by the request of (bearer and radio bearer release req.ind.) (See FIG. 381).
BEARER RELEASE resp. conf. (Bearer release resp.conf.) Is a confirmation information flow for notifying the TACF of the completion of the radio bearer release by the previous request (see FIG. 382).

RADIO BEARER RELEASE req. ind. (Radio bearer release req.ind.) Is activated in response to the radio bearer release request (see FIG. 383).
RADIO BEARER RELEASE resp. conf. (Radio bearer release resp.conf.) Is the RADIO BEARER RELEASE req. ind. It is used for confirmation of radio bearer release by request of (radio bearer release req.ind.) (See FIG. 384).
The TACF notifies the LRCF that the TA RELEASE req. ind. (TA release req.ind.) Is activated (see FIG. 385).

TERMINAL STATUS MAKE IDLE req. ind. (Terminal availability state req.ind.) Is used for a profile request of an update user. In order to release a call, this information flow is used to make the user's call state idle (see FIG. 386).
TERMINAL STATUS MAKE IDLE resp. conf. (Terminal state emptying req.ind.) Is the TERMINAL STATUS MAKE IDLE req. ind. It responds to the request for (terminal free state req.ind.) (See FIG. 387).
TA RELEASE resp. conf. (TA release resp.conf.) Is the TA RELEASE req. ind. Used for confirmation against (TA release req.ind.) (See FIG. 388).

(2.4.2.2.3.4): User disconnect
(2.4.2.3.4.1): Information flow diagram (Information flow diagram)
a) Functional model
FIG. 25 shows a functional model of user-side disconnection.
b) Information flows
FIG. 26 shows an information flow diagram of user-side disconnection.
C) Definition of information flows and information elements (Definitions of Information Flows, Information Elements)

In the following, the information flow and information elements will be described in the same manner as in FIG. 26, and the corresponding information elements and the like will be summarized in a table. However, the table may be omitted if there is no corresponding element.
CALL DISCONNECT req. ind. (Call disconnection req.ind.) Is used to notify the LRCF of disconnection on the user side (see FIG. 389).
USER PROFILE UPDATE req. ind. (User profile update req.ind.) Is used for a user profile update request. For call release, this information flow is used to indicate completion of call release (see FIG. 390).
USER PROFILE UPDATE resp. conf. (User profile update resp.conf.) Is the USER PROFILE UPDATE resp. conf. It responds to the request for (user profile update resp.conf.) (See FIG. 391).
CALL DISCONNECT resp. conf. (Call disconnection resp.conf.) Is the CALL DISCONNECT req. ind. It responds to the request (call disconnection req.ind.) (See FIG. 392).

(2.4.3): Access link control information flow (2.4.3.1): SDCCH Setup (SDCCH step-up)
The SDCCH step-up procedure will be described below.
(2.4.3.1.1): Normal Procedure Using Module (Common Procedure Modules Used)

(2.4.2.3.1.2): Information Flow Diagram (a) Functional model (Functional model)
FIG. 27 shows a functional model of SDCCH Setup (SDCCH step-up).
b) Information flows
FIG. 28 is an information flow diagram of SDCCH setup.

(2.4.2.3.1.3): Definitions of Information Flows and Information Elements (Definitions of Information Flows and Information Elements)
In the following, the information flow and information elements will be described in the same manner as in the definition in FIG. However, the table may be omitted if there is no corresponding element.

The MCF and TACF send a SIGNALING CHANNEL SETUP REQUEST req. ind. (Signal channel setup request req.ind.) Is used (see FIG. 393).
SCMAF sends a SIGNALING CHANNEL SETUP req. ind. (Signal channel setup req.ind.) Is used (see FIG. 394).
SCMF uses SIGNALING CHANNEL SETUP resp. To allocate radio resources to the signal channel. conf. (Signal channel setup resp.conf.) Is used (see FIG. 395).
SIGNALING CHANNEL SETUP REQUESTED req. ind. (Signal channel setup request req.ind.) Is used for receiving a signal channel request from the mobile terminal (detecting initial access) and for a setup request matching the signal channel in the network ( (See FIG. 396).

TACF and SACF are SIGNALING CONNECTION SETUP req. For setting up the signal connection between them and SCMF. ind. (Signal connection setup req.ind.) Is used (see FIG. 397).
SIGNALING CONNECTION SETUP resp. conf. (Signal connection setup resp.conf.
) Is used for reporting of signal channel establishment (including hardware channel and network channel) (see FIG. 398).
SCMAF uses SIGNALING CHANNEL SETUP REQUEST resp. To report signaling channel setup to the network. conf. (Signal channel setup request resp.conf.) Is used (see FIG. 399).

(2.4.3.2): Bearer Setup
Hereinafter, a bearer setup procedure for selecting a radio resource will be described.
(2.4.2.3.2.1): Normal Procedure Using Module (Common Procedure Modules Used)

(2.4.2.3.2.2): Information Flow Diagram
a) Functional model
The radio resource is selected under a BS different from the setup request call received from the mobile terminal. On the other hand, BSs are controlled by different TACFs. CCF has a relationship with only TACF. It has no relationship. TACCa controls both bearer selection and bearer setup. There are three types of BCFs, such as BCF1, BCF2, and BCFr.
FIG. 29 shows a functional model of bearer setup for radio resource selection.
b) Information flows
FIG. 30 shows a CC-Plane information flow diagram for bearer setup (radio resource selection).

(2.4.3.2.2.2.3): Definitions of Information Flows and Information Elements (Definitions of Information Flows and Information Elements)
In the following, the information flow and information elements will be described in the same manner as in FIG. 30, and the corresponding information elements and the like will be shown together in a table. However, the table may be omitted if there is no corresponding element.

BEARER SETUP req. ind. (Bearer setup req.ind.) Is used for a request to establish an access bearer from the CCF to the TACF (see FIG. 400).
IEs is a SETUP req. ind. It is a part of bearer capacity in (setup req.ind.).

  TACF selects CHANNEL SELECTION req. To select and register a radio resource capable of supporting the requested bearer capacity. ind. (Channel selection req.ind.) Is used. Such communication occurs when a new radio resource requires call setup and handover.

CHANNEL SELECTION resp. conf. (Channel selection resp.conf.) Is used for reporting radio resources registered for the TACF that requested registration (see FIG. 401).
The TACF requests a BEARER SETUP req. ind. (Bearer setup req.ind.) Is transmitted (see FIG. 402).

BEARER SETUP resp. conf. (Bearer setup resp.conf.) Is transmitted for confirming the establishment of the access bearer and for displaying the Bearer ID (bearer ID) between the BCFs (see FIG. 403).
BEARER SETUP req. ind. (Bearer setup req.ind.) Is used for a request to establish an access bearer from TACCa to TACFv (see FIG. 404).

The TACF requests a BEARER SETUP req. ind. (Bearer setup req.ind.) Is transmitted (see FIG. 405).
The BCF requests the bearer SETUP resp. conf. (Bearer setup resp.conf.) Is transmitted (see FIG. 406).
TACF requests BCFr to establish a radio bearer and a bearer establishment request between BCFs, so that BEARER & RADIO BEARER SETUP req. ind. (Bearer and radio bearer setup req.ind.) Is transmitted (see FIG. 407).

BCFr is RADIO BEARER SETUP PROCEEDING req. ind. Report the validity of the radio bearer received by (radio bearer setup procedure req.ind.) And the continuation of radio bearer establishment. This information flow does not require confirmation (see FIG. 408).
The TACF that controls the new access bearer sends a RADIO BEARER SETUP REQUEST req. ind. (Radio bearer setup request req.ind.) Is activated (see FIG. 409).

TACF requests TACAF to establish a radio bearer with RADIO BEARER SETUP req. ind. (Radio bearer setup req.ind.) Is transmitted (see FIG. 410).
TACAF uses RADIO BEARER SETUP req. To request radio bearer establishment from BCAF. ind. (Radio bearer setup req.ind.) Is transmitted (see FIG. 411).

The BCAF confirms the establishment of the radio bearer to the TACAF by using the RADIO BEARER SETUP resp. conf. (Radio bearer setup resp.conf.) Is transmitted (see FIG. 412).
BEARER & RADIO BEARER SETUP resp. conf. (Bearer and radio bearer setup resp.conf.) Is transmitted for confirmation of radio bearer establishment and completion of bearer establishment between BCFs (see FIG. 413).

BEARER SETUP resp. conf. (Bearer setup resp.conf.) Is used to confirm the completion of establishment of the access bearer (see FIG. 414).
BEARER SETUP resp. conf. (Bearer setup resp.conf.) Is used to confirm the completion of establishment of the access bearer (see FIG. 415).

(2.4.3.3): Radio bearer release
(2.4.3.1.3.1): Radio bearer release for TACF anchor approach
(2.4.3.3.1.1): Information flow diagram
a) Functional model
FIG. 31 shows a functional model of radio bearer release.
b) Information flows
FIG. 32 shows an information flow diagram for releasing a radio bearer.

(2.4.3.3.1.2): Definitions of Information Flows and Information Elements (Definitions of Information Flows and Information Elements)
In the following, the information flow and information elements will be described in the same manner as in the definition in FIG. However, the table may be omitted if there is no corresponding element.

The anchor CCF informs the anchor TACF of a call release attempt or fact detection, and to notify that the bearer associated with the call is in the process of releasing the BEARER RELEASE req. ind. (Bearer release req.ind.) Is transmitted (see FIG. 416).
TACCa uses RADIO BEARER RELEASE req. To request release of a radio bearer. ind. (Radio bearer release req.ind.) Is used. The net is RADIO BEARER RELEASE req. ind. (Radio bearer release req.ind.) Is created (see FIG. 417).
RADIO BEARER RELEASE resp. conf. (Radio bearer release resp.conf.) Is a confirmation information flow for the request (see FIG. 418).

TACCa uses a TA RELEASE req. ind. (TA release req.ind.
). This information flow is triggered only for the final call release.
TA RELEASE resp. conf. (TA release resp.conf.) Is a confirmation information flow for the request.
TACF uses BEARER RELEASE req. To release radio bearers to BCF. ind. (Bearer release req.ind.) Is activated (see FIG. 419).

BEARER RELEASE resp. conf. (Bearer release resp.conf.) Is a confirmation information flow for the request (see FIG. 420).
TACCa may request BEARER RELEASE req. For requesting bearer release for a call that is in the process of being released to TACFv. ind. (Bearer release req.ind.) Is transmitted (see FIG. 421).
TACF uses BEARER RELEASE req. To release radio bearers to BCF. ind. (Bearer release req.ind.) Is activated (see FIG. 422).
BEARER RELEASE resp. conf. (Bearer release resp.conf.) Is a confirmation information flow for the request (see FIG. 423).
TACF is used for BEARER & RADIO BEARER RELEASE req. ind. (Bearer and radio bearer release req.ind.) Are activated (see FIG. 424).
BEARER & RADIO BEARER RELEASE resp. conf. (Bearer and radio bearer release resp. Conf.) Is the BEARER & RADIO BEARER RELEASE req. ind. It is used for confirmation of bearer and radio bearer release by request of (bearer and radio bearer release req.ind.) (See FIG. 425).
BEARER RELEASE resp. conf. (Bearer release resp.conf.) Is a confirmation information flow for notifying the TACF of the completion of the request before releasing the radio bearer (see FIG. 426).
BEARER RELEASE resp. conf. (Bearer release resp.conf.) Is a confirmation information flow for notifying the CCF of the completion of the request before releasing the radio bearer (see FIG. 427).

TACAF is a RADIO BEARER RELEASE req. ind. (Radio bearer release req.ind.) Is activated (see FIG. 428).
BCAF is a RADIO BEARER RELEASE req. ind. (Radio Bearer RELEASE resp.) For confirmation of radio bearer release by request of (Radio Bearer Release req.ind.). conf. (Radio bearer release resp.conf.) Is used (see FIG. 429).

(2.4.3.4): SDCCH Release (SDCCH Release)
Hereinafter, the SDCCH release procedure will be described.
(2.4.3.1.4.1): Normal Procedure Using Module (Common Procedure Modules Used)
(2.4.3.2.4.2): Information Flow Diagram (Information Flow Diagram)
)
a) Functional model
FIG. 33 shows a functional model of SDCCH setup (SDCCH Setup). FIG. 33 shows a functional model for SDCCH release.
b) Information flows
FIG. 34 shows an information flow diagram for releasing SDCCH.
(2.4.4.3.4.3): Definitions of Information Flows and Information Elements (Definitions of Information Flows and Information Elements)

In the following, functional entity operations such as information flow are described in the same manner as in FIG. 34, and corresponding information elements and the like are shown together in a table. However, the table may be omitted if there is no corresponding element.
The MCF and the TACF request SIGNALING CHANNEL RELEASE REQUEST req. ind. (Signal channel release request req.ind.) Is used (see FIG. 430).
TACF and SACF are requested to release SIGNALING CONNECTION RELEASE req. For signaling channel (including both network and radio resources) requests. ind. (Signal connection release req.ind.) Is used (see FIG. 431).
SIGNALING CONNECTION RELEASE resp. conf. (Signal connection release resp.conf.) Is used for the signal channel release report (see FIG. 432).

(2.4.3.5): Handover (2.4.3.3.5.0): Handover process and relevant procedure modules (Handover process and relevant procedure modules)
Process 1: Handover start cause (Process 1: Handover trigger)
Detection of a handover start cause (Detection of handover triggering) is performed.
Process 2: Handover resource registration (Process 2: Handover resource reservation)
Registration of radio resources for handover (Reservation of radio resources for handover).
Process 3: Handover execution (Process 3: Handover execution)
If necessary, preparation on the network side (Preparing at network side, if any) is performed.
A request to the mobile terminal indicated as the cause of the start of handover (Request the mobile terminal as indicated by trigger) is performed.
Process 4: Completion of handover (Process 4: Handover completion)
Release unnecessary radio bearers and resources (Release of unneeded radio bearers and resources).

FIG. 35 shows a general flow of the handover process. FIG. 36 shows an information flow diagram of the handover processes 1 and 2.
FIG. 37 shows an information flow diagram showing execution of non-soft handover in handover process 1 (non-soft handover execution). FIG. 38 shows an information flow diagram showing handover branch addition in the handover process 1. Further, FIG. 39 shows an information flow diagram showing handover branch deletion in the handover process 1.

(2.4.3.5.1): Intra-cell sector branch addition handover Handover under the control of the same BCFr: (Handover controlled by the same BCFr)
(2.4.3.5.1.1): Module of common procedure (Common Procedure Modules)
(2.4.3.5.1.2): Information Flow Diagram (Information Flow Diagrams)
a) Functional model
FIG. 40 shows a functional model for adding a branch between inter-sector sectors.
b) Information Flow (Information Flow)
FIG. 41 shows a CC-Plane information flow diagram for adding an intra-cell sector branch.
(2.4.3.5.1.3): Definitions of information flows and Information Elements

Hereinafter, functional entity operations such as information flow will be described, and corresponding information elements and the like will be shown together in a table. However, the table may be omitted if there is no corresponding element.
TACFa uses BEARER SETUP req. To set up an access bearer to TACFv. ind. (Bearer setup req.ind.) Is transmitted (see FIG. 433).
This IE identifies the bearer between BCFa and BCFv.

  TACF is used for BCFr with INTRA BCFr HANDOVER BRANCH ADDITION req. ind. (The local station BCFr handover branch addition req.ind.) Is transmitted, and a setup of a new single or a plurality of hardware radio channels is requested (see FIG. 434).

  INTRA BCFr HANDOVER BRANCH ADDITION resp. conf. (The local station BCFr handover branch addition resp.conf.) Is the INTRA BCFr HANDOVER BRANCH ADDITION req. ind. It responds to (local station BCFr handover branch addition req.ind.). BCFr informs TACF of the completion of the setup of one or more hardware radio channels in INTRA BCFr HANDOVER BRANCH ADDITION resp. conf. (Own station BCFr handover branch addition resp.conf.) Is transmitted (see FIG. 435).

The base TACF that controls the newly assigned radio bearer may request RADIO BEARER SETUP REQUEST req. ind. (Radio bearer setup request req.ind.) Is transmitted (see FIG. 436).

The TACF adds a branch to the TACAF, and notifies the handover of its own BS Diversity Branch Addition Handover HANDOVER Branch Addition req. ind. (Handover branch addition req.ind.) Is transmitted and a new hardware radio channel is requested to be added to the existing hardware radio channel (see FIG. 437).
Note that * 1 is repeated for the number of terminal side handover branches, and * 2 is repeated for the number of calls on the TACF side.

TACAF is based on Handover Branch Addition resp. conf. (Handover branch addition resp.conf.) For notification of reception of HANDOVER Branch Addition resp. conf. (Handover branch addition resp.conf.) Is transmitted.
TACAF requests a radio bearer setup request from BCAF for RADIO BEARER
SETUP req. ind. (Radio bearer setup req.ind.) Is transmitted (see FIG. 438).

  RADIO BEARER SETUP resp. conf. (Radio Bearer Setup resp.conf.) Is RADIO BEARER SETUP req. ind. Respond to (Radio bearer setup req.ind.). BCAF informs TACAF that the radio bearer setup is complete, using RADIO BEARER SETUP resp. conf. (Radio bearer setup resp.conf.) Is transmitted (see FIG. 439).

(2.4.3.5.2): Inter-cell branch additional handover (2.4.3.5.2.1): Module of normal procedure (Common Procedure Modules)
(2.4.3.5.2.2): Information Flow Diagrams (Information Flow Diagrams)
a) Functional model
FIG. 42 shows a functional model for adding a branch between cells.
b) Information Flow (Information Flow)
FIG. 43 is a CC-Plane information flow diagram for adding an inter-cell branch.

(2.4.3.5.2.3): Definition of information flow and information elements
(Definitions of information flows and Information Elements)
The TACFa sends a HANDOVER CONNECTION SETUP req. ind. (Handover connection setup req.ind.) Is transmitted and an access bearer setup is requested (see FIG. 440).
This IE identifies the bearer between the CCF and BCF.

The BCF responds to TACF with a HANDOVER CONNECTION SETUP req. ind. (Handover connection setup req.ind.) For confirmation of HANDOVER CONNECTION SETUP resp. conf. (Handover connection setup resp.conf.) Is transmitted (see FIG. 441).
This IE identifies the bearer between BCFa and BCFv.
TACFa uses BEARER SETUP req. To set up an access bearer to TACFv. ind. (Bearer setup req.ind.) Is transmitted (see FIG. 442).
This IE identifies the bearer between BCFa and BCFv.

TACF sends a BEARER SETUP req. ind. (Bearer setup req.ind.) Is transmitted and a bearer setup is also requested (see FIG. 443).
This IE identifies the bearer between the BCF and CCF.

The BCF responds to the TACF with the BEARER SETUP req. ind. (BEARER SETUP resp. For bearer setup req.ind.) conf. (Bearer setup resp.conf.) Is transmitted (see FIG. 444).
This IE identifies the bearer between BCF and BCFr.

  TACF is the BEARr & RADIO BEARER SETUP req. ind. (Bearer and radio bearer setup req.ind.) And BEARER & RADIO BEARER SETUP req. ind. (Bearer and radio bearer setup req.ind.) Requests setup of a bearer between BCF and BCFr and a radio bearer (see FIG. 445).

  BEARER & RADIO BEARER SETUP resp. conf. (Bearer and radio bearer setup resp.conf.) Is the BEARER & RADIO BEARER SETUP req. ind. (Bearer and Radio Bearer Setup req.ind.), That is, BCFr will notify TACF of the completion of the radio bearer setup and the bearer setup completion between BCFr and BCF to BEARER & RADIO BEARER SETUP rep . conf. (Bearer and radio bearer setup resp.conf.) Is transmitted (see FIG. 446).

  The base TACF that controls the newly allocated radio bearer sends a radio bearer setup request between the mobile terminal and the BCFr under the control of the base TACF to the TACFa in the RADIO BEARER SETUP REQUEST req. ind. (Radio bearer setup request req.ind.) Is transmitted (see FIG. 447).

TACF notifies HANDOVER BRANCH ADDITION req. ind. (Handover branch addition req.ind.) Is transmitted, and HANDOVER BRANCH ADDITION req. ind. (Add handover branch req.ind.) Requests the setup of a new hardware radio channel without releasing the existing hardware radio channel or channels (see FIG. 448).
Note that * 1 is repeated as many times as the number of called cells, and * 2 is repeated as many times as the number of calls related to TACF.

TACAF is a Handover Branch Addition initiation req. ind. (Handover branch addition initialization req.ind.) For notification of reception of HANDOVER BRANCH ADDITION resp. conf. (Handover branch addition resp.conf.) Is transmitted.
TACAF uses BCAD with RADIO BEARER SETUP req. ind. (Radio Bearer Setup req.ind.) Is transmitted and RADIO BEARER SETUP req. ind. (Radio bearer setup req.ind.) Requests setup of a radio bearer (see FIG. 449).

RADIO BEARER SETUP resp. conf. (Radio Bearer Setup resp.conf.) Is the RADIO BEARER SETUP req. ind. In response to (Radio Bearer Setup req.ind.), BCAF notifies RADIO BEARER SETUP resp. conf. (Radio bearer setup resp.conf.) Is transmitted (see FIG. 450).
TACFa uses BEARER SETUP resp. To guarantee access bearer establishment to TACFv. conf. (Bearer setup resp.conf.) Is transmitted (see FIG. 451).

(2.4.5.3): Intra-cell sector branch deletion handover
Handover under the control of the same BCFr
(Handover controlled by the same BCFr)
(2.4.3.5.3.1): Normal procedure module
(Common Procedure Modules)
(2.4.3.5.3.2): Information flow diagram
(Information Flow Diagram)
a) Functional model
FIG. 44 shows a functional model of intra-sector inter-sector branch deletion handover (handover branch deletion).
b) Information Flow (Information Flow)
FIG. 45 shows a CC-Plane information flow diagram of the intra-cell sector branch deletion handover.

(2.4.3.5.3.3): Definitions of information flows and Information Elements
TACF responds to TACAF with HANDOVER BRANCH DELETION req. ind. (Handover branch deletion req.ind.) Is transmitted, and HANDOVER BRANCH DELETION req. ind. (Delete Handover Branch req.ind.) Requests release of single or multiple hardware radio channels (see FIG. 452).
Note that * 1 may be repeated by the number of handover branches related to the terminal.
* 2 is repeated for the number of calls related to the terminal.

  The Handover branch ID (handover branch ID) is used for specifying (only one) the transport route of the access radio link.

TACAF is a HANDOVER BRANCH DELETION req. ind. (Handover branch deletion req.ind.) For confirmation of HANDOVER BRANCH DELETION resp. conf. (Handover branch deletion resp.conf.) Is transmitted (see FIG. 453).
TACFa uses BEARER RELEASE req. To release an access bearer to TACFv. ind. (Bearer release req.ind.) Is transmitted (see FIG. 454).
The TACF may request an INTRA BCFr HANDOVER BRANCH DELETION req. ind. (Own station BCFr handover branch deletion req.ind.) Is transmitted (see FIG. 455).
This IE is included when the BCFr transmits this IF to the TACF.

INTRA BCFr HANDOVER BRANCH DELETION resp. conf. (The local station BCFr handover branch deletion resp.conf.) Is the INTRA BCFr HANDOVER BRANCH DELETION req. ind. In response to the local station BCFr handover branch deletion req.ind. conf. (Own station BCFr handover branch deletion resp.conf.) Is transmitted (see FIG. 456).
TACFv is a BEARER RELEASE req. ind. (BEARER RELEASE resp.) For confirmation of (bearer release req.ind.). conf. (Bearer release resp.conf.) Is transmitted (see FIG. 457).

(2.4.3.5.5.4): Inter-cell branch deletion handover (2.4.3.5.4.1): Module for normal procedure (Common Procedure Modules)
(2.4.3.5.4.2): Information Flow Diagram (Information Flow Diagram)
a) FIG. 46 shows a functional model of an intra-cell branch deletion handover.
b) FIG. 47 shows a CC-Plane information flow diagram of intra-cell branch deletion handover.

(2.4.3.5.4.3): Definitions of information flows and information elements (Definitions of information flows and Information Elements)
In the following, functional entity operations such as information flow are described, and corresponding information elements are summarized in a table. However, the table may be omitted if there is no corresponding element.

TACF responds to TACAF with HANDOVER BRANCH DELETION req. ind. (Handover branch deletion req.ind.) Is transmitted, and HANDOVER BRANCH DELETION req. ind. (Delete Handover Branch req.ind.) Requests release of one or more hardware radio channels (see FIG. 458).
Note that * 1 may be repeated by the number of handover branches related to the terminal.
* 2 is repeated for the number of calls related to the terminal. The Handover branch ID (handover branch ID) is used for specifying (only one) the transport route of the access radio link.

TACAF is a HANDOVER BRANCH DELETION req. ind. (Handover branch deletion req.ind.) For confirmation of HANDOVER BRANCH DELETION resp. conf. (Handover branch deletion resp.conf.) Is transmitted (see FIG. 459).
TACAF sends a RADIO BEARER RELEASE req. ind. (Radio bearer release req.ind.) Is transmitted (see FIG. 460).

RADIO BEARER RELEASE resp. conf. (Radio bearer release resp.conf.) Is the RADIO BEARER RELEASE req. ind. In response to (Radio Bearer Release req. conf. (Radio bearer release resp.conf.) Is transmitted (see FIG. 461).
The TACF removes the designated bearer in the diversity handover state with respect to the BCF. ind. (Handover connection release req.ind.) Is transmitted (see FIG. 462).

The BCF is connected to the TACF with the HANDOVER CONNECTION RELEASE req. ind. (Handover connection release req.ind.) For confirmation of HANDOVER CONNECTION RELEASE resp. conf. (Handover connection release resp.conf.) Is transmitted (see FIG. 463).
TACFa uses BEARER RELEASE req. To release an access bearer to TACFv. ind. (Bearer release req.ind.) Is transmitted (see FIG. 464).
The TACF requests BEARER RELEASE req. ind. (Bearer release req.ind.) Is transmitted (see FIG. 465).
BCF is a BEARER RELEASE req. ind. (BEARER RELEASE resp.) For confirmation of (bearer release req.ind.). conf. (Bearer release resp.conf.) Is transmitted (see FIG. 466).

The TACF sends a BEARR & RADIO BEARER RELEASE req. Request to the BCFr for a request to release the bearer between the BCF and the BCFr and a request to release the radio bearer. ind. (Bearer and radio bearer release req.ind.) Are transmitted (see FIG. 467).
This IE is included when the BCFr transmits this IF to the TACF.

BEARER & RADIO BEARER RELEASE resp. conf. (Bearer and radio bearer release resp. Conf.) Is the BEARER & RADIO BEARER RELEASE req. ind. (Bearer and radio bearer release req.ind.), BCFr notifies TACF that the bearer and radio bearer release has been completed. conf. (Bearer and radio bearer release resp.conf.) Are transmitted (see FIG. 468).
TACFv is the BEARER RELEASE req. ind. (BEARER RELEASE resp.) For confirmation of (bearer release req.ind.). conf (bearer release resp.conf.) is transmitted (see FIG. 469).

(2.4.3.5.5): Intra-cell branch switching handover (2.4.3.5.5.1): Module of common procedure (Common Procedure Modules)
(2.4.3.5.5.2): Information Flow Diagrams (Information Flow Diagrams)
a) Functional model
FIG. 48 shows a functional model for the intra-cell branch switching handover.
b) Information Flow (Information Flow)
FIG. 49 shows a CC-Plane information flow diagram of intra-cell branch switching handover.

(2.4.3.5.5.3): Definition of Information Flows and Information Elements Definitions of information flows and Information Elements)
In the following, functional entity operations such as information flow are described, and corresponding information elements are summarized in a table. However, the table may be omitted if there is no corresponding element.
TACFa uses BEARER SETUP req. To set up an access bearer to TACFv. ind. (Bearer setup req.ind.) Is transmitted (see FIG. 470).
This IE is a BCFa and BCFv. Identify bearers between.

TACF is the same as BCFr for INTRA BCFr HANDOVER BRANCH REPLACEMENT req. ind. (Own station BCFr handover branch switching req.ind.) Is transmitted, and INTRA BCFr HANDOVER BRANCH REPLACEMENT req. ind. (Own station BCFr handover branch switching req.ind.) Requests the setup of a new single or multiple hardware radio channels.

INTRA BCFr HANDOVER BRANCH REPLACEMENT resp. conf. (Local station BCFr handover branch switching resp.conf.) Is the above-mentioned INTRA BCFr HANDOVER BRANCH REPLACEMENT req. ind. In response to (local station BCFr handover branch switching req.ind.), BCFr transmits to TACF to notify the completion of setup of one or more hardware radio channels (see FIG. 471).
Note that * 1 may be repeated for the number of radio links to be set up.

The BCFr informs the TACF of the approval of the handover branch switching request by using the INTRA BCFr HANDOVER BRANCH REPLACEMENT PROCEEDING req. ind. (Own station BCFr handover branch switching procedure req.ind.) Is transmitted (see FIG. 472).
The base TACF that controls the newly assigned radio bearer sends a RADIO BEARER SETUP REQUEST req. ind. (Radio bearer setup request req.ind.) Is transmitted (see FIG. 473).

TACF notifies NON-SOFT HANDOVER EXECUTION req. ind. (Non-soft handover execution req.ind.) Is transmitted. NON-SOFT HANDOVER EXECUTION req. ind. (Non-soft-over execution req.ind.) Requests switching from an existing hardware radio channel to a designated hardware radio channel (see FIG. 474).
Note that * 1 is repeated for the number of handover branches for the terminal, and * 2 is repeated for the number of calls for TACF.

TACAF sends a RADIO BEARER SETUP req. ind. (Radio bearer setup req.ind.) Is transmitted (see FIG. 475).
RADIO BEARER SETUP resp. conf. (Radio Bearer Setup resp.conf.) Is the RADIO BEARER SETUP req. ind. In response to (Radio Bearer Setup req.ind.), BCAF notifies RADIO BEARER SETUP resp. conf. (Radio bearer setup resp.conf.) Is transmitted (see FIG. 476).

TACAF sends a RADIO BEARER RELEASE req. ind. (Radio bearer release req.ind.) Is transmitted (see FIG. 477).
RADIO BEARER RELEASE resp. conf. (Radio bearer release resp.conf.) Is the RADIO BEARER RELEASE req. ind. In response to (radio bearer release req.ind.), BCAF transmits to TACAF to notify the radio bearer release completion (see FIG. 478).
TACFa uses BEARER SETUP resp. To confirm the establishment of an access bearer to TACFv. conf. (Bearer setup resp.conf.) Is transmitted (see FIG. 479).

(2.4.3.55.6): Inter-cell branch switchover handover
(2.4.3.5.6.1): Modules for normal procedures (Common Procedures Modules)
(2.4.3.5.6.2): Information Flow Diagrams (Information Flow Diagrams)
a) Functional model
FIG. 50 shows a functional model of the inter-cell branch switchover handover.
b) Information Flow (Information Flows)
FIG. 51 shows a CC-Plane information flow diagram of inter-cell diversity handover.

(2.4.3.5.6.3): Definitions of Information Flows and Associated Information Elements Below, information flows are described, and corresponding information elements are summarized in a table. Show. However, the table may be omitted if there is no corresponding element.

The TACFa sends a HANDOVER CONNECTION SETUP req. ind. (Handover connection setup req.ind.) Is transmitted. HANDOVER CONNECTION SETUP req. ind. (Handover connection setup req.ind.) Requests setup of a new handover link (see FIG. 480).
Note that this IE is mandatory when the network has more than one handover mode.

The BCF responds to TACF with the HANDOVER CONNECTION SETUP req. ind. (Handover connection setup req.ind.) For confirmation of HANDOVER CONNECTION SETUP resp. conf. (Handover connection setup resp.conf.) Is transmitted (see FIG. 481).
This IE is a BCFa and BCFv. Identify bearers between.

TACCa uses BEARER SETUP req. To set up a handover link to TACFv. ind. (Bearer setup req.ind.) Is transmitted (see FIG. 482).
This IE is a BCFa and BCFv. Identify bearers between. A new FE may be provided for the link transition between BCFa and BCFv. The individual BCF link is referred to as FFS.

TACF sends a BEARER SETUP req. ind. (Bearer setup req.ind.) Is transmitted. BEARER SETUP req. ind. (Bearer setup req.ind.) Requests a new handover link on the network side (see FIG. 483).
This IE identifies the link between BCFa and BCFv. A new FE may be provided for link transition between BCFa and BCFv. The individual BCF link is referred to as FFS.

BCF sends the SETUP req. ind. (BEARER SETUP resp.) For confirmation of (bearer setup req.ind.). conf. (Bearer setup resp.conf.) Is transmitted (see FIG. 484).
This IE identifies the link between BCF and BCFr. A new FE may be provided for the link transition between BCFa and BCFv. The individual BCF link is referred to as FFS.

  TACF is the BEARr & RADIO BEARER SETUP req. ind. (Bearer and radio bearer setup req.ind.). BEARER & RADIO BEARER SETUP req. ind. (Bearer and radio bearer setup req.ind.) Requests bearer setup between BCF and BCFr, and setup of radio bearer (see FIG. 485).

  The BCFr notifies the TACF of the approval of the access radio link setup and the start of the access radio link setup in the BCFr with the RADIO BEARER SETUP PROCEEDING req. ind. (Radio bearer setup procedure req.ind.) Is transmitted (see FIG. 486).

  The base TACF that controls the newly allocated access radio link receives the RADIO BEARER SETUP REQUEST req. Request for the access radio link setup request between the mobile terminal and the BCFr under the control of the base TACF. ind. (Wireless bearer setup request req.ind.) Is transmitted (see FIG. 487).

TACF notifies NON-SOFT HANDOVER EXECUTION req. ind. (Non-soft handover execution req.ind.) Is transmitted. NON-SOFT HANDOVER EXECUTION req. ind. (Non-soft handover execution req.ind.) Requests switching from an existing hardware radio channel to a designated hardware radio channel (see FIG. 488).
Note that * 1 is repeated for the number of handover branches for the terminal, and * 2 is repeated for the number of calls for TACF.

TACAF uses BCAD with RADIO BEARER SETUP req. ind. (Radio Bearer Setup req.ind.) Is transmitted and RADIO BEARER SETUP req. ind. (Radio bearer setup req.ind.) Requests setup of an access radio link (see FIG. 489).
RADIO BEARER SETUP resp. conf. (Radio Bearer Setup resp.conf.) Is the above-mentioned RADIO BEARER SETUP req. ind. In response to (Radio bearer setup req.ind.), BCAF notifies TACAF that the access radio link setup is complete. conf. (Radio bearer setup resp.conf.) Is transmitted (see FIG. 490).

TACAF sends a RADIO BEARER RELEASE req. ind. (Radio bearer release req.ind.) Is transmitted (see FIG. 491).
RADIO BEARER RELEASE resp. conf. (Radio bearer release resp.conf.) Is the RADIO BEARER RELEASE req. ind. In response to (radio bearer release req.ind.), BCAF notifies TACAF that the access radio link has been released. conf. (Radio bearer release resp.conf.) Is transmitted (see FIG. 492).

  BEARER & RADIO BEARER SETUP resp. conf. (Bearer and radio bearer setup resp.conf.) Is the BEARER & RADIO BEARER SETUP req. ind. BCFr responds to (bearer and radio bearer setup req.ind.) To notify TACF that the access radio link setup is complete and for the link setup completion between BCFr and BCF BEARER & RADIO BEARER SETUP resp. conf. (Bearer and radio bearer setup resp.conf.) Are transmitted (see FIG. 493).

TACFa confirms the establishment of a handover link with TACFv by using BEARER SETUP resp. conf. (Bearer setup resp.conf.) Is transmitted (see FIG. 494).
The TACF removes the handover link instructed to BCFA by using HANDOVER CONNECTION RELEASE req. ind. (Handover connection release req.ind.) Is transmitted (see FIG. 495).

BCF responds to TACF with HANDOVER CONNECTION RELEASE req. ind. (HANDOVER CONNECTION RELEASE resp.) For confirmation of (handover connection release req.ind.). conf. (Handover connection release req.ind.) Is transmitted (see FIG. 496).
TACFa uses BEARER RELEASE req. To release the handover link on the network side with respect to TACFv. ind. (Bearer release req.ind.) Is transmitted (see FIG. 497).
TACF sends a BEARER RELEASE req. Request to BCF to release a handover link on the network side. ind. (Bearer release req.ind.) Is transmitted (see FIG. 498).
BCF is a BEARER RELEASE req. ind. (BEARER RELEASE resp.) For confirmation of (bearer release req.ind.). conf. (Bearer release resp.conf.) Is transmitted (see FIG. 499).
The TACF requests the BCFr to release the access link, or to release the handover link between the BCF and the BCFr, or to release the handover link between the BCAF and the BCFr. ind. (Bearer and radio bearer release req.ind.) Are transmitted (see FIG. 500).
This IE is included when this IF is transmitted from the BCFr to the TACF.

BEARER & RADIO BEARER RELEASE resp. conf. (Bearer and Radio Release req.ind.) Is BEARER & RADIO BEARER RELEASE req. ind. (Bearer and radio bear release req. conf. (Bearer and radio release req.ind.) Is transmitted (see FIG. 501).
TACFv is a confirm bearer RELEASE req. ind. (BEARER RELEASE resp.) For confirmation of (bearer release req.ind.). conf. (Bearer release resp.conf.) Is transmitted (see FIG. 502).

(2.4.3.55.7): ACCH switching FIG. 790 shows an example of the trigger of ACCH switching assumed in the present system. In FIG. 790, the service control station 1 is connected to a public line network (not shown) and controls a plurality of exchange stations 2a and 2b (although there are two in the example shown). The exchanges 2a and 2b have a plurality of lines with the corresponding base station control stations 3a and 3b. The base station control station 3a controls the base stations 6a to 6d, and the base station control device 3b controls the base stations 6e to 6h. Each of the base stations 6a to 6h forms radio zones 5a to 5f that are areas where radio communication with the mobile station device 6 is possible. The mobile station device 7 is located in one of these wireless zones and can communicate with the base station.

  In FIG. 790, the mobile station device 7 is located in the radio zone 5b, for example, and performs a plurality of communications with the base station 6d corresponding to the radio zone 5b via a plurality of traffic channels TCH. And In this case, there may be an ACCH using the same radio physical channel in each traffic channel used for transfer of communication contents.

  In such a case, in this system, as already described in the section (2.2.2), an arbitrary one (for example, ACCH1 in the figure) is selected from a plurality of ACCHs, and the mobile station All control signals associated with the device 7 can be transmitted and received on its ACCH. As a result, the hardware required for transmission / reception can be reduced compared to the case where all of the ACCH is supported by a plurality of radio resources, and the control signal transmission order is adjusted between the plurality of ACCHs. It is also possible to omit the control.

  By the way, in such a communication system, when the radio resources using the ACCH are released along with the release of the TCH due to the end of each communication, it is difficult to continuously secure the ACCH for other calls. A similar problem occurs when changing the transmission rate required for ACCH.

  That is, when the radio resources using the ACCH are released with the release of each connection or the connection corresponding to the release of the call, the ACCH is continued for another call. When secure allocation is required or when the transmission rate required for the ACCH is changed, the ACCH needs to be switched.

  Therefore, in the present system, when one mobile station apparatus 7 allows simultaneous communication of a plurality of calls, shares the ACCH associated with each TCH, and releases the radio resources using the ACCH, the ACCH Is switched to another radio channel.

(2.4.3.5.7.2): Information Flow Diagrams (Information Flow Diagrams)
a) Functional model
FIG. 52 shows functional entities related to ACCH switching. As shown in FIG. 52, these functional entities are roughly classified into functional entities arranged on the mobile station apparatus side and functional entities arranged on the network side including the base station. The location of these functional entities and their functions will be briefly described below.

  First, CCFA (Call Control Function) is arranged in one of the exchanges 2a and 2b in FIG. This CCFA is a function entity that controls call / connection. Note that a is an abbreviation of “anchor”, which means that it is installed at the start of communication and is fixed even if the mobile station device 6 moves.

  In one of the base station control stations 3a and 3b, a TACFa (Terminal Access Control Function) and a BCFA (Bearer Control Function) are arranged. Here, TACCa is a functional entity that controls access to the mobile station apparatus 7 from the network side and instructs activation and release of the ACCH. BCa (Bearer Control Function) is a functional entity that controls a bearer. Note that a is an abbreviation of “anchor” as described above.

  Next, TACFv and BCFv are arranged in one of the base station control stations 3a and 3b that are the same as or different from the base station control station in which TACCa and BCFa are arranged. Here, v is an abbreviation for visited.

  Next, BCFr (Bearer Control Function radio bearer associated) is arranged in one of the base stations 4a to 4h under the control of the base station control station in which TACFv and BCFv are arranged. This BCFr controls the radio bearer and activates and releases the ACCH.

  Further, TACAF (Terminal Access Control Agent Function) and BCAF (Bearer Control Agent Function) are arranged in the mobile station device 6. Here, TACAF is a function entity that controls access to the mobile station apparatus and instructs release, setting, etc. of ACCH. BCAF is a functional entity that controls the radio bearer of the mobile station apparatus, and executes release and setting of ACCH.

In addition, although the number “1” or “2” is added to the end of each functional entity, the one with the number “1” is the first among a plurality of communications performed by the mobile station device 7. The function entity corresponding to the second communication (hereinafter referred to as the first call communication), and the one with the numeral “2” is the second communication among the plurality of communication performed by the mobile station device 7 ( Hereinafter, it is a function entity corresponding to communication of the second call).
b) Information Flow (Information Flows)
53 and 54 show AC-CH switching CC-Plane information flow diagrams.

(2.4.3.5.7.3): Definitions of Information Flows and Associated Information Elements (Definitions of Information Flows and Associated Information Elements)
In the following, functional entities such as information flow are described, and corresponding information elements are summarized in a table. However, the table may be omitted if there is no corresponding element.

<Switching of ACCH>
Next, the ACCH switching procedure will be described in detail with reference to the sequence diagrams of FIGS. 53 and 54.
The sequence diagram of FIGS. 53 and 54 assumes the following situation.
a. Initially, the mobile station apparatus used the traffic channels TCH1 and TCH2 to perform communications for the first call and the second call.
b. Thereafter, communication of the first call using the traffic channel TCH1 was completed.
c. At this time, ACCH1 is set to the same radio resource as traffic channel TCH1 used for communication of the first call, and until the communication of the first call is completed, the first call and the first call are transmitted via this ACCH1. Control information for maintaining communication of two calls has been exchanged.
d. The traffic channel TCH1 is released with the end of communication of the first call, but thereafter, the ACCH is necessary to continue using the traffic channel TCH2. Therefore, it is necessary to switch the ACCH from ACCH1 to ACCH2 associated with the traffic channel TCH2 for communication of the second call.

  That is, FIGS. 53 and 54 assume the same situation as the ACCH switching operation of FIG. 262, and the ACCH is transferred from the radio bearer between BCAF1-BCCFr1 corresponding to the first call to between BCAF2-BCCFr2 corresponding to the second call. The operation sequence for switching to the radio bearer is shown in more detail than FIG.

  First, when the above conditions a to d occur and TACCa recognizes an opportunity for switching the ACCH, the TACCa determines the connection to which the ACCH is to be transferred, and notifies the BCFA of the initialization of the handover. Therefore, Handover Connection Setup req. ind. (Handover connection setup req.ind.) Is transmitted.

  This handover connection setup req. ind. Is a request for setting up ACCH, and its IE (Information Elements: information element) is a relation ID between BCF and TACF, a base station ID, and a handover mode as shown in FIG. 503. In FIGS. 503 to 523, M is an abbreviation for Mandatory and means essential, and O is an abbreviation for Optional and means optional. The handover mode shown in FIG. 503 is essential when the network has one or more handover modes.

  In FIG. 53, BCFA captures the DHT for ACCH, and then transfers the previous handover connection setup req. ind. For confirmation of Handover Connection Setup resp. conf. (Handover connection setup resp.conf.) Is returned. This handover connection setup resp. conf. As shown in FIG. 504, the IE is the relationship ID between the TACF and the BCF, and the bearer ID (between the BCF and BCF). Here, the bearer ID identifies the bearer between BCFA-BCFv.

  The TACFa transmits a Bearer Setup req. For setting up an access bearer to the ACCH to the TACFv2 corresponding to the communication of the second call. ind. (Bearer setup req.ind.) Is transmitted. This bearer setup req. ind. As shown in FIG. 505, the IE is a relationship ID between TACF and TACF, a bearer ID (between BCF and BCF), a base station ID, and a user / information / rate. Here, the bearer ID identifies the bearer between BCFA-BCFv.

  TACFv2 sets the short cell connection to the base station for ACCH, extracts the link reference having the same value as the associated TCH (in this case, traffic channel TCH2 for communication of the second call), and then to BCFv2 , Bearer Setup req. ind. (Bearer setup req.ind.) Is transmitted.

  This bearer setup req. ind. Is a request for bearer setup for ACCH (in this case, ACCH2 associated with traffic channel TCH2), and for its IE, as shown in FIG. 506, the relationship ID, bearer ID (TACF-BCF) BCF-BCF), base station ID, user / information / rate. Here, bearer ID is ID for identifying the bearer between BCFA-BCFv.

  Next, BCFv2 performs the bearer setup req. ind. Is received, the requested bearer is set up and the previous bearer setup req. ind. Bearer Setup resp. conf. (Bearer setup resp.conf.) Is returned. This bearer setup resp. conf. As shown in FIG. 507, the IE is the relationship ID and bearer ID (between BCF and BCFr) between TACF and BCF. Here, the bearer ID identifies the bearer between BCF and BCFr.

  Next, TACFv2 performs the bearer setup resp. conf. Is received to BCFr2, BEARER & RADIO Bearer Setup req. ind. (Bearer and radio bearer setup req.ind.).

  Here, bearer and radio bearer setup req. ind. Is a request for setting up a bearer between BCF and BCFr and setting up a radio bearer for ACCH. As shown in FIG. 508, the IE is a relationship ID and bearer ID between TACF and BCFr. is there.

  Receiving this, the BCFr2 specifies the corresponding TCH (in this case, the traffic channel TCH2) by the link reference, and starts transmitting the ACCH.

  After this, BCFr2 transfers to TACFv2, Radio Bearer Setup Proceeding req. ind. (Radio bearer setup procedure req.ind.) Is transmitted. This radio bearer setup procedure req. ind. Indicates that the TACF has accepted the radio bearer setup request and that the BCFr has begun setting up the radio bearer for the ACCH, the IE of which is shown in FIG. Thus, the relationship ID is TACF-BCFr.

  This radio bearer setup procedure req. ind. The TACFv2 that has received the message is sent to the TACFa, Radio Bearer Setup Request req. ind. (Radio bearer setup request req.ind.) Is transmitted. This radio bearer setup request req. ind. Is for the TACFa to control the newly assigned radio bearer in order to request the radio bearer setup for ACCH between the mobile station apparatus and the BCFr under the control of TACFv. 510, the relationship ID between TACF and TACF.

  Next, TACCa transfers to TACAF, Radio Bearer Setup req. ind. (Radio bearer setup req.ind.) Is transmitted. This radio bearer setup req. ind. Notifies the ACCH switching handover execution initialization and switches from the existing physical radio channel (physical radio channel corresponding to the first call) to the designated physical radio channel (physical radio channel corresponding to the second call). The IE is a request ID, as shown in FIG.

  On the other hand, this req. ind. As shown in FIG. 54, the TACAF that has received the data is transferred to BCAF2, and a radio bearer setup req. ind. (Radio bearer setup req.ind.) Is transmitted. This radio bearer setup req. ind. Is a request for setting up a radio bearer for ACCH (in this case, ACCH2), and the IE is a relation ID between TACAF and BCAF as shown in FIG.

  This req. ind. The BCAF 2 having received the new ACCH is set, and then the TACAF is sent to the Radio Bearer Setup resp. conf. (Radio bearer setup resp.conf.) Is returned. This radio bearer setup resp. conf. Is for notifying TACAF of completion of radio bearer setup for ACCH, and the IE is a relation ID between TACAF and BCAF as shown in FIG.

  Then, the TACAF sends a radio bearer setup resp. Indicating that the radio bearer setup to the ACCH (ACCH2 in this case) is completed to the TACCa. conf. (Radio bearer setup resp.conf.) Is transmitted. The radio bearer setup resp. conf. The IE of TAC is a relation ID between TACAF and BCAF, as in FIG.

  Next, TACAF moves to BCAF1, Radio Bearer Release req. ind. (Radio bearer release req.ind.) Is transmitted. This radio bearer release req. ind. Is a request for releasing a radio bearer, and its IE is a relation ID between TACAF and BCAF, as shown in FIG. 514.

  This req. ind. The BCAF 1 that has received the radio releases the ACCH used (in this case, the ACCH 1 associated with the traffic channel TCH 1), and then, to the TACAF, the Radio Bearer Release resp. conf. (Radio bearer release resp.conf.) Is returned. This radio bearer release resp. conf. As shown in FIG. 515, the IE is the relationship ID between TACAF and BCAF.

  On the other hand, the radio bearer setup resp. conf. The TACCa that has received the message is sent to the BCFa, the Handover Connection Release req. ind. (Handover connection release req.ind.) Is transmitted. This handover connection release req. ind. Is for deleting a bearer in a soft handover state, and the IE is a relationship ID between TACF and BCF and a bearer ID to be released as shown in FIG.

  This req. ind. The BCFA that received the request releases the old DHT, and then transfers the previous handover connection release req. Handover Connection Release resp. for confirming ind. conf. (Handover connection release resp.conf.) Is returned. This handover connection release resp. conf. As shown in FIG. 517, the IE is the relationship ID between TACF and BCF.

  Next, TACCa moves to TACFv1, Bearer Release req. ind. (Bearer release req.ind.) Is transmitted. This bearer release req. ind. Requests release of the bearer that has been accessing TACFv1, and the IE is a relationship ID between TACF and TACF as shown in FIG.

  This bearer release req. ind. The TACFv1 that has received the message is transferred to the Bearer Release req. ind. (Bearer release req.ind.) Is transmitted. This bearer release req. ind. Requests release of the bearer that has been accessing TACFv1, and the IE is a relationship ID between TACF and BCF as shown in FIG.

  This bearer release req. ind. The BCFv1 that has received the request transmits to the TACFv1 the previous bearer release req. ind. Bearer Release resp. conf. (Bearer release resp.conf.) Is returned to release the old resource. This bearer release resp. conf. As shown in FIG. 520, the IE is the relationship ID between TACF and BCF.

  The resp. conf. The TACFv1 that has received the message is transferred to BCFr1 with BEARER & RADIO Bearer Release req. ind. (Bearer and radio bearer release req.ind.) Are transmitted. This bearer and radio bearer release req. ind. Requests release of the bearer between BCF and BCFr and the radio bearer, and the IE is the relationship ID and Cause between TACF and BCFr as shown in FIG. The Cause is included when this IE is transmitted from the BCFr to the TACF.

  Meanwhile, bearer and radio bearer release req. ind. The BCFr1 that has received the transmission stops transmission, and then transfers to the TACFv1 to the BEARER & RADIO Bearer Release resp. conf. (Bearer and radio bearer release resp.conf.) Is returned to release the old resource. This bearer and radio bearer release resp. conf. Is the previous bearer and radio bearer release req. This is a response to ind and indicates that the release of the bearer and the radio bearer has been completed. The IE is a relation ID between TACF and BCFr as shown in FIG.

  And this resp. conf. The TACFv1 that has received the request has received the previous bearer release req. ind. In order to confirm the above, Bearer Release resp. conf. (Bearer release resp.conf.) Is transmitted. This resp. conf. As shown in FIG. 523, the IE is the relationship ID between TACF and TACF.

  Note that, in the above ACCH switching procedure, in order to simplify the description, the operation when the mobile station apparatus 6 is performing diversity handover is not considered. Here, when the mobile station apparatus 7 (see FIG. 790) performs diversity handover, a functional entity corresponding to the above TACFv1, BCFv1, TACFv2, BCFv2, BCFr1, BCFr2 is a base station to which a diversity handover branch is set. Located in each of the control station and the base station, the TACCa controls all of them in the same manner as the contents shown in FIGS. 53 and 54, and performs control channel switching in the diversity handover. In this case, the procedure between TACCa and TACAF is executed for all branches together.

  According to such an ACCH switching procedure, the access wireless link between the mobile station apparatus and the network is switched by newly setting an access wired link from the base station control station to which the TACFA is arranged to the base station. , ACCH replacement is performed.

<ACCH switching (when not switching access wired link)>
By the way, the ACCH switching procedure described above is to newly set an access wired link and switch the ACCH, but it is also possible to switch the ACCH without setting a new access wired link.
Since details have already been described with reference to FIGS. 53 and 54, they will be briefly described here.

  First, in FIG. 791, when an opportunity to switch the ACCH occurs, the TACCa detects that fact, determines the connection to be the ACCH transfer destination, and then instructs the TACFv2 to be the transfer destination to set the ACCH. . In response to this, TACFv2 further instructs BCFr2 to set the ACCH. As a result, the BCFr2 newly sets the ACCH and starts its transmission, and then returns a notification to that effect to the TACFv2. The TACFv2 that has received this return notifies the TACFa that the setting of the new ACCH has been completed. Receiving this notification, the TACCa this time, in the same way as the procedure shown in FIG. 53 and FIG. ind. Send. As a result, BCAF2 sets a new ACCH, while BCAF1 releases the existing ACCH. Then, TACAF notifies TACCa to that effect.

  On the other hand, the TACFa that has received this notification instructs the TACFv1 to release the ACCH. Upon receiving this, TACFv1 further instructs BCFr1 to release the ACCH. As a result, the BCFr1 releases the existing ACCH and stops its transmission, and then returns a notification to that effect to the TACFv1. The TACFv2 that has received this return notifies the TACFa that the release of the existing ACCH has been completed.

  According to such a procedure, since ACCH is switched by a functional entity as shown in FIG. 791, an access wired link on the network side is not set.

(2.4.3.5.5.8): Code switching (2.4.3.5.8.2): Information flow diagram (Information Flow Diagrams)
a) Functional model
FIG. 55 shows a functional model for function switching for code switching.
b) Information Flow (Information Flows)
FIG. 56 shows a CC-Plane information flow diagram for code switching.

(2.4.3.5.8.3): Definitions of Information Flows and Associated Information Elements (Definitions of Information Flows and Associated Information Elements)
The information flow and the like will be described below, and the corresponding information elements and the like are shown together in a table. However, the table may be omitted if there is no corresponding element.
Since the BCFr requests the TACF to switch the code, the code switching req. ind. Is transmitted (see FIG. 524).
The base TACF switches code req. ind. Is transmitted (see FIG. 525).
TACF switches code req. ind. Is transmitted (see FIG. 526).
Note that 1 is repeated for the number of terminal-side handover branches, and 2 is repeated for the number of calls on the TACF side.

TACAF performs code switching req. ind. Send. Code switching req. ind. Requests code switching (see FIG. 527).
Code switching resp. conf. Is code switching req. ind. BCAF responds to TACAF with a code switch resp. conf. Is transmitted (see FIG. 528).
Code switching resp. conf. Is code switching req. ind. TACAF responds to TACCa with a code switch req. ind. Code confirmation resp. conf. Is transmitted (see FIG. 529).
TACFa performs code switching req. ind. Code confirmation resp. conf. Is transmitted (see FIG. 530).
TACF performs code switching req. ind. Code confirmation resp. conf. Is transmitted (see FIG. 531).

(2.4.3.6): Transmission power control (Transmission Power Control)
(2.4.3.6.6.2): Information Flow Diagrams (Information Flow Diagrams)
a) Functional model
FIG. 57 shows a functional model of transmission power control.
b) Information Flow (Information Flows)
FIG. 58 shows a CC-Plane information flow diagram of transmission power control.

(2.4.3.6.3): Definitions of Information Flows and Associated Information Elements (Definitions of Information Flows and Associated Information Elements)
The information flow and the like will be described below, and the corresponding information elements and the like are shown together in a table. However, the table may be omitted if there is no corresponding element.
MRRC periodically sends a CELL CONDITION REPORT req. ind. (Cell status report req.ind.) Is transmitted (see FIG. 532).
TACCa sets transmission power value to notify TACFv of transmission power value req. ind. Is transmitted (see FIG. 533).
TACF sets transmission power value to notify BCFr of transmission power value req. ind. Is transmitted (see FIG. 534).

(2.4.4): Information flow of mobility service (Information Flow of Mobility Service)
(2.4.4.1): Terminal location updating (Terminal location updating)
(2.4.4.4.1.1): Normal procedure using modules (Common procedure modules used)
The normal procedure modules used within the scope of the terminal location update service form are shown below.
-TMUI inquiry (TMUI inquiry)
-User search by FPLMTS (FPLMTS user ID retryval)
-User authentication procedure (User authentication procedure)
-Start ciphering
-TMUI assignment (TMUI assignment)

(2.4.4.1.2): Information flow diagram
a) Functional model
FIG. 59 shows a functional model for terminal location update.
b) Information Flow (Information Flows)
FIG. 60 shows an information flow diagram of terminal location update. FIG. 61 shows an information flow diagram in which information elements for terminal location update are combined.

(2.4.4.4.1.3): Information flows and associated information elements
The information flow and related information elements are described below. All IEs are FFS.
Relationship rd (LRCF-LRDF) (Relationship rd (LRCF-LRDF))
The base SCF transmits an LAI update IF (LAI update IF) to the SDF, and the LAI update IF (LAI update IF) requests updating of the location area information.
The SDF returns a response confirmation to the base SCF, and guarantees completion of the update of the location area information (see FIG. 535).

Relationship rk (SACF-LRCF) (Relationship rk (SACF-LRCF))
The SACF transmits a terminal location update IF (terminal location update IF) to the base SCF, and the terminal location update IF (terminal location update IF) is used for requesting location information of the mobile terminal to be updated. The base SCF returns a response confirmation to the SACF and guarantees completion of the update of the terminal location information (see FIG. 536).
Relationship rl (MCF-SACF) (Relationship rl (MCF-SACF))
The MCF transmits a terminal location update IF (terminal location update IF) to the SACF, and the terminal location update IF (terminal location update IF) is used for requesting location information of the mobile terminal to be updated. The SACF returns a response confirmation to the MCF, and guarantees completion of the update of the terminal location information (see FIG. 537).

Here, special notes are listed below.
1) Relationship ID (relationship ID) identifies the relationship between the requester and the responder.
2) TMUI and TMUI assignment source ID (TMUI and TMUI allocation ID) shall be used as FPLMTS user ID (FPLMTS user ID) for relationship rl and relationship rk.
3) The terminal state indicates a state where the incoming call is possible or not possible.
4) The TC information is terminal data information indicating the terminal capacity.

(2.4.5): Security service information flow (2.4.5.1): User authentication a) Function model (Functional Model)
FIG. 62 shows a user authentication model.
b) Information Flow (Information Flows)
FIG. 63 shows an information flow diagram of user authentication.
C) Information Flow, Information Element, Functional Entity Operations (Definitions of Information Flows, Information Elements, and Functional Entity Actions)
Relationship rd (LRCF-LRDF) (Relationship rd (LRCF-LRDF))

The information flow and the like will be described below, and the corresponding information elements and the like are shown together in a table. However, the table may be omitted if there is no corresponding element.
The authentication information search IF is used to request security information for user authentication by the base LRDF (see FIG. 538).
Relationship rg (LRCF-TACF) (Relationship rg (LRCF-TACF)), Relationship rk (LRCF-SACF) (Relationship rk (LRCF-SACF))

An authentication challenge IF (authentication review IF) is used to confirm the legitimacy of the user's identity. The LRCF transmits a network subscription authentication review to the TACF / SACF and requests a response of the authentication calculation result (see FIG. 539).
Relationship rb (TACF-TACAF) (Relationship rb (TACF-TACAF)) relationship rl (SACF-MCF) (Relationship rl (SACF-MCF))

An authentication challenge IF (authentication review IF) is used to confirm the legitimacy of the user's identity. The TACF sends a network subscription authentication review to the TACAF and requests a response of the authentication calculation result. In addition, the SACF sends a network subscription authentication review to the MCF and requests a response of the authentication calculation result (see FIG. 540).
Relationship rv (UIMF-TACAF) (Relationship rv (UIMF-TACAF)) Relationship ry (UIMF-MCF) (Relationship ry (UIMF-MCF))

  Authentication req. ind. (Authentication req.ind.) Requests transmission of a random number and calculation of the random number and an authentication key held in the UIMF. Authentication resp. conf. An authentication calculation result is returned by (authentication resp.conf.) (See FIG. 541).

(2.4.5.2): Concealment start timing (Start ciphering)
(2.4.5.2.1): Information flow diagram
a) Functional model
FIG. 64 shows a functional model of the secrecy start timing.
b) Information Flow (Information Flows)
FIG. 65 shows an information flow diagram of concealment start timing.

(2.4.5.2.2): Information flows and associated information elements (Information flows and associated information elements)
The information flow and the like will be described below, and the corresponding information elements and the like are shown together in a table. However, the table may be omitted if there is no corresponding element.
Relationship rb (TACF-TACAF) (Relationship rb (TACF-TACAF))

The terminal requests start of application for encryption of information between the terminal and the network by Start ciphering IF (secret start timing IF). This flow is an information flow for requesting confirmation.
Relationship rg (LRCF-TACF) (Relationship rg (LRCF-TACF))
The terminal requests start of application for encryption of information between the terminal and the network by Start ciphering IF (secret start timing IF). This flow is an information flow for requesting confirmation (see FIG. 542).

Relationship rk (LRCF-SACF) (Relationship rk (LRCF-SACF))
The terminal requests start of application for encryption of information between the terminal and the network by Start ciphering IF (secret start timing IF). This flow is an information flow for requesting confirmation (see FIG. 543).
Relationship rl (SACF-MCF) (Relationship rl (SACF-MCF))
The terminal requests start of application for encryption of information between the terminal and the network by Start ciphering IF (secret start timing IF). This flow is an information flow for requesting confirmation.

(2.4.5.3): TMUI management, user ID search (User ID Retrieval)
(2.4.3.3.1): TMUI assignment (TMUI assignment)
(2.4.5.3.1.1): Information flow diagram (Information flow diagram)
a) Functional model
FIG. 66 shows a functional model of TMUI allocation.
b) Information Flow (Information Flows)
FIG. 67 shows an information flow diagram of TMUI assignment. In addition,
1) MCF-SACF is user authentication when there is no call,
2) TACAF-TACF is user authentication when there is a call,
3) If there is no effective user authentication in the base network, Authentication Info Retrieval req. ind. and resp. conf. (Authentication information search req.ind. And authentication information search resp.conf.). In the case of 2), an MCF-SACF relationship may be used.

(2.4.5.3.1.2): Information flows and associated information elements
The information flow and the like will be described below, and the corresponding information elements and the like are shown together in a table. However, the table may be omitted if there is no corresponding element.
Relationship rb (TACF-TACAF) (Relationship rb (TACF-TACAF))

The TMUI assignment IF (TMUI assignment IF) is used for TMUI assignment and transmission to the user after the user's identification by the network. The response confirmation is returned as a guarantee of the validity of the TMUI allocation (see FIG. 544).
Relationship rd (LRCF-LRDF) (Relationship rd (LRCF-LRDF))
The TMUI query IF is used for requesting a new TMUI from the base LRDF (see FIG. 545).
The TMUI modify IF (TMUI modification IF) is used for requesting the user to modify the TMUI information to the base LRDF and to send a confirmation confirmation after modification (see FIG. 546).
Relationship rg (LRCF-TACF) (Relationship rg (LRCF-TACF))

The TMUI assignment IF (TMUI assignment IF) is used for TMUI assignment and transmission to the user after the user's identification by the network. The response confirmation is returned as a guarantee of the validity of the TMUI allocation (see FIG. 547).
Relationship rk (LRCF-SACF) (Relationship rk (LRCF-SACF))
The TMUI assignment IF (TMUI assignment IF) is used for TMUI assignment and transmission to the user after the user's identification by the network. The response confirmation is returned as a guarantee of the validity of the TMUI allocation (see FIG. 548).
Relationship rl (SACF-MCF) (Relationship rl (SACF-MCF))
The TMUI assignment IF (TMUI assignment IF) is used for TMUI assignment and transmission to the user after the user's identification by the network. The response confirmation is returned as a guarantee of the validity of the allocation assignment of TMUI (see FIG. 549).

(2.4.3.2): User ID retrieval (User ID retryval)
This procedure is used to convert TMUI to FPLMTS user IMUI. When a new base network receives a set of TMUI or TMUI assignment source ID (TMUI assignment source ID) of TMUI and the user who becomes the FPLMTS user ID (FPLMTS user ID) from the mobile terminal side The base network initializes this procedure.
When the (new) base LRCF receives a TMUI or a set of TMUI assignment source IDs (TMUI assignment source ID) from the TMUI and the mobile terminal, the LRCF selects a procedure to be executed (see below). ).

1) Terminal Location Registration and Update (Terminal Location Registration and Update) Case A) When a new LRDF serving as a base is assigned a TMUI Case B) When a new LRDF different from the LRDF serving as a base is assigned a TMUI ( * Case B) is not described in this regulation. )
2) Mobile Originating Call
3) At failure: When the new base network fails to retrieve the IMUI due to, for example, the loss of the TMUI, the new base network tries to retrieve the FPLMTS user's IMUI (FPLMTS user IMUI) from the UIMF .

(2.4.5.3.2.2): Information flow diagram
FIG. 68 shows an information flow diagram of the user ID search.
(2.4.5.3.2.2): Information flows and associated information elements
Relationship rd (LRCF-LRDF) (Relationship rd (LRCF-LRDF))
IMUI retryval req. ind. (IMUI search req.ind.) Is used for IMUI search by TMUI. The LRCF transmits this information flow to the LRDF in the same network. IMUI retry resp. conf. (IMUI search resp.conf.) Responds to the request (see FIG. 550).
In the case of a mobile station call, this IE (TMUI assignment Source ID) is not included.
Relationship rl (SACF-LRCF) (Relationship rl (SACF-LRCF))

  IMUI retryval req. ind. (IMUI search req.ind.) Is used for IMUI search from the mobile station side. This information flow is used only when the network side does not convert the FPLMTS user's TMUI to IMUI. In the base network, the SCF transmits this information flow to the SACF. IMUI retry resp. conf. (IMUI search resp.conf.) Responds to the request (see FIG. 551).

Relationship rk (MCF-SACF) (Relationship rk (MCF-SACF))
IMUI retryval req. ind. (IMUI search req.ind.) Is used for IMUI search from the mobile station side. This information flow is used only when the network side does not convert the FPLMTS user's TMUI to IMUI. In the base network, the SACF transmits this information flow to the MCF. IMUI retry resp. conf. (IMUI search resp.conf.) Responds to the request (see FIG. 552).

Relationship rg (TACF-LRCF) (Relationship rg (TACF-LRCF))
IMUI retryval req. ind. (IMUI search req.ind.) Is used for IMUI search from the mobile station side. This information flow is used only when the network side does not convert the FPLMTS user's TMUI to IMUI. In the base network, the LRCF transmits this information flow to the TACF. IMUI retry resp. conf. (IMUI search resp.conf.) Responds to the request (see FIG. 553).

Relationship rb (TACAF-TACF) (Relationship rb (TACAF-TACF))
IMUI retryval req. ind. (IMUI search req.ind.) Is used for IMUI search from the mobile station side. This information flow is used only when the network side does not convert the FPLMTS user's TMUI to IMUI. In the base network, TACF transmits this information flow to TACAF. IMUI retry resp. conf. (IMUI search resp.conf.) Responds to the request (see FIG. 554).

(2.4.6): SDL diagram The SDL diagram of each functional entity is the IMT-2000 Recommendation Draft. Conforms to SDL diagram in FIF. However, scenario 3 in the access link setting procedure is not applied in this specification. The numbers described in the description part of the information flow transmission / reception between FEs in the SDL diagram are Q. This is the FEA number in the FIF.

(2.5): Protocol specification (2.5.1): Reference configuration FIG. 69 shows the correspondence between the physical node configuration and functional entities in this experimental system. The interfaces for defining the protocol of this experimental system are listed below.
・ Wireless interface ・ BTS-MCC simulator interface

(2.5.2): Radio interface specifications (2.5.2.1): Overview In section 2.5.2, the layer 1 to layer 3 protocol specifications in the radio interface are defined.
(2.5.2.2): Layer 1
The description is omitted here.
(2.5.2.3): Layer 2
(2.5.3.2.3.1): Overview Layer 2 includes a LAC (Link Access Control) sublayer and a MAC (Medium Access Control) sublayer. Furthermore, the LAC sublayer is composed of a Layer 3 matching sublayer and an LLC (Logical Link Control) sublayer.

  FIG. 70 shows a signal layer 2 protocol architecture on the radio interface. As an example, FIG. 71 shows a frame configuration in the case of the BSC function termination.

(2.5.2.3.1.1): LAC (Link Access Control) sublayer A variable length service data unit (SDU) between users of layer 2 is transferred with high reliability.
(2.5.3.2.3.1.1.1): Layer 3 matching sub-layer Primitive / parameter mapping between layer 3 and LLC and layer 3 SDU decomposition / assembly into LLC PDUs.
(2.5.2.3.3.1.2): LLC (Logical Link Control) sub-layer Provides a highly reliable transfer function using functions such as error control and flow control.
(2.5.2.3.1.2): MAC (Medium Access Control) sublayer Performs error detection of LLC PDUs, decomposition / assembly of LLC PDUs, and decomposition / assembly into layer 1 frames.

(2.5.3.2.2): Function (Functions)
(2.5.2.3.2.1): Functions of the LAC (Link Access Control) sublayer (2.5.2.2.2.1.1.1): Layer 3 matching sublayer Layer 3 matching sublayer The functions of each layer are listed below.
a) Signal Layer 3 PDU Assembly and Disassembly This function provides a mechanism for assembly of signal layer 3 PDUs into LLC PDUs or disassembly of signal layer 3 PDUs from LLC PDUs.
b) Link control A layer 3 entity that processes SDU of LAC is specified by SAPI. (Applications will be examined in the future)
c) Code type A code type is identified when applying hybrid ARQ.

(2.5.3.2.3.2.1.2): LLC (Logical Link Control) sub-layer a) Sequence integrity This function maintains the order of LLC and SDUs determined by the transfer efficiency of this layer. .
b) Error Correction by Selective Retransmission The hierarchical structure allows the receiving LLC entity to capture stray LLC SDUs. This function corrects sequential errors by retransmission.
c) Flow control This function enables the LLC receiver to control the information transmission rate of the originating LLC peer entity.
d) Error reporting function to layer management This function instructs the layer management of errors that have occurred.
e) Communication maintenance function With this function, it is possible to continue to establish a link connection state even if the two peer LLC entities constituting the link continue without data transfer.
f) Local Data Search This function allows local LLC users to search for non-contiguous SDUs that have not been released by the LLC entity.
g) Connection control This function establishes, releases, and resynchronizes the LLC link. Also, variable length information can be transmitted between users without guaranteeing delivery.
h) Transfer of user data This function is used to carry user data between LLC users. The LLC supports data transfer for both guaranteed and non-guaranteed data.
i) Protocol error detection and recovery This function detects and recovers from errors that occur during the operation of the protocol.
j) Status report This function enables the exchange of status information between the sending and receiving peer entities.

(2.5.2.3.2.2): MAC (Medium Access Control) Sublayer Functions The MAC sublayer functions are listed below.
a) Detection of CRC errors and countermeasures This function enables detection and countermeasures of LLC PDU corrosion via CRC. Corroded LLC PDUs are discarded.
b) Assembly of LLC PDU or BTS layer 3 into layer 1 frame or disassembly of LLC PDU or BTS layer 3 from layer 1 frame By this function, assembly mechanism of LLC PDU or BTS layer 3 into layer 1 frame, Or a disassembly mechanism from the layer 1 frame of the LLC PDU or BTS layer 3 is provided.
This function also includes a padding function for making the MAC PDU an integer multiple of the layer 1 frame. In RACH, a sequence number is assigned to eliminate double reception of MAC PDUs.
c) Address control In RACH / FACH, logical link identification (for each EG Mobile Terminal) using PID is performed.
d) Differentiation of signal contents Differentiation of user information / control information in RACH, FACH and UPCH is performed.
e) Differentiation of termination node The node (BTS / BSC function) where the signal is terminated is distinguished.

(2.5.2.3.3): Format and parameters (2.5.2.3.3.1): LAC sublayer format and parameters (2.5.2.3.3.3.1.1) ): Layer 3 matching sublayer a) SAPI (Service Access Point Identifier)
The service type of layer 2 provided to layer 3 is identified (see FIG. 555).
b) W bit
This is a disassembly / assembly bit and corresponds to the layer 3 frame and the layer 3 matching sub-layer frame (see FIG. 556).
c) Code type indicator Indicates the code type when hybrid ARQ is applied. Applicability is identified by version (see Figure 557).
d) Reservation layer 3 matching sub-layer version and the like are shown (see FIG. 558).

(2.5.2.3.3.3.1.2): LLC
(2.5.2.3.3.1.2.1): LLC PDU
FIG. 559 and FIG. 560 show a list of protocol data units (PDUs).
The definition of LLC PDU is shown below.
a) BGN PDU (Begin)
The BGN PDU is used for establishing an LLC link between two peer entities. The BGN PDU requires the peer transmitter buffer and receiver buffer to be disconnected and requires initialization of the modulation state of the peer transmitter and receiver.
b) BGAK PDU (Begin confirmation)
The BGAK PDU is used to confirm acceptance of the layer 2 link setup request from the peer entity.
c) BGREJ PDU (Begin rejection)
The BGREJ PDU is used for rejection of layer 2 link setup requests from peer LLC entities.

d) END PDU (End)
The END PDU is used for releasing the LLC link between two peer entities. e) ENDAK PDU (End Acknowledge)
The ENDAK PDU is used to confirm the release of the LLC link.
f) RS PDU (resynchronization)
The RS PDU is used for resynchronization of the buffer and data transfer state modulation.

g) RSAK PDU (Resynchronization confirmation)
The RSAK PDU is used for confirmation of the resynchronization request of the peer LLC entity.
h) ER PDU (error recovery)
The ER PDU is used for recovery from protocol errors.
i) ERAK PDU (error recovery confirmation)
The ERAK PDU is used to confirm recovery from protocol errors.

j) SD PDU (sequential data)
The SD PDU is used for transferring the PDU including the information field given by the user over the LLC link with the serial number.
k) POLL PDU (status request)
The POLL PDU is used for requesting status information of the peer LLC entity across the LLC link.
l) STAT PDU (response invariant state)
The STAT PDU is used to respond to a status request (POLL PDU) received from the peer LLC entity. The request includes information regarding the reception status of the SD, PDU, and SDwithPOLL PDU, the credit information of the peer transmitter, and the serial number [N (PS)] assigned to the POLL PDU or SDwithPOLL PDU.

m) USTAT PDU (response in variable state)
The USTAT PDU responds to the detection of single or multiple stray SD PDUs based on the examination of the serial number attached to the SD PDU. The response includes information regarding the reception status of the SD PDU and the credit information of the peer transmitter.
n) SDwithPOLL PDU (Sequential data and status request)
The SDwithPOLL PDU is a sequentially numbered PDU that is used for the transfer of the PDU including the information field given by the user over the LLC link and for requesting status information about the peer LLC entity.
o) UD PDU (unspecified data)
UD PDUs are used for uncertain data transfer between two LLC users. When an LLC user requests the transfer of unacknowledged information, the UD PDU sends information to its peer entity in an unaffected or variable state. UD PDUs do not carry serial numbers and can therefore be lost without notification.

p) MD PDU (management data)
MD PDUs are used for the transfer of unsecured management data between two management entities. When the management entity is reluctant to transfer unacknowledged information, the MD PDU sends information to the peer management entity in an unaffected or variable state. UD PDUs do not carry serial numbers and can therefore be lost without notification.

An invalid PDU means the following cases:
a) If the PDU code type is not known,
b) Inappropriate length for PDU state type Invalid PDUs are discarded without notification to the sender. No additional action is taken as a result of such a PDU (length violation reported in layer management above b), a) c)

(2.5.2.3.3.1.2.1): LLC PDU format (LLC PDU format)
72 to 88 show the LLC PDU format. There are 16 types of PDUs, a list of which is shown.
72 shows sequence data of PDU (SD PDU), FIG. 73 shows sequence data PDU (SDwithPOLL PDU) including a status request, FIG. 74 shows Poll PDU (POLL PDU), and FIG. 75 shows invariant status PDU (STAT PDU). 76 shows a variable state PDU (USTAT PDU), FIG. 77 shows a unit data PDU (UD PDU) management data PDU (MD PDU), FIG. 78 shows a Begin PDU (BGN PDU), and FIG. 79 shows a Begin confirmation PDU. 80 is a Begin rejection PDU (BGREJ PDU), FIG. 81 is an End PDU (END PDU), FIG. 82 is an End Confirmation PDU (ENDAK PDU), and FIG. 83 is a Resynchronization PDU (RS). 84 shows resynchronization confirmation PDU (RSAK) 85 shows an error recovery PDU (ER PDU), and FIG. 86 shows an error recovery confirmation PDU (ERAK PDU).
The features of this format will be described below.

(2.5.2.3.3.1.2.1.2.1): Coding conventions
LLC, PDU is 2.1 / I. 361 [4]. It consists of code rules specified in
Note that LLC is a trailer-oriented type. For example, protocol control information is sent at the end.

(2.5.2.3.3.3.1.2.2.2): Storage area Each PDU has a storage area bit (ie, R, Rsvd, Reserved). One of the functions of the storage area is achieved with an 8-bit configuration. On the other hand, other functions require further research. Functions other than the 8-bit array are not defined, and the code is treated as zero in that area. That area is ignored by the receiver.

(2.5.2.3.3.1.2.1.2.3): PDU length The maximum length of the information area of the SD, UD, and MD PDU is k octets. The maximum value of k is octets [FFS]. The value of k is established by a size negotiation procedure outside of LLC. If there is a bilateral agreement, it may be specified by another recommendation using LLC. Or it may be the maximum length of the PDU size of the protocol using LLC. The minimum value of k is 0 octets.

  The maximum length of the variable length SSCOP-UU region is j octets. The maximum value of j is octets [FFS]. The value of the value of j is established by bilateral agreement, but may be specified by other recommendations using LLC. Alternatively, it may be based on a protocol request using LLC. The minimum value of j is 0 octets.

(2.5.2.3.3.1.2.1.2.4): STAT and USTAT PDU coding The USTAT PDU has two list elements. A STAT PDU contains zero or more list elements. The transmitted STAT message may be divided into one or more STAT PDUs.

The STAT PDU procedure does not depend on the information in other STAT PDUs. This is strictly true, for example, even if multiple STAT PDUs are generated in response to a single POLL PDU, the single or multiple STAT PDUs disappear.
Span list items in STAT and USTAT PDUs are odd or even list elements, which are used for selective retransmission requests. Each odd element represents the first PDU of the lost gap, and each even element represents the first PDU of the received sequence number, with the exception that it may be the last. Note that an example of encoding the span list may be provided.

(2.5.2.3.3.1.1.2.3): State of LLC protocol entity This section describes the state of LLC entity by specific example of peer-to-peer protocol. The state is conceptual and reflects the general state of the LLC entity, ie the sequence of signals, and the state of the LLC entity when the user and the peer each exchange PDUs. Further, although other states are used in the description, this is to avoid subjecting additional states, and will be described in detail in the description of SDLs. The basic state is shown below.

State 1 (State 1) Idle (Idle)
Each LLC entity is conceptually in the same idle state (State 1) and will recover to this state when the connection is released.

State 2 (Outgoing Connection Pending)
The LLC entity is requesting a connection with the peer, and the entity remains in the call connection pending state (State 2) until it receives confirmation from the peer.

  State 3 (Incoming Connection Pending) The LLC entity has received a connection request from the peer and is waiting for a response from the user side. That is, it is in an incoming call connection state (State 3).

State 4 (State 4) Calling disconnection pending state (Outgoing Disconnection Pending)
The LLC entity is requesting the release of the peer-to-peer connection, and the entity proceeds to the call not connected pending state, (State 4). That state continues until the entity receives confirmation of the release of the peer entity and the LLC entity transitions to the idle state (State 1). After the transition to the idle state, it is the same as described above.

State 5 (Outgoing Resynchronization Pending)
The LLC entity is requesting resynchronization of the connection with the peer, and the entity is in the call resynchronization pending state (State 5).

State 6 (State 6) Incoming Resynchronization Pending
The LLC entity has received a resynchronization request from the peer and is waiting for a response from the user.

State 7 (State 7) Outgoing Recovery Pending
The LLC entity is requesting recovery with the connected peer, and the entity is in the call recovery pending state (State 7).

State 8 (Recovery Response Pending)
The LLC entity has completed recovery and has notified the user, and the entity is waiting for a response and is in the recovery response pending state (State 8).

State 9 (State 9) Incoming Recovery Pending state
The LLC entity has received a recovery request from the peer, and the entity is waiting for a response from the user and is in an incoming call recovery pending state (State 9).

State 10 (State 10) Preparation for data transfer (Data Transfer Ready)
If the connection establishment, resynchronization, or error recovery procedure is successful, the peer and the LLC entity transition to the data transfer ready state (State 10), allowing the guaranteed data transfer to be performed.

(2.5.2.3.3.1.2.4): LLC state variables (state variables)
This section describes the state variables by specific examples of peer-to-peer protocols.
SD and POLL PDUs are numbered independently and sequentially, with values from 0 to n minus 1 (where n is the module of the sequence number).
The module is equal to 28 and the numbered cycle in the whole range is from 0 to 28-1. All arithmetic operations based on the state variables and sequence numbers included in this example shown below are modules (VT (S), VT (PS), VT (A), VT (PA), VT (MS), VR ( R), VR (H), VR (MR)). When arithmetically comparing transmitter variables, VT (A) is considered the basis. When arithmetically comparing receiver variables, VR (R) is considered the basis. Further, the arithmetic state 256 is assigned to the variable states VT (SQ) and VR (SQ) as modulo. In the transmitter, the LLC maintains the following state variables.

a) VT (S) transmission state variable (Send state variable)
This is the sequence number of the SD PDU to be transmitted next (except for retransmission) as the first time. After the first transmission of the SD PDU (except for retransmission), the number increases.
b) VT (PS) poll transmission state variable (Poll Send state variable)
The current value of the poll sequence number. Increase until the next poll PDU transmission.
c) VT (A) confirmation state variable (Acknowledge state variable)
The next sequence number of an SD PDU that is expected to be confirmed irregularly, and that SD PDU forms the lower edge of an acceptable confirmation window. The VT (A) is updated upon confirmation of non-consecutive SD PDUs.

d) VT (PA) poll confirmation state variable (Poll acknowledged state variable)
This is the poll sequence number of the next STAT PDU that is expected to be received, and the STAT PDU is STAT PDU. In contrast, it forms the lower edge of an acceptable N (PS) window. If a STAT PDU is received containing an invalid N (PS), it is initialized as a recovery measure or release is performed. When STAT PDU is received, VT (PA) is STAT. Set to N (PS).
e) Maximum value of VT (MS) transmission state variable (Maximum Send state variable)
When the first SD PDU is rejected by the peer receiver [for example, when the receiver's acceptance permission value is VT (MS) -1 or higher], this is the sequence number of the SD PDU. This value indicates the upper edge of the transmit window. Based on the reception of USTAT PDU, STAT PDU, BGN PDU, BGAK PDU, RS PDU, RSAK PDU, ER PDU, or ERAK PDU, the transmitter is updated when VT (S), VT (MS), VT (MS) is updated Do not send a new SD PDU.

f) VT (PD) poll data state variable (Poll Data state variable)
If the confirmation is undecided, the state variable will contain the number of SD PDUs sent during the transmission of the POLL PDU, or the number of SD PDUs sent before the first POLL PDU was sent after the timer poll was started. Show. The VT (PD) increases based on the transmission of the SD PDU, and is reset to zero by the transmission of the POLL PDU.

g) VT (CC) connection control state variable (Connection Control state variable)
BGN, END, ER or RS PDU number that is not confirmed. VT (CC) increases based on transmission of BGN, END, ER or RS PDU. When an END PDU is sent in response to a protocol error, the SSCOP does not wait for the ENDAK PDU [eg, the SSCOP goes directly to state 1 (Idle)] and VT (CC) does not increase.

h) VT (SQ) transmitter connection sequence state variable (Transmitter Connection Sequence state variable)
This state variable is used to allow the receiver to identify the retransmitted BGN, ER, RS PDU. This state variable is initialized and increased based on the establishment of the SSCOP process, and is incorporated into the N (SQ) region before the first transmission of any one of BGN, RS, and ER PDUs.

The LLC maintains the following state variables at the receiver.
a) VR (R) reception state variable (Receive state variable)
This is the sequence number of the next irregular SD PDU that is expected to be received. Increased upon receipt of the next irregular SD PDU.

b) VR (H) Highest Expected State Variable (Highest Expected State Variable)
This is the SD PDU sequence number for which the highest value is expected. It is updated in the following two ways.
1) Reception of a new SD PDU;
2) Reception of POLL PDU

c) VR (MR): State variable (Maximum acceptable) according to the maximum value of the allowable reception amount.
(Receive state variable)
Sequence number of the first SD PDU that is not allowed to the receiver. [For example, when the receiver's acceptance permission value is VR (MR) -1 or more] The receiver discards the SD PDU together with N (S) and VR (MR). (As an example, when such an SD PDU transmits USTAT). Updating Updating VR (MR) is optional, but VR (MR) should not be set lower than VR (H). As an example, an example of VR (MR) determination method is shown in Appendix IV.

d) VR (SQ): Receiver Connection Sequence state variable
This state variable is used to identify the retransmitted BGN, ER, RS PDU. Based on receipt of BGN, ER, or RS PDU, this state variable is compared to the value of N (SQ) and then assigned to the value of N (SQ). If the values are different, the PDU is considered and VR (SQ) is set to N (SQ). If the values are equal, the PDU is determined to have been retransmitted.

(2.5.2.3.3.1.2.5): LLC PDU parameter a) N (S)
Regardless of the creation of a new SD or POLL PDU, VT (S) is mapped to N (S). b) Information field (Information field)
Information areas of SD, MD, and UD PDUs are mapped from message unit parameters AA-DATA, MAA-UNITDATA, and AA-UNITDATA, respectively. The information area is mapped to each message unit parameter, AA-DATA, MAA-UNITDATA, and AA-UNITDATA.

c) N (PS)
VT (PS) is mapped to N (PS) regardless of (PO (PS) after increment) POLL PDU generation. The POLL PDU receiver receives the POLL. N (PS) in the region STAT. Map to N (PS). In addition, the current value of VT (PS) is mapped to N (PS) to facilitate error recovery procedures and is held in the transmitter buffer with the corresponding SD PDU whenever an SD PDU is transmitted.

d) N (R)
VR (R) is mapped to N (R) regardless of when STAT or USTAT PDU is generated.
e) N (MR)
VR (MR) is mapped to N (MR) regardless of the generation of STAT, USTAT, RS, RSAK, ER, ERAK, BGN, BGAK PDU. This is the basis for credit approval by the receiver.
f) SSCOP-UU
The SSCOP-UU in the BGN, BGAK, BGREJ, END, and RS PDU are mapped from the parameter SSCOP-UU of the corresponding SSCOP signal and mapped to the SSCOP-UU.

g) Source (S) bit In the END PDU, this bit carries either SSCOP or SSCOP user as the cause of release. If the user is responsible for sending the END PDU, this bit is set to is bit i. This bit is set if the transmission cause of the END PDU is in SSCOP. This bit is mapped to the source area of AA-RELEASE.
[Note: Aspects of layer-to-layer communication need further research. ]
h) N (SQ)
This area carries connection sequence values. Regardless of the transmission of BGN, RS, and ER PDU, VT (SQ) is mapped to N (SQ). This area includes BGN, RS, ER PDU. Used to identify retransmissions.
i) PDU type area The coding of the type area is shown in FIG.

(2.5.2.3.3.1.2.6): LLC timer The description of the timer is omitted.

(2.5.2.3.3.1.2.7): LLC parameters Each LLC protocol parameter is shown below.
a) MaxCC
This is the maximum value of the state variable VT (CC), and BGN, END, ER, RS PDU. Corresponds to the maximum number of transmissions.
b) MaxPD
This is the maximum allowable value of the state variable VT (PD) before transmission of the POLL PDU and before VT (PD) is reset to zero.

c) MaxSTAT
This is the maximum number of list elements partitioned into STAT PDUs. If the number of list items exceeds MaxSTAT, the STAT message should be split. All PDUs carrying a segmented STAT message will probably contain a MaxSTAT list item except the last one. This parameter is not used for STAT PDU receivers due to length considerations. It is considered that only a sender having a purpose of dividing a STAT message is used. This parameter should be an odd (integer) number of 3 or greater.

The invalid value of MaxSTAT is [FFS]. This parameter may be changed on a valid basis.
Note that an invalid value causes the STAT PDU to be filled with 6 ATM cells that use the normal part of AAL type 5. Furthermore, the total length of the STAT PDU should not exceed the maximum SD PDU length.

d) Clear-buffer This parameter is set upon connection establishment. This parameter supports either Yes or No. When this parameter is set to Yes, the LLC can release the transmission buffer and other transmission units to release the connection. When this parameter is set to No, the LLC cannot release the transmission buffer and other transmission units to release the connection. Furthermore, if this parameter is set to No, the LLC will not be able to selectively release confirmed messages from the transmission buffer as long as old messages remain in the buffer.

e) Credit This parameter is used to adjust credit notification to layer management. If the transmission of a new SD PDU by the LLC is disturbed due to an improper credit, the credit takes a value of No. If transmission of a new SD PDU by LLC is permitted, the credit takes a value of Yes. The initial value of credit is Yes.

(2.5.2.3.3.1.2.8): LLC credits and flow control (2.5.2.3.3.1.2.1.8.1): credits and peer-to-peer flow control credits Is approved by the LLC receiver, which allows the transmission of a new SD PDU by the peer LLC transmitter. There is no standard in the credit determination process by the receiver entity, but it is related to buffer availability, connection bandwidth, and delay.

  Credit values are transmitted to the transmitter in the N (MR) region consisting of each BGN, BGAK, RS, RSAK, ER, ERAK, STAT and USTAT PDU sent by the receiver. N (MR) is written to the variable area VT (MS) in the transmitter. The credit value sent to the transmitter is the sequence number of the first SD PDU that is expected to be unacceptable to the receiver.

  The transmitter will not send any SD PDUs that exceed credit tolerance. The receiver will abandon any SD PDU that exceeds credit tolerance. (For example, such SD PDUs prompt for transmission of USTAT PDUs).

  Already approved credits can be reduced by performing flow control according to the receiver's rules. However, the variable area VR (MR) of the receiver credit cannot be reduced below the value VR (H). In other words, when the receiver receives the SD PDU numbered VR (H) -1, and confirms the reception, the credit value VR (MR) is greater than VR (H) or is set to VR (H). It becomes equal value.

  The operation window of the protocol in the transmitter is a band lower than VT (A) and a band higher than the credit valid value [VT (MS) -1]. Protocol modules are limited to values between 28-l from the operation window. Therefore, at the receiver, the approved credit using the arithmetic modular must take a value between VR (H) and VR (R) -1. If VR (MR) = VR (R) = VR (H), the operation window becomes zero. If VR (MR) = VR (R) −1, the operation window is the maximum.

  The LLC receiver allocates a buffer to support each connection. In principle, a valid receiver buffer must match or exceed the credit approved by the transmitter to avoid abandoning data that has been successfully transmitted. However, if a limited buffer is beneficial for the connection, credits can be approved within the valid buffer range. This method can obtain a higher amount of information than can be achieved by limiting credits to useful buffers, but if an error occurs, the data may have to be discarded. In the past, the receiver was unable to receive or confirm an SD PDU and could not transmit further. The receiver must also allocate enough buffer capacity to receive and transmit SD PDUs with VR (R) at all times unless VR (R) = VR (H) = VR (MR). Don't be. A method of approving credits within a range of buffer capacities is when a limited buffer is beneficial to support the connection and the LLC receiver is in this method and can maintain the quality of service (QoS) required for the connection. Should only be implemented.

(2.5.2.3.3.1.8.2): Local flow control
LLC events, such as the reception of PDUs or the reception of external signals or internal signals, usually proceed by regulations that cause them. However, in the phenomenon related to the LLC link state change, information is superior to data transfer.
As an example, there is a plan to detect congestion in a low protocol layer (for example, a long queuing delay). In that case, data transport should be temporarily reserved to gain an advantage over connection control messages. The means by which the LLC entity determines the congestion depends on the protocol environment including the protocol timer value and is not compatible with standardization.

  When the LLC entity detects local congestion (detection that the lower layer is busy as in the SDL example), AA-DATA. Request signal, AA-UNITDATA. Request signal, MAA-UNITDATA. Request signal. The option to reserve a response to is possible. In addition, retransmission of the requested SD PDU may be reserved. The data transport procedure makes it possible to achieve them without causing errors in the protocol.

Therefore, from the viewpoint of transmitting PDUs to the peer receiver, all types of PDUs except SD PDUs, MD PDUs, and UD PDUs can be highly advantageous. The SD PDU, MD PDU, and UD PDU can maintain the same effectiveness. The SD PDU can be more advantageous than the new transmission system from the viewpoint of practical use by retransmission. Their superiority is essentially only found in LLC.
As described above, an excellent effect can be obtained from local flow control by a user interface using LLC.

(2.5.2.3.3.30): MAC Sublayer Format and Parameters Hereinafter, details of the MAC PDU of each logical channel are shown in FIGS. 87 to 94. 87 is BCCH, FIG. 88 is PCH, FIG. 89 is RACH-L, S, FIG. 90 is FACH-L, FIG. 91 is FACH-S, FIG. 92 is SDCCH, FIG. 93 is ACCH, FIG. 94 shows each UPCH. The elements in the figure are listed below.

a) PAD
Included to make the length of the MAC sublayer frame an integral multiple of the layer 1 frame length (in units of 1 octet). The bit of the PAD is “all 0”.
b) Length (PAD) Indicates the amount of padding information (number of octets) in the MAC sublayer frame unit.
c) CRC
An error detection code (CRC) is added for each MAC sublayer frame unit to perform error detection. Based on the result, it is determined whether or not retransmission is necessary in the retransmission protocol of the higher layer (see FIG. 561).
d) W bit
Disassembly / assembly bit. The start, continuation, and end of the MAC sublayer frame are shown for each layer 1 frame unit (see FIG. 562).

e) Others: BI: BCCH identification information (see FIG. 563).
SFN: System Frame Number value used for uplink long code phase calculation and superframe synchronization.
Uplink interference power: The latest measured uplink interference amount for each sector. When the measurement start is not designated from the macro, the bit is set to “all 1” (see FIG. 564).
PID: An identifier for identifying a call or mobile station to which transmission information relates in RACH / FACH. The information length is 16 bits (see FIG. 565).

U / C: An identifier for identifying whether the information mounted on the MAC SDU in the RACH, FACH, or UPCH is user information or control information (see FIG. 566).
TN: In RACH, FACH, and UPCH, information mounted on the MAC SDU is an identifier for identifying the base station side terminal node (see FIG. 567).
Mo S: A bit for identifying the FACH-S mode (see FIG. 568).

CRC: An error detection code (CRC) is added for each layer 1 frame unit, and error detection is performed (see FIG. 569).

S bit: Assigned to prevent duplication of the same frame caused by retransmission between MS and BTS (layer 1 retransmission) when assembling MAC PDU in RACH.
TA: Tail bit for convolutional code.
D: A dummy bit.
(2.5.2.4): Layer 3 (Layer 3)
Next, Layer 3 (layer 3) will be described. In the following description, the ITU-T recommendation X series, I series, and Q series are simply X. XX, I.I. XX, Q. XX may be written.

(2.5.2.2.4.1): Protocol Architecture First, the protocol architecture of layer 3 will be described.
FIG. 95 is a diagram conceptually illustrating an example of a radio interface protocol architecture. The outline of each protocol control entity (Entity) shown in FIG. 95 is listed below.
CC: Q. In accordance with 2931, call control and connection control are performed.
MM-P: Q. In accordance with 2932, movement management related to users such as user authentication is performed. However, this MM-P is not used in this system.
MM-T: performs mobility management related to terminals such as terminal location registration / update and user authentication.
RRC: Handles triggers for radio resource allocation / reservation and handover activation / termination.
TAC: Sets and releases a signaling connection between the mobile terminal and the network.

(2.5.2.2.4.2): Message Format Next, the message format in layer 3 will be described.
(2.5.2.4.2.1): CC
First, the CC message will be described. FIG. 570 shows a list of message types (message types) of the CC message.

Next, each message described in FIG. 570 will be described. In the description of the positioning of information elements in the following description, “M” is an indispensable information element, and “O” is an optional information element. “OF” indicates that this is an information element used when ATM (Asynchronous Transfer Mode) is applied to the wireless section.

(2.5.2.2.2.1.1.1): ALERTING
First, the ALERTING message will be described. This message is forwarded from the called user to the network and from the network to the calling user to indicate that the called user has been called. Each information element constituting this message is shown in FIGS. 571 to 573. As shown in this figure, Message type is ALERTING, Significance (Global) is Global (Global), Connection displacement (Connection Identification) is ACCH, and Direction (Direction) is Both (Bidirectional).

  In the figure, a connection identifier (connection identifier), a narrow-band bearer capability (narrowband transmission capability) information element, a narrow-band high layer compatibility (narrowband high layer compatibility) information element, and a mobile bearer carrier transmission body. Capability) information element and Mobile high layer information (mobile high layer information) information element are provided for future expansion such as when FFS (ATM (Asynchronous Transfer Mode) is adopted in the radio section) It is.

  Also, the Broad-band high layer information information element is included when using the high layer information selection procedure, and the Mobile bearer capability information element is used when selecting the transmission ability. Is done.

(2.5.2.2.4.2.1.2): CALL PROCEEDING (call proceeding)
Next, the CALL PROCEEDING message will be described. This message is sent from the network to the originating user or from the terminating user to the network to indicate that the requested call setup has been initiated and no further call setup information is accepted. Each information element constituting this message is shown in FIGS. 574 to 576. As shown in this figure, Message type is CALL PROCESSEDING, Significance is Local (local), Connection displacement is SDCCH / ACCH, and Direction is Both.

(2.5.2.2.4.2.1.3): CONNECT
Next, the CONNECT message will be described. This message is sent from the incoming user to the network and from the network to the outgoing user to notify that the incoming user has accepted the call. Each information element constituting this message is shown in FIGS. 577 to 581. As shown in this figure, Message type is CONNECT, Significance is Global, Connection displacement is ACCH, and Direction is Both.

  In the figure, when the responding user wants to return a message to the originating user with the lower layer information, in the direction from the user to the network, the Broad-band low layer information (broadband lower layer information) information element is Included in the message. In addition, when the user includes a broadband lower layer information information element in the “response” (CONN) message, this information element is included in this message in the direction from the network to the user. For broadband layer information negotiation, this information element is optionally included in this message, but there may be networks that do not forward this information element to the calling user.

(2.5.4.2.4.2.1.4): CONNECT ACKNOWLEDGE (connect confirmation)
Next, the CONNECT ACKNOWLEDGE message will be described. This message is sent from the network to the called user to indicate that the user has been given a call. It is also sent from the originating user to the network to enable a symmetric call control procedure. Each information element constituting this message is shown in FIG. As shown in this figure, Message type is CONNECT ACKNOWLEDGE, Significance is Local, Connection displacement is ACCH, and Direction is Both.

  The Notification Indicator information element may be present when the notification procedure is applied. This information element can also be repeated in the message. The maximum length of this information element and the allowed number of repetitions are network options.

(2.5.2.2.4.2.1.5): PROGRESS (Progress)
Next, the PROGRESS message will be described. This message is forwarded from the network or from the user to indicate the event when interworking has occurred as a call process. Each information element constituting this message is shown in FIGS. 583 to 585. As shown in FIGS. 583 to 585, Message type is PROGRESS, Significance is global, Connection displacement is SDCCH / ACCH, and Direction is both (bidirectional).

(2.5.2.2.4.2.1.6): SETUP (call setup)
Next, the SETUP message will be described. This message is sent from the originating user to the network or from the network to the terminating user to initiate call setup. Each information element constituting this message is shown in FIGS. 586 to 594. As shown in this figure, Message type is SETUP, Significance is Global, Connection displacement is SDCCH / ACCH, and Direction is Both.

(2.5.2.4.2.1.7): RELEASE (release)
Next, the RELEASE message will be described. This message is sent from either the user or the network, indicating that the device sending this message has already disconnected the FPLMTS connection and, if any, sent to release the connection identifier and call number . Further, a device that has received a "release" (REL (RELEASE)) message must release the connection identifier, and after transmitting a "release complete" (REL COMP (RELEASE COMPLETE)) message, the call number must be released. Note that the description related to the connection identifier is valid only when ATM is applied to the wireless section in the future. FIG. 595 shows information elements constituting this message. As shown in this figure, Message type is RELEASE, Significance is Global, Connection displacement is SDCCH / ACCH, and Direction is Both.

(2.5.2.2.4.2.1.8): RELEASE COMPLETE (release complete)
Next, the RELEASE COMPLETE message will be described. This message is sent from the user or network to indicate that the device sending the message has released the call number value and, if any, the connection identifier. If the connection identifier is released, it can be reused. The device that receives this message must release the call number value. Note that the description related to the connection identifier is valid only when ATM is applied to the wireless section in the future. FIG. 596 shows each information element constituting this message. As shown in this figure, Message type is RELEASE COMPLETE, Significance is Local (however, globally meaningful information can be transferred when used as the first call release message), Connection displacement is SDCCH / ACCH, Direction is Both.

(2.5.2.2.4.2.1.9): INFORMATION (information)
Next, the INFORMATION message will be described. This message is sent by the user or the network to provide additional information. Specifically, it can be used to transmit additional information for call setup (eg, split call) or various call related information. Each information element constituting this message is shown in FIG. As shown in this figure, Message type is INFORMATION, Significance is Local (however, information having global meaning can be transferred), Connection displacement is SDCCH / ACCH, and Direction is Both.

(2.5.2.4.2.2): MM-T message Next, the MM-T message will be described.
(2.5.2.2.4.2.2.1): Message First, FIG. 598 shows an MM-T message Type (type).
Note that the coding of the message type is Q.3 when the upper 3 bits are “011”. 2931 related, when the lower 3 bits are "00010" This message indicates that the message is related to 2932, and the other message indicates that it is a MOBILITY FACILITY (mobility facility).

(2.5.2.2.4.2.2.2): MOBILITY FACILITY
Next, FIG. 599 shows the configuration of MOBILITY FACILITY. As shown in this figure, the message type is MOBILITY FACILITY, the signature is local, and the direction is both.

(2.5.2.2.4.2.2.3): FACILITY (facility)
Next, a list of information elements by function type in the MOBILITY FACILITY message is shown. In the following description, a mobile station is represented by an MS, and a network is represented by a network, a network, a NETWORK, or an NW. Further, the symbol “→” indicates the data traveling direction.

(A) Function type: Terminal Location Registration (terminal location registration)
This function type is sent from the MS to the NETWORK to request location registration when updating the location registration area or roaming. A list of information elements in this function type is shown in FIGS. As shown in this figure, in this function type, the protocol identifier is MM-T, the connection identification is SDCCH, and the direction is MS (MCF) → NETWORK (SACF).

(B) Function type: Terminal Location Registration (terminal location registration)
This function type is sent from the NETWORK to the MS as a response signal for a location registration request when updating the location registration area or roaming. This signal is classified into three types according to the component type. Hereinafter, a list of information elements in this function type is shown in FIGS. 602 to 604 for each type. As shown in these drawings, in this function type, the protocol identifier is MM-T, the connection identification is SDCCH, and the direction is NETWORK (SACF) → MS (MCF).

(B-1) When the component type is Return Result (when the location registration is performed normally)
A list of information elements in this case is as shown in FIG.
(B-2) When the component type is Return Error (return error) (when a quasi-normal condition such as an application error occurs)
A list of information elements in this case is as shown in FIG.
(B-3) When the component type is “Reject” (when quasi-normality occurs due to mismatch of information elements)
A list of information elements in this case is as shown in FIG.

(C) Function type: TMUI Assignment (TMUI assignment) This function type is sent from the NETWORK to the MS to notify the mobile station of the TMUI. FIG. 605 shows a list of information elements in this function type. As shown in this figure, in this function type, the protocol identifier is MM-T, the connection identification is SDCCH, and the direction is NETWORK (SACF / TACF) → MS (MCF / TACAF).

(D) Function type: TMUI Assignment (TMUI assignment) This function type is sent from the MS to the NETWORK as a response signal to the TMUI Assignment. This signal is classified into three types according to the component type. Hereinafter, a list of information elements in this function type is shown in FIGS. 606 to 608 for each type. As shown in these figures, in this function type, the protocol identifier is MM-T, the connection identification is SDCCH, and the direction is MS (MCF / TACAF) → NETWORK (SACF / TACF).

(C-1) When Component Type is Return Result The list of information elements in this case is as shown in FIG.
(C-2) When the component type is Return Error The list of information elements in this case is as shown in FIG.
(C-2) When Component Type is “Reject” A list of information elements in this case is as shown in FIG.

(E) Function type: Authentication Challenge (authentication challenge)
This function type is sent from the NETWORK to the MS so that the exchange recognizes the validity of the mobile station. A list of information elements in this function type is shown in FIGS. As shown in this figure, in this function type, the protocol identifier is MM-T, the connection identification is SDCCH / ACCH, the direction is NETWORK (SACF / TACF) → MS (MCF / TACAF)

(F) Function type: Authentication Challenge (authentication challenge)
This function type is sent from the MS to the NETWORK in order to notify the result of the procedure for the authentication request. This signal is classified into three types according to the component type. Hereinafter, a list of information elements in this function type is shown in FIGS. 611 to 613 for each type. As shown in these figures, the protocol identifier is MM-T, the connection identification is SDCCH / ACCH, and the direction is MS (MCF / TACAF) → NETWORK (SACF / TACF).

(F-1) When the component type is Return Result (when the authentication request is normally performed)
A list of information elements in this case is as shown in FIG.
(F-2) When Component Type is Return Error A list of information elements in this case is as shown in FIG.
(F-3) When Component Type is Reject The list of information elements in this case is as shown in FIG.

(G) Function type: Start Ciphering
This function type is sent from NETWORK to the MS to notify the mobile station of the start of secrecy. A list of information elements in this function type is shown in FIG. As shown in this figure, in this function type, the protocol identifier is MM-T, the connection identification is SDCCH / ACCH, and the direction is NETWORK (SACF / TACF) → MS (MCF / TACAF).

(H) Function type: Start Ciphering
This function type is sent from the MS to the NETWORK as a response signal for the start of secrecy. This signal is classified into three types according to the component type. A list of information elements in this function type is shown in FIGS. 615 to 617 for each type. As shown in these figures, the protocol identifier is MM-T, the connection identification is SDCCH / ACCH, and the direction is MS (MCF / TACAF) → NETWORK (SACF / TACF).

(H-1) When the component type is Return Result (when the start of secrecy is normally performed)
A list of information elements in this case is as shown in FIG.
(H-2) When the component type is Return Error The list of information elements in this case is as shown in FIG.
(H-3) When Component Type is Reject The list of information elements in this case is as shown in FIG.

(I) Function type: IMUI retry (IMUI retrieval)
This function type is sent from the NETWORK to the MS to inquire the mobile station for the IMUI. A list of information elements in this function type is shown in FIG. As shown in this figure, in this function type, the protocol identifier is MM-T, the connection identification is SDCCH, and the direction is NETWORK (SACF / TACF) → MS (MCF / TACAF).

(J) Function type: IMUI retry (IMUI retrieval)
This function type is sent from the MS to the NETWORK in order to notify the exchange of the IMUI in response to the IMUI inquiry. This signal is classified into three types according to the component type. A list of information elements in this function type is shown in FIGS. 619 to 621 for each type. As shown in these figures, the protocol identifier is MM-T, the connection identification is SDCCH, and the direction is MS (MCF / TACAF) → NETWORK (SACF / TACF).

(J-1) When the component type is “Return Result” (when IMUI retry is normally performed)
A list of information elements in this case is as shown in FIG.
(J-2) When Component Type is Return Error A list of information elements in this case is as shown in FIG.
(J-3) When Component Type is Reject The list of information elements in this case is as shown in FIG.

(2.5.2.4.2.3): RBC (Radio Bearer Control) message Next, the RBC message will be described.
(2.5.2.2.4.2.3.1): Message List First, FIG. 622 shows a list of RBC messages.

(2.5.2.2.4.2.3.2): Classification of RBC messages Next, classification of RBC messages will be described. RBC messages can be classified into those that affect the status of RBC-ID (generation / deletion) and messages that do not affect (continuation). Here, FIG. 623 shows RBC message classification (MESSAGE TYPE).

(2.5.2.4.2.3.3.1): Message Configuration Next, the message configuration will be described. Each message is composed of a basic part and an extended part. Furthermore, the basic part consists of message-specific parameters and basic components (options). Here, FIG. 96 shows the message structure, and the constituent elements in the figure are listed below.
Message specific parameters: Parameters specific to the message are set.
Basic information element: Parameters according to the procedure are set, and the basic information element included in the message differs depending on the procedure. It can be used from the time of system introduction.
Extension information element: An information element added when the system is extended.
The basic information element and the extended information element can be set in an arbitrary order. In addition, the component (operation instruction display) to which “*” is assigned is not included at present, and becomes effective when a new message is added in the future as a function is expanded.

(2.5.2.4.2.3.3.2): Information Element Basic Configuration Next, the information element basic configuration will be described. FIG. 97 shows the basic configuration of RBC information. In this figure, the message-specific parameter is an essential parameter in the message. In addition, in each parameter, when there is a variable length, or when there is no parameter setting value used in an optional form, it is displayed that there is no setting. (Set the parameter length or parameter presence / absence bit.)

(2.5.2.2.4.2.3.4): RBC message format Next, the RBC message format will be described.
(2.5.2.4.2.3.4.1): RADIO BEARER SETUP (radio bearer setting)
First, the RADIO BEARER SETUP message will be described. This message is sent from the network to the MS to set up the radio bearer. The information length and the like are as shown in FIG. 624, the protocol identifier is RBC, the connection identification is SDCCH / ACCH, and the direction is Network → MS.

(2.5.4.2.4.2.2.3.4.2): RADIO BERARER RELEASE (radio bearer release)
This message is sent from the network to the MS or the MS to the network to release the radio bearer. The information length and the like are as shown in FIG. 625. The protocol identifier is RBC, the connection identification is ACCH, and the direction is MS → Network, Network → MS.

(2.5.2.2.4.2.2.3.3): RADIO BERARER RELEASE COMPLETE (Radio bearer release complete)
This message is sent from the network to the MS and from the network to the MS to notify that the release of the designated radio bearer has been completed. The information length and the like are as shown in FIG. 626, the protocol identifier is RBC, the connection identification is ACCH, and the direction is Network → MS, MS → Network.

(2.5.2.4.2.3.4.4): HANDOVER COMMAND (handover command)
This message is sent from the network to the MS to designate a radio bearer at the time of handover. The information length and the like are as shown in FIG. 627. The protocol identifier is RBC, the connection identification is ACCH, and the direction is Network → MS.
Note that one or more basic information elements must be set in the HANDOVER COMMAND message.

(2.5.2.4.2.3.4.4): HANDOVER RESPONSE (handover response)
This message is sent to respond to HANDOVER COMMAND (single request for DHO branch deletion activation, single request for DHO branch addition, single request for code switching, and any combination thereof). The information length and the like are as shown in FIG. 628, the protocol identifier is RBC, the connection identification is ACCH, and the direction is MS → Network.

(2.5.2.4.2.4): RRC (Radio Resource Control) message Next, the RRC message will be described.
(2.5.2.2.4.2.4.1): Message List First, FIG. 629 shows a list of RRC messages.
The application of ROSE (Remote Operations Service Element) to the RRC protocol is FFS. The specification and drawings are based on ROSE application.

(2.5.2.2.4.2.4.2): RRC message format Next, the RRC message format will be described.
(2.5.2.4.2.4.2.1): Radio Resource Facility (RADIO RESOURCE FACILITY)
This message is sent from MS to Network to start the RRC procedure. The information length and the like are as shown in FIG. 630, the protocol identifier is RRC, the connection identification is SDCCH / ACCH, and the direction is MS → Network.

(2.5.2.4.2.5): TAC (Terminal Association Control) Message Format Next, the TAC message format will be described. First, FIG. 631 shows a list of RRC message names, and FIG. 632 shows correspondence between message names and information flow names.
Each message is described below.

(2.5.2.4.5.1): TERMINAL ASSOCIATION SETUP (terminal association setting)
This message is sent from the MS to the Network in order to notify the start of TERMINAL ASSOCIATION. The information length and the like are as shown in FIG. 633, the protocol identifier is TAC, the connection identification is SDCCH, and the direction is MS (TACAF) → Network (TACF).

(2.5.2.4.5.2): TERMINAL ASSOCIATION CONNECT (terminal association connection)
This message is sent from the network to the MS in order to notify that the TERMINAL ASSOCIATION SETUP is normally performed with a response signal to the TERMINAL ASSOCIATION SETUP. The information length is as shown in FIG. 634, the protocol identifier is TAC, the connection identification is SDCCH, and the direction is Network (TACF) → MS (TACAF).

(2.5.2.4.5.3): PAGING RESPONSE (paging response)
This message is sent from the MS to the Network as a response to the general call. The information length and the like are as shown in FIG. 635, the protocol identifier is TAC, the connection identification is SDCCH, and the direction is MS (TACAF) → Network (TACF).

(2.5.2.4.5.4): TERMINAL ASSOCIATION RELEASE (Terminal Association Release)
This message is sent from both the Network and the MS to request the release of the TERMINAL ASSOCIATION. The information length and the like are as shown in FIG. 636. The protocol identifier is TAC, the connection identification is SDCCH / ACCH, the direction is Network (TACF) → MS (TACAF), MS (TACAF) → Network (TACF).

(2.5.2.4.2.5): TERMINAL ASSOCIATION RELEASE COMPLETE (Terminal Association Release Complete)
This message is sent from both the Network and the MS as a response signal of TERMINAL ASSOCIATION RELEASE. The information length is as shown in FIG. 637, the protocol identifier is TAC, the connection identification is SDCCH / ACCH, the direction is Network (TACF) → MS (TACAF), MS (TACAF) → Network (TACF).

(2.5.2.4.5.6): PAGE AUTHIZED (page authorized)
This message is sent from the network to the MS in order to notify that the TERMINAL ASSOCIATION has been performed normally. The information length and the like are as shown in FIG. 638, the protocol identifier is TAC, the connection identification is SDCCH / ACCH, and the direction is Network (TACF) → MS (TACAF).

(2.5.2.4.2.6): Others Here, RACH, FACH, BCCH, and PCH layer 3 message will be described. The notation method is the same as that described above.

(2.5.2.2.4.2.6.1): SIGNALING CHANNEL SETUP REQUEST (signaling channel setting request)
Next, SIGNALING CHANNEL SETUP REQUEST will be described. This message is sent from the MS to the BTS to make a request for setting the SDCCH. The information length and the like are as shown in FIG. 639, the connection identification is RACH, and the direction is MS (SCMAF) → BTS (SCMF).
Note that mobile stations that simultaneously make random access within the same sector are identified by PID (packet identifier). This PID is a bit in layer 1 and is a random number assigned by the mobile station.

(2.5.2.2.4.2.6.2): SIGNALING CHANNEL SETUP RESPONSE (Signaling channel setting response)
Next, SIGNALING CHANNEL SETUP RESPONSE will be described. This message is sent from the BTS to the MS to make a request for setting the SDCCH. The information length and the like are as shown in FIG. 640, the connection identification is FACH, and the direction is BTS (SCMF) → MS (SCMAF).
The mobile station is identified by the PID in layer 1.

Next, SIGNALING CHANNEL SETUP FAILURE (signaling channel setting failure) will be described.
This message returns a rejection response from the BTS in response to the SDCCH request from the MS. The information length and the like are as shown in FIG. 641, the connection identification is FACH, and the direction is BTS (SCMF) → MS (SCMAF).
The mobile station is identified by the PID in layer 1.

(2.5.2.2.4.2.6.3): Broadcast information (BROADCAST INFORMATION)
Next, notification information will be described.
First, the broadcast information 1 (BROADCAST INFORMATION 1) will be described. This message is broadcast from the network to notify the user of the control channel structure, information on determination of the standby channel, regulation information, and the like. The information length and the like are as shown in FIG. 642, the connection identification is BCCH, and the direction is BTS (BCFr) → MS (BCAF).

  Next, the broadcast information 2 (BROADCAST INFORMATION 2) will be described. This message is notified to notify the user of call acceptance information from the network. The information length is as shown in FIG. 643, the connection identification is BCCH, and the direction is BTS (BCFr) → MS (BCAF).

(2.5.2.2.4.2.6.4): PAGING (paging)
Next, PAGING will be described. This message is sent to the user to make an incoming call for the first call to the user. The information length is as shown in FIG. 644. The protocol identifier is TAC, the connection identification is PCH, and the direction is BTS (BCFr) → MS (TACAF).
The Paged MS ID (paged MS ID) includes TMUI or IMUI. In addition, an I / T bit for identifying IMUI or TMUI is added to the head. The maximum length of this message is 112 bits. Also, in the figure, for the coding of the item with “*”, in the case of FFS and IMUI calls, the lower digits of the IMUI can be recognized from the PCH group calculation number, so the entire value of the IMUI is used as the Paged MS ID. It is not necessary to set.

(2.5.2.2.3): Information element format Next, the information element format will be described.
(2.5.2.4.3.1): CC
First, CC will be described.
(2.5.2.2.4.3.1.1): Common information element First, the common information element will be described.
The message in this protocol consists of the following parts:
(A) Protocol identifier (protocol discriminator)
(B) Call reference value
(C) Message type (Message types: including message consistency operation instruction display)
(D) Variable length information element (if necessary)

The information elements (a), (b), (c), and (d) are included in all messages. However, the information element (d) is defined according to each message type.
This configuration is shown as an example in FIG. The first three information elements (protocol identifier, call number, message type) must appear in the order specified in FIG. FIG. 98 is a diagram showing a message configuration.

(2.5.2.4.3.1.1.1) Protocol identifier Next, the protocol identifier will be described.
The protocol identifier is provided for the purpose of identifying the user / network call / connection control message from other messages defined in this system, and is coded according to other ITU-T / TTC standards and other standards. The message of this system is identified from the message of the OSI network layer protocol unit to be executed.

  This protocol identifier is arranged at the first of each message and is encoded as shown in FIGS. 99 and 645. 99 and 645 are diagrams for explaining a protocol discriminator (protocol identifier).

  In this system, the definition of the protocol identifier does not include that this protocol can share a signaling virtual channel with other layer 3 protocols. However, other layer 3 protocols are ITU-T Recommendation Q.3. Except when encapsulated in 2931 message. The value in FIG. 645 is an ITU-T recommendation X.X including a general format identifier. Reserved to distinguish the first octet of 25 packets from the protocol identifier.

(2.5.2.4.3.1.1.2) Call reference
The call number is provided on the local user / network interface for the purpose of identifying a message associated with a specific call, via B-ISDN (Broadband Aspects of Integrated Services Digital Network). It is not used for end-to-end. This call number is placed second in each message and is encoded as shown in FIG. The value of the call number length is shown in bits 1 to 4 of octet 1, and the call number information element length is 1 octet.

  The call number information element includes a call number value and a call number flag. The call number value “0” (all bits = “0”) is reserved for the global call number (see FIG. 100). The call number value set to “1” is reserved for the dummy call number value as shown in FIG. 100 and 101 are diagrams for explaining the call number.

  The call number value is assigned to the call on the originating side of the user / network interface. These call number values are essentially unique for the calling party within a particular signaling virtual channel. The call number value is assigned at the start of the call and is maintained for the duration of the call. After the call ends, the call number may be assigned to another call. Thus, if the same value is assigned to each call originated on both sides of the signaling virtual channel link, two equal call number values may be used on the same signaling virtual channel. In order to avoid a race condition due to a wrong scenario, it is desirable to avoid reusing the call number value immediately after release.

  Incidentally, the call reference flag (Call reference flag) takes a value of “0” or “1”. The call number flag is used to identify which side of the signaling virtual channel has generated the call number. In a message from the calling side to the called side, the call number flag is always set to “0”, and in a message from the called side to the calling side, the call number flag is always set to “1”. That is, the call number flag is provided for the purpose of identifying a call number value assigning side for a call and resolving simultaneous assignment to the same call number value. The call number flag is also applied to a procedure using a global call number (eg, initial setting procedure). The value of the global call number is “0”. A device that has received a message including the global call number must treat it as having received this message for all call numbers belonging to this signaling virtual channel (see FIG. 100).

  On the other hand, in coding the dummy call number, all bits of the call number value are set to 1 (see FIG. 101). In the future, dummy call number values are expected to be used for specific supplementary services. For dummy call numbers, flags are also used as described above. Note that the procedure in this system is not used for dummy call numbers. A device compatible with this system must discard the message received with the dummy call number.

(2.5.2.2.4.3.1.2): Message type (Message type)
Next, message types (including message consistency operation instruction display) will be described.
The message type is provided for the purpose of identifying the function of the transmitted message. This message type is arranged at the third position of each message and is encoded as shown in FIGS. 102, 646, and 647. FIG. 102 is a diagram showing a message type format, and FIGS. 646 and 647 constitute one table (a table showing coding of message types). In FIG. 646 and FIG. 647, the value “0000 0000” is used as an escape to the national regulation message. Also, the value “1111 1111” is reserved for the extension mechanism when all other message type values have been used (see FIGS. 646 and 647).

  On the other hand, the message consistency operation instruction display is used for the message transmission side to explicitly display the operation on the peer entity side when an unrecognized message is received. The format and coding of the message consistency operation instruction display are as shown in FIGS. 102, 646, and 647. This message consistency operation instruction display is valid only in the definition section “local”. Unless otherwise specified, which value is set in the operation instruction display of a message transmitted from the network to the user is an option on the network side.

(2.5.2.2.4.3.1.3): Variable length information element in FPLMTS environment Next, the variable length information element in the FPLMTS environment will be described.
(2.5.2.4.3.1.3.1): Coding rules First, coding rules will be described.
The coding of the variable length information element follows the coding rules described below. These rules are designed so that each device that processes a message finds information elements that are necessary for processing and ignores those that are not necessary.

  103 and 104 are diagrams showing the format of the variable length information element in the FPLMTS environment, and FIGS. 648 and 649 constitute one table (table showing the coding of the variable length information element in the FPLMTS environment). For the information elements specified in the following sections, the bit coding of information element identifiers is summarized in FIGS. 103 and 649-648.

  As shown in FIG. 104, the information element identifier value “1111 1111” is reserved for the extended method. If all other information element identifier values have been used, this extended method allows for further 65536 information element identification.

Certain variable length information elements in the message may appear in any order with the following exceptions.
(A) If the information element repeats without using the wideband repeat identifier information element, the following rules apply:
-Repeating information elements must be continuous.
This rule does not apply to broadband fixed shift information elements and broadband temporary shift information elements.

(B) If the information element is repeated using the broadband repetition identifier information element, the following rules apply:
The wideband repeat identifier must precede the first information element repeated.
The first repeated information element (following immediately after the broadband repeat identifier) is interpreted as having the highest priority. Repeated information elements are interpreted in descending order of priority.
-Repeating information elements must be continuous.
The information elements following the broadband temporary shift information element are regarded as one information element by combining the information elements, and the above-mentioned rules are applied. It should be noted that no error occurs when the information element is repeated only once in the message by the broadband repetition identifier information element. That is, the broadband repeat identifier is ignored.

(C) When a broadband fixed shift information element is used, it applies only to all information elements that follow it. The order of these information elements is defined by a new code group indicated by a broadband fixed shift.

(D) When a broadband temporary shift information element is used, it precedes immediately before the target information element.
Note that when the information elements used in the present system include spare bits, these spare bits are set to “0”. Further, when the information element is received, even if the spare bit is not set to “0”, no processing is performed on the spare bit.

  Further, as is apparent from the coding of the information element consistency instruction display shown in FIGS. 648 and 649, the second octet of the information element identifier includes the information element consistency instruction display. This information element consistency instruction display is valid only in the definition section “local”, and unless specified otherwise, which value is displayed in the operation instruction display of the information element included in the message sent from the network to the user. Whether to set is an option on the network side.

  The third and fourth octets of the information element indicate the length of the information element. The length of the information element does not include the lengths of the information element identifier field, the information element consistency indication display field, and the information element length field. In addition, the number of octets in the information element is binary-encoded, and the information element length display is a fixed length of 2 octets. The coding of information element length follows the integer value encoding rule shown in this section.

In this system, there may be an empty information element. For example, a “call setup” (SETUP) message may include a called number information element with an octet length of zero. In this case, the receiving side processes the information element as “not present”. Similarly, when there is no information element, it is processed as “empty information element”. An “empty information element” is an information element that satisfies the following condition.
Condition: It has an (valid) information element identifier and the information element length is zero.

  In this system, the following rules are applied to the coding of information elements. (A) The variable length information element is composed of octets or groups of octets. Octets or octet groups are assigned numbers for ease of reference. The first number in the octet number is an octet or group of octets.

(B) Each octet group is an independent unit within the information element. The internal structure of an octet group may be defined in a manner different from that shown below.

(C) Octet groups are formed through the use of some extension method. A method in which bit 8 is used as the extension bit and octet (N) can be extended to the next octet (Na, Nb,...) Is desirable. For example, a method based on the following rule can be adopted.
Bit value “0” indicates that the octet continues to the next octet. Bit value “1” indicates that this octet is the last octet.
If there is one octet (Nb), the previous octet (N and Na) is also present.
In the description of 2.5.2.2.4.1.3.5, etc., bit 8 is shown as follows.
"0/1 extension" ... when another octet of this octet group follows.
“1 extension”: this is the last octet on the extension area.
-“0 extension”: When another octet of this octet group always follows.

  In addition, when adding a specification, an additional octet can be defined after the last octet before it (in this case, the description of “1 extension” is changed to “0/1 extension”). Devices in the system need to be prepared to accept such additional octets. However, it is not necessary for the device to interpret these octets or to function according to their contents.

(D) In addition to the expansion method defined above, the display is extended to the next octet (N.1, N.2,...) By displaying bits 8 to 1 of octet (N).

(E) The extended methods (c) and (d) can be used in combination. However, extended law c) must have priority in order. Therefore, all octets Na, Nb,. 1, N. Must appear before 2, ... This rule is octet N. 1, N. 2, etc. must also be applied when extended using the extension method of octets Na, Nb,. A similar rule must also be applied when the expansion method (d) is repeated. That is, octet N.I. 1.1, N.I. 1.2, ... are octets Must appear before 2.

(F) Mark optional octets with an asterisk (*).
(G) If the information elements are structured using subfield identifiers, these subfield identifiers are position independent. That is, they need not appear in any particular order within the information elements.

  However, the above expansion method (c) cannot be used repeatedly. That is, the extension method of octet 4a cannot be incorporated into the octet to be octet 4b. Protocol designers should also take care to ensure that the resulting coding is the only interpretation when using multiple extensions. Furthermore, a coding standard field is defined for all information elements. An information element whose coding standard is defined as “national standard” defines the structure in the same way as the standard definition in this system.

  In addition, the following rules are defined in ITU-T Recommendation Q.3. Applies to coding of 2931 integer values. Note that these rules apply when coding is not specified.

(A) If the integer value is coded over 2 octets, the octet with the lower octet number contains the higher order bits. In particular, the octet having the smallest octet number includes the MSB (most significant bit), and the octet having the largest octet number includes the LSB (least significant bit).

(B) The following applies to fields that form within one octet or part of an octet.
-Bits with higher bit numbers include higher order bits.
In particular, the bit of the maximum bit number of integer coding indicates the MSB.
In particular, the bit with the smallest bit number in integer coding indicates LSB.
-Bit coding is performed by filling the small bit numbers (right-justified).
That is, the leading 0 part appears on the side of the octet or the larger bit number (left side) of the field.

(C) When an integer value is expressed in a fixed-length octet, bit coding is performed by filling a large octet number. That is, the leading 0 part appears on the side of the smaller octet number.

(D) When a variable length octet integer value is expressed (for example, when bit 8 is used as an extension bit), coding is performed so that the minimum number of octets is obtained. That is, there is no octet whose preceding contents are all “0”.

(2.5.2.4.1.3.1.2): Expansion of code group Next, the expansion of the code group will be described.
Using the format described in section 2.5.2.2.4.1.3.1.1, the information element identifier can take multiple values.

  Each information element identifier can be expanded to eight code groups, and a common information element identifier is used in each code group in order to facilitate shifting from one code group to another. The contents of the shift information element identify the next information element group or a code group used for the information element. The code group used at any given point in time is used as the “in-use code group”, and implicitly the code group 0 is the initial “in-use code group”. In this system, two code group shift procedures are applied. That is, fixed shift and temporary shift.

The reservation status of each code group is listed below.
Code groups 1 to 3 are reserved for future ITU-T / TTC use.
Code group 4 is reserved for ISO / IEC standard use.
Code group 5 is reserved as a domestic use information element group.
Code group 6 is reserved as an information element group specific to the public network or private network.
The code group 7 is reserved as a user-specific information element group.
Also, the coding rules defined in section 2.5.2.2.4.1.3.1.1 are applied to information elements belonging to any in-use code group.

A shift from one in-use code group to another code group (that is, a fixed shift) is possible only to a code group having a higher numerical value than the original code group.
When the temporary shift procedure is used, the information elements belonging to the code groups 4, 5, 6, and 7 can appear together with the information elements belonging to the code group 0 that is the currently used code group. (Refer to section 2.5.2.2.4.1.3.1.3.4)

  The user or network device should have the ability to recognize both fixed shift and temporary shift information elements as well as the ability to determine the information element length that follows (however, these devices must It does not need to be interpreted or function according to the content). This allows the device to determine the starting position of the subsequent information element.

  Code group 7 is an information element processing procedure that is not recognized except for future service definition, mutual agreement, or preparations to support a specific user via a local network (see ITU-TQ.2931) And is processed on the first exchange of the local network.

  Code group 6 is reserved as an information element specific to the local network (either public or private). As such, it has no meaning through local network boundaries, national or international boundaries. Therefore, the information element of the code group 6 follows the processing procedure of the information element that is not recognized in the first exchange beyond the boundary on the local network (see 5.6.8.1/ITU-TQ.2931). It is processed. However, this does not apply if there is an agreement between the two parties.

  Code group 5 is reserved as an information element for domestic use. As such, it has no meaning through international boundaries. Therefore, the information elements of code group 5 are processed in accordance with the processing procedure of information elements that are not recognized in the first exchange across international boundaries (see 5.6.8.1/ITU-TQ.2931). Is done. However, this does not apply if there is an agreement between the two parties.

Code group 4 is reserved for information elements defined as ISO / IEC standards.
Code groups 1 to 3 are reserved for future ITU-T / TTC use.

(2.5.2.4.3.1.3.3): Broadband-locking shift procedure Next, the broadband fixed-shift procedure will be described.
In the wideband fixed shift procedure, information elements are used to indicate new code groups in use. The designated code group is kept in use until another wideband fixed shift information element designating use of another code group appears. For example, it is assumed that code group 0 is in use at the start of message content analysis. When a wideband fixed shift of the code group 5 appears, the next information element is interpreted according to the information element identifier assigned by the code group 5 until another shift information element appears.

This procedure is used only for shifting to a higher-order code group than the original code group, and is effective only in a message including a wideband fixed shift information element. The code group in use at the start of all message content analysis is the code group 0.
105 and 650 are diagrams for explaining the wideband fixed shift information element. The wideband fixed shift information element is encoded as shown in FIGS. 105 and 650 using the information element format.

(2.5.2.4.3.1.3.4): Broadband Temporary Shift [Broadband-non-locking shift] Procedure Next, the broadband temporary shift procedure will be described.
A wideband temporary shift procedure is used to temporarily shift for lower or higher specified code groups. In this wideband temporary shift procedure, a wideband temporary shift information element is used to indicate a set of codes used to interpret the next single information element. Therefore, after the interpretation of the next single information element, the in-use code group before the temporary shift is used again for the interpretation of any subsequent information element. For example, it is assumed that code group 0 is in use at the start of message content analysis. When a wideband temporary shift of the code group 6 appears, only the next information element is interpreted according to the information element identifier assigned by the code group 6. After the interpretation of this information element, the code group 0 is used again for the interpretation of the subsequent information element. Even if the wideband temporary shift information element indicates the current code group, it should not be regarded as an error.

  The wideband fixed shift information element cannot immediately follow the wideband temporary shift information element. If this combination is received, it should be interpreted that only the broadband fixed shift information element has been received.

  106 and 651 are diagrams for explaining the wideband temporary shift information element. The wideband temporary shift information element is encoded as shown in FIGS. 106 and 651 using the information element format.

(2.5.2.4.3.1.3.5): ATM Adaptation Layer (AAL) parameters (ATM Adaptation Layer parameters)
Next, ATM adaptation layer (AAL) parameters will be described. The ATM adaptation layer (AAL) parameter is an unnecessary parameter in the current system, but this information element may be necessary (FFS) when ATM is applied to a radio section in the future.

  ATM Adaptation Layer (AAL) parameter information elements (ATM Adaptation Layer parameters information elements) have the required ATM Adaptation Layer parameter values (meaning end to end) for the ATM Adaptation Layer procedure elements used for the call. ) And includes parameters for all AAL sublayers selectable by the user. Note that the content of this information element is transparent to the network except in the case of interworking.

  107 to 111 and 652 to 654 are diagrams for explaining the AAL parameter information element, and the AAL parameter information element is encoded as shown in these drawings. The maximum length of this information element is 21 octets.

  In FIG. 108, the octet with the symbol “Note” exists only when the octet 7.1 indicates “n × 64 kbit / s” or “n × 8 kbit / s”. 109 and 110, the octet groups 6 to 8 used in the “response” (CONN) message are displayed in ITU-T Recommendation Q.3. 2931 is specified.

(2.5.2.4.3.1.3.6): ATM traffic descriptor (ATM traffic descriptor)
Next, the ATM traffic descriptor will be described. The ATM traffic descriptor is an unnecessary parameter in the current system, but this information element may be required when ATM is applied to a radio section in the future (FFS).

  The ATM traffic descriptor information element (ATM traffic descriptor information element) is provided for the purpose of defining a traffic parameter set for defining the traffic control capability.

  In this system, the ATM traffic descriptor indicates the value of the ATM peak cell rate (see TTC standard JT-371), and the ATM peak cell rate value (indicated in the ATM traffic descriptor information element) is the user plane information rate and Shows the sum of both all end-to-end user generated OAM (Maintenance / Operation / Management) F5 flows. If the user attempts to use an end-to-end OAMF5 flow message, the peak cell rate in the opposite direction of the one-way connection must not be displayed as “0”. Note that the peak cell rate is described by an integer value indicating the number of cells per second in 3 octets following the subfield.

  112 and 655 are diagrams for explaining the ATM traffic descriptor information element, and the ATM traffic descriptor information element is encoded as shown in these figures. The maximum length of this information element is 20 octets.

  In FIG. 112, when there is a peak cell rate of CLP = 0, the difference between the peak cell rate of CLP = 0 + 1 and the peak cell rate of CLP = 0 is used for network resource allocation by CLP = 1. Must be assumed. Also, if there is only a peak cell rate of CLP = 0 + 1, the network resource allocation must assume that the full peak cell rate can be used with CLP = 0.

(2.5.2.4.3.1.3.7): Broadband bearer capability
Next, the broadband transmission capability will be described. The broadband transmission capability is an unnecessary parameter in the current system, but this information element may be required when ATM is applied to the radio section in the future (FFS).

  The broadband bearer capacity information element is set for the purpose of displaying a necessary broadband connection oriented bearer service (see ITU-T-F811). (Note that the service is provided by the network.) Therefore, the broadband transmission capability information element is included only in the information used by the network. For the use of the broadband transmission capability information element for confirming communication possibility, see ITU-TQ. See 2931.

  There is no default for this broadband capability, and the broadband capability information element is processed by both network and user devices.

113 and 656 are diagrams for explaining the broadband transmission capability information element, and the broadband transmission capability information element is encoded as shown in these drawings. The maximum length of this information element is 7 octets.
In FIG. 113, the octet with the symbol “Note” can exist only when the bearer class “X” is displayed in octet 5.

(2.5.2.4.3.1.3.8): Broadband higher layer information (B-HLI) Next, broadband higher layer information will be described. Broadband high layer information information element checks for communication with addressed entities (eg, remote users addressed by originating users, interworking units, higher layer functional nodes of the network) It is set for the purpose of providing a means for performing. The broadband higher layer information information element is carried transparently within the B-ISDN network between the originating entity (eg, originating user) and the addressed terminating entity.

  114 and 657 are diagrams for explaining the broadband higher layer information information element, and the broadband higher layer information information element is encoded as shown in these drawings. The maximum length of this information element is 13 octets.

(2.5.2.4.3.1.3.9): Broadband lower layer information (B-LLI) Next, broadband lower layer information will be described. Broadband low layer information element can communicate to addressed entities (eg, remote users addressed by originating users, interworking units, higher layer functional nodes of the network) It is set for the purpose of providing a means for confirmation.

  This broadband lower layer information information element is carried transparently within the B-ISDN network between the originating entity (eg, originating user) and the addressed terminating entity. Also, for the negotiation of broadband lower layer information (see ITU-T Recommendation Q.2931), the broadband lower layer information information element passes transparently from the addressed called entity to the originating entity.

  115 to 116 and FIGS. 658 to 660 are diagrams for explaining the broadband lower layer information information element, and the broadband lower layer information information element is encoded as shown in these drawings. The maximum length of this information element is 17 octets.

  115 and 116, the octet to which (Note 1) is attached exists only when the octet 6 indicates the procedure of the confirmation type HDLC shown in FIGS. 658 to 660. Also, the octet with (Note 2) is present only when octet 6 indicates a user-specific layer 2 protocol. In addition, the octet to which (Note 3) is added is an ITU-T recommendation X. octet whose octet 7 is shown in FIGS. 658 to 660. 25 ISO / IEC8208 or X.25. 223 Present when referring to a Layer 3 protocol based on ISO / IEC8878. The octet with (Note 4) is present only when octet 7 indicates a user-specific layer 3 protocol. An octet with (Note 5) is present only when octet 7 indicates ISO / IEC TR9577.

(2.5.2.4.3.1.3.11): Called party number
Next, the called number will be described. A called party number information element is provided for the purpose of displaying a communication partner.

  117 and 661 are diagrams for explaining the called number information element, and the called number information element is coded as shown in these drawings. Note that the maximum length of this information element depends on the network.

  In FIG. 117, the number digits appear in the same order as input from the lower 4 bits of octet 6. The digits are encoded with BCD. If the use of the NSAP address is displayed for the address / number plan identification, the address is X. 213: It is coded with the expression of ISO / IEC8348. Furthermore, the filler is “1111”.

(2.5.2.4.3.1.3.12): Called party sub-address
Next, the destination subaddress will be described. A called sub address information element (Called party sub-address element) is provided for the purpose of indicating a sub address of a communication partner. For the definition of subaddress, see ITU-T Recommendation I.D. See 330.

118 and 662 are diagrams for explaining the destination subaddress information element, and the destination subaddress information element is encoded as shown in these drawings. The maximum length of this information element is 25 octets.
(2.5.2.4.3.1.3.13): Calling party number

  Next, the calling number will be described. A calling party number information element is provided for the purpose of displaying a call originator.

  119 and 663 to 664 are diagrams for explaining the calling number information element, and the calling number information element is coded as shown in these drawings. Note that the maximum length of this information element depends on the network.

  In FIG. 119, in the part marked with “Note 1”, the number digits appear in the same order as the order entered from the lower 4 bits of octet 6. The digits are encoded with BCD. When the use of the NSAP address is displayed for the address / number plan identification in the part marked “Note 2”, the address is X. It is encoded with the expression of 213 ISO / IEC8348. In addition, it is assumed that the filler to which “Note 3” is attached is “1111”.

(2.5.2.4.3.1.1.34): Calling sub-address (Calling party sub-address)
Next, the originating sub address will be described. The calling sub address information element (Calling party sub-address information element) is provided for the purpose of displaying the call originator.

  120 and 663 to 665 are diagrams for explaining the originating sub-address information element, and the originating sub-address information element is encoded as shown in these figures. Regarding the definition of the sub-address, the recommendation I.I. See 330. The maximum length of this information element is 25 octets.

(2.5.2.4.3.1.3.15): Reason display (Cause)
The contents and usage of the reason display information element are described in ITU-T Recommendation Q.3. 2610.

(2.5.2.4.3.1.3.16): Connection identifier
Next, the connection identifier will be described. The connection identifier is an unnecessary parameter in the current system, but this information element may be required when ATM is applied to a wireless section in the future (FFS).

  The connection identifier information element is used to identify a local ATM connection resource on the interface. This information element is present as an option in the “call setup” (SETUP) message, and is present as an option in the initial response to the “call setup” (SETUP) message.

  121 and 666 are diagrams for explaining the connection identifier information element, and the connection identifier information element is encoded as shown in these drawings. The length of this information element is 9 octets.

  In FIG. 121, when the “change addition display” field specifies “arbitrary VCI”, the VCI field must be ignored. When the restart class is “001” (see ITU-T recommendation Q.2931), the VCI field must be ignored. Furthermore, if VP-compatible signaling is indicated in octet 5, the VPCI field must be ignored.

(2.5.2.4.3.1.3.17): End-to-end transit delay
Next, end-to-end relay delay will be described. The end-to-end transit delay information element indicates the actual maximum end-to-end relay delay allowed per call and the cumulative relay delay expected for a virtual channel connection. It is set for the purpose of showing. This relay delay is the end-to-end one-way relay delay of user data transferred during the data transfer phase on the user plane between the originating user and the terminating user, and includes:

-Total processing time in end-user system (eg processing time, AAL handling delay, ATM cell assembly delay, any other processing delay)
-Network transfer delay (eg propagation delay, ATM layer transfer delay, any other intra-network processing delay)

  Note that the cumulative relay delay value (if any) indicated by the calling user in the “call setup” (SETUP) message indicates the relay delay from the calling user to the network boundary. Also, the cumulative relay delay value indicated by the network in the “call setup” (SETUP) message sent to the called user is the sum of the value indicated by the originating UNI and the transfer delay accumulated in the network, Does not include the transfer delay in the route to the subsequent incoming user. In addition, the cumulative relay delay value sent on both UNIs in the “answer” (CONN) message is the total end-to-end relay delay expected for user data transfer on the associated virtual channel connection provided for the call. Value.

  The maximum end-to-end relay delay value can also be used by the calling user to indicate the end-to-end relay delay request for the call. This field is included by the network in a “Call Setup” (SETUP) message and is used to indicate that the originating user has specified an end-to-end relay delay request for this call. For applicable procedures, see ITU-TQ. See 2931. Also, the maximum end-to-end relay delay is not included in the “response” (CONN) message.

  122 and 667 are diagrams for explaining the end-to-end relay delay information element, and the end-to-end relay delay information element is encoded as shown in these figures. The maximum length of this information element is 10 octets.

(2.5.4.2.4.3.1.3.18): Quality of Service (QOS) Parameter Next, the quality of service (QOS) parameter will be described.
In this system, in addition to the above-described end-to-end relay delay, a QOS parameter information element (Quality of Service parameter information element) is defined. The QOS parameter information element is set for the purpose of indicating a certain QOS class.

  Quality of Service (QOS) parameter information elements are not supported in B-ISUP Release 1. In other words, a network cannot transmit a QOS parameter information element, and such a network generates a default value (no QOS class designation) as a QOS parameter information element for transfer to a terminating user via a termination interface. Will do.

  123 and 668 are diagrams for explaining the quality of service (QOS) parameter information element, and the quality of service (QOS) parameter information element is coded as shown in these figures. The maximum length of this information element is 6 octets.

(2.5.2.4.3.1.3.19): Broadband Repeat indicator
Next, the broadband repetition identifier will be described.
The broadband repeat indicator information element is set for the purpose of indicating how to repeat the information element that is repeated in the message when it is included in the message. , Before the first of the information elements repeated in the message. However, when an information element that exists only once in a message and a wideband repetition identifier information element are combined, it should not be considered as an error.

  124 and 669 are diagrams for explaining the wideband repetition identifier information element, and the wideband repetition identifier information element is encoded as shown in these drawings. The maximum length of this information element is 5 octets.

(2.5.2.4.3.1.20): Initial setting display (Restart indicator)
Next, the initial setting display will be described.
Details of the initial setting display are matters to be defined in the future (FFS).
The initialization display information element is provided for the purpose of identifying the facility class to be initialized.

(2.5.2.4.3.1.3.21): Broadband sending complete
Next, completion of broadband transmission will be described. The broadband sending complete information element is provided for the purpose of indicating the completion of the called number as an option (see ITU-T recommendation Q.2931).
This information element is indispensable in the case of the collective mode procedure, but in the absence of this information element, it is not necessary to apply the regular error processing of “insufficient information element shortage”.
FIG. 125 is a diagram for explaining the wideband repetition identifier information element, and the wideband repetition identifier information element is encoded as shown in this figure. This information element length is 5 octets.

(2.5.2.4.3.1.3.22): Transit network selection
Next, relay network selection will be described. The relay network selection information element is provided for the purpose of indicating one requesting relay network. The relay network selection information element may appear repeatedly in one message to indicate the order of the relay networks through which the call must pass (see ITU-TQ.2931).

  126 and 670 are diagrams for explaining the relay network selection information element, and the relay network selection information element is coded as shown in these drawings. Note that the maximum length of this information element depends on the network.

(2.5.2.4.3.1.2.3.23): Notification identifier
Next, the notification identifier will be described. The notification identifier information element (Notification indicator information element) is provided for the purpose of notifying information related to a call.

  FIG. 127 is a diagram for explaining the notification identifier information element, and the notification identifier information element is coded as shown in these drawings. The maximum length of this information element can be applied within a range that does not contradict the maximum length of the message.

(2.5.2.4.3.1.2.34): OAM traffic descriptor (OAM traffic descriptor)
Next, the OAM traffic descriptor will be described. The OAM traffic descriptor is an unnecessary parameter in the current system, but this information element may be required when ATM is applied to the radio section in the future (FFS).

  The OAM traffic descriptor information element is provided for the purpose of providing information on the end-to-end OAM F5 information flow for performance management related to user connections included in calls and user-generated fault management. It has been. For the definition of the processing of this OAM traffic descriptor information element, see ITU-TQ. See 2931.

  128 and 671 are diagrams for explaining the OAM traffic descriptor information element, and the OAM traffic descriptor information element is encoded as shown in these figures. This information element length is 6 octets.

(2.5.2.4.2.3.1.4): Information elements for supporting a 64 kbit / s based circuit switched mode ISDN service Next, to support a 64 kbit / s based circuit switched mode ISDN service. The information elements of will be described.

(2.5.2.4.3.1.4.1): Coding rules First, coding rules will be described. The information elements described in this section 2.5.2.4.3.1.4 use a general information element format similar to that shown in FIG. The coding of these information elements is described in ITU-T Recommendation Q.3. 931 / ITU-TQ. Follow the 2931 coding rules.

(2.5.2.4.3.1.4.2): Narrowband bearer capability
Next, the narrow band transmission capability will be described. Narrowband transmission capability is an unnecessary parameter in the current system, but this information element may be required when ATM is applied in the future radio section (FFS).

  Narrowband bearer capability information element is provided to indicate a request for a narrowband ISDN circuit switched mode bearer service provided by the network and may be used by the network Contains information only (see ITU-T recommendation Q.931). For the usage of the narrowband transmission capability information element related to the communication possibility confirmation, see ITU-T Recommendation Q.3. See 931. Note that the narrowband transmission capability information element is transmitted transparently in the broadband ISDN.

  FIG. 129 is a diagram for explaining the narrowband transmission capability information element, and the narrowband transmission capability information element is encoded as shown in this figure and table.

(2.5.2.4.3.1.4.3): Narrowband high layer compatibility (Narrowband high layer compatibility)
Narrowband high layer compatibility information element (Narrowband high layer compatibility information element)
) Is provided for the purpose of providing a procedure for the other user to check the communication possibility (see ITU-T recommendation Q.931).

  FIG. 130 is a diagram for explaining the narrowband high layer compatibility information element, and the narrowband high layer compatibility information element is encoded as shown in this figure. The maximum length of this information element is 7 octets.

  However, the narrowband higher layer consistency information element is used within the broadband ISDN to be the originating entity (eg, the originating user) and the terminating entity addressed by the originating entity (eg, the partner user or network). Of the higher layer function node). If explicitly requested by the user at the time of subscription, the network with the capability to perform teleservice may analyze this information to provide a specific teleservice.

(2.5.2.4.3.1.4.4): Narrowband low layer compatibility (Narrowband low layer compatibility)
Next, narrowband low layer compatibility will be described. A narrowband low layer compatibility information element is associated with an addressed entity (eg, a remote user addressed by an originating user, an interworking unit, or a higher layer functional node of the network). It is provided for the purpose of providing means for confirming communication possibility.

  This narrowband lower layer consistency information element is carried transparently within the broadband ISDN between the originating entity (eg, originating user) and the terminating entity addressed by the originating entity. Also, for narrowband lower layer compatibility negotiation (see ITU-T recommendation Q.931), the narrowband lower layer compatibility information element is carried transparently from the called entity to the originating entity.

  FIG. 131 is a diagram for explaining the narrowband low layer compatibility information element, and the narrowband low layer compatibility information element is encoded as shown in this figure. The maximum length of this information element is 20 octets.

(2.5.2.4.3.1.4.5): Progress indicator
Next, the progress identifier will be described. The progress identifier information element (Progress indicator information element) is provided for the purpose of representing an event that occurred during call generation, and this information element may be included twice in the message.
FIG. 132 is a diagram for explaining the progress identifier information element, and the progress identifier information element is encoded as shown in FIG. The maximum length of this information element is 6 octets.

(2.5.2.4.3.2): MM-T information element format Next, the MM-T information element format will be described. Hereinafter, each information element will be described in order based on the list of MM-T specific information elements shown in FIG. 672.

(1) TMUI
First, TMUI will be described. The TMUI is a temporary number for identifying a mobile station and is updated at the time of location registration / location update. The TMUI is basically not updated except when the network side recognizes a TMUI mismatch at the time of outgoing / incoming call.
FIG. 133 is a diagram for explaining TMUI. In this figure, TMUI = M-SCP identification number (10 bits) + unique identification number (20 bits + 2 bits), and normal binary coding. To do. However, “2 bits” in the above equation indicates a double allocation avoidance bit. Further, the M-SCP Identification Number (M-SCP identification number) is used for identifying the M-SCP to which the TMUI is assigned, and takes a value of 0-999. Furthermore, the Unique Identification Number (unique identification number) is used for identifying the mobile station in the TMUI allocation node, and takes a value of 0 to 999999. The Double Assignment Evaluation Bit (TMUI double allocation avoidance bit) is used to avoid TMUI double allocation, and takes a value of 0 to 3.

(2) TMUI Assignment Source ID (TMUI Assignment Source ID)
Next, TMUI Assignment Source ID will be described. As shown in FIG. 134, the TMUI Assignment Source ID includes MCC (Mobile Country Code), MNC (Mobile Network Code), and LAI. In this system, BCD coding is used.

(3) IMUI
Next, IMUI will be described with reference to FIG. The IMUI is a number capable of recognizing a mobile station and is used in the network. In this system, the variable length is up to 15 digits including MCC and MNC, and is BCD coding.

(4) Execution Authentication Type (execution authentication type)
Next, the Execution Authentication Type will be described with reference to FIG. Execution Authentication Type is information for specifying an authentication procedure when the mobile station has a plurality of authentication procedures.

(5) Authentication Random Pattern (authentication random number)
Next, the Authentication Random Pattern will be described with reference to FIG. The Authentication Random Pattern indicates a random pattern for performing authentication in the mobile station.

(6) Authentication Ciphering Pattern (authentication calculation result)
Next, with reference to FIG. 138, the Authentication Ciphering Pattern will be described. The Authentication Ciphering Pattern indicates an encryption pattern obtained from an authentication random number in the mobile station.

(7) Execution Ciphering Type (Execution Secret Type) Next, the Execution Ciphering Type will be described with reference to FIG. Execution Ciphering Type is information that specifies which concealment procedure is used when the mobile station has a plurality of concealment procedures.

(8) TC Info (MS type)
Next, TC Info will be described with reference to FIG. TC Info is information used to identify the type of mobile station.

(2.5.2.4.3.3): RBC message information element Next, the RBC message information element will be described.
(2.5.2.4.3.1): Message type First, the message type will be described. As is clear from FIG. 141, the message type is provided in a form that does not include an operation instruction display in order to identify the function of the message to be transmitted. Various types in the figure will be described later.

(2.5.2.4.3.3.3.2): Information Element Identifier Next, the information element identifier will be described with reference to FIG. The information element identifier identifies optional information included in each message. When the first octet is “11111111”, the second and subsequent octets are valid. For the second and subsequent octets, the next octet is validated by the extension flag (bit 8). Note that no identifier is set for each unique parameter. Each information element identifier will be described later.

(2.5.2.4.3.3.3.3): RADIO BEARER SETUP Message Specific Parameters FIG. 143 shows the configuration of the RADIO BEARER SETUP message specific parameters. In this figure, RBC_ID is a number for identifying a connection identified by CR + CONN_ID on the CC protocol and an RBC connection corresponding to one-to-one, and CR (call number) is a call identifier for CC (2. CONN_ID is a CC connection identifier (see 2.5.2.4.1).

(2.5.2.4.3.3.3.4): RADIO BEARER RELEASE message specific parameter FIG. 144 shows the configuration of the RADIO BEARER RELEASE message specific parameter. As shown in this figure, the RADIO BEARER RELEASE message specific parameter is composed of an RBC_ID and a reason display.

(2.5.2.4.3.5): RADIO BEARER RELEASE COMPLETE message specific parameter FIG. 145 shows the configuration of the RADIO BEARER RELEASE message specific parameter. As shown in this figure, the RADIO BEARER RELEASE COMPLETE message specific parameter is composed of only RBC_ID.

(2.5.2.4.3.3.3.6): HANDOVER COMMAND message specific parameter FIG. 146 shows the configuration of the HANDOVER COMMAND message specific parameter. As shown in this figure, the HANDOVER COMMAND message-specific parameter is composed only of INVOKE_ID. Note that INVOKE_ID is an identification number for taking correspondence with the response signal when HANDOVER COMMAND is activated.

(2.5.2.4.3.3.3.7): HANDOVER RESPONSE message specific parameter FIG. 147 shows the configuration of the HANDOVER RESPONSE message specific parameter. As shown in this figure, the HANDOVER RESPONSE message specific parameter is composed only of INVOKE_ID.

(2.5.2.4.3.3.3.8): Radio Bearer Setting Information FIGS. 148 to 151 show the configuration of the radio bearer setting information. In FIG. 148, the “information element identifier” is the RADIO BEARER SETUP basic information element part (8 bits), the “length” is the length of the information element, and the “frequency band” is the frequency band set in the first call (call) ( f1: “00000000” to f256: “11111111”), “BTS number” is the BTS identification number (1 to) in the network, and “sector number” is the sector identification number in the BTS (1: “00000001” to 12: “ "00001100"), "Uplink short code type" is the information transfer rate per uplink code (see Fig. 150), and "Uplink number" is when using uplink multicode (use multiple short codes as uplink codes for one connection) The number of upstream short codes (1 to N), “upstream short code number” is the upstream show Code identification number (0 to 2047), “Downlink short code type” is information transfer rate per downlink code (see FIG. 150), “Downlink code number” is when downlink multicode is used (downlink code for one connection) The number of downlink short codes (1 to M) when a plurality of short codes are used is shown.

  The “downlink short code number” is an identification number (0-2047) of the downlink shortcode, and the “frame offset group” is downlinked when the mobile station communicates to equalize traffic within one frame time of the wired section. It indicates which time slot in one radio frame of the radio link is the leading edge of the logical frame, and takes 0 to 15 (see FIG. 151). The “slot offset group” is a value (0 to 3) obtained by shifting the downlink transmission timing in units of subslots in each slot for each short code in order to reduce pilot symbol overlap. The slot offset group remains unchanged until all Calls in the mobile station are released (see FIG. 151).

(2.5.2.4.3.3.3.9): DHO addition FIGS. 152 to 154 show the configuration of DHO addition. In FIG. 152, “information element identifier” indicates 8 bits indicating DHO addition, and the number of RBC_IDs indicates the number of simultaneously set connections (1 to H). The other components are as described above.

(2.5.2.4.3.3.10): DHO Deletion FIG. 155 shows a DHO deletion configuration. In FIG. 155, the “information element identifier” is 8 bits representing DHO deletion, and the other components are as described above.

(2.5.2.4.3.3.11): ACCH switching FIG. 156 shows a configuration of ACCH switching. In FIG. 156, the “information element identifier” is 8 bits representing DHO deletion, and the other components are as described above.

(2.5.2.4.3.3.12): Branch switching FIGS. 157 to 159 show the configuration of branch switching. In FIG. 157, the “information element identifier” is 8 bits representing branch switching, and the other components are as described above.

(2.5.2.4.3.3.13): User Rate Switching FIGS. 160 to 163 show the configuration of user rate switching. In FIG. 160, the “information element identifier” is 8 bits representing user rate switching, and the other components are as described above.

(2.5.2.4.3.3.14): Code switching FIGS. 164 to 165 show the configuration of code switching. In FIG. 164, “information element identifier” is 8 bits indicating code switching, and “old short code number” is the number of old short code numbers (1 to N) for switching (short code rearrangement), “old short code”. “Code number” is the identification number (0-2047) of the short code used before the switching (short code rearrangement) process, and “New short code number” is the new short that performs the switching (short code rearrangement) process. The number of code numbers (1 to M) and “new short code number” indicate an identification number (0 to 2047) of a new short code used after the switching (short code rearrangement) process. The elements are as described above.

(2.5.2.4.3.4): RRC message information element Next, the RRC message information element will be described.
(2.5.4.2.4.3.4.1): Message Type First, the message type will be described with reference to FIG. The message type is for identifying the function of the message to be transmitted.

(2.5.2.2.4.3.4.2): Facility Next, the structure of the facility is shown in FIG. In FIG. 167, “profile” indicates the type (ROSE protocol, CMIP protocol, ACSE protocol) of PDU (protocol data unit) stored after 4 octets, and “PDU” indicates ASE (application service element) identified by the profile. PDU. A “PDU” can store a plurality of PDUs, and this system uses the ROSE protocol.

(2.5.2.4.4.3.3): ROSE PDU
Next, the configuration of the ROSE PDU is shown in FIGS. 168 and 169. In FIG. 168, the “component type tag” is for identifying the component type (startup, result response (final), error response, rejection, result response (midway), etc.) shown in the figure. Required for components. “Component length” indicates the length of the component excluding the component type tag and the component length field, and the “invoke identifier tag” is used as a reference number for uniquely identifying the operation start, and associates the request with the response. . “Invogue identifier length” indicates the length of the field of the invogue identifier, “Invogue identifier” indicates the invogue identifier (startup ID), and “Operation value tag” is included in the “startup” component, etc. Used to indicate local operation, global operation). Further, the “operation value” defines a specific operation (transmission / reception candidate zone information, communicating zone information, DHO addition zone information, DHO deletion zone information, HHO execution zone information, outer loop information, quality deterioration notification information). .

(2.5.2.4.3.4.4): Operation-specific parameters Next, the operation-specific parameters will be described.
(A) Transmission / Reception Candidate Zone Information First, the transmission / reception candidate zone information will be described.
This operation is activated in the direction from the MS to the Network in order to notify the network of the radio status of the standby sector at the time of outgoing / incoming calls measured by the MS and the radio status of the surrounding sectors. Each parameter is shown in FIG.
In the figure, the perch CH reception SIR value and the perch CH transmission power value are used for downlink transmission power control.

(B) Communication Zone Information Next, communication zone information will be described.
This operation is sent from the MS to the Network to activate the radio channel downlink transmission power control based on the radio state of the communicating sector measured in the MS. Each parameter is shown in FIG.

(C) DHO additional zone information Next, the DHO additional zone information will be described.
This operation is used by the MS to activate the addition of the diversity link during communication to the network, and includes information on the additional candidate sector, the radio status of the additional candidate sector, and the radio status of the communicating sector. Each parameter is shown in FIG.
Note that only sectors that exceed the DHO additional threshold value are set as compared with the communication-in-service sector. If the candidate sector is in a condition worse than all the communication-in-service sectors during communication with the maximum number of branches, the DHO trigger is not transmitted as DHO additional zone information.

(D) DHO deletion zone information Next, the DHO deletion zone information will be described.
This operation is used to trigger diversity link deletion for the network based on the radio status of the communicating sector measured at the MS. Each parameter is shown in FIG.
In this function type, only sectors that exceed the DHO deletion threshold as compared with the communication-in-service sector are set. It should be noted that this function type is not used for sectors that may be replaced and deleted by adding DHO addition candidates (although the DHO deletion threshold is not exceeded).

(E) HHO execution zone information Next, the HHO execution zone information will be described.
This operation is used to start execution of branch switching handover for the network based on the radio conditions of the communicating sector and peripheral sectors measured in the MS. FIG. 677 shows each parameter.

(F) Outer Loop Information Next, the outer loop information will be described.
This operation is used for the MS to activate the outer loop transmission power control of the downlink radio channel for the network. Each parameter is shown in FIG.

(G) Quality degradation notification information Next, quality degradation notification information will be described.
This operation is used to initiate a branch switching handover to a different frequency channel for the network when the MS detects downlink radio channel quality degradation. Each parameter is shown in FIG.

(2.5.2.4.4.3): Operation-Specific Parameter Definition Next, the operation-specific parameter definition will be described.
(2.5.2.4.3.4.5.1): Number of in-zone candidate sectors, number of in-service sector sectors, number of DHO addition candidate sectors, number of DHO deletion sectors, number of HHO candidate sectors FIG. 170 shows the configuration of the number of candidate sectors, the number of in-service sectors, the number of DHO addition candidate sectors, the number of DHO deletion sectors, and the number of HHO candidate sectors. As for the “sector number” in FIG. 170, 1 to N are displayed in binary.

(2.5.2.4.3.4.5.2): BTS number FIG. 171 shows the structure of the BTS number. In FIG. 171, “BTS identifier” is a number (1 to 1) that can identify the BTS in the network.

(2.5.2.4.3.4.5.3): Sector number FIG. 172 shows the structure of the sector number. In FIG. 172, the “sector number” is a number (1 to 12) that can identify the sector in the BTS.

(2.5.2.4.3.4.5.4): Perch CH received SIR value FIG. 173 shows the structure of the perch CH received SIR value. In FIG. 173, “Perch CH reception SIR” indicates reception SIR of the perch CH of the serving sector, the peripheral sector, and the communicating sector measured by the MS.

(2.5.2.4.3.4.5.5): Perch CH transmission power value FIG. 174 shows the configuration of the perch CH transmission power value.

(2.5.2.4.3.4.5.6): Long code phase difference FIG. 175 shows the configuration of the long code phase difference. In FIG. 175, “Long code phase difference” indicates a long code phase difference between a standby sector or a communicating sector and a peripheral sector (handover destination sector), and is used when other zones are selected for DHO and outgoing / incoming calls. Is done. If it exceeds 128 [chip], it is extended with an extension bit (extended with the value “1”).

(2.5.2.4.3.4.5.7): Number of RBC IDs FIG. 176 shows the configuration of the number of RBC IDs. In FIG. 176, the “number of RBC IDs” is displayed in binary and takes a value of 1 to N.

(2.5.2.4.3.4.5.8): RBC ID
FIG. 177 shows the configuration of the RBC ID. In FIG. 177, “RBC_ID” is a number (1 to H) that identifies a connection identified by “CR + CONN_ID” and a one-to-one RBC connection on the CC protocol.

(2.5.2.4.3.4.5.9): Required SIR
FIG. 178 shows the configuration of the required SIR.

(2.5.2.4.3.4.10): FER measurement value FIG. 179 shows the configuration of the FER measurement value.

(2.5.2.4.3.5): Format of TAC (Terminal Association Control) Information Element Next, the format of the TAC information element will be described.
(2.5.2.4.5.1): TAC (Terminal Association Control) message format overview

First, an outline of the TAC message format will be described. The message in this protocol consists of the following parts:
(A) protocol discriminator (protocol identifier)
(B) Message type (message type)
(C) Message specific parameters (if necessary)
(D) Basic information elements (if necessary)
(E) Extended information element (if necessary)

  The information elements (a) and (b) are included in common in all messages. However, the information elements (c) to (e) are defined according to each message type.

  This configuration is shown as an example in FIG. The first two information elements (protocol discriminator, Message type) must appear in the order specified in FIG. FIG. 180 is a diagram showing a message configuration.

(2.5.2.4.3.5): protocol discriminator
First, the protocol discriminator will be described.
The protocol discriminator is provided for the purpose of discriminating the TAC message from other messages defined in this system, and is encoded by other ITU-T / TTC standards and other standards. The TAC message is identified from the unit message. The protocol discriminator is arranged at the first position of each message and is encoded as shown in FIG. FIG. 181 is a diagram for explaining the Protocol discriminator.

(2.5.2.4.5.3): Message type (including Message compatibility instruction indicator)
Next, Message type will be described. Message type is provided for the purpose of identifying the function of the message to be sent. This Message type is arranged second in each message and is encoded as shown in FIGS. 182 and 680. FIG. 182 and FIG. 680 are diagrams showing the format of Message type.

  Note that the Message compatibility instruction indicator is valid only in the definition section “local”, and what value is set in the Message compatibility instruction indicator that is sent to the user from the network, unless otherwise specified. Is an option on the network side (“000” is set in this system).

(2.5.2.4.5.4): Message-specific parameters Message-specific parameters are used to set information specific to the message, and will be described in detail below.
(2.5.2.4.3.5.4.1): TAC message unique parameters First, a list of TAC message unique parameter names is shown in FIG.

(1) TERMINAL ASSOCIATION SETUP message specific parameter (terminal association setting message specific parameter)
The TERMINAL ASSOCIATION SETUP message specific parameter information element is encoded as shown in FIGS. 183 and 682.

(2) PAGING RESPONSE message specific parameter (paging response message specific parameter) The PAGING RESPONSE message specific parameter information element is encoded as shown in FIGS. 184 and 683.

(3) TERMINAL ASSOCIATION RELEASE message specific parameter (terminal association release message specific parameter)
Also, the TERMINAL ASSOCIATION RELEASE message specific parameter information element is encoded as shown in FIGS. 185 and 684.

(2.5.2.4.3.5.4.2): Subfield of TAC message specific parameter Next, the subfield of the TAC message specific parameter will be described. (1) Coding rules

  First, coding rules will be described. The coding of the TAC message specific parameter subfield follows the coding convention described below. These specifications are specified so that each device that processes a message finds information elements that are necessary for processing. FIG. 685 shows a list of information element names of subfields of the TAC message specific parameter.

For the coding of integer values of TAC, the following rules apply:
(A) If the integer value is coded over 2 octets, the octet with the lower octet number contains the higher order bits. In particular, the octet with the smallest octet number is the MSB, and the octet with the largest octet number includes the LSB.
(B) The following applies to fields that form within one octet or part of an octet.
-Bits with higher bit numbers include higher order bits.
In particular, the bit of the maximum bit number of integer coding indicates the MSB.
In particular, the bit with the smallest bit number in integer coding indicates LSB.
-Bit coding is performed by filling the small bit numbers (right-justified).
In other words, the leading 0 part appears on the side of the large bit number (left side) of the field.
(C) When an integer value is expressed in a fixed-length octet, bit coding is performed by filling a large octet number. That is, the leading 0 part appears on the side of the smaller octet number.
(D) When expressing a variable-length octet integer value, coding is performed so that the minimum number of octets is obtained. That is, there is no octet whose preceding contents are all “0”.

(2) Cause (reason display)
Next, Cause will be described. The Cause information element is used to indicate the reason for releasing the TERMINAL ASSOCIATION, and is encoded as shown in FIGS. 186 and 686.

(3) Mobile station type (mobile station type)
Next, Mobile station type will be described. The Mobile station type information element is used to identify the type of mobile station, and is encoded as shown in FIGS. 187 and 687.

(4) Paged MS ID
Next, the Paged MS ID will be described. The Paged MS ID information element is used to identify the calling mobile station and is encoded as shown in FIGS. 188 and 688.

(5) Paging ID
Next, Paging ID will be described. The Paging ID information element is used for managing a call when a mobile station is called, and is a number temporarily assigned when a mobile station is simultaneously called. This Paging ID information element is encoded as shown in FIG.

(6) TMUI
Next, TMUI will be described. The TMUI information element is used for identifying a mobile station, and is a number updated at the time of location registration and location update. This TMUI information element is encoded as shown in FIGS. 190 and 689.

(2.5.2.4.3.5): Extended Information Element Next, the extended information element will be described. The TAC extension information element is not used in this system and is used for future extension. This TAC extension information element is encoded as shown in FIG.

(2.5.2.4.3.6): Others Here, RACH, FACH, BCCH, and PCH layer 3 messages are specified.
(2.5.2.4.3.6.1): Message type FIG. 192 shows the structure of the message type information element.

(2.5.2.4.3.6.2): Information element length The information element length information element sets the information element length of the message, and its configuration is shown in FIG.

(2.5.2.4.3.6.3): perch reception SIR
The perch reception SIR information element sets the reception SIR of the perch measured by the MS, and its configuration is shown in FIG.

(2.5.2.4.3.6.6.4): Short code number The short code number information element is used to set the upper and lower SDCCH short code numbers (0 to 2047). 195.

(2.5.2.2.4.3.6.5): Frame offset group The frame offset group information element sets a frame offset group for SDCCH, and its configuration is shown in FIG.

(2.5.2.4.3.6.6.6): Slot offset group The slot offset group information element sets a slot offset group for SDCCH, and its configuration is shown in FIG.

(2.5.2.4.3.3.6.7): Network number The configuration of the network number information element is shown in FIG.

(2.5.2.4.3.3.6.8): Network VER
The VER information element of the network indicates the VER of the network, and its configuration is shown in FIG.

(2.5.2.4.4.3.6.9): Mobile station common parameter VER
The mobile station common parameter VER information element indicates the VER of the mobile station common parameter, and its configuration is shown in FIG.

(2.5.2.4.3.6.10): BTS number The BTS number information element indicates the identification number of the BTS, and its configuration is shown in FIG.

(2.5.2.4.3.6.11): Sector number The sector number information element indicates a sector number (for example, 1 to 6, or 1 to 12) in the BTS. 202.

(2.5.2.4.3.6.12): Location registration area multiplexing number (N)
The location registration area multiplexing number (N) information element represents the location registration area multiplexing number multiplexed in the radio zone, and its configuration is shown in FIG.

(2.5.2.4.3.6.13): Location number The location number information element represents a location registration area (0 to 255) in which the mobile station is located. Show.

(2.5.2.4.3.6.14): Location Registration Timer FIG. 205 shows the configuration of the location registration timer information element.

(2.5.2.4.3.6.15): Corrected Base Station Required Received Power Value FIG. 206 shows the configuration of the corrected base station required received power value information element.

(2.5.2.4.3.6.16): Own station uplink long code number In the future (FFS), the RACH and SDCCH uplink long code numbers are set.

(2.5.2.4.3.6.17): Number of perimeter LCs for area zone determination (M) The configuration of the number of perimeter LCs for area zone determination (M) is shown in FIG.

(2.5.2.4.3.6.18): perch LC number The perch LC number is for future use (FFS).

(2.5.2.4.3.6.19): Number of frequency bands used by base station (K)
The base station use frequency band number (K) information element sets the number of frequency bands in which TCH exists in this sector, and its configuration is shown in FIG.

(2.5.2.4.3.6.20): Frequency band The frequency band information element sets the frequency band used in the TCH, and its configuration is shown in FIG.

(2.5.2.4.3.6.21): Restriction information The restriction information information element displays the restriction during construction, failure restriction and access restriction to the mobile station and will be used in the future. (FFS).

(2.5.2.4.3.6.22): Call admission information The call admission information element displays the status of whether or not a new call can be accepted to the mobile station. Used (FFS).

(2.5.2.4.3.6.23): Control CH structure information (including for packet) The control CH structure information information element includes the number of PCH, RACH-S / L, FACH-S / L and The code number to be used and the slot position are set and used in the future (FFS).

(2.5.2.4.3.6.24): BCCH reception section length The BCCH reception section length information element indicates a period during which the mobile station should receive BCCH after receiving a message including this information element. The structure is shown in FIG.

(2.5.2.4.3.6.25): Number of calling mobile stations The number of calling mobile stations information element represents the number of calling mobile stations (1-2) included in one call message. The configuration is shown in FIG.

(2.5.2.4.3.6.26): Paged MS ID
The Paged MS ID information element is a 112-bit information element for setting IMUI or TMUI, and its configuration is shown in FIG. Detailed coding will be determined in the future (FFS).

(2.5.2.4.3.6.27): Paging ID
FIG. 213 shows the configuration of the Paging ID information element.

(2.5.2.4.3.6.28): Extended information elements Other extended information elements will be determined in the future (FFS).

(2.5.3): BTS-MCC interface specification Next, the BTS-MCC interface specification will be described.
(2.5.3.1): Overview First, an overview will be described. Section 2.5.3 defines each protocol from layer 1 to layer 3 in the BTS-BCC interface.

(2.5.3.2): Layer 1
Since Layer 1 is defined in the base station transmission path interface and the switching center transmission path interface, description thereof is omitted here.

(2.5.3.3): ATM layer As described above, the ATM layer is defined in the base station transmission path interface and the switching center transmission path interface, and thus the description thereof is omitted here.

(2.5.3.4): AAL common part As described above, the AAL common part is defined in the base station transmission line interface and the switching center transmission line interface, and thus the description thereof is omitted here.

(2.5.3.5): AAL individual unit Since the AAL individual unit is defined in the base station transmission path interface and the switching center transmission path interface in the same manner as described above, description thereof is omitted here.

(2.5.3.6): Layer 3
Hereinafter, layer 3 will be described.

(2.5.3.6.1): Protocol Architecture First, the layer 3 protocol architecture in this interface will be described.
First, the Layer 3 protocol control entity defined in this system will be described.

The Procedure (procedure) that appears in the BTS-BCC interface is as follows.
(1) BTS-MCC link control procedure-SCMF-TACF / SACF SDCCH link setup and release procedure-TACF-BCFr access link setup, release procedure, etc. (2) Paging procedure-Notification of paging from TACF to BTS (3) Radio state management procedure Radio channel state measurement procedure between RFTR and RRC (however, this procedure is not used in this system)
(4) Other procedures such as information transfer to BTS

Based on the above procedure, this system defines the following Layer 3 protocol control entities.
(A) BC (Bearer Control): Forms and transfers a message for link control between TACF and BCFr. That is, the above procedure (1) is handled.
(B) BSM (Base Station Management): Forms and forwards Paging notification to the BTS and other BTS management messages. The above procedures (2) and (4) are handled.
(C) RCM (Radio Condition Management): Forms and transfers messages for measuring the state of radio resources. This protocol control entity is not used in this system.

  Next, the protocol architecture in this interface will be described. Messages from the Data link Layer on the control signal link of the BTS-MCC interface are distributed according to Protocol Discriminator, Link Reference (link reference), and Transaction ID (transaction ID) and transferred to each protocol control entity. Here, FIG. 214 shows a conceptual diagram of the protocol architecture on the BTS-MCC interface.

(2.5.3.6.2): Message format Next, the message format will be described.
(2.5.3.6.2.1): BC message First, the BC message will be described.

(2.5.3.6.2.1.1.1): Message Type (Type) List First, a message type (type) list of BC messages is shown in FIG. As shown in this figure, a bearer setup message, a bearer release message, and other messages are prepared as BC messages.

(2.5.3.6.1.2.1.2): Classification of BC Message Type In this system, BC protocol messages are classified as follows. -AAL type 2 link setup / release message for TCH or SDCCH-Request for setup / release of AAL type 2 link for ACCH and request for control of radio channel in BTS Included as an information element in the message. Alternatively, when control of the TCH / SDCCH AAL type 2 link is not performed simultaneously with these requests, a message not related to the state transition of the BC protocol entity is defined and transmitted and received as an information element in this message.
FIG. 691 shows BC message classification based on such rules.

(2.5.3.6.1.2.1.3): Message structure Each message is composed of a message common part and a basic information element (option). Here, FIG. 215 shows a message structure. In addition, since the parameter according to the procedure is set as the basic information element, the basic information element included in the message differs depending on the procedure.

(2.5.3.6.2.1.3.1): LINK SETUP REQUESTED (Link Setup Requested)
First, a message whose message name is LINK SETUP REQUEST will be described. This message is sent from the BTS to the MSCNW (BSC function) in order to select the short cell connection corresponding to the above-mentioned resource after selecting the short code and radio equipment in the BTS at the start of SDCCH establishment. FIG. 692 shows the information length and the like of each information element of this message. The protocol identifier of this message is BC, the connection identification is a control signal between BTS and MSCNW (BSC function), and the direction is BTS (SCMF) → MSCNW (BSC function) (SACF / TACF).

(2.5.3.6.2.1.3.2): LINK SETUP (Link Setting) Next, a message whose message name is LINK SETUP will be described. This message is sent from the MSCNW (BSC function) to the BTS when the short cell connection can be selected by the MSCNW (BSC function) (only when the TCH is set). In addition, in order to activate a radio bearer in the BTS, it is sent from the MSCNW (BSC function) to the BTS. FIG. 693 shows the information length and the like of each information element of this message. The protocol identifier of this message is BC, the connection identification is a control signal between BTS and MSCNW (BSC function), the direction is MSCNW (BSC function) (SACF / TACF) → BTS (SCMF) and MSCNW (BSC function) (TACF) → BTS (BCFr).

(2.5.3.6.2.1.1.3): LINK SETUP PROCEEDING (link setting proceeding)
Next, a message whose message name is LINK SETUP PROCEEDING will be described. This message is sent from the BTS to the MSCNW (BSC function) in order to notify the selection result of the radio resource at the time of the first call, the second call, and the HHO and the activation result of the radio equipment. FIG. 694 shows the information length and the like of each information element of this message. The protocol identifier of this message is BC, the connection identification is a control signal between BTS and MSCNW (BSC function), and the direction is BTS (BCFr) → MSCNW (BSC function) (TACF).

(2.5.3.6.2.1.3.4): LINK SETUP RESPONSE (link setting response)
Next, a message whose message name is LINK SETUP RESPONSE will be described. If this message is the first radio branch at the time of the first call, the second call, and the HHO, in order to notify that the setting of the radio bearer has been completed, the selection result of the radio resource and the radio equipment are provided at the time of the second call, the DHO. Is sent from the BTS to the MSCNW (BSC function). Also, it is sent from the BTS to the MSCNW (BSC function) in order to notify the synchronization establishment result in the base station when the SDCCH is established. FIG. 695 shows the information length and the like of each information element of this message. The protocol identifier of this message is BC, the connection identification is a control signal between BTS and MSCNW (BSC function), and the direction is BTS (BCFr) → MSCNW (BSC function) (TACF) and BTS (SCMF) → MSCNW (BSC function). (SACF / TACF).

(2.5.3.6.2.1.3.5): LINK FACILITY
Next, a message whose message name is LINK FACILITY will be described. This message is sent from the MSCNW (BSC function) to the BTS in order to request additional activation / deletion activation of radio resources and radio equipment at the time of intra-cell HOSHO, or to activate ACCH switching. FIG. 696 shows the information length of each information element of this message. The protocol identifier of this message is BC, the connection identification is a control signal between BTS and MSCNW (BSC function), and the direction is MSCNW (BSC function) (TACF) → BTS (BCFr).

(2.5.3.6.2.1.3.6): LINK FACILITY
Next, a message whose message name is LINK FACILITY will be described. Note that this message has a different direction from the above-mentioned LINK FACILITY. This message is sent from the BTS to the MSCNW (BSC function) in order to notify the additional activation result / deletion activation result of the radio resource and radio equipment at the time of intra-cell HOSHO, or to notify the squelch of the ACCH switching activation result. FIG. 697 shows the information length of each information element of this message. The protocol identifier of this message is BC, the connection identification is a control signal between BTS and MSCNW (BSC function), and the direction is BTS (BCFr) → MSCNW (BSC function) (TACF).

(2.5.3.6.2.1.3.7): LINK RELEASE (link release)
Next, a message whose message name is LINK RELEASE will be described. This message is sent from the MSCNW (BSC function) to the BTS to release the radio bearer. FIG. 698 shows the information length and the like of each information element of this message. The protocol identifier of this message is BC, the connection identification is a control signal between BTS-MSCNW (BSC function), the direction is MSCNW (BSC function) (TACF) → BTS (BCFr) and MSCNW (BSC function) (SACF / TACF) ) → BTS (SCMF).

(2.5.3.6.2.1.3.8): LINK RELEASE COMPLETE (link release complete)
Next, a message whose message name is LINK RELEASE COMPLETE will be described. This message is sent from the BTS or MSCNW (BSC function) to indicate that the device sending the message has released LINK REFERENCE and CONNECTION IDENTIFIER (connection identifier). The device receiving this message must release LINK REFERENCE. FIG. 699 shows the information length of each information element of this message. The protocol identifier of this message is BC, the connection identification is a control signal between BTS-MSCNW (BSC function), and the direction is BTS (BCCFr) → MSCNW (BSC function) (TACF) and BTS (SCMF) ← MSCNW (BSC function) ) (SACF / TACF).
Note that this information element is essential when this message is the first LINK REFERENCE release message. Further, when this message is transmitted as a result of the error processing condition, this information element is included in this message.

  As a supplement, the following FIGS. 700 to 706 show a list of basic information element configurations of LINK SETUP, LINK SETUP PROCEEDING, LINK SETUP RESPONSE, and LINK FACILITY in each pattern.

(2.5.3.6.2.2): BSM message format Next, the BSM message format will be described.
Here, the message configuration will be described first. As shown in FIG. 216, each message includes a protocol identifier, a message type, and basic information elements.

  Next, the basic configuration of the information element is shown in FIG. As is clear from this figure, the basic information element is configured to always set an information element identifier and an information element length before each parameter.

  Next, FIG. 707 shows a list of message types of BSM messages. As is clear from this figure, only PAGING is prepared as the BSM message.

(2.5.3.6.2.2.2.1): PAGING
Here, a message whose message name is PAGING will be described. This message is sent from the NW (BSC function) to the BTS to make an incoming call to the MS. FIG. 708 shows the information length and the like of each information element of this message. The protocol identifier of this message is BSM, the connection identification is BTS to NW (BSC function) control signal, and the direction is NW (BSC function) (TACF) → BTS (BCFr).
The “position number” is necessary when a plurality of position numbers are set in the BTS, and this corresponds to multi-layer position registration control. In addition, IMUI / TMUI is integrated with Paged MS ID in the definition of information elements. This system is indispensable.

(2.5.3.6.2.3): Information Element Next, the information element will be described.
(2.5.3.6.2.2.3.1): BC information element First, the BC information element will be described.
(2.5.3.6.2.3.1.1): Information Element Basic Configuration First, FIG. 218 shows an information element basic configuration.

(2.5.3.6.2.2.3.1.1.1): LINK ID (Link ID) Basic Information Element Next, FIG. 709 shows the information length and the like of the LINK ID basic information element. This basic information element uses LINK SETUP and LINK RELEASE messages, and the direction is NW (BSC function) (SACF / TACF) → BTS (SCMF / BCFr).

(2.5.3.6.2.2.3.1.1.2): Frequency unspecified TCH setup request information element (call initiated)
Next, FIG. 710 shows the information length and the like of this frequency non-designated TCH setup request information element. This basic information element uses a LINK SETUP message, and its direction is NW (BSC function) (TACF) → BTS (BCFr).

(2.5.3.6.2.2.3.1.1.3): Frequency unspecified type TCH setup request information element (active)
Next, FIG. 711 shows the information length and the like of this frequency non-designated TCH setup request information element. This basic information element uses a LINK SETUP message, and its direction is NW (BSC function) (TACF) → BTS (BCFr).

(2.5.3.6.2.2.3.1.1.4): Frequency unspecified type TCH setting request information element Next, the information length and the like of this frequency unspecified type TCH setting request information element are shown in FIG. Show. This basic information element uses a LINK SETUP message, and its direction is NW (BSC function) (TACF) → BTS (BCFr).

(2.5.3.6.2.2.3.1.5): DHO addition request information element The information length of the DHO addition request information element is shown in FIG. This basic information element uses a LINK SETUP message, and its direction is NW (BSC function) (TACF) → BTS (BCFr).

(2.5.3.6.2.2.3.1.1.6): INTRA BS DHO addition request information element (intra BS DHO addition request information)
Next, FIG. 714 shows the information length of the INTRA BS DHO addition request information element. This basic information element uses a LINK SETUP, LINK FACILITY (NW (BSC function) → BTS) message, and its direction is NW (BSC function) (TACF) → BTS (BCFr).

(2.5.3.6.2.3.3.1.1.7): ACCH setting request information element Next, the information length and the like of the ACCH setting request information element are shown in FIG. This basic information element uses a LINK SETUP, LINK FACILITY (NW (BSC function) → BTS) message, and its direction is NW (BSC function) (TACF) → BTS (BCFr).

(2.5.3.6.2.2.3.1.1.8): Frequency unspecified type TCH setting acceptance information element (call initiated)
Next, FIG. 716 shows information length and the like of this frequency non-designation type TCH setting acceptance information element. This basic information element uses a LINK SETUP PROCEEDING message, and its direction is BTS (BCFr) → NW (BSC function) (TACF).

(2.5.3.6.2.2.3.1.1.9): Frequency unspecified type TCH setting acceptance information element (active)
Next, FIG. 717 shows the information length and the like of this frequency non-designated TCH setting acceptance information element. This basic information element uses a LINK SETUP PROCEEDING message, and its direction is BTS (BCFr) → NW (BSC function) (TACF).

(2.5.3.6.2.2.3.1.10): Frequency non-designated TCH setting acceptance information element Next, FIG. 718 shows the information length of this frequency non-designated TCH setting acceptance information element. Show. This basic information element uses a LINK SETUP PROCEEDING message, and its direction is BTS (BCFr) → NW (BSC function) (TACF).

(2.5.3.6.2.3.1.1.1.11): Frequency unspecified type TCH setup response information element (call initiated)
Next, FIG. 719 shows information length and the like of this frequency non-designated TCH setup response information element. This basic information element uses a LINK SETUP RESPONSE message, and its direction is BTS (BCFr) → NW (BSC function) (TACF).

(2.5.3.6.2.3.3.1.1.12): Frequency unspecified type TCH setup response information element (active)
Next, FIG. 720 shows information length and the like of this frequency non-designated TCH setup response information element. This basic information element uses a LINK SETUP RESPONSE message, and its direction is BTS (BCFr) → NW (BSC function) (TACF).

(2.5.3.6.2.3.1.1.13): Frequency unspecified type TCH setting response information element Next, the information length and the like of this frequency unspecified type TCH setting response information element are shown in FIG. Show. This basic information element uses a LINK SETUP RESPONSE message, and its direction is BTS (BCFr) → NW (BSC function) (TACF).

(2.5.3.6.2.3.1.1.14): DHO additional setting response information element Next, the information length and the like of this DHO additional setting response information element are shown in FIG. This basic information element uses a LINK SETUP RESPONSE message, and its direction is BTS (BCFr) → NW (BSC function) (TACF).

(2.5.3.6.2.2.1.3.1.15): INTRA BS DHO additional setting response information element Next, the information length and the like of this INTRA BS DHO additional setting response information element are shown in FIG. This basic information element uses a LINK SETUP RESPONSE message and a LINK FACILITY message, and its direction is BTS (BCFr) → NW (BSC function) (TACF).

(2.5.3.6.2.3.1.1.16): ACCH setting response information element Next, the information length and the like of this ACCH setting response information element are shown in FIG. This basic information element uses a LINK SETUP RESPONSE message and a LINK FACILITY message, and its direction is BTS (BCFr) → MSCNW (BSC function) (TACF).

(2.5.3.6.2.2.1.3.1.17): INTRA BS DHO additional setting request information element Next, the information length and the like of this INTRA BS DHO additional setting request information element are shown in FIG. This basic information element uses a LINK FACILITY message, and its direction is NW (BSC function) (TACF) → BTS (BCFr).

(2.5.3.6.2.2.1.3.1.18): INTRA BS DHO Deletion Setting Request Information Element Next, FIG. 726 shows the information length of this INTRA BS DHO deletion setting request information element. This basic information element uses a LINK FACILITY message, and its direction is NW (BSC function) (TACF) → BTS (BCFr).

(2.5.3.6.2.3.1.1.1.19): INTRA BS HHO setting request information element Next, the information length and the like of this INTRA BS HHO setting request information element are shown in FIG. This basic information element uses a LINK FACILITY message, and its direction is NW (BSC function) (TACF) → BTS (BCFr).

(2.5.3.6.2.3.1.1.20): ACCH Release Request Information Element Next, the information length and the like of this ACCH release request information element are shown in FIG. This basic information element uses a LINK FACILITY message, and its direction is NW (BSC function) (TACF) → BTS (BCFr).

(2.5.3.6.2.2.1.1.21): Frequency non-designation type switching setting request information element Next, the information length and the like of this frequency non-designation type switching setting request information element are shown in FIG. Show. This basic information element uses a LINK FACILITY message, and its direction is NW (BSC function) (TACF) → BTS (BCFr).

(2.5.3.6.2.2.1.1.22): Frequency unspecified type switching setting request information element Next, the information length and the like of this frequency unspecified type switching setting request information element are shown in FIG. Show. This basic information element uses a LINK FACILITY message, and its direction is NW (BSC function) (TACF) → BTS (BCFr).

(2.5.3.6.2.3.1.1.23): Setting Completion Notification Information Element Next, the information length and the like of this setting completion notification information element are shown in FIG. This basic information element uses a LINK FACILITY message, and its direction is NW (BSC function) (TACF) → BTS (BCFr).

(2.5.3.6.2.2.1.3.1.14): INTRA BS HHO Deletion Setting Response Information Element Next, FIG. 732 shows the information length and the like of this INTRA BS HHO deletion setting response information element. This basic information element uses a LINK FACILITY message, and its direction is BTS (BCFr) → NW (BSC function) (TACF).

(2.5.3.6.2.3.3.1.25): INTRA BS HHO additional setting response information element Next, the information length and the like of this INTRA BS HHO additional setting response information element are shown in FIG. This basic information element uses a LINK FACILITY message, and its direction is BTS (BCFr) → NW (BSC function) (TACF).

(2.5.3.6.2.3.1.1.26): ACCH Release Response Information Element Next, the information length and the like of this ACCH release response information element are shown in FIG. This basic information element uses a LINK FACILITY message, and its direction is BTS (BCFr) → NW (BSC function) (TACF).

(2.5.3.6.2.3.1.1.27): Frequency designation type switching setting response information element Next, the information length and the like of this frequency designation type switching setting response information element are shown in FIG. This basic information element uses a LINK FACILITY message, and its direction is BTS (BCFr) → NW (BSC function) (TACF).

(2.5.3.6.2.3.1.1.28): Frequency designation type switching setting request information element Next, the information length and the like of this frequency designation type switching setting request information element are shown in FIG. 736. This basic information element uses a LINK FACILITY message, and its direction is BTS (BCFr) → NW (BSC function) (TACF).

(2.5.3.6.2.2.1.1.29): Frequency non-designation type switching setting reception information element Next, the information length of this frequency non-designation type switching setting reception information element is shown in FIG. Show. This basic information element uses a LINK FACILITY message, and its direction is BTS (BCFr) → NW (BSC function) (TACF).

(2.5.3.6.2.3.1.1.30): Frequency unspecified type switching setting response information element Next, the information length and the like of this frequency unspecified type switching setting response information element are shown in FIG. 738. Show. This basic information element uses a LINK FACILITY message, and its direction is BTS (BCFr) → NW (BSC function) (TACF).

(2.5.3.6.2.3.1.1.31): Code switching request information element Next, the information length and the like of this code switching request information element are shown in FIG. 739. This basic information element uses a LINK FACILITY message, and its direction is BTS (BCFr) → NW (BSC function) (TACF).

(2.5.3.6.2.3.1.1.32): TCH release request information element Next, the information length and the like of this TCH release request information element are shown in FIG. This basic information element uses a LINK RELEASE message, and its direction is NW (BSC function) (TACF) → BTS (BCFr).

(2.5.3.6.2.3.1.1.33): SDCCH Release Request Information Element Next, the information length and the like of this SDCCH release request information element are shown in FIG. This basic information element uses a LINK RELEASE message, and its direction is NW (BSC function) (SACF / TACF) → BTS (BCMF).

(2.5.3.6.2.2.1.3.34): CAUSE
Next, FIG. 742 shows information length and the like of this CAUSE. This basic information element uses a LINK RELEASE COMPLETE message, and its direction is BTS (BCFr) → NW (BSC function) (TACF) and BTS (SCMF) → NW (BSC function) (SACF / TACF).

(2.5.3.6.2.3.1.1.35): SDCCH setting request information element Next, FIG. 743 shows the information length and the like of this SDCCH setting request information element. This basic information element uses a LINK SETUP REQUESTED message, and its direction is BTS (SCMF) → NW (BSC function) (SACF / TACF).

(2.5.3.6.2.3.1.1.36): LAI Setting Request Information Element Next, the information length and the like of this LAI setting request information element are shown in FIG. This basic information element uses a LINK SETUP REQUESTED message, and its direction is BTS (SCMF) → NW (BSC function) (SACF / TACF).

(2.5.3.6.2.3.1.3): Information element definition (BC)
Next, the definition of each information element is shown.
(2.5.3.6.2.2.3.1.2.1): Protocol identifier First, the protocol identifier will be described.
The protocol identifier is set for the purpose of identifying the BC message from other messages defined in this system. The protocol identifier also identifies a message in the system from OSI network layer protocol unit messages encoded by other ITU-T Recommendations / TTC standards and other standards.
This protocol identifier is placed first in each message and is encoded as shown in FIGS. 219 and 745.

(2.5.3.6.2.2.3.1.2.2): Message Type Next, the message type will be described. The message type is set for the purpose of identifying the function of the message to be sent. This message type is arranged second in each message and is encoded as shown in FIGS. 220 and 746.

(2.5.3.6.2.2.3.1.2.3): LINK REFERENCE
Next, LINK REFERENCE will be described. LINK REFERENCE is set for the purpose of identifying individual instances of the BC protocol entity generated for each AAL TYPE 2 / TYPE 5 (AAL Type 2 / Type 5) link for TCH or SDCCH. This LINK REFERENCE is coded as shown in FIG.

  In the figure, “flag” indicates an E / A flag. This flag is “0” when sent from the generation side of LINK REFERENCE, and “1” when sent to the generation side of LINK REFERENCE. Become. In the figure, it is assumed that the second and subsequent octets are expanded by the value of LINK REFERENCE used.

(2.5.3.6.2.3.3.1.2.4): Information element identifier (INFORMATION ELEMENT IDENTIFIER)
Next, the information element identifier will be described. The information element identifier is for identifying an optional information element included in each message, and is encoded as shown in FIG.

(2.5.3.6.2.2.3.1.2.5): Information element length (LENGTH OF INFORMATION ELEMENT)
Next, the information element length will be described. The information element length indicates the length of all parameters set in the basic information element, and is encoded as shown in FIG.

(2.5.3.6.2.2.3.1.2.6): AAL TYPE and LINK IDENTIFIER (AAL type and link identifier)
First, AAL TYPE will be described. AAL TYPE represents an AAL type and is coded as shown in FIG. Here, “0010” represents AAL type 2 and “0101” represents AAL type 5.

  Next, FIG. 225 shows a coding example of LINK IDENTIFIER. In the figure, the sizes of VPCI and VCI (virtual channel identifiers) are based on ATM standard (UNI (user / network interface)) standard cells. As for VPCI, there are one type (using 0) in this system, 16 (4 bits) or more in commercial use, 256 / VPCI for VCI, and 256 / VCI for UCI.

(2.5.3.6.2.3.3.1.2.7): Transmission quality (TRANSMISION QUALITY)
Next, transmission quality will be described. The transmission quality designates the quality of the ATM link and is coded as shown in FIG. In this system, it is assumed that the allowable delay is 3 bits, the cell discard rate is 3 bits, and the reservation is 2 bits.

(2.5.3.6.2.2.3.1.2.8): Downlink transmission rate (TRANSMISION RATE (Fwd: Downlink))
Next, the downlink transmission rate will be described. The downlink transmission rate indicates a downlink information transfer rate. The downlink transmission speed in this system is assumed to be 8 kbps / 12.8 kbps / 32 kbps / 34.4 kbps / 64 kbps / 76.8 kbps / 128 kbps / 162.4 kbps / 384 kbps.

(2.5.3.6.2.2.3.1.2.9): Upstream transmission rate (TRANSMISSION RATE (Rvs))
Next, the uplink transmission rate will be described. The uplink transmission rate indicates the uplink information transfer rate. As an uplink transmission rate in this system, 8 kbps / 12.8 kbps / 32 kbps / 34.4 kbps / 64 kbps / 76.8 kbps / 128 kbps / 162.4 kbps / 384 kbps is assumed.

(2.5.3.6.2.3.1.3.10.): Sector number (SECTOR NUMBER)
Next, the sector number will be described. The sector number is a number (1 to 12) for identifying a sector in the BIS, and is coded as shown in FIG.
(2.5.3.6.2.2.3.1.11): Information transfer capability (BEARER CAPABILITY)

Next, the information transfer capability will be described. The information transfer capability is encoded as shown in FIG. 228, and this system assumes voice / packet / unrestricted digital.
(2.5.3.6.2.3.3.1.2.12): Frequency band selection condition (FREQENCY SELECTION INFO.)

  Next, frequency band selection conditions will be described. The frequency band selection condition is an information element notified from the switching station to the base station when the base station selects a frequency in a frequency band that can be used by the mobile station, and takes a value of 0 to 255. The base station selects a band with good resource selection conditions under an AND condition with a frequency band that can be used by the base station itself. This frequency band selection condition is coded as shown in FIG.

(2.5.3.6.2.3.1.3.13): Frequency band (FREQENCY)
Next, the frequency band will be described. The frequency band information element indicates a frequency band selected in the base station, and simultaneous connection connections in the mobile station are in the same frequency band. This frequency band takes f1 to f256 and is encoded as shown in FIG.

(2.5.3.6.2.3.1.2.14): Frame offset group (FRAME OFFSET GROUP)
Next, the frame offset group will be described. The frame offset group indicates which time slot in one radio frame of the downlink radio link is the head of the logical frame when the mobile station communicates in order to equalize the traffic within one frame time of the wired section. It takes a value from 0 to 15, and is coded as shown in FIG.
(2.5.3.6.2.3.1.2.15): Slot offset group (FRAME OFFSET GROUP)

  Next, the slot offset group will be described. The slot offset group indicates a value (0 to 15) obtained by shifting the downlink transmission timing for each short code in units of subslots in order to reduce the overlap of pilot symbols, and the value captured by the BTS at the time of the first call. NW (BSC function) manages and sets in this information. The slot offset group at the time of the first call does not change until all the calls in the mobile station are released. This slot offset group is coded as shown in FIG.

(2.5.3.6.2.2.1.3.16): Long code phase difference information (LONG CODE PHASE DIFFERENCE)
Next, the long code phase difference will be described. The long code phase difference is the long code phase calculated from the long code counter (SFN) of the perch that is waiting, or the long code counter of the perimeter of the upstream long code phase and the peripheral sector (handover destination sector) during communication. This is the difference (chip) from the long code phase calculated from (SFN), and is used when other zones are selected for DHO and outgoing / incoming calls. This long code phase difference is measured by the MS and reported to the NW (BSC function). In this system, 0 to 2-1 Chip is assumed, and coding is performed as shown in FIG. If the phase difference of the long code exceeds 128 Chip, it is extended by an extension bit.
(2.5.3.6.2.3.3.1.17): Long long code number (LONG CODE NUMBER (Rvs))

  Next, the upstream long code number will be described. The in-communication upstream long code number is information unique to the mobile station, and this information can be used continuously even if the frequency band is changed. This upstream long code number is encoded as shown in FIG.

(2.5.3.6.2.3.1.2.18): Upstream short code type (SHORT CODE TYPE (Rvs))
Next, the uplink short code type will be described. The upstream short code type is coded as shown in FIG.

(2.5.3.6.2.3.1.2.19): Number of uplink codes (NUMBER of SHORT CODE (Rvs))
Next, the number of uplink codes will be described. The number of uplink codes indicates the number of uplink short codes when using an uplink multicode (when a plurality of short codes are used as uplink CHs for one connection), and is coded as shown in FIG.

(2.5.3.6.2.3.1.2.20): Upstream short code number (SHORT CODE NUMBER (Rvs))
Next, the upstream short code number will be described. The uplink short code number is a number (0 to 1023) for identifying the uplink short code, and is a unique number in the uplink long code (MS). Note that the ACCH is set first. Further, the BTS recognizes that setting of ACCH is necessary when VPCI, VCI, and UCI (for ACCH) are simultaneously specified. This upstream short code number is encoded as shown in FIG.

(2.5.3.6.2.2.3.1.21): Downstream short code type (SHORT CODE TYPE (Fwd))
Next, the downlink short code type will be described. The downlink short code type is coded as shown in FIG.

(2.5.3.6.2.3.3.1.2.22): Number of downlink codes (NUMBER of SHORT CODE (Fwd))
Next, the number of downlink codes will be described. The number of downlink codes indicates the number of downlink short codes when using a downlink multicode (when a plurality of short codes are used as downlink CHs for one connection), and is coded as shown in FIG.

(2.5.3.6.2.2.3.1.2.23): AAL TYPE and LINK IDENTIFIER (for ACCH) (AAL type and link identifier (for ACCH))
First, AAL TYPE for ACCH will be described. This AAL TYPE represents an AAL type, is fixed to AAL type 2 (“0010”), and is encoded as shown in FIG.
Next, FIG. 241 shows a coding example of LINK IDENTIFIER for ACCH. Note that separate values may be used for LINK IDENTIFIER and TCH.

(2.5.3.6.2.3.1.2.24): Transmission quality (for ACCH) (TRANSMISION QUALITY (for ACCH))
Next, transmission quality for ACCH will be described. This transmission quality specifies the quality of the ATM link, and is encoded as shown in FIG. In this system, it is assumed that the allowable delay is 3 bits, the cell discard rate is 3 bits, and the reservation is 2 bits, and a fixed value is also assumed.

(2.5.3.6.2.3.1.2.25): Downlink transmission rate (for ACCH) (TRANSMISION RATE (Fwd) (for ACCH))
Next, the downlink transmission rate for ACCH will be described. This downlink transmission rate indicates a downlink information transfer rate, and is restricted by a code used in TCH. The downlink transmission speed in this system is assumed to be 8 kbps / 12.8 kbps / 32 kbps / 34.4 kbps / 64 kbps / 76.8 kbps / 128 kbps / 162.4 kbps / 384 kbps.

(2.5.3.6.2.3.1.2.26): Uplink transmission rate (for ACCH) (TRANSMISION RATE (Rvs) (for ACCH))
Next, the uplink transmission rate for ACCH will be described. This uplink transmission rate indicates an uplink information transfer rate, and is restricted by a code used in the TCH. As an uplink transmission rate in this system, 8 kbps / 12.8 kbps / 32 kbps / 34.4 kbps / 64 kbps / 76.8 kbps / 128 kbps / 162.4 kbps / 384 kbps is assumed.

(2.5.3.6.2.3.1.2.27): Downward short code number (SHORT CODE NUMBER (Fwd))
Next, the downlink short code number will be described. The downlink short code number is a number (0 to 1023) for identifying the downlink short code, and is a unique number in the downlink long code (MS). This downlink short code number is encoded as shown in FIG.

(2.5.3.6.2.3.1.2.28): Result (RESULT)
The result is for setting the result (OK / NG) and is coded as shown in FIG.

(2.5.3.6.2.2.3.1.29): CAUSE
Next, CAUSE will be described. This information element is mandatory if the LINK RELEASE COMPLETE message is the first LINK REFERENCE release message. This information element is also set when a LINK RELEASE COMPLETE message is transmitted as a result of the error processing condition. This CAUSE is encoded as shown in FIG.

(2.5.3.6.2.3.1.2.30): Initial transmission power (INITIAL TRANSMISSION POWER)
Next, the initial transmission power will be described. The initial transmission power specifies downlink transmission power and is coded as shown in FIG.

(2.5.3.6.2.3.1.3.32): Location Identity (location identification)
Next, the Location Identity will be described. The Location Identity is used to identify a location registration area where the mobile station is located, takes a value of 0 to 255, and is coded as shown in FIG.

(2.5.3.6.3.2): Information element format (BSM)
Next, the information element format of the BSM message will be described.

(2.5.3.6.2.3.2.1): Protocol identifier First, the protocol identifier will be described. The protocol identifier is set for the purpose of identifying the BSM message from other messages defined in this system. The protocol identifier is also used to identify this standard message from messages of OSI network layer protocol units encoded by other ITU-T Recommendations / TTC standards and other standards. This protocol identifier is placed first in each message and is encoded as shown in FIGS. 248 and 747.

(2.5.3.6.2.3.2.2): Message Type Next, the message type will be described. The message type is set for the purpose of identifying the function of the message to be sent. This message type is arranged second in each message and is encoded as shown in FIGS. 250 and 748.

(2.5.3.6.2.3.2.3): PCH group calculation information Next, the PCH group calculation information will be described. The PCH group calculation information is an information element for determining the PCH group number in the BTS, and is, for example, the lower 16 bits of the binary representation of IMUI. That is, the PCH group calculation information is determined from a part of the IMUI of each MS and is encoded as shown in FIG.

(2.5.3.6.6.3.2.4): Position number Next, the position number will be described. The position number is a number (0 to 255) for identifying a position registration area where the mobile station is located, and is encoded as shown in FIG.

(2.5.3.6.2.5): Paged MS ID
Next, the Paged MS ID will be described. The Paged MS ID is obtained by integrating IMUI / TMUI used for paging, and TMUI or IMUI is set as the number type. When the IMUI is set, an integer type IMUI converted from the BCD format IMUI is set. The Paged MS ID is encoded as shown in FIG.

(2.5.3.6.3.2.5.1): Number type Next, the number type set after octet 4 is shown in FIG.

(2.5.3.6.3.2.5.2): Number Length Next, the number of octets (number length) of numbers set after octet 4 is shown in FIG. Octets 1 to 3 are not included in the number length.

(2.5.3.6.3.2.5.3): TMUI
Next, the TMUI information element will be described. TMUI is used to identify a mobile station. The IMUI is a number that is updated at the time of location registration and location update and is dynamically assigned to the mobile station. The TMUI information element has a fixed length of 4 octets.

(2.5.3.6.3.2.5.4): Integer type IMUI
Next, the integer type IMUI will be described. The integer type IMUI is used to identify the mobile station. IMUI is used in re-PAGING when the network side recognizes TMUI mismatch with MS in PAGING using TMUI. The integer type IMUI is set by converting an IMUI in the BCD format into an integer type, and has a variable length and a maximum length of 7 octets.

(2.5.3.6.3.2.5.4): Paging ID (Paging ID)
Next, Paging ID will be described. The Paging ID is used for managing a call when a mobile station is called, and is a number temporarily assigned when a mobile station calls together. The Paging ID information element is encoded as shown in FIG.
(2.5.3.6.4.1): SDL diagram (BC)

  As a supplement, FIG. 255 shows an SDL diagram (SDL diagram) on the NE (BSC function) side for BC in SDCCH, FIG. 256 shows an SDL diagram on the NW (BSC function) side for BC in TCH / ACCH, and BC on SDCCH. FIG. 257 shows an SDL diagram on the BTS side for use in the BTS, and FIG. 258 shows an SDL diagram on the BTS side for BC in the TCH / ACCH.

(2.5.3.6.4.2): SDL diagram (BSM)
FIG. 254 shows an SDL diagram for BSM.

(3): Control peculiar to this system Since this system employs the configuration and protocol specifications described above, it is possible to carry out peculiar control that has not existed in the past. Hereinafter, specific control provided in this system will be described.

(3.1): Control of concealment start timing (3.1.1): Background of introduction of this control method As described above, when concealed signals (control signals) are transmitted / received, from which timing If it is not known whether the start has been performed, the secrecy cannot be properly released. In this case, if the secret release timing is incorrect, an unknown signal is acquired.

  Therefore, as another method for avoiding this, it is possible to notify the mobile device of a concealment start request from the network, and to conceal both the transmission signal and the received signal after notifying the concealment start request. Conceivable.

More specific description will be given with reference to FIGS. 755 and 756.
In FIG. 755, a confidentiality start request is notified from the network to the mobile device, and after the confidentiality start request notification, the mobile device MS and the network NW are configured to conceal both the transmission signal and the received signal. The secret processing sequence diagram at the time of normal operation is shown. In the initial state, it is assumed that transmission / reception signals are not concealed (not concealed) in both the mobile station MS and the network NW.

First, the network NW notifies the mobile device MS of a confidentiality start request (step S21).
Then, the network NW starts to conceal the transmission / reception signal after notifying the concealment start request (step S22).
On the other hand, when the mobile station MS receives the notification of the concealment start request, it thereafter starts concealing the transmission / reception signal (step S23), and thereafter the network NW with concealment of both the transmission signal and the reception signal. To communicate with.

  By the way, in the above-described conventional concealment processing sequence, the concealment of both the transmission signal and the reception signal is performed with the transmission of the concealment start request (network NW side) and the reception (mobile station MS side) as a trigger. There is a possibility that a signal cannot be received due to a shift in concealment start timing.

For example, as shown in FIG. 756, in a situation where the mobile station MS is not executing the concealment process in the initial state of the transmission / reception signal, communication is started, the network NW transmits a concealment start request (step S24), and the movement When the mobile station MS transmits a release request (call release request) to release the communication itself before receiving the concealment start request to the network NW (step S25), the network NW has already concealed the transmission / reception signal at the transmission timing TX. (Step S26), for simplification of the system, if the network NW side does not have a function of simultaneously decoding both the secret signal and the unconfidential signal, the secret is not implemented. Since the secrecy release request cannot be decrypted, there is a possibility that a situation in which communication cannot be performed smoothly may occur.
Therefore, the present control method is intended to provide a mobile device, a network, and a mobile communication system capable of receiving a signal even when the start timing of concealment is deviated.

(3.1.2): Outline of the present control method First, prior to specific description, an outline of the present control method will be described.
FIG. 757 shows a concealment process sequence diagram during normal operation between the mobile station MS and the network NW of the present embodiment. In the initial state, it is assumed that transmission / reception signals are not concealed (not concealed) in both the mobile station MS and the network NW.

First, the network NW notifies the mobile device MS of a confidentiality start request (step S31).
Then, the network NW starts to conceal the transmission signal (downstream signal) after notifying the concealment start request (step S32).
On the other hand, when the mobile station MS receives the notification of the concealment start request, it thereafter starts concealing the received signal (step S33), and thereafter, with the network NW while concealing the received signal. Communicate.

Further, the mobile station MS notifies the network NW of a secret start response to notify that the secret start request has been received (step S34).
Then, after notifying the concealment start response, the mobile device MS starts concealing the transmission signal (uplink signal) (step S35).

  Further, when the network NW receives the notification of the concealment start response, it thereafter starts concealing the received signal (step S36).

  As a result, until the mobile station MS receives the concealment start request, and the network NW side does not start concealment of the received signal until the concealment start response is received, the concealment start timing is not shifted. Signal reception is possible reliably.

  As a result, according to the present embodiment, in a situation where the mobile station MS is not executing the concealment process in the initial state of the transmission / reception signal, communication is started, the network NW transmits a concealment start request (step S37), and Even when the mobile station MS transmits a release request (call release request) to the effect that the communication itself is not performed before receiving the concealment start request to the network NW (step S38), at the transmission timing TX1, the transmission signal Since the network NW has not yet concealed the received signal since it has only been concealed (step S39), the network NW has a function of simultaneously decrypting both the concealed signal and the unconfidential signal in order to simplify the system. Even if it is not provided on the side, the confidentiality release request can be reliably received, and communication can be performed smoothly.

(3.1.3): Specific operation of this control method Next, a specific operation will be described with reference to FIGS.
FIG. 64 shows a functional model for explaining the start of concealment. As shown in the figure, a mobile terminal is provided with UIMF, MCF and TACAF. The UIMF holds information about mobile users and provides user authentication and confidentiality calculations. The MCF is an interface with a network for non-call related services. TACAF controls access to the mobile terminal such as call origination and paging detection.

  On the other hand, SACF, TACF, LRCF, and LRDF are provided on the network side. The SACF is an interface with a mobile terminal for non-call related services, and is connected to the MCF. Further, the TACF controls access to the mobile terminal such as execution of transmission and paging, and is connected to the TACAF. The LRCF performs mobility control and is connected to the TACF and the SACF. The LRDF stores various data related to mobility.

  In such a configuration, prior to mutual notification of ciphering start, user authentication (see 2.4.5.1) is performed according to the procedure shown in FIG. At this time, the network and the mobile terminal hold the authenticated secret keys in the UIMF and the LRDF, respectively, and deliver them to the TACAF / MCF and the TACF / SACF, respectively.

Thereafter, mutual notification of ciphering start timing is performed according to the sequence shown in FIG.
First, from the LRCF on the network side, Start Ciphering req. ind is notified to TACAF / MCF on the mobile terminal side via TACF / SACF. Thereby, the mobile terminal can detect that ciphering is applied to the signal transmitted from the network thereafter. Therefore, the TACF / SACF on the network side is the start ciphering resp. conf. When a signal is transmitted, control is performed so that signals transmitted thereafter are concealed using a concealment key. When the mobile terminal receives a signal that has been concealed, the concealment release control of the received signal is performed by TACAF / MCF. The secret key is obtained from the UIMF prior to this process. Thereby, concealment is ensured about the transmission signal (downlink signal) transmitted from the network side.

Next, the TACAF / MCF on the mobile terminal side starts Start Ciphering resq. Which instructs to conceal the signal transmitted from the mobile terminal side. conf is notified to TACF / SACF on the network side.
Thereby, the network side can detect that ciphering is applied to the received signal thereafter. For this reason, the TACAF / MCF on the mobile terminal side starts Start Ciphering req. When conf is transmitted, signals transmitted thereafter are concealed using a concealment key. When the concealed signal is received on the network side, the concealment cancellation of the received signal is controlled by the TACF / SACF. Thereby, concealment is ensured for the transmission signal (uplink signal) transmitted from the mobile terminal side.

  As described above, according to the present control method, for simplification of the system, even when the network NW side does not have the function of simultaneously decoding both the secret signal and the unconfidential signal, the secret start timing is There is no deviation between the mobile station MS side and the network NW side, and communication can be reliably and smoothly performed between the mobile station MS and the network NW side.

(3.2): Control for selecting a concealment method by negotiation between the mobile station and the network side (3.2.1): Background of introduction of this control method FIG. An outline sequence diagram in the case of performing concealment processing is shown.

  In such a mobile communication system, when a communication request is made from the mobile station MS side to the network NW side (step S41), a secret scheme unique to the mobile communication system (only the confidential processing or the confidential processing is performed) at the start of communication. And communication using the secret key generation process (step 42).

  Therefore, there is a problem that such a selection cannot be made when it is desired to select the level of the confidential processing and the confidential key generation processing according to the degree of security requested by the user on the mobile device side.

  In addition, there arises a problem that it is impossible to select a secret process or a secret key generation process in accordance with a multimedia service (voice, moving image) provided by a communication service on the mobile device or the network side.

Furthermore, it is difficult to introduce new concealment processing or new concealment key generation processing even if it is necessary to enhance secrecy in consideration of new services when expanding future mobile communication systems. It is.
Furthermore, when roaming between various networks, there arises a problem that all the concealment processing must be made common.

Therefore, the purpose of introducing this control method is to provide a mobile device, a network side control device, and a mobile communication system that can flexibly cope with various types of secret processing or various types of secret key generation processing.
Next, a preferred embodiment of the present invention will be described with reference to FIGS. 760 to 762.

(3.2.2): Outline of this control method FIG. 760 shows an outline sequence diagram of this control method.
First, a communication request is made from the mobile device MS side to the network NW side together with a notification of a secret scheme type that is secret scheme information that can be executed by the mobile device MS (step S51).

In this case, as the secret scheme type, there may be only the secret implementation type (= corresponding to the secret process) or the secret implementation type and the secret key generation type (= corresponding to the secret key generation process), but in FIG. Only the confidentiality execution types A, B, and C are notified as the confidentiality method type.
As a result, the network NW selects a secret scheme type to be actually communicated (step S52). For example, in FIG. 760, the concealment execution type A is selected as the concealment method type.

Then, prior to the start of communication, the network NW notifies the mobile device MS of a concealment start request including information on the selected concealment method type (step S53).
As a result, on the mobile station MS side, settings corresponding to the cipher method type selected by the network NW (in FIG. 760, secrecy execution type A) are made (step S54). On the other hand, on the network NW side, the in-network device is set according to the selected security method type (the security execution type A in FIG. 760) (step S55).

As a result, at the start of communication between the mobile station MS and the network NW, communication (step S56) is performed using the confidentiality implementation type A as the selected confidentiality method.
As a result, for example, according to the degree of security requested on the mobile station MS side, it is possible to select the level of the security method type (only the security implementation type or the security implementation type and the security key generation type) and perform the security. became.

In addition, it is possible to select a concealment method type in accordance with a multimedia service (voice, moving image) provided by the communication service on the mobile station MS side or the network NW side, and perform concealment.
Furthermore, when a future system expansion is necessary, it becomes easy to introduce a new type of concealment method when it becomes necessary to enhance secrecy in consideration of new services.
Furthermore, if at least a secret scheme type common to multiple networks is supported, it is possible to perform communications with concealment without having to share all the secret scheme types when roaming. It is possible to execute concealment using a unique concealment method type in the network in addition to the concealed concealment method type.

(3.2.3): Specific description of this control method A specific operation will now be described with reference to the sequence diagrams of FIGS. 761 and 762. In the following description, a case will be described in which both the security implementation type and the security key generation type are selected as the security method type. In FIG. 761 and FIG. 762, only parameters related to secrecy are described for simplicity of explanation, and parameters necessary for authentication are not shown.

Prior to the start of communication, the security control unit of the mobile station MS sets the priority order of the secret execution type and the secret key generation type (step S61).
Then, the security control unit of the mobile station MS, with respect to the security control unit of the network NW, performs a secret implementation type (A, B, C), a secret key generation type (X, Y, Z), and priority order information as a secret scheme type. Is notified as a communication setting request (step S62).
As a result, the security control unit of the network NW stores the secret execution type (A, B, C) (step S63).

Next, the security control unit of the network NW notifies the user information control unit of the notified secret key generation type (X, Y, Z) (step S64).
Accordingly, the user information control unit generates a random number (step S65).

Further, the user information control unit of the network NW selects one secret key generation type from the secret key generation types (X, Y, Z) (step S66).
Then, a secret key is generated based on the random number generated in step S65 and the secret key generation type selected in step S66 (in FIG. 761, secret key generation type = X) (step S67).
Subsequently, the user information control unit of the network NW notifies the security control unit of the generated random number, the generated secret key, and the selected secret key generation type (= X) as authentication information (step S68).

  The security control unit of the network NW stores the generated secret key (step S69), transmits the generated random number and the selected secret key generation type (= X) to the security control unit on the mobile station MS side, An authentication request is made (step S70). In the process of step S70, other parameters necessary for the authentication calculation are also transmitted when the authentication is requested.

The security control unit on the mobile device MS side where the authentication request is made sends the random number notified from the network NW side together with the authentication calculation request to the user information control unit of the mobile device MS and the selected secret key generation type (= X). Notice.
As a result, the user information control unit of the mobile device MS generates a secret key based on the notified random number and the selected secret key generation type (= X) (step S72).
The generated secret key is included in the authentication calculation response and notified to the security control unit (step S74).

  The security control unit of the mobile device MS stores the secret key notified from the user information control unit (step S75), and uses the authentication calculation result calculated by the user information control unit as the authentication response as the security of the network NW. The control unit is notified (step S76).

  Thereby, the security control unit of the network NW compares the authentication calculation result notified from the mobile station MS side with the authentication calculation result obtained by using the secret key generated in step S67 and other authentication parameters (not shown). An authentication calculation collation request is made to the user information control unit (step S77).

When the authentication is completed, the user information control unit on the network NW side makes a confidentiality execution request to the security control unit (step S78).
As a result, the security control unit of the network NW notifies the wireless access control unit on the network NW side together with the secret key stored in step S69 and the notification of the secret execution type (= A, B, C) stored in step S63. A confidentiality implementation request is made (step S79).
As a result, the wireless access control unit on the network NW side determines one secret execution type from the notified secret execution types (step S80: determined as the secret execution type B in FIG. D3).

Then, the radio access control unit on the network NW side notifies the determined secrecy execution type (= B) to the radio access control unit on the mobile station MS side and makes a cipher implementation request (step S81).
As a result, the radio access control unit on the mobile station MS side stores the notified confidentiality implementation type (= B) (step S82).
Then, the wireless access control unit of the mobile device MS requests the security control unit of the mobile device MS to read the secret key stored in step S75 (step S83).
The security control unit of the mobile device MS notifies the stored secret key to the wireless access control unit (step S84).

As a result, the radio access control unit of the mobile station MS uses the secrecy execution type (= B) selected on the network NW side and the secret key generated on the mobile station MS side to the radio access control unit on the network NW side. Is performed (step S85), and the communication in which the concealment is performed is started (step S86).
On the other hand, the wireless access control unit on the network NW side that has received the concealment execution response thereafter performs communication with concealment (step S87).

As described above, according to this control method, according to the degree of security requested by the mobile station MS side (mobile station or user), the security method type (only the security implementation type or the security implementation type and the security key generation type) ) Level can be selected and concealed.
Further, it is possible to select a concealment method type in accordance with a multimedia service (voice, moving image) provided by the communication service on the mobile station MS side or the network NW side, and to perform concealment.
Furthermore, when the mobile communication system is expanded in the future, it becomes easy to introduce a new type of concealment method even when it becomes necessary to enhance secrecy in consideration of new services.
Furthermore, if at least a secret scheme type common to multiple networks is supported, it is possible to perform communications with concealment without having to share all the secret scheme types when roaming. It is possible to execute concealment corresponding to an original concealment method type in the network in addition to the concealed concealment method type.

(3.3): Control for starting diversity handover at the same time as setting of access link (3.3.1): Background of introduction of this control method Originally, setting of access link and starting of diversity handover are separate procedures. . Therefore, when a certain mobile station performs communication, after an access link is set for the mobile station, diversity handover is started when it becomes a state where diversity handover should be started due to movement of the mobile station. It has been a common method so far.

  However, there are cases where the mobile station is already located at a position where diversity handover can be applied when the access link is set up. Conventionally, even in such a case, an access link setting and a transition procedure to diversity handover are separately performed.

  For example, in FIG. 763 (a), the radio zones 11 and 12 are formed by the base station 21, but the mobile station 10 is located in the diversity handover zone 13, which is an area where the radio zones 11 and 12 overlap. In this state, when there is a call from the mobile station 10 or an incoming call to the mobile station 10, first, the minimum access link necessary for the mobile station 10 to start communication, for example, between the mobile station 10 and the base station 21. The wireless access link 41 and the wired access link 51 between the base station 21 and the base station controller 30 are set. When the access link setting is completed, as shown in FIG. 763 (b), a procedure for performing diversity handover within the base station, that is, a procedure for adding the radio access link 42 corresponding to the radio zone 12 is performed. It is.

  In addition, the mobile station may be in a state where diversity handover between base stations is possible at the time of setting the access link. For example, in FIG. 764 (a), the mobile station 10 is located in the diversity handover zone 15 where the radio zone 11 formed by the base station 21 and the radio zone 14 formed by the base station 22 overlap. Also in this case, when the mobile station 10 makes a call or the like, first, the minimum access link necessary for the mobile station 10 to start communication, that is, in the illustrated example, the wireless link corresponding to the wireless zone 11 is used. A wired access link 51 connecting the access link 41 to the base station 21 and the base station control device 30 is set. When the access link setting is completed, as shown in FIG. 764 (b), the procedure for performing the inter-base station diversity handover, that is, the radio access link 44 corresponding to the radio zone 14, the base station 22 and A procedure for adding a wired access link 52 connecting the base station control devices 30 is performed.

  As described above, under the conventional technology, even in a situation where diversity handover is possible at the time of setting an access link, each is handled as a separate procedure, such as first performing the former and then performing the latter. It was.

  However, in order to set the access link, it is necessary to execute a series of procedures shown in FIG. 765 between the mobile station and the network side. In addition, a series of procedures shown in FIG. 766 is performed for the transition to the diversity handover within the base station, and a series of procedures depicted in FIG. 767 is performed for the transition to the diversity handover between the base stations. (Note that the various types of information shown in these figures have already been explained, and will also appear when explaining the control methods newly introduced in this system. Therefore, the duplicate description here is omitted.)

  Therefore, under the prior art, when a mobile station is in a state where it can make a transition to diversity handover, if the mobile station makes a call, etc., until the diversity handover is executed after the call is made In addition, there is a problem that the amount of a series of control signals exchanged between the mobile station and the network and within the network increases, and the control burden of the system becomes heavy.

In addition, when the access link is set, the mobile station can use only one radio access link even though it is in a state where diversity handover should be performed. There is a problem that the amount of interference given to the radio access link increases and the capacity of the cell deteriorates.
This control method is a method introduced to solve the above problems.

(3.3.2): Overview of this control method In this system, when a call is made to a mobile station or an incoming call is generated and an access link is set to the mobile station, the mobile station performs diversity handover. If the mobile station is in a state in which the mobile station can perform the diversity handover, the mobile station sets the access link to the mobile station at the same time that the mobile station can start the diversity handover, and the mobile station starts the diversity handover simultaneously with the access link setting. That is, when a call is made or a call is received, a sub-branch for performing diversity handover is set in addition to the main branch, and diversity handover is started from the beginning of communication of the mobile station. FIG. 768 (a) shows a state in which an intra-base station diversity handover is started at the same time when an access link is set for the mobile station 10 in this system, and FIG. 768 (b) shows an access link being set. At the same time, a state in which diversity handover between base stations is started is shown.

(3.3.2.1): Control for starting intra-base station diversity handover simultaneously with setting of access link FIG. 769 is issued to mobile station 10 when mobile station 10 is in the state shown in FIG. 768 (a). It is a sequence diagram which shows operation | movement when a call or an incoming call generate | occur | produces and an access link is set.

  In FIG. 769, TACAFa is a functional entity of the mobile station 10 in FIG. 768 (a). TACFa is a functional entity in the base station controller, and is a functional entity TACF as an anchor generated first when the mobile station 10 starts communication. TACFv1 is a functional entity that the base station control device has in order to control the base station 21 where the mobile station 10 is located. The BCFr1 is a functional entity for radio resource control that the base station 21 that is the destination of the mobile station 10 has.

Hereinafter, this control method will be described with reference to FIG. 768 (a) and FIG.
As already described, the mobile station always monitors the reception level of the perch channel in the surrounding zone. Therefore, when the mobile station 10 in FIG. 768 (a) is located in the radio zone 11, the mobile station 10 monitors the reception level of the perch channel in the radio zone 12 adjacent to the thorn.

  Here, if the reception level of the perch channel in the radio zone 12 exceeds the threshold, the mobile station 10 notifies the network side of the perch channel corresponding to the radio zone 12 as a diversity handover branch candidate.

  It is assumed that the mobile station 10 is located in the diversity handover zone 13 and a call is made from the mobile station 10, for example, in a state where the diversity handover branch candidates are notified to the network side. In this case, when the base station controller 30 sets a diversity handover branch in the mobile station 10, it simultaneously generates a request for setting an access link for the mobile station 10 and a request for transition to diversity handover. In this system, the following procedures are performed in accordance with these requirements.

    (1) First, in order to set up an access link corresponding to the mobile station 10, the base station control device 30 for controlling the base station 21 that is the destination of the mobile station 10 from the functional entity TACCFa of the base station control device 30. For the functional entity TACFv of BEARER SETUP req. ind. (Access link setting request) is sent. This BEARER SETUP req. ind. Includes contents shown in FIG. 404 and those shown in FIG. 433.

    (2) The functional entity TACFv1 transmits the BEARER SETUP req. ind. Is received from the functional entity BCFr of the base station 21 with BEARER & RADIO BEARER SETUP req. ind. And INTRA BCFr HANDOVER BRANCH ADDITION req. ind. A single message containing both contents is sent.

  Here, BEARER & RADIO BEARER SETUP req. ind. 407 is as shown in FIG. 407, and the wireless access link 42 from the base station 21 to the mobile station 10 and the wired access link 51 from the base station 21 to the base station controller 30 (that is, the setting of the main branch). ).

  Also, INTRA BCFr HANDOVER BRANCH ADDITION req. ind. Is a request for additional setting of a sub-branch for diversity handover within the own station, that is, the one corresponding to the radio access link 42 in FIG. 768 (a), and its contents are as shown in FIG.

  Note that the above BEARER & RADIO BEARER SETUP req. ind. And INTRA BCFr HANDOVER BRANCH ADDITION req. ind. The message including both of the contents described above has already been explained as the LINK SETUP message in the section (2.5.3.6.2.1.3.2). The content of this message is shown in FIG. 693 referred to in the same chapter. As shown in the figure, this message contains an INTRA BS DHO additional setting request information element related to a sub-branch to be added in order to perform diversity handover, in addition to an ACCH setting request information element that requests setting of an access link. .

    (3) Next, the BCFr is a RADIO BEARER SETUP PROCEEDING req. ind. And INTRA BCFr HANDOVER BRANCH ADDITION resp. conf. A message containing both of the above is sent to TACFv1.

Here, RADIO BEARER SETUP PROCEEDING req. ind. Is a report indicating that a wireless access link corresponding to the wireless access link 41 in FIG. 768 (a) is being set up, and the contents thereof are as shown in FIG.
Also, INTRA BCFr HANDOVER BRANCH ADDITION resp. conf. Is a report to the effect that the additional setting of the radio access link 41 for performing the diversity handover within the own station has been completed, and the contents are as shown in FIG.

    (4) TACFv1 is the above-mentioned RADIO BEARER SETUP PROCEEDING req. ind. And INTRA BCFr HANDOVER BRANCH ADDITION resp. conf. Is received from the BCFr1, the mobile station 10 is requested to set up a radio access link (corresponding to the radio access links 41 and 42), and the RADIO BEARER SETUP REQUEST req. ind. (Wireless access link setting request) is transmitted. This RADIO BEARER SETUP REQUEST req. ind. Includes the contents shown in FIG. 409 and the contents shown in FIG. 436.

    (5) Next, the TACFa of the base station control device 30 performs HANDOVER BRANCH ADDITION req. ind. (Handover branch addition setting request) and RADIO BEARER SETUP req. ind. One message with the content of (Radio access link setting request) is transmitted to the TACAF of the mobile station 10.

  This message requests the setting of both the radio access link 41 (main branch that establishes synchronization later) and the radio access link 42 (sub-branch to be added to the main branch for diversity handover).

  This message is the RADIO BEARER SETUP message already described in the section (2.5.2.2.4.2.3.1). The contents of this message are shown in FIG. 624 referenced in the same chapter. As shown in the figure, this message includes DHO addition information for designating a sub-branch to be added to the main branch when performing diversity handover, in addition to information on the main branch.

    (6) Next, TACAFa of the mobile station 10 starts an operation of establishing synchronization with the BCFr1 of the base station 21 via the main branch via the radio access link.

    (7) When synchronization is established, BEARr & RADIO BEARER SETUP resp. For reporting completion of establishment of the radio access link from BCFr1 of base station 21 to TACFv1 of base station controller 30. conf. Is sent. FIG. 413 shows this BEARER & RADIO BEARER SETUP resp. conf. The contents of

(8) TACFv1 is the BEARER & RADIO BEARER SETUP resp. conf. Is received, the BEARER SETUP resp. conf. Send. FIG. 414 shows the BEARER SETUP resp. conf. The contents of
Thus, the access link setting for the mobile station 10 and the shift to the diversity handover are completed.

(3.3.2.2): Control for starting diversity handover between base stations simultaneously with setting of access link FIG. 770 is a diagram for mobile station 10 when mobile station 10 is in the state shown in FIG. 768 (b). It is a sequence diagram which shows operation | movement in the case of setting of an access link.

  In FIG. 770, TACAFa is a functional entity of the mobile station 10 in FIG. 768 (b). TACCa is a functional entity of the base station controller, and is a functional entity that is first generated when the mobile station 10 starts communication. TACFv1 and TACFv2 are functional entities that the base station control device 30 has to control each base station (the base stations 21 and 22 in FIG. 768 (b)) where the mobile station 10 is located. It is. Further, BCFr1 and BCFr2 are functional entities for radio resource control respectively possessed by each base station (base stations 21 and 22 in the example of FIG. 768 (b)) where mobile station 10 is located.

Hereinafter, this control method will be described with reference to FIG. 768 (b) and FIG. 770.
As shown in FIG. 768 (b), when the mobile station 10 enters the diversity handover zone 13, a call is made from the mobile station 10, and the base station controller 30 makes an access link setting request to the mobile station 10 and A request for transition to diversity handover is generated at the same time. Then, following the generation of these requests, the following procedures are advanced.

    (1) First, in order to establish an access link corresponding to the mobile station 10, the BEARER SETUP req. ind. Is sent. FIG. 404 shows the BEARER SETUP req. ind. The contents of

    (2) TACFv1 is the BEARER SETUP req. ind. , BEARr & RADIO BEARER SETUP req. Requesting the BCFr1 of the base station 21 to request setting of a wireless access link with the mobile station 10 and a wired access link with the base station controller 30. ind. Send. FIG. 407 shows the BEARER & RADIO BEARER SETUP req. ind. The contents of

    (3) The BCFr1 of the base station 21 uses this BEARER & RADIO BEARER SETUP req. ind. Is received, RADIO BEARER SETUP PROCEEDING req. For starting the setting of the wireless access link and the wired access link and reporting that the access link is being set up. ind. To TACFv1. FIG. 404 shows the RADIO BEARER SETUP PROCEEDING req. ind. The contents are shown.

    (4) The TACFv1 in the base station control device 30 uses the RADIO BEARER SETUP PROCEEDING req. ind. , RADIO BEARER SETUP REQUEST req. Shown in FIG. 409 is requested to request the mobile station 10 to set the radio access link 41 in accordance with the setting of the radio access link 41 on the base station 21 side. ind. Is sent to TACCa.

    (5) Next, the TACFa of the base station control device 30 adds an additional access link (corresponding to the radio access link 44) to the TACFv2 for controlling one base station 22 where the mobile station 10 is located. BEARER SETUP req. Shown in FIG. ind. Send.

    (6) TACFv2 uses this BEARER SETUP req. ind. Is received, the BCFr2 of the base station 22 is requested to set a wireless access link (corresponding to the wireless access link 44) with the mobile station 10 and a wired access link with the base station controller 30. BEARER & RADIO BEARER SETUP req. ind. Send. This BEARER & RADIO BEARER SETUP req. ind. The contents of are shown in FIG.

    (7) Next, when the BCFr2 of the base station 22 completes the setting of the wireless access link and the wired access link, in order to report to that effect, a BEARER & RADIO BEARER SETUP resp. conf. Is transmitted to TACFv2 of the base station controller 30.

    (8) Next, TACFv2 uses the above-mentioned BEARER & RADIO BEARER SETUP resp. conf. , The RADIO BEARER SETUP REQUEST req. Shown in FIG. 447 to request the TACCa to set the radio access link 44 to the mobile station 10. ind. Send.

(9) Next, the TACCa uses the RADIO BEARER SETUP REQUEST req. ind. Is received, the HANDOVER BRANCH ADDITION req. ind. And RADIO BEARER SETUP req. ind. A single message containing both contents is sent.
This message requests the setting of both the radio access link 41 (main branch that establishes synchronization later) and the radio access link 44 (sub-branch added to the main branch for diversity handover).

    (10) Next, the mobile station 10 starts a synchronization establishment operation with the base station 21 via the radio access link 41 (main branch).

    (11) When synchronization is established, the BEARr & RADIO BEARER SETUP resp. For reporting the completion of establishment of the radio access link from the BCFr1 to the TACFv1 of the base station 21. conf. Is sent. FIG. 413 shows this BEARER & RADIO BEARER SETUP resp. conf. The contents of

(12) Next, from the TACFv1 to the TACFa, a BEARER SETUP resp. conf. (Access link setting resp.conf.) Is transmitted. FIG. 414 shows the BEARER SETUP resp. conf. The contents of
Thus, the access link setting for the mobile station 10 and the shift to the diversity handover are completed.

(3.3.3): Operation of mobile station and base station when this control method is implemented (3.3.3.1): Operation of mobile station FIG. 786 is a base station control in FIG. From the device's TACCa to the mobile station's TACAFa, the HANDOVER BRANCH ADDITION req. ind. And RADIO BEARER SETUP req. ind. The detailed operation | movement after the message containing both of these contents is transmitted is shown.

  As shown in FIG. 786, the mobile station (TACAFa) transmits the above-mentioned HANDOVER BRANCH ADDITION req. ind. And RADIO BEARER SETUP req. ind. If you receive, set the main branch. That is, the mobile station allocates radio physical resources (frequency, code) for forming the main branch to the radio apparatus of the mobile station, and synchronizes each uplink and downlink communication with the base station (BCFr1). Establish. Then, upon completion of this synchronization establishment, voice or data communication is started.

  Then, when the mobile station completes the setting of the main branch in this way, it immediately sets the sub-branch. In this case, after setting the radio physical resource for forming the sub-branch in the radio device, the reception operation via the sub-branch is started immediately without performing synchronization establishment as in the case of the main branch, and diversity combining is performed. Do.

  FIG. 787 shows a control flow of the mobile station for enabling the above operation. In this system, the mobile station may receive a message including both the main branch setting request and the sub-branch additional setting request from the base station controller when the access link is not set up with the network side. Therefore, the control flow can cope with such a case.

  That is, when receiving a signal from the signal reception waiting state (step S1), the mobile station determines whether or not main branch information is included in the received signal (step S2). If the main branch information is included, the main branch is set according to the information (step S3).

Next, the mobile station determines whether or not sub-branch information is included in the received signal (step S5). If sub-branch information is included, the sub-branch is set according to the information (step S6). In some cases, the received signal includes a plurality of sub-branch information. In such a case, the corresponding sub-branch is set for all the sub-branch information (steps S4 and S5).
Then, when there is no subbranch information to set a subbranch in the received signal, the process returns to the signal reception waiting state.

  In this way, when a signal is received, the corresponding branch is set for all branch information (main branch and sub-branch) included in the received signal. When the message including the main branch setting request and the sub branch setting long time is sent from the side, the above-described operation (FIG. 786) is obtained, and the diversity handover can be started simultaneously with the access link setting. .

Although the case of diversity handover between base stations has been described above as an example, the same applies to the case where intra-base station diversity handover is started simultaneously with the setting of an access link.
For reference, FIG. 788 shows the operation of the mobile station after setting the conventional access link, and FIG. 789 shows the control flow of the mobile station.

  As shown in FIG. 788, under the prior art, RADIO BEARE SETUP req. ind. Is sent from the base station controller to the mobile station, and then the HANDOVER BRANCH ADDITON req. ind. Was sent from the base station controller to the mobile station. That is, the number of times a message is sent from the base station controller to the mobile station is one more than in the case of this system.

  In addition, under the conventional technology, RADIO BEARE SETUP req. ind. And HANDOVER BRANCH ADDITON req. ind. Are sent to the mobile station as separate messages, the mobile station side processes the received message according to the flow shown in FIG. That is, when a signal is received from the signal waiting state (step S11), if the signal includes main branch information, the main branch is set to wait for signal reception (steps S12 and S13), and if the sub branch information is included. The sub-branch is set and waiting for signal reception (steps S12 and S14).

  According to this system, one message including both main branch information and sub-branch information is sent to the mobile station, and the mobile station sets both the main brachinch and the sub-branch by receiving this message. Therefore, it is possible to efficiently shift to the diversity handover without receiving useless signal reception between the network side and the mobile station.

(3.3.3.2): Operation of base station As already described with reference to FIG. 769, in the present system, when a transition to the intra-base station diversity handover is performed simultaneously with the setting of the access link, BEARER & RADIO BEARER SETUP req. ind. And INTRA-BCFr HANDOVER BRANCH ADDITION req. ind. A message containing both of these contents is sent to the base station.
The base station in this system reads all of the plurality of branch information included in this message, and sets each branch according to each branch information. The specific control flow is the same as the control flow for the mobile station (FIG. 787), and a description thereof will be omitted.

(3.4): Method for performing diversity handover at the time of branch switching (3.4.1): Background of introduction of this control method The mobile station has exited from the wireless zone in which it is located and has been in the service until then. When moving to an adjacent radio zone different from the frequency band used in the radio zone, branch switching is performed. In addition, when a mobile station is located in a certain radio zone and the communication quality deteriorates at this time, branch switching is also performed when the communication frequency of the mobile station is switched to another frequency band in the radio zone. Is done.

  By the way, under the conventional technique, after this branch switching, the transition to the diversity handover may be continuously performed. FIG. 771 shows an example.

  In FIG. 771, the frequency f1 is used in the cell 1, and the frequency f2 is used in the cells 2 and 3. Here, it is assumed that the mobile station located in the cell 1 moves in the direction of the arrow and enters the zone where the cells 1, 2 and 3 overlap.

  In this case, branch switching is performed when the mobile station goes out of the cell 1 range, but the point where this branch switching is performed is in the diversity handover zone where the cells 2 and 3 overlap.

  Therefore, under the conventional technique, first, branch switching is performed to switch the branch used by the mobile station from one corresponding to cell 1 to one corresponding to cell 2, and then adding a branch corresponding to cell 3 The procedure of starting a handover was taken.

  However, in order to perform branch switching, it is necessary to execute many procedures shown in FIG. 772 between the mobile station and the network side. Also, the transition to diversity handover performed after branch switching requires many procedures as shown in FIG. 767 (note that the various types of information shown in these figures have already been described). In addition, since it also appears when explaining a control method newly introduced in this system, a duplicate description is omitted here.)

  Thus, under the prior art, when switching to diversity handover is possible when a branch switching opportunity occurs, a procedure for branch switching that requires transmission and reception of many types of control signals and Since procedures for shifting to the diversity handover state are performed one after another, the amount of control signals exchanged between the mobile station and the network side and within the network increases, and the control burden on the system increases. There was.

  In addition, at the time of branch switching, the mobile station can use only one radio access link even though it is in a state where diversity handover should be performed, so that the radio access link used by the mobile station is another radio access link. There is a problem that the amount of interference given to the access link is increased, and the capacity of the cell is deteriorated.

Note that the above-described problems occur when the mobile station can shift to diversity handover between base stations after branch switching (FIG. 771), or when the mobile station can shift to diversity handover within base station after branch switching. It is a problem that also occurs.
This control method is a method introduced to solve the above problems.

(3.4.2): Contents of this control method In this system, when a branch switching opportunity occurs, if a transition to diversity handover is possible, diversity handover is performed from the branch configuration before the trigger occurs. Switch directly to the branch configuration for

  FIG. 773 is a sequence diagram showing operations performed in the present system when the mobile station moves from the cell 1 to the diversity handover zone in which the cells 2 and 3 overlap as shown in FIG. 771.

  In FIG. 773, TACAFa is a functional entity of the mobile station in FIG. 771. TACFa is a functional entity in the base station controller, which is first generated when the mobile station starts communication. TACFv1, TACFv2, and TACFv3 are functional entities in the base station controller for controlling each base station that is the destination of the mobile station 10, and in the example of FIG. It is a functional entity for controlling each base station. BCFr1, BCFr2, and BCFr3 are functional entities for radio resource control in each base station where the mobile station 10 is located. In the example of FIG. 771, the radio in each base station of the cells 1, 2, and 3 is used. Implements resource control.

Hereinafter, this control method will be described with reference to FIGS. 771 and 773.
In FIG. 771, when a mobile station enters a diversity handover zone in which cells 2 and 3 overlap, cells 2 and 3 are notified to the network side as candidates for diversity handover, and these candidates are recognized by the network side. .

  In this state, for example, if the mobile station moves out of cell 1 and moves to a diversity handover zone in which cells 2 and 3 overlap, the base station controller requests the mobile station to switch branches and request to shift to diversity handover. Are generated at the same time. Then, following the generation of these requests, the following procedures are advanced.

    (1) The TACFa of the base station control apparatus transmits a BEARER SETUP req. For establishing an access link of the mobile station via the base station of the cell 2 to the TACFv2. ind. Send.

    (2) TACFv2 is the BEARER SETUP req. ind. , BEARr & RADIO BEARER SETUP req. Is sent to BCFr2 in the base station of cell 2. ind. Send. This BEARER & RADIO BEARER SETUP req. ind. Is a request for setting a wireless access link from the base station to the mobile station in cell 2 and setting a wired access link from the base station to the base station controller.

    (3) Next, the BCFr2 of the base station of the cell 2 sets the BEARER & RADIO BEARER SETUP req. ind. When the wireless access link and the wired access link are set up, the RADIO BEARER SETUP PROCEEDING req. For reporting that the access link is being set up is received. ind. Is transmitted to TACFv2 of the base station controller.

    (4) Next, TACFv2 uses the above RADIO BEARER SETUP PROCEEDING req. ind. , RADIO BEARER SETUP REQUEST req. Requesting the mobile station to set up a radio access link with the base station of cell 2. ind. Is sent to TACCa.

    (5) TACCa uses the RADIO BEARER SETUP REQUEST req. ind. Is received, BEARER SETUP req. ind. To TACFv3. This BEARER SETUP req. ind. Is a request for setting an access link to the mobile station via the base station of the other cell 3.

    (6) TACFv3 uses this BEARER SETUP req. ind. Is received, BEARr & RADIO BEARER SETUP req. ind. Send. This BEARER & RADIO BEARER SETUP req. ind. Calls for setting a wireless access link between the mobile station and the base station of the cell 3 and a wired access link between the base station and the base station controller.

    (7) The BCFr3 of the base station of the cell 3 uses the BEARER & RADIO BEARER SETUP req. ind. Is received, BEARER & RADIO BEARER SETUP resp. Reports the fact that the requested wireless access link and wired access link are set and the access link setting is complete. conf. Is transmitted to the TACFv3 of the base station controller.

    (8) TACFv3 is the BEARER & RADIO BEARER SETUP resp. conf. , RADIO BEARER SETUP REQUEST req. For requesting the mobile station to set up each radio access link between the base stations of cells 2 and 3. ind. Is sent to TACCa.

(9) TACCa uses the RADIO BEARER SETUP REQUEST req. ind. Is received, NON-SOFT HANDOVER EXECUTION req. Requesting switching of the main branch to TACAFa of the mobile station. ind. And HANDOVER BRANCH ADDITION req. ind. A single message containing both contents is sent.
This message requests the mobile station to switch from the branch corresponding to cell 1 (frequency f1) to the branch corresponding to cell 2 (frequency f2; main branch) and to the branch corresponding to the new cell 3 (frequency f1). (Frequency f2; sub-branch) is requested to be set.

  This message is the HANDOVER COMMAND message already explained in the section (2.5.2.2.4.2.3.4). The contents of this message are shown in FIG. 627 referenced in the same chapter. As shown in the figure, this message includes DHO additional information related to a sub-branch to be added in order to perform diversity handover, in addition to branch switching information including information related to a new main branch after branch switching.

    (10) Next, the mobile station starts an operation of establishing synchronization with the base station of cell 2 via the main branch.

    (11) When synchronization is established, BEARr & RADIO BEARER SETUP resp. For reporting completion of establishment of the radio access link from BCFr2 of the base station of cell 2 to TACFv2 of the base station controller. conf. Is sent.

    (12) Next, from TACFv2 to TACFa, BEARER SETUP resp. conf. Is sent.

    (13) This BEARER SETUP resp. conf. Is transmitted, TACFa of the base station controller requests TACFv1 to release BEARER RELEASE req. Requesting the release of the access link that the base station of cell 1 has maintained for the mobile station. ind. Send.

    (14) TACFv1 is the BEARER RELEASE req. ind. , BEARr & RADIO BEARER RELEASE req. Requesting that BCFr1 in the base station of cell 1 release the wireless access link and the wired access link that have been maintained for the mobile station. ind. Send.

    (15) The BCFr1 of the base station of the cell 1 uses this BEARER & RADIO BEARER RELEASE req. ind. , The wireless access link and the wired access link that have been maintained for the mobile station are released, and the BEARER & RADIO BEARER RELEASE resp. conf. Send.

    (16) The TACFv1 of the base station controller is configured to use this BEARER & RADIO BEARER RELEASE resp. conf. Is received, the BEARER RELEASE resp. conf. Send.

As a result, the mobile station shifts to a diversity handover state using each branch corresponding to the cells 2 and 3.
As described above, the operation of this system has been described by taking as an example the case where the mobile station can shift to the inter-base station diversity handover after the branch switching (FIG. 771). When possible, basically the same operation is performed.
However, in this case, one message including information for instructing branch switching and information for instructing addition of a branch for diversity handover from the base station controller to the base station used for intra-base station diversity handover. Will be sent.

(3.4.3): Operation of mobile station and base station when this control method is implemented (3.4.3.1): Operation of mobile station As described above, in this system, branch switching is performed. At the same time, when a transition to diversity handover is performed, a message including both a branch switching command and a sub-branch addition command for diversity handover is sent to the mobile station.

  Therefore, when the message from the network side includes both a branch switching instruction and a sub-branch addition instruction for diversity handover, the mobile station performs branch switching and further adds diversity handover setting. I do. The specific control flow is basically the same as that described in section (3.3.3.1).

(3.4.3.2): Operation of base station As already described, in this system, when switching to diversity handover within a base station at the same time as branch switching, branch switching commands and diversity handover are performed. A message containing both the sub-branch add command is sent to the base station.
Therefore, if the message from the network side includes both a branch switching instruction and a sub-branch addition instruction for diversity handover, the base station performs branch switching, and further adds diversity handover setting. I do.

(3.5): Branch configuration and frequency band control method when a mobile station capable of communication corresponding to a plurality of calls is communicating and another new call is generated in the mobile station (part 2) 1)

(3.5.1): Background of introduction of this control method A mobile station apparatus capable of simultaneously performing communication corresponding to a plurality of calls is provided.
Under conventional technology, in this type of mobile station, there has been no means for making the same branch configuration and frequency band for communication corresponding to each call, so when performing communication corresponding to multiple calls In some cases, the branch configuration and frequency band are different for each call. For this reason, it is necessary to perform handover control and transmission power control of the mobile station for each call, and there is a problem that the burden on the overhead on the network side is excessive.
This control method is introduced to solve this problem.

(3.5.2): Contents of this control method In FIG. 774 (a), BTS1 and BTS2 form a radio zone of frequency f1. The MS performs communication corresponding to call-1 by performing diversity handover using BTS1 and BTS2.
In this state, it is assumed that a new call is generated in the MS due to, for example, a call originating from the MS.

In this system, in such a case, control is performed so that the new call (call-2 in the above example) and the existing call (call-1 in the above example) use the same branch configuration and frequency band for communication. .
That is, in the example shown in FIG. 774 (a), the communication corresponding to the existing call call-1 is performed using the frequency band f1 and the diversity handover branch via BTS1 and BTS2. . Therefore, when a new call call-2 occurs in the MS, as shown in FIG. 774 (b), communication corresponding to the new call call-2 also uses the frequency band f1, and BTS1 and BTS2 This is performed using a diversity handover branch passing through.

FIG. 775 is a sequence diagram showing the operation of this system for performing the control exemplified in FIGS. 774 (a) and (b).
In FIG. 775, TACAFa is a functional entity of the MS in FIGS. 774 (a) and (b). TACFa is a functional entity in the base station controller, and is first generated when the MS starts communication. TACFv1 and TACFv2 are the functional entities in the base station controller for controlling the BTS1 and BTS2 that are the locations of the MS, and the BCFr1 and BCFr2 are the BTS1 and BTS2 that are the locations of the MS. There is a functional entity for each radio resource control.

Hereinafter, this control method will be described with reference to FIGS. 774 and 775.
As shown in FIG. 774 (a), when the MS performs diversity handover using BTS1 and BTS2 and performs call-1 communication, if another call-2 occurs in the MS, the base station control The TACCa of the device generates an access link setting request corresponding to the new call call-2 and a request that the branch configuration of the new call call-2 should be the same diversity handover branch as the existing call call-1. And the following procedures are advanced with the generation of these requests.

    (1) The TACFa of the base station controller requests the TACFv1 of the base station controller that controls the BTS1 where the MS is located to set the access link for the new call call-2 via the BTS. BEARER SETUP req. ind. Send.

    (2) TACFv1 is the BEARER SETUP req. ind. , BEARr & RADIO BEARER SETUP req. ind. Send. This BEARER & RADIO BEARER SETUP req. ind. Requests a wireless access link setup for a new call call-2 from BTS1 to MS and a wired access link setup from BTS1 to the base station controller.

    (3) Next, the BCFr1 of BTS1 is the BEARER & RADIO BEARER SETUP req. ind. Is received, RADIO BEARER SETUP PROCEEDING req. Which starts setting up the requested wireless access link and wired access link and reports that the access link is being set up. ind. Is transmitted to TACFv1 of the base station controller.

    (4) TACFv1 is the RADIO BEARER SETUP PROCEEDING req. ind. Is received from RADIO BEARER SETUP REQUEST req. To request the TACCa to set up a radio access link between the MS and the BTS 1. ind. Send.

    (5) On the other hand, the TACCa of the base station control apparatus requests the BEARER SETUP req. Requesting the TACFv2 to set the access link for the new call “call-2” via the BTS2. ind. Send.

    (6) TACFv2 uses this BEARER SETUP req. ind. , BEARr & RADIO BEARER SETUP req. ind. Send. This BEARER & RADIO BEARER SETUP req. ind. Requires a wireless access link between the MS and the BTS 2 and a wired access link between the BTS 2 and the base station controller.

    (7) BCFr2 of BTS2 is the BEARER & RADIO BEARER SETUP req. ind. Is received, BEARER & RADIO BEARER SETUP resp. Is set in order to set the requested wireless access link and wired access link and report the completion of access link setting. conf. To TACFv2.

    (8) TACFv2 is the BEARER & RADIO BEARER SETUP resp. conf. Is received, the RADIO BEARER SETUP REQUEST req. Requesting the setting of the radio access link between the MS and the BTS 2 is requested. ind. Is sent to TACCa.

    (9) TACCa is the RADIO BEARER SETUP REQUEST req. ind. (Radio access link setup request via BTS1) Following this, RADIO BEARER SETUP REQUEST req. ind. (HANDOVER BRANCH ADDITION req.) When receiving (setting request for wireless access link via BTS2). ind. And RADIO BEARER SETUP req. ind. A message containing both of the above is sent to the TACAFa of the MS.

Here, RADIO BEARER SETUP req. ind. Is a request for setting a main branch (a branch where synchronization is established later, which is a branch via BTS 1 in this case).
In addition, HANDOVER BRANCH ADDITION req. ind. Is a request for setting a sub-branch (branch via BTS 2 in this case) for performing diversity handover.
This message requests the MS to set the radio access link (main branch) via BTS1 and the radio access link (subbranch) via BTS2 for the new call call-2.

    (10) Next, the MS starts a synchronization establishment operation with the BTS 1 via the main branch.

    (11) When synchronization is established, BEARr & RADIO BEARER SETUP resp. For reporting completion of establishment of the radio access link from BCFr1 to TACFv1 of BTS1. conf. Is sent.

(12) Next, from the TACFv1 to the TACFa, a BEARER SETUP resp. conf. Is sent.
As a result, the MS uses the diversity handover branch via BTS1 and 2 for both the existing call call-1 and the new call call-2, and performs communication using the frequency f1.

(3.6): Branch configuration and frequency band control method when a mobile station capable of communication corresponding to a plurality of calls is communicating and another new call is generated in the mobile station (part 2) 2)

(3.6.1): Background of introduction of this control method In the control method of (3.5) above, when a new call occurs during communication of a mobile station, the branch configuration and frequency of communication of a new call Control was performed to match the bandwidth to that of existing calls.
However, when a new call occurs, the reason is that some branches in the existing call communication branch configuration are congested, or the frequency band used for existing call communication is congested. Therefore, the same branch configuration and frequency band as the existing call branch configuration and frequency band may not be allocated to the new call. In such a case, a new call is not accepted and a call loss occurs.
This control method is introduced to solve this problem.

(3.6.2): Contents of this control method In this control method, a new call is generated when a mobile station capable of communication of a plurality of calls is communicating, and there is a lack of communication capacity. Can maintain the communication of all calls including the existing call and the new call when setting up the new call when the branch configuration and frequency band of the communication of the new call cannot be matched with those of the existing call. A possible branch configuration and frequency band are selected, and the branch configuration and frequency band of an existing call are changed to the selected branch configuration and frequency band.

FIGS. 776 (a) and (b) show a specific application example of the present control method.
In FIG. 776 (a), the MS performs call-1 communication using the branch of the frequency f1 set with the BTS1.
In this state, a new call call-2 is generated by a call from the MS, but BTS1 has no remaining communication capacity that can be allocated to the new call call-2.

  However, the BTS 2 adjacent to the BTS 1 still has sufficient communication capacity to cover the communication for the existing call call-1 and the new call call-2. Further, this BTS2 uses the band of the frequency f1 like BTS1, and if the branch configuration for communication of the existing call call-1 is a diversity handover branch configuration using both BTS1 and BTS2, Since the transmission power per branch is reduced, the communication capacity of BTS1 can be given a margin sufficient to be allocated to the communication of the new call call-2.

  Therefore, in this application example, when a new call call-2 is set, as shown in FIG. 776 (b), the branch configuration for communication of the existing call call-1 is a diversity handover branch using both BTS1 and BTS2. The configuration is changed, and the same branch configuration and frequency are assigned to the new call call-2.

FIGS. 777 (a) and (b) show another specific application example of the present control method.
In FIG. 777 (a), the MS performs call-1 communication using the branch of the frequency f1 set with the BTS1. In this state, a new call call-2 is generated by a call from the MS, but BTS1 has no remaining communication capacity that can be allocated to the new call call-2.

  However, BTS2 adjacent to BTS1 still has a communication capacity sufficient to cover both the existing call call-1 and the new call call-2. However, in this application example, since the frequency used by BTS2 is f2, which is different from that of BTS1, diversity handover using BTS1 and BTS2 cannot be performed.

  Therefore, in this application example, when the new call call-2 is set, the branch configuration for communication of the existing call call-1 is changed to a branch configuration using BTS2 as shown in FIG. This call branch-2 is also assigned the same branch configuration and frequency.

FIG. 778 is a sequence diagram showing the operation of this system for carrying out the application example shown in FIGS. 776 (a) and (b).
In FIG. 778, TACAFa is a functional entity of the MS in FIGS. 776 (a) and (b). TACFa is a functional entity in the base station controller, and is first generated when the MS starts communication. TACFv1-2 is an instance of a functional entity of the base station controller that controls the BTS1 where the MS is located, and corresponds to call-1, TACFv2-1 and TACFv2-2, It is an instance of each functional entity of the base station control device that controls the BTS 2 that is the location destination, and corresponds to call-1 and call-2, respectively. BCFr1-2 is an instance of a functional entity for radio resource control possessed by BTS1 that is the location of the MS, and corresponds to call-1, BCFr2-1 and BCFr2-2 are , Are instances of functional entities for radio resource control possessed by the BTS 2 where the MS is located, and correspond to call-1 and call-2, respectively.

Hereinafter, this control method will be described with reference to FIGS. 776 and 778.
As shown in FIG. 776 (a), when the MS performs communication of the call call-1 using the BTS1, another new call call-2 occurs in the MS. The TACCa of the base station controller is the radio resource occupied by the existing call Call-1 generated on the MS and the BS where the MS is located (BTS1 and BTS2 in the case of FIG. 776 (a)). Determine available radio resources and based on the results, determine how to handle all calls on the MS, including new calls.

  This determination method is as already described with reference to FIGS. 776 (a) and (b). As shown in FIG. 776 (b), the TACFa of the base station control apparatus determines the branch between MS and BTS1. A decision is made that a diversity handover branch consisting of a branch between the MS and the BTS 2 should be set up for each call-1 and call-2 communication.

Based on this determination, the system performs the following operations.
(1) The TACFa of the base station control device transmits an access link for the new call call-2 via the BTS1 to the TACFv1-2 in the base station control device corresponding to the BTS1 where the MS is located. BEARER SETUP req. ind. Send.

(2) The above BEARER SETUP req. ind. TACFv1-2 receives BEARr & RADIO BEARER SETUP req. To BCFr1-2 of BTS1. ind. Send.
This BEARER & RADIO BEARER SETUP req. ind. Is a request for setting a wireless access link for a new call call-2 from BTS1 to MS and a wired access link from BTS1 to the base station controller.

    (3) Also, the TACCa of the base station control device accesses the TACFv2-1 in the base station control device corresponding to the BTS2 where the MS is located, for the existing call call-1 via the BTS2. BEARER SETUP req. Requesting link setting. ind. Send.

    (4) The above BEARER SETUP req. ind. TACFv2-1 receives BEARr & RADIO BEARER SETUP req. ind. Send. This BEARER & RADIO BEARER SETUP req. ind. Requests the setting of the wireless access link for the existing call call-1 from the BTS2 to the MS and the wired access link from the BTS2 to the base station controller.

    (5) BCFr1-2 of BTS1 is BEARER & RADIO BEARER SETUP req. ind. When the setting of the wireless access link and the wired access link is started according to RADIO BEARER SETUP PROCEEDING req. For reporting that the access link is being set up. ind. Is transmitted to TACFv1-2 of the base station controller.

    (6) TACFv1-2 is the RADIO BEARER SETUP PROCEEDING req. ind. Is received, RADIO BEARER SETUP REQUEST req. Requesting establishment of a radio access link for a new call call-2 between the MS and BTS1. ind. Is sent to TACCa.

    (7) On the other hand, BCFr2-1 of BTS2 is the BEARER & RADIO BEARER SETUP req. ind. If a wireless access link and a wired access link are set up according to the above, BEARER & RADIO BEARER SETUP PROCEEDING req. ind. Is transmitted to TACFv2-1.

    (8) TACFv2-1 is the BEARER & RADIO BEARER SETUP PROCEEDING req. ind. , RADIO BEARER SETUP REQUEST req. Requesting the setup of the radio access link for the existing call call-1 between the MS and BTS2. ind. Is sent to TACCa.

    (9) Further, the TACCa requests the TACFv2-2 of the base station controller that controls the BTS2 where the MS is located to set the access link for the new call call-2 via the BTS2. BEARER SETUP req. ind. Send.

    (10) The BEARER SETUP req. ind. TACFv2-2 receives BEARR & RADIO BEARER SETUP req. To BCFr2-2 of BTS2. ind. Send. This BEARER & RADIO BEARER SETUP req. ind. Requests the setting of the wireless access link for the new call call-2 from the BTS2 to the MS and the wired access link from the BTS2 to the base station controller.

    (11) BCFr2-2 of BTS2 is BEARER & RADIO BEARER SETUP req. ind. If a wireless access link and a wired access link are set up according to the above, BEARER & RADIO BEARER SETUP PROCEEDING req. ind. Is transmitted to TACFv2-2.

    (12) TACFv2-2 is the BEARER & RADIO BEARER SETUP resp. conf. Is received, RADIO BEARER SETUP REQUEST req. Requesting the establishment of a radio access link for the new call call-2 between the MS and BTS2. ind. Is sent to TACCa.

(13) Next, TACCa is
RADIO BEARER SETUP REQUEST req. From TACFv1-2. ind. (Radio access link setting request via BTS1 for new call call-2),
RADIO BEARER SETUP REQUEST req. From TACFv2-1. ind. (Radio access link setup request via BTS2 for existing call call-1) and RADIO BEARER SETUP REQUEST req. From TACFv2-2. ind. (Radio access link setting request via BTS2 for new call call-2) has been received so far, HANDOVER BRANCH ADDITION req. ind. And RADIO BEARER SETUP req. ind. A message containing both of the above is sent to the TACAFa of the MS.
Here, RADIO BEARER SETUP req. ind. Is a request for setting a main branch for call-2 (a branch for which synchronization is established later, which is a branch via BTS1 in this case).
In addition, HANDOVER BRANCH ADDITION req. ind. Is a request for setting a sub-branch (branch via BTS 2 here) for performing diversity handover for both call-1 and call-2.

    (14) Next, the MS starts a synchronization establishment operation with BTS1.

    (15) When synchronization is established, BEARr & RADIO BEARER SETUP resp. conf. Is sent.

(16) Next, BEARER SETUP resp. For reporting completion of access link establishment from TACFv1-2 of BTS1 to TACCFa of the base station controller. conf. Is sent.
With this, the MS uses the diversity handover branch via BTS1 and 2 for both the existing call call-1 and the new call call-2, and performs communication using the frequency f1.

  Next, FIG. 779 is a sequence diagram showing the operation of this system for implementing the application example shown in FIGS. 777 (a) and (b). The meanings of TACAFa, TACFv1-1, etc. shown in FIG. 782 are the same as those shown in FIG.

Hereinafter, this control method will be described with reference to FIGS. 777 and 779.
As shown in FIG. 777 (a), when the MS performs call-1 communication using BTS1, call-2, which is another new call, is generated in the MS. The TACCa of the base station controller is in the radio resource occupied by the existing call call-1 generated on the MS and the BTS in which the MS is located (BTS1 and BTS2 in the case of FIG. 777 (a)). Determine available radio resources and based on the results, determine how to handle all calls on the MS, including new calls.

  This determination method is as already described with reference to FIGS. 777 (a) and (b). In this application example, the TACCa of the base station controller determines that the branch between the MS and the BTS 2 should be set for each communication of call-1 and call-2, as shown in FIG. 777 (b). To do.

Based on this determination, the system performs the following operations.
(1) The TACFa of the base station controller is an access link for the existing call call-1 via the BTS-2 to the TACFv2-1 of the base station controller that controls the BTS2 where the MS is located BEARER SETUP req. ind. Send.

    (2) The above BEARER SETUP req. ind. TACFv2-1 receives BEARr & RADIO BEARER SETUP req. ind. Send. This BEARER & RADIO BEARER SETUP req. ind. Is a request for setting a wireless access link from the BTS 2 to the MS for the existing call call-1 and a wired access link from the BTS 2 to the base station controller.

    (3) Further, the TACCa of the base station control apparatus accesses the TACFv2-2 of the base station control apparatus that controls the BTS2 that is the location of the MS, and an access link for the new call call-2 via the BTS2. BEARER SETUP req. ind. Send.

    (4) The above BEARER SETUP req. ind. TACFv2-2 receives BEARR & RADIO BEARER SETUP req. To BCFr2-2 of BTS2. ind. Send. This BEARER & RADIO BEARER SETUP req. ind. Requests the setting of the wireless access link from BTS2 to MS and the wired access link from BTS2 to the base station controller for the new call call-2.

    (5) On the other hand, BCFr2-1 of BTS2 is BEARER & RADIO BEARER SETUP req. ind. When the setting of the wireless access link and the wired access link is started in accordance with RADIO BEARER SETUP PROCEEDING req. For reporting that the access link is being set up. ind. Is transmitted to TACFv2-1.

    (6) TACFv2-1 is the RADIO BEARER SETUP PROCEEDING req. ind. Is received, RADIO BEARER SETUP REQUEST req. Requesting the TACCa to set up a radio access link for the existing call call-1 between the MS and BTS2. ind. Send.

    (7) Also, BCFr2-2 of BTS2 is the BEARER & RADIO BEARER SETUP req. ind. When the wireless access link and the wired access link are set up according to RADIO BEARER SETUP PROCEEDING req. ind. Is transmitted to TACFv2-2.

    (8) TACFv2-2 uses the RADIO BEARER SETUP PROCEEDING req. ind. Is received, RADIO BEARER SETUP REQUEST req. Requesting TACCa to set up a radio access link for a new call call-2 between the MS and BTS2. ind. Send.

(9) The TACCF is a NON-SOFT HANDOVER EXECUTION req. ind. And RADIO BEARER SETUP req. ind. A single message containing both contents is sent.
Here, NON-SOFT HANDOVER BRANCH EXECUTEION req. ind. Requests to switch the existing radio access link (radio access link via BTS1) for the existing call call-1 to the branch via BTS2.
Also, RADIO BEARER SETUP REQUEST req. ind. Requests the setting of the radio access link via BTS2 for the new call call-2.

    (10) Next, the MS starts a synchronization establishing operation with the BTS 2 for the existing call call-1.

    (11) Further, the MS starts a synchronization establishment operation with the BTS 2 for the new call call-2.

    (12) When synchronization is established for the existing call call-1, BEARr & RADIO BEARER SETUP resp. For reporting completion of establishment of the radio access link from BCFr2-1 to TACFv2-1 of BTS2. conf. Is sent.

    (13) When synchronization is established for the new call “call-2”, the BEARER & RADIO BEARER SETUP resp. conf. Is sent.

    (14) TACFv2-1 is a BEARER & RADIO BEARER SETUP resp. conf. Is received, BEARER SETUP resp. To the effect that establishment of the radio access link via BTS2 is completed for the existing call call-1. conf. Is transmitted to the TACFa of the base station controller.

    (15) In addition, TACFv2-2 is a BEARER & RADIO BEARER SETUP resp. conf. Is received, BEARER SETUP resp. To the effect that establishment of the radio access link via BTS2 is completed for the new call call-2. conf. Is transmitted to the TACFa of the base station controller.

    (16) TACFa is a BEARER SETUP resp. From TACFv2-1. conf. And BEARER SETUP resp. From TACFv2-2. conf. Is received, Bearer Release req. Requesting the TACFv1-1 to release the access link for the existing call call-1. ind. Send.

    (17) TACFv1-1 uses the Bearer Release req. ind. , BEARr & RADIO BEARER RELEASE req. Requesting the BCFr1-1 to release the access link via the BTS1 maintained for the existing call call-1. ind. Send.

    (18) BCFr1-1 is the BEARER & RADIO BEARER RELEASE req. ind. Is received, the access link maintained for the existing call call-1 is released, and BEARER & RADIO BEARER RELEASE resp. conf. Is transmitted to TACFv1-1.

(19) Next, BEARER RELEASE resp. For reporting access link release completion from TACFv1-1 of BTS1 to TACFa of the base station controller. conf. Is sent.
With this, the MS performs communication using the branch via BTS2 and the frequency f2 for both the existing call call-1 and the new call call-2.

(3.7): Control method when a handover trigger occurs in a mobile station performing communication of multiple calls (part 1)
(3.7.1): Background of the introduction of this control method This control method is also intended to solve problems when using a mobile station apparatus that can simultaneously handle a plurality of calls.
When this type of mobile station performs communication corresponding to a plurality of calls, a handover may occur. However, if no measures are taken in such a case, depending on whether the handover is performed for each call. The branch configuration and frequency band may be different for each call. In such a case, it is necessary to perform handover control and transmission power control of the mobile station for each call, and the burden on the network-side overhead becomes excessive.
This control method is introduced to solve this problem.

(3.7.2): Contents of this control method In this control method, when a mobile station capable of communication of multiple calls is communicating, a handover trigger occurs due to movement of the mobile station, etc. Determines a new branch configuration and frequency band capable of maintaining communication of all calls in progress, and sets the branch configuration and frequency band set for all calls to the new branch configuration and frequency band. Change to.

FIGS. 780 (a) and (b) show a specific application example of the present control method.
In FIG. 780 (a), the MS uses a diversity handover branch including a branch of frequency f1 set between BTS1 and a branch of frequency f1 set between BTS2, and call-1 and call- The communication corresponding to 2 is performed.

In this application example, the MS approaches the BTS 3 and communication using the frequency f 1 is possible between the MS and the BTS 3.
Further, in this application example, the communication capacity of the BTS 3 has a sufficient margin, and it is possible to perform communication between the MS and the BTS 3 for both the calls call-1 and call-2.

  Therefore, in this application example, as shown in FIG. 780 (b), handover is performed to add the branch via BTS3 to the current branch configuration of the MS, and the calls call-1 and call-2 occurring on the MS For all, the branch configuration is changed to the diversity handover branch configuration via BTS1, BTS2, and BTS3, respectively.

781 (a) and (b) show another specific application example of the present control method.
In FIG. 781 (a), the MS performs call-1 and call1-2 communication using the branch of the frequency f1 set with BTS1.
In this application example, since the MS has moved away from the BTS 1 and is approaching the BTS 3, there is a need to add a branch between the MS and the BTS 3 to the MS.
Further, in this application example, the communication capacity of the BTS 3 has a sufficient margin, and it is possible to perform communication between the MS and the BTS 3 for both the calls call-1 and call-2.

However, in this application example, the frequency used by BTS3 is f2, which is different from that of BTS1, and therefore, diversity handover using BTS1 and BTS2 cannot be performed.
Therefore, in this application example, as shown in FIG. 781 (b), the branch configuration for communication is changed to a branch configuration using BTS3 for both call-1 and call-2.

FIG. 782 is a sequence diagram showing the operation of this system for implementing the application example shown in FIGS. 780 (a) and 780 (b).
In FIG. 782, TACAFa is a functional entity of the MS in FIGS. 780 (a) and (b). TACFa is a functional entity TACF in the base station controller, which is first generated when the MS starts communication. TACFv3-1 and TACFv3-2 are instances of functional entities possessed by the base station controller for controlling the BTS3 where the MS is located, and call-1 and call-2 respectively. It corresponds. BCFr3-1 and BCFr3-2 are instances of functional entities for radio resource control possessed by the BTS3 that is the location of the MS, and correspond to the calls call-1 and call-2, respectively. Yes.

  Hereinafter, a control method for switching from the state shown in FIG. 780 (a) to the state shown in FIG. 780 (b) will be described with reference to FIG.

    (1) The TACFa of the base station control device establishes an access link for the existing call call-1 via the BTS3, and therefore, to the functional entity TACFv3-1 of the base station control device corresponding to the BTS3, the BEARER SETUP req . ind. Send.

    (2) The above BEARER SETUP req. ind. TACFv3-1 receives BEARR & RADIO BEARER SETUP req. To BCFr3-1 of BTS3. ind. Send. This BEARER & RADIO BEARER SETUP req. ind. Calls for setting a wireless access link from BTS3 to MS and a wired access link from BTS3 to the base station controller for call-1.

    (3) In addition, the TACCa of the base station control device establishes an access link for call-2 via BTS3, so that the BEARER SETUP req is sent to the functional entity TACFv3-2 of the base station control device corresponding to BTS3. . ind. Send.

    (4) The above BEARER SETUP req. ind. TACFv3-2 receives BEARR & RADIO BEARER SETUP req. To BCFr3-2 of BTS3. ind. Send. This BEARER & RADIO BEARER SETUP req. ind. Requests the setting of the radio access link for call-2 from BTS3 to MS and the wired access link from BTS3 to the base station controller.

    (5) On the other hand, BCFr3-1 of BTS3 is the BEARER & RADIO BEARER SETUP req. ind. When the access link is set according to BEARER & RADIO BEARER SETUP resp. conf. Is transmitted to TACFv3-1.

    (6) TACFv3-1 is the BEARER & RADIO BEARER SETUP resp. conf. Is received from RADIO BEARER SETUP REQUEST req. To request the TACCa of the base station controller to set up a radio access link for call-1 between the MS and BTS3. ind. Send.

    (7) In addition, BCFr3-2 of BTS3 is a BEARER & RADIO BEARER SETUP req. ind. When the access link is set according to BEARER & RADIO BEARER SETUP resp. conf. Is transmitted to TACFv3-2.

    (8) TACFv3-2 is the BEARER & RADIO BEARER SETUP resp. conf. , Requesting TACCa to set up a radio access link for call-2 between the MS and BTS 3, RADIO BEARER SETUP REQUEST req. ind. Send.

    (9) The TACCF is a HANDOVER BRANCH ADDITION req. ind. Send. This HANDOVER BRANCH ADDITION req. ind. Requests additional configuration of a new radio access link via BTS3 without releasing existing radio access links for call-1 and call-2 (radio access link via BTS1 and radio access link via BTS2) To do.

    (10) TACAFa of MS is the above-mentioned HANDOVER BRANCH ADDITION req. ind. When the setup of the radio access link for call-1 and call-2 via BTS3 is completed in accordance with Handover Branch Addition resp. conf. To the TACCF of the base station controller.

  As a result, the MS performs communication by using the diversity handover branch including BTS1, BTS2, and BTS3 for both call-1 and call-2.

FIG. 783 is a sequence diagram showing the operation of this system for implementing the application example shown in FIGS. 781 (a) and (b).
In FIG. 783, TACAFa is a functional entity of the MS in FIGS. 781 (a) and (b). TACFa is a functional entity TACF in the base station controller, which is first generated when the MS starts communication. TACFv1-1 and TACFv1-2 are instances of functional entities included in the base station controller for controlling BTS1, and correspond to call-1 and call-2, respectively. TACFv3-1 and TACFv3-2 are instances of functional entities included in the base station controller for controlling the BTS 3, and correspond to call-1 and call-2, respectively. BCFr1-1 and BCFr1-2 are instances of functional entities for radio resource control possessed by BTS1, and correspond to call-1 and call-2, respectively. BCFr3-1 and BCFr3-2 are instances of functional entities for radio resource control possessed by BTS3, and correspond to calls call-1 and call-2, respectively.

  Hereinafter, a control method for switching from the state shown in FIG. 781 (a) to the state shown in FIG. 781 (b) will be described with reference to FIG.

    (1) The TACFa of the base station control device establishes an access link for call-1 via the BTS3, so that the function entity TACFv3-1 of the base station control device corresponding to the BTS3 receives the BEARER SETUP req. ind. Send.

    (2) The above BEARER SETUP req. ind. TACFv3-1 receives BEARR & RADIO BEARER SETUP req. To BCFr3-1 of BTS3. ind. Send. This BEARER & RADIO BEARER SETUP req. ind. Calls for setting a wireless access link from BTS3 to MS and a wired access link from BTS3 to the base station controller for call-1.

    (3) In addition, the TACCa of the base station control device establishes an access link for call-2 via BTS3, so that the BEARER SETUP req is sent to the functional entity TACFv3-2 of the base station control device corresponding to BTS3. . ind. Send.

    (4) The above BEARER SETUP req. ind. TACFv3-2 receives BEARR & RADIO BEARER SETUP req. To BCFr3-2 of BTS3. ind. Send. This BEARER & RADIO BEARER SETUP req. ind. Requests the setting of the radio access link for call-2 from BTS3 to MS and the wired access link from BTS3 to the base station controller.

    (5) On the other hand, BCFr3-1 of BTS3 is the BEARER & RADIO BEARER SETUP req. ind. When the access link setting is started according to, BEARER & RADIO BEARER SETUP Processing. For reporting that the access link is being set. req. ind. Is transmitted to TACFv3-1.

    (6) TACFv3-1 is the BEARER & RADIO BEARER SETUP Proceeding. req. ind. Is received from RADIO BEARER SETUP REQUEST req. To request the TACCa of the base station controller to set up a radio access link for call-1 between the MS and BTS3. ind. Send.

    (7) In addition, BCFr3-2 of BTS3 is a BEARER & RADIO BEARER SETUP req. ind. When the access link setting is started according to, BEARER & RADIO BEARER SETUP Processing. For reporting that the access link is being set. req. ind. Is transmitted to TACFv3-2.

    (8) TACFv3-2 is the BEARER & RADIO BEARER SETUP Proceeding. req. ind. , Requesting TACCa to set up a radio access link for call-2 between the MS and BTS 3, RADIO BEARER SETUP REQUEST req. ind. Send.

    (9) TACCa is a non-soft HANDOVER Execution req. ind. Send. This Non-soft HANDOVER Execution req. ind. Is a request for switching the radio access link for call-1 and call-2 from the radio access link via BTS1 to the radio access link via BTS3.

    (10) TACAFa of MS is the above-mentioned Non-soft HANDOVER Execution req. ind. When the radio access link is switched according to the above, the synchronization establishment operation is started with call BTS3 for call-1.

    (11) Furthermore, the MS starts synchronization establishment operation with call BTS3 for call-2.

    (12) When synchronization is established for call-1, BEARR & RADIO BEARER SETUP resp. For reporting completion of establishment of the radio access link from BCFr3-1 to TACFv3-1 of BTS3. conf. Is sent.

    (13) TACFv3-1 is a BEARER & RADIO BEARER SETUP resp. conf. , BEARER SETUP resp. To report that call-1 has been successfully established via BTS3. conf. Is sent to TACCa.

    (14) When synchronization is established for call-2, BEARR & RADIO BEARER SETUP resp. For reporting completion of establishment of the radio access link from BCFr 3-2 to TACFv 3-2 of BTS3. conf. Is sent.

    (15) TACFv3-2 is a BEARER & RADIO BEARER SETUP resp. conf. Is received, BEARER SETUP resp. To the effect that establishment of the radio access link via BTS3 is completed for call-2. conf. Is sent to TACCa.

    (16) TACFa is a BEARER SETUP resp. From TACFv3-1. conf. And BEARER SETUP resp. From TACFv3-2. conf. Is received, Bearer Release req. Requesting the TACFv1-1 to release the access link for call-1. ind. Send.

    (17) TACFv1-1 uses the Bearer Release req. ind. , BEARr & RADIO BEARER RELEASE req. Requesting cancellation of access link setting via BTS1 for call-1 to BCFr1-1. ind. Send.

    (18) BCFr1-1 is the BEARER & RADIO BEARER RELEASE req. ind. , The access link maintained for call-1 is released, and BEARER & RADIO BEARER RELEASE resp. conf. Is transmitted to TACFv1-1.

    (19) Next, BEARER RELEASE resp. For reporting access link release completion from TACFv1-1 to TACFa. conf. Is sent.

In (20) to (23), operations similar to the above (16) to (19) are executed for call-2.
With this, the MS communicates with both call-1 and call-2 using the branch via BTS3.

(3.8): Control method in the case where an opportunity for handover occurs in a mobile station performing communication of multiple calls (part 2)
(3.8.1): Background of introduction of the present control method In the control method of (3.7) above, when the mobile station performs a communication corresponding to a plurality of calls, when an opportunity for handover occurs. The branch configuration and the frequency band that enable communication corresponding to all calls are determined, and handover for all calls is performed according to the determination.
When trying to implement this control method, there is a situation in which it is impossible to allocate radio resources to all calls due to a lack of communication capacity of the base station where the mobile station is located. Can occur.
In such a case, if no measures are taken, all calls must be disconnected.

However, calls that are in communication include high priority calls (for example, emergency calls) and low priority calls, and it is impossible to maintain communication for all calls, but high priority calls. For calls, radio resources may be allocated to maintain communication.
In such a case, it is very unreasonable to disconnect all calls despite maintaining high priority call communication.
This control method is introduced to eliminate such unreasonableness.

(3.8.2): Contents of this control method In this control method, when a mobile station capable of communication of a plurality of calls is performing communication, the trigger of the handover is caused by the movement of the mobile station, etc. When this occurs, the handover is controlled according to the following procedure.

a. The mobile station or network side device (for example, base station control device) determines whether or not there is a new branch configuration or frequency band that can maintain all calls in communication.
b. When there is no branch configuration or frequency band capable of maintaining all calls during communication, the mobile station or network side device recognizes the free capacity that can be allocated to the communication of the mobile station.
c. Calls that match the available capacity are selected from those with high priority, and calls that are not selected are released. For calls with the same priority level, all calls are released or some are selected according to a certain rule (the calls to be released may be selected at random or, for example, those with a long connection start time may be selected. Good), free the other.
d. The selected call is handed over to the branch or frequency band using the above free capacity.
With such control, calls other than high-priority calls are disconnected so that high-priority calls can be maintained. For high-priority calls, handover is performed so that the branch configuration and frequency band of each call are the same. Is done.

FIGS. 784 (a) and (b) show a specific application example of the present control method.
In FIG. 784 (a), the MS performs communication corresponding to call-1 and call-2 using the branch of frequency f1 via BTS1.
In this application example, the MS is shifting from the area of BTS1 to the area of BTS3, and the handover from BTS1 to BTS3 is to be performed.

However, the communication capacity of BTS3 is small and BTS3 can maintain high priority call-1, but communication between MS and BTS3 for both call-1 and low priority call-2. Can't do it.
Also, the frequency used by BTS3 is f2, and diversity handover cannot be performed with BTS1.

  Therefore, in this application example, as shown in FIG. 784 (b), call-2 with low priority in MS is disconnected, and only call-2 with high priority is changed from the branch via BTS1 to the branch via BTS3. A handover to be switched is performed, and only high-priority call-1 communication is maintained.

  FIG. 785 is a sequence diagram showing the operation of this system for implementing the application example shown in FIGS. 784 (a) and (b). In FIG. 788, the meanings of TACAFa, TACFv1-1, and the like are the same as those described with reference to FIG.

  Hereinafter, a control method for switching from the state shown in FIG. 784 (a) to the state shown in FIG. 784 (b) will be described with reference to FIG.

    (1) The TACFa of the base station control device establishes an access link for the existing call call-1 via the BTS3, and therefore, to the functional entity TACFv3-1 of the base station control device corresponding to the BTS3, the BEARER SETUP req . ind. Send.

    (2) The above BEARER SETUP req. ind. TACFv3-1 receives BEARR & RADIO BEARER SETUP req. To BCFr3-1 of BTS3. ind. Send. This BEARER & RADIO BEARER SETUP req. ind. Calls for setting a wireless access link from BTS3 to MS and a wired access link from BTS3 to the base station controller for call-1.

    (3) Next, the TACFa of the base station control device releases the access link that has been maintained for call-2 having a low priority to the functional entity TACFv1-2 of the base station control device corresponding to BTS1. , BEARER RELEASE req. ind. Send.

    (4) The above BEARER RELEASE req. ind. TACFv1-2 receives BEARR & RADIO BEARER RELEASE req. To BCFr1-2 of BTS1. ind. Send. This BEARER & RADIO BEARER RELEASE req. ind. Requests release of the radio access link for call-2 from BTS1 to MS and the wired access link from BTS1 to the base station controller.

    (5) On the other hand, BCFr3-1 of BTS3 is the BEARER & RADIO BEARER SETUP req. ind. When the access link setting is started according to RADIO BEARER SETUP Proceeding req. For reporting that the access link is being set. ind. Is transmitted to TACFv3-1.

    (6) TACFv3-1 is the BEARER & RADIO BEARER SETUP Proceeding req. ind. Is received from RADIO BEARER SETUP REQUEST req. To request the TACCa of the base station controller to set up a radio access link for call-1 between the MS and BTS3. ind. Send.

    (7) Also, BCFr1-2 of BTS1 is BEARER & RADIO BEARER RELEASE req. From TACFv1-2. ind. When the access link is released according to BEARER & RADIO BEARER RELEASE resp. conf. Is transmitted to TACFv1-2.

    (8) TACFv1-2 is the BEARER & RADIO BEARER RELEASE resp. conf. , The BEARER RELEASE resp., Which reports the release of the access link maintained for call-2 to TACCa. conf. Send.

    (9) TACCa is used in this BEARER RELEASE resp. conf. Is received, Non-soft Handover Execution req. Requesting that the connection destination of the MS should be switched from BTS1 to BTS3. ind. To the TACAFa of the MS.

    (10) TACAFa of MS is the above-mentioned Non-soft Handover Execution req. ind. When the radio access link is switched according to the above, the synchronization establishment operation is started with call BTS3 for call-1.

    (11) When synchronization is established for call-1, BEARR & RADIO BEARER SETUP resp. For reporting the completion of establishment of the radio access link from BCFr3-1 to TACFv3-1 of BTS3. conf. Is sent.

    (12) TACFv3-1 is a BEARER & RADIO BEARER SETUP resp. conf. , BEARER SETUP resp. To report that call-1 has been successfully established via BTS3. conf. Is sent to TACCa.

    (13) TACFa is a BEARER SETUP resp. From TACFv3-1. conf. Is received, the Bearer Release req. Requesting the TACFv1-1 to release the access link via the BTS1 for the call-1 that is no longer necessary. ind. Send.

    (14) TACFv1-1 uses the Bearer Release req. ind. , BEARr & RADIO BEARER RELEASE req. Requesting release of the access link via BTS1 for call-1 to BCFr1-1. ind. Send.

    (15) BCFr1-1 is the BEARER & RADIO BEARER RELEASE req. ind. , The access link via BTS1 that has been maintained for call-1 is released, and BEARER & RADIO BEARER RELEASE resp. conf. Is transmitted to TACFv1-1.

(16) Next, BEARER RELEASE resp. For reporting access link release completion from TACFv1-1 to TACCa. conf. Is sent.
With this, the MS communicates only with call-1 having a high priority by using a branch via BTS3.

(3.9): Handover control method for ending handover procedure without waiting for confirmation of establishment of branch synchronization (3.9.1): Background of introduction of this control method In the conventional mobile communication system, the following procedure is used. Was performing a handover.
(1) A new branch is set between the mobile station and the new base station.
(2) A new base station confirms the establishment of radio signal synchronization from the mobile station.
(3) Report synchronization establishment from the new base station to the base station controller.
(4) End the handover procedure.

  However, as explained so far, this system adds a new branch to the branch used for communication as needed, and uses these branches as a whole, so that the minimum necessary transmission is possible. A control method for obtaining desired communication quality with electric power is adopted. For this reason, there is no guarantee that a desired communication quality can be obtained for each of all branches, and synchronization may not be established for a branch that communicates with low transmission power (a sub-branch in the case of diversity handover). .

Therefore, if control for adding a new branch to the mobile station in this system is performed according to (1) to (4) above, confirmation of establishment of synchronization for the new branch cannot be obtained, and handover is performed. There may be a problem that the procedure is continued for a long time without being completed.
This control method is introduced to solve this problem.

(3.9.2): Contents of this control method In this system, when performing a handover, the handover procedure is terminated by starting the communication of the layer 3 message, rather than waiting for confirmation of synchronization establishment for the branch. .
That is, when the base station control device sends a new branch setting request to the base station and the mobile station, the base station control device ends the handover procedure without waiting for confirmation of establishment of synchronization for the new branch.

  Further, when the mobile station receives a request for setting a new branch, the mobile station sets a frequency corresponding to the branch to enable signal reception using the branch. After that, the mobile station considers that the branch has been established by receiving any significant signal via the branch, and immediately uses the reception signal via the branch and the reception signal via the other branch. Start diversity synthesis.

  Similarly, when the base station receives a request for setting a new branch, the base station makes it possible to receive a signal using the branch by performing frequency setting corresponding to the branch, and then performs some sort of operation via the branch. When a significant signal is received, it is considered that the branch has been established, and a signal via a new branch is immediately started. When the base station performs diversity handover within the base station, it starts diversity combining using a received signal that has passed through a new branch and a received signal that has passed through another branch. In addition, when performing intra-base station diversity handover using the base station and another base station, the base station sends a received signal that has passed through a new branch to the base station control device, and the base station control device Diversity combining using the received signal and the received signal via another base station is started.

This control method is used in the control methods up to the previous chapter.
For example, FIG. 41 shows a branch addition operation sequence for performing intra-base station diversity handover, and FIG. 43 shows a branch addition operation sequence for performing inter-base station diversity handover. When the establishment of layer 1 is completed, the mobile station can communicate at that time. Therefore, on the network side, the branch addition procedure is completed without waiting for confirmation of establishment of synchronization for the newly added sub-branch.

  Further, FIG. 770 shows an operation example of shifting to the diversity handover between base stations simultaneously with the setting of the access link. In this example, the mobile station establishes synchronization for the main branch between TACAFa and BCFr1 (Layer 1 Sync.). Is completed, layer 3 message communication can be started. Therefore, the handover procedure is terminated without confirming synchronization establishment for the sub-branch between TACAFa and BCFr2.

FIG. 773 shows an operation example in which a branch is added for diversity handover at the same time as branch switching. In this example, the mobile station establishes synchronization for the main branch after branch switching between TACAFa and BCFr2 ( Layer 1 message communication can be started by ending Layer 1 Sync.). Therefore, the handover procedure is terminated without confirming the synchronization establishment for the sub-branch between TACAFa and BCFr3.
The same applies to other operation examples (FIGS. 775, 778, etc.) that perform diversity handover. )

(3.10): Code resource management control method (3.10.1): Background of introduction of this control method In general code resource management control, reassignment of code resources (call relocation) At the start of the call and at the end of the call.
In the method of performing reallocation at the time of call occurrence, relocation is performed at the start of connection, which causes a problem that a delay until the start of connection is large.

Further, in the method of performing reallocation at the end of a call, the control for reallocation becomes redundant control, which causes a problem that the control load increases.
Further, a code resource that can be allocated to a line (referred to as an allocatable code resource) is divided into code resources having a plurality of bandwidths, and an unused code resource having any one code resource length can be allocated to the line In a wireless communication system, it is inevitable that a “fragment” is generated in which available code resources are scattered by repeatedly securing (= allocating) and releasing code resources in the code resource space.

  On the other hand, in order to secure code resources with a wide bandwidth, it is necessary to reserve unused code resources having a bandwidth corresponding to a continuous code resource space according to the bandwidth.

Therefore, it is necessary to reallocate code resources to lines in order to organize the fragments and secure unused code resources having the necessary bandwidth.
However, if the code resource is reassigned to the line at the time of the call occurrence, there is a problem that a call connection delay occurs.

  In addition, when the call is made at the end of the call, the broadband call does not always occur next, so that the redundancy control is performed, and the control load on the system increases.

Therefore, setting a trigger for reassigning code resources to lines (= call relocation) greatly improves the usability of the user and reduces the burden on the system.
Therefore, the present control method optimizes the timing for reassigning code resources to a line, reduces the frequency of reassignment, and suppresses call connection delay, base station It is an object of the present invention to provide a device, a base station control device, and a control method thereof.

(3.10.2): Overview of the present control method FIG. 793 shows the allocation status of code resources to lines at a certain point in time.
In the status of allocation to the line shown in FIG. 793, only code resources CR5-2, CR5-7, CR5-8, CR5-9, CR5-11, CR5-15 and CR5-16 are unused (unallocated). Yes, it is available.

  This is because the “clause” corresponding to the upper level of these code resources is not used. In an arbitrary “section”, if a lower “leaf” and an upper section out of the section are not used, a code resource corresponding to the section can be used. More specifically, in the node N1, since the lower leaves (= CR5-15 and CR5-16) and the upper node N2 that are output from the node N1 are unused, the code resource CR4- corresponding to the node N 8 becomes available.

  This is because the lower code resources divide and use one higher code resource.

More specifically, the bandwidth relationship of each code resource required for the level 1 code resource CR1, the level 2 code resource CR2, the level 3 code resource CR3, the level 4 code resource CR4, and the level 5 code resource CR5 is as follows: become that way.
CR1 = 2 × (CR2)
= 4 x (CR3)
= 8 x (CR4)
= 16 x (CR5)

  Therefore, for example, when a bandwidth corresponding to one level 4 code resource CR4 is allocated as a level 5 code resource, it can be used as two level 5 code resources CR5.

  Incidentally, in the allocation situation shown in FIG. 793, there are seven unused (= unallocated) level 5 code resources CR5 (= CR5-2, CR5-7, CR5-8, CR5-9, CR5-11, CR5). −15 and CR5-16) In spite of this, the level 3 code resource CR3 that is a code resource that requires a bandwidth corresponding to the four level 5 code resources CR5 cannot be secured.

  This is because all level 3 code resources CR3-1 to CR3-4 are independent from each other (that is, a continuous code resource space cannot be formed by combining a part of them), and further lower This is because at least a part of the code resource is used.

  Accordingly, when the level 3 code resource CR3 is to be used, as shown in FIG. 794, the level 3 code resource CR3 is configured with the code resource used in any section of the level 3 code resource CR3. It is necessary to move to a code resource part other than the code resource.

In this case, it is the radio base station that determines whether or not a code resource having a desired bandwidth can be secured, and the base station controller reallocates the code resource.
More specifically, when the radio base station determines that the level 3 code resource CR3-4 cannot be secured, the base station control apparatus determines that the level 5 code resource CR5-11 is to be secured. Is moved to the level 5 code resource CR5-9 having the same resource length that is unused (step S1), and the level 4 code resource CR4-7 is moved to the level 4 code resource CR4-6 having the same resource length that is not used (Step S2).
As a result, the level 3 code resource CR3-4 is secured.

By the way, as described above, when the timing for reallocating code resources greatly contributes to reducing the burden on the system.
Therefore, in this control method, a case where there is no continuous unused allocatable code resource having a preset bandwidth as a trigger for the reallocation is triggered.
More specifically, the level 3 code resource CR3 is set as a reference code resource and an assignable code resource having the maximum bandwidth that can be assigned, and a bandwidth corresponding to the level 3 code resource CR3 is set as a reference bandwidth. The point of time when the 3 code resource CR3 cannot be assigned to the line (see FIG. 793) is used as a trigger for the reassignment of the code resource.

  As a result, when the level 3 code resource CR3 cannot be assigned to the line, the reassignment process as shown in FIG. 794 is performed. In principle, the reassignment process is performed at the time of call occurrence. Therefore, connection delay can be suppressed.

  In addition, under the situation where level 3 code resource CR3 can be allocated to the line, since the reallocation process is not performed, it is possible to reduce the system control burden compared to the case where the reallocation is always performed at the end of the call. It becomes.

  As described above, the frequency of code resource reassignment (relocation) to the line is minimized, and at the time of call occurrence, code resource relocation is not accompanied, thereby suppressing connection delay. It is possible to improve the quality of service for users and improve usability.

It is a block diagram which shows the whole structure of the W-CDMA mobile communication system concerning one Embodiment of this invention. It is a block diagram which shows the structure of the access type | system | group interface in this system. It is a figure which shows the functional network architecture of this system. It is the figure which divided and showed the functional network architecture of this system in the communication control plane and the radio | wireless resource control plane. It is a figure which shows the function model of an outgoing 1st call. It is a figure which shows the function model of an outgoing call addition. 2 is an information diagram of a first call. 2 is an information diagram of a first call. 2 is an information diagram of a first call. 2 is an information diagram of a first call. 2 is an information diagram of a first call. 2 is an information diagram of a first call. 2 is an information diagram of a first call. 2 is an information diagram of a first call. It is an information diagram of an additional call. It is an information diagram of an additional call. It is an information diagram of an additional call. It is an information diagram of an additional call. It is a figure which shows the function model of an incoming first call. It is a figure which shows the functional model of an incoming call addition. It is an information flow diagram of an incoming first call. It is an information flow diagram of an incoming first call. It is an information flow diagram of an incoming first call. It is an information flow diagram of an incoming first call. It is an information flow diagram of an incoming first call. It is an information flow diagram of an incoming first call. It is an information flow diagram of an incoming first call. It is an information flow diagram of an incoming first call. It is an information flow diagram of an incoming first call. It is an information flow diagram of an incoming first call. It is an information flow diagram of an incoming call addition. It is an information flow diagram of an incoming call addition. It is an information flow diagram of an incoming call addition. It is an information flow diagram of an incoming call addition. It is an information flow diagram of an incoming call addition. It is an information flow diagram of an incoming call addition. It is a figure which shows the basic model of a user side cutting | disconnection. It is an information flow diagram of user side disconnection. It is a figure which shows the basic model of a net | network side cutting | disconnection. It is an information flow diagram of network side cutting. It is a figure which shows the functional model of the emergency release, ie, the radio link failure detected by the mobile device. It is a figure which shows the functional model of the failure of emergency release, ie, the radio link detected by a mobile station. It is a figure which shows the functional model of the failure of emergency release, ie, the radio link detected by a mobile station. It is a figure which shows the machine model in the case of emergency release, ie, the detection of the radio link failure by a network. It is a figure which shows the functional model of the radio | wireless link failure detected by the mobile station call release, ie, a network. It is a figure which shows the functional model of the radio | wireless link failure detected by the mobile station call release, ie, a network. It is a figure which shows the functional model of a user side cutting | disconnection. It is an information flow diagram of user side disconnection. It is a figure which shows the functional model of SDCCH Setup (SDCCH step-up). It is a figure which shows the information flow diagram of SDCCH setup. It is a figure which shows the information flow diagram of SDCCH setup. It is a figure which shows the functional model of the bearer setup for radio | wireless resource selection. It is a CC-Plane information flow diagram for bearer setup (radio resource selection). It is a CC-Plane information flow diagram for bearer setup (radio resource selection). It is a CC-Plane information flow diagram for bearer setup (radio resource selection). It is a CC-Plane information flow diagram for bearer setup (radio resource selection). It is a figure which shows the function model of a radio bearer release. 2 is an information flow diagram for radio bearer release. 2 is an information flow diagram for radio bearer release. It is a figure which shows the functional model of DCCH release. SDCCH is an information flow diagram for release. It is a figure which shows the general flow of a hand-over process. It is a figure which shows the general flow of a hand-over process. It is a figure which shows the general flow of a hand-over process. 3 is an information flow diagram of handover processes 1 and 2. 3 is an information flow diagram of handover processes 1 and 2. 3 is an information flow diagram of handover processes 1 and 2. 3 is an information flow diagram of handover processes 1 and 2. 3 is an information flow diagram of handover processes 1 and 2. 2 is a diagram illustrating execution of non-soft handover in a handover process 1; 4 is a diagram showing branch addition for handover in the handover process 1; 6 is a diagram showing branch deletion of handover in the handover process 1; It is a figure which shows the functional model of the branch addition between the sectors in a cell. It is a CC-Plane information flow diagram of branch addition between sectors in a cell. It is a CC-Plane information flow diagram of branch addition between sectors in a cell. It is a figure which shows the functional model of branch addition between cells. It is a CC-Plane information flow diagram for adding an inter-cell branch. It is a CC-Plane information flow diagram for adding an inter-cell branch. It is a CC-Plane information flow diagram for adding an inter-cell branch. It is a CC-Plane information flow diagram for adding an inter-cell branch. It is a figure which shows the functional model of the branch deletion handover between sectors in a cell. It is a figure which shows the CC-Plane information flow of the branch deletion handover between sectors in a cell. It is a figure which shows the CC-Plane information flow of the branch deletion handover between sectors in a cell. It is a figure which shows the functional model of the branch deletion handover between cells. It is a CC-Plane information flow diagram of branch deletion handover between cells. It is a CC-Plane information flow diagram of branch deletion handover between cells. It is a figure which shows the functional model of the branch switching handover in a cell. It is a CC-Plane information flow diagram of intra-cell branch switching handover. It is a CC-Plane information flow diagram of intra-cell branch switching handover. It is a figure which shows the functional model of the branch switching inter-cell handover. It is a CC-Plane information flow diagram of inter-cell diversity handover. It is a CC-Plane information flow diagram of inter-cell diversity handover. It is a CC-Plane information flow diagram of inter-cell diversity handover. It is a CC-Plane information flow diagram of inter-cell diversity handover. It is a CC-Plane information flow diagram of inter-cell diversity handover. It is a CC-Plane information flow diagram of inter-cell diversity handover. It is a figure which shows the functional model of ACCH switching. It is an information flow diagram of ACCH switching. It is an information flow diagram of ACCH switching. It is a CC-Plane information flow diagram of ACCH switching. It is a CC-Plane information flow diagram of ACCH switching. It is a figure which shows the functional model of code switching. It is a CC-Plane information flow diagram of code switching. The function model of transmission power control is shown. It is a CC-Plane information flow diagram of transmission power control. It is a figure which shows the functional model of terminal position update. It is an information flow diagram of terminal location update. It is an information flow diagram of terminal location update. It is an information flow diagram of terminal location update. It is an information flow diagram of terminal location update. It is the information flow diagram which combined the information element of terminal position update. It is the information flow diagram which combined the information element of terminal position update. It is a figure which shows the model of user authentication. It is an information flow diagram of user authentication. It is a figure which shows the functional model of a secrecy start timing. It is an information flow diagram of a secrecy start timing. It is a figure which shows the functional model of allocation of TMUI. It is an information flow diagram of a TMUI assignment. It is an information flow diagram of search of user ID. It is a figure which shows the pair of a physical node structure and a functional entity in this system. It is a figure which shows the protocol architecture of the signal layer 2 on a radio interface. It is a figure which shows the frame structure in the case of a BSC function termination | terminus. It is a figure which shows the sequence data of PDU (SD PDU). It is a figure which shows the content of the sequence data PDU (SDwithPOLL PDU) containing a status request. It is a figure which shows the content of Poll PDU. It is a figure which shows the content of an invariant state PDU (STAT PDU). It is a figure which shows the content of a variable state PDU (USTAT PDU). It is a figure which shows the content of unit data PDU (UD PDU) and management data PDU (MD PDU). It is a figure which shows the content of Begin PDU (BGN PDU). It is a figure which shows the content of Begin confirmation PDU (BGAK PDU). It is a figure which shows the content of Begin rejection PDU (BGREJ PDU). It is a figure which shows the content of End PDU (END PDU). It is a figure which shows the content of End confirmation PDU (ENDAK PDU). It is a figure which shows the content of the resynchronization PDU (RS PDU). It is a figure which shows the content of the resynchronization confirmation PDU (RSAK PDU). It is a figure which shows the content of error recovery PDU (ER PDU). It is a figure which shows the content of error recovery confirmation PDU (ERAK PDU). It is a figure which shows the content of BCCH. It is a figure which shows the content of PCH. It is a figure which shows the content of RACH-L, S. It is a figure which shows the content of FACH-L. It is a figure which shows the content of FACH-S. It is a figure which shows the content of SDCCH. It is a figure which shows the content of ACCH. It is a figure which shows the content of UPCH. It is a figure which shows notionally an example of a radio | wireless interface protocol architecture. It is a figure which shows the message structure of a RBC message. It is a figure which shows RBC information basic composition. It is a figure which shows a message structure. It is a figure for demonstrating Protocol discriminator (protocol identifier). It is a figure for demonstrating a call number. It is a figure for demonstrating a call number. It is a figure which shows the format of a message classification. It is a figure which shows the format of the variable-length information element in a FPLMTS environment. It is a figure which shows the format of the variable-length information element in a FPLMTS environment. It is a figure for demonstrating a broadband fixed shift information element. It is a figure for demonstrating a broadband temporary shift information element. It is a figure for demonstrating an AAL parameter information element. It is a figure for demonstrating an AAL parameter information element. It is a figure for demonstrating an AAL parameter information element. It is a figure for demonstrating an AAL parameter information element. It is a figure for demonstrating an AAL parameter information element. It is a figure for demonstrating an ATM traffic descriptor information element. It is a figure for demonstrating an ATM traffic descriptor information element. It is a figure for demonstrating a broadband transmission capability information element. It is a figure for demonstrating a broadband high-order layer information information element. It is a figure for demonstrating a broadband low-order layer information information element. It is a figure for demonstrating a broadband low-order layer information information element. It is a figure for demonstrating a broadband low-order layer information information element. It is a figure for demonstrating a called number information element. It is a figure for demonstrating a destination subaddress information element. It is a figure for demonstrating a calling number information element. It is a figure for demonstrating a calling number information element. It is a figure for demonstrating a calling subaddress information element. It is a figure for demonstrating a connection identifier information element. It is a figure for demonstrating an end-end relay delay information element. It is a figure for demonstrating a quality of service (QOS) parameter information element. It is a figure for demonstrating a broadband repetition identifier information element. It is a figure for demonstrating a broadband repetition identifier information element. It is a figure for demonstrating a relay network selection information element. It is a figure for demonstrating a notification identifier information element. It is a figure for demonstrating an OAM traffic descriptor information element. It is a figure for demonstrating a narrow-band transmission capability information element. It is a figure for demonstrating a narrow-band high layer compatibility information element. It is a figure for demonstrating a narrow band low layer compatibility information element. It is a figure for demonstrating a progress identifier information element. It is a figure for demonstrating TMUI. It is a figure for demonstrating TMUI Assignment Source ID. It is a figure for demonstrating IMUI. It is a figure for demonstrating Execution Authentication Type. It is a figure for demonstrating Authentication Random Pattern. It is a figure for demonstrating Authentication Ciphering Pattern. It is a figure for demonstrating Execution Ciphering Type. It is a figure for demonstrating TC Info. It is a figure for demonstrating the message type of a RBC message information element. It is a figure for demonstrating an information element identifier. It is a figure for demonstrating a RADIO BEARER SETUP message intrinsic | native parameter. It is a figure for demonstrating a RADIO BEARER RELEASE message intrinsic | native parameter. It is a figure for demonstrating a RADIO BEARER RELEASE COMPLETE message intrinsic | native parameter. It is a figure for demonstrating a HANDOVER COMMAND message intrinsic | native parameter. It is a figure for demonstrating a HANDOVER RESPONSE message intrinsic | native parameter. It is a figure which shows the structure of radio | wireless bearer setting information. It is a figure which shows the structure of radio | wireless bearer setting information. It is a figure which shows the structure of radio | wireless bearer setting information. It is a figure which shows the structure of radio | wireless bearer setting information. It is a figure which shows the structure of DHO addition. It is a figure which shows the structure of DHO addition. It is a figure which shows the structure of DHO addition. It is a figure which shows the structure of DHO addition. It is a figure which shows the structure of DHO deletion. It is a figure which shows the structure of ACCH switching. It is a figure which shows the structure of branch switching. It is a figure which shows the structure of branch switching. It is a figure which shows the structure of branch switching. It is a figure which shows the structure of user rate switching. It is a figure which shows the structure of user rate switching. It is a figure which shows the structure of user rate switching. It is a figure which shows the structure of user rate switching. It is a figure which shows the structure of code switching. It is a figure which shows the structure of code switching. It is a figure for demonstrating the message type of a RRC message information element. It is a figure which shows the structure of a facility. It is a figure which shows the structure of ROSE PDU. It is a figure which shows the structure of ROSE PDU. It is a figure which shows the structure of the number of area candidate sectors, the number of area areas in communication, the number of DHO addition candidate sectors, the number of DHO deletion sectors, and the number of HHO candidate sectors. It is a figure which shows the structure of a BTS number. It is a figure which shows the structure of a sector number. It is a figure which shows the structure of a perch CH reception SIR value. It is a figure which shows the structure of a perch CH transmission power value. It is a figure which shows the structure of a long code phase difference. It is a figure which shows the structure of the number of RBC ID. It is a figure which shows the structure of RBC ID. It is a figure which shows the structure of required SIR. It is a figure which shows the structure of a FER measurement value. It is a figure which shows a TAC message structure. It is a figure for demonstrating Protocol discriminator. It is a figure which shows the format of Message type. It is a figure for demonstrating a TERMINAL ASSOCIATION SETUP message specific parameter information element. It is a figure for demonstrating the PAGING RESPONSE message specific parameter information element. It is a figure for demonstrating a TERMINAL ASSOCIATION RELEASE message specific parameter information element. It is a figure for demonstrating Cause information element. It is a figure for demonstrating a Mobile station type information element. It is a figure for demonstrating a Paged MS ID information element. It is a figure for demonstrating a Paging ID information element. It is a figure for demonstrating a TMUI information element. It is a figure for demonstrating a TAC extension information element. It is a figure for demonstrating a message classification information element. It is a figure for demonstrating an information element length information element. It is a figure for demonstrating a perch reception SIR information element. It is a figure for demonstrating a short code number information element. It is a figure for demonstrating a frame offset group information element. It is a figure which shows the structure of a slot offset group information element. It is a figure which shows the structure of a network number information element. It is a figure which shows the structure of the VER information element of a network. It is a figure which shows the structure of a mobile station common parameter VER information element. It is a figure which shows the structure of a BTS number information element. It is a figure which shows the structure of a sector number information element. It is a figure which shows the structure of a location registration area multiplexing number (N) information element. It is a figure which shows the structure of a position number information element. It is a figure which shows the structure of a location registration timer information element. It is a figure which shows the structure of the base station required received power value information element after correction | amendment. It is a figure which shows the structure of the perch LC number (M) information element for a visiting zone determination. It is a figure which shows the structure of a base station use frequency band number (K) information element. It is a figure which shows the structure of a frequency band information element. It is a figure which shows the structure of a BCCH receiving area length information element. It is a figure which shows the structure of a calling mobile station number information element. It is a figure which shows the structure of a Paged MS ID information element. It is a figure which shows the structure of a Paging ID information element. It is a conceptual diagram of the protocol architecture on the interface between BTS-MCC. It is a figure which shows the message structure of BC message. It is a figure which shows the message structure of a BSM message. It is a figure which shows the information element basic composition of a BSM message. It is a figure which shows the information element basic composition of BC message. It is a figure for demonstrating a protocol identifier. It is a figure for demonstrating message classification. It is a figure for demonstrating LINK REFERENCE. It is a figure for demonstrating an information element identifier. It is a figure for demonstrating information element length. It is a figure for demonstrating AAL TYPE. It is a figure for demonstrating LINK IDENTIFIER. It is a figure for demonstrating transmission quality. It is a figure for demonstrating a sector number. It is a figure for demonstrating information transfer capability. It is a figure for demonstrating frequency band selection conditions. It is a figure for demonstrating a frequency band. It is a figure for demonstrating a frame offset group. It is a figure for demonstrating a slot offset group. It is a figure for demonstrating long code phase difference information. It is a figure for demonstrating an uplink long code number. It is a figure for demonstrating an uplink short code classification. It is a figure for demonstrating the number of uplink codes. It is a figure for demonstrating an uplink short code number. It is a figure for demonstrating a downlink short code classification. It is a figure for demonstrating the number of downlink codes. It is a figure for demonstrating AAL TYPE (for ACCH). It is a figure for demonstrating LINK IDENTIFIER (for ACCH). It is a figure for demonstrating transmission quality (for ACCH). It is a figure for demonstrating a downlink short code number. It is a figure for demonstrating a result. It is a figure for demonstrating CAUSE. It is a figure for demonstrating initial transmission power. It is a figure for demonstrating Location Identity. It is a figure for demonstrating the protocol identifier of a BSM message. It is a figure for demonstrating message classification. It is a figure for demonstrating PCH group calculation information. It is a figure for demonstrating a position number. It is a figure for demonstrating Paged MS ID. It is a figure for demonstrating Paging ID. It is a SDL figure for BSM. It is a SDL figure by NE (BSC function) side for BC in SDCCH. It is a SDL figure by NE (BSC function) side for BC in SDCCH. It is a SDL figure by the side of NW (BSC function) for BC in TCH / ACCH. It is a SDL figure by the side of NW (BSC function) for BC in TCH / ACCH. It is a SDL figure by the side of BTS for BC in SDCCH. It is a SDL figure by the side of BTS for BC in SDCCH. It is a SDL figure by the side of BTS for BC in TCH / ACCH. It is a SDL figure by the side of BTS for BC in TCH / ACCH. It is the block diagram which showed an example of the handover in this system. It is the block diagram which showed an example of the system which permits communication of a several call simultaneously with one mobile station apparatus. It is the block diagram which showed the structure in connection with ACCH switching of this system by the functional entity. It is a sequence diagram which shows an example of the switching operation | movement of ACCH in this system. It is a figure which shows the structure of an OSI reference model. It is a figure which shows the sequence between the network and the mobile station apparatus at the time of the incoming call in this system. It is a figure which shows description of the abbreviation used by this specification. It is a figure which shows the content of a service. It is a figure which shows the content of 8 kbit / s voice bearer service. It is a figure which shows the content of a 64 kbit / s unrestricted bearer service. It is a figure which shows the content of the multiple rate non-restriction bearer service. It is a figure which shows a functional entity (Functional Entity) name. It is a figure which shows the relationship of each functional entity. TA SETUP req. ind. (TA setup req.ind.) Is a diagram for explaining. TA SETUP req. ind. It is a figure for demonstrating an example of (TA setup req.ind.). TA SETUP PERMISSION req. ind. (TA setup permission req.ind.) Is a diagram for explaining. Reverse Long Code Retrieval req. Used for searching for an uplink long code. ind. FIG. 10 is a diagram for explaining (uplink long code search req.ind.). Reverse Long Code Retrieval req. Used for searching for an uplink long code. ind. FIG. 10 is a diagram for explaining (uplink long code search req.ind.). Reverse Long Code Retrieval resp. Used for searching for an uplink long code. conf. (Uplink long code search resp.conf.) Is a diagram for explaining. TERMINAL STATUS UPDATE req. Used for terminal status update. ind. It is a figure for demonstrating (terminal state update req.ind.). TERMINAL STATUS UPDATE resp. conf. It is a figure for demonstrating (terminal state update resp.conf). ADD ROUTING INFO req. Sent to the LRDF to add a routing address to the subscriber's profile. ind. FIG. 11 is a diagram for explaining (routing information addition req.ind.). ADD ROUTING INFO resp. ind. It is a figure for demonstrating (routing information addition resp.ind.). In order to notify the TACF of the approval of access to the network of the mobile terminal, TA SETUP PERMISSION resp. conf. It is a figure for demonstrating LRCF which activates (TA setup permission resp.conf.). Reverse Long Code Retrieval resp. Used for uplink long code search. conf. (Uplink long code search resp.conf.) Is a diagram for explaining. TA SETUP resp. Notifies completion of establishment of terminal access. conf. (TA setup resp.conf.) Is a diagram for explaining. TA SETUP resp. Used for confirmation of terminal access, setup of connection completion between CCAF and TACAF. conf. (TA setup resp.conf.) Is a diagram for explaining. SETUP req. Used for connection establishment request. ind. FIG. 6 is a diagram for explaining (setup req.ind.). TACF Instance ID Indication req. Used for searching for an upstream long code. ind. FIG. 6 is a diagram for explaining (TACF instance ID instruction req.ind.). CELL CONDITION MEASUREMENT req. ind. It is a figure for demonstrating (cell state detection req.ind.). CELL CONDITION MEASUREMENT req. ind. (Cell state detection req. Ind.) CELL CONDITION MEASUREMENT resp. conf. It is a figure for demonstrating (cell state detection resp.conf.). CELL CONDITION REPORT req. ind. (Cell state report req. Ind.) Is a diagram for explaining. CALL SETUP PERMISSION req. For outgoing user authentication request. ind. It is a figure for demonstrating SSF which invokes (call setup permission req.ind.). USER PROFILE RETRIVAL req. Used for user profile search request. ind. (User Pro) Ille Search req. ind. It is a figure for demonstrating. USER PROFILE RETRIVAL rep. conf. It is a figure for demonstrating (user profile search resp.conf.). CALL SETUP PERMISSION resp. For sending user authentication notification. conf. It is a figure for demonstrating LRCF which invokes (call setup permission resp.conf.). SETUP req. Used for connection establishment request. ind. FIG. 6 is a diagram for explaining (setup req.ind.). PROCEEDING req. ind. It is a figure explaining (procedure req. Ind.). Measurement Condition Notification req. Used for instructing detection and reporting of cell selection information in the mobile device. ind. It is a figure for demonstrating (state detection req.ind.). Measurement Condition Notification req. Used for instructing detection and reporting of cell selection information in the mobile device. ind. FIG. 10 is another diagram for explaining (state detection req. Ind.). REPORT req. Used for reporting network status and / or other types of information (eg, attention, hold, hold, release, etc.). ind. It is a figure for demonstrating (report req.ind.). REPORT req. Used for reporting network status and / or other types of information (eg, attention, hold, hold, release, etc.). ind. It is another figure for demonstrating (report req.ind.). SETUP resp. Used for confirmation of connection establishment. conf. It is a figure for demonstrating (setup resp.conf.). SETUP resp. Used for confirmation of connection establishment. conf. It is a figure for demonstrating (setup resp.conf.). SETUP req. Used for connection establishment request. ind. It is a figure for demonstrating (setup req.ind). ROUTING INFO. Used for routing search. QUERY req. ind. It is a figure for demonstrating (routing information search req.ind.). TERMINAL ID RETRIVAL req. Used for user profile search request. ind. It is a figure for demonstrating (terminal ID search req.ind.). Terminal ID search req. ind. TERMINAL ID RETRIEVAL resp. conf. It is a figure for demonstrating (terminal ID search resp.conf.). For example, TERMINAL STATUS QUERY req. Is used for searching for a terminal state when the terminal is accessing. ind. It is a figure for demonstrating (terminal state search req.ind.). Terminal state search req. ind. TERMINAL STATUS QUERY resp. conf. It is a figure for demonstrating (terminal state search resp.conf.). TERMINAL STATUS UPDATE req. Used for terminal status update. ind. It is a figure for demonstrating (terminal state update req.ind.). Terminal status update req. ind. TERMINAL STATUS UPDATE resp. conf. It is a figure for demonstrating (terminal state update resp.conf.). PAGING AREA QUERY req. Used for searching for a paging area including TACF when it is recognized that the terminal is not accessing. ind. FIG. 6 is a diagram for explaining (paging area search req.ind.). Paging area search req. ind. PAGING AREA QUERY resp. conf. FIG. 10 is a diagram for explaining (paging area search resp.conf.). PAGE req. Used to start paging of TACF. ind. (Page req.ind.) It is a figure for demonstrating. PAGING req. Is used to encode the mobile device in order to determine the communication path by positioning the mobile device in the network. ind. (Paging req.ind.) It is a figure for demonstrating. PAGING req. ind. (Paging rep.ind.) Used as a response to PAGING resp. conf. It is a figure for demonstrating (paging resp.conf.). PAGING resp. Used when notifying the LRCF of the paging result. conf. It is a figure for demonstrating (paging resp.conf.). Reverse Long Code Retrieval req. Used for uplink long code search. ind. FIG. 10 is a diagram for explaining (uplink long code search req.ind.). Reverse Long Code Retrieval req. Used for searching for an uplink long code. ind. FIG. 10 is a diagram for explaining (uplink long code search req.ind.). Reverse Long Code Retrieval resp. Used for searching for an uplink long code. conf. (Uplink long code search resp.conf.) Is a diagram for explaining. Cell Condition Measurement req. Used to start detection of cell selection information. ind. (Cell state detection req.ind.) Is a diagram for explaining. Cell Condition Measurement req. ind. (Cell Condition Measurement resp.) That provides a detection result of cell selection information in response to a request from (cell state detection req.ind.). conf. (Cell state detection resp.conf.) Is a diagram for explaining. Cell Condition Report req. Used to report cell selection information. ind. FIG. 6 is a diagram for explaining (cell state report req.ind.). ADD ROUTING INFO. Sent to LRDFp to add routing information to the subscriber profile. req. ind. FIG. 11 is a diagram for explaining (routing information addition req.ind.). ADD ROUTING INFO. req. ind. (ADD ROUTING INFO.) Which is a response to (routing information addition req.ind.). resp. conf. It is a figure for demonstrating (routing information addition resp.conf.). PAGE AUTHORIZED req. Used to notify the authentication result of the terminal to TACF. ind. It is a figure for demonstrating (page authentication req.ind.). Reverse Long Code Retrieval resp. Used for uplink long code search. conf. (Uplink long code search resp.conf.) Is a diagram for explaining. It is a figure explaining Routing address and TACF instance ID (address routing and TACF instance ID). SETUP req. Used for establishing a connection. ind. FIG. 6 is a diagram for explaining (setup req.ind.). TERMINATION ATTEMPT req. Used for requesting the user's profile when communication continuation is required. ind. It is a figure explaining (termination trial req.ind.). USER PROFILE RETRIVAL req. Used to retrieve the profile of the called user from the LRDF. ind. It is a figure for demonstrating (user profile search req.ind.). USER PROFILE RETRIVAL resp. Responding to a request from the LRCF. conf. It is a figure for demonstrating (user profile search resp.conf.). TERMINATION ATTEMPT resp. Responds to a request from the SSF. conf. It is a figure for demonstrating (termination trial resp.conf.). SETUP req. Used for establishing a connection. ind. FIG. 6 is a diagram for explaining (setup resp.conf.). Proceeding req., Which reports the validity and authentication of the called party's connection setup as desired, and also reports that the routing and call status is ongoing. ind. It is a figure for demonstrating (continuation req.ind.). Measurement Condition Notification req. Used to indicate detection and reporting of cell selection information in the mobile device. ind. It is a figure for demonstrating (state detection req.ind.). REPORT req. Used for reporting the network reporting status and / or other types of information. ind. It is a figure for demonstrating (report req.ind). SETUP resp. Used for confirmation of connection establishment. conf. It is a figure for demonstrating (setup req.ind). The transmitted SETUP resp. conf. (SETUP resp.conf.) CONNECTED req. ind. It is a figure for demonstrating (connection req.ind). call ID (call ID) and RELEASE req. used to release resources built into the call connection such as channel. ind. (Release req.ind.) Is a diagram for explaining. The RELEASE resp. Used to indicate the release of all resources previously incorporated in the connection. conf. It is a figure for demonstrating (release resp.conf.). TA RELEASE req. Used to notify detection of call release. ind. It is a figure explaining (release req.ind.). TERMINAL STATUS MAKE IDLE req. Used to make the terminal call state idle. ind. It is a figure for demonstrating (terminal availability state req.ind.). TERMINAL STATUS MAKE IDLE req. ind. (TERMINAL STATUS MAKE IDLE resp. Responding to the request of the terminal availability state req.ind.) conf. It is a figure for demonstrating (terminal availability state resq.ind.). TA RELEASE req. ind. (TA release req.ind.) TA RELEASE resp. conf. (TA release resp.conf.) Is a diagram for explaining. RELEASE req. Used to release resources built into the call connection such as call number, channel. ind. (Release req.ind.) Is a diagram for explaining. The RELEASE resp. Used to indicate the release of all resources previously incorporated in the connection. conf. It is a figure for demonstrating (release resp.conf.). TA RELEASE req. To notify LRCF of detection of call release attempt. ind. It is a figure for demonstrating TACF which activates (release req.ind.). TERMINAL STATUS MAKE IDLE req. Used to make the terminal call state idle. ind. It is a figure for demonstrating (terminal availability state req.ind.). TERMINAL STATUS MAKE IDLE req. ind. TERMINAL STATUS MAKE IDLE resp. Responds to the request of (station free state req.ind.). conf. It is a figure for demonstrating (terminal availability state resq.ind.). TA RELEASE req. ind. (TA release req.ind.) TA RELEASE resp. conf. (TA release resp.conf.) Is a diagram for explaining. RADIO LINK FAILURE req. Used for notification of radio link failure detected by BCAF or BCFr. ind. (Radio link failure req.ind.) Is a diagram for explaining. RELEASE NOTIFICATION req. Used to report connection release between network and terminal. ind. (Release notification req.ind.) Is a diagram for explaining. RADIO LINK FAILURE req. Used for notification of detection of radio link failure. ind. (Radio link failure req.ind.) Is a diagram for explaining. RADIO LINK FAILURE req. Used for notification of detection of radio link failure. ind. (Radio link failure req.ind.) Is a diagram for explaining. RADIO LINK FAILURE req. ind. RADIO LINK FAILURE resp. Used for confirmation of (radio link failure req.ind.) conf. (Radio link failure resp.conf.) Is a diagram for explaining. RADIO BEARER RELEASE req. Used for radio bearer release request. ind. (Radio bear release req.ind.) Is a diagram for explaining. BEARER RELEASE req. Sent by the TACF to release the bearer to the BCF. ind. (Bearer release req.ind.) Is a diagram for explaining. BCF is RADIO BEARER RELEASE req. ind. RADIO BEARER RELEASE resp. conf. It is a figure for demonstrating. BEARER RELEASE req. Sent to request the TACF in which the anchor TACF is in operation to release the bearer that is releasing the call. ind. (Bearer release req.ind.) Is a diagram for explaining. BEARER RELEASE req. Used to cause BCF to release radio bearer. ind. (Bearer release req.ind.) Is a diagram for explaining. BEARER RELEASE req. ind. (BEARER RELEASE resp. Used to confirm (bearer release req.ind.). conf. It is a figure for demonstrating (bearer release resp.conf.). BEARER & RADIO BEARER RELEASE req. ind. It is a figure for demonstrating TACF which releases a bearer and a radio bearer by activating (bearer and radio bearer release req.ind.). BEARER & RADIO BEARER RELEASE req. ind. (BEARER & RADIO BEARER RELEASE resp. Used for confirmation of bearer and radio bearer release by request of (bearer and radio bearer release req.ind.). conf. (Bearer and radio bearer release resp.conf.) FIG. BEARER RELEASE resp. Used to notify completion of radio bearer release. conf. It is a figure for demonstrating (bearer release resp.conf.). TA RELEASE req. Sent by TACF to notify LRCF of detection of call release attempt. ind. (TA release req.ind.) Is a diagram for explaining. TERMINAL STATUS MAKE IDLE req. Used for requesting updated user profile. ind. It is a figure for demonstrating (terminal availability state req.ind.). TERMINAL STATUS MAKE IDLE req. ind. TERMINAL STATUS MAKE IDLE resp. Responds to the request of (station free state req.ind.). conf. It is a figure for demonstrating (terminal state emptying resq.ind.). TA RELEASE req. ind. TA RELEASE resp. Used for confirmation against (TA release req.ind.). conf. (TA release resp.conf.) Is a diagram for explaining. BCFr or BCFA. RADIO LINK FAILURE req. Used for detection of radio link failure and notification of reports. ind. (Radio link failure req.ind.) Is a diagram for explaining. RADIO LINK FAILURE req. Used for notification of geolink failure detection. ind. (Radio link failure req.ind.) Is a diagram for explaining. RADIO LINK FAILURE req. ind. RADIO LINK FAILURE resp. Used to confirm (radio link failure req.ind.). conf. FIG. 6 is a diagram for explaining (radio link failure resp.conf.). RADIO BEARER RELEASE req. Used for radio bearer release request. ind. FIG. 6 is a diagram for explaining (radio bearer release req.ind.). RELEASE NOTIFICATION req. Used to indicate connection release between network and terminal. ind. (Release notification req.ind.) Is a diagram for explaining. RELEASE NOTIFICATION req. ind. (RELEASE NOTIFICATION resp. Used to confirm (release notification req.ind.). conf. (Release notification resp.conf.) Is a diagram for explaining. BEARER RELEASE req. Used to cause BCF to release radio bearer. ind. (Bearer release req.ind.) Is a diagram for explaining. BEARER RELEASE req. ind. (BEARER RELEASE resp. Used to confirm (bearer release req.ind.). conf. It is a figure for demonstrating (bearer release resp.conf.). BEARER RELEASE req. ind. It is a figure for demonstrating the anchor TACF which requests | requires the release of the bearer which is releasing the call to the TACF in operation by transmission of (bearer release req.ind.). BEARER RELEASE req. Used to cause BCF to release radio bearer. ind. (Bearer release req.ind.) Is a diagram for explaining. BEARER RELEASE req. ind. (BEARER RELEASE resp. Used to confirm (bearer release req.ind.). conf. It is a figure for demonstrating (bearer release resp.conf.). BEARER & RADIO BEARER RELEASE req. Used by TACF to release bearers and radio bearers. ind. (Bearer and radio bearer release req.ind.) FIG. BEARER & RADIO BEARER RELEASE req. ind. (BEARER & RADIO BEARER RELEASE resp. Used for confirmation of bearer and radio bearer release by request of (bearer and radio bearer release req.ind.) conf. (Bearer and radio bearer release resp.conf.) FIG. BEARER RELEASE resp. Used to notify completion of radio bearer release. conf. It is a figure for demonstrating (bearer release resp.conf.). RADIO BEARER RELEASE req. Activated in response to a radio bearer release request. ind. FIG. 6 is a diagram for explaining (radio bearer release req.ind.). RADIO BEARER RELEASE req. ind. (Radio Bearer RELEASE resp. Used for confirmation of radio bearer release by request of (Radio Bearer Release req.ind.). conf. (Radio bearer release resp.conf.) Is a diagram for explaining. TA RELEASE req. Sent by TACF to notify LRCF of detection of call release attempt. ind. (TA release req.ind.) Is a diagram for explaining. TERMINAL STATUS MAKE IDLE req. Used for update user profile request. ind. It is a figure for demonstrating (terminal availability state req.ind.). TERMINAL STATUS MAKE IDLE req. ind. (TERMINAL STATUS MAKE IDLE resp. Responding to the request of the terminal availability state req.ind.) conf. It is a figure for demonstrating (terminal state emptying req.ind.). TA RELEASE req. ind. TA RELEASE resp. Used for confirmation against (TA release req.ind.). conf. (TA release resp.conf.) Is a diagram for explaining. CALL DISCONNECT req. Used for notifying detection of disconnection on the user side to the LRCF. ind. FIG. 6 is a diagram for explaining (call disconnection req.ind.). USER PROFILE UPDATE req. Used for user profile update request. ind. It is a figure for demonstrating (user profile update req.ind.). USER PROFILE UPDATE resp. conf. (USER PROFILE UPDATE resp.) Responding to the request (user profile update resp.conf.). conf. It is a figure for demonstrating (user profile update resp.conf.). CALL DISCONNECT req. ind. CALL DISCONNECT resp. Responding to the request (call disconnect req.ind.). conf. It is a figure for demonstrating (call disconnection resp.conf.). SIGNALING CHANNEL SETUP REQUEST req. Used to request the network to set up a signaling channel. ind. FIG. 6 is a diagram for explaining (signal channel setup request req.ind.). SIGNALING CHANNEL SETUP req. Used to make a signal channel set allocation request to the network. ind. FIG. 6 is a diagram for explaining (signal channel setup req.ind.). SIGNALING CHANNEL SETUP resp. Used to allocate radio resources to the signal channel. conf. FIG. 6 is a diagram for explaining (signal channel setup resp.conf.). SIGNALING CHANNEL SETUP REQUESTED req. Used to indicate reception of a signal channel request (detection of initial access) from the mobile terminal and to request a setup matching the signal channel in the network. ind. FIG. 6 is a diagram for explaining (signal channel setup request req.ind.). SIGNALING CONNECTION SETUP req. For requesting setup of signal connection between TACF and SACF and SCMF. ind. It is a figure for demonstrating. SIGNALING CONNECTION SETUP resp. Used for reporting signaling channel establishment (including hardware and network channels). conf. It is a figure for demonstrating (signal connection setup resp.conf.). SIGNALING CONNECTION SETUP req. Used to set up signal connection between TACF and SACF and SCMF. ind. FIG. 6 is a diagram for explaining (signal connection setup req.ind.). BEARER SETUP req. Used for request to establish access bearer from CCF to TACF. ind. (Bearer setup req.ind.) Is a diagram for explaining. CHANNEL SELECTION resp. Used for reporting radio resources registered for the TACF that requested registration. conf. FIG. 6 is a diagram for explaining (channel selection resp.conf.). A BEARER SETUP req. Request for establishing an access bearer that the TACF sends to the BCF. ind. (Bearer setup req.ind.) Is a diagram for explaining. BEARER SETUP resp. Sent for confirmation of access bearer establishment and for display of Bearer ID (bearer ID) between BCFs. conf. It is a figure for demonstrating (bearer setup resp.conf.). BEARER SETUP req. Used for request to establish access bearer from TACCF to TACFv. ind. (Bearer setup req.ind.) Is a diagram for explaining. A BEARER SETUP req. Request for establishing an access bearer that the TACF sends to the BCF. ind. (Bearer setup req.ind.) Is a diagram for explaining. A BEARER SETUP resp. Request for establishing an access bearer sent by the BCF to the TACF. conf. It is a figure for demonstrating (bearer setup resp.conf.). BEARER & RADIO BEARER SETUP req. Sent for BCFr request for establishing a radio bearer and a bearer establishment request between BCFs. ind. It is a figure for demonstrating (bearer and radio | wireless bearer setup req.ind.). RADIO BEARER SETUP PROCEEDING req. To send to report the validity of the radio bearer received by the BCFr and the continuation of radio bearer establishment. ind. FIG. 6 is a diagram for explaining (radio bearer setup procedure req.ind.). RADIO BEARER SETUP REQUEST req. Sent to request a newly approved radio bearer from the TACF controlling the new access bearer to the TACF having the signal connection. ind. It is a figure for demonstrating. RADIO BEARER SETUP req. To be transmitted to TACAF for requesting establishment of a radio bearer. ind. FIG. 6 is a diagram for explaining (radio bearer setup req.ind.). RADIO BEARER SETUP req. That TACAF sends to BCAF to establish a radio bearer request. ind. FIG. 6 is a diagram for explaining (radio bearer setup req.ind.). In order to confirm the completion of establishment of the radio bearer that BCAF transmits to TACAF, RADIO BEARER SETUP resp. conf. FIG. 6 is a diagram for explaining (radio bearer setup resp.conf.). In order to confirm the establishment of the radio bearer and the bearer establishment between the BCFs, the transmitted BEARER & RADIO BEARER SETUP resp. conf. (Bearer and radio bearer setup resp.conf.) Is a diagram for explaining. BEARER SETUP resp. Used for confirming completion of access bearer establishment. conf. It is a figure for demonstrating (bearer setup resp.conf.). BEARER SETUP resp. Used for confirming completion of access bearer establishment. conf. It is a figure for demonstrating (bearer setup resp.conf.). BEARER RELEASE req. Used to notify that the bearer associated with the call is in the process of being released. ind. (Bearer release req.ind.) Is a diagram for explaining. RADIO BEARER RELEASE req. Used to make a radio bearer release request. ind. FIG. 6 is a diagram for explaining (radio bearer release req.ind.). RADIO BEARER RELEASE req. ind. RADIO BEARER RELEASE resp. Used to confirm (radio bearer release req.ind.). conf. (Radio bearer release resp.conf.) Is a diagram for explaining. BEARER RELEASE req. Used to cause BCF to release radio bearer. ind. (Bearer release req.ind.) Is a diagram for explaining. BEARER RELEASE resp. conf. It is a figure for demonstrating (bearer release resp.conf.). BEARER RELEASE req. Sent to request bearer release related to a call in which TACFa is releasing to TACFv. ind. (Bearer release req.ind.) Is a diagram for explaining. BEARER RELEASE req. Used to release radio bearer to BCF. ind. (Bearer release req.ind.) Is a diagram for explaining. BEARER RELEASE req. ind. (BEARER RELEASE resp. Used to confirm (bearer release req.ind.). conf. It is a figure for demonstrating (bearer release resp.conf.). BEARER & RADIO BEARER RELEASE req. Used for bearer and radio bearer release. ind. (Bearer and radio bearer release req.ind.) FIG. BEARER & RADIO BEARER RELEASE req. ind. (BEARER & RADIO BEARER RELEASE resp. Used for confirmation of bearer and radio bearer release by request of (bearer and radio bearer release req.ind.). conf. (Bearer and radio bearer release resp.conf.) FIG. BEARER RELEASE resp. Used for notification of completion of request for radio bearer release to TACF. conf. It is a figure for demonstrating (bearer release resp.conf.). BEARER RELEASE resp. Used for notification of completion of request for radio bearer release to CCF. conf. It is a figure for demonstrating (bearer release resp.conf.). RADIO BEARER RELEASE req. Used by TACAF for radio bearer release request. ind. FIG. 6 is a diagram for explaining (radio bearer release req.ind.). RADIO BEARER RELEASE req. ind. (Radio Bearer RELEASE resp. Used for confirmation of radio bearer release by (Radio Bearer Release req.ind.). conf. FIG. 6 is a diagram for explaining (radio bearer release resp.conf.). SIGNALING CHANNEL RELEASE REQUEST req. For request to release signaling channel used between MCF and TACF. ind. FIG. 6 is a diagram for explaining (signal channel release request req.ind.). SIGNALING CONNECTION RELEASE req. Used for a request to release a signaling channel (including both network and radio resources). ind. FIG. 6 is a diagram for explaining (signal connection release req.ind.). SIGNALING CONNECTION RELEASE resp. Used for signaling channel release reporting. conf. (Signal connection release resp.conf.) Is a diagram for explaining. BEARER SETUP req. That TACFa sends to TACFv to set up an access bearer. ind. It is a figure which shows the content of (bearer setup req.ind.). INTRA BCFr HANDOVER BRANCH ADDITION req. ind. (Own station BCFr) Add additional branch req. ind. FIG. An INTRA BCFr HANDOVER BRANCH ADDITION resp. Sent by the BCFr to notify the TACF of completion of setup of one or more hardware radio channels. conf. It is a figure which shows the content of (own station BCFr handover branch addition resp.conf.). RADIO BEARER SETUP REQUEST req. Which is transmitted for a radio bearer setup request between the mobile terminal and the BCFr under the control of TACF by the base TACF. ind. It is a figure which shows the content of (Radio bearer setup request req.ind.). HANDOVER Branch Addition req. Used for notification of BS diversity of the local station of handover with added branch. ind. (Handover branch addition req.ind.) Is a diagram for explaining. RADIO BEARER SETUP req. That TACAF sends to BCAF for a radio bearer setup request. ind. It is a figure which shows the content of (radio bearer setup req.ind.). A BCAD BEARER SETUP resp. Sent from the BCAF to the TACAF to notify the radio bearer setup completion. conf. It is a figure which shows the content of (Radio bearer setup resp.conf.). HANDOVER CONNECTION SETUP req. Used for notification of handover initialization. ind. (Handover connection setup req.ind.) Is a diagram for explaining. , BCF is HANDOVER CONNECTION SETUP req. ind. (HANDOVER CONNECTION SETUP resp.) To be transmitted for confirmation of (handover connection setup req.ind.). conf. It is a figure which shows the content of (handover connection setup resp.conf.). BEARER SETUP req. That TACFa sends to TACFv to set up an access bearer. ind. It is a figure which shows the content of (bearer setup req.ind.). BEARER SETUP req. That TACF sends to BCF. ind. It is a figure which shows the content of (bearer setup req.ind.). BCF sends the BEARER SETUP req. ind. (BEARER SETUP resp.) To be transmitted for confirmation of (bearer setup req.ind.). conf. It is a figure which shows the content of (bearer setup resp.conf.). BEARER & RADIO BEARER SETUP resp. conf. It is a figure which shows the content of (bearer and radio | wireless bearer setup resp.conf.). The BCFr sends a BEARER & RADIO BEARER SETUP resp. To notify the TACF of the completion of the radio bearer setup and the bearer setup completion between the BCFr and the BCF. conf. It is a figure which shows the content of (bearer and radio | wireless bearer setup resp.conf.). RADIO BEARER SETUP REQUEST req. To be transmitted for notification of a radio bearer setup request between the mobile terminal and the BCFr under the control of the base TACF by the base TACF. ind. It is a figure which shows the content of (Radio bearer setup request req.ind.). HANDOVER BRANCH ADDITION req. Used for notification of initialization of handover. ind. It is a figure which shows the content of (handover branch addition req.ind.). RADIO BEARER SETUP req. Sent from TACAF to BCAF. ind. It is a figure which shows the content of (radio bearer setup req.ind.). A BCAD BEARER SETUP resp. Sent from the BCAF to the TACAF to notify the radio bearer setup completion. conf. It is a figure which shows the content of (Radio bearer setup resp.conf.). A BEARER SETUP resp. Sent from the TACFa to the TACFv to guarantee access bearer establishment. conf. It is a figure which shows the content of (bearer setup resp.conf.). HANDOVER BRANCH DELETION req. ind. It is a figure explaining the content of (handover branch deletion req.ind.). TACAF responds to TACF with HANDOVER BRANCH DELETION req. ind. (HANDOVER BRANCH DELETION resp.) To be transmitted for confirmation of (handover branch deletion req.ind.) conf. It is a figure which shows the content of (handover branch deletion resp.conf.). BEARER RELEASE req. That TACFa sends to TACFv to release the access bearer. ind. It is a figure which shows the content of (bearer release req.ind.). INTRA BCFr HANDOVER BRANCH DELETION req. Which TACF sends to BCFr for request to release one or more hardware radio channels. ind. It is a figure which shows the content of (own station BCFr handover branch deletion req.ind.). An INTRA BCFr HANDOVER BRANCH DELETION resp. That the BCFr sends to the TACF to announce the release of one or more hardware radio channels. conf. It is a figure which shows the content of (own station BCFr handover branch deletion resp.conf.). TACFv is BEARER RELEASE req. ind. (BEARER RELEASE resp.) To be transmitted for confirmation of (bearer release req.ind.). conf. It is a figure which shows the content of (bearer release resp.conf.). TACA sends TACAF to TACF HANDOVER BRANCH DELETION req. ind. It is a figure which shows the content of (handover branch deletion req.ind.). TACAF responds to TACF with HANDOVER BRANCH DELETION req. ind. (HANDOVER BRANCH DELETION resp.) To be transmitted for confirmation of (handover branch deletion req.ind.) conf. It is a figure which shows the content of (handover branch deletion resp.conf.). RADIO BEARER RELEASE req. Sent from TACAF to BCAF for request to release radio bearer. ind. It is a figure which shows the content of (Radio bearer release req.ind.). A BCAD BEARER RELEASE resp. Sent from the BCAF to the TACAF to notify the radio bearer release completion. conf. It is a figure which shows the content of (Radio bearer release resp.conf.). The TACF sends HANDOVER CONNECTION RELEASE req. To send the indicated bearer in the diversity handover state to the BCF. ind. It is a figure which shows the content of (handover connection release req.ind.). When the BCF is connected to the TACF, the HANDOVER CONNECTION RELEASE req. ind. (HANDOVER CONNECTION RELEASE resp. To be transmitted for confirmation of (handover connection release req.ind.)) conf. It is a figure which shows the content of (handover connection release resp.conf.). BEARER RELEASE req. That TACFa sends to TACFv to release the access bearer. ind. It is a figure which shows the content of (bearer release req.ind.). BEARER RELEASE req. Sent by the TACF to the BCF for a bearer release request. ind. It is a figure which shows the content of (bearer release req.ind.). BCF sends BEARER RELEASE req. ind. (BEARER RELEASE resp.) To be transmitted for confirmation of (bearer release req.ind.). conf. It is a figure which shows the content of (bearer release resp.conf.). A BEARER & RADIO BEARER RELEASE req. That is sent to the BCFr for a request to release the bear between the BCF and the BCFr and a request to release the radio bearer. ind. It is a figure which shows the content of (bearer and radio | wireless bearer release req.ind.). BEARr & RADIO BEARER RELEASE resp. BCFr transmits to TACF to notify bearer and radio bearer release completion. conf. It is a figure which shows the content of (bearer and radio | wireless bearer release resp.conf.). TACFv is in the BEARER RELEASE req. ind. (BEARER RELEASE resp.) To be transmitted for confirmation of (bearer release req.ind.). It is a figure which shows the content of conf (bearer release resp.conf.). BEARER SETUP req. That TACFa sends to TACFv to set up an access bearer. ind. It is a figure which shows the content of (bearer setup req.ind.). FIG. 6 is a diagram showing the contents transmitted by BCFr to notify TACF of completion of setup of one or more hardware radio channels. The BCFr transmits to the TACF to notify the approval of the handover branch switching request. INTRA BCFr HANDOVER BRANCH REPLACEEMENT PROCEEDING req. ind. It is a figure which shows the content of (local station BCFr handover branch switching procedure req.ind.). RADIO BEARER SETUP REQUEST req. That is transmitted for a setup request between the mobile terminal and the BCFr under the control of the base TACF by the base TACF to the anchor TACFa. ind. It is a figure which shows the content of (Radio bearer setup request req.ind.). NON-SOFT HANDOVER EXECUTION req. That TACF sends to TACAF to initialize non-soft handover execution. ind. FIG. RADIO BEARER SETUP req. That TACAF sends to BCAF for a radio bearer setup request. ind. It is a figure which shows the content of (radio bearer setup req.ind.). A BCAD BEARER SETUP resp. Sent from the BCAF to the TACAF to notify the radio bearer setup completion. conf. It is a figure which shows the content of (Radio bearer setup resp.conf.). RADIO BEARER RELEASE req. Sent from TACAF to BCAF for request to release radio bearer. ind. It is a figure which shows the content of (Radio bearer release req.ind.). A BCAD BEARER RELEASE resp. Sent from the BCAF to the TACAF to notify the radio bearer release completion. conf. FIG. The BEARER SETUP resp. TACFa transmits to the TACFv to confirm the establishment of the access bearer. conf. It is a figure which shows the content of (bearer setup resp.conf.). HANDOVER CONNECTION SETUP req. Sent by TACCa to BCFa for notification of handover initialization. ind. FIG. The BCF sends the HANDOVER CONNECTION SETUP req. ind. (HANDOVER CONNECTION SETUP rep. To send for confirmation of (handover connection setup req.ind.). conf. It is a figure which shows the content of (handover connection setup resp.conf.). BEARER SETUP req. That TACFa sends to TACFv to set up a handover link. ind. It is a figure which shows the content of (bearer setup req.ind.). A BEARER SETUP req. That the TACF sends to the BCF to request a new handover link on the network side. ind. FIG. The BCF sends the SETUP req. ind. (BEARER SETUP resp.) To be transmitted for confirmation of (bearer setup req.ind.). conf. It is a figure which shows the content of (bearer setup resp.conf.). BEARER & RADIO BEARER SETUP req. That TACF sends to BCFr to request bearer setup and radio bearer setup between BCF and BCFr. ind. FIG. RADIO BEARER SETUP PROCEEDING req. Sent by the BCFr to notify the TACF of the approval of the access radio link setup and the start of the access radio link setup at the BCFr. ind. It is a figure which shows the content of (radio bearer setup procedure req.ind.). RADIO BEARER SETUP REQUEST req. ind. FIG. NON-SOFT HANDOVER EXECUTION req. That TACF sends to TACAF to initialize non-soft handover execution. ind. FIG. RADIO BEARER SETUP req. That TACAF sends to BCAF to request setup of an access radio link. ind. It is a figure which shows the content of (radio bearer setup req.ind.). A BCAD BEARER SETUP resp. Sent by BCAF to notify TACAF that the access radio link setup is complete. conf. It is a figure which shows the content of (Radio bearer setup resp.conf.). RADIO BEARER RELEASE req. Sent from TACAF to BCAF for request to release access radio link. ind. It is a figure which shows the content of (Radio bearer release req.ind.). The BCAF transmits a RADIO BEARER RELEASE resp. To notify the TACAF that the access radio link has been released. conf. It is a figure which shows the content of (Radio bearer release resp.conf.). BEARr & RADIO BEARER SETUP resp. Sent to TACF for notification of completion of access radio link setup and for notification of completion of link setup between BCFr and BCF. conf. FIG. The BEARER SETUP resp. TACFa transmits to the TACFv to confirm the establishment of the handover link. conf. It is a figure which shows the content of (bearer setup resp.conf.). HANDOVER CONNECTION RELEASE req. That TACF sends to delete the designated handover link to BCFA. ind. It is a figure which shows the content of (handover connection release req.ind.) BCF sends HANDOVER CONNECTION RELEASE req. To TACF. ind. (HANDOVER CONNECTION RELEASE resp. To be transmitted for confirmation of (handover connection release req.ind.)) conf. It is a figure which shows the content of (handover connection release req.ind.). BEARER RELEASE req. That TACFa transmits to TACFv to release the handover link on the network side. ind. It is a figure which shows the content of (bearer release req.ind.). BEARER RELEASE req. Sent by the TACF to the BCF for a handover link release request on the network side. ind. It is a figure which shows the content of (bearer release req.ind.). BCF sends BEARER RELEASE req. ind. (BEARER RELEASE resp.) To be transmitted for confirmation of (bearer release req.ind.). conf. It is a figure which shows the content of (bearer release resp.conf.). The BEARER & RADIO BEARER RELEASE req. Is sent to the BCFr for an access link release request or a handover link release request between the BCF and the BCFr and a handover link release request between the BCAF and the BCF. ind. FIG. A BEARr & RADIO BEARER RELEASE resp. Sent by the BCFr to notify the TACF that the access link has been released or the handover link has been released. conf. It is a figure which shows the content of (Bearer and radio release req.ind.). TACFv is in response to TACFa, confirm BEARER RELEASE req. ind. (BEARER RELEASE resp.) To be transmitted for confirmation of (bearer release req.ind.). conf. It is a figure which shows the content of (bearer release resp.conf.). HANDOVER CONNECTION SETUP req. That TACFA sends to BCFa for handover initialization. ind. FIG. BCF responds to TACF with HANDOVER CONNECTION SETUP req. ind. (HANDOVER CONNECTION SETUP rep. To send for confirmation of (handover connection setup req.ind.). conf. It is a figure which shows the content of (handover connection setup resp.conf.). TACFa is ACCH. BEARER SETUP req. ind. It is a figure which shows the content of (bearer setup req.ind.). A BEARER SETUP req. That the TACF sends to the BCF to request bearer setup for the ACCH. ind. FIG. BCF responds to TACF with BEARER SETUP req. ind. (BEARER SETUP resp.) To be transmitted for confirmation of (bearer setup req.ind.). conf. It is a figure which shows the content of (bearer setup resp.conf.). BEARER & RADIO BEARER SETUP req. ind. It is a figure explaining the content of (TACF-> BCFr). RADIO BEARER SETUP PROCEEDING req. ind. It is a figure explaining the content of (BCFr-> TACF). RADIO BEARER SETUP REQUEST req. ind. FIG. RADIO BEARER SETUP req. ind. It is a figure explaining the content of (TACF-> TACAF). RADIO BEARER SETUP req. ind. It is a figure explaining the content of (TACF-> BCAF). The BCAD transmits a RADIO BEARER SETUP resp. To notify TACAF that the radio bearer has been set up for ACCH. conf. It is a figure which shows the content of (Radio bearer setup resp.conf.). RADIO BEARER RELEASE req. Sent by TACAF for BCA release request to BCA. ind. It is a figure which shows the content of (Radio bearer release req.ind.). The BCAD BEARER RELEASE resp. Sent from the BCAF to the TACAF to notify the radio bearer release completion. conf. It is a figure which shows the content of (Radio bearer release resp.conf.). The HANDOVER CONNECTION RELEASE req. That TACF sends to delete the indicated bearer that is in soft handover to BCFA. ind. It is a figure which shows the content of (handover connection release req.ind.). BCF sends HANDOVER CONNECTION RELEASE req. To TACF. ind. (HANDOVER CONNECTION RELEASE resp. To be transmitted for confirmation of (handover connection release req.ind.)) conf. It is a figure which shows the content of (handover connection release resp.conf.). BEARER RELEASE req. That TACFa sends to TACFv to release the access bearer. ind. It is a figure which shows the content of (bearer release req.ind.). BEARER RELEASE req. Sent by the TACF to the BCF for a bearer release request. ind. It is a figure which shows the content of (bearer release req.ind.). BCF sends BEARER RELEASE req. ind. (BEARER RELEASE resp.) To be transmitted for confirmation of (bearer release req.ind.). conf. It is a figure which shows the content of (bearer release resp.conf.). BEARr & RADIO BEARER RELEASE req. That TACF sends to BCFr for a bearer release request between BCFr and BCF, and a radio bearer release request. ind. It is a figure which shows the content of (bearer and radio | wireless bearer release req.ind.). The BCFr transmits to the TACAF the bearer release completion and the radio bearer release completion notification, and the BEARER & RADIO BEARER RELEASE resp. conf. FIG. TACFv is BEARER RELEASE req. ind. (BEARER RELEASE resp.) To be transmitted for confirmation of (bearer release req.ind.). conf. It is a figure which shows the content of (bearer release resp.conf.). BCFr transmits to TACF for a code switching request. ind. FIG. Code switching req. Transmitted from the base TACF to TACCa for code switching. ind. FIG. The code switching req. Sent by the TACF to TACAF for code switching. ind. FIG. Code switching req. Transmitted by TACAF to BCAF. ind. FIG. Code switching resp. Sent by BCAF to notify TACAF of the completion of code switching. conf. FIG. TACAF performs code switching req. ind. Code resp. conf. FIG. TACFa performs code switching req. ind. Code resp. conf. FIG. TACF switches code req. ind. Code resp. conf. FIG. CELL CONDITION REPORT req. Which MRRC periodically transmits to RRC to notify each radio state of the handover branch. ind. It is a figure which shows the content of (cell state report req.ind.). Transmission power value setting for notification of transmission power value transmitted by TACFA to TACFv req. ind. FIG. Transmission power value setting that TACF transmits to BCFr for notification of transmission power value req. ind. FIG. It is a figure for demonstrating LAI update IF. It is a figure for demonstrating Terminal location update IF (SACF-visited SCF). It is a figure for demonstrating Terminal location update IF (MCF-SACF). It is a figure for demonstrating authentication information IF. It is a figure for demonstrating Authentication challenge IF (LRCF-TACF & LRCF-SACF). It is a figure for demonstrating Authentication challenge IF (TACF-TACAF & SACF-MCF). Authentication req. ind. And Authentication resp. conf. It is a figure for demonstrating. It is a figure for demonstrating Start ciphering IF (TACF-TACAF & LRCF-TACF). It is a figure for demonstrating Start ciphering IF (LRCF-SACF). It is a figure for demonstrating TMUI assignment IF (TACF-TACAF). It is a figure for demonstrating TMUI query IF. It is a figure for demonstrating TMUI modify IF. It is a figure for demonstrating TMUI assignment IF (LRCF-TACF). It is a figure for demonstrating TMUI assignment IF (LRCF-SACF). It is a figure for demonstrating TMUI assignment IF (SACF-MCF). IMUI retryval req. ind. And IMUI retry resp. conf. It is a figure for demonstrating (LRCF-LRDF). IMUI retryval req. ind. And IMUI retry resp. conf. It is a figure for demonstrating (SACF-LRCF). IMUI retryval req. ind. And IMUI retry resp. conf. It is a figure for demonstrating (MCF-SACF). IMUI retryval req. ind. And IMUI retry resp. conf. It is a figure for demonstrating (TACF-LRCF). IMUI retryval req. ind. And IMUI retry resp. conf. It is a figure for demonstrating (TACAF-TACF). It is a figure for demonstrating SAPI about a layer 3 matching sublayer. It is a figure for demonstrating W bit about a layer 3 matching sublayer. It is a figure for demonstrating the code | symbol type | mold indicator about a layer 3 matching sublayer. It is a figure for demonstrating the reservation about a layer 3 matching sublayer. It is a figure which shows the list | wrist of a protocol data unit (PDU). It is a figure which shows the list | wrist of a protocol data unit (PDU). It is explanatory drawing of a CRC bit. It is explanatory drawing of a W bit. It is explanatory drawing of BCCH identification information. It is explanatory drawing of uplink interference electric power information. It is explanatory drawing of the identifier for identifying the call or mobile station with which transmission information relates. It is explanatory drawing of the identifier for identifying whether the information mounted in MAC SDU is user information or control information. It is explanatory drawing of the identifier for identifying whether the information mounted in MAC SDU is a base station side termination node. It is explanatory drawing of the Mo S bit for identifying the mode of FACH-S. It is explanatory drawing of the CRC bit added per layer 1 frame. It is a figure which shows the list of Message Type (message type) of CC message. It is a figure which shows each information element which comprises an ALERTING message. It is a figure which shows each information element which comprises an ALERTING message. It is a figure which shows each information element which comprises an ALERTING message. It is a figure which shows each information element which comprises a CALL PROCEEDING message. It is a figure which shows each information element which comprises a CALL PROCEEDING message. It is a figure which shows each information element which comprises a CALL PROCEEDING message. It is a figure which shows each information element which comprises a CONNECT message. It is a figure which shows each information element which comprises a CONNECT message. It is a figure which shows each information element which comprises a CONNECT message. It is a figure which shows each information element which comprises a CONNECT message. It is a figure which shows each information element which comprises a CONNECT message. It is a figure which shows each information element which comprises a CONNECT ACKNOWLEDGE message. It is a figure which shows each information element which comprises a PROGRESS message. It is a figure which shows each information element which comprises a PROGRESS message. It is a figure which shows each information element which comprises a PROGRESS message. It is a figure which shows each information element which comprises a SETUP message. It is a figure which shows each information element which comprises a SETUP message. It is a figure which shows each information element which comprises a SETUP message. It is a figure which shows each information element which comprises a SETUP message. It is a figure which shows each information element which comprises a SETUP message. It is a figure which shows each information element which comprises a SETUP message. It is a figure which shows each information element which comprises a SETUP message. It is a figure which shows each information element which comprises a SETUP message. It is a figure which shows each information element which comprises a SETUP message. It is a figure which shows each information element which comprises a RELEASE message. It is a figure which shows each information element which comprises a RELEASE COMPLETE message. It is a figure which shows each information element which comprises an INFORMATION message. It is a figure which shows MM-T message Type (type). It is a figure which shows the structure of MOBILITY FACILITY. It is a figure which shows the list of the information elements in Terminal Location Registration (terminal location registration). It is a figure which shows the list of the information elements in Terminal Location Registration (terminal location registration). It is a figure which shows the list of the information element in case a component classification is Return Result (return result) (when position registration is performed normally). It is a figure which shows the list of the information elements when the component type is Return Error (return error) (when a sub-normality such as an application error occurs). FIG. 6 is a diagram showing a list of information elements when the component type is “Reject” (when quasi-normality occurs due to information element mismatch or the like). It is a figure which shows the list of the information elements in TMUI Assignment (TMUI assignment). It is a figure which shows the list of the information element in case a component classification is Return Result. It is a figure which shows the list of the information element in case a component classification is Return Error. It is a figure which shows the list of the information element in case a component classification is Reject. It is a figure which shows the list of the information elements in Authentication Challenge (authentication challenge). It is a figure which shows the list of the information elements in Authentication Challenge (authentication challenge). It is a figure which shows the list of the information element in case a component classification is Return Result (when an authentication request is performed normally). It is a figure which shows the list of the information element in case a component classification is Return Error. It is a figure which shows the list of the information element in case a component classification is Reject. It is a figure which shows the list of the information elements in Start Ciphering (confidential start). It is a figure which shows the list of the information elements in case a component classification is Return Result (when a secrecy start is performed normally). It is a figure which shows the list of the information element in case a component classification is Return Error. It is a figure which shows the list of the information element in case a component classification is Reject. It is a figure which shows the list of the information elements in IMUI retry (IMUI retrieval). It is a figure which shows the list of the information elements in case a component classification is Return Result (when IMUI retryval is performed normally). It is a figure which shows the list of the information element in case a component classification is Return Error. It is a figure which shows the list of the information element in case a component classification is Reject. It is a figure which shows the list of RBC messages. It is a figure which shows the classification | category (MESSAGE TYPE) of a RBC message. It is a figure explaining the information length etc. of a RADIO BEARER SETUP message. It is a figure explaining the information length etc. of a RADIO BEARER RELEASE message. It is a figure explaining the information length etc. of a RADIO BEARER RELEASE COMPLETE message. It is a figure explaining the information length etc. of a HANDOVER COMMAND message. It is a figure explaining the information length etc. of a HANDOVER RESPONSE message. It is a figure which shows the list of RRC messages. It is a figure explaining the information length etc. of a RADIO RESOURCE FACILITY message. It is a figure which shows the list of RRC message names. It is a figure which shows a response | compatibility with a message name and an information flow name. It is a figure explaining the information length etc. of a TERMINAL ASSOCIATION SETUP message. It is a figure explaining the information length etc. of a TERMINAL ASSOCIATION CONNECT message. It is a figure explaining the information length etc. of a TERMINAL ASSOCIATION CONNECT message. It is a figure explaining the information length etc. of a TERMINAL ASSOCIATION CONNECT message. It is a figure explaining the information length etc. of a TERMINAL ASSOCIATION CONNECT message. It is a figure explaining the information length etc. of a TERMINAL ASSOCIATION CONNECT message. It is a figure explaining the information length etc. of a RACH message. It is a figure explaining the information length etc. of a FACH message. It is a figure explaining the information length etc. of a FACH message. It is a figure explaining the information length etc. of a BCCH message. It is a figure explaining the information length etc. of a BCCH message. It is a figure explaining the information length etc. of a TERMINAL ASSOCIATION CONNECT message. It is a figure for demonstrating Protocol discriminator (protocol identifier). It is a figure for demonstrating Protocol discriminator (protocol identifier). It is a figure which shows the format and coding of a message consistency operation instruction display. It is a figure which shows the format and coding of a message consistency operation instruction display. It is a figure which shows the format and coding of a message consistency operation instruction display. FIG. 4 is a diagram illustrating coding of variable length information elements in an FPLMTS environment. FIG. 4 is a diagram illustrating coding of variable length information elements in an FPLMTS environment. FIG. 4 is a diagram illustrating coding of variable length information elements in an FPLMTS environment. FIG. 4 is a diagram illustrating coding of variable length information elements in an FPLMTS environment. It is a figure for demonstrating a broadband fixed shift information element. It is a figure for demonstrating a broadband temporary shift information element. It is a figure for demonstrating an AAL parameter information element. It is a figure for demonstrating an AAL parameter information element. It is a figure for demonstrating an AAL parameter information element. It is a figure for demonstrating an AAL parameter information element. It is a figure for demonstrating an AAL parameter information element. It is a figure for demonstrating an ATM traffic descriptor information element. It is a figure for demonstrating a broadband transmission capability information element. It is a figure for demonstrating a broadband transmission capability information element. It is a figure for demonstrating a broadband high-order layer information information element. It is a figure for demonstrating a broadband high-order layer information information element. It is a figure for demonstrating a broadband low-order layer information information element. It is a figure for demonstrating a broadband low-order layer information information element. It is a figure for demonstrating a broadband low-order layer information information element. It is a figure for demonstrating a broadband low-order layer information information element. It is a figure for demonstrating a broadband low-order layer information information element. It is a figure for demonstrating a called number information element. It is a figure for demonstrating a called number information element. It is a figure for demonstrating a destination subaddress information element. It is a figure for demonstrating a destination subaddress information element. It is a figure for demonstrating a calling number information element. It is a figure for demonstrating a calling number information element. It is a figure for demonstrating a calling number information element. It is a figure for demonstrating a calling subaddress information element. It is a figure for demonstrating a calling subaddress information element. It is a figure for demonstrating a connection identifier information element. It is a figure for demonstrating an end-end relay delay information element. It is a figure for demonstrating a quality of service (QOS) parameter information element. It is a figure for demonstrating a broadband repetition identifier information element. It is a figure for demonstrating a relay network selection information element. It is a figure for demonstrating an OAM traffic descriptor information element. It is a figure for demonstrating an OAM traffic descriptor information element. It is a figure which shows the list of an MM-T specific information element. It is a figure explaining the parameter of outgoing / incoming candidate zone information. It is a figure explaining the parameter of zone information during communication. It is a figure explaining the parameter of DHO addition zone information. It is a figure explaining the parameter of DHO deletion zone information. It is a figure explaining the parameter of HHO execution zone information. It is a figure explaining the parameter of outer loop information. It is a figure explaining the parameter of quality degradation notification information. It is a figure which shows the format of Message type. It is a figure which shows the format of Message type. It is a figure which shows a TAC message intrinsic | native parameter name list. It is a figure for demonstrating a TERMINAL ASSOCIATION SETUP message specific parameter information element. It is a figure for demonstrating the PAGING RESPONSE message specific parameter information element. It is a figure for demonstrating a TERMINAL ASSOCIATION RELEASE message specific parameter information element. It is a figure which shows the information element name list of the subfield of a TAC message specific parameter. It is a figure for demonstrating Cause information element. It is a figure for demonstrating a Mobile station type information element. It is a figure for demonstrating a Mobile station type information element. It is a figure for demonstrating a Paged MS ID information element. It is a figure for demonstrating a Paging ID information element. It is a figure which shows the message Type (type) list of BC message. It is a figure which shows BC message classification. It is a figure for demonstrating the information element of a LINK SETUP REQUESTED message. It is a figure for demonstrating the information element of a LINK SETUP message. It is a figure for demonstrating the information element of a LINK SETUP PROCEEDING message. It is a figure for demonstrating the information element of a LINK SETUP RESPONSE message. It is a figure for demonstrating the information element of a LINK FACILITY (MSCNW-> BTS) message. It is a figure for demonstrating the information element of a LINK FACILITY (BTS-> MSCNW) message. It is a figure for demonstrating the information element of a LINK RELEASE message. It is a figure for demonstrating the information element of a LINK RELEASE COMPLETE message. It is a figure which shows the list of the basic information element structure of LINK SETUP, LINK SETUP PROCEEDING, LINK SETUP RESPONSE, and LINK FACILITY. It is a figure which shows the list of the basic information element structure of LINK SETUP, LINK SETUP PROCEEDING, LINK SETUP RESPONSE, and LINK FACILITY. It is a figure which shows the list of the basic information element structure of LINK SETUP, LINK SETUP PROCEEDING, LINK SETUP RESPONSE, and LINK FACILITY. It is a figure which shows the list of the basic information element structure of LINK SETUP, LINK SETUP PROCEEDING, LINK SETUP RESPONSE, and LINK FACILITY. It is a figure which shows the list of the basic information element structure of LINK SETUP, LINK SETUP PROCEEDING, LINK SETUP RESPONSE, and LINK FACILITY. It is a figure which shows the list of the basic information element structure of LINK SETUP, LINK SETUP PROCEEDING, LINK SETUP RESPONSE, and LINK FACILITY. It is a figure which shows the list of the basic information element structure of LINK SETUP, LINK SETUP PROCEEDING, LINK SETUP RESPONSE, and LINK FACILITY. It is a figure which shows the message type list of a BSM message. It is a figure for demonstrating the information element of a PAGING message. It is a figure shown about the information length etc. of a LINK ID basic information element. It is a figure shown about the information length etc. of a frequency non-designated type TCH setting request information element. It is a figure shown about the information length etc. of a frequency non-designated type TCH setting request information element. It is a figure shown about the information length etc. of a frequency non-designated type TCH setting request information element. It is a figure shown about the information length etc. of a DHO addition request information element. It is a figure shown about the information length etc. of an INTRA BS DHO addition request | requirement information element. It is a figure shown about the information length etc. of an ACCH setting request information element. It is a figure shown about the information length etc. of a frequency non-designated type TCH setting reception information element. It is a figure shown about the information length etc. of a frequency non-designated type TCH setting reception information element. It is a figure shown about the information length etc. of a frequency non-designated type TCH setting reception information element. It is a figure shown about the information length etc. of a frequency non-designated type TCH setting response information element. It is a figure shown about the information length etc. of a frequency non-designated type TCH setting response information element. It is a figure shown about the information length etc. of a frequency non-designated type TCH setting response information element. It is a figure shown about the information length etc. of a DHO addition setting response information element. It is a figure shown about the information length etc. of an INTRA BS DHO addition setting response information element. It is a figure shown about the information length etc. of an ACCH setting response information element. It is a figure shown about the information length etc. of an INTRA BS DHO addition setting request information element. It is a figure shown about the information length etc. of an INTRA BS DHO deletion setting request information element. It is a figure shown about the information length etc. of the INTRA BS HHO setting request information element. It is a figure shown about the information length etc. of an ACCH release request information element. It is a figure shown about the information length etc. of a frequency non-designation type | mold switching setting request information element. It is a figure shown about the information length etc. of a frequency non-designation type | mold switching setting request information element. It is a figure shown about the information length etc. of a setting completion notification information element. It is a figure shown about the information length etc. of an INTRA BS HHO deletion setting response information element. It is a figure shown about the information length etc. of an INTRA BS HHO addition setting response information element. It is a figure shown about the information length etc. of an ACCH release response information element. It is a figure shown about the information length etc. of a frequency designation | designated type | mold switch setting response information element. It is a figure shown about the information length etc. of a frequency designation | designated type | mold switch setting request information element. It is a figure shown about the information length etc. of a frequency non-designated type | mold switch setting reception information element. It is a figure shown about the information length etc. of a frequency non-designation type | mold switching setting response information element. It is a figure shown about the information length etc. of a code switching request information element. It is a figure shown about the information length etc. of a TCH release request information element. It is a figure shown about the information length etc. of a SDCCH release request information element. It is a figure shown about the information length etc. of CAUSE. It is a figure shown about the information length etc. of a SDCCH setting request information element. It is a figure shown about the information length etc. of a LAI setting request information element. It is explanatory drawing about the encoding of the protocol identifier for identifying a BC message. It is a figure for demonstrating encoding of the message type for identifying the function of BC message. It is a figure for demonstrating the encoding of the protocol identifier for identifying a BSM message. It is a figure for demonstrating encoding of the message type for identifying the function of a BSM message. It is a figure which shows the number classification set after the octet 4. It is a figure which shows the number of octets (number length) of the number set after the octet 4. It is explanatory drawing of an example of the confidential execution state in a mobile communication system. FIG. 75 is an explanatory diagram of a problem in the mobile communication system shown in FIG. 751. It is a figure which shows schematic structure of the mobile communication system in the setting of a secrecy start. It is a figure explaining operation | movement of the mobile communication system in the setting of a secrecy start. Normal operation between the mobile station MS and the network NW when configured to notify the mobile device from the network of the start of concealment and then conceal both the transmission signal and the received signal after the notification of the start of concealment It is a concealment process sequence diagram at the time. FIG. 76 is a diagram for describing a problem that occurs in the concealment processing sequence illustrated in FIG. 755. (3.1) It is a secrecy execution sequence diagram at the time of normal operation in the chapter control method. (3.1) It is a figure explaining the effect in the control method of a chapter. It is a general | schematic sequence diagram in the case of performing a concealment process using the intrinsic | native concealment system in a mobile communication system. (3.2) It is a sequence diagram for demonstrating the outline | summary operation | movement in the control method of a chapter. (3.2) It is a sequence diagram (the 1) for demonstrating the detailed operation | movement in the control method of a chapter. (3.2) It is the sequence diagram (the 1) for demonstrating the detailed operation | movement in the control method of a chapter. (3.2) It is a sequence diagram (the 2) for demonstrating the detailed operation | movement in the control method of a chapter. It is a figure which shows the conventional operation | movement in case the access link is set with respect to the said mobile station, when the mobile station is located in the zone which can communicate by the diversity handover in a base station. It is a figure which shows the conventional operation | movement in case the setting of the access link with respect to the said mobile station is performed when the mobile station is located in the zone which can communicate by the diversity handover between base stations. It is a sequence diagram which shows a series of procedures performed between a mobile station and the network side in order to set an access link. It is a sequence diagram which shows a series of procedures performed in order to transfer to the diversity handover in a base station. It is a sequence diagram which shows a series of procedures performed in order to transfer to the diversity handover between base stations. It is a figure which shows a mode that a diversity handover is started simultaneously with an access link being set with respect to a mobile station in the system which concerns on this invention. FIG. 5 is a sequence diagram showing an operation when an access link is set for a mobile station when the mobile station is in a state where diversity handover within a base station is possible in the system according to the present invention. FIG. 6 is a sequence diagram showing an operation when an access link is set for a mobile station when the mobile station is in a state where diversity handover between base stations is possible in the system according to the present invention. It is a figure which shows an example in case the shift to a diversity handover is performed continuously after branch switching is performed under the prior art. It is a sequence diagram which shows a series of procedures performed between a mobile station and the network side in order to perform branch switching. FIG. 77 is a sequence diagram showing operations performed in the system according to the present invention when the mobile station moves to the diversity handover zone as shown in FIG. 771. When a mobile station capable of communication corresponding to a plurality of calls is communicating, when another new call occurs in the mobile station, the branch configuration and frequency band of the system according to the present invention are changed. It is a figure which shows an example of control. 774 is a sequence diagram illustrating an operation of the present system for performing the control illustrated in FIG. 774; FIG. When a mobile station capable of communication corresponding to a plurality of calls is communicating, when another new call occurs in the mobile station, the branch configuration and frequency band of the system according to the present invention are changed. It is a figure which shows another example of control. When a mobile station capable of communication corresponding to a plurality of calls is communicating, when another new call occurs in the mobile station, the branch configuration and frequency band of the system according to the present invention are changed. It is a figure which shows another example of control. FIG. 7B is a sequence diagram showing the operation of this system for performing control as exemplified in FIG. 776. FIG. 7B is a sequence diagram showing the operation of this system for performing control as exemplified in FIG. 776. FIG. 7B is a sequence diagram showing the operation of this system for performing control as exemplified in FIG. 777; FIG. 7B is a sequence diagram showing the operation of this system for performing control as exemplified in FIG. 777; The figure shows a specific application example of the present control method showing an example of control performed in the system according to the present invention when an opportunity for handover occurs in a mobile station performing communication of a plurality of calls. FIG. 10 shows another example of control performed in the system according to the present invention when an opportunity for handover occurs in a mobile station that performs communication of a plurality of calls. FIG. 780 is a sequence diagram illustrating an operation of the present system for implementing the application example of FIG. 780; FIG. FIG. 78 is a sequence diagram illustrating an operation of the present system for implementing the application example of FIG. 781. It is a figure which shows another example of the control performed in the system which concerns on this invention, when the opportunity of a handover arises in the mobile station which is performing communication of multiple calls. FIG. 784 is a sequence diagram illustrating an operation of the present system for implementing the application example of FIG. 784. FIG. 10 is a sequence diagram showing the operation of the present system when an access link is established for a mobile station when the mobile station is located in a zone where communication by diversity handover between base stations is possible. 787 is a flowchart showing a mobile station control flow in the operation shown in FIG. 786; FIG. 10 is a sequence diagram showing an operation in a conventional system when an access link is established for a mobile station when the mobile station is located in a zone where communication by diversity handover between base stations is possible. 789 is a flowchart showing a control flow of the mobile station in the operation shown in FIG. 788. It is a figure explaining the opportunity which ACCH switching generate | occur | produces in the system which concerns on this invention. It is a sequence diagram which shows the operation example of ACCH switching which does not switch a wired access link. It is a figure explaining the method of the uplink transmission power control of the mobile station in the system which concerns on this invention. (3.10) It is a figure explaining the operation | movement of the reassignment of the code resource in a chapter. It is a figure explaining the operation | movement and effect of the reassignment of the code resource in a chapter (3.10).

Explanation of symbols

10 ... Mobile equipment

Claims (40)

In a base station controller that communicates with a mobile device capable of diversity combining under the control of an exchange station via a plurality of radio base stations,
A base station control apparatus comprising: a concealment processing unit that performs concealment processing on transmission information to be transmitted to the mobile station received from the exchange and generates concealment transmission information. In a base station controller that communicates with a mobile device capable of diversity combining under the control of an exchange station via a plurality of radio base stations,
Retransmission control information adding means for adding retransmission control information to the confidential transmission information subjected to the confidential processing in the exchange;
Distribution means for distributing the confidential transmission information to which the retransmission control information is added to the plurality of radio base stations;
A base station control device comprising: In an exchange that communicates with a mobile device capable of diversity combining, a plurality of radio base stations, and a base station controller according to claim 2,
An exchange comprising: a concealment processing means for performing concealment processing on transmission information to be transmitted to the mobile device to generate the concealment transmission information. In a mobile communication system comprising a mobile device capable of diversity combining, a plurality of radio base stations, and a base station controller that performs communication via the radio base station under the control of an exchange,
When transmitting information from the exchange side to the mobile station side, the base station controller distributes the information to the plurality of radio base stations, and performs a concealment process on the information before distributing the information. A mobile communication system characterized by being applied. In a mobile communication system comprising a mobile device capable of diversity combining, a plurality of radio base stations, and a base station controller that performs communication via the radio base station under the control of an exchange,
When transmitting information from the switching station side to the mobile station side, the switching station performs a concealment process on the information before distributing the information to the base station controller. A mobile communication system. In a mobile communication system comprising a mobile device capable of diversity combining, a plurality of radio base stations, and a base station controller that performs communication via the radio base station under the control of an exchange,
A mobile communication system comprising a second layer concealment processing means for performing concealment processing on information handled only in a layer corresponding to a second layer or higher layer in the OSI reference model. In a mobile communication system comprising a mobile device capable of diversity combining, a plurality of radio base stations, and a base station controller that performs communication via the radio base station under the control of an exchange,
Third layer concealment processing means for performing concealment processing on information handled only in layers corresponding to the third layer and higher layers in the OSI reference model;
Second layer mutual notification means for performing mutual notification of confidentiality start in a layer corresponding to the second layer in the OSI reference model;
A mobile communication system comprising: In a mobile communication system comprising a mobile device capable of diversity combining, a plurality of radio base stations, and a base station controller that performs communication via the radio base station under the control of an exchange,
Third layer concealment processing means for performing concealment processing on information handled only in layers corresponding to the third layer and higher layers in the OSI reference model;
Retransmission control information adding means for adding retransmission control information to information that has been subjected to concealment processing by the third layer concealment processing means in a layer corresponding to the second layer in the OSI reference model;
Distribution means for distributing the confidential transmission information to which the retransmission control information is added to the plurality of radio base stations;
A mobile communication system comprising: In a control method of a base station controller that performs communication via a plurality of radio base stations with a mobile device capable of diversity combining under the control of an exchange,
A control method for a base station control apparatus, comprising: a concealment processing step for performing concealment processing on transmission information to be transmitted to the mobile station received from the exchange and generating concealment transmission information. In a control method of a base station controller that performs communication via a plurality of radio base stations with a mobile device capable of diversity combining under the control of an exchange,
A retransmission control information adding step of adding retransmission control information to the confidential transmission information subjected to the confidential processing in the exchange;
A delivery step of delivering the confidential transmission information to which the retransmission control information is added to the plurality of radio base stations;
A control method for a base station control apparatus comprising: In a control method of a switching station that performs communication via a mobile station capable of diversity combining, a plurality of radio base stations, and a base station control device according to claim 3,
A switching center control method comprising: a concealment processing step of performing concealment processing on transmission information to be transmitted to the mobile device to generate the concealment transmission information. In a control method of a mobile communication system comprising a mobile device capable of diversity combining, a plurality of radio base stations, and a base station controller that performs communication via the radio base station under the control of an exchange station,
When transmitting information from the exchange side to the mobile station side, the base station controller distributes the information to the plurality of radio base stations, and performs a concealment process on the information before distributing the information. A control method for a mobile communication system, comprising a step. In a control method of a mobile communication system comprising a mobile device capable of diversity combining, a plurality of radio base stations, and a base station controller that performs communication via the radio base station under the control of an exchange station,
When transmitting information from the switching station side to the mobile station side, the switching station performs a concealment process on the information before distributing the information to the base station controller. A method for controlling a mobile communication system. In a control method of a mobile communication system comprising a mobile device capable of diversity combining, a plurality of radio base stations, and a base station controller that performs communication via the radio base station under the control of an exchange station,
A control method for a mobile communication system, comprising: a second layer concealment process step of performing concealment processing on information handled only in a layer corresponding to the second layer or higher layer in the OSI reference model. In a control method of a mobile communication system comprising a mobile device capable of diversity combining, a plurality of radio base stations, and a base station controller that performs communication via the radio base station under the control of an exchange station,
A third layer concealment processing step of performing concealment processing on information handled only in a layer corresponding to a layer corresponding to the third layer or higher in the OSI reference model;
A second layer mutual notification step of performing mutual notification of confidentiality start in a layer corresponding to the second layer in the OSI reference model;
A method for controlling a mobile communication system, comprising: In a control method of a mobile communication system comprising a mobile device capable of diversity combining, a plurality of radio base stations, and a base station controller that performs communication via the radio base station under the control of an exchange station,
A third layer concealment processing step of performing concealment processing on information handled only in a layer corresponding to a layer corresponding to the third layer or higher in the OSI reference model;
A retransmission control information adding step of adding retransmission control information to information subjected to the concealment process by the third layer concealment process step in a layer corresponding to the second layer in the OSI reference model;
A delivery step of delivering the confidential transmission information to which the retransmission control information is added to the plurality of radio base stations;
A method for controlling a mobile communication system, comprising: In a mobile device that communicates with the network via a wireless line,
A decryption processing start timing setting means for setting a decryption processing start timing for starting the decryption processing of the confidential reception signal in correspondence with the confidential processing start timing of the transmission signal in the network independently of the confidential processing start timing of the transmission signal; A mobile device characterized by that. Comprising decryption processing means for performing a decryption process on a confidential reception signal received from the network via the wireless line;
The decryption processing start timing setting means includes a confidentiality request determination means for determining whether or not a reception confidentiality start request has been received from the network;
Decryption processing instruction means for starting the decryption processing means based on the timing of receiving the reception confidentiality start request based on the determination,
The mobile device according to claim 17. In a mobile device that communicates with the network via a wireless line,
A mobile device comprising: a concealment process start timing setting means for setting a concealment process start timing for performing concealment processing on a transmission signal independently of a concealment reception signal decoding process start timing. A transmission concealment start request means for transmitting a transmission concealment start request to the network via the wireless line;
A concealment processing means for generating a concealment transmission signal by performing concealment processing on the transmission signal,
The concealment process start timing setting unit includes a concealment processing instruction unit that starts concealment processing in the concealment processing unit based on the timing at which the transmission concealment start request is transmitted.
The mobile device according to claim 19. In a network side control device that communicates with a mobile device via a wireless line,
Decryption process start timing setting means for setting a decryption process start timing for starting the decryption process of the secret reception signal in correspondence with the secret process start timing of the transmission signal in the mobile unit independently of the secret process start timing of the transmission signal. A network-side control device comprising: Comprising a decryption processing means for performing a decryption process on a confidential reception signal received from the mobile station via the wireless line;
The decryption processing start timing setting means includes a confidentiality request determination means for determining whether or not a reception confidentiality start request has been received from the network;
Decryption processing instruction means for starting the decryption processing means based on the timing of receiving the reception confidentiality start request based on the determination,
The network-side control device according to claim 21, In a network side control device that communicates with a mobile device via a wireless line,
A network-side control device, comprising: a concealment process start timing setting unit configured to set a concealment process start timing for performing concealment processing on a transmission signal independently of a concealment reception signal decoding process start timing. A transmission concealment start request means for transmitting a transmission concealment start request to the mobile device via the wireless line;
A concealment processing means for generating a concealment transmission signal by performing concealment processing on the transmission signal,
The concealment process start timing setting unit includes a concealment processing instruction unit that starts concealment processing in the concealment processing unit based on the timing at which the transmission concealment start request is transmitted.
24. The network side control device according to claim 23. In a mobile communication system that performs communication between a mobile device and a network via a wireless line,
The network includes a concealment start request means for transmitting a concealment start request to the mobile device via the wireless line;
First secret transmission signal generating means for generating a first secret transmission signal by performing concealment processing on a first transmission signal that is a transmission signal from the network to the mobile device after transmission of the secret start request;
First secret transmission signal transmitting means for transmitting the first secret transmission signal to the mobile device;
Response determination means for determining whether or not a concealment start response indicating acceptance of the concealment start request is received from the mobile device;
First decoding processing means for starting decoding of a second secret transmission signal transmitted from the mobile device when the mobile device accepts the confidentiality start request based on the determination of the response determining means,
The mobile device includes request determination means for determining whether or not the concealment start request is received;
Based on the determination of the request determination unit, a concealment start response unit that transmits the concealment start response when accepting the concealment start request;
Second decryption processing means for starting decryption of the first secret transmission signal transmitted by the network when accepting the secret start request;
Second secret transmission signal generating means for generating a second secret transmission signal by performing concealment processing on a second transmission signal that is a transmission signal from the mobile device to the network after transmitting the secret start response;
A second secret transmission signal transmitting means for transmitting the second secret transmission signal to the network;
A mobile communication system. In a control method of a mobile device that communicates with a network via a wireless line,
A decryption process start timing setting step for setting a decryption process start timing for starting the decryption process of the secret reception signal in correspondence with the secrecy process start timing of the transmission signal in the network independently of the secrecy process start timing of the transmission signal. A method for controlling a mobile device, characterized by comprising: Comprising a decryption process step of performing a decryption process on a confidential reception signal received from the network via the wireless line;
The decryption processing start timing setting step includes a concealment request determination step for determining whether or not a reception concealment start request has been received from the network;
A decryption processing instruction step for starting decryption processing in the decryption processing step based on the timing of receiving the reception concealment start request based on the determination,
27. The method of controlling a mobile device according to claim 26. In a control method of a mobile device that communicates with a network via a wireless line,
A mobile device control method comprising: a concealment process start timing setting step for setting a concealment process start timing for performing concealment processing on a transmission signal independently of a concealment reception signal decoding process start timing. A transmission concealment start request step for transmitting a transmission concealment start request to the network via the wireless line;
A concealment processing step of generating a concealment transmission signal by performing concealment processing on the transmission signal,
The concealment process start timing setting step includes a concealment processing instruction step for starting concealment processing in the concealment processing step based on the timing at which the transmission concealment start request is transmitted.
29. A method of controlling a mobile device according to claim 28. In a control method of a network side control device that performs communication with a mobile device via a wireless line,
A decryption process start timing setting step for setting a decryption process start timing for starting the decryption process of the secret reception signal in correspondence with the secrecy process start timing of the transmission signal in the mobile unit independently of the secrecy process start timing of the transmission signal; A control method for a network-side control device, comprising: Comprising a decryption processing step of performing a decryption process on a confidential reception signal received from the mobile station via the wireless line;
The decryption processing start timing setting step includes a concealment request determination step for determining whether or not a reception concealment start request has been received from the network;
A decryption processing instruction step for starting decryption processing in the decryption processing step based on the timing of receiving the reception concealment start request based on the determination,
The control method of the network side control apparatus according to claim 30. In a control method of a network side control device that performs communication with a mobile device via a wireless line,
A control method for a network-side control device, comprising: a concealment process start timing setting step for setting a concealment process start timing for performing concealment processing on a transmission signal independently of a concealment reception signal decoding process start timing. A transmission concealment start request step for transmitting a transmission concealment start request to the mobile device via the wireless line;
A concealment processing step of generating a concealment transmission signal by performing concealment processing on the transmission signal,
The concealment process start timing setting step includes a concealment processing instruction step for starting concealment processing in the concealment processing step based on the timing at which the transmission concealment start request is transmitted.
The control method of the network side control apparatus according to claim 32. In a control method of a mobile communication system that performs communication between a mobile device and a network via a wireless line,
A concealment start request step for transmitting a concealment start request from the network side to the mobile device via the wireless line;
A first concealment transmission signal generating step of performing concealment processing on the first transmission signal that is a transmission signal from the network to the mobile device after transmission of the concealment start request, and generating a first concealment transmission signal;
A first secret transmission signal transmission step of transmitting the first secret transmission signal to the mobile device;
A response determination step of determining whether or not the network has received a concealment start response to accept the concealment start request from the mobile device;
A first decryption processing step for starting decryption of a second concealment transmission signal transmitted from the mobile device when the mobile device accepts the concealment start request based on the determination in the response determination step;
A request determination step of determining whether or not the mobile station has received the concealment start request;
Based on the determination in the request determination step, a concealment start response step of transmitting the concealment start response to the network side when the mobile station accepts the concealment start request;
A second decryption processing step for starting decryption of the first concealment transmission signal transmitted by the network when the mobile device accepts the concealment start request;
A second secret transmission signal generating step of generating a second secret transmission signal by performing a concealment process on a second transmission signal that is a transmission signal to the network from the mobile device after transmission of the secret start response;
A second secret transmission signal transmission step of transmitting the second secret transmission signal from the mobile device side to the network,
A control method for a mobile communication system. In a mobile device that communicates with the network via a wireless line,
A mobile device comprising: a concealment process notifying unit that informs the network side of concealment process specifying information for specifying one or a plurality of concealment processes that can be performed.   The secret process notification means includes secret key generation process notification means for notifying the network side of secret key generation process specifying information for specifying a process for generating a secret key that can be processed together with the notification of the secret process specification information. A mobile device characterized by that. In a mobile device that communicates with the network via a wireless line,
36. The mobile device according to claim 35, further comprising a secret communication unit that performs a cipher process corresponding to a cipher execution request notified from the network side and communicates with the network. The secret communication means includes a secret key generating means for generating a corresponding secret key based on a secret key generation specifying notification for specifying a secret key generating process notified from the network side;
A concealment processing means for performing the concealment process using the generated concealment key;
38. The mobile device according to claim 37, comprising: In a network side control device that communicates with a mobile device via a wireless line,
A concealment process determining means for determining concealment processing in actual communication based on concealment process specifying information for identifying one or a plurality of concealment processes that can be performed in the mobile device notified from the mobile device;
A concealment processing execution requesting means for notifying a concealment execution request to request the mobile device to perform concealment using the determined concealment process;
A network-side control device comprising: Based on the secret key generation process specifying information specifying one or a plurality of secret key generation processes that can be processed by the mobile station notified from the mobile station, the secret key generation process used for actual communication is selected. A secret key generation processing selection means;
A secret key generation notification means for performing a secret key generation process notification for notifying the mobile device of the selected secret key generation process;
40. The network side control apparatus according to claim 39, comprising:

Images