WO2020001773A1 - Appareil et procédé pour des communications fiables en connectivité multiple - Google Patents

Appareil et procédé pour des communications fiables en connectivité multiple Download PDF

Info

Publication number
WO2020001773A1
WO2020001773A1 PCT/EP2018/067415 EP2018067415W WO2020001773A1 WO 2020001773 A1 WO2020001773 A1 WO 2020001773A1 EP 2018067415 W EP2018067415 W EP 2018067415W WO 2020001773 A1 WO2020001773 A1 WO 2020001773A1
Authority
WO
WIPO (PCT)
Prior art keywords
user terminal
data packet
receiving
transmit
response
Prior art date
Application number
PCT/EP2018/067415
Other languages
English (en)
Inventor
Daniela Laselva
Klaus Ingemann Pedersen
Nurul MAHMOOD
Original Assignee
Nokia Technologies 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 Technologies Oy filed Critical Nokia Technologies Oy
Priority to PCT/EP2018/067415 priority Critical patent/WO2020001773A1/fr
Publication of WO2020001773A1 publication Critical patent/WO2020001773A1/fr

Links

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
    • H04W28/12—Flow control between communication endpoints using signalling between network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/189—Transmission or retransmission of more than one copy of a message
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/14—Multichannel or multilink protocols
    • 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/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • 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/15—Flow control; Congestion control in relation to multipoint traffic

