WO2022223178A1 - Gestion de tunnel f1-u temporaire pour mobilité de service de diffusion/multidiffusion (mbs) - Google Patents

Gestion de tunnel f1-u temporaire pour mobilité de service de diffusion/multidiffusion (mbs) Download PDF

Info

Publication number
WO2022223178A1
WO2022223178A1 PCT/EP2022/054502 EP2022054502W WO2022223178A1 WO 2022223178 A1 WO2022223178 A1 WO 2022223178A1 EP 2022054502 W EP2022054502 W EP 2022054502W WO 2022223178 A1 WO2022223178 A1 WO 2022223178A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
tunnel
network node
temporary
over
Prior art date
Application number
PCT/EP2022/054502
Other languages
English (en)
Inventor
Philippe Godin
David NAVRÁTIL
Esa Mikael MALKAMÄKI
Original Assignee
Nokia Technologies Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Technologies Oy filed Critical Nokia Technologies Oy
Publication of WO2022223178A1 publication Critical patent/WO2022223178A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H04W36/087—Reselecting an access point between radio units of access points
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/22—Manipulation of transport tunnels
    • 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/08—Access point devices
    • H04W88/085—Access point devices with remote components

Definitions

  • Some example embodiments may generally relate to communications including mobile or wireless telecommunication systems, such as Long Term Evolution (LTE) or fifth generation (5G) radio access technology or new radio (NR) access technology, or other communications systems.
  • LTE Long Term Evolution
  • 5G fifth generation
  • NR new radio
  • certain example embodiments may generally relate to systems and/or methods for handling temporary Fl-U tunnel for multicast broadcast service (MBS) mobility.
  • MMS multicast broadcast service
  • Examples of mobile or wireless telecommunication systems may include the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Long Term Evolution (LTE) Evolved UTRAN (E-UTRAN), LTE- Advanced (LTE- A), MulteFire, LTE-A Pro, and/or fifth generation (5G) radio access technology or new radio (NR) access technology.
  • UMTS Universal Mobile Telecommunications System
  • UTRAN Long Term Evolution
  • E-UTRAN Evolved UTRAN
  • LTE- A LTE- Advanced
  • MulteFire LTE-A Pro
  • 5G wireless systems refer to the next generation (NG) of radio systems and network architecture.
  • NG next generation
  • a 5G system is mostly built on a 5G new radio (NR), but a 5G (or NG) network can also build on the E-UTRA radio.
  • NR provides bitrates on the order of 10-20 Gbit/s or higher, and can support at least service categories such as enhanced mobile broadband (eMBB) and ultra-reliable low-latency-communication (URLLC) as well as massive machine type communication (mMTC).
  • eMBB enhanced mobile broadband
  • URLLC ultra-reliable low-latency-communication
  • mMTC massive machine type communication
  • NR is expected to deliver extreme broadband and ultra-robust, low latency connectivity and massive networking to support the Internet of Things (IoT).
  • IoT and machine-to-machine (M2M) communication With IoT and machine-to-machine (M2M) communication becoming more widespread, there will be a growing need for networks that meet the needs of lower power, low data rate, and long battery life.
  • the next generation radio access network (NG-RAN) represents the RAN for 5G, which can provide both NR and LTE (and LTE-Advanced) radio accesses.
  • the nodes that can provide radio access functionality to a user equipment may be named next-generation NB (gNB) when built on NR radio and may be named next-generation eNB (NG-eNB) when built on E-UTRA radio.
  • gNB next-generation NB
  • NG-eNB next-generation eNB
  • FIG. 1 illustrates an example signaling diagram, according to an embodiment
  • FIG. 2 illustrates an example signaling diagram, according to an embodiment
  • FIG. 3 illustrates an example signaling diagram, according to an embodiment
  • FIG. 4 illustrates an example signaling diagram, according to an embodiment
  • FIG. 5A illustrates an example flow diagram of a method, according to an embodiment
  • FIG. 5B illustrates an example flow diagram of a method, according to an embodiment
  • FIG. 6A illustrates an example flow diagram of a method, according to an embodiment
  • FIG. 6B illustrates an example flow diagram of a method, according to an embodiment
  • Fig. 7 A illustrates an example flow diagram of a method, according to an embodiment
  • FIG. 7B illustrates an example flow diagram of a method, according to an embodiment
  • FIG. 8A illustrates an example block diagram of an apparatus, according to an embodiment
  • Fig. 8B illustrates an example block diagram of an apparatus, according to an embodiment.
  • a target central unit (CU) user plane (UP) can deliver MBS data received from a core network to a distributed unit (DU) for Point-to- Multipoint (PtM) delivery over a shared Fl-U tunnel ⁇
  • the target DU PtP leg needs to deliver the data forwarded from the source gNB and the data buffered at the target gNB until traffic over the DU PtP leg catches up with the traffic over the DU PtM leg.
  • a problem arises in determining how to send the forwarded and buffered data to the DU PtP leg, since sending this data over the shared Fl-U tunnel mixed with other traffic is complicated.
  • Fig. 1 illustrates an example signaling diagram of a method for a target gNB (T-gNB) to receive forwarded data from a source gNB (S-gNB).
  • T-gNB target gNB
  • S-gNB source gNB
  • the S-gNB may transmit a HO request including an UL tunnel endpoint identifier (TEID) to the T-gNB.
  • TEID tunnel endpoint identifier
  • the s-gNB may send and the T-gNB may receive forwarded data until SNO.
  • the T-gNB may send, to the UE, the forwarded and buffered data over radio PtP leg of UE until this leg has caught up with the PtM leg of UE.
  • a disaggregated gNB i.e., a gNB with a CU and DU split.
  • this can be accomplished when the target gNB is split between CU and DU in a multi-vendor scenario, i.e., with the CU and DU which are separate nodes owned by different vendors and connected through an FI interface.
  • Certain example embodiments may provide several solutions for addressing the issue of minimizing packet loss during mobility when the target gNB is split into a CU node and DU node, which may or may not be owned by different vendors. More precisely, some example embodiments can provide methods for sending, to the UE, the forwarded and buffered data over the radio PtP leg of the UE until this leg has caught up with the PtM leg of the UE, e.g., when the target gNB is split between CU and DU. The PtP leg catches up to the PtM leg when the forwarded, i.e. data with corresponding SN lower than SNO, and buffered data, i.e.
  • SN1 may be the SN associated with the first data transmitted over the PtM leg after the completion of HO in the target, i.e. after the target gNB received the RRCReconfigurationComplete message from the UE.
  • the target gNB could determine the SN1 from a status message, e.g. PDCP status report.
  • An embodiment may be configured to allow the DU to manage a temporary tunnel with the CU UP.
  • the timing for setting up and/or releasing this tunnel can vary according to the solutions provided, as well as the type of data that is transmitted over that temporary tunnel. Certain embodiments may also depend on whether or not target gNB wants to process the forwarded data at PDCP, e.g. to cipher or compress the header. For example, some embodiments may be applicable if the target gNB does not want to process the forwarded data at PDCP.
  • One embodiment may be configured to forward data via a CU UP and to buffer incoming data from a core network (and referred to as “fresh data” in the drawings) at the CU UP.
  • Fig. 2 illustrates an example signaling diagram, according to this embodiment.
  • the target CU UP may start buffering new incoming data, e.g., from a user plane function (UPF) starting from sequence number NO (SN NO).
  • UPF user plane function
  • SN NO sequence number NO
  • the target CU UP may start buffering data forwarded from the source gNB.
  • the SN NO may be indicated in a HO request acknowledgement to the source gNB.
  • the target CU CP may set up a temporary Fl-U tunnel from the target CU UP to the target DU in order to feed, at 220, the DU PtP leg at the target side with the forwarded data followed by the incoming data buffered at the target CU UP after the CU UP has PDCP processed the incoming data.
  • PDCP processing of the forwarded and incoming data may occur in the target CU UP.
  • the DU may deliver the buffered forward data and the buffered incoming data to one or more UE(s) over the PtP leg.
  • the target DU may detect, at 230, that data delivery over the PtP leg is caught up with the delivery over the PtM leg.
  • the target DU may then, at 235, request to release the temporary Fl-U tunnel when the DU detects that the data delivery over the PtP leg has caught up with the delivery of data over the PtM leg.
  • the target CU CP may release the temporary Fl-U tunnel from the target CU UP to the target DU.
  • FIG. 2 is provided as one example. Other examples or modifications are possible according to certain embodiments.
  • An embodiment may be configured to forward data via a CU UP and to buffer incoming data from a core network received via the CU UP over a shared tunnel at a DU.
  • Fig. 3 illustrates an example signaling diagram, according to this embodiment.
  • the target DU may itself buffer the data forwarded from the source gNB via the CU UP and the incoming data from the core network received via the target CU UP (e.g., over a separate shared Fl-U tunnel).
  • Fig. 3 illustrates an example signaling diagram, according to this embodiment.
  • the target DU may itself buffer the data forwarded from the source gNB via the CU UP and the incoming data from the core network received via the target CU UP (e.g., over a separate shared Fl-U tunnel).
  • the target CU CP may setup a temporary Fl-U tunnel from the target CU UP to the DU and, at 307, may setup a forwarding tunnel from the source gNB to the target CU UP.
  • the DU may start buffering incoming data received from the target CU UP over a shared Fl-U tunnel, e.g., starting at sequence number NO (SN NO).
  • the CU CP may receive an indication of the SN NO from the DU when the temporary Fl-U tunnel is created at step 305, e.g., in an F1AP message, such as a UE context setup response message.
  • the SN NO may be indicated in a HO request acknowledgement to the source gNB.
  • the target CU UP may perform PDCP processing of data forwarded from the source gNB before delivery to the DU.
  • the PDCP processed forwarded data may be transmitted to the DU over the temporary Fl-U tunnel.
  • the DU may deliver the forwarded data to at least one UE over a PtP leg together with and/or followed by the buffered incoming data (e.g., until DU detects that data delivery over the PtP leg has caught up with delivery of data over PtM leg such as 345).
  • the DU may detect or determine that the data forwarding has ended. For example, the end of the forwarded data may be detected when the forwarded data reaches SN NO.
  • the DU may request release of the temporary forwarding Fl-U tunnel (e.g., requesting to release the Fl-U DL TEID of the forwarding tunnel) when an end of the forwarded data is detected and, at 340, the target CU CP may release the temporary forwarding Fl-U tunnel after the PDCP processed data have been sent to the DU or after receiving the above release request from the DU.
  • the temporary forwarding Fl-U tunnel e.g., requesting to release the Fl-U DL TEID of the forwarding tunnel
  • the DU may deliver, to the at least one UE, the buffered forwarded data and the buffered incoming data until it is detected that delivery of data over the point-to-point (PtP) leg has caught up with delivery of data over a point-to-multipoint (PtM) leg.
  • PtP point-to-point
  • PtM point-to-multipoint
  • Fig. 3 is provided as one example. Other examples or modifications to Fig. 3 are possible according to certain embodiments.
  • FIG. 4 illustrates an example signaling diagram, according to this embodiment.
  • the target DU may itself buffer the data which is directly forwarded from the source gNB and may buffer the incoming data from the core network received via a CU UP, e.g., over shared Fl-U tunnel starting from SN NO.
  • the target CU CP may set up a temporary Fl-U forwarding tunnel directly from the source gNB to target DU.
  • the Fl-U DL TEID and/or SN NO may be sent back to the source gNB in a HO request acknowledgement.
  • the DU may start buffering incoming data from CU UP received over a separate shared tunnel, e.g., starting at SN NO.
  • the DU may receive forwarded data directly from the source gNB over the temporary forwarding tunnel.
  • the DU may deliver the forwarded data to at least one UE over a PtP leg together with and/or followed by the buffered incoming data (e.g., until DU detects that data delivery over the PtP leg has caught up with delivery of data over PtM leg).
  • the DU may detect or determine that the data forwarding has ended. For example, the end of the forwarded data may be detected when the forwarded data reaches SN NO. As also illustrated in the example of Fig. 4, at 435, the DU may request release of the temporary forwarding Fl-U tunnel (e.g., requesting to release the Fl-U DF TEID of the forwarding tunnel) when all of the data has been forwarded. Alternatively, the source gNB may request release of the temporary forwarding Fl-U tunnel. At 440, e.g., responsive to receiving a request to release the temporary tunnel, the target CU CP may release the temporary forwarding Fl-U tunnel.
  • the temporary forwarding Fl-U tunnel e.g., requesting to release the Fl-U DF TEID of the forwarding tunnel
  • the DU may deliver, to the at least one UE, the buffered forwarded data and the buffered incoming data until it is detected that delivery of data over the point-to-point (PtP) leg has caught up with delivery of data over a point-to- multipoint (PtM) leg.
  • PtP point-to-point
  • PtM point-to- multipoint
  • PDCP COUNT can be used instead of PDCP SN and thus PDCP COUNT NO may be used instead of SN NO. It should be noted, however, that PDCP COUNT may be known by just the CU UP, since DU sees just PDCP SN. As such, SN NO can be used towards the target DU.
  • the PDCP processing for the forwarded data may occur in the source gNB.
  • PDCP processing just adds the PDCP header with SN (no ciphering or integrity protection, and possibly no header compression).
  • PDCP COUNT of multicast radio bearer may be assumed to be synchronized between gNBs.
  • Fig. 4 is provided as one example. Other examples or modifications to Fig. 4 are possible according to certain embodiments.
  • FIG. 2-4 are provided to illustrate some, but not necessarily all, example embodiments.
  • Fig. 5A illustrates an example flow diagram of a method for handling temporary Fl-U tunnel for MBS mobility, according to an example embodiment.
  • the flow diagram of Fig. 5 A may be performed by a network entity or network node in a communications system, such as LTE or 5G NR.
  • the network entity performing the method of Fig. 5 A may include or be included in a base station, access node, node B, eNB, gNB, NG-RAN node, transmission- reception points (TRPs), high altitude platform stations (HAPS), relay station or the like.
  • TRPs transmission- reception points
  • HAPS high altitude platform stations
  • 5A may include a CU (e.g., CU UP and/or CU CP) of a network node, such as the CU CP or CU UP of the target node illustrated in the examples of Figs. 2-4, or a similar radio node or unit.
  • a CU e.g., CU UP and/or CU CP
  • a network node such as the CU CP or CU UP of the target node illustrated in the examples of Figs. 2-4, or a similar radio node or unit.
  • the method may include, 500, buffering, at the CU UP of the target network node (e.g., target gNB), data forwarded from a source network node (e.g., source gNB) and buffering new incoming data from a core network (e.g. UPF).
  • target network node e.g., target gNB
  • source network node e.g., source gNB
  • UPF core network
  • the method may include, at 505, setting up, by the CU CP of the target network node, a temporary Fl-U tunnel from the CU UP of the target network node to a DU of the target network node to feed the DU point-to-point (PtP) leg with the forwarded data together with and/or followed by the incoming data buffered at the CU UP of the target network node after the CU UP has PDCP processed the data.
  • PtP point-to-point
  • the method may include, at 510, receiving a request from the DU to release the temporary Fl-U tunnel when data delivery over the point-to-point (PtP) leg has caught up with data delivery over a point-to-multipoint (PtM) leg and, at 515, releasing the temporary Fl-U tunnel.
  • the buffering of the incoming data may include buffering incoming data from a UPF starting from sequence number NO (SN NO) or packet data convergence protocol (PDCP) count NO (COUNT NO).
  • the method may include indicating the sequence number NO (SN NO) or the packet data convergence protocol (PDCP) count NO (COUNT NO) in a handover request acknowledgement to the source network node.
  • Fig. 5B illustrates an example flow diagram of a method for handling temporary Fl-U tunnel for MBS mobility, according to an example embodiment.
  • the flow diagram of Fig. 5B may be performed by a network entity or network node in a communications system, such as LTE or 5G NR.
  • the network entity performing the method of Fig. 5B may include or be included in a base station, access node, node B, eNB, gNB, NG-RAN node, transmission- reception points (TRPs), high altitude platform stations (HAPS), relay station or the like.
  • the network node performing the method of Fig. 5B may include a DU of a network node, such as the DU of the target node illustrated in the examples of Figs. 2-4, or a similar radio node or unit.
  • the method may include, 550, receiving, at a DU of a target network node (e.g., target gNB), data forwarded from a source network node (e.g., source gNB) and new incoming data over a temporary Fl-U tunnel setup from a CU UP of the target network node to the DU of the target network node.
  • the method may include, at 555, transmitting or forwarding the forwarded data and the incoming data to at least one user equipment over a point-to-point (PtP) leg.
  • PtP point-to-point
  • 5B may include, at 560, detecting when delivery of data over the point-to-point (PtP) leg has caught up with the delivery of data over a point-to-multipoint (PtM) leg.
  • the method may include, at 565, based on the detecting, requesting a CU CP to release the temporary Fl-U tunnel from the CU UP of the target network node.
  • Fig. 6A illustrates an example flow diagram of a method for handling temporary Fl-U tunnel for MBS mobility, according to an example embodiment.
  • the flow diagram of Fig. 6 A may be performed by a network entity or network node in a communications system, such as LTE or 5G NR.
  • the network entity performing the method of Fig. 6 A may include or be included in a base station, access node, node B, eNB, gNB, NG-RAN node, transmission- reception points (TRPs), high altitude platform stations (HAPS), relay station or the like.
  • TRPs transmission- reception points
  • HAPS high altitude platform stations
  • 6A may include a CU (e.g., CU UP and/or CU CP) of a network node, such as the CU CP or CU UP or the target node illustrated in the examples of Figs. 2-4, or a similar radio node or unit.
  • a CU e.g., CU UP and/or CU CP
  • a network node such as the CU CP or CU UP or the target node illustrated in the examples of Figs. 2-4, or a similar radio node or unit.
  • the method may include, 600, setting up, by a CU CP of a target network node (e.g., a target gNB), a forwarding tunnel (e.g., an Xn-U tunnel) from a source network node (e.g., a source gNB) to a CU UP of the target network node and a temporary Fl-U tunnel from the CU UP of the target network node to a DU of the target network node.
  • a target network node e.g., a target gNB
  • a forwarding tunnel e.g., an Xn-U tunnel
  • the method may also include, at 605, processing (e.g., PDCP processing) data received from the source network node over the forwarding tunnel and, at 610, transmitting the processed forwarded data to the DU of the target network node over the temporary Fl-U tunnel.
  • processing e.g., PDCP processing
  • the processing 605 may include PDCP processing the data received from the source network node and the transmitting 610 may include transmitting the PDCP processed forwarded data to the DU.
  • the method may then include, at 615, releasing the temporary Fl-U tunnel after all of the processed forwarded data have been sent to the DU.
  • the method may include receiving, at the CU CP, a request from the DU to release the temporary Fl-U tunnel after the processed forwarded data have been sent over the temporary Fl-U tunnel, and releasing the temporary Fl-U tunnel in response to the request.
  • the release request from the DU may be received when an end of the forwarded data is detected and the detection may happen when the forwarded data reaches sequence number NO (SN NO) or packet convergence protocol count NO (COUNT NO).
  • the sequence number NO (SN NO) or PDCP count NO (COUNT NO) may be received by CU CP from the DU when the temporary Fl-U tunnel is created.
  • the sequence number NO (SN NO) or PDCP count NO (COUNT NO) may be sent to the source network node in a handover request acknowledgement message.
  • Fig. 6B illustrates an example flow diagram of a method for handling temporary Fl-U tunnel for MBS mobility, according to an example embodiment.
  • the flow diagram of Fig. 6B may be performed by a network entity or network node in a communications system, such as LTE or 5G NR.
  • the network entity performing the method of Fig. 6B may include or be included in a base station, access node, node B, eNB, gNB, NG-RAN node, transmission- reception points (TRPs), high altitude platform stations (HAPS), relay station or the like.
  • TRPs transmission- reception points
  • HAPS high altitude platform stations
  • the method may include, 650, receiving, at a DU of a target network node (e.g., target gNB), data forwarded from a source network node (e.g., source gNB) over a first temporary Fl-U tunnel from a CU UP of the target network node and buffering incoming data received from the CU UP over a different second shared Fl-U tunnel.
  • a target network node e.g., target gNB
  • a source network node e.g., source gNB
  • the buffering of the incoming data may include buffering incoming data starting from sequence number NO (SN NO) or PDCP count NO (COUNT NO).
  • the method of Fig. 6B may include, at 655, transmitting, to at least one user equipment, over a point-to-point (PtP) leg the forwarded data received over the first temporary Fl-U tunnel together with and/or followed by the buffered incoming data received over the second shared Fl-U tunnel until it is detected that delivery of data over the point-to-point (PtP) leg has caught up with the delivery of data over a point-to-multipoint (PtM) leg.
  • the transmitting 655 of the buffered incoming data may include transmitting the buffered incoming data after the transmitting of the forwarded data to the at least one user equipment.
  • the method may include, at 660, requesting release of the first temporary Fl-U tunnel after all of the forwarded data has been received over the first temporary Fl-U tunnel.
  • the end of the forwarded data may be detected when the forwarded data reaches sequence number NO (SN NO) or PDCP count NO (COUNT NO).
  • the method may include indicating the sequence number NO (SN NO) or the PDCP count NO (COUNT NO) to the CU CP when the first temporary Fl-U tunnel is created in an F1AP message, such as a UE context setup response message.
  • the method may also include indicating the sequence number NO (SN NO) or the PDCP count NO (COUNT NO) received by the CU CP in a handover request acknowledgement to the source network node.
  • Fig. 7A illustrates an example flow diagram of a method for handling temporary Fl-U tunnel for MBS mobility, according to an example embodiment.
  • the flow diagram of Fig. 7 A may be performed by a network entity or network node in a communications system, such as LTE or 5G NR.
  • the network node performing the method of Fig. 7A may include a CU (e.g., CU UP and/or CU CP) of a network node, such as the CU CP or CU UP or the target node illustrated in the examples of Figs. 2-4, or a similar radio node or unit.
  • a CU e.g., CU UP and/or CU CP
  • a network node such as the CU CP or CU UP or the target node illustrated in the examples of Figs. 2-4, or a similar radio node or unit.
  • the method may include, 700, setting up, by a CU CP of a target network node (e.g., a target gNB), a temporary Fl-U forwarding tunnel directly from a source network node (e.g., a source gNB) to a DU of the target network node.
  • the method of Fig. 7A may include, at 705, receiving a request to release the temporary Fl-U forwarding tunnel after all of the data have been forwarded and, at 710, releasing the temporary Fl-U forwarding tunnel.
  • the receiving 705 may include receiving the request to release the temporary Fl-U forwarding tunnel from the distributed unit (DU) and/or from the source network node.
  • sequence number NO may be received by the CU CP from the DU when the Fl-U forwarding tunnel is created or when the DU starts to buffer incoming data.
  • the method may include indicating at least one of the sequence number NO (SN NO) or the PDCP count NO (COUNT NO) or a tunnel endpoint identifier (TEID) of the temporary Fl-U forwarding tunnel in a handover request acknowledgement to the source network node.
  • the tunnel endpoint identifier (TEID) of the temporary Fl-U forwarding tunnel is a downlink tunnel endpoint identifier of the DU which is received by the CU CP from the DU when the Fl-U forwarding tunnel is created.
  • Fig. 7B illustrates an example flow diagram of a method for handling temporary Fl-U tunnel for MBS mobility, according to an example embodiment.
  • the flow diagram of Fig. 7B may be performed by a network entity or network node in a communications system, such as FTE or 5G NR.
  • the network entity performing the method of Fig. 7B may include or be included in a base station, access node, node B, eNB, gNB, NG-RAN node, transmission- reception points (TRPs), high altitude platform stations (HAPS), relay station or the like.
  • the network node performing the method of Fig. 7B may include a DU of a network node, such as the DU of the target node illustrated in the examples of Figs. 2-4, or a similar radio node or unit.
  • the method may include, 750, receiving, at a DU of a target network node (e.g., target gNB), data that is directly forwarded from a source network node (e.g., source gNB) over a first Fl-U forwarding tunnel and buffering incoming data from a CU UP of the target network node received over a second shared Fl-U tunnel.
  • the method may include, at 755, transmitting the forwarded data to at least one user equipment over a point-to-point (PtP) leg until an end of the forwarded data is detected.
  • PtP point-to-point
  • the method may include, at 760, requesting the release of the first Fl-U forwarding tunnel after all the forwarded data has been sent over the PtP leg.
  • the method may also include, at 765, transmitting the buffered incoming data to at least one user equipment over the point-to- point (PtP) leg after and/or together with the forwarded data until it is detected that delivery of data over the point-to-point (PtP) leg has caught up with the delivery of data over a point-to-multipoint (PtM) leg.
  • the transmitting 765 of the buffered incoming data may include transmitting the buffered incoming data after transmission of the forwarded data to the at least one user equipment.
  • the buffering of the incoming data may include buffering incoming data starting from sequence number NO (SN NO) or PDCP count NO (COUNT NO).
  • the end of the forwarded data may be detected when the forwarded data reaches sequence number NO (SN NO) or packet convergence protocol count NO (COUNT NO).
  • the sequence number NO (SN NO) may be sent to a CU CP of the target network node, and to the source network node via the CU CP, when the first Fl-U forwarding tunnel is created.
  • apparatus 10 may be a node, host, or server in a communications network or serving such a network.
  • apparatus 10 may be a network node, a sensing node, satellite, base station, a Node B, an evolved Node B (eNB), 5G Node B or access point, next generation Node B (NG-NB or gNB), TRP, HAPS, integrated access and backhaul (IAB) node, and/or a WLAN access point, associated with a radio access network, such as a LTE network, 5G or NR.
  • apparatus 10 may be gNB or other similar radio node, for instance.
  • apparatus 10 may be comprised of an edge cloud server as a distributed computing system where the server and the radio node may be stand-alone apparatuses communicating with each other via a radio path or via a wired connection, or they may be located in a same entity communicating via a wired connection.
  • apparatus 10 represents a gNB
  • it may be configured in a central unit (CU) and distributed unit (DU) architecture that divides the gNB functionality.
  • the CU may be a logical node that includes gNB functions such as transfer of user data, mobility control, radio access network sharing, positioning, and/or session management, etc.
  • the CU may control the operation of DU(s) over a front-haul interface.
  • the DU may be a logical node that includes a subset of the gNB functions, depending on the functional split option. It should be noted that one of ordinary skill in the art would understand that apparatus 10 may include components or features not shown in Fig. 8 A.
  • apparatus 10 may include a processor 12 for processing information and executing instructions or operations.
  • processor 12 may be any type of general or specific purpose processor.
  • processor 12 may include one or more of general-purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application- specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, or any other processing means, as examples. While a single processor 12 is shown in Fig. 8A, multiple processors may be utilized according to other embodiments.
  • apparatus 10 may include two or more processors that may form a multiprocessor system (e.g., in this case processor 12 may represent a multiprocessor) that may support multiprocessing.
  • processor 12 may represent a multiprocessor
  • the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).
  • Processor 12 may perform functions associated with the operation of apparatus 10, which may include, for example, precoding of antenna gain/phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatus 10, including processes related to management of communication or communication resources.
  • Apparatus 10 may further include or be coupled to a memory 14 (internal or external), which may be coupled to processor 12, for storing information and instructions that may be executed by processor 12.
  • Memory 14 may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor- based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and/or removable memory.
  • memory 14 can be comprised of any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, hard disk drive (HDD), or any other type of non- transitory machine or computer readable media, or other appropriate storing means.
  • the instructions stored in memory 14 may include program instructions or computer program code that, when executed by processor 12, enable the apparatus 10 to perform tasks as described herein.
  • apparatus 10 may further include or be coupled to (internal or external) a drive or port that is configured to accept and read an external computer readable storage medium, such as an optical disc, USB drive, flash drive, or any other storage medium.
  • an external computer readable storage medium such as an optical disc, USB drive, flash drive, or any other storage medium.
  • the external computer readable storage medium may store a computer program or software for execution by processor 12 and/or apparatus 10.
  • apparatus 10 may also include or be coupled to one or more antennas 15 for transmitting and receiving signals and/or data to and from apparatus 10.
  • Apparatus 10 may further include or be coupled to a transceiver 18 configured to transmit and receive information.
  • the transceiver 18 may include, for example, a plurality of radio interfaces that may be coupled to the antemia(s) 15, or may include any other appropriate transceiving means.
  • the radio interfaces may correspond to a plurality of radio access technologies including one or more of GSM, NB-IoT, LTE, 5G, WLAN, Bluetooth, BT-LE, NFC, radio frequency identifier (RFID), ultrawideband (UWB), MulteFire, and the like.
  • the radio interface may include components, such as filters, converters (for example, digital-to-analog converters and the like), mappers, a Fast Fourier Transform (FFT) module, and the like, to generate symbols for a transmission via one or more downlinks and to receive symbols (via an uplink, for example).
  • filters for example, digital-to-analog converters and the like
  • mappers for example, mappers, and the like
  • FFT Fast Fourier Transform
  • transceiver 18 may be configured to modulate information on to a carrier waveform for transmission by the antenna(s) 15 and demodulate information received via the antenna(s) 15 for further processing by other elements of apparatus 10.
  • transceiver 18 may be capable of transmitting and receiving signals or data directly.
  • apparatus 10 may include an input and/or output device (I/O device), or an input/output means.
  • memory 14 may store software modules that provide functionality when executed by processor 12.
  • the modules may include, for example, an operating system that provides operating system functionality for apparatus 10.
  • the memory may also store one or more functional modules, such as an application or program, to provide additional functionality for apparatus 10.
  • the components of apparatus 10 may be implemented in hardware, or as any suitable combination of hardware and software.
  • processor 12 and memory 14 may be included in or may form a part of processing circuitry/means or control circuitry/means.
  • transceiver 18 may be included in or may form a part of transceiver circuitry /means.
  • circuitry may refer to hardware-only circuitry implementations (e.g., analog and/or digital circuitry), combinations of hardware circuits and software, combinations of analog and/or digital hardware circuits with software/firmware, any portions of hardware processor(s) with software (including digital signal processors) that work together to cause an apparatus (e.g., apparatus 10) to perform various functions, and/or hardware circuit(s) and/or processor(s), or portions thereof, that use software for operation but where the software may not be present when it is not needed for operation.
  • hardware-only circuitry implementations e.g., analog and/or digital circuitry
  • combinations of hardware circuits and software e.g., combinations of analog and/or digital hardware circuits with software/firmware
  • any portions of hardware processor(s) with software including digital signal processors
  • circuitry may also cover an implementation of merely a hardware circuit or processor (or multiple processors), or portion of a hardware circuit or processor, and its accompanying software and/or firmware.
  • the term circuitry may also cover, for example, a baseband integrated circuit in a server, cellular network node or device, or other computing or network device.
  • apparatus 10 may be or may be a part of a network element or RAN node, such as a base station, access point, Node B, eNB, gNB, TRP, HAPS, IAB node, WLAN access point, or the like.
  • apparatus 10 may be a gNB or other radio node, or may be a CU and/or DU of a gNB.
  • apparatus 10 may be controlled by memory 14 and processor 12 to perform the functions associated with any of the embodiments described herein.
  • apparatus 10 may be configured to perform one or more of the processes depicted in any of the flow charts or signaling diagrams described herein, such as those illustrated in Figs. 2-4, 5A, 5B, 6A, 6B, 7A or 7C, or any other method described herein.
  • apparatus 10 may be configured to perform a procedure relating to handling temporary Fl-U tunnel for MBS mobility, as discussed elsewhere herein, for example.
  • Fig. 8B illustrates an example of an apparatus 20 according to another embodiment.
  • apparatus 20 may be a node or element in a communications network or associated with such a network, such as a UE, communication node, mobile equipment (ME), mobile station, mobile device, stationary device, IoT device, or other device.
  • a UE a node or element in a communications network or associated with such a network
  • UE communication node
  • ME mobile equipment
  • mobile station mobile device
  • mobile device stationary device
  • IoT device IoT device
  • a UE may alternatively be referred to as, for example, a mobile station, mobile equipment, mobile unit, mobile device, user device, subscriber station, wireless terminal, tablet, smart phone, IoT device, sensor or NB-IoT device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications thereof (e.g., remote surgery), an industrial device and applications thereof (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain context), a consumer electronics device, a device operating on commercial and/or industrial wireless networks, or the like.
  • apparatus 20 may be implemented in, for instance, a wireless handheld device, a wireless plug-in accessory, or the like.
  • apparatus 20 may include one or more processors, one or more computer-readable storage medium (for example, memory, storage, or the like), one or more radio access components (for example, a modem, a transceiver, or the like), and/or a user interface.
  • apparatus 20 may be configured to operate using one or more radio access technologies, such as GSM, LTE, LTE-A, NR, 5G, WLAN, WiFi, NB-IoT, Bluetooth, NFC, MulteFire, and/or any other radio access technologies. It should be noted that one of ordinary skill in the art would understand that apparatus 20 may include components or features not shown in Fig. 8B. [0064] As illustrated in the example of Fig.
  • apparatus 20 may include or be coupled to a processor 22 for processing information and executing instructions or operations.
  • processor 22 may be any type of general or specific purpose processor.
  • processor 22 may include one or more of general-purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, as examples. While a single processor 22 is shown in Fig. 8B, multiple processors may be utilized according to other embodiments.
  • apparatus 20 may include two or more processors that may form a multiprocessor system (e.g., in this case processor 22 may represent a multiprocessor) that may support multiprocessing.
  • processor 22 may represent a multiprocessor
  • the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).
  • Processor 22 may perform functions associated with the operation of apparatus 20 including, as some examples, precoding of antenna gain/phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatus 20, including processes related to management of communication resources.
  • Apparatus 20 may further include or be coupled to a memory 24 (internal or external), which may be coupled to processor 22, for storing information and instructions that may be executed by processor 22.
  • Memory 24 may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor- based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and/or removable memory.
  • memory 24 can be comprised of any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, hard disk drive (HDD), or any other type of non- transitory machine or computer readable media.
  • the instructions stored in memory 24 may include program instructions or computer program code that, when executed by processor 22, enable the apparatus 20 to perform tasks as described herein.
  • apparatus 20 may further include or be coupled to (internal or external) a drive or port that is configured to accept and read an external computer readable storage medium, such as an optical disc, USB drive, flash drive, or any other storage medium.
  • an external computer readable storage medium such as an optical disc, USB drive, flash drive, or any other storage medium.
  • the external computer readable storage medium may store a computer program or software for execution by processor 22 and/or apparatus 20.
  • apparatus 20 may also include or be coupled to one or more antennas 25 for receiving a downlink signal and for transmitting via an uplink from apparatus 20.
  • Apparatus 20 may further include a transceiver 28 configured to transmit and receive information.
  • the transceiver 28 may also include a radio interface (e.g., a modem) coupled to the antenna 25.
  • the radio interface may correspond to a plurality of radio access technologies including one or more of GSM, LTE, LTE-A, 5G, NR, WLAN, NB-IoT, Bluetooth, BT-LE, NFC, RFID, UWB, and the like.
  • the radio interface may include other components, such as filters, converters (for example, digital-to-analog converters and the like), symbol demappers, signal shaping components, an Inverse Fast Fourier Transform (IFFT) module, and the like, to process symbols, such as OFDMA symbols, carried by a downlink or an uplink.
  • filters for example, digital-to-analog converters and the like
  • symbol demappers for example, digital-to-analog converters and the like
  • signal shaping components for example, an Inverse Fast Fourier Transform (IFFT) module, and the like
  • IFFT Inverse Fast Fourier Transform
  • transceiver 28 may be configured to modulate information on to a carrier waveform for transmission by the antenna(s) 25 and demodulate information received via the antenna(s) 25 for further processing by other elements of apparatus 20.
  • transceiver 28 may be capable of transmitting and receiving signals or data directly.
  • apparatus 20 may include an input and/or output device (I/O device).
  • apparatus 20 may further include a user interface, such as a graphical user interface or touchscreen.
  • memory 24 stores software modules that provide functionality when executed by processor 22.
  • the modules may include, for example, an operating system that provides operating system functionality for apparatus 20.
  • the memory may also store one or more functional modules, such as an application or program, to provide additional functionality for apparatus 20.
  • the components of apparatus 20 may be implemented in hardware, or as any suitable combination of hardware and software.
  • apparatus 20 may optionally be configured to communicate with apparatus 10 via a wireless or wired communications link 70 according to any radio access technology, such as NR.
  • processor 22 and memory 24 may be included in or may form a part of processing circuitry or control circuitry.
  • transceiver 28 may be included in or may form a part of transceiving circuitry.
  • apparatus 20 may be a UE, SL UE, relay UE, mobile device, mobile station, ME, IoT device and/or NB-IoT device, or the like, for example.
  • apparatus 20 may be controlled by memory 24 and processor 22 to perform the functions associated with any of the embodiments described herein, such as one or more of the operations illustrated in, or described with respect to, Figs. 2-4, 5A, 5B, 6A, 6B, 7A, or any other method described herein.
  • apparatus 20 may be controlled to perform a process relating to handling temporary Fl-U tunnel for MBS mobility, as described in detail elsewhere herein.
  • an apparatus may include means for performing a method, a process, or any of the variants discussed herein.
  • the means may include one or more processors, memory, controllers, transmitters, receivers, and/or computer program code for causing the performance of the operations.
  • certain example embodiments provide several technological improvements, enhancements, and/or advantages over existing technological processes and constitute an improvement at least to the technological field of wireless network control and/or management.
  • certain embodiments provide an approach for transmitting forwarded and buffered data to the DU PtP leg.
  • certain embodiments provide a solution for transmitting the forwarded and buffered data in a case where the target network node (e.g., gNB) is split between CU and DU, such as, but not limited to, in a multi vendor scenario.
  • Example embodiments avoid the complexity of mixing traffic over the shared Fl-U tunnel.
  • some example embodiments minimize packet loss during mobility when the target network node is split into a CU node and DU node, which may or may not be owned by different vendors. For instance, some example embodiments can provide methods for sending, to the UE, the forwarded and buffered data over the radio PtP leg of the UE until this leg has caught up to the PtM leg of the UE, e.g., when the target gNB is split between CU and DU. Accordingly, the use of certain example embodiments results in improved functioning of communications networks and their nodes, such as base stations, eNBs, gNBs, and/or IoT devices, UEs or mobile stations.
  • communications networks and their nodes such as base stations, eNBs, gNBs, and/or IoT devices, UEs or mobile stations.
  • any of the methods, processes, signaling diagrams, algorithms or flow charts described herein may be implemented by software and/or computer program code or portions of code stored in memory or other computer readable or tangible media, and may be executed by a processor.
  • an apparatus may include or be associated with at least one software application, module, unit or entity configured as arithmetic operation(s), or as a program or portions of programs (including an added or updated software routine), which may be executed by at least one operation processor or controller.
  • Programs also called program products or computer programs, including software routines, applets and macros, may be stored in any apparatus-readable data storage medium and may include program instructions to perform particular tasks.
  • a computer program product may include one or more computer-executable components which, when the program is run, are configured to carry out some example embodiments.
  • the one or more computer-executable components may be at least one software code or portions of code. Modifications and configurations required for implementing the functionality of an example embodiment may be performed as routine(s), which may be implemented as added or updated software routine(s).
  • software routine(s) may be downloaded into the apparatus.
  • software or computer program code or portions of code may be in source code form, object code form, or in some intermediate form, and may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program.
  • carrier may include a record medium, computer memory, read-only memory, photoelectrical and/or electrical carrier signal, telecommunications signal, and/or software distribution package, for example.
  • the computer program may be executed in a single electronic digital computer or it may be distributed amongst a number of computers.
  • the computer readable medium or computer readable storage medium may be a non-transitory medium.
  • example embodiments may be performed by hardware or circuitry included in an apparatus, for example through the use of an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array (FPGA), or any other combination of hardware and software.
  • ASIC application specific integrated circuit
  • PGA programmable gate array
  • FPGA field programmable gate array
  • the functionality of example embodiments may be implemented as a signal, such as a non-tangible means, that can be carried by an electromagnetic signal downloaded from the Internet or other network.
  • an apparatus such as a node, device, or a corresponding component, may be configured as circuitry, a computer or a microprocessor, such as single-chip computer element, or as a chipset, which may include at least a memory for providing storage capacity used for arithmetic operation(s) and/or an operation processor for executing the arithmetic operation(s).
  • Example embodiments described herein may apply to both singular and plural implementations, regardless of whether singular or plural language is used in connection with describing certain embodiments.
  • an embodiment that describes operations of a single network node may also apply to embodiments that include multiple instances of the network node, and vice versa.

