[go: up one dir, main page]

EP2537386B1 - Optimisation d'accès à base de conflit - Google Patents

Optimisation d'accès à base de conflit Download PDF

Info

Publication number
EP2537386B1
EP2537386B1 EP10707960.0A EP10707960A EP2537386B1 EP 2537386 B1 EP2537386 B1 EP 2537386B1 EP 10707960 A EP10707960 A EP 10707960A EP 2537386 B1 EP2537386 B1 EP 2537386B1
Authority
EP
European Patent Office
Prior art keywords
data packets
buffer
transmission
contention
resources
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.)
Active
Application number
EP10707960.0A
Other languages
German (de)
English (en)
Other versions
EP2537386A1 (fr
Inventor
Anna Larmo
Riikka Susitaival
Stefan Henrik Andreas Wager
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.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
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 Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of EP2537386A1 publication Critical patent/EP2537386A1/fr
Application granted granted Critical
Publication of EP2537386B1 publication Critical patent/EP2537386B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • 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
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • 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
    • 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
    • H04W72/566—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient
    • H04W72/569—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient of the traffic information

Definitions

  • the present invention relates generally to uplink transmissions, and more particularly to resource scheduling for uplink transmissions in LTE systems.
  • the base station dynamically allocates dedicated uplink resources to user terminals operating within the wireless network.
  • the basic assumption is that uplink resources are allocated only when the user terminal has data to send.
  • the user terminal When the user terminal has data to send, it sends a Scheduling Request (SR) to the base station at the first opportunity to request resources for the uplink transmission and waits for a Scheduling Grant (SG).
  • SR Scheduling Request
  • the base station dynamically allocates dedicated uplink resources to the requesting user terminal and sends an uplink Scheduling Grant (SG) to the user terminal identifying the allocated uplink resources.
  • BSRs Buffer Status Reports
  • BSRs Buffer Status Reports
  • the dynamic allocation of uplink resources can significantly increase the transmission efficiency so that uplink resources are not left unused if some of the user terminals have no data or only a small amount of data to send.
  • dedicated resource scheduling takes too long.
  • the user plane latency for scheduling uplink transmission on dedicated uplink resources is in the order of 11.5 ms due to uplink control channel cycle times, transmission times, and processing delays associated with the generation, transmission, and decoding of the SR and SG.
  • the 3GPP LTE-Advanced target for user plane latency is 10 ms or less.
  • 3GPP draft R2-080152 "Clearing pending BSR"; 3rd generation partnership project (3GPP), Mobile competence centre; 650, Route des Lucioles; F-06921 Sophia-Antipolis Cedex, France, vol. RAN WG2, no. Sevilla, Spain; 8 January 2008 , describes communication between a user equipment, UE, and an enhanced NodeB, eNodeB. More specifically, buffer status report, BSR, pendency is discussed in terms of whether or not the BSR has been successfully transmitted from the UE to the eNodeB.
  • 3GPP draft R2-101060 "The impact of contention based access”; 3rd generation partnership project (3GPP), mobile competence centre; 650, Route des Lucioles, F-06921 Sophia-Antilopis Cedex; France, vol. RAN WG2, no. San Francisco, USA; 12 February 2010 , describes the introduction of contention based (CB) access on PUSCH as a possible method for UP delay reduction and the impact this contention based access may have on RAN1 and RAN2.
  • 3GPP draft 3rd generation partnership project
  • 3GPP 3rd generation partnership project
  • 650 Route des Lucioles, F-06921 Sophia-Antilopis Cedex; France, vol. RAN WG2, no. San Francisco, USA
  • CB contention based
  • the present invention improves resource scheduling procedures by incorporating contention-based resource scheduling operations with existing dedicated resource scheduling operations.
  • the present invention controls the status of a pending scheduling request after the transmission of data packets on contention-based uplink resources based on the status of a transmission buffer.
  • a mobile station comprises a transmission buffer, a receiver, a transmitter, and a controller.
  • the controller triggers a scheduling request and buffer status report when data enters the transmission buffer.
  • the receiver receives a contention-based scheduling grant that schedules contention-based uplink resources
  • the transmitter transmits one or more data packets retrieved from the transmission buffer along with the buffer status report on the contention-based resources to the network station. If one or more data packets remain in the transmission buffer after transmission of the buffer status report on the contention-based resources, the controller maintains the pending status of the buffer status report and the corresponding scheduling request and subsequently transmits the scheduling request on an uplink control channel.
  • the controller ensures that the network station will eventually be made aware of a need for uplink transmission resources for the remaining data, even if the buffer status report transmitted on the contention-based resources is lost or otherwise not correctly received by the network station.
  • the mobile station receives a dedicated scheduling grant, allocating dedicated resources for uplink transmission and no data packets remain in the transmission buffer upon receipt of the dedicated scheduling grant, the mobile station implements pro-active retransmission by transmitting one or more data packets awaiting acknowledgement from a higher protocol layer on said dedicated resources.
  • Figure 1 illustrates a mobile communication network 10 including a base station 20 and a plurality of user terminals 30.
  • a scheduler 22 at the base station 20 coordinates the transmissions from the user terminals 30 to the base station 20 on the uplink.
  • the scheduler 22 determines when the user terminals 30 are allowed to transmit on the uplink and allocates uplink resources to the user terminals 30.
  • the scheduler 22 may allocate either dedicated resources or contention-based resources to the user terminal 30.
  • Scheduling uplink resources is a function of the medium access control (MAC) layer in LTE systems.
  • MAC medium access control
  • the exemplary embodiment is described in the context an LTE system; however, those skilled in the art will appreciate that the present invention is applicable to communication systems using other standards now known or later developed where transmission on uplink resources are scheduled by the network.
  • LTE systems use a request-grant procedure for scheduling user terminals 30 on dedicated uplink resources.
  • a user terminal 30 sends a scheduling request (SR) to the base station 20 at the first opportunity when the user terminal 30 has data to send.
  • the scheduler 22 at the base station 20 allocates uplink resources to the user terminal 30 and sends a scheduling grant (SG) to the user terminal 30 that gives permission to the user terminal 30 to transmit data on the resources identified in the SG.
  • the transmission buffers for the uplink are located at the user terminals 30, the user terminals 30 provide information about transmission buffer levels to the base station 20 by sending a buffer status report (BSR).
  • BSR buffer status report
  • a BSR is triggered when data arrives in the transmission buffer containing a higher priority than data already in the transmission buffer.
  • a BSR can also be triggered when a predetermined period of time has elapsed since the last BSR, or when the serving cell for the user terminal 30 changes.
  • the user plane latency for scheduling uplink transmission on dedicated uplink resources is in the order of 11.5 ms in the best case due to uplink control channel cycle times, transmission times, and processing delays associated with the generation, transmission, and decoding of the SR and SG.
  • a mechanism is also provided for contention-based access on uplink resources that have not been allocated to a specific user terminal 30 by the scheduler 22. There will be times when uplink resources are still available after allocating dedicated resources to the user terminals 30.
  • the base station 20 may allow all eligible user terminals 30 to send data on a contention basis without first requesting resources by sending a contention-based scheduling grant on a control channel to all user terminals 30. For example, time-aligned user terminals 30 that have data packets to transmit may use the resources allocated by the CBG to transmit the data packets.
  • FIG. 2 illustrates an exemplary contention-based access procedure 100 for the uplink in a wireless communication system according to one exemplary embodiment of the present invention.
  • data arriving at the transmit buffer of a user terminal 30 triggers a BSR and SR (110). While the BSR and SR are pending, the base station 20 sends a Contention-Based scheduling Grant (CBG) indicating that uplink resources are available (120).
  • CBG Contention-Based scheduling Grant
  • the base station 20 may, for example, transmit the CBG on the PDCCH. While the CBG is not addressed to a specific user terminal 30 and is not generated responsive to an SR, the CBG may use a Contention-Based Radio Network Temporary Identifier (CB-RNTI) to identify the CBG to the user terminals 30.
  • CB-RNTI Contention-Based Radio Network Temporary Identifier
  • the user terminals 30 may be made aware of the CB-RNTI as part of system broadcast information, or the CB-RNTI may be signaled to each user terminal 30 during connection setup.
  • the CBG identifies the uplink resources available for contention-based access and may have the same format as a dedicated SG, e.g., may specify a modulating and coding scheme, transport format, etc., to be used for the contention-based uplink transmission. Alternatively, a new format could be defined to efficiently signal several CBGs.
  • each user terminal 30 compatible with contention-based operations listens for both a CBG addressed to a CB-RNTI and an SG addressed to their dedicated C-RNTI. It will be appreciated that contention-based operations are backwards compatible as any user terminals 30 incompatible with contention-based operations will not decode the CBG addressed to a CB-RNTI.
  • the user terminal 30 Responsive to the CBG, transmits data retrieved from the transmission buffer on the uplink resources identified in the CBG and appends the BSR to one or more of the transmitted data packets (130).
  • the hybrid automatic repeat request (HARQ) retransmission protocol is typically not used for transmissions on contention-based resources. If the transmission buffer is emptied by the contention-based transmission, the BSR and SR may be cancelled. However, when data remains in the transmission buffer, it may be beneficial to keep the BSR and SR pending because transmissions on the contention-based resources are not as reliable as a scheduled transmission on dedicated resources.
  • BSR Buffer Status Report
  • the user terminal 30 cannot be certain that the BSR will be received.
  • the present invention reduces the impact of such contention-based transmission errors by maintaining the pending status of the BSR, and therefore the pending status of the corresponding SR, when one or more data packets remain in a transmission buffer after the transmission of data packets on the contention-based resources (140).
  • the user terminal 30 transmits the pending SR to the base station 20 (150). Maintaining the pending status of the BSR and SR when data packets remain in the transmission buffer, and subsequently sending the SR to the base station 20, speeds up the process of receiving a dedicated SG at the user terminal 30.
  • the present invention potentially enables a faster recovery of any failed transmissions associated with contention-based operations by speeding up the process necessary to enable retransmissions, e.g., RLC or MAC retransmissions, of any missing data packets
  • a user terminal 30 may transmit data packets on contention-based resources after sending a SR to the base station 20. If the transmission buffers are emptied by a CB transmission, the user terminal 30 may not have data to send when it receives the dedicated SG from the base station 20. The user terminal 30 is still required to transmit something on the dedicated resources. The user terminal 30 may, for example, transmit padding to the base station 20 on the dedicated resources. However, the uplink resource is essentially wasted in this case.
  • the user terminal 30 may implement a pro-active retransmission of an unacknowledged radio link control (RLC) packet when it has no data left in its transmission or retransmission buffer.
  • RLC radio link control
  • the RLC layer is above the MAC layer where HARQ operations are performed.
  • the RLC layer is responsible for segmentation of Packet Data Convergence Protocol (PDCP) packets into RLC packet data units (PDUs), which are passed to the MAC layer.
  • PDCP Packet Data Convergence Protocol
  • PDUs RLC packet data units
  • AM acknowledged mode
  • the RLC layer also implements a retransmission protocol to ensure error free delivery of data packets to higher layers.
  • AM is typically used for TCP-based services where error-free data delivery is important.
  • the user terminal 30 may, instead, retrieve data waiting to be acknowledged from the RLC transmission buffer and pro-actively retransmit the retrieved RLC PDUs. It will be appreciated that these pro-active retransmissions of RLC PDUs are not requested by the base station 20. To ensure that such unprompted pro-active retransmission do not interfere with normal RLC operations, the RLC retransmission counter should not be incremented when a pro-active retransmission is performed at the MAC level.
  • FIG. 3 shows one exemplary pro-active retransmission process 200 according to the present invention.
  • the user terminal 30 transmits an SR to the base station 20 to request uplink resources and waits for a SG (210). While the user terminal 30 is waiting for the SG, the base station 20 sends a CBG to the user terminals 30 on the PDCCH as previously described (220). Because the user terminal 30 has data to send, it transmits data contained in its transmission buffer on the uplink resources identified in the CBG (230). It is presumed in this example that the transmission buffer is emptied by the contention-based transmission.
  • the base station 20 allocates uplink resources to the user terminal 30 (240) and sends an SG to the user terminal 30 (250). Because the user terminal 30 no longer has any data in its transmission buffers, the user terminal 30 retrieves data packets from the RLC transmission buffer (260) that were already sent and are awaiting acknowledgement, and pro-actively retransmits the retrieved RLC data packets to the base station 20 on the dedicated resources allocated to the user terminal 30 by the SG (270). To ensure that the unprompted retransmission does not interfere with normal RLC operations, the user terminal 30 does not increment the RLC retransmission counter. The RLC entities at the base station 20 will delete any duplicate RLC PDUs. According to normal HARQ operations, the base station 20 will acknowledge the packets sent (280). However, the acknowledgement is only of the MAC layer packets containing the RLC PDU, and not of the RLC PDU.
  • FIG. 4 shows one exemplary user terminal 30 according to the present invention.
  • User terminal 30 comprises antenna 32, transceiver 34, a controller 36, and buffer system 40.
  • Transceiver 34 configured to transmit data packets to the base station and receive data packets from the base station via antenna 32.
  • Controller 36 processes the signals transmitted and received by the user terminal 30 and controls the operation of user terminal 30, and particularly implements MAC and RLC layer protocols.
  • the controller 36 performs physical layer processing such as coding/decoding, modulation/demodulation, etc. and implements higher layer protocols including MAC protocols and RLC protocols.
  • the controller 36 may comprise one or more microprocessors, firmware, hardware, or a combination thereof.
  • the buffer system 40 comprises memory for storing data to be transmitted or retransmitted.
  • the buffer system includes a MAC transmission and retransmission buffers 42, 44 for HARQ operations, as well as a RLC transmission and retransmission buffers 46, 48 for AM operations.
  • the buffer system 40 may also contain the PDCP-level buffers, but for simplicity reasons, the PDCP-level buffers are left out of this example.
  • the controller 36 implements MAC layer and RLC layer protocols as herein described.
  • the controller 36 implements MAC layer operations, such as generating and sending BSRs and SRs, maintaining MAC transmission and retransmission buffers 42, 44, processing received SGs or CBGs, and retrieving data from the transmission and retransmission buffers 40 for transmission on the scheduled resources.
  • Controller 36 may also include a RLC retransmission counter 38 that tracks the number of retransmissions of RLC PDUs.
  • the MAC transmission buffer 42 stores new data (e.g. transport blocks) waiting for transmission. After transmission on dedicated uplink resources, the transmitted data packets await acknowledgement by the base station 20.
  • the data packets are put in the retransmission buffer 44 and the controller 36 resends the data packets. Because HARQ retransmission is not typically used for contention-based transmissions, data transmitted on CB resources does not typically await acknowledgement and is typically removed from the transmission buffer 42.
  • the RLC transmission buffer 46 stores new RLC PDUs waiting for transmission. After transmission on uplink resources, the RLC PDUs are kept in the transmission buffer 46 while waiting for acknowledgement by the base station 20.
  • the PDU is moved to the RLC retransmission buffer 48.
  • the controller 36 increments the RLC counter 38 and resends the PDU in the retransmission buffer 48 unless the RLC counter 38 indicates the maximum number of retransmissions has been reached.
  • RLC PDUs stored in the RLC transmission buffer 46 awaiting acknowledgement can be retransmitted proactively in response to an SG from the base station 20 when there is no other data in the transmission buffers. In this case, the RLC counter is not incremented.
  • the contention-based access procedure described herein reduces the time it takes to access uplink resources and signaling overhead by allowing a synchronized user terminal 30 to send data on the uplink without first requesting resources for the transmission.
  • the present invention may, of course, be carried out in other ways than those specifically set forth herein without departing from the claims.
  • the present embodiments are to be considered in all respects as illustrative and not restrictive, and all changes coming within the appended claims are intended to be embraced therein.

Landscapes

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

Claims (12)

  1. Station mobile (30) comprenant :
    un tampon de transmission (40) configuré pour stocker un ou plusieurs paquets de données destinés à être transmis à une station de réseau ;
    un récepteur (34) configuré pour recevoir, à partir de la station de réseau, une autorisation de planification à base de conflit, attribuant des ressources à base de conflit pour une transmission en liaison montante de la station mobile à la station de réseau ; et
    un émetteur (34) configuré pour transmettre, en réponse à l'autorisation de planification à base de conflit, un ou plusieurs paquets de données contenus dans le tampon de transmission (40), sur lesdites ressources à base de conflit, dans laquelle, si un rapport d'état de tampon est en attente, ledit émetteur est en outre configuré pour transmettre le rapport d'état de tampon avec les un ou plusieurs paquets de données transmis sur lesdites ressources à base de conflit ;
    la station mobile étant caractérisée en ce qu'elle comprend en outre :
    un dispositif de commande (36) configuré pour maintenir un état en attente du rapport d'état de tampon et une demande de planification correspondante lorsqu'un ou plusieurs paquets de données restent dans le tampon de transmission (40) après la transmission du rapport d'état de tampon sur lesdites ressources à base de conflit,
    dans laquelle le récepteur (34) est en outre configuré pour recevoir, à partir de la station de réseau, une autorisation de programmation dédiée, attribuant des ressources dédiées pour une transmission en liaison montante de la station mobile à la station de réseau, et
    dans laquelle l'émetteur (34) est en outre configuré pour exécuter une retransmission proactive, lorsqu'il ne reste plus de paquets de données dans le tampon de transmission (40) lors de la réception de l'autorisation de planification dédiée, en transmettant, en réponse à l'autorisation de planification dédiée, un ou plusieurs paquets de données en attente d'un accusé de réception d'une couche de protocole supérieure sur lesdites ressources dédiées.
  2. Station mobile (30) selon la revendication 1, dans laquelle le rapport d'état de tampon reflète un état du tampon de transmission (40) après que les paquets de données ont été retirés du tampon de transmission (40) pour la transmission.
  3. Station mobile (30) selon la revendication 1, dans laquelle le dispositif de commande (36) est en outre configuré pour annuler l'état en attente du rapport d'état de tampon et la demande de planification correspondante lorsqu'il ne reste plus de paquets de données dans le tampon de transmission (40) .
  4. Station mobile (30) selon la revendication 1, dans laquelle l'émetteur (34) transmet le rapport d'état de tampon avec les un ou plusieurs paquets de données transmis en ajoutant le rapport d'état de tampon à au moins un paquet de données des un ou plusieurs paquets de données transmis avant la transmission de l'au moins un paquet de données à la station de réseau.
  5. Station mobile (30) selon la revendication 1, dans laquelle le tampon de transmission (40) comprend un nouveau tampon de transmission de données configuré pour stocker des paquets de données en attente d'une première transmission à la station de réseau, et dans laquelle l'émetteur (34) est en outre configuré pour transmettre, en réponse à l'autorisation de planification dédiée, un ou plusieurs paquets de données contenus dans le nouveau tampon de transmission de données sur lesdites ressources dédiées.
  6. Station mobile (30) selon la revendication 1,
    dans laquelle le tampon de transmission (40) stocke des paquets de données dans une couche de protocole, et
    dans laquelle un compteur de retransmission est configuré pour maintenir une valeur actuelle lorsque l'émetteur (34) transmet un ou plusieurs paquets de données à partir de la couche de protocole supérieure sur lesdites ressources dédiées.
  7. Procédé de transmission de données à partir d'une station mobile, le procédé comprenant :
    la réception (120), à partir d'une station de réseau, d'une autorisation de planification à base de conflit attribuant des ressources à base de conflit pour une transmission en liaison montante de la station mobile à la station de réseau ;
    la transmission (130), en réponse à l'autorisation de planification à base de conflit, d'un ou de plusieurs paquets de données contenus dans un tampon de transmission sur lesdites ressources à base de conflit ;
    si un rapport d'état de tampon est en attente, la transmission du rapport d'état de tampon avec les un ou plusieurs paquets de données transmis sur lesdites ressources à base de conflit ; et le procédé étant caractérisé par :
    le maintien (140) d'un état en attente du rapport d'état de tampon et d'une demande de planification correspondante lorsqu'un ou plusieurs paquets de données restent dans le tampon de transmission après la transmission du rapport d'état de tampon sur les ressources à base de conflit ;
    la réception (250), à partir de la station de réseau, d'une autorisation de planification dédiée, attribuant des ressources dédiées pour une transmission en liaison montante de la station mobile à la station de réseau ; et
    la mise en oeuvre d'une retransmission proactive lorsqu'aucun paquet de données ne reste dans le tampon de transmission lors de la réception de l'autorisation de planification dédiée en transmettant (270), en réponse à la dite autorisation de planification dédiée, un ou plusieurs paquets de données en attente d'un accusé de réception d'une couche de protocole supérieure sur lesdites ressources dédiées.
  8. Procédé selon la revendication 7, dans lequel le rapport d'état de tampon reflète un état du tampon de transmission après que les paquets de données ont été retirés du tampon de transmission pour la transmission.
  9. Procédé selon la revendication 7, comprenant en outre l'annulation de l'état en attente du rapport d'état de tampon et de la demande de planification correspondante lorsqu'il ne reste plus de paquets de données dans le tampon de transmission.
  10. Procédé selon la revendication 7, dans lequel la transmission du rapport d'état de tampon avec les un ou plusieurs paquets de données transmis comprend l'ajout du rapport d'état de tampon à au moins un paquet de données des un ou plusieurs paquets de données transmis avant la transmission de l'au moins un paquet de données à la station de réseau.
  11. Procédé selon la revendication 7, dans lequel le tampon de transmission comprend un nouveau tampon de transmission de données configuré pour stocker des paquets de données en attente d'une première transmission à la station de réseau, le procédé comprenant en outre la transmission (270), en réponse à l'autorisation de planification dédiée, d'un ou de plusieurs paquets de données contenus dans le nouveau tampon de transmission de données sur lesdites ressources dédiées.
  12. Procédé selon la revendication 7, dans lequel la retransmission proactive est en outre mise en oeuvre en maintenant un compteur de retransmission à une valeur actuelle après la transmission d'un ou de plusieurs paquets de données de la couche de protocole supérieure sur lesdites ressources dédiées.
EP10707960.0A 2010-02-15 2010-02-15 Optimisation d'accès à base de conflit Active EP2537386B1 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/IB2010/000284 WO2011098849A1 (fr) 2010-02-15 2010-02-15 Optimisation d'accès à base de conflit

Publications (2)

Publication Number Publication Date
EP2537386A1 EP2537386A1 (fr) 2012-12-26
EP2537386B1 true EP2537386B1 (fr) 2019-09-18

Family

ID=42990247

Family Applications (1)

Application Number Title Priority Date Filing Date
EP10707960.0A Active EP2537386B1 (fr) 2010-02-15 2010-02-15 Optimisation d'accès à base de conflit

Country Status (4)

Country Link
US (1) US9185722B2 (fr)
EP (1) EP2537386B1 (fr)
CN (1) CN102742348B (fr)
WO (1) WO2011098849A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12457604B2 (en) 2020-06-02 2025-10-28 Huawei Technologies Co., Ltd. Communication method and apparatus

Families Citing this family (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20130005290A (ko) * 2010-03-18 2013-01-15 알까뗄 루슨트 업링크 송신을 위한 방법, 기지국 및 중계 노드
KR101691480B1 (ko) * 2010-04-06 2017-01-09 삼성전자주식회사 이동통신 시스템에서 패킷 재전송 방법 및 장치
US10028302B2 (en) * 2013-03-08 2018-07-17 Huawei Technologies Co., Ltd. System and method for uplink grant-free transmission scheme
CN104080185B (zh) * 2013-03-29 2018-03-23 普天信息技术研究院有限公司 一种适用于tcp/ip业务的无线资源调度方法
EP3032855B1 (fr) * 2013-09-11 2019-07-24 Huawei Technologies Co., Ltd. Procédé de transmission de données et équipement utilisateur
US10327263B2 (en) 2014-02-16 2019-06-18 Lg Electronics Inc. Method and apparatus for transmitting scheduling request using contention-based resources in wireless communication system
US20150359000A1 (en) * 2014-06-09 2015-12-10 Qinghua Li Multi-user scheduling channel status reporting for wi-fi
WO2016070381A1 (fr) * 2014-11-06 2016-05-12 华为技术有限公司 Procédé d'émission de données, procédé, dispositif et appareil de mesure de ressources
WO2016175632A1 (fr) * 2015-04-30 2016-11-03 Lg Electronics Inc. Procédé et appareil pour commander la congestion d'une émission de pusch basée sur la contention ou d'une émission de sr basée sur la contention dans un système de communication sans fil
US10470210B2 (en) * 2015-05-11 2019-11-05 Lg Electronics Inc. Method for performing RLC retransmission based on contention-based PUSCH in a wireless communication system and a device therefor
US10966119B2 (en) 2015-05-12 2021-03-30 Lg Electronics Inc. Method for transmitting a contention-based PUSCH in a wireless communication system and a device therefor
JP2018520529A (ja) * 2015-05-21 2018-07-26 インテル アイピー コーポレーション 非競合ベースの低レイテンシのスケジューリング要求の送信
EP3298847B1 (fr) * 2015-05-22 2020-07-01 LG Electronics Inc. Procédé de configuration d'autorisations de liaison montante sur une pluralité de sous-trames dans un système de communications sans fil, et dispositif associé
US10555322B2 (en) 2015-06-18 2020-02-04 Intel IP Corporation Low latency contention based scheduling request
US10009923B2 (en) * 2016-01-28 2018-06-26 Qualcomm Incorporated Contention-based data transmissions on return link
KR102693262B1 (ko) 2016-09-22 2024-08-08 삼성전자주식회사 상향링크 데이터 재송신을 제어하기 위한 장치 및 방법
US10440735B2 (en) 2016-11-29 2019-10-08 Telefonaktiebolaget Lm Ericsson (Publ) Uplink hopping pattern for contention-based reliable communication
US10708944B2 (en) 2017-01-06 2020-07-07 Telefonaktiebolaget Lm Ericsson (Publ) Preconfigured grants with a distribution pattern
WO2018145078A1 (fr) * 2017-02-06 2018-08-09 Intel IP Corporation Mécanismes de retransmission pour opérations harq basées sur des groupes de blocs de codes (cbg)
CA3146623C (fr) 2017-03-08 2024-05-28 Lg Electronics Inc. Procede et appareil d'emission et de reception d'un signal sans fil dans un systeme de communication sans fil
CN108712735B (zh) * 2017-03-29 2021-09-24 株式会社Kt 用于配置传输块以发送数据的方法和设备
CN110945901B (zh) * 2017-04-24 2022-03-01 摩托罗拉移动有限责任公司 复制用于无线电承载的pdcp pdu
CN114826490B (zh) * 2017-05-05 2024-06-21 北京三星通信技术研究有限公司 调度方法、harq-ack反馈方法和相应设备
WO2018230996A1 (fr) * 2017-06-15 2018-12-20 엘지전자 주식회사 Procédé d'émission et de réception de demande de planification entre un terminal et une station de base dans un système de communication sans fil, et dispositif prenant en charge ce procédé
US10454620B2 (en) 2017-06-16 2019-10-22 At&T Intellectual Property I, L.P. Facilitating notifications to indicate failed code block groups in 5G or other next generation networks
US10631195B2 (en) * 2017-06-16 2020-04-21 Hughes Network Systems, Llc Buffer status report trigger enhancement in a long term evolution and satellite communication system

Family Cites Families (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2006135985A (ja) * 2004-11-04 2006-05-25 Samsung Electronics Co Ltd 移動通信システムにおけるソフトハンドオーバー領域に位置した端末機のための上りリンクデータの送信をスケジューリングする方法及び装置
KR100651548B1 (ko) * 2004-11-05 2006-11-29 삼성전자주식회사 상향링크 패킷 데이터 서비스를 지원하는 이동통신시스템에서 단말 식별자를 이용하여 상향링크 데이터전송을 스케쥴링하는 방법 및 장치
JP2006157167A (ja) * 2004-11-25 2006-06-15 Toshiba Corp 音声通信端末
WO2008054274A1 (fr) * 2006-11-01 2008-05-08 Telefonaktiebolaget Lm Ericsson (Publ) Procédé pour réduire un retard dans un système de communication utilisant un harq
US20080146242A1 (en) * 2006-12-18 2008-06-19 Nokia Corporation Method for requesting an uplink resource allocation during a downlink data transmission
JP4976904B2 (ja) * 2007-04-06 2012-07-18 株式会社エヌ・ティ・ティ・ドコモ 再送制御方法及び送信側装置
EP1986455A1 (fr) * 2007-04-27 2008-10-29 Matsushita Electric Industrial Co., Ltd. Communication de planification d'informations associées dans un système de communication mobile
HUE044307T2 (hu) * 2007-06-19 2019-10-28 Optis Cellular Tech Llc Eljárások és rendszerek erõforrások ütemezésére telekommunikációs rendszerben
US8077644B2 (en) * 2007-07-20 2011-12-13 Infineon Technologies Ag Data transfer in a computing device
KR101591824B1 (ko) * 2007-09-18 2016-02-04 엘지전자 주식회사 무선 통신 시스템에서의 폴링 과정 수행 방법
EP3048835B1 (fr) * 2008-02-20 2020-09-30 Amazon Technologies, Inc. Appareil et procede pour la construction d'une unite de donnees qui inclut un rapport d'etat du tampon
JP5129863B2 (ja) * 2008-02-25 2013-01-30 エルジー エレクトロニクス インコーポレイティド 無線通信システムにおけるランダムアクセス実行方法
US9203562B2 (en) * 2008-03-07 2015-12-01 Mediatek Inc. Cooperating timer and retransmission counter for buffer management in a HARQ wireless network
CN101978758B (zh) 2008-03-28 2014-11-12 爱立信电话股份有限公司 网络驱动l3控制信令优先化
CN101562894B (zh) 2008-04-26 2010-10-20 华为技术有限公司 一种缓冲区状态报告的发送方法及其设备
EP2131517A3 (fr) * 2008-06-03 2010-01-20 Innovative Sonic Limited Procédé et appareil pour améliorer la transmission de lien HARQ
GB2461159B (en) * 2008-06-18 2012-01-04 Lg Electronics Inc Method for transmitting Mac PDUs
EP2136599B1 (fr) * 2008-06-18 2017-02-22 LG Electronics Inc. Détection de défaillances de procédures d'accès aléatoire
US8031668B2 (en) * 2008-06-23 2011-10-04 Sunplus Mmobile Inc. Method for optimizing discontinuous reception in random access and scheduling request
US8681806B2 (en) * 2008-06-23 2014-03-25 Koninklijke Philips N.V. Method for communicating in a network and radio stations associated
US8873474B2 (en) * 2008-10-17 2014-10-28 Telefonaktiebolaget L M Ericsson (Publ) Method and mobile terminal providing priority-based uplink scheduling information
US8279818B2 (en) * 2008-10-31 2012-10-02 Htc Corporation Methods of packet element transmission in wireless communications system
EP2182770B1 (fr) * 2008-11-04 2011-09-21 HTC Corporation Procédé pour une transmission montante améliorée dans un système de communications sans fil
WO2010057540A1 (fr) * 2008-11-21 2010-05-27 Telefonaktiebolaget L M Ericsson (Publ) Dispositifs et procédé de transmission dans un système de communication avec une transmission de données basée sur un conflit
US8897252B2 (en) * 2009-06-17 2014-11-25 Htc Corporation Method for transmitting data in a wireless communication system and system thereof

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
CATT: "The impact of the contention based access", 3GPP DRAFT; R2-101060, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. San Francisco, USA; 20100222, 12 February 2010 (2010-02-12), XP050421374 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12457604B2 (en) 2020-06-02 2025-10-28 Huawei Technologies Co., Ltd. Communication method and apparatus

Also Published As

Publication number Publication date
CN102742348B (zh) 2016-05-18
US9185722B2 (en) 2015-11-10
US20120300744A1 (en) 2012-11-29
CN102742348A (zh) 2012-10-17
WO2011098849A1 (fr) 2011-08-18
EP2537386A1 (fr) 2012-12-26

Similar Documents

Publication Publication Date Title
EP2537386B1 (fr) Optimisation d'accès à base de conflit
US11805515B2 (en) Blind scheduling apparatus and method in a mobile communication system
US8755408B2 (en) Method and apparatus for MAC message reliability
EP2207394B1 (fr) Procédé et appareil pour améliorer un processus de libération de ressource de planification semi-persistante dans un système de communication sans fil
EP2613468B1 (fr) Procédé pour la transmission en liaison montante d'une couche de contrôle de liaison radio (rlc) et noeud b évolué (enb)
KR102810505B1 (ko) Urllc 서비스를 위한 낮은 레이턴시 harq 프로토콜
US7403528B2 (en) Method of data communication using a control message
US20110069668A1 (en) Dedicated Acknowledgement and Delivery of Management Messages in Wireless Communication Systems
EP2874371B1 (fr) Procédé et dispositif de transmission de paquet de données
CN101741529A (zh) 处理传输时间间隔集束的方法及其相关装置
CN101651601A (zh) 一种资源配置方法、系统及相关装置
KR101669266B1 (ko) 네트워크에서 통신하는 방법, 제 2 스테이션 및 이를 위한 시스템
CN102118236B (zh) 一种基于竞争资源的反馈方法和装置
KR20170054218A (ko) 통신 시스템에서의 빠른 접속을 위한 방법 및 장치

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20120904

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO SE SI SK SM TR

DAX Request for extension of the european patent (deleted)
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20180117

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 28/06 20090101ALI20190307BHEP

Ipc: H04W 72/12 20090101AFI20190307BHEP

Ipc: H04W 24/10 20090101ALI20190307BHEP

INTG Intention to grant announced

Effective date: 20190410

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602010061088

Country of ref document: DE

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1182834

Country of ref document: AT

Kind code of ref document: T

Effective date: 20191015

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20190918

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190918

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190918

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191218

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190918

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190918

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191218

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190918

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191219

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1182834

Country of ref document: AT

Kind code of ref document: T

Effective date: 20190918

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190918

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190918

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200120

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190918

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190918

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190918

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190918

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190918

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190918

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200224

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190918

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190918

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602010061088

Country of ref document: DE

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG2D Information on lapse in contracting state deleted

Ref country code: IS

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190918

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200119

26N No opposition filed

Effective date: 20200619

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190918

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20200229

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190918

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200215

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200229

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200229

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200215

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200229

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200229

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20220225

Year of fee payment: 13

Ref country code: DE

Payment date: 20220225

Year of fee payment: 13

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190918

Ref country code: MT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190918

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190918

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190918

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602010061088

Country of ref document: DE

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20230215

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230215

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230215

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230901