JP5092690B2 - Call connection method, radio control apparatus, and terminal - Google Patents

Description

  The present invention relates to a call connection method, a radio control apparatus, and a terminal. The present invention also relates to a terminal that performs wireless communication with a wireless control device.

  Wireless technology has been greatly developed due to improvement in communication speed and diversification of communication technology. Mobile communication terminals have greatly improved functions, and the design and user interface have been refined. As a result, the quality required for mobile communication has changed in recent years.For example, from the level that it is only necessary to be able to communicate, it is easy to use and connect as a device that anyone can carry around on a daily basis. “Comfortableness” is demanded.

  One indicator of such “feeling” is “call connection time”. For example, when a user places a mobile phone, the more immediately the call is connected, the less stress the user receives.

The call connection sequence requires a plurality of procedures such as an RRC (Radio Resource Control) connection procedure and an authentication procedure (see, for example, Non-Patent Documents 1 to 3).
3rd Generation Partnership Project, "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)", 3GPP TS36.300, 2007-06, V8 .1.0, 19.2.2.3 3rd Generation Partnership Project, "Interlayer procedures in Connected Mode (Release 7)", 3GPP TS25.303, 2006-03, V7.0.0, Chapter 6 3rd Generation Partnership Project, "Security architecture (Release 7)", 3GPP TS33.102, 2006-12, V7.1.0, Chapters 6.3.1, 6.4.5

However, since the call connection sequence requires a plurality of procedures as described above, there is a problem that time is required for call connection.
The present invention has been made in view of these points, and an object of the present invention is to provide a call connection method, a radio control apparatus, and a terminal that can shorten the call connection time.

In order to solve the above problems, the present invention provides a call connection method for a wireless mobile communication system having a terminal, a wireless control device, and a host device of the wireless control device. In this call connection method, an authentication procedure of the terminal performed between the terminal, the wireless control device, and the higher-level device, and a setting for performing secret authentication communication between the terminal and the wireless control device are performed. A part of a secret authentication setting procedure is executed in parallel, and a wireless communication qualification confirmation and secret authentication key generation request performed from the radio control apparatus to the terminal in the authentication procedure, and the secret authentication setting procedure The start of the secret authentication communication that is performed on the terminal from the wireless control device is simultaneously performed.

  With the disclosed method, the call connection time can be shortened.

Hereinafter, the principle of the present invention will be described in detail with reference to the drawings.
FIG. 1 is a diagram showing an outline of call connection. In the figure, a call connection procedure of a terminal, a wireless control device, and a higher-level device of the wireless control device constituting the wireless communication system is shown. The call connection of the wireless communication system is divided into an RRC connection connection procedure 1, an authentication procedure 2, a secret authentication setting procedure 3, and a data line connection procedure 4.

In RRC connection connection procedure 1, a wireless connection between the terminal and the wireless control device is connected.
In the authentication procedure 2, it is confirmed between the terminal and the host device whether the terminal that has accessed the wireless network is a valid terminal.

In the secret authentication setting procedure 3, a setting for performing secret authentication communication between the terminal and the wireless control device is performed.
In the data line connection procedure 4, a communication line for user data is connected between the terminal, the radio control device, and the host device.

In the call connection shown in the figure, as shown in the figure, a part of the authentication procedure 2 and the secret authentication setting procedure 3 are executed in parallel. Thereby, the call connection time can be shortened.
Next, a first embodiment of the present invention will be described in detail with reference to the drawings.

  FIG. 2 is a diagram illustrating a configuration example of a wireless communication network according to the first embodiment. The radio communication network shown in the figure includes UE (User Equipment) 11 to 14, Node B (Base) 21 to 23, RNC (Radio Network Controller) 31, 32, MSC (Mobile-services Switching Center) / xGSN (serving / gateway General packet radio service support node) 41, and VLR (Visitor Location Register) / HLR (Home Location Register) 51. For example, a next-generation wireless communication system such as 3.5G to 4.0G is applied to the wireless communication network shown in the figure.

