WO2010013526A1 - 移動通信システム、制御装置、基地局装置、システム制御方法、および装置制御方法 - Google Patents

移動通信システム、制御装置、基地局装置、システム制御方法、および装置制御方法 Download PDF

Info

Publication number
WO2010013526A1
WO2010013526A1 PCT/JP2009/058991 JP2009058991W WO2010013526A1 WO 2010013526 A1 WO2010013526 A1 WO 2010013526A1 JP 2009058991 W JP2009058991 W JP 2009058991W WO 2010013526 A1 WO2010013526 A1 WO 2010013526A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
data
information
control
control device
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/JP2009/058991
Other languages
English (en)
French (fr)
Japanese (ja)
Inventor
佳央 植田
林　貞福
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
NEC Corp
Original Assignee
NEC Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to AU2009277764A priority Critical patent/AU2009277764B2/en
Priority to BR122014019674A priority patent/BR122014019674A2/pt
Priority to BR122015021024A priority patent/BR122015021024A2/pt
Priority to BR122015021029A priority patent/BR122015021029A2/pt
Priority to BR122015007063A priority patent/BR122015007063A2/pt
Priority to KR1020137003881A priority patent/KR101450487B1/ko
Priority to BR122015021023A priority patent/BR122015021023A2/pt
Priority to KR1020137003882A priority patent/KR101450488B1/ko
Priority to BR122015021028A priority patent/BR122015021028A2/pt
Priority to CA2732689A priority patent/CA2732689C/en
Priority to RU2011107746/07A priority patent/RU2486698C2/ru
Priority to BR122015021031A priority patent/BR122015021031A2/pt
Priority to KR1020137017049A priority patent/KR101497853B1/ko
Priority to US13/054,896 priority patent/US9113392B2/en
Priority to EP09802771.7A priority patent/EP2315471B1/en
Priority to BRPI0911022A priority patent/BRPI0911022A2/pt
Priority to BR122013013478A priority patent/BR122013013478A2/pt
Priority to KR1020147033302A priority patent/KR101497891B1/ko
Priority to BR122015007062A priority patent/BR122015007062A2/pt
Application filed by NEC Corp filed Critical NEC Corp
Priority to BR122015021026A priority patent/BR122015021026A2/pt
Priority to KR1020137003883A priority patent/KR101450489B1/ko
Priority to KR1020127026821A priority patent/KR101377836B1/ko
Priority to BR122015007068-6A priority patent/BR122015007068A2/pt
Priority to KR1020117004845A priority patent/KR101333855B1/ko
Priority to CN200980130582.2A priority patent/CN102113369B/zh
Priority to ES09802771.7T priority patent/ES2632397T3/es
Priority to JP2010522648A priority patent/JP5223922B2/ja
Publication of WO2010013526A1 publication Critical patent/WO2010013526A1/ja
Anticipated expiration legal-status Critical
Priority to US14/163,580 priority patent/US9072029B2/en
Priority to US14/474,358 priority patent/US9307480B2/en
Priority to US14/474,352 priority patent/US9247485B2/en
Priority to US14/474,380 priority patent/US9247486B2/en
Priority to US15/053,059 priority patent/US9565121B2/en
Priority to US15/380,455 priority patent/US9787541B2/en
Priority to US15/694,325 priority patent/US10404536B2/en
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/04—Registration at HLR or HSS [Home Subscriber Server]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/0816—Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/36—Flow control; Congestion control by determining packet size, e.g. maximum transfer unit [MTU]
    • H04L47/365—Dynamic adaptation of the packet size
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/02—Access restriction performed under specific conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/02—Access restriction performed under specific conditions
    • H04W48/06—Access restriction performed under specific conditions based on traffic conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/29—Control channels or signalling for resource management between an access point and the access point controlling device
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H04W92/12—Interfaces between hierarchically different network devices between access points and access point controllers
    • 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/02—Terminal 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/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/12—Access point controller devices