Definitions

  • the exemplary and non-limiting embodiments of the invention relate generally to communications.
  • multi-connectivity In communication systems, connections between communicating parties were in the past single connections. Recently, multi-connectivity has been the object of increasing research. This applies especially to wireless communication systems comprising user terminals in cells served by base stations or the like.
  • a communicating party such as a user terminal is not connected only to a single cell on a single frequency layer, but simultaneously to multiple cells on different frequency layers or even different, not necessarily co-sited radio interfaces. Multi connectivity can also be between two cells on the same frequency layer
  • Ultra-reliable communication is another topic which is becoming more and more relevant. There will be more and more use cases which require an extremely small packet loss rate, and at the same time have a tight delay budget which does not allow for many retransmissions. A prominent example of such use cases is autonomous driving, vehicular safety in general, and industrial communication. Multi-connectivity has been seen as a solution for providing reliable communication links.
  • Processing data packets which are transmitted through more than one transmission link presents challenges as fast and reliable transmission of data is of importance in many applications.
  • an apparatus in a communication system configured to communicate with a user terminal
  • the apparatus comprising: at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform: control communication with another apparatus configured to communicate with the user terminal; receive from a network element a data packet to be transmitted to a user terminal; transmit the data packet to the user terminal; transmit the data packet to the other apparatus; receive a response from the user terminal, the response indicating the data packet was not received successfully and request the other apparatus to transmit the data packet to the user terminal.
  • an apparatus in a communication system configured to communicate with a user terminal
  • the apparatus comprising: at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform: control communication with another apparatus configured to communicate with the user terminal; receive from the other apparatus a data packet to be transmitted to a user terminal; receive an indication that the data packet is to be transmitted to the user terminal and based on the indication, transmit the data packet to the user terminal.
  • a method in an apparatus in a communication system comprising: controlling communication with another apparatus configured to communicate with the user terminal; receiving from a network element a data packet to be transmitted to a user terminal; transmitting the data packet to the user terminal; transmitting the data packet to the other apparatus; receiving a response from the user terminal, the response indicating the data packet was not received successfully and requesting the other apparatus to transmit the data packet to the user terminal.
  • a method in an apparatus in a communication system comprising: controlling communication with another apparatus configured to communicate with the user terminal; receiving from the other apparatus a data packet to be transmitted to a user terminal; receiving an indication that the data packet is to be transmitted to the user terminal and based on the indication, transmitting the data packet to the user terminal.
  • Figure 1 illustrates an example of a communication system
  • FIGS. 2, 3 and 4 are flowcharts illustrating embodiments of the invention.
  • FIGS 5A, 5B and 5C illustrate some embodiments of the invention.
  • FIGS 6 and 7 illustrate simplified examples of apparatuses applying some embodiments of the invention.
  • Embodiments are applicable to any base station, communication network element, user equipment (UE], user terminal (UT], server, corresponding component, and/or to any communication system or any combination of different communication systems that support required functionalities.
  • UE user equipment
  • UT user terminal
  • server server
  • corresponding component and/or to any communication system or any combination of different communication systems that support required functionalities.
  • UMTS universal mobile telecommunications system
  • LTE long term evolution
  • LTE- A long term evolution advanced
  • NR New Radio
  • WiMAX Wireless Local Area Network
  • PCS personal communications services
  • UWB ultra-wideband
  • Fig. 1 illustrates an example of a communication system where some embodiments of the invention may be applied.
  • the example of Fig. 1 follows 5G terminology, but the embodiments of the invention are not limited to 5G but may be applied also in other systems supporting dual or multi-connectivity.
  • 5G system is currently being developed.
  • the first 5G NR specifications have been released in June, 2018. It is likely to use multiple input - multiple output (MIMO] antennas, many more base stations or nodes than the LTE (a so- called small cell concept], including macro sites operating in co-operation with smaller stations and perhaps also employing a variety of radio technologies for better coverage and enhanced data rates.
  • MIMO multiple input - multiple output
  • 5G will likely be comprised of more than one radio interface (RI] configuration, each optimized for certain use cases and/or spectrum.
  • RI radio interface
  • 5G mobile communications will cater to different service class with a wider range of use cases and related applications including video streaming, augmented reality, different ways of data sharing and various forms of machine type applications, including vehicular safety, different sensors and real time control.
  • 5G is expected to have multiple radio interfaces, namely below 6GHz, cmWave and mmWave, and also can be integrated with existing legacy radio access technologies, such as the LTE. Integration with the LTE may be implemented, at least in the early phase, as a system, where macro coverage is provided by the LTE and 5G radio interface access comes from small cells by aggregation to the LTE. In other words, 5G is planned to support both inter-RAT operability (such as LTE-5G] and inter-RI operability (inter-radio interface operability, such as below 6GHz - cmWave, below 6GHz - cmWave - mmWave).
  • inter-RAT operability such as LTE-5G
  • inter-RI operability inter-radio interface operability, such as below 6GHz - cmWave, below 6GHz - cmWave - mmWave.
  • One of the concepts considered to be used in 5G networks is network slicing in which multiple independent and dedicated virtual sub-networks (net
  • a user terminal 100 is simultaneously connected 102, 104 to two base stations 106, 108.
  • the base stations may be, for instance, a macro cell 106 and a small cell 108.
  • the small cell 108 has its own baseband, i.e. it is not a remote radio head of the macro base station 106.
  • the base stations are connected 110 to a network element 112.
  • the base stations may be connected to each other through an interface 118, which may be an Xn/X2 interface.
  • the base stations 106, 108 comprise logical layers Packet Data Convergence Protocol PDCP, Radio Link Control Layer RLC, Media Access Control MAC and physical layer PHY.
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control Layer
  • MAC Media Access Control MAC
  • User terminal comprises similar logical layers as the base stations, but they are not shown in Fig. 1, for simplicity.
  • Dual connectivity as standardized by 3GPP in LTE Release 12/13, extends the LTE-Advanced Carrier Aggregation (CA] functionality to allow a user terminal to simultaneously receive/send data from two different eNBs. So far DC has been proposed as a solution to boost the throughput performance, using data split at PDCP layer.
  • CA LTE-Advanced Carrier Aggregation
  • NR new radio
  • MC multi-connectivity
  • URLLC Ultra Reliable Low Latency Communication
  • NR DC/MC is built on top of LTE DC.
  • a user terminal is connected to one Master gNB (MgNB] and one Secondary (SgNB].
  • MgNB Master Cell Group
  • SgNB Secondary Cell Group
  • MCG denotes a group of serving cells associated with the MgNB, comprising of the Primary Cell (PCell] and optionally one or more Secondary Cells (SCells].
  • Secondary Cell Group (SCG] denotes a group of serving cells associated with the SgNB, comprising of PSCell (Primary SCell] and optionally one or more Scells.
  • At least one cell in SCG has a configured uplink (UL] component carrier (CC] and one of them, named PSCell, is configured with PUCCH (Physical Uplink Common Control Channel] resources.
  • UL uplink
  • CC component carrier
  • PSCell Physical Uplink Common Control Channel
  • FIG. 1 illustrates an example of data duplication in NR DC/MC.
  • the gNB towards which the traffic is terminated from the core network and which is in control of the PDCP duplication is called the PDCP anchor node, whereas any other gNB serving the duplicated PDCP packets for a given UE may be termed as the PDCP duplicating node.
  • base station 106 is the anchor node and base station 108 the duplicating node.
  • a packet When a packet arrives at the PDCP-anchor gNB 106, it may be duplicated at the PDCP layer and, if so, the duplicated packet is forwarded to one or more PDCP duplicating gNB node(s] 108 over the Xn network interface ⁇ 118.
  • the same data packet i.e. PDCP Packet Data Unit PDU with a given sequence number, SN] is then independently transmitted to the same UE through multiple links (the anchor gNB and the duplicating gNBs ⁇ .
  • the RLC/MAC/PHY in the MgNB and SgNB operate independently, and thus also RRM functionalities such as scheduling, link adaptation and hybrid ARQ operation are conducted separately within those base station nodes.
  • DC with PDCP data duplication therefore offers additional redundancy, thereby lowering the error probability, as errors in the two transmission paths (i.e. from the MgNB and SgNB towards the UE] are typically uncorrelated.
  • This system also has some drawbacks.
  • the cost of the solution is the usage of radio resources at two gNBs for the same PDUs of one user.
  • the additional redundancy may cause additional scheduling queuing delays at the gNBs of the system as the number of transmitted packets increases.
  • a scheduling approach is proposed, where a conditional scheduling of duplicated packets is enforced.
  • Fig. 2 is a flowchart illustrating an embodiment of the invention.
  • Fig. 2 illustrates an example of the operation of an apparatus or a network element such as base station (gNB] or a part of a base station, the apparatus being configured to communicate with a user terminal
  • the steps of the flowchart may also be in different order than illustrated in Fig. 3.
  • the apparatus may be an anchor gNB or a base station 106, for example.
  • the apparatus is configured to control communication with another apparatus configured to communicate with the user terminal.
  • the other apparatus may be the base station 108 and the communication is realised using Xn/X2 interface.
  • the apparatus is configured to receive from a network element a data packet (PDCP PDU ⁇ to be transmitted to a user terminal 100.
  • PDCP PDU ⁇ data packet
  • step 206 the apparatus is configured to transmit the data packet to the user terminal.
  • the apparatus is configured to duplicate the data packet and transmit the data packet to the other apparatus.
  • the Xn/X2 interface is utilised in the transmission.
  • the transmission comprises an indication of "conditional scheduling”, i.e. the other apparatus is not to transmit the packet without an explicit request, or if other conditions are fulfilled.
  • the apparatus is configured to receive a response from the user terminal, the response indicating the data packet was not received successfully.
  • the response is Hybrid Automatic Repeat Request negative Acknowledgment (HARQ Negative-ACK ⁇ associated with a PDCP PDU (mapped to a PDCP PDU Sequence Number ⁇ .
  • the apparatus is configured to request the other apparatus to transmit the data packet to the user terminal.
  • the base station 106 may send immediate explicit request to the base station 108 to immediately schedule the given PDCP PDU.
  • step 214 also the apparatus is configured to transmit the data packet to the user terminal.
  • Fig. 3 is a flowchart illustrating an embodiment of the invention.
  • the figure illustrates another example of the operation of an apparatus or a network element such as base station or a part of a base station.
  • the steps of the flowchart may also be in different order than illustrated in Fig. 3.
  • the apparatus is configured to receive from a network element a data packet (PDCP PDU] to be transmitted to a user terminal 100.
  • PDCP PDU data packet
  • step 304 the apparatus is configured to transmit the data packet to the user terminal. These steps correspond to the steps 204 and 206 of Fig. 2.
  • the apparatus is configured to receive a response from the user terminal, the response indicating the data packet was not received successfully.
  • the response is Hybrid Automatic Repeat Request negative Acknowledgment (HARQ Negative-ACK] associated with a PDCP PDU (mapped to a PDCP PDU Sequence Number ⁇ .
  • HARQ Negative-ACK Hybrid Automatic Repeat Request negative Acknowledgment
  • the apparatus is configured to duplicate the data packet and transmit the data packet to the other apparatus.
  • the Xn/X2 interface is utilised in the transmission. The transmission comprises an indication to the other apparatus to transmit the packet immediately.
  • the apparatus may configured to transmit the data packet to the user terminal (not shown in the flow chart ⁇ .
  • the procedure outlined in Fig. 3 is simpler as compared to the procedure of Fig. 2 and will work well when assuming a low-latency Xn/X2 interface to quickly forward the failing PDU(s] to the base station 108.
  • the procedure of Fig. 2 may be preferred as it achieves better performance at the cost of additional inter-node interface capacity usage.
  • Fig. 4 is a flowchart illustrating an embodiment of the invention.
  • the Fig. illustrates an example of the operation of an apparatus or a network element such as base station (gNB) or a part of a base station, the apparatus being configured to communicate with a user terminal
  • the steps of the flowchart may also be in different order than illustrated in Fig. 3.
  • the apparatus may be a duplicating gNB or a base station 108, for example.
  • the apparatus is configured to control communication with another apparatus configured to communicate with the user terminal.
  • the other apparatus may be the anchor gNB or base station 106 and the communication is realised using Xn/X2 interface.
  • the apparatus is configured to receive from the other apparatus a data packet (PDCP PDU] to be transmitted to a user terminal.
  • the data packet may be stored in a buffer.
  • the buffer may comprise also other data packets received earlier from the other apparatus and which have not yet transmitted to the user terminal.
  • step 406 the apparatus is configured to receive an indication that the data packet is to be transmitted to the user terminal.
  • the indication is received from the other apparatus in connection with the data packet.
  • the indication is received from the other apparatus after receiving the data packet.
  • the indication is received from the user terminal.
  • the apparatus is configured to, based on the indication, transmit the data packet to the user terminal.
  • the data packet is sent right after the reception of the packet from the other apparatus.
  • the other apparatus may be assumed that the other apparatus has received a NACK regarding the data packet from the user terminal.
  • the user terminal may be configured to transmit the HARQ NACK to both the anchor and duplicate gNBs.
  • both the anchor and duplicate gNBs may be configured to initiate the scheduling of the data packet or buffered data packets for that user terminal.
  • the duplicate gNB cannot necessarily map the PHY transmission (of a different cell] to a given data packet PDCP PDU and therefore it is not capable to identify the failing data packet without further assistance, it may be configured to send any buffered data packets to the user terminal.
  • the number of buffered data packets will be very limited, if not just one.
  • Figs. 5A, 5B and 5C illustrate some embodiments of communication between an anchor gNB 106, duplicate gNB 108 and user terminal UT 100.
  • the anchor gNB 106 is configured to transmit 500 a data packet (PDCP PDU] to the user terminal 100.
  • PDCP PDU data packet
  • the anchor gNB 106 is configured to duplicate the PDU and forward 502 them timely to the duplicate gNB along with a message that the PDU is to be sent to the user terminal upon a request from the anchor gNB.
  • the duplicate gNB will buffer the PDU associated to the "conditional scheduling” indication without immediate transmitting them.
  • the anchor gNB may provide an indication to the duplicate gNB to discard the PDU buffered at the duplicate gNB after receiving from the user terminal an indication (PHY ACK] of the successful reception of the PDU.
  • the duplicate gNB may discard the PDU after a timer is expired, whose length is set based on the delay budget available for the service.
  • the anchor gNB may be configured to send immediate explicit request 506 to the duplicate gNB to immediately schedule the given PDU.
  • the anchor gNB 106 and duplicate gNB 108 will then proceed with their transmissions 508 or retransmissions 510 of the PDU to the user terminal.
  • the anchor gNB 106 is configured to transmit 520 a data packet (PDCP PDU] to the user terminal 100.
  • PDCP PDU data packet
  • the anchor gNB may be configured to duplicate the PDU and transmit 524 it to the duplicate gNB with an immediate explicit request to immediately schedule the given PDU.
  • the anchor gNB 106 and duplicate gNB 108 will then proceed with their transmissions 526 or retransmissions 528 of the PDU to the user terminal.
  • the anchor gNB 106 is configured to transmit 530 a data packet (PDCP PDU] to the user terminal 100.
  • PDCP PDU data packet
  • the anchor gNB 106 is configured to duplicate the PDU and forward 532 them to the duplicate gNB along with a message that the PDU is to be sent to the user terminal upon a request from the anchor gNB.
  • the duplicate gNB will buffer the PDU associated to the "conditional scheduling” indication without immediate transmitting them.
  • the user terminal is configured to transmit the indication 534A, 534B the successfulness of the reception of the PDU to both the anchor and duplicate gNBs.
  • the anchor gNB 106 and duplicate gNB 108 will then proceed with their transmissions 538 or retransmissions 536 of the PDU to the user terminal.
  • MgNB may act as an anchor NB and SgNB as a duplicate GnB.
  • the anchor NB may be SgNB and the supplicate NB may be MgNB.
  • the transmission of a PDCP PDU takes place only by the anchor gNB unless the user terminal is unable to receive that PDC correctly, in which case it will be resent via the anchor gNB (i.e. HARQ retransmission] and a copy of the PDU will be sent urgently via the duplicate gNB (as a first transmission ⁇ .
  • the delay budget e.g. 1 ms] of a URLLC user terminal
  • a probability P of successful delivery may be defined as follows:
  • Ps Probability of successful delivery after two transmissions from anchor gNB and one transmission from 1st from duplicate gNB
  • P e 2 Block error probability after a transmission from duplicate gNB.
  • different settings of the Block Error Rate, BLER, targets may be chosen for the first transmissions at the anchor gNB and duplicate gNB in order to assure that the reliability target of the URLLC user terminal is met:
  • a larger number of potential transmissions for a given PDU may be accommodated, for example by using - when feasible - a number of duplicating nodes larger than one.
  • the number of duplicating nodes and the BLER target for the first transmission at the anchor gNB or at any duplicated node may be optimized based on the latency budget and reliability figure.
  • One approach could be to select a larger BLER target on the anchor gNB (e.g. 10% ⁇ whereas using a lower value for the selective duplicated packets on the duplicate gNB (e.g. 1% or 0.1% ⁇ .
  • Fig. 6 illustrates an embodiment.
  • the figure illustrates a simplified example of an apparatus applying embodiments of the invention.
  • the apparatus may be a base station or a part of a base station.
  • the apparatus may be an anchor gNB and in some embodiments a duplicate gNB.
  • the apparatus is depicted herein as an example illustrating some embodiments. It is apparent to a person skilled in the art that the apparatus may also comprise other functions and/or structures and not all described functions and structures are required. Although the apparatus has been depicted as one entity, different modules and memory may be implemented in one or more physical or logical entities.
  • the apparatus of the example includes a control circuitry 600 configured to control at least part of the operation of the apparatus.
  • the apparatus may comprise a memory 602 for storing data. Furthermore the memory may store software 604 executable by the control circuitry 600. The memory may be integrated in the control circuitry.
  • the apparatus comprises a transceiver 606.
  • the transceiver is operationally connected to the control circuitry 600. It may be connected to an antenna arrangement (not shown ⁇ .
  • the apparatus may further comprise interface circuitry 608 configured to connect the apparatus to other devices and network elements of communication system, for example to other corresponding apparatuses and network elements.
  • the interface may provide a wired or wireless connection to the communication network.
  • the software 604 may comprise a computer program comprising program code means adapted to cause the control circuitry 600 of the apparatus to control communication with another apparatus configured to communicate with the user terminal; receive from a network element a data packet to be transmitted to a user terminal; transmit the data packet to the user terminal; transmit the data packet to the other apparatus; receive a response from the user terminal, the response indicating the data packet was not received successfully; and request the other apparatus to transmit the data packet to the user terminal.
  • the software 604 may comprise a computer program comprising program code means adapted to cause the control circuitry 600 of the apparatus to control communication with another apparatus configured to communicate with the user terminal; receive from the other apparatus a data packet to be transmitted to a user terminal; receive an indication that the data packet is to be transmitted to the user terminal; and based on the indication, transmit the data packet to the user terminal.
  • the apparatus of Fig. 7 may comprise a remote control unit RCU 700, such as a host computer or a server computer, operatively coupled (e.g. via a wireless or wired network] to a remote radio head RRH 702 located in the base station.
  • RCU 700 remote control unit
  • the apparatus of Fig. 7, utilizing such shared architecture may comprise a remote control unit RCU 700, such as a host computer or a server computer, operatively coupled (e.g. via a wireless or wired network] to a remote radio head RRH 702 located in the base station.
  • RCU 700 such as a host computer or a server computer
  • the execution of at least some of the described processes may be shared among the RRH 702 and the RCU 700.
  • the RCU 700 may generate a virtual network through which the RCU 700 communicates with the RRH 702.
  • virtual networking may involve a process of combining hardware and software network resources and network functionality into a single, software-based administrative entity, a virtual network.
  • Network virtualization may involve platform virtualization, often combined with resource virtualization.
  • Network virtualization may be categorized as external virtual networking which combines many networks, or parts of networks, into the server computer or the host computer (e.g. to the RCU]. External network virtualization is targeted to optimized network sharing. Another category is internal virtual networking which provides network-like functionality to the software containers on a single system. Virtual networking may also be used for testing the terminal device.
  • the virtual network may provide flexible distribution of operations between the RRH and the RCU.
  • any digital signal processing task may be performed in either the RRH or the RCU and the boundary where the responsibility is shifted between the RRH and the RCU may be selected according to implementation.
  • the apparatuses or controllers able to perform the above-described steps may be implemented as an electronic digital computer, which may comprise a working memory (RAM], a central processing unit (CPU], and a system clock.
  • the CPU may comprise a set of registers, an arithmetic logic unit, and a controller.
  • the controller is controlled by a sequence of program instructions transferred to the CPU from the RAM.
  • the controller may contain a number of microinstructions for basic operations.
  • the implementation of microinstructions may vary depending on the CPU design.
  • the program instructions may be coded by a programming language, which may be a high-level programming language, such as C, Java, etc., or a low-level programming language, such as a machine language, or an assembler.
  • the electronic digital computer may also have an operating system, which may provide system services to a computer program written with the program instructions.
  • circuitry refers to all of the following: (a] hardware-only circuit implementations, such as implementations in only analog and/or digital circuitry, and (b] combinations of circuits and software (and/or firmware], such as (as applicable]: (i] a combination of processors] or (ii] portions of processor(s]/software including digital signal processors], software, and memory(ies] that work together to cause an apparatus to perform various functions, and (c] circuits, such as a microprocessors] or a portion of a microprocessors], that require software or firmware for operation, even if the software or firmware is not physically present.
  • circuitry' applies to all uses of this term in this application.
  • the term 'circuitry' would also cover an implementation of merely a processor (or multiple processors] or a portion of a processor and its (or their] accompanying software and/or firmware.
  • the term 'circuitry' would also cover, for example and if applicable to the particular element, a baseband integrated circuit or applications processor integrated circuit for a mobile phone or a similar integrated circuit in a server, a cellular network device, or another network device.
  • An embodiment provides a computer program embodied on a distribution medium, comprising program instructions which, when loaded into an electronic apparatus, are configured to control the apparatus to execute the embodiments described above.
  • the computer program may be in source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, which may be any entity or device capable of carrying the program.
  • carrier include a record medium, computer memory, read-only memory, and a software distribution package, for example.
  • the computer program may be executed in a single electronic digital computer or it may be distributed amongst a number of computers.
  • the apparatus may also be implemented as one or more integrated circuits, such as application-specific integrated circuits ASIC.
  • Other hardware embodiments are also feasible, such as a circuit built of separate logic components.
  • a hybrid of these different implementations is also feasible.

Landscapes

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

Abstract

La présente invention propose une solution pour des communications fiables dans un appareil d'un système de communication. La solution consiste à : contrôler (202) une communication avec un autre appareil configuré pour communiquer avec le terminal utilisateur ; recevoir (204), d'un élément de réseau, un paquet de données devant être transmis à un terminal utilisateur ; transmettre (206) le paquet de données au terminal utilisateur ; transmettre (208) le paquet de données à l'autre appareil ; recevoir (210) une réponse du terminal utilisateur, la réponse indiquant que le paquet de données n'a pas été reçu avec succès, et demander (212) à l'autre appareil de transmettre le paquet de données au terminal utilisateur.
PCT/EP2018/067415 2018-06-28 2018-06-28 Appareil et procédé pour des communications fiables en connectivité multiple WO2020001773A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2018/067415 WO2020001773A1 (fr) 2018-06-28 2018-06-28 Appareil et procédé pour des communications fiables en connectivité multiple

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2018/067415 WO2020001773A1 (fr) 2018-06-28 2018-06-28 Appareil et procédé pour des communications fiables en connectivité multiple

Publications (1)

Publication Number Publication Date
WO2020001773A1 true WO2020001773A1 (fr) 2020-01-02

Family

ID=62837896

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2018/067415 WO2020001773A1 (fr) 2018-06-28 2018-06-28 Appareil et procédé pour des communications fiables en connectivité multiple

Country Status (1)

Country Link
WO (1) WO2020001773A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022197312A1 (fr) * 2021-03-19 2022-09-22 Nokia Technologies Oy Adaptation de liaison pour connexions multiples
US11979237B2 (en) 2019-05-02 2024-05-07 Nokia Technologies Oy Methods of packet combining for packet duplication

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017182927A1 (fr) * 2016-04-19 2017-10-26 Nokia Technologies Oy Dversité de retransmission à connectivité double/multiple par porteuse divisée
WO2017220855A1 (fr) * 2016-06-22 2017-12-28 Nokia Technologies Oy Procédé et appareil pour réaliser une duplication de paquets dans un scénario à connectivité multiple

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017182927A1 (fr) * 2016-04-19 2017-10-26 Nokia Technologies Oy Dversité de retransmission à connectivité double/multiple par porteuse divisée
WO2017220855A1 (fr) * 2016-06-22 2017-12-28 Nokia Technologies Oy Procédé et appareil pour réaliser une duplication de paquets dans un scénario à connectivité multiple

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
MEDIATEK INC: "UP architecture 3: Alternatives 3C & 3D", vol. RAN WG2, no. Ljubljana, Slovenia; 20131007 - 20131011, 28 September 2013 (2013-09-28), XP050719266, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG2_RL2/TSGR2_83bis/Docs/> [retrieved on 20130928] *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11979237B2 (en) 2019-05-02 2024-05-07 Nokia Technologies Oy Methods of packet combining for packet duplication
WO2022197312A1 (fr) * 2021-03-19 2022-09-22 Nokia Technologies Oy Adaptation de liaison pour connexions multiples

Similar Documents

Publication Publication Date Title
US11159271B2 (en) Protocol layer packet coding for transmitter/receiver buffer optimization
US20230412322A1 (en) Apparatus and method for reliable communication in multi-connectivity
US8295159B2 (en) Timer poll retransmission expiry in a wireless communication system
CN110741722A (zh) 用于多连接通信中的分组复制的控制机制
US20190200273A1 (en) Flushing PDCP Packets To Reduce Network Load In Multi-Connectivity Scenarios
US11147122B2 (en) Data forwarding support
WO2018019498A1 (fr) Atténuation des erreurs de correspondance de débit dans un réseau sans fil
EP3634076B1 (fr) Procédé et dispositif de traitement de données
WO2020093915A1 (fr) Gestion d&#39;unités de données de protocole de protocole de convergence de données par paquets (pdcp)
US11729685B2 (en) Method and device for transmitting data in case of PDCP version change in wireless communication system
EP3777414B1 (fr) Politique d&#39;ordonnancement optimisée d&#39;urllc de connectivité multi-noeuds avec duplication de données
WO2023000275A1 (fr) Procédé, dispositif et support lisible par ordinateur pour des communications
WO2020001773A1 (fr) Appareil et procédé pour des communications fiables en connectivité multiple
EP3714566A1 (fr) Transmission d&#39;informations supplémentaires
US11336416B2 (en) Apparatus and method for communication
WO2021116082A1 (fr) Système de communication
CN111357223B (zh) 一种通信的方法、装置和计算机可读存储介质
WO2020151811A1 (fr) Appareil de communication, procédé et programme d&#39;ordinateur
US20240049076A1 (en) Method and apparatus for performing conditional pscell addition and change continuously in wireless communication system
EP4211836B1 (fr) Transmission par rafales de paquets de données avec rétroaction
WO2023005872A1 (fr) Procédé de communication et appareil de communication
WO2023174375A1 (fr) Procédé et appareil utilisés dans un nœud pour une communication sans fil
WO2021008672A1 (fr) Appareil, procédé et programme informatique pour la transmission fiable de commande
WO2018232627A1 (fr) Appareil de communication, procédé et programme informatique

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: 18737551

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: 18737551

Country of ref document: EP

Kind code of ref document: A1