WO2022075906A1 - Nœud de réseau, nœud de réseau demandeur et procédés de communication sur un chemin comprenant un équipement utilisateur distant, un équipement utilisateur relais et un nœud de réseau radio - Google Patents

Nœud de réseau, nœud de réseau demandeur et procédés de communication sur un chemin comprenant un équipement utilisateur distant, un équipement utilisateur relais et un nœud de réseau radio Download PDF

Info

Publication number
WO2022075906A1
WO2022075906A1 PCT/SE2021/050963 SE2021050963W WO2022075906A1 WO 2022075906 A1 WO2022075906 A1 WO 2022075906A1 SE 2021050963 W SE2021050963 W SE 2021050963W WO 2022075906 A1 WO2022075906 A1 WO 2022075906A1
Authority
WO
WIPO (PCT)
Prior art keywords
network node
information
path
control
network
Prior art date
Application number
PCT/SE2021/050963
Other languages
English (en)
Inventor
Min Wang
Antonino ORSINO
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2022075906A1 publication Critical patent/WO2022075906A1/fr

Links

Classifications

    • 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
    • H04W40/22—Communication route or path selection, e.g. power-based or shortest path routing using selective relaying for reaching a BTS [Base Transceiver Station] or an access point
    • 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/0231—Traffic management, e.g. flow control or congestion control based on communication conditions
    • H04W28/0236—Traffic management, e.g. flow control or congestion control based on communication conditions radio quality, e.g. interference, losses or delay
    • 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/0289—Congestion control
    • 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/248—Connectivity information update
    • 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
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • Embodiments herein relate to a network node, a requesting network node and methods performed therein regarding wireless communication. Furthermore, a computer program product and a computer-readable storage medium are also provided herein. Especially, embodiments herein relate to handling or enabling communication, e.g. handling communication involving a relaying User Equipment (UE) between a UE and a
  • UE User Equipment
  • UEs also known as wireless communication devices, mobile stations, stations (STA) and/or wireless devices,
  • the RAN covers a geographical area which is divided into service areas or cell areas, with each service area or cell area being served by network node such as an access node e.g. a Wi-Fi access point or a radio base station (RBS), which in some radio access technologies (RAT) may also be called, for example, a NodeB, an evolved NodeB
  • RAT radio access technologies
  • the service area or cell area is a geographical area where radio coverage is provided by the radio network node.
  • the radio network node operates on radio frequencies to communicate over an air interface with the wireless devices within range of the access node.
  • the radio network node communicates over a downlink (DL) to the wireless device and the wireless device communicates over an uplink
  • a Universal Mobile Telecommunications System is a third-generation telecommunication network, which evolved from the second generation (2G) Global System for Mobile Communications (GSM).
  • the UMTS terrestrial radio access network (UTRAN) is essentially a RAN using wideband code division multiple access (WCDMA)
  • HSPA High-Speed Packet Access
  • 3GPP Third Generation Partnership Project
  • telecommunications suppliers propose and agree upon standards for present and future generation networks and UTRAN specifically, and investigate enhanced data rate and radio capacity.
  • a controller node such as a radio network controller (RNC) or a base station controller (BSC), which supervises and coordinates various activities of the plural radio network nodes connected thereto.
  • RNCs are typically connected to one or more core networks.
  • the Evolved Packet System comprises the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), also known as the Long-Term Evolution (LTE) radio access network, and the Evolved Packet Core (EPC), also known as System Architecture Evolution (SAE) core network.
  • E-UTRAN also known as the Long-Term Evolution (LTE) radio access network
  • EPC also known as System Architecture Evolution (SAE) core network.
  • E-UTRAN/LTE is a 3GPP radio access technology wherein the radio network nodes are directly connected to the EPC core network.
  • the Radio Access Network (RAN) of an EPS has an essentially “flat” architecture comprising radio network nodes connected directly to one or more core networks.
  • transmit- and receive-antenna elements may utilize beamforming, such as transmitside and receive-side beamforming.
  • Transmit-side beamforming means that the transmitter can amplify the transmitted signals in a selected direction or directions, while suppressing the transmitted signals in other directions.
  • a receiver can amplify signals from a selected direction or directions, while suppressing unwanted signals from other directions.
  • NR uses Orthogonal Frequency Division Multiplexing (OFDM) in the downlink, i.e. , from a network node, gNB, eNB, or base station, to a UE.
  • OFDM Orthogonal Frequency Division Multiplexing
  • the basic NR physical resource over an antenna port can thus be seen as a time-frequency grid as illustrated in Fig. 1 , where a resource block (RB) in a 14-symbol slot is shown.
  • a resource block corresponds to 12 contiguous subcarriers in the frequency domain. Resource blocks are numbered in the frequency domain, starting with 0 from one end of the system bandwidth.
  • Each resource element corresponds to one OFDM subcarrier during one OFDM symbol interval.
  • Different subcarrier spacing values are supported in NR.
  • downlink and uplink transmissions in NR will be organized into equally-sized subframes of 1ms each, similar to LTE.
  • a subframe is further divided into multiple slots of equal duration.
  • Downlink transmissions are dynamically scheduled, i.e., in each slot the gNB transmits downlink control information (DCI) about which UE data is to be transmitted to and which resource blocks in the current downlink slot the data is transmitted on.
  • This control information is typically transmitted in the first one or two OFDM symbols in each slot in NR.
  • the control information is carried on the Physical Downlink Control Channel (PDCCH) and data is carried on the Physical Downlink Shared Channel (PDSCH).
  • PDCCH Physical Downlink Control Channel
  • PDSCH Physical Downlink Shared Channel
  • a UE first detects and decodes PDCCH and, if a PDCCH is decoded successfully, it then decodes the corresponding PDSCH based on the downlink assignment provided by decoded control information in the PDCCH.
  • SSB synchronization signal block
  • CSI channel state information
  • RS reference signal
  • Uplink data transmissions carried on Physical Uplink Shared Channel (PUSCH)
  • PUSCH Physical Uplink Shared Channel
  • the DCI which is transmitted in the DL region, always indicates a scheduling time offset so that the PUSCH is transmitted in a slot in the UL region.
  • Sidelink transmissions are direct communications between two UEs without signal relay through a base station.
  • Sidelink transmissions over NR are specified for release (Rel.) 16.
  • These are enhancements of the PROximity-based SErvices (ProSe) specified for LTE.
  • Four new enhancements are particularly introduced to NR sidelink transmissions as follows:
  • a physical sidelink feedback channel (PSFCH) is introduced for a receiver UE to reply the decoding status to a transmitter UE.
  • PSFCH physical sidelink feedback channel
  • PSSCH Physical Sidelink Shared Channel
  • UE Physical Sidelink Shared Channel
  • SIBs system information blocks
  • RRC radio resource control
  • SCI sidelink control information
  • PSFCH which is an SL version of PLICCH:
  • the PSFCH is transmitted by a sidelink receiver UE for unicast and groupcast, which conveys 1 bit information over 1 RB for the hybrid automatic repeat request (HARQ) acknowledgement (ACK) and the negative ACK (NACK).
  • HARQ hybrid automatic repeat request
  • NACK negative ACK
  • CSI channel state information
  • MAC medium access control
  • CE control element
  • PSCCH which is an SL version of PDCCH:
  • PSCCH which conveys a part of SCI, which is an SL version of DCI, to be decoded by any UE for the channel sensing purpose, including the reserved timefrequency resources for transmissions, demodulation reference signal (DMRS) pattern and antenna port, etc.
  • DMRS demodulation reference signal
  • S-PSS/S-SSS Similar to downlink transmissions in NR, in sidelink transmissions, primary and secondary synchronization signals, called S-PSS and S-SSS, respectively, are supported. Through detecting the S-PSS and S-SSS, a UE is able to identify the sidelink synchronization identity (SSID) from the UE sending the S-PSS/S-SSS. Through detecting the S-PSS/S-SSS, the UE is therefore able to know the characteristics of the UE transmitting the S-PSS/S-SSS. A series of process of acquiring timing and frequency synchronization together with SSIDs of UEs is called initial cell search.
  • SSID sidelink synchronization identity
  • the UE sending the S-PSS/S-SSS may not be necessarily involved in sidelink transmissions, and a node, such as a UE/eNB/gNB, sending the S-PSS/S- SSS is called a synchronization source.
  • a node such as a UE/eNB/gNB
  • sending the S-PSS/S- SSS is called a synchronization source.
  • PSBCH Physical Sidelink Broadcast Channel
  • the PSBCH is transmitted along with the S-PSS/S-SSS as a synchronization signal/PSBCH block (SSB).
  • the SSB has the same numerology as PSCCH/PSSCH on that carrier, and an SSB should be transmitted within the bandwidth of the configured bandwidth part (BWP).
  • the PSBCH conveys information related to synchronization, such as the direct frame number (DFN), indication of the slot and symbol level time resources for sidelink transmissions, in-coverage indicator, etc.
  • the SSB is transmitted periodically at every 160 ms.
  • DM RS phase tracking reference signal
  • CSI-RS CSI-RS
  • SCI sidelink control information
  • This a version of the DCI for SL is sent on the PSCCH.
  • This part is used for channel sensing purposes, including the reserved time-frequency resources for transmissions, demodulation reference signal (DM RS) pattern and antenna port, etc., and can be read by all UEs while the remaining, for example, second stage, scheduling and control information, such as, e.g., a 8-bits source identity (ID) and a 16-bits destination ID, New Data Indicator (NDI), redundancy version (RV) and HARQ process ID, is sent on the PSSCH to be decoded by the receiver UE.
  • ID 8-bits source identity
  • NDI New Data Indicator
  • RV redundancy version
  • NR sidelink transmissions have the following two modes of resource allocations:
  • Mode 1 Sidelink resources are scheduled by a gNB.
  • Mode 2 The UE autonomously selects sidelink resources from a (pre-)configured sidelink resource pool(s) based on the channel sensing mechanism.
  • a gNB can be configured to adopt Mode 1 or Mode 2.
  • Mode 2 For the out-of-coverage UE, only Mode 2 can be adopted.
  • Mode 1 supports the following two kinds of grants:
  • Dynamic grant When the traffic to be sent over sidelink arrives at a transmitter UE, this UE should launch the four-message exchange procedure to request sidelink resources from a gNB, e.g., scheduling request (SR) on UL, grant, buffer status report (BSR) on UL, grant for data on SL sent to UE.
  • a gNB may allocate a sidelink radio network temporary identifier (SL-RNTI) to the transmitter UE. If this sidelink resource request is granted by a gNB, then a gNB indicates the resource allocation for the PSCCH and the PSSCH in the DCI conveyed by PDCCH with cyclic redundancy check (CRC) scrambled with the SL-RNTI.
  • SR scheduling request
  • BSR buffer status report
  • a transmitter UE When a transmitter UE receives such a DCI, a transmitter UE can obtain the grant only if the scrambled CRC of DCI can be successfully solved by the assigned SL-RNTI. A transmitter UE then indicates the time-frequency resources and the transmission scheme of the allocated PSSCH in the PSCCH, and launches the PSCCH and the PSSCH on the allocated resources for sidelink transmissions.
  • a grant is obtained from a gNB
  • a transmitter UE can only transmit a single transport block (TB). As a result, this kind of grant is suitable for traffic with a loose latency requirement.
  • Configured grant For the traffic with a strict latency requirement, performing the four-message exchange procedure to request sidelink resources may induce unacceptable latency. In this case, prior to the traffic arrival, a transmitter UE may perform the four-message exchange procedure and request a set of resources. If a grant can be obtained from a gNB, then the requested resources are reserved in a periodic manner. Upon traffic arriving at a transmitter UE, this UE can launch the PSCCH and the PSSCH on the upcoming resource occasion. In fact, this kind of grant is also known as grant-free transmissions.
  • a sidelink receiver UE In both dynamic grant and configured grant, a sidelink receiver UE cannot receive the DCI, since it is addressed to the transmitter UE, and therefore a receiver UE should perform blind decoding to identify the presence of PSCCH and find the resources for the PSSCH through the SCI.
  • CRC is also inserted in the SCI without any scrambling.
  • this transmitter UE when traffic arrives at a transmitter UE, this transmitter UE should autonomously select resources for the PSCCH and the PSSCH. To further minimize the latency of the feedback HARQ ACK/NACK transmissions and subsequently retransmissions, a transmitter UE may also reserve resources for PSCCH/PSSCH for retransmissions. To further enhance the probability of successful TB decoding at one shot and thus suppress the probability to perform retransmissions, a transmitter UE may repeat the TB transmission along with the initial TB transmission. This mechanism is also known as blind retransmission. As a result, when traffic arrives at a transmitter UE, then this transmitter UE should select resources for the following transmissions:
  • a particular resource selection procedure may therefore be imposed to Mode 2 based on channel sensing.
  • the channel sensing algorithm involves measuring reference signal received power (RSRP) on different subchannels and requires knowledge of the different UEs power levels of DMRS on the PSSCH or the DMRS on the PSCCH, depending on the configuration. This information is known only after receiver SCI launched by (all) other UEs.
  • the sensing and selection algorithm is rather complex.
  • D2D device to device
  • the discovery procedure has two modes, mode A based on open announcements (broadcasts) and mode B, which is request/response.
  • the discovery mechanism is controlled by the application layer, such as ProSe.
  • the discovery message is sent on the Physical Sidelink Discovery Channel (PSDCH) which is not available in NR. Also, there is a specific resource pool for announcement and monitoring of discovery messages.
  • the discovery procedure can be used to detect UEs supporting certain services or applications before initiating direct communication.
  • L3 Layer 3 (L3) UE-to-Network relay.
  • the ProSe 5G UE-to-Network Relay entity provides the functionality to support connectivity to the network for Remote UEs, see Fig. 2. It can be used for both public safety services and commercial services, e.g., interactive service.
  • a UE is considered to be a Remote UE for a certain ProSe UE-to-Network relay if it has successfully established a PC5 link to this ProSe 5G UE-to-Network Relay.
  • a Remote UE can be located within NG-RAN coverage or outside of NG-RAN coverage.
  • PC5 communication herein means a device-to-device communication between the remote UE and the UE-to-Network Relay.
  • Fig. 2 shows architecture model using a ProSe 5G UE-to-Network Relay in Figure 6.6.1-1 in TR 23.752 [3],
  • the ProSe 5G UE-to-Network Relay shall relay unicast traffic, such as UL and DL, between the Remote UE and the network.
  • the ProSe UE-to-Network Relay shall provide generic function that can relay any IP traffic.
  • One-to-one Direct Communication is used between Remote UEs and ProSe 5G UE-to-Network Relays for unicast traffic as specified in solutions for Key Issue #2 in the TR 23.752 v0.3.0 [3],
  • the protocol stack for Layer-3 UE-to-Network Relays is shown in Fig. 3.
  • Fig. 3 shows protocol stack for ProSe 5G UE-to-Network Relay in Figure 6.6.1-2 TR 23.752 [3]
  • Hop-by-hop security is supported in the PC5 link and Uu link. If there are requirements beyond hop-by-hop security for protection of Remote UE's traffic, security over IP layer needs to be applied.
  • a ProSe 5G UE-to-Network Relay capable UE may register to the network (if not already registered) and establish a protocol data unit (PDU) session enabling the necessary relay traffic, or it may need to connect to additional PDU session(s) or modify the existing PDU session in order to provide relay traffic towards Remote UE(s).
  • PDU session(s) supporting UE-to-Network Relay shall only be used for Remote ProSe UE(s) relay traffic.
  • Fig. 4 shows ProSe 5G UE-to-Network Relay in Figure 6.6.2-1 in TR 23.752 [3],
  • Authorization and provisioning is performed for the ProSe UE-to-NW relay, see 0a, and Remote UE, see Ob.
  • Authorization and provisioning procedure may be any solution for key issue #1 and #3 in the TR 23.752 vO.3.0 [3],
  • the ProSe 5G UE-to-Network Relay may establish a PDU session for relaying with default PDU session parameters received in step Oa-b or pre-configured in the UE-to-NW relay, e.g., single-network slice selection assistance information (S-NSSAI), data network name (DNN), session and service continuity (SSC) mode.
  • S-NSSAI single-network slice selection assistance information
  • DNN data network name
  • SSC session and service continuity
  • IPv6 IPv6 prefix via prefix delegation function from the network as defined in TS 23.501 [4]
  • the Remote UE Based on the Authorization and provisioning in step Oa-b, the Remote UE performs discovery of a ProSe 5G UE-to-Network Relay using any solution for key issue #1 and #3 in the TR 23.752 v0.3.0 [2], As part of the discovery procedure the Remote UE learns about the connectivity service the ProSe UE-to-Network Relay provides. 3. The Remote UE selects a ProSe 5G UE-to-Network Relay and establishes a connection for One-to-one ProSe Direct Communication as described in TS 23.287 [5],
  • the ProSe 5G UE-to- Network Relay initiates a new PDU session establishment or modification procedure for relaying.
  • IPv6 prefix or IPv4 address is allocated for the remote UE as it is defined in TS 23.303 [6] clauses 5.4.4.2 and 5.4.4.3. From this point, the uplink and downlink relaying can start.
  • the ProSe 5G UE-to-Network Relay sends a Remote UE Report, Remote User ID, IP info, message to the session manager function (SMF) for the PDU session associated with the relay.
  • the Remote User ID is an identity of the Remote UE user, provided via User Info, that was successfully connected in step 3.
  • the SMF stores the Remote User IDs and the related IP info in the ProSe 5G UE-to-Network Relay's for the PDU connection associated with the relay.
  • the UE-to-network Relay shall report TCP/UDP port ranges assigned to individual Remote UE(s) (along with the Remote User ID); for IPv6, the UE-to-network Relay shall report IPv6 prefix(es) assigned to individual Remote UE(s) (along with the Remote User ID).
  • the Remote UE Report message shall be sent when the Remote UE disconnects from the ProSe 5G UE-to-Network Relay, e.g., upon explicit layer-2 link release or based on the absence of keep alive messages over PC5, to inform the SMF that the Remote UE(s) have left.
  • HPLMN Home public land mobile network
  • VPN Visiting PLMN
  • the ProSe 5G UE-to-Network Relay is authorised to operate, needs to support the transfer of the Remote UE related parameters in case the SMF is in the HPLMN.
  • the Remote UE After being connected to the ProSe 5G UE-to-Network Relay, the Remote UE keeps performing the measurement of the signal strength of the discovery message sent by the ProSe 5G UE-to-Network Relay for relay reselection.
  • the solution may also work when the ProSe 5G UE-to-Network Relay UE connects in EPS using LTE.
  • the Remote UE report the procedures defined in TS 23.303 [5] can be used.
  • L2 Layer 2 (L2) UE-to-Network relay
  • the protocol architecture supporting a layer 2 (L2) UE-to-Network Relay UE is provided.
  • the L2 UE-to-Network Relay UE provides forwarding functionality that can 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 can be located within NG-RAN coverage or outside of NG-RAN coverage.
  • Fig. 5 illustrates the protocol stack for the user plane transport, related to a PDU Session, including a Layer 2 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 Data Network (DN) over the PDU session.
  • DN Data Network
  • DN Data Network
  • DN Data Network
  • FIG. 5 shows User Plane Stack for L2 UE-to-Network Relay UE in Figure A.2.1-1 in TR 23.752 [3]
  • the adaptation relay layer within the UE-to-Network Relay UE can 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.
  • the definition of the adaptation relay layer is under the responsibility of RAN WG2.
  • Fig. 6 illustrates the protocol stack of the non-access stratum (NAS) connection for the Remote UE to the NAS-MM and NAS-SM components.
  • the NAS messages are transparently transferred between the Remote UE and 5G-AN over the Layer 2 UE-to- Network Relay UE using:
  • PDCP end-to-end connection where the role of the UE-to-Network Relay UE is to relay the PDUs over the signalling radio bear without any modifications.
  • AMF Access and Mobility Management Function
  • the role of the UE-to-Network Relay UE is to relay the PDUs from the signaling radio bearer without any modifications.
  • FIG. 6 shows Control Plane for L2 UE-to-Network Relay UE in Figure A.2.2-1 in TR 23.752 [3],
  • Fig. 7 shows Connection Establishment for Indirect Communication via UE-to- Network Relay UE in Figure 6.7.3-1 in TR 23.752 [3]:
  • the Remote UE and UE-to-Network Relay UE may independently perform the initial registration to the network according to registration procedures in TS 23.502 [8],
  • the allocated 5G Global Unique Temporary Identifier (GUTI) of the Remote UE is maintained when later NAS signalling between Remote UE and Network is exchanged via the UE-to-Network Relay UE.
  • GUI Global Unique Temporary Identifier
  • the Remote UE and UE-to-Network Relay UE independently get the service authorization for indirect communication from the network.
  • the Remote UE and UE-to-Network Relay UE perform UE-to-Network Relay UE discovery and selection.
  • Remote UE initiates a one-to-one communication connection with the selected UE-to-Network Relay UE over PC5, by sending an indirect communication request message to the UE-to-Network Relay.
  • the UE-to-Network Relay UE If the UE-to-Network Relay UE is in CM_IDLE state, triggered by the communication request received from the Remote UE, the UE-to-Network Relay UE sends a Service Request message over PC5 to its serving AMF.
  • the UE-to-Network Relay UE's AMF may perform authentication of the UE- to-Network Relay UE based on NAS message validation and, if needed, the AMF will check the subscription data. If the UE-to-Network Relay UE is already in CM_CONNECTED state and is authorised to perform Relay service, then step 5 is omitted.
  • the UE-to-Network Relay UE sends the indirect communication response message to the Remote UE.
  • Remote UE sends a NAS message to the serving AMF.
  • the NAS message is encapsulated in an RRC message that is sent over PC5 to the UE-to-Network Relay UE, and the UE-to-Network Relay UE forwards the message to the NG-RAN.
  • the NG- RAN derives Remote UE's serving AMF and forwards the NAS message to this AMF.
  • the NAS message is initial registration message. Otherwise, the NAS message is service request message.
  • the Remote UE's serving AMF may perform authentication of the Remote UE based on NAS message validation and if needed the Remote UE's AMF checks the subscription data.
  • Remote UE may trigger the PDU Session Establishment procedure as defined in clause 4.3.2.2 of TS 23.502 [8],
  • the data is transmitted between Remote UE and UPF via UE-to-Network Relay UE and NG-RAN.
  • the UE-to-Network Relay UE forwards all the data messages between the Remote UE and NG-RAN using RAN specified L2 relay method.
  • BAP Backhaul adaptation protocol
  • the BAP sublayer supports the following functions:
  • Routing of packets to next hop Differentiating traffic to be delivered to upper layers from traffic to be delivered to egress link;
  • the BAP Control PDU is used to convey one of the following in addition to the PDU header: flow control feedback per BH RLC channel; flow control feedback per BAP routing ID; flow control polling;
  • Fig. 8 shows the formats of the BAP Control PDU for flow control feedback in Fig 6.2.3.1-1 in TS 38.340.
  • Fig. 8 shows BAP Control PDU format for flow control feedback per BH RLC channel in TS 38.340 [11]
  • Fig. 9 shows BAP Control PDU format for flow control feedback per BAP routing ID in Figure 6.2.3.1-2 in TS 38.340 [11],
  • Fig. 10 shows the formats of the BAP Control PDU for flow control polling, or Fig. 10 shows BAP Control PDU format for flow control feedback polling in Figure 6.2.3.2-1 in TS 38.340 [11],
  • Fig. 11 shows the format of the BAP Control PDU for BH RLF indication.
  • Fig. 11 shows BAP Control PDU format for BH RLF indication in Figure 6.2.3.3-1: TS 38.340 [11],
  • sidelink (SL) based UE-to-network (U2N) relay and UE to UE (U2U) relay will be studied in the scope.
  • the study will also consider forward compatibility, i.e. , the solution may be easily extended to be applicable for multihop relay.
  • Remote UE may also operate as a relay UE for other remote UEs.
  • control PDUs are beneficial to apply since they make it feasible for any node on a path to quickly distribute path status information to other nodes on the same path.
  • control PDU based signalling alternative also gives lower signalling overhead.
  • the adaptation layer is one important design component for L2 relay based relay mechanism, and below issues may be considered:
  • An object of embodiments herein is to provide a mechanism that improves the performance in the wireless communication network using relay UEs.
  • the object is achieved by providing a method performed by a network node for communicating over a path comprising a remote UE, a relay UE, and a radio network node in a wireless communication network.
  • the network node transmits one or more control PDlls in the adaptation layer to distribute information related to the path, to one or more other network nodes in the wireless communication network.
  • the one or more control PDUs comprise information reflecting at least one of the following: Congestion status; QoS satisfaction status; radio link monitoring (RLM) status; Mobility status; Topology upgradation information; Any failure event indicator/cause on any of the above status information; Available PC5 measurements; Available Uu measurements; Location information and/or Information to enable/disable a certain action or configuration.
  • a method performed by a network node for communicating over a path comprising a remote UE, a relay UE, and a radio network node in a wireless communication network.
  • the network node may transmit, generate or apply one or multiple control PDUs in the adaptation layer to distribute information related to the path, to other network nodes in the wireless communication network.
  • the control PDUs reflect path status e.g.
  • Congestion status at least one of the below information: Congestion status; QoS satisfaction status; RLM status; Mobility status; Topology upgradation information; Any failure event indicator/cause on any of the above status information; Available PC5 measurements, if available; Available Uu measurements, if available; Location information; Information to enable/disable a certain action or configuration.
  • the object is achieved by providing a method performed by a requesting network node for communicating over a path comprising a remote UE, a relay UE, and a radio network node in a wireless communication network.
  • the requesting network node receives one or more control PDUs in the adaptation layer to distribute information related to the path, from a network node in the wireless communication network.
  • the one or more control PDUs comprise information reflecting at least one of the following: Congestion status; QoS satisfaction status; RLM status; Mobility status; Topology upgradation information; Any failure event indicator/cause on any of the above status information; Available PC5 measurements; Available llu measurements; Location information and/or Information to enable/disable a certain action or configuration.
  • a method performed by a requesting network node, such as a remote UE, or a relay UE, for communicating over a path comprising a remote UE, a relay UE and a radio network node in a wireless communication network.
  • the requesting network node receives one or multiple control PDUs in the adaptation layer to distribute information related to the path, to other network nodes in the wireless communication network.
  • the control PDUs reflect path status, e.g.
  • Congestion status at least one of the below information: Congestion status; QoS satisfaction status; RLM status; Mobility status; Topology upgradation information; Any failure event indicator/cause on any of the above status information; Available PC5 measurements, if available; Available Uu measurements, if available; Location information; Information to enable/disable a certain action or configuration.
  • the object is achieved by providing a network node, and a requesting network node configured to perform the methods herein, respectively.
  • a network node for communicating over a path comprising a remote UE, a relay UE, and a radio network node in a wireless communication network.
  • the network node is configured to transmit one or more control PDUs in the adaptation layer to distribute information related to the path, to one or more other network nodes in the wireless communication network.
  • the one or more control PDUs comprise information reflecting at least one of the following: Congestion status; QoS satisfaction status; RLM status; Mobility status; Topology upgradation information; Any failure event indicator/cause on any of the above status information; Available PC5 measurements; Available Uu measurements; Location information and/or Information to enable/disable a certain action or configuration.
  • a requesting network node for communicating over a path comprising a remote UE, a relay UE, and a radio network node in a wireless communication network.
  • the requesting network node is configured to receive one or more control PDUs, in the adaptation layer to distribute information related to the path, from a network node in the wireless communication network, wherein the one or more control PDUs comprise information reflecting at least one of the following: congestion status; QoS satisfaction status; RLM status; Mobility status; Topology upgradation information; Any failure event indicator/cause on any of the above status information; Available PC5 measurements; Available llu measurements; Location information and/or Information to enable/disable a certain action or configuration.
  • a computer program product comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out any of the methods above, as performed by the network node or the requesting network node, respectively.
  • a computer- readable storage medium having stored thereon a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any of the methods above, as performed by the network node or the requesting network node, respectively.
  • Embodiments herein propose, for example, for a path involving at least one source remote UE, and one relay UE, that any node, i.e. the network node, in the path may apply one or more control PDlls in the adaptation layer to distribute information related to the path, to other network nodes.
  • the control PDlls reflect at least one of the below information
  • the information may be relevant to a single hop or multiple hops of the path.
  • the information may be per node, per radio bearer, per service, per application or per RLC channel, or per logical channel, or per destination. It is herein proposed a control PDU in the adaptation layer so that the network node on a path involving at least one source remote UE and one relay UE, can distribute status information on the path fast.
  • the network node avoids using upper layer signaling such as RRC to distribute information along the path. This can reduce control signaling overhead and thus efficiently improve performance of the wireless communication network.
  • Fig. 1 illustrates a time-frequency grid showing a basic NR physical resource over an antenna port
  • Fig. 2 illustrates a ProSe 5G UE-to-Network Relay entity that provides a functionality to support connectivity to the network for Remote UEs;
  • Fig. 3 illustrates a protocol stack for Layer-3 UE-to-Network Relays
  • Fig. 4 illustrates ProSe 5G UE-to-Network Relay
  • Fig. 5 illustrates a protocol stack for a user plane transport
  • Fig. 6 illustrates a protocol stack of the non-access stratum (NAS) connection for a Remote UE to NAS-MM and NAS-SM components;
  • NAS non-access stratum
  • Fig. 7 illustrates connection establishment for Indirect Communication via UE-to-Network Relay UE
  • Fig. 8 illustrates a formats of the BAP Control PDU for flow control feedback
  • Fig. 9 illustrates BAP Control PDU format for flow control feedback per BAP routing ID
  • Fig. 10 illustrates BAP Control PDU format for flow control feedback polling
  • Fig. 12 is a schematic overview depicting a wireless communication network according to embodiments herein;
  • Fig. 13 is a combined signalling scheme and flowchart according to embodiments herein;
  • Fig. 14 is a block diagram depicting a method in a network node according to embodiments herein;
  • Fig. 15 is a block diagram depicting a method in a requesting network node according to embodiments herein;
  • Fig. 16 is a block diagram depicting network nodes according to embodiments herein;
  • Fig. 17 is a block diagram depicting requesting network nodes according to embodiments herein;
  • Fig. 18 schematically illustrates a telecommunication network connected via an intermediate network to a host computer;
  • Fig. 19 is a generalized block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection; and Figs. 20, 21 , 22, and 23 are flowcharts illustrating methods implemented in a communication system including a host computer, a base station, and a user equipment.
  • Embodiments herein are described within the context of 3GPP NR radio technology (3GPP TS 38.300 V15.2.0 (2018-06)). It is understood that the problems and solutions described herein are equally applicable to wireless access networks and userequipments (UEs) implementing other access technologies and standards.
  • NR is used as an example technology where embodiments are suitable, and using NR in the description therefore is particularly useful for understanding the problem and solutions solving the problem.
  • embodiments are applicable also to 3GPP LTE, or 3GPP LTE and NR integration, also denoted as non-standalone NR.
  • Embodiments herein relate to wireless communication networks in general.
  • Fig. 12 is a schematic overview depicting a wireless communication network 1.
  • the wireless communication network 1 comprises one or more RANs and one or more CNs.
  • the wireless communication network 1 may use one or a number of different technologies, such as Wi-Fi, NR, Long Term Evolution (LTE), LTE-Advanced, Fifth Generation (5G), Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications/enhanced Data rate for GSM Evolution (GSM/EDGE), Worldwide Interoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations.
  • Embodiments herein relate to recent technology trends that are of particular interest in a 5G context, however, embodiments are also applicable in further development of the existing wireless communication systems such as e.g. WCDMA and LTE.
  • wireless devices e.g. a UE 10, also denoted as a source remote UE or remote UE 10, such as a mobile station, a non-access point (non-AP) STA, a STA, a user equipment and/or a wireless terminal, communicate via one or more Access Networks (AN), e.g. RAN, to one or more core networks (CN).
  • AN e.g. RAN
  • CN core networks
  • UE is a non-limiting term which means any terminal, wireless communication terminal, user equipment, Machine Type Communication (MTC) device, Device to Device (D2D) terminal, or node e.g. smart phone, laptop, mobile phone, sensor, relay, mobile tablets or even a small base station capable of communicating using radio communication with a network node within an area served by the network node.
  • MTC Machine Type Communication
  • D2D Device to Device
  • the wireless communication network 1 comprises a radio network node 12 providing radio coverage over a geographical area, a first service area 11, of a radio access technology (RAT), such as LTE, Wi-Fi, WiMAX or similar.
  • the radio network node 12 may be a transmission and reception point e.g. a radio network node such as a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP ST A), an access node, an access controller, a base station, e.g.
  • WLAN Wireless Local Area Network
  • AP ST A Access Point Station
  • a radio base station such as a NodeB, an evolved Node B (eNB, eNode B), a gNodeB (gNB), a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a transmission arrangement of a radio base station, a stand-alone access point or any other network unit or node capable of communicating with a UE within the area served by the radio network node 12 depending e.g. on the radio access technology and terminology used.
  • the radio network node 12 may alternatively or additionally be a controller node or a packet processing node such as a radio controller node or similar. It should be noted that a service area may be denoted as cell, beam, beam group or similar to define an area of radio coverage.
  • the wireless communication network 1 further comprises a relay UE 13 communicating with the radio network node 12 and the remote UE 10.
  • the radio network node 12 may be referred to as a serving network node wherein the first cell may be referred to as a serving cell or primary cell, and the serving network node communicates with the relay UE 13 in form of DL transmissions to the relay UE 13 and UL transmissions from the relay UE 13.
  • the relay UE 13 communicates with the source remote UE 10.
  • Embodiments herein relate to communication over a path comprising at least the remote UE 10, the relay UE 13, and the radio network node 12 in the wireless communication network. Any node along the path generates or applies one or more control PDUs in the adaptation layer to distribute information related to the path, to other network nodes in the wireless communication network.
  • the control PDUs comprises an indication of one or more of the below information:
  • At least one of the below information field may be included in the medium access control (MAC) control element (CE) payload.
  • MAC medium access control
  • CE control element
  • QoS information field such as packet delay budget per flow, per logical channel, per service etc.
  • QoS information field such as number of transmitted or received packets, number of lost packets, number of delayed packets etc.
  • Congestion indicator such as no congestion, congested. One indicator indicates that there is no congestion risk. Another indicator indicates that there is a congestion detected. Another indicator indicates that the detected congestion is resolved.
  • Load information Depending on definition of the load, the load information could be reflected by any load metric.
  • RLM and/or RLF measurement results including lower layer and/or higher measurement results, in sync, or out of sync indicators, beam failure indicators etc.
  • the embodiments are described in the context of NR, i.e. , remote UE and relay UE are deployed in a same NR cell or different NR cells.
  • the embodiments are also applicable to other relay scenarios including UE to network relay or UE to UE relay where the link between remote UE and relay UE may be based on LTE sidelink or NR sidelink, the Uu connection between relay UE and base station may be LTE Uu or NR Uu.
  • a relay scenario containing multiple relay hops is also covered.
  • the connection between remote UE 10 and relay UE 13 is also not limited to sidelink. Any short-range communication technology such as Wifi is equally applicable.
  • any grant issued by the gNB is for a sidelink transmission between two UEs.
  • the embodiments are also applicable to a relay scenario where the relay UE 13 is configured with multiple connections, i.e., the number of connections is equal or larger than two, to the RAN, e.g., dual connectivity (DC), carrier aggregation (CA), etc.
  • DC dual connectivity
  • CA carrier aggregation
  • control PDUs are discussed in context of layer two (L2) relay, the embodiments are not limited to L2 relay, they are also applicable to layer three (L3) relay mechanisms in case adaptation layer is configured.
  • Radio network node can be substituted with “transmission point”. Distinction between the transmission points (TPs) may typically be based on reference signals (RS) or different synchronization signals transmitted. Several TPs may be logically connected to the same radio network node but if they are geographically separated, or are pointing in different propagation directions, the TPs may be subject to the same mobility issues as different radio network nodes. In subsequent sections, the terms “radio network node” and “TP” can be thought of as interchangeable.
  • Embodiments herein disclose a network node such as the remote UE 10, the relay UE 13, or the radio network node 12 that applies one or more control PDUs in the adaptation layer to distribute information related to the path, to other network nodes.
  • the control PDUs reflect at least one of the below information: • Congestion status.
  • the information may be relevant to a single hop or multiple hops of the path.
  • the information may be per node, per radio bearer, per service, per application or per RLC channel, or per logical channel, or per destination.
  • At least one of the below information field may be included in the MAC CE payload:
  • QoS information field such as packet delay budget per flow, per logical channel, per service etc.
  • QoS information field such as number of transmitted or received packets, number of lost packets, number of delayed packets etc.
  • Congestion indicator such as no congestion, congested. One indicator indicates that there is no congestion risk. Another indicator indicates that there is a congestion detected. Another indicator indicates that the detected congestion is resolved.
  • Load information Depending on definition of the load, the load information could be reflected by any load metric.
  • RLM and/or RLF measurement results including lower layer and/or higher measurement results, in sync, or out of sync indicators, beam failure indicators etc.
  • control PDlls there may be a field defined in the PDU to indicate the type or purpose of the control PDU.
  • one control PDU may carry status information for more than one types or purposes, in this case, multiple fields indicating types or purposes may be included in the control PDU.
  • a bitmap field may be included in a control PDU to reduce the control signaling overhead.
  • the bitmap field comprises multiple bits, and each bit is associated with a specific control PDU type. The bit is set to the value “1” indicating presence of the corresponding type of status information in the PDU, while the bit is set to the value “0” indicating absence of the corresponding type of status information in the PDU.
  • a network node e.g. the requesting network node such as the remote UE 10, the relay UE 13, or the radio network node 12, on the path may send a request or polling message along the path, to trigger information reporting from another network node on the path.
  • a request or polling message may trigger report message by one or multiple intended network nodes on the path.
  • a request or polling message may trigger report message from all network nodes (may excluding initiating network node) on the path.
  • the request/polling message and/or report message may be carried by a specific type of control PDU.
  • a requesting network node can send a request or polling message using a control PDU, while a receiving node, i.e. the network node, may reply with the report message using a control PDU.
  • a network node on the path may aggregate or summarize all received control PDUs on status information from different reporting nodes, and may generate an aggregated control PDU, which carries aggregated information, this may be valid only if a destination node of the control PDU is the same. In this way, the control signaling overhead due to transmission of control PDUs can be minimized.
  • source addresses or IDs of all reporting nodes may be included, so that the receiving node would be able to understand that the summarized information was based on what sources.
  • multiple control PDU needs to be sent they can be multiplexed one after another using the grant received and the available transport blocks are big enough to carry them (this may be valid if the destination node of the control PDU is the same or different).
  • a retransmission timer may be defined for triggering retransmission of a control PDU.
  • the network node that initiates transmission of the control PDU may start the timer after each transmission/retransmission of the control PDU. After the timer is expired, if the network node did not receive acknowledgement, response or report message from the intended node, the initiating network node may retransmit the control PDU again. The timer can be stopped if the initiating node has received acknowledgement, response or report message from the intended node.
  • a prohibit timer may be defined for preventing a network node to transmit or retransmit a same (type of) control PDU too frequently.
  • the network node that initiates transmission of a control PDU can start the timer after each transmission/retransmission of the control PDU. While the prohibit timer is running, the network node cannot transmit/retransmit the same (type of) control PDU again.
  • the prohibit timer may be stopped if the initiating network node has received acknowledgement, response or report message from the intended receiving network node. After the prohibit timer is expired, the initiating network node may send the same (type of) control PDU again.
  • a maximum number of transmissions/retransmissions for the control PDU may be defined, in case the network node has transmitted/retransmitted the control PDU for the maximum number of times, however, the network node has not received any acknowledgement, response or report message from the intended receiving node.
  • the network node may trigger a failure indicator indicating the corresponding link or hop or path has the failure so that the connection is broken.
  • the network node may also send a report message to other nodes (e.g., gNB) on the path.
  • the maximum number of transmission/retransmissions may be also applicable to a data PDU.
  • an additional timer may be defined for limiting maximum number retransmissions for a control or data PDU.
  • the additional timer may be started after first transmission of the PDU. In case the transmission has been responded by at least one of the intended nodes, the additional timer may be stopped. When the additional timer is expired, the network node may trigger a failure indicator indicating the corresponding link or hop or path has the failure so that the connection is broken. The network node may also send a report message to other nodes (e.g., gNB) on the path.
  • gNB node
  • a network node on a path may choose to use upper layer signaling (such as, e.g., RRC) to request/poll/report certain status information of the path.
  • the network node may make the choice by itself, depending on a status information category or requirement.
  • the network node may request/poll/report status information which requires short latency using a control PDU.
  • the network node may request/poll/report status information which does not require short latency using an upper layer signaling, such as RRC.
  • the network node may request/poll/report status information which does not require high security using a control PDU.
  • the network node may request/poll/report status information which require high security using an upper layer signaling, such as RRC.
  • an upper layer signaling such as RRC.
  • the signaling alternative using a control PDU or an upper layer signaling or both, is configured by a gNB or a controlling node (e.g., a relay node).
  • a precedence order may be configured or predefined in a spec so that the network node knows whether control PDU or upper layer signaling should be prioritized in case the network node receives both at the same time or within a time window.
  • Fig. 13 is a combined flowchart and signalling scheme according to embodiments herein. The actions may be performed in any suitable order.
  • the relay UE 13 being an example of the requesting network node, may request the remote UE 10 to send a control PDU for the path.
  • the remote UE 10 generates the control PDU in the adaptation layer to distribute information related to the path, to the relay UE 13.
  • the remote UE 10 transmits the control PDU in the adaptation layer to the relay UE 13.
  • the method actions performed by the network node, such as the remote UE 10 or the relay UE 13 or the radio network node 12 for communicating over a path comprising the remote UE 10, the relay UE 13, and the radio network node 12 in the wireless communication network will now be described with reference to a flowchart depicted in Fig. 14.
  • the actions do not have to be taken in the order stated below, but may be taken in any suitable order. Actions performed in some embodiments are marked with dashed boxes.
  • the network node may receive a request or a polling message to trigger information reporting to another network node on the path.
  • the request may be indicated in a control PDU.
  • the network node may apply the one or more control PDlls in the adaptation layer to distribute information related to the path.
  • the network node may generate or apply one or multiple control PDlls in the adaptation layer to distribute information related to the path, to other network nodes in the wireless communication network.
  • the one or more control PDlls may comprise one or more fields to indicate one or more types or purposes of the one or more control PDUs.
  • there are multiple types of control PDUs that are defined for indicating different status information there may be a field defined in the PDU to indicate the type or purpose of the control PDU.
  • one control PDU may carry status information for more than one type or purpose. In this case, multiple fields indicating types or purposes may be included in the control PDU.
  • the information may be included in a MAC CE payload.
  • the network node transmits one or more control PDUs in the adaptation layer to distribute information related to the path, to one or more other network nodes in the wireless communication network.
  • the one or more control PDUs comprise information reflecting at least one of the following:
  • MAC medium access control
  • CE control element
  • QoS information field such as packet delay budget per flow, per logical channel, per service etc.
  • QoS information field such as number of transmitted or received packets, number of lost packets, number of delayed packets etc.
  • Congestion indicator such as no congestion, congested. One indicator indicates that there is no congestion risk. Another indicator indicates that there is a congestion detected. Another indicator indicates that the detected congestion is resolved.
  • Load information Depending on definition of the load, the load information could be reflected by any load metric.
  • RLM and/or RLF measurement results including lower layer and/or higher measurement results, in sync, or out of sync indicators, beam failure indicators etc.
  • the network node may initiate a timer, which may be a retransmission timer or a prohibit timer.
  • the timer may be a retransmission timer that may be defined for triggering retransmission of a control PDU.
  • the network node that initiates transmission of the control PDU may start the timer after each transmission/retransmission of the control PDU. After the timer is expired, if the network node did not receive acknowledgement, a response or report message from the intended node, the initiating network node may retransmit the control PDU again.
  • the timer can be stopped if the initiating node has received an acknowledgement, response or report message from the intended node.
  • the prohibit timer may be defined for preventing the network node to transmit or retransmit a same (type of) control PDU too frequently.
  • the network node that initiates transmission of the control PDU can start the prohibit timer after each transmission/retransmission of the control PDU. While the prohibit timer is running, the network node cannot transmit/retransmit the same (type of) control PDU again.
  • the prohibit timer may be stopped if the initiating network node has received acknowledgement, response or report message from the intended receiving network node. After the prohibit timer is expired, the initiating network node may send the same (type of) control PDU again.
  • the timer may be stopped if the network node has received acknowledgement, response or report message from the one or more other network nodes; and/or after the timer is expired, the network node may send the same control PDU again.
  • the network node may receive a confirmation, acknowledgement, response or report message from the intended receiving network node, such as the requesting network node.
  • the method actions performed by the requesting network node such as the remote UE 10 or the relay UE 13 or the radio network node 12 for communicating over the path comprising the remote UE 10, the relay UE 13, and the radio network node 12 in the wireless communication network will now be described with reference to a flowchart depicted in Fig. 15.
  • the actions do not have to be taken in the order stated below, but may be taken in any suitable order. Actions performed in some embodiments are marked with dashed boxes.
  • the requesting network node may transmit the request or the polling message to trigger information reporting to the network node on the path, or any other network node on the path.
  • the request may be indicated in a control PDU.
  • the requesting network node receives the one or more control PDUs in the adaptation layer to distribute information related to the path, from the network node, such as another UE or a relay UE, in the wireless communication network.
  • the control PDUs reflect (comprise indication of) at least one of the below information, thus, the one or more control PDUs comprise information reflecting at least one of the following: • Congestion status
  • the requesting network node may aggregate or summarize all received control PDlls on status information from different reporting network nodes if a destination node of the control PDlls is the same. Thus, the requesting network node may generate an aggregated control PDU, which carries aggregated information, this may be valid only if the destination node of the control PDU is the same.
  • the requesting network node may then transmit the aggregated control PDU to another network node. In this way, the control signaling overhead due to transmission of control PDUs can be minimized.
  • source addresses or IDs of all reporting nodes may be included, so that a receiving node would be able to understand that the aggregated or summarized information was based on what sources.
  • Action 1505. Alternatively, if multiple control PDUs need to be sent, they can be multiplexed one after another using the grant received and the available transport blocks are big enough to carry them (this may be valid if the destination node of the control PDU is the same or different). Thus, the requesting network node may multiplex multiple control PDUs one after another using a grant received and available transport blocks that are big enough to carry them.
  • the requesting network node may transmit the confirmation, acknowledgement, response or report message from the intended receiving network node.
  • Fig. 16 is a block diagram depicting the network node such as the remote UE, the relay UE, or a radio network node for communicating over a path comprising the remote UE 10, the relay UE 13, and the radio network node 12 in the wireless communication network according to embodiments herein.
  • the network node may comprise processing circuitry 1601 , e.g. one or more processors, configured to perform the methods herein.
  • the network node may comprise a receiving unit 1602, e.g. a receiver or a transceiver.
  • the network node, the processing circuitry 1601 , and/or the receiving unit 1602 may be configured to receive the request or polling message to trigger information reporting to another network node on the path.
  • the request may be indicated in a control PDU.
  • the network node may comprise a generating unit 1603.
  • the network node, the processing circuitry 1601, and/or the generating unit 1603 may be configured to apply the one or more control PDlls in the adaptation layer to distribute information related to the path. For example, generate or apply the one or multiple control PDlls in the adaptation layer to distribute information related to the path, to other network nodes in the wireless communication network.
  • the one or more control PDlls may comprise one or more fields to indicate one or more types or purposes of the one or more control PDUs. In case that there are multiple types of control PDUs that are defined for indicating different status information, there may be a field defined in the PDU to indicate the type or purpose of the control PDU. Alternatively, one control PDU may carry status information for more than one types or purposes, in this case, multiple fields indicating types or purposes may be included in the control PDU.
  • the information may be included in a MAC CE payload.
  • the network node may comprise a transmitting unit 1604, e.g. a transmitter or a transceiver.
  • the network node, the processing circuitry 1601, and/or the transmitting unit 1604 is configured to transmit the one or more control PDUs in the adaptation layer to distribute information related to the path, to one or more other network nodes in the wireless communication network.
  • the one or more control PDUs comprise information reflecting (comprise indication of) at least one of the following:
  • MAC medium access control
  • CE control element
  • QoS information field such as packet delay budget per flow, per logical channel, per service etc.
  • QoS information field such as number of transmitted or received packets, number of lost packets, number of delayed packets etc.
  • Congestion indicator such as no congestion, congested. One indicator indicates that there is no congestion risk. Another indicator indicates that there is a congestion detected. Another indicator indicates that the detected congestion is resolved.
  • Load information Depending on definition of the load, the load information could be reflected by any load metric.
  • RLM and/or RLF measurement results including lower layer and/or higher measurement results, in sync, or out of sync indicators, beam failure indicators etc.
  • the network node may comprise a timing unit 1605, e.g. a timer.
  • the network node, the processing circuitry 1601, and/or the timing unit 1605 may be configured to initiate the timer or the prohibit timer.
  • the timer may be a retransmission timer that may be defined for triggering retransmission of a control PDU.
  • the network node that initiates transmission of the control PDU may start the timer after each transmission/retransmission of the control PDU. After the timer is expired, if the network node did not receive acknowledgement, response or report message from the intended node, the initiating network node may retransmit the control PDU again.
  • the timer can be stopped if the initiating node has received acknowledgement, response or report message from the intended node.
  • the prohibit timer may be defined for preventing the network node to transmit or retransmit a same (type of) control PDU too frequently.
  • the network node that initiates transmission of the control PDU can start the prohibit timer after each transmission/retransmission of the control PDU. While the prohibit timer is running, the network node cannot transmit/retransmit the same (type of) control PDU again.
  • the prohibit timer may be stopped if the initiating network node has received acknowledgement, response or report message from the intended receiving network node. After the prohibit timer is expired, the initiating network node may send the same (type of) control PDU again.
  • the timer may be stopped if the network node has received acknowledgement, response or report message from the one or more other network nodes; and/or after the timer is expired, the network node may send the same control PDU again.
  • the network node, the processing circuitry 1601, and/or the receiving unit 1602 may be configured to receive the confirmation, acknowledgement, response or report message from the intended receiving network node, such as the requesting network node.
  • the network node further comprises a memory 1606.
  • the memory comprises one or more units to be used to store data on, such as indications, control PDUs, requests, RSs, strengths or qualities, UL grants, indications, requests, commands, timers, applications to perform the methods disclosed herein when being executed, and similar.
  • the network node may comprise the processing circuitry and the memory, said memory comprising instructions executable by said processing circuitry whereby said network node is operative to perform the methods herein.
  • the network node comprises a communication interface 1609 comprising e g. one or more antennas.
  • the methods according to the embodiments described herein for the network node are respectively implemented by means of e.g. a computer program product 1607 or a computer program, comprising instructions, i.e. , software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the network node.
  • the computer program product 1607 may be stored on a computer-readable storage medium 1608, e g. a universal serial bus (USB) stick, a disc or similar.
  • the computer-readable storage medium 1608, having stored thereon the computer program product may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the network node.
  • the computer-readable storage medium may be a non-transitory or a transitory computer-readable storage medium.
  • Fig. 17 is a block diagram depicting the requesting network node, such as the remote UE, the relay UE, or the radio network node, for communicating over the path comprising the remote UE 10, the relay UE 13, and the radio network node 12 in the wireless communication network.
  • the requesting network node such as the remote UE, the relay UE, or the radio network node
  • the requesting network node may comprise processing circuitry 1701 , e.g. one or more processors, configured to perform the methods herein.
  • processing circuitry 1701 e.g. one or more processors, configured to perform the methods herein.
  • the requesting network node may comprise a transmitting unit 1702, e.g. a transmitter or a transceiver.
  • the requesting network node, the processing circuitry 1701 and/or the transmitting unit 1702 may be configured to transmit the request or polling message to trigger information reporting to the network node on the path, or any other network node on the path.
  • the request may be indicated in a control PDU.
  • the requesting network node may comprise a receiving unit 1703, e.g. a receiver or a transceiver.
  • the requesting network node, the processing circuitry 1701 and/or the receiving unit 1702 is configured to receive the one or more control PDUs in the adaptation layer to distribute information related to the path, from the network node, such as another UE or a relay UE, in the wireless communication network.
  • the control PDUs reflect (comprise indication of) at least one of the below information, thus, the one or more control PDUs comprise information reflecting at least one of the following:
  • the requesting network node may comprise an aggregating unit 1704.
  • the requesting network node, the processing circuitry 1701 and/or the aggregating unit 1704 may be configured to aggregate or summarize all received control PDlls on status information from different reporting network nodes if the destination node of the control PDlls is the same, and may generate an aggregated control PDU, which carries aggregated information, this may be valid only if the destination node of the control PDU is the same.
  • the requesting network node, the processing circuitry 1701 and/or the transmitting unit 1702 may be configured to transmit the aggregated control PDU to another network node. In this way, the control signaling overhead due to transmission of control PDUs can be minimized.
  • source addresses or IDs of all reporting nodes may be included, so that the receiving node would be able to understand that the aggregated or summarized information was based on what sources.
  • control PDU needs to be sent, they can be multiplexed one after another using the grant received and the available transport blocks are big enough to carry them, this may be valid if the destination node of the control PDU is the same or different.
  • the requesting network node, the processing circuitry 1701 and/or the transmitting unit 1702 may be configured to multiplex multiple control PDUs one after another using the grant received and available transport blocks that are big enough to carry them.
  • the requesting network node, the processing circuitry 1701 and/or the transmitting unit 1702 may be configured to transmit the confirmation, acknowledgement, response or report message from the intended receiving network node.
  • the requesting network node further comprises a memory 1705.
  • the memory comprises one or more units to be used to store data on, such as indications, control PDUs, strengths or qualities, grants, scheduling information, timers, applications to perform the methods disclosed herein when being executed, and similar.
  • the requesting network node comprises a communication interface 1708 comprising e.g. transmitter, receiver, transceiver and/or one or more antennas.
  • the methods according to the embodiments described herein for the requesting network node are respectively implemented by means of e.g. a computer program product 1706 or a computer program product, comprising instructions, i.e., software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the requesting network node.
  • the computer program product 1706 may be stored on a computer- readable storage medium 1707, e.g. a USB stick, a disc or similar.
  • the computer- readable storage medium 1707, having stored thereon the computer program product may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the requesting network node.
  • the computer-readable storage medium may be a non-transitory or transitory computer-readable storage medium.
  • radio network node can correspond to any type of radio network node or any network node, which communicates with a wireless device and/or with another network node.
  • network nodes are NodeB, Master eNB, Secondary eNB, a network node belonging to Master cell group (MCG) or Secondary Cell Group (SCG), base station (BS), multistandard radio (MSR) radio node such as MSR BS, eNodeB, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU), Remote Radio Head (RRH), nodes in distributed antenna system (DAS), core network node e.g.
  • Mobility Switching Centre MSC
  • MME Mobile Management Entity
  • O&M Operation and Maintenance
  • OSS Operation Support System
  • SON Self-Organizing Network
  • positioning node e.g. Evolved Serving Mobile Location Centre (E-SMLC), Minimizing Drive Test (MDT) etc.
  • E-SMLC Evolved Serving Mobile Location Centre
  • MDT Minimizing Drive Test
  • wireless device or user equipment refers to any type of wireless device communicating with a network node and/or with another UE in a cellular or mobile communication system.
  • UE refers to any type of wireless device communicating with a network node and/or with another UE in a cellular or mobile communication system.
  • Examples of UE are target device, device-to-device (D2D) UE, proximity capable UE (aka ProSe UE), machine type UE or UE capable of machine to machine (M2M) communication, PDA, PAD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles etc.
  • D2D device-to-device
  • ProSe UE proximity capable UE
  • M2M machine type UE or UE capable of machine to machine
  • PDA personal area network
  • PAD tablet
  • mobile terminals smart phone
  • LEE laptop embedded equipped
  • LME laptop mounted equipment
  • the embodiments are described for 5G. However the embodiments are applicable to any RAT or multi-RAT systems, where the UE receives and/or transmit signals (e.g. data) e.g. LTE, LTE FDD/TDD, WCDMA/HSPA, GSM/GERAN, Wi Fi, WLAN, CDMA2000 etc.
  • signals e.g. data
  • LTE Long Term Evolution
  • LTE FDD/TDD Long Term Evolution
  • WCDMA/HSPA Wideband Code Division Multiple Access
  • GSM/GERAN Wireless FDD/TDD
  • Wi Fi Wireless Fidelity
  • WLAN Wireless Local Area Network
  • CDMA2000 Code Division Multiple Access 2000
  • ASIC application-specific integrated circuit
  • Several of the functions may be implemented on a processor shared with other functional components of a wireless device or network node, for example.
  • processors or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware, read-only memory (ROM) for storing software, random-access memory for storing software and/or program or application data, and non-volatile memory.
  • DSP digital signal processor
  • ROM read-only memory
  • RAM random-access memory
  • non-volatile memory non-volatile memory
  • a communication system includes a telecommunication network 3210, such as a 3GPP-type cellular network, which comprises an access network 3211 , such as a radio access network, and a core network 3214.
  • the access network 3211 comprises a plurality of base stations 3212a, 3212b, 3212c, such as NBs, eNBs, gNBs or other types of wireless access points being examples of the radio network node 12 herein, each defining a corresponding coverage area 3213a, 3213b, 3213c.
  • Each base station 3212a, 3212b, 3212c is connectable to the core network 3214 over a wired or wireless connection 3215.
  • a first user equipment (UE) 3291 being an example of the UE 10 and relay UE 13, located in coverage area 3213c is configured to wirelessly connect to, or be paged by, the corresponding base station 3212c.
  • a second UE 3292 in coverage area 3213a is wirelessly connectable to the corresponding base station 3212a. While a plurality of UEs 3291 , 3292 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 3212.
  • the telecommunication network 3210 is itself connected to a host computer 3230, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm.
  • the host computer 3230 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider.
  • the connections 3221, 3222 between the telecommunication network 3210 and the host computer 3230 may extend directly from the core network 3214 to the host computer 3230 or may go via an optional intermediate network 3220.
  • the intermediate network 3220 may be one of, or a combination of more than one of, a public, private or hosted network; the intermediate network 3220, if any, may be a backbone network or the Internet; in particular, the intermediate network 3220 may comprise two or more sub-networks (not shown).
  • the communication system of Figure 6 as a whole enables connectivity between one of the connected UEs 3291 , 3292 and the host computer 3230.
  • the connectivity may be described as an over-the-top (OTT) connection 3250.
  • the host computer 3230 and the connected UEs 3291 , 3292 are configured to communicate data and/or signaling via the OTT connection 3250, using the access network 3211 , the core network 3214, any intermediate network 3220 and possible further infrastructure (not shown) as intermediaries.
  • the OTT connection 3250 may be transparent in the sense that the participating communication devices through which the OTT connection 3250 passes are unaware of routing of uplink and downlink communications.
  • a base station 3212 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 3230 to be forwarded (e.g., handed over) to a connected UE 3291. Similarly, the base station 3212 need not be aware of the future routing of an outgoing uplink communication originating from the UE 3291 towards the host computer 3230.
  • a host computer 3310 comprises hardware 3315 including a communication interface 3316 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 3300.
  • the host computer 3310 further comprises processing circuitry 3318, which may have storage and/or processing capabilities.
  • the processing circuitry 3318 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • the host computer 3310 further comprises software 3311 , which is stored in or accessible by the host computer 3310 and executable by the processing circuitry 3318.
  • the software 3311 includes a host application 3312.
  • the host application 3312 may be operable to provide a service to a remote user, such as a UE 3330 connecting via an OTT connection 3350 terminating at the UE 3330 and the host computer 3310. In providing the service to the remote user, the host application 3312 may provide user data which is transmitted using the OTT connection 3350.
  • the communication system 3300 further includes a base station 3320 provided in a telecommunication system and comprising hardware 3325 enabling it to communicate with the host computer 3310 and with the UE 3330.
  • the hardware 3325 may include a communication interface 3326 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 3300, as well as a radio interface 3327 for setting up and maintaining at least a wireless connection 3370 with a UE 3330 located in a coverage area (not shown in Fig.19) served by the base station 3320.
  • the communication interface 3326 may be configured to facilitate a connection 3360 to the host computer 3310.
  • connection 3360 may be direct or it may pass through a core network (not shown in Fig.19) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system.
  • the hardware 3325 of the base station 3320 further includes processing circuitry 3328, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • the base station 3320 further has software 3321 stored internally or accessible via an external connection.
  • the communication system 3300 further includes the UE 3330 already referred to.
  • Its hardware 3335 may include a radio interface 3337 configured to set up and maintain a wireless connection 3370 with a base station serving a coverage area in which the UE 3330 is currently located.
  • the hardware 3335 of the UE 3330 further includes processing circuitry 3338, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • the UE 3330 further comprises software 3331, which is stored in or accessible by the UE 3330 and executable by the processing circuitry 3338.
  • the software 3331 includes a client application 3332.
  • the client application 3332 may be operable to provide a service to a human or non-human user via the UE 3330, with the support of the host computer 3310.
  • an executing host application 3312 may communicate with the executing client application 3332 via the OTT connection 3350 terminating at the UE 3330 and the host computer 3310.
  • the client application 3332 may receive request data from the host application 3312 and provide user data in response to the request data.
  • the OTT connection 3350 may transfer both the request data and the user data.
  • the client application 3332 may interact with the user to generate the user data that it provides.
  • the host computer 3310, base station 3320 and UE 3330 illustrated in Fig. 19 may be identical to the host computer 3230, one of the base stations 3212a, 3212b, 3212c and one of the UEs 3291 , 3292 of Fig. 18, respectively.
  • the inner workings of these entities may be as shown in Fig. 19 and independently, the surrounding network topology may be that of Fig. 18.
  • the OTT connection 3350 has been drawn abstractly to illustrate the communication between the host computer 3310 and the user equipment 3330 via the base station 3320, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure may determine the routing, which it may be configured to hide from the UE 3330 or from the service provider operating the host computer 3310, or both. While the OTT connection 3350 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).
  • the wireless connection 3370 between the UE 3330 and the base station 3320 is in accordance with the teachings of the embodiments described throughout this disclosure.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 3330 using the OTT connection 3350, in which the wireless connection 3370 forms the last segment. More precisely, the teachings of these embodiments may improve the performance since path information is handled more efficiently and thereby provide benefits such as reduced user waiting time, and better responsiveness.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection 3350 may be implemented in the software 3311 of the host computer 3310 or in the software 3331 of the UE 3330, or both.
  • sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 3350 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 3311, 3331 may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 3350 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the base station 3320, and it may be unknown or imperceptible to the base station 3320. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling facilitating the host computer’s 3310 measurements of throughput, propagation times, latency and the like.
  • the measurements may be implemented in that the software 3311 , 3331 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 3350 while it monitors propagation times, errors etc.
  • Fig. 20 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figs. 18 and 19. For simplicity of the present disclosure, only drawing references to Fig. 20 will be included in this section.
  • the host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE.
  • the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the UE executes a client application associated with the host application executed by the host computer.
  • Fig. 21 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 18 and 19. For simplicity of the present disclosure, only drawing references to Figure 21 will be included in this section.
  • the host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the UE receives the user data carried in the transmission.
  • Fig. 22 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 18 and 19. For simplicity of the present disclosure, only drawing references to Figure 22 will be included in this section.
  • the UE receives input data provided by the host computer.
  • the UE provides user data.
  • the UE provides the user data by executing a client application.
  • the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer.
  • the executed client application may further consider user input received from the user.
  • the UE initiates, in an optional third substep 3630, transmission of the user data to the host computer.
  • the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.
  • Fig. 23 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 18 and 19. For simplicity of the present disclosure, only drawing references to Figure 23 will be included in this section.
  • the base station receives user data from the UE.
  • the base station initiates transmission of the received user data to the host computer.
  • the host computer receives the user data carried in the transmission initiated by the base station.

