+

WO2013167339A1 - Gestion d'unités de données d'état en provenance de flux de données multiples - Google Patents

Gestion d'unités de données d'état en provenance de flux de données multiples Download PDF

Info

Publication number
WO2013167339A1
WO2013167339A1 PCT/EP2013/057644 EP2013057644W WO2013167339A1 WO 2013167339 A1 WO2013167339 A1 WO 2013167339A1 EP 2013057644 W EP2013057644 W EP 2013057644W WO 2013167339 A1 WO2013167339 A1 WO 2013167339A1
Authority
WO
WIPO (PCT)
Prior art keywords
data unit
status data
link
radio link
link control
Prior art date
Application number
PCT/EP2013/057644
Other languages
English (en)
Inventor
Jani Matti Johannes Moilanen
Hans Thomas Hoehne
Alexander Sayenko
Original Assignee
Nokia Siemens Networks Oy
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
Application filed by Nokia Siemens Networks Oy filed Critical Nokia Siemens Networks Oy
Publication of WO2013167339A1 publication Critical patent/WO2013167339A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/24—Radio transmission systems, i.e. using radiation field for communication between two or more posts
    • H04B7/26—Radio transmission systems, i.e. using radiation field for communication between two or more posts at least one of which is mobile
    • H04B7/2612—Arrangements for wireless medium access control, e.g. by allocating physical layer transmission capacity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/34—Selective release of ongoing connections