The UEs 11 to 14 are mobile communication terminals such as mobile phones. UE11-14 performs radio | wireless communication with NodeB21-23 which is a base station.
The RNCs 31 and 32 control the NodeBs 21 to 23 and mediate exchange of signals between the NodeBs 21 to 23 and the MSC / xGSN 41 of the host device. The MSC / xGSN 41 is a switching node and performs connection switching between transmission lines. The VLR / HLR 51 is an authentication server, and performs registration and authentication of the UEs 11 to 14. MSC / xGSN 41 and VLR / HLR 51 constitute a core network.

When performing wireless communication, the UEs 11 to 14 perform call communication with the wireless communication network illustrated in FIG.
FIG. 3 is a diagram showing a call connection sequence from the UE side when the call connection procedure is not shortened. In the figure, the call connection of the UE caller (for example, the UE making the call) is shown. The call connection is roughly divided into an RRC connection connection procedure 61, an authentication procedure 62, a concealment / authentication setting procedure 63, and a data line connection procedure 64, as shown by the dotted frame in the figure. 3 corresponds to the MSC / xGSN 41 and the VLR / HLR 51 shown in FIG. The authentication procedure 62 and the concealment / authentication setting procedure 63 are performed by the VLR / HLR 51, and the data line connection procedure 64 is performed by the MSC / xGSN 41.

In the RRC connection connection procedure 61, a radio connection between the UE and the RNC is connected.
In the authentication procedure 62, it is confirmed between the UE and the host device (VLR / HLR) whether the UE that has accessed the wireless network is a valid UE. Further, the UE and the host device each calculate a secret / authentication key for performing secret / authentication communication between the UE and the RNC.

  In the concealment / authentication setting procedure 63, the concealment / authentication key calculated by the host apparatus in the authentication procedure 62 is notified to the RNC. The RNC performs the secrecy / authentication communication in accordance with the secrecy / authentication key and the secrecy / authentication conditions notified from the host device, and the UE performs the secrecy / authentication communication according to the secrecy / authentication key and the secrecy / authentication conditions calculated by the UE. Set up.

In the data line connection procedure 64, a communication line for user data is connected between the UE, the RNC, and the host device (MSC / xGSN).
Hereinafter, the process of the sequence diagram of FIG. 3 will be described in detail.

In step S1, the UE makes a connection request for a radio connection between the UE and the RNC to the RNC (RRC Connection Request).
In step S2, when the RNC receives a connection request for radio connection from the UE, the RNC issues a setup request for radio connection connection to the UE that has requested connection (RRC Connection Setup Request).

  In step S3, the UE receives a setup request from the RNC, sets up a radio connection, and when the setup is completed, the UE notifies the RNC of the completion of the radio connection (RRC Connection Setup Complete). Through the above processing, communication between the UE and the RNC becomes possible.

  In step S4, the UE makes a service request to the higher-level device (Initial Direct Transfer (Service Request)). At this time, for example, the UE transmits information such as its own subscriber number to the higher-level device.

In step S5, the RNC transmits the service request and predetermined information received from the UE to the higher-level device (Initial UE Message (Service Request)).
In step S6, the higher-level apparatus determines whether the UE requesting communication is a valid UE based on the subscriber information transmitted from the UE, or is valid for the UE via the RNC (wireless communication qualification). And request to generate a secret / authentication encryption key (Authentication and Ciphering Request).

  In step S7, the RNC notifies the UE of the confirmation of the wireless communication qualification received from the higher-level device and the generation of the secret / authentication encryption key (Downlink Direct Transfer (Authentication and Ciphering Request)).

In step S8, the UE notifies the RNC that the request from the higher-level device has been received (Uplink Direct Transfer (Authentication and Ciphering Response)).
In step S9, the RNC notifies the host device of the response received from the UE (Authentication and Ciphering Response).

  In steps S10a and 10b, the UE and the host device generate a secret / authentication key for performing secret / authentication communication between the UE and the RNC. The UE generates a secret / authentication key common to the host device based on the predetermined information transmitted from the host device in steps S6 and S7.

