Methods and apparatus for supporting slicing optimization in wireless communication system

Abstract

The disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates and satisfying various service requirements. The disclosure provides a method performed by a source node in a wireless communication system. The method includes: transmitting, to a terminal, configuration information on a first triggering condition for reporting of information on a successful handover, the information on the successful handover including slice-related information of the successful handover, the slice-related information being associated with a service continuity for the terminal at a target node; receiving, from a terminal via the target node, the information on the successful handover; and performing self-optimization based on the slice-related information.

Description

METHODS AND APPARATUS FOR SUPPORTING SLICING OPTIMIZATION IN WIRELESS COMMUNICATION SYSTEM

[0001] The disclosure relates to operations of network node and a terminal in a wireless communication system, and more particularly, relates to methods and apparatus for supporting slicing optimization in wireless communication system.

[0002] 5thgeneration (5G) mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6 gigahertz (GHz) frequency band such as 3.5GHz, but also in the ultra-high frequency band referred to as millimeter wave (mmWave) bands such as 28GHz and 39GHz (above 6GHz) bands. In 6thgeneration (6G) mobile communication technology, referred to as beyond 5G, it is expected that it will be paramount to secure new frequency resources such as the sub-6GHz band, ultra-high frequency bands, and upper mid band (7-24GHz) to handle the rapidly increased data traffic due to the spread of artificial intelligence (AI) technology and the increase in streaming services, to improve user perceived performance, and to efficiently utilize all available frequency resources as needed. To this end, reallocation, reuse, or sharing of existing frequency bands from 2ndgeneration (2G) to 5G for 6G can be considered.

[0003] Since the introduction of 5G, the communications market has been increasingly interested in improving system operation efficiency, sustainability, and user experience. Accordingly, in addition to improving traditional communications performance such as data transmission speed and delay time, the introduction of new innovative technologies such as AI, reducing operating costs, improving energy efficiency, expanding service coverage, and introducing new services are becoming increasingly important.

[0004] Since the early stages of 5G mobile communication technology, a goal has been to support services and satisfy performance requirements for enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC), including beamforming and massive multiple-input multiple-output (MIMO) to mitigate path loss of radio waves in ultra-high frequency bands and increase the range of radio transmission, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of band-width part (BWP), new channel coding methods such as low density parity check (LDPC) codes for large-capacity data transmission and polar codes for reliable transmission of control information, layer 2 (L2) pre-processing, and networks that provide dedicated networks specialized for specific services. Standardization of slicing (network slicing) etc. has been progressing.

[0005] Furthermore, discussions have been held on improving and enhancing the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, including vehicle-to-everything (V2X) to help autonomous vehicles make decisions based on their own location and status information transmitted by the vehicle and to increase user convenience, new radio unlicensed (NR-U) for system operation that meets various regulatory requirements in unlicensed bands, NR terminal low power consumption technology (i.e., UE power saving), non-terrestrial network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, positioning, NR support up to 71GHz, support of reduced capability NR devices for lower cost and complexity compared to general terminals, user equipment (UE) power saving enhancement for improved power management in preparation for the use of various terminal types, and sidelink. Standardization of the physical layer has been performed for technologies such as sidelink enhancement, duplex enhancements which study a new form of duplexing called subband non-overlapping full duplex (SBFD), network energy saving which secures the idle period in which the base station operates in maximum power saving mode to the maximum extent and reduces power consumption, and network controlled repeaters which have improved performance compared to existing repeaters by having the function of receiving and processing side control information from the network.

[0006] In addition, standardization of the wireless interface architecture / protocol layer for technologies such as the industrial Internet of things (IIoT) for supporting new services through linkage and convergence with other industries, integrated access and backhaul (IAB) that provides nodes for expanding network service areas by integrating wireless backhaul links and access links, mobility enhancement technology including conditional handover (CHO) and dual active protocol stack (DAPS) handover, 2-step random access channel (RACH) for NR that simplifies random access procedures, multicast and broadcast, standardization of support for multi universal subscriber identity module (USIM) devices that provide services to users using information of two or more subscriber identity modules (SIMs), sidelink relay that provides relay-related functions to support connections between terminals in long distances and between terminals and networks, small data transfer (SDT) which transmits small data or signaling in an inactive state without transitioning to a connected state, mobility enhancements including layer 1 (L1) / L2 triggered mobility (LTM) / subsequent conditional PSCell addition / change (SCPAC) / and conditional handover (CHO) with candidate SCGs, extended reality (XR) enhancement to support XR services in NR systems, etc. has also been performed, and standardization of system architecture / services such as 5G baseline architecture (e.g., service-based architecture, service-based interface) for grafting network functions virtualization (NFV) and software-defined networking (SDN) technologies, mobile edge computing (MEC) that provides services based on the location of the terminal, non-public networks (NPN) that can be used only by some permitted terminals for non-public purposes, disaster roaming that supports the use of communication services through other carriers' networks in the event of a communication disaster, proximity-based service via 5GS, and unmanned Standardization has also been made in the system architecture / service areas, including support of an unmanned aircraft system (UAS) to support remote identification, tracking, and authorization of uncrewed aerial vehicles (UAVs), structural enhancements to support XR and interactive media services, 5GS to support AI / machine learning (ML) services, and advanced mobile edge computing to provide edge computing services in roaming networks, etc. has also been performed.

[0007] Currently, standardization is in progress for technologies such as beam prediction using AI / ML technology, channel state information (CSI) prediction to improve positioning accuracy, ultra-low-power terminal technology using low-power wake-up receivers, technology for transmitting long term evolution (LTE) broadcasts to 5G networks, MIMO transmission technology using multiple base stations, and ultra-low-power terminals (ambient IoT) that transmit data by obtaining power from an external source without a battery. At the radio interface architecture / protocol layer, standardization is in progress for technologies such as LTM scenario support and conditional LTM support between central units (CUs), simultaneous support for the same XR service between multiple devices, NTN coverage enhancement and evolution, AI / ML-based mobility support, and terminal-to-terminal connection relay across multiple hops between terminals and networks.

[0008] In addition, standardization of system architecture / service fields for satellite communication optimization methods, 5G system energy usage management and efficiency, SBI-based user plane evolution, ambient IoT technology, data service provision methods in IMS (IP multimedia subsystem), and avatar communication service persists. When such 5G mobile communication systems are commercialized, a vast increase in devices connected to the communication network will be realized, and accordingly, it is expected that the functions and performance of 5G mobile communication systems will be strengthened and integrated operation of connected devices will be required. To this end, new research will be additionally conducted on XR to efficiently support augmented reality (AR), virtual reality (VR), and mixed reality (MR), 5G performance improvement and complexity reduction using AI / ML, AI service support, metaverse service support, and drone communication.

[0009] The development of these 5G mobile communication systems is expected to serve as the basis for enhancing 5G performance and ultimately evolving into 6G. In the 6G era, eMBB, URLLC, and mMTC services, are expected to evolve into immersive communication (IC), hyper-reliable and low-latency communication (HRLLC), and massive communication (MC) services, respectively. In addition, new services such as AI and communication, integrated sensing and communication, and ubiquitous connectivity are expected to be additionally supported. For these 6G services, improved performance requirements compared to 5G are also essential, and standardization to define these is also in progress.

[0010] In this manner, to satisfy the expanded services and improved performance requirements of 6G, it is expected that it will be essential to optimize and improve system operation, such as introducing AI technology, improving energy efficiency, expanding coverage, and applying next-generation security technology, as well as developing sustainable communication technology, in addition to simply improving existing communication performance.

[0011] To this end, the latest AI technology is applied to all areas from the communication system design stage to development, management, and operation to improve communication performance and realize AI internalization technology that realizes network automation and efficiency, technology that improves user-perceived performance and network operation efficiency by improving power consumption of networks and terminals, technology that reduces power consumption in core base station components such as radio frequency (RF) and modems and in the channel coding and signal modulation and transmission / reception processes, multi-antenna transmission technology (e.g., extreme MIMO (X-MIMO)) that utilizes large antennas to overcome propagation path loss due to high frequency compared to the 3.5 GHz band of 5G communication and provide equivalent coverage, transmission / reception technology based on multiple base stations (e.g., distributed MIMO (D-MIMO)) to improve quality in cell edge areas, full-duplex communication (e.g., SBFD) technology to improve frequency efficiency and system network, next-generation encryption technology (e.g., post quantum cryptography (PQC)) and zero trust architecture (ZTA) technology to strengthen 6G communication security, and initial access delay and mobility. Research will be focused on technologies to minimize delay, design a hardware-friendly protocol structure for ultra-high-speed data processing, and expand the application of integrity protection technologies.

[0012] In addition, research will be conducted on the structure of mobile communication systems (prevention of redundant functions, simplification of functions, etc.), introduction of new planes for providing service providers, user privacy protection measures, realistic services, enhancement of network resiliency, network sharing technologies, improved security technologies (false base stations, lower layer protection, etc.), and intent-based network operation and management.

[0013] In wireless communication system, the terminal may perform mobility procedures - such as handover or layer 1 / layer 2 triggered mobility (LTM) - from a current network node to other network nodes. When a current network node(or source node) commands or configures a target node, the current network node needs to consider not only the radio signal strength measured at that cell but also whether the cell can maintain service continuity for the terminal's offered by network slice. To support mobility operation considering the service continuity, network nodes therefore need to exchange slice-related mobility information with one another and perform automated self-optimization based on those exchanged information.

[0014]

[0015] The disclosure relates to methods and apparatus for supporting slicing optimization in wireless communication system.

[0016] Accordingly, an aspect of the disclosure is to provide methods and apparatus for supporting self-optimization of the network node associated with a mobility operation of the terminal.

[0017] In addition, an aspect of the disclosure is to provide methods and an apparatus for configuring slice-related information of the mobility operation used for the self-optimization.

[0018] Furthermore, an aspect of the disclosure is to provide methods and an apparatus for exchanging the slice-related information between the network node and other nodes.

[0019] Additional aspects will be set forth in part in the description which follows and, in part, will be apparent from the description, or may be learned by practice of the presented embodiments.

[0020] Aspects of the disclosure are to address at least the above-mentioned problems and / or disadvantages and to provide at least the advantages described below.

[0021]

[0022] In accordance with an embodiment of the disclosure, a method performed by a source node in a wireless communication system is provided. The method includes transmitting, to a terminal, configuration information on a first triggering condition for reporting of information on a successful handover, the information on the successful handover including slice-related information of the successful handover, and the slice-related information being associated with a service continuity for the terminal at a target node; receiving, from a terminal via the target node, the information on the successful handover; and performing self-optimization based on the slice-related information.

[0023] In accordance with an embodiment of the disclosure, a method performed by a terminal in a wireless communication system is provided. The method includes receiving, from a source node, configuration information on a triggering condition for reporting of information on a successful handover, the information on the successful handover including slice-related information of the successful handover, and the slice-related information being associated with a service continuity for the terminal at a target node; performing the successful handover from the source node to the target node; and transmitting, to the target node, the information on the successful handover, wherein the slice-related information is transmitted from the target node to the source node, and wherein the slice-related information is used for self-optimization of the source node.

[0024] In accordance with an embodiment of the disclosure, a source node in a wireless communication system is provided. The source node includes a transceiver; a processor communicatively coupled to the transceiver; and memory, communicatively coupled to the processor, storing instructions executable by the processor to cause the source node to transmit, to a terminal, configuration information on a first triggering condition for reporting of information on a successful handover, the information on the successful handover including slice-related information of the successful handover, and the slice-related information being associated with a service continuity for the terminal at a target node, receive, from a terminal via the target node, the information on the successful handover, and perform self-optimization based on the slice-related information.

[0025] In accordance with an embodiment of the disclosure, a terminal in a wireless communication system is provided. The terminal includes a transceiver; a processor communicatively coupled to the transceiver; and memory, communicatively coupled to the processor, storing instructions executable by the processor to cause the terminal to receive, from a source node, configuration information on a triggering condition for reporting of information on a successful handover, the information on the successful handover including slice-related information of the successful handover, and the slice-related information being associated with a service continuity for the terminal at a target node, perform the successful handover from the source node to the target node, and transmit, to the target node, the information on the successful handover, wherein the slice-related information is transmitted from the target node to the source node, and wherein the slice-related information is used for self-optimization of the source node.

[0026]

[0027] Embodiments of the disclosure provide a method performed by a first node in a wireless communication system, including: transmitting a third message to a user equipment (UE), wherein the third message includes first information for configuring reporting of slice-related successful handover information; receiving a sixth message from a second node, wherein the sixth message includes the slice-related successful handover information; and performing self-optimization based on the sixth message, wherein the first information includes information related to at least one of: slice replacement occurs, a service requirement of the UE cannot be met, a service of the UE is interrupted, a threshold of an interruption time of a user plane related to the UE, a threshold of a time interval between a next handover and a current handover of the UE, a threshold of a camping time of the UE.

[0028] Embodiments of the disclosure provide a method performed by a user equipment (UE) in a wireless communication system, including: receiving a third message from a first node, wherein the third message includes first information for configuring reporting of slice-related successful handover information; and transmitting an eighth message to a second node, wherein the eighth message includes the slice-related successful handover information, wherein the eighth message is used for the first node and / or the second node to perform self-optimization, and wherein the first information includes information related to at least one of: slice replacement occurs, a service requirement of the UE cannot be met, a service of the UE is interrupted, a threshold of an interruption time of a user plane related to the UE, a threshold of a time interval between a next handover and a current handover of the UE, a threshold of a camping time of the UE.

[0029] Embodiments of the disclosure provide a node device in a wireless communication system, including: a transceiver configured to transmit and receive signals; and a processor coupled to the transceiver and configured to perform methods performed by any node in a wireless communication system according to embodiments of the disclosure.

[0030] Embodiments of the disclosure provide a user equipment (UE) in a wireless communication system, including: a transceiver configured to transmit and receive signals; and a processor coupled to the transceiver and configured to perform methods performed by a user equipment (UE) in a wireless communication system according to embodiments of the disclosure.

[0031] Embodiments of the disclosure provide a computer-readable medium having stored thereon computer-readable instructions which, when executed by a processor, perform methods performed by any node and / or a user equipment (UE) in a wireless communication system according to embodiments of the disclosure.

[0032] The methods performed by a node and / or user equipment (UE) in the wireless communication system provided by the disclosure can effectively support the node and / or user equipment to perform network self-optimization and perform slice-related handover by exchanging information associated with slice-related handover between the node and / or user equipment.

[0033]

[0034] According to an embodiment of the disclosure, the network node may perform self-optimization by obtaining information on a cause of radio link failure (RLF) or service interruption which occurs after handover.

[0035] Furthermore, according to an embodiment of the disclosure, the network node may ensure service continuity of network slices for the terminal.

[0036] In addition, according to an embodiment of the disclosure, by receiving mobility configurations from network node with self-optimization, the terminal may perform handover with an uninterrupted experience in service

[0037] The effects obtainable in the disclosure are not limited to the above-mentioned effects, and other effects not mentioned herein will be clearly understood from the following description by those skilled in the art to which the disclosure belongs.

[0038]

[0039] The above and other aspects, features and advantages of certain embodiments of the disclosure will be more apparent from the following description taken in conjunction with the accompanying drawings, in which:

[0040] Figure 1 illustrates an exemplary system architecture SAE;

[0041] Figure 2 illustrates an exemplary system architecture according to an embodiment of the disclosure;

[0042] Figure 3a illustrates a schematic diagram of a method for supporting slice optimization associated with an RLF according to an embodiment of the disclosure;

[0043] Figure 3b illustrates a schematic diagram of a method for supporting slice optimization associated with an RLF according to an embodiment of the disclosure;

[0044] Figure 3c illustrates a schematic diagram of a method for supporting slice optimization associated with an RLF according to an embodiment of the disclosure;

[0045] Figure 3d illustrates a schematic diagram of a method for supporting slice optimization associated with an RLF according to an embodiment of the disclosure;

[0046] Figure 3e illustrates a schematic diagram of a method for supporting slice optimization associated with an RLF according to an embodiment of the disclosure;

[0047] Figure 3f illustrates a schematic diagram of a method for supporting slice optimization associated with an RLF according to an embodiment of the disclosure;

[0048] Figure 3g illustrates a schematic diagram of a method for supporting slice optimization associated with an RLF according to an embodiment of the disclosure;