Definitions

  • This disclosure relates to wireless communications and more particularly to handling of status data units from a multiple of data streams in a wireless communication system.
  • a wireless communication system can be seen as a facility that enables wireless carriers between two or more nodes such as fixed or mobile communication devices, access points such as base stations, servers machine type devices, and so on.
  • a communication system and compatible communicating devices typically operate in accordance with a given standard or specification which sets out what the various entities associated with the system are permitted to do and how that should be achieved. For example, the standards,
  • wireless systems can define the manner how and what communication devices shall communicate, how various aspects of the communications shall be implemented and how the devices shall be configured.
  • wireless systems include public land mobile networks (PLMN) such as cellular networks, satellite based communication systems and different wireless local networks, for example wireless local area networks (WLAN) .
  • PLMN public land mobile networks
  • WLAN wireless local area networks
  • Wireless systems can be divided into coverage areas referred to as cells.
  • a user can access the communication system by means of an appropriate communication device.
  • a communication device of a user is often referred to as user equipment (UE) or terminal.
  • UE user equipment
  • a communication device is provided with an appropriate signal receiving and transmitting arrangement for enabling
  • Wireless systems enable mobility for users where a mobile device can communicate over an air interface with another communication device such as e.g. a base station and/or other user equipment.
  • Examples of mobile communication systems are those based on standards by the 3rd Generation Partnership Project (3GPP) .
  • 3GPP 3rd Generation Partnership Project
  • LTE long-term evolution
  • UMTS Universal Mobile Telecommunications System
  • HSDPA High-Speed Downlink Packet Access
  • Tx Multiflow transmission
  • RLC radio link control
  • PDUs RLC protocol data units
  • RLC status PDU may define status information of a multiple of RLC PDUs and may thus refer to a multiple of PDU sequence numbers (SN) .
  • the feedback information can comprise for example ACK/NACK
  • HSPA high-speed packet access
  • RLC status PDUs arrive in the same sequence at a mobile device as they were sent by the element controlling the transmission. Therefore, the current HSPA RLC protocols define that if a mobile device receives a RLC status PDU that refers to a sequence number which is outside a RLC transmission window of the receiving mobile device it shall be considered as a sign of unexpected behaviour and the mobile device shall initiate a RLC reset to recover from this situation.
  • a RLC receive/transmission window refers to the number of outstanding received/sent packets. In normal operation a RLC transmission window must not exceed a RLC window divided by two.
  • a controlling element for example a RNC
  • the RNC may decide to send it via a second NodeB. This may happen e.g. if the radio link of the second NodeB is expected to have a better signal quality, for reasons of congestion and so on.
  • the first status PDU is delayed in the first NodeB it is possible that the status PDU sent via the second NodeB arrives at the mobile device first and the mobile device will shift its RLC window forward accordingly.
  • this PDU may be
  • the same RLC status PDU can be transmitted from more than one NodeB. Also in this case a status PDU that arrives first at a mobile device causes shift of the RLC transmission window, where after the (bicasted) status PDU arriving from another NodeB can cause a RLC reset.
  • a mobile device shall ignore any parts of RLC status PDU that refer to sequence numbers that fall outside the relevant RLC transmission window.
  • a problem with this approach can be that it may not provide sufficient robustness in a case where the RLC state machines at the network and the mobile device are out of synchronisation.
  • a result of this can be that a RLC reset might not be provided when it would actually be needed.
  • Embodiments of the invention aim to address one or several of the above issues.
  • a method for handling communications via multiple data streams comprising receiving at least one status data unit via a radio link control layer link of a multiple of possible links, and controlling radio link control resets.
  • controlling comprises determining how sequence information of the at least one status data unit received via the radio link control layer link relates to a predefined window
  • an apparatus for a communication device for controlling communications via multiple data streams comprising at least one processor, and at least one memory including computer program code, wherein the at least one memory and the computer program code are configured, with the at least one processor, to receive at least one status data unit via a radio link control layer link of a multiple of possible links, determine how sequence information of the at least one status data unit received via the radio link control layer link relates to a predefined window, and determine, based on the determined relation and at least one of information associated with said radio link control layer link and the received at least one status data unit whether to at least partially ignore the at least one status data unit or to perform a radio link control reset.
  • the determining whether to at least partially ignore the at least one status data unit or to perform the radio link control reset is provided in response to determining whether a radio link control status data unit refers to at least one sequence number which is outside a radio link control transmission window .
  • sequence information of the at least one status data unit received via said link is within the predefined window, information identifying said link may be stored. If it is determined that the sequence information of the at least one status data unit is outside the
  • At least part of the at least one status data unit is ignored.
  • Sequence information of at least one previously received status data unit for said one link may be stored.
  • sequence information of the at least one status data unit may be compared to the stored sequence information to determine timing of the status data unit.
  • the radio control link reset is performed.
  • the stored latest sequence information may be updated for the one link.
  • the comparing can comprise calculating a normalised sequence number for a received status data unit based on a stored latest sequence number and size of the window.
  • the storing of sequence information may comprise storing the latest sequence number of the latest received status data unit per each link or per each base station.
  • a mobile device arranged to implement the embodiments may also be provided.
  • a computer program comprising program code means adapted to perform the herein described methods may also be provided.
  • apparatus and/or computer program product that can be embodied on a computer readable medium for providing at least one of the above methods is provided .
  • Figure 1 shows a schematic diagram of a communication system where the invention may be embodied
  • Figure 2 shows a schematic diagram of a mobile device implementing certain embodiments
  • Figure 3 shows an example of an arrangement where data can be received on multiple links
  • Figure 4 shows an example of a problematic scenario with the multiple data floes of Figure 3; and Figures 5 to 7 show flowcharts according certain embodiments.
  • UTS Universal Mobile Telecommunications System
  • 3GPP base stations are known as Node Bs (for UMTS) and enhanced Node Bs (for 3GPP Long Term Evolution, LTE) .
  • the base station typically provide features such as user plane Radio Link Control/Medium Access Control/Physical layer protocol (RLC/MAC/PHY) and control plane Radio Resource
  • Radio Access system examples include those provided by base stations of systems that are based on technologies such as wireless local area network (WLAN) and/or WiMax (Worldwide Interoperability for Microwave
  • Mobile communication devices 1 can be provided with wireless access via base stations or similar wireless transmitter and/or receiver nodes providing radio service areas or cells.
  • Figure 1 shows two bases stations 2 and 4 proving cell 3 and 5, respectively.
  • a mobile communication device 1 may be located in the service areas of different cells, communicate with more than one cell and be handed over from a cell to another.
  • the base station nodes can be connected to a core communications network via appropriate gateways and/or backhaul systems. It is noted that the base stations and mobile devices are only schematically shown for illustration purposes in Figure 1, and that the number and type of these can vary considerably from that shown.
  • Base stations are typically controlled by at least one appropriate controller apparatus so as to enable operation thereof and management of mobile communication devices in communication with the base stations.
  • the control apparatus can be interconnected with other control entities.
  • the control apparatus can be
  • control apparatus and functions may be distributed between a plurality of control units. Two or more base stations may be controlled a control apparatus 6.
  • a possible mobile device for communications with the base stations is often referred to as user equipment (UE) or terminal.
  • a mobile device for implementing the embodiments may be provided by any device capable of sending radio signals to and/or receiving radio signals from multiple cells.
  • Non-limiting examples include a mobile station (MS) such as a mobile phone or what is known as a 'smart phone', a portable computer provided with a wireless interface card or other wireless interface facility, personal data assistant (PDA) provided with wireless communication capabilities, or any combinations of these or the like.
  • MS mobile station
  • PDA personal data assistant
  • a mobile device may provide, for example, communication of data for carrying communications such as voice, electronic mail (email) , text message, multimedia and so on. Users may thus be offered and provided numerous services via their devices.
  • Non-limiting examples of these services include two-way or multi-way calls, data communication or multimedia services or simply an access to a data communications network system, such as the Internet. User may also be provided broadcast or multicast data.
  • Non-limiting examples of the content include downloads, television and radio programs, videos, advertisements, various alerts and other information.
  • a mobile device may receive and transmit signals over an air interface with multiple base stations via an appropriate transceiver apparatus.
  • transceiver apparatus of a mobile device 20 is designated schematically by block 26.
  • the transceiver apparatus 26 may be provided for example by means of a radio part and associated antenna arrangement.
  • the antenna arrangement may be arranged internally or externally to the mobile device.
  • a mobile device is also provided with at least one data processing entity 21, at least one memory 22, and other possible components 23 for use in software and hardware aided execution of tasks it is designed to perform, including control of access to and communications with access systems and other communication devices.
  • the data processing, storage and other relevant control apparatus can be provided on an appropriate circuit board and/or in chipsets. This feature is denoted by reference 24.
  • the user may control the operation of the mobile device by means of a suitable user interface such as key pad 25, voice commands, touch sensitive screen or pad, combinations thereof or the like.
  • a display 28, a speaker and a microphone can be also provided.
  • a mobile communication device may comprise appropriate connectors (either wired or wireless) to other devices and/or for connecting external accessories, for example hands-free equipment, thereto.
  • a wireless communication device such as a base station and/or a mobile station, can be provided for example with a Multiple Input / Multiple Output (MIMO) antenna system for enabling multi-flow communications.
  • MIMO Multiple Input / Multiple Output
  • MIMO arrangements as such are known.
  • MIMO systems use multiple antennas at the
  • transmitter and receiver along with advanced digital signal processing to improve link quality and capacity. More data can be received and/or sent where there are more antenna elements .
  • downlink data flow can be split to independent data streams at radio link control (RLC) layer.
  • RLC radio link control
  • the splitting can be done in a radio network
  • RNC radio network controller
  • RLC protocol termination points are provided in the SRNC and the UE . Downlink data between the terminations flows via the two Node Bs .
  • Figure 4 shows an example of a possible scenario.
  • the controlling element in the example RNC sends a RLC status PDU first via a first NodeB (NB1) .
  • the RNC may decide to send the next RLC status PDU via a second NodeB (NB2) . This may happen e.g. if the radio link of the second NodeB is expected to have a better signal quality, for reasons of congestion and so on. If for some reason the first RLC status PDU is delayed in the first
  • NodeB e.g. if the first NodeB decides to schedule other, higher priority traffic, it may happen that the RLC status PDUs arrive at the mobile device in "wrong" order, i.e. PDU2 arrives before PDU1. After reception of PDU2 the mobile device advances its RLC window forward based thereon. When the status PDU from the first NodeB finally arrives it can refer to sequence numbers that fall outside the RLC transmission window of the receiving device, resulting an unnecessary RLC reset.
  • a mobile device for example a user equipment (UE) is adapted to utilize information regarding the link wherefrom it has received a RLC status PDU and/or information regarding a received RLC status PDU to determine whether it should ignore the RLC status PDU or perform a RLC reset.
  • the determination can be provided when sequence information, typically in the form of sequence numbers (SNs) , of the PDU referring to the relevant PDUs falls outside a RLC transmission window.
  • sequence information typically in the form of sequence numbers (SNs)
  • Control of radio link control resets comprises determining at 52 how sequencing information of a status data unit or a plurality of status data units received via the one link relates to a predefined window. It is then determined at 54, based on the determined relation between the sequencing information and the predefined window and also at least one of information associated with said one link and the received status data unit whether to ignore the at least one status data unit or to perform a radio link control reset.
  • the determining whether to ignore the status data unit or to perform the radio link control reset can be provided in response to determining whether a radio link control status data unit refers to a sequence number of a PDU that is outside a radio link control transmission window.
  • a user equipment (UE) capable of receiving via a multiple of links receives a radio link control (RLC) status PDU at 60
  • RLC radio link control
  • the UE can update a RLC state machine thereof at 65.
  • the UE can store at 64 information regarding the identity (ID) of the link on which it received the PDU.
  • ID the identity of the link on which it received the PDU.
  • a variable can be provided in the state machine of the UE to store information of the latest link ID. In the example this is done by setting the latest link ID parameter to equal with ID value X of the latest received link.
  • the RLC status PDU associates with falls outside the RLC transmission window of the UE It can be alternatively determined at 62 that at least one of the SNs of PDU the RLC status PDU associates with falls outside the RLC transmission window of the UE . In this case a further determination is made at 66 to check if the PDU was received from same link as the latest stored link ID. If yes, UE can perform RLC reset at 67. If it is determined that the PDU was received from a different link than the latest stored link ID, the UE can ignore the status PDU, or at least those parts thereof that are determined as falling outside transmission window, at 68.
  • a RLC status PDU may define status information for a multiple of RLC PDUs and thus the RLC status PDU may refer to a multiple of sequence numbers.
  • the status information of PDUs is typically sent in ascending order, it is possible to determine that if the first sequence number (SN) is already out of RLC transmission window so are the others and there is no need to check the other SNs.
  • RLC status PDU may be ignored, meaning that the status of those PDUs with SNs falling outside RLC transmission window are ignored but the rest of the status information, i.e. the part associated with SNs that fall inside RLC transmission window, is used normally to update the RLC state variables of the UE .
  • the operation may be as follows.
  • the UE can maintain a local state variable where it writes the last sequence number (LSN) of the latest received status PDU.
  • LSN last sequence number
  • a check is made at 71 if the RLC status PDU is within the RLC transmission window. If yes, the LSN(x) value is set accordingly at 72 and the status machine is updated at 73. If the RLC status PDU is not within the RLC transmission window, further determinations can follow .
  • RLC status PDU is determined at 74 to be "older” than the most recent RLC status PDU received from the same link
  • UE performs RLC reset at 75. If the RLC status PDU is determined to be newer, or the same, than the most recent RLC status PDU received from the same link and if the SNs it refers to fall (at least partly) outside the RLC transmission window the UE can ignore the RLC status PDU (or at least the parts that fall outside transmission window) at 77 and update the last sequence number (LSN) for the link at 76.
  • LSN last sequence number
  • This embodiment may provide protection against false RLC resets also in cases where several consecutive "out-of- window" status PDUs are received from a link.
  • a UE can store one variable, for example the last sequence number (LSN) per each link or per each base station site.
  • LSN last sequence number
  • the LSN of status report can be compared to the stored LSN to determine which one is "older". This can be done e.g. with a normalization procedure, for example with a normalization procedure used elsewhere in the RLC protocol.
  • the stored LSN value can be used as the RLC window basis to calculate the "normalized" LSN value of the received status PDU. If it is out of the transmission window it is considered to be older than the stored value and the RLC reset procedure is
  • this can be calculated based on: (SN - basis_SN+ WINDOW_SIZE) MOD WINDOW_SIZE.
  • the stored LSN value is 200, and a status PDU with LSN 100 is received, then assuming the maximum RLC sequence number value of 1024 and 200 as a basis for the RLC window, the result is 924. This value is larger than the total number of outstanding packets as governed by the RLC transmission window size (1024 / 2) .
  • the stored LSN value can become outdated if a RNC does not send status PDUs for a long period of time over a particular link. To avoid any unwanted
  • a UE advancing forward its RLC window can ensure that the distance between the stored LSN value and the beginning of the RLC window is less than the RLC transmission window size, i.e., the RLC window size divided by two.
  • the embodiments may provide advantage e.g. because data flow disruptions can be avoided during the serving cell change. This is so since transmission of RLC status PDUs is not limited to a certain link, for example to a serving link only, and thus a user equipment does not have to ignore valid RLC status PDUs even if these come from a "wrong" link. Good flexibility for a RNC to schedule RLC status PDUs may be provided. This can improve robustness of the links.
  • the required data processing apparatus and functions of a base station apparatus, a communication device and any other appropriate apparatus may be provided by means of one or more data processors.
  • the described functions at each end may be provided by separate processors or by an integrated circuit
  • the data processors may be of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) ,
  • ASIC application specific integrated circuits
  • gate level circuits and processors based on multi core processor
  • the data processing may be distributed across several data processing modules.
  • a data processor may be provided by means of, for example, at least one chip. Appropriate memory capacity can also be provided in the relevant devices.
  • the memory or memories may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory.
  • the various embodiments may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects of the invention may be implemented in hardware, while other aspects may be
  • firmware or software which may be executed by a controller, microprocessor or other computing device, although the invention is not limited thereto. While various aspects of the invention may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
  • the software may be stored on such physical media as memory chips, or memory blocks implemented within the processor, magnetic media such as hard disk or floppy disks, and optical media such as for example DVD and the data variants thereof, CD.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne des procédés et appareils servant à des communications via des flux de données multiples. Au moins une unité de données d'état peut être reçue via une liaison de la couche de commande de liaison radioélectrique parmi une multiplicité de liaisons possibles. La commande des réinitialisations de la liaison radioélectrique comporte les étapes consistant à déterminer la façon dont des informations d'ordre de l'unité ou des unités de données d'état reçues via la liaison de la couche de commande de liaison radioélectrique sont liées à une fenêtre prédéfinie. On détermine alors, en se basant sur la relation déterminée ainsi que sur des informations associées à ladite liaison de la couche de commande de liaison radioélectrique et / ou sur l'unité ou les unités de données d'état reçues, s'il y a lieu d'ignorer au moins partiellement l'unité ou les unités de données d'état ou d'effectuer une réinitialisation de la commande de liaison radioélectrique.