Definitions

  • the present invention relates to a mobile communication system that performs data communication with a fixed-length or variable-length data size.
  • HSDPA High Speed Downlink Packet Access
  • MAC-hs protocol or MAC-ehs protocol is used in the MAC (Medium Access Control) layer.
  • RNC Radio Network Controller
  • UE User Equipment
  • Node-B Node-B
  • the Node-B notifies the RNC of the allowable data amount, and the RNC transmits data to the Node-B within the allowable data amount.
  • the Node-B considers the capacity of the radio channel, the quality report notified from the UE, the priority assigned to the bearer, the state of the transmission path between the RNC and the Node-B as parameters. To determine the allowable data amount.
  • the allowable data amount is notified by a frame protocol control message called CAPACITY ALLOCATION.
  • FIG. 1 is a table showing an example of parameter settings in each case of HSDPA. Referring to FIG. 1, parameter setting examples in cases 1 to 3 are shown. Case 1 has already been defined in 3GPP release 5 and later, and cases 2 and 3 will be defined in 3GPP release 7 and later.
  • the size of the PDU (Protocol Data Unit) in the RLC (Radio Link Control) layer (hereinafter referred to as “RLC PDU size”) is a fixed length, and the MAC layer uses the MAC-hs protocol.
  • a PDU is a unit of a transmission signal in a predetermined protocol.
  • a PDU includes a header according to a predetermined protocol and a payload carrying data in that protocol.
  • 64QAM Quadrature Amplitude Modulation
  • MIMO Multiple Input Multiple Output
  • the RLC PDU size is fixed length as in Case 1, but the MAC layer uses the MAC-ehs protocol.
  • the MAC-ehs protocol 64QAM and MIMO can be used.
  • MAC-ehs a transmission method called Improved Layer 2 in Downlink is used.
  • 64QAM is one of digital modulation systems, and expresses 64 values by a combination of 8 types of phases and 8 types of amplitudes.
  • MIMO is a wireless communication technology that expands a data communication band by simultaneously using a plurality of antennas.
  • the MAC-ehs protocol arranged in Node-B divides user data.
  • Improved Layer 2 can transfer data more efficiently than a transmission method in which user data is divided into fixed lengths by RLC.
  • the RLC PDU size is variable length, and the MAC layer uses the MAC-ehs protocol.
  • Node-B specifies the maximum length of the RLC PDU size.
  • the RNC can select the RLC PDU size within the maximum length specified by the Node-B.
  • Node-B can control the maximum value of the RLC PDU size.
  • CAPACITY ALLOCATION TYPE 2 In the flow control of Release 7 of 3GPP where the MAC-ehs protocol is introduced, a format called CAPACITY ALLOCATION TYPE 2 is used instead of the format called CAPACITY ALLOCATION TYPE 1 used in Release 5 of 3GPP.
  • the NodeB can control the following four elements. (1) Maximum MAC-d / c PDU Length (MAC-d PDU length) (2) HS-DSCH Credit (the number of MAC-d PDUs that can be transmitted during the HS-DSCH transmission interval) (3) HS-DSCH interval (period in which the number of MAC-d PDUs indicated by HS-DSCH Credit is transmitted) (4) HS-DSCH Repetition Period (Number of repetitions indicating how many times the above period is repeated) For example, when the wireless line is congested, the MAC-d / c PDU length (Maximum MAC-d / c PDU Length) is reduced or the HS-DSCH Credit is reduced in order to reduce the amount of downlink data. That's fine. Note that HS-DSCH (High-Speed Downlink Shared Channel) is a channel shared by a plurality of HSDPA data communications.
  • Case 2 and Case 3 defined in 3GPP Release 7 or later differ in whether the RLC PDU size is fixed length or variable length.
  • the maximum value of the RLC PDU size can be changed in the range of 1504 octets or less in the flow control. As a result of such flow control, it becomes possible to perform data communication more efficiently according to a changing communication situation.
  • case 2 as in case 1, 64QAM and MIMO can be used while performing flow control using an existing and simple algorithm with a fixed RLC PDU size.
  • FIG. 2 is a table showing NBAP protocol parameters. This table is shown in 3GPP TS 24.433 9.2.1.31IA. Referring to FIG. 2, it can be seen that there is no information element to notify whether the RLC PDU size is a fixed length or a variable length, and the setting cannot be notified by the NBAP protocol. For this reason, there is a problem that the setting state of whether the RLC PDU size is fixed length or variable length may be inconsistent between the RNC and Node-B.
  • the current NBAP assumes that the HS-DSCH MAC-d PDU Size Format IE is “Flexible MAC-d PDU Size”.
  • the RNC sets the RLC PDU size as a fixed length
  • the Node-B sets the RLC PDU size as a variable length, which may cause a state mismatch between the RNC and the Node-B.
  • the Node-B may instruct the RNC to change the RLC PDU size in the flow control if the RLC PDU size is set to have a variable length. However, the RNC cannot change the RLC PDU size because the RLC PDU size is set to a fixed length.
  • the Node-B when the Node-B instructs the RNC to have a size larger than the fixed length set in the RNC, the Node-B can receive a PDU having a size larger than the fixed length.
  • the RNC if the RLC PDU size is set to a fixed length, the RNC will divide the data into a fixed length. In that case, the utilization efficiency of system resources such as bandwidth cannot be sufficiently increased.
  • Node-B instructs RNC that the size is smaller than the fixed length set in RNC
  • RNC with RNC PDU size set to fixed length cannot transmit data to Node-B.
  • data of a size exceeding the limit is sent to Node-B. In that case, a serious failure occurs in flow control and system operation.
  • FIG. 3 is a table showing an example of a communication form for explaining the problem of flow control.
  • FIG. 4 is a diagram illustrating an example of a sequence in which a flow control defect occurs.
  • the RLC-PDU size is 82 bytes
  • the MAC-ehs protocol is used
  • MIMO and 64QAM are used.
  • the RNC sets the RLC-PDU size as a fixed length (step 901).
  • the logical channel (Logical Channel) is not multiplexed in the MAC-d layer, and the MAC-d header is not added. Therefore, in this example, the MAC-d PDU size is equal to the RLC PDU size (step 902).
  • the RNC creates an NBAP: RL SETUP REQUEST message (step 903) and transmits it to the NodeB (step 904).
  • the NBAP: RL SETUP REQUEST message includes a Maximum MAC-d PDU Size Extended IE in which 82 bytes, which is the maximum value of the MAC-d PDU size, is set.
  • the NodeB recognizes that the maximum value of the MAC-d PDU size is 82 bytes by receiving the NBAP: RL SETUP REQUEST message (step 904), and sets the maximum value of 64QAM, MIMO, and MAC-ehs. Information is set together with the information (step 905).
  • Node-B decides to make the MAC-d PDU size smaller than 82 bytes due to congestion of the radio line in the flow control (step 908).
  • Node-B sets the maximum value of MAC-d PDU size to a new value smaller than 82 bytes (step 909) and HS-DSCH including Maximum MAC-d PDU Size Extended IE that sets the value.
  • the CAPACITY ALLOCATION TYPE 2 control frame is transmitted to the RNC (step 910). This frame is a frame used by the Node-B to notify the RNC of control information for flow control.
  • the flow control information includes MAC-d / c PDU Length, credits, and transmission interval.
  • the RNC Since the RLC PDU size is set to a fixed length, the RNC cannot transmit data shorter than the fixed length, and data communication stops (step 911).
  • An object of the present invention is to provide a technique for preventing a setting state of whether the data size of data communication is a fixed length or a variable length from being inconsistent between apparatuses in a mobile communication system.
  • a mobile communication system includes: A control device and a base station device; Data communication between the control device and the base station device is performed with a fixed length data size and a variable length data size, The control device transmits information indicating whether the data size of the data communication is a fixed length or a variable length, The base station apparatus receives the information from the control apparatus.
  • the control apparatus of the present invention a communication means for communicating with a base station apparatus using a fixed-length data size and a variable-length data size, Transmitting means for transmitting to the base station apparatus information indicating whether the data size of the data communication is a fixed length or a variable length.
  • a base station apparatus includes a control unit, communication means for communicating using a fixed-length data size and a variable-length data size, Receiving means for receiving, from the control device, information indicating whether the data size of the data communication is a fixed length or a variable length.
  • a system control method is a communication control method for a mobile communication system including a control device and a base station device, Data communication between the control device and the base station device is performed with a fixed length data size and a variable length data size, The control device transmits information indicating whether the data size of the data communication is a fixed length or a variable length, The base station apparatus receives the information from the control apparatus.
  • An apparatus control method communicates with a base station apparatus using a fixed-length data size and a variable-length data size, Information indicating whether the data size of the data communication is fixed length or variable length is transmitted to the base station apparatus.
  • FIG. 2 is a block diagram showing a configuration of Node-B 12 according to the first embodiment. It is a block diagram which shows the structure of the mobile communication system by 2nd Embodiment. It is a sequence diagram which shows operation
  • the wireless communication system shown as an embodiment of the present invention is a 3GPP W-CDMA mobile communication system.
  • FIG. 5 shows the configuration of the RNC 11 according to the first embodiment.
  • the RNC 11 determines whether the data size of the data communication is a fixed length or a variable length, and a communication unit 11A that communicates with the base station apparatus using a fixed length data size and a variable length data size.
  • the RNC 11 can notify the Node-B 12 of information (identification information) indicating whether the data size of data communication is fixed or variable.
  • FIG. 6 shows the configuration of the Node-B 12 according to the first embodiment.
  • the Node-B 12 receives information indicating whether the data size of data communication is a fixed length or a variable length from the control device (RNC 11), the control device, and the fixed length data.
  • the communication unit 12A communicates using a size and a variable length data size.
  • the Node-B 12 receives the information (identification information) transmitted from the RNC 11, so that the setting state of whether the transmission data size of the data communication is fixed length or variable length is inconsistent between the devices. Can be prevented.
  • FIG. 7 is a block diagram showing a configuration of a mobile communication system according to the second embodiment.
  • This embodiment embodies the configuration of the RNC 11 according to the first embodiment shown in FIG. 5 and the Node-B 11 according to the first embodiment shown in FIG.
  • the mobile communication system of this embodiment includes an RNC 11 and a Node-B 12.
  • the RNC 11 is connected to a CN (Core Network) (not shown) and a Node-B 11 and controls the Node-B 12 to realize communication of user data by a UE (not shown).
  • the Node-B 12 is connected to a UE (not shown) via a radio channel, and relays user data between the UE and the RNC 11.
  • the mobile communication system can perform data communication by HSDPA, and supports both cases where the transmission data size of downlink data by HSDPA is fixed length and variable length.
  • the RNC 11 notifies (transmits) identification information indicating whether the transmission data size of the downlink data is a fixed length or a variable length to the Node-B 12. This identification information is notified by a call control protocol message terminated by the RNC 11 and the Node-B 12.
  • the message used for notification of identification information is a message sent from the RNC 11 to the Node-B 12 when setting, changing, or adding a radio link.
  • the Node-B 12 operates based on the identification information notified from the RNC 11. For example, the Node-B 12 performs data communication flow control based on the identification information. In the flow control, the Node-B 12 adaptively changes a plurality of elements according to the communication status and notifies the RNC 11 of these elements.
  • the RNC 11 is within the limits of the notified elements, and according to the format of the downlink data size notified to the Node-B 12 by the identification information (whether the transmission data size of the downlink data is fixed length or variable length)
  • the downlink data is transmitted to Node-B12.
  • the amount of downlink data can be appropriately controlled according to the communication status, and congestion can be appropriately dealt with.
  • the elements of the flow control include, for example, an allowable transmission data size, an allowable data frame transmission interval, or an allowable number of data frame transmissions within a predetermined time.
  • the Node-B 12 performs flow control with the transmission data size fixed among these elements.
  • the identification information may be 1-bit information, for example. Specifically, when the bit is “1”, it indicates that the RLC PDU size is a variable length, and when it is “0”, it indicates that the RLC PDU size is a fixed length.
  • identification information indicating whether the transmission data size is fixed length or variable length is notified from the RNC 11 to the Node-B 12, and the Node-B 12 is based on the identification information notified from the RNC 11. Therefore, it is possible to prevent the setting state of whether the transmission data size is fixed length or variable length from being inconsistent between apparatuses.
  • the Node-B 12 when the radio link is set, if the RNC 11 notifies the Node-B 12 whether the transmission data size is a fixed length or a variable length, the Node-B 12 and the RNC 11 immediately after the radio link is set. Based on the matching recognition, flow control with a fixed transmission data size can be performed. Similarly, when it is notified whether the transmission data size is a fixed length or a variable length when the radio link is changed or added, the Node-B 12 sets the transmission data size immediately after changing or adding the radio link. Fixed flow control can be implemented.
  • the RNC 11 includes a transmission line termination unit 19, a call control unit 13 and a call control protocol processing unit 14 that form a control plane, an Iu interface termination unit 15 and an RLC protocol function unit 16 that form a user plane.
  • the call control unit 13 performs various processes related to call control. Call control includes establishment of a call when originating from or terminating at the UE and releasing the established call. Call control includes establishment and release of HSDPA communication by the UE. In call control, the call control unit 13 transmits / receives a call control message to / from the Node-B 12, UE, or CN.
  • the call control protocol processing unit 14 performs message editing and analysis of the NBAP protocol that is a call control protocol with the Node-B 12 under the control of the call control unit 13.
  • the call control unit 13 transmits / receives an NBAP protocol message to / from the Node-B 12 via the call control protocol processing unit 14, and performs MIMO, 64QAM, or MAC-ehs settings.
  • the Iu interface termination unit 15 terminates the Iu interface with the CN. More specifically, the Iu interface terminator 15 is a PDCP (Packet Data Convergence Protocol) defined in 3GPP TS25.323, an Iu user plane protocol defined in 3GPP TS25.415, or 3GPP TS29.
  • PDCP Packet Data Convergence Protocol
  • Iu user plane protocol defined in 3GPP TS25.415
  • 3GPP TS29 3GPP TS29.
  • the GTP-U protocol function shown in 060 is realized.
  • the Iu interface termination unit 15 extracts the RLC PDU from the downlink signal received from the upper CN via the Iu interface and transmits the RLC PDU to the RLC protocol function unit 16. In the uplink example, the Iu interface termination unit 15 transmits the uplink data from the RLC protocol function unit 16 to the CN via the Iu interface.
  • the RLC protocol function unit 16 realizes the RLC function defined in 3GPP TS25.322.
  • the RLC function is a function that performs various processes related to control of the radio link. With this RLC function, the RLC protocol function unit 16 executes RLC protocol processing on data transmitted and received by the UE.
  • Three types of modes are defined as RLC transmission methods. The first is Acknowledged Mode (hereinafter abbreviated as RLC-AM). The second is Unknowledged Mode (RLC-UM). The third is Transparent Mode (RLC-TM).
  • RLC-AM In RLC-AM mode, until 3GPP Release 6, the RLC-PDU (Protocol Data Unit) size was fixed length, and user data was divided by the RLC layer.
  • RLC-PDU Protocol Data Unit
  • Node-B 12 uses the MAC-ehs protocol instead of the MAC-hs protocol.
  • RNC11's RLC protocol does not divide data, but Node-B12's MAC-ehs protocol performs segmentation of upper data, so that in addition to fixed-length RLC-AM, flexible variable-length RLC-AM data is now possible.
  • variable length data up to 1503 octets is transmitted from the RNC 11 to the Node-B 12 as the maximum RLC PDU size.
  • the MAC-d protocol function unit 17 implements the MAC-d protocol, which is one of the MAC functions defined in 3GPP TS25.321.
  • the MAC-d protocol is a part of the MAC layer protocol, and the entire MAC layer protocol is composed of the MAC-d protocol and the MAC-hs protocol or the MAC-ehs protocol.
  • the MAC-d protocol can multiplex a plurality of logical channels from a plurality of RLC protocol function units 16. However, when MAC-ehs is used in Node-B 12, no logical channel is multiplexed.
  • the frame protocol function unit 18 implements the HS-DSCH frame protocol function defined in 3GPP TS25.435.
  • the HS-DSCH frame protocol is a protocol for generating and disassembling HS-DSCH frames used for HSDPA.
  • the frame protocol function unit 18 of the RNC 11 generates a lower data frame.
  • HS-DSCH DATA FRAME TYPE2 is used as the frame type. Therefore, the frame protocol function unit 18 generates a data frame of HS-DSCH DATA FRAME TYPE2.
  • the frame protocol function unit 18 performs flow control processing with the frame protocol function unit 23 of the Node-B 12.
  • the frame protocol function unit 23 of the Node-B 12 transmits HS-DSCH CAPACITY ALLOCATION TYPE 2 to the frame protocol function unit 18 of the RNC 11 when detecting interference in the radio channel, insufficient transmission power, or congestion on the transmission path of the Iub interface. By doing so, the RNC 11 is instructed to suppress transmission of the downlink data frame.
  • the frame protocol function unit 23 of the Node-B 12 increases the transmission of downlink data frames by transmitting the HS-DSCH CAPACITY ALLOCATION TYPE 2 to the frame protocol function unit 18 of the RNC 11. To RNC11.
  • the instruction to suppress and increase the downlink data frame is performed by instructing the MAC-d / c PDU Length, credit, or transmission interval.
  • the frame protocol function unit 18 of the RNC 11 performs HS-DSCH DATA according to the MAC-d / c PDU Length, credit, or transmission interval notified by the HS-DSCH CAPACITY ALLOCATION TYPE 2 received from the frame protocol function unit 23 of the Node-B 12. Send FRAME TYPE2 data.
  • the transmission line termination unit 19 transmits / receives data to / from the transmission line termination unit 20 of the Node-B 12 in a format suitable for the transport bearer (Transport Bearer) on the transmission line (Iub interface) with the Node-B 12.
  • Transport Bearer for example, ATM (Asynchronous Transfer Mode) or IP (Internet Protocol) is used.
  • the Node-B 12 includes a transmission line termination unit 20, a radio transmission / reception unit 25, an NBAP protocol function unit 21 and a call control unit 22 that form a control plane, and a frame protocol function unit that forms a user plane. 23 and a MAC-ehs protocol function unit 24.
  • the transmission line termination unit 20 is opposed to the transmission line termination unit 19 of the RNC 11 via a transmission line (Iub interface) between the RNC 11 and between the transmission line termination unit 19 of the RNC 11 in a format suitable for the transport bearer. Send and receive data with.
  • a transmission line Iub interface
  • the NBAP protocol function unit 21 performs message editing and analysis of the NBAP protocol transmitted and received with the RNC 11 under the control of the call control unit 22.
  • the call control unit 22 performs various processes related to call control.
  • the call control unit 22 transmits / receives a call control message to / from the RNC 11 or the UE.
  • the frame protocol function unit 23 is opposed to the frame protocol function unit 18 of the RNC 11 and implements an HS-DSCH frame protocol function. Specifically, the frame protocol function unit 23 receives the HS-DSCH Frame Protocol HS-DSCH DATA FRAME TYPE 2 data frame from the frame protocol function unit 18 of the RNC 11, extracts the MAC-d PDU in the frame, and extracts the MAC-d PDU. -Send to ehs protocol function unit 24.
  • the frame protocol function unit 23 performs flow control processing with the frame protocol function unit 18 of the RNC 11 as described above.
  • the MAC-ehs protocol function unit 24 divides the data from the RNC 11 (Segmentation), and transmits it to the UE via the radio transmission / reception unit 25. By dividing the data by the MAC-ehs protocol function unit 24 of the Node-B 12, it is possible to avoid inefficient padding at the RLC level of the RNC 11.
  • the radio transmission / reception unit 25 is connected to the UE via a radio line, and transmits / receives a call control message from the call control unit 22 and user data from the MAC-ehs protocol function unit 24.
  • FIG. 8 is a sequence diagram showing the operation of the mobile communication system according to the second embodiment.
  • the RNC 11 when a radio link is set, changed, or added, the RNC 11 notifies the Node-B 12 whether the RLC PDU size is a fixed length or a variable length.
  • FIG. 8 illustrates a sequence when a radio link is set up. Further, here, the operation of the system is shown until the RNC 11 notifies the Node-B 12 whether the RLC PDU size is a fixed length or a variable length, and the Node-B 12 performs flow control according to the notification.
  • the call control unit 13 of the RNC 11 first determines whether the RLC PDU size is fixed or variable (step 101).
  • the call control unit 13 sets an RLC size identifier indicating that the RLC PDU size is “fixed length” to the RLC protocol function unit 16 (step 102). Next, the call control unit 13 sets the RLC PDU size as the MAC-d PDU size (step 103). Further, the call control unit 13 sets the RLC size identifier to “fixed length” (step 104).
  • the call control unit 13 sets an RLC size identifier indicating that the RLC PDU size is “variable length” to the RLC protocol function unit 16 ( Step 105).
  • the call control unit 13 sets the maximum value of the RLC PDU size as the MAC-d PDU size (step 106). Further, the call control unit 13 sets the RLC size identifier to “variable length” (step 107).
  • the call control protocol processing unit 14 edits the NBAP RL SETUP REQUEST message in which, for example, MIMO and 64QAM are used, MAC-d PDU size, and RLC size identifier are set (Step 108), and transmits it to the Node-B 12 (Step 109).
  • RLC size identifier it is possible to notify the Node-B 12 from the RNC 11 whether the RLC PDU size is a fixed length or a variable length.
  • FIG. 9 is a diagram for explaining an outline of the NBAP protocol message.
  • FIG. 9 shows that an RLC size identifier (RLC Size Indicator), which is a new parameter, is added to the information element table of 3GPP TS25.433 9.2.1.31IA. Whether the RLC size is a fixed length or a variable length is set in this Indicator.
  • RLC Size Indicator an RLC size identifier
  • the call control unit 22 of the Node-B 12 that has received the NBAP protocol message acquires the MAC-d PDU size from the message (step 110).
  • the call control unit 22 further acquires the RLC size identifier and applies the value of the identifier to the flow control in the frame protocol function unit 23 (step 111). Further, the call control unit 22 further sets, for example, information indicating that the MAC-ehs protocol is used in the MAC-ehs protocol function unit 24 (step 112).
  • the frame protocol function unit 23 that performs flow control activates flow control when, for example, congestion of a wireless line is detected (step 113).
  • the frame protocol function unit 23 first checks the RLC size identifier (step 114).
  • the frame protocol function unit 23 controls other parameters while fixing the MAC-d PDU Length IE (step 115). For example, the congestion of the wireless line is dealt with by regulating the credit, transmission interval, or repetition period without changing the MAC-d PDU Length IE.
  • the frame protocol function unit 23 controls various parameters including the MAC-d PDU Length IE (step 116).
  • the flow control instruction by the frame protocol function unit 23 is notified to the RNC 11 by the HS-DSCH CAPACITY ALLOCATION TYPE 2 message (step 117).
  • the frame protocol function unit 18 of the RNC 11 controls the transmission of downlink data in accordance with the instruction from the frame protocol function unit 23 of the Node-B 12 (step 118).
  • the RLC size identifier is set in the NBAP RL SETUP REQUEST message.
  • the RCL PDU size identifier may be set in the NBAP RL ADDITION REQUEST message.
  • the radio link when the radio link is changed, it may be set in an NBAP RL RECONFIGURATION PREPARE message or an RL RECONFIGURATION REQUEST message.
  • the recognition of the RNC 11 and the Node-B 12 can be matched, and the HSDPA communication using the MAC-ehs protocol can be executed satisfactorily.
  • existing processing can be used for the RLC protocol function unit 16.
  • the MAC-ehs protocol can be used even when the RLC-PDU size is a fixed length, so that compatibility with systems prior to 3GPP Release 7 is maintained. For example, even if the UE moves from the Cover area of Node-B before 3GPP Release 7 to the Cover area of Node-B 12 after 3GPP Release 7, and the Serving Cell Change is performed, the RLC PDU size remains the fixed length. I can leave. Since it is not necessary to reset the RLC process, it is possible to reduce data loss in the upper user (for example, UE).
  • RLC PDU size identification information (RLC PDU size identifier) is used by the Node-B 12 for a priority queue (Priority Queue).
  • the Node-B 12 performs flow control for each priority queue using this identification information. Details of this example are described below.
  • the Node-B 12 When the Node-B 12 receives the downlink user data from the RNC 11, the Node-B 12 evaluates the common channel priority indicator (CmCH-PI) of the MAC-d PDU data, and the MAC-d is sent to the Priority Queue associated with each MAC-d PDU data. Distributes PDU data.
  • this CmCH-PI is associated not only with the priority queue of Node-B 12 but also with identification information of the RLC PDU size. Therefore, the RLC PDU size identification information affects the selection of the MAC-d PDU length (Maximum MAC-d / c PDU Length) in the flow control performed for each Priority Queue.
  • the Node-B 12 can be selected for each Priority Queue, in other words, for each associated priority (CmCH-PI).
  • Flow control can be implemented.
  • CmCH-PI corresponds to the Scheduling Priority Indicator notified by the NBAP in FIG.
  • CmCH-PI is set and updated by the RNC 11.
  • the Priority Queue is a storage area (buffer) that temporarily stores downlink user data from the RNC 11.
  • QoS requirements are considered. Examples of QoS include traffic class and peak rate.
  • FIG. 10 shows a modification example of 3GPP TS25.433 regarding the identification information of the RLC PDU size, that is, the RLC PDU size format in the above description.
  • the case where the identification information is normally notified from the RNC 11 to the Node-B 12 by a call control protocol message is shown as a normal operation.
  • abnormal operation it is preferable to consider abnormal operation. In the following, an example of operation when there is an abnormality in the notification from the RNC 11 to the Node-B 12 as an abnormal operation will be described.
  • the message indicates that the MAC- If it includes either an information element indicating that the PDU size of d is a fixed length or an information element indicating the PDU size of the maximum MAC-d, the Node-B 12 cannot correctly interpret the message. . Therefore, the Node-B 12 transmits a message rejecting the setting, change, or addition of the communication link to the RNC 11. As a result, the request from the RNC 11 is rejected and the procedure is aborted.
  • the Nede-B 12 Upon receiving the following messages 1 to 3, the Nede-B 12 detects “Abnormal Condition”, that is, an abnormal setting, rejects the request from the RNC 11, and stops the procedure.
  • Abnormal Condition that is, an abnormal setting
  • the RADIO LINK SETUP REQUEST message received from the RNC includes an information element DL RLC PDU Size Format of a predetermined priority Queue in which the RLC PDU size is set to have a variable length, and an information element HS -If the DSCH MAC-d PDU Size Format has a value where the MAC-d PDU size is a fixed length, the Node-B sends a RADIO LINK SETUP FAILURE message rejecting the request procedure from the RNC to the RNC.
  • the RADIO LINK SETUP REQUEST message received from the RNC does not include the information element Maximum MAC-d PDU Size Extended of the predetermined Priority Queue, and the information element DL RLC PDU Size Format is an RLC PDU size with a variable length. If so, the Node-B sends a RADIO LINK SETUP FAILURE message rejecting the request procedure from the RNC.
  • the RADIO LINK SETUP REQUEST message received from the RNC includes the information element HS-DSCH MAC-d PDU Size Format set so that the MAC-d PDU size is variable length, and includes the information element DL RLC PDU Size Format. If not, Node-B sends a RADIO LINK SETUP FAILURE message rejecting the request procedure from the RNC.
  • the RADIO LINK ADDITION REQUEST message received from the RNC does not include the information element Maximum MAC-d PDU Size Extended of the predetermined Priority Queue, and the information element DL RLC PDU Size Format is the RLC PDU length. If so, the Node-B sends a RADIO LINK ADDITION FAILURE message rejecting the request procedure from the RNC.
  • the RADIO LINK ADDITION REQUEST message received from the RNC includes the information element HS-DSCH MAC-d PDU Size Format set so that the MAC-d PDU size is variable length, and the information element DL RLC PDU Size Format is included. If not, the base station sends a RADIO LINK ADDITION FAILURE message that rejects the request procedure from the RNC.
  • RL RECONFIGURATION REQUEST message [1] In reconfiguration of synchronous radio link (1) In new configuration, RLC PDU size is set to be variable length and Maximum MAC-d PDU Size Extended is used If there is a priority queue that has not been set, the Node-B sends a RADIO LINK RECONFIGURATION FAILURE message rejecting the request procedure from the RNC to the RNC. (2) In the new configuration, there is a priority queue in which the corresponding Node B Communication Context is set so that the MAC-d PDU size is fixed length and the RLC PDU size is variable length If so, the Node-B sends a RADIO LINK RECONFIGURATION FAILURE message rejecting the request procedure from the RNC to the RNC.
  • the corresponding Node B Communication Context is set so that the MAC-d PDU size is variable length, and does not include the information element DL RLC PDU Size format of the predetermined priority queue
  • Node-B sends a RADIO LINK RECONFIGURATION FAILURE message to the RNC rejecting the request procedure from the RNC.
  • Asynchronous radio link reconfiguration (1) In new configuration, RLC PDU size is set to be variable length and Maximum MAC-d PDU Size Extended is not set to be used , Priority queue exists, Node-B sends a RADIO LINK RECONFIGURATION FAILURE message rejecting the request procedure from the RNC to the RNC.
  • the corresponding Node B Communication Context is set so that the MAC-d PDU size is fixed length and the RLC PDU size is variable length If so, the Node-B sends a RADIO LINK RECONFIGURATION FAILURE message rejecting the request procedure from the RNC to the RNC.
  • the corresponding Node B Communication Context is set so that the MAC-d PDU size is variable length, and does not include the information element DL RLC PDU Size format of the predetermined priority queue Node-B sends a RADIO LINK RECONFIGURATION FAILURE message to the RNC rejecting the request procedure from the RNC.
  • Node B Communication Context is a term defined in 3GPP, and is data information (context) managed for each mobile device (UE).
  • the basic configuration of the mobile communication system according to the third embodiment is the same as the configuration of the system according to the second embodiment shown in FIG.
  • FIG. 11 is a diagram illustrating an example of HS-DSCH DATA FRAME TYPE 2 according to the third embodiment.
  • an RLC size identifier (RLC Size Indicator) is defined in the second bit from the most significant bit of the fourth octet.
  • FIG. 12 is a sequence diagram showing the operation of the mobile communication system according to the third embodiment.
  • the call control unit 13 of the RNC 11 first determines whether the RLC PDU size is fixed or variable (step 201). If the RLC PDU size is fixed, the call control unit 13 sets an RLC size identifier indicating that the RLC PDU size is “fixed length” to the frame protocol function unit 18 (step 202). On the other hand, if the RLC PDU size is variable in the determination in step 201, the call control unit 13 sets an RLC size identifier indicating that the RLC PDU size is “variable length” to the frame protocol function unit 18 ( Step 202).
  • the frame protocol function unit 18 of the RNC 11 transmits the data frame of HS-DSCH DATA FRAME TYPE 2
  • the RLC size identifier is inserted into the second bit from the most significant bit of the fourth octet of the frame (step 204).
  • the frame protocol function unit 23 of the Node-B 12 that has received the data frame of HS-DSCH DATA FRAME TYPE 2 acquires the RLC size identifier from the frame and applies the value of the identifier to the flow control (step 205).
  • the frame protocol function unit 23 that performs flow control activates flow control when, for example, congestion of a wireless line is detected (step 206).
  • the frame protocol function unit 23 first checks the RLC size identifier (step 207).
  • the frame protocol function unit 23 controls other parameters while fixing the MAC-d PDU Length IE (step 208). For example, the congestion of the wireless line is dealt with by regulating the credit, transmission interval, or repetition period without changing the MAC-d PDU Length IE.
  • the frame protocol function unit 23 controls various parameters including the MAC-d PDU Length IE (step 209).
  • the flow control instruction by the frame protocol function unit 23 is notified to the RNC 11 by the HS-DSCH CAPACITY ALLOCATION TYPE2 message (step 210).
  • the frame protocol function unit 18 of the RNC 11 controls transmission of downlink data in accordance with an instruction from the frame protocol function unit 23 of the Node-B 12 (step 211).
  • the RNC 11 notifies the RLC PDU size identifier to the Node-B 12 using the HS-DSCH DATA FRAME TYPE 2 and the Node-B 12 receives the HS-DSCH DATA FRAME TYPE 2.
  • the RLC PDU size identifier is dynamically managed according to the notification by the frame. Therefore, in this embodiment, it is possible to dynamically control whether the RLC PDU size is a fixed length or a variable length.
  • the basic configuration of the mobile communication system according to the fourth embodiment is the same as the configuration of the system according to the second embodiment shown in FIG.
  • FIG. 13 is a diagram showing an example of the definition of HS-DSCH MAC-d PDU Size Format according to the fourth embodiment.
  • “Fixed MAC-d PDU Size for MAC-ehs” can be set as the value of HS-DSCH MAC-d PDU Size Format.
  • Indexed MAC-d PDU Size is prepared for MAC-hs
  • Flexible MAC-d PDU Size is prepared for MAC-ehs. Yes.
  • “Fixed MAC-d PDU Size for MAC-ehs” is newly introduced for MAC-ehs having a fixed RLC PDU size.
  • HS-DSCH MAC-d PDU Size Format of an HS-DSCH transport channel is set to “Flexible MAC-d PDU Size”, all the MAC-s of that HS-DSCH transport channel are set.
  • d Flow RLC PDU size is variable length.
  • HS-DSCH MAC-d PDU Size Format of a HS-DSCH transport channel is set to “Fixed MAC-d PDU Size”, all MAC-d flow RLC PDUs of that HS-DSCH transport channel are set. Size is fixed length.
  • HS-DSCH MAC-d flow information used in the second embodiment is an information element indicating the nature of each logical channel mapped to Priority Queue. Since the RLC PDU size identifier is notified by HS-DSCH MAC-d flow information, it is possible to indicate whether the RLC PDU size is fixed length or variable length for each logical channel. In other words, a logical channel having a fixed RLC PDU size and a logical channel having a variable RLC PDU size could be mixed.
  • HS-DSCH MAC-d PDU Size Format used in the fourth embodiment is an information element that specifies the nature of the HS-DSCH transport channel. Since the HS-DSCH MAC-d PDU Size Format informs whether the RLC PDU size is a fixed length or variable length, a logical channel with an RLC PDU size of a fixed length and an RLC PDU are included in the HS-DSCH transport channel. Mixing with logical channels of variable length is not allowed.
  • the processing in the RNC 11 and Node-B 12 is simpler than in the second embodiment. It becomes.
  • the flow control in HSDPA communication which is downlink high-speed data communication is exemplified, but the present invention is not limited to this.
  • the fifth embodiment exemplifies a mobile communication system that implements HSUPA (High Speed Uplink Packet Access) communication, which is uplink high-speed data communication, and performs flow control thereof.
  • HSUPA High Speed Uplink Packet Access
  • 3GPP Release 8 introduces MAC-i / MAC-is protocol for HSUPA, and makes RLC PDU size variable length.
  • the MAC-e / MAC-es protocol is defined.
  • the MAC-i / MAC-is protocol and the MAC-e / MAC-es protocol are exclusive, and the UE has either the MAC-i / MAC-is protocol or the MAC-e / MAC-es protocol. Only one will exist. If the RLC PDU size is variable, it is necessary to use the MAC-i / MAC-is protocol.
  • RLC PDU size is fixed length or variable length
  • RLC PDU size in addition to whether RLC PDU size is fixed length or variable length, in case of variable length, RLC PDU size The minimum and maximum values can be notified.
  • the maximum MAC-d PDU size (Maximum MAC-d) for each logical channel mapped to MAC-d flow from RNC to Node-B.
  • PDU Size Extended IE can only be notified.
  • the MAC-d protocol does not multiplex logical channels, so the MAC-d PDU size is the same as the RLC PDU size.
  • the Node-B schedules transmission of uplink data from a UE, and notifies the UE of the power permitted to use the UE based on the scheduling result (grant ( The method of giving the transmission permission) is employed.
  • the power available to the UE is indicated by the grant.
  • the UE determines the amount of data that can be transmitted on the uplink based on the given grant.
  • Node-B uses MAC-i / MAC-is and can consider the maximum value of RLC PDU size in its flow control.
  • the current NBAP protocol cannot notify whether the RLC PDU size of the logical channel to be multiplexed is a fixed length or a variable length, and if the RLC PDU size is a variable length, the minimum RLC PDU size The value cannot be notified. For this reason, there is a case where a state mismatch regarding the RLC PDU size occurs between the Node-B, the RNC, and the UE, and the grant may not be appropriately granted from the Node-B to the UE.
  • the UE cannot transmit data in the uplink. Also, even if the RLC PDU size is variable length, if the grant given to the UE from Node-B is smaller than the value corresponding to the minimum value of the RLC PDU size, the UE still transmits data to the uplink. Can not do it.
  • the control signal preferably uses MAC-i / MAC-is while keeping the RLC PDU size as a fixed length, but the current NBAP cannot notify such a setting.
  • the RNC has a RLC-PDU size that is fixed or variable with respect to Node-B, and if the RLC PDU size is variable, RLC- The minimum value of the PDU size is also notified.
  • the Node-B that has received the notification from the RNC determines the grant to be given to the UE by determining whether the RLC PDU size is a fixed length or a variable length in HSUPA flow control. In addition, when the RLC PDU size is variable length, the Node-B determines the grant to be given to the UE in consideration of the minimum value of the RLC PDU size notified from the RNC when the RLC PDU size is variable length. To do.
  • the Node-B may grant a grant that can transmit data having an RLC PDU size larger than the minimum value of the RLC PDU size so that the UE to which the grant is granted cannot transmit data. Grant to the UE.
  • the mobile communication system according to the present embodiment is the same as the system according to the second embodiment shown in FIG. 7 in that the mobile communication system includes the RNC 11 and the Node-B 12.
  • the present embodiment focuses on uplink data communication, the MAC-d protocol function unit 17 and the MAC-ehs protocol function unit 24 are unnecessary, and instead, the MAC-i protocol and the MAC-is protocol are used.
  • a protocol function unit for realizing the above is required.
  • the call control unit 13 of the RNC 11 determines whether the RLC PDU size is fixed or variable.
  • the call control protocol processing unit 14 edits the NBAP protocol message in which the information about the RLC PDU size, such as the minimum value when the RLC PDU size is fixed length or variable length, and the variable length is set, and transmits it to the Node-B 12 To do.
  • the operation of the system of the present embodiment is the same as the operation of the system of the second embodiment.
  • the call control unit 22 that has received the NBAP protocol message acquires information on the RLC PDU size from the message, and the flow control unit applies the information to the flow control.
  • the operation of the system of the present embodiment is the same as the operation of the system of the second embodiment.
  • the flow control in this embodiment is control for uplink data transmitted from the UE
  • flow control by the Node-B 12 is instructed to the UE.
  • the flow control instruction is notified to the UE as grant of the above-described grant.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Databases & Information Systems (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Communication Control (AREA)
PCT/JP2009/058991 2008-08-01 2009-05-14 移動通信システム、制御装置、基地局装置、システム制御方法、および装置制御方法 Ceased WO2010013526A1 (ja)

Priority Applications (34)

Application Number Priority Date Filing Date Title
BR122015007062A BR122015007062A2 (pt) 2008-08-01 2009-05-14 estação base, dispositivo de controle, terminal e método
BR122015021024A BR122015021024A2 (pt) 2008-08-01 2009-05-14 estação base, dispositivo de controle e meio de comunicação
BR122015021029A BR122015021029A2 (pt) 2008-08-01 2009-05-14 estação base, dispositivo de controle, terminal e método
BR122015007063A BR122015007063A2 (pt) 2008-08-01 2009-05-14 estação base, dispositivo de controle, terminal para um sistema de comunicação móvel e método
KR1020137003881A KR101450487B1 (ko) 2008-08-01 2009-05-14 이동 통신 시스템, 제어 디바이스, 기지국 디바이스, 시스템 제어 방법 및 디바이스 제어 방법
BR122015021023A BR122015021023A2 (pt) 2008-08-01 2009-05-14 estação base, dispositivo de controle, terminal e método
KR1020137003882A KR101450488B1 (ko) 2008-08-01 2009-05-14 이동 통신 시스템, 제어 디바이스, 기지국 디바이스, 시스템 제어 방법 및 디바이스 제어 방법
BR122015021028A BR122015021028A2 (pt) 2008-08-01 2009-05-14 estação base, dispositivo de controle, método de comunicação, método para uma estação base, método para um dispositivo de controle e terminal
BR122015021026A BR122015021026A2 (pt) 2008-08-01 2009-05-14 estação base, dispositivo de controle e meio de comunicação
RU2011107746/07A RU2486698C2 (ru) 2008-08-01 2009-05-14 Мобильная система передачи данных, устройство управления, устройство базовой станции, способ управления системой и способ управления устройством
BR122015021031A BR122015021031A2 (pt) 2008-08-01 2009-05-14 estação base, dispositivo de controle, terminal, método para uma estação base, método para um dispositivo de controle e método para um terminal
KR1020137017049A KR101497853B1 (ko) 2008-08-01 2009-05-14 이동 통신 시스템, 제어 디바이스, 기지국 디바이스, 시스템 제어 방법 및 디바이스 제어 방법
US13/054,896 US9113392B2 (en) 2008-08-01 2009-05-14 Mobile communication system, control device, base station device, system control method and device control method
EP09802771.7A EP2315471B1 (en) 2008-08-01 2009-05-14 Mobile communication system, control device, base station device and communication control method
BRPI0911022A BRPI0911022A2 (pt) 2008-08-01 2009-05-14 sistema de comunicação móvel, dispositivo de controle, dispositivo de estação base, método de controle de comunicação e método de controle de dispositivo
BR122013013478A BR122013013478A2 (pt) 2008-08-01 2009-05-14 estação base, dispositivo de controle, terminal em um sistema de comunicação móvel e sistema de comunicação móvel
KR1020147033302A KR101497891B1 (ko) 2008-08-01 2009-05-14 이동 통신 시스템, 제어 디바이스, 기지국 디바이스, 시스템 제어 방법 및 디바이스 제어 방법
AU2009277764A AU2009277764B2 (en) 2008-08-01 2009-05-14 Mobile communication system, control device, base station device, system control method and device control method
BR122014019674A BR122014019674A2 (pt) 2008-08-01 2009-05-14 dispositivo de estação base, dispositivo de controle, terminal, sistema de comunicação móvel e método
CA2732689A CA2732689C (en) 2008-08-01 2009-05-14 Mobile communication system, control device, base station device, system control method and device control method
KR1020137003883A KR101450489B1 (ko) 2008-08-01 2009-05-14 이동 통신 시스템, 제어 디바이스, 기지국 디바이스, 시스템 제어 방법 및 디바이스 제어 방법
KR1020127026821A KR101377836B1 (ko) 2008-08-01 2009-05-14 이동 통신 시스템, 제어 디바이스, 기지국 디바이스, 시스템 제어 방법 및 디바이스 제어 방법
BR122015007068-6A BR122015007068A2 (pt) 2008-08-01 2009-05-14 Estação base, dispositivo de controle, terminal em um sistema de comunicação móvel e método
KR1020117004845A KR101333855B1 (ko) 2008-08-01 2009-05-14 이동 통신 시스템, 제어 디바이스, 기지국 디바이스, 시스템 제어 방법 및 디바이스 제어 방법
CN200980130582.2A CN102113369B (zh) 2008-08-01 2009-05-14 移动通信系统、控制设备、基站设备、系统控制方法和设备控制方法
ES09802771.7T ES2632397T3 (es) 2008-08-01 2009-05-14 Sistema de comunicación móvil, dispositivo de control, dispositivo de estación de base y método de control de comunicación
JP2010522648A JP5223922B2 (ja) 2008-08-01 2009-05-14 移動通信システム、制御装置、基地局装置、システム制御方法、および装置制御方法
US14/163,580 US9072029B2 (en) 2008-08-01 2014-01-24 Mobile communication system, control device, base station device, system control method and device control method
US14/474,358 US9307480B2 (en) 2008-08-01 2014-09-02 Mobile communication system, control device, base station device, system control method and device control method
US14/474,352 US9247485B2 (en) 2008-08-01 2014-09-02 Mobile communication system, control device, base station device, system control method and device control method
US14/474,380 US9247486B2 (en) 2008-08-01 2014-09-02 Mobile communication system, control device, base station device, system control method and device control method
US15/053,059 US9565121B2 (en) 2008-08-01 2016-02-25 Mobile communication system, control device, base station device, system control method and device control method
US15/380,455 US9787541B2 (en) 2008-08-01 2016-12-15 Mobile communication system, control device, base station device, system control method and device control method
US15/694,325 US10404536B2 (en) 2008-08-01 2017-09-01 Mobile communication system, control device, base station device, system control method and device control method

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2008-200277 2008-08-01
JP2008200277 2008-08-01

Related Child Applications (5)

Application Number Title Priority Date Filing Date
US13/054,896 A-371-Of-International US9113392B2 (en) 2008-08-01 2009-05-14 Mobile communication system, control device, base station device, system control method and device control method
US14/163,580 Division US9072029B2 (en) 2008-08-01 2014-01-24 Mobile communication system, control device, base station device, system control method and device control method
US14/474,352 Continuation US9247485B2 (en) 2008-08-01 2014-09-02 Mobile communication system, control device, base station device, system control method and device control method
US14/474,358 Continuation US9307480B2 (en) 2008-08-01 2014-09-02 Mobile communication system, control device, base station device, system control method and device control method
US14/474,380 Continuation US9247486B2 (en) 2008-08-01 2014-09-02 Mobile communication system, control device, base station device, system control method and device control method

Publications (1)

Publication Number Publication Date
WO2010013526A1 true WO2010013526A1 (ja) 2010-02-04

Family

ID=41610236

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2009/058991 Ceased WO2010013526A1 (ja) 2008-08-01 2009-05-14 移動通信システム、制御装置、基地局装置、システム制御方法、および装置制御方法

Country Status (11)

Country Link
US (8) US9113392B2 (enExample)
EP (5) EP2603035B1 (enExample)
JP (11) JP5223922B2 (enExample)
KR (7) KR101333855B1 (enExample)
CN (5) CN102113369B (enExample)
AU (1) AU2009277764B2 (enExample)
BR (12) BR122015007062A2 (enExample)
CA (1) CA2732689C (enExample)
ES (5) ES2632397T3 (enExample)
RU (6) RU2486698C2 (enExample)
WO (1) WO2010013526A1 (enExample)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102469631A (zh) * 2010-11-05 2012-05-23 中兴通讯股份有限公司 Ue能力的发送方法、传递方法和系统及无线网络控制器
JP2013009376A (ja) * 2008-08-01 2013-01-10 Nec Corp 移動通信システム、制御装置、基地局装置、ユーザ端末、システム制御方法、および装置制御方法
JP2015508970A (ja) * 2012-02-29 2015-03-23 ▲ホア▼▲ウェイ▼技術有限公司 スタンドアロンな高速専用物理制御チャネルを確立するための方法および装置

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2393373A1 (en) 2002-07-15 2004-01-15 Anthony Gerkis Apparatus, system and method for the transmission of data with different qos attributes.
TWI423710B (zh) * 2010-10-15 2014-01-11 Acer Inc 行動通訊裝置、系統、以及連線建立方法
KR20120120775A (ko) * 2011-04-25 2012-11-02 주식회사 팬택 무선통신 시스템에서 제어 정보의 다중 전송을 동적으로 제어하는 방법 및 장치
IN2014KN01157A (enExample) 2011-11-09 2015-10-16 Ericsson Telefon Ab L M
CN103162024A (zh) * 2013-03-25 2013-06-19 中联重科股份有限公司 输送管
KR101438630B1 (ko) 2013-04-15 2014-09-05 현대자동차 주식회사 선택적 촉매 환원(scr) 시스템의 우레아 분사 노즐의 막힘 방지 방법
CN105471763B (zh) * 2014-09-04 2020-09-15 中兴通讯股份有限公司 控制报文传输方法及装置
WO2017028017A1 (zh) * 2015-08-14 2017-02-23 华为技术有限公司 通信的方法、网络设备和用户设备
JP6955509B2 (ja) 2015-12-21 2021-10-27 コーニング インコーポレイテッド アルカリ含有量が低いホウケイ酸ガラス
WO2018206855A1 (en) 2017-05-12 2018-11-15 Nokia Technologies Oy Protocol data unit session splitting function and signalling
EP3911001A4 (en) * 2019-01-09 2022-03-16 Panasonic Intellectual Property Corporation of America BASE STATION, TERMINAL, TRANSMISSION METHOD AND RECEIVING METHOD
CN115361704B (zh) * 2022-09-20 2024-11-12 北京科技大学 基于基站mac子层直接传输的c2d通信系统及i/o数据通信方法

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2001103093A (ja) * 1999-09-30 2001-04-13 Sharp Corp データ伝送方法及びデータ伝送装置
JP2008200277A (ja) 2007-02-20 2008-09-04 Ykk Corp スライドファスナー用スライダー

Family Cites Families (44)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
NZ232223A (en) 1989-01-27 1993-03-26 British Telecomm Alternate burst communication for cordless phones re-established after channel failure
FI104143B (fi) 1997-07-31 1999-11-15 Nokia Networks Oy Menetelmä tietoliikenneresurssien kontrolloimiseksi
GB2355623B (en) * 1999-10-19 2003-07-16 Ericsson Telefon Ab L M Packet transmission in a UMTS network
KR100519612B1 (ko) * 2000-04-07 2005-10-07 노키아 코포레이션 투과 ｒｌｃ를 통한 고정 크기 ｐｄｕ들의 전송
RU2242092C2 (ru) * 2001-07-06 2004-12-10 Самсунг Электроникс Ко., Лтд. Способ установки в исходное состояние объекта уровня управления доступом к среде в системе связи с широкополосным множественным доступом с кодовым разделением каналов, использующей высокоскоростной пакетный доступ к нисходящей линии связи
ES2518221T3 (es) * 2001-08-21 2014-11-04 Core Wireless Licensing S.à.r.l. Transmisión de datos de una red de comunicaciones
KR20030022929A (ko) * 2001-09-11 2003-03-19 한빛전자통신 주식회사 3지피피 시스템의 알엔씨에서 호 서비스 장치 및 방법
KR100747464B1 (ko) 2002-01-05 2007-08-09 엘지전자 주식회사 고속하향링크패킷접속（ｈｓｄｐａ）시스템을 위한타이머를 이용한 교착상황 회피방법
GB2386513B (en) 2002-02-07 2004-08-25 Samsung Electronics Co Ltd Apparatus and method for transmitting/receiving serving hs-scch set information in an hsdpa communication system
TWI241813B (en) * 2002-05-10 2005-10-11 Interdigital Tech Corp Cognitive flow control based on channel quality conditions
KR100876765B1 (ko) * 2002-05-10 2009-01-07 삼성전자주식회사 이동 통신 시스템에서 데이터 재전송 장치 및 방법
FR2850828B1 (fr) * 2003-01-31 2005-04-29 Evolium Sas Procede pour la gestion de la qualite de service dans un systeme de radiocommunications mobiles
CN100444568C (zh) * 2003-06-11 2008-12-17 株式会社Ntt都科摩 数据包通信方法、控制装置及移动站
KR100516554B1 (ko) * 2003-08-25 2005-09-22 삼성전자주식회사 고속 순방향 패킷 접속 통신 시스템에서 프로토콜 데이터유닛 처리 방법
US7136396B2 (en) 2003-11-24 2006-11-14 Interdigital Technology Corporation Method and apparatus for compiling a protocol data unit
KR100520146B1 (ko) * 2003-12-22 2005-10-10 삼성전자주식회사 고속 순방향 패킷 접속 통신 시스템에서 데이터 처리장치및 방법
KR100539930B1 (ko) * 2003-12-22 2005-12-28 삼성전자주식회사 부호분할다중접속 이동통신시스템에서 데이터 전송 최적화를 위한 전송 포맷 선택 방법
KR100617696B1 (ko) 2004-03-12 2006-08-28 삼성전자주식회사 무선 통신 시스템에서 연속된 데이터 유닛 수신 방법 및장치와 송신을 위한 데이터 유닛의 생성 방법 및 장치와그 데이터버스트 구조
CN1710829A (zh) * 2004-06-18 2005-12-21 北京三星通信技术研究有限公司 在wcdma系统的增强上行专用信道中支持低数据速率的方法
KR100678941B1 (ko) 2004-09-03 2007-02-07 삼성전자주식회사 할당된 시간 동안 양방향으로 데이터를 송수신하는 방법및 그 방법을 이용하는 무선 디바이스
EP1643694A3 (en) 2004-09-30 2008-10-08 Samsung Electronics Co., Ltd. Method and apparatus for transmitting uplink nonscheduled data in a mobile communication system
ES2309876T3 (es) 2004-12-15 2008-12-16 Panasonic Corporation Apoyo del trafico de tasa de bits garantizada para transmisiones del enlace ascendente.
KR100918435B1 (ko) * 2005-01-31 2009-09-24 삼성전자주식회사 무선 통신 시스템에서 데이터 트래픽 제어 시스템 및 방법
KR100762647B1 (ko) * 2005-03-31 2007-10-01 삼성전자주식회사 기지국 장치 및 이를 이용한 무선 자원 관리 방법
US8085657B2 (en) 2005-04-01 2011-12-27 Sony Corporation Flow control in a cellular communication system
EP1917751A4 (en) * 2005-08-26 2011-07-06 Ericsson Telefon Ab L M RIVER CONTROL AT UMTS
CN100442773C (zh) * 2005-11-07 2008-12-10 华为技术有限公司 通过高速下行分组接入技术hsdpa传输ip报文的方法
KR101216751B1 (ko) 2006-02-07 2012-12-28 엘지전자 주식회사 이동 통신 시스템에서 식별자를 이용한 충돌 회피 방법
CN100426799C (zh) * 2006-02-28 2008-10-15 华为技术有限公司 一种高速下行包接入硬切换方法和系统
CN101039170B (zh) * 2006-03-15 2011-08-03 华为技术有限公司 支持数据包重传分割级联的方法
JP2007300508A (ja) 2006-05-01 2007-11-15 Ntt Docomo Inc 基地局、移動局および通信方法
JP4781939B2 (ja) 2006-08-21 2011-09-28 富士通株式会社 無線通信装置
JP4923849B2 (ja) * 2006-08-21 2012-04-25 富士通株式会社 無線受信装置
JP5140975B2 (ja) * 2006-09-14 2013-02-13 富士通株式会社 移動通信システム及びその通信方法
KR101420895B1 (ko) * 2007-02-02 2014-07-28 인터디지탈 테크날러지 코포레이션 Ｕｔｒａ ｒ6 셀과 ｒ7 셀 간의 핸드오버를 제어하기 위한 방법 및 장치
US8503423B2 (en) * 2007-02-02 2013-08-06 Interdigital Technology Corporation Method and apparatus for versatile MAC multiplexing in evolved HSPA
US8498284B2 (en) * 2007-02-02 2013-07-30 Interdigital Technology Corporation Method and apparatus for enhancing RLC for flexible RLC PDU size
DK2421207T3 (en) * 2007-02-06 2015-01-19 Ericsson Telefon Ab L M Radio Link Control Packet Data Unit of flexible length
DK2140632T3 (en) * 2007-03-16 2018-12-17 Interdigital Tech Corp METHOD OF WIRELESS COMMUNICATION AND DEVICE FOR SUPPORTING CONFIGURATION OF RADIO CONNECTION CONTROL PARAMETERS
CN101641897A (zh) * 2007-03-16 2010-02-03 交互数字技术公司 演进型hspa系统内部的应答模式无线电链路控制架构及方法
CN101355547B (zh) * 2007-07-23 2011-06-15 鼎桥通信技术有限公司 一种媒体接入控制专用信道数据包大小的配置方法及装置
CN101355439B (zh) * 2007-07-27 2010-12-01 鼎桥通信技术有限公司 用户设备能力的控制方法、系统及无线网络控制器
KR101586550B1 (ko) * 2007-09-28 2016-01-20 라쿠텐 인코포레이티드 업링크 프로토콜 변경을 지원하기 위한 방법 및 장치
ES2632397T3 (es) 2008-08-01 2017-09-12 Nec Corporation Sistema de comunicación móvil, dispositivo de control, dispositivo de estación de base y método de control de comunicación

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2001103093A (ja) * 1999-09-30 2001-04-13 Sharp Corp データ伝送方法及びデータ伝送装置
JP2008200277A (ja) 2007-02-20 2008-09-04 Ykk Corp スライドファスナー用スライダー

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"Common test environments for User Equipment(UE); Conformanc tetesting(Release 8)", 3GPP TS 34.108 V8.3.0, June 2008 (2008-06-01), XP014042179 *
"UTRAN Iub interface Node B Application Part (NBAP) signalling(Release 8)", 3GPP TS 25.433 V8.1.0, June 2008 (2008-06-01), XP014042542 *
"UTRAN Iur interface user plane protocols for Common Transport Channel data streams (Release 7)", 3GPP TS 25.425 V7.7.0, March 2008 (2008-03-01), XP014041747 *
See also references of EP2315471A4

Cited By (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9072029B2 (en) 2008-08-01 2015-06-30 Nec Corporation Mobile communication system, control device, base station device, system control method and device control method
US9307480B2 (en) 2008-08-01 2016-04-05 Nec Corporation Mobile communication system, control device, base station device, system control method and device control method
JP2013211924A (ja) * 2008-08-01 2013-10-10 Nec Corp 移動通信システム、制御装置、基地局装置、ユーザ端末、システム制御方法、および装置制御方法
JP2014140206A (ja) * 2008-08-01 2014-07-31 Nec Corp 基地局装置、制御装置、端末、移動通信システム、およびその方法
JP2015043613A (ja) * 2008-08-01 2015-03-05 日本電気株式会社 基地局装置、制御装置、端末、およびその方法
US10404536B2 (en) 2008-08-01 2019-09-03 Nec Corporation Mobile communication system, control device, base station device, system control method and device control method
JP2013009376A (ja) * 2008-08-01 2013-01-10 Nec Corp 移動通信システム、制御装置、基地局装置、ユーザ端末、システム制御方法、および装置制御方法
US9247485B2 (en) 2008-08-01 2016-01-26 Nec Corporation Mobile communication system, control device, base station device, system control method and device control method
US9787541B2 (en) 2008-08-01 2017-10-10 Nec Corporation Mobile communication system, control device, base station device, system control method and device control method
US9247486B2 (en) 2008-08-01 2016-01-26 Nec Corporation Mobile communication system, control device, base station device, system control method and device control method
US9113392B2 (en) 2008-08-01 2015-08-18 Nec Corporation Mobile communication system, control device, base station device, system control method and device control method
US9565121B2 (en) 2008-08-01 2017-02-07 Nec Corporation Mobile communication system, control device, base station device, system control method and device control method
CN102469631A (zh) * 2010-11-05 2012-05-23 中兴通讯股份有限公司 Ue能力的发送方法、传递方法和系统及无线网络控制器
US9713135B2 (en) 2012-02-29 2017-07-18 Huawei Technologies Co., Ltd. Method and apparatus for establishing a standalone high speed dedicated physical control channel
JP2015508970A (ja) * 2012-02-29 2015-03-23 ▲ホア▼▲ウェイ▼技術有限公司 スタンドアロンな高速専用物理制御チャネルを確立するための方法および装置

Also Published As

Publication number Publication date
HK1182871A1 (en) 2013-12-06
BR122013013478A2 (pt) 2016-02-10
RU2635108C2 (ru) 2017-11-09
CN102113369B (zh) 2016-06-08
BR122015021029A2 (pt) 2019-08-27
US9247485B2 (en) 2016-01-26
EP2600650B1 (en) 2016-09-07
JP6624183B2 (ja) 2019-12-25
JP5700148B2 (ja) 2015-04-15
JP5403181B2 (ja) 2014-01-29
RU2011107746A (ru) 2012-09-10
US20170099186A1 (en) 2017-04-06
BR122015007062A2 (pt) 2016-02-10
US9113392B2 (en) 2015-08-18
KR20130036340A (ko) 2013-04-11
US9787541B2 (en) 2017-10-10
ES2493169T3 (es) 2014-09-11
JP2012239206A (ja) 2012-12-06
JP2013211924A (ja) 2013-10-10
KR20130036339A (ko) 2013-04-11
US20150036491A1 (en) 2015-02-05
RU2012135474A (ru) 2014-02-27
KR101450489B1 (ko) 2014-10-15
BR122015007068A2 (pt) 2019-08-20
RU2015154991A (ru) 2017-06-27
RU2015154992A (ru) 2017-06-23
EP2600651A1 (en) 2013-06-05
JP2014140206A (ja) 2014-07-31
US20150036490A1 (en) 2015-02-05
US10404536B2 (en) 2019-09-03
KR101450487B1 (ko) 2014-10-13
US20110122802A1 (en) 2011-05-26
ES2635430T3 (es) 2017-10-03
JP5354128B2 (ja) 2013-11-27
KR20110038161A (ko) 2011-04-13
EP2605578A1 (en) 2013-06-19
JP2013138494A (ja) 2013-07-11
JP5338999B2 (ja) 2013-11-13
CN104301940B (zh) 2018-04-24
EP2315471B1 (en) 2017-04-05
RU2611721C1 (ru) 2017-02-28
US20140369306A1 (en) 2014-12-18
ES2632397T3 (es) 2017-09-12
US9247486B2 (en) 2016-01-26
CA2732689C (en) 2014-10-28
JP2015043613A (ja) 2015-03-05
CN103476063B (zh) 2016-08-10
RU2013108898A (ru) 2014-09-10
JP5783316B2 (ja) 2015-09-24
JPWO2010013526A1 (ja) 2012-01-05
RU2635548C2 (ru) 2017-11-14
AU2009277764B2 (en) 2014-12-04
ES2606634T3 (es) 2017-03-24
JP2013009376A (ja) 2013-01-10
EP2315471A4 (en) 2012-10-24
JP5223922B2 (ja) 2013-06-26
US20180013622A1 (en) 2018-01-11
CN104301942B (zh) 2018-04-03
BRPI0911022A2 (pt) 2015-12-29
KR101497853B1 (ko) 2015-03-04
CA2732689A1 (en) 2010-02-04
JP6248991B2 (ja) 2017-12-20
ES2606179T3 (es) 2017-03-23
AU2009277764A1 (en) 2010-02-04
KR101377836B1 (ko) 2014-03-26
RU2486698C2 (ru) 2013-06-27
CN104301941B (zh) 2018-04-20
CN102113369A (zh) 2011-06-29
KR20130041213A (ko) 2013-04-24
CN103476063A (zh) 2013-12-25
EP2600651B1 (en) 2016-09-07
US20140140299A1 (en) 2014-05-22
CN104301941A (zh) 2015-01-21
JP2015233309A (ja) 2015-12-24
EP2605578B1 (en) 2017-05-03
KR101497891B1 (ko) 2015-03-03
RU2613334C1 (ru) 2017-03-16
JP2014060743A (ja) 2014-04-03
EP2600650A1 (en) 2013-06-05
KR20140146223A (ko) 2014-12-24
US9565121B2 (en) 2017-02-07
KR20120123728A (ko) 2012-11-09
JP2013211923A (ja) 2013-10-10
EP2315471A1 (en) 2011-04-27
BR122015021031A2 (pt) 2019-08-27
CN104301942A (zh) 2015-01-21
BR122015021028A2 (pt) 2019-08-27
KR101450488B1 (ko) 2014-10-13
US20160197838A1 (en) 2016-07-07
BR122014019674A2 (pt) 2016-02-10
BR122015021023A2 (pt) 2019-08-27
JP5263432B2 (ja) 2013-08-14
US9072029B2 (en) 2015-06-30
KR101333855B1 (ko) 2013-11-27
RU2529008C2 (ru) 2014-09-27
EP2603035A1 (en) 2013-06-12
EP2603035B1 (en) 2014-08-06
JP5403118B2 (ja) 2014-01-29
BR122015021024A2 (pt) 2019-08-27
CN104301940A (zh) 2015-01-21
US9307480B2 (en) 2016-04-05
JP5495199B2 (ja) 2014-05-21
BR122015007063A2 (pt) 2016-02-10
BR122015021026A2 (pt) 2019-08-27
KR20130093158A (ko) 2013-08-21
JP2018050326A (ja) 2018-03-29

Similar Documents

Publication Publication Date Title
JP6624183B2 (ja) 基地局装置、制御装置およびその方法
RU2574345C2 (ru) Мобильная система передачи данных, устройство управления, устройство базовой станции, способ управления системой и способ управления устройством
AU2014246624B2 (en) Mobile communication system, control device, base station device, system control method and device control method

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 200980130582.2

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 09802771

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2009277764

Country of ref document: AU

WWE Wipo information: entry into national phase

Ref document number: 13054896

Country of ref document: US

WWE Wipo information: entry into national phase

Ref document number: 2010522648

Country of ref document: JP

ENP Entry into the national phase

Ref document number: 2732689

Country of ref document: CA

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2009277764

Country of ref document: AU

Date of ref document: 20090514

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 1349/CHENP/2011

Country of ref document: IN

ENP Entry into the national phase

Ref document number: 20117004845

Country of ref document: KR

Kind code of ref document: A

REEP Request for entry into the european phase

Ref document number: 2009802771

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2009802771

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2011107746

Country of ref document: RU

ENP Entry into the national phase

Ref document number: PI0911022

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20110119