[0049] Figure 4a illustrates a schematic diagram of a method for exchanging configuration information associated with a slice-related handover between nodes according to an embodiment of the disclosure;

[0050] Figure 4b illustrates a schematic diagram of a method for exchanging configuration information associated with a slice-related handover between nodes according to an embodiment of the disclosure;

[0051] Figure 4c illustrates a schematic diagram of a method for exchanging configuration information associated with a slice-related handover between nodes according to an embodiment of the disclosure;

[0052] Figure 5 illustrates a schematic diagram of a method for exchanging configuration for slice-related successful handover information according to embodiments of the disclosure;

[0053] Figure 6a illustrates a schematic diagram of a method for exchanging slice-related successful handover information according to embodiments of the disclosure;

[0054] Figure 6b illustrates a schematic diagram of a method for exchanging slice-related successful handover information according to embodiments of the disclosure;

[0055] Figure 6c illustrates a schematic diagram of a method for exchanging slice-related successful handover information according to embodiments of the disclosure;

[0056] Figure 6d illustrates a schematic diagram of a method for exchanging slice-related successful handover information according to embodiments of the disclosure;

[0057] Figure 7a illustrates a schematic diagram of a method for exchanging information related to user history information according to embodiments of the disclosure;

[0058] Figure 7b illustrates a schematic diagram of a method for exchanging information related to user history information according to embodiments of the disclosure;

[0059] Figure 7c illustrates a schematic diagram of a method for exchanging information related to user history information according to embodiments of the disclosure;

[0060] Figure 7d illustrates a schematic diagram of a method for exchanging information related to user history information according to embodiments of the disclosure;

[0061] Figure 7e illustrates a schematic diagram of a method for exchanging information related to user history information according to embodiments of the disclosure;

[0062] Figure 7f illustrates a schematic diagram of a method for exchanging information related to user history information according to embodiments of the disclosure;

[0063] Figure 8 illustrates a flowchart of a method performed by a first node in a wireless communication system according to embodiments of the disclosure;

[0064] Figure 9 illustrates a flowchart of a method performed by a UE in a wireless communication system according to embodiments of the disclosure;

[0065] Figure 10 illustrates a schematic diagram of a node according to embodiments of the disclosure; and

[0066] Figure 11 illustrates a schematic diagram of a user equipment (UE) according to embodiments of the disclosure.

[0067]

[0068] The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of various embodiments of the disclosure as defined by the claims and their equivalents. It includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the various embodiments described herein can be made without departing from the scope and spirit of the disclosure. In addition, descriptions of well-known functions and constructions may be omitted for clarity and conciseness.

[0069] The terms and words used in the following description and claims are not limited to the bibliographical meanings, but, are merely used by the inventor to enable a clear and consistent understanding of the disclosure. Accordingly, it should be apparent to those skilled in the art that the following description of various embodiments of the disclosure is provided for illustration purpose only and not for the purpose of limiting the disclosure as defined by the appended claims and their equivalents.

[0070] It is to be understood that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "a component surface" includes reference to one or more of such surfaces.

[0071] The term "include" or "may include" refers to the existence of a corresponding disclosed function, operation or component which can be used in various embodiments of the disclosure and does not limit one or more additional functions, operations, or components. The terms such as "include" and / or "have" may be construed to denote a certain characteristic, number, step, operation, constituent element, component or a combination thereof, but may not be construed to exclude the existence of or a possibility of addition of one or more other characteristics, numbers, steps, operations, constituent elements, components or combinations thereof.

[0072] The term "or" used in various embodiments of the disclosure includes any or all of combinations of listed words. For example, the expression "A or B" may include A, may include B, or may include both A and B.

[0073] Unless defined differently, all terms used herein, which include technical terminologies or scientific terminologies, have the same meaning as that understood by a person skilled in the art to which the disclosure belongs. Such terms as those defined in a generally used dictionary are to be interpreted to have the meanings equal to the contextual meanings in the relevant field of art, and are not to be interpreted to have ideal or excessively formal meanings unless clearly defined in the disclosure.

[0074] Figures discussed below and various embodiments for describing the principles of the disclosure in this patent document are only for illustration and should not be interpreted as limiting the scope of the disclosure in any way. Those skilled in the art will understand that the principles of the disclosure can be implemented in any suitably arranged system or device.

[0075]

[0076] Figure 1 illustrates an exemplary system architecture 100 of system architecture evolution (SAE). User equipment (UE) 101 is a terminal device for receiving data. An evolved universal terrestrial radio access network (E-UTRAN) 102 is a radio access network, which includes a macro base station (eNodeB / NodeB) that provides UE with interfaces to access the radio network. A mobility management entity (MME) 103 is responsible for managing mobility context, session context and security information of the UE. A serving gateway (SGW) 104 mainly provides functions of user plane, and the MME 103 and the SGW 104 may be in the same physical entity. A packet data network gateway (PGW) 105 is responsible for functions of charging, lawful interception, etc., and may be in the same physical entity as the SGW 104. A policy and charging rules function entity (PCRF) 106 provides quality of service (QoS) policies and charging criteria. A general packet radio service support node (SGSN) 108 is a network node device that provides routing for data transmission in a universal mobile telecommunications system (UMTS). A home subscriber server (HSS)109 is a home subsystem of the UE, and is responsible for protecting user information including a current location of the user equipment, an address of a serving node, user security information, and packet data context of the user equipment, etc.

[0077]

[0078] Figure 2 illustrates an exemplary system architecture 200 according to various embodiments of the disclosure. Other embodiments of the system architecture 200 can be used without departing from the scope of the disclosure.

[0079] User equipment (UE) 201 is a terminal device for receiving data. A next generation radio access network (NG-RAN) 202 is a radio access network, which includes a base station (a gNB or an eNB connected to 5G core network 5GC, and the eNB connected to the 5GC is also called ng-gNB) that provides UE with interfaces to access the radio network. An access control and mobility management function entity (AMF) 203 is responsible for managing mobility context and security information of the UE. A user plane function entity (UPF) 204 mainly provides functions of user plane. A session management function entity SMF 205 is responsible for session management. A data network (DN) 206 includes, for example, services of operators, access of Internet and service of third parties.

[0080] Nodes mentioned in the disclosure may include: gNB, gNB central unit (gNB-CU), gNB distributed unit (gNB-DU), gNB central unit control plane (gNB-CU-CP), gNB central unit user plane (gNB CU-UP), en-gNB, eNB, ng-eNB, UE, access and mobility management function (AMF), session management function (SMF), mobility management entity (MME) and other network entities or network logic units, and cells and / or slices managed by them, etc.

[0081] The signal strength and / or signal quality mentioned in the disclosure may be a received signal strength indicator (RSSI), a reference signal receiving power, RSRP), a reference signal receiving quality (RSRQ), and a signal to interference plus noise ratio (SINR), etc.

[0082] The measurement result and / or measurement report described in the disclosure may be a signal strength and / or a signal quality.

[0083] In the disclosure, a failure type and / or problem type may also be a report type.

[0084] In the disclosure, self-optimization network (SON) related reports may include one or more of the following: a connection establishment failure (CEF) report, or a random access report, or a successful handover report (SHR), or a radio link failure (RLF) report, or a measurement report, or other wireless connection related reports.

[0085] In the disclosure, the radio link failure includes two cases: radio link failure and handover failure.

[0086] In the disclosure, user equipment (UE) may be used interchangeably with user, terminal, etc.

[0087] In the disclosure, in a handover scenario, the last serving node may be a source node of the handover (handover source node) or a target node of the handover (handover target node). For example, in case that the UE is not successfully handed over to the handover target node, the last serving node may be the handover source node; and in case that the UE is handed over to the handover target node but a radio link failure occurs and the UE reselects an accessing node, the last serving node may be the handover target node.

[0088] In the disclosure, a target cell and / or node may also referred to as a (candidate) target cell and / or node.

[0089] In the disclosure, handover may be used interchangeably with mobility, Cell Switch, etc.

[0090] A node may collect radio link failure reports and / or Successful Handover reports from the UE for self-optimization of handover, etc.

[0091] In slice-related handover, the handover procedure needs to be optimized.

[0092]

[0093] Example 1

[0094] One aspect of the disclosure proposes a method for supporting slice optimization, which may include: a first node transmits a first message including slice-related radio link failure information to a second node, so that the second node can obtain slice-related radio link failure information. For example, the slice-related radio link failure information may be used for the second node to analyze the reason of a slice-related radio link failure and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration, or it may be used for the second node to analyze whether the problem originates from itself or other nodes when analyzing the reason of a radio link failure and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration, or it may be forwarded by the second node to other nodes for the other nodes to analyze a failure reason and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration. If the first node is a UE, when a handover failure and / or radio link failure occurs, the fist node records and / or generates and / or reports the first message. This solution can reduce handover failures and / or radio link failures, and / or improve the robustness of handover.

[0095] In some implementations, the first message may be or may be included in one or more of: a User Information Response (UEInformationResponse), Secondary Cell Group Failure Information (SCGFailureInformation), Master Cell Group Failure Information (MCGFailureInformation) of RRC; a FAILURE INDICATION message, a HANDOVER REPORT message, an ACCESS AND MOBILITY INDICATION message, a S-NODE MODIFICATION REQUEST message, a SgNB MODIFICATION REQUEST message, a SCG FAILURE INFORMATION REPORT message, an RRC TRANSFER message of Xn; an ACCESS AND MOBILITY INDICATION message of F1; an UPLINK RAN CONFIGURATION TRANSFER message, a DOWNLINK RAN CONFIGURATION TRANSFER message of NG; or an other and / or newly defined RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message. This information may be included in a report, where the report may be a Connection Establishment Failure (CEF) report, or a Random Access report, or a Successful Handover report, or a Radio Link Failure (RLF) report, or a measurement report, or other wireless connection related reports.

[0096] In some implementations, the first message and / or slice-related radio link failure information may include one or more of the following fields or related information:

[0097] · UE identification (ID): which indicates the user corresponding to the slice-related radio link failure information.

[0098] · Identification and / or identification list of slices supported by and / or available for a reconnect cell.

[0099] · Identification and / or identification list of slices supported by and / or available for a source cell.

[0100] · Identification and / or identification list of slices supported by and / or available for a target cell.

[0101] · Identification and / or identification list of slices accessed on a reconnect cell.

[0102] · Identification and / or identification list of slices accessed on a source cell.

[0103] · Identification and / or identification list of slices accessed on a target cell.

[0104] · Identification and / or identification list of slices corresponding to Protocol Data Unit (PDU) sessions (PDU session resources) established on the reconnect cell and / or accepted by the reconnect cell.

[0105] · Information and / or information list of PDU sessions (PDU session resources) established on the reconnect cell and / or accepted by the reconnect cell, including one or more of the following: PDU session (PDU session resource) identification, slice identification, QoS flow identification, number of PDU sessions (PDU session resources) established and / or accepted.

[0106] · Identification and / or identification list of slices corresponding to PDU sessions (PDU session resources) that cannot be established on the reconnect cell and / or are rejected by the reconnect cell.

[0107] · Information and / or information list of PDU sessions (PDU session resources) that cannot be established on the reconnect cell and / or are rejected by the reconnect cell, including one or more of the following: PDU session (PDU session resource) identification, slice identification, QoS flow identification, number of PDU sessions (PDU session resources) that cannot be established and / or rejected.

[0108] · Identification and / or identification list of slices corresponding to PDU sessions (PDU session resources) established on the source cell and / or accepted by the source cell.

[0109] · Information and / or information list of PDU sessions (PDU session resources) established on the source cell and / or accepted by the source cell, including one or more of the following: PDU session (PDU session resource) identification, slice identification, QoS flow identification, number of PDU sessions (PDU session resources) established and / or accepted.

[0110] · Identification and / or identification list of slices corresponding to PDU sessions (PDU session resources) established on the target cell and / or serving cell and / or accepted by the target cell and / or serving cell.

[0111] · Information and / or information list of PDU sessions (PDU session resources) established on the target cell and / or serving cell and / or accepted by the target cell and / or serving cell, including one or more of the following: PDU session (PDU session resource) identification, slice identification, QoS flow identification, number of PDU sessions (PDU session resources) established and / or accepted.

[0112] · Identification and / or identification list of slices corresponding to PDU sessions (PDU session resources) that cannot be established on the target cell and / or serving cell and / or are rejected by the target cell and / or serving cell.

[0113] · Information and / or information list of PDU sessions (PDU session resources) that cannot be established on the target cell and / or serving cell and / or are rejected by the target cell and / or serving cell, including one or more of the following: PDU session (PDU session resource) identification, slice identification, QoS flow identification, number of PDU sessions (PDU session resources) that cannot be established and / or rejected.

[0114] · Identification and / or identification list of slices corresponding to PDU sessions (PDU session resources) accepted by a target cell in a handover (preparation) procedure.

[0115] · Information and / or information list of PDU sessions (PDU session resources) accepted by a target cell in a handover (preparation) procedure, including one or more of the following: PDU session (PDU session resource) identification, slice identification, QoS flow identification, number of PDU sessions (PDU session resources) accepted.

[0116] · Identification and / or identification list of slices corresponding to PDU sessions (PDU session resources) rejected by a target cell in a handover (preparation) procedure.

[0117] · Information and / or information list of PDU sessions (PDU session resources) rejected by a target cell in a handover (preparation) procedure, including one or more of the following: PDU session (PDU session resource) identification, slice identification, QoS flow identification, number of PDU sessions (PDU session resources) rejected.

[0118] · Whether a service requirement can be met on a reconnect cell.

[0119] · Identification and / or identification list of slices corresponding to PDU sessions (PDU session resources) that meet a service requirement on a reconnect cell: in some implementations, for example, if there are one or more PDU sessions (PDU session resources) and / or slices that meet a service requirement on the reconnect cell, this information is included in the first message. Alternatively, for example, if there are one or more PDU sessions (PDU session resources) and / or slices that do not meet a service requirement on the reconnect cell, this information is included in the first message. This information is used to indicate slices corresponding to PDU sessions (PDU session resources) that meet a requirement.

[0120] · Information and / or information list of PDU sessions (PDU session resources) that meet a service requirement on a reconnect cell, including one or more of the following: PDU session (PDU session resource) identification, slice identification, QoS flow identification, number of PDU sessions (PDU session resources) that meet a service requirement. In some implementations, for example, if there are one or more PDU sessions (PDU session resources) and / or slices that meet a service requirement on the reconnect cell, this information is included in the first message. Alternatively, for example, if there are one or more PDU sessions (PDU session resources) and / or slices that do not meet a service requirement on the reconnect cell, this information is included in the first message. This information is used to indicate slices corresponding to PDU sessions (PDU session resources) that meet a requirement.

[0121] · Identification and / or identification list of slices corresponding to PDU sessions (PDU session resources) that do not meet a service requirement on a reconnect cell. In some implementations, for example, if there are one or more PDU sessions (PDU session resources) and / or slices that do not meet a service requirement on the reconnect cell, this information is included in the first message. This information is used to indicate slices corresponding to PDU sessions (PDU session resources) that do not meet a requirement.

[0122] · Information and / or information list of PDU sessions (PDU session resources) that do not meet a service requirement on a reconnect cell, including one or more of the following: PDU session (PDU session resource) identification, slice identification, QoS flow identification, number of PDU sessions (PDU session resources) that do not meet a service requirement. In some implementations, for example, if there are one or more PDU sessions (PDU session resources) and / or slices that do not meet a service requirement on the reconnect cell, this information is included in the first message. This information is used to indicate slices corresponding to PDU sessions (PDU session resources) that do not meet a requirement.

[0123] · Information related to whether slice replacement / remapping has occurred: it may indicate whether slice replacement has occurred.

[0124] · Identification and / or identification list of original slices related to slice replacement that occurred: for example, the original slice may be a slice before the slice replacement. For example, the original slice may be a slice which is replaced in the slice replacement. If slice replacement occurs, this information is included in the first message.

[0125] · Identification and / or identification list of replacing slices related to slice replacement that occurred: for example, it may be identification and / or identification list of alternative slices. For example, it may also be identification and / or identification list of slices after the slice replacement. For example, it may be identification and / or identification list of slices that replace the original slices after the slice replacement. If slice replacement occurs, this information is included in the first message.