Through the above processing, authentication of the UE and generation of a secret / authentication key for performing secret / authentication communication between the UE and the RNC are performed.
In step S11, the host device instructs the RNC and UE to perform confidential / authenticated communication (Security Mode Command). Since the RNC does not know the concealment / authentication key, the higher-level apparatus transmits the concealment / authentication key generated in step S10b to the RNC together with the concealment / authentication communication instruction.

In step S <b> 12, the RNC performs settings for performing confidential / authentication communication in downlink communication based on the confidential / authentication key received from the host device.
In step S13, the RNC instructs the UE to perform confidential / authenticated communication (Security Mode Command). At this time, the RNC notifies the UE of the downlink concealment start time (Activation Time) on when the downlink concealment / authentication communication starts. For example, in the example of the figure, the UE notifies the UE to start the downstream confidential / authentication communication from the data line connection procedure 64.

  In step S14, the UE notifies the RNC that the confidential / authentication communication instruction has been received (Security Mode Complete). At this time, the UE notifies the RNC of the upstream concealment start time when the upstream concealment / authentication communication starts. For example, in the example of the figure, the RNC is notified that the upstream concealment / authentication communication is started from the data line connection procedure 64.

In step S <b> 15, the RNC performs settings for performing confidential / authentication communication in uplink communication based on the confidential / authentication key received from the host device.
In step S16, the RNC notifies the higher-level device that the setting of the confidential / authentication communication has been completed (Security Mode Complete).

  In Steps S17a and 17b, the UE and the RNC start the concealment / authentication communication based on the downlink concealment start time and the uplink concealment start time exchanged in Steps S13 and S14. With the above processing, the confidentiality / authentication setting of the UE and the RNC is performed.

  In step S18, the UE requests the host device (MSC / xGSN) to connect the data line via the RNC (Uplink Direct Transfer). For example, a request is made to connect an i-mode (registered trademark) line.

In step S19, the RNC notifies the host apparatus of the data line connection request received from the UE (NAS Message).
In step S20, the higher-level device permits data line connection permission to the RNC (RAB Assignment Request). At this time, the higher-level apparatus notifies the RNC of the service channel of the data line assigned to the UE.

In step S21, the RNC issues a setup request for connecting a data line to the UE (RAB Setup).
In step S22, the UE notifies the RNC that the setup for data line connection has been completed (RAB Setup Complete).

  In step S23, the RNC notifies the host device that the setup for data line connection has been completed (RAB Assignment Response). Through the above processing, the UE can connect the data line to the wireless communication network.

In steps S24a and 24b, the UE-RNC starts data communication.
Next, call connection when the call connection procedure is shortened will be described.
FIG. 4 is a diagram showing a call connection sequence from the UE side when the call connection procedure is shortened. 4 is divided into an RRC connection connection procedure 71, an authentication procedure 72, a concealment / authentication setting procedure 73, and a data line connection procedure 74 as in FIG. However, in FIG. 4, a part of the authentication procedure 72 and a part of the concealment / authentication setting procedure 73 are performed in parallel to shorten the call connection time.

The processing of step S31 to step S36 is the same as step S1 to step S6 of FIG. 3, and detailed description thereof is omitted.
In step S37, the RNC notifies the UE of the confirmation that the wireless communication qualification received from the higher-level device (VLR / HLR) exists and the generation of the secret / authentication encryption key. In addition, the RNC instructs the UE to start confidential / authenticated communication and notifies the confidential start time.

That is, in the sequence of FIG. 4, the process of step S7 of FIG. 3 and the process of step S13 are performed in parallel (including simultaneously).
In step S38, the UE notifies the RNC that the request from the higher-level device has been received. Further, the UE notifies the RNC of the fact that the instruction for the confidential / authentication communication has been received and the upstream confidentiality start time.