PCT/EP2013/057644 2012-05-07 2013-04-12 Gestion d'unités de données d'état en provenance de flux de données multiples WO2013167339A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
EP2012058388 2012-05-07
EPPCT/EP2012/058388 2012-05-07

Publications (1)

Publication Number Publication Date
WO2013167339A1 true WO2013167339A1 (fr) 2013-11-14

Family

ID=48083197

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2013/057644 WO2013167339A1 (fr) 2012-05-07 2013-04-12 Gestion d'unités de données d'état en provenance de flux de données multiples

Country Status (1)

Country Link
WO (1) WO2013167339A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015164005A1 (fr) * 2014-04-21 2015-10-29 Qualcomm Incorporated Synchronisation au niveau d'une entité de couche de commande de liaison radio (rlc)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1337125A2 (fr) * 2002-02-16 2003-08-20 Lg Electronics Inc. Procédé de changement de SRNS dans un système de communication mobile
EP1758408A1 (fr) * 2005-03-28 2007-02-28 Huawei Technologies Co., Ltd. Procede de reception d informations de commande de diffusion multimedia ou de service multidiffusion
EP2015526A2 (fr) * 2007-06-18 2009-01-14 LG Electronics, Inc. Comportement de protocole de convergence de données par paquets avec liaison descendante durant un transfert
EP2136570A1 (fr) * 2007-04-06 2009-12-23 NTT DoCoMo, Inc. Fenêtre de contrôle et procédé de contrôle de retransmission, et dispositif côté émission

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1337125A2 (fr) * 2002-02-16 2003-08-20 Lg Electronics Inc. Procédé de changement de SRNS dans un système de communication mobile
EP1758408A1 (fr) * 2005-03-28 2007-02-28 Huawei Technologies Co., Ltd. Procede de reception d informations de commande de diffusion multimedia ou de service multidiffusion
EP2136570A1 (fr) * 2007-04-06 2009-12-23 NTT DoCoMo, Inc. Fenêtre de contrôle et procédé de contrôle de retransmission, et dispositif côté émission
EP2015526A2 (fr) * 2007-06-18 2009-01-14 LG Electronics, Inc. Comportement de protocole de convergence de données par paquets avec liaison descendante durant un transfert

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015164005A1 (fr) * 2014-04-21 2015-10-29 Qualcomm Incorporated Synchronisation au niveau d'une entité de couche de commande de liaison radio (rlc)
CN106233655A (zh) * 2014-04-21 2016-12-14 高通股份有限公司 在无线电链路控制(rlc)层实体处的同步
JP2017518669A (ja) * 2014-04-21 2017-07-06 クアルコム，インコーポレイテッド 無線リンク制御（ｒｌｃ）層エンティティにおける同期