[0126] · Information related to whether service interruption occurs: for example, it may indicate whether service interruption occurs. It may also include information related to service interruption. For example, when service interruption occurs, this information is included in the first message. The information related to service interruption may include one or more of the following: a service type corresponding to the service interruption, (identification and / or identification list of) PDU sessions corresponding to the service interruption, (identification and / or identification list of) slices corresponding to the PDU sessions corresponding to the service interruption, service requirements corresponding to the service interruption, etc.

[0127] · Information related to whether a UE supports slice replacement: used to indicate whether the UE supports slice replacement.

[0128] · Identification and / or identification list of slices corresponding to PDU sessions (PDU session resources) accepted by a (candidate) target cell in a handover preparation procedure.

[0129] · Information and / or information list of PDU sessions (PDU session resources) accepted by a (candidate) target cell in a handover preparation procedure, including one or more of the following: (candidate) target cell identification, PDU session (PDU session resource) identification, slice identification, QoS flow identification, number of PDU sessions (PDU session resources) accepted, whether all PDU sessions (PDU session resources) are accepted, whether some of the PDU sessions (PDU session resources) are rejected, whether all the PDU sessions (PDU session resources) are rejected.

[0130] · Identification and / or identification list of slices corresponding to PDU sessions (PDU session resources) rejected by a (candidate) target cell in a handover preparation procedure.

[0131] · Information and / or information list of PDU sessions (PDU session resources) rejected by a (candidate) target cell in a handover preparation procedure, including one or more of the following: (candidate) target cell identification, PDU session (PDU session resource) identification, slice identification, QoS flow identification, number of PDU sessions (PDU session resources) rejected, whether all PDU sessions (PDU session resources) are accepted, whether some of the PDU sessions (PDU session resources) are rejected, whether all the PDU sessions (PDU session resources) are rejected.

[0132] In some implementations, for example, since when selecting a target cell, measurement results and / or slices supported by a target cell need to be considered, a case where a cell with the best measurement result is not selected due to the consideration of the slices supported by the target cell may occur. The node can use the above information to perform mobility optimization, such as adjusting a strategy for selecting a target cell (e.g., adjusting a measurement result threshold for selecting a target cell, adjusting the considered supporting slices for selecting a target cell, etc.). For example, consider a case where a reconnect cell (e.g., cell 1) does not support one or more slices (e.g., slice A) accessed by the UE, but slice replacement is performed for the unsupported slice on the reconnect cell. After the UE accesses a new slice (i.e., a replacing slice, for example, slice B), the service may continue. Through the first message or one or more of the above information, the node may know that cell 1 can support service continuity for a UE accessing slice A (e.g., through slice replacement). In subsequent mobility strategies, if the node encounters a similar UE (e.g., a UE that needs to access the same slice (e.g., slice A)), and if the UE's measurement report for cell 1 is good (e.g., higher than a measurement result threshold for selecting a target cell), the node may select cell 1 as a target cell, because cell 1 can perform slice replacement to ensure the UE's service continuity. This optimization can avoid not selecting cell 1 because cell 1 does not support slice A, but selecting other cells that support slice A but have poor measurement results, resulting in radio link failure.

[0133]

[0134] Example 2

[0135] One aspect of the disclosure proposes a method for supporting slice optimization, which may include: a third node transmits a second message including configuration information associated with a slice-related handover to a fourth node. After receiving the message, the fourth node may perform analysis and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration and / or make handover decisions based on the received slice-related radio link failure information and / or configuration information associated with a slice-related handover, and / or transmit the configuration information associated with a slice-related handover to other nodes, for the other nodes to perform analysis and / or make related self-optimization decisions and / or perform self-optimization and / or make handover decisions based on the configuration information associated with a slice-related handover and / or other information (e.g., (slice-related) radio link failure information).

[0136] In some implementations, the second message may be included in one or more of: a SN STATUS TRANSFER message, a HANDOVER REPORT message, a UE CONTEXT SETUP REQUEST message, a UE CONTEXT SETUP RESPONSE message, a UE CONTEXT MODIFICATION REQUEST message, a UE CONTEXT MODIFICATION RESPONSE message, a UE CONTEXT MODIFICATION REQUIRED message, a UE CONTEXT MODIFICATION CONFIRM message of Xn; or an other and / or newly defined RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message.

[0137] In some implementations, the second message and / or the configuration information associated with a slice-related handover may include one or more of the following fields or related information:

[0138] · UE identification: which indicates the user corresponding to the configuration information associated with a slice-related handover, and / or the user corresponding to the slice-related radio link failure information.

[0139] · Identification and / or identification list of (candidate) target cells in a handover preparation procedure.

[0140] · Identification and / or identification list of slices corresponding to PDU sessions (PDU session resources) accepted by a (candidate) target cell in a handover preparation procedure.

[0141] · Information and / or information list of PDU sessions (PDU session resources) accepted by a (candidate) target cell in a handover preparation procedure, including one or more of the following: (candidate) target cell identification, PDU session (PDU session resource) identification, slice identification, QoS flow identification, number of PDU sessions (PDU session resources) accepted.

[0142] · Identification and / or identification list of slices corresponding to PDU sessions (PDU session resources) rejected by a (candidate) target cell in a handover preparation procedure.

[0143] · Information and / or information list of PDU sessions (PDU session resources) rejected by a (candidate) target cell in a handover preparation procedure, including one or more of the following: (candidate) target cell identification, PDU session (PDU session resource) identification, slice identification, QoS flow identification, number of PDU sessions (PDU session resources) rejected.

[0144] · Identification and / or identification list of slices supported by and / or available for a (candidate) target cell.

[0145] Regarding a radio link failure, if the radio link failure occurs within a short period of time after handover, the radio link failure may be caused by handover. In this case, the source node has released the user context. In a case of conditional handover, the source node needs to know the slice information of the selected candidate target cell when performing optimization. For example, if a reselected cell is not among the candidate target cells, a strategy for selecting candidate target cells needs to be optimized; and if the reselected cell is among the candidate target cells, a strategy for setting execution conditions for handover needs to be optimized. The selection of candidate target cells and the setting of execution conditions for handover need to consider condition of the slices supported by the cells (e.g., slices supported by the candidate target cells), and / or condition of the acceptance of PDU sessions (PDU session resources) (e.g., PDU sessions (PDU session resources) accepted by the candidate target cells). The source node may make self-optimization strategies based on the information of the above-mentioned second message.

[0146] Alternatively, the source gNB CU transmits the configuration information associated with a slice-related handover of the (candidate) target cells to the source gNB DU, and the source gNB DU may make handover decisions based on this information, e.g., a Layer 1 / Layer 2 Triggered Mobility (LTM) cell switch. And / or, the source gNB CU transmits the configuration information associated with a slice-related handover of the (candidate) target cells to a (candidate) target gNB DU, and the (candidate) target gNB DU may make handover decisions based on this information, e.g., a (subsequent) Layer 1 / Layer 2 Triggered Mobility (LTM) cell switch. And / or, the source gNB CU transmits the configuration information associated with a slice-related handover of the (candidate) target cells to a (candidate) target gNB CU, and the (candidate) target gNB CU may transmit the configuration information associated with a slice-related handover of the (candidate) target cells to a (candidate) target gNB DU, and the (candidate) target gNB DU may make handover decisions based on this information, e.g., a (subsequent) Layer 1 / Layer 2 Triggered Mobility (LTM) cell switch. For example, the source gNB DU may select a cell that can support the slice accessed by the UE as a target cell for the LTM for handover. For example, the (candidate) target gNB DU may select a cell that can support the slice accessed by the UE as a target cell for the (subsequent) LTM for handover. In some implementations, for example, the above steps may occur in an LTM preparation procedure.

[0147]

[0148] Example 3

[0149] One aspect of the disclosure proposes a method for supporting slice optimization, which may include: a fifth node transmits to a sixth node a third message including a request and / or configuration for (generation and / or reporting of) slice-related successful handover information (i.e., information associated with a successful slice-related handover). After receiving the message, the sixth node may transmit the request and / or configuration to other nodes and / or the UE. The sixth node may also be a UE. The UE records the information associated with a successful slice-related handover in the slice-related successful handover information and / or reports the slice-related successful handover information to a node according to the request and / or configuration for the slice-related successful handover information, and the node may make related self-optimization decisions based on the information in the slice-related successful handover information. For example, the UE records the information associated with a successful slice-related handover in the slice-related successful handover information, and the node may perform optimization of the slice-related handover based on the information in the slice-related successful handover information. For example, if the UE's service cannot continue at the target node, although the handover is successful, but the UE's service is interrupted, and the node can use the above slice-related successful handover information for analysis to avoid subsequent handovers causing service interruption of the UE. The slice-related successful handover information may be included in a Successful Handover Report (SHR) and / or other SON-related reports. The slice-related successful handover information may also be called a slice-related successful handover report. Alternatively, the source node may transmit the request and / or configuration for slice-related successful handover information to the target node, the target node transmits the slice-related successful handover information to the source node, and the source node makes related self-optimization decisions based on the received slice-related successful handover information, for example, adjusting subsequent slice-related handover decisions to ensure handover robustness and / or service continuity. The slice-related successful handover information may be included in an ACCESS AND MOBILITY INDICATION message of Xn.

[0150] In some implementations, the third message may be included in one or more of: an ACCESS AND MOBILITY INDICATION message and / or a HANDOVER REQUEST message of Xn; a UE CONTEXT MODIFICATION REQUIRED message of F1; an OtherConfig or successHO-Config or RRCReconfiguration message or RRCResume message of RRC; or may be transmitted by MAC CE; or an other and / or newly defined RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message.

[0151] In some implementations, the third message and / or the request and / or configuration for slice-related successful handover information may include one or more of the following fields or related information:

[0152] · UE identification: which indicates the user corresponding to the request and / or configuration for (generation and / or reporting of) slice-related successful handover information.

[0153] · Transmitting node identification: used to identify the node that transmits the message.

[0154] · Receiving node identification: used to identify the node that receives the message.

[0155] · Indication of a request of slice-related successful handover information: used to indicate a request to collect and / or report slice-related successful handover information.

[0156] · Information for triggering and / or configuring the generation and / or reporting of slice-related successful handover information: used to represent information (and / or condition) used for triggering and / or configuring the generation and / or reporting of slice-related successful handover information. When the information (and / or condition) for triggering and / or configuring the generation and / or reporting of slice-related successful handover information is met, the UE and / or the message receiving node may generate and / or report slice-related successful handover information. In some implementations, the information (and / or condition) for triggering and / or configuring the generation and / or reporting of slice-related successful handover information may be included in the configuration of slice-related successful handover information which, for example, may be successHO-Config. The information (and / or condition) for triggering and / or configuring the generation and / or reporting of slice-related successful handover information may include one or more of the following: slice replacement occurs (e.g., at the target node), a service requirement (of the UE) cannot be met, a service (of the UE) is interrupted, a threshold of an interruption time of a user plane (of the UE), a threshold of a time interval between a next handover and a current handover (of the UE), a threshold of a camping time (of the UE), etc. Herein, a triggering method related to the threshold of an interruption time of a user plane (of the UE) may be: when the interruption time of the user plane is greater than and / or equal to the configured interruption time threshold of the user plane, the generation and / or reporting of slice-related successful handover information is triggered and / or configured. Herein, a triggering method related to the threshold of a time interval between a next handover and a current handover (of the UE) may be: when the time interval between the next handover and the current handover is less than and / or equal to the configured time interval threshold between the next handover and the current handover, the generation and / or reporting of slice-related successful handover information is triggered and / or configured. By means of the above methods, information of the situation that UE performs handover frequently may be transmitted to the node. The node may perform self-optimization, for example, optimizing mobility decisions. For example, the node may select the target cell of the next handover as the target cell of the current handover, or the node may adjust execution conditions of the conditional handover to avoid frequent handover. Herein, a triggering method related to the threshold of a camping time (of the UE) may be: when the camping time of the UE is less than and / or equal to the configured camping time threshold of the UE, the generation and / or reporting of slice-related successful handover information is triggered and / or configured. By means of the above methods, information of the situation that the camping time at the target node is too short may be transmitted to the node. The node may perform self-optimization, for example, optimizing mobility decisions. For example, the node may select the target cell of the next handover as the target cell of the current handover, or the node may adjust execution conditions of the conditional handover to avoid frequent handover. Herein, a triggering method related to the threshold of a time interval between a next handover and a current handover (of the UE) may be: when the time interval between the next handover and the current handover is greater than and / or equal to the configured time interval threshold between the next handover and the current handover, the generation and / or reporting of slice-related successful handover information is triggered and / or configured. Herein, a triggering method related to the threshold of a camping time (of the UE) may be: when the camping time of the UE is greater than and / or equal to the configured camping time threshold of the UE, the generation and / or reporting of slice-related successful handover information is triggered and / or configured.

[0157] · Slice-related command information: informing the UE and / or the message receiving node of the slice-related command information, which is used for the UE and / or the message receiving node to include the slice-related command information when generating slice-related successful handover information subsequently. When receiving the slice-related successful handover information, the node may find configuration information associated with a slice-related handover applied by the node for the UE based on the slice-related command information, so as to analyze the problems and / or the cause of the problems, and / or make related self-optimization decisions. The slice-related command information can be any information that a node can understand. For example, it may be composed of one or more numbers. After obtaining the information, the node can find the configuration information associated with the slice-related handover corresponding to the handover.

[0158] In some implementations, the third message may also be used for other SON-related reports. For example, the other SON-related reports may be a Connection Establishment Failure (CEF) report, or a Random Access report, or a Successful Handover report, or a Radio Link Failure (RLF) report, or a measurement report, or other wireless connection related reports. Related content of the third message is exchanged between nodes, for example, between the source node and the target node, between the original accessing node and the new accessing node, etc. The node may transmit the related content of the third message to the UE for configuration of other SON related reports, e.g., may be transmitted through an RRCReestablishment message or an RRCReconfiguration message or an RRCResume message or an RRCSetup message; or may be transmitted by MAC CE; or an other and / or newly defined RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message. In some implementations, after the node transmits the related content of the third message to the UE, the UE may add the slice-related command information to other SON-related reports. After the UE transmits the report to the node, the node may find the configuration information associated with the slice-related handover corresponding to the handover applied by the node for the UE according to the slice-related command information., and / or make related self-optimization decisions.

[0159]

[0160] Example 4

[0161] One aspect of the disclosure proposes a method for supporting slice optimization, which may include: a seventh node transmits a fourth message including information about that slice-related successful handover information is available to an eighth node, so that the eighth node knows that the seventh node has slice-related successful handover information stored.

[0162] In some implementations, the fourth message may be included in one or more of: UE-MeasurementsAvailable or RRCReestablishmentComplete message or RRCReconfigurationComplete message or RRCResumeComplete message or RRCSetupComplete message; or may be transmitted by MAC CE; or an other and / or newly defined RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message.

[0163] In some implementations, the fourth message and / or information about that slice-related successful handover information is available may include one or more of the following fields or related information:

[0164] · UE identification: which indicates the user corresponding to the information about that slice-related successful handover information is available.

[0165] · Transmitting node identification: used to identify the node that transmits the message.

[0166] · Receiving node identification: used to identify the node that receives the message.

[0167] · Information about that slice-related successful handover information is available: used to indicate that the slice-related successful handover information is available, indicating that slice-related successful handover information exists. This field may be represented by a single bit. For example, when the bit is 1, it means that the slice-related successful handover information is available, and when the bit is 0, it means that the slice-related successful handover information is not available; alternatively, when the bit is 0, it means that the slice-related successful handover information is available, and when the bit is 1, it means that the slice-related successful handover information is not available.

[0168] In some implementations, the eighth node may transmit a fifth message including a request for slice-related successful handover information to the seventh node according to its own situation and / or according to the fourth message received from the seventh node including information about that the slice-related successful handover information is available, to request the seventh node to report slice-related successful handover information.

[0169] In some implementations, the fifth message may be included in one or more of: a UEInformationRequest message of RRC; or an other and / or newly defined RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message.

[0170] In some implementations, the fifth message and / or the request for slice-related successful handover information may include one or more of the following fields or related information:

[0171] · UE identification: which indicates the user corresponding to the request for slice-related successful handover information.

[0172] · Transmitting node identification: used to identify the node that transmits the message.

[0173] · Receiving node identification: used to identify the node that receives the message.