That is, in the sequence of FIG. 4, the process of step S8 of FIG. 3 and the process of step S14 are performed in parallel.
Steps S39 to S40a and 40b are the same as steps S9 to S10a and 10b in FIG. 3, and a detailed description thereof will be omitted.

  In step S41, the UE starts concealment / authentication communication based on the upstream concealment start time notified to the RNC in step S38. The process of step S41 is the same as step S17a of FIG. 3, and the detailed description thereof is omitted.

  In step S42, the UE requests the host apparatus (MSC / xGSN) to establish a data line via the RNC. Note that since the concealment / authentication communication has been started in step S41, the UE performs concealment / authentication processing on the uplink signal of the data line connection request in step S42 and transmits it to the RNC.

  In step S43, the host device (VLR / HLR) instructs the RNC and the UE to perform secret communication. Since the RNC does not know the secret / authentication key, the higher-level device transmits the secret / authentication key generated in step S40b to the RNC together with the secret / authentication communication instruction.

In step S44, the RNC performs setting for performing the secret / authentication communication in the downlink / uplink communication based on the secret / authentication key received from the host device.
The processes in steps S45 and S46 are the same as steps S16 and S17b in FIG. 3, and detailed description thereof is omitted.

  In step S47, the RNC receives the data line connection request in step S42. That is, when the RNC receives the data line connection request encrypted with the concealment / authentication key in step S42, the RNC has not yet received the concealment / authentication key in step S40b from the host device. The request cannot be received. Therefore, the RNC suspends the reception process of the UE data line connection request until the setting of the confidential / authentication communication in step S46 is completed.

The processing from step S48 to step S53a, 53b is the same as step S19 to step S24a, 24b in FIG. 3, and detailed description thereof is omitted.
FIG. 5 is a sequence diagram for explaining suspension of a data line connection request. The sequence in the figure shows the processing from step S31 to step S46 in FIG.

  In step S40a of the authentication procedure 72, the UE calculates a secret / authentication key. Therefore, the UE can start the secret / authentication communication from step S41. In step S42, since the UE can perform the data line connection procedure, the UE makes a data line connection request to the host device.

  As described above, the RNC receives the secret / authentication key from the higher-level device in step S43. That is, the RNC does not receive the concealment / authentication key at the stage of receiving the signal in step S42, and cannot decrypt the concealment / authentication of the signal from the UE.

  Therefore, the RNC holds the signal from the UE in step S42 in, for example, a buffer, and performs the signal reception process in step S42 after step S46 in which concealment / authentication can be performed.

  FIG. 6 is a functional block diagram of the RNC. As shown in the figure, the RNC 80 includes a task management unit 81, a task execution unit 82, and a buffer 83. The RNC 80 has a function as shown in the figure by executing a program stored in a storage device such as an HDD (Hard Disk Drive) by a CPU (Central Processing Unit).

  The task management unit 81 manages a task that performs each process of the RNC described with reference to FIG. For example, the task order is managed so that the RNC executes processing in an appropriate order. The task execution unit 82 executes a task managed by the task management unit 81. The buffer 83 temporarily stores signals (data) transmitted from the UE and the host device.

  When the task management unit 81 receives the signal of step S36 in FIG. 4 from the host device, the task management unit 81 confirms that the UE has the wireless communication qualification, notifies the generation request of the secret / authentication encryption key, and the secret / authentication communication. The task that simultaneously issues the start instruction (including the confidential start time) is called (step S37 in FIG. 4).

  Further, the task management unit 81 performs task management so that the reception process of the data line connection request signal is not performed even if the data line connection request signal transmitted from the UE is stored in the buffer 83. The task management unit 81 performs task management so that the concealment / authentication start process in step S46 in FIG. 4 is completed and the data line connection request signal reception process is performed (step S47 in FIG. 4).

  Note that the UE has the same function as in FIG. 6 and executes predetermined processing. When the task management unit of the UE receives the signal of step S37 in FIG. 4 from the RNC, the notification that the request has been received from the higher-level device and the notification that the start instruction of the secret / authentication communication has been received to the RNC. Are called simultaneously (step S38 in FIG. 4).

  In this way, a part of the authentication procedure 72 and a part of the concealment / authentication setting procedure 73 are performed in parallel as shown in steps S37 and S38. Then, as shown in step S47, the data line connection request from the UE is put on hold until the RNC can perform confidential / authenticated communication. Thereby, the connection time of the call connection can be shortened.

