WO2011018915A1 - 移動通信システム、基地局、上位装置、ゲートウェイ装置、通信方法、プログラム - Google Patents
移動通信システム、基地局、上位装置、ゲートウェイ装置、通信方法、プログラム Download PDFInfo
- Publication number
- WO2011018915A1 WO2011018915A1 PCT/JP2010/059330 JP2010059330W WO2011018915A1 WO 2011018915 A1 WO2011018915 A1 WO 2011018915A1 JP 2010059330 W JP2010059330 W JP 2010059330W WO 2011018915 A1 WO2011018915 A1 WO 2011018915A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- base station
- message
- control information
- hnb
- terminal
- Prior art date
Links
- 238000010295 mobile communication Methods 0.000 title claims abstract description 67
- 238000000034 method Methods 0.000 title claims description 76
- 238000004891 communication Methods 0.000 title claims description 60
- 238000012546 transfer Methods 0.000 claims description 62
- 230000005540 biological transmission Effects 0.000 claims description 52
- 230000007704 transition Effects 0.000 claims description 21
- 238000010586 diagram Methods 0.000 description 29
- 238000012545 processing Methods 0.000 description 11
- 238000006243 chemical reaction Methods 0.000 description 10
- 230000008859 change Effects 0.000 description 7
- 230000004048 modification Effects 0.000 description 6
- 238000012986 modification Methods 0.000 description 6
- 101100162210 Aspergillus parasiticus (strain ATCC 56775 / NRRL 5862 / SRRC 143 / SU-1) aflM gene Proteins 0.000 description 4
- 101100102500 Caenorhabditis elegans ver-1 gene Proteins 0.000 description 4
- 230000008901 benefit Effects 0.000 description 4
- 230000008569 process Effects 0.000 description 3
- 230000004044 response Effects 0.000 description 3
- 230000001960 triggered effect Effects 0.000 description 3
- 230000006978 adaptation Effects 0.000 description 1
- 230000003044 adaptive effect Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 238000013468 resource allocation Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0055—Transmission or use of information for re-establishing the radio link
- H04W36/0064—Transmission or use of information for re-establishing the radio link of control information between different access points
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
- H04W36/0022—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0055—Transmission or use of information for re-establishing the radio link
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/34—Reselection control
- H04W36/38—Reselection control by fixed network equipment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/04—Large scale networks; Deep hierarchical networks
- H04W84/042—Public Land Mobile systems, e.g. cellular systems
- H04W84/045—Public Land Mobile systems, e.g. cellular systems using private Base Stations, e.g. femto Base Stations, home Node B
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/08—Access point devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/16—Gateway arrangements
Definitions
- the present invention relates to a mobile communication system, a base station, a host device, a gateway device, a communication method, and a program.
- Node-B base station
- RNC Radio Network Controller
- CN Core Network
- AMR Adaptive Multi-Rate
- AMR is a method for dynamically changing the rate of voice data in accordance with the line conditions and the like.
- a transcoder is installed in the CN in order to make the voice data encoding and decoding rates the same, and recoding (transcoding) is performed by the transcoder as necessary. 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 the plurality of subframes varies depending on the audio data rate, and an RFCI (RAB sub-flow combination indicator) value is defined as an identifier for each combination. That is, the RFCI value is defined for each audio data rate.
- RAB sub-flow combination indicator RAB sub-flow combination indicator
- RFCI information is set in each Node-B as control information in speech 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.
- the RFCI information is also used for Wide-Band AMR (broadband audio codec) and CS streaming service (Fax and modem communication).
- the Node-B When transmitting audio data encoded at a certain rate, the Node-B transmits the audio data to which the RFCI value corresponding to the rate is added to the other Node-B, and the audio data from the other Node-B. , The audio data is decoded at a rate corresponding to the RFCI value added to the audio data.
- a UE User Equipment: terminal
- a voice call through two Node-Bs
- the RFCI value indicates a data frame having the same structure. Therefore, audio data can be encoded / decoded between the two Node-Bs at the same rate without going through a transcoder in the CN.
- Such a method of performing a voice call without going through a transcoder is called a transcoder free operation (TrFO). This method is defined in 3GPP TS 23.153 (Non-Patent Document 1).
- the two RFCI information may indicate data frames having different structures even if the RFCI values are the same.
- voice data cannot be encoded / decoded at the same rate between the two Node-Bs without going through the transcoder, a voice call can be made while maintaining the transcoder-free operation (TrFO). Can't do it.
- the RFCI information may not match between the source Node-B to which the UE connects before moving and the destination Node-B to which the UE connects after moving. It is thought that there are many.
- Non-Patent Document 2 so-called SRNS (Serving Radio Network Subsystem) relocation, in which the RNC to which the UE's source Node-B is connected and the RNC to which the destination Node-B is connected, is different. It is specified that, when an error occurs, RFCI information is taken over between RNCs via an Iu-UP Initialization message specified by the Iu-UP (Iu interface user plane) protocol via CN.
- Iu-UP Iu interface user plane
- 3GPP TS 23.153 3GPP TS 25.415 3GPP TS 25.413 3GPP TS 25.467 3GPP TS 25.468 3GPP TS 25.469
- HNB Home Node-B: small base station
- HNB-GW Home Node-Gateway
- CN Home Node-Gateway
- this mobile communication system includes UE1, HNB-S2, HNB-T3, HNB-GW4, CN6 including CN node 5, HNB-GW7, and HNB-X8. .
- UE1 is a third generation mobile cellular phone (terminal).
- HNB-S2, HNB-T3, and HNB-X8 are small base stations for homes and small offices.
- HNB-S2 is a source HNB to which UE1 connects before moving.
- HNB-T3 is a destination HNB to which UE1 connects after moving.
- the HNB-X8 is an HNB having a UE (not shown) as a communication partner of the UE1 under its control.
- 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.
- CN6 is a third generation mobile switching network.
- CN node 5 is a core network device such as HMS (Home NodeB Management System) and MSC (Mobile Switching Center) provided in CN 6.
- HMS Home NodeB Management System
- MSC Mobile Switching Center
- UE1 moves from HNB-S2 under the same HNB-GW4 to HNB-T3. Such movement is called intra-HNB-GW relocation.
- UE1 Before moving, UE1 performs a voice call with a UE under HNB-X8 via HNB-S2, HNB-GW4, CN6, HNB-GW7, and HNB-X8.
- UE1 After moving, UE1 performs a voice call with a UE under HNB-X8 via HNB-T3, HNB-GW4, CN6, HNB-GW7, and HNB-X8.
- the opposite system of the communication partner of UE1 is a 3GPP wireless communication system configured by HNB-X8 / HNB-GW7 / CN6, but is configured by an existing Node-B / RNC / CN.
- 3GPP wireless communication system may be used.
- HNB-S2 and HNB-T3 are under the same HNB-GW4 but have different vendors.
- an object of the present invention is to solve the above-described problems and to perform a voice call while maintaining a transcoder-free operation (TrFO) even when intra-HNB-GW relocation occurs between HNBs.
- a base station, a host device, a gateway device, a communication method, and a program are examples of the above-described problems.
- the first mobile communication system of the present invention is: A terminal, a source base station to which the terminal connects before moving, a destination base station to which the terminal connects after moving, and a host device under the control of the source base station and the destination base station,
- a mobile communication system comprising: The source base station and the destination base station are preset with control information in speech coding, The source base station includes the control information of its own station in a first message, and transmits the first message to the host device.
- the higher-level device includes the control information of the source base station in a second message and transmits the second message to the destination base station.
- the second mobile communication system of the present invention is A terminal, a source base station to which the terminal connects before moving, a destination base station to which the terminal connects after moving, and a gateway apparatus for connecting the source base station and the destination base station to a core network
- a mobile communication system comprising: For each identifier, the source base station and the destination base station set in advance control information for identifying the structure of the data frame of the voice encoded voice data indicated by the identifier, as control information in voice encoding.
- the source base station includes the control information of its own station in a first message, and transmits the first message to the gateway device.
- the destination base station includes the control information of its own station in a second message, and transmits the second message to the gateway device.
- the gateway device is Storing the control information of the source base station included in the first message and the control information of the destination base station included in the second message;
- the control information of the source base station and the destination base station do not match
- voice data is subsequently received from the destination base station
- the identifier added to the voice data is changed to the source base station. Converted into an identifier indicating a data frame of the same structure in the control information of the station,
- the voice data to which the converted identifier is added is transmitted to the core network.
- the first base station of the present invention The source base station to which the terminal connects before moving, Control information in speech encoding is preset, a control unit that includes the control information of its own station in a message, A transmission / reception unit that transmits the message to a higher-level device.
- the second base station of the present invention The base station to which the terminal connects after moving, A control unit in which control information in speech encoding is preset; And a transmission / reception unit that receives a first message including the control information of the source base station to which the terminal was connected before the movement from the host device.
- the host device of the present invention is A host device under control of a source base station to which the terminal connects before moving and a destination base station to which the terminal connects after moving;
- the source base station and the destination base station are preset with control information in speech coding,
- a transmission / reception unit for receiving a first message including the control information of the source base station from the source base station;
- a control unit including the control information of the source base station in a second message, The transmission / reception unit transmits the second message to the destination base station.
- the gateway device of the present invention A gateway device that connects a source base station to which a terminal is connected before moving and a destination base station to which the terminal is connected after moving to a core network, For each identifier, the source base station and the destination base station set in advance control information for identifying the structure of the data frame of the voice encoded voice data indicated by the identifier, as control information in voice encoding. Has been A first message including the control information of the source base station is received from the source base station, and a second message including the control information of the destination base station is received from the destination base station.
- a transmission / reception unit for receiving; A storage unit for storing the control information of the source base station included in the first message and the control information of the destination base station included in the second message; When the control information of the source base station and the destination base station do not match, when voice data is subsequently received from the destination base station, the identifier added to the voice data is changed to the source base station.
- a control unit for converting to an identifier indicating a data frame of the same structure in the control information of the station;
- a second transmission / reception unit that transmits the audio data to which the converted identifier is added to the core network.
- the first communication method of the present invention includes: A terminal, a source base station to which the terminal connects before moving, a destination base station to which the terminal connects after moving, and a host device under the control of the source base station and the destination base station, A communication method using a mobile communication system comprising: The source base station includes control information in its own speech coding in a first message, and transmits the first message to the host device; The host device includes the control information of the source base station in a second message, and transmits the second message to the destination base station.
- the second communication method of the present invention includes: A terminal, a source base station to which the terminal connects before moving, a destination base station to which the terminal connects after moving, and a gateway apparatus for connecting the source base station and the destination base station to a core network
- a communication method by a mobile communication system comprising: As the control information in the speech encoding of the local station, the source base station uses, for each identifier, control information for identifying the structure of the data frame of the speech encoded speech data indicated by the identifier in the first message.
- the destination base station includes the control information of its own station in a second message, and transmits the second message to the gateway device;
- the gateway device storing the control information of the source base station included in the first message and the control information of the destination base station included in the second message;
- the gateway device receives the voice data from the destination base station after that when the control information of the source base station and the destination base station do not match, the identifier added to the voice data is changed to the identifier. Converting to an identifier indicating a data frame of the same structure in the control information of the source base station; And the gateway device transmitting voice data to which the converted identifier is added to the core network.
- the third communication method of the present invention is: A communication method by a source base station to which a terminal connects before moving, Including control information in the voice encoding of the local station in the message; Transmitting the message to a higher-level device.
- the fourth communication method of the present invention is: A communication method by a destination base station to which a terminal connects after moving, Receiving from the host device a first message including control information in speech encoding of the source base station to which the terminal was connected before moving.
- the fifth communication method of the present invention is: A communication method by a host device under control of a source base station to which a terminal connects before moving and a destination base station to which the terminal connects after moving, Receiving from the source base station a first message including control information in speech encoding of the source base station; Including the control information of the source base station in a second message; Transmitting the second message to the destination base station.
- the sixth communication method of the present invention is: A communication method by a gateway device that connects a source base station to which a terminal connects before moving and a destination base station to which the terminal connects after moving to a core network, Control information for identifying the structure of a data frame of voice-coded voice data indicated by the identifier is provided for each identifier as control information in voice coding of the source base station from the source base station.
- the first program of the present invention is: To the source base station that the terminal connects to before moving, A procedure for including control information in the speech encoding of the own station in the message; And a procedure for transmitting the message to a host device.
- the second program of the present invention is: To the base station to which the terminal connects after moving, A procedure for receiving a first message including control information in speech coding of a source base station to which the terminal was connected before moving from the host device is executed.
- the third program of the present invention is: In a host device under the control of a source base station to which the terminal connects before moving and a destination base station to which the terminal connects after moving, Receiving from the source base station a first message including control information in speech encoding of the source base station; Including the control information of the source base station in a second message; And a step of transmitting the second message to the destination base station.
- the fourth program of the present invention is: A gateway device that connects a source base station to which the terminal connects before moving and a destination base station to which the terminal connects after moving to the core network, Control information for identifying the structure of a data frame of voice-coded voice data indicated by the identifier is provided for each identifier as control information in voice coding of the source base station from the source base station.
- the source base station transmits its own control information to the host device, and the host device transmits the source base station control information to the destination base station. .
- the destination base station can take over control information from the source base station, when relocation occurs between the source base station and the destination base station, the voice is kept while maintaining the transcoder-free operation (TrFO). You can make a call.
- the gateway device when the control information of the source base station and the destination base station does not match, the gateway device is added to the voice data received from the destination base station thereafter.
- the identifier is converted into an identifier indicating a data frame having the same structure in the control information of the source base station.
- a voice call is performed while maintaining the transcoder-free operation (TrFO) when relocation occurs between the source base station and the destination base station. It can be performed.
- FIG. 1 is a diagram showing a configuration of a mobile communication system configured with HNB / HNB-GW / CN.
- FIG. It is a block diagram which shows the internal structure of HNB and a high-order apparatus in the mobile communication system of the 1st Embodiment of this invention. It is a sequence diagram explaining operation
- 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) that is either the HNB-GW4 or the CN node 5.
- the HNB-S2's RFCI information is notified from the HNB-S2 to the HNB-T3 via the host device 9.
- 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, a transmission / reception unit 22A that transmits the first message to the higher-level device 9, Have
- the higher-level 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 transmitting / receiving unit 91A transmits the second message to the HNB-T3.
- the HNB-T3 of the present embodiment initializes the RFCI information of the HNB-T3 and the transmission / reception unit 31A that receives the second message from the higher-level device 9, and sets (re-set) the RFCI information included in the second message. And a control unit 32A for setting).
- step S101 the HNB-S2 transmits a first message including the HCI-S2 RFCI information to the host device 9.
- step S102 the host device 9 transmits the second message including the RFCI information included in the first message received from the HNB-S2 to the HNB-T3.
- the HNB-T3 can take over the RFCI information from the HNB-S2 via the host device 9, intra-HNB-GW relocation occurs between the HNB-S2 and the HNB-T3. In some cases, there is an effect that a voice call can be performed while maintaining a transcoder-free operation (TrFO).
- the present embodiment is an example in which the host device 9 is HNB-GW 4 and the first embodiment is more specific.
- the HNB-S2's RFCI information is notified from the HNB-S2 to the HNB-T3 via the HNB-GW4 by a RANAP message.
- the HNB-GW 4 of the present embodiment includes 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. 45B and an RFCI holding unit 46B.
- the HNB transceiver 41B constitutes the transceiver 91A in FIG. 2, and the other functional blocks constitute the controller 92A in FIG.
- the HNB-S2 of the present embodiment includes an anti-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.
- the HNB-GW transmission / reception unit 21B constitutes the transmission / reception unit 22A of FIG. 2
- the other functional blocks constitute the control unit 21A of FIG.
- the HNB-T3 of the present embodiment includes a pair-to-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.
- the HNB-GW transmission / reception unit 31B constitutes the transmission / reception unit 31A in FIG. 2
- the other functional blocks constitute the control unit 32A in FIG.
- the HNB transceiver 41B has an interface for connecting to the HNB-S2 and HNB-T3, and transmits / receives audio data to / from the HNB-S2 and HNB-T3.
- the RANAP function units 22B, 32B, and 42B realize a RANAP (Radio Access Network Application Part) protocol function defined by 3GPP TS 25.413 (Non-patent Document 3).
- the RANAP function units 22B, 32B, and 42B have a function of generating a RANAP message and a function of terminating the RANAP message.
- the CN transmission / reception unit 43 ⁇ / b> B has an interface for connection with the CN node 5, and transmits / receives voice data between the CN nodes 5.
- the Iu-UP frame control units 23B, 33B, and 44B realize the Iu-UP protocol function defined in 3GPP TS25.415 (Non-Patent Document 2).
- the Iu-UP frame control units 23B, 33B, and 44B have a function of generating an Iu-UP Initialization message (hereinafter abbreviated as an Iu-UP Init message) and a function of terminating the Iu-UP Init message.
- the Iu-UP frame control unit 44B has a function of notifying the RFCI holding unit 46B of the RFCI information included in the Iu-UP Init message and the RFCI holding unit when the Iu-UP Initialization restarts. And a function of requesting comparison of RFCI information to 46B.
- the Iu-UP frame transfer units 24B, 34B, and 45B realize the Iu-UP protocol function defined in 3GPP TS25.415 (Non-patent Document 2).
- the Iu-UP frame transfer units 24B, 34B, and 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, a function of notifying the comparison result based on the comparison request of the RFCI information from the Iu-UP frame control unit 44B, Have
- the HNB-GW transmission / reception units 21B and 31B have an interface for connecting to the HNB-GW 4, and transmit / receive audio data to / from the HNB-GW 4.
- a RAB parameter related to a radio access bearer (RAB) between a UE and a CN is set as a RANAP between the CN and the RNC (HNB-GW). It is stipulated to notify by message.
- the RAB parameters are QoS (Quality of Service) parameters (data transmission rate, block size, error rate, etc.) corresponding to the type of service.
- the RAB parameter is closely related to the RFCI information exchanged by the Iu-UP Initialization message, and only the RFCI information is changed by restarting the Iu-UP Initialization without changing the RAB parameter (RAB Modification). If this happens, there is a risk of inconsistencies in the state.
- 3GPP TS25.415 (Non-Patent Document 2) specifies that Iu-UP Initialization from the same SRNS should not be restarted except for RAB Modification to prevent such procedures from occurring. (First provision).
- the mobile communication system configured by the existing Node-B / RNC / CN has a function of taking over the RFCI information by the Iu-UP Initialization message
- the mobile communication system configured by the HNB / HNB-GW / CN When applied, in FIG. 1, Iu-UP Initialization is activated for CN 6 from each of HNB-S2 and HNB-T3. However, in this case, as seen from CN6, the same SRNS (HNB-GW4) restarts Iu-UP Initialization, which violates the first rule.
- Second regulation The problem of the first regulation can be solved by terminating the Iu-UP Initialization message with the HNB-GW (that is, not terminating with the CN).
- Non-Patent Document 4 if the Iu-UP message is terminated by the HNB-GW, there is a concern about the increase in signal processing and complexity of the HNB-GW. It is specified that the protocol message is not terminated by the HNB-GW (second specification). Therefore, when the Iu-UP Initialization message is terminated at the HNB-GW, the second rule is violated.
- the transcoder-free operation (TrFO) is maintained when intra-HNB-GW relocation occurs between HNB-S2 and HNB-T3 without changing the first and second rules. It is possible to make a voice call as it is.
- step S201 the HNB-S2 starts a relocation procedure by transmitting a RANAP: Relocation Required message requesting the movement of the UE1 from the HNB-S2 to the HNB-GW4.
- the RFCI information of the Iu-UP Init message is added to the 9.1.9 RANAP: Relocation Required message of 3GPP TS25.413 (Non-patent Document 3).
- FIG. 6 shows a RANAP: Relocation Required message changed according to the present embodiment.
- FIG. 6 shows only the changed part.
- the RFCI value “RFCI” “RFCI”
- the data size of each subflow “Length” are included. of Subflow "is added as RFCI information.
- the HNB-GW 4 terminates the RANAP: Relocation Required message at the RANAP function unit 42B, and acquires the RFCI information.
- step S202 the HNB-GW 4 sends a RANAP: Relocation Request message requesting the movement of the UE 1 to the HNB-T3 to the HNB-T3, thereby requesting the HNB-T3 to secure the resource.
- the RANAP function unit 42B acquires the RFCI information and includes the RFCI information in the RANAP: Relocation Request message.
- FIG. 7 shows a RANAP: Relocation Request message changed according to the present embodiment.
- FIG. 7 shows only the changed part.
- RFCI that is an RFCI value
- RCFI Subflow that is the number of subflows constituting the data frame indicated by the RFCI value.
- And“ Length of Subflow ” which is the data size for each subflow, are added as RFCI information.
- the HNB-T3 terminates the RANAP: Relocation Request message at the RANAP function unit 32B. If the RFCI information is included in the RANAP: Relocation Request message, the HNB-T3 initializes the RFCI information of the HNB-T3 and resets the RFCI information included in the RANAP: Relocation Request message.
- the HNB-T3 subsequently receives uplink voice data from the UE1 and downlink voice data from the CN6, the structure of the data frame of the voice data is determined based on the RFCI value added to the voice data. In addition, the rate can be recognized correctly.
- FIG. 8 shows an image of the Iu-UP Protocol state transition diagram changed according to the present embodiment. 8 shows a RANAP: Relocation Request message including RFCI information (in FIG. 8, Intra-HNB-GW Relocation-Req) is received, and the “Support Mode Data Transfer Ready” state is directly changed from the “NULL” state to the “Support Mode Data Transfer Ready” state. It means to make a transition.
- the HNB-T3 receives a RANAP: Relocation Request message without executing the Iu-UP Initialization procedure
- the state of the Iu-UP frame transfer unit 33B is changed from the “NULL” state using this as a trigger. , Transition to the “Support Mode Data Transfer Ready” state, and the Iu-UP frame data can be transferred.
- the signal name for transition 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 HNB-T3 After execution of step S202, the HNB-T3 responds to the RANAP: Relocation Request message by transmitting a RANAP: Relocation Request ACK message to the HNB-GW 4 in step S203.
- step S204 the HNB-GW 4 sends a Relocation command message to the HNB-S2, thereby instructing the start of Relocation.
- step S205 the HNB-S2 sends a RRC: Reconfiguration message to the UE 1 to instruct reconfiguration of the radio channel.
- step S206 the HNB-T3 detects UE1 by synchronization with the wireless Layer1, and notifies the UE1 that it has detected by transmitting a Relocation Detect message to the HNB-GW4.
- step S207 UE1 notifies RNB: Reconfiguration Complete message to HNB-T3 that radio resource allocation has been completed.
- step S208 the HNB-T3 sends a RANAP: Relocation Complete message to the HNB-GW 4 to notify that the relocation has been completed.
- step S209 the HNB-GW 4 sends a RANAP: Iu Release Command message to the HNB-S2, thereby requesting the release of the HNB-S2 resource.
- step S210 the HNB-S2 sends a RANAP: Iu Release Complete message to the HNB-GW 4 to notify that the HNB-S2 resources have been released.
- step S211 UE1 transmits / receives voice data (user data) to / from HNB-GW4 via HNB-T3.
- the HNB-S2 notifies the HNB-S2 of the RFCI information of the HNB-S2 by the RANAP: Relocation Required message
- the HNB-GW4 transmits the RFCI information of the HNB-S2 to the RANAP: Since the notification is sent to the HNB-T3 by the Relocation Request message, the HNB-T3 can take over the RFCI information from the HNB-S2 without executing the Iu-UP Initialization procedure.
- the HNB-T3 transitions to a state in which the voice data can be transferred triggered by the reception of the RANAP: Relocation Request message from the HNB-GW4, the voice data can be transferred without executing the Iu-UP Initialization procedure. It becomes possible to transmit.
- the HNB-T3 can take over the RFCI information from the HNB-S2 and transmit the voice data without executing the Iu-UP Initialization procedure. Therefore, the intra-connection between the HNB-S2 and the HNB-T3 is possible. Even when HNB-GW relocation occurs, a voice call can be performed while maintaining the transcoder-free operation (TrFO).
- 3GPP TS 25.467 stipulates that the RANAP message is terminated at the HNB and HNB-GW. Therefore, there is an advantage that it is not necessary to newly support a protocol when adding a function related to the present embodiment to the RANAP message.
- Second Merit Currently, 3GPP is examining the Intra HNB-GW Relocation procedure, but it is common to use a RANAP message for the signal of this procedure.
- the present embodiment is an example in which the host device 9 is HNB-GW 4 and the first embodiment is more specific.
- the HNB-S2's RFCI information is notified from the HNB-S2 to the HNB-T3 via the HNB-GW4 by means of a Direct Transfer message of RANAP User Adaptation (hereinafter abbreviated as RUA).
- RUA Direct Transfer message of RANAP User Adaptation
- RUA is defined in 3GPP TS 25.468 (Non-Patent Document 5). Further, the RUA Direct Transfer message is a message used for transferring the RANAP message.
- the HNB-GW 4 of this embodiment differs from the HNB-GW 4 of the second embodiment shown in FIG. 4 in that an RUA function unit 47B is added.
- the RUA function unit 47B is one of the components constituting the control unit 92A of FIG.
- the HNB-S2 of the present embodiment is different from the HNB-S2 of the second embodiment shown in FIG. 4 in that an RUA function unit 25B is added.
- the RUA function unit 25B is one of the components constituting the control unit 21A of FIG.
- the HNB-T3 of the present embodiment is different from the HNB-T3 of the second embodiment shown in FIG. 4 in that an RUA function unit 35B is added.
- the RUA function unit 35B is one of the components constituting the control unit 32A of FIG.
- the RUA function units 25B, 35B, and 47B realize the RUA protocol function defined in 3GPP TS 25.468 (Non-Patent Document 5).
- the RUA function units 25B, 35B, and 47B have a function of generating a RUA message and a function of terminating the RUA message.
- step S301 the HNB-S2 starts a relocation procedure by transmitting a RANAP: Relocation Required message requesting the movement of the UE1 from the HNB-S2 to the HNB-GW4.
- FIG. 11 shows the RUA Direct Transfer message changed according to the present embodiment. Note that FIG. 11 shows only the changed part.
- RFCI that is an RFCI value
- RCFI Subflow that is the number of subflows constituting the data frame indicated by the RFCI value
- Length of that is the data size of each subflow. Subflow "is added as RFCI information.
- the HNB-GW 4 terminates the RANAP: Relocation Required message in the RANAP function unit 42B, and terminates the RUA Direct Transfer message in the RUA function unit 47B, and acquires the RFCI information.
- step S302 the HNB-GW 4 requests the HNB-T3 to secure the resource by transmitting to the HNB-T3 a RANAP: Relocation Request message that requests the UE 1 to move to the HNB-T3.
- an RUA Direct Transfer message for transferring the RANAP: Relocation Request message is also transmitted.
- the RUA function 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.
- the HNB-T3 terminates the RANAP: Relocation Request message in the RANAP function unit 32B and terminates the RUA Direct Transfer message in the RUA function unit 35B. If RFCI information is included in the RUA Direct Transfer message, the HNB-T3 initializes the RFCI information of the HNB-T3 and resets it to the RFCI information included in the RUA Direct Transfer message.
- the HNB-T3 subsequently receives uplink voice data from the UE1 and downlink voice data from the CN6, the structure of the data frame of the voice data is determined based on the RFCI value added to the voice data. In addition, the rate can be recognized correctly.
- the HNB-T3 triggers the reception of the RUA Direct Transfer message to change the state of the Iu-UP frame transfer unit 33B from the “NULL” state to the “Support Mode”. Transition to the “Data Transfer Ready” state, and the Iu-UP frame data can be transferred.
- the subsequent steps S303 to S311 are the same as the steps S203 to S211 in FIG.
- the HNB-S2 notifies the HNB-S2 of the RFCI information of the HNB-S2 by the RUA Direct Transfer message, and the HNB-GW4 transmits the RFCI information of the HNB-S2 to the RUA Direct Transfer. Since the message is notified to the HNB-T3, the HNB-T3 can take over the RFCI information from the HNB-S2 without executing the Iu-UP Initialization procedure.
- HNB-T3 transmits voice data without executing the Iu-UP Initialization procedure because it transitions to a state in which voice data can be transferred triggered by reception of the RUA Direct Transfer message from HNB-GW4. It becomes possible to do.
- the HNB-T3 can take over the RFCI information from the HNB-S2 and transmit the voice data without executing the Iu-UP Initialization procedure. Therefore, the intra-connection between the HNB-S2 and the HNB-T3 is possible. Even when HNB-GW relocation occurs, a voice call can be performed while maintaining the transcoder-free operation (TrFO).
- the present embodiment is an example in which the host device 9 is HNB-GW 4 and the first embodiment is more specific.
- the HNB-S2's RFCI information is notified from the HNB-S2 to the HNB-T3 via the HNB-GW4 using a Relocation message of Home Node B Application Part (hereinafter abbreviated as HNBAP).
- HNBAP Home Node B Application Part
- HNBAP is defined in 3GPP TS 25.469 (Non-Patent Document 6).
- the HNBAP Relocation message is not defined in 3GPP, and is well known as one of the proposals in the Intra HNB-GW relocation procedure currently being studied, and is not directly related to the present invention.
- the HNB-GW 4 of this embodiment is different from the HNB-GW 4 of the second embodiment shown in FIG. 4 in that an HNBAP function unit 48B is added.
- the HNBAP function unit 48B is one of the components constituting the control unit 92A in FIG.
- the HNB-S2 of this embodiment is different from the HNB-S2 of the second embodiment shown in FIG. 4 in that an HNBAP function unit 26B is added.
- the HNBAP function unit 26B is one of the components constituting the control unit 21A in FIG.
- the HNB-T3 of this embodiment is different from the HNB-T3 of the second embodiment shown in FIG. 4 in that an HNBAP function unit 36B is added.
- the HNBAP function unit 36B is one of the components constituting the control unit 32A in FIG.
- the HNBAP function units 26B, 36B, and 48B realize the HNBAP protocol function defined in 3GPP TS 25.469 (Non-Patent Document 6).
- the HNBAP function units 26B, 36B, and 48B have a function of generating an HNBAP message and a function of terminating the HNBAP message.
- step S401 the HNB-S2 starts a relocation procedure by transmitting an HNBAP: Relocation Required message requesting the movement of the UE1 from the HNB-S2 to the HNB-GW4.
- the RFCI information of the Iu-UP Init message is added to the HNBAP: Relocation Required message.
- RFCI information can be added to HNBAP: Relocation Required at this time, for example, as in FIG.
- the HNB-GW 4 terminates the HNBAP: Relocation Required message at the HNBAP function unit 48B, and acquires the RFCI information.
- step S402 the HNB-GW 4 requests the HNB-T3 to secure resources by transmitting an HNBAP: Relocation Request message requesting the movement of the UE 1 to the HNB-T3 to the HNB-T3.
- the HNBAP function unit 48B acquires the RFCI information and includes the RFCI information in the HNBAP: Relocation Request message. At this time, RFCI information can be added to the HNBAP: Relocation Request message, for example, as in FIG.
- the HNB-T3 terminates the HNBAP: Relocation Request message at the HNBAP function unit 36B. If RFCI information is included in the HNBAP: Relocation Request message, the HNB-T3 initializes the RFCI information of the HNB-T3, and resets the RFCI information included in the HNBAP: Relocation Request message.
- the HNB-T3 subsequently receives uplink voice data from the UE1 and downlink voice data from the CN6, the structure of the data frame of the voice data is determined based on the RFCI value added to the voice data. In addition, the rate can be recognized correctly.
- Non-patent Document 2 the state transition diagram of the Iu-UP Protocol of 3GPP TS25.415 (Non-patent Document 2) regarding the state transition of HNB-T3 (see FIG. 8), the “Support Mode directly from the“ NULL ”state.
- a condition for transitioning to the “Data Transfer Ready” state a condition for receiving an HNBAP: Relocation Request message including RFCI information (in FIG. 8, Intra-HNB-GW Relocation-Req) is added.
- the HNB-T3 changes the state of the Iu-UP frame transfer unit 33B from the “NULL” state to the “Support” using the reception of the HNBAP: Relocation Request message as a trigger.
- the mode is changed to “Mode Data Transfer Ready” state, and the Iu-UP frame data can be transferred.
- the subsequent steps S403 to S411 are the same as the steps S203 to S211 in FIG.
- the HNB-S2 notifies the HNB-S2 of the RFCI information of the HNB-S2 to the HNB-GW4 using the HNBAP: Relocation Required message, and the HNB-GW4 transmits the RFCI information of the HNB-S2 to the HNBAP: Since the notification is sent to the HNB-T3 by the Relocation Request message, the HNB-T3 can take over the RFCI information from the HNB-S2 without executing the Iu-UP Initialization procedure.
- the HNB-T3 transitions to a state in which the voice data can be transferred triggered by 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 becomes possible to transmit.
- the HNB-T3 can take over the RFCI information from the HNB-S2 and transmit the voice data without executing the Iu-UP Initialization procedure. Therefore, the intra-connection between the HNB-S2 and the HNB-T3 is possible. Even when HNB-GW relocation occurs, a voice call can be performed while maintaining the transcoder-free operation (TrFO).
- the present embodiment is an example in which the host device 9 is HNB-GW 4 and the first embodiment is more specific.
- the configuration of this embodiment is the same as that of the second embodiment shown in FIG.
- the HNB-GW 4 notifies the HNB-T 3 of the RFCI information of the HNB-S 2 by the Iu-UP Init message during the relocation processing from the HNB-S 2 to the HNB-T 3 of the UE 1.
- the Iu-UP Init message is transmitted and received between the HNB and the HNB-GW when the HNB tries to establish communication with the HNB under the control of the UE's communication partner, such as when a relocation occurs. Message.
- Non-Patent Document 2 In Iu-UP Ver2 of 3GPP TS25.415 (Non-Patent Document 2), it is defined that an Iu-UP Init message is transmitted from the CN to the RNC. However, this rule presupposes a mobile communication system composed of existing Node-B / RNC / CN of 3GPP.
- Non-Patent Document 4 Stipulates that messages of the Iu-UP protocol are not terminated by the HNB-GW.
- the specification of 3GPP is changed to allow the Iu-UP message to be terminated by the HNB-GW.
- HNB-GW 4 has previously acquired the RFC information of the HNB-S2. That is, when establishing communication between HNB-S2 and HNB-X8, HNB-S2 sends an Iu-UP Init message including the RFCI information of HNB-S2 to HNB-GW4. , HNB-GW4 acquires the RFCI information of HNB-S2. This procedure is performed before step S501 in FIG. 14 and is not described in FIG.
- the HNB-T3 transmits an Iu-UP Init message including the RFCI information of the HNB-T3 to the HNB-GW4.
- the HNB-GW 4 terminates the Iu-UP Init message in the Iu-UP frame control unit 44B, and the HNB-T3 RFCI information included in the Iu-UP Init message and the HNB-S2 previously obtained RFCI information. Compare with.
- the HNB-GW 4 responds to the Iu-UP Init message by transmitting an Iu-UP Init ACK message to the HNB-T 3 in step S504.
- step S503 if the HCI-S2 and HNB-T3 RFCI information does not match, the HNB-GW4 matches the HNB-T3 RFCI information with the HNB-S2 RFCI information.
- step S505 the HNB-S2 The Iu-UP Init message including the RFCI information is transmitted to the HNB-T3.
- the HNB-T3 responds to the Iu-UP Init message by sending an Iu-UP Init ACK message to the HNB-GW 4 in step S506. Also, the HNB-T3 initializes the RFCI information of the HNB-T3 and resets it to the RFCI information of the HNB-S2 included in the Iu-UP Init message.
- steps S507 to S515 is the same as the processing in steps S203 to S211 in FIG.
- the HNB-GW 4 notifies the HNB-S2 of the RFCI information to the HNB-T3 by an Iu-UP Init message, so that the HNB-T3 takes over the RFCI information from the HNB-S2. Is possible.
- Non-Patent Document 4 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.
- Non-Patent Document 2 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, that is, both CN and UTRAN.
- the initialization procedure is used to detect the mismatch of RFCI when indicated by the control function of the Iu-UP procedure, that is, when SRNS relocation or RAB establishment is performed on Iu, or when CN or HNB-GW is performing TrFO. Invoked when trying to resolve.
- the Initialization procedure cannot be restarted by SRNC for RAB without requesting RAB Modification by RANAP.
- Iu-UP Ver1 of 3GPP TS25.415 (Non-Patent Document 2), it is specified that an Iu-UP Init message is transmitted from the RNC to the CN, but the Iu-UP Init message is transmitted from the CN to the RNC. Sending is not stipulated. Therefore, the rules for Iu-UP Ver1 may be revised in the same manner as Iu-UP Ver2.
- Non-Patent Document 2 the description of Iu-UP Ver1 in 6.5.2 of 3GPP TS25.415 (Non-Patent Document 2), which is changed according to the present embodiment, is as follows.
- the initialization procedure can be controlled by two Iu access points, that is, both CN and UTRAN.
- the initialization procedure is used to detect the mismatch of RFCI when indicated by the control function of the Iu-UP procedure, that is, when SRNS relocation or RAB establishment is performed on Iu, or when CN or HNB-GW is performing TrFO. Invoked when trying to resolve.
- the Initialization procedure cannot be restarted by SRNC for RAB without requesting RAB Modification by RANAP.
- the present embodiment is an example in which the host device 9 is the CN node 5 and the first embodiment is more specific.
- 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 to the HNB-T3 of the UE1.
- the CN node 5 performs the operation performed by the HNB-GW 4 in the third embodiment, and the HNB-GW 4 exchanges between the HNB-S2 / HNB-T3 and the CN node 5. Only the transfer is performed without terminating the RANAP message and the Iu-UP Init message.
- Non-Patent Document 2 stipulates that restart of Iu-UP Initialization when Intra HNB-GW relocation occurs is not allowed.
- the CN node 5 includes an HNB-GW transmission / reception unit 51C for HNB-GW4, a RANAP function unit 52C, an HNB-GW transmission / reception unit 53C for HNB-GW7, an Iu -An UP frame control unit 54C, an Iu-UP frame transfer unit 55C, and an RFCI holding unit 56C.
- the HNB-GW transmission / reception unit 51C constitutes the transmission / reception unit 91A in FIG. 2, and the other functional blocks constitute the control unit 92A in FIG.
- HNB-S2 and HNB-T3 in the present embodiment are the same as the configurations of HNB-S2 and HNB-T3 in the second embodiment shown in FIG.
- the HNB-GW transmission / reception unit 51C has an interface for connecting to the HNB-GW 4 and transmits / receives audio data to / from the HNB-GW 4.
- the HNB-GW transmission / reception unit 53C has an interface for connecting to the HNB-GW 7, and transmits / receives audio data to / from the HNB-GW 7.
- the other RANAP function unit 52C, Iu-UP frame control unit 54C, Iu-UP frame transfer unit 55C, and RFCI holding unit 56C are respectively the RANAP function unit 42B and the Iu-UP frame control unit shown in FIG. The same operation as 44B, Iu-UP frame transfer unit 45B, and RFCI holding unit 46B is performed.
- the CN node 5 has acquired the RFCI information of HNB-S2 in advance. That is, when establishing communication between HNB-S2 and HNB-X8, HNB-S2 sends an Iu-UP Init message including the RFCI information of HNB-S2 to CN node 5 via HNB-GW4. As a result, the CN node 5 acquires the RFCI information of the HNB-S2. This procedure is performed before step S601 in FIG. 16, and is not described in FIG.
- processing similar to that performed by HNB-S2, HNB-T3, and HNB-GW4 in steps S201 and S202 of FIG. 5 is performed in steps S601 and S602, and HNB-S2, HNB-T3, and Performed by the CN node 5.
- step S603 the HNB-T3 transmits an Iu-UP Init message including the RFCI information of the HNB-T3 to the CN node 5 via the HNB-GW4.
- the CN node 5 terminates the Iu-UP Init message in the Iu-UP frame control unit 54C, and the HNB-T3 RFCI information included in the Iu-UP Init message and the previously acquired HNB-S2 RFCI information. Compare with.
- step S604 the CN node 5 sends a response to the Iu-UP Init message by transmitting an Iu-UP Init ACK message to the HNB-T3 via the HNB-GW4.
- step S603 if the RFCI information of HNB-S2 and HNB-T3 do not match, CN node 5 matches the RFCI information of HNB-T3 with the RFCI information of HNB-S2, so in step S605, HNB-S2 The Iu-UP Init message including the RFCI information is transmitted to the HNB-T3 via the HNB-GW4.
- step S606 the HNB-T3 sends a response to the Iu-UP Init message by transmitting an Iu-UP Init ACK message to the CN node 5 via the HNB-GW4. Also, the HNB-T3 initializes the RFCI information of the HNB-T3 and resets it to the RFCI information of the HNB-S2 included in the Iu-UP Init message.
- 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- This is the same as the processing performed by GW4.
- the CN node 5 notifies the HNB-S2 of the RFCI information of the HNB-S2 to the HNB-T3 by an Iu-UP Init message, so that the HNB-T3 takes over the RFCI information from the HNB-S2. Is possible.
- Non-Patent Document 2 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 Modification by RANAP or without Intra HNB-GW relocation.
- Non-Patent Document 2 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 Modification by RANAP or without Intra HNB-GW relocation.
- the mobile communication system of this embodiment is characterized by HNB-S2 and HNB-T3, and HNB-GW4.
- each of the HNB-S2 and the HNB-T3 notifies the RFCI information to the HNB-GW4, and when the HNB-GW4 does not match the RFCI information of the HNB-S2 and the HNB-T3, the 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 the HNB-S2.
- 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, a transmission / reception unit 22D that transmits the first message to the HNB-GW4, Have
- 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.
- the HNB-GW 4 of the present embodiment receives the first message from the HNB-S2 and receives the second message from the HNB-T3, and the HNB included in the first message.
- 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
- the control unit 43D that performs the RFCI conversion for converting the RFCI value added to the voice data into the RFCI value indicating the data frame having the same structure as the voice data in the RFCI information of the HNB-S2.
- step S701 the HNB-S2 transmits a first message including the RFCI information of the HNB-S2 to the HNB-GW4.
- step S702 the HNB-T3 transmits a second message including the HCI-T3 RFCI information to the HNB-GW4.
- the HNB-GW 4 stores the HNB-S2 RFCI information included in the first message and the HNB-T3 RFCI information included in the second message in the storage unit 42D. Also, the RFCI information of HNB-S2 and HNB-T3 is compared.
- step S703 UE1 transmits / receives voice data (user data) to / from HNB-GW4 via HNB-T3.
- the HCI-S2 and the HNB-T3 do not match the RFCI information
- the HCI-S2 adds the RFCI value added to the audio data.
- RFCI conversion is performed to convert the data frame into the RFCI value indicating the data frame having the same structure as the voice data.
- the HNB-GW 4 transmits the voice data to which the RFCI converted RFCI value is added to the CN 6.
- the HNB-GW 4 transmits the voice data received from the HNB-T3 and the RFCI value added to the voice data to the CN 6 as they are. To do.
- the HNB-GW 4 when the HNB-S4 and the HNB-T3 do not match the RFCI information, the HNB-GW 4 subsequently converts the RFCI value added to the audio data received from the HNB-T3 to the HNB-T3. -Convert to an RFCI value indicating a data frame of the same structure in the RFCI information of S2.
- each of the HNB-S2 and the HNB-T3 notifies the RFCI information to the HNB-GW4 by an Iu-UP Init message, and the HNB-GW4 matches the RFCI information of the HNB-S2 and the HNB-T3. If not, the RFCI value added to the audio data received from the HNB-T3 is converted into an RFCI value indicating a data frame having the same structure in the RFCI information of the HNB-S2.
- Non-patent Document 4 stipulates that messages of the Iu-UP protocol are not terminated by the HNB-GW.
- the specification of 3GPP is changed to allow the Iu-UP message to be terminated by the HNB-GW.
- the HNB-GW 4 of the present embodiment includes an HNB transceiver 41E, a RANAP function unit 42E, a CN transceiver 43E, an Iu-UP frame controller 44E, and an Iu-UP frame transfer unit. 45E, an RFCI holding unit 46E, and an RFCI conversion unit 47E.
- the HNB transceiver 41E constitutes the first transceiver 41D of FIG. 17
- the CN transceiver 43E constitutes the second transceiver 44D of FIG. 17
- the RFCI holding unit 46E 17 storage units 42D, and the other functional blocks form the control unit 43B of FIG.
- the HNB-S2 of the present embodiment includes an anti-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.
- the HNB-GW transmission / reception unit 21E constitutes the transmission / reception unit 22D of FIG. 17, and the other functional blocks constitute the control unit 21D of FIG.
- the HNB-T3 of the present embodiment includes an anti-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.
- the HNB-GW transmission / reception unit 31E constitutes the transmission / reception unit 32D of FIG. 17, and the other functional blocks constitute the control unit 31D of FIG.
- the RFCI conversion unit 47E performs an RFCI conversion for converting the RFCI value added to the audio data received from the HNB-T3 into an RFCI value indicating a data frame having the same structure in the RFCI information of the HNB-S2.
- the other HNB transceiver 41E, the RANAP function unit 42E, the CN transceiver 43E, the Iu-UP frame controller 44E, the Iu-UP frame transfer unit 45E, and the RFCI holding unit 46E are respectively 4 performs the same operations as those for the HNB transmission / reception unit 41B, the RANAP function unit 42B, the CN transmission / reception unit 43B, the Iu-UP frame control unit 44B, the Iu-UP frame transfer unit 45B, and the RFCI holding unit 46B shown in FIG. .
- 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 are respectively connected to the HNB-GW transmission / reception shown in FIG. Operations similar to those of the unit 21B, the RANAP function unit 22B, the Iu-UP frame control unit 23B, and the Iu-UP frame transfer unit 24B are performed.
- 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 are respectively connected to the HNB-GW transmission / reception shown in FIG. Operations similar to those of the unit 31B, the RANAP function unit 32B, the Iu-UP frame control unit 33B, and the Iu-UP frame transfer unit 34B are performed.
- HNB-GW 4 has previously acquired the RFC information of the HNB-S2. That is, when establishing communication between HNB-S2 and HNB-X8, HNB-S2 sends an Iu-UP Init message including the RFCI information of HNB-S2 to HNB-GW4. , HNB-GW4 acquires the RFCI information of HNB-S2. This procedure is performed before step S801 in FIG. 20, and is not described in FIG.
- steps S801 and S802 similar to the processing in steps S201 and S202 in FIG. 5 is performed.
- step S803 the HNB-T3 transmits an Iu-UP Init message including the RFCI information of the HNB-T3 to the HNB-GW4.
- the HNB-GW 4 terminates the Iu-UP Init message at the Iu-UP frame control unit 44E, and the HNB-T3 RFCI information included in the Iu-UP Init message and the HNB-S2 previously obtained RFCI information. Compare with.
- step S804 the HNB-GW 4 sends a response to the Iu-UP Init message by transmitting an Iu-UP Init ACK message to the HNB-T3.
- Steps S805 to S812 Similar to the processing of Steps S203 to S211 of FIG. 5 is performed, and then UE1 transmits the HNB-GW4 and the voice data (user data) via HNB-T3 in Step S813. Send and receive.
- 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 do not match.
- 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 subjected to RFCI conversion.
- the HNB-GW 4 transfers the audio data transmitted from the UE 1 via the HNB-T3 from the Iu-UP frame transfer unit 45E to the RFCI conversion unit 47E, and adds it to the audio data at the RFCI conversion unit 47E.
- the RFCI conversion is performed for converting the RFCI value thus converted into an RFCI value indicating a data frame having the same structure as the voice data in the RFCI information of the HNB-S2. Thereafter, the audio data to which the RFCI-converted RFCI value is added is transferred to the Iu-UP frame transfer unit 45E and transmitted to the CN 6 via the CN transmission / reception unit 43E.
- the HNB-GW 4 when the HNB-S4 and the HNB-T3 do not match the RFCI information, the HNB-GW 4 subsequently converts the RFCI value added to the audio data received from the HNB-T3 to the HNB-T3. -Convert to an RFCI value indicating a data frame of the same structure in the RFCI information of S2.
- Non-Patent Document 4 the description in 7.2 of 3GPP TS25.467 (Non-Patent Document 4), which is changed according to the present embodiment, is as follows.
- Iu-UP terminates only at CN, HNB, and HNB-GW.
- control information handed over from the HNB-S2 to the HNB-T3 has been described as being only the RFCI information.
- the present invention is not limited to this, and the IPTI (Inter PDU Transmission Interval) is used. ) Additional information may be taken over.
- the IPTI information defines the data transmission interval (cycle) of the subflow, and the IPTI information uniquely calculates the audio data based on the toll data size of the subflow and the AMR codec rate without taking over the audio data. can do.
- the present invention can be applied to intra-HNB-GW relocation between HNBs.
- the present invention is based on inter-HNB-GW relocation (HNB-S2 and HNB-T3). May be applied to a relocation where the HNB-GW to which is connected is not the same.
- the HNB-T3 transmits the HNB-T3 RFCI information included in the Iu-UP Init message, but at the time of attempting to transmit the Iu-UP Init message. If the HNB-S2 RFCI information is received, the transmission of the Iu-UP Init message by the HNB-T3 may be prohibited.
- the method performed in the HNB-S, HNB-T, HNB-GW, and CN node of the present invention may be applied to a program for causing a computer to execute.
- the program can be stored in a storage medium and can be provided to the outside via a network.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
端末と、前記端末が移動前に接続する移動元基地局と、前記端末が移動後に接続する移動先基地局と、前記移動元基地局および前記移動先基地局を配下に持つ上位装置と、を有してなる移動通信システムであって、
前記移動元基地局および前記移動先基地局は、音声符号化における制御情報が予め設定されており、
前記移動元基地局は、自局の前記制御情報を第1のメッセージに含め、該第1のメッセージを前記上位装置に送信し、
前記上位装置は、前記移動元基地局の前記制御情報を第2のメッセージに含め、該第2のメッセージを前記移動先基地局に送信する。
端末と、前記端末が移動前に接続する移動元基地局と、前記端末が移動後に接続する移動先基地局と、前記移動元基地局および前記移動先基地局をコアネットワークに接続するゲートウェイ装置と、を有してなる移動通信システムであって、
前記移動元基地局および前記移動先基地局は、音声符号化における制御情報として、識別子ごとに、該識別子が示す、音声符号化された音声データのデータフレームの構造を識別する制御情報が予め設定されており、
前記移動元基地局は、自局の前記制御情報を第1のメッセージに含め、該第1のメッセージを前記ゲートウェイ装置に送信し、
前記移動先基地局は、自局の前記制御情報を第2のメッセージに含め、該第2のメッセージを前記ゲートウェイ装置に送信し、
前記ゲートウェイ装置は、
前記第1のメッセージに含まれる、前記移動元基地局の前記制御情報と、前記第2のメッセージに含まれる、前記移動先基地局の前記制御情報と、を格納し、
前記移動元基地局および前記移動先基地局の前記制御情報が一致しない場合、以降に、前記移動先基地局から音声データを受信すると、該音声データに付加されている識別子を、前記移動元基地局の前記制御情報内で同じ構造のデータフレームを示している識別子に変換し、
前記変換された識別子が付加された音声データを前記コアネットワークに送信する。
端末が移動前に接続する移動元の基地局であって、
音声符号化における制御情報が予め設定されており、自局の前記制御情報をメッセージに含める制御部と、
前記メッセージを上位装置に送信する送受信部と、を有する。
端末が移動後に接続する移動先の基地局であって、
音声符号化における制御情報が予め設定されている制御部と、
上位装置から、前記端末が移動前に接続していた移動元の基地局の前記制御情報を含む第1のメッセージを受信する送受信部と、を有する。
端末が移動前に接続する移動元基地局と、前記端末が移動後に接続する移動先基地局と、を配下に持つ上位装置であって、
前記移動元基地局および前記移動先基地局は、音声符号化における制御情報が予め設定されており、
前記移動元基地局から、前記移動元基地局の前記制御情報を含む第1のメッセージを受信する送受信部と、
前記移動元基地局の前記制御情報を第2のメッセージに含める制御部と、を有し、
前記送受信部は、前記第2のメッセージを前記移動先基地局に送信する。
端末が移動前に接続する移動元基地局と、前記端末が移動後に接続する移動先基地局と、をコアネットワークに接続するゲートウェイ装置であって、
前記移動元基地局および前記移動先基地局は、音声符号化における制御情報として、識別子ごとに、該識別子が示す、音声符号化された音声データのデータフレームの構造を識別する制御情報が予め設定されており、
前記移動元基地局から、前記移動元基地局の前記制御情報を含む第1のメッセージを受信するとともに、前記移動先基地局から、前記移動先基地局の前記制御情報を含む第2のメッセージを受信する送受信部と、
前記第1のメッセージに含まれる、前記移動元基地局の前記制御情報と、前記第2のメッセージに含まれる、前記移動先基地局の前記制御情報と、を格納する記憶部と、
前記移動元基地局および前記移動先基地局の前記制御情報が一致しない場合、以降に、前記移動先基地局から音声データを受信すると、該音声データに付加されている識別子を、前記移動元基地局の前記制御情報内で同じ構造のデータフレームを示している識別子に変換する制御部と、
前記変換された識別子が付加された音声データを前記コアネットワークに送信する第2の送受信部と、を有する。
端末と、前記端末が移動前に接続する移動元基地局と、前記端末が移動後に接続する移動先基地局と、前記移動元基地局および前記移動先基地局を配下に持つ上位装置と、を有してなる移動通信システムによる通信方法であって、
前記移動元基地局が、自局の音声符号化における制御情報を第1のメッセージに含め、該第1のメッセージを前記上位装置に送信するステップと、
前記上位装置が、前記移動元基地局の前記制御情報を第2のメッセージに含め、該第2のメッセージを前記移動先基地局に送信するステップと、を有する。
端末と、前記端末が移動前に接続する移動元基地局と、前記端末が移動後に接続する移動先基地局と、前記移動元基地局および前記移動先基地局をコアネットワークに接続するゲートウェイ装置と、を有してなる移動通信システムによる通信方法であって、
前記移動元基地局が、自局の音声符号化における制御情報として、識別子ごとに、該識別子が示す、音声符号化された音声データのデータフレームの構造を識別する制御情報を第1のメッセージに含め、該第1のメッセージを前記ゲートウェイ装置に送信するステップと、
前記移動先基地局が、自局の前記制御情報を第2のメッセージに含め、該第2のメッセージを前記ゲートウェイ装置に送信するステップと、
前記ゲートウェイ装置が、前記第1のメッセージに含まれる、前記移動元基地局の前記制御情報と、前記第2のメッセージに含まれる、前記移動先基地局の前記制御情報と、を格納するステップと、
前記ゲートウェイ装置が、前記移動元基地局および前記移動先基地局の前記制御情報が一致しない場合、以降に、前記移動先基地局から音声データを受信すると、該音声データに付加されている識別子を、前記移動元基地局の前記制御情報内で同じ構造のデータフレームを示している識別子に変換するステップと、
前記ゲートウェイ装置が、前記変換された識別子が付加された音声データを前記コアネットワークに送信するステップと、を有する。
端末が移動前に接続する移動元の基地局による通信方法であって、
自局の音声符号化における制御情報をメッセージに含めるステップと、
前記メッセージを上位装置に送信するステップと、を有する。
端末が移動後に接続する移動先の基地局による通信方法であって、
上位装置から、前記端末が移動前に接続していた移動元の基地局の音声符号化における制御情報を含む第1のメッセージを受信するステップと、を有する。
端末が移動前に接続する移動元基地局と、前記端末が移動後に接続する移動先基地局と、を配下に持つ上位装置による通信方法であって、
前記移動元基地局から、前記移動元基地局の音声符号化における制御情報を含む第1のメッセージを受信するステップと、
前記移動元基地局の前記制御情報を第2のメッセージに含めるステップと、
前記第2のメッセージを前記移動先基地局に送信するステップと、を有する。
端末が移動前に接続する移動元基地局と、前記端末が移動後に接続する移動先基地局と、をコアネットワークに接続するゲートウェイ装置による通信方法であって、
前記移動元基地局から、前記移動元基地局の音声符号化における制御情報として、識別子ごとに、該識別子が示す、音声符号化された音声データのデータフレームの構造を識別する制御情報を含む第1のメッセージを受信するとともに、前記移動先基地局から、前記移動先基地局の前記制御情報を含む第2のメッセージを受信するステップと、
前記第1のメッセージに含まれる、前記移動元基地局の前記制御情報と、前記第2のメッセージに含まれる、前記移動先基地局の前記制御情報と、を格納するステップと、
前記移動元基地局および前記移動先基地局の前記制御情報が一致しない場合、以降に、前記移動先基地局から音声データを受信すると、該音声データに付加されている識別子を、前記移動元基地局の前記制御情報内で同じ構造のデータフレームを示している識別子に変換するステップと、
前記変換された識別子が付加された音声データを前記コアネットワークに送信するステップと、を有する。
端末が移動前に接続する移動元の基地局に、
自局の音声符号化における制御情報をメッセージに含める手順と、
前記メッセージを上位装置に送信する手順と、を実行させる。
端末が移動後に接続する移動先の基地局に、
上位装置から、前記端末が移動前に接続していた移動元の基地局の音声符号化における制御情報を含む第1のメッセージを受信する手順を実行させる。
端末が移動前に接続する移動元基地局と、前記端末が移動後に接続する移動先基地局と、を配下に持つ上位装置に、
前記移動元基地局から、前記移動元基地局の音声符号化における制御情報を含む第1のメッセージを受信する手順と、
前記移動元基地局の前記制御情報を第2のメッセージに含める手順と、
前記第2のメッセージを前記移動先基地局に送信する手順と、を実行させる。
端末が移動前に接続する移動元基地局と、前記端末が移動後に接続する移動先基地局と、をコアネットワークに接続するゲートウェイ装置に、
前記移動元基地局から、前記移動元基地局の音声符号化における制御情報として、識別子ごとに、該識別子が示す、音声符号化された音声データのデータフレームの構造を識別する制御情報を含む第1のメッセージを受信するとともに、前記移動先基地局から、前記移動先基地局の前記制御情報を含む第2のメッセージを受信する手順と、
前記第1のメッセージに含まれる、前記移動元基地局の前記制御情報と、前記第2のメッセージに含まれる、前記移動先基地局の前記制御情報と、を格納する手順と、
前記移動元基地局および前記移動先基地局の前記制御情報が一致しない場合、以降に、前記移動先基地局から音声データを受信すると、該音声データに付加されている識別子を、前記移動元基地局の前記制御情報内で同じ構造のデータフレームを示している識別子に変換する手順と、
前記変換された識別子が付加された音声データを前記コアネットワークに送信する手順と、を実行させる。
(第1の実施形態)
本実施形態は、HNB-S2およびHNB-T3と、HNB-GW4またはCNノード5のいずれかである上位装置(以下、上位装置9と称す)と、に特徴がある。
(第2の実施形態)
本実施形態は、上位装置9をHNB-GW4として、第1の実施形態をより具体化した例である。
(1)第1の規定
3GPP TS25.415(非特許文献2)では、UEとCN間の無線アクセスベアラ(RAB:Radio Access Bearer)に関するRABパラメータを、CNとRNC(HNB-GW)間でRANAPメッセージにより通知することが規定されている。具体的には、RABパラメータは、サービスの種類に応じたQoS(Quality of Service)のパラメータ(データ伝送レート、ブロックサイズ、エラー率など)である。
(2)第2の規定
上記第1の規定の問題は、Iu-UP Initializationメッセージを、HNB-GWで終端する(すなわち、CNで終端しない)ことで、解決することができると考えられる。
(1)第1のメリット
RANAPメッセージは、HNBおよびHNB-GWにて終端することが3GPP TS 25.467(非特許文献4)に規定されている。そのため、RANAPメッセージに本実施形態に関する機能を追加する上で、新規にプロトコルを追加でサポートする必要がないというメリットがある。
(2)第2のメリット
現在、3GPPでは、Intra HNB-GW Relocation手順が検討されているが、本手順の信号にRANAPメッセージを使用することが一般的である。そのため、RANAPメッセージに本実施形態に関する機能を追加することで、Intra HNB-GW Relocation手順に新たな信号を追加する必要がないというメリットがある。
(第3の実施形態)
本実施形態は、上位装置9をHNB-GW4として、第1の実施形態をより具体化した例である。
(第4の実施形態)
本実施形態は、上位装置9をHNB-GW4として、第1の実施形態をより具体化した例である。
(第5の実施形態)
本実施形態は、上位装置9をHNB-GW4として、第1の実施形態をより具体化した例である。また、本実施形態の構成は、図4に示した第2の実施形態の構成と同様である。
(第6の実施形態)
本実施形態は、上位装置9をCNノード5として、第1の実施形態をより具体化した例である。
(第7の実施形態)
本実施形態の移動通信システムは、HNB-S2およびHNB-T3と、HNB-GW4と、に特徴がある。
(第8の実施形態)
本実施形態は、第7の実施形態をより具体化した例である。
Claims (40)
- 端末と、前記端末が移動前に接続する移動元基地局と、前記端末が移動後に接続する移動先基地局と、前記移動元基地局および前記移動先基地局を配下に持つ上位装置と、を有してなる移動通信システムであって、
前記移動元基地局および前記移動先基地局は、音声符号化における制御情報が予め設定されており、
前記移動元基地局は、自局の前記制御情報を第1のメッセージに含め、該第1のメッセージを前記上位装置に送信し、
前記上位装置は、前記移動元基地局の前記制御情報を第2のメッセージに含め、該第2のメッセージを前記移動先基地局に送信する、移動通信システム。 - 前記移動先基地局は、前記上位装置から前記第2のメッセージを受信すると、自局の前記制御情報を初期化し、前記第2のメッセージに含まれる、前記移動元基地局の前記制御情報に設定する、請求項1に記載の移動通信システム。
- 前記上位装置は、前記移動元基地局および前記移動先基地局をコアネットワークに接続するゲートウェイ装置であり、
前記第1のメッセージは、前記移動元基地局からの前記端末の移動を要求する時に、前記移動元基地局から前記ゲートウェイ装置に対して送信するRANAP:Relocation Requiredメッセージであり、
前記第2のメッセージは、前記移動先基地局への前記端末の移動を要求する時に、前記ゲートウェイ装置から前記移動先基地局に対して送信するRANAP:Relocation Requestメッセージである、請求項1または2に記載の移動通信システム。 - 前記移動先基地局は、前記ゲートウェイ装置から前記RANAP:Relocation Requestメッセージを受信すると、音声データを転送可能な状態に遷移する、請求項3に記載の移動通信システム。
- 前記上位装置は、前記移動元基地局および前記移動先基地局をコアネットワークに接続するゲートウェイ装置であり、
前記第1のメッセージは、前記移動元基地局からの前記端末の移動を要求する時に、前記移動元基地局から前記ゲートウェイ装置に対して送信するRANAP:Relocation Requiredメッセージを転送するために使用する、RUA Direct Transferメッセージであり、
前記第2のメッセージは、前記移動先基地局への前記端末の移動を要求する時に、前記ゲートウェイ装置から前記移動先基地局に対して送信するRANAP:Relocation Requestメッセージを転送するために使用する、RUA Direct Transferメッセージである、請求項1または2に記載の移動通信システム。 - 前記移動先基地局は、前記ゲートウェイ装置から前記RUA Direct Transferメッセージを受信すると、音声データを転送可能な状態に遷移する、請求項5に記載の移動通信システム。
- 前記上位装置は、前記移動元基地局および前記移動先基地局をコアネットワークに接続するゲートウェイ装置であり、
前記第1のメッセージは、前記移動元基地局からの前記端末の移動を要求する時に、前記移動元基地局から前記ゲートウェイ装置に対して送信するHNBAP:Relocation Requiredメッセージであり、
前記第2のメッセージは、前記移動先基地局への前記端末の移動を要求する時に、前記ゲートウェイ装置から前記移動先基地局に対して送信するHNBAP:Relocation Requestメッセージである、請求項1または2に記載の移動通信システム。 - 前記移動先基地局は、前記ゲートウェイ装置から前記HNBAP:Relocation Requestメッセージを受信すると、音声データを転送可能な状態に遷移する、請求項7に記載の移動通信システム。
- 前記移動先基地局は、自局の前記制御情報を第3のメッセージに含め、該第3のメッセージを前記上位装置に送信し、
前記上位装置は、前記移動元基地局および前記移動先基地局の前記制御情報が一致しない場合に、前記第2のメッセージを前記移動先基地局に送信する、請求項1または2に記載の移動通信システム。 - 前記上位装置は、前記移動元基地局および前記移動先基地局をコアネットワークに接続するゲートウェイ装置であり、
前記第1のメッセージは、前記移動元基地局が前記端末の通信相手の端末を配下に持つ基地局との通信を確立する時に、前記移動元基地局から前記ゲートウェイ装置に対して送信するIu-UP Initializationメッセージであり、
前記第2のメッセージは、前記移動先基地局が前記端末の通信相手の端末を配下に持つ基地局との通信を確立する時に、前記ゲートウェイ装置から前記移動先基地局に対して送信するIu-UP Initializationメッセージであり、
前記第3のメッセージは、前記移動先基地局が前記端末の通信相手の端末を配下に持つ基地局との通信を確立する時に、前記移動先基地局から前記ゲートウェイ装置に対して送信するIu-UP Initializationメッセージである、請求項9に記載の移動通信システム。 - 前記上位装置は、コアネットワーク内に配置されたコアネットワーク装置であり、
前記第1のメッセージは、前記移動元基地局が前記端末の通信相手の端末を配下に持つ基地局との通信を確立する時に、前記移動元基地局から前記コアネットワーク装置に対して送信するIu-UP Initializationメッセージであり、
前記第2のメッセージは、前記移動先基地局が前記端末の通信相手の端末を配下に持つ基地局との通信を確立する時に、前記コアネットワーク装置から前記移動先基地局に対して送信するIu-UP Initializationメッセージであり、
前記第3のメッセージは、前記移動先基地局が前記端末の通信相手の端末を配下に持つ基地局との通信を確立する時に、前記移動先基地局から前記コアネットワーク装置に対して送信するIu-UP Initializationメッセージである、請求項9に記載の移動通信システム。 - 端末と、前記端末が移動前に接続する移動元基地局と、前記端末が移動後に接続する移動先基地局と、前記移動元基地局および前記移動先基地局をコアネットワークに接続するゲートウェイ装置と、を有してなる移動通信システムであって、
前記移動元基地局および前記移動先基地局は、音声符号化における制御情報として、識別子ごとに、該識別子が示す、音声符号化された音声データのデータフレームの構造を識別する制御情報が予め設定されており、
前記移動元基地局は、自局の前記制御情報を第1のメッセージに含め、該第1のメッセージを前記ゲートウェイ装置に送信し、
前記移動先基地局は、自局の前記制御情報を第2のメッセージに含め、該第2のメッセージを前記ゲートウェイ装置に送信し、
前記ゲートウェイ装置は、
前記第1のメッセージに含まれる、前記移動元基地局の前記制御情報と、前記第2のメッセージに含まれる、前記移動先基地局の前記制御情報と、を格納し、
前記移動元基地局および前記移動先基地局の前記制御情報が一致しない場合、以降に、前記移動先基地局から音声データを受信すると、該音声データに付加されている識別子を、前記移動元基地局の前記制御情報内で同じ構造のデータフレームを示している識別子に変換し、
前記変換された識別子が付加された音声データを前記コアネットワークに送信する、移動通信システム。 - 前記第1のメッセージは、前記移動元基地局が前記端末の通信相手の端末を配下に持つ基地局との通信を確立する時に、前記移動元基地局から前記ゲートウェイ装置に対して送信するIu-UP Initializationメッセージであり、
前記第2のメッセージは、前記移動先基地局が前記端末の通信相手の端末を配下に持つ基地局との通信を確立する時に、前記移動先基地局から前記ゲートウェイ装置に対して送信するIu-UP Initializationメッセージである、請求項12に記載の移動通信システム。 - 端末が移動前に接続する移動元の基地局であって、
音声符号化における制御情報が予め設定されており、自局の前記制御情報をメッセージに含める制御部と、
前記メッセージを上位装置に送信する送受信部と、を有する基地局。 - 前記上位装置は、自局をコアネットワークに接続するゲートウェイ装置であり、
前記メッセージは、自局からの前記端末の移動を要求する時に、自局から前記ゲートウェイ装置に対して送信するRANAP:Relocation Requiredメッセージである、請求項14に記載の基地局。 - 前記上位装置は、自局をコアネットワークに接続するゲートウェイ装置であり、
前記メッセージは、自局からの前記端末の移動を要求する時に、自局から前記ゲートウェイ装置に対して送信するRANAP:Relocation Requiredメッセージを転送するために使用する、RUA Direct Transferメッセージである、請求項14に記載の基地局。 - 前記上位装置は、自局をコアネットワークに接続するゲートウェイ装置であり、
前記メッセージは、自局からの前記端末の移動を要求する時に、自局から前記ゲートウェイ装置に対して送信するHNBAP:Relocation Requiredメッセージである、請求項14に記載の基地局。 - 前記上位装置は、コアネットワーク内に配置されたコアネットワーク装置であり、
前記メッセージは、自局が前記端末の通信相手の端末を配下に持つ基地局との通信を確立する時に、自局から前記コアネットワーク装置に対して送信するIu-UP Initializationメッセージである、請求項14に記載の基地局。 - 端末が移動後に接続する移動先の基地局であって、
音声符号化における制御情報が予め設定されている制御部と、
上位装置から、前記端末が移動前に接続していた移動元の基地局の前記制御情報を含む第1のメッセージを受信する送受信部と、を有する基地局。 - 前記制御部は、前記上位装置から前記第1のメッセージを受信すると、自局の前記制御情報を初期化し、前記第1のメッセージに含まれる、移動元の基地局の前記制御情報に設定する、請求項19に記載の基地局。
- 前記上位装置は、自局をコアネットワークに接続するゲートウェイ装置であり、
前記第1のメッセージは、自局への前記端末の移動を要求する時に、前記ゲートウェイ装置から自局に対して送信するRANAP:Relocation Requestメッセージである、請求項19または20に記載の基地局。 - 前記制御部は、前記ゲートウェイ装置から前記RANAP:Relocation Requestメッセージを受信すると、音声データを転送可能な状態に遷移する、請求項21に記載の基地局。
- 前記上位装置は、自局をコアネットワークに接続するゲートウェイ装置であり、
前記第1のメッセージは、自局への前記端末の移動を要求する時に、前記ゲートウェイ装置から自局に対して送信するRANAP:Relocation Requestメッセージを転送するために使用する、RUA Direct Transferメッセージである、請求項19または20に記載の基地局。 - 前記上位装置は、自局をコアネットワークに接続するゲートウェイ装置であり、
前記第1のメッセージは、自局への前記端末の移動を要求する時に、前記ゲートウェイ装置から自局に対して送信するHNBAP:Relocation Requestメッセージである、請求項19または20に記載の基地局。 - 前記制御部は、自局の前記制御情報を第2のメッセージに含め、
前記送受信部は、前記第2のメッセージを前記上位装置に送信し、また、前記上位装置において、自局および移動元の基地局の前記制御情報が一致しない場合に、前記上位装置から前記第1のメッセージを受信する、請求項19または20に記載の基地局。 - 前記上位装置は、コアネットワーク内に配置されたコアネットワーク装置であり、
前記第1のメッセージは、自局が前記端末の通信相手の端末を配下に持つ基地局との通信を確立する時に、前記コアネットワーク装置から自局に対して送信するIu-UP Initializationメッセージであり、
前記第2のメッセージは、自局が前記端末の通信相手の端末を配下に持つ基地局との通信を確立する時に、自局から前記コアネットワーク装置に対して送信するIu-UP Initializationメッセージである、請求項25に記載の基地局。 - 端末が移動前に接続する移動元基地局と、前記端末が移動後に接続する移動先基地局と、を配下に持つ上位装置であって、
前記移動元基地局および前記移動先基地局は、音声符号化における制御情報が予め設定されており、
前記移動元基地局から、前記移動元基地局の前記制御情報を含む第1のメッセージを受信する送受信部と、
前記移動元基地局の前記制御情報を第2のメッセージに含める制御部と、を有し、
前記送受信部は、前記第2のメッセージを前記移動先基地局に送信する、上位装置。 - 前記送受信部は、前記移動先基地局から、前記移動先基地局の前記制御情報を含む第3のメッセージを受信し、前記移動元基地局および前記移動先基地局の前記制御情報が一致しない場合に、前記第2のメッセージを前記移動先基地局に送信する、請求項27に記載の上位装置。
- 前記上位装置は、コアネットワーク内に配置されたコアネットワーク装置であり、
前記第1のメッセージは、前記移動元基地局が前記端末の通信相手の端末を配下に持つ基地局との通信を確立する時に、前記移動元基地局から前記コアネットワーク装置に対して送信するIu-UP Initializationメッセージであり、
前記第2のメッセージは、前記移動先基地局が前記端末の通信相手の端末を配下に持つ基地局との通信を確立する時に、前記コアネットワーク装置から前記移動先基地局に対して送信するIu-UP Initializationメッセージであり、
前記第3のメッセージは、前記移動先基地局が前記端末の通信相手の端末を配下に持つ基地局との通信を確立する時に、前記移動先基地局から前記コアネットワーク装置に対して送信するIu-UP Initializationメッセージである、請求項9に記載の移動通信システム。 - 端末が移動前に接続する移動元基地局と、前記端末が移動後に接続する移動先基地局と、をコアネットワークに接続するゲートウェイ装置であって、
前記移動元基地局および前記移動先基地局は、音声符号化における制御情報として、識別子ごとに、該識別子が示す、音声符号化された音声データのデータフレームの構造を識別する制御情報が予め設定されており、
前記移動元基地局から、前記移動元基地局の前記制御情報を含む第1のメッセージを受信するとともに、前記移動先基地局から、前記移動先基地局の前記制御情報を含む第2のメッセージを受信する送受信部と、
前記第1のメッセージに含まれる、前記移動元基地局の前記制御情報と、前記第2のメッセージに含まれる、前記移動先基地局の前記制御情報と、を格納する記憶部と、
前記移動元基地局および前記移動先基地局の前記制御情報が一致しない場合、以降に、前記移動先基地局から音声データを受信すると、該音声データに付加されている識別子を、前記移動元基地局の前記制御情報内で同じ構造のデータフレームを示している識別子に変換する制御部と、
前記変換された識別子が付加された音声データを前記コアネットワークに送信する第2の送受信部と、を有するゲートウェイ装置。 - 端末と、前記端末が移動前に接続する移動元基地局と、前記端末が移動後に接続する移動先基地局と、前記移動元基地局および前記移動先基地局を配下に持つ上位装置と、を有してなる移動通信システムによる通信方法であって、
前記移動元基地局が、自局の音声符号化における制御情報を第1のメッセージに含め、該第1のメッセージを前記上位装置に送信するステップと、
前記上位装置が、前記移動元基地局の前記制御情報を第2のメッセージに含め、該第2のメッセージを前記移動先基地局に送信するステップと、を有する通信方法。 - 端末と、前記端末が移動前に接続する移動元基地局と、前記端末が移動後に接続する移動先基地局と、前記移動元基地局および前記移動先基地局をコアネットワークに接続するゲートウェイ装置と、を有してなる移動通信システムによる通信方法であって、
前記移動元基地局が、自局の音声符号化における制御情報として、識別子ごとに、該識別子が示す、音声符号化された音声データのデータフレームの構造を識別する制御情報を第1のメッセージに含め、該第1のメッセージを前記ゲートウェイ装置に送信するステップと、
前記移動先基地局が、自局の前記制御情報を第2のメッセージに含め、該第2のメッセージを前記ゲートウェイ装置に送信するステップと、
前記ゲートウェイ装置が、前記第1のメッセージに含まれる、前記移動元基地局の前記制御情報と、前記第2のメッセージに含まれる、前記移動先基地局の前記制御情報と、を格納するステップと、
前記ゲートウェイ装置が、前記移動元基地局および前記移動先基地局の前記制御情報が一致しない場合、以降に、前記移動先基地局から音声データを受信すると、該音声データに付加されている識別子を、前記移動元基地局の前記制御情報内で同じ構造のデータフレームを示している識別子に変換するステップと、
前記ゲートウェイ装置が、前記変換された識別子が付加された音声データを前記コアネットワークに送信するステップと、を有する通信方法。 - 端末が移動前に接続する移動元の基地局による通信方法であって、
自局の音声符号化における制御情報をメッセージに含めるステップと、
前記メッセージを上位装置に送信するステップと、を有する通信方法。 - 端末が移動後に接続する移動先の基地局による通信方法であって、
上位装置から、前記端末が移動前に接続していた移動元の基地局の音声符号化における制御情報を含む第1のメッセージを受信するステップと、を有する通信方法。 - 端末が移動前に接続する移動元基地局と、前記端末が移動後に接続する移動先基地局と、を配下に持つ上位装置による通信方法であって、
前記移動元基地局から、前記移動元基地局の音声符号化における制御情報を含む第1のメッセージを受信するステップと、
前記移動元基地局の前記制御情報を第2のメッセージに含めるステップと、
前記第2のメッセージを前記移動先基地局に送信するステップと、を有する通信方法。 - 端末が移動前に接続する移動元基地局と、前記端末が移動後に接続する移動先基地局と、をコアネットワークに接続するゲートウェイ装置による通信方法であって、
前記移動元基地局から、前記移動元基地局の音声符号化における制御情報として、識別子ごとに、該識別子が示す、音声符号化された音声データのデータフレームの構造を識別する制御情報を含む第1のメッセージを受信するとともに、前記移動先基地局から、前記移動先基地局の前記制御情報を含む第2のメッセージを受信するステップと、
前記第1のメッセージに含まれる、前記移動元基地局の前記制御情報と、前記第2のメッセージに含まれる、前記移動先基地局の前記制御情報と、を格納するステップと、
前記移動元基地局および前記移動先基地局の前記制御情報が一致しない場合、以降に、前記移動先基地局から音声データを受信すると、該音声データに付加されている識別子を、前記移動元基地局の前記制御情報内で同じ構造のデータフレームを示している識別子に変換するステップと、
前記変換された識別子が付加された音声データを前記コアネットワークに送信するステップと、を有する通信方法。 - 端末が移動前に接続する移動元の基地局に、
自局の音声符号化における制御情報をメッセージに含める手順と、
前記メッセージを上位装置に送信する手順と、を実行させるプログラム。 - 端末が移動後に接続する移動先の基地局に、
上位装置から、前記端末が移動前に接続していた移動元の基地局の音声符号化における制御情報を含む第1のメッセージを受信する手順を実行させるプログラム。 - 端末が移動前に接続する移動元基地局と、前記端末が移動後に接続する移動先基地局と、を配下に持つ上位装置に、
前記移動元基地局から、前記移動元基地局の音声符号化における制御情報を含む第1のメッセージを受信する手順と、
前記移動元基地局の前記制御情報を第2のメッセージに含める手順と、
前記第2のメッセージを前記移動先基地局に送信する手順と、を実行させるプログラム。 - 端末が移動前に接続する移動元基地局と、前記端末が移動後に接続する移動先基地局と、をコアネットワークに接続するゲートウェイ装置に、
前記移動元基地局から、前記移動元基地局の音声符号化における制御情報として、識別子ごとに、該識別子が示す、音声符号化された音声データのデータフレームの構造を識別する制御情報を含む第1のメッセージを受信するとともに、前記移動先基地局から、前記移動先基地局の前記制御情報を含む第2のメッセージを受信する手順と、
前記第1のメッセージに含まれる、前記移動元基地局の前記制御情報と、前記第2のメッセージに含まれる、前記移動先基地局の前記制御情報と、を格納する手順と、
前記移動元基地局および前記移動先基地局の前記制御情報が一致しない場合、以降に、前記移動先基地局から音声データを受信すると、該音声データに付加されている識別子を、前記移動元基地局の前記制御情報内で同じ構造のデータフレームを示している識別子に変換する手順と、
前記変換された識別子が付加された音声データを前記コアネットワークに送信する手順と、を実行させるプログラム。
Priority Applications (17)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR1020147008049A KR20140046085A (ko) | 2009-08-12 | 2010-06-02 | 이동 통신 시스템, 기지국, 상위 장치, 게이트웨이 장치 및 통신 방법 |
BR122016009666A BR122016009666A2 (pt) | 2009-08-12 | 2010-06-02 | estação base de destino de movimento, estação base de origem de movimento, aparelho de gateway, sistema de comunicação móvel e terminal |
KR1020127006142A KR101420945B1 (ko) | 2009-08-12 | 2010-06-02 | 이동 통신 시스템, 기지국, 상위 장치, 게이트웨이 장치 및 통신 방법 |
AU2010283393A AU2010283393B2 (en) | 2009-08-12 | 2010-06-02 | Mobile Communication System, Base Station, Higher-Order Apparatus, Gateway Apparatus, Communication Method, and Program |
EP10808100.1A EP2466988B1 (en) | 2009-08-12 | 2010-06-02 | Mobile communication system, base station, higher-order apparatus, communication method, and program |
BR122016009667A BR122016009667A2 (pt) | 2009-08-12 | 2010-06-02 | estação base de destino de movimento, estação base de origem de movimento, aparelho de gateway, sistema de comunicação móvel e terminal |
JP2011526699A JP5660040B2 (ja) | 2009-08-12 | 2010-06-02 | 移動通信システム、基地局、上位装置、ゲートウェイ装置、通信方法、プログラム |
CN201080035810.0A CN102474908B (zh) | 2009-08-12 | 2010-06-02 | 移动通信系统、基站、上位装置、网关装置、通信方法 |
BR122016009671A BR122016009671A2 (pt) | 2009-08-12 | 2010-06-02 | estação base de destino de movimento, estação base de origem de movimento, aparelho de gateway, sistema de comunicação móvel e terminal |
RU2012108887/07A RU2518437C2 (ru) | 2009-08-12 | 2010-06-02 | Система мобильной связи, базовая станция, устройство более высокого порядка, шлюзовое устройство, способ связи и программа |
BR122016009668A BR122016009668A2 (pt) | 2009-08-12 | 2010-06-02 | estação base de destino de movimento, estação base de origem de movimento, aparelho de gateway, sistema de comunicação móvel e terminal |
US13/389,396 US9020508B2 (en) | 2009-08-12 | 2010-06-02 | Mobile communication system, base station, higher-order apparatus, gateway apparatus, communication method, and program |
BR112012003079A BR112012003079A2 (pt) | 2009-08-12 | 2010-06-02 | sistema de comunicação móvel, estação base de uma origem de movimento, estação base de um destino de movimento, aparelho de ordem superior, aparelho de gateway, método de comunicação e programa |
CA2770738A CA2770738C (en) | 2009-08-12 | 2010-06-02 | Mobile communication system, base station, higher-order apparatus, gateway apparatus, communication method, and program |
US14/695,877 US9503937B2 (en) | 2009-08-12 | 2015-04-24 | Mobile communication system, base station, higher-order apparatus, gateway apparatus, communication method, and program |
US15/297,528 US20170041832A1 (en) | 2009-08-12 | 2016-10-19 | Mobile communication system, base station, higher-order apparatus, gateway apparatus, communication method, and program |
US15/885,030 US10172046B2 (en) | 2009-08-12 | 2018-01-31 | Mobile communication system, base station, higher-order apparatus, gateway apparatus, communication method, and program |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2009-187320 | 2009-08-12 | ||
JP2009187320 | 2009-08-12 |
Related Child Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/389,396 A-371-Of-International US9020508B2 (en) | 2009-08-12 | 2010-06-02 | Mobile communication system, base station, higher-order apparatus, gateway apparatus, communication method, and program |
US14/695,877 Continuation US9503937B2 (en) | 2009-08-12 | 2015-04-24 | Mobile communication system, base station, higher-order apparatus, gateway apparatus, communication method, and program |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2011018915A1 true WO2011018915A1 (ja) | 2011-02-17 |
Family
ID=43586095
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2010/059330 WO2011018915A1 (ja) | 2009-08-12 | 2010-06-02 | 移動通信システム、基地局、上位装置、ゲートウェイ装置、通信方法、プログラム |
Country Status (10)
Country | Link |
---|---|
US (4) | US9020508B2 (ja) |
EP (1) | EP2466988B1 (ja) |
JP (4) | JP5660040B2 (ja) |
KR (2) | KR101420945B1 (ja) |
CN (7) | CN105657759B (ja) |
AU (1) | AU2010283393B2 (ja) |
BR (5) | BR122016009668A2 (ja) |
CA (2) | CA2770738C (ja) |
RU (4) | RU2518437C2 (ja) |
WO (1) | WO2011018915A1 (ja) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105657759B (zh) | 2009-08-12 | 2019-12-27 | 日本电气株式会社 | 移动通信系统、基站、上位装置、网关装置、通信方法 |
US20170087060A1 (en) * | 2011-11-18 | 2017-03-30 | Sofsera Corporation | Tooth surface repairing material |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2002185555A (ja) * | 2000-12-14 | 2002-06-28 | Nec Corp | 通信方式および方法ならびに交換ノード |
JP2002185554A (ja) * | 2000-12-13 | 2002-06-28 | Nec Corp | 通信方式およびトランスコーダのアライメント方法 |
JP2009187320A (ja) | 2008-02-06 | 2009-08-20 | Nippon Telegr & Teleph Corp <Ntt> | サービス提供システム、サービス提供方法およびサービス提供プログラム |
Family Cites Families (28)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5663957A (en) * | 1995-07-12 | 1997-09-02 | Ericsson Inc. | Dual mode satellite/cellular terminal |
DE60026138T2 (de) | 2000-04-26 | 2006-10-26 | Fujitsu Ltd., Kawasaki | Mehrpunkt-kommunikationsverfahren und kommunikationssteuereinrichtung |
JP3518496B2 (ja) | 2000-08-23 | 2004-04-12 | 日本電気株式会社 | 移動体通信サービスシステム及びその提供方法 |
KR100428736B1 (ko) | 2001-04-26 | 2004-04-27 | 주식회사 현대시스콤 | 이동통신망 및 그의 운용방법 |
KR100837351B1 (ko) * | 2002-04-06 | 2008-06-12 | 엘지전자 주식회사 | 이동통신 시스템의 무선링크 파라미터 갱신 방법 |
US20060007861A1 (en) * | 2002-04-12 | 2006-01-12 | Siemens Aktiengesellschaft | Mechanism to support high speed circuit switched data services via an iu interface |
AU2002317686A1 (en) | 2002-05-31 | 2003-12-19 | Siemens Aktiengesellschaft | Interrogation of the current valid bit rate for the interruption of a trfo call |
RU2310277C2 (ru) * | 2002-06-07 | 2007-11-10 | Сименс Акциенгезелльшафт | Способ и устройство для передачи ip-пакетов между сетевым радиоконтроллером (rnc) и другим устройством сети мобильной радиосвязи |
KR100512359B1 (ko) | 2002-10-07 | 2005-09-02 | 엘지전자 주식회사 | 서로 다른 이동통신 시스템간의 메시지 변환 장치 및 방법 |
RU2006124546A (ru) | 2003-12-09 | 2008-01-20 | Алкател Уайрлесс, Инк. (Us) | Способ и система для основанной на пакетах работы без последовательного соединения |
US7580388B2 (en) | 2004-06-01 | 2009-08-25 | Lg Electronics Inc. | Method and apparatus for providing enhanced messages on common control channel in wireless communication system |
KR101141326B1 (ko) * | 2004-06-01 | 2012-05-03 | 엘지전자 주식회사 | 무선통신 시스템에서 공통제어채널 상의 개선된 메시지제공 방법 및 장치 |
US7729346B2 (en) * | 2004-09-18 | 2010-06-01 | Genband Inc. | UMTS call handling methods and apparatus |
CN100469189C (zh) * | 2005-09-20 | 2009-03-11 | 展讯通信(上海)有限公司 | 移动通信系统中主叫端及被主叫端的快速呼叫建立方法 |
CN1964564B (zh) * | 2005-10-10 | 2012-07-04 | 华为技术有限公司 | 无线通信系统中用户面承载资源分配方法及无线通信系统 |
US20070140293A1 (en) | 2005-12-16 | 2007-06-21 | Anjana Agarwal | RFCI mapping to support backward-compatible transcoder-free operation for UMTS |
KR20080106936A (ko) * | 2006-03-03 | 2008-12-09 | 가부시키가이샤 엔티티 도코모 | 기지국 및 핸드오버 제어방법 |
JP4838181B2 (ja) * | 2007-03-19 | 2011-12-14 | 株式会社エヌ・ティ・ティ・ドコモ | ハンドオーバ方法及び無線基地局 |
CN101370005B (zh) * | 2007-08-16 | 2012-07-18 | 中兴通讯股份有限公司 | 一种在高速分组接入信道上传输信令的方法 |
CN101374258B (zh) * | 2007-08-20 | 2012-07-04 | 华为技术有限公司 | 一种实现网络后向兼容的系统和附着、去附着方法 |
US20090262684A1 (en) * | 2008-04-18 | 2009-10-22 | Amit Khetawat | Method and Apparatus for Home Node B Registration using HNBAP |
CN101321320A (zh) * | 2008-06-03 | 2008-12-10 | 华为技术有限公司 | 多媒体回落的方法及移动交换中心 |
US20100041387A1 (en) * | 2008-08-15 | 2010-02-18 | Amit Khetawat | Method and Apparatus for Inter Home Node B Cell Update Handling |
US8331384B2 (en) * | 2009-05-12 | 2012-12-11 | Cisco Technology, Inc. | System and method for femto coverage in a wireless network |
CN105657759B (zh) * | 2009-08-12 | 2019-12-27 | 日本电气株式会社 | 移动通信系统、基站、上位装置、网关装置、通信方法 |
CN102714817B (zh) * | 2009-12-10 | 2016-11-23 | 日本电气株式会社 | 网关设备、中继方法、程序和毫微微系统 |
US20120002637A1 (en) * | 2010-06-18 | 2012-01-05 | Interdigital Patent Holdings, Inc. | Method and apparatus for supporting home node-b mobility |
EP3103313B1 (en) | 2014-02-09 | 2020-07-22 | Inductoheat, Inc. | Single shot inductor for heat treatment of closely spaced multiple eccentric cylindrical components arranged along the longitudinal axis of a workpiece |
-
2010
- 2010-06-02 CN CN201610084795.8A patent/CN105657759B/zh active Active
- 2010-06-02 BR BR122016009668A patent/BR122016009668A2/pt not_active Application Discontinuation
- 2010-06-02 RU RU2012108887/07A patent/RU2518437C2/ru active
- 2010-06-02 BR BR112012003079A patent/BR112012003079A2/pt not_active Application Discontinuation
- 2010-06-02 KR KR1020127006142A patent/KR101420945B1/ko active IP Right Grant
- 2010-06-02 CN CN201610085001.XA patent/CN105554826B/zh active Active
- 2010-06-02 CN CN201610085003.9A patent/CN105554827B/zh active Active
- 2010-06-02 CN CN201080035810.0A patent/CN102474908B/zh active Active
- 2010-06-02 AU AU2010283393A patent/AU2010283393B2/en active Active
- 2010-06-02 JP JP2011526699A patent/JP5660040B2/ja active Active
- 2010-06-02 WO PCT/JP2010/059330 patent/WO2011018915A1/ja active Application Filing
- 2010-06-02 CN CN201610084812.8A patent/CN105813149B/zh active Active
- 2010-06-02 KR KR1020147008049A patent/KR20140046085A/ko active Search and Examination
- 2010-06-02 BR BR122016009667A patent/BR122016009667A2/pt not_active Application Discontinuation
- 2010-06-02 BR BR122016009671A patent/BR122016009671A2/pt not_active Application Discontinuation
- 2010-06-02 US US13/389,396 patent/US9020508B2/en active Active
- 2010-06-02 CA CA2770738A patent/CA2770738C/en active Active
- 2010-06-02 CN CN201610084931.3A patent/CN105722160B/zh active Active
- 2010-06-02 CA CA2860689A patent/CA2860689C/en active Active
- 2010-06-02 BR BR122016009666A patent/BR122016009666A2/pt not_active Application Discontinuation
- 2010-06-02 CN CN201610085004.3A patent/CN105813150B/zh active Active
- 2010-06-02 EP EP10808100.1A patent/EP2466988B1/en active Active
-
2014
- 2014-02-18 RU RU2014105984/07A patent/RU2572564C2/ru active
- 2014-12-02 JP JP2014243951A patent/JP5928563B2/ja active Active
-
2015
- 2015-04-24 US US14/695,877 patent/US9503937B2/en active Active
- 2015-12-01 RU RU2015151398A patent/RU2640034C2/ru active
-
2016
- 2016-04-12 JP JP2016079476A patent/JP6315021B2/ja active Active
- 2016-10-19 US US15/297,528 patent/US20170041832A1/en not_active Abandoned
-
2017
- 2017-12-01 RU RU2017141859A patent/RU2671952C1/ru active
- 2017-12-08 JP JP2017235827A patent/JP6512271B2/ja active Active
-
2018
- 2018-01-31 US US15/885,030 patent/US10172046B2/en active Active
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2002185554A (ja) * | 2000-12-13 | 2002-06-28 | Nec Corp | 通信方式およびトランスコーダのアライメント方法 |
JP2002185555A (ja) * | 2000-12-14 | 2002-06-28 | Nec Corp | 通信方式および方法ならびに交換ノード |
JP2009187320A (ja) | 2008-02-06 | 2009-08-20 | Nippon Telegr & Teleph Corp <Ntt> | サービス提供システム、サービス提供方法およびサービス提供プログラム |
Non-Patent Citations (1)
Title |
---|
See also references of EP2466988A4 |
Also Published As
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP2706766B1 (en) | Network node, terminal, bandwidth modification determination method and bandwidth modification method | |
JP6512271B2 (ja) | 移動通信システム、基地局、上位装置、ゲートウェイ装置、通信方法、プログラム | |
AU2015201880A1 (en) | Mobile communication system, base station, higher-order apparatus, gateway apparatus, communication method, and program |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 201080035810.0 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 10808100 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2010283393 Country of ref document: AU |
|
ENP | Entry into the national phase |
Ref document number: 2010283393 Country of ref document: AU Date of ref document: 20100602 Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2011526699 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 13389396 Country of ref document: US |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2770738 Country of ref document: CA |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2010808100 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 20127006142 Country of ref document: KR Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2205/CHENP/2012 Country of ref document: IN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2012108887 Country of ref document: RU |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112012003079 Country of ref document: BR |
|
ENP | Entry into the national phase |
Ref document number: 112012003079 Country of ref document: BR Kind code of ref document: A2 Effective date: 20120210 |