Abstract

Des modes de réalisation portent sur, par exemple, un procédé mis en œuvre par un nœud de réseau pour communiquer sur un chemin comprenant un UE distant (10), un UE relais (13) et un nœud de réseau radio (12) dans un réseau de communication sans fil. Le nœud de réseau transmet une ou plusieurs PDU de commande dans la couche d'adaptation pour distribuer des informations relatives au trajet, à un ou plusieurs autres nœuds de réseau dans le réseau de communication sans fil. La ou les PDU de commande comprennent des informations reflétant au moins l'un des éléments suivants : État de congestion; État de satisfaction de la QoS ; RLM ; État de mobilité ; Topologie ; Tout indicateur/cause d'événement de défaillance sur l'une quelconque des informations de statut susmentionnées ; Mesures de PC5 disponibles ; Mesures Uu disponibles ; Informations de localisation et/ou informations pour activer/désactiver une certaine action ou une certaine configuration.
PCT/SE2021/050963 2020-10-06 2021-09-30 Nœud de réseau, nœud de réseau demandeur et procédés de communication sur un chemin comprenant un équipement utilisateur distant, un équipement utilisateur relais et un nœud de réseau radio WO2022075906A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202063087891P 2020-10-06 2020-10-06
US63/087,891 2020-10-06

