[go: up one dir, main page]

WO2025159668A1 - Activation de l'agrégation ue sur une couche de liaison de données (l2) dans un réseau de communications sans fil - Google Patents

Activation de l'agrégation ue sur une couche de liaison de données (l2) dans un réseau de communications sans fil

Info

Publication number
WO2025159668A1
WO2025159668A1 PCT/SE2024/050060 SE2024050060W WO2025159668A1 WO 2025159668 A1 WO2025159668 A1 WO 2025159668A1 SE 2024050060 W SE2024050060 W SE 2024050060W WO 2025159668 A1 WO2025159668 A1 WO 2025159668A1
Authority
WO
WIPO (PCT)
Prior art keywords
network node
logical channel
service
data flow
data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/SE2024/050060
Other languages
English (en)
Inventor
Min Wang
Ming Li
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Priority to PCT/SE2024/050060 priority Critical patent/WO2025159668A1/fr
Publication of WO2025159668A1 publication Critical patent/WO2025159668A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
    • H04W40/32—Connectivity information management, e.g. connectivity discovery or connectivity update for defining a routing cluster membership
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/40—Resource management for direct mode communication, e.g. D2D or sidelink
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/04—Terminal devices adapted for relaying to or from another terminal or user
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/18—Interfaces between hierarchically similar devices between terminal devices