Similar Documents

Publication Publication Date Title
US20200280882A1 (en) Methods, apparatuses and computer program product for pdu formatting according to sdu segmentation
US11711167B2 (en) Apparatus, method and computer program
CN111801922B (zh) 用于支持v2x业务的控制信道结构设计
US12245181B2 (en) Multi-transmit-receive point transmission for ultra reliable low latency communication
AU2022287633B2 (en) Communication apparatus, method and computer program
CN109792322B (zh) 通信的方法、计算机可读介质和用于通信的装置
US20200128599A1 (en) Data transmission method, terminal device, and network device
KR20190103179A (ko) Rlc 계층 상태 리포트 제어 pdu의 전송 방법 및 관련 장치
WO2016116165A1 (fr) Procédé, appareil et système pour la configuration d'un canal de commande sur la liaison montante
US20100074178A1 (en) Method for Indication of Consecutive Data Units in a RAN
WO2013167339A1 (fr) Gestion d'unités de données d'état en provenance de flux de données multiples
US11968683B2 (en) Apparatus, method and computer program
US20230308229A1 (en) Apparatus, method, and computer program
CN111357223B (zh) 一种通信的方法、装置和计算机可读存储介质
WO2017080615A1 (fr) Procédé, système, et appareil
WO2019157738A1 (fr) Procédé, appareil et programme informatique
WO2018019358A1 (fr) Deuxième couche efficace pour réseau 5g
WO2021008672A1 (fr) Appareil, procédé et programme informatique pour la transmission fiable de commande
WO2019192730A1 (fr) Appareil, procédé et programme informatique
WO2018232627A1 (fr) Appareil de communication, procédé et programme informatique
WO2015118103A1 (fr) Sélection d'espacement de porteuses dans une agrégation de porteuses

Legal Events

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

Ref document number: 13715239

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13715239

Country of ref document: EP

Kind code of ref document: A1

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载