Publications (1)

Publication Number Publication Date
WO2022075906A1 true WO2022075906A1 (fr) 2022-04-14

Family

ID=81126305

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2021/050963 WO2022075906A1 (fr) 2020-10-06 2021-09-30 Nœud de réseau, nœud de réseau demandeur et procédés de communication sur un chemin comprenant un équipement utilisateur distant, un équipement utilisateur relais et un nœud de réseau radio

Country Status (1)

Country Link
WO (1) WO2022075906A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024031345A1 (fr) * 2022-08-09 2024-02-15 Apple Inc. Pdu de commande de srap pour relais d'ue à ue

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180279319A1 (en) * 2017-03-23 2018-09-27 Nokia Technologies Oy Dynamic provisioning of quality of service for end-to-end quality of service control in device-to-device communication
EP3429244A1 (fr) * 2016-06-03 2019-01-16 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Procédé et dispositif pour une transmission de relais
US20200281043A1 (en) * 2017-05-05 2020-09-03 Huawei Technologies Co., Ltd. Data receiving status reporting method and apparatus

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3429244A1 (fr) * 2016-06-03 2019-01-16 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Procédé et dispositif pour une transmission de relais
US20180279319A1 (en) * 2017-03-23 2018-09-27 Nokia Technologies Oy Dynamic provisioning of quality of service for end-to-end quality of service control in device-to-device communication
US20200281043A1 (en) * 2017-05-05 2020-09-03 Huawei Technologies Co., Ltd. Data receiving status reporting method and apparatus

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024031345A1 (fr) * 2022-08-09 2024-02-15 Apple Inc. Pdu de commande de srap pour relais d'ue à ue

