WO2024060102A1 - Procédé, dispositif et support de stockage informatique de communication - Google Patents

Procédé, dispositif et support de stockage informatique de communication Download PDF

Info

Publication number
WO2024060102A1
WO2024060102A1 PCT/CN2022/120370 CN2022120370W WO2024060102A1 WO 2024060102 A1 WO2024060102 A1 WO 2024060102A1 CN 2022120370 W CN2022120370 W CN 2022120370W WO 2024060102 A1 WO2024060102 A1 WO 2024060102A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
indication
rlc
transmitting
entity
Prior art date
Application number
PCT/CN2022/120370
Other languages
English (en)
Inventor
Da Wang
Lin Liang
Gang Wang
Original Assignee
Nec Corporation
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 Nec Corporation filed Critical Nec Corporation
Priority to PCT/CN2022/120370 priority Critical patent/WO2024060102A1/fr
Publication of WO2024060102A1 publication Critical patent/WO2024060102A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution

Definitions

  • Embodiments of the present disclosure generally relate to the field of telecommunication, and in particular, to methods, devices and computer storage media of communication for multipath with relay.
  • MP multipath
  • UE remote user equipment
  • the direct path means that the remote UE is connected to the network directly.
  • the indirect path means that the remote UE is connected to the network via a relay UE using PC5 interface or a non-standardized UE-UE interconnection.
  • the support of MP with relay has a potential to improve reliability or robustness as well as throughput.
  • a solution of MP with relay in user plane aspects is still incomplete and needs to be further developed.
  • embodiments of the present disclosure provide methods, devices and computer storage media of communication for MP with relay.
  • a method of communication comprises: receiving, at a first terminal device, an indication indicating whether a packet duplication is activated or deactivated for a split radio bearer for a direct path between the first terminal device and a network device and an indirect path between the first terminal device and the network device via a second terminal device; and performing, based on the indication, activation or deactivation of the packet duplication for the split radio bearer.
  • a method of communication comprises: transmitting, at a network device, an indication indicating whether a packet duplication is activated or deactivated for a split radio bearer for a direct path between a first terminal device and the network device and an indirect path between the first terminal device and the network device via a second terminal device.
  • a method of communication comprises: receiving, at a second terminal device and from a network device, a fifth indication indicating whether a packet duplication is activated or deactivated for a split radio bearer for a direct path between a first terminal device and the network device and an indirect path between the first terminal device and the network device via the second terminal device; and transmitting, to the first terminal device, a second indication indicating whether the packet duplication is activated or deactivated for the split radio bearer.
  • a device of communication comprising a processor configured to cause the device to perform the method according to any of the first to third aspects of the present disclosure.
  • a computer readable medium having instructions stored thereon.
  • the instructions when executed on at least one processor, cause the at least one processor to perform the method according to any of the first to third aspects of the present disclosure.
  • FIG. 1 illustrates an example communication network in which some embodiments of the present disclosure can be implemented
  • FIG. 2 illustrates a diagram illustrating example bearer types for which some embodiments of the present disclosure can be implemented
  • FIG. 3A illustrates an example protocol stack of a MP split data radio bearer (DRB) in which some embodiments of the present disclosure can be implemented;
  • DRB MP split data radio bearer
  • FIG. 3B illustrates an example protocol stack of a MP split signaling radio bearer (SRB) in which some embodiments of the present disclosure can be implemented;
  • SRB MP split signaling radio bearer
  • FIG. 3C illustrates another example protocol stack of a MP split DRB in which some embodiments of the present disclosure can be implemented
  • FIG. 3D illustrates another example protocol stack of a MP split SRB in which some embodiments of the present disclosure can be implemented
  • FIG. 4A illustrates a schematic diagram illustrating a process of communication according to embodiments of the present disclosure
  • FIG. 4B illustrates a schematic diagram illustrating another process of communication according to embodiments of the present disclosure
  • FIG. 5 illustrates an example method of communication implemented at a first terminal device in accordance with some embodiments of the present disclosure
  • FIG. 6 illustrates an example method of communication implemented at a network device in accordance with some embodiments of the present disclosure
  • FIG. 7 illustrates an example method of communication implemented at a second terminal device in accordance with some embodiments of the present disclosure.
  • FIG. 8 is a simplified block diagram of a device that is suitable for implementing embodiments of the present disclosure.
  • terminal device refers to any device having wireless or wired communication capabilities.
  • the terminal device include, but not limited to, user equipment (UE) , personal computers, desktops, mobile phones, cellular phones, smart phones, personal digital assistants (PDAs) , portable computers, tablets, wearable devices, internet of things (IoT) devices, Ultra-reliable and Low Latency Communications (URLLC) devices, Internet of Everything (IoE) devices, machine type communication (MTC) devices, device on vehicle for V2X communication where X means pedestrian, vehicle, or infrastructure/network, devices for Integrated Access and Backhaul (IAB) , Space borne vehicles or Air borne vehicles in Non-terrestrial networks (NTN) including Satellites and High Altitude Platforms (HAPs) encompassing Unmanned Aircraft Systems (UAS) , eXtended Reality (XR) devices including different types of realities such as Augmented Reality (AR) , Mixed Reality (MR) and Virtual Reality (VR) , the unmanned aerial vehicle (UAV)
  • UE user equipment
  • the ‘terminal device’ can further has ‘multicast/broadcast’ feature, to support public safety and mission critical, V2X applications, transparent IPv4/IPv6 multicast delivery, IPTV, smart TV, radio services, software delivery over wireless, group communications and IoT applications. It may also incorporate one or multiple Subscriber Identity Module (SIM) as known as Multi-SIM.
  • SIM Subscriber Identity Module
  • the term “terminal device” can be used interchangeably with a UE, a mobile station, a subscriber station, a mobile terminal, a user terminal or a wireless device.
  • network device refers to a device which is capable of providing or hosting a cell or coverage where terminal devices can communicate.
  • a network device include, but not limited to, a Node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a next generation NodeB (gNB) , a transmission reception point (TRP) , a remote radio unit (RRU) , a radio head (RH) , a remote radio head (RRH) , an IAB node, a low power node such as a femto node, a pico node, a reconfigurable intelligent surface (RIS) , and the like.
  • NodeB Node B
  • eNodeB or eNB evolved NodeB
  • gNB next generation NodeB
  • TRP transmission reception point
  • RRU remote radio unit
  • RH radio head
  • RRH remote radio head
  • IAB node a low power node such as a fe
  • the terminal device or the network device may have Artificial intelligence (AI) or Machine learning capability. It generally includes a model which has been trained from numerous collected data for a specific function, and can be used to predict some information.
  • AI Artificial intelligence
  • Machine learning capability it generally includes a model which has been trained from numerous collected data for a specific function, and can be used to predict some information.
  • the terminal or the network device may work on several frequency ranges, e.g. FR1 (410 MHz to 7125 MHz) , FR2 (24.25GHz to 71GHz) , frequency band larger than 100GHz as well as Tera Hertz (THz) . It can further work on licensed/unlicensed/shared spectrum.
  • the terminal device may have more than one connection with the network devices under Multi-Radio Dual Connectivity (MR-DC) application scenario.
  • MR-DC Multi-Radio Dual Connectivity
  • the terminal device or the network device can work on full duplex, flexible duplex and cross division duplex modes.
  • test equipment e.g. signal generator, signal analyzer, spectrum analyzer, network analyzer, test terminal device, test network device, channel emulator.
  • the terminal device may be connected with a first network device and a second network device.
  • One of the first network device and the second network device may be a master node and the other one may be a secondary node.
  • the first network device and the second network device may use different radio access technologies (RATs) .
  • the first network device may be a first RAT device and the second network device may be a second RAT device.
  • the first RAT device is eNB and the second RAT device is gNB.
  • Information related with different RATs may be transmitted to the terminal device from at least one of the first network device or the second network device.
  • first information may be transmitted to the terminal device from the first network device and second information may be transmitted to the terminal device from the second network device directly or via the first network device.
  • information related with configuration for the terminal device configured by the second network device may be transmitted from the second network device via the first network device.
  • Information related with reconfiguration for the terminal device configured by the second network device may be transmitted to the terminal device from the second network device directly or via the first network device.
  • the singular forms ‘a’ , ‘an’ and ‘the’ are intended to include the plural forms as well, unless the context clearly indicates otherwise.
  • the term ‘includes’ and its variants are to be read as open terms that mean ‘includes, but is not limited to. ’
  • the term ‘based on’ is to be read as ‘at least in part based on. ’
  • the term ‘one embodiment’ and ‘an embodiment’ are to be read as ‘at least one embodiment. ’
  • the term ‘another embodiment’ is to be read as ‘at least one other embodiment. ’
  • the terms ‘first, ’ ‘second, ’ and the like may refer to different or same objects. Other definitions, explicit and implicit, may be included below.
  • values, procedures, or apparatus are referred to as ‘best, ’ ‘lowest, ’ ‘highest, ’ ‘minimum, ’ ‘maximum, ’ or the like. It will be appreciated that such descriptions are intended to indicate that a selection among many used functional alternatives can be made, and such selections need not be better, smaller, higher, or otherwise preferable to other selections.
  • direct path may be interchangeably used with “master cell group (MCG) ” or “direct transmission” or “direct path transmission” , “MCG transmission” or “Uu path” .
  • MCG master cell group
  • indirect path may be interchangeably used with “indirect transmission” , “indirect path transmission” , “PC5 path” , “sidelink path” or “relay path” .
  • packet duplication may be interchangeably used with “packet data convergence protocol (PDCP) duplication” .
  • a RLC entity for a sidelink interface may be interchangeably used with “a SL RLC entity” or “a PC5 RLC entity” .
  • a RLC entity for an air interface may be interchangeably used with “a Uu RLC entity” .
  • a first terminal device may refer to a terminal device functioning as remote UE
  • a second terminal device may refer to a terminal device functioning as relay UE
  • a MP relay solution may also be utilized to for UE aggregation where UE is connected to a network via a direct path and via another UE using a non-standardized UE-UE interconnection.
  • UE aggregation aims to provide applications requiring high uplink (UL) bitrates on 5G terminals, in cases when normal UEs are too limited by UL UE transmission power to achieve required bitrate, especially at the edge of a cell. Additionally, UE aggregation may improve reliability and stability and reduce delay of services as well. That is, if a channel condition of a terminal is deteriorating, another terminal may be used to make up for traffic performance unsteadiness caused by channel condition variation.
  • a network device transmits, via a direct path between a first terminal device (e.g., remote UE) and the network device or an indirect path between the first terminal device and the network device via a second terminal device (e.g., relay UE) , an indication indicating whether a packet duplication is activated or deactivated for a split radio bearer for the direct and indirect paths. Based on the indication, the first terminal device performs activation or deactivation of the packet duplication for the split radio bearer. In this way, a packet duplication of a MP split radio bearer may be dynamically controlled.
  • FIG. 1 illustrates a schematic diagram of an example communication network 100 in which some embodiments of the present disclosure can be implemented.
  • the communication network 100 may include a terminal device 110, a terminal device 120 and a network device 130.
  • the network device 130 may provide one or more cells (not shown) to serve one or more terminal devices.
  • the terminal device 110 and the terminal device 120 are served by the network device 130.
  • the terminal device 110 and the terminal device 120 may be served by the same cell of the network device 130. In some embodiments, the terminal device 110 and the terminal device 120 may be served by different intra-frequency cells of the network device 130. In some embodiments, the terminal device 110 and the terminal device 120 may be served by different inter-frequency cells of the network device 130.
  • the terminal device 110 may directly communicate with the network device 130 (i.e., via a direct path) .
  • the terminal device 110 may also communicate with the network device 130 via the terminal device 120 (i.e., via an indirect path) .
  • the terminal device 110 serves as remote UE, and the terminal device 120 serves as relay UE.
  • the terminal device 120 may directly communicate with the network device 130 (i.e., via a direct path) .
  • the terminal device 120 may also communicate with the network device 130 via the terminal device 110 (i.e., via an indirect path) .
  • the terminal device 120 serves as remote UE, and the terminal device 110 serves as relay UE.
  • the terminal device 110 is an example of remote UE and taking the terminal device 120 as an example of relay UE.
  • the network device 130 and any of the terminal device 110 and the terminal device 120 may communicate with each other via an air interface (e.g., Uu interface) , for example, via a wireless communication channel.
  • the wireless communication channel may comprise a physical uplink control channel (PUCCH) , a physical uplink shared channel (PUSCH) , a physical random-access channel (PRACH) , a physical downlink control channel (PDCCH) , a physical downlink shared channel (PDSCH) and a physical broadcast channel (PBCH) .
  • PUCCH physical uplink control channel
  • PUSCH physical uplink shared channel
  • PRACH physical random-access channel
  • PDCCH physical downlink control channel
  • PDSCH physical downlink shared channel
  • PBCH physical broadcast channel
  • any other suitable channels are also feasible.
  • the terminal device 110 may be connected with the terminal device 120 via a sidelink (SL) interface (for example, PC5 interface or the like) .
  • the terminal device 120 serves as a Layer-2 (L2) UE-to-Network (U2N) relay.
  • L2 Layer-2
  • U2N UE-to-Network
  • the terminal device 110 and the terminal device 120 may communicate with each other via a SL channel such as a physical sidelink shared channel (PSSCH) , a physical sidelink control channel (PSCCH) , a physical sidelink feedback channel (PSFCH) , a physical sidelink broadcast channel (PSBCH) or the like.
  • a PC5 connection may be established between the terminal device 110 and the second device 120.
  • the terminal device 110 may be connected with the terminal device 120 via an ideal UE-UE inter-connection or backhaul connection.
  • the communication network 100 may include any suitable number of network devices and/or terminal devices adapted for implementing implementations of the present disclosure.
  • the communications in the communication network 100 may conform to any suitable standards including, but not limited to, Global System for Mobile Communications (GSM) , Long Term Evolution (LTE) , LTE-Evolution, LTE-Advanced (LTE-A) , New Radio (NR) , Wideband Code Division Multiple Access (WCDMA) , Code Division Multiple Access (CDMA) , GSM EDGE Radio Access Network (GERAN) , Machine Type Communication (MTC) and the like.
  • GSM Global System for Mobile Communications
  • LTE Long Term Evolution
  • LTE-Evolution LTE-Advanced
  • NR New Radio
  • WCDMA Wideband Code Division Multiple Access
  • CDMA Code Division Multiple Access
  • GERAN GSM EDGE Radio Access Network
  • MTC Machine Type Communication
  • Examples of the communication protocols include, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, 5.5G, 5G-Advanced networks, or the sixth generation (6G) networks.
  • a direct bearer, an indirect bearer and a MP split bearer may be supported.
  • the direct bearer may refer to a radio bearer mapped to the direct path on an air interface (e.g., Uu interface) .
  • the indirect bearer may refer to a radio bearer mapped to the indirect path via relay UE.
  • the MP split bearer may refer to a radio bearer mapped to both of the direct path and the indirect path based on a split bearer framework. This will be detailed in connection with FIG. 2 below.
  • FIG. 2 illustrates a diagram 200 illustrating example bearer types for which some embodiments of the present disclosure can be implemented.
  • a Uu PDCP entity may communicate with a Uu radio link control (RLC) entity via a direct bearer, and thus a direct bearer may be formed.
  • RLC radio link control
  • a Uu PDCP entity may communicate with a sidelink relay adaptation protocol (SRAP) entity and a SL RLC entity, and thus an indirect bearer may be formed.
  • SRAP sidelink relay adaptation protocol
  • a Uu PDCP entity may communicate with a Uu RLC entity via a MP split bearer and also communicate with a SRAP entity and a SL RLC entity to form a MP split bearer.
  • FIG. 3A illustrates an example protocol stack 300A of a MP split DRB in which some embodiments of the present disclosure can be implemented.
  • remote UE and relay UE communicate with each other via a SL interface.
  • one PDCP entity at the remote UE is configured with one direct Uu RLC channel and one indirect PC5 RLC channel.
  • a PDCP entity delivers to a Uu RLC entity and a PC5 RLC entity with SRAP entity in the remote UE side.
  • a PDCP entity receives from a Uu RLC entity and a PC5 RLC entity with SRAP entity in the remote UE side.
  • FIG. 3B illustrates an example protocol stack 300B of a MP split SRB in which some embodiments of the present disclosure can be implemented.
  • remote UE and relay UE communicate with each other via a SL interface.
  • one PDCP entity at the remote UE is configured with one direct Uu RLC channel and one indirect PC5 RLC channel.
  • a PDCP entity delivers to a Uu RLC entity and a PC5 RLC entity with SRAP entity in the remote UE side.
  • a PDCP entity receives from a Uu RLC entity and a PC5 RLC entity with SRAP entity in the remote UE side.
  • FIG. 3C illustrates another example protocol stack 300C of a MP split DRB in which some embodiments of the present disclosure can be implemented.
  • remote UE and relay UE communicate with each other via an ideal UE-UE inter-connection.
  • one PDCP entity at the remote UE is configured with one direct Uu RLC channel and one indirect non-standard connection associated with the relay UE.
  • a PDCP entity delivers to a Uu RLC entity and a non-standard connection with the relay UE with SRAP entity in the remote UE side.
  • a PDCP entity receives from a Uu RLC entity and a non-standard connection associated with the relay UE with SRAP entity in the remote UE side.
  • FIG. 3D illustrates another example protocol stack 300D of a MP split SRB in which some embodiments of the present disclosure can be implemented.
  • remote UE and relay UE communicate with each other via an ideal UE-UE inter-connection.
  • one PDCP entity at the remote UE is configured with one direct Uu RLC channel and one indirect non-standard connection associated with the relay UE.
  • a PDCP entity delivers to a Uu RLC entity and a non-standard connection associated with the relay UE with SRAP entity in the remote UE side.
  • a PDCP entity receives from a Uu RLC entity and a non-standard connection associated with the relay UE with SRAP entity in the remote UE side.
  • Embodiments of the present disclosure provide a solution of communication for MP with relay in user plane aspects. Details of the solution will be described with reference to FIGs. 4A and 4B.
  • FIG. 4A illustrates a schematic diagram illustrating a process 400A of communication according to embodiments of the present disclosure.
  • the process 400A may involve the terminal device 110, the terminal device 120 and the network device 130 as illustrated in FIG. 1. It is assumed that the terminal device 110 serves as remote UE, the terminal device 120 serves as relay UE.
  • the network device 130 may transmit 410 an indication indicating whether a packet duplication is activated or deactivated for a split radio bearer for a direct path between the terminal device 110 and the network device 130 and an indirect path between the terminal device 110 and the network device 130 via the terminal device 120 (i.e. MP split radio bearer) .
  • the split radio bearer is one split DRB.
  • the network device 130 may transmit 411, via the direct path and to the terminal device 110, an indication (for convenience, also referred to as a first indication herein) indicating whether the packet duplication is activated or deactivated for the split radio bearer for the direct path and the indirect path.
  • the network device 130 may indicate to the terminal device 110 to activate or deactivate packet duplication for the MP split radio bearer via the direct path.
  • the network device 130 may transmit the first indication via a radio resource control (RRC) message, e.g., a RRCReconfiguration message or any other suitable messages.
  • RRC radio resource control
  • the network device 130 may transmit the first indication via a medium access control (MAC) control element (CE) . It is to be noted that any other suitable ways are also feasible.
  • MAC medium access control
  • the first indication may comprise an identity of the split radio bearer. In some embodiments, the first indication may indicate whether a packet duplication is activated or deactivated for one split radio bearer. In some embodiments, the first indication may further indicate whether each RLC entity associated with the MP split radio bearer is activated or deactivated.
  • the network device 130 may transmit 412, to the terminal device 120, an indication (for convenience, also referred to as a fifth indication herein) indicating whether the packet duplication is activated or deactivated for the split radio bearer for the direct path and the indirect path of the terminal device 110.
  • an indication for convenience, also referred to as a fifth indication herein
  • the network device 130 may transmit the fifth indication via a RRC message, e.g., a RRCReconfiguration message or any other suitable messages. In some embodiments, the network device 130 may transmit the fifth indication via a MAC CE. It is to be noted that any other suitable ways are also feasible.
  • the fifth indication may comprise an identity of the terminal device 110. In some embodiments, the fifth indication may comprise an identity of the split radio bearer. In some embodiments, the fifth indication may comprise both the identity of the terminal device 110 and the identity of the split radio bearer.
  • the fifth indication may indicate whether a packet duplication is activated or deactivated for one split radio bearer. In some embodiments, the fifth indication may further indicate whether each associated RLC entity is activated or deactivated.
  • the terminal device 120 may transmit 413, to the terminal device 110, a second indication indicating whether the packet duplication is activated or deactivated for the split radio bearer for the direct path and the indirect path.
  • the second indication may comprise an identity of the split radio bearer.
  • the terminal device 120 may transmit the second indication to the terminal device 110 via a RRC message. In some embodiments, the terminal device 120 may transmit the second indication to the terminal device 110 via a MAC CE. It is to be noted that any other suitable ways are also feasible.
  • the terminal device 110 Upon reception of the indication (e.g., the first indication or the second indication or both) indicating whether the packet duplication is activated or deactivated for the MP split radio bearer for the direct path and the indirect path, the terminal device 110 performs 420 activation or deactivation of the packet duplication for the MP split radio bearer.
  • the indication e.g., the first indication or the second indication or both
  • the terminal device 110 may transmit, to the network device 130 via the indirect path, a RRC message for recovery of the RLF or reporting failure of the direct path.
  • RLF radio link failure
  • the terminal device 110 may set the primary RLC entity to be a RLC entity associated with the indirect path (i.e. PC5 RLC entity) .
  • the PDCP entity of the MP split SRB may deliver the PDCP PDU of the RRC message to the PC5 RLC entity.
  • the terminal device 110 may transmit, to the network device 130 via the direct path, a RRC message for recovery of the RLF or reporting failure of the indirect path.
  • a RRC message for recovery of the RLF or reporting failure of the indirect path.
  • the terminal device 110 may set the primary RLC entity to be a RLC entity associated with the direct path (Uu RLC entity) .
  • the PDCP entity of the MP split SRB may deliver the PDCP PDU of the RRC message to the Uu RLC entity.
  • a PDCP entity may deliver redundant packets to a Uu RLC entity and a SL RLC entity with SRAP entity in a remote UE side. If successful delivery of a PDCP Data protocol data unit (PDU) is confirmed by one Uu RLC entity, the PDCP entity may indicate to the SL RLC entity to discard the duplicated PDCP Data PDU. However, a SL RLC entity at a relay UE is not aware of this information, and would continue the transmission of the packets, which results in radio resource waste.
  • PDU PDCP Data protocol data unit
  • FIG. 4B illustrates a schematic diagram illustrating another process 400B of communication according to embodiments of the present disclosure.
  • the process 400B may involve the terminal device 110, the terminal device 120 and the network device 130 as illustrated in FIG. 1. It is assumed that the terminal device 110 serves as remote UE, the terminal device 120 serves as relay UE.
  • a SL RLC entity of the terminal device 110 may receive 431, from an upper layer (e.g., PDCP entity) , an indication (for convenience, also referred to as a third indication herein) for discarding a RLC SDU. If neither the RLC SDU nor a segment of the RLC SDU has been submitted to lower layers, the SL RLC entity of the terminal device 110 may discard 432 the RLC SDU.
  • an upper layer e.g., PDCP entity
  • the SL RLC entity of the terminal device 110 may transmit 433, to a SL RLC entity of the terminal device 120, an indication (for convenience, also referred to as a fourth indication herein) for discarding the RLC SDU.
  • the fourth indication may be transmitted via a RLC control PDU.
  • the RLC control PDU may comprise serial number (SN) information of a set of RLC SDUs that is to be discarded or has been successfully delivered.
  • the terminal device 120 may discard 434 the RLC SDU. For example, if neither the RLC SDU nor a segment of the RLC SDU has been delivered to an upper layer, the SL RLC entity of the terminal device 120 may discard the RLC SDU. In some embodiments, the SL RLC entity of terminal device 120 may indicate 435 to the Uu RLC entity of the terminal device 120 to discard the RLC SDU. For example, if the RLC SDU or a segment of the RLC SDU has been delivered to the upper layer, the SL RLC entity of the terminal device 120 may transmit, to a Uu RLC entity of the terminal device 120, an indication (for convenience, also referred to a seventh indication herein) for discarding the RLC SDU.
  • an indication for convenience, also referred to a seventh indication herein
  • the Uu RLC entity of the terminal device 120 may discard 436 the RLC SDU upon reception of the indication from the SL RLC entity of the terminal device 120. For example, if neither the RLC SDU nor a segment of the RLC SDU has been submitted to lower layers, the Uu RLC entity of the terminal device 120 may discard the RLC SDU.
  • a SL RLC entity of a remote UE may indicate a SL RLC entity of a relay UE to discard packets which have been successfully delivered.
  • redundant data may not be transmitted over the indirect path.
  • the network device 130 may transmit 441, to the terminal device 120 (e.g., the Uu RLC entity of the terminal device 120) , an indication (for convenience, also referred to as a sixth indication herein) for discarding a RLC SDU.
  • the sixth indication may be transmitted by a RLC control PDU.
  • the RLC control PDU may comprise SN information of a set of RLC SDUs that is to be discarded or has been successfully delivered.
  • the network device 130 may transmit, as the sixth indication, an indication (e.g., the fifth indication) indicating deactivation of packet duplication for the split radio bearer in a MAC CE or a RRC message.
  • the Uu RLC entity of the terminal device 120 may discard 442 the RLC SDU. For example, if neither the RLC SDU nor a segment of the RLC SDU has been delivered to an upper layer, the Uu RLC entity of the terminal device 120 may discard the RLC SDU. In some embodiments, the Uu RLC entity of the terminal device 120 may indicate 443 to the SL RLC entity of the terminal device 120 to discard the SL RLC SDU.
  • the Uu RLC entity of the terminal device 120 may transmit, to the SL RLC entity of the terminal device 120, an indication (for convenience, also referred to as an eighth indication herein) for discarding the RLC SDU.
  • the SL RLC entity of the terminal device 120 may discard 444 the RLC SDU. For example, if neither the RLC SDU nor a segment of the RLC SDU has been submitted to lower layers, the SL RLC entity of the terminal device 120 may discard the RLC SDU.
  • a Uu RLC entity of a network may indicate a Uu RLC entity of a relay UE to discard packets which have been successfully delivered.
  • redundant data may also not be transmitted over the indirect path.
  • a remote UE may determine to transmit a SL MAC PDU. In this case, less flexibility may be caused.
  • Embodiments of the present disclosure provide a solution for handing the collision of SL and UL transmissions.
  • the terminal device 110 may perform the set of sidelink transmissions or the set of uplink transmissions based on priorities of the set of sidelink transmissions and the set of uplink transmissions.
  • the terminal device 110 may prioritize the set of sidelink transmissions over the set of uplink transmissions. In other words, the terminal device 110 may prioritize the SL MAC PDU for the set of SL transmissions.
  • the terminal device 110 may prioritize the set of uplink transmissions over the set of sidelink transmissions. In other words, the terminal device 110 may prioritize the UL MAC PDU for the set of UL transmissions.
  • the set of uplink transmissions may comprise a transmission over a set of logical channels and a set of MAC CEs
  • the set of sidelink transmissions comprises a transmission over a set of logical channels and a set of MAC CEs in a SL MAC PDU.
  • a network may control whether to activate or deactivate packet duplication for a MP split radio bearer dynamically.
  • embodiments of the present disclosure provide methods of communication implemented at a terminal device and a network device. These methods will be described below with reference to FIGs. 5 to 7.
  • FIG. 5 illustrates an example method 500 of communication implemented at a first terminal device in accordance with some embodiments of the present disclosure.
  • the method 500 may be performed at the terminal device 110 as shown in FIG. 1.
  • the method 500 will be described with reference to FIG. 1. It is to be understood that the method 500 may include additional blocks not shown and/or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard.
  • a first terminal device receives an indication indicating whether a packet duplication is activated or deactivated for a split radio bearer for a direct path between the terminal device 110 and the network device 130 and an indirect path between the terminal device 110 and the network device 130 via a second terminal device (e.g., the terminal device 120) .
  • the terminal device 110 may receive the indication via a MAC CE. In some embodiments, the terminal device 110 may receive the indication via a RRC message. In some embodiments, the indication may further indicate whether each associated RLC entity is activated or deactivated.
  • the terminal device 110 may receive, via the direct path from the network device 130, a first indication indicating whether the packet duplication is activated or deactivated for the split radio bearer for the direct path and the indirect path. In some embodiments, the terminal device 110 may receive, via the indirect path from the second terminal device 120, a second indication indicating whether the packet duplication is activated or deactivated for the split radio bearer for the direct path and the indirect path. In some embodiments, the second indication may comprise an identity of the split radio bearer.
  • the terminal device 110 performs, based on the indication, activation or deactivation of the packet duplication for the split radio bearer.
  • the terminal device 110 may receive, at a RLC entity for a sidelink interface from an upper layer of the terminal device 110, a third indication for discarding a RLC SDU. If neither the RLC SDU nor a segment of the RLC SDU has been submitted to lower layers, the terminal device 110 may discard the RLC SDU by the RLC entity for the sidelink interface. If the RLC SDU or a segment of the RLC SDU has been submitted to the lower layers, the terminal device 110 may transmit, to a RLC entity for a sidelink interface of the second terminal device, a fourth indication for discarding the RLC SDU.
  • the terminal device 110 may transmit the fourth indication via a RLC control PDU.
  • the RLC control PDU may comprise serial number information of a set of RLC SDUs that is to be discarded or has been successfully delivered.
  • the terminal device 110 may perform the set of sidelink transmissions or the set of uplink transmissions based on priorities of the set of sidelink transmissions and the set of uplink transmissions.
  • the terminal device 110 may prioritize the set of sidelink transmissions over the set of uplink transmissions.
  • the set of uplink transmissions may comprise a transmission over a set of logical channels and a set of MAC CEs
  • the set of sidelink transmissions may comprise a transmission over a set of logical channels and a set of MAC CEs in a sidelink MAC PDU.
  • FIG. 6 illustrates an example method 600 of communication implemented at a network device in accordance with some embodiments of the present disclosure.
  • the method 600 may be performed at the network device 130 as shown in FIG. 1.
  • the method 600 will be described with reference to FIG. 1. It is to be understood that the method 600 may include additional blocks not shown and/or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard.
  • the network device 130 transmits an indication indicating whether a packet duplication is activated or deactivated for a split radio bearer for a direct path between a first terminal device (e.g., the terminal device 110) and the network device 130 and an indirect path between the terminal device 110 and the network device 130 via a second terminal device (e.g., the terminal device 120) .
  • the network device 130 may transmit the indication via a MAC CE. In some embodiments, the network device 130 may transmit the indication via a RRC message. In some embodiments, the indication may further indicate whether each associated RLC entity is activated or deactivated.
  • the network device 130 may transmit, to the first terminal device via the direct path, a first indication indicating whether the packet duplication is activated or deactivated for the split radio bearer for the direct path and the indirect path. In some embodiments, the network device 130 may transmit to the second terminal device 120, a fifth indication indicating whether the packet duplication is activated or deactivated for the split radio bearer for the direct path and the indirect path of the terminal device 110.
  • the network device 130 may transmit, to the second terminal device 120, a sixth indication for discarding a RLC SDU.
  • the network device 130 may transmit the sixth indication via a RLC control PDU.
  • the RLC control PDU may comprise serial number information of a set of RLC SDUs that is to be discarded or has been successfully delivered.
  • the network device 130 may transmit, as the sixth indication, an indication (e.g., the fifth indication) indicating deactivation of packet duplication for the split radio bearer in a MAC CE or in a RRC message.
  • FIG. 7 illustrates an example method 700 of communication implemented at a second terminal device in accordance with some embodiments of the present disclosure.
  • the method 700 may be performed at the terminal device 120 as shown in FIG. 1.
  • the method 700 will be described with reference to FIG. 1. It is to be understood that the method 700 may include additional blocks not shown and/or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard.
  • a second terminal device receives, from the network device 130, a fifth indication indicating whether a packet duplication is activated or deactivated for a split radio bearer for a direct path between the terminal device 120 and the network device 130 and an indirect path between the terminal device 120 and the network device 130 via the terminal device 120.
  • the terminal device 120 transmits, to the terminal device 110, a second indication indicating whether the packet duplication is activated or deactivated for the split radio bearer.
  • the terminal device 120 may receive the fifth indication via a MAC CE. In some embodiments, the terminal device 120 may receive the fifth indication via a RRC message.
  • the fifth indication comprises at least one of an identity of the terminal device 110 or an identity of the split radio bearer.
  • the terminal device 120 may transmit the second indication via a MAC CE. In some embodiments, the terminal device 120 may transmit the second indication via a RRC message.
  • the second indication may comprise an identity of the split radio bearer.
  • At least one of the fifth indication or the second indication may further indicate whether each associated RLC entity is activated or deactivated.
  • the terminal device 120 may receive, by a RLC entity for a sidelink interface of the terminal device 120 and from a RLC entity for a sidelink interface of the terminal device 110, a fourth indication for discarding a RLC SDU. If neither the RLC SDU nor a segment of the RLC SDU has been delivered to an upper layer, the terminal device 120 may discard the RLC SDU by the RLC entity for the sidelink interface of the terminal device 120. If the RLC SDU or a segment of the RLC SDU has been delivered to the upper layer, the terminal device 120 may transmit, from the RLC entity for the sidelink interface of the terminal device 120 to a RLC entity for an air interface of the terminal device 120, a seventh indication for discarding the RLC SDU. If neither the RLC SDU nor a segment of the RLC SDU has been submitted to lower layers by the RLC entity for the air interface of the terminal device 120, the terminal device 120 may discard the RLC SDU by the RLC entity for the air interface.
  • the terminal device 120 may receive the fourth indication via a RLC control PDU.
  • the terminal device 120 may receive, from the network device 130, a sixth indication for discarding a RLC SDU. If neither the RLC SDU nor a segment of the RLC SDU has been delivered to an upper layer, the terminal device 120 may discard the RLC SDU by a RLC entity for an air interface of the terminal device 120. If the RLC SDU or a segment of the RLC SDU has been delivered to the upper layer, the terminal device 120 may transmit, from the RLC entity for the air interface of the terminal device 120 to a RLC entity for a sidelink interface of the terminal device 120, an eighth indication for discarding the RLC SDU. If neither the RLC SDU nor a segment of the RLC SDU has been submitted to lower layers by the RLC entity for the sidelink interface of the terminal device 120, the terminal device 120 may discard the RLC SDU by the RLC entity for the sidelink interface.
  • the terminal device 120 may receive the sixth indication via a RLC control PDU.
  • the RLC control PDU may comprise SN information of a set of RLC SDUs that is to be discarded or has been successfully delivered.
  • FIG. 8 is a simplified block diagram of a device 800 that is suitable for implementing embodiments of the present disclosure.
  • the device 800 can be considered as a further example implementation of the terminal device 110 or the terminal device 120 or the network device 130 as shown in FIG. 1. Accordingly, the device 800 can be implemented at or as at least a part of the terminal device 110 or the terminal device 120 or the network device 130.
  • the device 800 includes a processor 810, a memory 820 coupled to the processor 810, a suitable transmitter (TX) and receiver (RX) 840 coupled to the processor 810, and a communication interface coupled to the TX/RX 840.
  • the memory 810 stores at least a part of a program 830.
  • the TX/RX 840 is for bidirectional communications.
  • the TX/RX 840 has at least one antenna to facilitate communication, though in practice an Access Node mentioned in this application may have several ones.
  • the communication interface may represent any interface that is necessary for communication with other network elements, such as X2/Xn interface for bidirectional communications between eNBs/gNBs, S1/NG interface for communication between a Mobility Management Entity (MME) /Access and Mobility Management Function (AMF) /SGW/UPF and the eNB/gNB, Un interface for communication between the eNB/gNB and a relay node (RN) , or Uu interface for communication between the eNB/gNB and a terminal device.
  • MME Mobility Management Entity
  • AMF Access and Mobility Management Function
  • RN relay node
  • Uu interface for communication between the eNB/gNB and a terminal device.
  • the program 830 is assumed to include program instructions that, when executed by the associated processor 810, enable the device 800 to operate in accordance with the embodiments of the present disclosure, as discussed herein with reference to FIGs. 1 to 7.
  • the embodiments herein may be implemented by computer software executable by the processor 810 of the device 800, or by hardware, or by a combination of software and hardware.
  • the processor 810 may be configured to implement various embodiments of the present disclosure.
  • a combination of the processor 810 and memory 820 may form processing means 850 adapted to implement various embodiments of the present disclosure.
  • the memory 820 may be of any type suitable to the local technical network and may be implemented using any suitable data storage technology, such as a non-transitory computer readable storage medium, semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples. While only one memory 820 is shown in the device 800, there may be several physically distinct memory modules in the device 800.
  • the processor 810 may be of any type suitable to the local technical network, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples.
  • the device 800 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
  • a first terminal device comprises a circuitry configured to: receive an indication indicating whether a packet duplication is activated or deactivated for a split radio bearer for a direct path between the first terminal device and a network device and an indirect path between the first terminal device and the network device via a second terminal device; and perform, based on the indication, activation or deactivation of the packet duplication for the split radio bearer.
  • a network device comprises a circuitry configured to: transmit an indication indicating whether a packet duplication is activated or deactivated for a split radio bearer for a direct path between a first terminal device and the network device and an indirect path between the first terminal device and the network device via a second terminal device.
  • a second terminal device comprises a circuitry configured to:receive, from a network device, a fifth indication indicating whether a packet duplication is activated or deactivated for a split radio bearer for a direct path between a first terminal device and the network device and an indirect path between the first terminal device and the network device via the second terminal device; and transmit, to the first terminal device, a second indication indicating whether the packet duplication is activated or deactivated for the split radio bearer.
  • circuitry used herein may refer to hardware circuits and/or combinations of hardware circuits and software.
  • the circuitry may be a combination of analog and/or digital hardware circuits with software/firmware.
  • the circuitry may be any portions of hardware processors with software including digital signal processor (s) , software, and memory (ies) that work together to cause an apparatus, such as a terminal device or a network device, to perform various functions.
  • the circuitry may be hardware circuits and or processors, such as a microprocessor or a portion of a microprocessor, that requires software/firmware for operation, but the software may not be present when it is not needed for operation.
  • the term circuitry also covers an implementation of merely a hardware circuit or processor (s) or a portion of a hardware circuit or processor (s) and its (or their) accompanying software and/or firmware.
  • a method of communication comprises: receiving, at a first terminal device, an indication indicating whether a packet duplication is activated or deactivated for a split radio bearer for a direct path between the first terminal device and a network device and an indirect path between the first terminal device and the network device via a second terminal device; and performing, based on the indication, activation or deactivation of the packet duplication for the split radio bearer.
  • receiving the indication comprises at least one of the following: receiving, via the direct path from the network device, a first indication indicating whether the packet duplication is activated or deactivated for the split radio bearer for the direct path and the indirect path; receiving, via the indirect path from the second terminal device, a second indication indicating whether the packet duplication is activated or deactivated for the split radio bearer for the direct path and the indirect path; receiving the first indication via a medium access control (MAC) control element (CE) ; or receiving the first indication via a radio resource control (RRC) message.
  • MAC medium access control
  • CE control element
  • RRC radio resource control
  • the indication further indicates whether each associated radio link control (RLC) entity is activated or deactivated.
  • RLC radio link control
  • the method above further comprises: receiving, at a radio link control (RLC) entity for a sidelink interface from an upper layer of the first terminal device, a third indication for discarding a RLC service data unit (SDU) ; in accordance with a determination that neither the RLC SDU nor a segment of the RLC SDU has been submitted to lower layers, discarding the RLC SDU by the RLC entity for the sidelink interface; and in accordance with a determination that the RLC SDU or a segment of the RLC SDU has been submitted to the lower layers, transmitting, to a RLC entity for a sidelink interface of the second terminal device, a fourth indication for discarding the RLC SDU.
  • RLC radio link control
  • transmitting the fourth indication comprises: transmitting the fourth indication via a RLC control protocol data unit (PDU) .
  • PDU RLC control protocol data unit
  • the method above further comprises: in accordance with a determination that a set of uplink transmissions and a set of sidelink transmissions are to be performed, performing the set of sidelink transmissions or the set of uplink transmissions based on priorities of the set of sidelink transmissions and the set of uplink transmissions.
  • performing the set of sidelink transmissions or the set of uplink transmissions comprises: in accordance with a determination that a value of a highest priority among the set of uplink transmissions is higher than or equal to a value of a highest priority among the set of sidelink transmissions, prioritizing the set of sidelink transmissions over the set of uplink transmissions.
  • the set of uplink transmissions comprises a transmission over a set of logical channels and a set of medium access control (MAC) control elements (CEs)
  • the set of sidelink transmissions comprises a transmission over a set of logical channels and a set of MAC CEs in a sidelink MAC protocol data unit (PDU) .
  • MAC medium access control
  • CEs control elements
  • PDU sidelink MAC protocol data unit
  • a method of communication comprises: transmitting, at a network device, an indication indicating whether a packet duplication is activated or deactivated for a split radio bearer for a direct path between a first terminal device and the network device and an indirect path between the first terminal device and the network device via a second terminal device.
  • transmitting the indication comprises at least one of the following: transmitting, to the first terminal device via the direct path, a first indication indicating whether the packet duplication is activated or deactivated for the split radio bearer for the direct path and the indirect path; transmitting, to the second terminal device, a fifth indication indicating whether the packet duplication is activated or deactivated for the split radio bearer for the direct path and the indirect path of the first terminal device; transmitting the first indication via a medium access control (MAC) control element (CE) ; or transmitting the first indication via a radio resource control (RRC) message.
  • MAC medium access control
  • CE control element
  • RRC radio resource control
  • the indication further indicates whether each associated radio link control (RLC) entity is activated or deactivated.
  • RLC radio link control
  • the method above further comprises: transmitting, to the second terminal device, a sixth indication for discarding a radio link control (RLC) service data unit (SDU) .
  • RLC radio link control
  • transmitting the sixth indication comprises at least one of the following: transmitting the sixth indication via a RLC control protocol data unit (PDU) ; or transmitting, as the sixth indication, an indication indicating deactivation of packet duplication for the split radio bearer in a medium access control (MAC) control element (CE) or a radio resource control (RRC) message.
  • PDU RLC control protocol data unit
  • MAC medium access control
  • CE control element
  • RRC radio resource control
  • a method of communication comprises: receiving, at a second terminal device and from a network device, a fifth indication indicating whether a packet duplication is activated or deactivated for a split radio bearer for a direct path between a first terminal device and the network device and an indirect path between the first terminal device and the network device via the second terminal device; and transmitting, to the first terminal device, a second indication indicating whether the packet duplication is activated or deactivated for the split radio bearer.
  • receiving the fifth indication comprises at least one of the following: receiving the fifth indication via a medium access control (MAC) control element (CE) ; or receiving the fifth indication via a radio resource control (RRC) message.
  • MAC medium access control
  • CE control element
  • RRC radio resource control
  • the fifth indication comprises at least one of an identity of the first terminal device or an identity of the split radio bearer.
  • transmitting the second indication comprises at least one of the following: transmitting the second indication via a medium access control (MAC) control element (CE) ; or transmitting the second indication via a radio resource control (RRC) message.
  • MAC medium access control
  • CE control element
  • RRC radio resource control
  • the second indication comprises an identity of the split radio bearer.
  • At least one of the fifth indication or the second indication further indicates whether each associated radio link control (RLC) entity is activated or deactivated.
  • RLC radio link control
  • the method above further comprises: receiving, by a radio link control (RLC) entity for a sidelink interface of the second terminal device and from a RLC entity for a sidelink interface of the first terminal device, a fourth indication for discarding a RLC service data unit (SDU) ; in accordance with a determination that neither the RLC SDU nor a segment of the RLC SDU has been delivered to an upper layer, discarding the RLC SDU by the RLC entity for the sidelink interface of the second terminal device; in accordance with a determination that the RLC SDU or a segment of the RLC SDU has been delivered to the upper layer, transmitting, to a RLC entity for an air interface of the second terminal device, a seventh indication for discarding the RLC SDU; and in accordance with a determination that neither the RLC SDU nor a segment of the RLC SDU has been submitted to lower layers, discarding the RLC SDU by the RLC entity for the air interface of the second terminal device.
  • RLC radio link control
  • receiving the fourth indication comprises: receiving the fourth indication via a RLC control protocol data unit (PDU) .
  • PDU RLC control protocol data unit
  • the method further comprises: receiving, by the second terminal device and from the network device, a sixth indication for discarding a radio link control (RLC) service data unit (SDU) ; in accordance with a determination that neither the RLC SDU nor a segment of the RLC SDU has been delivered to an upper layer, discarding the RLC SDU by an RLC entity for an air interface of the second terminal device; in accordance with a determination that the RLC SDU or a segment of the RLC SDU has been delivered to the upper layer, transmitting, to a RLC entity for a sidelink interface of the second terminal device, an eighth indication for discarding the RLC SDU; and in accordance with a determination that neither the RLC SDU nor a segment of the RLC SDU has been submitted to lower layers, discarding the RLC SDU by the RLC entity for the sidelink interface of the second terminal device.
  • RLC radio link control
  • SDU radio link control
  • receiving the sixth indication comprises: receiving the sixth indication via a RLC control protocol data unit (PDU) .
  • PDU RLC control protocol data unit
  • the RLC control PDU comprises serial number information of a set of RLC SDUs that is to be discarded or has been successfully delivered.
  • a device of communication comprises: a processor configured to cause the device to perform any of the methods above.
  • various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representation, it will be appreciated that the 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 present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium.
  • the computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the process or method as described above with reference to FIGs. 1 to 7.
  • program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types.
  • the functionality of the program modules may be combined or split between program modules as desired in various embodiments.
  • Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
  • Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented.
  • the program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
  • the above program code may be embodied on a machine readable medium, which may be any tangible medium that may contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
  • the machine readable medium may be a machine readable signal medium or a machine readable storage medium.
  • a machine readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
  • machine readable storage medium More specific examples of the machine readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
  • RAM random access memory
  • ROM read-only memory
  • EPROM or Flash memory erasable programmable read-only memory
  • CD-ROM portable compact disc read-only memory
  • magnetic storage device or any suitable combination of the foregoing.