In the above, the call connection request from the UE side has been described. Hereinafter, a call connection request in the case where a UE is called from a host device (switch side (MSC / xGSN side)) will be described.
FIG. 7 is a diagram showing a call connection sequence from the exchange when the call connection procedure is not shortened. The call connection is divided into an RRC connection connection procedure 91, an authentication procedure 92, a concealment / authentication setting procedure 93, and a data line connection procedure 94 as in the sequence diagram of FIG.

  The direction of the data line connection procedure 94 is different from the data line connection procedure 64 in the sequence diagram of FIG. Moreover, the process of step S51-step S67a, 67b is the same as that of step S1-step S17a, 17b of FIG. 3, The detailed description is abbreviate | omitted.

In step S68, the host device (MSC / xGSN) notifies the RNC that there has been a data line connection request from the UE on the other side (NAS Message).
In step S69, the RNC notifies the UE that there has been a data line connection request from the counterpart UE (Downlink Direct Transfer).

In step S70, the higher-level device notifies the RNC of the service channel of the data line assigned to the UE (RAB Assignment Request).
In step S71, the RNC issues a setup request for connecting a data line to the UE (RAB Setup).

In step S72, the UE notifies the RNC that setup for data line connection has been completed (RAB Setup Complete).
In step S73, the RNC notifies the host device that the setup for data line connection has been completed (RAB Assignment Response). Through the above processing, the UE can connect the data line to the wireless communication network.

In steps S74a and 74b, the UE-RNC starts data communication.
FIG. 8 is a diagram showing a call connection sequence from the exchange side when the call connection procedure is shortened. 8, the call connection is divided into an RRC connection connection procedure 101, an authentication procedure 102, a concealment / authentication setting procedure 103, and a data line connection procedure 104 as in FIG. However, in FIG. 8, a part of the authentication procedure 102 and a part of the concealment / authentication setting procedure 103 are performed at the same time, thereby shortening the connection time of the call connection.

  The processing from step S81 to step S91 is the same as that from step S31 to step S41 in FIG. That is, in the sequence of FIG. 8, the processing of step S57 and step S63 of FIG. 7 is performed simultaneously, and the processing of step S58 and step S64 is performed simultaneously to shorten the call connection time.

In step S92, the host apparatus (MSC / xGSN) transmits a data line connection request to the RNC.
In step S93, the host device (VLR / HLR) instructs the RNC and the UE to perform confidential / authenticated communication. Since the RNC does not know the secret / authentication key, the higher-level device notifies the secret / authentication key generated in step S90b to the RNC together with the secret / authentication communication instruction.

In step S <b> 94, the RNC performs settings for performing confidential / authentication communication in downlink / uplink communication based on the confidential / authentication key received from the host device.
The processing in steps S95 and S96 is the same as that in steps S66 and S67b in FIG. 7, and detailed description thereof will be omitted.

  In step S97, the RNC receives the data line connection request from the host device in step S92. That is, when the RNC receives the data line connection request in step S92, the RNC has not yet received the secret / authentication key in step S93 from the host device. Cannot send. Therefore, the RNC suspends the reception processing of the data line connection request from the host device until the concealment / authentication start setting in step S96 is completed.

The processes in steps S98 to S103a and 103b are the same as those in steps S69 to S74a and 74b in FIG.
As described above, a part of the authentication procedure 102 and a part of the concealment / authentication setting procedure 103 are simultaneously performed as shown in steps S87 and S88. Then, as shown in step S97, the RNC suspends the data line connection request from the host device until confidential / authenticated communication is possible. Thereby, the connection time of the call connection can be shortened.

  Next, a second embodiment of the present invention will be described in detail with reference to the drawings. In the first embodiment, the RNC itself has suspended the reception process of the data line connection request until the RNC can perform confidential / authenticated communication. In the second embodiment, until the RNC can perform confidential / authenticated communication, the UE side delays the start of confidential / authenticated communication.

  FIG. 9 is a diagram showing a call connection sequence from the UE side when the call connection procedure according to the second embodiment is shortened. 9, the call connection is divided into an RRC connection connection procedure 111, an authentication procedure 112, a concealment / authentication setting procedure 113, and a data line connection procedure 114 as in FIG. However, in FIG. 9, a part of the authentication procedure 112 and a part of the concealment / authentication setting procedure 113 are performed in parallel to shorten the connection time of the call connection.