Landscapes

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

Abstract

L'invention concerne des systèmes, des procédés, des appareils et des produits programmes d'ordinateur pour la gestion d'un tunnel Fl-U temporaire pour une mobilité de service de diffusion/multidiffusion (MBS).
PCT/EP2022/054502 2021-04-19 2022-02-23 Gestion de tunnel f1-u temporaire pour mobilité de service de diffusion/multidiffusion (mbs) WO2022223178A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202163176605P 2021-04-19 2021-04-19
US63/176,605 2021-04-19

Publications (1)

Publication Number Publication Date
WO2022223178A1 true WO2022223178A1 (fr) 2022-10-27

Family

ID=80933763

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2022/054502 WO2022223178A1 (fr) 2021-04-19 2022-02-23 Gestion de tunnel f1-u temporaire pour mobilité de service de diffusion/multidiffusion (mbs)

Country Status (1)

Country Link
WO (1) WO2022223178A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2451211A1 (fr) * 2009-07-02 2012-05-09 Huawei Technologies Co., Ltd. Procédé et appareil destinés à traiter un transfert lors d'une transmission sans fil à liaison terrestre autonome
US20180367273A1 (en) * 2017-06-16 2018-12-20 Kyungmin Park Distributed Unit Status Information
WO2020095804A1 (fr) * 2018-11-09 2020-05-14 Sharp Kabushiki Kaisha Réseau et procédés pour prendre en charge une mobilité inter-domaine dans un réseau d'accès radio virtualisé
WO2020175490A1 (fr) * 2019-02-27 2020-09-03 Sharp Kabushiki Kaisha Réseau d'accès radio et procédés

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2451211A1 (fr) * 2009-07-02 2012-05-09 Huawei Technologies Co., Ltd. Procédé et appareil destinés à traiter un transfert lors d'une transmission sans fil à liaison terrestre autonome
US20180367273A1 (en) * 2017-06-16 2018-12-20 Kyungmin Park Distributed Unit Status Information
WO2020095804A1 (fr) * 2018-11-09 2020-05-14 Sharp Kabushiki Kaisha Réseau et procédés pour prendre en charge une mobilité inter-domaine dans un réseau d'accès radio virtualisé
WO2020175490A1 (fr) * 2019-02-27 2020-09-03 Sharp Kabushiki Kaisha Réseau d'accès radio et procédés

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INCORPORATED: "Data forwarding in handover with NR multicast", vol. RAN WG3, no. Online; 20210125 - 20210205, 15 January 2021 (2021-01-15), XP051975071, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG3_Iu/TSGR3_111-e/Docs/R3-210369.zip R3-210369_Data forwarding in handover with NR multicast.doc> [retrieved on 20210115] *
SAMSUNG: "TP for MBS BL CR for 38.473-Bearer management for broadcasting over F1", vol. RAN WG3, no. 20210125 - 20210204, 15 January 2021 (2021-01-15), XP051974959, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG3_Iu/TSGR3_111-e/Docs/R3-210226.zip R3-210226 Text Proposal for 38.473.doc> [retrieved on 20210115] *