Landscapes

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

Abstract

Des modes de réalisation de la présente divulgation concernent des procédés, des dispositifs et des supports lisibles par ordinateur de communication. Un premier dispositif terminal reçoit une indication indiquant si une duplication de paquets est activée ou désactivée pour un support radio divisé en vue d'un trajet direct entre le premier dispositif terminal et un dispositif de réseau et d'un trajet indirect entre le premier dispositif terminal et le dispositif de réseau par l'intermédiaire d'un second dispositif terminal, et exécute, sur la base de l'indication, l'activation ou la désactivation de la duplication de paquets pour le support radio divisé. De cette manière, la duplication de paquets pour un support radio divisé peut être commandée de manière dynamique.
PCT/CN2022/120370 2022-09-21 2022-09-21 Procédé, dispositif et support de stockage informatique de communication WO2024060102A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/120370 WO2024060102A1 (fr) 2022-09-21 2022-09-21 Procédé, dispositif et support de stockage informatique de communication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/120370 WO2024060102A1 (fr) 2022-09-21 2022-09-21 Procédé, dispositif et support de stockage informatique de communication

Publications (1)

Publication Number Publication Date
WO2024060102A1 true WO2024060102A1 (fr) 2024-03-28

Family

ID=90453588

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/120370 WO2024060102A1 (fr) 2022-09-21 2022-09-21 Procédé, dispositif et support de stockage informatique de communication