The processing in steps S111 to S120a and 120b is the same as that in steps S31 to S40a and 40b in FIG. 4, and a detailed description thereof will be omitted.
In step S121, the UE makes a data line connection request to connect the data line to the host apparatus (MSC / xGSN) via the RNC.

  In step S122, the higher-level device (VLR / HLR) instructs the RNC and the UE to perform secret communication. Since the RNC does not know the secret / authentication key, the higher-level device transmits the secret / authentication key generated in step S120b to the RNC together with the secret communication instruction.

In step S123, the RNC performs settings for performing confidential / authentication communication in downlink / uplink communication based on the confidential / authentication key received from the host device.
In step S124, the UE starts secret / authentication communication.

In step S125, the RNC notifies the host device that the setting of the confidential / authentication communication has been completed. In step S126, the RNC notifies the host device of the data line connection request received in step S121 from the UE.

In step S127, the RNC starts secret / authentication communication.
Note that the processing from step S128 to step S132a, 132b is the same as that from step S49 to step S53a, 53b in FIG. 4, and a detailed description thereof will be omitted.

  As shown in the sequence of the figure, the UE generates a concealment / authentication key in step S120a. In step S121, the UE makes a data line connection request without performing communication concealment / authentication processing. This is because the RNC has not yet acquired the concealment / authentication key from the host device (VLR / HLR) and cannot solve the data line connection request subjected to the concealment / authentication process. Since the data line connection request in step S121 does not include important information such as the telephone number of the UE, there is no problem even if it is transmitted to the RNC without performing concealment / authentication processing.

  FIG. 10 is a functional block diagram of the UE. As shown in the figure, the UE 120 has a task management unit 121 and a task execution unit 122. For example, the UE 120 has a function as shown in the figure by executing a program stored in a storage device such as a nonvolatile memory by the CPU.

  The task management unit 121 manages a task for performing each process of the UE described in FIG. For example, the task order is managed so that the UE executes processing in an appropriate order. The task execution unit 122 executes a task managed by the task management unit 121.

  When the task management unit 121 receives confirmation from the RNC that it has wireless communication qualification and notification of a secret / authentication key generation request (step S117 in FIG. 9), the task management unit 121 confirms that the RNC has wireless communication qualification. A task for simultaneously performing the notification of reception and the notification of reception of the secret / authentication encryption key generation request is called (step S118 in FIG. 9).

  In addition, when the secret / authentication key is generated as shown in step S120a of FIG. 9, the task management unit 121 normally calls a secret / authentication start task so as to start secret / authentication communication. However, the RNC may not yet receive the concealment / authentication key from the host device as described above. Therefore, the task management unit 121 calls the task to make a data line connection request first. Then, the RNC concealment / authentication setting process is completed (the data line connection request is made first), and the concealment / authentication start task is called.

  The RNC also has the same function as that shown in FIG. 10 and executes predetermined processing. When the task management unit of the RNC receives the signal of step S116 in FIG. 9 from the host device, the task of simultaneously confirming that the UE is qualified for wireless communication and notifying the generation of the secret / authentication encryption key (Step S117 in FIG. 9).

  As described above, a part of the authentication procedure 112 and a part of the concealment / authentication setting procedure 113 are simultaneously performed as shown in steps S117 and S118. Then, as shown in step S124, until the RNC can perform confidentiality / authentication communication, the UE starts delaying confidentiality / authentication communication start. Thereby, the connection time of the call connection can be shortened.

  FIG. 11 is a diagram showing another call connection sequence when the call connection procedure is shortened. 11, the call connection is divided into an RRC connection connection procedure 131, an authentication procedure 132, a concealment / authentication setting procedure 133, and a data line connection procedure 134 as in FIG. However, in FIG. 11, the RRC connection connection procedure 131 and the authentication procedure 132 are further shortened with respect to the sequence of FIG.

  In step S141 in FIG. 11, step S111 and step S114 in FIG. 9 are performed simultaneously. Thereby, the RRC connection connection procedure 131 and the authentication procedure 132 are shortened.

  Note that the processes in steps S145 to S161a and S161b are the same as those in steps S116 to S132a and 132b in FIG. 9, and a detailed description thereof will be omitted. Further, the shortening of the RRC connection connection procedure 131 and the authentication procedure 132 is described in Non-Patent Document 1.

  As described above, a part of the processing of the authentication procedure 132 and a part of the processing of the concealment / authentication setting procedure 133 are overlapped and a part of the processing of the RRC connection connection procedure 131 and the part of the authentication procedure 132 is overlapped. Thus, the call connection time can be further shortened.