[0174] · A request for slice-related successful handover information: used to indicate a request for slice-related successful handover information, indicating that the slice-related successful handover information is requested. This field may be represented by a single bit. For example, when the bit is 1, it means that slice-related successful handover information is requested, and when the bit is 0, it means that slice-related successful handover information is not requested; alternatively, when the bit is 0, it indicates that slice-related successful handover information is requested, and when the bit is 1, it indicates that slice-related successful handover information is not requested.

[0175] In some implementations, the seventh node transmits a sixth message including slice-related successful handover information to the eighth node, so that the eighth node can obtain related information of the slice-related handover. In some implementations, for example, the seventh node transmits the sixth message including the slice-related successful handover information to the eighth node based on the request for the slice-related successful handover information received from the eighth node. In some implementations, for example, the UE records the information associated with a successful slice-related handover in the slice-related successful handover information and / or reports the slice-related successful handover information to a node, and the node may make related self-optimization decisions based on the information in the slice-related successful handover information. For example, the UE records the information associated with a successful slice-related handover in the slice-related successful handover information, and the node may perform optimization of the slice-related handover based on the information in the slice-related successful handover information. For example, if the UE's service cannot continue at the target node, although the handover is successful, but the UE's service is interrupted, and the node can use the above slice-related successful handover information for analysis to avoid subsequent handovers causing service interruption of the UE. The slice-related successful handover information may be included in a Successful Handover Report (Successful Handover Report, SHR). The slice-related successful handover information may also be called a slice-related successful handover report. Alternatively, the target node may transmit slice-related successful handover information to the source node, and the source node may make related self-optimization decisions based on the received slice-related successful handover information, for example, adjusting subsequent slice-related handover decisions to ensure handover robustness and / or service continuity. The slice-related successful handover information may be included in an ACCESS AND MOBILITY INDICATION message of Xn. If the seventh node is a UE, the UE records and / or generates and / or reports the sixth message according to the request and / or configuration for (generation and / or reporting of) the slice-related successful handover information (i.e., information associated with a successful slice-related handover). This solution can reduce handover failures and / or radio link failures, and / or improve the robustness of handover.

[0176] In some implementations, the sixth message may be included in one or more of: a User Information Response (UEInformationResponse), Secondary Cell Group Failure Information (SCGFailureInformation), Master Cell Group Failure Information (MCGFailureInformation) of RRC; a FAILURE INDICATION message, a HANDOVER REPORT message, an ACCESS AND MOBILITY INDICATION message, a S-NODE MODIFICATION REQUEST message, a SgNB MODIFICATION REQUEST message, a SCG FAILURE INFORMATION REPORT message, an RRC TRANSFER message of Xn; an ACCESS AND MOBILITY INDICATION message of F1; an UPLINK RAN CONFIGURATION TRANSFER message, a DOWNLINK RAN CONFIGURATION TRANSFER message of NG; or an other and / or newly defined RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message. This information may be included in a report, where the report may be a Connection Establishment Failure (CEF) report, or a Random Access report, or a Successful Handover report, or a Radio Link Failure (RLF) report, or a measurement report, or other wireless connection related reports.

[0177] In some implementations, the sixth message and / or the slice-related successful handover information may include one or more of the following fields or related information:

[0178] · UE identification: which indicates the user corresponding to the slice-related successful handover information.

[0179] · Identification of slice-related handover: which indicates whether the handover is a slice-related handover. This field may be represented by a single bit. For example, when the bit is 1, it means that the handover is a slice-related handover; and when the bit is 0, it means that the handover is not a slice-related handover; alternatively, when the bit is 0, it indicates that the handover is a slice-related handover, and when the bit is 1, it indicates that the handover is not a slice-related handover.

[0180] · Slice-related command information: used by the UE to include the slice-related command information when generating slice-related successful handover information. The slice-related command information may come from a request and / or configuration for slice-related successful handover information. When the node receives the slice-related successful handover information, it can find the configuration information associated with the slice-related handover of this handover applied by the node for the UE according to the slice-related command information, so as to analyze the problems and / or the cause of the problems, and / or make related self-optimization decisions. The slice-related command information can be any information that a node can understand. For example, it may be composed of one or more numbers. After obtaining the information, the node can find the slice-related handover configuration information corresponding to the handover.

[0181] · Information related to whether a UE supports slice replacement: used to indicate whether the UE supports slice replacement.

[0182] · Information related to whether slice replacement has occurred: it may indicate whether slice replacement has occurred.

[0183] · Identification and / or identification list of original slices related to slice replacement that occurred: for example, the original slice may be a slice before the slice replacement. For example, the original slice may be a slice which is replaced in the slice replacement. If slice replacement occurs, this information is included in the sixth message.

[0184] · Identification and / or identification list of replacing slices related to slice replacement that occurred: for example, it may be identification and / or identification list of alternative slices. For example, it may also be identification and / or identification list of slices after the slice replacement. For example, it may be identification and / or identification list of slices that replace the original slices after the slice replacement. If slice replacement occurs, this information is included in the sixth message.

[0185] · Whether a service requirement can be met on a target cell.

[0186] · Identification and / or identification list of slices corresponding to PDU sessions (PDU session resources) that meet a service requirement on a target cell: in some implementations, for example, if there are one or more PDU sessions (PDU session resources) and / or slices that meet a service requirement on the target cell, this information is included in the sixth message. Alternatively, for example, if there are one or more PDU sessions (PDU session resources) and / or slices that do not meet a service requirement on the target cell, this information is included in the sixth message. This information is used to indicate slices corresponding to PDU sessions (PDU session resources) that meet a requirement.

[0187] · Information and / or information list of PDU sessions (PDU session resources) that meet a service requirement on a target cell, including one or more of the following: PDU session (PDU session resource) identification, slice identification, QoS flow identification, number of PDU sessions (PDU session resources) that meet a service requirement. in some implementations, for example, if there are one or more PDU sessions (PDU session resources) and / or slices that meet a service requirement on the target cell, this information is included in the sixth message. Alternatively, for example, if there are one or more PDU sessions (PDU session resources) and / or slices that do not meet a service requirement on the target cell, this information is included in the sixth message. This information is used to indicate slices corresponding to PDU sessions (PDU session resources) that meet a requirement.

[0188] · Identification and / or identification list of slices corresponding to PDU sessions (PDU session resources) that do not meet a service requirement on a target cell: in some implementations, for example, if there are one or more PDU sessions (PDU session resources) and / or slices that do not meet a service requirement on the target cell, this information is included in the sixth message. This information is used to indicate slices corresponding to PDU sessions (PDU session resources) that do not meet a requirement.

[0189] · Information and / or information list of PDU sessions (PDU session resources) that do not meet a service requirement on a target cell, including one or more of the following: PDU session (PDU session resource) identification, slice identification, QoS flow identification, number of PDU sessions (PDU session resources) that do not meet a service requirement. In some implementations, for example, if there are one or more PDU sessions (PDU session resources) and / or slices that do not meet a service requirement on the target cell, this information is included in the sixth message. This information is used to indicate slices corresponding to PDU sessions (PDU session resources) that do not meet a requirement.

[0190] · Service parameters achieved on a target cell: in some implementations, for example, if there is a situation where a service requirement is (not) met, this information is included in the sixth message. Alternatively, for example, if there are one or more PDU sessions (PDU session resources) and / or slices that (do not) meet a service requirement on the target cell, this information is included in the sixth message.

[0191] · Difference between a service parameter achieved on a target cell and a service requirement: in some implementations, for example, if there is a situation where a service requirement is not met, this information is included in the sixth message. Alternatively, for example, if there are one or more PDU sessions (PDU session resources) and / or slices that do not meet a service requirement on the target cell, this information is included in the sixth message.

[0192] · Service requirement that needs to be achieved: in some implementations, for example, if there is a situation where a service requirement is (not) met, this information is included in the sixth message. Alternatively, for example, if there are one or more PDU sessions (PDU session resources) and / or slices that (do not) meet a service requirement on the target cell, this information is included in the sixth message. This information may include one or more of the following: slice identification, PDU session (PDU session resource) identification, and service requirements that need to be achieved.

[0193] · Whether a service is interrupted: for example, it may indicate whether service interruption occurs.

[0194] · Information corresponding to an interrupted service: it may include one or more of the following: a service type corresponding to the service interruption, (identification and / or identification list of) PDU sessions corresponding to the service interruption, (identification and / or identification list of) slices corresponding to the PDU sessions corresponding to the service interruption, service requirements corresponding to the service interruption, etc.

[0195] · Identification and / or identification list of slices corresponding to PDU sessions (PDU session resources) established on a target cell and / or accepted by a target cell.

[0196] · Information and / or information list of PDU sessions (PDU session resources) established on a target cell and / or accepted by a target cell, including one or more of the following: PDU session (PDU session resource) identification, slice identification, QoS flow identification, number of PDU sessions (PDU session resources) established and / or accepted, whether all PDU sessions (PDU session resources) are accepted, whether some of the PDU sessions (PDU session resources) are rejected, whether all the PDU sessions (PDU session resources) are rejected.

[0197] · Identification and / or identification list of slices corresponding to PDU sessions (PDU session resources) that cannot be established on a target cell and / or are rejected by a target cell.

[0198] · Information and / or information list of PDU sessions (PDU session resources) that cannot be established on a target cell and / or are rejected by a target cell, including one or more of the following: PDU session (PDU session resource) identification, slice identification, QoS flow identification, number of PDU sessions (PDU session resources) that cannot be established and / or rejected, whether all PDU sessions (PDU session resources) are accepted, whether some of the PDU sessions (PDU session resources) are rejected, whether all the PDU sessions (PDU session resources) are rejected.

[0199] · Execution condition for a handover: for example, used to indicate the execution condition of the handover.

[0200] · Execution condition for a next handover.

[0201] · Identification of a target cell for a next handover.

[0202] · Whether the target cell of the next handover belongs to configured and / or requested handover candidate cells.

[0203] The next handover is the next handover after the handover corresponding to a successful handover generation and / or reporting configuration. Alternatively, the next handover may be the next handover after the handover corresponding to the request and / or configuration for (generation and / or reporting of) slice-related successful handover information (i.e., information associated with a successful slice-related handover).

[0204]

[0205] Example 5

[0206] One aspect of the disclosure proposes a method for supporting slice optimization, which may include: a ninth node transmits a seventh message including information related to a request and / or trigger (e.g., a trigger condition, etc.) for reporting of user history information to a tenth node. After receiving the seventh message, the tenth node transmits user history information to the ninth node according to the information of the seventh message.

[0207] In some implementations, the seventh message may be included in one or more of: an ACCESS AND MOBILITY INDICATION message and / or a HANDOVER REQUEST message of Xn; a UE CONTEXT MODIFICATION REQUIRED message of F1; an OtherConfig or successHO-Config or RRCReconfiguration message or RRCResume message of RRC; or may be transmitted by MAC CE; or an other and / or newly defined RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message.

[0208] In some implementations, the seventh message and / or information related to a request and / or trigger for reporting of user history information may include one or more of the following fields or related information:

[0209] · UE identification: which indicates a UE corresponding to the information related to a request and / or trigger for reporting of user history information.

[0210] · Transmitting node identification: used to identify the node that transmits the message.

[0211] · Receiving node identification: used to identify the node that receives the message.

[0212] · Indication of a request for user history information: used to indicate to request and / or trigger the user history information to be reported.

[0213] · Information (and / or conditions) related to a request and / or trigger for reporting of user history information: which represents the information (and / or conditions) used for a request and / or trigger for reporting of user history information. When the information related to a request and / or trigger for reporting of user history information is met, the message receiving node reports user history information. The information (and / or conditions) related to a request and / or trigger for reporting of user history information may include one or more of the following: a threshold of a time interval between a next handover and a current handover, a threshold of a camping time, etc. Herein, a triggering method (and / or a triggering condition) related to the threshold of a time interval between a next handover and a current handover may be: when the time interval between the next handover and the current handover is less than and / or equal to the configured time interval threshold between the next handover and the current handover, user history information is reported. Herein, a triggering method (and / or a triggering condition) related to the threshold of a camping time may be: when the camping time of the UE is less than and / or equal to the configured camping time threshold of the UE, user history information is reported.

[0214] In some implementations, the tenth node may transmit user history information to the ninth node according to its own situation and / or after receiving the seventh message transmitted by the ninth node. The tenth node makes related self-optimization decisions based on the user history information. In some implementations, for example, the target node transmits user history information to the source node, and the source node makes related self-optimization decisions based on the user history information. For example, when the camping time of the UE is short and multiple handovers occur in a short period of time, the source node may directly hand over the UE to a cell with a long camping time to avoid frequent handover.

[0215] The user history information may include information of a cell serving the UE in a connected state before the target cell. The user history information includes one or more of:

[0216] · UE identification: which indicates a UE corresponding to the user history information.

[0217] · Identification of a cell previously connected to and / or camped on: used to identify a cell that served the UE before the UE connects to the target node.

[0218] · A camping time on the cell indicated by the identification of the cell above.

[0219] In the disclosure, slice replacement may also be referred to as slice remapping.

[0220] In the disclosure, the self-optimization (decisions and / or strategies) may include network energy saving, load balancing, coverage optimization, mobility optimization and / or management, making and / or update configuration, etc.

[0221] In the disclosure, results and reports may be referred to each other.

[0222] In the disclosure, time can be represented by one or more of the following: timestamp, time point, time interval, timer, period of time, time length, time period, time spacing, etc. The time length may be the length of time from a certain time point, which may be the current time. The time may be a relative time or an absolute time. In some implementations, the period of time may be represented by separate fields, for example, by a combination of a start time and an end time, or by a combination of a start time and a time period.

[0223] In the disclosure, Quality of Experience (QoE) parameters and / or user experience parameters may include one or more of the following: Round-trip time, Jitter duration, Corruption duration, Average throughput, Initial playout delay, Playout Delay at Initial Startup, Device information, Rendered viewports, Codec information, Buffer level, Representation switch events, Play List, Media presentation description (MPD) information, Interactivity Summary, Interactivity Event List, etc., and the satisfaction of QoE parameters. Herein, The satisfaction of QoE parameters may include one or more of the following: whether QoE parameters meet QoE requirements, the proportion of QoE parameters which meet QoE requirements, proportion of QoE parameters which do not meet QoE requirements, information of time when QoE parameters meet the requirements, information of time when QoE parameters do not meet the requirements, cells whose QoE parameters meet the requirements (ID and / or ID list), cells whose QoE parameters do not meet the requirements (ID and / or ID list), beams whose QoE parameters meet the requirements (ID and / or ID list), beams whose QoE parameters do not meet the requirements (ID and / or ID list), slices whose QoE parameters meet the requirements (ID and / or ID list), slices whose QoE parameters do not meet the requirements (ID and / or ID list), nodes whose QoE parameters meet the requirements (ID and / or ID list), nodes whose QoE parameters do not meet the requirements, information of locations where QoE parameters meet the requirements, information of locations where QoE parameters do not meet the requirements, etc.

[0224] In the disclosure, Quality of Service (QoS) parameters and / or QoS may include at least one of the following: packet loss rate, delay, throughput, data rate, etc., and the satisfaction of QoS parameters. Herein, The satisfaction of QoS parameters may include one or more of the following: whether QoS parameters meet QoS requirements, proportion of QoS parameters which meet QoS requirements, proportion of QoS parameters which do not meet QoS requirements, information of time when QoS parameters meet requirements, information of time when QoS parameters do not meet requirements, cells whose QoS parameters meet the requirements (ID and / or ID list), cells whose QoS parameters do not meet the requirements (ID and / or ID list), beams whose QoS parameters meet the requirements (ID and / or ID list), beams whose QoS parameters do not meet the requirements (ID and / or ID list), slices whose QoS parameters meet the requirements (ID and / or ID list), slices whose QoS parameters do not meet the requirements (ID and / or ID list), nodes whose QoS parameters meet the requirements (ID and / or ID list), nodes whose QoS parameters do not meet the requirements (ID and / or ID list), information of locations where QoS parameters meet the requirements, information of locations where QoS parameters do not meet the requirements, etc.

[0225] In the disclosure, service requirements may include one or more of the following: service requirements, Service-Level Agreement (SLA) requirements, application layer requirements, QoS requirements, QoE requirements, etc. A requirement may refer to a threshold that a related parameter need to reach.

[0226] In the disclosure, service parameters may include one or more of the following: service parameters, application layer parameters, QoS parameters, QoE parameters, etc.

[0227] Exemplary embodiments of the disclosure are further described below with reference to the accompanying drawings.