Similar Documents

Publication Publication Date Title
US20240064838A1 (en) User equipment and method in a wireless communications network
US20230370902A1 (en) Relay UE Selection for Transmission Over Sidelink
WO2022074126A1 (fr) Technique permettant de gérer une défaillance de liaison radio dans des communications radio relayées
US20230389106A1 (en) Methods, apparatuses, computer program product and system for handling radio link failure in relayed radio communications
US20230397081A1 (en) Failure monitoring and recovery mechanism in case of sl relay
WO2022075906A1 (fr) Nœud de réseau, nœud de réseau demandeur et procédés de communication sur un chemin comprenant un équipement utilisateur distant, un équipement utilisateur relais et un nœud de réseau radio
WO2022062846A1 (fr) Procédé et appareil de commutation de trajet
US20230370152A1 (en) Technique for Radio Resource Allocation in a Relayed Radio Communication
US20230413229A1 (en) Method and Apparatus for Relay Communication
US20230403626A1 (en) Method and apparatus for relay communication
WO2022028277A1 (fr) Procédés et appareils pour l'attribution de ressources à un dispositif terminal
WO2023035860A1 (fr) Procédé et appareil de radiomessagerie
US20230328526A1 (en) Technique for Header Integrity in a Relayed Radio Communication
US20240137820A1 (en) Technique for Mobility Update Reporting
US20230397085A1 (en) Monitoring procedure for relay path scenarios
WO2022210184A1 (fr) Système de communication et station de base
WO2022206813A1 (fr) Procédés, ue, ue relais et nœud de réseau pour communication sur liaison latérale
US20230388770A1 (en) Technique for discovery in proximity services comprising different discovery models
WO2023005351A1 (fr) Dispositif terminal, noeud de réseau et procédés à l'intérieur de celui-ci pour gérer un commutateur de trajet et un transfert
WO2022086398A1 (fr) Équipement utilisateur, nœud de réseau radio et procédés effectués dans un réseau de communications sans fil
WO2022194853A1 (fr) Technique de commutation d'une communication radio relayée
WO2024033295A2 (fr) Découverte et (re-)sélection de relais u2u
WO2022152798A1 (fr) Technique de rapport de mise à jour de mobilité

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21878108

Country of ref document: EP

Kind code of ref document: A1