In the above, the call connection request from the UE side has been described. In the following, call processing from the exchange side (MSC / xGSN) will be described.
FIG. 12 is a diagram showing a call connection sequence from the exchange side when the call connection procedure is shortened. The call connection of FIG. 12 is also divided into an RRC connection connection procedure 141, an authentication procedure 142, a concealment / authentication setting procedure 143, and a data line connection procedure 144 as in FIG.

The processes in steps S171 to S180a and 180b are the same as those in steps S111 to S120a and 120b in FIG. 9, and a detailed description thereof will be omitted.
In step S181, the host device (MSC / xGSN) notifies the RNC that there has been a data line connection request from the UE on the other side.

In step S182, the RNC notifies the UE that there was a data line connection request from the UE on the other side. In step S183, the higher-level device (VLR / HLR) Instruct to perform authentication communication. Since the RNC does not know the concealment / authentication key, the higher-level apparatus transmits the concealment / authentication key generated in step S180b to the RNC together with the concealment / authentication communication instruction.

In step S184, the RNC performs settings for performing confidential / authentication communication in downlink / uplink communication based on the confidential / authentication key received from the host device.
In step S185, the UE starts confidential / authenticated communication.

In step S186, the RNC notifies the higher-level device that the setting of the confidential / authentication communication has been completed.
Hereinafter, the processing of step S187 to steps S192a and 192b is the same as that of step S127 to steps S132a and 132b of FIG. 9, and detailed description thereof will be omitted.

  In this way, a part of the authentication procedure and a part of the concealment / authentication setting procedure are simultaneously performed as shown in steps S177 and S178. And as shown to step S185, until RNC can perform secrecy / authentication communication, the start of secrecy / authentication communication is delayed on the UE side. Thereby, the connection time of the call connection can be shortened.

  The process of overlapping a part of the RRC connection connection procedure 141 and the authentication procedure 142 described with reference to FIG. 11 can also be applied to the sequences of FIG. 4, FIG. 8, and FIG.

It is the figure which showed the outline | summary of call connection. It is the figure which showed the structural example of the radio | wireless communication network which concerns on 1st Embodiment. It is the figure which showed the call connection sequence from the UE side in the case of not shortening a call connection procedure. It is the figure which showed the call connection sequence from the UE side at the time of shortening a call connection procedure. It is a sequence diagram explaining suspension of a data line connection request. It is a functional block diagram of RNC. It is the figure which showed the call connection sequence from the exchange side in the case of not shortening a call connection procedure. It is the figure which showed the call connection sequence from the exchange side at the time of shortening a call connection procedure. It is the figure which showed the call connection sequence from UE side at the time of shortening the call connection procedure which concerns on 2nd Embodiment. It is a functional block diagram of UE. It is the figure which showed another call connection sequence at the time of shortening a call connection procedure. It is the figure which showed the call connection sequence from the exchange side at the time of shortening a call connection procedure.

Explanation of symbols

1 RRC connection connection procedure 2 Authentication procedure 3 Secret authentication setting procedure 4 Data line connection procedure

Claims (10)