[0228] The text and drawings are provided as examples only to help understand the disclosure. They should not be construed as limiting the scope of the disclosure in any way. Although certain embodiments and examples have been provided, based on the disclosure herein, it is obvious to those skilled in the art that changes can be made to the illustrated embodiments and examples without departing from the scope of the disclosure.

[0229]

[0230] Figure 3a illustrates a schematic diagram of an aspect of a method for supporting slice optimization according to embodiments of the disclosure. Specifically, Figure 3a illustrates a process of exchanging slice-related radio link failure information between two nodes, so that the second node can obtain the slice-related radio link failure information. For example, the slice-related radio link failure information may be used for the second node to analyze the reason of a slice-related radio link failure and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration, or it may be used for the second node to analyze whether the problem originates from itself or other nodes when analyzing the reason of a radio link failure and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration, or it may be forwarded by the second node to other nodes for the other nodes to analyze a failure reason and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration.

[0231] In some implementations, for example, the first node may be a UE and the second node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In other implementations, for example, the first node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB, and the second node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In yet other implementations, for example, the first node may be an AMF or SMF or MME, and the second node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB. In yet other implementations, for example, the first node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB, and the second node may be an AMF or SMF or MME.

[0232] Step 301A: the first node transmits slice-related radio link failure information to the second node. The slice-related radio link failure information may be the aforementioned first message.

[0233] Step 302A: the second node may analyze the reason of a slice-related radio link failure and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration based on the received slice-related radio link failure information, or it may be used for the second node to analyze whether the problem originates from itself or other nodes when analyzing the reason of a radio link failure and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration, or it may be forwarded by the second node to other nodes for the other nodes to analyze a failure reason and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration.

[0234]

[0235] Figure 3b illustrates a schematic diagram of an aspect of a method for supporting slice optimization according to embodiments of the disclosure. Specifically, Figure 3b illustrates a process of exchanging slice-related radio link failure information between two nodes, so that the second node can obtain the slice-related radio link failure information. For example, the slice-related radio link failure information may be used for the second node to analyze the reason of a slice-related radio link failure and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration, or it may be used for the second node to analyze whether the problem originates from itself or other nodes when analyzing the reason of a radio link failure and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration, or it may be forwarded by the second node to other nodes for the other nodes to analyze a failure reason and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration.

[0236] In some implementations, for example, the first node may be a UE and the second node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In other implementations, for example, the first node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB, and the second node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In yet other implementations, for example, the first node may be an AMF or SMF or MME, and the second node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB. In yet other implementations, for example, the first node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB, and the second node may be an AMF or SMF or MME.

[0237] Step 301B: the second node transmits a request for slice-related radio link failure information to the first node to request the first node to report the slice-related radio link failure information.

[0238] Step 302B: the first node transmits slice-related radio link failure information to the second node. The slice-related radio link failure information may be the aforementioned first message.

[0239] Step 303B: the second node may analyze the reason of a slice-related radio link failure and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration based on the received slice-related radio link failure information, or it may be used for the second node to analyze whether the problem originates from itself or other nodes when analyzing the reason of a radio link failure and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration, or it may be forwarded by the second node to other nodes for the other nodes to analyze a failure reason and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration.

[0240]

[0241] Figure 3c illustrates a schematic diagram of an aspect of a method for supporting slice optimization according to embodiments of the disclosure. Specifically, Figure 3c illustrates a process of exchanging slice-related radio link failure information between two nodes, so that the second node can obtain the slice-related radio link failure information. For example, it may be used for the second node to analyze the reason of a slice-related radio link failure and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration, or it may be used for the second node to analyze whether the problem originates from itself or other nodes when analyzing the reason of a radio link failure and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration, or it may be forwarded by the second node to other nodes for the other nodes to analyze a failure reason and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration.

[0242] In some implementations, for example, the first node may be a UE and the second node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In other implementations, for example, the first node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB, and the second node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In yet other implementations, for example, the first node may be an AMF or SMF or MME, and the second node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB. In yet other implementations, for example, the first node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB, and the second node may be an AMF or SMF or MME.

[0243] Step 301C: the first node transmits information about that slice-related radio link failure information is available to the second node to inform the second node that the first node has available slice-related radio link failure information.

[0244] Step 302C: the second node transmits a request for slice-related radio link failure information to the first node to request the first node to report the slice-related radio link failure information.

[0245] Step 303C: the first node transmits slice-related radio link failure information to the second node. The slice-related radio link failure information may be the aforementioned first message.

[0246] Step 304C: the second node may analyze the reason of a slice-related radio link failure and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration based on the received slice-related radio link failure information, or it may be used for the second node to analyze whether the problem originates from itself or other nodes when analyzing the reason of a radio link failure and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration, or it may be forwarded by the second node to other nodes for the other nodes to analyze a failure reason and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration.

[0247]

[0248] Figure 3d illustrates a schematic diagram of an aspect of a method for supporting slice optimization according to embodiments of the disclosure. Specifically, Figure 3d illustrates a process of exchanging slice-related radio link failure information between a UE, a node, and a last serving node, so that the last serving node can obtain slice-related radio link failure information. For example, it may be used for the last serving node to analyze the reason of a slice-related radio link failure and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration, or it may be used for the last serving node to analyze whether the problem originates from itself or other nodes when analyzing the reason of a radio link failure and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration, or it may be forwarded by the last serving node to other nodes for the other nodes to analyze a failure reason and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration.

[0249] Step 301D: a handover procedure is performed between the UE and the last serving node.

[0250] Step 302D: a radio link failure occurs between the UE and the last serving node, and the UE performs an RRC setup or reestablishment process with the node.

[0251] Step 303D: the UE transmits information about that slice-related radio link failure information is available to the node to inform the node that the UE has available slice-related radio link failure information. The information about that slice-related radio link failure information is available may be carried by an RRCResumeComplete message or an RRCSetupComplete message or an RRCReestablishmentComplete message or an RRCReconfigurationComplete message.

[0252] Step 304D: the node transmits a request for slice-related radio link failure information to the UE to request the UE to report the slice-related radio link failure information. The request for slice-related radio link failure information may be carried by a UEInformationRequest message of RRC.

[0253] Step 305D: UE transmits slice-related radio link failure information to the node. The slice-related radio link failure information may be the aforementioned first message. The slice-related radio link failure information may be carried by a UEInformationResponse message of RRC. The radio link failure information may be included in a Radio Link Failure (RLF) report.

[0254] Step 306D: the node transmits slice-related radio link failure information to the last serving node. The slice-related radio link failure information may be the aforementioned first message. The slice-related radio link failure information may be carried by a FAILURE INDICATION message or a HANDOVER REPORT message or an ACCESS AND MOBILITY INDICATION message. The radio link failure information may be included in a Radio Link Failure (RLF) report.

[0255] Step 307D: the last serving node may analyze the reason of a slice-related radio link failure and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration based on the received slice-related radio link failure information, or it may be used for the last serving node to analyze whether the problem originates from itself or other nodes when analyzing the reason of a radio link failure and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration, or it may be forwarded by the last serving node to other nodes for the other nodes to analyze a failure reason and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration. For example, when the last serving node determines that the problem originates from another node (e.g., the source node of the handover) when analyzing the reason of the radio link failure, the last serving node may forward the slice-related radio link failure information to the other node.

[0256]

[0257] Figure 3e illustrates a schematic diagram of an aspect of a method for supporting slice optimization according to embodiments of the disclosure. Specifically, Figure 3e illustrates a process of exchanging slice-related radio link failure information between a UE, a master node, and a secondary node, so that the secondary node can obtain the slice-related radio link failure information. For example, it may be used for the secondary node to analyze the reason of a slice-related radio link failure and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration, or it may be used for the secondary node to analyze whether the problem originates from itself or other nodes when analyzing the reason of a radio link failure and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration, or it may be forwarded by the secondary node to other nodes for the other nodes to analyze a failure reason and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration.

[0258] Step 301E: the UE performs a dual-connectivity handover procedure with the nodes.

[0259] Step 302E: a radio link failure occurs between the UE and the secondary node. The UE transmits slice-related radio link failure information to the master node. The slice-related radio link failure information may be the aforementioned first message. The slice-related radio link failure information may be carried by an SCGFailureInformation message. The radio link failure information may be included in a Radio Link Failure (RLF) report.

[0260] Step 303E: the master node transmits slice-related radio link failure information to the secondary node. The slice-related radio link failure information may be the aforementioned first message. The slice-related radio link failure information may be carried by a SgNB Modification Request message or a SCG Failure Information Report message or a FAILURE INDICATION message or a HANDOVER REPORT message or an ACCESS AND MOBILITY INDICATION message. The radio link failure information may be included in a Radio Link Failure (RLF) report.

[0261] Step 304E: the secondary node may analyze the reason of a slice-related radio link failure and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration based on the received slice-related radio link failure information, or it may be used for the secondary node to analyze whether the problem originates from itself or other nodes when analyzing the reason of a radio link failure and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration, or it may be forwarded by the secondary node to other nodes for the other nodes to analyze a failure reason and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration. For example, when the secondary node determines that the problem originates from another node (e.g., the source node of the handover) when analyzing the reason of the radio link failure, the secondary node may forward the slice-related radio link failure information to the other node.

[0262]

[0263] Figure 3f illustrates a schematic diagram of an aspect of a method for supporting slice optimization according to embodiments of the disclosure. Specifically, Figure 3f illustrates a process of exchanging slice-related radio link failure information between a UE, a master node, and a secondary node, so that the master node can obtain the slice-related radio link failure information. For example, it may be used for the master node to analyze the reason of a slice-related radio link failure and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration, or it may be used for the master node to analyze whether the problem originates from itself or other nodes when analyzing the reason of a radio link failure and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration, or it may be forwarded by the master node to other nodes for the other nodes to analyze a failure reason and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration.

[0264] Step 301F: the UE performs a dual-connectivity handover procedure with the nodes.

[0265] Step 302F: a radio link failure occurs between the UE and the secondary node. The UE transmits slice-related radio link failure information to the master node. The slice-related radio link failure information may be the aforementioned first message. The slice-related radio link failure information may be carried by a MCGFailureInformation message. The radio link failure information may be included in a Radio Link Failure (RLF) report.

[0266] Step 303F: the secondary node transmits slice-related radio link failure information to the primary node. The slice-related radio link failure information may be the aforementioned first message. The slice-related radio link failure information may be carried by an RRC TRANSFER message or a FAILURE INDICATION message or a HANDOVER REPORT message or an ACCESS AND MOBILITY INDICATION message. The radio link failure information may be included in a Radio Link Failure (RLF) report.

[0267] Step 304F: the master node may analyze the reason of a slice-related radio link failure and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration based on the received slice-related radio link failure information, or it may be used for the master node to analyze whether the problem originates from itself or other nodes when analyzing the reason of a radio link failure and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration, or it may be forwarded by the master node to other nodes for the other nodes to analyze a failure reason and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration. For example, when the master node determines that the problem originates from another node (e.g., the source node of the handover) when analyzing the reason of the radio link failure, the master node may forward the slice-related radio link failure information to the other node

[0268]

[0269] Figure 3g illustrates a schematic diagram of an aspect of a method for supporting slice optimization according to embodiments of the disclosure. Specifically, Figure 3g illustrates a process of exchanging slice-related radio link failure information between a UE, a node, a last serving node, and an AMF, so that the last serving node can obtain the slice-related radio link failure information. For example, it may be used for the last serving node to analyze the reason of a slice-related radio link failure and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration, or it may be used for the last serving node to analyze whether the problem originates from itself or other nodes when analyzing the reason of a radio link failure and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration, or it may be forwarded by the last serving node to other nodes for the other nodes to analyze a failure reason and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration.

[0270] Step 301G: a handover procedure is performed between the UE and the last serving node.

[0271] Step 302G: a radio link failure occurs between the UE and the last serving node, and the UE performs an RRC setup or reestablishment process with the node.

[0272] Step 303G: the UE transmits information about that slice-related radio link failure information is available to the node to inform the node that the UE has available slice-related radio link failure information. The information about that slice-related radio link failure information is available may be carried by an RRCResumeComplete message or an RRCSetupComplete message or an RRCReestablishmentComplete message or an RRCReconfigurationComplete message.

[0273] Step 304G: the node transmits a request for slice-related radio link failure information to the UE to request the UE to report the slice-related radio link failure information. The request for slice-related radio link failure information may be carried by a UEInformationRequest message of RRC.

[0274] Step 305G: UE transmits slice-related radio link failure information to the node. The slice-related radio link failure information may be the aforementioned first message. The slice-related radio link failure information may be carried by a UEInformationResponse message of RRC. The radio link failure information may be included in a Radio Link Failure (RLF) report.

[0275] Step 306G: the node transmits slice-related radio link failure information to the AMF. The slice-related radio link failure information may be the aforementioned first message. The slice-related radio link failure information may be carried by an UPLINK RAN CONFIGURATION TRANSFER message. The radio link failure information may be included in a Radio Link Failure (RLF) report.

[0276] Step 307G: the AMF transmits slice-related radio link failure information to the last serving node. The slice-related radio link failure information may be the aforementioned first message. The slice-related radio link failure information may be carried by a DOWNLINK RAN CONFIGURATION TRANSFER message. The radio link failure information may be included in a Radio Link Failure (RLF) report.

[0277] Step 308G: the last serving node may analyze the reason of a slice-related radio link failure and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration based on the received slice-related radio link failure information, or it may be used for the last serving node to analyze whether the problem originates from itself or other nodes when analyzing the reason of a radio link failure and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration, or it may be forwarded by the last serving node to other nodes for the other nodes to analyze a failure reason and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration. For example, when the last serving node determines that the problem originates from another node (e.g., the source node of the handover) when analyzing the reason of the radio link failure, the last serving node may forward the slice-related radio link failure information to the other node.

[0278]

[0279] Figure 4a illustrates a schematic diagram of an aspect of a method for supporting slice optimization according to embodiments of the disclosure. Specifically, Figure 4a illustrates a process of exchanging configuration information associated with a slice-related handover between two nodes. After receiving the information, the fourth node may perform analysis and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration based on the received slice-related radio link failure information and / or configuration information associated with a slice-related handover, and / or transmit the configuration information associated with a slice-related handover to other nodes, for the other nodes to perform analysis and / or make related self-optimization decisions and / or perform self-optimization based on the configuration information associated with a slice-related handover and / or other information (e.g., (slice-related) radio link failure information).

[0280] In some implementations, for example, the third node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB, and the fourth node may be a UE. In other implementations, for example, the third node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB, and the fourth node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In yet other implementations, for example, the third node may be an AMF or SMF or MME, and the fourth node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB. In yet other implementations, for example, the third node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB, and the fourth node may be an AMF or SMF or MME.

[0281] Step 401A: the third node transmits configuration information associated with a slice-related handover to the fourth node. The configuration information associated with a slice-related handover may be the aforementioned second message.

[0282] Step 402A: the fourth node may make related self-optimization decisions and / or perform self-optimization and / or update configuration based on the received configuration information associated with a slice-related handover, or it may be forwarded by the fourth node to other nodes for the other nodes to make related self-optimization decisions and / or perform self-optimization and / or update configuration.

[0283]

[0284] Figure 4b illustrates a schematic diagram of an aspect of a method for supporting slice optimization according to embodiments of the disclosure. Specifically, Figure 4b illustrates a process of exchanging slice-related radio link failure information and / or configuration information associated with a slice-related handover between a UE, a reconnect node, a last serving node (e.g., a handover target node), and a handover source node. After receiving the information, the handover source node may perform analysis and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration based on the received slice-related radio link failure information and / or configuration information associated with a slice-related handover, and / or transmit the configuration information associated with a slice-related handover to other nodes, for the other nodes to perform analysis and / or make related self-optimization decisions and / or perform self-optimization and / or make handover decisions based on the configuration information associated with a slice-related handover and / or other information (e.g., (slice-related) radio link failure information).

[0285] Step 401B: the handover source node transmits configuration information associated with a slice-related handover to the last serving node (e.g., handover target node). The configuration information associated with a slice-related handover may be the aforementioned second message. The configuration information associated with a slice-related handover may be carried by a SN STATUS TRANSFER message.

[0286] Step 402B: a radio link failure occurs between the UE and the last serving node (e.g., handover target node).

