WO2023187662A1 - Support de mobilité pour nœud de liaison terrestre et d'accès intégré (iab) avec équipements utilisateurs (ue) connectés - Google Patents

Support de mobilité pour nœud de liaison terrestre et d'accès intégré (iab) avec équipements utilisateurs (ue) connectés Download PDF

Info

Publication number
WO2023187662A1
WO2023187662A1 PCT/IB2023/053099 IB2023053099W WO2023187662A1 WO 2023187662 A1 WO2023187662 A1 WO 2023187662A1 IB 2023053099 W IB2023053099 W IB 2023053099W WO 2023187662 A1 WO2023187662 A1 WO 2023187662A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
iab
ues
network
message
Prior art date
Application number
PCT/IB2023/053099
Other languages
English (en)
Inventor
Paul Schliwa-Bertling
Qian Chen
Filip BARAC
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 WO2023187662A1 publication Critical patent/WO2023187662A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0009—Control or signalling for completing the hand-off for a plurality of users or terminals, e.g. group communication or moving wireless networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H04W36/083—Reselecting an access point wherein at least one of the access points is a moving node
    • 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/12—Access point controller devices

Definitions

  • the present disclosure relates to operations of a cellular communications systems for providing mobility support for Integrated Access and Backhaul (IAB) nodes.
  • IAB Integrated Access and Backhaul
  • IAB Integrated Access and Backhaul
  • An IAB node can be connected to the 5G system via an IAB donor node first. Then UEs can connect to IAB node which provide the access to 5G system.
  • IAB node moves from one IAB donor node to another IAB donor node with UEs connected to the IAB node.
  • Embodiments of a method performed by a network node implementing a target IAB donor node central unit (CU) of a telecommunications network are disclosed herein.
  • the method comprises triggering a move of a plurality of UEs connected to an IAB node to switch to the target IA donor node CU via a source IAB donor node CU.
  • the method further comprises triggering a path switch procedure towards a core network of the telecommunications network for all UEs of the plurality of UEs connected to the IAB node.
  • Embodiments of a network node implementing a target IAB donor node CU of a telecommunications network are also disclosed herein.
  • the network node comprises a network interface, and processing circuitry associated with the network interface.
  • the processing circuitry configured to cause the network node to trigger a move of a plurality of UEs connected to an IAB node to switch to the target IA donor node CU via a source IAB donor node CU.
  • the processing circuitry is further configured to trigger a path switch procedure towards a core network of the telecommunications network for all UEs of the plurality of UEs connected to the IAB node.
  • Embodiments of a network node implementing a target IAB donor node CU of a telecommunications network are also disclosed herein.
  • the network node is adapted to trigger a move of a plurality of UEs connected to an IAB node to switch to the target IA donor node CU via a source IAB donor node CU.
  • the network node is further adapted to trigger a path switch procedure towards a core network of the telecommunications network for all UEs of the plurality of UEs connected to the IAB node.
  • Embodiments of a method performed by a network node implementing a target IAB donor node CU of a telecommunications network are also disclosed herein.
  • the method comprises receiving, from a source IAB donor node CU via a core network (CN) of the telecommunications network, a message comprising resource information for a plurality of UEs connected to the IAB node.
  • the method further comprises providing, to the CN, a message comprising a new RRC configuration for an IAB mobile termination (MT) and resource information allocated for each UE of the plurality of UEs.
  • MT IAB mobile termination
  • the method also comprises triggering a move of the plurality of UEs to switch to the target IAB donor node CU via the CN and the source IAB donor node CU.
  • the method additionally comprises triggering a towards the CN, including a list of the plurality of UEs, to inform the CN of a successfully move of the plurality of UEs.
  • triggering the move of the plurality of UEs to switch to the target IAB donor node CU via the CN and the source IAB donor node CU comprises sending a Next Generation Application Protocol (NGAP) message to the CN to request Radio Resource Control (RRC) reconfiguration of the plurality of UEs, the NGAP message comprising RRC reconfiguration information for each UE of the plurality of UEs.
  • NGAP Next Generation Application Protocol
  • RRC Radio Resource Control
  • Some embodiments may provide that triggering the move of the plurality of UEs to switch to the target IAB donor node CU via the CN and the source IAB donor node CU comprises sending a message via the CN to the source IAB donor node CU to trigger the move of the plurality of UEs.
  • Embodiments of a network node implementing a target IAB donor node CU of a telecommunications network are also disclosed herein.
  • the network node comprises a network interface, and processing circuitry associated with the network interface.
  • the processing circuitry is configured to cause the network node to receive, from a source IAB donor node CU via a CN of the telecommunications network, a message comprising resource information for a plurality of UEs connected to the IAB node.
  • the processing circuitry is further configured to provide, to the CN, a message comprising a new RRC configuration for an IAB MT and resource information allocated for each UE of the plurality of UEs.
  • the processing circuitry is also configured to trigger a move of the plurality of UEs to switch to the target IAB donor node CU via the CN and the source IAB donor node CU.
  • the processing circuitry is additionally configured to trigger a handover-notify message towards the CN, including a list of the plurality of UEs, to inform the CN of a successful move of the plurality of UEs.
  • the processing circuitry is further configured to cause the network node to perform any of the operations attributed to the network node above.
  • Embodiments of a network node implementing a target IAB donor node CU of a telecommunications network are also disclosed herein.
  • the network node is adapted to receive, from a source IAB donor node CU via a CN of the telecommunications network, a message comprising resource information for a plurality of UEs connected to the IAB node.
  • the network node is further adapted to provide, to the CN, a message comprising a new RRC configuration for an IAB MT and resource information allocated for each UE of the plurality of UEs.
  • the network node is also adapted to trigger a move of the plurality of UEs to switch to the target IAB donor node CU via the CN and the source IAB donor node CU.
  • the network node is additionally adapted to trigger a handover-notify message towards the CN, including a list of the plurality of UEs, to inform the CN of a successful move of the plurality of UEs.
  • the network node is further adapted to perform any of the operations attributed to the network node above.
  • Embodiments of a method performed by a network node of a CN of a telecommunications network are also disclosed herein.
  • the method comprises receiving, from a source IAB donor node CU, a message comprising a list of information for a plurality of UEs connected to the IAB node.
  • the method further comprises preparing for handover for an IAB MT and all UEs of the plurality of UEs.
  • the method also comprises sending, to a target IAB donor node CU, a message comprising resource information for the plurality of UEs connected to the IAB node.
  • Some embodiments may provide that the method further comprises receiving, from the target IAB donor node CU, an NGAP message to request Radio Resource Configuration (RRC) reconfiguration of the plurality of UEs, the NGAP message comprising RRC reconfiguration information for each UE of the plurality of UEs, and sending the NGAP message to the source IAB donor node CU.
  • RRC Radio Resource Configuration
  • the method may further comprise receiving, from the target IAB donor node CU, an NGAP message to request the source IAB donor node CU to trigger the mobility of the plurality of UEs connected to the IAB node, and sending the NGAP message to the source IAB donor node CU to request the source IAB donor CU to trigger the mobility of the plurality of UEs connected to the IAB node.
  • the method may further comprise sending an NGAP UE-CONTEXT-RELEASE-COMMAND message to the source IAB donor node CU, the message including a list of the plurality of UEs.
  • Embodiments of a network node of a CN of a telecommunications network are also disclosed herein.
  • the network node com comprises a network interface, and processing circuitry associated with the network interface.
  • the processing circuitry is configured to cause the network node to receive, from a source IAB donor node CU a message comprising a list of information for a plurality of UEs connected to the IAB node.
  • the processing circuitry is further configured to cause the network node to prepare for handover for an IAB MT and all UEs of the plurality of UEs.
  • the processing circuitry is also configured to cause the network node to send, to a target IAB donor node CU, a message comprising resource information for the plurality of UEs connected to the IAB node.
  • the processing circuitry is further configured to cause the network node to perform any of the operations attributed to the network node above.
  • Embodiments of a network node of a CN of a telecommunications network are also disclosed herein.
  • the network node is adapted to receive, from a source IAB donor node CU a message comprising a list of information for a plurality of UEs connected to the IAB node.
  • the network node is further adapted to prepare for handover for an IAB MT and all UEs of the plurality of UEs.
  • the network node is also adapted to send, to a target IAB donor node CU, a message comprising resource information for the plurality of UEs connected to the IAB node.
  • the network node is further adapted to perform any of the operations attributed to the network node above.
  • Embodiments of a method performed by a network node implementing a source IAB donor node CU of a telecommunications network are also disclosed.
  • the method comprises sending, to a target IAB donor node CU via a CN of the telecommunications network, a message comprising resource information for a plurality of UEs connected to the IAB node.
  • the method further comprises receiving a message via the CN from the target IAB donor node CU to trigger a move of the plurality of UEs.
  • Figure 1 illustrates one example of a cellular communications system in which some embodiments of the present disclosure may be implemented
  • Figure 2 illustrates a wireless communication system represented as a 5G network architecture composed of core Network Functions (NFs), where interaction between any two NFs is represented by a point-to-point reference point/interface according to some embodiments of the present disclosure
  • NFs core Network Functions
  • Figure 3 illustrates a 5G network architecture using service-based interfaces between NFs in a control plane (CP) (instead of the point-to-point reference points/interfaces used in the 5G network architecture of Figure 2) according to some embodiments of the present disclosure
  • Figure 4 illustrates mobility of an Integrated Access and Backhaul (IAB) node together with connected User Equipments (UEs) according to some embodiments of the present disclosure
  • IAB Integrated Access and Backhaul
  • Figures 5A-5B show an example of an IAB node move from an old IAB donor node to a new IAB donor node according to some embodiments of the present disclosure
  • Figures 6A-6C shows another example of an IAB node move from an old IAB donor node to a new IAB donor node according to some embodiments of the present disclosure
  • Figure 7 is a schematic block diagram of a radio access node according to some embodiments of the present disclosure.
  • Figure 8 is a schematic block diagram that illustrates a virtualized embodiment of the radio access node of Figure 7 according to some embodiments of the present disclosure
  • Figure 9 is a schematic block diagram of the radio access node of Figure 7 according to some other embodiments of the present disclosure.
  • Figure 10 is a schematic block diagram of a wireless communication device according to some embodiments of the present disclosure.
  • Figure 11 is a schematic block diagram of the wireless communication device of Figure 10 according to some other embodiments of the present disclosure.
  • IAB Integrated Access and Backhaul
  • two parts of the IAB node, IAB-MT and IAB-DU are moved separately first. All User Equipments (UEs) connected to the IAB node are moved as well. The move of the UEs connected to the IAB node are handled as a group.
  • aspects disclosed herein provide a solution to support the IAB node mobility together with the UEs connected to the IAB node.
  • Embodiments disclosed herein may provide one or more of the following technical advantage(s).
  • such embodiments provide mobility with service continuity for connected UEs during IAB node mobility.
  • group UE handling provides efficient mobility handling.
  • Radio Node As used herein, a "radio node” is either a radio access node or a wireless communication device.
  • Radio Access Node As used herein, a “radio access node” or “radio network node” or “radio access network node” is any node in a Radio Access Network (RAN) of a cellular communications network that operates to wirelessly transmit and/or receive signals.
  • RAN Radio Access Network
  • a radio access node examples include, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB) in a Third Generation Partnership Project (3GPP) Fifth Generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP Long Term Evolution (LTE) network), a high-power or macro base station, a low-power base station (e.g., a micro base station, a pico base station, a home eNB, or the like), a relay node, a network node that implements part of the functionality of a base station (e.g., a network node that implements a gNB Central Unit (gNB-CU) or a network node that implements a gNB Distributed Unit (gNB-DU)) or a network node that implements part of the functionality of some other type of radio access node.
  • a base station e.g., a New Radio (NR) base station (gNB)
  • Core Network Node is any type of node in a core network or any node that implements a core network function.
  • Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), a Service Capability Exposure Function (SCEF), a Home Subscriber Server (HSS), or the like.
  • MME Mobility Management Entity
  • P-GW Packet Data Network Gateway
  • SCEF Service Capability Exposure Function
  • HSS Home Subscriber Server
  • a core network node examples include a node implementing an Access and Mobility Management Function (AMF), a User Plane Function (UPF), a Session Management Function (SMF), an Authentication Server Function (AUSF), a Network Slice Selection Function (NSSF), a Network Exposure Function (NEF), a Network Function (NF) Repository Function (NRF), a Policy Control Function (PCF), a Unified Data Management (UDM), or the like.
  • AMF Access and Mobility Management Function
  • UPF User Plane Function
  • SMF Session Management Function
  • AUSF Authentication Server Function
  • NSSF Network Slice Selection Function
  • NEF Network Exposure Function
  • NRF Network Exposure Function
  • NRF Network Exposure Function
  • PCF Policy Control Function
  • UDM Unified Data Management
  • a "communication device” is any type of device that has access to an access network.
  • Some examples of a communication device include, but are not limited to: mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or Personal Computer (PC).
  • the communication device may be a portable, hand-held, computer-comprised, or vehiclemounted mobile device, enabled to communicate voice and/or data via a wireless or wireline connection.
  • Wireless Communication Device One type of communication device is a wireless communication device, which may be any type of wireless device that has access to (i.e., is served by) a wireless network (e.g., a cellular network).
  • a wireless communication device include, but are not limited to: a User Equipment device (UE) in a 3GPP network, a Machine Type Communication (MTC) device, and an Internet of Things (loT) device.
  • UE User Equipment
  • MTC Machine Type Communication
  • LoT Internet of Things
  • Such wireless communication devices may be, or may be integrated into, a mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or PC.
  • the wireless communication device may be a portable, hand-held, computer-comprised, or vehicle-mounted mobile device, enabled to communicate voice and/or data via a wireless connection.
  • Network Node As used herein, a "network node” is any node that is either part of the RAN or the core network of a cellular communications network/system.
  • TRP Transmission/Reception Point
  • a TRP may be either a network node, a radio head, a spatial relation, or a Transmission Configuration Indicator (TCI) state.
  • a TRP may be represented by a spatial relation or a TCI state in some embodiments.
  • a TRP may be using multiple TCI states.
  • a TRP may a part of the gNB transmitting and receiving radio signals to/from UE according to physical layer properties and parameters inherent to that element.
  • multi-TRP Multiple TRP
  • a serving cell can schedule UE from two TRPs, providing better Physical Downlink Shared Channel (PDSCH) coverage, reliability and/or data rates.
  • PDSCH Physical Downlink Shared Channel
  • DCI Downlink Control Information
  • MAC Medium Access Control
  • a set Transmission Points is a set of geographically co-located transmit antennas (e.g., an antenna array (with one or more antenna elements)) for one cell, part of one cell or one Positioning Reference Signal (PRS) -only TP.
  • TPs can include base station (eNB) antennas, Remote Radio Heads (RRHs), a remote antenna of a base station, an antenna of a PRS-only TP, etc.
  • eNB base station
  • RRHs Remote Radio Heads
  • One cell can be formed by one or multiple TPs. For a homogeneous deployment, each TP may correspond to one cell.
  • a set of TRPs is a set of geographically co-located antennas (e.g., an antenna array (with one or more antenna elements)) supporting TP and/or Reception Point (RP) functionality.
  • RP Reception Point
  • FIG. 1 illustrates one example of a cellular communications system 100 in which embodiments of the present disclosure may be implemented.
  • the cellular communications system 100 is a 5G system (5GS) including a Next Generation RAN (NG-RAN) and a 5G Core (5GC).
  • the RAN includes base stations 102-1 and 102-2, which in the 5GS include NR base stations (gNBs) and optionally next generation eNBs (ng-eNBs) (e.g., LTE RAN nodes connected to the 5GC), controlling corresponding (macro) cells 104-1 and 104-2.
  • the base stations 102-1 and 102-2 are generally referred to herein collectively as base stations 102 and individually as base station 102.
  • the (macro) cells 104-1 and 104-2 are generally referred to herein collectively as (macro) cells 104 and individually as (macro) cell 104.
  • the RAN may also include a number of low power nodes 106-1 through 106-4 controlling corresponding small cells 108-1 through 108-4.
  • the low power nodes 106-1 through 106-4 can be small base stations (such as pico or femto base stations) or RRHs, or the like.
  • one or more of the small cells 108-1 through 108-4 may alternatively be provided by the base stations 102.
  • the low power nodes 106-1 through 106-4 are generally referred to herein collectively as low power nodes 106 and individually as low power node 106.
  • the cellular communications system 100 also includes a core network 110, which in the 5G System (5GS) is referred to as the 5GC.
  • the base stations 102 (and optionally the low power nodes 106) are connected to the core network 110.
  • the base stations 102 and the low power nodes 106 provide service to wireless communication devices 112-1 through 112-5 in the corresponding cells 104 and 108.
  • the wireless communication devices 112-1 through 112-5 are generally referred to herein collectively as wireless communication devices 112 and individually as wireless communication device 112.
  • the wireless communication devices 112 are oftentimes UEs, but the present disclosure is not limited thereto.
  • Figure 2 illustrates a wireless communication system represented as a 5G network architecture composed of core Network Functions (NFs), where interaction between any two NFs is represented by a point-to-point reference point/interface.
  • Figure 2 can be viewed as one particular implementation of the system 100 of Figure 1.
  • the 5G network architecture shown in Figure 2 comprises a plurality of UEs 112 connected to either a RAN 102 or an Access Network (AN) as well as an AMF 200.
  • the R(AN) 102 comprises base stations, e.g., such as eNBs or gNBs or similar.
  • the 5GC NFs shown in Figure 2 include a NSSF 202, an AUSF 204, a UDM 206, the AMF 200, a SMF 208, a PCF 210, and an Application Function (AF) 212.
  • NSSF 202 Seen from the core network side, the 5GC NFs shown in Figure 2 include a NSSF 202, an AUSF 204, a UDM 206, the AMF 200, a SMF 208, a PCF 210, and an Application Function (AF) 212.
  • AF Application Function
  • the N1 reference point is defined to carry signaling between the UE 112 and AMF 200.
  • the reference points for connecting between the AN 102 and AMF 200 and between the AN 102 and UPF 214 are defined as N2 and N3, respectively.
  • N4 is used by the SMF 208 and UPF 214 so that the UPF 214 can be set using the control signal generated by the SMF 208, and the UPF 214 can report its state to the SMF 208.
  • N9 is the reference point for the connection between different UPFs 214
  • N14 is the reference point connecting between different AMFs 200, respectively.
  • N15 and N7 are defined since the PCF 210 applies policy to the AMF 200 and SMF 208, respectively.
  • N12 is required for the AMF 200 to perform authentication of the UE 112.
  • N8 and N10 are defined because the subscription data of the UE 112 is required for the AMF 200 and SMF 208.
  • the 5GC network aims at separating UP and CP.
  • the UP carries user traffic while the CP carries signaling in the network.
  • the UPF 214 is in the UP and all other NFs, i.e., the AMF 200, SMF 208, PCF 210, AF 212, NSSF 202, AUSF 204, and UDM 206, are in the CP.
  • Separating the UP and CP guarantees each plane resource to be scaled independently. It also allows UPFs to be deployed separately from CP functions in a distributed fashion. In this architecture, UPFs may be deployed very close to UEs to shorten the Round Trip Time (RTT) between UEs and data network for some applications requiring low latency.
  • RTT Round Trip Time
  • the core 5G network architecture is composed of modularized functions.
  • the AMF 200 and SMF 208 are independent functions in the CP. Separated AMF 200 and SMF 208 allow independent evolution and scaling.
  • Other CP functions like the PCF 210 and AUSF 204 can be separated as shown in Figure 2.
  • Modularized function design enables the 5GC network to support various services flexibly.
  • Each NF interacts with another NF directly. It is possible to use intermediate functions to route messages from one NF to another NF.
  • a set of interactions between two NFs is defined as service so that its reuse is possible. This service enables support for modularity.
  • the UP supports interactions such as forwarding operations between different UPFs.
  • Figure 3 illustrates a 5G network architecture using service-based interfaces between the NFs in the CP, instead of the point-to-point reference points/interfaces used in the 5G network architecture of Figure 2.
  • the NFs described above with reference to Figure 2 correspond to the NFs shown in Figure 3.
  • the service(s) etc. that a NF provides to other authorized NFs can be exposed to the authorized NFs through the service-based interface.
  • the service based interfaces are indicated by the letter "N" followed by the name of the NF, e.g., Namf for the service based interface of the AMF 200 and Nsmf for the service based interface of the SMF 208, etc.
  • the AMF 200 provides UE-based authentication, authorization, mobility management, etc.
  • a UE 112 even using multiple access technologies is basically connected to a single AMF 200 because the AMF 200 is independent of the access technologies.
  • the SMF 208 is responsible for session management and allocates Internet Protocol (IP) addresses to UEs. It also selects and controls the UPF 214 for data transfer. If a UE 112 has multiple sessions, different SMFs 208 may be allocated to each session to manage them individually and possibly provide different functionalities per session.
  • the AF 212 provides information on the packet flow to the PCF 210 responsible for policy control in order to support QoS.
  • the PCF 210 determines policies about mobility and session management to make the AMF 200 and SMF 208 operate properly.
  • the AUSF 204 supports authentication function for UEs or similar and thus stores data for authentication of UEs or similar while the UDM 206 stores subscription data of the UE 112.
  • the Data Network (DN) not part of the 5GC network, provides Internet access or operator services and similar.
  • An NF may be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g., a cloud infrastructure.
  • Solutions discussed herein address for support IAB node mobility between inter-IAB-donor-CU together with the UEs connected to the IAB node.
  • the solutions discussed herein address both mobility of the IAB-MT (e.g., during inter-IAB-donor-CU) as well as mobility of the UEs connected to the IAB-DU.
  • IAB node mobility with change of IAB donor node via Xn are first discussed.
  • the inter-IAB-donor-CU change of IAB-MT is supported due to topology adaptation for a single-connected IAB node.
  • the IAB-MT switches connection from an old path (e.g., via the old IAB donor node) to a new path (e.g., via new IAB donor node), while the IAB DU part of the IAB remains under the control of the old IAB donor node.
  • Support is also provided for the switch of the IAB-DU part from the old IAB donor node to the new IAB donor node.
  • the UE connects to the IAB node also switches from the old path to the new path via the new IAB donor node.
  • Figure 4 illustrates the mobility of an IAB node together with connected UEs according to some examples disclosed herein.
  • Figures 5A-5B show an example of the IAB node moves from old IAB donor node to the new IAB donor node (i.e., IAB node mobility for inter lAB-donor-CU with Xn interface).
  • the source lAB-donor-CU triggers the move of IAB-MT from south path to target path as specified in TS 38.401 for Rel-17.
  • the target lAB-donor-CU send NGAP Path Switch Request to AMF for the IAB-MT.
  • the operations in clause 4.9.1.2.2/4.9.1.2.3 between AMF/SMF/UPF(s) are performed.
  • the AMF sends the NGAP Path Switch Request Acknowledge message to target lAB-donor-CU.
  • the target lAB-donor-CU trigger the UE context release towards the source lAB-donor-CU which in turn triggers furth release of resource on the source path related to IAB-MT.
  • the Fl-C connection between migration IAB node and target lAB-donor-CU is established based on new TNL addresses information exchanged in step 500.
  • the target lAB-donor-CU configures BH RLC channels, BAP-sublayer routing entries and mapping rules on the target path. Note that the details of path and configuration management depend on the work in RAN WGs.
  • the target lAB-donor-CU triggers the move of the group of UEs connected to IAB node to switch to the target lAB-donor-CU via the source lAB-donor- CU. Note that the details of the move of UEs connected to IAB node depend on the work in RAN WGs. Operations then continue at step 514 in Figure 5B.
  • step 514 when UE connects to the target lAB- donor-CU via RRC signalling, the target lAB-donor-CU triggers the path switch procedure towards the 5GC for all the UEs connected to IAB node.
  • step 516 the steps in clause 4.9.1.2.2/4.9.1.2.3 between AMF/SMF/UPF(s) are performed.
  • the path switch operations are performed by these multiple old AMFs and new AMFs for the corresponding group of UEs.
  • the AMF sends the NGAP Path Switch Request Acknowledge message to target lAB-donor- CU.
  • the target lAB-donor-CU triggers the UE context release towards the source lAB-donor-CU which in turn triggers furth release of resource on the source path related to IAB-MT.
  • FIG. 6A-6C shows an example of the IAB node moves from old IAB donor node to the new IAB donor node (i.e., IAB node mobility for inter lAB-donor-CU with N2 interface).
  • the source lAB-donor-CU sends a HANDOVER REQUIRED message to the target lAB-donor- CU over the N2 interface. This message may also include a list of information for the UEs connected to the IAB node.
  • This message includes the request of migrating IAB node's TNL address information in the RRC container.
  • the ON prepare the handover for IAB-MT and all connected UEs as specified in step 2-8 of clause 4.9.1.3.2 in TS 23.502.
  • the ON sends the HANDOVER REQUEST message to target lAB-donor-CU, including the transparent container from source lAB-donor-CU and the resource information prepared in CN for all the UEs.
  • the target lAB-donor- CU performs admission control, allocates resources for lAB-MT/UEs connected to the IAB node involving target lAB-donor-DU. Note that the detailed handling of UEs connected to IAB node depends on the work in RAN WGs.
  • the target lAB-donor-CU provides the new RRC configuration for the IAB-MT as part of the HANDOVER REQUEST ACKNOWLEDGE message.
  • the RRC configuration includes a BAP address of the lAB-donor-DU in the target lAB-donor-CU's topology, default BH RLC channel and a default BAP routing ID configuration for UL Fl- C/non-Fl traffic mapping on the target path.
  • the RRC configuration may include the new TNL address(es) anchored at the target lAB-donor-DU for the migrating node as requested in step 1.
  • the target lAB-donor-CU also provides the resource information allocated for all connected UEs.
  • the CN performs steps 11-12 of clause 4.9.1.3.2 in TS 23.502 for IAB-MT and all connected UEs.
  • the CN sends the HANDOVER COMMAND to source lAB-donor-CU including the RRC configuration information received in step 5.
  • the source lAB-donor-CU performs steps 2-3 of clause 4.9.1.3.3 of 23.502 for IAB-MT of the migrating IAB node.
  • the IAB-MT of the migrating IAB node performs step 4 of clause 4.9.1.3.3 towards the target lAB-donor-CU.
  • the target lAB-donor-CU triggers the NGAP HANDOVER NOTIFY message towards the 5GC for the migrating IAB-MT.
  • the ON and the IAB-MT of the IAB node perform steps 6-12 of clause 4.9.1.3.3 in TS 23.502 for the IAB-MT.
  • the ON triggers NGAP UE CONTEXT RELEASE COMMAND message towards the source lAB- donor-CU which in turn triggers furth release of resource on the source path related to IAB-MT. Operations then continue at step 622 of Figure 6B.
  • the Fl-C connection between migration IAB node and target lAB-donor-CU is established based on new TNL addresses information for IAB node exchanged in step 5.
  • the target lAB-donor-CU configures BH RLC channels, BAP-sublayer routing entries and mapping rules on the target path.
  • the target lAB-donor-CU triggers the move of the group of UEs connected to IAB node to switch to the target lAB-donor-CU via CN and source lAB-donor-CU.
  • One alternative for step 624 is based on the handlings in step 600-608 above that the resources for the all UEs connected to the IAB node are prepared at the target path.
  • the target lAB-donor-CU performs further the following:
  • the target lAB-donor-CU sends a NGAP message, e.g., Connected UE Reconfiguration Request message to CN (e.g., target AMF) to request the RRC reconfiguration of the UEs connected to the migrating IAB node.
  • CN e.g., target AMF
  • the message includes RRC Reconfiguration information for all connected UEs.
  • the target AMF sends a message to source AMF, e.g., the Namf_COMMUNICATIN_N2infoNotify including the RRC Reconfiguration information for all connected UEs.
  • source AMF e.g., the Namf_COMMUNICATIN_N2infoNotify including the RRC Reconfiguration information for all connected UEs.
  • the CN e.g., the source AMF
  • sends the NGAP message e.g., Connected UE Reconfiguration Command message to the source lAB-donor-CU including the RRC reconfiguration information.
  • step 624 Another alternative for step 624 is based on that there is no handling of the UEs connected to the IAB node in step 600-608 above.
  • the target lAB-donor-CU needs to trigger the source lAB-donor-CU node to trigger the move of the UEs connected to the IAB node with separate signalling: [0067]
  • steps 624b.l-624b.3 The target lAB-donor-CU sends message via CN to source lAB-donor-CU to trigger the move of UEs connected to the IAB node.
  • Example messages e.g., NGAP messages in steps 624b.l/624b.3 and service operation between AMFs in steps 624b.2 are showing in the figure. These messages may not be linked to a particular UE.
  • steps 624b.4-624.11 After receiving the request from target lAB-donor-CU above, the source lAB-donor-CU performs the steps as specified in clause 4.9.1.2.2/3 in TS 23.502 with following enhancement: the NGAP messages between RAN and CN, and the service operations between AMFs (e.g., steps 624b.4 1 624b.5 I 624b.7 1 624b.9 1 624b.11) includes the list of UEs connected to the IAB node. The message may link to one of the UE that connected to the IAB node or it's not linked to a specific UE.
  • the source lAB-donor-CU via migrating IAB node, sends the RRCReconfiguration message to each connected UE based on one of the two alternatives discussed above. It is to be understood that, in circumstances in which the UEs served by a mobile node are served by different AMFs (e.g., different AMFs within a set of AMFs, or even different AMFs from different sets of AMFs), the group signalling described above between the RAN and the CN is performed towards these multiple old AMFs and new AMFs for the corresponding group of UEs. Operations then resume at step 626 in Figure 6C.
  • AMFs e.g., different AMFs within a set of AMFs, or even different AMFs from different sets of AMFs
  • the UEs connect to the migrating IAB node perform step 4 of clause 4.9.1.3.3 towards the target lAB-donor-CU as a response to the RRC reconfiguration in step 624.
  • the target lAB-donor-CU triggers the HANDOVER NOTIFY message towards 5GC including the list of UEs connected to the IAB node.
  • the CN performs steps 6-11 of clause 4.9.1.3.3 in TS.23.502 for all connected UEs.
  • the CN sends NGAP UE CONTEXT RELEASE COMMAND message to the source lAB-donor-CU including the list of UEs connected to the IAB node.
  • the source lAB-donor-CU triggers the release of resource on the source path.
  • the impacts on services, entities, and interfaces are as follows:
  • FIG. 7 is a schematic block diagram of a radio access node 700 according to some embodiments of the present disclosure.
  • the radio access node 700 may be, for example, a base station 102 or 106 or a network node that implements all or part of the functionality of the base station 102 or gNB described herein.
  • the radio access node 700 includes a control system 702 that includes one or more processors 704 (e.g., Central Processing Units (CPUs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), and/or the like), memory 706, and a network interface 708.
  • the one or more processors 704 are also referred to herein as processing circuitry.
  • the radio access node 700 may include one or more radio units 710 that each includes one or more transmitters 712 and one or more receivers 714 coupled to one or more antennas 716.
  • the radio units 710 may be referred to or be part of radio interface circuitry.
  • the radio unit(s) 710 is external to the control system 702 and connected to the control system 702 via, e.g., a wired connection (e.g., an optical cable).
  • the radio unit(s) 710 and potentially the antenna(s) 716 are integrated together with the control system 702.
  • the one or more processors 704 operate to provide one or more functions of a radio access node 700 as described herein.
  • the function(s) are implemented in software that is stored, e.g., in the memory 706 and executed by the one or more processors 704.
  • Figure 8 is a schematic block diagram that illustrates a virtualized embodiment of the radio access node 700 according to some embodiments of the present disclosure. This discussion is equally applicable to other types of network nodes. Further, other types of network nodes may have similar virtualized architectures. Again, optional features are represented by dashed boxes.
  • a "virtualized" radio access node is an implementation of the radio access node 700 in which at least a portion of the functionality of the radio access node 700 is implemented as a virtual component(s) (e.g., via a virtual machine(s) executing on a physical processing node(s) in a network(s)).
  • the radio access node 700 may include the control system 702 and/or the one or more radio units 710, as described above.
  • the control system 702 may be connected to the radio unit(s) 710 via, for example, an optical cable or the like.
  • the radio access node 700 includes one or more processing nodes 800 coupled to or included as part of a network(s) 802.
  • Each processing node 800 includes one or more processors 804 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 806, and a network interface 808.
  • processors 804 e.g., CPUs, ASICs, FPGAs, and/or the like
  • functions 810 of the radio access node 700 described herein are implemented at the one or more processing nodes 800 or distributed across the one or more processing nodes 800 and the control system 702 and/or the radio unit(s) 710 in any desired manner.
  • some or all of the functions 810 of the radio access node 700 described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment(s) hosted by the processing node(s) 800.
  • additional signaling or communication between the processing node(s) 800 and the control system 702 is used in order to carry out at least some of the desired functions 810.
  • the control system 702 may not be included, in which case the radio unit(s) 710 communicate directly with the processing node(s) 800 via an appropriate network interface(s).
  • a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of radio access node 700 or a node (e.g., a processing node 800) implementing one or more of the functions 810 of the radio access node 700 in a virtual environment according to any of the embodiments described herein is provided.
  • a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).
  • FIG 9 is a schematic block diagram of the radio access node 700 according to some other embodiments of the present disclosure.
  • the radio access node 700 includes one or more modules 900, each of which is implemented in software.
  • the module(s) 900 provide the functionality of the radio access node 700 described herein. This discussion is equally applicable to the processing node 800 of Figure 8 where the modules 900 may be implemented at one of the processing nodes 800 or distributed across multiple processing nodes 800 and/or distributed across the processing node(s) 800 and the control system 702.
  • FIG 10 is a schematic block diagram of a wireless communication device 1000 according to some embodiments of the present disclosure.
  • the wireless communication device 1000 includes one or more processors 1002 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 1004, and one or more transceivers 1006 each including one or more transmitters 1008 and one or more receivers 1010 coupled to one or more antennas 1012.
  • the transceiver(s) 1006 includes radio-front end circuitry connected to the antenna(s) 1012 that is configured to condition signals communicated between the antenna(s) 1012 and the processor(s) 1002, as will be appreciated by on of ordinary skill in the art.
  • the processors 1002 are also referred to herein as processing circuitry.
  • the transceivers 1006 are also referred to herein as radio circuitry.
  • the functionality of the wireless communication device 1000 described above may be fully or partially implemented in software that is, e.g., stored in the memory 1004 and executed by the processor(s) 1002.
  • the wireless communication device 1000 may include additional components not illustrated in Figure 10 such as, e.g., one or more user interface components (e.g., an input/output interface including a display, buttons, a touch screen, a microphone, a speaker(s), and/or the like and/or any other components for allowing input of information into the wireless communication device 1000 and/or allowing output of information from the wireless communication device 1000), a power supply (e.g., a battery and associated power circuitry), etc.
  • a power supply e.g., a battery and associated power circuitry
  • a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of the wireless communication device 1000 according to any of the embodiments described herein is provided.
  • a carrier comprising the aforementioned computer program product is provided.
  • the carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).
  • FIG 11 is a schematic block diagram of the wireless communication device 1000 according to some other embodiments of the present disclosure.
  • the wireless communication device 1000 includes one or more modules 1100, each of which is implemented in software.
  • the module(s) 1100 provide the functionality of the wireless communication device 1000 described herein.
  • any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses.
  • Each virtual apparatus may comprise a number of these functional units.
  • These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processor (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as Read Only Memory (ROM), Random Access Memory (RAM), cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein.
  • the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.
  • Embodiment 1 A method performed by a network node implementing a target Integrated Access and Backhaul (IAB) donor node central unit (CU) of a telecommunications network, the method comprising:
  • IAB Integrated Access and Backhaul
  • CU central unit
  • triggering a move of a plurality of User Equipments (UEs) connected to an IAB node to switch to the target IAB donor node CU via a source IAB donor node CU; and
  • UEs User Equipments
  • Embodiment 2 A network node (700) implementing a target Integrated Access and Backhaul (IAB) donor node central unit (CU) of a telecommunications network, the network node comprising:
  • processing circuitry (702) associated with the network interface configured to cause the network node to: o trigger (512) a move of a plurality of User Equipments (UEs) connected to an IAB node to switch to the target IAB donor node CU via a source IAB donor node CU; and o trigger (514) a path switch procedure towards a core network of the telecommunications network for all UEs of the plurality of UEs connected to the IAB node.
  • UEs User Equipments
  • Embodiment 3 A network node (700) implementing a target Integrated Access and Backhaul (IAB) donor node central unit (CU) of a telecommunications network, the network node adapted to:
  • IAB Integrated Access and Backhaul
  • CU central unit
  • Embodiment 4 A method performed by a network node implementing a target Integrated Access and Backhaul (IAB) donor node central unit (CU) of a telecommunications network, the method comprising:
  • • triggering (624) a move of the plurality of UEs to switch to the target IAB donor node CU via the CN and the source IAB donor node CU; and • triggering (628) a message towards the CN, including a list of the plurality of UEs, to inform the CN of a successful move of the plurality of UEs.
  • Embodiment 5 The method of embodiment 4, wherein triggering (624) the move of the plurality of UEs to switch to the target IAB donor node CU via the CN and the source IAB donor node CU comprises sending (624a.1) a Next Generation Application Protocol (NGAP) message to the CN to request Radio Resource Control (RRC) reconfiguration of the plurality of UEs, the NGAP message comprising RRC reconfiguration information for each UE of the plurality of UEs.
  • NGAP Next Generation Application Protocol
  • RRC Radio Resource Control
  • Embodiment 6 The method of any one of embodiments 4-5, wherein triggering the move of the plurality of UEs to switch to the target IAB donor node CU via the CN and the source IAB donor node CU comprises sending (624b.l-624b.3) a message via the CN to the source IAB donor node CU to trigger the move of the plurality of UEs.
  • Embodiment 7 A network node (700) implementing a target Integrated Access and Backhaul (IAB) donor node central unit (CU) of a telecommunications network, the network node comprising:
  • processing circuitry (702) associated with the network interface configured to cause the network node to: o receive (604), from a source IAB donor node CU via a core network (CN) of the telecommunications network, a message comprising resource information for a plurality of UEs connected to the IAB node; o provide (604), to the CN, a message comprising a new RRC configuration for an IAB mobile termination (MT) and resource information allocated for each UE of the plurality of UEs; o trigger (624) a move of the plurality of UEs to switch to the target IAB donor node CU via the CN and the source IAB donor node CU; and o trigger (628) a message towards the CN, including a list of the plurality of UEs, to inform the CN of a successful move of the plurality of UEs.
  • CN core network
  • Embodiment 8 The network node of embodiment 7, wherein the processing circuitry is further configured to cause the network node to perform the method of any one of claims 5 and 6.
  • Embodiment 9 A network node (700) implementing a target Integrated Access and Backhaul (IAB) donor node central unit (CU) of a telecommunications network, the network node adapted to:
  • IAB Integrated Access and Backhaul
  • CU central unit
  • trigger (624) a move of the plurality of UEs to switch to the target IAB donor node CU via the CN and the source IAB donor node CU;
  • Embodiment 10 The network node of embodiment 9, wherein the network node is further adapted to perform the method of any one of claims 5 and 6.
  • Embodiment 11 A method performed by a network node of a core network (CN) of a telecommunications network, the method comprising:
  • Embodiment 12 The method of embodiment 11, further comprising:
  • NGAP Next Generation Application Protocol
  • RRC Radio Resource Configuration
  • Embodiment 13 The method of any one of embodiments 11-12, further comprising: • receiving (624b.1), from the target IAB donor node CU, a Next Generation Application Protocol (NGAP) message to request the source IAB donor node CU to trigger the mobility of the plurality of UEs connected to the IAB node; and
  • NGAP Next Generation Application Protocol
  • Embodiment 14 The method of any one of embodiments 11-13, further comprising sending (632) an NGAP U E-CONTEXT-RELEASE-COMMAND message to the source IAB donor node CU, the message including a list of the plurality of UEs.
  • Embodiment 15 A network node (700) of a core network (CN) of a telecommunications network, the network node comprising:
  • processing circuitry (702) associated with the network interface configured to cause the network node to: o receive (600), from a source Integrated Access and Backhaul (IAB) donor node central unit (CU) a message comprising a list of information for a plurality of User Equipments (UEs) connected to the IAB node; o prepare (602) for handover for an IAB mobile termination (MT) and all UEs of the plurality of UEs; and o send (604), to a target IAB donor node CU, a message comprising resource information for the plurality of UEs connected to the IAB node.
  • IAB Integrated Access and Backhaul
  • Embodiment 16 The network node of embodiment 15, wherein the processing circuitry is further configured to cause the network node to perform the method of any one of claims 12-14.
  • Embodiment 17 A network node (700) of a core network (CN) of a telecommunications network, the network node adapted to:
  • Embodiment 18 The network node of embodiment 16, wherein the network node is further adapted to perform the method of any one of claims 12-14.
  • Embodiment 19 A method performed by a network node implementing a source Integrated Access and Backhaul (IAB) donor node central unit (CU) of a telecommunications network, the method comprising:

Landscapes

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

Abstract

Des procédés et un appareil pour fournir un support de mobilité pour des nœuds de liaison terrestre et d'accès intégré (IAB) avec des équipements utilisateurs (UE) connectés sont divulgués ici. Dans un mode de réalisation donné à titre d'exemple, un procédé mis en œuvre par un nœud de réseau mettant en œuvre une unité centrale (CU) de nœud donneur IAB cible d'un réseau de télécommunications comprend le déclenchement d'un déplacement d'une pluralité d'UE connectés à un nœud IAB pour passer à la CU de nœud donneur IAB cible par l'intermédiaire d'une CU de nœud donneur IAB source. Le procédé comprend en outre le déclenchement d'une procédure de commutation de trajet vers un réseau central du réseau de télécommunications pour tous les UE de la pluralité d'UE connectés au nœud IAB.
PCT/IB2023/053099 2022-03-29 2023-03-28 Support de mobilité pour nœud de liaison terrestre et d'accès intégré (iab) avec équipements utilisateurs (ue) connectés WO2023187662A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202263324884P 2022-03-29 2022-03-29
US63/324,884 2022-03-29

Publications (1)

Publication Number Publication Date
WO2023187662A1 true WO2023187662A1 (fr) 2023-10-05

Family

ID=86142736

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2023/053099 WO2023187662A1 (fr) 2022-03-29 2023-03-28 Support de mobilité pour nœud de liaison terrestre et d'accès intégré (iab) avec équipements utilisateurs (ue) connectés

Country Status (1)

Country Link
WO (1) WO2023187662A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150049734A1 (en) * 2012-06-22 2015-02-19 Lg Electronics Inc. Method and apparatus for transmitting indication in wireless communication system
WO2019246446A1 (fr) * 2018-06-21 2019-12-26 Google Llc Maintien d'interfaces de communication et de signalisation par l'intermédiaire d'un transfert intercellulaire de station de base donneuse
US20210345206A1 (en) * 2020-04-30 2021-11-04 Qualcomm Incorporated Inter-donor cell management in wireless communication network
WO2021262077A1 (fr) * 2020-06-26 2021-12-30 Telefonaktiebolaget Lm Ericsson (Publ) Transfert intercellulaire de nœud iab dans une migration entre cu, f1 récursive et aspects de signalisation de rrc

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150049734A1 (en) * 2012-06-22 2015-02-19 Lg Electronics Inc. Method and apparatus for transmitting indication in wireless communication system
WO2019246446A1 (fr) * 2018-06-21 2019-12-26 Google Llc Maintien d'interfaces de communication et de signalisation par l'intermédiaire d'un transfert intercellulaire de station de base donneuse
US20210345206A1 (en) * 2020-04-30 2021-11-04 Qualcomm Incorporated Inter-donor cell management in wireless communication network
WO2021262077A1 (fr) * 2020-06-26 2021-12-30 Telefonaktiebolaget Lm Ericsson (Publ) Transfert intercellulaire de nœud iab dans une migration entre cu, f1 récursive et aspects de signalisation de rrc

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Solution for mobility", vol. SA WG2, no. e-meeting ;20220406 - 20220412, 29 March 2022 (2022-03-29), XP052133061, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_sa/WG2_Arch/TSGS2_150E_Electronic_2022-04/Docs/S2-2202216.zip S2-2202216_FS_VMR_Solution for mobility.docx> [retrieved on 20220329] *
HONG CHENG ET AL: "TR 23.700-05: Sol#12, update on F1-C support during full migration", vol. 3GPP SA 2, no. Online; 20220817 - 20220826, 10 August 2022 (2022-08-10), XP052185252, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_152E_Electronic_2022-08/Docs/S2-2206858.zip S2-2206858 pCR TR 23700-05-Sol 12 update on IAB Node Migration Procedure.docx> [retrieved on 20220810] *
TR 23.700-05

Similar Documents

Publication Publication Date Title
US11937337B2 (en) Methods and apparatuses for alternative data over non-access stratum, donas, data delivery in a roaming scenario
US20220256393A1 (en) TSN AND 5GS QoS MAPPING - A USER PLANE BASED METHOD
US20210274472A1 (en) Dynamic rsfp
JP2023504228A (ja) アプリケーションプログラミングインタフェース（ａｐｉ）フィルタに基づくａｐｉ能力変更の報告
WO2022097096A1 (fr) Notification d&#39;état de catastrophe dans des rmtp alternatifs
WO2022070042A1 (fr) Influence de la fonction d&#39;application dans la relocalisation d&#39;un contexte d&#39;application
US20240196316A1 (en) Systems and methods for inhomogeneous slice support
WO2020254968A1 (fr) Systèmes et procédés se rapportant à une suspension de connexion initiée par un réseau et à une libération initiale de rrc
US20240080787A1 (en) Redirection and retry of registration
US20230388909A1 (en) Ensuring network control of simultaneous access to network slices with application awareness
WO2022154718A1 (fr) Systèmes et procédés de récupération de contexte d&#39;ue et de transfert de données pour prendre en charge une transmission de petites données
WO2022029659A1 (fr) Activation autonome d&#39;une caractéristique au niveau d&#39;un dispositif de communication sans fil pour répondre au temps de survie d&#39;une application consommant un service de communication
WO2023187662A1 (fr) Support de mobilité pour nœud de liaison terrestre et d&#39;accès intégré (iab) avec équipements utilisateurs (ue) connectés
WO2021137180A1 (fr) Utilisation de dnai pour identifier une smf prenant en charge une connexion à un dn local
EP4133814B1 (fr) Lancement d&#39;une procédure d&#39;enregistrement demandée par un réseau
WO2023179231A1 (fr) Procédé et appareil de configuration d&#39;informations de cellule, support de stockage lisible et système de puce
US20230269573A1 (en) Systems and methods for ue context management in sidelink relay scenarios
US20240023182A1 (en) Handling the unknown rrc establishment cause value in nr
US20230337069A1 (en) QoS UPDATE HANDLING ALTERNATIVES DURING Xn HO
WO2022238911A1 (fr) Direction commandée d&#39;un équipement utilisateur à la suite d&#39;un découpage en tranches
WO2023214043A1 (fr) Approvisionnement de règles ursp en itinérance
WO2022233541A1 (fr) Nouvel attribut à la définition du type clientcredentialsassertion pour permettre la rétrocompatibilité avec les producteurs rel-16 nf
WO2022069364A1 (fr) Sélection d&#39;une smf
WO2023037341A1 (fr) Exposition de transmission redondante dans un système de communication cellulaire
CN117062179A (zh) 一种网络切片的通信方法、通信装置、接入网设备和终端设备

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

Country of ref document: EP

Kind code of ref document: A1

DPE1 Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101)