In a call connection method for a wireless mobile communication system having a terminal, a wireless control device, and a host device of the wireless control device,
An authentication procedure of the terminal performed between the terminal, the wireless control device, and the higher-level device, and a secret authentication setting procedure for performing settings for performing secret authentication communication between the terminal and the wireless control device. in parallel some running,
Wireless communication qualification confirmation and secret authentication key generation request made to the terminal from the radio control apparatus in the authentication procedure, and the secrecy performed from the radio control apparatus to the terminal in the secret authentication setting procedure Simultaneously start authentication communication,
A call connection method.   In a call connection method for a wireless mobile communication system having a terminal, a wireless control device, and a host device of the wireless control device,
  An authentication procedure of the terminal performed between the terminal, the wireless control device, and the higher-level device, and a secret authentication setting procedure for performing settings for performing secret authentication communication between the terminal and the wireless control device. Run some in parallel,
  A notification that the wireless communication qualification is received from the higher-level device performed from the terminal of the authentication procedure to the wireless control device and a notification that a request for generating a secret authentication key has been received, and the secret authentication Simultaneously performing notification of reception of the start instruction of the secret authentication communication performed from the terminal of the setting procedure to the wireless control device,
  A call connection method. A notification that the wireless communication qualification is received from the higher-level device performed from the terminal of the authentication procedure to the wireless control device and a notification that a request for generating a secret authentication key has been received, and the secret authentication 3. The call connection according to claim 1, wherein a notification indicating that the start instruction of the secret authentication communication performed from the terminal in the setting procedure to the radio network controller is received at the same time. Method. The radio controller according to claim 1 or 2, characterized in that delays reception processing of the data line connection request from the terminal to the confidential authentication setting concealment authentication setting processing procedure is completed Call connection method. The radio controller according to claim 1 or 2, characterized in that delays reception processing of the data line connection request from the host system to the ciphering authentication setting concealment authentication setting processing procedure is completed Call connection method. The terminal, the said concealed authenticate communication setting is completed wireless control device, a call connection method according to claim 1 or 2, characterized in that initiating the secret authentication communication. In a wireless control device that performs wireless communication with a terminal,
Secret authentication for performing authentication of the terminal performed between the terminal, the wireless control device, and a higher-level device of the wireless control device, and setting for performing confidential authentication communication between the terminal and the wireless control device Execution means for executing a part of the setting procedure in parallel;
With
The execution means includes a wireless communication qualification confirmation and a secret authentication key generation request that are performed from the radio control device of the authentication procedure to the terminal, and a radio authentication device to the terminal of the secret authentication setting procedure. Simultaneously with the start instruction of the secret authentication communication performed
A wireless control device. In a terminal that performs wireless communication with a wireless control device,
Secret authentication for performing the authentication procedure of the terminal performed between the terminal, the wireless control device, and the host device of the wireless control device, and setting for performing the secret authentication communication between the terminal and the wireless control device Execution means for executing a part of the setting procedure in parallel;
With
The execution means includes a wireless communication qualification confirmation and a secret authentication key generation request that are performed from the radio control device of the authentication procedure to the terminal, and a radio authentication device to the terminal of the secret authentication setting procedure. Simultaneously with the start instruction of the secret authentication communication performed
A terminal characterized by that.   In a wireless control device that performs wireless communication with a terminal,
  Secret authentication for performing authentication of the terminal performed between the terminal, the wireless control device, and a higher-level device of the wireless control device, and setting for performing confidential authentication communication between the terminal and the wireless control device Execution means for executing a part of the setting procedure in parallel;
  With
  The execution means is notified from the terminal of the authentication procedure to the radio network controller that it has received a radio communication qualification from the host device and a notification that a secret authentication key generation request has been received. And simultaneously notifying that the start instruction of the secret authentication communication performed to the radio network controller from the terminal in the secret authentication setting procedure is received,
  A wireless control device.   In a terminal that performs wireless communication with a wireless control device,
  Secret authentication for performing the authentication procedure of the terminal performed between the terminal, the wireless control device, and the host device of the wireless control device, and setting for performing the secret authentication communication between the terminal and the wireless control device Execution means for executing a part of the setting procedure in parallel;
  With
  The execution means is notified from the terminal of the authentication procedure to the radio network controller that it has received a radio communication qualification from the host device and a notification that a secret authentication key generation request has been received. And simultaneously notifying that the start instruction of the secret authentication communication performed to the radio network controller from the terminal in the secret authentication setting procedure is received,
  A terminal characterized by that.

Images