[0287] Step 403B: the UE transmits slice-related radio link failure information to the reconnect node. The slice-related radio link failure information may be the aforementioned first message. The slice-related radio link failure information may be carried by a UEInformationResponse message of RRC. The radio link failure information may be included in a Radio Link Failure (RLF) report.

[0288] Step 404B: the reconnect node transmits slice-related radio link failure information to the last serving node (e.g., handover target node). The slice-related radio link failure information may be the aforementioned first message. The slice-related radio link failure information may be carried by a FAILURE INDICATION message or a HANDOVER REPORT message or an ACCESS AND MOBILITY INDICATION message. The radio link failure information may be included in a Radio Link Failure (RLF) report.

[0289] Step 405B: the last serving node (e.g., handover target node) transmits slice-related radio link failure information and / or configuration information associated with a slice-related handover to the handover source node. The slice-related radio link failure information may be the aforementioned first message. The configuration information associated with a slice-related handover may be the aforementioned second message. The slice-related radio link failure information and / or configuration information associated with a slice-related handover may be carried by a FAILURE INDICATION message or a HANDOVER REPORT message or an ACCESS AND MOBILITY INDICATION message. The radio link failure information may be included in a Radio Link Failure (RLF) report.

[0290] Step 406B: the handover source node may make related self-optimization decisions and / or perform self-optimization and / or update configuration based on the received slice-related radio link failure information and / or configuration information associated with a slice-related handover, or it may be forwarded by the handover source node to other nodes for the other nodes to make related self-optimization decisions and / or perform self-optimization and / or update configuration.

[0291]

[0292] Figure 4c illustrates a schematic diagram of an aspect of a method for supporting slice optimization according to embodiments of the disclosure. Specifically, Figure 4c illustrates a process of exchanging slice-related radio link failure information and / or configuration information associated with a slice-related handover between a UE, a reconnect node, a last serving node, and a handover source node. After receiving the information, the handover source node may perform analysis and / or make related self-optimization decisions and / or perform self-optimization and / or update configuration based on the received slice-related radio link failure information and / or configuration information associated with a slice-related handover, and / or transmit the configuration information associated with a slice-related handover to other nodes, for the other nodes to perform analysis and / or make related self-optimization decisions and / or perform self-optimization and / or make handover decisions based on the configuration information associated with a slice-related handover and / or other information (e.g., (slice-related) radio link failure information).

[0293] Step 401C: a handover procedure is performed between the UE and the last serving node. (e.g. handover target node).

[0294] Step 402C: the handover source node transmits configuration information associated with a slice-related handover to the last serving node (e.g., handover target node). The configuration information associated with a slice-related handover may be the aforementioned second message. The configuration information associated with a slice-related handover may be carried by a SN STATUS TRANSFER message.

[0295] Step 403C: a radio link failure occurs between the UE and the last serving node (e.g., handover target node).

[0296] Step 404C: the UE performs an RRC setup or reestablishment process with the reconnect node.

[0297] Step 405C: the UE transmits information about that slice-related radio link failure information is available to the reconnect node to inform the reconnect node that the UE has available slice-related radio link failure information. The information about that slice-related radio link failure information is available may be carried by an RRCResumeComplete message or an RRCSetupComplete message or an RRCReestablishmentComplete message or an RRCReconfigurationComplete message.

[0298] Step 406C: the reconnect node transmits a request for slice-related radio link failure information to the UE to request the UE to report the slice-related radio link failure information. The request for slice-related radio link failure information may be carried by a UEInformationRequest message of RRC.

[0299] Step 407C: the UE transmits slice-related radio link failure information to the reconnect node. The slice-related radio link failure information may be the aforementioned first message. The slice-related radio link failure information may be carried by a UEInformationResponse message of RRC. The radio link failure information may be included in a Radio Link Failure (RLF) report.

[0300] Step 408C: the reconnect node transmits slice-related radio link failure information to the last serving node (e.g., handover target node). The slice-related radio link failure information may be the aforementioned first message. The slice-related radio link failure information may be carried by a FAILURE INDICATION message or a HANDOVER REPORT message or an ACCESS AND MOBILITY INDICATION message. The radio link failure information may be included in a Radio Link Failure (RLF) report.

[0301] Step 409C: the last serving node (e.g., handover target node) transmits slice-related radio link failure information and / or configuration information associated with a slice-related handover to the handover source node. The slice-related radio link failure information may be the aforementioned first message. The configuration information associated with a slice-related handover may be the aforementioned second message. The slice-related radio link failure information and / or configuration information associated with a slice-related handover may be carried by a FAILURE INDICATION message or a HANDOVER REPORT message or an ACCESS AND MOBILITY INDICATION message. The radio link failure information may be included in a Radio Link Failure (RLF) report.

[0302] Step 410C: the handover source node may make related self-optimization decisions and / or perform self-optimization and / or update configuration based on the received slice-related radio link failure information and / or configuration information associated with a slice-related handover, or it may be forwarded by the handover source node to other nodes for the other nodes to make related self-optimization decisions and / or perform self-optimization and / or update configuration.

[0303]

[0304] Figure 5 illustrates a schematic diagram of an aspect of a method for supporting slice optimization according to embodiments of the disclosure. Specifically, Figure 5 illustrates a process of exchanging a request and / or configuration for slice-related successful handover information between two nodes. The sixth node may generate slice-related successful handover information based on the received request and / or configuration for slice-related successful handover information, and / or forward it to other nodes.

[0305] In some implementations, for example, the fifth node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB, and the sixth node may be a UE. In other implementations, for example, the fifth node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB, and the sixth node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In yet other implementations, for example, the fifth node may be an AMF or SMF or MME, and the sixth node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB. In yet other implementations, for example, the fifth node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB, and the sixth node may be an AMF or SMF or MME.

[0306] Step 501A: the fifth node transmits a request and / or configuration for slice-related successful handover information to the sixth node. The request and / or configuration for slice-related successful handover information may be the aforementioned third message.

[0307] Step 502A: the sixth node may generate slice-related successful handover information based on the received request and / or configuration for slice-related successful handover information, and / or forward it to other nodes.

[0308]

[0309] Figure 6a illustrates a schematic diagram of an aspect of a method for supporting slice optimization according to embodiments of the disclosure. Specifically, Figure 6a illustrates a process of exchanging slice-related successful handover information between two nodes. The eighth node may make self-optimization strategies and / or perform self-optimization based on the slice-related successful handover information, or may forward it to other nodes for the other nodes to make self-optimization strategies and / or perform self-optimization.

[0310] In some implementations, for example, the seventh node may be a UE and the eighth node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In other implementations, for example, the seventh node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB, and the eighth node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In yet other implementations, for example, the seventh node may be an AMF or SMF or MME, and the eighth node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB. In yet other implementations, for example, the seventh node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB, and the eighth node may be an AMF or SMF or MME.

[0311] Step 601A: the seventh node transmits information about that slice-related successful handover information is available to the eighth node. The information about that slice-related successful handover information is available may be the aforementioned fourth message.

[0312] Step 602A: the eighth node transmits information of a request for slice-related successful handover information to the seventh node. The request for slice-related successful handover information may be the aforementioned fifth message.

[0313] Step 603A: the seventh node transmits slice-related successful handover information to the eighth node. The slice-related successful handover information may be the aforementioned sixth message.

[0314] Step 604A: the eighth node may make self-optimization strategies and / or perform self-optimization, or may forward the information to other nodes for the other nodes to make self-optimization strategies and / or perform self-optimization. For example, if the eighth node is the target node of the handover, the eighth node may forward the slice-related successful handover information to the source node of the handover, for the handover source node to make self-optimization strategies and / or perform self-optimization.

[0315]

[0316] Figure 6b illustrates a schematic diagram of an aspect of a method for supporting slice optimization according to embodiments of the disclosure. Specifically, Figure 6b illustrates a process of exchanging slice-related successful handover information between two nodes. The eighth node may make self-optimization strategies and / or perform self-optimization based on the slice-related successful handover information, or may forward it to other nodes for the other nodes to make self-optimization strategies and / or perform self-optimization.

[0317] In some implementations, for example, the seventh node may be a UE and the eighth node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In other implementations, for example, the seventh node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB, and the eighth node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In yet other implementations, for example, the seventh node may be an AMF or SMF or MME, and the eighth node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB. In yet other implementations, for example, the seventh node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB, and the eighth node may be an AMF or SMF or MME.

[0318] Step 601B: the eighth node transmits information of a request for slice-related successful handover information to the seventh node. The request for slice-related successful handover information may be the aforementioned fifth message.

[0319] Step 602B: the seventh node transmits slice-related successful handover information to the eighth node. The slice-related successful handover information may be the aforementioned sixth message.

[0320] Step 603B: the eighth node may make self-optimization strategies and / or perform self-optimization, or may forward the information to other nodes for the other nodes to make self-optimization strategies and / or perform self-optimization. For example, if the eighth node is the target node of the handover, the eighth node may forward the slice-related successful handover information to the source node of the handover, for the handover source node to make self-optimization strategies and / or perform self-optimization.

[0321]

[0322] Figure 6c illustrates a schematic diagram of an aspect of a method for supporting slice optimization according to embodiments of the disclosure. Specifically, Figure 6c illustrates a process of exchanging slice-related successful handover information between two nodes. The eighth node may make self-optimization strategies and / or perform self-optimization based on the slice-related successful handover information, or may forward it to other nodes for the other nodes to make self-optimization strategies and / or perform self-optimization.

[0323] In some implementations, for example, the seventh node may be a UE and the eighth node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In other implementations, for example, the seventh node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB, and the eighth node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In yet other implementations, for example, the seventh node may be an AMF or SMF or MME, and the eighth node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB. In yet other implementations, for example, the seventh node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB, and the eighth node may be an AMF or SMF or MME.

[0324] Step 601C: the seventh node transmits slice-related successful handover information to the eighth node. The slice-related successful handover information may be the aforementioned sixth message.

[0325] Step 602C: the eighth node may make self-optimization strategies and / or perform self-optimization, or may forward the information to other nodes for the other nodes to make self-optimization strategies and / or perform self-optimization. For example, if the eighth node is the target node of the handover, the eighth node may forward the slice-related successful handover information to the source node of the handover, for the handover source node to make self-optimization strategies and / or perform self-optimization.

[0326]

[0327] Figure 6d illustrates a schematic diagram of an aspect of a method for supporting slice optimization according to embodiments of the disclosure. Specifically, Figure 6d illustrates a process of exchanging slice-related successful handover information between a UE, a target node, and a source node. The source node may make self-optimization strategies and / or perform self-optimization based on the slice-related successful handover information, or may forward it to other nodes for the other nodes to make self-optimization strategies and / or perform self-optimization.

[0328] Step 601D: the source node transmits a request and / or configuration for slice-related successful handover information to the UE. The request and / or configuration for slice-related successful handover information may be the aforementioned third message. The request and / or configuration for slice-related successful handover information may be carried by an RRCReconfiguration message.

[0329] Step 602D: a handover procedure in which the UE is handed over to the target cell is performed.

[0330] Step 603D: the UE transmits information about that slice-related successful handover information is available to the target node. The information about that slice-related successful handover information is available may be the aforementioned fourth message. The information about that slice-related successful handover information is available may be carried by an RRCReconfigurationComplete message.

[0331] Step 604D: the target node transmits information of a request for slice-related successful handover information to the UE. The request for slice-related successful handover information may be the aforementioned fifth message. The request for slice-related successful handover information may be carried by a UEInformationRequest message.

[0332] Step 605D: the UE transmits slice-related successful handover information to the target node. The slice-related successful handover information may be the aforementioned sixth message. The slice-related successful handover information may be carried by a UEInformationResponse message. To distinguish it from step 606D and the like, the message carrying or including slice-related successful handover information in step 605D may also be called an eighth message and the like. More generally, it should be understood that any message names or sequence numbers of messages herein are merely used as examples or distinctions, and they may also have any other name or sequence number. For example, in different scenarios, steps and / or operations, a first message may also be referred to as a second message, and so on.

[0333] Step 606D: the target node transmits slice-related successful handover information to the source node. The slice-related successful handover information may be the aforementioned sixth message. The slice-related successful handover information may be carried by a FAILURE INDICATION message or a HANDOVER REPORT message or an ACCESS AND MOBILITY INDICATION message.

[0334] Step 607D: the source node may make self-optimization strategies and / or perform self-optimization.

[0335]

[0336] Figure 7a illustrates a schematic diagram of an aspect of a method for supporting slice optimization according to embodiments of the disclosure. Specifically, Figure 7a illustrates a process of exchanging information related to a request and / or trigger for reporting of user history information between two nodes, in which, after obtaining the information related to the request and / or trigger for reporting of user history information, a tenth node reports user history information to a ninth node. After obtaining the user history information, the ninth node may make self-optimization strategies and / or perform self-optimization and / or forward it to other nodes.

[0337] In some implementations, for example, the ninth node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB, and the tenth node may be a UE. In other implementations, for example, the ninth node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB, and the tenth node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In yet other implementations, for example, the ninth node may be an AMF or SMF or MME, and the tenth node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB. In yet other implementations, for example, the ninth node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB, and the tenth node may be an AMF or SMF or MME.

[0338] Step 701A: the ninth node transmits information related to a request and / or trigger for reporting of user history information to the tenth node. The information related to a request and / or trigger for reporting of user history information may be the aforementioned seventh message.

[0339] Step 702A: the tenth node transmits user history information to the ninth node. The user history information may include an identification list of cells which the UE was previously and / or currently connected to and / or camped on, and / or a list of corresponding camping times.

[0340] Step 703A: the ninth node may make self-optimization strategies and / or perform self-optimization based on the user history information, or may forward it to other nodes for the other nodes to make self-optimization strategies and / or perform self-optimization.

[0341]

[0342] Figure 7b illustrates a schematic diagram of an aspect of a method for supporting slice optimization according to embodiments of the disclosure. Specifically, Figure 7b illustrates a process of exchanging user history information between a source node and a target node. Based on the user history information, the source node may make self-optimization strategies and / or perform self-optimization, and / or forward it to other nodes.

[0343] Step 701B: the target node transmits user history information to the source node. The user history information may include an identification list of cells which the UE was previously and / or currently connected to and / or camped on, and / or a list of corresponding camping times. In some implementations, for example, the target node may transmit the user history information to the source node according to its own situation or according to a configuration, for example, a configuration configured by the OAM to the target node. In some implementations, for example, the OAM configures the target node with that, if the camping time of the UE on the target node is less than and / or equal to a threshold, the target node transmits the user history information to the source node.

[0344] Step 702B: the source node may make self-optimization strategies and / or perform self-optimization based on the user history information, or may forward it to other nodes for the other nodes to make self-optimization strategies and / or perform self-optimization.

[0345]

[0346] Figure 7c illustrates a schematic diagram of an aspect of a method for supporting slice optimization according to embodiments of the disclosure. Specifically, Figure 7c illustrates a process of exchanging user history information between a source node and a target node. Based on the user history information, the source node may make self-optimization strategies and / or perform self-optimization, and / or forward it to other nodes.

[0347] Step 701C: optionally, the source node transmits information related to a request and / or trigger for reporting of user history information to the target node. The information related to a request and / or trigger for reporting of user history information may be the aforementioned seventh message. In some implementations, for example, the information related to a request and / or trigger for reporting of user history information may be carried by a HANDOVER REQUEST message.

[0348] Step 702C: the source node transmits an RRC reconfiguration message to the UE.

[0349] Step 703C: the UE transmits an RRC reconfiguration complete message to the source node.

[0350] Step 704C: the UE accesses the target node.

[0351] Step 705C: the target node transmits user history information to the source node. The user history information may include an identification list of cells which the UE was previously and / or currently connected to and / or camped on, and / or a list of corresponding camping times. The user history information may be carried by a FAILURE INDICATION message or a HANDOVER REPORT message or an ACCESS AND MOBILITY INDICATION message.

[0352] Step 706C: the source node may make self-optimization strategies and / or perform self-optimization based on the user history information, or may forward it to other nodes for the other nodes to make self-optimization strategies and / or perform self-optimization.

[0353]

[0354] Figure 7d illustrates a schematic diagram of an aspect of a method for supporting slice optimization according to embodiments of the disclosure. Specifically, Figure 7d illustrates a process of exchanging user history information between a secondary node and a master node. The secondary node may make self-optimization strategies and / or perform self-optimization based on the user history information, and / or forward it to other nodes.