Definitions

  • Embodiments herein relate to enabling UE aggregation on a data link layer, L2, in a wireless communications network.
  • embodiments herein relate to a network node and method therein for enabling UE aggregation on L2 in a wireless communications network.
  • Embodiments herein also relate to a first UE and method therein for enabling UE aggregation on L2 in a wireless communications network.
  • Embodiments herein further relate to a second UE and method therein for enabling UE aggregation on L2 in a wireless communications network.
  • the embodiments herein also relate to a computer program and a carrier.
  • a wireless communications network comprises network nodes, e.g. eNodeBs/gNBs/Radio Base Stations (RBSs), providing radio coverage over at least one respective geographical area forming a cell. This is commonly referred to as a Radio Access Network, RAN.
  • RAN Radio Access Network
  • the RAN is in turn connected to the core network in the wireless communications network via a so-called backhaul network.
  • Wireless devices also referred to as User Equipments (UEs), mobile stations, and/or wireless terminals, are served in the cells by the respective radio base station and are communicating with respective radio base station in the RAN over an air/radio interface.
  • UEs User Equipments
  • the wireless devices transmit data over the air/radio interface to the radio base stations in uplink, UL, transmissions and the radio base stations transmit data over the air/radio interface to the wireless devices in downlink, DL, transmissions.
  • L2 NR sidelink Layer 2 (L2) UE-to-Network relay
  • the L2 based UE-to-Network relay is described.
  • the protocol architecture supporting a L2 UE-to-Network relay UE is also provided.
  • the L2 UE-to-Network relay UE provides forwarding functionality that may relay any type of traffic over the PC5 link.
  • the L2 UE-to-Network relay UE provides the functionality to support connectivity to the 5GS for remote UEs.
  • a UE is considered to be a remote UE if it has successfully established a PC5 link to the L2 UE- to-Network relay UE.
  • a remote UE may be located within NG-RAN coverage or outside of NG-RAN coverage.
  • FIG. 1 illustrates the protocol stack for the user plane transport, related to a Packet Data Unit (PDU) Session, including a L2 UE-to-Network relay UE.
  • the PDU layer corresponds to the PDU carried between the remote UE and the Data Network, DN, over the PDU session.
  • the PDU layer corresponds to the PDU carried between the remote UE and the DN over the PDU session.
  • PDCP Packet Data Convergence Protocol
  • the relay function is performed below PDCP. This means that data security is ensured between the remote UE and the gNB without exposing raw data at the UE-to-Network relay UE.
  • the adaptation relay layer within the UE-to-Network relay UE may differentiate between Signalling Radio Bearers, SRBs, and Data Radio Bearers, DRBs, for a particular remote UE.
  • the adaptation relay layer is also responsible for mapping PC5 traffic to one or more DRBs of the Uu link.
  • the definition of the adaptation relay layer is under the responsibility of RAN WG2.
  • FIG. 2 illustrates the protocol stack of the Non-Access Stratum (NAS) connection for the remote UE to the NAS Mobility Management (NAS-MM) and NAS Session Management (NAS-SM) components.
  • the NAS messages are transparently transferred between the remote UE and 5G Access Network (5G-AN) over the L2 UE-to- Network relay UE using a PDCP end-to-end connection.
  • 5G-AN 5G Access Network
  • 5G-AN 5G Access Network
  • the role of the UE-to- Network relay UE is to relay the PDUs over the SRB without any modifications, the N2 connection between the 5G-AN and the Access and Mobility Management Function (AMF) over the N2 interface, and the N11 connection of the AMF and Session Management Function (SMF) over the N11 interface.
  • the role of the UE-to-Network relay UE is to relay the PDUs from the SRB without any modifications.
  • the multi-carrier nature of the physical layer is only exposed to the Medium Access Control (MAC) layer on the data link layer, L2, for which one Hybrid Automatic Repeat Request (HARQ) entity is required per serving cell.
  • MAC Medium Access Control
  • L2 Hybrid Automatic Repeat Request
  • CA Carrier Aggregation
  • a basic framework of upper layer based aggregation schemes i.e. on the radio link layer, L3, may be supported in 3GPP Rel-18.
  • a study objective has been defined wherein mechanisms to support a multi-path scenario is to be specified.
  • the multi-path scenario describes a UE that is connected to the same gNB using one direct path and one indirect path, wherein the one indirect path is either via (1) a L2 UE-to-Network relay, or via (2) another UE, wherein the UE-UE inter-connection is assumed to be ideal.
  • the UE is thus allowed to connect to the same gNB using two different paths which leads to two different options.
  • the remote may connect to the same gNB using a direct Uu path and an indirect Sidelink (SL) relay path which uses a SL backhaul and a Uu hop.
  • the remote UE may connect to the same gNB using a direct Uu path and an indirect relay path which uses an ideal backhaul and a Uu hop.
  • the second option differs from the first option in that, due to the backhaul link between remote UE and relay UE, UE aggregation is to be achieved, i.e.
  • a first issue is how to distribute services and flows to different lower layer connections.
  • each service/flow may be mapped to a different cell, deployed on a different component carrier, via an RRC parameter allowedServingCells in the information element IE LogicalChannelConfig- This, however, can not be directly re-used for UE aggregation on a lower layer.
  • the selected relay UEs may belong to the same serving cell as the remote UE.
  • another issue may, for example, be how to schedule a grant by the gNB to the UE pair, i.e. the remote UE and the relay UE, intended for the service.
  • the object is achieved by a method performed by a network node for enabling UE aggregation on a data link layer, L2, in a wireless communications network.
  • the method comprises determining an identity, ID, of at least one indirect path for a logical channel on L2 for a service or data flow of a first UE.
  • the method also comprises configuring the logical channel on L2 for the service or data flow of the first UE based on the determined ID of the at least one indirect path.
  • the object is achieved by a network node for enabling UE aggregation on a data link layer, L2, in a wireless communications network.
  • the network node is configured to determine an ID of at least one indirect path for a logical channel on L2 for a service or data flow of a first UE.
  • the network node is also configured to configure the logical channel on L2 for the service or data flow of the first UE based on the determined ID of the at least one indirect path.
  • the object is achieved by a method performed by a first UE for enabling UE aggregation on L2 in a wireless communications network.
  • the method comprises receiving, from a network node in the wireless communications network, information indicating an ID of at least one indirect path for a logical channel on L2 for a service or data flow of the first UE.
  • the method also comprises transmitting, to the network node, data associated with the service or data flow of the first UE using the logical channel on L2 over the at least one indirect path based on the indicated I D(s), and/or receiving, from the network node, data associated with the service or data flow of the first UE using the logical channel on L2 over the at least one indirect path based on the indicated I D(s).
  • the object is achieved by a first UE for enabling UE aggregation on L2 in a wireless communications network.
  • the first UE is configured to receive, from a network node in the wireless communications network, information indicating an ID of at least one indirect path for a logical channel on L2 for a service or data flow of the first UE.
  • the first UE is also configured to transmit, to the network node, data associated with the service or data flow of the first UE using the logical channel on L2 over the at least one indirect path based on the indicated I D(s) , and/or receive, from the network node, data associated with the service or data flow of the first UE using the logical channel on L2 over the at least one indirect path based on the indicated ID(s).
  • the object is achieved by a method performed by a second UE for enabling UE aggregation on L2 in a wireless communications network.
  • the method comprises receiving information indicating an ID of at least one indirect path for a logical channel on L2 for a service or data flow of a first UE.
  • the method also comprises receiving data associated with the service or data flow of the first UE using the logical channel on L2 based on the indicated ID(s).
  • the method further comprises transmitting the received data associated with the service or data flow of the first UE using the logical channel on L2 based on the indicated ID(s).
  • the object is achieved by a second UE for enabling UE aggregation on L2 in a wireless communications network.
  • the second UE is configured to receive information indicating an ID of at least one indirect path for a logical channel on L2 for a service or data flow of a first UE.
  • the second UE is also configured to receive data associated with the service or data flow of the first UE using the logical channel on L2 based on the indicated I D(s).
  • the second UE is further configured to transmit the received data associated with the service or data flow of the first UE using the logical channel on L2 based on the indicated I D(s).
  • a computer program is also provided configured to perform the method described above.
  • carriers are also provided configured to carry the computer program configured for performing the method described above.
  • the network node, as well as, the first and second UEs are provided with a UE aggregation framework that enables distribution of services and flows to different connections on the lower data link layer (e.g. MAC layer on L2) and improves performance of grant scheduling for the indirect path as compared to higher layers by reducing signalling overhead and latency due to scheduling compared to UE aggregation in the higher radio link layer (e.g. PDCP layer on L3).
  • a UE aggregation framework that enables distribution of services and flows to different connections on the lower data link layer (e.g. MAC layer on L2) and improves performance of grant scheduling for the indirect path as compared to higher layers by reducing signalling overhead and latency due to scheduling compared to UE aggregation in the higher radio link layer (e.g. PDCP layer on L3).
  • Figure 1 illustrates the User Plane Stack for L2 UE-to-Network relay UE in TR 23.752 23.752 v 17.0.0 standard
  • Figure 2 illustrates the Control Plane for L2 UE-to-Network relay UE in TR 23.752 23.752 v 17.0.0 standard
  • Figure 3 illustrates L2 Structure for DL with CA configured in TS 38.300 v17.5.0 standard
  • Figure 4 illustrates L2 Structure for UL with CA configured in TS 38.300 v17.5.0 standard
  • Figure 5 is a schematic block diagram of a wireless communications network comprising network nodes and UEs according to some embodiments
  • Figure 6 is another schematic block diagram of a wireless communications network comprising network nodes and UEs according to some embodiments
  • Figure 7 is a flowchart depicting embodiments of a method in a network node
  • Figure 8 is a flowchart depicting embodiments of a method in a first UE
  • Figure 9 is a flowchart depicting embodiments of a method in a second UE.
  • Figure 10 is a block diagram depicting embodiments of a network node
  • Figure 11 is a block diagram depicting embodiments of a first UE.
  • Figure 12 is a block diagram depicting embodiments of a second UE.
  • node may be a network node or a UE.
  • network nodes are NodeB, base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB, gNodeB. MeNB, SeNB, integrated access backhaul (I AB) node, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), Central Unit (e.g. in a gNB), Distributed Unit (e.g.
  • gNB Baseband Unit
  • C-RAN access point
  • AP access point
  • RU Remote Radio Unit
  • RRH Remote Radio Head
  • DAS distributed antenna system
  • core network node e.g. Mobile Switching Center (MSC), Mobility Management Entity (MME), etc
  • O&M Operations & Maintenance
  • OSS Operations Support Systems
  • SON Self-Organizing Networks
  • positioning node e.g. E-SMLC
  • Examples of UEs may be any type of wireless device communicating with a network node and/or with another UE in a cellular or mobile communication system, such as, e.g.
  • radio access technology may be used, which may refer to any RAT, such as, e.g. UTRA, E-UTRA, narrow band internet of things (NB-loT), WiFi, Bluetooth, next generation RAT, New Radio (NR), 4/5/6G, etc.
  • any of the equipment denoted by the terms “node”, “network node” or “radio network node” may be capable of supporting a single or multiple RATs.
  • the term “direct path” is meant to describe a direct connection from a remote or target UE to a gNB, e.g. a direct connection via an air interface.
  • the term “indirect path” is meant to describe an indirect connection between a remote UE and a network node, e.g. gNB, via an intermediate node.
  • the intermediate node may also be known as a relay UE, anchor UE, or an assisting UE, etc.
  • an indirect path comprise two hops; that is, a first hop between the remote UE and the relay UE using an ideal backhaul link, and second hop between relay UE and gNB using the air interface, i.e. a llu hop.
  • the embodiments described herein are applicable to the case where a remote UE connects to the same or different network nodes, e.g. gNBs, via at least two paths, wherein one of the at least two paths is a direct path and one of the at least two paths is an indirect path using an ideal backhaul link.
  • An ideal backhaul link is assumed herein to be a dedicated point-to-point connection with high throughput and low latency.
  • Such an ideal backhaul link may, for example, be a connection utilizing Ethernet, cable, fiber, etc., or a wireless connection utilizing Wifi, Uu, SL, Bluetooth, Zigbee, etc.
  • a backhaul link between a remote UE and a relay UE may be also referred to as an inter-UE connection.
  • UE data of the remote UE may be aggregated by applying an option similar to carrier aggregation, CA.
  • CA carrier aggregation
  • the multi-path nature of the physical layer, L1 is only exposed to the MAC layer on L2 for which one HARQ entity is required per path; that is, in both UL and DL, there is one independent HARQ entity per path and one transport block is generated per assignment/grant per path in the absence of spatial multiplexing.
  • Each transport block and its potential HARQ retransmissions are mapped to a single path.
  • Figures 5-6 depicts examples of a wireless communications network 100 in which embodiments herein may operate. Figures 5-6 further depicts example scenarios or use cases for UE aggregation as described by the embodiments herein.
  • the wireless communications network 100 may be a radio communications network, such as, 6G, NR or NR+ telecommunications network. However, the wireless communications network 100 may also employ technology of any one of 3/4/5G, LTE, LTE-Advanced, WCDMA, GSM/EDGE, WiMax, UMB, GSM, or any other similar network or system.
  • the wireless communications network 100 may also employ technology transmitting on millimetre- waves (mmW), such as, an Ultra Dense Network, UDN.
  • mmW millimetre- waves
  • the wireless communications network 100 may also employ transmission supporting WiFi transmissions, e.g. the wireless communications standard IEEE 802.11 ad or similar.
  • the wireless communications network 100 may comprise a first and/or a second network node 110, 111.
  • the first and/or second network node 110, 111 may be configured to serve wireless devices in at least one cell or coverage area 115, 116, respectively.
  • the first and/or second network node 110, 111 may correspond to any type of network node or radio network node capable of communicating with wireless devices in the wireless communications network 100, such as, a base station (BS), a radio base station, gNB, eNB, eNodeB, a Home NodeB, a Home eNodeB, a femto Base Station (BS), or a pico BS in the wireless communications network 100.
  • first and second network nodes 110, 111 are repeaters, multi-standard radio (MSR) radio nodes such as MSR BSs, network controllers, radio network controllers (RNCs), base station controllers (BSCs), relays, donor node controlling relays, base transceiver stations (BTSs), access points (APs), transmission points, transmission nodes, Remote Radio Units (RRUs), Remote Radio Heads (RRHs) or nodes in distributed antenna system (DAS).
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • relays donor node controlling relays, base transceiver stations (BTSs), access points (APs), transmission points, transmission nodes, Remote Radio Units (RRUs), Remote Radio Heads (RRHs) or nodes in distributed antenna system (DAS).
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • APs access points
  • transmission points transmission nodes
  • RRUs Remote
  • a first and second UE 121, 122 are located within range of the first network node 110.
  • the first and second UE 121 , 122 are configured to communicate within the wireless communications network 100 via the first network node 110 over a radio link 131, 132 served by the first network node 110, i.e. forming a direct communication path (i.e. direct path or Uu link) between the first UE 121 and the first network node 110, as well as, a direct communication path (i.e. direct path or Uu link) between the second UE 122 and the first network node 110.
  • a direct communication path i.e. direct path or Uu link
  • the first and second UE 121, 122 may be configured to transmit data over an air or radio interface to the first network node 110 in uplink, UL, transmissions, and the first network node 110 may transmit data over an air or radio interface to the first and second UE 121 , 122 in downlink, DL, transmissions.
  • the first and second UE 121, 122 may be any type of wireless devices or mobile terminals capable of communicating with a network node and with another UE in a cellular, mobile or radio communication network or system, such as, the wireless communications network 100. Examples of such UEs are mobile phones, cellular phones, Personal Digital Assistants (PDAs), smart phones, tablets, Laptop Mounted Equipment (LME) (e.g.
  • UEs are loT devices, sensors equipped with wireless communication capabilities, Machine Type Communication (MTC) devices, Machine to Machine (M2M) devices, Customer Premises Equipment (CPE), target devices, device-to- device (D2D) enabled wireless devices, wireless devices capable of machine to machine (M2M) communication, etc.
  • MTC Machine Type Communication
  • M2M Machine to Machine
  • CPE Customer Premises Equipment
  • D2D device-to- device
  • M2M machine to machine
  • first and second UE 121 , 122 are configured to communicate with each other over an inter-UE connection 133.
  • This enables the formation of an indirect communication path between the first UE 121 and the first network node 110 via the second UE 122.
  • the inter- UE connection 133 is assumed to provide an ideal wireless backhaul link between the first UE 121 and second UE 122. This example scenario should, however, not be construed as limiting, but only to serve a general example by which the different embodiments herein may be best described.
  • Figure 7 is an illustrated example of actions or operations which may be taken by the first and/or second network node 110, 111 in the wireless communications network 100 as shown in Figures 5-6. This, for example, in order to map services of a first UE 121, i.e. a remote UE, to one or multiple aggregated paths on the data link layer, L2, e.g. on the MAC layer.
  • the method may comprise the following actions.
  • the network node 110, 111 determines an identity, ID, of at least one indirect path for a logical channel on L2 for a service or data flow of a first UE 121. This means, for example, that the network node 110, 111 may assign a unique identifier to at least one indirect path for a logical channel on L2 for a service or data flow of a first UE 121.
  • the at least one indirect path comprises an inter-UE connection 133 between the first UE 121 and a second UE 122 and a direct radio link 132 between the second UE 122 and the network node 110, 111.
  • the network node 110, 111 may, for a service/a flow employed by the first UE 121 , i.e. a remote UE, which supports UE aggregation, map the logical channel associated with the service/the flow to an indirect path, wherein the indirect path comprises an inter-UE connection between the first UE, i.e. the remote UE, and the second UE 122, i.e. the relay UE.
  • the ID of the at least one indirect path may be an ID of a second UE 122.
  • the network node 110, 111 may identify the indirect path by an ID of the second UE 122, i.e. the relay UE, and map the logical channel associated with the service or the data flow to the ID of the second UE 122, i.e. the relay UE.
  • the service or the data flow may be mapped to a radio interface identity, such as, e.g.
  • the service or the data flow may be mapped to a short or local ID of the second UE 122, wherein the short or local ID is determined based on a normal Uu ID of the second UE 122.
  • the ID of a second UE 122 may be one of: a radio link ID of the second UE 122, or a local ID based on the radio link ID of the second UE 122.
  • the direct path may comprise a direct radio link 131 between the first UE 121 and the network node 110, 111.
  • the network node 110, 111 may also identify a direct path for a logical channel on L2 for the service or data flow of the first UE 121.
  • the network node 110, 111 may map the logical channel associated with the service or the data flow to an additional RRC parameter that may be configured by the network node 110, 111 to the second UE 122, i.e. the relay UE.
  • This additional RRC parameter may indicate that the logical channel associated with the service or the data flow is allowed to be mapped to the direct path towards the network node 110, 111.
  • the first UE 121 i.e. the remote UE, may itself be treated by the network node 110, 111 as a special relay UE.
  • the first UE 121 is enabled to interpret whether the logical channel is allowed to be mapped to the direct path towards the network node 110, 111.
  • the first UE 121 may be configured by the network node 110, 111, as described below in Action 702, with both the parameter allowedRelayUEs and the parameter allowedServingCells in the information element IE LogicalChannelConfig at the same time. This may indicate to the first UE 121 that the logical channel is allowed to be mapped to both direct paths and indirect paths.
  • the logical channel configuration may further comprise information indicating if the logical channel on L2 for the service or data flow of the first UE 121 is allowed on one or both of the at least one indirect path and the direct path.
  • the logical channel configuration may be provided by an Information Element, IE LogicalChannelConfig, or by one or more Radio Resource Control, RRC, parameters.
  • two additional parameters may be defined, and later configured, by the network node 110, 111 for indicating to the first UE 121 whether the logical channel is allowed to be only mapped to direct paths and/or indirect paths.
  • such parameters may be necessary, since the logical channel may be allowed to be mapped to direct paths or indirect paths alone, as well as, both of them.
  • These two parameter may, for example, be referred to as onlyMapTolndirectPaths and onlyMapToDirectPaths as exemplified in the example of the information element IE LogicalChannelConfig used to configure the logical channel parameters.
  • the parameters are shown as the highlighted part of the corresponding ASN.1 code of the standard document TS 38.331 defining the IE LogicalChannelConfig-.
  • RelayUEIndex OPTIONAL - Cond PDCP-UEAggregation-Duplication onlyMapTolndirectPaths-r19 ENUMERATED ⁇ true ⁇ OPTIONAL, - Need R onlyMapToDirectPaths-r19 ENUMERATED ⁇ true ⁇ OPTIONAL - Need R ]] ⁇
  • LogicalChannelConfig field descriptions may in this case read as described below in Table 1:
  • the ID of the at least one indirect path may be an ID identifying an indirect path for the first UE 121 at the network node 110, 111.
  • the network node 110, 111 may identify the indirect path by an ID of the path, i.e. a determined path ID of the indirect path, and map the logical channel associated with the service or the data flow to the ID of the path.
  • both direct paths and indirect paths may be covered.
  • the network node 110, 111 may assign an index value to each direct or indirect paths.
  • the network node 110, 111 may index direct paths and indirect paths within separate value ranges. This means that through the IDs of paths, i.e. the indexes, configured in the information element IE LogicalChannelConfig, the first UE 121 enabled to determine which direct and indirect paths that the first UE 121 is allowed to transmit the data of the service or the data flow on.
  • the network node 110, 111 may index direct paths within a value range comprising lower values than that of the value range of the indirect paths, while indexing indirect paths within a value range comprising higher values than that of the value range of the direct paths.
  • the network node 110, 111 may index indirect paths within a value range comprising lower values than that of the value range of the direct paths, while indexing direct paths within a value range comprising higher values than that of the value range of the indirect paths.
  • the value ranges of the direct paths and the value ranges of the indirect paths may be non-overlapping and has the advantage that the first UE 121 may directly identify whether a path is a direct path or an indirect path through the ID of the path without reading other configuration parameters of the path.
  • the network node 110, 111 may index direct paths and indirect paths within the same value range.
  • the value ranges of the direct paths and the value ranges of the indirect paths may be overlapping.
  • the network node 110, 111 may index a path with any value within the value range regardless of whether the path is a direct path or an indirect path. This is advantageous in that fragmentation of the path ID spaces may be avoided.
  • this further means that, for each path configured to the service or the flow, the first UE 121 will need to check other configuration parameters in addition to the path ID so as to be able to identify whether the path is a direct path or an indirect path.
  • LogicalChannelConfig field descriptions may in this case read as described below in Table 2:
  • the first UE 121 may build a MAC PDU comprising Service Data Units (SDUs) belonging to different services, data flows, and/or logical channels that are allowed to map to the path. Subsequently, the first UE 121 may send the MAC PDU on the path using the UL grant.
  • SDUs Service Data Units
  • the network node 110, 111 After determines the ID of at least one indirect path for a logical channel on L2 for a service or data flow of a first UE 121 in Action 701, the network node 110, 111 configures the logical channel on L2 for the service or data flow of the first UE 121 based on the determined ID of the at least one indirect path. This means, for example, that the network node 110, 111 is able to map a service or data flow of a first UE 121, i.e. remote UE, to an indirect path on the data link layer, L2, and perform the UE aggregation on L2.
  • the network node 110, 111 may, in some embodiments, transmit, to the first UE 121 , data associated with the service or data flow of the first UE 121 using the logical channel on L2 over the at least one indirect path based on the determined ID of the at least one indirect path.
  • the network node 110, 111 may exchange DL data with the first UE 121 associated with the service or data flow of the first UE 121 using the logical channel on L2 over the at least one indirect path.
  • the network node 110, 111 may, in some embodiments, receive, from the first UE 121, data associated with the service or data flow of the first UE 121 using the logical channel on L2 over the at least one indirect path based on the determined ID of the at least one indirect path.
  • the first UE 121 may exchange UL data with the network node 110, 111 associated with the service or data flow of the first UE 121 using the logical channel on L2 over the at least one indirect path.
  • Figure 8 is an illustrated example of actions or operations which may be taken by the first UE 121 in the wireless communications network 100 as shown in Figures 5-6. This, for example, in order to enable services or data flows of a first UE 121 , i.e. a remote UE, to use one or multiple aggregated paths on the data link layer (L2), e.g. on the MAC layer.
  • the method may comprise the following actions.
  • the first UE 121 receives, from a network node 110, 111 in the wireless communications network 100, information indicating an identity, ID, of at least one indirect path for a logical channel on L2 for a service or data flow of the first UE 121.
  • the received information further indicates for which of the at least one indirect and direct paths the logical channel on L2 for the service or data flow of the first UE 121 is allowed on. This means, for example, that the first UE 121 is able to be informed about all available paths for the logical channel on L2 for a particular service or data flow of the first UE 121.
  • the first UE 121 may transmit, to the network node 110, 111 , data associated with the service or data flow of the first UE 121 using the logical channel on L2 over the at least one indirect path based on the indicated ID(s). This means, for example, that the first UE 121 may exchange UL data with the network node 110, 111 associated with the service or data flow of the first UE 121 using the logical channel on L2 over the at least one indirect path via the second UE 122, and thus perform UE aggregation on L2.
  • the transmitting may comprise transmitting data associated with the service or data flow of the first UE 121 using the logical channel on L2 over the allowed at least one indirect and direct paths.
  • the first UE 121 may exchange UL data with the network node 110, 111 associated with the service or data flow of the first UE 121 using the logical channel on L2 over the at least one indirect path via the second UE 122 and at least one direct path towards the network node 110, 111 , and thus perform UE aggregation on L2.
  • the first UE 121 may receive, from the network node 110, 111 , data associated with the service or data flow of the first UE 121 using the logical channel on L2 over the at least one indirect path based on the indicated ID(s). This means, for example, that the first UE 121 may exchange DL data with the network node 110, 111 associated with the service or data flow of the first UE 121 using the logical channel on L2 over the at least one indirect path via the second UE 122, and thus perform UE aggregation on L2.
  • the receiving may comprise receiving data associated with the service or data flow of the first UE 121 using the logical channel on L2 over the allowed at least one indirect and direct paths.
  • the first UE 121 may exchange DL data with the network node 110, 111 associated with the service or data flow of the first UE 121 using the logical channel on L2 over the at least one indirect path via the second UE 122 and at least one direct path towards the network node 110, 111, and thus perform UE aggregation on L2.
  • Figure 9 is an illustrated example of actions or operations which may be taken by the second UE 122 in the wireless communications network 100 as shown in Figures 5-6. This, for example, in order to enable services or data flows of a first UE 121 , i.e. a remote UE, to use one or multiple aggregated paths on the data link layer (L2), e.g. on the MAC layer.
  • the method may comprise the following actions.
  • the second UE 122 receives information indicating an identity, ID, of at least one indirect path for a logical channel on L2 for a service or data flow of a first UE 121.
  • this may comprise receiving the information from the first UE 121 over an inter-UE connection 133 between the first UE 121 and a second UE 122.
  • the second UE 122 is able to store, be configured with and use configuration information provided by the first UE 110, 111 as described above with reference to Actions 801-803, and thus be configured to operate as a relay UE for the at least one indirect path.
  • this may comprise receiving the information from the network node 110, 111 over a direct radio link 132 between the second UE 122 and the network node 110, 111.
  • the second UE 122 is able to store, be configured with and use configuration information provided by the network node 110, 111 as described above with reference to Actions 701-702, and thus be configured to operate as a relay UE for the at least one indirect path.
  • the second UE 122 After receiving the information in Action 901 , the second UE 122 receives data associated with the service or data flow of the first UE 121 using the logical channel on L2 based on the indicated ID(s).
  • the second UE 122 i.e. the relay UE, operate as a relay UE for the at least one indirect path between the first UE 121 and the network node 110, 111.
  • this may comprise receiving the data from the first UE 121 over an inter-UE connection 133 between the first UE 121 and the second UE 122.
  • the second UE 122 i.e.
  • the relay UE may operate and act as a relay UE for UL data on the at least one indirect path between the first UE 121 and the network node 110, 111.
  • this may comprise receiving the data from the network node 110, 111 over a direct radio link 132 between the second UE 122 and the network node 110, 111.
  • the second UE 122 i.e. the relay UE, may operate and act as a relay UE for DL data on the at least one indirect path between the first UE 121 and the network node 110, 111.
  • the second UE 122 After receiving the data in Action 902, the second UE 122 transmits the received data associated with the service or data flow of the first UE 121 using the logical channel on L2 based on the indicated ID(s).
  • the second UE 122 i.e. the relay UE, operate as a relay UE for the at least one indirect path between the first UE 121 and the network node 110, 111.
  • the relay UE in case data from the first UE 121 was received over an inter-UE connection 133 between the first UE
  • this may comprise transmitting the received data to the network node 110, 111 over a direct radio link 132 between the second UE
  • the second UE 122 i.e. the relay UE
  • this may comprise transmitting the received data to the first UE 121 over an inter-UE connection 133 between the first UE 121 and the second UE 122.
  • the second UE 122 i.e. the relay UE
  • the network node 110, 111 may comprise the following arrangement depicted in Figure 10.
  • Figure 10 shows a schematic block diagram of embodiments of the network node 110,
  • the network node 110, 111 may comprise processing circuitry or processor 1010 and a memory 1020.
  • the processing circuitry 1110 may also comprise a receiving module 1011 and a transmitting module 1012.
  • the receiving module 1011 and the transmitting module 1012 may also be configured to communicate and perform transmissions over the wireless communications network 100.
  • the receiving module 1011 and the transmitting module 1012 comprise Radio Frequency, RF, processing circuitry capable of transmitting a radio signal via a radio interface (not shown) within the wireless communications network 100.
  • the receiving module 1011 and the transmitting module 1012 may also form part of a single transceiver.
  • the functionality described in the embodiments above as being performed by the network node 110, 111 may be provided by the processing circuitry 1010 executing instructions stored on a computer-readable medium, such as, e.g., the memory 1020 shown in Figure 10.
  • Alternative embodiments of the network node 110, 111 may comprise additional components, such as, for example, a determining module 1013, a configuring module 1014, and a granting module 1015, each responsible for providing its respective functionality necessary to support the embodiments described herein.
  • the network node 110, 111 or processing circuitry 1010 is configured to, or may comprise the determining module 1013 configured to, determine an identity, ID, of at least one indirect path for a logical channel on L2 for a service or data flow of a first UE 121. Also, the network node 110, 111 or processing circuitry 1010 is configured to, or may comprise the configuring module 1114 configured to, configure the logical channel on L2 for the service or data flow of the first UE 121 based on the determined ID of the at least one indirect path. In some embodiments, the at least one indirect path may comprise an inter-UE connection 133 between the first UE 121 and a second UE 122 and a direct radio link 132 between the second UE 122 and the network node 110, 111.
  • the ID of the at least one indirect path may be one of: an ID of a second UE 122, an ID identifying an indirect path for the first UE 121 at the network node 110, 111, or an ID of an inter-UE connection 133 between the first UE 121 and a second UE 122.
  • the ID of a second UE 122 may be one of: a radio link ID of the second UE 122, or a local ID based on the radio link ID of the second UE 122.
  • the network node 110, 111 or processing circuitry 1010 may be configured to, or may comprise the transmitting module 1012 configured to, transmit, to the first UE 121 and/or the second UE 122, a logical channel configuration for the logical channel on L2 for the service or data flow of the first UE 121 , wherein the logical channel configuration comprise information indicating the determined ID of the at least one indirect path.
  • the logical channel configuration may further comprise information indicating if the logical channel on L2 for the service or data flow of the first UE 121 is allowed on one or both of the at least one indirect path and the direct path.
  • the logical channel configuration may be provided by an Information Element, IE LogicalChannelConfig, or by one or more Radio Resource Control, RRC, parameters.
  • a first part of the index value range may be arranged to indicate the IDs of direct paths allowed for the logical channel on L2 for the service or data flow of the first UE 121
  • a second part of the index value range may be arranged to indicate the IDs of indirect paths allowed for the logical channel on L2 for the service or data flow of the first UE 121.
  • the first and second parts of the index value range may be either overlapping or non-overlapping.
  • the direct path comprises a direct radio link 131 between the first UE 121 and the network node 110, 111.
  • the network node 110, 111 or processing circuitry 1010 may be configured to, or may comprise the transmitting module 1012 configured to, transmit, to the first UE 121 , data associated with the service or data flow of the first UE 121 using the logical channel on L2 over the at least one indirect path based on the determined ID of the at least one indirect path.
  • the network node 110, 111 or processing circuitry 1010 may be configured to, or may comprise the receiving module 1011 configured to, receive data associated with the service or data flow of the first UE 121 using the logical channel on L2 over the at least one indirect path based on the determined ID of the at least one indirect path.
  • the embodiments for enabling UE aggregation on a data link layer, L2, in a wireless communications network 100 described above may be implemented through one or more processors, such as the processing circuitry 1010 in the network node 110, 111 depicted in Figure 10, together with computer program code for performing the functions and actions of the embodiments herein.
  • the program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code or code means for performing the embodiments herein when being loaded into the processing circuitry 1010 in the network node 110, 111.
  • the computer program code may e.g. be provided as pure program code in the network node 110, 111 or on a server and downloaded to the network node 110, 111.
  • modules of the network node 110, 111 may in some embodiments be implemented as computer programs stored in memory, e.g. in the memory modules 1020 in Figure 10, for execution by processors or processing modules, e.g. the processing circuitry 1010 of Figure 10.
  • processors or processing modules e.g. the processing circuitry 1010 of Figure 10.
  • the processing circuitry 1010 and the memory 1020 described above may refer to a combination of analog and digital circuits, and/or one or more processors configured with software and/or firmware, e.g. stored in a memory, that when executed by the one or more processors such as the processing circuitry 1020 perform as described above.
  • processors may be included in a single application-specific integrated circuit (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a system-on-a-chip (SoC).
  • ASIC application-specific integrated circuit
  • SoC system-on-a-chip
  • the first UE 121 may comprise the following arrangement depicted in Figure 11.
  • Figure 11 shows a schematic block diagram of embodiments of the first UE 121.
  • the first UE 121 may comprise processing circuitry or processor 1110 and a memory 1120.
  • the processing circuitry 1110 may also comprise a receiving module 1111 and a transmitting module 1112.
  • the receiving module 1111 and the transmitting module 1112 may also be configured to communicate and perform transmissions over the wireless communications network 100.
  • the receiving module 1111 and the transmitting module 1112 comprise Radio Frequency, RF, processing circuitry capable of transmitting a radio signal via a radio interface (not shown) within the wireless communications network 100.
  • the receiving module 1111 and the transmitting module 1112 may also form part of a single transceiver. It should also be noted that some or all of the functionality described in the embodiments above as being performed by the first UE 121 may be provided by the processing circuitry 1110 executing instructions stored on a computer-readable medium, such as, e.g., the memory 1120 shown in Figure 11.
  • the first UE 121 or processing circuitry 1110 is configured to, or may comprise the receiving module 1111 configured to, receive, from a network node 110, 111 in the wireless communications network 100, information indicating an identity, ID, of at least one indirect path for a logical channel on L2 for a service or data flow of the first UE 121. Also, the first UE 121 or processing circuitry 1110 is configured to, or may comprise the transmitting module 1112 configured to, transmit, to the network node 110, 111, data associated with the service or data flow of the first UE 121 using the logical channel on L2 over the at least one indirect path based on the indicated IDs.
  • the first UE 121 or processing circuitry 1110 is configured to, or may comprise the receiving module 1111 configured to, receive, from the network node 110, 111 , data associated with the service or data flow of the first UE 121 using the logical channel on L2 over the at least one indirect path based on the indicated ID(s).
  • the received information may further indicates for which of the at least one indirect and direct paths the logical channel on L2 for the service or data flow of the first UE 121 is allowed on.
  • the first UE 121 or processing circuitry 1110 may be configured to, or may comprise the transmitting module 1112 configured to, transmit data associated with the service or data flow of the first UE 121 using the logical channel on L2 over the allowed at least one indirect and direct paths.
  • the first UE 121 or processing circuitry 1110 may be configured to, or may comprise the receiving module 1111 configured to, receive data associated with the service or data flow of the first UE 121 using the logical channel on L2 over the allowed at least one indirect and direct paths.
  • the embodiments for enabling UE aggregation on a data link layer, L2, in a wireless communications network 100 described above may be implemented through one or more processors, such as the processing circuitry 1110 in the the first UE 121 depicted in Figure 11, together with computer program code for performing the functions and actions of the embodiments herein.
  • the program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code or code means for performing the embodiments herein when being loaded into the processing circuitry 1110 in the first UE 121.
  • the computer program code may e.g. be provided as pure program code in the first UE 121 or on a server and downloaded to the first UE 121.
  • modules of the first UE 121 may in some embodiments be implemented as computer programs stored in memory, e.g. in the memory modules 1120 in Figure 11, for execution by processors or processing modules, e.g. the processing circuitry 1110 of Figure 11.
  • processing circuitry 1110 and the memory 1120 described above may refer to a combination of analog and digital circuits, and/or one or more processors configured with software and/or firmware, e.g. stored in a memory, that when executed by the one or more processors such as the processing circuitry 1120 perform as described above.
  • processors as well as the other digital hardware, may be included in a single application-specific integrated circuit (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a system-on-a-chip (SoC).
  • ASIC application-specific integrated circuit
  • SoC system-on-a-chip
  • the second UE 122 may comprise the following arrangement depicted in Figure 12.
  • Figure 12 shows a schematic block diagram of embodiments of second UE 122.
  • the second UE 122 may comprise processing circuitry or processor 1210 and a memory 1220.
  • the processing circuitry 1110 may also comprise a receiving module 1211 and a transmitting module 1212.
  • the receiving module 1211 and the transmitting module 1212 may also be configured to communicate and perform transmissions over the wireless communications network 100.
  • the receiving module 1211 and the transmitting module 1212 comprise Radio Frequency, RF, processing circuitry capable of transmitting a radio signal via a radio interface (not shown) within the wireless communications network 100.
  • the receiving module 1211 and the transmitting module 1212 may also form part of a single transceiver. It should also be noted that some or all of the functionality described in the embodiments above as being performed by the second UE 122 may be provided by the processing circuitry 1210 executing instructions stored on a computer-readable medium, such as, e.g., the memory 1220 shown in Figure 12.
  • the second UE 122 or processing circuitry 1210 is configured to, or may comprise the receiving module 1211 configured to, receive information indicating an identity, ID, of at least one indirect path for a logical channel on L2 for a service or data flow of a first UE 121. Also, the second UE 122 or processing circuitry 1210 is configured to, or may comprise the receiving module 1211 configured to, receive data associated with the service or data flow of the first UE 121 using the logical channel on L2 based on the indicated ID(s).
  • the second UE 122 or processing circuitry 1210 is configured to, or may comprise the transmitting module 1212 configured to, transmit the received data associated with the service or data flow of the first UE 121 using the logical channel on L2 based on the indicated ID(s).
  • the second UE 122 or processing circuitry 1210 may be configured to, or may comprise the receiving module 1211 configured to, receive the information from the first UE 121 over an inter-UE connection 133 between the first UE 121 and a second UE 122, or to receive the information from the network node 110, 111 over a direct radio link 132 between the second UE 122 and the network node 110, 111.
  • the second UE 122 or processing circuitry 1210 may be configured to, or may comprise the receiving module 1211 configured to, receive the data from the first UE 121 over an inter-UE connection 133 between the first UE 121.
  • the second UE 122 or processing circuitry 1210 may be configured to, or may comprise the transmitting module 1212 configured to, transmit the received data to the network node 110, 111 over a direct radio link 132 between the second UE 122 and the network node 110, 111.
  • the second UE 122 or processing circuitry 1210 may be configured to, or may comprise the receiving module 1211 configured to, receive the data from the network node 110, 111 over a direct radio link 132 between the second UE 122 and the network node 110, 111.
  • the second UE 122 or processing circuitry 1210 may be configured to, or may comprise the transmitting module 1212 configured to, transmit the received data to the first UE 121 over an inter-UE connection 133 between the first UE 121 and the second UE 122.
  • the embodiments for enabling UE aggregation on a data link layer, L2, in a wireless communications network 100 described above may be implemented through one or more processors, such as the processing circuitry 1210 in the second UE 122 depicted in Figure 12, together with computer program code for performing the functions and actions of the embodiments herein.
  • the program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code or code means for performing the embodiments herein when being loaded into the processing circuitry 1210 in the second UE 122.
  • the computer program code may e.g. be provided as pure program code in the second UE 122 or on a server and downloaded to the second UE 122.
  • modules of the second UE 122 may in some embodiments be implemented as computer programs stored in memory, e.g. in the memory modules 1220 in Figure 12, for execution by processors or processing modules, e.g. the processing circuitry 1210 of Figure 12.
  • processing circuitry 1210 and the memory 1220 described above may refer to a combination of analog and digital circuits, and/or one or more processors configured with software and/or firmware, e.g. stored in a memory, that when executed by the one or more processors such as the processing circuitry 1220 perform as described above.
  • processors as well as the other digital hardware, may be included in a single application-specific integrated circuit (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a system-on-a-chip (SoC).
  • ASIC application-specific integrated circuit
  • SoC system-on-a-chip
  • the network node 110, 111 may receive a scheduling request indicating an identity, ID, of an indirect path.
  • the network node 110, 111 may also, according to some embodiments, grant transmission resources to the first UE 121 for data associated with the service or data flow of the first UE 121 on the logical channel of L2 over the identified indirect path via the second UE 122 based on scheduling request resources associated with the identified indirect path in the network node 110, 111.
  • This is also illustrated in additional actions 703-704, which describes generally how a scheduling request for a service may be mapped to an indirect path.
  • the identified indirect path may comprise an inter-UE connection 133 between the first UE 121 and a second UE 122 and a direct radio link 132 between the second UE 122 and the network node 110, 111.
  • the scheduling request resources associated with the identified indirect path in the network node 110, 111 may belong to the scheduling request resources and/or configurations of the first UE 121 and/or the second UE 122.
  • the network node 110, 111 may receive a scheduling request message indicating the ID of the indirect path from both the first UE 121 and the second UE 122.
  • the network node 110, 111 may grant transmission resources based on either of the scheduling request resources associated with the indirect path in the network node 110, 111 belonging to the first UE 121 and the second UE 122.
  • the network node 110, 111 in case no valid scheduling request resources is available among the scheduling request resources associated with the identified indirect path in the network node 110, 111 , receiving information from the first UE 121 or the second UE 122 triggering a RACH procedure.
  • the various embodiments and examples on how the network node 110, 111 may interact with a first UE 121 sending a scheduling request, SR, or a buffer status report, BSR, to request resources for an indirect path via a second UE 122 described above, are further described below in even more detail.
  • the first UE 121 , the second UE 122 and the network node 110, 111 apply one of the following examples described below to handle SRs.
  • the corresponding logical channel configuration may be mapped or associated with a SR resource or SR configuration belonging to the first UE 121.
  • the first UE 121 may trigger an SR and transmit the SR to the network node 110, 111 using the SR resource.
  • the network node 110, 111 may interpret the SR that the first UE 121 is requesting UL resources on the indirect path for the second UE 122. Hence, the first UE 121 may send the SR to the network node 110, 111 on behalf of the second UE 122.
  • the corresponding logical channel configuration may be mapped or associated with a SR resource or SR configuration belonging to the second UE 122.
  • the first UE 121 may inform the second UE 122 of arrival of the new data for the service.
  • the second UE 122 may then trigger an SR and transmit the SR to the network node 110, 111 using the SR resource.
  • the network node 110, 111 may interpret the SR in that the second UE 122 is requesting UL resources on the indirect path.
  • it may also occur that both the first UE 121 and the second UE 122 have SR resources or SR configurations mapped to the logical channel.
  • the first UE 121 may share the information with the second UE 122, i.e. the new data arrival for the logical channel.
  • both the first UE 121 and the second UE 122 may therefore trigger a SR and transmit the SR to the network node(s) 110, 111.
  • the network node(s) 110, 111 may thus determine how to schedule resources to the second UE 122 based on the received SRs.
  • the first UE 121 may have no valid SR resources for a logical channel mapped to an indirect path, e.g. either the logical channel has no SR resources configured or the configured SR resources are not valid due to transmission failures.
  • the first UE 121 may further check with the second UE 122 on whether the second UE 122 has valid SR resources for the logical channel. Subsequently, if the second UE 122 has valid SR resources for the logical channel, the first UE 121 may, for example, not follow the legacy Uu procedure and trigger a RACH procedure towards the network node 110, 111 wherein the SR is indicated via the RACH procedure. In this case, the second UE 122 may trigger a SR towards its serving network node 110, 111 instead.
  • the second UE 122 may be up to the implementation of the first UE 121 and the second UE 122 to determine which of the first UE 121 and the second UE 122 is to trigger a RACH procedure towards the network node 110, 111.
  • the network node 110, 111 may determine which of the first UE 121 and the second UE 122 is to trigger a RACH procedure towards the network node 110, 111 when neither the first UE 121 or the second UE 122 has valid SR resources for the logical channel. Additionally, the first UE 121 may share the logical channel configuration and the buffer status of the logical channel with the second UE 122 via the inter-UE connection if needed.
  • the first UE 121 , the second UE 122 and the network node 110, 111 apply one of the following examples described below to handle BSRs.
  • the first UE 121 may build a BSR MAC Control Element (CE) comprising the buffer status of all logical channels including the logical channel even though it is mapped to the indirect path.
  • CE BSR MAC Control Element
  • the first UE 121 may leave it to the network node 110, 111 to exclude the buffer status of the logical channel for the first UE 121, since the network node 110, 111 has knowledge about which logical channels are mapped to the indirect path.
  • the first UE 121 may build a BSR MAC Control Element (CE) comprising the buffer status of all logical channels except the logical channel.
  • CE BSR MAC Control Element
  • the second UE 122 may also include buffer status of the logical channel in the BSRs triggered by the second UE 122. This may be advantageous to improve transmission reliability for BSRs triggered by both the first UE 121 and the second UE 122, since one of the first UE 121 and the second UE 122 may fail to transmit a BSR due to bad radio quality, or congestion.
  • the first UE 121 may determine which of the direct or indirect path to transmit the data of the logical channel.
  • the first UE 121 may determine the path with strongest Uu radio quality, e.g. measured in RSRP, RSRQ, SINR or other similar measurements, etc.
  • the first UE 121 may determines the path with lowest Uu congestion. A further option it is up to the implementation in the first UE 121 to determine on which path to transmit the data of the logical channel.
  • the first UE 121 may send an SR or BSR on the selected path to the network node 110, 111 indicating the determine and selected path of the first UE 121.
  • the network node 110, 111 may select the path for the first UE 121 to transmit the data of the logical channel.
  • the network node 110, 111 may signal its decision to the first UE 121 via, for example, RRC signalling, a MAC CE or a L1 signalling (e.g., DCI on PDCCH).
  • the network node 110, 111 or processing circuitry 1010 may be configured to, or may comprise the receiving module 1011 configured to, receive a scheduling request indicating an identity, ID, of an indirect path. Also, the network node 110, 111 or processing circuitry 1010 may be configured to, or may comprise the granting module 1014 configured to, grant transmission resources to the first UE 121 for data associated with the service or data flow of the first UE 121 on the logical channel of L2 over the identified indirect path via the second UE 122 based on scheduling request resources associated with the identified indirect path in the network node 110, 111.
  • the network node 110, 111 or processing circuitry 1010 may be configured to, or may comprise the receiving module 1011 configured to, receive a scheduling request message indicating the ID of the indirect path from both the first UE 121 and the second UE 122.
  • the network node 110, 111 or processing circuitry 1010 may be configured to, or may comprise the granting module 1014 configured to, grant transmission resources based on either of the scheduling request resources associated with the indirect path in the network node 110, 111 belonging to the first UE 121 and the second UE 122.
  • the network node 110, 111 or processing circuitry 1010 may be configured to, or may comprise the receiving module 1011 configured to, receive information from the first UE 121 or the second UE 122 triggering a RACH procedure.
  • the first UE 121 may further receive data associated with the service or data flow of the first UE 121 on the logical channel of L2 over a indirect path via the second UE 122.
  • the first UE 121 may also transmit information indicating the reception of the data to the second UE 122 and/or a scheduling request indicating an identity, ID, of the indirect path to a network node 110, 111 in the wireless communications network 100 based on the scheduling request resources associated with the indirect path in the first UE 121.
  • This is also illustrated in additional actions 803-804, which describes generally how a scheduling request for a service may be mapped to an indirect path.
  • the scheduling request resources associated with the indirect path in the first UE 121 belongs to the scheduling request resources and/or configurations of the first UE 121 and/or the second UE 122. In some embodiments, in case the scheduling request resources associated with the indirect path in the first UE 121 belongs to the scheduling request resources and/or configurations of the first UE 121 but no valid scheduling request resources are available, the first UE 121 may further transmit, to the second UE 122, information indicating to the second UE 122 to transmit a scheduling request to the network node 110, 111 if the second UE 122 has valid scheduling request resources, or transmit, to the network node 110, 111 , information triggering a RACH procedure.
  • the first UE 121 may further receive information from the second UE 122 indicating that the second UE 122 has valid scheduling request resources associated with the indirect path, and in response, refraining from transmitting information triggering a RACH procedure to the network node 110, 111.
  • the first UE 121 or processing circuitry 1110 may be configured to, or may comprise the receiving module 1111 configured to, receive data associated with the service or data flow of the first UE 121 on the logical channel of L2 over a indirect path via the second UE 122.
  • the first UE 121 or processing circuitry 1110 may be configured to, or may comprise the transmitting module 1112 configured to, transmit information indicating the reception of the data to the second UE 122 and/or a scheduling request indicating an identity, ID, of the indirect path to a network node 110, 111 in the wireless communications network 100 based on the scheduling request resources associated with the indirect path in the first UE 121.
  • the first UE 121 or processing circuitry 1110 may be configured to, or may comprise the transmitting module 1112 configured to, transmit, to the second UE 122, information indicating to the second UE 122 to transmit a scheduling request to the network node 110, 111 if the second UE 122 has valid scheduling request resources, or transmit, to the network node 110, 111, information triggering a RACH procedure.
  • the first UE 121 or processing circuitry 1110 may be configured to, or may comprise the receiving module 1111 configured to, receive information from the second UE 122 indicating that the second UE 122 has valid scheduling request resources associated with the indirect path, and in response, refrain from transmitting information triggering a RACH procedure to the network node 110, 111.
  • the second UE 122 may further receive, from the first UE 121, information indicating that data associated with the service or data flow of the first UE 121 for the logical channel on L2 over an indirect path via the second UE 122 has been received.
  • the second UE 122 may receive information indicating to the second UE 122 to transmit a scheduling request to the network node 110, 111 if the second UE 122 has valid scheduling request resources associated with an indirect path.
  • the second UE 121 may transmit a scheduling request indicating an identity, ID, of the indirect path to a network node 110, 111 in the wireless communications network 100 based on the scheduling request resources associated with the indirect path in the second UE 121. This is also illustrated in additional actions 904-905, which describes generally how a scheduling request for a service may be mapped to an indirect path.
  • the second UE 121 may transmit information to the first UE 121 indicating that the second UE 122 has valid scheduling request resources associated with the indirect path. In some embodiments, in case no valid scheduling request resources is available among the scheduling request resources associated with the indirect path in the second UE 122, the second UE 121 may transmit, to the network node 110, 111 , information triggering a RACH procedure.
  • the second UE 122 or processing circuitry 1210 may be configured to, or may comprise the receiving module 1211 configured to, receive, from the first UE 121, information indicating that data associated with the service or data flow of the first UE 121 for the logical channel on L2 over an indirect path via the second UE 122 has been received-
  • the second UE 122 or processing circuitry 1210 may be configured to, or may comprise the receiving module
  • the second UE 122 or processing circuitry 1210 may be configured to, or may comprise the transmitting module 1212 configured to transmit a scheduling request indicating an identity, ID, of the indirect path to a network node 110, 111 in the wireless communications network 100 based on the scheduling request resources associated with the indirect path in the second UE 121.
  • the second UE 122 or processing circuitry 1210 may be configured to, or may comprise the transmitting module
  • the second UE 122 or processing circuitry 1210 may be configured to, or may comprise the transmitting module 1212 configured to, in case no valid scheduling request resources is available among the scheduling request resources associated with the indirect path in the second UE 122, transmit, to the network node 110, 111 , information triggering a RACH procedure.
  • the network node 110, 111 may schedules a resource to the second UE 122 for a logical channel of the first UE 121 mapped to the indirect path are further described below in more detail.
  • the resource may be a UL grant for the second UE 122 to transmit the UL data of the logical channel received from the first UE 121 via the inter-UE connection 133.
  • the resource may be a DL assignment for the second UE 122 to receive the DL data from the network node 110, 111. After the second UE 122 has received the DL data, the second UE 122 may forward the DL data to the first UE 121 via the inter-UE connection 133. This is because the DL data is intended for the first UE 121.
  • the network node 110, 111 may send a DCI indicating the resource to the second UE 122.
  • the DCI may be addressed to an ID of the second UE 122 (e.g. a C-RNTI of the second UE 122).
  • the second UE 122 may request the first UE 121 to forward the data to the second UE 122 via the inter-UE connection 133.
  • the first UE 121 may then forward the data to the second UE 122.
  • the first UE 121 may generate a MAC PDU comprising the data and forward the generated MAC PDU or Transport Block (TB) to the second UE 122.
  • TB Transport Block
  • the network node 110, 111 may send a DCI indicating the resource for the second UE 122 to the first UE 121.
  • the DCI is addressed to an ID of the first UE 121 (e.g. a C-RNTI of the first UE 121).
  • the DCI may also carry an indicator indicating that the resource is intended for the second UE 122.
  • the indicator may be an Uu ID of the second UE 122, such as, e.g. a C-RNTI, a l-RNTI (full or short l-RNTI), a resume ID, a CS-RNTI, etc.
  • the indicator may be an a short ID which is converted from any llu ID of the second UE 122.
  • the short ID may have shorter size than a normal llu ID.
  • a computer-readable medium may include removable and non-removable storage devices including, but not limited to, Read Only Memory (ROM), Random Access Memory (RAM), compact discs (CDs), digital versatile discs (DVD), etc.
  • program modules may include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types.
  • Computer-executable instructions, associated data structures, and program modules represent examples of program code for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represents examples of corresponding acts for implementing the functions described in such steps or processes.

Landscapes

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

Abstract

L'invention concerne un procédé mis en œuvre par un nœud de réseau (110, 111) pour permettre l'agrégation d'UE sur une couche de liaison de données, L2, dans un réseau de communications sans fil (100). Le procédé consiste à déterminer une identité, ID, d'au moins un trajet indirect pour un canal logique sur L2 pour un service ou un flux de données d'un premier UE (121). En outre, le procédé consiste à configurer le canal logique sur L2 pour le service ou le flux de données du premier UE (121) sur la base de l'ID déterminé du ou des trajets indirects. L'invention concerne également un nœud de réseau, ainsi que des programmes informatiques et des porteuses. En outre, l'invention concerne également un premier et un second UE, des procédés associés, ainsi que des programmes informatiques et des porteuses.
PCT/SE2024/050060 2024-01-24 2024-01-24 Activation de l'agrégation ue sur une couche de liaison de données (l2) dans un réseau de communications sans fil Pending WO2025159668A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/SE2024/050060 WO2025159668A1 (fr) 2024-01-24 2024-01-24 Activation de l'agrégation ue sur une couche de liaison de données (l2) dans un réseau de communications sans fil

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/SE2024/050060 WO2025159668A1 (fr) 2024-01-24 2024-01-24 Activation de l'agrégation ue sur une couche de liaison de données (l2) dans un réseau de communications sans fil

Publications (1)

Publication Number Publication Date
WO2025159668A1 true WO2025159668A1 (fr) 2025-07-31

Family

ID=96545411

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2024/050060 Pending WO2025159668A1 (fr) 2024-01-24 2024-01-24 Activation de l'agrégation ue sur une couche de liaison de données (l2) dans un réseau de communications sans fil

Country Status (1)

Country Link
WO (1) WO2025159668A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3796610A1 (fr) * 2018-05-17 2021-03-24 Huawei Technologies Co., Ltd. Procédé et dispositif de communication
US20220394433A1 (en) * 2021-06-04 2022-12-08 Huawei Technologies Co., Ltd. Methods and apparatuses for user equipment aggregation
WO2023108641A1 (fr) * 2021-12-17 2023-06-22 Zte Corporation Procédé, dispositif et produit-programme d'ordinateur pour des communications sans fil
US20230354152A1 (en) * 2022-07-05 2023-11-02 Intel Corporation Sidelink relay enhancements to support multipath
US20240015558A1 (en) * 2022-07-05 2024-01-11 Qualcomm Incorporated Sidelink carrier aggregation

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3796610A1 (fr) * 2018-05-17 2021-03-24 Huawei Technologies Co., Ltd. Procédé et dispositif de communication
US20220394433A1 (en) * 2021-06-04 2022-12-08 Huawei Technologies Co., Ltd. Methods and apparatuses for user equipment aggregation
WO2023108641A1 (fr) * 2021-12-17 2023-06-22 Zte Corporation Procédé, dispositif et produit-programme d'ordinateur pour des communications sans fil
US20230354152A1 (en) * 2022-07-05 2023-11-02 Intel Corporation Sidelink relay enhancements to support multipath
US20240015558A1 (en) * 2022-07-05 2024-01-11 Qualcomm Incorporated Sidelink carrier aggregation

Similar Documents

Publication Publication Date Title
US10721118B2 (en) Method for configuring dual-connectivity by terminal, and apparatus therefor
US10660018B2 (en) Device-to-device communication
JP2022130732A (ja) 基地局及びその方法
CN112154709A (zh) 基于移动设备中继的覆盖范围扩展方法
CN115336381B (zh) 在无线网络中建立信令连接
US9924556B2 (en) Radio communication system, base station, mobile station, communication control method, and non-transitory computer readable medium
EP3202216B1 (fr) Noeud de réseau, un noeud de gestion de mobilité et leurs procédés pour gérer des défaillances de tunnel gtp dans un réseau de communication radio
US10667160B2 (en) Wireless communications device, a network node and methods therein for measurement reporting
US12464420B2 (en) Communication method and communication apparatus
US20250159561A1 (en) Communication system and base station
CN116158190A (zh) 通信系统及通信终端
CN113728676A (zh) 在集成接入和回程网络中的子节点处和父节点处的资源对准
CN116158137A (zh) 通信系统及基站
US12245085B2 (en) Method and device for group handover in communication system
CN113366782A (zh) 用于控制传输的第一通信设备、第二通信设备以及在其中执行的方法
US20240397396A1 (en) Switching method, terminal device and network device
EP4351191A1 (fr) Système de communication et station de base
CN116250373A (zh) 通信系统
WO2020167188A1 (fr) Entité de protocole pdcp, entité de commande rlc et procédés réalisés dans celles-ci pour fournir une connectivité multiple
US20250159734A1 (en) Mobile node configuration method, mobile node, and donor device
CN104038986A (zh) 处理基地台的选择的方法及其通信装置
WO2025159668A1 (fr) Activation de l'agrégation ue sur une couche de liaison de données (l2) dans un réseau de communications sans fil
US10932163B1 (en) Controlling handover based on source and target capabilities with respect to dual connectivity
US20250301515A1 (en) Method for wireless communication, terminal device, and relay node
EP4478800A1 (fr) Système de 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: 24920517

Country of ref document: EP

Kind code of ref document: A1