Country Status (1)

Country Link
WO (1) WO2024060102A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190174513A1 (en) * 2016-09-30 2019-06-06 Panasonic Intellectual Property Corporation Of America Uplink resource allocation among different ofdm numerology schemes
US20200084663A1 (en) * 2018-09-12 2020-03-12 Kyungmin Park Session Packet Duplication Control
US20210153063A1 (en) * 2019-11-19 2021-05-20 Huawei Technologies Co., Ltd. Methods, apparatus, and systems for ue cooperation with ue relaying

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190174513A1 (en) * 2016-09-30 2019-06-06 Panasonic Intellectual Property Corporation Of America Uplink resource allocation among different ofdm numerology schemes
US20200084663A1 (en) * 2018-09-12 2020-03-12 Kyungmin Park Session Packet Duplication Control
US20210153063A1 (en) * 2019-11-19 2021-05-20 Huawei Technologies Co., Ltd. Methods, apparatus, and systems for ue cooperation with ue relaying

Similar Documents

Publication Publication Date Title
WO2023201490A1 (fr) Procédé, dispositif et support de stockage informatique destinés à la communication
WO2023141830A1 (fr) Procédé, dispositif et support de stockage destinés à la communication
WO2023184273A1 (fr) Procédé, dispositif, et support de stockage informatique destinés à la communication
WO2023102846A1 (fr) Procédé, dispositif et support lisible par ordinateur destinés aux communications
WO2023141837A1 (fr) Procédé, dispositif et support de stockage destinés à des communications
WO2024060102A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2024055305A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2024060148A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2024207377A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2024060242A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2023230884A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2024168618A1 (fr) Dispositifs et procédés de communication
WO2024212059A1 (fr) Dispositifs et procédés de communication
WO2023173423A1 (fr) Procédés, dispositifs et support lisible par ordinateur pour des communications
WO2024020959A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2023155103A1 (fr) Procédé, dispositif et support de stockage informatique destinés à des communications
WO2024207449A1 (fr) Dispositifs, procédés et support à des fins de communication
WO2024164113A1 (fr) Dispositifs, procédés et support aux fins d'une communication
WO2024197958A1 (fr) Procédés, dispositifs et support lisible par ordinateur pour rejet de paquets
WO2023123442A1 (fr) Procédé, dispositif et support lisible par ordinateur destinés à des communications
WO2024119378A1 (fr) Procédé, dispositif et support de stockage informatique pour la communication
WO2024082188A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2023108502A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2024092657A1 (fr) Procédé, dispositif et support d'enregistrement informatique de communication
WO2023206169A1 (fr) Procédé, dispositif, et support de stockage informatique destinés à la communication

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

Country of ref document: EP

Kind code of ref document: A1