[0355] Step 701D: optionally, the secondary node transmits information related to a request and / or trigger for reporting of user history information to the master node. The information related to a request and / or trigger for reporting of user history information may be the aforementioned seventh message. In some implementations, for example, the information related to a request and / or trigger for reporting of user history information may be carried by a S-NODE CHANGE REQUIRED message.

[0356] Step 702D: the secondary node or master node transmits an RRC reconfiguration message to the UE.

[0357] Step 703D: the UE transmits an RRC reconfiguration complete message to the secondary node or master node.

[0358] Step 704D: the UE accesses the target secondary node.

[0359] Step 705D: the master node transmits user history information to the secondary node. The user history information may include an identification list of (secondary primary) cells which the UE was previously and / or currently connected to and / or camped on, and / or a list of corresponding camping times. The user history information may be carried by a SgNB Modification Request message or a SCG Failure Information Report message or a FAILURE INDICATION message or a HANDOVER REPORT message or an ACCESS AND MOBILITY INDICATION message.

[0360] Step 706D: the secondary node may make self-optimization strategies and / or perform self-optimization based on the user history information, or may forward it to other nodes for the other nodes to make self-optimization strategies and / or perform self-optimization.

[0361]

[0362] Figure 7e illustrates a schematic diagram of an aspect of a method for supporting slice optimization according to embodiments of the disclosure. Specifically, Figure 7e illustrates a process of exchanging user history information between a secondary node and a master node. The secondary node may make self-optimization strategies and / or perform self-optimization based on the user history information, and / or forward it to other nodes.

[0363] Step 701E: optionally, the master node transmits information related to a request and / or trigger for reporting of user history information to the secondary node. The information related to a request and / or trigger for reporting of user history information may be the aforementioned seventh message. In some implementations, for example, the information related to a request and / or trigger for reporting of user history information may be carried by a S-NODE ADDITION REQUEST message.

[0364] Step 702E: the secondary node or master node transmits an RRC reconfiguration message to the UE.

[0365] Step 703E: the UE transmits an RRC reconfiguration complete message to the secondary node or master node.

[0366] Step 704E: the UE accesses the secondary node.

[0367] Step 705E: the secondary node transmits user history information to the master node. The user history information may include an identification list of (secondary primary) cells which the UE was previously and / or currently connected to and / or camped on, and / or a list of corresponding camping times. The user history information may be carried by an RRC TRANSFER message or a FAILURE INDICATION message or a HANDOVER REPORT message or an ACCESS AND MOBILITY INDICATION message. The radio link failure information may be included in a Radio Link Failure (RLF) report.

[0368] Step 706E: the master node may make self-optimization strategies and / or perform self-optimization based on the user history information, or may forward it to other nodes for the other nodes to make self-optimization strategies and / or perform self-optimization.

[0369]

[0370] Figure 7f illustrates a schematic diagram of an aspect of a method for supporting slice optimization according to embodiments of the disclosure. Specifically, Figure 7f illustrates a process of exchanging user history information between a source secondary node, a source master node, a target master node, or a target secondary node. Based on the user history information, the source secondary node may make self-optimization strategies and / or perform self-optimization, and / or forward to other nodes.

[0371] Step 701F: optionally, the source secondary node transmits information related to a request and / or trigger for reporting of user history information to the source master node. The information related to a request and / or trigger for reporting of user history information may be the aforementioned seventh message. In some implementations, for example, the information related to a request and / or trigger for reporting of user history information may be carried by a S-NODE CHANGE REQUIRED message.

[0372] Step 702F: optionally, the source master node transmits information related to a request and / or trigger for reporting of user history information to the target master node or target secondary node. The information related to a request and / or trigger for reporting of user history information may be the aforementioned seventh message. In some implementations, for example, the information related to a request and / or trigger for reporting of user history information may be carried by a HANDOVER REQUEST message. In some implementations, for example, the information related to a request and / or trigger for reporting of user history information may be carried by a S-NODE ADDITION REQUEST message.

[0373] Step 703F: the source secondary node or source master node transmits an RRC reconfiguration message to the UE.

[0374] Step 704F: the UE transmits an RRC reconfiguration complete message to the source secondary node or source master node.

[0375] Step 705F: the UE accesses the target master node or target secondary node.

[0376] Step 706F: the target master node or target secondary node transmits user history information to the master node. The user history information may include an identification list of (secondary primary) cells which the UE was previously and / or currently connected to and / or camped on, and / or a list of corresponding camping times. The user history information may be carried by an RRC TRANSFER message or a FAILURE INDICATION message or a HANDOVER REPORT message or an ACCESS AND MOBILITY INDICATION message.

[0377] Step 707F: the source master node transmits user history information to the source secondary node. The user history information may include an identification list of (secondary primary) cells which the UE was previously and / or currently connected to and / or camped on, and / or a list of corresponding camping times. The user history information may be carried by a SgNB Modification Request message or a SCG Failure Information Report message or a FAILURE INDICATION message or a HANDOVER REPORT message or an ACCESS AND MOBILITY INDICATION message.

[0378] Step 708F: the source secondary node may make self-optimization strategies and / or perform self-optimization based on the user history information, or may forward it to other nodes for the other nodes to make self-optimization strategies and / or perform self-optimization.

[0379] It should be understood that, depending on the application scenario, the various example aspects, methods, steps, processes, etc. shown above in conjunction with the drawings can be combined and implemented in any manner, and are not limited herein.

[0380]

[0381] Figure 8 illustrates a flowchart of a method 800 performed by a first node in a wireless communication system according to embodiments of the disclosure.

[0382] The method 800 performed by the first node in the wireless communication system according to embodiments of the disclosure may include: in step S801, transmitting a third message to a user equipment (UE), wherein the third message includes first information for configuring reporting of slice-related successful handover information; in step S802, receiving a sixth message from a second node, wherein the sixth message includes the slice-related successful handover information; and in step S803, performing self-optimization based on the sixth message. In some implementations, the first information includes information related to at least one of: slice replacement occurs, a service requirement of the UE cannot be met, a service of the UE is interrupted, a threshold of an interruption time of a user plane related to the UE, a threshold of a time interval between a next handover and a current handover of the UE, a threshold of a camping time of the UE.

[0383] According to embodiments of the disclosure, the slice-related successful handover information includes information related to at least one of: information related to whether slice replacement occurs, identification and / or identification list of original slices related to slice replacement that occurred, identification and / or identification list of replacing slices related to slice replacement that occurred, whether a service requirement can be met on a target cell, identification and / or identification list of slices corresponding to PDU sessions or PDU session resources that do not meet a service requirement on the target cell, information related to whether service interruption occurs, and information related to an interrupted service.

[0384] According to embodiments of the disclosure, the slice-related successful handover information further includes information related to at least one of: identification and / or identification list of slices corresponding to protocol data unit (PDU) sessions or PDU session resources that meet a service requirement on the target cell, information and / or information list of PDU sessions or PDU session resources that meet a service requirement on the target cell, information and / or information list of PDU sessions or PDU session resources that do not meet a service requirement on the target cell, service parameters achieved on the target cell, a difference between a service parameter achieved on the target cell and a service requirement, a service requirement that needs to be achieved, identification and / or identification list of slices corresponding to PDU sessions or PDU session resources established on a target cell and / or accepted by a target cell, information and / or information list of PDU sessions or PDU session resources established on a target cell and / or accepted by a target cell, identification and / or identification list of slices corresponding to PDU sessions or PDU session resources that cannot be established on a target cell and / or are rejected by a target cell, information and / or information list of PDU sessions or PDU session resources that cannot be established on a target cell and / or are rejected by a target cell, execution conditions for a handover, execution conditions for a next handover, identification of a target cell for a next handover, and information related to whether the target cell of the next handover belongs to the configured handover candidate cells.

[0385] According to embodiments of the disclosure, the slice-related successful handover information is generated by the UE based on the first information and is transmitted by the UE to the second node.

[0386] According to embodiments of the disclosure, the method further includes: transmitting a second message to the second node, wherein the second message includes configuration information associated with a slice-related handover; receiving a first message from the second node, wherein the first message includes slice-related radio link failure information and / or configuration information associated with a slice-related handover; and performing self-optimization based on the first message.

[0387] According to embodiments of the disclosure, the configuration information associated with a slice-related handover includes information related to at least one of: identification and / or identification list of slices corresponding to PDU sessions or PDU session resources accepted by a candidate target cell, and identification and / or identification list of slices supported by and / or available for the candidate target cell.

[0388] According to embodiments of the disclosure, the configuration information associated with a slice-related handover further includes information related to at least one of: identification and / or identification list of candidate target cells, information and / or information list of PDU sessions or PDU session resources accepted by the candidate target cells, identification and / or identification list of slices corresponding to PDU sessions or PDU session resources rejected by the candidate target cells, information and / or information list of PDU sessions or PDU session resources rejected by the candidate target cells.

[0389] According to embodiments of the disclosure, the slice-related radio link failure information includes information related to at least one of: identification and / or identification list of slices supported by and / or available for a reconnect cell, identification and / or identification list of slices supported by and / or available for a target cell, identification and / or identification list of slices accessed on the reconnect cell, identification and / or identification list of slices accessed on a source cell, identification and / or identification list of slices accessed on the target cell, identification and / or identification list of slices corresponding to PDU sessions or PDU session resources that cannot be established on the reconnect cell and / or are rejected by the reconnect cell, identification and / or identification list of slices corresponding to PDU sessions or PDU session resources established on the source cell and / or accepted by the source cell, identification and / or identification list of slices corresponding to PDU sessions or PDU session resources established on the target cell and / or serving cell and / or accepted by the target cell and / or serving cell.

[0390] According to embodiments of the disclosure, the slice-related radio link failure information further includes information related to at least one of: identification and / or identification list of slices supported by and / or available for a source cell, identification and / or identification list of slices corresponding to protocol data unit (PDU) sessions or PDU session resources established on a reconnect cell and / or accepted by a reconnect cell, information and / or information list of PDU sessions or PDU session resources established on a reconnect cell and / or accepted by a reconnect cell, information and / or information list of PDU sessions or PDU session resources that cannot be established on the reconnect cell and / or are rejected by the reconnect cell, information and / or information list of PDU sessions or PDU session resources established on the source cell and / or accepted by the source cell, information and / or information list of PDU sessions or PDU session resources established on the target cell and / or serving cell and / or accepted by the target cell and / or serving cell, identification and / or identification list of slices corresponding to PDU sessions or PDU session resources that cannot be established on the target cell and / or serving cell and / or are rejected by the target cell and / or serving cell, information and / or information list of PDU sessions or PDU session resources that cannot be established on the target cell and / or serving cell and / or are rejected by the target cell and / or serving cell, identification and / or identification list of slices corresponding to PDU sessions or PDU session resources accepted by the target cell, identification and / or identification list of slices corresponding to PDU sessions or PDU session resources rejected by the target cell, information and / or information list of PDU sessions or PDU session resources rejected by the target cell, whether a service requirement can be met on the reconnect cell, identification and / or identification list of slices corresponding to PDU sessions or PDU session resources that meet a service requirement on the reconnect cell, information and / or information lists of PDU sessions or PDU session resources that meet a service requirement on the reconnect cell, identification and / or identification list of slices corresponding to PDU sessions or PDU session resources that do not meet a service requirement on the reconnect cell, information and / or information list of PDU sessions or PDU session resources that do not meet a service requirement on the reconnect cell, information related to whether slice replacement has occurred, identification and / or identification list of original slices related to slice replacement that occurred and / or or identification list, identification and / or identification list of replacing slices related to slice replacement that occurred, information related to whether a service is interrupted, information related to whether the UE supports slice replacement, identification and / or identification list of slices corresponding to PDU sessions or PDU session resources accepted by the target cell, information and / or information list of PDU sessions or PDU session resources accepted by the target cell, identification and / or identification list of slices corresponding to PDU sessions or PDU session resources rejected by the target cell, and information and / or information list of PDU sessions or PDU session resources rejected by the target cell.

[0391] According to embodiments of the disclosure, the method further includes: transmitting a seventh message to the second node, wherein the seventh message includes information related to a trigger condition for reporting of user history information; and receiving the user history information from the second node, wherein the information related to the trigger condition includes at least one of: a threshold of a time interval between a next handover and a current handover of the UE, and a threshold of a camping time of the UE.

[0392]

[0393] Figure 9 illustrates a flowchart of a method 900 performed by a user equipment (UE) in a wireless communication system according to embodiments of the disclosure.

[0394] The method 900 performed by a user equipment (UE) in a wireless communication system according to embodiments of the disclosure may include: in step S901, receiving a third message from a first node, wherein the third message includes first information for configuring reporting of slice-related successful handover information; and in step S902, transmitting an eighth message to a second node, wherein the eighth message includes the slice-related successful handover information, wherein the eighth message is used for the first node and / or the second node to perform self-optimization. In some implementations, the first information includes information related to at least one of: slice replacement occurs, a service requirement of the UE cannot be met, a service of the UE is interrupted, a threshold of an interruption time of a user plane related to the UE, a threshold of a time interval between a next handover and a current handover of the UE, a threshold of a camping time of the UE.

[0395] According to embodiments of the disclosure, the slice-related successful handover information includes information related to at least one of: information related to whether slice replacement occurs, identification and / or identification list of original slices related to slice replacement that occurred, identification and / or identification list of replacing slices related to slice replacement that occurred, whether a service requirement can be met on a target cell, identification and / or identification list of slices corresponding to PDU sessions or PDU session resources that do not meet a service requirement on the target cell, information related to whether service interruption occurs, and information related to an interrupted service.

[0396] According to embodiments of the disclosure, the slice-related successful handover information further includes information related to at least one of: identification and / or identification list of slices corresponding to protocol data unit (PDU) sessions or PDU session resources that meet a service requirement on the target cell, information and / or information list of PDU sessions or PDU session resources that meet a service requirement on the target cell, information and / or information list of PDU sessions or PDU session resources that do not meet a service requirement on the target cell, service parameters achieved on the target cell, a difference between a service parameter achieved on the target cell and a service requirement, a service requirement that needs to be achieved, identification and / or identification list of slices corresponding to PDU sessions or PDU session resources established on a target cell and / or accepted by a target cell, information and / or information list of PDU sessions or PDU session resources established on a target cell and / or accepted by a target cell, identification and / or identification list of slices corresponding to PDU sessions or PDU session resources that cannot be established on a target cell and / or are rejected by a target cell, information and / or information list of PDU sessions or PDU session resources that cannot be established on a target cell and / or are rejected by a target cell, execution conditions for a handover, execution conditions for a next handover, identification of a target cell for a next handover, and information related to whether the target cell of the next handover belongs to the configured handover candidate cells.

[0397] According to embodiments of the disclosure, the method further includes: generating the slice-related successful handover information based on the first information, wherein the slice-related successful handover information is further transmitted by the second node to the first node.

[0398] According to embodiments of the disclosure, the method further includes: transmitting a first message to the second node through a reconnect node, wherein the first message includes slice-related radio link failure information.

[0399] According to embodiments of the disclosure, the slice-related radio link failure information includes information related to at least one of: identification and / or identification list of slices supported by and / or available for a reconnect cell, identification and / or identification list of slices supported by and / or available for a target cell, identification and / or identification list of slices accessed on the reconnect cell, identification and / or identification list of slices accessed on a source cell, identification and / or identification list of slices accessed on the target cell, identification and / or identification list of slices corresponding to PDU sessions or PDU session resources that cannot be established on the reconnect cell and / or are rejected by the reconnect cell, identification and / or identification list of slices corresponding to PDU sessions or PDU session resources established on the source cell and / or accepted by the source cell, identification and / or identification list of slices corresponding to PDU sessions or PDU session resources established on the target cell and / or serving cell and / or accepted by the target cell and / or serving cell.

