Mobile communication system, base station, higher-order apparatus, communication method, and program
21 claims: 5 independent, 16 dependent
- 1UEと、第1のHNBと、第2のHNBと、HNB-GWと、を有する移動通信システムであって、 前記HNB-GWはコアネットワークの外部に設けられ、 前記第1のHNBは、前記UEと通信する手段と、前記UEが前記第1のHNBから前記第2のHNBへIntra HNB-GWのリロケーションを実行するとき、RFCI情報を含む第1のメッセージを前記HNB-GWに送信する手段と、を有し、 前記HNB-GWは、前記第1のメッセージを受信する手段と、前記RFCI情報を含む第2のメッセージを前記第2のHNBに送信する手段と、を有し、 前記第2のHNBは、前記UEと通信する手段と、前記HNB-GWから前記第2のメッセージを受信する手段と、を有し、 前記RFCI情報は、Iu-UP Initializationの実行を伴わずに前記第2のHNBへ送信される、移動通信システム。
- 2前記第2のメッセージは、RANAPメッセージを含む、請求項1に記載の移動通信システム。
- 3前記第2のメッセージは、Relocation Requestメッセージを含む、請求項1または2に記載の移動通信システム。
- 4前記第1のメッセージは、RANAPメッセージを含む、請求項1乃至3のいずれか1項に記載の移動通信システム。
- 5前記第1のメッセージは、リロケーションを要求するメッセージを含む、請求項1乃至4のいずれか1項に記載の移動通信システム。
- 6UEと、第1のHNBと、第2のHNBと、HNB-GWと、を有する移動通信システムにおける第1のHNBであって、 前記HNB-GWはコアネットワークの外部に設けられ、 前記UEと通信する手段と、 前記UEが前記第1のHNBから前記第2のHNBへIntra HNB-GWのリロケーションを実行するとき、RFCI情報を含む第1のメッセージを前記HNB-GWに送信する手段と、を有し、 前記RFCI情報は、Iu-UP Initializationの実行を伴わずに前記第2のHNBへ送信される、第1のHNB。
- 7前記第1のメッセージは、RANAPメッセージを含む、請求項6に記載の第1のHNB。
- 8前記第1のメッセージは、リロケーションを要求するメッセージを含む、請求項6または7に記載の第1のHNB。
- 9UEと、第1のHNBと、第2のHNBと、HNB-GWと、を有する移動通信システムにおける第2のHNBであって、 前記HNB-GWはコアネットワークの外部に設けられ、 前記UEと通信する手段と、前記UEが前記第1のHNBから前記第2のHNBへIntra HNB-GWのリロケーションを実行するとき、RFCI情報を含む第2のメッセージをIu-UP Initializationの実行を伴わずに前記HNB-GWから受信する手段と、を有する、第2のHNB。
- 10前記第2のメッセージは、RANAPメッセージを含む、請求項9に記載の第2のHNB。
- 11前記第2のメッセージは、Relocation Requestメッセージを含む、請求項9または10に記載の第2のHNB。
- 12UEと、第1のHNBと、第2のHNBと、HNB-GWと、を有する移動通信システムにおけるHNB-GWであって、 前記HNB-GWはコアネットワークの外部に設けられ、 前記UEが前記第1のHNBから前記第2のHNBへIntra HNB-GWのリロケーションを実行するとき、前記第1のHNBから、RFCI情報を含む第1のメッセージを受信する手段と、前記RFCI情報を含む第2のメッセージを前記第2のHNBに送信する手段と、を有し、 前記RFCI情報は、Iu-UP Initializationの実行を伴わずに前記第2のHNBへ送信される、HNB-GW。
- 13前記第2のメッセージは、RANAPメッセージを含む、請求項12に記載のHNB-GW。
- 14前記第2のメッセージは、Relocation Requestメッセージを含む、請求項12または13に記載のHNB-GW。
- 15前記第1のメッセージは、RANAPメッセージを含む、請求項12乃至14のいずれか1項に記載のHNB-GW。
- 16前記第1のメッセージは、リロケーションを要求するメッセージを含む、請求項12乃至14のいずれか1項に記載のHNB-GW。
- 17UEと、第1のHNBと、第2のHNBと、HNB-GWと、を有する移動通信システムにおけるUEであって、 前記HNB-GWはコアネットワークの外部に設けられ、 前記第1のHNBと通信する手段と、前記第2のHNBと通信する手段とを有し、 前記第1のHNBから前記第2のHNBへIntra HNB-GWのリロケーションを実行するとき、RFCI情報を含む第1のメッセージが、前記第1のHNBから前記HNB-GWに送信され、 前記RFCI情報を含む第2のメッセージが、前記HNB-GWから前記第2のHNBへIu-UP Initializationの実行を伴わずに送信される、UE。
- 18前記第2のメッセージは、RANAPメッセージを含む、請求項17に記載のUE。
- 19前記第2のメッセージは、Relocation Requestメッセージを含む、請求項17または18に記載のUE。
- 20前記第1のメッセージは、RANAPメッセージを含む、請求項17乃至19のいずれか1項に記載のUE。
- 21前記第1のメッセージは、リロケーションを要求するメッセージを含む、請求項17乃至20のいずれか1項に記載のUE。
Independent claims21
207 paragraphs, as filed
The present invention relates to a mobile communication system, a base station, a host device, a gateway device, a communication method, and a program.
As an existing mobile communication system of 3GPP (3rd Generation Partnership Project), a mobile communication system consisting of Node-B (base station), RNC (Radio Network Controller), and CN (Core Network) is there.
AMR (Adaptive Multi-Rate) is an example of a voice data coding method in a mobile communication system having such a configuration. AMR is a method that dynamically changes the rate of voice data according to the line conditions and the like.
In a mobile communication system using AMR, a transcoder is installed in the CN in order to make the coding and decoding rates of voice data the same, and if necessary, recoding (transcoding) is performed by the transcoder. Is going.
A data frame of audio data encoded by AMR is composed of a plurality of subflows having different data sizes. The combination of these plurality of subframes differs depending on the rate of audio data, and the RFCI (RAB sub-Flow Combination Indicator) value is defined as an identifier for each combination. That is, the RFCI value will be defined for each rate of voice data.
Further, in the mobile communication system using AMR, RFCI information is set in each Node-B as control information in voice coding. The RFCI information includes information for identifying the structure of the data frame indicated by the RFCI value for each RFCI value, specifically, information on the number of subflows constituting the data frame and the data size for each subflow. In addition to AMR, RFCI information is also used for Wide-Band AMR (wideband voice codec) and CS streaming service (Fax and modem communication).
When Node-B transmits audio data encoded at a certain rate, it transmits audio data with an RFCI value added corresponding to that rate to other Node-B, and audio data from other Node-B. Is received, the voice data is decoded at a rate corresponding to the RFCI value added to the voice data.
Here, when a UE (User Equipment: terminal) makes a voice call via two Node-Bs, if the RFCI information matches between the two Node-Bs, each of these two RFCI information The RFCI value indicates a data frame with the same structure. Therefore, it is possible to encode / decode audio data at the same rate between two Node-Bs without going through a transcoder in the CN. Such a method of making a voice call without going through a transcoder is called Transcoder Free Operation (TrFO). This method is specified in 3GPP TS23.153 (Non-Patent Document 1).
On the other hand, if the RFCI information does not match between the two Node-Bs, the two RFCI information may indicate data frames with different structures even if the RFCI values are the same. In this case, voice data cannot be encoded / decoded at the same rate between two Node-Bs without going through the transcoder, so voice calls can be made while maintaining transcoder free operation (TrFO). You can't do it.
Therefore, in order to make a voice call while maintaining transcoder-free operation (TrFO), it is desirable to match the RFCI information between the two Node-Bs.
However, in a mobile communication system, the movement of the UE occurs frequently, so that the RFCI information may not match between the source Node-B to which the UE connects before the move and the destination Node-B to which the UE connects after the move. It is thought that there are many.
Therefore, in 3GPP TS25.415 (Non-Patent Document 2), the RNC to which the source Node-B of the UE is connected and the RNC to which the destination Node-B are connected are different, so-called SRNS (Serving Radio Network Subsystem) relocation. It is stipulated that RFCI information should be taken over between RNCs via CN by the Iu-UP Initialization message specified by the Iu-UP (Iu interface user plane) protocol.
<p><nplcit num="1"><text>3GPP TS 23.153</text></nplcit><nplcit num="2"><text>3GPP TS 25.415</text></nplcit><nplcit num="3"><text>3GPP TS 25.413</text></nplcit><nplcit num="4"><text>3GPP TS 25.467</text></nplcit><nplcit num="5"><text>3GPP TS 25.468</text></nplcit><nplcit num="6"><text>3GPP TS 25.469</text></nplcit></p>
<p> By the way, recently, 3GPP is composed of a small base station for homes and small offices called HNB (Home Node-B: small base station), HNB-GW (Home Node-Gateway), and CN. Mobile communication systems are being studied. The configuration of this mobile communication system will be described in detail with reference to FIG.</p><p> Referring to FIG. 1, this mobile communication system has UE1, HNB-S2, HNB-T3, HNB-GW4, CN6 including CN node 5, HNB-GW7, and HNB-X8. ..</p><p> UE1 is a 3rd generation mobile mobile phone (terminal).</p><p> The HNB-S2, HNB-T3, and HNB-X8 are small base stations for homes and small offices.</p><p> HNB-S2 is a migration source HNB to which UE1 connects before migration.</p><p> HNB-T3 is a destination HNB to which UE1 connects after moving.</p><p> HNB-X8 is an HNB that has a UE (not shown) of the communication partner of UE1 under its control.</p><p> HNB-GW4 is a gateway device that connects HNB-S2 and HNB-T3 to CN6, and HNB-GW7 is a gateway device that connects HNB-X8 to CN6.</p><p> CN6 is a 3rd generation mobile exchange network.</p><p> CN node 5 is a core network device such as HMS (Home Node B Management System) and MSC (Mobile Switching Center) provided in CN6.</p><p> UE1 moves from HNB-S2 under the same HNB-GW4 to HNB-T3. Such movement is called intra-HNB-GW relocation.</p><p> Before moving, UE1 makes a voice call with the UE under HNB-X8 via HNB-S2, HNB-GW4, CN6, HNB-GW7, and HNB-X8.</p><p> After moving, UE1 makes a voice call with the UE under HNB-X8 via HNB-T3, HNB-GW4, CN6, HNB-GW7, and HNB-X8.</p><p> In FIG. 1, the opposite system of the communication partner of UE1 is a 3GPP wireless communication system composed of HNB-X8 / HNB-GW7 / CN6, but it is composed of the existing Node-B / RNC / CN. It may be a 3GPP wireless communication system.</p><p> Here, it is assumed that the HNB is installed by an individual, not a mobile phone operator. Therefore, although HNB-S2 and HNB-T3 are under the same HNB-GW4, it is assumed that the vendors are different.</p><p> Therefore, it is quite possible that the RFCI information does not match between HNB-S2 and HNB-T3 when intra-HNB-GW relocation occurs between HNB-S2 and HNB-T3 by UE1.</p><p> If the RFCI information does not match, there is a problem that voice calls cannot be made while maintaining transcoder-free operation (TrFO).</p><p> Therefore, in 3GPP, even in the mobile communication system composed of HNB / HNB-GW / CN, discussions are being made toward standardization of the intra-HNB-GW relocation method between HNBs, but RFCI information between HNBs. No solution has been provided if they do not match.</p><p> Therefore, an object of the present invention is to solve the above-mentioned problems, and to make a voice call while maintaining transcoder-free operation (TrFO) even when an intra-HNB-GW relocation occurs between HNBs. , Base station, host device, gateway device, communication method, program.</p>
<p> The first mobile communication system of the present invention includes a terminal, a mobile source base station to which the terminal connects before moving, a mobile destination base station to which the terminal connects after moving, the mobile source base station, and the moving destination. A mobile communication system including a higher-level device having a base station under its control, wherein control information in voice coding is preset in the mobile source base station and the mobile destination base station, and the mobile is described. The original base station includes the control information of its own station in the first message, transmits the first message to the higher-level device, and the higher-level device transfers the control information of the mobile source base station to the second higher-level device. The second message is included in the message and transmitted to the destination base station.</p><p> The second mobile communication system of the present invention includes a terminal, a mobile source base station to which the terminal connects before moving, a mobile destination base station to which the terminal connects after moving, the mobile source base station, and the moving destination. A mobile communication system including a gateway device for connecting a base station to a core network, wherein the mobile source base station and the mobile destination base station are used as control information in voice coding for each identifier. The control information that identifies the structure of the data frame of the voice-encoded voice data indicated by the identifier is preset, and the moving source base station includes the control information of its own station in the first message, and the control information is included in the first message. The first message is transmitted to the gateway device, the destination base station includes the control information of its own station in the second message, and the second message is transmitted to the gateway device. , The control information of the mobile source base station included in the first message and the control information of the mobile destination base station included in the second message are stored. When the control information of the moving source base station and the moving destination base station do not match, when voice data is subsequently received from the moving destination base station, the identifier added to the voice data is used as the moving source base. It is converted into an identifier indicating a data frame having the same structure in the control information of the station, and the voice data to which the converted identifier is added is transmitted to the core network.</p><p> The first base station of the present invention is a movement source base station to which a terminal is connected before moving, and control information in voice coding is preset, and the control information of the own station is included in a message. It has a unit and a transmission / reception unit that transmits the message to a higher-level device.</p><p> The second base station of the present invention is a destination base station to which the terminal is connected after the movement, and the terminal is moved from the control unit in which the control information in the voice coding is preset and the host device before the terminal is moved. It has a transmission / reception unit for receiving a first message including the control information of the mobile source base station connected to the device.</p><p> The higher-level device of the present invention is a higher-level device having a moving source base station to which the terminal connects before moving and a moving destination base station to which the terminal connects after moving, and the moving source base station and the above. In the destination base station, control information in voice coding is preset, and a transmission / reception unit that receives a first message including the control information of the movement source base station from the movement source base station and the movement It has a control unit that includes the control information of the original base station in the second message, and the transmission / reception unit transmits the second message to the destination base station.</p><p> The gateway device of the present invention is a gateway device that connects a mobile base station to which a terminal connects before moving and a mobile destination base station to which the terminal connects after moving to a core network, and is the mobile base station. And the destination base station is preset with control information for identifying the structure of the data frame of the voice-encoded voice data indicated by the identifier for each identifier as the control information in the voice coding. A first message including the control information of the mobile source base station is received from the mobile source base station, and a second message including the control information of the mobile destination base station is received from the mobile destination base station. A storage unit that stores the transmission / reception unit, the control information of the mobile source base station included in the first message, and the control information of the mobile destination base station included in the second message. When the control information of the moving source base station and the moving destination base station do not match, when the voice data is subsequently received from the moving destination base station, the identifier added to the voice data is moved. A control unit that converts a data frame having the same structure into an identifier in the control information of the original base station, It has a second transmission / reception unit that transmits voice data to which the converted identifier is added to the core network.</p><p> The first communication method of the present invention includes a terminal, a mobile source base station to which the terminal connects before moving, a mobile destination base station to which the terminal connects after moving, the mobile source base station, and the mobile destination base. It is a communication method by a mobile communication system having a higher-level device having a station under its control, and the mobile source base station includes control information in voice coding of its own station in a first message, and the first message. A step of transmitting the message 1 to the higher-level device, and a step of the higher-level device including the control information of the mobile source base station in the second message and transmitting the second message to the destination base station. And have.</p><p> The second communication method of the present invention includes a terminal, a moving source base station to which the terminal is connected before moving, a moving destination base station to which the terminal is connected after moving, the moving source base station, and the moving destination base. It is a communication method by a mobile communication system including a gateway device for connecting a station to a core network, and the mobile source base station uses the identifier as control information in voice coding of its own station for each identifier. The step of including the control information for identifying the structure of the data frame of the voice-encoded voice data in the first message and transmitting the first message to the gateway device, and the destination base station The step of including the control information of the own station in the second message and transmitting the second message to the gateway device, and the said of the mobile source base station in which the gateway device is included in the first message. A step for storing the control information and the control information of the destination base station included in the second message, and When the gateway device subsequently receives voice data from the mobile destination base station when the control information of the mobile source base station and the mobile destination base station does not match, the identifier added to the voice data is used. , The step of converting the data frame of the same structure into the identifier indicating the data frame in the control information of the mobile source base station, and the gateway device transmitting the voice data to which the converted identifier is added to the core network. Has steps to do.</p><p> The third communication method of the present invention is a communication method by the base station of the movement source to which the terminal is connected before moving, and includes a step of including control information in voice coding of the own station in a message and a higher-level device including the message. Has a step to send to.</p><p> The fourth communication method of the present invention is a communication method by a destination base station to which the terminal is connected after the movement, and is a voice code of the movement source base station to which the terminal is connected before the movement from the host device. It has a step of receiving a first message including control information in the conversion.</p><p> The fifth communication method of the present invention is a communication method by a host device having a moving source base station to which the terminal connects before moving and a moving destination base station to which the terminal connects after moving. The step of receiving the first message including the control information in the voice coding of the mobile source base station from the mobile source base station, the step of including the control information of the mobile source base station in the second message, and the above-mentioned It has a step of transmitting a second message to the destination base station.</p><p> The sixth communication method of the present invention is a communication method using a gateway device that connects a mobile source base station to which a terminal connects before moving and a mobile destination base station to which the terminal connects after moving to a core network. , From the mobile base station, as control information in the voice coding of the mobile base station, each identifier includes control information for identifying the structure of the data frame of the voice-encoded voice data indicated by the identifier. A step of receiving the first message and receiving a second message from the destination base station including the control information of the destination base station, and the source base included in the first message. The step of storing the control information of the station and the control information of the mobile destination base station included in the second message coincides with the control information of the mobile source base station and the mobile destination base station. If not, when voice data is subsequently received from the destination base station, the identifier added to the voice data is an identifier indicating a data frame having the same structure in the control information of the moving source base station. And the steps to convert to It has a step of transmitting voice data to which the converted identifier is added to the core network.</p><p> The first program of the present invention includes a procedure for including control information in voice coding of the own station in a message at a moving source base station to which the terminal is connected before moving, and a procedure for transmitting the message to a higher-level device. To execute.</p><p> The second program of the present invention includes control information in the voice coding of the base station of the movement source to which the terminal is connected before the movement from the host device to the base station of the movement destination to which the terminal is connected after the movement. Perform the procedure to receive the first message.</p><p> The third program of the present invention connects the mobile source base station to a higher-level device having a mobile base station to which the terminal connects before moving and a mobile destination base station to which the terminal connects after moving, from the mobile base station. The procedure for receiving the first message including the control information in the voice coding of the mobile source base station, the procedure for including the control information of the mobile source base station in the second message, and the second message are described above. Execute the procedure for transmitting to the destination base station.</p><p> The fourth program of the present invention provides a gateway device for connecting a mobile base station to which a terminal connects before moving and a mobile base station to which the terminal connects after moving to a core network, to the mobile base station. As the control information in the voice coding of the mobile source base station, a first message including the control information indicating the structure of the data frame of the voice-encoded voice data indicated by the identifier is received for each identifier. At the same time, the procedure for receiving the second message including the control information of the mobile destination base station from the mobile destination base station, and the control information of the mobile source base station included in the first message. If the procedure for storing the control information of the mobile destination base station and the control information of the mobile source base station and the mobile destination base station, which are included in the second message, do not match, thereafter, When voice data is received from the destination base station, the procedure for converting the identifier added to the voice data into an identifier indicating a data frame having the same structure in the control information of the movement source base station, and The procedure of transmitting the voice data to which the converted identifier is added to the core network is executed.</p>
<p> According to the first mobile communication system of the present invention, the mobile source base station transmits the control information of its own station to the host device, and the host device transmits the control information of the mobile source base station to the mobile destination base station. ..</p><p> Therefore, since the mobile destination base station can inherit the control information from the mobile source base station, the voice is maintained while maintaining the transcoder-free operation (TrFO) when the relocation between the mobile source base station and the mobile destination base station occurs. You can make a call.</p><p> According to the second mobile communication system of the present invention, when the control information of the mobile source base station and the mobile destination base station do not match, the gateway device is subsequently added to the voice data received from the mobile destination base station. The identifier is converted into an identifier indicating a data frame having the same structure in the control information of the source base station.</p><p> Therefore, even if control information is not inherited between the mobile source base station and the mobile destination base station, a voice call is made while maintaining transcoder-free operation (TrFO) when a relocation occurs between the mobile source base station and the mobile destination base station. It can be performed.</p>
<figref num="1">It is a figure which shows the structure of the mobile communication system which is composed of HNB / HNB-GW / CN.</figref><figref num="2">It is a block diagram which shows the internal structure of the HNB and the superordinate device in the mobile communication system of 1st Embodiment of this invention.</figref><figref num="3">It is a sequence diagram explaining the operation of the mobile communication system of 1st Embodiment of this invention.</figref><figref num="4">It is a block diagram which shows the internal structure of HNB and HNB-GW in the mobile communication system of 2nd Embodiment of this invention.</figref><figref num="5">It is a sequence diagram explaining the operation of the mobile communication system of the 2nd Embodiment of this invention.</figref><figref num="6">It is a figure which shows the RANAP: Relocation Required message modified by the 2nd Embodiment of this invention.</figref><figref num="7">It is a figure which shows the RANAP: Relocation Request message modified by the 2nd Embodiment of this invention.</figref><figref num="8">It is a state transition diagram of the Iu-UP Protocol modified by the second embodiment of the present invention.</figref><figref num="9">It is a block diagram which shows the internal structure of HNB and HNB-GW in the mobile communication system of 3rd Embodiment of this invention.</figref><figref num="10">It is a sequence diagram explaining the operation of the mobile communication system of the 3rd Embodiment of this invention.</figref><figref num="11">It is a figure which shows the RUA Direct Transfer message modified by the 3rd Embodiment of this invention.</figref><figref num="12">It is a block diagram which shows the internal structure of HNB and HNB-GW in the mobile communication system of 4th Embodiment of this invention.</figref><figref num="13">It is a sequence diagram explaining the operation of the mobile communication system of 4th Embodiment of this invention.</figref><figref num="14">It is a sequence diagram explaining the operation of the mobile communication system of the 5th Embodiment of this invention.</figref><figref num="15">It is a block diagram which shows the internal structure of the CN node in the mobile communication system of 6th Embodiment of this invention.</figref><figref num="16">It is a sequence diagram explaining the operation of the mobile communication system of the 6th Embodiment of this invention.</figref><figref num="17">It is a block diagram which shows the internal structure of HNB and HNB-GW in the mobile communication system of 7th Embodiment of this invention.</figref><figref num="18">It is a sequence diagram explaining the operation of the mobile communication system of 7th Embodiment of this invention.</figref><figref num="19">It is a block diagram which shows the internal structure of HNB and HNB-GW in the mobile communication system of 8th Embodiment of this invention.</figref><figref num="20">It is a sequence diagram explaining the operation of the mobile communication system of 8th Embodiment of this invention.</figref>
Hereinafter, embodiments of the present invention will be described with reference to the drawings.
In the embodiment described below, the overall configuration of the mobile communication system itself is the same as that shown in FIG. (First Embodiment) This embodiment is characterized by HNB-S2 and HNB-T3, and a higher-level device (hereinafter referred to as higher-level device 9) which is either HNB-GW4 or CN node 5. ..
In the present embodiment, the RFCI information of the HNB-S2 is notified from the HNB-S2 to the HNB-T3 via the host device 9.
Referring to FIG. 2, the HNB-S2 of the present embodiment includes a control unit 21A that includes the RFCI information of the HNB-S2 in the first message, and a transmission / reception unit 22A that transmits the first message to the host device 9. Has.
Further, the host device 9 of the present embodiment includes a transmission / reception unit 91A that receives the first message from the HNB-S2, and a control unit 92A that includes the RFCI information included in the first message in the second message. Then, the transmission / reception unit 91A transmits the second message to the HNB-T3.
Further, the HNB-T3 of the present embodiment initializes the RFID information of the transmission / reception unit 31A that receives the second message from the host device 9 and the HNB-T3, and sets (re-) the RFCI information included in the second message. It has a control unit 32A to be set).
Hereinafter, the operation of the mobile communication system of the present embodiment will be described with reference to the sequence diagram shown in FIG.
In step S101, the HNB-S2 transmits a first message including the RFCI information of the HNB-S2 to the host device 9.
In step S102, the host device 9 transmits a second message including the RFCI information included in the first message received from the HNB-S2 to the HNB-T3.
As described above, in the present embodiment, since the HNB-T3 can inherit the RFCI information from the HNB-S2 via the host device 9, the intra-HNB-GW relocation between the HNB-S2 and the HNB-T3 occurs. At times, the effect is that voice calls can be made while maintaining transcoder-free operation (TrFO). (Second Embodiment) This embodiment is an example in which the first embodiment is more embodied by using the host device 9 as HNB-GW4.
In this embodiment, the RFCI information of HNB-S2 is notified from HNB-S2 to HNB-T3 via HNB-GW4 by a RANAP message.
Referring to FIG. 4, the HNB-GW4 of the present embodiment has an HNB transmission / reception unit 41B, a RANAP function unit 42B, a CN transmission / reception unit 43B, an Iu-UP frame control unit 44B, and an Iu-UP frame transfer unit. It has 45B and an RFCI holding unit 46B. In FIG. 4, the HNB transmission / reception unit 41B constitutes the transmission / reception unit 91A of FIG. 2, and the other functional blocks constitute the control unit 92A of FIG.
Further, the HNB-S2 of the present embodiment includes an HNB-GW transmission / reception unit 21B, a RANAP function unit 22B, an Iu-UP frame control unit 23B, and an Iu-UP frame transfer unit 24B. In FIG. 4, the HNB-GW transmission / reception unit 21B constitutes the transmission / reception unit 22A of FIG. 2, and the other functional blocks constitute the control unit 21A of FIG.
Further, the HNB-T3 of the present embodiment includes an HNB-GW transmission / reception unit 31B, a RANAP function unit 32B, an Iu-UP frame control unit 33B, and an Iu-UP frame transfer unit 34B. In FIG. 4, the HNB-GW transmission / reception unit 31B constitutes the transmission / reception unit 31A of FIG. 2, and the other functional blocks constitute the control unit 32A of FIG.
The HNB transmitter / receiver 41B has an interface for connecting to HNB-S2 and HNB-T3, and transmits / receives audio data to / from HNB-S2 and HNB-T3.
The RANAP functional units 22B, 32B, and 42B realize the RANAP (Radio Access Network Application Part) protocol function specified in 3GPP TS25.413 (Non-Patent Document 3). For example, the RANAP function units 22B, 32B, 42B have a function of generating a RANAP message and a function of terminating the RANAP message.
The CN transmission / reception unit 43B has an interface for connecting to the CN node 5 and transmits / receives voice data between the CN nodes 5.
The Iu-UP frame control units 23B, 33B, 44B realize the Iu-UP protocol function specified in 3GPP TS25.415 (Non-Patent Document 2). For example, the Iu-UP frame control units 23B, 33B, 44B have a function of generating an Iu-UP Initialization message (hereinafter abbreviated as Iu-UP Init message) and a function of terminating the Iu-UP Init message. .. In addition, the Iu-UP frame control unit 44B has a function to notify the RFCI information contained in the Iu-UP Init message to the RFCI holder 46B, and the RFCI holder when the Iu-UP Initialization is restarted. It has a function to request comparison of RFCI information to 46B.
The Iu-UP frame transfer units 24B, 34B, 45B realize the Iu-UP protocol function specified in 3GPP TS25.415 (Non-Patent Document 2). For example, the Iu-UP frame transfer units 24B, 34B, 45B have a function of transferring Iu-UP frame data.
The RFCI holding unit 46B has a function of holding the RFCI information notified from the Iu-UP frame control unit 44B and a function of notifying the comparison result based on the comparison request of the RFCI information from the Iu-UP frame control unit 44B. Has.
The HNB-GW transmission / reception units 21B and 31B have an interface for connecting to the HNB-GW4 and transmit / receive voice data to / from the HNB-GW4.
Here, two current provisions of 3GPP related to this embodiment will be described. (1) First provision 3GPP TS25.415 (Non-Patent Document 2) sets the RAB parameter for radio access bearer (RAB) between UE and CN between CN and RNC (HNB-GW). It is stipulated to notify by message. Specifically, the RAB parameter is a QoS (Quality of Service) parameter (data transmission rate, block size, error rate, etc.) according to the type of service.
However, RAB parameters are closely related to the RFCI information exchanged by the Iu-UP Initialization message, and only the RFCI information is changed by restarting Iu-UP Initialization without changing the RAB parameters (RAB Modifiation). If so, there is a risk of state inconsistency.
Therefore, 3GPP TS25.415 (Non-Patent Document 2) stipulates that Iu-UP Initialization must not be restarted from the same SRNS except for RAB Modifiation in order to prevent such a procedure from occurring. (1st provision).
If the function of taking over RFCI information by Iu-UP Initialization message in the existing mobile communication system composed of Node-B / RNC / CN is changed to the mobile communication system composed of HNB / HNB-GW / CN. When applied, Iu-UP Initialization will be invoked for CN6 from each of HNB-S2 and HNB-T3 in Figure 1. However, in this case, from the viewpoint of CN6, Iu-UP Initialization was restarted by the same SRNS (HNB-GW4), which violates the first provision. (2) Second provision It is considered that the problem of the first provision above can be solved by terminating the Iu-UP Initialization message at HNB-GW (that is, not at CN).
However, in 3GPP TS25.467 (Non-Patent Document 4), when the Iu-UP message is terminated at HNB-GW, there is a concern that the signal processing at HNB-GW will increase and the processing will become complicated, so Iu-UP It is stipulated that protocol messages should not be terminated by HNB-GW (second specification). Therefore, if the Iu-UP Initialization message is terminated by HNB-GW, the second rule is violated.
In this embodiment, transcoder-free operation (TrFO) was maintained when the intra-HNB-GW relocation between HNB-S2 and HNB-T3 occurred without changing the first and second provisions above. It makes it possible to make a voice call as it is.
Hereinafter, the operation of the present embodiment will be described with reference to the sequence diagram shown in FIG.
First, in step S201, HNB-S2 starts the Relocation procedure by sending a RANAP: Relocation Required message requesting the movement of UE1 from HNB-S2 to HNB-GW4.
In this embodiment, the RFCI information of the Iu-UP Init message is added to the RANAP: Relocation Required message of 9.1.9 of 3GPP TS 25.413 (Non-Patent Document 3). FIG. 6 shows the RANAP: Relocation Required message modified by this embodiment. Note that FIG. 6 shows only the changed parts. The RANAP: Relocation Required message of the present embodiment includes the RFCI value "RFCI", the number of subflows constituting the data frame indicated by the RFCI value "RCFI Subflow", and the data size for each subflow "Length". "of Subflow" is added as RFCI information.
HNB-GW4 terminates the RANAP: Relocation Required message at the RANAP function unit 42B and acquires RFCI information.
Further, in step S202, HNB-GW4 requests the allocation of resources of HNB-T3 by sending a RANAP: Relocation Request message requesting the movement of UE1 to HNB-T3 to HNB-T3.
In the present embodiment, if the RANAP: Relocation Required message contains RFCI information in step S201, the RANAP function unit 42B acquires the RFCI information and includes the RFCI information in the RANAP: Relocation Request message.
That is, in the present embodiment, RFCI information is added to the RANAP: Relocation Request message of 9.1.10 of 3GPP TS 25.413 (Non-Patent Document 3). FIG. 7 shows a RANAP: Relocation Request message modified by the present embodiment. Note that FIG. 7 shows only the changed parts. Similar to the RANAP: Relocation Required message in FIG. 6, the RANAP: Relocation Request message of the present embodiment includes the RFCI value "RFCI" and the number of subflows constituting the data frame indicated by the RFCI value "RCFI Subflow". "And" Length of Subflow ", which is the data size for each subflow, are added as RFCI information.
HNB-T3 terminates the RANAP: Relocation Request message at the RANAP function unit 32B. If the RANAP: Relocation Request message contains RFCI information, HNB-T3 initializes the RFCI information of HNB-T3 and resets it to the RFCI information included in the RANAP: Relocation Request message.
As a result, when the HNB-T3 subsequently receives the uplink audio data from UE1 and the downlink audio data from CN6, the structure of the data frame of the audio data is determined by the RFCI value added to the audio data. , And even the rate can be recognized correctly.
Further, in the present embodiment, in the state transition diagram of the Iu-UP Protocol of 3GPP TS25.415 (Non-Patent Document 2) regarding the state transition of HNB-T3, the "Support Mode Data Transfer Ready" state is directly changed from the "NULL" state. Add a condition to transition to. FIG. 8 shows an image of the Iu-UP Protocol state transition diagram modified by the present embodiment. Figure 8 shows that when a RANAP: Relocation Request message containing RFCI information (in Figure 8, it is referred to as Intra-HNB-GW Relocation-Req) is received, the status changes from "NULL" to "Support Mode Data Transfer Ready" directly. It means to make a transition.
As a result, even if the Iu-UP Initialization procedure is not executed, when the HNB-T3 receives the RANAP: Relocation Request message, it triggers the state of the Iu-UP frame transfer unit 33B from the "NULL" state. , "Support Mode Data Transfer Ready" is entered and Iu-UP frame data can be transferred.
In the present embodiment, the signal name for transitioning from the "NULL" state to the "Support Mode Data Transfer Ready" state is Intra-HNB-GW Relocation-Req, but the signal name is not limited to this.
The following steps S203 to S211 are well known as one of the proposed studies of the Intra HNB-GW Relocation procedure currently under study in the mobile communication system composed of HNB / HNB-GW / CN, and the present invention Not directly related to.
After executing step S202, HNB-T3 responds to the RANAP: Relocation Request message by sending a RANAP: Relocation Request ACK message to HNB-GW4 in step S203.
Next, in step S204, HNB-GW4 instructs the start of Relocation by sending a Relocation command message to HNB-S2.
Next, in step S205, HNB-S2 instructs UE1 to reconfigure the radio channel by transmitting an RRC: Reconfiguration message to UE1.
Next, in step S206, the HNB-T3 detects the UE1 by synchronizing with the wireless layer 1, and notifies that the UE1 has been detected by transmitting a Relocation Detect message to the HNB-GW4.
Next, in step S207, UE1 notifies that the allocation of radio resources is completed by sending an RRC: Reconfiguration Complete message to HNB-T3.
Next, in step S208, HNB-T3 notifies that Relocation is completed by sending a RANAP: Relocation Complete message to HNB-GW4.
Next, in step S209, HNB-GW4 requests the release of the resources of HNB-S2 by sending a RANAP: Iu Release Command message to HNB-S2.
Next, in step S210, HNB-S2 notifies that the resources of HNB-S2 have been released by sending a RANAP: Iu Release Complete message to HNB-GW4.
After that, UE1 transmits / receives voice data (user data) to / from HNB-GW4 via HNB-T3 in step S211.
As described above, in the present embodiment, the HNB-S2 notifies the HNB-GW4 of the RFCI information of the HNB-S2 by the RANAP: Relocation Required message, and the HNB-GW4 notifies the RFCI information of the HNB-S2 by the RANAP: Relocation Required message. Since the HNB-T3 is notified by the Relocation Request message, the HNB-T3 can inherit the RFCI information from the HNB-S2 without performing the Iu-UP Initialization procedure.
In addition, HNB-T3 uses the reception of the RANAP: Relocation Request message from HNB-GW4 as a trigger to transition to a state in which voice data can be transferred, so voice data can be transferred without executing the Iu-UP Initialization procedure. It will be possible to send.
Therefore, the HNB-T3 can take over the RFCI information from the HNB-S2 and transmit the audio data without performing the Iu-UP Initialization procedure. Therefore, the intra- between the HNB-S2 and the HNB-T3 Even when HNB-GW relocation occurs, voice calls can be made while maintaining transcoder-free operation (TrFO).
Further, in this embodiment, since it is not necessary to execute the Iu-UP Initialization procedure, it is necessary to change the first provision that does not allow the restart of Iu-UP Initialization from the same SRNS (HNB-GW4) in 3GPP. There is no.
Further, in the present embodiment, since it is not necessary to terminate the Iu-UP Initialization message at HNB-GW, there is also a second provision in 3GPP that does not allow the message of the Iu-UP protocol to be terminated at HNB-GW. No need to change.
Further, in the present embodiment, since the RANAP message is used for the notification of RFCI information, the following merits can be obtained. (1) First merit RANAP message is stipulated in 3GPP TS 25.467 (Non-Patent Document 4) to be terminated at HNB and HNB-GW. Therefore, there is an advantage that it is not necessary to newly support a protocol in order to add the function related to the present embodiment to the RANAP message. (2) Second merit Currently, 3GPP is considering the Intra HNB-GW Relocation procedure, but it is common to use a RANAP message for the signal of this procedure. Therefore, by adding the function related to this embodiment to the RANAP message, there is an advantage that it is not necessary to add a new signal to the Intra HNB-GW Relocation procedure. (Third Embodiment) This embodiment is an example in which the first embodiment is more embodied by using the host device 9 as the HNB-GW4.
In this embodiment, the RFCI information of HNB-S2 is notified from HNB-S2 to HNB-T3 via HNB-GW4 by the Direct Transfer message of RANAP User Adaption (hereinafter abbreviated as RUA).
RUA is defined in 3GPP TS 25.468 (Non-Patent Document 5). The RUA Direct Transfer message is a message used to transfer a RANAP message.
Referring to FIG. 9, the HNB-GW4 of the present embodiment is different from the HNB-GW4 of the second embodiment shown in FIG. 4 in that the RUA functional unit 47B is added. The RUA functional unit 47B is one of the constituent elements of the control unit 92A in FIG.
Further, the HNB-S2 of the present embodiment is different from the HNB-S2 of the second embodiment shown in FIG. 4 in that the RUA functional unit 25B is added. The RUA function unit 25B is one of the constituent elements of the control unit 21A in FIG.
Further, the HNB-T3 of the present embodiment is different from the HNB-T3 of the second embodiment shown in FIG. 4 in that the RUA functional unit 35B is added. The RUA function unit 35B is one of the constituent elements of the control unit 32A in FIG.
The RUA function units 25B, 35B, 47B realize the RUA protocol function specified in 3GPP TS 25.468 (Non-Patent Document 5). For example, the RUA functional units 25B, 35B, 47B have a function of generating a RUA message and a function of terminating the RUA message.
Hereinafter, the operation of this embodiment will be described with reference to the sequence diagram shown in FIG.
First, in step S301, HNB-S2 starts the Relocation procedure by sending a RANAP: Relocation Required message requesting the movement of UE1 from HNB-S2 to HNB-GW4.
In the present embodiment, when the RANAP: Relocation Required message is transmitted, the RUA Direct Transfer message for transferring the RANAP: Relocation Required message is also transmitted.
Further, in the present embodiment, the RFCI information of the Iu-UP Init message is added to the RUA Direct Transfer message of 9.1.4 of 3GPP TS 25.468 (Non-Patent Document 5). FIG. 11 shows a RUA Direct Transfer message modified by the present embodiment. Note that FIG. 11 shows only the changed parts. The RUA Direct Transfer message of the present embodiment includes the RFCI value "RFCI", the number of subflows constituting the data frame indicated by the RFCI value "RCFI Subflow", and the data size for each subflow "Length of". "Subflow" is added as RFCI information.
HNB-GW4 terminates the RANAP: Relocation Required message at the RANAP functional unit 42B and terminates the RUA Direct Transfer message at the RUA functional unit 47B to acquire RFCI information.
Further, in step S302, the HNB-GW4 requests the HNB-T3 to secure resources by sending a RANAP: Relocation Request message requesting the movement of the UE1 to the HNB-T3 to the HNB-T3.
In the present embodiment, when the RANAP: Relocation Request message is transmitted, the RUA Direct Transfer message for transferring the RANAP: Relocation Request message is also transmitted.
Further, in the present embodiment, if the RUA Direct Transfer message contains RFCI information in step S301, the RUA functional unit 47B acquires the RFCI information and includes the RFCI information in the RUA Direct Transfer message. The RUA Direct Transfer message at this time is the same as that shown in FIG.
HNB-T3 terminates the RANAP: Relocation Request message at the RANAP function unit 32B and terminates the RUA Direct Transfer message at the RUA function unit 35B. If the RUA Direct Transfer message contains RFCI information, HNB-T3 initializes the RFCI information of HNB-T3 and resets it to the RFCI information contained in the RUA Direct Transfer message.
As a result, when the HNB-T3 subsequently receives the uplink audio data from UE1 and the downlink audio data from CN6, the structure of the data frame of the audio data is determined by the RFCI value added to the audio data. , And even the rate can be recognized correctly.
Further, in the present embodiment, in the state transition diagram (see FIG. 8) of the Iu-UP Protocol of 3GPP TS25.415 (Non-Patent Document 2) regarding the state transition of HNB-T3, the "Support Mode" is directly applied from the "NULL" state. As a condition for transitioning to the "Data Transfer Ready" state, a condition for receiving a RUA Direct Transfer message containing RFCI information (intra-HNB-GW Relocation-Req in Fig. 8) is added.
As a result, even if the Iu-UP Initialization procedure is not executed, the HNB-T3 triggers the reception of the RUA Direct Transfer message and changes the state of the Iu-UP frame transfer unit 33B from the "NULL" state to the "Support Mode". It transitions to the Data Transfer Ready "state and becomes a state where Iu-UP frame data can be transferred.
The subsequent processes of steps S303 to S311 are the same as the processes of steps S203 to S211 of FIG.
As described above, in the present embodiment, the HNB-S2 notifies the HNB-S2 of the RFCI information of the HNB-S2 to the HNB-GW4 by a RUA Direct Transfer message, and the HNB-GW4 notifies the RFCI information of the HNB-S2 to the RUA Direct Transfer. Since the message notifies HNB-T3, HNB-T3 can inherit the RFCI information from HNB-S2 without performing the Iu-UP Initialization procedure.
In addition, HNB-T3 uses the reception of the RUA Direct Transfer message from HNB-GW4 as a trigger to transition to a state in which voice data can be transferred, so voice data can be transmitted without performing the Iu-UP Initialization procedure. It becomes possible to do.
Therefore, the HNB-T3 can take over the RFCI information from the HNB-S2 and transmit the audio data without performing the Iu-UP Initialization procedure. Therefore, the intra- between the HNB-S2 and the HNB-T3 Even when HNB-GW relocation occurs, voice calls can be made while maintaining transcoder-free operation (TrFO).
Further, in this embodiment, since it is not necessary to execute the Iu-UP Initialization procedure, it is necessary to change the first provision that does not allow the restart of Iu-UP Initialization from the same SRNS (HNB-GW4) in 3GPP. There is no.
Further, in the present embodiment, since it is not necessary to terminate the Iu-UP Initialization message at HNB-GW, there is also a second provision in 3GPP that does not allow the message of the Iu-UP protocol to be terminated at HNB-GW. No need to change. (Fourth Embodiment) This embodiment is an example in which the first embodiment is more embodied by using the host device 9 as the HNB-GW4.
In this embodiment, the RFCI information of HNB-S2 is notified from HNB-S2 to HNB-T3 via HNB-GW4 by the Relocation message of Home Node B Application Part (hereinafter, abbreviated as HNBAP).
HNBAP is defined in 3GPP TS 25.469 (Non-Patent Document 6). However, the HNBAP Relocation message is not specified in 3GPP and is well known as one of the proposals in the Intra HNB-GW relocation procedure currently under consideration, and is not directly related to the present invention.
Referring to FIG. 12, the HNB-GW4 of the present embodiment is different from the HNB-GW4 of the second embodiment shown in FIG. 4 in that the HNB AP functional unit 48B is added. The HNBAP functional unit 48B is one of the constituent elements of the control unit 92A in FIG.
Further, the HNB-S2 of the present embodiment is different from the HNB-S2 of the second embodiment shown in FIG. 4 in that the HNB AP functional unit 26B is added. The HNBAP functional unit 26B is one of the constituent elements of the control unit 21A in FIG.
Further, the HNB-T3 of the present embodiment is different from the HNB-T3 of the second embodiment shown in FIG. 4 in that the HNB AP functional unit 36B is added. The HNBAP functional unit 36B is one of the constituent elements of the control unit 32A in FIG.
The HNBAP function units 26B, 36B, 48B realize the HNBAP protocol function specified in 3GPP TS 25.469 (Non-Patent Document 6). For example, the HNBAP functional units 26B, 36B, 48B have a function of generating an HNBAP message and a function of terminating the HNBAP message.
Hereinafter, the operation of the present embodiment will be described with reference to the sequence diagram shown in FIG.
First, in step S401, HNB-S2 starts the Relocation procedure by sending an HNBAP: Relocation Required message requesting the movement of UE1 from HNB-S2 to HNB-GW4.
In this embodiment, the RFCI information of the Iu-UP Init message is added to this HNBAP: Relocation Required message. RFCI information can be added to HNBAP: Relocation Required at this time, as in FIG. 11, for example.
HNB-GW4 terminates the HNBAP: Relocation Required message at the HNBAP function unit 48B and acquires RFCI information.
Further, in step S402, the HNB-GW4 requests the HNB-T3 to secure the resources by sending the HNBAP: Relocation Request message requesting the movement of the UE1 to the HNB-T3 to the HNB-T3.
In the present embodiment, if the HNBAP: Relocation Required message contains RFCI information in step S401, the HNBAP functional unit 48B acquires the RFCI information and includes the RFCI information in the HNBAP: Relocation Request message. RFCI information can be added to the HNBAP: Relocation Request message at this time, as in FIG. 11, for example.
HNB-T3 terminates the HNBAP: Relocation Request message at the HNBAP function unit 36B. If the HNBAP: Relocation Request message contains RFCI information, HNB-T3 initializes the RFCI information of HNB-T3 and resets it to the RFCI information included in the HNBAP: Relocation Request message.
As a result, when the HNB-T3 subsequently receives the uplink audio data from UE1 and the downlink audio data from CN6, the structure of the data frame of the audio data is determined by the RFCI value added to the audio data. , And even the rate can be recognized correctly.
Further, in the present embodiment, in the state transition diagram (see FIG. 8) of the Iu-UP Protocol of 3GPP TS25.415 (Non-Patent Document 2) regarding the state transition of HNB-T3, the "Support Mode" is directly applied from the "NULL" state. As a condition for transitioning to the "Data Transfer Ready" state, a condition for receiving an HNBAP: Relocation Request message containing RFCI information (intra-HNB-GW Relocation-Req in Fig. 8) is added.
As a result, even if the Iu-UP Initialization procedure is not executed, the HNB-T3 triggers the reception of the HNBAP: Relocation Request message to change the status of the Iu-UP frame transfer unit 33B from the "NULL" status to "Support". Mode Data Transfer Ready "Transitions to the state where Iu-UP frame data can be transferred.
Subsequent processes in steps S403 to S411 are the same as those in steps S203 to S211 in FIG.
As described above, in the present embodiment, the HNB-S2 notifies the HNB-GW4 of the RFCI information of the HNB-S2 by the HNBAP: Relocation Required message, and the HNB-GW4 notifies the RFCI information of the HNB-S2 by the HNBAP: Relocation Required message. Since the HNB-T3 is notified by the Relocation Request message, the HNB-T3 can inherit the RFCI information from the HNB-S2 without performing the Iu-UP Initialization procedure.
In addition, since the HNB-T3 transitions to a state in which voice data can be transferred by triggering the reception of the HNBAP: Relocation Request message from the HNB-GW4, the voice data can be transferred without executing the Iu-UP Initialization procedure. It will be possible to send.
Therefore, the HNB-T3 can take over the RFCI information from the HNB-S2 and transmit the audio data without performing the Iu-UP Initialization procedure. Therefore, the intra- between the HNB-S2 and the HNB-T3 Even when HNB-GW relocation occurs, voice calls can be made while maintaining transcoder-free operation (TrFO).
Further, in this embodiment, since it is not necessary to execute the Iu-UP Initialization procedure, it is necessary to change the first provision that does not allow the restart of Iu-UP Initialization from the same SRNS (HNB-GW4) in 3GPP. There is no.
Further, in the present embodiment, since it is not necessary to terminate the Iu-UP Initialization message at HNB-GW, there is also a second provision in 3GPP that does not allow the message of the Iu-UP protocol to be terminated at HNB-GW. No need to change. (Fifth Embodiment) This embodiment is an example in which the first embodiment is more embodied by using the host device 9 as the HNB-GW4. Further, the configuration of the present embodiment is the same as the configuration of the second embodiment shown in FIG.
In the present embodiment, the HNB-GW4 notifies the HNB-T3 of the RFCI information of the HNB-S2 by the Iu-UP Init message when the UE1 is relocated from the HNB-S2 to the HNB-T3. The Iu-UP Init message is sent and received between the HNB and the HNB-GW when the HNB tries to establish communication with the HNB that has the terminal of the UE communication partner under its control, such as when a Relocation occurs. Message.
Iu-UP Ver2 of 3GPP TS25.415 (Non-Patent Document 2) stipulates that Iu-UP Init messages should be sent from CN to RNC. However, this provision presupposes a mobile communication system consisting of 3GPP's existing Node-B / RNC / CN.
Therefore, it is necessary to enable the Iu-UP Init message to be transmitted from CN to HNB-GW even in a mobile communication system composed of HNB / HNB-GW / CN, but 3GPP TS25.467 (Non-Patent Document 4) ) Specifies that Iu-UP protocol messages are not terminated at HNB-GW.
Therefore, in this embodiment, the provisions of 3GPP are changed to allow Iu-UP messages to be terminated at HNB-GW.
Hereinafter, the operation of the present embodiment will be described with reference to the sequence diagram shown in FIG.
In FIG. 14, it is assumed that the HNB-GW4 has acquired the RFCI information of the HNB-S2 in advance. That is, when establishing communication between HNB-S2 and HNB-X8, HNB-S2 sends an Iu-UP Init message containing RFCI information of HNB-S2 to HNB-GW4, which causes it. , HNB-GW4 has acquired the RFCI information of HNB-S2. This procedure was performed prior to step S501 in FIG. 14 and is not shown in FIG.
First, the processing of steps S501 and S502 similar to the processing of steps S201 and S202 of FIG. 5 is performed.
The HNB-T3 then sends an Iu-UP Init message containing the RFCI information of the HNB-T3 to the HNB-GW4 in step S503. HNB-GW4 terminates the Iu-UP Init message at the Iu-UP frame control unit 44B, and the RFCI information of HNB-T3 included in the Iu-UP Init message and the RFCI information of HNB-S2 acquired in advance. Make a comparison with.
Next, in step S504, the HNB-GW4 responds to the Iu-UP Init message by transmitting the Iu-UP Init ACK message to the HNB-T3.
If the RFCI information of HNB-S2 and HNB-T3 does not match in step S503, HNB-GW4 matches the RFCI information of HNB-T3 with the RFCI information of HNB-S2, so that HNB-S2 in step S505. Send an Iu-UP Init message containing RFCI information to HNB-T3.
Next, in step S506, the HNB-T3 responds to the Iu-UP Init message by transmitting the Iu-UP Init ACK message to the HNB-GW4. In addition, HNB-T3 initializes the RFCI information of HNB-T3 and resets it to the RFCI information of HNB-S2 included in the Iu-UP Init message.
Subsequent processes of steps S507 to S515 are the same as the processes of steps S203 to S211 of FIG.
As described above, in the present embodiment, the HNB-GW4 notifies the HNB-T3 of the RFCI information of the HNB-S2 by the Iu-UP Init message, so that the HNB-T3 inherits the RFCI information from the HNB-S2. Becomes possible.
Therefore, even when intra-HNB-GW relocation occurs between HNB-S2 and HNB-T3, voice calls can be made while maintaining transcoder-free operation (TrFO).
Further, the description in 7.2 of 3GPP TS25.467 (Non-Patent Document 4), which is changed by the present embodiment, is as follows.
Iu-UP terminates only at CN, HNB, and HNB-GW.
In addition, the description of Iu-UP Ver2 in 6.5.2 of 3GPP TS25.415 (Non-Patent Document 2), which is changed by this embodiment, is as follows.
The Initialization procedure can be controlled by two Iu access points, both CN and UTRAN.
The Initialization procedure is indicated by the control function of the Iu-UP procedure, that is, when SRNS is relocated or RAB is established on Iu, or when CN or HNB-GW is performing TrFO, RFCI mismatch. Triggered when trying to resolve. The Initialization procedure cannot be restarted by SRNC for RAB without requesting RAB Modifiation by RANAP.
In addition, in Iu-UP Ver1 of 3GPP TS25.415 (Non-Patent Document 2), although it is stipulated that the Iu-UP Init message is sent from RNC to CN, the Iu-UP Init message is sent from CN to RNC. Sending is not specified. Therefore, the provisions of Iu-UP Ver1 may be revised in the same way as Iu-UP Ver2.
In this case, the description of Iu-UP Ver1 in 6.5.2 of 3GPP TS25.415 (Non-Patent Document 2), which is changed by this embodiment, is as follows.
The Initialization procedure can be controlled by two Iu access points, both CN and UTRAN.
The Initialization procedure is indicated by the control function of the Iu-UP procedure, that is, when SRNS is relocated or RAB is established on Iu, or when CN or HNB-GW is performing TrFO, RFCI mismatch. Triggered when trying to resolve. The Initialization procedure cannot be restarted by SRNC for RAB without requesting RAB Modifiation by RANAP. (Sixth Embodiment) This embodiment is an example in which the first embodiment is more embodied with the host device 9 as the CN node 5.
In the present embodiment, the CN node 5 notifies the HNB-T3 of the RFCI information of the HNB-S2 by the Iu-UP Init message at the time of the relocation process from the HNB-S2 of the UE1 to the HNB-T3.
That is, in the present embodiment, the CN node 5 performs the operation performed by the HNB-GW4 in the third embodiment, and the HNB-GW4 exchanges between the HNB-S2 / HNB-T3 and the CN node 5. Only forward the RANAP and Iu-UP Init messages that are sent, without terminating them.
However, the current 3GPP TS25.415 (Non-Patent Document 2) stipulates that restarting Iu-UP Initialization when Intra HNB-GW relocation occurs is not allowed.
Therefore, in this embodiment, the provisions of 3GPP are changed to allow the restart of Iu-UP Initialization even when Intra HNB-GW relocation occurs.
Referring to FIG. 15, the CN node 5 of the present embodiment includes the HNB-GW transmission / reception unit 51C for HNB-GW4, the RANAP function unit 52C, the HNB-GW transmission / reception unit 53C for HNB-GW7, and Iu. It has a -UP frame control unit 54C, an Iu-UP frame transfer unit 55C, and an RFCI holding unit 56C. In FIG. 15, the HNB-GW transmission / reception unit 51C constitutes the transmission / reception unit 91A of FIG. 2, and the other functional blocks constitute the control unit 92A of FIG.
The configurations of HNB-S2 and HNB-T3 of this embodiment are the same as the configurations of HNB-S2 and HNB-T3 of the second embodiment shown in FIG.
The HNB-GW transmission / reception unit 51C has an interface for connecting to the HNB-GW4 and transmits / receives voice data to / from the HNB-GW4.
The HNB-GW transmission / reception unit 53C has an interface for connecting to the HNB-GW7, and transmits / receives voice data to / from the HNB-GW7.
The other RANAP function unit 52C, Iu-UP frame control unit 54C, Iu-UP frame transfer unit 55C, and RFCI holding unit 56C are the RANAP function unit 42B and Iu-UP frame control unit shown in FIG. 4, respectively. Performs the same operation as 44B, Iu-UP frame transfer unit 45B, and RFCI holding unit 46B.
Hereinafter, the operation of the present embodiment will be described with reference to the sequence diagram shown in FIG.
In FIG. 16, it is assumed that the CN node 5 has acquired the RFCI information of the HNB-S2 in advance. That is, when establishing communication between HNB-S2 and HNB-X8, HNB-S2 sends an Iu-UP Init message containing RFCI information of HNB-S2 to CN node 5 via HNB-GW4. As a result, CN node 5 has acquired the RFCI information of HNB-S2. This procedure was performed prior to step S601 in FIG. 16 and is not shown in FIG.
First, in steps S201 and S202 of FIG. 5, the same processing as that performed by HNB-S2, HNB-T3, and HNB-GW4 is performed, but in steps S601 and S602, HNB-S2, HNB-T3, and Performed by CN node 5.
Next, in step S603, the HNB-T3 transmits an Iu-UP Init message containing the RFCI information of the HNB-T3 to the CN node 5 via the HNB-GW4. CN node 5 terminates the Iu-UP Init message at the Iu-UP frame control unit 54C, and the RFCI information of HNB-T3 included in the Iu-UP Init message and the RFCI information of HNB-S2 acquired in advance. Make a comparison with.
Next, in step S604, the CN node 5 responds to the Iu-UP Init message by transmitting the Iu-UP Init ACK message to the HNB-T3 via the HNB-GW4.
If the RFCI information of HNB-S2 and HNB-T3 does not match in step S603, CN node 5 matches the RFCI information of HNB-T3 with the RFCI information of HNB-S2, so that HNB-S2 in step S605. Send an Iu-UP Init message containing RFCI information to HNB-T3 via HNB-GW4.
Next, in step S606, the HNB-T3 responds to the Iu-UP Init message by transmitting the Iu-UP Init ACK message to the CN node 5 via the HNB-GW4. In addition, HNB-T3 initializes the RFCI information of HNB-T3 and resets it to the RFCI information of HNB-S2 included in the Iu-UP Init message.
In the subsequent steps S607 to S615, the processing performed by UE1, HNB-S2, HNB-T3, and CN node 5 is performed in steps S203 to S211 of FIG. 5, UE1, HNB-S2, HNB-T3, and HNB-. It is the same as the processing performed by GW4.
As described above, in the present embodiment, the CN node 5 notifies the HNB-T3 of the RFCI information of the HNB-S2 by the Iu-UP Init message, so that the HNB-T3 inherits the RFCI information from the HNB-S2. Becomes possible.
Therefore, even when intra-HNB-GW relocation occurs between HNB-S2 and HNB-T3, voice calls can be made while maintaining transcoder-free operation (TrFO).
The description of Iu-UP Ver1 in 6.5.2 of 3GPP TS25.415 (Non-Patent Document 2), which is changed by this embodiment, is as follows.
The Initialization procedure cannot be restarted for RAB without requesting RAB Modifiation by RANAP or without Intra HNB-GW relocation.
In addition, the description of Iu-UP Ver2 in 6.5.2 of 3GPP TS25.415 (Non-Patent Document 2), which is changed by this embodiment, is as follows.
The Initialization procedure cannot be restarted for RAB without requesting RAB Modifiation by RANAP or without Intra HNB-GW relocation. (7th Embodiment) The mobile communication system of this embodiment is characterized by HNB-S2, HNB-T3, and HNB-GW4.
In this embodiment, each of HNB-S2 and HNB-T3 notifies HNB-GW4 of RFCI information, and when HNB-GW4 does not match the RFCI information of HNB-S2 and HNB-T3, from HNB-T3. The RFCI value added to the received audio data is converted into an RFCI value indicating a data frame having the same structure in the RFCI information of HNB-S2.
Referring to FIG. 17, the HNB-S2 of the present embodiment includes a control unit 21D that includes the RFCI information of the HNB-S2 in the first message, and a transmission / reception unit 22D that transmits the first message to the HNB-GW4. Has.
Further, the HNB-T3 of the present embodiment includes a control unit 31D that includes the RFCI information of the HNB-T3 in the second message, and a transmission / reception unit 32D that transmits the second message to the HNB-GW4.
Further, the HNB-GW4 of the present embodiment receives the first message from the HNB-S2 and the second message from the HNB-T3, the first transmission / reception unit 41D, and the HNB included in the first message. -If the storage unit 42D that stores the RFCI information of S2 and the RFCI information of HNB-T3 included in the second message does not match the RFCI information of HNB-S2 and HNB-T3, then the voice from HNB-T3 When data is received, the RFCI value added to the audio data is converted into an RFCI value that indicates a data frame with the same structure as the audio data in the RFCI information of HNB-S2. It also has a second transmission / reception unit 44D that transmits voice data to which the RFCI value converted by the control unit 43D is added to CN6.
Hereinafter, the operation of the mobile communication system of the present embodiment will be described with reference to the sequence diagram shown in FIG.
In step S701, the HNB-S2 transmits a first message containing the RFCI information of the HNB-S2 to the HNB-GW4.
In step S702, the HNB-T3 transmits a second message containing the RFCI information of the HNB-T3 to the HNB-GW4.
The HNB-GW4 stores the RFCI information of HNB-S2 included in the first message and the RFCI information of HNB-T3 included in the second message in the storage unit 42D. Also, compare the RFCI information of HNB-S2 and HNB-T3.
After that, in step S703, UE1 transmits / receives voice data (user data) to / from HNB-GW4 via HNB-T3.
At this time, if the RFCI information of HNB-S2 and HNB-T3 does not match, when HNB-GW4 receives voice data from HNB-T3, the RFCI value added to the voice data is set to HNB-S2. Performs RFCI conversion to convert to an RFCI value that indicates a data frame with the same structure as the audio data in the RFCI information of.
Then, the HNB-GW4 transmits the voice data to which the RFCI-converted RFCI value is added to the CN6.
If the RFCI information of HNB-S2 and HNB-T3 match, HNB-GW4 transmits the voice data received from HNB-T3 and the RFCI value added to the voice data to CN6 as it is. To do.
As described above, in the present embodiment, when the RFCI information of HNB-S2 and HNB-T3 does not match, the HNB-GW4 subsequently sets the RFCI value added to the voice data received from the HNB-T3 to the HNB. -Convert to an RFCI value that indicates a data frame with the same structure in the RFC I information in S2.
Therefore, even if RFCI information is not inherited between HNB-S2 and HNB-T3, voice calls can be made while maintaining transcoder-free operation (TrFO) when intra-HNB-GW relocation occurs between HNB. .. (8th Embodiment) This embodiment is an example in which the 7th embodiment is more embodied.
In this embodiment, each of HNB-S2 and HNB-T3 notifies HNB-GW4 of RFCI information by an Iu-UP Init message, and HNB-GW4 matches the RFCI information of HNB-S2 and HNB-T3. If not, the RFCI value added to the audio data received from HNB-T3 is converted to the RFCI value indicating the data frame of the same structure in the RFCI information of HNB-S2.
However, the UTRAN architecture for 3G Home NodeB of 3GPP TS25.467 (Non-Patent Document 4) stipulates that Iu-UP protocol messages are not terminated at HNB-GW.
Therefore, in this embodiment, the provisions of 3GPP are changed to allow Iu-UP messages to be terminated at HNB-GW.
Referring to FIG. 19, the HNB-GW4 of the present embodiment has an HNB transmission / reception unit 41E, a RANAP function unit 42E, a CN transmission / reception unit 43E, an Iu-UP frame control unit 44E, and an Iu-UP frame transfer unit. It has 45E, an RFCI holding unit 46E, and an RFCI conversion unit 47E. In FIG. 19, the HNB transmission / reception unit 41E constitutes the first transmission / reception unit 41D in FIG. 17, the CN transmission / reception unit 43E constitutes the second transmission / reception unit 44D in FIG. The storage unit 42D of 17 is configured, and the other functional blocks constitute the control unit 43B of FIG.
Further, the HNB-S2 of the present embodiment includes an HNB-GW transmission / reception unit 21E, a RANAP function unit 22E, an Iu-UP frame control unit 23E, and an Iu-UP frame transfer unit 24E. In FIG. 19, the HNB-GW transmission / reception unit 21E constitutes the transmission / reception unit 22D of FIG. 17, and other functional blocks constitute the control unit 21D of FIG.
Further, the HNB-T3 of the present embodiment includes an HNB-GW transmission / reception unit 31E, a RANAP function unit 32E, an Iu-UP frame control unit 33E, and an Iu-UP frame transfer unit 34E. In FIG. 19, the HNB-GW transmission / reception unit 31E constitutes the transmission / reception unit 32D of FIG. 17, and other functional blocks constitute the control unit 31D of FIG.
The RFCI conversion unit 47E is a function that performs RFCI conversion that converts the RFCI value added to the audio data received from HNB-T3 into the RFCI value that indicates the data frame of the same structure in the RFCI information of HNB-S2. Has.
In HNB-GW4, the other HNB transmission / reception unit 41E, RANAP function unit 42E, CN transmission / reception unit 43E, Iu-UP frame control unit 44E, Iu-UP frame transfer unit 45E, and RFCI holding unit 46E are respectively. , The same operation as the HNB transmission / reception unit 41B, RANAP function unit 42B, CN transmission / reception unit 43B, Iu-UP frame control unit 44B, Iu-UP frame transfer unit 45B, and RFCI holding unit 46B shown in FIG. ..
Further, in the HNB-S2, the HNB-GW transmission / reception unit 21E, the RANAP function unit 22E, the Iu-UP frame control unit 23E, and the Iu-UP frame transfer unit 24E each transmit / receive to the HNB-GW shown in FIG. It operates in the same manner as the unit 21B, the RANAP function unit 22B, the Iu-UP frame control unit 23B, and the Iu-UP frame transfer unit 24B.
Further, in the HNB-T3, the HNB-GW transmission / reception unit 31E, the RANAP function unit 32E, the Iu-UP frame control unit 33E, and the Iu-UP frame transfer unit 34E each transmit / receive to the HNB-GW shown in FIG. Performs the same operations as unit 31B, RANAP function unit 32B, Iu-UP frame control unit 33B, and Iu-UP frame transfer unit 34B.
Hereinafter, the operation of the present embodiment will be described with reference to the sequence diagram shown in FIG.
In FIG. 20, it is assumed that the HNB-GW4 has acquired the RFCI information of the HNB-S2 in advance. That is, when establishing communication between HNB-S2 and HNB-X8, HNB-S2 sends an Iu-UP Init message containing RFCI information of HNB-S2 to HNB-GW4, which causes it. , HNB-GW4 has acquired the RFCI information of HNB-S2. This procedure was performed prior to step S801 in FIG. 20 and is not shown in FIG.
First, the processing of steps S801 and S802 similar to the processing of steps S201 and S202 of FIG. 5 is performed.
The HNB-T3 then sends an Iu-UP Init message containing the RFCI information of the HNB-T3 to the HNB-GW4 in step S803. The HNB-GW4 terminates the Iu-UP Init message with the Iu-UP frame control unit 44E, and the RFCI information of HNB-T3 included in the Iu-UP Init message and the RFCI information of HNB-S2 acquired in advance. Make a comparison with.
Next, in step S804, the HNB-GW4 responds to the Iu-UP Init message by transmitting the Iu-UP Init ACK message to the HNB-T3.
After that, the processing of steps S805 to S812 similar to the processing of steps S203 to S211 in FIG. 5 is performed, and then UE1 performs the processing of HNB-GW4 and voice data (user data) via HNB-T3 in step S813. Send and receive.
At this time, if the RFCI information of HNB-S2 and HNB-T3 does not match in step S803, the RFCI information of HNB-T3 and HNB-X8 also does not match. Then, in the two RFCI information of HNB-T3 and HNB-X8, even if the RFCI value is the same, it may indicate a data frame with a different structure, so it is transmitted from UE1 via HNB-T3. The received voice data needs to be RFCI-converted.
Therefore, the HNB-GW4 transfers the audio data transmitted from the UE1 via the HNB-T3 from the Iu-UP frame transfer unit 45E to the RFCI conversion unit 47E, and the RFCI conversion unit 47E adds the audio data to the audio data. RFCI conversion is performed to convert the obtained RFCI value into an RFCI value indicating a data frame having the same structure as the voice data in the RFCI information of HNB-S2. After that, the voice data to which the RFCI-converted RFCI value is added is transferred to the Iu-UP frame transfer unit 45E, and transmitted to CN6 via the CN transmission / reception unit 43E.
As described above, in the present embodiment, when the RFCI information of HNB-S2 and HNB-T3 does not match, the HNB-GW4 subsequently sets the RFCI value added to the voice data received from the HNB-T3 to the HNB. -Convert to an RFCI value that indicates a data frame with the same structure in the RFC I information in S2.
Therefore, even if RFCI information is not inherited between HNB-S2 and HNB-T3, voice calls can be made while maintaining transcoder-free operation (TrFO) when intra-HNB-GW relocation occurs between HNB. ..
The description in 7.2 of 3GPP TS25.467 (Non-Patent Document 4), which is changed by this embodiment, is as follows.
Iu-UP terminates only at CN, HNB, and HNB-GW.
Although the present invention has been described above with reference to the embodiments, the present invention is not limited to the above embodiments. Various modifications that can be understood by those skilled in the art can be made to the structure and details of the present invention within the scope of the present invention.
For example, in the first to fourth embodiments, it has been described that the control information to be inherited from HNB-S2 to HNB-T3 is only RFCI information, but the present invention is not limited to this, and IPTI (Inter PDU Transmission Interval) is used. ) Information may be taken over additionally.
The IPTI information defines the data transmission interval (cycle) of the subflow, and the voice data is uniquely calculated by the tall data size of the subflow and the rate of the AMR codec without taking over the voice data from the IPTI information. can do.
Further, in the first to sixth embodiments, it has been explained that the present invention can be applied to the intra-HNB-GW relocation between HNBs, but the present invention describes the inter-HNB-GW relocation (HNB-S2 and HNB-T3). May be applied to relocations where the HNB-GW to which is connected is not the same).
Further, in the fifth and sixth embodiments, the HNB-T3 transmits the RFCI information of the HNB-T3 by including it in the Iu-UP Init message, but at the time when the Iu-UP Init message is to be transmitted. , If the RFCI information of HNB-S2 is received, the transmission of Iu-UP Init message by HNB-T3 may be prohibited.
The method performed by the HNB-S, HNB-T, HNB-GW, and CN node of the present invention may be applied to a program for being executed by a computer. Further, the program can be stored in a storage medium and can be provided to the outside via a network.
This application claims priority on the basis of Japanese application Japanese Patent Application No. 2009-187320 filed on August 12, 2009, and incorporates all of its disclosures herein.
20 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13 Sheet 14 Sheet 15 Sheet 16 Sheet 17 Sheet 18 Sheet 19 Sheet 20
Every citation, both ways
| Reference | Relation |
|---|---|
| NEC,Iu UP Handling during Intra HNB-GW mobility[online], 3GPP TSG-RAN WG3#65 R3-091969,インターネット<URL:http://www.3gpp.org/ftp/tsg_ran/WG3_Iu/TSGR3_65/Docs/R3-091969.zip>,2009年 8月28日,1-5頁 | Non-patent |
| NEC, ZTE, Orange,Iu UP Handling during Intra HNB-GW mobility[online], 3GPP TSG-RAN WG3#66bis R3-100079,インターネット<URL:http://www.3gpp.org/ftp/tsg_ran/WG3_Iu/TSGR3_66bis/Docs/R3-100079.zip>,2010年 1月22日,1-4頁 | Non-patent |
56 members in 10 offices
Priority claims5
| Document | Office | Kind | Date |
|---|---|---|---|
| 2009187320 | Japan | A | |
| 2009187320 | Japan | A | |
| 2009187320 | Japan | – | |
| 2009187320 | – | – | – |
| JP20090187320 | – | – | – |
Members56
| Document | Office | Kind | |
|---|---|---|---|
| CA2770738A1 | Canada | A1 | |
| CA2860689A1 | Canada | A1 | |
| WO2011018915A1 | World Intellectual Property Organization (WIPO) | A1 | |
| AU2010283393A1 | Australia | A1 | |
| CN102474908A | China | A | |
| KR20120055631A | Republic of Korea | A | |
| EP2466988A1 | European Patent Office (EPO) | A1 | |
| US2012202499A1 | United States of America | A1 | |
| JPWO2011018915A1 | Japan | A1 | |
| RU2012108887A | Russian Federation | A | |
| KR20140046085A | Republic of Korea | A | |
| RU2518437C2 | Russian Federation | C2 | |
| KR101420945B1 | Republic of Korea | B1 | |
| AU2010283393B2 | Australia | B2 | |
| JP5660040B2 | Japan | B2 | |
| JP2015065689A | Japan | A | |
| US9020508B2 | United States of America | B2 | |
| AU2015201880A1 | Australia | A1 | |
| US2015230139A1 | United States of America | A1 | |
| RU2014105984A | Russian Federation | A | |
| RU2572564C2 | Russian Federation | C2 | |
| CN102474908B | China | B | |
| CN105554826A | China | A | |
| CN105554827A | China | A | |
| JP5928563B2 | Japan | B2 | |
| CN105657759A | China | A | |
| CN105722160A | China | A | |
| JP2016129433A | Japan | A | |
| CN105813149A | China | A | |
| CN105813150A | China | A | |
| BR112012003079A2 | Brazil | A2 | |
| AU2015201880B2 | Australia | B2 | |
| CA2770738C | Canada | C | |
| US9503937B2 | United States of America | B2 | |
| US2017041832A1 | United States of America | A1 | |
| RU2015151398A | Russian Federation | A | |
| EP2466988A4 | European Patent Office (EPO) | A4 | |
| RU2640034C2 | Russian Federation | C2 | |
| JP2018038093A | Japan | A | |
| JP6315021B2 | Japan | B2 | |
| CA2860689C | Canada | C | |
| US2018167851A1 | United States of America | A1 | |
| RU2671952C1 | Russian Federation | C1 | |
| US10172046B2 | United States of America | B2 | |
| CN105554826B | China | B | |
| JP6512271B2This record | Japan | B2 | |
| BR122016009666A2 | Brazil | A2 | |
| BR122016009667A2 | Brazil | A2 | |
| BR122016009668A2 | Brazil | A2 | |
| BR122016009671A2 | Brazil | A2 | |
| CN105813149B | China | B | |
| CN105813150B | China | B | |
| CN105722160B | China | B | |
| CN105554827B | China | B | |
| CN105657759B | China | B | |
| EP2466988B1 | European Patent Office (EPO) | B1 |
6 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Cancellation because of no payment of annual feesLAPS | LAPS | |
| Certificate of patent or registration of utility modelJAPANESE INTERMEDIATE CODE: R150R150 | R150 | |
| First payment of annual fees (during grant procedure)JAPANESE INTERMEDIATE CODE: A61A61 | A61 | |
| Written decision to grant a patent or to grant a registration (utility model)JAPANESE INTERMEDIATE CODE: A01A01 | A01 | |
| Decision of grant or rejection writtenTRDD | TRDD | |
| Written request for application examinationJAPANESE INTERMEDIATE CODE: A621A621 | A621 |
Numbers
- Publication
- 6512271
- Publication, DOCDB
- 6512271
- Publication, EPODOC
- JP6512271B
- Application
- 235827
- Application, DOCDB
- 2017235827
- Application, EPODOC
- JP20170235827
Titles2
- Japanese
- 移動通信システム、基地局、上位装置、ゲートウェイ装置、通信方法、プログラム
- English
- Mobile communication system, base station, host device, gateway device, communication method, program
Classification
- CPC, 7
- H04W36/0064
- H04W36/38
- H04W88/08
- H04W84/045
- H04W88/16
- H04W36/08
- H04W36/0016
- IPC, 2
- H04W36 08
- H04W92 12