Similar Documents

Publication Publication Date Title
EP3855804B1 (fr) Surveillance du temps de survie et transfert de statut pour une communication sans fil sensible au temps
US11729046B2 (en) Failure indication of master cell group with fallback to radio resource control re-establishment
WO2022234458A1 (fr) Enregistrement efficace dans une zone où un service de tranche est partiellement pris en charge
US20220322048A1 (en) Distributing multicast packets in individual protocol data unit (pdu) sessions
EP4014693A1 (fr) Commande d&#39;opérations d&#39;un noeud d&#39;accès et de liaison terrestre intégrés (iab)
WO2023065279A1 (fr) Commutation de partie de bande passante (bwp) pour une transmission de données de petite taille à autorisation configurée
US20230105497A1 (en) Reduced channel state information reporting time for cell activation
WO2023285099A1 (fr) Interfonctionnement entre un transfert de couche 3 (l3) et un changement intercellulaire centrique de couche 1 (l1)/couche 2 (l2)
EP3742860B1 (fr) Solutions améliorant la mobilité sans réponse d&#39;accès aléatoire
WO2023055368A1 (fr) Sessions d&#39;unités de données de protocole spécifiques à une application
WO2022223178A1 (fr) Gestion de tunnel f1-u temporaire pour mobilité de service de diffusion/multidiffusion (mbs)
EP4239956A2 (fr) Restauration d&#39;un service de multidiffusion/diffusion après défaillance de la fonction du plan utilisateur de multidiffusion/diffusion sans redémarrage
EP4240100A1 (fr) Restauration de service de diffusion pour service de diffusion/multidiffusion lors d&#39;une défaillance ou d&#39;un redémarrage d&#39;un noeud d&#39;accès radio
US20230328578A1 (en) Selection of shared central unit user plane by central unit control plane
US20230216776A1 (en) Methods and apparatuses for configuration of user device(s) for reception of point-to-multipoint transmission
EP4239957A2 (fr) Restauration d&#39;un service de multidiffusion/diffusion après défaillance de multidiffusion/diffusion avec redémarrage
US20240236905A1 (en) Efficient registration in an area where a service is supported partially
US20230269016A1 (en) Working clock determination for a mobile user equipment
EP4366207A1 (fr) Gestion de distribution de données sans perte pendant une commutation de trajet indirect d&#39;un équipement utilisateur basé sur une liaison latérale à un relais de réseau
US12041498B2 (en) Controlling operations of an integrated access and backhaul (IAB) node
US20240023176A1 (en) Method of intra-next-generation-node-b mobility
WO2024077606A1 (fr) Établissement de trajet indirect rapide pour un équipement utilisateur de liaison latérale à un relais de réseau
US20230269795A1 (en) Methods and apparatuses for user plane function control for multicast transport
WO2023272665A1 (fr) Procédé, dispositif et support lisible par ordinateur pour la communication
WO2022028774A1 (fr) Transfert de pile de protocoles de communication actifs doubles en cascade pour réduire l&#39;interruption

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

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

Country of ref document: EP

Kind code of ref document: A1