[0400] According to embodiments of the disclosure, the slice-related radio link failure information further includes information related to at least one of: identification and / or identification list of slices supported by and / or available for a source cell, identification and / or identification list of slices corresponding to protocol data unit (PDU) sessions or PDU session resources established on a reconnect cell and / or accepted by a reconnect cell, information and / or information list of PDU sessions or PDU session resources established on a reconnect cell and / or accepted by a reconnect cell, information and / or information list of PDU sessions or PDU session resources that cannot be established on the reconnect cell and / or are rejected by the reconnect cell, information and / or information list of PDU sessions or PDU session resources established on the source cell and / or accepted by the source cell, information and / or information list of PDU sessions or PDU session resources established on the target cell and / or serving cell and / or accepted by the target cell and / or serving cell, identification and / or identification list of slices corresponding to PDU sessions or PDU session resources that cannot be established on the target cell and / or serving cell and / or are rejected by the target cell and / or serving cell, information and / or information list of PDU sessions or PDU session resources that cannot be established on the target cell and / or serving cell and / or are rejected by the target cell and / or serving cell, identification and / or identification list of slices corresponding to PDU sessions or PDU session resources accepted by the target cell, identification and / or identification list of slices corresponding to PDU sessions or PDU session resources rejected by the target cell, information and / or information list of PDU sessions or PDU session resources rejected by the target cell, whether a service requirement can be met on the reconnect cell, identification and / or identification list of slices corresponding to PDU sessions or PDU session resources that meet a service requirement on the reconnect cell, information and / or information lists of PDU sessions or PDU session resources that meet a service requirement on the reconnect cell, identification and / or identification list of slices corresponding to PDU sessions or PDU session resources that do not meet a service requirement on the reconnect cell, information and / or information list of PDU sessions or PDU session resources that do not meet a service requirement on the reconnect cell, information related to whether slice replacement has occurred, identification and / or identification list of original slices related to slice replacement that occurred and / or or identification list, identification and / or identification list of replacing slices related to slice replacement that occurred, information related to whether a service is interrupted, information related to whether the UE supports slice replacement, identification and / or identification list of slices corresponding to PDU sessions or PDU session resources accepted by the target cell, information and / or information list of PDU sessions or PDU session resources accepted by the target cell, identification and / or identification list of slices corresponding to PDU sessions or PDU session resources rejected by the target cell, and information and / or information list of PDU sessions or PDU session resources rejected by the target cell.

[0401] It should be understood that methods 800 and 900, etc. according to embodiments of the disclosure may also include any method or step described in conjunction with various examples, aspects, drawings, etc. of the disclosure.

[0402]

[0403] Figure 10 illustrates a schematic diagram of a node 1000 according to embodiments of the disclosure.

[0404] As shown in Figure 10, a node (or node device, for example, the first node or the second node as described above, etc.) 1000 according to embodiments of the disclosure may include a transceiver 1010 and a processor 1020. The transceiver 1010 may be configured to transmit and receive signals. The processor 1020 may be coupled to transceiver 1010 and may be configured to (e.g., control the transceiver 1010 to) perform methods performed by any node according to embodiments of the disclosure.

[0405]

[0406] Figure 11 illustrates a schematic diagram of a user equipment (UE) 1100 according to embodiments of the disclosure.

[0407] As shown in Figure 11, a user equipment 1100 according to embodiments of the disclosure may include a transceiver 1110 and a processor 1120. The transceiver 1110 may be configured to transmit and receive signals. The processor 1120 may be coupled to transceiver 1110 and may be configured to (e.g., control the transceiver 1110 to) perform methods performed by a user equipment (UE) according to embodiments of the disclosure. In the disclosure, a processor may also be referred to as a controller.

[0408] Embodiments of the disclosure also provide a computer-readable medium having stored thereon computer-readable instructions which, when executed by a processor, implement any method according to embodiments of the disclosure.

[0409] Various embodiments of the disclosure may be implemented as computer-readable codes embodied on a computer-readable recording medium from a specific perspective. A computer-readable recording medium is any data storage device that can store data readable by a computer system. Examples of computer-readable recording media may include read-only memory (ROM), random access memory (RAM), compact disk read-only memory (CD-ROM), magnetic tape, floppy disk, optical data storage device, carrier wave (e.g., data transmission via the Internet), etc. Computer-readable recording media can be distributed by computer systems connected via a network, and thus computer-readable codes can be stored and executed in a distributed manner. Furthermore, functional programs, codes and code segments for implementing various embodiments of the disclosure can be easily explained by those skilled in the art to which the embodiments of the disclosure are applied.

[0410] It will be understood that the embodiments of the disclosure may be implemented in the form of hardware, software, or a combination of hardware and software. Although not illustrated in Figures 10 and 11, the software may be stored as program instructions or computer-readable codes executable on a processor on a non-transitory computer-readable medium. Examples of non-transitory computer-readable recording media include magnetic storage media (such as ROM, floppy disk, hard disk, etc.) and optical recording media (such as CD-ROM, digital video disk (DVD), etc.). Non-transitory computer-readable recording media may also be distributed on computer systems coupled to a network, so that computer-readable codes are stored and executed in a distributed manner. The medium can be read by a computer, stored in a memory, and executed by a processor. Various embodiments may be implemented by a computer or a portable terminal including a controller and a memory, and the memory may be an example of a non-transitory computer-readable recording medium suitable for storing program (s) with instructions for implementing embodiments of the disclosure. The disclosure may be realized by a program with code for concretely implementing the apparatus and method described in the claims, which is stored in a machine (or computer)-readable storage medium. The program may be electronically carried on any medium, such as a communication signal transmitted via a wired or wireless connection, and the disclosure suitably includes its equivalents.

[0411] What has been described above is only the specific implementation of the disclosure, but the scope of protection of the disclosure is not limited thereto. Anyone who is familiar with this technical field may make various changes or substitutions within the technical scope disclosed in the disclosure, and these changes or substitutions should be covered within the scope of protection of the disclosure. Therefore, the scope of protection of the disclosure should be based on the scope of protection of the claims.

Claims

A method performed by a source node in a wireless communication system, the method comprising:transmitting, to a terminal, configuration information on a first triggering condition for reporting of information on a successful handover, the information on the successful handover including slice-related information of the successful handover, and the slice-related information being associated with a service continuity for the terminal at a target node;receiving, from a terminal via the target node, the information on the successful handover; andperforming self-optimization based on the slice-related information.The method of claim 1,wherein the first triggering condition includes at least one of: slice replacement occurs, a service requirement of the terminal cannot be met, a service of the terminal is interrupted, a threshold of an interruption time of a user plane related to the terminal, a threshold of a time interval between a next handover and a current handover of the terminal, a threshold of a camping time of the terminal,wherein the slice-related information includes at least one of: information related to whether slice replacement occurs, identification and / or identification list of original slices related to slice replacement that occurred, identification and / or identification list of replacing slices related to slice replacement that occurred, whether a service requirement can be met on a target cell, identification and / or identification list of slices corresponding to PDU (protocol data unit) sessions or PDU session resources that do not meet a service requirement on the target cell, information related to whether service interruption occurs, and information related to an interrupted service,wherein the slice-related information is generated by the terminal based on the first triggering condition, andwherein the slice-related information is transmitted from the terminal to the target node.The method of claim 1, further comprising:transmitting, to the target node, configuration information associated with a slice-related handover;receiving, from the target node, slice-related radio link failure information associated with a radio link failure between the terminal and the target node after the successful handover; andperforming self-optimization based on the slice-related radio link failure information,wherein the slice-related radio link failure information is transmitted from the terminal to the target node via a reconnect node.The method of claim 3,wherein the configuration information associated with the slice-related handover includes information related to at least one of:identification and / or identification list of slices corresponding to PDU (protocol data unit) sessions or PDU session resources accepted by a candidate target cell, and identification and / or identification list of slices supported by and / or available for the candidate target cell, andwherein the slice-related radio link failure information includes information related to at least one of: identification and / or identification list of slices supported by and / or available for a reconnect cell, identification and / or identification list of slices supported by and / or available for a target cell, identification and / or identification list of slices accessed on the reconnect cell, identification and / or identification list of slices accessed on a source cell, identification and / or identification list of slices accessed on the target cell, identification and / or identification list of slices corresponding to PDU sessions or PDU session resources that cannot be established on the reconnect cell and / or are rejected by the reconnect cell, identification and / or identification list of slices corresponding to PDU sessions or PDU session resources established on the source cell and / or accepted by the source cell, identification and / or identification list of slices corresponding to PDU sessions or PDU session resources established on the target cell and / or serving cell and / or accepted by the target cell and / or serving cell.The method of claim 1, further comprising:transmitting, to the target node, configuration information on a second triggering condition for reporting of user history information;receiving, from the target node, the user history information; andperforming self-optimization based on the user history information,wherein the configuration information on the second triggering condition includes at least one of: information on a threshold of a time interval between a next handover and a current handover of the terminal, and information on a threshold of a camping time of the terminal.A method performed by a terminal in a wireless communication system, the method comprising:receiving, from a source node, configuration information on a triggering condition for reporting of information on a successful handover, the information on the successful handover including slice-related information of the successful handover, and the slice-related information being associated with a service continuity for the terminal at a target node;performing the successful handover from the source node to the target node; andtransmitting, to the target node, the information on the successful handover,wherein the slice-related information is transmitted from the target node to the source node, andwherein the slice-related information is used for self-optimization of the source node.The method of claim 6,wherein the triggering condition includes at least one of:slice replacement occurs, a service requirement of the terminal cannot be met, a service of the terminal is interrupted, a threshold of an interruption time of a user plane related to the terminal, a threshold of a time interval between a next handover and a current handover of the terminal, a threshold of a camping time of the terminal,wherein the slice-related information includes at least one of: information related to whether slice replacement occurs, identification and / or identification list of original slices related to slice replacement that occurred, identification and / or identification list of replacing slices related to slice replacement that occurred, whether a service requirement can be met on a target cell, identification and / or identification list of slices corresponding to PDU (protocol data unit) sessions or PDU session resources that do not meet a service requirement on the target cell, information related to whether service interruption occurs, and information related to an interrupted service, andwherein the slice-related information is generated based on the triggering condition.The method of claim 6, further comprising:identifying a radio link failure between the terminal and the target node after the successful handover; andtransmitting, to a reconnect node, slice-related radio link failure information,wherein the slice-related radio link failure information is transmitted from the reconnect node to the source node via the target node,wherein the slice-related radio link failure information is used for self-optimization of the source node, andwherein the slice-related radio link failure information includes information related to at least one of: identification and / or identification list of slices supported by and / or available for a reconnect cell, identification and / or identification list of slices supported by and / or available for a target cell, identification and / or identification list of slices accessed on the reconnect cell, identification and / or identification list of slices accessed on a source cell, identification and / or identification list of slices accessed on the target cell, identification and / or identification list of slices corresponding to PDU (protocol data unit) sessions or PDU session resources that cannot be established on the reconnect cell and / or are rejected by the reconnect cell, identification and / or identification list of slices corresponding to PDU sessions or PDU session resources established on the source cell and / or accepted by the source cell, identification and / or identification list of slices corresponding to PDU sessions or PDU session resources established on the target cell and / or serving cell and / or accepted by the target cell and / or serving cell.A source node in a wireless communication system, the source node comprising:a transceiver;a processor communicatively coupled to the transceiver; andmemory, communicatively coupled to the processor, storing instructions executable by the processor to cause the source node to:transmit, to a terminal, configuration information on a first triggering condition for reporting of information on a successful handover, the information on the successful handover including slice-related information of the successful handover, and the slice-related information being associated with a service continuity for the terminal at a target node,receive, from a terminal via the target node, the information on the successful handover, andperform self-optimization based on the slice-related information.The source node of claim 9,wherein the first triggering condition includes at least one of: slice replacement occurs, a service requirement of the terminal cannot be met, a service of the terminal is interrupted, a threshold of an interruption time of a user plane related to the terminal, a threshold of a time interval between a next handover and a current handover of the terminal, a threshold of a camping time of the terminal,wherein the slice-related information includes at least one of: information related to whether slice replacement occurs, identification and / or identification list of original slices related to slice replacement that occurred, identification and / or identification list of replacing slices related to slice replacement that occurred, whether a service requirement can be met on a target cell, identification and / or identification list of slices corresponding to PDU (protocol data unit) sessions or PDU session resources that do not meet a service requirement on the target cell, information related to whether service interruption occurs, and information related to an interrupted service,wherein the slice-related information is generated by the terminal based on the first triggering condition, andwherein the slice-related information is transmitted from the terminal to the target node.The source node of claim 9,wherein the instructions executable by the processor further cause the source node to:transmit, to the target node, configuration information associated with a slice-related handover,receive, from the target node, slice-related radio link failure information associated with a radio link failure between the terminal and the target node after the successful handover, andperform self-optimization based on the slice-related radio link failure information, andwherein the slice-related radio link failure information is transmitted from the terminal to the target node via a reconnect node,wherein the configuration information associated with the slice-related handover includes information related to at least one of: identification and / or identification list of slices corresponding to PDU (protocol data unit) sessions or PDU session resources accepted by a candidate target cell, and identification and / or identification list of slices supported by and / or available for the candidate target cell, andwherein the slice-related radio link failure information includes information related to at least one of: identification and / or identification list of slices supported by and / or available for a reconnect cell, identification and / or identification list of slices supported by and / or available for a target cell, identification and / or identification list of slices accessed on the reconnect cell, identification and / or identification list of slices accessed on a source cell, identification and / or identification list of slices accessed on the target cell, identification and / or identification list of slices corresponding to PDU sessions or PDU session resources that cannot be established on the reconnect cell and / or are rejected by the reconnect cell, identification and / or identification list of slices corresponding to PDU sessions or PDU session resources established on the source cell and / or accepted by the source cell, identification and / or identification list of slices corresponding to PDU sessions or PDU session resources established on the target cell and / or serving cell and / or accepted by the target cell and / or serving cell.The source node of claim 9,wherein the instructions executable by the processor further cause the source node to:transmit, to the target node, configuration information on a second triggering condition for reporting of user history information,receive, from the target node, the user history information, andperform self-optimization based on the user history information, andwherein the configuration information on the second triggering condition includes at least one of: information on a threshold of a time interval between a next handover and a current handover of the terminal, and information on a threshold of a camping time of the terminal.A terminal in a wireless communication system, the terminal comprising:a transceiver;a processor communicatively coupled to the transceiver; andmemory, communicatively coupled to the processor, storing instructions executable by the processor to cause the terminal to:receive, from a source node, configuration information on a triggering condition for reporting of information on a successful handover, the information on the successful handover including slice-related information of the successful handover, and the slice-related information being associated with a service continuity for the terminal at a target node,perform the successful handover from the source node to the target node, andtransmit, to the target node, the information on the successful handover,wherein the slice-related information is transmitted from the target node to the source node, andwherein the slice-related information is used for self-optimization of the source node.The terminal of claim 13,wherein the triggering condition includes at least one of: slice replacement occurs, a service requirement of the terminal cannot be met, a service of the terminal is interrupted, a threshold of an interruption time of a user plane related to the terminal, a threshold of a time interval between a next handover and a current handover of the terminal, a threshold of a camping time of the terminal,wherein the slice-related information includes at least one of: information related to whether slice replacement occurs, identification and / or identification list of original slices related to slice replacement that occurred, identification and / or identification list of replacing slices related to slice replacement that occurred, whether a service requirement can be met on a target cell, identification and / or identification list of slices corresponding to PDU (protocol data unit) sessions or PDU session resources that do not meet a service requirement on the target cell, information related to whether service interruption occurs, and information related to an interrupted service, andwherein the slice-related information is generated based on the triggering condition.The terminal of claim 13,wherein the instructions executable by the processor further cause the terminal to:identify a radio link failure between the terminal and the target node after the successful handover, andtransmit, to a reconnect node, slice-related radio link failure information,wherein the slice-related radio link failure information is transmitted from the reconnect node to the source node via the target node,wherein the slice-related radio link failure information is used for self-optimization of the source node, andwherein the slice-related radio link failure information includes information related to at least one of: identification and / or identification list of slices supported by and / or available for a reconnect cell, identification and / or identification list of slices supported by and / or available for a target cell, identification and / or identification list of slices accessed on the reconnect cell, identification and / or identification list of slices accessed on a source cell, identification and / or identification list of slices accessed on the target cell, identification and / or identification list of slices corresponding to PDU (protocol data unit) sessions or PDU session resources that cannot be established on the reconnect cell and / or are rejected by the reconnect cell, identification and / or identification list of slices corresponding to PDU sessions or PDU session resources established on the source cell and / or accepted by the source cell, identification and / or identification list of slices corresponding to PDU sessions or PDU session resources established on the target cell and / or serving cell and / or accepted by the target cell and / or serving cell.

Images