Node in wireless communication system, user equipment and method performed by same

Abstract

The invention provides a node in a wireless communication system, user equipment and a method performed by the same. A method performed by a first node in a wireless communication system comprises: receiving a second message from a user equipment (UE) or a third node, the second message comprising predicted slice information of the UE; selecting a target node based on the predicted slice information; sending a seventeenth message to the target node, wherein the seventeenth message comprises information of a quality of experience parameter associated with the UE; and receiving an eighteenth message from the target node, the eighteenth message comprising a slice remapping decision associated with the UE and / or an applicable time of the slice remapping decision.

Description

Technical Field

[0001] The present disclosure relates to the technical field of wireless communications, and more particularly, to a node, a user equipment and a method executed by the node in a wireless communication system. Background Art

[0002] In order to meet the increased demand for wireless data communication services since the deployment of 4G communication systems, efforts have been made to develop improved 5G or quasi-5G communication systems. Therefore, 5G or quasi-5G communication systems are also referred to as "super 4G networks" or "post-LTE systems."

[0003] Wireless communication is one of the most successful innovations in modern history. The number of subscribers to wireless communication services recently exceeded 5 billion and continues to grow rapidly. The demand for wireless data services is growing rapidly due to the increasing popularity of smartphones and other mobile data devices (e.g., tablets, laptops, netbooks, e-book readers, and machine-type devices) among consumers and enterprises. In order to meet the high growth of mobile data services and support new applications and deployments, it is critical to improve the efficiency and coverage of the wireless interface. Summary of the invention

[0004] An embodiment of the present disclosure provides a method performed by a first node in a wireless communication system, comprising: receiving a second message from a user equipment UE or a third node, the second message including predicted slice information of the UE; selecting a target node based on the predicted slice information; sending a seventeenth message to the target node, the seventeenth message including information on experience quality parameters associated with the UE; and receiving an eighteenth message from the target node, the eighteenth message including a slice remapping decision associated with the UE and / or the applicable time of the slice remapping decision.

[0005] According to an embodiment of the present disclosure, the method also includes: sending a first message to the UE or a third node, the first message including a request for the predicted slice information, wherein the second message is sent by the UE or the third node based on the first message.

[0006] According to an embodiment of the present disclosure, the seventeenth message also includes the predicted slice information and / or slice performance request related information, wherein the slice performance request related information is used to trigger the target node to collect slice performance, and wherein the predicted slice information is used for slice-related switching decision making.

[0007] According to an embodiment of the present disclosure, the method also includes: sending a nineteenth message to the UE, the nineteenth message including first information about the target node's support for the slice.

[0008] According to an embodiment of the present disclosure, the first information includes priority information of the target node, wherein the priority information is determined based on the number of predicted slices included in the predicted slice information that the target node can support.

[0009] According to an embodiment of the present disclosure, the method also includes: receiving a seventh message from the target node, the seventh message including information about slice-related performance acquired by the target node.

[0010] According to an embodiment of the present disclosure, the method also includes: receiving a measurement report from the UE, the measurement report including one or more of the following: a reference signal received power RSRP measurement report, a reference signal received quality RSRQ measurement report, and a signal to interference plus noise ratio SINR measurement report.

[0011] An embodiment of the present disclosure provides a method performed by a user equipment UE in a wireless communication system, comprising: sending a second message to a first node, the second message including predicted slice information of the UE; and receiving a nineteenth message from the first node, wherein the predicted slice information is used by the first node to select a target node; wherein information on experience quality parameters associated with the UE is included in a seventeenth message, and the seventeenth message is sent from the first node to the target node; and wherein a slice remapping decision associated with the UE and / or the applicable time of the slice remapping decision is included in an eighteenth message, and the eighteenth message is sent from the target node to the first node.

[0012] According to an embodiment of the present disclosure, the nineteenth message includes first information about the target node's support for the slice.

[0013] According to an embodiment of the present disclosure, the first information includes priority information of the target node, wherein the priority information is determined based on the number of predicted slices included in the predicted slice information that the target node can support.

[0014] According to an embodiment of the present disclosure, the method also includes: sending a measurement report to the first node, the measurement report including one or more of the following: a reference signal received power RSRP measurement report, a reference signal received quality RSRQ measurement report, and a signal to interference plus noise ratio SINR measurement report.

[0015] According to an embodiment of the present disclosure, the method also includes: receiving a first message from the first node, the first message including a request for the predicted slice information, and sending the second message to the first node based on the first message.

[0016] According to an embodiment of the present disclosure, the seventeenth message also includes the predicted slice information and / or slice performance request related information, wherein the slice performance request related information is used to trigger the target node to collect slice performance, and wherein the predicted slice information is used for slice-related switching decision making.

[0017] An embodiment of the present disclosure provides a method performed by a second node in a wireless communication system, comprising: receiving a seventeenth message from a first node, the seventeenth message including information on experience quality parameters associated with a user equipment UE; and sending an eighteenth message to the first node, the eighteenth message including a slice remapping decision associated with the UE and / or the applicable time of the slice remapping decision.

[0018] According to an embodiment of the present disclosure, the seventeenth message also includes predicted slice information and / or slice performance request related information of the UE, wherein the slice performance request related information is used to trigger the second node to collect slice performance.

[0019] According to an embodiment of the present disclosure, the method also includes: sending a seventh message to the first node, and the seventh message includes information about the slice-related performance obtained by the second node.

[0020] According to an embodiment of the present disclosure, the method also includes: receiving a fifth message from a third node, the fifth message including slice load information obtained by the third node.

[0021] According to an embodiment of the present disclosure, the method further includes: determining a slice remapping decision associated with the UE and / or an applicable time of the slice remapping decision based on the quality of experience parameter and / or the slice load information.

[0022] According to an embodiment of the present disclosure, the method also includes: receiving an eighth message and / or a ninth message from a third node, wherein the eighth message includes information indicating that the predicted slice load is too large, and the ninth message includes information indicating the amount of load that the second node can receive.

[0023] An embodiment of the present disclosure provides a first node device in a wireless communication system, comprising: a transceiver configured to send and receive signals; and a processor coupled to the transceiver and configured to execute a method performed by the first node in the wireless communication system according to an embodiment of the present disclosure.

[0024] An embodiment of the present disclosure provides a second node device in a wireless communication system, comprising: a transceiver configured to send and receive signals; and a processor coupled to the transceiver and configured to execute a method performed by the second node in the wireless communication system according to an embodiment of the present disclosure.

[0025] An embodiment of the present disclosure provides a user equipment UE in a wireless communication system, comprising: a transceiver configured to send and receive signals; and a processor coupled to the transceiver and configured to execute a method performed by the user equipment UE in the wireless communication system according to an embodiment of the present disclosure.

[0026] An embodiment of the present disclosure provides a computer-readable medium having computer-readable instructions stored thereon, which, when executed by a processor, are used to implement a method performed by a first node and / or a second node and / or a user equipment in a wireless communication system according to an embodiment of the present disclosure.

[0027] The method provided by the present disclosure, which is performed by the first node and / or the second node and / or the user equipment in the wireless communication system, can effectively support the node and / or the user equipment to perform slice-related switching or decision-making by exchanging slice-related information between the nodes and / or the user equipment. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0029] Figure 1 is an exemplary system architecture 100 of System Architecture Evolution (SAE);

[0030] Figure 2 is an exemplary system architecture 200 according to various embodiments of the present disclosure;

[0031] Figures 3A-3H Schematic diagrams of one aspect of a method for supporting slicing according to an embodiment of the present disclosure are respectively shown;

[0032] Figures 4A-4C Schematic diagrams of one aspect of a method for supporting slicing according to an embodiment of the present disclosure are respectively shown;

[0033] Figures 5A-5E Schematic diagrams of one aspect of a method for supporting slicing according to an embodiment of the present disclosure are respectively shown;

[0034] Figure 6 A schematic diagram showing one aspect of a method for supporting slicing according to an embodiment of the present disclosure;

[0035] Figure 7 A schematic diagram showing one aspect of a method for supporting slicing according to an embodiment of the present disclosure;

[0036] Figure 8A schematic diagram showing one aspect of a method for supporting slicing according to an embodiment of the present disclosure;

[0037] Figures 9A-9B Schematic diagrams of one aspect of a method for supporting slicing according to an embodiment of the present disclosure are respectively shown;

[0038] Figures 10A-10B Schematic diagrams of one aspect of a method for supporting slicing according to an embodiment of the present disclosure are respectively shown;

[0039] Fig.11 A schematic diagram showing one aspect of a method for supporting slicing according to an embodiment of the present disclosure;

[0040] Figures 12A-12F Schematic diagrams of one aspect of a method for supporting slicing according to an embodiment of the present disclosure are respectively shown;

[0041] Fig.13 A flowchart of a method performed by a first node in a wireless communication system according to an embodiment of the present disclosure is shown;

[0042] Fig.14 A flow chart of a method performed by a user equipment in a wireless communication system according to an embodiment of the present disclosure is shown;

[0043] Fig.15 A flowchart of a method performed by a second node in a wireless communication system according to an embodiment of the present disclosure is shown;

[0044] Fig.16 A schematic diagram of a node according to an embodiment of the present disclosure is shown;

[0045] Fig.17 A schematic diagram showing a user equipment according to an embodiment of the present disclosure is shown;

[0046] Fig.18A A schematic diagram showing one aspect of a method for supporting slicing according to an embodiment of the present disclosure; and

[0047] Fig.19A A schematic diagram showing one aspect of a method for supporting slicing according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0048] The following description with reference to the accompanying drawings is provided to facilitate a comprehensive understanding of the various embodiments of the present disclosure as defined by the claims and their equivalents. This description includes various specific details to facilitate understanding but should be considered as exemplary only. Therefore, one of ordinary skill in the art will recognize that various changes and modifications can be made to the various embodiments described herein without departing from the scope and spirit of the present disclosure. In addition, for the sake of clarity and conciseness, descriptions of well-known functions and structures may be omitted.

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

[0050] It should 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.

[0051] The term "include" or "may include" refers to the presence of the corresponding disclosed functions, operations or components that can be used in various embodiments of the present disclosure, rather than limiting the presence of one or more additional functions, operations or features. In addition, the term "include" or "have" may be interpreted as indicating certain characteristics, numbers, steps, operations, constituent elements, components or combinations thereof, but should not be interpreted as excluding the possibility of the presence of one or more other characteristics, numbers, steps, operations, constituent elements, components or combinations thereof.

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

[0053] Unless defined differently, all terms (including technical terms or scientific terms) used in the present disclosure have the same meanings as understood by those skilled in the art described in the present disclosure. Common terms as defined in dictionaries are interpreted as having meanings consistent with the context in the relevant technical field, and should not be interpreted ideally or overly formally unless clearly defined in the present disclosure.

[0054] The accompanying drawings discussed below and the various embodiments used to describe the principles of the present disclosure in this patent document are for illustration only and should not be interpreted in any way as limiting the scope of the present disclosure. Those skilled in the art will appreciate that the principles of the present disclosure can be implemented in any suitably arranged system or device.

[0055] Figure 1 It is an exemplary system architecture 100 of System Architecture Evolution (SAE). User Equipment (UE) 101 is a terminal device used to receive data. Evolved Universal Terrestrial Radio Access Network (E-UTRAN) 102 is a radio access network, which includes a macro base station (eNodeB / NodeB) that provides a wireless network interface for the UE to access. The Mobility Management Entity (MME) 103 is responsible for managing the mobility context, session context and security information of the UE. The Serving Gateway (SGW) 104 mainly provides user plane functions, and the MME 103 and SGW 104 may be in the same physical entity. The Packet Data Network Gateway (PGW) 105 is responsible for functions such as billing and lawful interception, and may also be in the same physical entity as the SGW 104. The Policy and Charging Rules Function Entity (PCRF) 106 provides Quality of Service (QoS) policies and charging criteria. The General Packet Radio Service Support Node (SGSN) 108 is a network node device that provides routing for data transmission in the Universal Mobile Telecommunications System (UMTS). The Home Subscriber Server (HSS) 109 is the home subsystem of the UE and is responsible for protecting user information including the current location of the user equipment, the address of the service node, user security information, and the packet data context of the user equipment.

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

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

[0058] The nodes described in the present disclosure may include: gNB, gNB Central Unit (gNB-CU), gNB Distributed Unit (gNB-DU), gNB-CU-ControlPlane (gNB CU-CP)), gNB-CU-User Plane (gNB CU-UP)), en-gNB, eNB, ng-eNB, UE, Access and Mobility Management Function (Access and Mobility Management Function (AMF)), Session Management Function (Session Management Function (SMF)), Mobility Management Entity (MobilityManagement Entity (MME)), User Plane Function (User Plane Function (UPF)) and other network entities or network logical units and the cells and / or beams managed by them.

[0059] The fields described in the present disclosure may be the average value, instantaneous value, maximum value, minimum value, etc. of the corresponding parameter, which is not limited in the present disclosure.

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

[0061] In the present disclosure, a slice identifier may be identified by one or more single network slice selection assistance information (S-NSSAI).

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

[0063] In the present disclosure, self-organizing network (SON) related reports and / or self-optimization network (SON) related reports may include one or more of the following: connection establishment failure (CEF) report, or random access (Random Access) report, or successful handover (Successful Handover) report, or radio link failure (RLF) report, or measurement report, or other reports related to wireless connection.

[0064] In the present disclosure, radio link failure includes two situations: radio link failure and handover failure.

[0065] In the present disclosure, user equipment (UE) may be referred to as user, terminal, etc.

[0066] In the present disclosure, load, load condition, load information, etc. may refer to resource status (Resource Status) interchangeably.

[0067] When selecting a target node, the base station selects a node that supports user slicing as the target node. This process may have at least one of the following problems:

[0068] 1. If the user's service changes, the accessed slice needs to be changed, but the service node does not support the target slice, and the managed slices cannot guarantee the needs of the new service, the base station needs to switch the user, which may cause frequent switching problems only due to the slice.

[0069] 2. If the target node does not support user slices, slice remapping is required, and user access to the remapped slice may result in the inability to guarantee the quality of user experience.

[0070] 3. After switching, when the slice is overloaded, the target base station needs to switch the user to other nodes, which may cause frequent switching problems.

[0071] Example 1

[0072] An embodiment of the present disclosure proposes a method for supporting slicing, which may include: a second node sends a first message containing a predicted slice information request (i.e., a request for predicted slice information) to a first node to request the first node to report the requested predicted slice information. The second node may allocate resources based on the predicted slice information obtained from the first node. In some embodiments, for example, resources may be reserved for the predicted slice so that when the accessed slice needs to be changed, the slice to be accessed has sufficient resources to support access and / or guarantee transmission performance, so as to avoid the need to switch the UE and / or the UE needs to reselect a cell due to insufficient slice resources, resulting in service interruption. Alternatively, the second node may select a target node for switching based on the predicted slice information obtained from the first node. In some embodiments, for example, a node that supports the predicted slice may be selected as the target node to ensure the stability and robustness of the switching, and to prevent the UE from needing to reselect a serving cell when the switched target node cannot support a certain slice, resulting in service interruption, etc.

[0073] In some embodiments, the first message may be included in one or more of the following: a resource status request (RESOURCE STATUS REQUEST) message or a resource status response (RESOURCE STATUS RESPONSE) message or a resource status failure (RESOURCE STATUS FAILURE) message or a resource status update (RESOURCE STATUS UPDATE) message or a handover request confirmation (HANDOVER REQUEST ACKNOWLEDGE) message or a handover request (HANDOVERREQUEST) message or an NG-RAN node configuration update (NG-RAN NODE CONFIGURATION UPDATE) message or an NG-RAN node configuration update confirmation (NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE) message or an Xn setup request (XN SETUP REQUEST) message or an Xn setup response (XN SETUP RESPONSE) message of NG; an NG setup request (NG SETUP REQUEST) message or an NG setup response (NG SETUP RESPONSE) message or a RAN configuration update (RANCONFIGURATION UPDATE) message of NG. UPDATE) message or RAN Configuration Update Acknowledge (RAN CONFIGURATION UPDATE ACKNOWLEDGE) message or AMF Configuration Update (AMF CONFIGURATION UPDATE) message or AMF Configuration Update Acknowledge (AMF CONFIGURATION UPDATE ACKNOWLEDGE) message or AMF Status Indication (AMF STATUS INDICATION) message or Overload Start (OVERLOAD START) message or Overload Stop (OVERLOAD STOP) message or Handover Required (HANDOVER REQUIRED) message or Handover Command (HANDOVER COMMAND) message or Handover Request (HANDOVER REQUEST) message or Handover Request Acknowledge (HANDOVER REQUEST ACKNOWLEDGE) message or Uplink RAN ​​Configuration Transfer (UPLINK RAN CONFIGURATION TRANSFER) message or Downlink RAN ​​Configuration Transfer (DOWNLINK RAN CONFIGURATION TRANSFER) message;or F1 SETUP REQUEST message or F1 SETUP RESPONSE message or gNB-DU CONFIGURATION UPDATE message or gNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message or gNB-CU CONFIGURATION UPDATE message or gNB-CUCONFIGURATION UPDATE ACKNOWLEDGE message or gNB-DU STATUSINDICATION message or RESOURCE STATUS REQUEST message or RESOURCE STATUS RESPONSE message or RESOURCE STATUS FAILURE message or RESOURCE STATUS UPDATE message UE CONTEXT SETUP REQUEST message or RESOURCE STATUS RESPONSE message or RESOURCE STATUS FAILURE message or RESOURCE STATUS UPDATE message UE CONTEXT SETUP REQUEST) message or UE CONTEXT SETUP RESPONSE message or UE CONTEXT RELEASE REQUEST message or UE CONTEXT RELEASE COMMAND message or UE CONTEXT RELEASE COMPLETE message or UE CONTEXT MODIFICATION REQUEST message or UE CONTEXT MODIFICATION RESPONSE message or UE CONTEXT MODIFICATION REQUIRED message or UE CONTEXT MODIFICATION CONFIRM message;or gNB CU UP E1 SETUP REQUEST message of E1 or gNB CU UP E1 SETUP RESPONSE message or gNB CU CP E1 SETUP REQUEST message or gNB CU CP E1 SETUP RESPONSE message or gNB CUUP CONFIGURATION UPDATE message or gNB CU UP CONFIGURATION UPDATE ACKNOWLEDGE message or gNB CU CP CONFIGURATION UPDATE ACKNOWLEDGE message or gNB CU UP status indication (GNB-CU-UP STATUS INDICATION) message or Resource status request (RESOURCE STATUS REQUEST) message or Resource status response (RESOURCE STATUSRESPONSE) message or Resource status failure (RESOURCE STATUS FAILURE) message or Resource status update (RESOURCE STATUS UPDATE) message Bearer context setup request (BEARER CONTEXT SETUP REQUEST) message or Bearer context setup response (BEARER CONTEXT SETUP RESPONSE) message or Bearer context modification request (BEARER CONTEXT MODIFICATION REQUEST) message or Bearer context modification response (BEARERCONTEXTMODIFICATION RESPONSE) message or Bearer context modification required (BEARERCONTEXTMODIFICATION REQUIRED) message or BearerCONTEXTMODIFICATIONCONFIRM message or BearerCONTEXTRELEASECOMMAND message or BearerCONTEXTRELEASECOMMAND message CONTEXT RELEASE COMPLETE) message or bearer context release request (BEARERCONTEXT RELEASE REQUEST) message;or RRC reconfiguration (RRCReconfiguration) message or RRC recovery (RRCResume) message or RRC reconstruction (RRCReestablishment) message or RRC establishment (RRCSetup) message or RRC reconfiguration complete (RRCReconfigurationComplete) message or RRC recovery complete (RRCResumeComplete) message or RRC reconstruction complete (RRCReestablishmentComplete) message or RRC establishment complete (RRCSetupComplete) message; it can also be sent in the form of a medium access control (MAC) control element (CE); or another and / or newly defined RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message and / or RRC container, etc. In some embodiments, the first message may include one or more of the following fields or related information:;

[0074] UE ID: indicates the user corresponding to the requested predicted slice information. It can be a UE ID or a UE ID list.

[0075] Sending node ID: used to identify the node that sends the message.

[0076] Receiving node ID: used to identify the node that receives the message.

[0077] · Request prediction slice information flag: used to indicate request prediction slice information. This field can be represented by a single bit, for example, when the bit is 1, it indicates request prediction slice information, and when the bit is 0, it indicates no request prediction slice information; or, when the bit is 0, it indicates request prediction slice information, and when the bit is 1, it indicates no request prediction slice information.

[0078] Prediction registration request: used to indicate the type of prediction request, for example, it can include start, end, add, update, etc.

[0079] Registration Request: used to indicate the type of request, for example, it can include start, end, add, update, etc.

[0080] ·Registration request reporting: used to indicate the type of reporting request, for example, it may include start, end, add, update, etc.

[0081] Request prediction time: used to indicate the predicted time point and / or time interval. The time can be relative or absolute. The time interval can be represented by a timer, a combination of the start time and the end time, a combination of the start time and the time interval, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits represent the predicted start time, and the last n bits represent the predicted end time. It can also be represented by a separate field, including one or more of the following:

[0082] o Prediction start time: used to indicate the prediction start time. The start time can be a relative time or an absolute time.

[0083] o Prediction end time: used to indicate the end time of the prediction. The end time can be a relative time or an absolute time.

[0084] · Request for prediction content applicable time: used to indicate the time point and / or time interval corresponding to the prediction content. The time can be relative time or absolute time. The time interval can be indicated by a timer, a combination of a start time and an end time, a combination of a start time and a time interval, etc. If it is a time interval, it can be indicated by 2*n bits, for example, the first n bits indicate the start time, and the last n bits indicate the end time. It can also be indicated by a separate field, including one or more of the following:

[0085] o Start time: used to indicate the start time of the applicable time. The start time can be a relative time or an absolute time.

[0086] ο End time: used to indicate the end time of the applicable time. The end time can be a relative time or an absolute time.

[0087] Prediction request information: Request information for predicting slice information. It may include one or more of the following:

[0088] οNumber of slices: The number of slices corresponding to the requested predicted slice information.

[0089] o Slice identifier and / or identifier list: the range of slices for which predicted slice information is requested. For example, the slice corresponding to the predicted and / or reported predicted slice information should be one or more of the slice identifiers and / or slice lists.

[0090] οNumber of cells: The number of cells corresponding to the requested predicted slice information.

[0091] ο Number of switches: The number of switches corresponding to the requested predicted slice information.

[0092] οCell identifier and / or identifier list: the cell identifier and / or identifier list of the slice for which prediction slice information is requested.

[0093] οNumber of nodes: The number of nodes corresponding to the requested predicted slice information.

[0094] οNode identifier and / or identifier list: the node identifier and / or identifier list of the slice for which the predicted switching information is requested.

[0095] Request prediction content reporting time: used to indicate the time point and / or time interval for prediction content reporting. The time can be relative or absolute. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a time interval, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits represent the start time, and the last n bits represent the end time. It can also be represented by a separate field, including one or more of the following:

[0096] o Start time: used to indicate the start time of the reporting time. The start time can be a relative time or an absolute time.

[0097] End time: used to indicate the end time of the reporting time. The end time can be a relative time or an absolute time.

[0098] Prediction content reporting method: used to indicate the requested content reporting method, which can include single reporting, periodic reporting, on-demand reporting, event-triggered reporting, etc.

[0099] Prediction content reporting period: used to indicate the interval time for periodic reporting of the prediction content. In some embodiments, the reporting period may also be the prediction time for the reported data. In some embodiments, for example, if there is no content in this field, it means that a single report is sufficient, and the single reporting time is from the prediction start time to the end time.

[0100] Events and / or conditions that trigger reporting: indicates that when the events and / or conditions that trigger reporting are met, the predicted slice information needs to be reported. The events and / or conditions that trigger reporting include one or more of the following:

[0101] o Predicted slice information change: When the predicted slice information changes, a report is triggered. The change can be addition, reduction, update, etc.

[0102] ο Prediction slice information generation: When the prediction slice information is generated, it is reported.

[0103] οPrediction information meets prediction request information: When the prediction information meets the above prediction request information, it is reported.

[0104] o The number of slices corresponding to the predicted slice information reaches a predetermined threshold value: the event and / or condition triggering the report may include one or more of the following: an event, an event type, a predetermined threshold value, etc.

[0105] o Predicted slice information exceeds and / or is not in the predetermined slice identifier and / or identifier list: When the predicted slice information exceeds and / or is not in the predetermined slice identifier and / or identifier list, report. The event and / or condition triggering the report may include one or more of the following: event, event type, predetermined slice identifier and / or identifier list, etc.

[0106] οThe number of cells corresponding to the predicted slice information reaches a predetermined threshold value: the event and / or condition triggering the report may include one or more of the following: event, event type, predetermined threshold value, etc.

[0107] οThe number of switching times corresponding to the predicted slice information reaches a predetermined threshold value: the event and / or condition triggering the report may include one or more of the following: event, event type, predetermined threshold value, etc.

[0108] o The cell corresponding to the predicted slice information exceeds and / or is not in the predetermined cell identifier and / or identifier list: When the cell corresponding to the predicted slice information exceeds and / or is not in the predetermined cell identifier and / or identifier list, report. The event and / or condition triggering the report may include one or more of the following: event, event type, predetermined cell identifier and / or identifier list, etc.

[0109] οThe number of nodes corresponding to the predicted slice information reaches a predetermined threshold value: the event and / or condition triggering the report may include one or more of the following: event, event type, predetermined threshold value, etc.

[0110] o The node corresponding to the predicted slice information exceeds and / or is not in the predetermined node identifier and / or identifier list: when the node corresponding to the predicted slice information exceeds and / or is not in the predetermined node identifier and / or identifier list, report. The event and / or condition triggering the report may include one or more of the following: event, event type, predetermined node identifier and / or identifier list, etc.

[0111] The current serving cell does not support the predicted slice information

[0112] o The time difference between the applicable time of the predicted slice information and the current time is greater than and / or less than and / or equal to a predetermined threshold value: the event and / or condition triggering the report may include one or more of the following: event, event type, predetermined threshold value, event satisfaction time, etc. Among them, the event satisfaction time may also be referred to as hysteresis. In some embodiments, when the time to satisfy the event reaches the event satisfaction time, the report is made.

[0113] o Reaching a predetermined time: starting from the receipt of the message, when the timing reaches a predetermined time, reporting is performed. The event and / or condition triggering the report may include one or more of the following: event, event type, predetermined time, etc.

[0114] · Requested predicted slice information: The requested predicted slice information may include one or more of the following: predicted slice identifier, residence time corresponding to the predicted slice, access time corresponding to the predicted slice, departure time corresponding to the predicted slice, access probability, departure probability, priority, prediction precision and / or accuracy, etc.

[0115] In some embodiments, the first node sends a second message containing predicted slice information to the second node according to its own situation and / or according to the first message containing predicted slice information request received from the second node. In some embodiments, for example, the second node can select the target node for switching based on the predicted slice information obtained from the first node. In some embodiments, for example, a node that supports more predicted slices can be selected as the target node to ensure the stability and robustness of the switching, and to prevent the UE from needing to reselect a service cell when the switched target node cannot support a certain slice, resulting in service interruption, etc. In another embodiment, for example, the second node can allocate resources based on the predicted slice information obtained from the first node, for example, reserve resources for the slices in the predicted slice information to avoid the inability to provide services normally due to a shortage of slice resources after the slice is changed.

[0116] In some embodiments, the second message may be included in one or more of the following: a resource status request (RESOURCE STATUS REQUEST) message or a resource status response (RESOURCE STATUS RESPONSE) message or a resource status failure (RESOURCE STATUS FAILURE) message or a resource status update (RESOURCE STATUS UPDATE) message or a handover request confirmation (HANDOVER REQUEST ACKNOWLEDGE) message or a handover request (HANDOVERREQUEST) message or an NG-RAN node configuration update (NG-RAN NODE CONFIGURATION UPDATE) message or an NG-RAN node configuration update confirmation (NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE) message or an Xn setup request (XN SETUP REQUEST) message or an Xn setup response (XN SETUP RESPONSE) message of NG; an NG setup request (NG SETUP REQUEST) message or an NG setup response (NG SETUP RESPONSE) message or a RAN configuration update (RANCONFIGURATION UPDATE) message of NG. UPDATE) message or RAN Configuration Update Acknowledge (RAN CONFIGURATION UPDATE ACKNOWLEDGE) message or AMF Configuration Update (AMF CONFIGURATION UPDATE) message or AMF Configuration Update Acknowledge (AMF CONFIGURATION UPDATE ACKNOWLEDGE) message or AMF Status Indication (AMF STATUS INDICATION) message or Overload Start (OVERLOAD START) message or Overload Stop (OVERLOAD STOP) message or Handover Required (HANDOVER REQUIRED) message or Handover Command (HANDOVER COMMAND) message or Handover Request (HANDOVER REQUEST) message or Handover Request Acknowledge (HANDOVER REQUEST ACKNOWLEDGE) message or Uplink RAN ​​Configuration Transfer (UPLINK RAN CONFIGURATION TRANSFER) message or Downlink RAN ​​Configuration Transfer (DOWNLINK RAN CONFIGURATION TRANSFER) message;or F1 SETUP REQUEST message or F1 SETUP RESPONSE message or gNB-DU CONFIGURATION UPDATE message or gNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message or gNB-CU CONFIGURATION UPDATE message or gNB-CUCONFIGURATION UPDATE ACKNOWLEDGE message or gNB-DU STATUSINDICATION message or RESOURCE STATUS REQUEST message or RESOURCE STATUS RESPONSE message or RESOURCE STATUS FAILURE message or RESOURCE STATUS UPDATE message UE CONTEXT SETUP REQUEST message or RESOURCE STATUS RESPONSE message or RESOURCE STATUS FAILURE message or RESOURCE STATUS UPDATE message UE CONTEXT SETUP REQUEST) message or UE CONTEXT SETUP RESPONSE message or UE CONTEXT RELEASE REQUEST message or UE CONTEXT RELEASE COMMAND message or UE CONTEXT RELEASE COMPLETE message or UE CONTEXT MODIFICATION REQUEST message or UE CONTEXT MODIFICATION RESPONSE message or UE CONTEXT MODIFICATION REQUIRED message or UE CONTEXT MODIFICATION CONFIRM message;or gNB CU UP E1 SETUP REQUEST message of E1 or gNB CU UP E1 SETUP RESPONSE message or gNB CU CP E1 SETUP REQUEST message or gNB CU CP E1 SETUP RESPONSE message or gNB CUUP CONFIGURATION UPDATE message or gNB CU UP CONFIGURATION UPDATE ACKNOWLEDGE message or gNB CU CP CONFIGURATION UPDATE ACKNOWLEDGE message or gNB CU UP status indication (GNB-CU-UP STATUS INDICATION) message or Resource status request (RESOURCE STATUS REQUEST) message or Resource status response (RESOURCE STATUSRESPONSE) message or Resource status failure (RESOURCE STATUS FAILURE) message or Resource status update (RESOURCE STATUS UPDATE) message Bearer context setup request (BEARER CONTEXT SETUP REQUEST) message or Bearer context setup response (BEARER CONTEXT SETUP RESPONSE) message or Bearer context modification request (BEARER CONTEXT MODIFICATION REQUEST) message or Bearer context modification response (BEARERCONTEXTMODIFICATION RESPONSE) message or Bearer context modification required (BEARERCONTEXTMODIFICATION REQUIRED) message or BearerCONTEXTMODIFICATIONCONFIRM message or BearerCONTEXTRELEASECOMMAND message or BearerCONTEXTRELEASECOMMAND message CONTEXT RELEASE COMPLETE) message or bearer context release request (BEARERCONTEXT RELEASE REQUEST) message;or RRC reconfiguration (RRCReconfiguration) message or RRC recovery (RRCResume) message or RRC reconstruction (RRCReestablishment) message or RRC establishment (RRCSetup) message or RRC reconfiguration complete (RRCReconfigurationComplete) message or RRC recovery complete (RRCResumeComplete) message or RRC reconstruction complete (RRCReestablishmentComplete) message or RRC establishment complete (RRCSetupComplete) message; it can also be sent in the form of MAC CE; or another and / or newly defined RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message and / or RRC container, etc.;

[0117] In some implementations, the second message may include one or more of the following fields or related information:

[0118] UE ID: indicates the user corresponding to the predicted slice information. It can be a UE ID or a UE ID list.

[0119] Sending node ID: used to identify the node that sends the message.

[0120] Receiving node ID: used to identify the node that receives the message.

[0121] Predicted slice information: used to indicate predicted slice information. The predicted slice information may include one or more of the following: predicted slice identifier, predicted residence time corresponding to the slice, predicted access time corresponding to the slice, predicted departure time corresponding to the slice, access probability, departure probability, priority, prediction precision and / or accuracy, etc.

[0122] Applicable time corresponding to the predicted slice information: used to indicate the time point and / or time interval corresponding to the predicted content. The time can be relative time or absolute time. The time interval can be represented by a timer, a combination of the start time and the end time, a combination of the start time and the time interval, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits represent the start time, and the last n bits represent the end time. It can also be represented by a separate field, including one or more of the following:

[0123] o Start time: used to indicate the start time of the applicable time. The start time can be a relative time or an absolute time.

[0124] ο End time: used to indicate the end time of the applicable time. The end time can be a relative time or an absolute time.

[0125] Events and / or conditions that trigger the report: Indicates the events and / or conditions that trigger the report. The events and / or conditions that trigger the report include one or more of the following:

[0126] o Predicted slice information change: When the predicted slice information changes, a report is triggered. The change can be addition, reduction, update, etc.

[0127] ο Prediction slice information generation: When the prediction slice information is generated, it is reported.

[0128] οPrediction information meets prediction request information: When the prediction information meets the above prediction request information, it is reported.

[0129] o The number of slices corresponding to the predicted slice information reaches a predetermined threshold value.

[0130] o The predicted slice information exceeds and / or is not in the predetermined slice identifier and / or identifier list

[0131] The number of cells corresponding to the predicted slice information reaches a predetermined threshold value.

[0132] The number of switching times corresponding to the predicted slice information reaches a predetermined threshold value.

[0133] o The cell corresponding to the predicted slice information exceeds and / or is not in the predetermined cell identifier and / or identifier list

[0134] The number of nodes corresponding to the predicted slice information reaches a predetermined threshold value

[0135] o The node corresponding to the predicted slice information exceeds and / or is not in the predetermined node identifier and / or identifier list

[0136] The current serving cell does not support the predicted slice information

[0137] The time difference between the applicable time of the predicted slice information and the current time is greater than and / or less than and / or equal to a predetermined threshold value.

[0138] o Reaching a preset time: starting from the time the message is received, reporting is performed when the time reaches a preset time.

[0139] Example 2

[0141] The embodiment of the present disclosure proposes a method for supporting slicing, which may include: a third node sends a third message containing a slice load condition request to a fourth node to request the fourth node to report the slice load condition (or slice load information). The slice load condition may include a measured slice load condition, and may also include a predicted slice load condition. After the third node obtains the slice load condition of the fourth node and / or other nodes, it may make relevant decisions based on the slice load condition of the fourth node and / or other nodes, such as SON-related decisions, to avoid frequent switching, local overload, overload, impaired service performance, etc. For example, when the node on the access network side makes a decision on load balancing and / or network energy saving and / or slice remapping, the overall load condition of the slice should be considered, so the access network side node can obtain the overall load condition of the slice from the core network side node to make a decision on load balancing and / or network energy saving and / or slice remapping. The third node may also evaluate the decision made based on the slice load condition of the fourth node and / or other nodes. In some embodiments, for example, when a local overload phenomenon occurs after the decision is made, it means that the decision made is inappropriate.

[0142] In some embodiments, the third message may be included in one or more of the following: a resource status request (RESOURCE STATUS REQUEST) message or a resource status response (RESOURCE STATUS RESPONSE) message or a resource status failure (RESOURCE STATUS FAILURE) message or a resource status update (RESOURCE STATUS UPDATE) message or a handover request confirmation (HANDOVER REQUEST ACKNOWLEDGE) message or a handover request (HANDOVERREQUEST) message or an NG-RAN node configuration update (NG-RAN NODE CONFIGURATION UPDATE) message or an NG-RAN node configuration update confirmation (NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE) message or an Xn setup request (XN SETUP REQUEST) message or an Xn setup response (XN SETUP RESPONSE) message of NG; an NG setup request (NG SETUP REQUEST) message or an NG setup response (NG SETUP RESPONSE) message or a RAN configuration update (RANCONFIGURATION UPDATE) message of NG. UPDATE) message or RAN Configuration Update Acknowledge (RAN CONFIGURATION UPDATE ACKNOWLEDGE) message or AMF Configuration Update (AMF CONFIGURATION UPDATE) message or AMF Configuration Update Acknowledge (AMF CONFIGURATION UPDATE ACKNOWLEDGE) message or AMF Status Indication (AMF STATUS INDICATION) message or Overload Start (OVERLOAD START) message or Overload Stop (OVERLOAD STOP) message or Handover Required (HANDOVER REQUIRED) message or Handover Command (HANDOVER COMMAND) message or Handover Request (HANDOVER REQUEST) message or Handover Request Acknowledge (HANDOVER REQUEST ACKNOWLEDGE) message or Uplink RAN ​​Configuration Transfer (UPLINK RAN CONFIGURATION TRANSFER) message or Downlink RAN ​​Configuration Transfer (DOWNLINK RAN CONFIGURATION TRANSFER) message;or F1 SETUP REQUEST message or F1 SETUP RESPONSE message or gNB-DU CONFIGURATION UPDATE message or gNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message or gNB-CU CONFIGURATION UPDATE message or gNB-CUCONFIGURATION UPDATE ACKNOWLEDGE message or gNB-DU STATUSINDICATION message or RESOURCE STATUS REQUEST message or RESOURCE STATUS RESPONSE message or RESOURCE STATUS FAILURE message or RESOURCE STATUS UPDATE message UE CONTEXT SETUP REQUEST message or RESOURCE STATUS RESPONSE message or RESOURCE STATUS FAILURE message or RESOURCE STATUS UPDATE message UE CONTEXT SETUP REQUEST) message or UE CONTEXT SETUP RESPONSE message or UE CONTEXT RELEASE REQUEST message or UE CONTEXT RELEASE COMMAND message or UE CONTEXT RELEASE COMPLETE message or UE CONTEXT MODIFICATION REQUEST message or UE CONTEXT MODIFICATION RESPONSE message or UE CONTEXT MODIFICATION REQUIRED message or UE CONTEXT MODIFICATION CONFIRM message;or gNB CU UP E1 SETUP REQUEST message of E1 or gNB CU UP E1 SETUP RESPONSE message or gNB CU CP E1 SETUP REQUEST message or gNB CU CP E1 SETUP RESPONSE message or gNB CUUP CONFIGURATION UPDATE message or gNB CU UP CONFIGURATION UPDATE ACKNOWLEDGE message or gNB CU CP CONFIGURATION UPDATE ACKNOWLEDGE message or gNB CU UP status indication (GNB-CU-UP STATUS INDICATION) message or Resource status request (RESOURCE STATUS REQUEST) message or Resource status response (RESOURCE STATUSRESPONSE) message or Resource status failure (RESOURCE STATUS FAILURE) message or Resource status update (RESOURCE STATUS UPDATE) message Bearer context setup request (BEARER CONTEXT SETUP REQUEST) message or Bearer context setup response (BEARER CONTEXT SETUP RESPONSE) message or Bearer context modification request (BEARER CONTEXT MODIFICATION REQUEST) message or Bearer context modification response (BEARERCONTEXTMODIFICATION RESPONSE) message or Bearer context modification required (BEARERCONTEXTMODIFICATION REQUIRED) message or BearerCONTEXTMODIFICATIONCONFIRM message or BearerCONTEXTRELEASECOMMAND message or BearerCONTEXTRELEASECOMMAND message CONTEXT RELEASE COMPLETE) message or bearer context release request (BEARERCONTEXT RELEASE REQUEST) message;or RRC reconfiguration (RRCReconfiguration) message or RRC recovery (RRCResume) message or RRC reconstruction (RRCReestablishment) message or RRC establishment (RRCSetup) message or RRC reconfiguration complete (RRCReconfigurationComplete) message or RRC recovery complete (RRCResumeComplete) message or RRC reconstruction complete (RRCReestablishmentComplete) message or RRC establishment complete (RRCSetupComplete) message; it can also be sent in the form of MAC CE; or another and / or newly defined RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message and / or RRC container, etc. In some embodiments, the third message may include one or more of the following fields or related information:;

[0143] Sending node ID: used to identify the node that sends the message.

[0144] Receiving node ID: used to identify the node that receives the message.

[0145] Measurement ID: used to identify the measurement.

[0146] Registration request: used to identify the type of request. It can include start, end, add, update, etc.

[0147] Slice load condition request identifier: used to indicate information about the requested slice load condition. The request may request a measured slice load condition or a predicted slice load condition.

[0148] · Scope of requested report: used to indicate the scope of requested report, where the scope may be one or more of the following identifiers and / or identifier lists: slice, service, scenario, node, UE, cell, beam, channel, protocol data unit session (Protocol Data Unit Session), data radio bearer (Data Radio Bearers, DRB), QoS flow, QoS level, etc. Identifiers and / or identifier lists, etc. The service may be a service type, quality of service (Quality of Service, QoS), scenario, etc. The service type may include one or more of the following: voice service, video service, virtual reality service, augmented reality service, call service, etc. The service quality may include one or more of the following: latency, throughput, reliability, packet loss rate, data rate, etc., which may be identified by a 5G service quality indicator (5G QoS Identifier, 5QI), a service quality level indicator (QoS Class Identifier, QCI), etc. The scenarios may include one or more of the following: Ultra-reliable and Low Latency Communications (URLLC), Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC), etc.

[0149] · Requested slice load situation reporting period: used to indicate the interval time for periodic reporting of the requested slice load situation. The reporting period can also be the reporting time of the reported data. In some implementations, for example, if there is no content in this field, it means that a single report is sufficient, and the single reporting time is from the start time to the end time of the report.

[0150] · Reporting method of requested slice load: used to indicate the reporting method of the requested slice load, which can include single reporting, periodic reporting, on-demand reporting, event-triggered reporting, etc.

[0151] Slice load reporting time: used to indicate the time point and / or time interval for reporting the slice load. The time can be a relative time or an absolute time. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a time interval, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits represent the start time, and the last n bits represent the end time. It can also be represented by a separate field, including one or more of the following:

[0152] o Start time: used to indicate the start time of the reporting time. The start time can be a relative time or an absolute time.

[0153] End time: used to indicate the end time of the reporting time. The end time can be a relative time or an absolute time.

[0154] Slice load measurement time: used to indicate the time point and / or time interval and / or measurement period of slice load measurement. The time can be relative or absolute. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a time interval, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits represent the start time, and the last n bits represent the end time. It can also be represented by a separate field, including one or more of the following:

[0155] oStart time: used to indicate the start time of the measurement time. The start time can be a relative time or an absolute time.

[0156] ο End time: used to indicate the end time of the measurement time. The end time can be a relative time or an absolute time.

[0157] Applicable time corresponding to the requested slice load condition: used to indicate the valid time point and / or time interval corresponding to the requested slice load condition. The time can be a relative time or an absolute time. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a time interval, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits represent the start time, and the last n bits represent the end time. It can also be represented by a separate field, including one or more of the following:

[0158] o Start time: used to indicate the start time of the applicable time. The start time can be a relative time or an absolute time.

[0159] ο End time: used to indicate the end time of the applicable time. The end time can be a relative time or an absolute time.

[0160] Prediction ID: used to identify this prediction request.

[0161] Slice load prediction request flag: used to indicate request for slice load prediction information.

[0162] · Scope of requested prediction: used to indicate the scope of requested prediction, where the scope may be one or more of the following identifiers and / or identifier lists: slice, service, scenario, node, UE, cell, beam, channel, protocol data unit session (Protocol Data Unit Session), data radio bearer (Data Radio Bearers, DRB), QoS flow, QoS level, etc. Identifiers and / or identifier lists, etc. The service may be a service type, quality of service (Quality of Service, QoS), scenario, etc. The service type may include one or more of the following: voice service, video service, virtual reality service, augmented reality service, call service, etc. The quality of service may include one or more of the following: latency, throughput, reliability, packet loss rate, data rate, etc., which may be identified by a 5G service quality indicator (5G QoS Identifier, 5QI), a service quality level indicator (QoS Class Identifier, QCI), etc. The scenarios may include one or more of the following: Ultra-reliable and Low Latency Communications (URLLC), Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC), etc.

[0163] · Requested predicted slice load situation reporting period: used to indicate the interval time for periodic reporting of the requested predicted slice load situation. In some implementations, the reporting period may also be the predicted time for the reported data. If there is no content in this field, it means that a single report is sufficient, and the single reporting time is the predicted start time to the end time.

[0164] · Requested predicted slice load reporting method: used to indicate the requested predicted slice load reporting method, which can include single reporting, periodic reporting, on-demand reporting, event-triggered reporting, etc.

[0165] Predicted slice load situation reporting time: used to indicate the time point and / or time interval for reporting the predicted slice load situation. The time can be a relative time or an absolute time. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a time interval, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits represent the start time, and the last n bits represent the end time. It can also be represented by a separate field, including one or more of the following:

[0166] o Start time: used to indicate the start time of the reporting time. The start time can be a relative time or an absolute time.

[0167] End time: used to indicate the end time of the reporting time. The end time can be a relative time or an absolute time.

[0168] Predicted slice load prediction time: used to indicate the predicted time point and / or time interval corresponding to the predicted slice load. The time can be a relative time or an absolute time. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a time interval, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits represent the start time, and the last n bits represent the end time. It can also be represented by a separate field, including one or more of the following:

[0169] o Start time: used to indicate the start time of the prediction time. The start time can be a relative time or an absolute time.

[0170] End time: used to indicate the end time of the forecast time. The end time can be a relative time or an absolute time.

[0171] Predicted slice load condition validity time: used to indicate the valid time point and / or time interval corresponding to the predicted slice load condition. The time can be a relative time or an absolute time. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a time interval, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits represent the start time, and the last n bits represent the end time. It can also be represented by a separate field, including one or more of the following:

[0172] oStart time: used to indicate the start time of the validity period. The start time can be a relative time or an absolute time.

[0173] ο End time: used to indicate the end time of the validity period. The end time can be a relative time or an absolute time.

[0174] Triggering conditions and / or events for reporting slice load conditions: indicates that when the triggering events and / or conditions for reporting are met, slice load information (or information related to the slice load conditions) needs to be reported. The slice load information includes the currently measured slice load information and may also include predicted slice load information. The events and / or conditions that trigger reporting include one or more of the following: the slice load is greater than and / or equal to and / or less than a predetermined threshold value, the slice load is predicted to be greater than and / or equal to and / or less than a predetermined threshold value, an overload is about to occur, and an overload is predicted to occur.

[0175] Slice load status requested to be reported: used to indicate the specific parameters of the slice load status requested to be reported. The load condition may include one or more of the following: the load condition and / or load information may include one or more of the following: physical resource block (PRB) usage ratio, the number of available PRBs, the number of allocated PRBs, scheduling physical downlink control channel (PDCCH) control channel element (CCE) usage, transport network layer (TNL) capacity indication, radio resource status, comprehensive available capacity group, comprehensive available resource group, number of active user terminals, number of radio resource control (RRC) connections, slice available capacity, hardware capacity indication, S1TNL load indication, hardware load indication, almost blank subframe (ABS) status, reference signal received power (RSRP) measurement report list, reference signal received quality (RSRQ) measurement report, signal to interference plus noise ratio (SINR) measurement report, channel state information (ChannelState The following information may be used for the analysis: Cell Signaling Information (CSI) report, cell report indication, channel occupancy time ratio, energy detection threshold, signal strength and / or signal quality, channel busy ratio, data volume, and jitter of various content parameters.

[0176] ·Indication of whether partial reporting is possible: used to indicate whether the message receiving node can perform partial reporting. That is, whether the message receiving node can report part of the requested information. If the indication is that partial reporting is possible, the message receiving node only needs to report part of the requested information. If the indication is that partial reporting is not possible, the message receiving node must report all the requested information. If one or more of the requested information cannot be reported, the message receiving node sends a request failure message to the message sending node. The information requested to be reported may include one or more of the slice load conditions requested to be reported above, or it may be one or more of the predicted ranges and / or requested reporting ranges requested above. This indication can allow the message receiving node to report part of the information according to its own situation, so as to avoid the message receiving node having to send a request failure message when it cannot report one or more of the requested information, resulting in a request failure, so that the message sending node needs to re-request. However, the message sending node does not know which messages the message receiving node can send, resulting in the message sending node having to keep trying to request, causing a signaling burden.

[0177] ·Indication of whether the requested information must be reported: used to indicate whether the requested information must be reported. If it is indicated that the information must be reported, the message receiving node must report the information and / or the load condition corresponding to the information. The information requested to be reported may include one or more of the slice load conditions requested to be reported above, or it may be one or more of the predicted ranges requested above and / or the ranges requested to be reported. The message receiving node can determine which parameters to report based on the indication and / or its own request.

[0178] ·Priority of requested reported information: used to indicate the priority of the information requested to be reported. In some embodiments, the message receiving node must report high priority information. The message receiving node may report and / or not report low priority information according to its own situation. The information requested to be reported may include one or more of the slice load conditions requested to be reported above, or it may be one or more of the predicted ranges requested above and / or the ranges requested to be reported. The message receiving node may determine which parameters to report based on the priority and its own request.

[0179] In some embodiments, the fourth node sends a fourth message including a slice load status response to the third node to inform the third node whether the fourth node can report the slice load status, so that the third node knows whether it can receive the requested report content later. In some embodiments, for example, if the fourth message received by the third node indicates that the fourth node can report the slice load status, the third node can subsequently receive the slice load status reported by the fourth node, for example, and can report it through a subsequent fifth message.

[0180] In some embodiments, the fourth message may be included in one or more of the following: a resource status request (RESOURCE STATUS REQUEST) message or a resource status response (RESOURCE STATUS RESPONSE) message or a resource status failure (RESOURCE STATUS FAILURE) message or a resource status update (RESOURCE STATUS UPDATE) message or a handover request confirmation (HANDOVER REQUEST ACKNOWLEDGE) message or a handover request (HANDOVERREQUEST) message or an NG-RAN node configuration update (NG-RAN NODE CONFIGURATION UPDATE) message or an NG-RAN node configuration update confirmation (NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE) message or an Xn setup request (XN SETUP REQUEST) message or an Xn setup response (XN SETUP RESPONSE) message of NG; an NG setup request (NG SETUP REQUEST) message or an NG setup response (NG SETUP RESPONSE) message or a RAN configuration update (RANCONFIGURATION UPDATE) message of NG. UPDATE) message or RAN Configuration Update Acknowledge (RAN CONFIGURATION UPDATE ACKNOWLEDGE) message or AMF Configuration Update (AMF CONFIGURATION UPDATE) message or AMF Configuration Update Acknowledge (AMF CONFIGURATION UPDATE ACKNOWLEDGE) message or AMF Status Indication (AMF STATUS INDICATION) message or Overload Start (OVERLOAD START) message or Overload Stop (OVERLOAD STOP) message or Handover Required (HANDOVER REQUIRED) message or Handover Command (HANDOVER COMMAND) message or Handover Request (HANDOVER REQUEST) message or Handover Request Acknowledge (HANDOVER REQUEST ACKNOWLEDGE) message or Uplink RAN ​​Configuration Transfer (UPLINK RAN CONFIGURATION TRANSFER) message or Downlink RAN ​​Configuration Transfer (DOWNLINK RAN CONFIGURATION TRANSFER) message;or F1 SETUP REQUEST message or F1 SETUP RESPONSE message or gNB-DU CONFIGURATION UPDATE message or gNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message or gNB-CU CONFIGURATION UPDATE message or gNB-CUCONFIGURATION UPDATE ACKNOWLEDGE message or gNB-DU STATUSINDICATION message or RESOURCE STATUS REQUEST message or RESOURCE STATUS RESPONSE message or RESOURCE STATUS FAILURE message or RESOURCE STATUS UPDATE message UE CONTEXT SETUP REQUEST message or RESOURCE STATUS RESPONSE message or RESOURCE STATUS FAILURE message or RESOURCE STATUS UPDATE message UE CONTEXT SETUP REQUEST) message or UE CONTEXT SETUP RESPONSE message or UE CONTEXT RELEASE REQUEST message or UE CONTEXT RELEASE COMMAND message or UE CONTEXT RELEASE COMPLETE message or UE CONTEXT MODIFICATION REQUEST message or UE CONTEXT MODIFICATION RESPONSE message or UE CONTEXT MODIFICATION REQUIRED message or UE CONTEXT MODIFICATION CONFIRM message;or gNB CU UP E1 SETUP REQUEST message of E1 or gNB CU UP E1 SETUP RESPONSE message or gNB CU CP E1 SETUP REQUEST message or gNB CU CP E1 SETUP RESPONSE message or gNB CUUP CONFIGURATION UPDATE message or gNB CU UP CONFIGURATION UPDATE ACKNOWLEDGE message or gNB CU CP CONFIGURATION UPDATE ACKNOWLEDGE message or gNB CU UP status indication (GNB-CU-UP STATUS INDICATION) message or Resource status request (RESOURCE STATUS REQUEST) message or Resource status response (RESOURCE STATUSRESPONSE) message or Resource status failure (RESOURCE STATUS FAILURE) message or Resource status update (RESOURCE STATUS UPDATE) message Bearer context setup request (BEARER CONTEXT SETUP REQUEST) message or Bearer context setup response (BEARER CONTEXT SETUP RESPONSE) message or Bearer context modification request (BEARER CONTEXT MODIFICATION REQUEST) message or Bearer context modification response (BEARERCONTEXTMODIFICATION RESPONSE) message or Bearer context modification required (BEARERCONTEXTMODIFICATION REQUIRED) message or BearerCONTEXTMODIFICATIONCONFIRM message or BearerCONTEXTRELEASECOMMAND message or BearerCONTEXTRELEASECOMMAND message CONTEXT RELEASE COMPLETE) message or bearer context release request (BEARERCONTEXT RELEASE REQUEST) message;or RRC reconfiguration (RRCReconfiguration) message or RRC recovery (RRCResume) message or RRC reconstruction (RRCReestablishment) message or RRC establishment (RRCSetup) message or RRC reconfiguration complete (RRCReconfigurationComplete) message or RRC recovery complete (RRCResumeComplete) message or RRC reconstruction complete (RRCReestablishmentComplete) message or RRC establishment complete (RRCSetupComplete) message; it can also be sent in the form of MAC CE; or another and / or newly defined RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message and / or RRC container, etc. In some embodiments, the fourth message may include one or more of the following fields or related information:;

[0181] Sending node ID: used to identify the node that sends the message.

[0182] Receiving node ID: used to identify the node that receives the message.

[0183] Measurement identifier: used to identify the measurement. In some implementations, for example, the measurement identifier may be consistent with the measurement identifier in the fourth message, and is used to associate the response message with the request message.

[0184] Slice load status request confirmation: used to indicate whether the slice load status can be measured and / or reported. The slice load status can be a bit indicating whether the request can be measured and / or reported.

[0185] Predicted slice load status confirmation: used to indicate whether the slice load status can be predicted and / or reported. The slice load status can be a bit indicating whether the request can be measured and / or reported.

[0186] · Scope that can be measured and / or reported: used to indicate the scope that can be measured and / or predicted and / or reported, where the scope can be one or more of the following identifiers and / or identifier lists: slice, service, scenario, node, UE, cell, beam, channel, protocol data unit session (Protocol Data Unit Session), data radio bearer (Data Radio Bearers, DRB), QoS flow, QoS level, etc. Identifier and / or identifier list, etc. The service can be a service type, quality of service (Quality of Service, QoS), scenario, etc. The service type may include one or more of the following: voice service, video service, virtual reality service, augmented reality service, call service, etc. The service quality may include one or more of the following: latency, throughput, reliability, packet loss rate, data rate, etc., which can be identified by 5G service quality indication (5G QoS Identifier, 5QI), service quality level indication (QoS Class Identifier, QCI), etc. The scenarios may include one or more of the following: Ultra-reliable and Low Latency Communications (URLLC), Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC), etc.

[0187] Slice load conditions that can be measured and / or reported: used to indicate specific parameters of slice load conditions that can be measured and / or reported. The load condition may include one or more of the following: the load condition and / or load information may include one or more of the following: PRB usage ratio, number of available PRBs, number of allocated PRBs, scheduled PDCCH CCE usage, transport network layer (Transport Network Layer (TNL)) capacity indication, radio resource status, comprehensive available capacity group, comprehensive available resource group, number of active user terminals, number of radio resource control (Radio Resource Control (RRC)) connections, slice available capacity, hardware capacity indication, S1 TNL load indication, hardware load indication, almost blank subframe (Almost Blank Subframe (ABS)) status, reference signal received power (Reference Signal Received Power (RSRP)) measurement report list, reference signal received quality (Reference Signal Receiving Quality (RSRQ)) measurement report, signal to interference plus noise ratio (Signal to Interference plus Noise Ratio (SINR)) measurement report, channel state information (Channel State Information (CSI)) report, cell report indication, channel occupancy (Channel Occupancy) time ratio, energy detection (Energy The load conditions may be based on measurement results or prediction results.

[0188] ·Scope that cannot be measured and / or reported: used to indicate the scope that cannot be measured and / or predicted and / or reported, where the scope can be one or more of the following identifiers and / or identifier lists: slice, service, scenario, node, UE, cell, beam, channel, protocol data unit session (Protocol Data Unit Session), data radio bearer (Data Radio Bearers, DRB), QoS flow, QoS level, etc. Identifier and / or identifier list, etc. The service can be a service type, quality of service (Quality of Service, QoS), scenario, etc. The service type may include one or more of the following: voice service, video service, virtual reality service, augmented reality service, call service, etc. The service quality may include one or more of the following: latency, throughput, reliability, packet loss rate, data rate, etc., which can be identified by a 5G service quality indicator (5G QoS Identifier, 5QI), a service quality level indicator (QoS Class Identifier, QCI), etc. The scenarios may include one or more of the following: Ultra-reliable and Low Latency Communications (URLLC), Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC), etc.

[0189] Slice load conditions that cannot be measured and / or reported: used to indicate specific parameters of slice load conditions that cannot be measured and / or reported. The load condition may include one or more of the following: the load condition and / or load information may include one or more of the following: PRB usage ratio, number of available PRBs, number of allocated PRBs, scheduled PDCCHCE usage, transport network layer (Transport Network Layer (TNL)) capacity indication, radio resource status, comprehensive available capacity group, comprehensive available resource group, number of active user terminals, number of radio resource control (Radio Resource Control (RRC)) connections, slice available capacity, hardware capacity indication, S1 TNL load indication, hardware load indication, almost blank subframe (Almost Blank Subframe (ABS)) status, reference signal received power (Reference Signal Received Power (RSRP)) measurement report list, reference signal received quality (Reference Signal Receiving Quality (RSRQ)) measurement report, signal to interference plus noise ratio (Signal to Interference plus Noise Ratio (SINR)) measurement report, channel state information (Channel State Information (CSI)) report, cell report indication, channel occupancy (Channel Occupancy) time ratio, energy detection (Energy The load conditions may be based on measurement results or prediction results.

[0190] Reason: indicates the reason why measurement and / or reporting cannot be performed. The reason may include one or more of the following: slice unavailable, measurement unavailable, slice load measurement unavailable, slice temporarily unavailable, measurement temporarily unavailable, slice measurement temporarily unavailable, reporting time unavailable, reporting period unavailable, slice corresponding to prediction unavailable, prediction unavailable, slice load prediction unavailable, prediction temporarily unavailable, slice prediction temporarily unavailable, prediction time unavailable, prediction reporting time unavailable, prediction information valid time unavailable, prediction information reporting period unavailable, slice not supported, measurement not supported, slice load measurement not supported, slice temporarily not supported, measurement temporarily not supported, slice measurement temporarily not supported, reporting time not supported, reporting period not supported, slice corresponding to prediction not supported, prediction not supported, slice load prediction not supported, prediction temporarily not supported, slice prediction temporarily not supported, prediction time not supported, prediction reporting time not supported, prediction information valid time not supported, prediction information reporting period not supported, etc.

[0191] In some embodiments, the fourth node sends a fifth message containing a slice load condition or a slice load condition update to the third node according to its own situation and / or according to the third message containing a slice load condition request received from the third node, so as to inform the third node of the slice load condition (or referred to as slice load information) measured (or obtained) by the fourth node. In some embodiments, after the fourth node receives the third message that the slice load request of the third node can request, the fourth node informs the third node through the fourth message that the fourth node can report part and / or all of the requested slice load conditions, and then the fourth node sends the slice load condition to the fourth node according to the third message containing the slice load request. After the third node obtains the slice load conditions of the fourth node and / or other nodes, it can make relevant decisions based on the slice load conditions of the fourth node and / or other nodes, such as SON-related decisions, to avoid frequent switching, local overload, overload, impaired service performance, etc. The third node can also evaluate the decisions made based on the slice load conditions of the fourth node and / or other nodes. In some embodiments, for example, when a local overload phenomenon occurs after a decision is made, it means that the decision made is inappropriate.

[0192] In some embodiments, the fifth message may be included in one or more of the following: a resource status request (RESOURCE STATUS REQUEST) message or a resource status response (RESOURCE STATUS RESPONSE) message or a resource status failure (RESOURCE STATUS FAILURE) message or a resource status update (RESOURCE STATUS UPDATE) message or a handover request confirmation (HANDOVER REQUEST ACKNOWLEDGE) message or a handover request (HANDOVERREQUEST) message or an NG-RAN node configuration update (NG-RAN NODE CONFIGURATION UPDATE) message or an NG-RAN node configuration update confirmation (NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE) message or an Xn setup request (XN SETUP REQUEST) message or an Xn setup response (XN SETUP RESPONSE) message of NG; an NG setup request (NG SETUP REQUEST) message or an NG setup response (NG SETUP RESPONSE) message or a RAN configuration update (RANCONFIGURATION UPDATE) message of NG. UPDATE) message or RAN Configuration Update Acknowledge (RAN CONFIGURATION UPDATE ACKNOWLEDGE) message or AMF Configuration Update (AMF CONFIGURATION UPDATE) message or AMF Configuration Update Acknowledge (AMF CONFIGURATION UPDATE ACKNOWLEDGE) message or AMF Status Indication (AMF STATUS INDICATION) message or Overload Start (OVERLOAD START) message or Overload Stop (OVERLOAD STOP) message or Handover Required (HANDOVER REQUIRED) message or Handover Command (HANDOVER COMMAND) message or Handover Request (HANDOVER REQUEST) message or Handover Request Acknowledge (HANDOVER REQUEST ACKNOWLEDGE) message or Uplink RAN ​​Configuration Transfer (UPLINK RAN CONFIGURATION TRANSFER) message or Downlink RAN ​​Configuration Transfer (DOWNLINK RAN CONFIGURATION TRANSFER) message;or F1 SETUP REQUEST message or F1 SETUP RESPONSE message or gNB-DU CONFIGURATION UPDATE message or gNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message or gNB-CU CONFIGURATION UPDATE message or gNB-CUCONFIGURATION UPDATE ACKNOWLEDGE message or gNB-DU STATUSINDICATION message or RESOURCE STATUS REQUEST message or RESOURCE STATUS RESPONSE message or RESOURCE STATUS FAILURE message or RESOURCE STATUS UPDATE message UE CONTEXT SETUP REQUEST message or RESOURCE STATUS RESPONSE message or RESOURCE STATUS FAILURE message or RESOURCE STATUS UPDATE message UE CONTEXT SETUP REQUEST) message or UE CONTEXT SETUP RESPONSE message or UE CONTEXT RELEASE REQUEST message or UE CONTEXT RELEASE COMMAND message or UE CONTEXT RELEASE COMPLETE message or UE CONTEXT MODIFICATION REQUEST message or UE CONTEXT MODIFICATION RESPONSE message or UE CONTEXT MODIFICATION REQUIRED message or UE CONTEXT MODIFICATION CONFIRM message;or gNB CU UP E1 SETUP REQUEST message of E1 or gNB CU UP E1 SETUP RESPONSE message or gNB CU CP E1 SETUP REQUEST message or gNB CU CP E1 SETUP RESPONSE message or gNB CUUP CONFIGURATION UPDATE message or gNB CU UP CONFIGURATION UPDATE ACKNOWLEDGE message or gNB CU CP CONFIGURATION UPDATE ACKNOWLEDGE message or gNB CU UP status indication (GNB-CU-UP STATUS INDICATION) message or Resource status request (RESOURCE STATUS REQUEST) message or Resource status response (RESOURCE STATUSRESPONSE) message or Resource status failure (RESOURCE STATUS FAILURE) message or Resource status update (RESOURCE STATUS UPDATE) message Bearer context setup request (BEARER CONTEXT SETUP REQUEST) message or Bearer context setup response (BEARER CONTEXT SETUP RESPONSE) message or Bearer context modification request (BEARER CONTEXT MODIFICATION REQUEST) message or Bearer context modification response (BEARERCONTEXTMODIFICATION RESPONSE) message or Bearer context modification required (BEARERCONTEXTMODIFICATION REQUIRED) message or BearerCONTEXTMODIFICATIONCONFIRM message or BearerCONTEXTRELEASECOMMAND message or BearerCONTEXTRELEASECOMMAND message CONTEXT RELEASE COMPLETE) message or bearer context release request (BEARERCONTEXT RELEASE REQUEST) message;or RRC reconfiguration (RRCReconfiguration) message or RRC recovery (RRCResume) message or RRC reconstruction (RRCReestablishment) message or RRC establishment (RRCSetup) message or RRC reconfiguration complete (RRCReconfigurationComplete) message or RRC recovery complete (RRCResumeComplete) message or RRC reconstruction complete (RRCReestablishmentComplete) message or RRC establishment complete (RRCSetupComplete) message; it can also be sent in the form of MAC CE; or another and / or newly defined RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message and / or RRC container, etc. In some embodiments, the fifth message may include one or more of the following fields or related information:;

[0193] Sending node ID: used to identify the node that sends the message.

[0194] Receiving node ID: used to identify the node that receives the message.

[0195] Measurement ID: used to identify the measurement.

[0196] · Scope corresponding to the load condition: used to indicate the scope corresponding to the load condition, wherein the scope may be one or more of the following identifiers and / or identifier lists: slice, service, scenario, node, UE, cell, beam, channel, protocol data unit session (Protocol Data Unit Session), data radio bearer (Data Radio Bearers, DRB), QoS flow, QoS level, etc. Identifiers and / or identifier lists, etc. The service may be a service type, quality of service (Quality of Service, QoS), scenario, etc. The service type may include one or more of the following: voice service, video service, virtual reality service, augmented reality service, call service, etc. The service quality may include one or more of the following: latency, throughput, reliability, packet loss rate, data rate, etc., which may be identified by a 5G service quality indicator (5G QoS Identifier, 5QI), a service quality level indicator (QoS Class Identifier, QCI), etc. The scenarios may include one or more of the following: Ultra-reliable and Low Latency Communications (URLLC), Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC), etc.

[0197] ·Measured slice load: used to indicate the measured slice load. The slice load may include PRB usage ratio, number of available PRBs, number of allocated PRBs, scheduled PDCCH CCE usage, transport network layer (TNL) capacity indication, radio resource status, comprehensive available capacity group, comprehensive available resource group, number of active user terminals, number of radio resource control (RRC) connections, slice available capacity, hardware capacity indication, S1 TNL load indication, hardware load indication, almost blank subframe (ABS) status, reference signal received power (RSRP) measurement report list, reference signal received quality (RSRQ) measurement report, signal to interference plus noise ratio (SINR) measurement report, channel state information (CSI) report, cell report indication, channel occupancy (Channel Occupancy) time ratio, energy detection (Energy The load conditions may be based on measurement results or prediction results.

[0198] · Applicable time of the measured slice load condition: used to indicate the time point and / or time interval corresponding to the measured slice load condition. The time can be a relative time or an absolute time. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a time interval, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits represent the start time, and the last n bits represent the end time. It can also be represented by a separate field, including one or more of the following:

[0199] o Start time: used to indicate the start time of the applicable time. The start time can be a relative time or an absolute time.

[0200] ο End time: used to indicate the end time of the applicable time. The end time can be a relative time or an absolute time.

[0201] · Predicted slice load: used to indicate the predicted slice load. The slice load may include PRB usage ratio, number of available PRBs, number of allocated PRBs, scheduled PDCCH CCE usage, transport network layer (TNL) capacity indication, radio resource status, comprehensive available capacity group, comprehensive available resource group, number of active user terminals, number of radio resource control (RRC) connections, slice available capacity, hardware capacity indication, S1 TNL load indication, hardware load indication, almost blank subframe (ABS) status, reference signal received power (RSRP) measurement report list, reference signal received quality (RSRQ) measurement report, signal to interference plus noise ratio (SINR) measurement report, channel state information (CSI) report, cell report indication, channel occupancy (Channel Occupancy) time ratio, energy detection (Energy The load conditions may be based on measurement results or prediction results.

[0202] · Applicable time of the predicted slice load condition: used to indicate the time point and / or time interval corresponding to the predicted slice load condition. The time can be a relative time or an absolute time. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a time interval, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits represent the start time, and the last n bits represent the end time. It can also be represented by a separate field, including one or more of the following:

[0203] o Start time: used to indicate the start time of the applicable time. The start time can be a relative time or an absolute time.

[0204] ο End time: used to indicate the end time of the applicable time. The end time can be a relative time or an absolute time.

[0205] ·Conditions and / or events that trigger reporting of the sub-slice load condition: Indicates the events and / or conditions that trigger reporting of the sub-slice load condition. The slice load condition includes the currently measured slice load information, and may also include predicted slice load information. The events and / or conditions that trigger reporting include one or more of the following: the slice load is greater than and / or equal to and / or less than a predetermined threshold value, the slice load is predicted to be greater than and / or equal to and / or less than a predetermined threshold value, an overload is about to occur, and an overload is predicted to occur.

[0206] ·Measurement time of the reported slice load: used to indicate the time point and / or time interval and / or measurement period of the measurement of the reported slice load. The time can be a relative time or an absolute time. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a time interval, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits represent the start time, and the last n bits represent the end time. It can also be represented by a separate field, including one or more of the following:

[0207] oStart time: used to indicate the start time of the measurement time. The start time can be a relative time or an absolute time.

[0208] ο End time: used to indicate the end time of the measurement time. The end time can be a relative time or an absolute time.

[0209] The fields in the third message, the fourth message, and the fifth message can be used for measured load information or predicted load information.

[0210] Example 3

[0211] An embodiment of the present disclosure proposes a method for supporting slices, which may include: a fifth node sends a sixth message containing a slice-related performance request (e.g., a request for slice-related performance) to a sixth node to request the sixth node to report the requested slice-related performance. In some embodiments, for example, the fifth node may use slice-related performance to evaluate slice-related decisions, for example, better slice-related performance (e.g., better than one or more predetermined standards or performance levels) may indicate that the slice-related decision is correct, and poor slice-related performance (e.g., worse than one or more predetermined standards or performance levels) may indicate that the slice-related decision is inappropriate and needs to be optimized and updated. In other embodiments, for example, the fifth node may also use slice-related performance to evaluate artificial intelligence machine learning models, for example, it may be possible to evaluate whether the model can continue to be used, whether the model needs to be trained and / or adjusted, etc. In yet other embodiments, for example, the fifth node may make decisions based on slice-related performance. For example, if the slice-related performance meets the needs of the user and / or business, the user may be switched and / or converted to the slice. For example, if the slice-related performance can meet the related requirements of other slices, such as QoS requirements, the fifth node can map other slices to the slice when performing slice remapping. The fifth node can also use the collected slice performance information for training and / or reasoning of an artificial intelligence machine learning model, for example, for prediction of slice information, etc.

[0212] In some embodiments, the sixth message may be included in one or more of the following: a resource status request (RESOURCE STATUS REQUEST) message or a resource status response (RESOURCE STATUS RESPONSE) message or a resource status failure (RESOURCE STATUS FAILURE) message or a resource status update (RESOURCE STATUS UPDATE) message or a handover request confirmation (HANDOVER REQUEST ACKNOWLEDGE) message or a handover request (HANDOVERREQUEST) message or an NG-RAN node configuration update (NG-RAN NODE CONFIGURATION UPDATE) message or an NG-RAN node configuration update confirmation (NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE) message or an Xn setup request (XN SETUP REQUEST) message or an Xn setup response (XN SETUP RESPONSE) message of NG; an NG setup request (NG SETUP REQUEST) message or an NG setup response (NG SETUP RESPONSE) message or a RAN configuration update (RANCONFIGURATION UPDATE) message of NG. UPDATE) message or RAN Configuration Update Acknowledge (RAN CONFIGURATION UPDATE ACKNOWLEDGE) message or AMF Configuration Update (AMF CONFIGURATION UPDATE) message or AMF Configuration Update Acknowledge (AMF CONFIGURATION UPDATE ACKNOWLEDGE) message or AMF Status Indication (AMF STATUS INDICATION) message or Overload Start (OVERLOAD START) message or Overload Stop (OVERLOAD STOP) message or Handover Required (HANDOVER REQUIRED) message or Handover Command (HANDOVER COMMAND) message or Handover Request (HANDOVER REQUEST) message or Handover Request Acknowledge (HANDOVER REQUEST ACKNOWLEDGE) message or Uplink RAN ​​Configuration Transfer (UPLINK RAN CONFIGURATION TRANSFER) message or Downlink RAN ​​Configuration Transfer (DOWNLINK RAN CONFIGURATION TRANSFER) message;or F1 SETUP REQUEST message or F1 SETUP RESPONSE message or gNB-DU CONFIGURATION UPDATE message or gNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message or gNB-CU CONFIGURATION UPDATE message or gNB-CUCONFIGURATION UPDATE ACKNOWLEDGE message or gNB-DU STATUSINDICATION message or RESOURCE STATUS REQUEST message or RESOURCE STATUS RESPONSE message or RESOURCE STATUS FAILURE message or RESOURCE STATUS UPDATE message UE CONTEXT SETUP REQUEST message or RESOURCE STATUS RESPONSE message or RESOURCE STATUS FAILURE message or RESOURCE STATUS UPDATE message UE CONTEXT SETUP REQUEST) message or UE CONTEXT SETUP RESPONSE message or UE CONTEXT RELEASE REQUEST message or UE CONTEXT RELEASE COMMAND message or UE CONTEXT RELEASE COMPLETE message or UE CONTEXT MODIFICATION REQUEST message or UE CONTEXT MODIFICATION RESPONSE message or UE CONTEXT MODIFICATION REQUIRED message or UE CONTEXT MODIFICATION CONFIRM message;or gNB CU UP E1 SETUP REQUEST message of E1 or gNB CU UP E1 SETUP RESPONSE message or gNB CU CP E1 SETUP REQUEST message or gNB CU CP E1 SETUP RESPONSE message or gNB CUUP CONFIGURATION UPDATE message or gNB CU UP CONFIGURATION UPDATE ACKNOWLEDGE message or gNB CU CP CONFIGURATION UPDATE ACKNOWLEDGE message or gNB CU UP status indication (GNB-CU-UP STATUS INDICATION) message or Resource status request (RESOURCE STATUS REQUEST) message or Resource status response (RESOURCE STATUSRESPONSE) message or Resource status failure (RESOURCE STATUS FAILURE) message or Resource status update (RESOURCE STATUS UPDATE) message Bearer context setup request (BEARER CONTEXT SETUP REQUEST) message or Bearer context setup response (BEARER CONTEXT SETUP RESPONSE) message or Bearer context modification request (BEARER CONTEXT MODIFICATION REQUEST) message or Bearer context modification response (BEARERCONTEXTMODIFICATION RESPONSE) message or Bearer context modification required (BEARERCONTEXTMODIFICATION REQUIRED) message or BearerCONTEXTMODIFICATIONCONFIRM message or BearerCONTEXTRELEASECOMMAND message or BearerCONTEXTRELEASECOMMAND message CONTEXT RELEASE COMPLETE) message or bearer context release request (BEARERCONTEXT RELEASE REQUEST) message;or RRC reconfiguration (RRCReconfiguration) message or RRC recovery (RRCResume) message or RRC reconstruction (RRCReestablishment) message or RRC establishment (RRCSetup) message or RRC reconfiguration completion (RRCReconfigurationComplete) message or RRC recovery completion (RRCResumeComplete) message or RRC reconstruction completion (RRCReestablishmentComplete) message or RRC establishment completion (RRCSetupComplete) message of RRC; it can also be downlink PDU session information (DL PDU SESSIONINFORMATION) or uplink PDU session information (UL PDU Session Information) or downlink user data (DLUSER DATA) or downlink data transmission status (DL DATA DELIVERY STATUS) or auxiliary information data (ASSISTANCE INFORMATION DATA) of the user plane; there can also be MAC CE; or another and / or newly defined RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message and / or RRC container and / or user plane frame, etc. In some implementations, the sixth message may include one or more of the following fields or related information:

[0213] Sending node ID: used to identify the node that sends the message.

[0214] Receiving node ID: used to identify the node that receives the message.

[0215] Request ID: used to identify this request.

[0216] Measurement ID: used to identify the measurement.

[0217] Slice performance request indication: used to indicate the request to report slice performance.

[0218] · Requested content: used to indicate the content requested to be reported. The content may include one or more of the following: QoS parameters, QoE parameters, load information, actual slice information, time information, UE identifier, slice identifier, cell identifier, beam identifier, etc. The actually connected slice information may be the actually accessed slice information, which may include one or more of the following: the actually accessed slice identifier, access time information, departure time information, slice residence time, etc. In some embodiments, for example, the actual slice information may be used to evaluate the accuracy of the predicted slice information. In some embodiments, for example, load information may be used to make and / or evaluate slice-related decisions. For example, to evaluate remapping decisions. If an overload occurs after the remapping decision is implemented, it means that the remapping decision is inappropriate.

[0219] ·Scope corresponding to the requested content: The scope may be one or more of the following identifiers and / or identifier lists: slice, UE, UE not to be measured, UE to be measured, etc. The above scope may also represent the slice performance excluding one or more UEs, for example, other users in the slice excluding the switched user, or other users in the slice excluding the user corresponding to the slice remapping.

[0220] · Requested content reporting method: used to indicate the requested content reporting method, which can include single reporting, periodic reporting, on-demand reporting, event-triggered reporting, etc.

[0221] · Reporting period of the requested content: used to indicate the interval time of reporting the requested content, or the time interval between two adjacent reports. The reporting period may also be the measurement time of the reported data. If there is no content in this field, it means that a single report is sufficient, and the single reporting time is the measurement start time to the measurement end time. In some embodiments, for example, the reporting period may be a reporting period for periodic reporting.

[0222] Request measurement time: used to indicate the time point and / or time interval of the measurement. The time can be relative or absolute. The time interval can be represented by a timer, a combination of the start time and the end time, a combination of the start time and the time interval, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits represent the measurement start time, and the last n bits represent the measurement end time. It can also be represented by a separate field, including one or more of the following:

[0223] o Measurement start time: used to indicate the start time of the measurement. The start time can be a relative time or an absolute time.

[0224] οMeasurement end time: used to indicate the end time of the measurement. The end time can be a relative time or an absolute time.

[0225] Request report time: used to indicate the time point and / or time interval of the report. The time can be relative or absolute. The time interval can be represented by a timer, a combination of the start time and the end time, a combination of the start time and the time interval, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits represent the start time, and the last n bits represent the end time. It can also be represented by a separate field, including one or more of the following:

[0226] o Start time: used to indicate the start time of reporting. The start time can be a relative time or an absolute time.

[0227] End time: used to indicate the end time of the report. The end time can be a relative time or an absolute time.

[0228] Applicable time corresponding to the requested report content: used to indicate the applicable time point and / or time interval corresponding to the requested report content. The time can be a relative time or an absolute time. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a time interval, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits represent the start time, and the last n bits represent the end time. It can also be represented by a separate field, including one or more of the following:

[0229] o Start time: used to indicate the start time of the applicable time. The start time can be a relative time or an absolute time.

[0230] ο End time: used to indicate the end time of the applicable time. The end time can be a relative time or an absolute time.

[0231] ·Indication of whether partial reporting can be performed: used to indicate whether the message receiving node can perform partial reporting. In other words, whether the message receiving node can report part of the information requested to be reported. If the indication is that partial reporting can be performed, the message receiving node only needs to report part of the information requested to be reported. If the indication is that partial reporting cannot be performed, the message receiving node must report all the information requested to be reported. If one or more of the requested information cannot be reported, the message receiving node sends a request failure message to the message sending node. The information requested to be reported may include one or more of the above-mentioned requested contents, or one or more of the ranges corresponding to the above-mentioned requested contents. The indication can allow the message receiving node to report part of the information according to its own situation, so as to avoid the message receiving node having to send a request failure message when it cannot report one or more of the requested information, resulting in a request failure, so that the message sending node needs to re-request. However, the message sending node does not know which messages the message receiving node can send, resulting in the message sending node having to keep trying to request, causing a signaling burden.

[0232] Indication of whether the requested information must be reported: used to indicate whether the requested information must be reported. If the information is indicated to be reported, the message receiving node must report the information and / or the load corresponding to the information. The information requested to be reported may include one or more of the above-mentioned requested contents, or one or more of the ranges corresponding to the above-mentioned requested contents. The message receiving node may determine which parameters to report based on the indication and / or its own request.

[0233] ·Priority of the requested information: used to indicate the priority of the requested information. In some embodiments, the message receiving node must report high priority information. The message receiving node may report and / or not report low priority information according to its own situation. The requested information may include one or more of the above-mentioned requested contents, or one or more of the ranges corresponding to the above-mentioned requested contents. The message receiving node may determine which parameters to report according to the priority and its own request.

[0234] In some embodiments, the sixth node sends a seventh message containing slice-related performance (or information about slice-related performance) to the fifth node according to its own situation and / or according to the sixth message containing a slice-related performance request received from the fifth node. In some embodiments, for example, the fifth node can use slice-related performance to evaluate slice-related decisions. For example, better slice-related performance can indicate that the slice-related decision is correct, and poor slice-related performance indicates that the slice-related decision is inappropriate and needs to be optimized and updated. For example, the fifth node can also use slice-related performance to evaluate artificial intelligence machine learning models, for example, to evaluate whether the model can continue to be used, whether the model needs to be trained and / or adjusted, etc.

[0235] In some embodiments, the seventh message may be included in one or more of the following: a resource status request (RESOURCE STATUS REQUEST) message or a resource status response (RESOURCE STATUS RESPONSE) message or a resource status failure (RESOURCE STATUS FAILURE) message or a resource status update (RESOURCE STATUS UPDATE) message or a handover request confirmation (HANDOVER REQUEST ACKNOWLEDGE) message or a handover request (HANDOVERREQUEST) message or an NG-RAN node configuration update (NG-RAN NODE CONFIGURATION UPDATE) message or an NG-RAN node configuration update confirmation (NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE) message or an Xn setup request (XN SETUP REQUEST) message or an Xn setup response (XN SETUP RESPONSE) message of NG; an NG setup request (NG SETUP REQUEST) message or an NG setup response (NG SETUP RESPONSE) message or a RAN configuration update (RANCONFIGURATION UPDATE) message of NG. UPDATE) message or RAN Configuration Update Acknowledge (RAN CONFIGURATION UPDATE ACKNOWLEDGE) message or AMF Configuration Update (AMF CONFIGURATION UPDATE) message or AMF Configuration Update Acknowledge (AMF CONFIGURATION UPDATE ACKNOWLEDGE) message or AMF Status Indication (AMF STATUS INDICATION) message or Overload Start (OVERLOAD START) message or Overload Stop (OVERLOAD STOP) message or Handover Required (HANDOVER REQUIRED) message or Handover Command (HANDOVER COMMAND) message or Handover Request (HANDOVER REQUEST) message or Handover Request Acknowledge (HANDOVER REQUEST ACKNOWLEDGE) message or Uplink RAN ​​Configuration Transfer (UPLINK RAN CONFIGURATION TRANSFER) message or Downlink RAN ​​Configuration Transfer (DOWNLINK RAN CONFIGURATION TRANSFER) message;or F1 SETUP REQUEST message or F1 SETUP RESPONSE message or gNB-DU CONFIGURATION UPDATE message or gNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message or gNB-CU CONFIGURATION UPDATE message or gNB-CUCONFIGURATION UPDATE ACKNOWLEDGE message or gNB-DU STATUSINDICATION message or RESOURCE STATUS REQUEST message or RESOURCE STATUS RESPONSE message or RESOURCE STATUS FAILURE message or RESOURCE STATUS UPDATE message UE CONTEXT SETUP REQUEST message or RESOURCE STATUS RESPONSE message or RESOURCE STATUS FAILURE message or RESOURCE STATUS UPDATE message UE CONTEXT SETUP REQUEST) message or UE CONTEXT SETUP RESPONSE message or UE CONTEXT RELEASE REQUEST message or UE CONTEXT RELEASE COMMAND message or UE CONTEXT RELEASE COMPLETE message or UE CONTEXT MODIFICATION REQUEST message or UE CONTEXT MODIFICATION RESPONSE message or UE CONTEXT MODIFICATION REQUIRED message or UE CONTEXT MODIFICATION CONFIRM message;or gNB CU UP E1 SETUP REQUEST message of E1 or gNB CU UP E1 SETUP RESPONSE message or gNB CU CP E1 SETUP REQUEST message or gNB CU CP E1 SETUP RESPONSE message or gNB CUUP CONFIGURATION UPDATE message or gNB CU UP CONFIGURATION UPDATE ACKNOWLEDGE message or gNB CU CP CONFIGURATION UPDATE ACKNOWLEDGE message or gNB CU UP status indication (GNB-CU-UP STATUS INDICATION) message or Resource status request (RESOURCE STATUS REQUEST) message or Resource status response (RESOURCE STATUSRESPONSE) message or Resource status failure (RESOURCE STATUS FAILURE) message or Resource status update (RESOURCE STATUS UPDATE) message Bearer context setup request (BEARER CONTEXT SETUP REQUEST) message or Bearer context setup response (BEARER CONTEXT SETUP RESPONSE) message or Bearer context modification request (BEARER CONTEXT MODIFICATION REQUEST) message or Bearer context modification response (BEARERCONTEXTMODIFICATION RESPONSE) message or Bearer context modification required (BEARERCONTEXTMODIFICATION REQUIRED) message or BearerCONTEXTMODIFICATIONCONFIRM message or BearerCONTEXTRELEASECOMMAND message or BearerCONTEXTRELEASECOMMAND message CONTEXT RELEASE COMPLETE) message or bearer context release request (BEARERCONTEXT RELEASE REQUEST) message;or RRC reconfiguration (RRCReconfiguration) message or RRC recovery (RRCResume) message or RRC reconstruction (RRCReestablishment) message or RRC establishment (RRCSetup) message or RRC reconfiguration completion (RRCReconfigurationComplete) message or RRC recovery completion (RRCResumeComplete) message or RRC reconstruction completion (RRCReestablishmentComplete) message or RRC establishment completion (RRCSetupComplete) message of RRC; it can also be downlink PDU session information (DL PDU SESSIONINFORMATION) or uplink PDU session information (UL PDU Session Information) or downlink user data (DLUSER DATA) or downlink data transmission status (DL DATA DELIVERY STATUS) or auxiliary information data (ASSISTANCE INFORMATION DATA) of the user plane; there can also be MAC CE; or another and / or newly defined RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message and / or RRC container and / or user plane frame, etc.;

[0236] In some implementations, the seventh message may include one or more of the following fields or related information:

[0237] Sending node ID: used to identify the node that sends the message.

[0238] Receiving node ID: used to identify the node that receives the message.

[0239] Request ID: used to identify this request.

[0240] Measurement ID: used to identify the measurement.

[0241] Reported content: used to indicate the reported content. The content may include one or more of the following: QoS parameters, QoE parameters, load information, actual slice information, time information, UE identifier, slice identifier, cell identifier, beam identifier, etc. The actual slice information may be the slice information actually accessed, and may include one or more of the following: the slice identifier actually accessed, the time information of access, the time information of leaving, the residence time of the slice, etc.

[0242] · Scope corresponding to the reported content: The scope may be one or more of the following identifiers and / or identifier lists: slice, UE, UE not performing measurement, UE performing measurement, cell, etc. The above scope may also represent the slice performance excluding one or more UEs, for example, other users in the slice excluding the switching user, or other users in the slice excluding the user corresponding to the slice remapping.

[0243] Applicable time corresponding to the reported content: used to indicate the applicable time point and / or time interval corresponding to the reported content. The time can be a relative time or an absolute time. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a time interval, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits represent the start time, and the last n bits represent the end time. It can also be represented by a separate field, including one or more of the following:

[0244] o Start time: used to indicate the start time of the applicable time. The start time can be a relative time or an absolute time.

[0245] ο End time: used to indicate the end time of the applicable time. The end time can be a relative time or an absolute time.

[0246] Example 4

[0247] An embodiment of the present disclosure proposes a method for supporting slicing, which may include: a seventh node sends an eighth message containing a predicted excessive slice load to an eighth node, so that the eighth node can be aware of the predicted excessive slice load, and the eighth node can refer to the information in the switching decision. In some embodiments, for example, when the eighth node receives a switching request to switch to the slice, the eighth node may reject the switching request because it knows that the predicted slice load is too large, so as to avoid the need to switch the UE to other cells in a short time after receiving the UE to cope with the excessive slice load.

[0248] In some embodiments, the eighth message may be included in one or more of the following: a resource status request (RESOURCE STATUS REQUEST) message or a resource status response (RESOURCE STATUS RESPONSE) message or a resource status failure (RESOURCE STATUS FAILURE) message or a resource status update (RESOURCE STATUS UPDATE) message or a handover request confirmation (HANDOVER REQUEST ACKNOWLEDGE) message or a handover request (HANDOVERREQUEST) message or an NG-RAN node configuration update (NG-RAN NODE CONFIGURATION UPDATE) message or an NG-RAN node configuration update confirmation (NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE) message or an Xn setup request (XN SETUP REQUEST) message or an Xn setup response (XN SETUP RESPONSE) message of NG; an NG setup request (NG SETUP REQUEST) message or an NG setup response (NG SETUP RESPONSE) message or a RAN configuration update (RANCONFIGURATION UPDATE) message of NG. UPDATE) message or RAN Configuration Update Acknowledge (RAN CONFIGURATION UPDATE ACKNOWLEDGE) message or AMF Configuration Update (AMF CONFIGURATION UPDATE) message or AMF Configuration Update Acknowledge (AMF CONFIGURATION UPDATE ACKNOWLEDGE) message or AMF Status Indication (AMF STATUS INDICATION) message or Overload Start (OVERLOAD START) message or Overload Stop (OVERLOAD STOP) message or Handover Required (HANDOVER REQUIRED) message or Handover Command (HANDOVER COMMAND) message or Handover Request (HANDOVER REQUEST) message or Handover Request Acknowledge (HANDOVER REQUEST ACKNOWLEDGE) message or Uplink RAN ​​Configuration Transfer (UPLINK RAN CONFIGURATION TRANSFER) message or Downlink RAN ​​Configuration Transfer (DOWNLINK RAN CONFIGURATION TRANSFER) message;or F1 SETUP REQUEST message or F1 SETUP RESPONSE message or gNB-DU CONFIGURATION UPDATE message or gNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message or gNB-CU CONFIGURATION UPDATE message or gNB-CUCONFIGURATION UPDATE ACKNOWLEDGE message or gNB-DU STATUSINDICATION message or RESOURCE STATUS REQUEST message or RESOURCE STATUS RESPONSE message or RESOURCE STATUS FAILURE message or RESOURCE STATUS UPDATE message UE CONTEXT SETUP REQUEST message or RESOURCE STATUS RESPONSE message or RESOURCE STATUS FAILURE message or RESOURCE STATUS UPDATE message UE CONTEXT SETUP REQUEST) message or UE CONTEXT SETUP RESPONSE message or UE CONTEXT RELEASE REQUEST message or UE CONTEXT RELEASE COMMAND message or UE CONTEXT RELEASE COMPLETE message or UE CONTEXT MODIFICATION REQUEST message or UE CONTEXT MODIFICATION RESPONSE message or UE CONTEXT MODIFICATION REQUIRED message or UE CONTEXT MODIFICATION CONFIRM message;or gNB CU UP E1 SETUP REQUEST message of E1 or gNB CU UP E1 SETUP RESPONSE message or gNB CU CP E1 SETUP REQUEST message or gNB CU CP E1 SETUP RESPONSE message or gNB CUUP CONFIGURATION UPDATE message or gNB CU UP CONFIGURATION UPDATE ACKNOWLEDGE message or gNB CU CP CONFIGURATION UPDATE ACKNOWLEDGE message or gNB CU UP status indication (GNB-CU-UP STATUS INDICATION) message or Resource status request (RESOURCE STATUS REQUEST) message or Resource status response (RESOURCE STATUSRESPONSE) message or Resource status failure (RESOURCE STATUS FAILURE) message or Resource status update (RESOURCE STATUS UPDATE) message Bearer context setup request (BEARER CONTEXT SETUP REQUEST) message or Bearer context setup response (BEARER CONTEXT SETUP RESPONSE) message or Bearer context modification request (BEARER CONTEXT MODIFICATION REQUEST) message or Bearer context modification response (BEARERCONTEXTMODIFICATION RESPONSE) message or Bearer context modification required (BEARERCONTEXTMODIFICATION REQUIRED) message or BearerCONTEXTMODIFICATIONCONFIRM message or BearerCONTEXTRELEASECOMMAND message or BearerCONTEXTRELEASECOMMAND message CONTEXT RELEASE COMPLETE) message or bearer context release request (BEARERCONTEXT RELEASE REQUEST) message;or RRC reconfiguration (RRCReconfiguration) message or RRC recovery (RRCResume) message or RRC reconstruction (RRCReestablishment) message or RRC establishment (RRCSetup) message or RRC reconfiguration complete (RRCReconfigurationComplete) message or RRC recovery complete (RRCResumeComplete) message or RRC reconstruction complete (RRCReestablishmentComplete) message or RRC establishment complete (RRCSetupComplete) message; it can also be sent in the form of MAC CE; or another and / or newly defined RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message and / or RRC container, etc. In some embodiments, the eighth message may include one or more of the following fields or related information:;

[0249] Sending node ID: used to identify the node that sends the message.

[0250] Receiving node ID: used to identify the node that receives the message.

[0251] Slice ID corresponding to the predicted overload: used to identify the slice ID corresponding to the predicted overload situation of the slice.

[0252] The cell identifier corresponding to the predicted excessive load: used to identify the cell identifier corresponding to the predicted excessive load of the slice.

[0253] Predicted overload: The load may be one or more of the following: PRB usage ratio, number of available PRBs, number of allocated PRBs, scheduled PDCCH CCE usage, transport network layer (TNL) capacity indication, radio resource status, integrated available capacity group, integrated available resource group, number of active user terminals, number of radio resource control (RRC) connections, slice available capacity, hardware capacity indication, S1 TNL load indication, hardware load indication, almost blank subframe (ABS) status, reference signal received power (RSRP) measurement report list, reference signal received quality (RSRQ) measurement report, signal to interference plus noise ratio (SINR) measurement report, channel state information (CSI) report, cell report indication, channel occupancy (Channel Occupancy) time ratio, energy detection (Energy Detection) threshold, signal strength and / or signal quality, channel busy ratio, data volume, and jitter of various content parameters. It can also be represented by a ratio. In some embodiments, for example, it can be the ratio of the load when overloaded to the current load, or the ratio of the load when overloaded to the current instantaneous input rate, or the ratio of the load when overloaded to the total load, or the ratio of the overload when overloaded to the current load, or the ratio of the load when overloaded to the current instantaneous input rate, or the ratio of the load when overloaded to the total load, etc.

[0254] Time information corresponding to the predicted overload: used to indicate when the predicted overload occurs.

[0255] The accuracy and / or confidence of the forecast

[0256] Action: used to indicate the action that the receiving node of the message should apply. The action may include one or more of the following: for example, rejecting RRC establishment, rejecting non-emergency RRC establishment, rejecting RRC establishment for signaling, allowing only emergency session establishment, allowing only mobile terminated services, allowing only high-priority sessions, etc. In some embodiments, the action may be a configured action, that is, the receiving node of the message must implement it in accordance with the action. In other embodiments, the action may also be a recommended action, and the receiving node of the message may implement it in accordance with the recommended action or not according to its own situation.

[0257] Example 5

[0258] An embodiment of the present disclosure proposes a method for supporting slicing, which may include: a seventh node sends a ninth message containing load information that can be received by (a specific node and / or a specific slice) to an eighth node, so that the eighth node can know the load that can be received by the eighth node itself and / or any other associated node. The eighth node can refer to this information in subsequent switching decisions. In some embodiments, for example, when the eighth node receives a switching request that requires switching to the slice, if the load of the UE is less than and / or equal to the load that can be received, the eighth node can accept the switching request; if the load of the UE is greater than the load information that can be received, the eighth node can reject the switching request to avoid the need to switch the UE to other cells in a short time after receiving the UE to cope with the situation where the slice load is too large.

[0259] In some embodiments, the ninth message may be included in one or more of the following: a resource status request (RESOURCE STATUS REQUEST) message or a resource status response (RESOURCE STATUS RESPONSE) message or a resource status failure (RESOURCE STATUS FAILURE) message or a resource status update (RESOURCE STATUS UPDATE) message or a handover request confirmation (HANDOVER REQUEST ACKNOWLEDGE) message or a handover request (HANDOVERREQUEST) message or an NG-RAN node configuration update (NG-RAN NODE CONFIGURATION UPDATE) message or an NG-RAN node configuration update confirmation (NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE) message or an Xn setup request (XN SETUP REQUEST) message or an Xn setup response (XN SETUP RESPONSE) message of NG; an NG setup request (NG SETUP REQUEST) message or an NG setup response (NG SETUP RESPONSE) message or a RAN configuration update (RANCONFIGURATION UPDATE) message or RAN Configuration Update Acknowledge (RAN CONFIGURATION UPDATE ACKNOWLEDGE) message or AMF Configuration Update (AMF CONFIGURATION UPDATE) message or AMF Configuration Update Acknowledge (AMF CONFIGURATION UPDATE ACKNOWLEDGE) message or AMF Status Indication (AMF STATUS INDICATION) message or Overload Start (OVERLOAD START) message or Overload Stop (OVERLOAD STOP) message or Handover Required (HANDOVER REQUIRED) message or Handover Command (HANDOVER COMMAND) message or Handover Request (HANDOVER REQUEST) message or Handover Request Acknowledge (HANDOVER REQUEST ACKNOWLEDGE) message or Uplink RAN ​​Configuration Transfer (UPLINK RAN CONFIGURATION TRANSFER) message or Downlink RAN ​​Configuration Transfer (DOWNLINK RAN CONFIGURATION TRANSFER) message;or F1 SETUP REQUEST message or F1 SETUP RESPONSE message or gNB-DU CONFIGURATION UPDATE message or gNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message or gNB-CU CONFIGURATION UPDATE message or gNB-CUCONFIGURATION UPDATE ACKNOWLEDGE message or gNB-DU STATUSINDICATION message or RESOURCE STATUS REQUEST message or RESOURCE STATUS RESPONSE message or RESOURCE STATUS FAILURE message or RESOURCE STATUS UPDATE message UE CONTEXT SETUP REQUEST message or RESOURCE STATUS RESPONSE message or RESOURCE STATUS FAILURE message or RESOURCE STATUS UPDATE message UE CONTEXT SETUP REQUEST) message or UE CONTEXT SETUP RESPONSE message or UE CONTEXT RELEASE REQUEST message or UE CONTEXT RELEASE COMMAND message or UE CONTEXT RELEASE COMPLETE message or UE CONTEXT MODIFICATION REQUEST message or UE CONTEXT MODIFICATION RESPONSE message or UE CONTEXT MODIFICATION REQUIRED message or UE CONTEXT MODIFICATION CONFIRM message;or gNB CU UP E1 SETUP REQUEST message of E1 or gNB CU UP E1 SETUP RESPONSE message or gNB CU CP E1 SETUP REQUEST message or gNB CU CP E1 SETUP RESPONSE message or gNB CUUP CONFIGURATION UPDATE message or gNB CU UP CONFIGURATION UPDATE ACKNOWLEDGE message or gNB CU CP CONFIGURATION UPDATE ACKNOWLEDGE message or gNB CU UP status indication (GNB-CU-UP STATUS INDICATION) message or Resource status request (RESOURCE STATUS REQUEST) message or Resource status response (RESOURCE STATUSRESPONSE) message or Resource status failure (RESOURCE STATUS FAILURE) message or Resource status update (RESOURCE STATUS UPDATE) message Bearer context setup request (BEARER CONTEXT SETUP REQUEST) message or Bearer context setup response (BEARER CONTEXT SETUP RESPONSE) message or Bearer context modification request (BEARER CONTEXT MODIFICATION REQUEST) message or Bearer context modification response (BEARERCONTEXTMODIFICATION RESPONSE) message or Bearer context modification required (BEARERCONTEXTMODIFICATION REQUIRED) message or BearerCONTEXTMODIFICATIONCONFIRM message or BearerCONTEXTRELEASECOMMAND message or BearerCONTEXTRELEASECOMMAND message CONTEXT RELEASE COMPLETE) message or bearer context release request (BEARERCONTEXT RELEASE REQUEST) message;or RRC reconfiguration (RRCReconfiguration) message or RRC recovery (RRCResume) message or RRC reconstruction (RRCReestablishment) message or RRC establishment (RRCSetup) message or RRC reconfiguration complete (RRCReconfigurationComplete) message or RRC recovery complete (RRCResumeComplete) message or RRC reconstruction complete (RRCReestablishmentComplete) message or RRC establishment complete (RRCSetupComplete) message; it can also be sent in the form of MAC CE; or another and / or newly defined RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message and / or RRC container, etc. In some embodiments, the ninth message may include one or more of the following fields or related information:;

[0260] Sending node ID: used to identify the node that sends the message.

[0261] Receiving node ID: used to identify the node that receives the message.

[0262] Receivable payload information: information indicating the receivable payload.

[0263] o Receivable load: The load may be one or more of the following: PRB usage ratio, number of available PRBs, number of allocated PRBs, scheduled PDCCH CCE usage, transport network layer (Transport Network Layer (TNL)) capacity indication, radio resource status, comprehensive available capacity group, comprehensive available resource group, number of active user terminals, number of radio resource control (Radio Resource Control (RRC)) connections, slice available capacity, hardware capacity indication, S1TNL load indication, hardware load indication, almost blank subframe (Almost Blank Subframe (ABS)) status, reference signal received power (Reference Signal Received Power (RSRP)) measurement report list, reference signal received quality (Reference Signal Receiving Quality (RSRQ)) measurement report, signal to interference plus noise ratio (Signal to Interference plus Noise Ratio (SINR)) measurement report, channel state information (Channel State Information (CSI)) report, cell report indication, channel occupancy (Channel Occupancy) time ratio, energy detection (Energy The information may include a detection threshold, signal strength and / or signal quality, channel busy ratio, data volume, and jitter of various content parameters. It may also be represented by a ratio. In some implementations, for example, the receivable load may be a ratio of the current load, the receivable load may be a ratio of the current instantaneous input rate, or the receivable load may be a ratio of the total load.

[0264] οCan receive the slice identifier corresponding to the load

[0265] o can receive the cell identifier corresponding to the load

[0266] o Actions corresponding to the load amount can be received: actions that the receiving node of the message should apply. The actions may include one or more of the following: for example, rejecting RRC establishment, rejecting non-emergency RRC establishment, rejecting RRC establishment for signaling, allowing only emergency session establishment, allowing only mobile terminated services, allowing only high-priority sessions, etc. In some embodiments, the action may be a configured action, that is, the receiving node of the message must implement it in accordance with the action. In other embodiments, the action may also be a recommended action, and the receiving node of the message may implement or not implement it in accordance with the recommended action according to its own situation.

[0267] The time corresponding to the receivable load: It is used to indicate the time at which the receivable load can be received.

[0268] The accuracy and / or confidence of the forecast

[0269] Example 6

[0270] An embodiment of the present disclosure proposes a method for supporting slicing, which may include: a ninth node sending a tenth message including a slice resource allocation decision to a tenth node, so that the tenth node knows the slice resource allocation decision, and the tenth node can use resources according to the slice resource allocation decision, or the tenth node forwards the message to other nodes, so that the other nodes can use resources according to the slice resource allocation decision. The slice resource allocation decision may be a current slice resource allocation decision or a predicted resource allocation decision.

[0271] In some embodiments, the tenth message may be included in one or more of the following: a resource status request (RESOURCE STATUS REQUEST) message or a resource status response (RESOURCE STATUS RESPONSE) message or a resource status failure (RESOURCE STATUS FAILURE) message or a resource status update (RESOURCE STATUS UPDATE) message or a handover request confirmation (HANDOVER REQUEST ACKNOWLEDGE) message or a handover request (HANDOVERREQUEST) message or an NG-RAN node configuration update (NG-RAN NODE CONFIGURATION UPDATE) message or an NG-RAN node configuration update confirmation (NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE) message or an Xn setup request (XN SETUP REQUEST) message or an Xn setup response (XN SETUP RESPONSE) message of NG; an NG setup request (NG SETUP REQUEST) message or an NG setup response (NG SETUP RESPONSE) message or a RAN configuration update (RANCONFIGURATION UPDATE) message of NG. UPDATE) message or RAN Configuration Update Acknowledge (RAN CONFIGURATION UPDATE ACKNOWLEDGE) message or AMF Configuration Update (AMF CONFIGURATION UPDATE) message or AMF Configuration Update Acknowledge (AMF CONFIGURATION UPDATE ACKNOWLEDGE) message or AMF Status Indication (AMF STATUS INDICATION) message or Overload Start (OVERLOAD START) message or Overload Stop (OVERLOAD STOP) message or Handover Required (HANDOVER REQUIRED) message or Handover Command (HANDOVER COMMAND) message or Handover Request (HANDOVER REQUEST) message or Handover Request Acknowledge (HANDOVER REQUEST ACKNOWLEDGE) message or Uplink RAN ​​Configuration Transfer (UPLINK RAN CONFIGURATION TRANSFER) message or Downlink RAN ​​Configuration Transfer (DOWNLINK RAN CONFIGURATION TRANSFER) message;or F1 SETUP REQUEST message or F1 SETUP RESPONSE message or gNB-DU CONFIGURATION UPDATE message or gNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message or gNB-CU CONFIGURATION UPDATE message or gNB-CUCONFIGURATION UPDATE ACKNOWLEDGE message or gNB-DU STATUSINDICATION message or RESOURCE STATUS REQUEST message or RESOURCE STATUS RESPONSE message or RESOURCE STATUS FAILURE message or RESOURCE STATUS UPDATE message UE CONTEXT SETUP REQUEST message or RESOURCE STATUS RESPONSE message or RESOURCE STATUS FAILURE message or RESOURCE STATUS UPDATE message UE CONTEXT SETUP REQUEST) message or UE CONTEXT SETUP RESPONSE message or UE CONTEXT RELEASE REQUEST message or UE CONTEXT RELEASE COMMAND message or UE CONTEXT RELEASE COMPLETE message or UE CONTEXT MODIFICATION REQUEST message or UE CONTEXT MODIFICATION RESPONSE message or UE CONTEXT MODIFICATION REQUIRED message or UE CONTEXT MODIFICATION CONFIRM message;or gNB CU UP E1 SETUP REQUEST message of E1 or gNB CU UP E1 SETUP RESPONSE message or gNB CU CP E1 SETUP REQUEST message or gNB CU CP E1 SETUP RESPONSE message or gNB CUUP CONFIGURATION UPDATE message or gNB CU UP CONFIGURATION UPDATE ACKNOWLEDGE message or gNB CU CP CONFIGURATION UPDATE ACKNOWLEDGE message or gNB CU UP status indication (GNB-CU-UP STATUS INDICATION) message or Resource status request (RESOURCE STATUS REQUEST) message or Resource status response (RESOURCE STATUSRESPONSE) message or Resource status failure (RESOURCE STATUS FAILURE) message or Resource status update (RESOURCE STATUS UPDATE) message Bearer context setup request (BEARER CONTEXT SETUP REQUEST) message or Bearer context setup response (BEARER CONTEXT SETUP RESPONSE) message or Bearer context modification request (BEARER CONTEXT MODIFICATION REQUEST) message or Bearer context modification response (BEARERCONTEXTMODIFICATION RESPONSE) message or Bearer context modification required (BEARERCONTEXTMODIFICATION REQUIRED) message or BearerCONTEXTMODIFICATIONCONFIRM message or BearerCONTEXTRELEASECOMMAND message or BearerCONTEXTRELEASECOMMAND message CONTEXT RELEASE COMPLETE) message or bearer context release request (BEARERCONTEXT RELEASE REQUEST) message;or RRC reconfiguration (RRCReconfiguration) message or RRC recovery (RRCResume) message or RRC reconstruction (RRCReestablishment) message or RRC establishment (RRCSetup) message or RRC reconfiguration complete (RRCReconfigurationComplete) message or RRC recovery complete (RRCResumeComplete) message or RRC reconstruction complete (RRCReestablishmentComplete) message or RRC establishment complete (RRCSetupComplete) message; it can also be sent in the form of MAC CE; or another and / or newly defined RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message and / or RRC container, etc. In some embodiments, the tenth message may include one or more of the following fields or related information:;

[0272] Sending node ID: used to identify the node that sends the message.

[0273] Receiving node ID: used to identify the node that receives the message.

[0274] Time information corresponding to the resource allocation decision: the time may be the current time, or a future time point and / or time period.

[0275] Resource allocation decision: The resource allocation decision may include one or more of the following:

[0276] o Dedicated resource allocation decision: The dedicated resource allocation decision may include one or more of the following: the starting position of the dedicated resource, the ending position of the dedicated resource, the resource size of the dedicated resource, the proportion of the dedicated resource, the RRM policy dedicated proportion, the RRM policy minimum proportion, the RRM policy maximum proportion, etc. In some embodiments, the resource indicated by the RRM policy dedicated proportion is a dedicated resource.

[0277] o Priority resource allocation decision: The priority resource allocation decision may include one or more of the following: the starting position of the priority resource, the ending position of the priority resource, the resource size of the priority resource, the ratio of the priority resource, the RRM policy exclusive ratio, the RRM policy minimum ratio, the RRM policy maximum ratio, etc. In some embodiments, the resources indicated from the RRM policy exclusive ratio to the RRM policy minimum ratio are exclusive resources.

[0278] o Shared resource allocation decision: The shared resource allocation decision may include one or more of the following: the starting position of the shared resource, the ending position of the shared resource, the resource size of the shared resource, the proportion of the shared resource, the RRM policy exclusive proportion, the RRM policy minimum proportion, the RRM policy maximum proportion, etc. In some embodiments, the resources indicated from the RRM policy minimum proportion to the RRM policy maximum proportion are exclusive resources.

[0279] oRRM policy ratio: may include one or more of the following: RRM policy exclusive ratio, RRM policy minimum ratio, RRM policy maximum ratio, etc.

[0280] Example 7

[0281] An embodiment of the present disclosure proposes a method for supporting slicing, which may include: an eleventh node sends an eleventh message containing a slice resource usage request to a twelfth node to request the twelfth node to report the slice resource usage. The eleventh node may evaluate the decision made according to the slice resource usage. For example, if the occupancy rate of the priority resource is high, it means that the decision is inappropriate, for example, the use of other slice shared resources cannot be guaranteed. The eleventh node may also set a slice resource allocation decision according to the slice resource usage. For example, if the occupancy rate of the priority resource is high, the priority resource may be set as a dedicated resource to ensure the use of other slice shared resources.

[0282] In some embodiments, the eleventh message may be included in one or more of the following: a resource status request (RESOURCE STATUS REQUEST) message or a resource status response (RESOURCE STATUS RESPONSE) message or a resource status failure (RESOURCE STATUS FAILURE) message or a resource status update (RESOURCE STATUSUPDATE) message or a handover request confirmation (HANDOVER REQUEST ACKNOWLEDGE) message or a handover request (HANDOVER REQUEST) message or an NG-RAN node configuration update (NG-RAN NODE CONFIGURATION UPDATE) message or an NG-RAN node configuration update confirmation (NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE) message or an Xn setup request (XN SETUP REQUEST) message or an Xn setup response (XN SETUP RESPONSE) message of NG; an NG setup request (NG SETUP REQUEST) message or an NG setup response (NG SETUP RESPONSE) message or a RAN configuration update (RAN CONFIGURATION UPDATE) message of NG. UPDATE) message or RAN Configuration Update Acknowledge (RAN CONFIGURATION UPDATE ACKNOWLEDGE) message or AMF Configuration Update (AMF CONFIGURATION UPDATE) message or AMF Configuration Update Acknowledge (AMF CONFIGURATION UPDATE ACKNOWLEDGE) message or AMF Status Indication (AMF STATUS INDICATION) message or Overload Start (OVERLOAD START) message or Overload Stop (OVERLOAD STOP) message or Handover Required (HANDOVER REQUIRED) message or Handover Command (HANDOVER COMMAND) message or Handover Request (HANDOVER REQUEST) message or Handover Request Acknowledge (HANDOVER REQUEST ACKNOWLEDGE) message or Uplink RAN ​​Configuration Transfer (UPLINK RAN CONFIGURATION TRANSFER) message or Downlink RAN ​​Configuration Transfer (DOWNLINK RAN CONFIGURATION TRANSFER) message;or F1 SETUP REQUEST message or F1 SETUP RESPONSE message or gNB-DU CONFIGURATION UPDATE message or gNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message or gNB-CU CONFIGURATION UPDATE message or gNB-CUCONFIGURATION UPDATE ACKNOWLEDGE message or gNB-DU STATUSINDICATION message or RESOURCE STATUS REQUEST message or RESOURCE STATUS RESPONSE message or RESOURCE STATUS FAILURE message or RESOURCE STATUS UPDATE message UE CONTEXT SETUP REQUEST message or RESOURCE STATUS RESPONSE message or RESOURCE STATUS FAILURE message or RESOURCE STATUS UPDATE message UE CONTEXT SETUP REQUEST) message or UE CONTEXT SETUP RESPONSE message or UE CONTEXT RELEASE REQUEST message or UE CONTEXT RELEASE COMMAND message or UE CONTEXT RELEASE COMPLETE message or UE CONTEXT MODIFICATION REQUEST message or UE CONTEXT MODIFICATION RESPONSE message or UE CONTEXT MODIFICATION REQUIRED message or UE CONTEXT MODIFICATION CONFIRM message;or gNB CU UP E1 SETUP REQUEST message of E1 or gNB CU UP E1 SETUP RESPONSE message or gNB CU CP E1 SETUP REQUEST message or gNB CU CP E1 SETUP RESPONSE message or gNB CUUP CONFIGURATION UPDATE message or gNB CU UP CONFIGURATION UPDATE ACKNOWLEDGE message or gNB CU CP CONFIGURATION UPDATE ACKNOWLEDGE message or gNB CU UP status indication (GNB-CU-UP STATUS INDICATION) message or Resource status request (RESOURCE STATUS REQUEST) message or Resource status response (RESOURCE STATUSRESPONSE) message or Resource status failure (RESOURCE STATUS FAILURE) message or Resource status update (RESOURCE STATUS UPDATE) message Bearer context setup request (BEARER CONTEXT SETUP REQUEST) message or Bearer context setup response (BEARER CONTEXT SETUP RESPONSE) message or Bearer context modification request (BEARER CONTEXT MODIFICATION REQUEST) message or Bearer context modification response (BEARERCONTEXTMODIFICATION RESPONSE) message or Bearer context modification required (BEARERCONTEXTMODIFICATION REQUIRED) message or BearerCONTEXTMODIFICATIONCONFIRM message or BearerCONTEXTRELEASECOMMAND message or BearerCONTEXTRELEASECOMMAND message CONTEXT RELEASE COMPLETE) message or bearer context release request (BEARERCONTEXT RELEASE REQUEST) message;or RRC reconfiguration (RRCReconfiguration) message or RRC recovery (RRCResume) message or RRC reconstruction (RRCReestablishment) message or RRC establishment (RRCSetup) message or RRC reconfiguration complete (RRCReconfigurationComplete) message or RRC recovery complete (RRCResumeComplete) message or RRC reconstruction complete (RRCReestablishmentComplete) message or RRC establishment complete (RRCSetupComplete) message; it can also be sent in the form of MAC CE; or another and / or newly defined RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message and / or RRC container, etc.;

[0283] In some implementations, the eleventh message may include one or more of the following fields or related information:

[0284] Sending node ID: used to identify the node that sends the message.

[0285] Receiving node ID: used to identify the node that receives the message.

[0286] Measurement ID: used to identify the measurement.

[0287] Request ID: used to identify this request.

[0288] Slice resource usage request identifier: used to indicate a request for slice resource usage.

[0289] Slice ID: used to identify the slice corresponding to the slice resource usage request.

[0290] · Scope of requested report: used to indicate the scope of requested report, where the scope may be one or more of the following identifiers and / or identifier lists: slice, service, scenario, node, UE, cell, beam, channel, protocol data unit session (Protocol Data Unit Session), data radio bearer (Data Radio Bearers, DRB), QoS flow, QoS level, etc. Identifiers and / or identifier lists, etc. The service may be a service type, quality of service (Quality of Service, QoS), scenario, etc. The service type may include one or more of the following: voice service, video service, virtual reality service, augmented reality service, call service, etc. The service quality may include one or more of the following: latency, throughput, reliability, packet loss rate, data rate, etc., which may be identified by a 5G service quality indicator (5G QoS Identifier, 5QI), a service quality level indicator (QoS Class Identifier, QCI), etc. The scenarios may include one or more of the following: Ultra-reliable and Low Latency Communications (URLLC), Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC), etc.

[0291] · Reporting method of requested slice resource usage: used to indicate the reporting method of requested slice resource usage, which can include single reporting, periodic reporting, on-demand reporting, event-triggered reporting, etc.

[0292] · Requested slice resource usage reporting period: used to indicate the interval for periodic reporting of the requested slice resource usage. The reporting period can also be the reporting time of the reported data. If there is no content in this field, it means that a single report is sufficient, and the single reporting time is from the start time to the end time of the report.

[0293] Slice resource usage reporting time: used to indicate the time point and / or time interval for reporting slice resource usage. The time can be relative or absolute. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a time interval, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits represent the start time, and the last n bits represent the end time. It can also be represented by a separate field, including one or more of the following:

[0294] o Start time: used to indicate the start time of the reporting time. The start time can be a relative time or an absolute time.

[0295] End time: used to indicate the end time of the reporting time. The end time can be a relative time or an absolute time.

[0296] Slice resource usage measurement time: used to indicate the time point and / or time interval for measuring slice resource usage. The time can be relative or absolute. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a time interval, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits represent the start time, and the last n bits represent the end time. It can also be represented by a separate field, including one or more of the following:

[0297] oStart time: used to indicate the start time of the measurement time. The start time can be a relative time or an absolute time.

[0298] ο End time: used to indicate the end time of the measurement time. The end time can be a relative time or an absolute time.

[0299] Applicable time corresponding to the requested slice resource usage: used to indicate the applicable time point and / or time interval corresponding to the requested slice resource usage report. The time can be a relative time or an absolute time. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a time interval, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits represent the start time, and the last n bits represent the end time. It can also be represented by a separate field, including one or more of the following:

[0300] o Start time: used to indicate the start time of the applicable time. The start time can be a relative time or an absolute time.

[0301] ο End time: used to indicate the end time of the applicable time. The end time can be a relative time or an absolute time.

[0302] ·Conditions and / or events triggering reporting: When the conditions and / or events triggering reporting are met, reporting is performed. The conditions and / or events triggering reporting may include one or more of the following:

[0303] o When the proportion of actually used resources to allocated resources is greater than and / or equal to and / or less than a predetermined threshold. The condition and / or event should include an event, event type, predefined threshold, time information of meeting the condition, etc. For example, reporting is performed only when the time actually meeting the condition meets the configured time information of meeting the condition.

[0304] Request content: may include one or more of the following:

[0305] οAmount of dedicated resources actually used: The actual amount of dedicated resources used may include one or more of the following: the proportion of dedicated resources actually used to the allocated dedicated resources, the starting position of dedicated resources actually used, the ending position of dedicated resources actually used, the resource size of dedicated resources actually used, the proportion of dedicated resources actually used, etc.

[0306] οAmount of priority resources actually used: The actual amount of priority resources used may include one or more of the following: the proportion of priority resources actually used to the allocated priority resources, the starting position of priority resources actually used, the ending position of priority resources actually used, the resource size of priority resources actually used, the proportion of priority resources actually used, etc.

[0307] οActual amount of shared resources used: The actual amount of shared resources used may include one or more of the following: the proportion of shared resources actually used to the allocated shared resources, the starting position of shared resources actually used, the ending position of shared resources actually used, the resource size of shared resources actually used, the proportion of shared resources actually used, etc.

[0308] ο Slice performance: may include one or more of the following: QoS parameters, QoE parameters, etc.

[0309] o Service type corresponding to the slice: The service type may include one or more of the following: service type, quality of service (QoS), scenario, etc. The service type may include one or more of the following: voice service, video service, virtual reality service, augmented reality service, call service, etc. The quality of service may include one or more of the following: latency, throughput, reliability, packet loss rate, data rate, etc., which may be identified by 5G service quality indication (5G QoS Identifier, 5QI), service quality level indication (QoS Class Identifier, QCI), etc. The scenario may include one or more of the following: Ultra-reliable and Low Latency Communications (URLLC), Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC), etc.

[0310] In some implementations, the twelfth node sends a twelfth message containing slice resource usage to the eleventh node according to its own situation and / or based on the eleventh message containing a slice resource usage request received from the eleventh node. The twelfth node can send the slice resource usage to the eleventh node, and the eleventh node can use the information to evaluate whether its resource allocation decision is reasonable. For example, if the occupancy rate of the priority resource is high, it means that the decision is inappropriate, for example, the use of other slice shared resources cannot be guaranteed. It can also be that the eleventh node sets the slice resource allocation decision according to the slice resource usage. For example, if the occupancy rate of the priority resource is high, the priority resource can be set as a dedicated resource to guarantee the use of other slice shared resources.

[0311] In some embodiments, the twelfth message may be included in one or more of the following: a resource status request (RESOURCE STATUS REQUEST) message or a resource status response (RESOURCE STATUS RESPONSE) message or a resource status failure (RESOURCE STATUS FAILURE) message or a resource status update (RESOURCE STATUSUPDATE) message or a handover request confirmation (HANDOVER REQUEST ACKNOWLEDGE) message or a handover request (HANDOVER REQUEST) message or an NG-RAN node configuration update (NG-RAN NODE CONFIGURATION UPDATE) message or an NG-RAN node configuration update confirmation (NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE) message or an Xn setup request (XN SETUP REQUEST) message or an Xn setup response (XN SETUP RESPONSE) message of NG; an NG setup request (NG SETUP REQUEST) message or an NG setup response (NG SETUP RESPONSE) message or a RAN configuration update (RAN CONFIGURATION UPDATE) message of NG. UPDATE) message or RAN Configuration Update Acknowledge (RAN CONFIGURATION UPDATE ACKNOWLEDGE) message or AMF Configuration Update (AMF CONFIGURATION UPDATE) message or AMF Configuration Update Acknowledge (AMF CONFIGURATION UPDATE ACKNOWLEDGE) message or AMF Status Indication (AMF STATUS INDICATION) message or Overload Start (OVERLOAD START) message or Overload Stop (OVERLOAD STOP) message or Handover Required (HANDOVER REQUIRED) message or Handover Command (HANDOVER COMMAND) message or Handover Request (HANDOVER REQUEST) message or Handover Request Acknowledge (HANDOVER REQUEST ACKNOWLEDGE) message or Uplink RAN ​​Configuration Transfer (UPLINK RAN CONFIGURATION TRANSFER) message or Downlink RAN ​​Configuration Transfer (DOWNLINK RAN CONFIGURATION TRANSFER) message;or F1 SETUP REQUEST message or F1 SETUP RESPONSE message or gNB-DU CONFIGURATION UPDATE message or gNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message or gNB-CU CONFIGURATION UPDATE message or gNB-CUCONFIGURATION UPDATE ACKNOWLEDGE message or gNB-DU STATUSINDICATION message or RESOURCE STATUS REQUEST message or RESOURCE STATUS RESPONSE message or RESOURCE STATUS FAILURE message or RESOURCE STATUS UPDATE message UE CONTEXT SETUP REQUEST message or RESOURCE STATUS RESPONSE message or RESOURCE STATUS FAILURE message or RESOURCE STATUS UPDATE message UE CONTEXT SETUP REQUEST) message or UE CONTEXT SETUP RESPONSE message or UE CONTEXT RELEASE REQUEST message or UE CONTEXT RELEASE COMMAND message or UE CONTEXT RELEASE COMPLETE message or UE CONTEXT MODIFICATION REQUEST message or UE CONTEXT MODIFICATION RESPONSE message or UE CONTEXT MODIFICATION REQUIRED message or UE CONTEXT MODIFICATION CONFIRM message;or gNB CU UP E1 SETUP REQUEST message of E1 or gNB CU UP E1 SETUP RESPONSE message or gNB CU CP E1 SETUP REQUEST message or gNB CU CP E1 SETUP RESPONSE message or gNB CUUP CONFIGURATION UPDATE message or gNB CU UP CONFIGURATION UPDATE ACKNOWLEDGE message or gNB CU CP CONFIGURATION UPDATE ACKNOWLEDGE message or gNB CU UP status indication (GNB-CU-UP STATUS INDICATION) message or Resource status request (RESOURCE STATUS REQUEST) message or Resource status response (RESOURCE STATUSRESPONSE) message or Resource status failure (RESOURCE STATUS FAILURE) message or Resource status update (RESOURCE STATUS UPDATE) message Bearer context setup request (BEARER CONTEXT SETUP REQUEST) message or Bearer context setup response (BEARER CONTEXT SETUP RESPONSE) message or Bearer context modification request (BEARER CONTEXT MODIFICATION REQUEST) message or Bearer context modification response (BEARERCONTEXTMODIFICATION RESPONSE) message or Bearer context modification required (BEARERCONTEXTMODIFICATION REQUIRED) message or BearerCONTEXTMODIFICATIONCONFIRM message or BearerCONTEXTRELEASECOMMAND message or BearerCONTEXTRELEASECOMMAND message CONTEXT RELEASE COMPLETE) message or bearer context release request (BEARERCONTEXT RELEASE REQUEST) message;or RRC reconfiguration (RRCReconfiguration) message or RRC recovery (RRCResume) message or RRC reconstruction (RRCReestablishment) message or RRC establishment (RRCSetup) message or RRC reconfiguration complete (RRCReconfigurationComplete) message or RRC recovery complete (RRCResumeComplete) message or RRC reconstruction complete (RRCReestablishmentComplete) message or RRC establishment complete (RRCSetupComplete) message; it can also be sent in the form of MAC CE; or another and / or newly defined RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message and / or RRC container, etc.;

[0312] In some implementations, the twelfth message may include one or more of the following fields or related information:

[0313] Sending node ID: used to identify the node that sends the message.

[0314] Receiving node ID: used to identify the node that receives the message.

[0315] Measurement identifier: used to identify the measurement. The measurement identifier may be consistent with the measurement identifier in the eleventh message, so as to associate the message with the request message.

[0316] Request ID: used to identify the request corresponding to this report.

[0317] Slice ID: used to identify the slice corresponding to the slice resource usage.

[0318] · Actual use of dedicated resources: indicates the actual amount of dedicated resources used. The actual use of dedicated resources may include one or more of the following: the proportion of dedicated resources actually used to the allocated dedicated resources, the starting position of dedicated resources actually used, the ending position of dedicated resources actually used, the resource size of dedicated resources actually used, the proportion of dedicated resources actually used, etc. Actual use of priority resources: indicates the actual amount of priority resources used. The actual use of priority resources may include one or more of the following: the proportion of priority resources actually used to the allocated priority resources, the starting position of priority resources actually used, the ending position of priority resources actually used, the resource size of priority resources actually used, the proportion of priority resources actually used, etc.

[0319] · Actual used shared resources: indicates the actual amount of shared resources used. The actual amount of shared resources used may include one or more of the following: the proportion of actually used shared resources to the allocated shared resources, the starting position of actually used shared resources, the ending position of actually used shared resources, the resource size of actually used shared resources, the proportion of actually used shared resources, etc.

[0320] Slice performance: indicates the performance of the service transmitted on the slice. It may include one or more of the following: QoS parameters, QoE parameters, etc.

[0321] ·Service type corresponding to the slice: The service may be a service type, quality of service (QoS), scenario, etc. The service type may include one or more of the following: voice service, video service, virtual reality service, augmented reality service, call service, etc. The quality of service may include one or more of the following: latency, throughput, reliability, packet loss rate, data rate, etc., which may be identified by 5G QoS Identifier (5QI), QoS Class Identifier (QCI), etc. The scenario may include one or more of the following: Ultra-reliable and Low Latency Communications (URLLC), Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC), etc.

[0322] Applicable time corresponding to slice resource usage: used to indicate the applicable time point and / or time interval corresponding to the reported slice resource usage. The time can be a relative time or an absolute time. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a time interval, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits represent the start time, and the last n bits represent the end time. It can also be represented by a separate field, including one or more of the following:

[0323] o Start time: used to indicate the start time of the applicable time. The start time can be a relative time or an absolute time.

[0324] ο End time: used to indicate the end time of the applicable time. The end time can be a relative time or an absolute time.

[0325] The conditions and / or events that trigger the report: The conditions and / or events that trigger the report may include one or more of the following:

[0326] o When the proportion of actually used resources to allocated resources is greater than and / or equal to and / or less than a predetermined threshold. The condition and / or event should include an event, event type, predefined threshold, time information of meeting the condition, etc. For example, reporting is performed only when the time actually meeting the condition meets the configured time information of meeting the condition.

[0327] Example 8

[0328] An embodiment of the present disclosure provides a method for supporting slicing, which may include: a thirteenth node sends a thirteenth message including a slice support information request to a fourteenth node, for requesting the fourteenth node to report the slice support information. The thirteenth node obtains the slice support information of the fourteenth node, and may make relevant decisions based on the slice support information, such as SON-related decisions, selecting a target node, whether to request slice prediction information, etc.

[0329] In some embodiments, the thirteenth message may be included in one or more of the following: a resource status request (RESOURCE STATUS REQUEST) message or a resource status response (RESOURCE STATUS RESPONSE) message or a resource status failure (RESOURCE STATUS FAILURE) message or a resource status update (RESOURCE STATUSUPDATE) message or a handover request confirmation (HANDOVER REQUEST ACKNOWLEDGE) message or a handover request (HANDOVER REQUEST) message or an NG-RAN node configuration update (NG-RAN NODE CONFIGURATION UPDATE) message or an NG-RAN node configuration update confirmation (NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE) message or an Xn setup request (XN SETUP REQUEST) message or an Xn setup response (XN SETUP RESPONSE) message of NG; an NG setup request (NG SETUP REQUEST) message or an NG setup response (NG SETUP RESPONSE) message or a RAN configuration update (RAN CONFIGURATION UPDATE) message of NG. UPDATE) message or RAN Configuration Update Acknowledge (RAN CONFIGURATION UPDATE ACKNOWLEDGE) message or AMF Configuration Update (AMF CONFIGURATION UPDATE) message or AMF Configuration Update Acknowledge (AMF CONFIGURATION UPDATE ACKNOWLEDGE) message or AMF Status Indication (AMF STATUS INDICATION) message or Overload Start (OVERLOAD START) message or Overload Stop (OVERLOAD STOP) message or Handover Required (HANDOVER REQUIRED) message or Handover Command (HANDOVER COMMAND) message or Handover Request (HANDOVER REQUEST) message or Handover Request Acknowledge (HANDOVER REQUEST ACKNOWLEDGE) message or Uplink RAN ​​Configuration Transfer (UPLINK RAN CONFIGURATION TRANSFER) message or Downlink RAN ​​Configuration Transfer (DOWNLINK RAN CONFIGURATION TRANSFER) message;or F1 SETUP REQUEST message or F1 SETUP RESPONSE message or gNB-DU CONFIGURATION UPDATE message or gNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message or gNB-CU CONFIGURATION UPDATE message or gNB-CUCONFIGURATION UPDATE ACKNOWLEDGE message or gNB-DU STATUSINDICATION message or RESOURCE STATUS REQUEST message or RESOURCE STATUS RESPONSE message or RESOURCE STATUS FAILURE message or RESOURCE STATUS UPDATE message UE CONTEXT SETUP REQUEST message or RESOURCE STATUS RESPONSE message or RESOURCE STATUS FAILURE message or RESOURCE STATUS UPDATE message UE CONTEXT SETUP REQUEST) message or UE CONTEXT SETUP RESPONSE message or UE CONTEXT RELEASE REQUEST message or UE CONTEXT RELEASE COMMAND message or UE CONTEXT RELEASE COMPLETE message or UE CONTEXT MODIFICATION REQUEST message or UE CONTEXT MODIFICATION RESPONSE message or UE CONTEXT MODIFICATION REQUIRED message or UE CONTEXT MODIFICATION CONFIRM message;or gNB CU UP E1 SETUP REQUEST message of E1 or gNB CU UP E1 SETUP RESPONSE message or gNB CU CP E1 SETUP REQUEST message or gNB CU CP E1 SETUP RESPONSE message or gNB CUUP CONFIGURATION UPDATE message or gNB CU UP CONFIGURATION UPDATE ACKNOWLEDGE message or gNB CU CP CONFIGURATION UPDATE ACKNOWLEDGE message or gNB CU UP status indication (GNB-CU-UP STATUS INDICATION) message or Resource status request (RESOURCE STATUS REQUEST) message or Resource status response (RESOURCE STATUSRESPONSE) message or Resource status failure (RESOURCE STATUS FAILURE) message or Resource status update (RESOURCE STATUS UPDATE) message Bearer context setup request (BEARER CONTEXT SETUP REQUEST) message or Bearer context setup response (BEARER CONTEXT SETUP RESPONSE) message or Bearer context modification request (BEARER CONTEXT MODIFICATION REQUEST) message or Bearer context modification response (BEARERCONTEXTMODIFICATION RESPONSE) message or Bearer context modification required (BEARERCONTEXTMODIFICATION REQUIRED) message or BearerCONTEXTMODIFICATIONCONFIRM message or BearerCONTEXTRELEASECOMMAND message or BearerCONTEXTRELEASECOMMAND message CONTEXT RELEASE COMPLETE) message or bearer context release request (BEARERCONTEXT RELEASE REQUEST) message;or RRC reconfiguration (RRCReconfiguration) message or RRC recovery (RRCResume) message or RRC reconstruction (RRCReestablishment) message or RRC establishment (RRCSetup) message or RRC reconfiguration complete (RRCReconfigurationComplete) message or RRC recovery complete (RRCResumeComplete) message or RRC reconstruction complete (RRCReestablishmentComplete) message or RRC establishment complete (RRCSetupComplete) message; it can also be sent in the form of MAC CE; or another and / or newly defined RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message and / or RRC container, etc. In some embodiments, the thirteenth message may include one or more of the following fields or related information:;

[0330] Sending node ID: used to identify the node that sends the message.

[0331] Receiving node ID: used to identify the node that receives the message.

[0332] Content of the slice support information request: may include one or more of the following:

[0333] o Slice information supported by the cell: used to indicate the slice information supported by the cell. It may include a cell identifier, supported slice identifiers, etc. The cell may be a cell included in the node, a source cell and / or a target cell in handover, or an alternative target cell in handover (also referred to as an alternative cell).

[0334] o Information on slice prediction support: used to indicate whether slice prediction can be performed. This field can be represented by a single bit. For example, if the bit is 1, it indicates that slice prediction is supported, that is, slice prediction can be performed, and if the bit is 0, it indicates that slice prediction is not supported, that is, slice prediction cannot be performed; or if the bit is 0, it indicates that slice prediction is supported, that is, slice prediction can be performed, and if the bit is 1, it indicates that slice prediction is not supported, that is, slice prediction cannot be performed.

[0335] οCell identifier: used to indicate the cell corresponding to the slice.

[0336] In some embodiments, the fourteenth node may send a fourteenth message containing slice support information to the thirteenth node based on its own situation and / or based on the thirteenth message containing a slice support information request received from the thirteenth node. The fourteenth node may send the slice support information to the thirteenth node, and the thirteenth node may use the information for decision making, for example, SON-related decisions, selecting a target node, whether to request slice prediction information, etc.

[0337] In some embodiments, the fourteenth message may be included in one or more of the following: a resource status request (RESOURCE STATUS REQUEST) message or a resource status response (RESOURCE STATUS RESPONSE) message or a resource status failure (RESOURCE STATUS FAILURE) message or a resource status update (RESOURCE STATUSUPDATE) message or a handover request confirmation (HANDOVER REQUEST ACKNOWLEDGE) message or a handover request (HANDOVER REQUEST) message or an NG-RAN node configuration update (NG-RAN NODE CONFIGURATION UPDATE) message or an NG-RAN node configuration update confirmation (NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE) message or an Xn setup request (XN SETUP REQUEST) message or an Xn setup response (XN SETUP RESPONSE) message of NG; an NG setup request (NG SETUP REQUEST) message or an NG setup response (NG SETUP RESPONSE) message or a RAN configuration update (RAN CONFIGURATION UPDATE) message of NG. UPDATE) message or RAN Configuration Update Acknowledge (RAN CONFIGURATION UPDATE ACKNOWLEDGE) message or AMF Configuration Update (AMF CONFIGURATION UPDATE) message or AMF Configuration Update Acknowledge (AMF CONFIGURATION UPDATE ACKNOWLEDGE) message or AMF Status Indication (AMF STATUS INDICATION) message or Overload Start (OVERLOAD START) message or Overload Stop (OVERLOAD STOP) message or Handover Required (HANDOVER REQUIRED) message or Handover Command (HANDOVER COMMAND) message or Handover Request (HANDOVER REQUEST) message or Handover Request Acknowledge (HANDOVER REQUEST ACKNOWLEDGE) message or Uplink RAN ​​Configuration Transfer (UPLINK RAN CONFIGURATION TRANSFER) message or Downlink RAN ​​Configuration Transfer (DOWNLINK RAN CONFIGURATION TRANSFER) message;or F1 SETUP REQUEST message or F1 SETUP RESPONSE message or gNB-DU CONFIGURATION UPDATE message or gNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message or gNB-CU CONFIGURATION UPDATE message or gNB-CUCONFIGURATION UPDATE ACKNOWLEDGE message or gNB-DU STATUSINDICATION message or RESOURCE STATUS REQUEST message or RESOURCE STATUS RESPONSE message or RESOURCE STATUS FAILURE message or RESOURCE STATUS UPDATE message UE CONTEXT SETUP REQUEST message or RESOURCE STATUS RESPONSE message or RESOURCE STATUS FAILURE message or RESOURCE STATUS UPDATE message UE CONTEXT SETUP REQUEST) message or UE CONTEXT SETUP RESPONSE message or UE CONTEXT RELEASE REQUEST message or UE CONTEXT RELEASE COMMAND message or UE CONTEXT RELEASE COMPLETE message or UE CONTEXT MODIFICATION REQUEST message or UE CONTEXT MODIFICATION RESPONSE message or UE CONTEXT MODIFICATION REQUIRED message or UE CONTEXT MODIFICATION CONFIRM message;or gNB CU UP E1 SETUP REQUEST message of E1 or gNB CU UP E1 SETUP RESPONSE message or gNB CU CP E1 SETUP REQUEST message or gNB CU CP E1 SETUP RESPONSE message or gNB CUUP CONFIGURATION UPDATE message or gNB CU UP CONFIGURATION UPDATE ACKNOWLEDGE message or gNB CU CP CONFIGURATION UPDATE ACKNOWLEDGE message or gNB CU UP status indication (GNB-CU-UP STATUS INDICATION) message or Resource status request (RESOURCE STATUS REQUEST) message or Resource status response (RESOURCE STATUSRESPONSE) message or Resource status failure (RESOURCE STATUS FAILURE) message or Resource status update (RESOURCE STATUS UPDATE) message Bearer context setup request (BEARER CONTEXT SETUP REQUEST) message or Bearer context setup response (BEARER CONTEXT SETUP RESPONSE) message or Bearer context modification request (BEARER CONTEXT MODIFICATION REQUEST) message or Bearer context modification response (BEARERCONTEXTMODIFICATION RESPONSE) message or Bearer context modification required (BEARERCONTEXTMODIFICATION REQUIRED) message or BearerCONTEXTMODIFICATIONCONFIRM message or BearerCONTEXTRELEASECOMMAND message or BearerCONTEXTRELEASECOMMAND message CONTEXT RELEASE COMPLETE) message or bearer context release request (BEARERCONTEXT RELEASE REQUEST) message;or RRC reconfiguration (RRCReconfiguration) message or RRC recovery (RRCResume) message or RRC reconstruction (RRCReestablishment) message or RRC establishment (RRCSetup) message or RRC reconfiguration complete (RRCReconfigurationComplete) message or RRC recovery complete (RRCResumeComplete) message or RRC reconstruction complete (RRCReestablishmentComplete) message or RRC establishment complete (RRCSetupComplete) message; it can also be sent in the form of MAC CE; or another and / or newly defined RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message and / or RRC container, etc. In some embodiments, the fourteenth message may include one or more of the following fields or related information:;

[0338] Sending node ID: used to identify the node that sends the message.

[0339] Receiving node ID: used to identify the node that receives the message.

[0340] Slice information supported by the cell: used to indicate the slice information supported by the cell. It may include a cell identifier, supported slice identifiers, etc. The cell may be a cell included in the node, a source cell and / or a target cell in handover, or a candidate target cell in handover (also referred to as a candidate cell).

[0341] Information on slice prediction support: used to indicate whether slice prediction can be performed. This field can be represented by a single bit. For example, if the bit is 1, it indicates that slice prediction is supported, that is, slice prediction can be performed; if the bit is 0, it indicates that slice prediction is not supported, that is, slice prediction cannot be performed; or if the bit is 0, it indicates that slice prediction is supported, that is, slice prediction can be performed.

[0342] This bit being 1 indicates that slice prediction is not supported, that is, slice prediction cannot be performed.

[0343] Cell ID: used to indicate the cell to which the slice corresponds.

[0344] Example 9

[0345] An embodiment of the present disclosure proposes a method for supporting slicing, which may include: a fifteenth node sends a fifteenth message containing an applicable time of a remapping decision to a sixteenth node, so as to inform the sixteenth node of the applicable time of the remapping decision, and the sixteenth node applies the remapping decision only within the applicable time.

[0346] In some embodiments, the fifteenth message may be included in one or more of the following: a resource status request (RESOURCE STATUS REQUEST) message or a resource status response (RESOURCE STATUS RESPONSE) message or a resource status failure (RESOURCE STATUS FAILURE) message or a resource status update (RESOURCE STATUSUPDATE) message or a handover request confirmation (HANDOVER REQUEST ACKNOWLEDGE) message or a handover request (HANDOVER REQUEST) message or an NG-RAN node configuration update (NG-RAN NODE CONFIGURATION UPDATE) message or an NG-RAN node configuration update confirmation (NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE) message or an Xn setup request (XN SETUP REQUEST) message or an Xn setup response (XN SETUP RESPONSE) message of NG; an NG setup request (NG SETUP REQUEST) message or an NG setup response (NG SETUP RESPONSE) message or a RAN configuration update (RAN CONFIGURATION UPDATE) message of NG. UPDATE) message or RAN Configuration Update Acknowledge (RAN CONFIGURATION UPDATE ACKNOWLEDGE) message or AMF Configuration Update (AMF CONFIGURATION UPDATE) message or AMF Configuration Update Acknowledge (AMF CONFIGURATION UPDATE ACKNOWLEDGE) message or AMF Status Indication (AMF STATUS INDICATION) message or Overload Start (OVERLOAD START) message or Overload Stop (OVERLOAD STOP) message or Handover Required (HANDOVER REQUIRED) message or Handover Command (HANDOVER COMMAND) message or Handover Request (HANDOVER REQUEST) message or Handover Request Acknowledge (HANDOVER REQUEST ACKNOWLEDGE) message or Uplink RAN ​​Configuration Transfer (UPLINK RAN CONFIGURATION TRANSFER) message or Downlink RAN ​​Configuration Transfer (DOWNLINK RAN CONFIGURATION TRANSFER) message;or F1 SETUP REQUEST message or F1 SETUP RESPONSE message or gNB-DU CONFIGURATION UPDATE message or gNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message or gNB-CU CONFIGURATION UPDATE message or gNB-CUCONFIGURATION UPDATE ACKNOWLEDGE message or gNB-DU STATUSINDICATION message or RESOURCE STATUS REQUEST message or RESOURCE STATUS RESPONSE message or RESOURCE STATUS FAILURE message or RESOURCE STATUS UPDATE message UE CONTEXT SETUP REQUEST message or RESOURCE STATUS RESPONSE message or RESOURCE STATUS FAILURE message or RESOURCE STATUS UPDATE message UE CONTEXT SETUP REQUEST) message or UE CONTEXT SETUP RESPONSE message or UE CONTEXT RELEASE REQUEST message or UE CONTEXT RELEASE COMMAND message or UE CONTEXT RELEASE COMPLETE message or UE CONTEXT MODIFICATION REQUEST message or UE CONTEXT MODIFICATION RESPONSE message or UE CONTEXT MODIFICATION REQUIRED message or UE CONTEXT MODIFICATION CONFIRM message;or gNB CU UP E1 SETUP REQUEST message of E1 or gNB CU UP E1 SETUP RESPONSE message or gNB CU CP E1 SETUP REQUEST message or gNB CU CP E1 SETUP RESPONSE message or gNB CUUP CONFIGURATION UPDATE message or gNB CU UP CONFIGURATION UPDATE ACKNOWLEDGE message or gNB CU CP CONFIGURATION UPDATE ACKNOWLEDGE message or gNB CU UP status indication (GNB-CU-UP STATUS INDICATION) message or Resource status request (RESOURCE STATUS REQUEST) message or Resource status response (RESOURCE STATUSRESPONSE) message or Resource status failure (RESOURCE STATUS FAILURE) message or Resource status update (RESOURCE STATUS UPDATE) message Bearer context setup request (BEARER CONTEXT SETUP REQUEST) message or Bearer context setup response (BEARER CONTEXT SETUP RESPONSE) message or Bearer context modification request (BEARER CONTEXT MODIFICATION REQUEST) message or Bearer context modification response (BEARERCONTEXTMODIFICATION RESPONSE) message or Bearer context modification required (BEARERCONTEXTMODIFICATION REQUIRED) message or BearerCONTEXTMODIFICATIONCONFIRM message or BearerCONTEXTRELEASECOMMAND message or BearerCONTEXTRELEASECOMMAND message CONTEXT RELEASE COMPLETE) message or bearer context release request (BEARERCONTEXT RELEASE REQUEST) message;or RRC reconfiguration (RRCReconfiguration) message or RRC recovery (RRCResume) message or RRC reconstruction (RRCReestablishment) message or RRC establishment (RRCSetup) message or RRC reconfiguration complete (RRCReconfigurationComplete) message or RRC recovery complete (RRCResumeComplete) message or RRC reconstruction complete (RRCReestablishmentComplete) message or RRC establishment complete (RRCSetupComplete) message; it can also be sent in the form of MAC CE; or another and / or newly defined RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message and / or RRC container, etc.;

[0347] The fifteenth message may include one or more of the following fields or related information:

[0348] Sending node ID: used to identify the node that sends the message.

[0349] Receiving node ID: used to identify the node that receives the message.

[0350] Remapping decision: The remapping decision may include one or more of the following:

[0351] ο Slice ID: used to indicate the source slice information in the remapping decision.

[0352] οRemapped slice identifier: used to represent the slice identifier to be remapped in the remapping decision.

[0353] Applicable time of remapping decision: used to indicate the applicable time point and / or time interval corresponding to the remapping decision. The time can be relative time or absolute time. The time interval can be represented by a timer, a combination of start time and end time, a combination of start time and time interval, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits represent the start time, and the last n bits represent the end time. It can also be represented by a separate field, including one or more of the following:

[0354] o Start time: used to indicate the start time of the applicable time. The start time can be a relative time or an absolute time.

[0355] ο End time: used to indicate the end time of the applicable time. The end time can be a relative time or an absolute time.

[0356] Example 10

[0357] An embodiment of the present disclosure proposes a method for supporting slicing, which may include: a seventeenth node sends a sixteenth message containing experience quality parameters to an eighteenth node, so as to inform the eighteenth node of the experience quality parameters of one or more users, and the eighteenth node may refer to the information when making resource allocation and / or switching decisions to ensure the user's experience quality parameters.

[0358] In some embodiments, the sixteenth message may be included in one or more of the following: a resource status request (RESOURCE STATUS REQUEST) message or a resource status response (RESOURCE STATUS RESPONSE) message or a resource status failure (RESOURCE STATUS FAILURE) message or a resource status update (RESOURCE STATUSUPDATE) message or a handover request confirmation (HANDOVER REQUEST ACKNOWLEDGE) message or a handover request (HANDOVER REQUEST) message or an NG-RAN node configuration update (NG-RAN NODE CONFIGURATION UPDATE) message or an NG-RAN node configuration update confirmation (NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE) message or an Xn setup request (XN SETUP REQUEST) message or an Xn setup response (XN SETUP RESPONSE) message of NG; an NG setup request (NG SETUP REQUEST) message or an NG setup response (NG SETUP RESPONSE) message or a RAN configuration update (RAN CONFIGURATION UPDATE) message of NG. UPDATE) message or RAN Configuration Update Acknowledge (RAN CONFIGURATION UPDATE ACKNOWLEDGE) message or AMF Configuration Update (AMF CONFIGURATION UPDATE) message or AMF Configuration Update Acknowledge (AMF CONFIGURATION UPDATE ACKNOWLEDGE) message or AMF Status Indication (AMF STATUS INDICATION) message or Overload Start (OVERLOAD START) message or Overload Stop (OVERLOAD STOP) message or Handover Required (HANDOVER REQUIRED) message or Handover Command (HANDOVER COMMAND) message or Handover Request (HANDOVER REQUEST) message or Handover Request Acknowledge (HANDOVER REQUEST ACKNOWLEDGE) message or Uplink RAN ​​Configuration Transfer (UPLINK RAN CONFIGURATION TRANSFER) message or Downlink RAN ​​Configuration Transfer (DOWNLINK RAN CONFIGURATION TRANSFER) message;or F1 SETUP REQUEST message or F1 SETUP RESPONSE message or gNB-DU CONFIGURATION UPDATE message or gNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message or gNB-CU CONFIGURATION UPDATE message or gNB-CUCONFIGURATION UPDATE ACKNOWLEDGE message or gNB-DU STATUSINDICATION message or RESOURCE STATUS REQUEST message or RESOURCE STATUS RESPONSE message or RESOURCE STATUS FAILURE message or RESOURCE STATUS UPDATE message UE CONTEXT SETUP REQUEST message or RESOURCE STATUS RESPONSE message or RESOURCE STATUS FAILURE message or RESOURCE STATUS UPDATE message UE CONTEXT SETUP REQUEST) message or UE CONTEXT SETUP RESPONSE message or UE CONTEXT RELEASE REQUEST message or UE CONTEXT RELEASE COMMAND message or UE CONTEXT RELEASE COMPLETE message or UE CONTEXT MODIFICATION REQUEST message or UE CONTEXT MODIFICATION RESPONSE message or UE CONTEXT MODIFICATION REQUIRED message or UE CONTEXT MODIFICATION CONFIRM message;or gNB CU UP E1 SETUP REQUEST message of E1 or gNB CU UP E1 SETUP RESPONSE message or gNB CU CP E1 SETUP REQUEST message or gNB CU CP E1 SETUP RESPONSE message or gNB CUUP CONFIGURATION UPDATE message or gNB CU UP CONFIGURATION UPDATE ACKNOWLEDGE message or gNB CU CP CONFIGURATION UPDATE ACKNOWLEDGE message or gNB CU UP status indication (GNB-CU-UP STATUS INDICATION) message or Resource status request (RESOURCE STATUS REQUEST) message or Resource status response (RESOURCE STATUSRESPONSE) message or Resource status failure (RESOURCE STATUS FAILURE) message or Resource status update (RESOURCE STATUS UPDATE) message Bearer context setup request (BEARER CONTEXT SETUP REQUEST) message or Bearer context setup response (BEARER CONTEXT SETUP RESPONSE) message or Bearer context modification request (BEARER CONTEXT MODIFICATION REQUEST) message or Bearer context modification response (BEARERCONTEXTMODIFICATION RESPONSE) message or Bearer context modification required (BEARERCONTEXTMODIFICATION REQUIRED) message or BearerCONTEXTMODIFICATIONCONFIRM message or BearerCONTEXTRELEASECOMMAND message or BearerCONTEXTRELEASECOMMAND message CONTEXT RELEASE COMPLETE) message or bearer context release request (BEARERCONTEXT RELEASE REQUEST) message;or RRC reconfiguration (RRCReconfiguration) message or RRC recovery (RRCResume) message or RRC reconstruction (RRCReestablishment) message or RRC establishment (RRCSetup) message or RRC reconfiguration complete (RRCReconfigurationComplete) message or RRC recovery complete (RRCResumeComplete) message or RRC reconstruction complete (RRCReestablishmentComplete) message or RRC establishment complete (RRCSetupComplete) message; it can also be sent in the form of MAC CE; or another and / or newly defined RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message and / or RRC container, etc.;

[0359] The sixteenth message may include one or more of the following fields or related information:

[0360] Sending node ID: used to identify the node that sends the message.

[0361] Receiving node ID: used to identify the node that receives the message.

[0362] User ID: used to identify the user corresponding to the experience quality parameter.

[0363] Experience quality parameter: identifies the experience quality parameter of the user. The experience quality parameter may be a measured experience quality parameter or a predicted experience quality parameter.

[0364] The network self-optimization decision and / or self-optimization network (SON) related decision described in the present disclosure may include network energy saving, load balancing, coverage optimization, mobility optimization and / or management, formulation and / or update of configuration, etc.

[0365] Results and reports may refer to each other in this disclosure.

[0366] In the present disclosure, time may be represented by one or more of the following: timestamp, time point, time interval, timer, time period, time length, time cycle, time interval, etc. The time length may be the time length from a certain time point, and the time point may be the current moment. The time may be a relative time or an absolute time. In some embodiments, the time period may be represented by a separate field, for example, a combination of a start time and an end time, or a combination of a start time and a time period. In the present 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 of switch events, play list, media presentation description information (MPD (Media presentation description) Information), interactivity summary, interactivity event list, etc.

[0367] In the present disclosure, quality of experience (QoE) parameters may be referred to interchangeably with user experience parameters, application layer measurement parameters, and the like.

[0368] In this disclosure, quality of experience may be interchangeable with user experience, application layer measurement, etc.

[0369] In this disclosure, quality of experience measurement may be interchangeably referred to as user experience measurement, application layer measurement, etc.

[0370] In the present disclosure, Quality of Service (QoS) parameters and / or service quality parameters may include at least one of the following: packet loss rate, delay, throughput, data rate, etc. In the present disclosure, QoS parameters may refer to each other with service quality parameters.

[0371] In the present disclosure, the load condition and / or load information may include one or more of the following: PRB usage ratio, the number of available PRBs, the number of allocated PRBs, the usage of scheduled PDCCH CCE, the capacity indication of the transport network layer (Transport Network Layer (TNL)), the radio resource status, the comprehensive available capacity group, the comprehensive available resource group, the number of active user terminals, the number of radio resource control (Radio Resource Control (RRC)) connections, the available capacity of the slice, the hardware capacity indication, the S1 TNL load indication, the hardware load indication, the almost blank subframe (Almost Blank Subframe (ABS)) status, the reference signal received power (Reference Signal Received Power (RSRP)) measurement report list, the reference signal received quality (Reference Signal Receiving Quality (RSRQ)) measurement report, the signal to interference plus noise ratio (Signal to Interference plus Noise Ratio (SINR)) measurement report, the channel state information (Channel State Information (CSI)) report, the cell report indication, the channel occupancy (Channel Occupancy) time ratio, the energy detection (Energy The load condition and load information may include a load detection threshold, signal strength and / or signal quality, channel busy ratio, data volume, and jitter of various content parameters. In the present disclosure, load condition and load information may refer to each other.

[0372] In the present disclosure, applicable time may also be used interchangeably with corresponding time, effective time, or effective time.

[0373] In this disclosure, slices may also refer to businesses, services, etc.

[0374] Exemplary embodiments of the present disclosure are further described below in conjunction with the accompanying drawings.

[0375] The text and drawings are provided as examples only to help understand the present disclosure. They should not be interpreted as limiting the scope of the present disclosure in any way. Although certain embodiments and examples have been provided, it will be apparent to those skilled in the art based on what is disclosed herein that the embodiments and examples shown may be changed without departing from the scope of the present disclosure.

[0376] Figure 3A A schematic diagram of one aspect of a method for supporting slicing according to an embodiment of the present disclosure is shown. Specifically, Figure 3AThe process of interactively predicting slice information between two nodes is shown, so that the second node can make resource allocation and / or switching decisions based on the predicted slice information.

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

[0378] Step 301A: The first node sends predicted slice information to the second node. The predicted slice information may be the aforementioned second message.

[0379] Step 302A: The second node may make resource allocation and / or resource reservation based on the received predicted slice information, or may refer to the predicted slice information when making a switching decision.

[0380] Figure 3B A schematic diagram of one aspect of a method for supporting slicing according to an embodiment of the present disclosure is shown. Specifically, Figure 3B The process of interactively predicting slice information between two nodes is shown, so that the second node can make resource allocation and / or switching decisions based on the predicted slice information.

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

[0382] Step 301B: The second node sends a predicted slice information request to the first node. The predicted slice information request may be the aforementioned first message.

[0383] Step 302B: The first node sends predicted slice information to the second node. The predicted slice information may be the aforementioned second message.

[0384] Step 303B: The second node may make resource allocation and / or resource reservation based on the received predicted slice information, or may refer to the predicted slice information when making a switching decision.

[0385] Figure 3C A schematic diagram of one aspect of a method for supporting slicing according to an embodiment of the present disclosure is shown. Specifically, Figure 3C The process of interactively predicting slice information between the UE and the service node is shown, so that the service node can make resource allocation and / or switching decisions based on the predicted slice information.

[0386] Step 301C: The service node sends a predicted slice information request to the UE. The predicted slice information request may be the aforementioned first message.

[0387] Step 302C: The UE sends predicted slice information to the serving node. The predicted slice information may be the aforementioned second message.

[0388] Step 303C: The service node may make resource allocation and / or resource reservation based on the received predicted slice information, or may refer to the predicted slice information when making a switching decision.

[0389] Step 304C: The UE evaluates the predicted slice information based on subsequent slice conditions (eg, slice conditions that the UE actually accesses later), for example, performance evaluation, accuracy evaluation, etc.

[0390] Figure 3D A schematic diagram of one aspect of a method for supporting slicing according to an embodiment of the present disclosure is shown. Specifically, Figure 3D The process of interactively predicting slice information between the UE, the source node, and the target node is shown, so that the source node can make resource allocation and / or switching decisions based on the predicted slice information, and the target node can make resource allocation and / or subsequent switching decisions based on the predicted slice information.

[0391] Step 301D: The source node sends a predicted slice information request to the UE. The predicted slice information request may be the aforementioned first message.

[0392] Step 302D: The UE sends predicted slice information to the source node. The predicted slice information may be the aforementioned second message.

[0393] Step 303D: The UE sends a measurement report to the source node. In this document, the measurement report may include but is not limited to the RSRP measurement report, RSRQ measurement report, SINR measurement report, etc. as described above.

[0394] Step 304D: The source node makes a handover decision based on the measurement report, the predicted slice information, etc. For example, the source node may select a node that supports the predicted slice as the target node to ensure the stability and robustness of the handover and prevent the UE from needing to reselect a serving cell when the switched target node cannot support a certain slice, resulting in service interruption.

[0395] Step 305D: The source node sends predicted slice information to the target node. The predicted slice information may be the aforementioned second message. The predicted slice information may be carried by the seventeenth message. In some embodiments, the seventeenth message may be a handover request message or any other suitable message, which is not limited herein. In the following, the handover request message is used as an example of the seventeenth message for explanation.

[0396] Step 306D: The target node sends the eighteenth message to the source node. In some implementations, the eighteenth message may be a handover request confirmation message, or any other suitable message, which is not limited herein. In the following, the handover request confirmation message is used as an example of the eighteenth message for description.

[0397] Step 307D: The source node sends the predicted slice information and / or the target cell's support for the slice to the UE. The predicted slice information may be the aforementioned second message. The target cell's support for the slice may include one or more of the following: an identifier of the target cell, a slice identifier and / or an identifier list supported by the target cell, and a priority of the target cell. The target cell's support for the slice may be obtained by the source node from the target cell. The target cell priority may be set according to the target cell's support for the predicted slice information. For example, a cell that supports the predicted slice has a higher priority, wherein the specific priority setting may be that a cell that supports a larger number of predicted slices is set with a higher priority. The predicted slice information and / or the target cell's support for the slice may be carried by the nineteenth message. In some embodiments, the nineteenth message may be an RRC reconfiguration message, or any other suitable message, such as an RRC reestablishment message, etc., which is not limited herein. In the following, the RRC reconfiguration message is described as an example of the nineteenth message. In some embodiments, for example, in conditional switching, the UE may select a cell that supports the predicted slice as the target cell when the execution condition is met based on the predicted slice information and the target cell's support for the slice.

[0398] Step 308D: Perform subsequent switching process.

[0399] Step 309D: The UE evaluates the predicted slice information based on subsequent slice conditions, for example, performance evaluation, accuracy evaluation, etc.

[0400] Figure 3E A schematic diagram of one aspect of a method for supporting slicing according to an embodiment of the present disclosure is shown. Specifically, Figure 3E The process of interactively predicting slice information between the UE, the source node, and the target node is shown, so that the source node can make resource allocation and / or switching decisions based on the predicted slice information, and the target node can make resource allocation and / or subsequent switching decisions based on the predicted slice information.

[0401] Step 301E: The source node sends a slice-related performance request to the target node. The slice-related performance request may be the aforementioned sixth message.

[0402] Step 302E: The target node sends a slice-related performance response to the source node to inform the target node whether it can report slice-related performance. The slice-related performance response may include one or more of the following:

[0403] Sending node ID: used to identify the node that sends the message.

[0404] Receiving node ID: used to identify the node that receives the message.

[0405] Measurement identifier: used to identify the measurement. In some implementations, for example, the measurement identifier may be consistent with the measurement identifier in step 301E, and is used to associate the response message with the request message.

[0406] Slice-related performance request confirmation: used to indicate whether the slice-related performance situation can be measured and / or reported. The slice-related performance situation can be a bit indicating whether the request can be measured and / or reported.

[0407] Measurable content: used to indicate the content that can be measured. The content may include one or more of the following: QoS parameters, QoE parameters, load information, actual slice information, time information, UE identifier, slice identifier, cell identifier, beam identifier, etc. The actual slice information may be the slice information actually accessed, and may include one or more of the following: the slice identifier actually accessed, access time information, departure time information, slice residence time, etc.

[0408] · Scope that can be measured and / or reported: used to indicate the scope that can be measured and / or predicted and / or reported. The scope can be one or more of the following identification representations and / or identification lists: slice, UE, UE that does not perform measurement, UE that performs measurement, etc. The above scope can also represent the slice performance excluding one or more UEs, for example, it can be other users in the slice excluding the switched user, or it can be other users in the slice excluding the user corresponding to the slice remapping.

[0409] · Scope where measurement and / or reporting cannot be performed: used to indicate a scope where measurement and / or prediction and / or reporting cannot be performed. The scope may be one or more of the following identifiers and / or identifier lists: slice, UE, UE that does not perform measurement, UE that performs measurement, etc. The above scope may also indicate the performance of a slice excluding one or more UEs, for example, other users in the slice excluding the user who switches the user, or other users in the slice excluding the user corresponding to the slice remapping.

[0410] Content that cannot be measured: used to indicate content that cannot be measured. The content may include one or more of the following: QoS parameters, QoE parameters, load information, actual slice information, time information, UE identifier, slice identifier, cell identifier, beam identifier, etc. The actual slice information may be the slice information actually accessed, and may include one or more of the following: the slice identifier actually accessed, access time information, departure time information, slice residence time, etc.

[0411] Reason: indicates the reason why measurement and / or reporting cannot be performed. The reason may include one or more of the following: slice unavailable, measurement unavailable, slice load measurement unavailable, slice temporarily unavailable, measurement temporarily unavailable, slice measurement temporarily unavailable, reporting time unavailable, reporting period unavailable, etc.

[0412] Step 303E: The UE sends a measurement report to the source node.

[0413] Step 304E: The source node predicts the slice information, and the source node makes a handover decision based on the measurement report, the predicted slice information, etc. For example, the source node may select a node that supports the predicted slice as the target node to ensure the stability and robustness of the handover, and prevent the UE from needing to reselect a serving cell when the switched target node cannot support a certain slice, resulting in service interruption, etc.

[0414] Step 305E: The source node sends predicted slice information and / or slice performance request indication (also referred to as slice performance request related information in this article) to the target node. The predicted slice information may be the aforementioned second message. The slice performance request indication is used to trigger the target node to collect slice performance. The indication may be the request identifier in the aforementioned sixth message, or the slice performance request indication in the sixth message. The predicted slice information and / or slice performance request indication may be carried by a switching request message. The predicted slice information may be used for making subsequent switching decisions, for example, making switching decisions related to slices, etc.

[0415] Step 306E: The target node sends a handover request confirmation message to the source node.

[0416] Step 307E: The source node sends the predicted slice information and / or the target cell's support for the slice to the UE. The predicted slice information may be the aforementioned second message. The target cell's support for the slice may include one or more of the following: an identifier of the target cell, a slice identifier and / or an identifier list supported by the target cell, a priority of the target cell, a slice identifier and / or an identifier list of the predicted slices (for example, the predicted slices included in the predicted slice information) supported by the target cell, and the number of predicted slices supported by the target cell. The target cell's support for the slice may be the target cell's support for the predicted slices included in the predicted slice information, or it may be the target cell's own slice support capability. The target cell priority may be set according to the target cell's support for the predicted slice information. For example, a cell that supports the predicted slice has a higher priority, wherein the specific priority setting may be that a cell that supports a larger number of predicted slices is set with a higher priority. The predicted slice information and / or the target cell's support for the slice may be carried by an RRC reconfiguration message. In some embodiments, for example, in conditional switching, the UE may select a cell that supports the predicted slice as the target cell when the execution condition is met based on the predicted slice information and the target cell's support for the slice. In some implementations, information such as the priority of the target cell and the number of predicted slices supported by the target cell may be determined by the source node, or may be determined by the target cell itself and sent to the source node.

[0417] Step 308E: Perform subsequent switching process.

[0418] Step 309E: The target node sends the collected (or acquired) slice-related performance to the source node. The slice-related performance may be the seventh message mentioned above.

[0419] Step 310E: The source node evaluates the predicted slice information based on the collected slice-related performance, for example, performance evaluation, accuracy evaluation, etc.

[0420] Figure 3F A schematic diagram of one aspect of a method for supporting slicing according to an embodiment of the present disclosure is shown. Specifically, Figure 3F The process of interactively predicting slice information among UE, source node, target node, and AMF is shown, so that the source node can make resource allocation and / or switching decisions based on the predicted slice information, and the target node can make resource allocation and / or subsequent switching decisions based on the predicted slice information.

[0421] Step 301F: The source node sends a predicted slice information request to the AMF. The predicted slice information request may be the aforementioned first message.

[0422] Step 302F: AMF sends predicted slice information to the source node. The predicted slice information may be the aforementioned second message.

[0423] Step 303F: The UE sends a measurement report to the source node.

[0424] Step 304F: The source node makes a handover decision based on the measurement report, the predicted slice information, etc. For example, the source node may select a node that supports the predicted slice as the target node to ensure the stability and robustness of the handover and prevent the UE from needing to reselect a serving cell when the switched target node cannot support a certain slice, resulting in service interruption, etc.

[0425] Step 305F: The source node sends predicted slice information to the target node. The predicted slice information may be the aforementioned second message. The predicted slice information may be carried by the handover request message.

[0426] Step 306F: The target node sends a handover request confirmation message to the source node.

[0427] Step 307F: The source node sends the predicted slice information and / or the target cell's support for the slice to the UE. The predicted slice information may be the aforementioned second message. The target cell's support for the slice may include one or more of the following: the target cell's identifier, the slice identifier and / or identifier list supported by the target cell, and the target cell's priority. The target cell priority may be set according to the target cell's support for the predicted slice information. For example, a cell that supports the predicted slice has a higher priority, wherein the specific priority setting may be to set a higher priority for a cell that supports a greater number of predicted slices. The predicted slice information and / or the target cell's support for the slice may be carried by an RRC reconfiguration message. In some embodiments, for example, in conditional switching, the UE may select a cell that supports the predicted slice as the target cell when the execution conditions are met based on the predicted slice information and the target cell's support for the slice.

[0428] Step 308F: Perform subsequent switching process.

[0429] Step 309F: AMF evaluates the predicted slice information based on subsequent slice conditions, for example, performance evaluation, accuracy evaluation, etc.

[0430] Figure 3G A schematic diagram of one aspect of a method for supporting slicing according to an embodiment of the present disclosure is shown. Specifically, Figure 3GThe process of interactively predicting slice information among UE, source node, target node, and AMF is shown, so that the source node can make resource allocation and / or switching decisions based on the predicted slice information, and the target node can make resource allocation and / or subsequent switching decisions based on the predicted slice information.

[0431] Step 301G: The UE sends a measurement report to the source node.

[0432] Step 302G: The source node makes a handover decision based on the received measurement report.

[0433] Step 303G: The source node sends a handover required message carrying a target cell list to the AMF.

[0434] Step 304G: AMF performs prediction based on the slice information and selects a target cell according to the predicted slice information, for example, selecting a cell supporting the predicted slice as the target cell in the target cell list received from the source node.

[0435] Step 305G: The AMF sends predicted slice information to the target cell. The predicted slice information may be the aforementioned second message. The predicted slice information may be carried by the handover request message.

[0436] Step 306G: The target node sends a handover request confirmation message to the AMF.

[0437] Step 307G: The AMF sends predicted slice information to the source node. The predicted slice information may be the aforementioned second message. The predicted slice information may be carried by the handover command message.

[0438] Step 308G: The source node sends the predicted slice information and / or the target cell's support for the slice to the UE. The predicted slice information may be the aforementioned second message. The target cell's support for the slice may include one or more of the following: the target cell's identifier, the slice identifier and / or identifier list supported by the target cell, and the target cell's priority. The target cell priority may be set according to the target cell's support for the predicted slice information. For example, a cell that supports the predicted slice has a higher priority, wherein the specific priority setting may be to set a higher priority for a cell that supports a greater number of predicted slices. The predicted slice information and / or the target cell's support for the slice may be carried by an RRC reconfiguration message. In some embodiments, for example, in conditional switching, the UE may select a cell that supports the predicted slice as the target cell when the execution conditions are met based on the predicted slice information and the target cell's support for the slice.

[0439] Step 309G: Perform subsequent switching process.

[0440] Step 310G: AMF evaluates the predicted slice information based on subsequent slice conditions, for example, performance evaluation, accuracy evaluation, etc.

[0441] Figure 3H A schematic diagram of one aspect of a method for supporting slicing according to an embodiment of the present disclosure is shown. Specifically, Figure 3H The process of interactively predicting slice information between the UE, the source node, and the target node is shown, so that the source node can make resource allocation and / or switching decisions based on the predicted slice information, and the target node can make resource allocation and / or subsequent switching decisions based on the predicted slice information.

[0442] Step 301H: The source node sends a slice-related performance request to the target node. The slice-related performance request may be the aforementioned sixth message.

[0443] Step 302H: The target node sends a slice-related performance response to the source node to inform the target node whether it can report slice-related performance. The slice-related performance response may include one or more of the following:

[0444] Sending node ID: used to identify the node that sends the message.

[0445] Receiving node ID: used to identify the node that receives the message.

[0446] Measurement identifier: used to identify the measurement. In some implementations, for example, the measurement identifier may be consistent with the measurement identifier in step 301H, and is used to associate the response message with the request message.

[0447] Slice-related performance request confirmation: used to indicate whether the slice-related performance situation can be measured and / or reported. The slice-related performance situation can be a bit indicating whether the request can be measured and / or reported.

[0448] Measurable content: used to indicate the content that can be measured. The content may include one or more of the following: QoS parameters, QoE parameters, load information, actual slice information, time information, UE identifier, slice identifier, cell identifier, beam identifier, etc. The actual slice information may be the slice information actually accessed, and may include one or more of the following: the slice identifier actually accessed, access time information, departure time information, slice residence time, etc.

[0449] · Scope that can be measured and / or reported: used to indicate the scope that can be measured and / or predicted and / or reported. The scope can be one or more of the following identification representations and / or identification lists: slice, UE, UE that does not perform measurement, UE that performs measurement, etc. The above scope can also represent the slice performance excluding one or more UEs, for example, it can be other users in the slice excluding the switched user, or it can be other users in the slice excluding the user corresponding to the slice remapping.

[0450] · Scope where measurement and / or reporting cannot be performed: used to indicate a scope where measurement and / or prediction and / or reporting cannot be performed. The scope may be one or more of the following identifiers and / or identifier lists: slice, UE, UE that does not perform measurement, UE that performs measurement, etc. The above scope may also indicate the performance of a slice excluding one or more UEs, for example, other users in the slice excluding the user who switches the user, or other users in the slice excluding the user corresponding to the slice remapping.

[0451] Content that cannot be measured: used to indicate content that cannot be measured. The content may include one or more of the following: QoS parameters, QoE parameters, load information, actual slice information, time information, UE identifier, slice identifier, cell identifier, beam identifier, etc. The actual slice information may be the slice information actually accessed, and may include one or more of the following: the slice identifier actually accessed, access time information, departure time information, slice residence time, etc.

[0452] Reason: indicates the reason why measurement and / or reporting cannot be performed. The reason may include one or more of the following: slice unavailable, measurement unavailable, slice load measurement unavailable, slice temporarily unavailable, measurement temporarily unavailable, slice measurement temporarily unavailable, reporting time unavailable, reporting period unavailable, etc.

[0453] Step 303H: The UE sends a measurement report to the source node.

[0454] Step 304H: The source node predicts the slice information, and the source node makes a handover decision based on the measurement report, the predicted slice information, etc. For example, the source node may select a node that supports the predicted slice as the target node to ensure the stability and robustness of the handover, and prevent the UE from needing to reselect a serving cell when the switched target node cannot support a certain slice, resulting in service interruption, etc.

[0455] Step 305H: The source node sends predicted slice information and / or slice performance request indication (also referred to as slice performance request related information in this article) to the target node. The predicted slice information may be the aforementioned second message. The slice performance request indication is used to trigger the target node to collect slice performance. The indication may be the request identifier in the aforementioned sixth message, or the slice performance request indication in the sixth message. The predicted slice information and / or slice performance request indication may be carried by a switching request message. The predicted slice information may be used for making subsequent switching decisions, for example, making switching decisions related to slices, etc.

[0456] Step 306H: The target node sends the predicted slice information and / or the target cell's support for the slice to the source node. The predicted slice information may be the aforementioned second message. The target cell's support for the slice may include one or more of the following: an identifier of the target cell, a slice identifier and / or an identifier list supported by the target cell, a priority of the target cell, a slice identifier and / or an identifier list of the predicted slices (for example, the predicted slices included in the predicted slice information) supported by the target cell, and the number of predicted slices supported by the target cell. The target cell's support for the slice may be the target cell's support for the predicted slices included in the predicted slice information, or it may be the target cell's own slice support capability. The target cell priority may be set according to the target cell's support for the predicted slice information. For example, a cell that supports the predicted slice has a higher priority, wherein the specific priority setting may be that a cell that supports a larger number of predicted slices is set with a higher priority. The predicted slice information and / or the target cell's support for the slice may be carried by an RRC reconfiguration message. In some embodiments, for example, in conditional switching, the UE may select a cell that supports the predicted slice as the target cell when the execution condition is met based on the predicted slice information and the target cell's support for the slice. The predicted slice information and / or the target cell's support for the slice may be carried by the handover request confirmation message.

[0457] Step 307H: The source node sends the predicted slice information and / or the target cell's support for the slice to the UE. The predicted slice information may be the aforementioned second message. The target cell's support for the slice may include one or more of the following: an identifier of the target cell, a slice identifier and / or an identifier list supported by the target cell, a priority of the target cell, a slice identifier and / or an identifier list of the predicted slices (for example, the predicted slices included in the predicted slice information) supported by the target cell, and the number of predicted slices supported by the target cell. The target cell's support for the slice may be the target cell's support for the predicted slices included in the predicted slice information, or it may be the target cell's own slice support capability. The target cell priority may be set according to the target cell's support for the predicted slice information. For example, a cell that supports the predicted slice has a higher priority, wherein the specific priority setting may be that a cell that supports a larger number of predicted slices is set with a higher priority. The predicted slice information and / or the target cell's support for the slice may be carried by an RRC reconfiguration message. In some embodiments, for example, in conditional switching, the UE may select a cell that supports the predicted slice as the target cell when the execution condition is met based on the predicted slice information and the target cell's support for the slice. In some implementations, information such as the priority of the target cell and the number of predicted slices supported by the target cell may be determined by the source node, or may be determined by the target cell itself and sent to the source node.

[0458] Step 308H: Perform subsequent switching process.

[0459] Step 309H: The target node sends the collected (or acquired) slice-related performance to the source node. The slice-related performance may be the seventh message mentioned above.

[0460] Step 310H: The source node evaluates the predicted slice information based on the collected slice-related performance, for example, performance evaluation, accuracy evaluation, etc.

[0461] Figure 4A A schematic diagram of one aspect of a method for supporting slicing according to an embodiment of the present disclosure is shown. Specifically, Figure 4A The process of exchanging slice load conditions between two nodes is shown, so that a third node can know the slice load conditions. The third node can refer to the information when making SON-related decisions, or refer to the information when making switching decisions, or use the slice load information to evaluate whether a slice remapping decision is appropriate.

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

[0463] Step 401A: The fourth node sends a slice load status to the third node. The slice load status may be the fifth message mentioned above.

[0464] Step 402A: The fourth node makes resource allocation and / or switching decisions and / or slice remapping decisions and / or decision performance evaluation based on the slice load situation.

[0465] Figure 4B A schematic diagram of one aspect of a method for supporting slicing according to an embodiment of the present disclosure is shown. Specifically, Figure 4B The process of exchanging slice load conditions between two nodes is shown, so that a third node can know the slice load conditions. The third node can refer to the information when making SON-related decisions, or refer to the information when making switching decisions, or use the slice load information to evaluate whether a slice remapping decision is appropriate.

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

[0467] Step 401B: The third node sends a slice load status request to the fourth node. The slice load status request may be the aforementioned third message.

[0468] Step 402B: The fourth node sends a slice load status to the third node. The slice load status may be the fifth message mentioned above.

[0469] Step 403B: The fourth node makes resource allocation and / or switching decisions and / or slice remapping decisions and / or decision performance evaluation based on the slice load situation.

[0470] If the fourth node is required to perform periodic reporting in step 401B, step 402B is performed periodically.

[0471] Figure 4C A schematic diagram of one aspect of a method for supporting slicing according to an embodiment of the present disclosure is shown. Specifically, Figure 4C The process of exchanging slice load conditions between two nodes is shown, so that a third node can know the slice load conditions. The third node can refer to the information when making SON-related decisions, or refer to the information when making switching decisions, or use the slice load information to evaluate whether a slice remapping decision is appropriate.

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

[0473] Step 401C: The third node sends a slice load status request to the fourth node. The slice load status request may be the aforementioned third message.

[0474] Step 402C: The fourth node sends a slice load request response to the third node. The slice load response may be the aforementioned fourth message.

[0475] Step 403C: The fourth node sends the slice load status to the third node. The slice load status may be the fifth message mentioned above.

[0476] Step 404C: The fourth node makes resource allocation and / or switching decisions and / or slice remapping decisions and / or decision performance evaluation based on the slice load situation.

[0477] If the fourth node is required to perform periodic reporting in step 401C, step 403C is performed periodically.

[0478] Figure 5A A schematic diagram of one aspect of a method for supporting slicing according to an embodiment of the present disclosure is shown. Specifically, Figure 5A The process of exchanging slice load conditions between two nodes is shown, so that the fifth node can know the slice-related performance. The fifth node can refer to the information when making SON-related decisions, or refer to the information when making switching decisions. It can also use the slice-related performance information to evaluate whether the slice remapping decision is appropriate, or use the slice-related performance information to evaluate whether the decision is appropriate, etc.

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

[0480] Step 501A: The sixth node sends slice-related performance to the fifth node. The slice-related performance may be the seventh message mentioned above.

[0481] Step 502A: The fifth node makes resource allocation and / or switching decisions and / or slice remapping decisions and / or decision performance evaluation based on slice-related performance.

[0482] Figure 5B A schematic diagram of one aspect of a method for supporting slicing according to an embodiment of the present disclosure is shown. Specifically, Figure 5B The process of exchanging slice performance between two nodes is shown, so that the fifth node can know the slice-related performance. The fifth node can refer to the information when making SON-related decisions, or refer to the information when making switching decisions. It can also use the slice-related performance information to evaluate whether the slice remapping decision is appropriate, or use the slice-related performance information to evaluate whether the decision is appropriate, etc.

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

[0484] Step 501B: The fifth node sends a slice-related performance request to the sixth node. The slice-related performance request may be the aforementioned sixth message.

[0485] Step 502B: The sixth node sends slice-related performance to the fifth node. The slice-related performance may be the seventh message mentioned above.

[0486] Step 503B: The fifth node makes resource allocation and / or switching decisions and / or slice remapping decisions and / or decision performance evaluation based on slice-related performance.

[0487] Figure 5C A schematic diagram of one aspect of a method for supporting slicing according to an embodiment of the present disclosure is shown. Specifically, Figure 5C The process of exchanging slice performance between two nodes is shown, so that the fifth node can know the slice-related performance. The fifth node can refer to the information when making SON-related decisions, or refer to the information when making switching decisions. It can also use the slice-related performance information to evaluate whether the slice remapping decision is appropriate, or use the slice-related performance information to evaluate whether the decision is appropriate, etc.

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

[0489] Step 501C: The fifth node sends a slice-related performance request to the sixth node. The slice-related performance request may be the aforementioned sixth message.

[0490] Step 502C: The sixth node notifies the fifth node whether it can report according to the slice-related performance request. The message may be a slice-related performance request response message. The message may include: a sending node identifier, a receiving node identifier, a slice identifier, a cell identifier, a user identifier, parameters that can be reported, parameters that cannot be reported, reasons for not being reported, etc.

[0491] Step 503C: The sixth node sends slice-related performance to the fifth node. The slice-related performance may be the seventh message mentioned above.

[0492] Step 504C: The fifth node makes resource allocation and / or switching decisions and / or slice remapping decisions and / or decision performance evaluation based on slice-related performance.

[0493] If step 501C requests periodic reporting, step 503C is performed periodically.

[0494] Figure 5D A schematic diagram of one aspect of a method for supporting slicing according to an embodiment of the present disclosure is shown. Specifically, Figure 5DThe process of inter-node interaction of slice-related performance is shown so that the source node can know the slice-related performance. The source node can refer to the information when making SON-related decisions, or refer to the information when making switching decisions. The source node can also use the slice-related performance information to evaluate whether a slice remapping decision is appropriate, or use the slice-related performance information to evaluate whether a decision is appropriate.

[0495] Step 501D: The UE sends a measurement report to the source node.

[0496] Step 502D: The source node makes a handover decision based on the measurement report.

[0497] Step 503D: The source node sends a slice-related performance request to the target node. The slice-related performance request may be the aforementioned sixth message. The slice-related performance request may be carried by a slice request message.

[0498] Step 504D: The target node sends a slice-related performance response to the source node to inform the target node whether it can report slice-related performance. The slice-related performance response may include one or more of the following:

[0499] Sending node ID: used to identify the node that sends the message.

[0500] Receiving node ID: used to identify the node that receives the message.

[0501] Measurement identifier: used to identify the measurement. In some implementations, for example, the measurement identifier may be consistent with the measurement identifier in step 503D, and is used to associate the response message with the request message.

[0502] Slice-related performance request confirmation: used to indicate whether the slice-related performance situation can be measured and / or reported. The slice-related performance situation can be a bit indicating whether the request can be measured and / or reported.

[0503] Measurable content: used to indicate the content that can be measured. The content may include one or more of the following: QoS parameters, QoE parameters, load information, actual slice information, time information, UE identifier, slice identifier, cell identifier, beam identifier, etc. The actual slice information may be the slice information actually accessed, and may include one or more of the following: the slice identifier actually accessed, access time information, departure time information, slice residence time, etc.

[0504] · Scope that can be measured and / or reported: used to indicate the scope that can be measured and / or predicted and / or reported. The scope can be one or more of the following identification representations and / or identification lists: slice, UE, UE that does not perform measurement, UE that performs measurement, etc. The above scope can also represent the slice performance excluding one or more UEs, for example, it can be other users in the slice excluding the switched user, or it can be other users in the slice excluding the user corresponding to the slice remapping.

[0505] · Scope where measurement and / or reporting cannot be performed: used to indicate a scope where measurement and / or prediction and / or reporting cannot be performed. The scope may be one or more of the following identifiers and / or identifier lists: slice, UE, UE that does not perform measurement, UE that performs measurement, etc. The above scope may also indicate the performance of a slice excluding one or more UEs, for example, other users in the slice excluding the user who switches the user, or other users in the slice excluding the user corresponding to the slice remapping.

[0506] Content that cannot be measured: used to indicate content that cannot be measured. The content may include one or more of the following: QoS parameters, QoE parameters, load information, actual slice information, time information, UE identifier, slice identifier, cell identifier, beam identifier, etc. The actual slice information may be the slice information actually accessed, and may include one or more of the following: the slice identifier actually accessed, access time information, departure time information, slice residence time, etc.

[0507] Reason: indicates the reason why measurement and / or reporting cannot be performed. The reason may include one or more of the following: slice unavailable, measurement unavailable, slice load measurement unavailable, slice temporarily unavailable, measurement temporarily unavailable, slice measurement temporarily unavailable, reporting time unavailable, reporting period unavailable, etc.

[0508] The slice-related performance response can be carried by the switching request confirmation message.

[0509] Step 505D: The source node sends an RRC reconfiguration message to the UE.

[0510] Step 506D: Perform a subsequent switching process.

[0511] Step 507D: The target node sends the collected (or acquired) slice-related performance to the source node. The slice-related performance may be the seventh message mentioned above.

[0512] Step 508D: The source node evaluates the decision made based on the collected slice-related performance.

[0513] Figure 5EA schematic diagram of one aspect of a method for supporting slicing according to an embodiment of the present disclosure is shown. Specifically, Figure 5E The process of inter-node interaction of slice-related performance is shown so that the source node can know the slice-related performance. The source node can refer to the information when making SON-related decisions, or refer to the information when making switching decisions. The source node can also use the slice-related performance information to evaluate whether a slice remapping decision is appropriate, or use the slice-related performance information to evaluate whether a decision is appropriate.

[0514] Step 501E: The source node sends a slice-related performance request to the target node. The slice-related performance request may be the aforementioned sixth message.

[0515] Step 502E: The target node sends a slice-related performance response to the source node to inform the target node whether it can report slice-related performance. The slice-related performance response may include one or more of the following:

[0516] Sending node ID: used to identify the node that sends the message.

[0517] Receiving node ID: used to identify the node that receives the message.

[0518] Measurement identifier: used to identify the measurement. In some implementations, for example, the measurement identifier may be consistent with the measurement identifier in step 501E, and is used to associate the response message with the request message.

[0519] Slice-related performance request confirmation: used to indicate whether the slice-related performance situation can be measured and / or reported. The slice-related performance situation can be a bit indicating whether the request can be measured and / or reported.

[0520] Measurable content: used to indicate the content that can be measured. The content may include one or more of the following: QoS parameters, QoE parameters, load information, actual slice information, time information, UE identifier, slice identifier, cell identifier, beam identifier, etc. The actual slice information may be the slice information actually accessed, and may include one or more of the following: the slice identifier actually accessed, access time information, departure time information, slice residence time, etc.

[0521] · Scope that can be measured and / or reported: used to indicate the scope that can be measured and / or predicted and / or reported. The scope can be one or more of the following identification representations and / or identification lists: slice, UE, UE that does not perform measurement, UE that performs measurement, etc. The above scope can also represent the slice performance excluding one or more UEs, for example, it can be other users in the slice excluding the switched user, or it can be other users in the slice excluding the user corresponding to the slice remapping.

[0522] · Scope where measurement and / or reporting cannot be performed: used to indicate a scope where measurement and / or prediction and / or reporting cannot be performed. The scope may be one or more of the following identifiers and / or identifier lists: slice, UE, UE that does not perform measurement, UE that performs measurement, etc. The above scope may also indicate the performance of a slice excluding one or more UEs, for example, other users in the slice excluding the user who switches the user, or other users in the slice excluding the user corresponding to the slice remapping.

[0523] Content that cannot be measured: used to indicate content that cannot be measured. The content may include one or more of the following: QoS parameters, QoE parameters, load information, actual slice information, time information, UE identifier, slice identifier, cell identifier, beam identifier, etc. The actual slice information may be the slice information actually accessed, and may include one or more of the following: the slice identifier actually accessed, access time information, departure time information, slice residence time, etc.

[0524] Reason: indicates the reason why measurement and / or reporting cannot be performed. The reason may include one or more of the following: slice unavailable, measurement unavailable, slice load measurement unavailable, slice temporarily unavailable, measurement temporarily unavailable, slice measurement temporarily unavailable, reporting time unavailable, reporting period unavailable, etc.

[0525] Step 503E: The UE sends a measurement report to the source node.

[0526] Step 504E: The source node makes a handover decision based on the measurement report.

[0527] Step 505E: The source node sends a slice performance request indication (also referred to as slice performance request related information in this article) to the target node. The slice performance request indication is used to trigger the target node to collect slice performance. The indication can be the request identifier in the aforementioned sixth message, or the slice performance request indication in the sixth message. The slice performance request indication can be carried by the handover request message.

[0528] Step 506E: The target node sends a handover request confirmation message to the source node.

[0529] Step 507E: The source node sends an RRC reconfiguration message to the UE.

[0530] Step 508E: Perform subsequent switching process.

[0531] Step 509E: The target node sends the collected (or acquired) slice-related performance to the source node. The slice-related performance may be the seventh message mentioned above.

[0532] Step 510E: The source node evaluates the decision made based on the collected slice-related performance.

[0533] Figure 6 A schematic diagram of one aspect of a method for supporting slicing according to an embodiment of the present disclosure is shown. Specifically, Figure 6 The process of interactively predicting that the slice load is too large between two nodes is shown, so that the eighth node can know the situation that the predicted slice is about to be overloaded. The eighth node can refer to this information when making SON-related decisions, or refer to this information when making switching decisions, or use the slice-related performance information to evaluate whether the slice remapping decision is appropriate, or use the slice-related performance information to evaluate whether the decision is appropriate, etc.

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

[0535] Step 601A: The seventh node sends a message to the eighth node predicting that the slice load is too large. The predicted slice load is too large may be the eighth message mentioned above.

[0536] Step 602A: The eighth node makes resource allocation and / or switching decisions and / or slice remapping decisions and / or decision performance evaluation based on the predicted slice overload situation.

[0537] Figure 7 A schematic diagram of one aspect of a method for supporting slicing according to an embodiment of the present disclosure is shown. Specifically, Figure 7 The process of exchanging the receivable load information between two nodes is shown, so that the eighth node can know the receivable load situation, and the eighth node can refer to the information when making a switching decision, or refer to the information when making a SON-related decision, or use the slice-related performance information to evaluate whether the slice remapping decision is appropriate, or use the slice-related performance information to evaluate whether the decision is appropriate, etc. For example, when receiving a switching request, the information is referenced to avoid receiving too many switching requests resulting in excessive load, and the received UE needs to be switched to other nodes, resulting in service interruption due to frequent switching.

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

[0539] Step 701A: The seventh node sends the receivable load information to the eighth node. The receivable load information may be the ninth message mentioned above.

[0540] Step 702A: The eighth node makes switching decisions and / or slice remapping decisions and / or decision performance evaluation based on the load information that can be received.

[0541] Figure 8 A schematic diagram of one aspect of a method for supporting slicing according to an embodiment of the present disclosure is shown. Specifically, Figure 8The process of interactive slicing resource partitioning decision between two nodes is shown, so that the tenth node can obtain the resource partitioning decision and make resource allocation decisions according to the resource partitioning decision.

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

[0543] Step 801A: The ninth node sends a slice resource partitioning decision to the tenth node. The slice resource partitioning decision may be the tenth message mentioned above.

[0544] Step 802A: The tenth node makes a resource allocation decision based on the acquired resource partitioning decision and in accordance with the resource partitioning decision.

[0545] Fig.9A A schematic diagram of one aspect of a method for supporting slicing according to an embodiment of the present disclosure is shown. Specifically, Fig.9A The process of interacting slice resource usage between two nodes is shown, so that the eleventh node can evaluate resource partitioning decisions and / or adjust slice resource partitioning decisions based on slice resource usage, etc.

[0546] In some embodiments, for example, the twelfth node may be a UE, and the eleventh node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In other embodiments, for example, the eleventh node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB, and the twelfth node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In still other embodiments, for example, the eleventh node may be an AMF or an SMF or an MME, and the twelfth node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB. In still other embodiments, for example, the eleventh node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB, and the twelfth node may be an AMF or an SMF or an MME.

[0547] Step 901A: The twelfth node sends the slice resource usage to the eleventh node. The slice resource usage may be the twelve messages mentioned above.

[0548] Step 902A: The eleventh node may evaluate resource partitioning decisions and / or adjust slice resource partitioning decisions based on slice resource usage, etc.

[0549] Fig. 9B A schematic diagram of one aspect of a method for supporting slicing according to an embodiment of the present disclosure is shown. Specifically, Fig. 9B The process of interacting slice resource usage between two nodes is shown, so that the eleventh node can evaluate resource partitioning decisions and / or adjust slice resource partitioning decisions based on slice resource usage, etc.

[0550] In some embodiments, for example, the twelfth node may be a UE, and the eleventh node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In other embodiments, for example, the eleventh node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB, and the twelfth node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In still other embodiments, for example, the eleventh node may be an AMF or an SMF or an MME, and the twelfth node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB. In still other embodiments, for example, the eleventh node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB, and the twelfth node may be an AMF or an SMF or an MME.

[0551] Step 901B: The eleventh node sends a slice resource usage request to the twelfth node. The slice resource usage request may be the eleventh message mentioned above.

[0552] Step 902B: The twelfth node sends the slice resource usage to the eleventh node. The slice resource usage may be the twelve messages mentioned above.

[0553] Step 903B: The eleventh node may evaluate resource partitioning decisions and / or adjust slice resource partitioning decisions based on slice resource usage, etc.

[0554] Figure 8 Can be used with Fig.9A or Fig. 9B Combined with, for example, Figure 8 Occurs after step Fig.9A or Fig. 9B Steps; can also be Fig.9A or Fig. 9B Occurs after step Figure 8 Steps; can also be Fig.9A or Fig. 9B Occurs after step Figure 8 Steps, reoccurrence Fig.9A or Fig. 9B step.

[0555] Fig. 10A A schematic diagram of one aspect of a method for supporting slicing according to an embodiment of the present disclosure is shown. Specifically, Fig. 10AThe process of exchanging slice support information between two nodes is shown, so that the thirteenth node can obtain the slice support information of the fourteenth node and / or other nodes. The thirteenth node can make switching decisions based on the information and / or further request slice prediction information, etc.

[0556] In some embodiments, for example, the thirteenth node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB, and the fourteenth node may be a UE. In other embodiments, for example, the thirteenth node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB, and the fourteenth node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In still other embodiments, for example, the thirteenth node may be an AMF or an SMF or an MME, and the fourteenth node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB. In still other embodiments, for example, the thirteenth node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB, and the fourteenth node may be an AMF or an SMF or an MME.

[0557] Step 1001A: The fourteenth node sends slice support information to the thirteenth node. The slice support information may be the fourteenth message mentioned above.

[0558] Step 1002A: The thirteenth node makes a switching decision based on the slice support information, for example, selecting a node that supports the required slice as the target node, or further requesting slice prediction information. For example, if the fourteenth node supports slice prediction, the thirteenth node can FIG. 3A to FIG. 3H Request slice prediction information.

[0559] Fig. 10B A schematic diagram of one aspect of a method for supporting slicing according to an embodiment of the present disclosure is shown. Specifically, Fig. 10B The process of exchanging slice support information between two nodes is shown, so that the thirteenth node can obtain the slice support information of the fourteenth node and / or other nodes. The thirteenth node can make switching decisions based on the information and / or further request slice prediction information, etc.

[0560] In some embodiments, for example, the thirteenth node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB, and the fourteenth node may be a UE. In other embodiments, for example, the thirteenth node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB, and the fourteenth node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In still other embodiments, for example, the thirteenth node may be an AMF or an SMF or an MME, and the fourteenth node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB. In still other embodiments, for example, the thirteenth node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB, and the fourteenth node may be an AMF or an SMF or an MME.

[0561] Step 1001A: The thirteenth node sends a slice support information request to the fourteenth node to request the fourteenth node to send slice support information. The slice support information request may be the thirteenth message mentioned above.

[0562] Step 1002A: The fourteenth node sends slice support information to the thirteenth node. The slice support information may be the fourteenth message mentioned above.

[0563] Step 1003A: The thirteenth node makes a switching decision based on the slice support information, for example, selecting a node that supports the required slice as the target node, or further requesting slice prediction information. For example, if the fourteenth node supports slice prediction, the thirteenth node can FIG. 3A to FIG. 3H Request slice prediction information.

[0564] Fig.11 A schematic diagram of one aspect of a method for supporting slicing according to an embodiment of the present disclosure is shown. Specifically, Fig.11 The process of exchanging the applicable time of the remapping decision between two nodes is shown, so that the sixteenth node can know the applicable time of the remapping decision and only apply the relevant remapping decision within the applicable time.

[0565] In some embodiments, for example, the fifteenth node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB, and the sixteenth node may be a UE. In other embodiments, for example, the fifteenth node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB, and the sixteenth node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In still other embodiments, for example, the fifteenth node may be an AMF or an SMF or an MME, and the sixteenth node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB. In still other embodiments, for example, the fifteenth node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB, and the sixteenth node may be an AMF or an SMF or an MME.

[0566] Step 1101A: The fifteenth node sends the remapping decision applicable time to the sixteenth node. The remapping applicable time may be the fifteenth message mentioned above.

[0567] Step 1102A: The sixteenth node applies the relevant remapping decision only within the applicable time of the remapping decision. The sixteenth node may make relevant decisions based on the remapping decision and / or the applicable time of the remapping decision, such as slice decision, PDU session reconstruction and / or modification, etc. In some embodiments, for example, the sixteenth node may reconstruct and / or modify the PDU session of one or more users of a certain slice to another slice based on the remapping decision within the applicable time of the remapping decision. In another embodiment, for example, the sixteenth node may select a switching target node for the user based on the remapping decision within the applicable time of the remapping decision.

[0568] Fig. 12A A schematic diagram of one aspect of a method for supporting slicing according to an embodiment of the present disclosure is shown. Specifically, Fig. 12AThe process of exchanging experience quality parameters between two nodes is shown, so that the eighteenth node can refer to the experience quality parameter information when making relevant decisions, wherein the relevant decisions may include switching decisions, resource allocation decisions, slice remapping decisions, etc. In some embodiments, for example, a node and / or cell that can guarantee the experience quality parameter is selected as a switching target node and / or cell to ensure the experience quality; the experience quality parameter may also be considered when making a resource allocation decision to ensure the experience quality; or if the slice to which the user currently belongs does not support and / or has a shortage of resources, when slice remapping is required, the node needs to select a slice that can support the experience quality as a remapped slice to ensure the experience quality.

[0569] In some embodiments, for example, the seventeenth node may be a UE, and the eighteenth node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In other embodiments, for example, the seventeenth node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB, and the eighteenth node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In still other embodiments, for example, the seventeenth node may be an AMF or an SMF or an MME, and the eighteenth node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB. In still other embodiments, for example, the seventeenth node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB, and the eighteenth node may be an AMF or an SMF or an MME.

[0570] Step 1201A: The seventeenth node sends an experience quality parameter to the eighteenth node. The experience quality parameter may be the sixteenth message mentioned above.

[0571] Step 1202A: The eighteenth node refers to the experience quality parameter information when making relevant decisions, wherein the relevant decisions may include handover decisions, resource allocation decisions, slice remapping decisions, etc. In some implementations, for example, a node and / or cell that can guarantee the experience quality parameter is selected as a handover target node and / or cell to ensure the experience quality; the experience quality parameter may also be considered when making a resource allocation decision to ensure the experience quality; or if the slice to which the user currently belongs does not support and / or has insufficient resources, and slice remapping is required, the node needs to select a slice that can support the experience quality as a remapped slice to ensure the experience quality.

[0572] Fig. 12BA schematic diagram of one aspect of a method for supporting slicing according to an embodiment of the present disclosure is shown. Specifically, Fig. 12B Shows the process by which AMF makes slice remapping decisions.

[0573] Step 1201B: The UE sends a measurement report to the source node.

[0574] Step 1202B: The source node makes a mobility decision based on the measurement report.

[0575] Step 1203B: The source node sends an experience quality parameter to the AMF. The experience quality parameter may be the aforementioned message 16. The experience quality parameter may be sent by a HANDOVER REQUIRED message. The message may also carry information of multiple target cells, so that the AMF may select one of the multiple target cells as a handover target cell based on the remapping decision.

[0576] Step 1204B: AMF makes a remapping decision based on the quality of experience parameters.

[0577] Step 1205B: AMF sends the slice remapping decision and / or the slice remapping decision applicable time to the target node. The slice remapping decision applicable time may be the aforementioned fifteenth message. The slice remapping decision and / or the slice remapping decision applicable time may be carried by a handover request (HANDOVER REQUEST) message.

[0578] Step 1206B: The target node sends the received slice information to the AMF. The received slice information may include a user identifier, an identifier corresponding to the received slice, etc. The received slice information may be carried by a handover request confirmation message.

[0579] Step 1207B: AMF sends a switching command to the source node.

[0580] Step 1208B: Other switching processes.

[0581] Step 1209B: AMF sends a slice-related performance request and / or a slice load request to the target node (step 1209B and subsequent steps, the target node is the user's service node). The slice-related performance request may be the aforementioned sixth message. The slice load request may be the aforementioned third message.

[0582] Step 1210B: The target node sends a slice-related performance response and / or a slice load response to the AMF. The slice-related performance response may be the message in the aforementioned step 502C. The slice load response may be the aforementioned fourth message.

[0583] Step 1211B: The target node sends slice-related performance and / or slice load conditions to the AMF. The slice-related performance may be the aforementioned seventh message. The slice load condition may be the aforementioned fifth message. After the AMF obtains the slice-related performance and / or slice load condition, it may evaluate whether the slice remapping decision is appropriate. For example, if the slice-related performance is poor and / or the slice load is overloaded, the slice remapping decision may be evaluated as inappropriate.

[0584] If the request in step 1209B needs to be reported periodically, step 1211B is performed periodically.

[0585] Step 1210B may be omitted.

[0586] Fig. 12C A schematic diagram of one aspect of a method for supporting slicing according to an embodiment of the present disclosure is shown. Specifically, Fig. 12C The process by which a target node makes a slice remapping decision is shown.

[0587] Step 1201C: The UE sends a measurement report to the source node.

[0588] Step 1202C: The source node makes a mobility decision based on the measurement report.

[0589] Step 1203C: The source node sends an experience quality parameter to the target node. The experience quality parameter may be the sixteenth message mentioned above. The experience quality parameter may be sent by a handover request (HANDOVER REQUEST) message.

[0590] Step 1204C: The target node makes a remapping decision based on the quality of experience parameter.

[0591] Step 1205C: The target node sends the slice remapping decision and / or the slice remapping decision applicable time to the source node. The slice remapping decision applicable time may be the aforementioned fifteenth message. The slice remapping decision and / or the slice remapping decision applicable time may be carried by a HANDOVER REQUEST ACKNOWLEGEMENT message.

[0592] Step 1206C: Other switching processes.

[0593] Step 1207C: The target node (step 1207C and subsequent steps, the target node is the user's service node) sends a slice-related performance request and / or a slice load request to the AMF. The slice-related performance request may be the aforementioned sixth message. The slice load request may be the aforementioned third message.

[0594] Step 1208C: AMF sends a slice-related performance response and / or a slice load response to the target node. The slice-related performance response may be the message in the aforementioned step 502C. The slice load response may be the aforementioned fourth message.

[0595] Step 1209C: AMF sends slice-related performance and / or slice load status to the target node. The slice-related performance may be the aforementioned seventh message. The slice load status may be the aforementioned fifth message. After the target node obtains the slice-related performance and / or slice load status, it may evaluate whether the slice remapping decision is appropriate. For example, if the slice-related performance is poor and / or the slice load is overloaded, the slice remapping decision may be evaluated as inappropriate.

[0596] If the request in step 1207C needs to be reported periodically, step 1209C is performed periodically.

[0597] Step 1208C may be omitted.

[0598] Fig.12D A schematic diagram of one aspect of a method for supporting slicing according to an embodiment of the present disclosure is shown. Specifically, Fig.12D The process by which a target node makes a slice remapping decision is shown.

[0599] Step 1200D: AMF sends (for example, the target node) to the access network side node (for example, in this figure, the target node is used as an identifier and example) information about the load amount that can be received and / or the predicted slice load is too large. The load amount information that can be received may be the aforementioned ninth message. The predicted slice load is too large may be the aforementioned eighth message.

[0600] Step 1201D.A: The target node sends a slice load information request to the AMF, wherein the slice load information request may be the aforementioned third message.

[0601] Step 1201D.B: AMF sends a slice load information response to the target node, where the slice load status response may be the aforementioned fourth message.

[0602] Step 1201D.C: AMF sends slice load information (or slice load status) to the target node, where the slice load status may be the fifth message mentioned above.

[0603] Step 1202D.A: The source node sends a predicted slice information request to the UE. The predicted slice information request may be the aforementioned first message.

[0604] Step 1202D.B: The UE sends predicted slice information to the source node. The predicted slice information may be the aforementioned second message. In this embodiment, the predicted slice information may be predicted slice information of the UE. In other embodiments, the predicted slice information may also be predicted slice information associated with the UE or any other UE or node.

[0605] Step 1203D: The UE sends a measurement report to the source node.

[0606] Step 1204D: The source node makes a mobility decision based on the measurement report and / or the predicted slice information, for example, performs target node selection. For example, a node and / or cell that can support the predicted slice (e.g., one or more predicted slices included in the predicted slice information) is selected as the target cell.

[0607] Step 1205D: The source node sends an experience quality parameter to the target node. The experience quality parameter may be the aforementioned sixteenth message. The experience quality parameter may be sent by a handover request (HANDOVER REQUEST) message.

[0608] Step 1206D: The target node makes a remapping decision based on quality of experience parameters and / or slice load information.

[0609] Step 1207D: The target node sends the slice remapping decision and / or the slice remapping decision applicable time to the source node. The slice remapping decision applicable time may be the aforementioned fifteenth message. The slice remapping decision and / or the slice remapping decision applicable time may be carried by a HANDOVER REQUEST ACKNOWLEGEMENT message.

[0610] Step 1208D: Other switching processes.

[0611] Step 1209D.A: The target node (step 1209D.A and subsequent steps, the target node is the user's service node) sends a slice-related performance request and / or a slice load situation request to the AMF. The slice-related performance request may be the aforementioned sixth message. The slice load situation request may be the aforementioned third message.

[0612] Step 1209D.B: The AMF sends a slice-related performance response and / or a slice load response to the target node. The slice-related performance response may be the message in the aforementioned step 502C. The slice load response may be the aforementioned fourth message.

[0613] Step 1209D.C: AMF sends slice-related performance and / or slice load status to the target node. The slice-related performance may be the aforementioned seventh message. The slice load status may be the aforementioned fifth message. After the target node obtains the slice-related performance and / or slice load status, it may evaluate whether the slice remapping decision is appropriate. For example, if the slice-related performance is poor and / or the slice load is overloaded, the slice remapping decision may be evaluated as inappropriate.

[0614] If the request in step 1201D.A needs to be reported periodically, step 1201D.C is performed periodically.

[0615] Step 1201D.B may be omitted.

[0616] If the request in step 1209D.A needs to be reported periodically, step 1209D.C is performed periodically.

[0617] Step 1209D.B may be omitted.

[0618] Step 1201D.A, step 1201D.B, and step 1201D.C can be replaced by step 1200D. Step 1200D can be replaced by step 1201D.A, step 1201D.B, and step 1201D.C.

[0619] In some implementations, for example, step 1201D.A, step 1201D.B, and step 1201D.C may be omitted.

[0620] In some embodiments, for example, step 1200D may be omitted.

[0621] Fig.12E A schematic diagram of one aspect of a method for supporting slicing according to an embodiment of the present disclosure is shown. Specifically, Fig.12E Shows the process by which AMF makes slice remapping decisions.

[0622] Step 1201E: The service node sends the experience quality parameter to the AMF. The experience quality parameter may be the sixteenth message mentioned above.

[0623] Step 1202E: AMF makes a remapping decision based on the quality of experience parameters.

[0624] Step 1203E: AMF sends the slice remapping decision and / or the slice remapping decision applicable time to the service node. The slice remapping decision applicable time may be the fifteenth message mentioned above.

[0625] Step 1204E: The service node performs the RRC reconfiguration process with the user.

[0626] Step 1205E: AMF sends a slice-related performance request and / or a slice load condition request to the service node. The slice-related performance request may be the aforementioned sixth message. The slice load condition request may be the aforementioned third message.

[0627] Step 1206E: The service node sends a slice-related performance response and / or a slice load response to the AMF. The slice-related performance response may be the message in the aforementioned step 502C. The slice load response may be the aforementioned fourth message.

[0628] Step 1207E: The service node sends slice-related performance and / or slice load status to the AMF. The slice-related performance may be the aforementioned seventh message. The slice load status may be the aforementioned fifth message. After the service node obtains the slice-related performance and / or slice load status, it may evaluate whether the slice remapping decision is appropriate. For example, if the slice-related performance is poor and / or the slice load is overloaded, the slice remapping decision may be evaluated as inappropriate.

[0629] If the request in step 1205E needs to be reported periodically, step 1207E is performed periodically.

[0630] Step 1206E may be omitted.

[0631] Fig.12F A schematic diagram of one aspect of a method for supporting slicing according to an embodiment of the present disclosure is shown. Specifically, Fig.12F The process by which a service node makes slice remapping decisions is shown.

[0632] Step 1201F: The service node makes a remapping decision based on quality of experience parameters and / or load information.

[0633] Step 1202F: The service node sends the slice remapping decision and / or the slice remapping decision applicable time to the AMF. The slice remapping decision applicable time may be the fifteenth message mentioned above.

[0634] Step 1203F: The service node performs the RRC reconfiguration process with the user.

[0635] Step 1204F: The service node sends a slice-related performance request and / or a slice load condition request to the AMF. The slice-related performance request may be the aforementioned sixth message. The slice load condition request may be the aforementioned third message.

[0636] Step 1205F: The service node sends a slice-related performance response and / or a slice load response to the AMF. The slice-related performance response may be the message in the aforementioned step 502C. The slice load response may be the aforementioned fourth message.

[0637] Step 1206F: The service node sends slice-related performance and / or slice load status to the AMF. The slice-related performance may be the aforementioned seventh message. The slice load status may be the aforementioned fifth message. After the service node obtains the slice-related performance and / or slice load status, it may evaluate whether the slice remapping decision is appropriate. For example, if the slice-related performance is poor and / or the slice load is overloaded, the slice remapping decision may be evaluated as inappropriate.

[0638] If the request in step 1204F needs to be reported periodically, step 1206F is performed periodically.

[0639] Step 1205F may be omitted.

[0640] Fig.18A A schematic diagram of one aspect of a method for supporting slicing according to an embodiment of the present disclosure is shown. Specifically, Fig.18A The process of interactively slicing related self-optimization information between two nodes is shown, so that the twentieth node can formulate a self-optimization strategy and / or update the configuration. Alternatively, the twentieth node forwards the information to other nodes so that the other nodes can formulate a self-optimization strategy and / or update the configuration.

[0641] In some embodiments, for example, the nineteenth node may be a UE, and the twentieth node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In other embodiments, for example, the nineteenth node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB, and the twentieth node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In still other embodiments, for example, the nineteenth node may be an AMF or an SMF or an MME, and the twentieth node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB. In still other embodiments, for example, the nineteenth node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB, and the twentieth node may be an AMF or an SMF or an MME.

[0642] Step 1801A: Optionally, the 19th node sends information that slice-related self-optimization information is available to the 20th node, so as to inform the 20th node that the 19th node has the slice-related self-optimization information. The slice-related self-optimization information may include one or more of the following: slice-related self-optimization information is available, slice-related information is available, etc. The information may be included in an RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message and / or MAC CE.

[0643] Step 1802A: Optionally, the 20th node may send a slice-related self-optimization information request to the 19th node based on the slice-related self-optimization information available information received in step 1801A, so as to request the 19th node to send the slice-related self-optimization information to the 20th node; or the 20th node may autonomously send a slice-related self-optimization information request to the 19th node, so as to request the 19th node to send the slice-related self-optimization information to the 20th node. The slice-related self-optimization information request may include one or more of the following: a slice-related self-optimization information request, a slice-related information request, etc. The information may be included in an RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message and / or MACCE.

[0644] Step 1803A: The 19th node sends slice-related self-optimization information to the 20th node. In some embodiments, for example, the 19th node sends the slice-related self-optimization information to the 20th node based on the slice-related self-optimization information request received from the 20th node. In other embodiments, for example, the 19th node autonomously sends the slice-related self-optimization information to the 20th node. The information may be included in an RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message and / or MAC CE.

[0645] The slice-related self-optimization information may be included in one or more of the following: RRC user information response (UEInformationResponse), secondary cell group failure information (SCGFailureInformation), primary cell group failure information (MCGFailureInformation); Xn's failure indication (FAILURE INDICATION) message, handover report (HANDOVER REPORT) message, access and mobility indication (ACCESS AND MOBILITY INDICATION) message, secondary node modification request (S-NODE MODIFICATION REQUEST) message, secondary gNB modification request (SgNB MODIFICATIONREQUEST) message, secondary cell group failure information report (SCG FAILURE INFORMATION REPORT) message, RRC transfer (RRC TRANSFER) message; F1's access and mobility indication (ACCESS AND MOBILITY INDICATION) message; NG's uplink RAN ​​configuration forwarding (UPLINK RAN CONFIGURATION TRANSFER) message, downlink RAN ​​configuration forwarding (DOWNLINK RAN CONFIGURATION TRANSFER) message; or another and / or newly defined RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message and / or MAC CE. The slice-related self-optimization information may be included in a report. In some embodiments, for example, the report may be a Connection Establishment Failure (CEF) report, or a Random Access (Random Access) report, or a Successful Handover (Successful Handover) report, or a Radio Link Failure (RLF) report, or a measurement report, or other reports related to a wireless connection, or a new report.

[0646] The slice-related self-optimization information may include one or more of the following:

[0647] Sending node ID: used to identify the node that sends the message.

[0648] Receiving node ID: used to identify the node that receives the message.

[0649] UE ID: used to identify the UE corresponding to the slice-related self-optimization information.

[0650] · Information of the slice accessed before the switch: used to indicate the information and / or information list of the slice accessed before the switch. It may include one or more of the following: the slice identifier accessed before the switch, the access time corresponding to the slice accessed before the switch, the departure time corresponding to the slice accessed before the switch, the access time and / or the stay time corresponding to the slice accessed before the switch. In some embodiments, for example, the information is used to determine which cells can be selected as the target cells for the switch, for example, the cell of the slice accessed before the switch can be used as the target cell for the switch. In some other embodiments, for example, the information can be used to determine whether slice remapping occurs during the switch, and / or whether the remapping strategy is correct.

[0651] · Information on slices accessed in the source cell: used to indicate information and / or a list of slices accessed in the source cell. It may include one or more of the following: an identifier of a slice accessed in the source cell, an access time corresponding to the slice accessed in the source cell, a departure time corresponding to the slice accessed in the source cell, an access time and / or a stay time corresponding to the slice accessed in the source cell. In some embodiments, for example, the information may be used to determine whether slice remapping occurs before and after the switch, and / or whether the remapping strategy is correct. In some embodiments, for example, the information is used to determine which cells can be selected as target cells for the switch, for example, a cell of a slice accessed in the source cell may be used as a target cell for the switch, or a cell of a slice accessed in the source cell may not be used as a target cell for the switch.

[0652] Slice information supported by the source cell: used to indicate the slice information supported by the source cell. It may include one or more of the following: slice identifiers and / or identifier lists supported by the source cell.

[0653] · Information of the slice accessed after the switch: used to indicate the slice information and / or information list accessed after the switch. It may include one or more of the following: the slice identifier accessed after the switch, the access time corresponding to the slice accessed after the switch, the departure time corresponding to the slice accessed after the switch, the access time and / or the stay time corresponding to the slice accessed after the switch. In some embodiments, for example, this information can be used to determine whether slice remapping occurs before and after the switch, and / or whether the remapping strategy is correct. In some embodiments, for example, this information is used to determine which cells can be selected as the target cell for the switch, for example, the cell of the slice accessed after the switch can be used as the target cell for the switch, or the cell of the slice accessed after the switch can not be used as the target cell for the switch.

[0654] · Information on slices accessed in the target cell: used to indicate information and / or a list of slices accessed in the target cell. It may include one or more of the following: an identifier of a slice accessed in the target cell, an access time corresponding to the slice accessed in the target cell, a departure time corresponding to the slice accessed in the target cell, an access time and / or a stay time corresponding to the slice accessed in the target cell. In some embodiments, for example, the information may be used to determine whether slice remapping occurs before and after the switch, and / or whether the remapping strategy is correct. In some embodiments, for example, the information is used to determine which cells can be selected as target cells for switching, for example, a cell of a slice accessed in the target cell may be used as a target cell for switching, or a cell of a slice accessed in the target cell may not be used as a target cell for switching.

[0655] Slice information supported by the target cell: used to indicate the slice information supported by the target cell. It may include one or more of the following: slice identifiers and / or identifier lists supported by the target cell.

[0656] · Information about the slice accessed before the link failure: used to indicate the information and / or information list of the slice accessed before the link failure. It may include one or more of the following: the slice identifier accessed before the link failure, the access time corresponding to the slice accessed before the link failure, the departure time corresponding to the slice accessed before the link failure, the access time and / or the stay time corresponding to the slice accessed before the link failure. In some embodiments, for example, the information is used to determine which cells can be selected as the target cells for switching, for example, the cell supporting the slice accessed before the link failure can be used as the target cell for switching, or the cell supporting the slice accessed before the link failure is not used as the target cell for switching. In some other embodiments, for example, the information can be used to determine whether slice remapping occurred before the link failure, and / or whether the remapping strategy is correct. In other embodiments, for example, the information can be used to determine whether the slice remapping strategy is appropriate, and / or to select an appropriate remapped slice.

[0657] Slice information supported by the cell accessed before the link failure: used to indicate the slice information and / or information list supported by the cell accessed before the link failure. It may include one or more of the following: slice identifiers and / or identifier lists supported by the cell accessed before the link failure.

[0658] · Information of the slice accessed after the link failure: used to indicate the slice information and / or information list accessed after the link failure. It may include one or more of the following: the slice identifier accessed after the link failure, the access time corresponding to the slice accessed after the link failure, the departure time corresponding to the slice accessed after the link failure, the access time and / or the stay time corresponding to the slice accessed after the link failure. In some embodiments, for example, the information can be used to determine whether slice remapping occurred before the link failure, and / or whether the remapping strategy is correct. In some embodiments, for example, the information is used to determine which cells can be selected as the target cells for switching, for example, the cell that supports the slice accessed after the link failure can be used as the target cell for switching. In some other embodiments, for example, the information can be used to determine whether slice remapping occurred before the link failure, and / or whether the remapping strategy is correct. In other embodiments, for example, the information can be used to determine whether the slice remapping strategy is appropriate, and / or to select an appropriate remapped slice.

[0659] Slice information supported by the cell accessed after link failure: used to indicate slice information and / or information list supported by the cell accessed after link failure. It may include one or more of the following: slice identifiers and / or identifier lists supported by the cell accessed after link failure.

[0660] ·Reconnected slice information: used to indicate the reconnected slice information and / or information list. It may include one or more of the following: the reconnected slice identifier, the access time corresponding to the reconnected slice, the departure time corresponding to the reconnected slice, the access time and / or the stay time corresponding to the reconnected slice. In some embodiments, for example, the reconnected slice may be a slice that is reconnected after a link failure and / or a switching failure occurs. In some embodiments, for example, this information may be used to determine whether slice remapping is appropriate. In yet other embodiments, for example, this information may be used to determine whether the coverage of the slice is appropriate. In some embodiments, for example, this information is used to determine which cells can be selected as target cells for switching, for example, a cell that supports the reconnected slice can be used as a target cell for switching.

[0661] Slice information supported by the reconnected cell: used to indicate the slice information supported by the reconnected cell. It may include one or more of the following: slice identifiers and / or identifier lists supported by the reconnected cell.

[0662] Information of the slice you want to access: used to indicate the slice information and / or information list that the UE wants to access. It may include one or more of the following: the slice identifier and / or identifier list that the UE wants to access, the access time corresponding to the slice you want to access, the departure time corresponding to the slice you want to access, the access time and / or the stay time corresponding to the slice you want to access. In some embodiments, for example, the information is used to determine which cells can be selected as the target cell for handover, for example, a cell that supports the slice you want to access can be used as the target cell for handover.

[0663] ·Information of slices actually accessed: used to indicate information and / or information list of slices actually accessed by the UE. It may include one or more of the following: an identifier and / or identifier list of slices actually accessed, an access time corresponding to the slices actually accessed, a departure time corresponding to the slices actually accessed, an access time and / or a stay time corresponding to the slices actually accessed. In some embodiments, for example, the information is used to determine which cells can be selected as target cells for switching, for example, a cell supporting the slices actually accessed can be used as a target cell for switching.

[0664] Cause of failure: For example, it may include one or more of the following: no available slice for access, no available slice for handover. The failure may be one or more of the following: link failure, handover failure, random access failure, etc.

[0665] Random access purpose: For example, it may include one or more of the following: No slices are available for access.

[0666] Step 1804A: The twentieth node may make self-optimization decisions and / or update configurations based on the received slice-related self-optimization information, or the twentieth node may forward the information to other nodes for the other nodes to formulate self-optimization strategies and / or update configurations.

[0667] Fig.19A A schematic diagram of one aspect of a method for supporting slicing according to an embodiment of the present disclosure is shown. Specifically, Fig.19AThe process of interactive slice-related measurement and / or data collection configuration between two nodes is shown, so that the twenty-first node can collect data and / or configure other nodes to collect data and / or measure according to the slice-related measurement and / or data collection configuration. The twenty-first node can send the collected slice-related measurement and / or data collection results to the twenty-second node, and the twenty-second node can use the slice-related measurement and / or data collection results to make self-optimization decisions and / or update configurations and / or AI / ML related operations. Among them, AI / ML related operations include one or more of the following: AI / ML model training, AI / ML model reasoning, AI / ML model evaluation, AI / ML performan...

Claims

1. A method performed by a first node in a wireless communication system, comprising: receiving a second message from a user equipment UE or a third node, where the second message includes predicted slice information of the UE; Selecting a target node based on the predicted slice information; Sending a seventeenth message to the target node, where the seventeenth message includes information about an experience quality parameter associated with the UE; as well as An eighteenth message is received from the target node, the eighteenth message including a slice remapping decision associated with the UE and / or an applicable time of the slice remapping decision.

2. The method according to claim 1, further comprising: sending a first message to the UE or the third node, where the first message includes a request for the predicted slice information, The second message is sent by the UE or the third node based on the first message.

3. The method according to claim 1, wherein: The seventeenth message also includes the predicted slice information and / or slice performance request related information, wherein the slice performance request related information is used to trigger the target node to collect slice performance, and wherein the predicted slice information is used for making switching decisions related to the slice.

4. The method according to claim 1, further comprising: A nineteenth message is sent to the UE, wherein the nineteenth message includes first information about the target node's support for the slice.

5. The method according to claim 4, wherein: The first information includes priority information of the target node, wherein the priority information is determined based on the number of predicted slices included in the predicted slice information that the target node can support.

6. The method according to claim 1, further comprising: A seventh message is received from the target node, wherein the seventh message includes information about slice-related performance acquired by the target node.

7. A method performed by a user equipment UE in a wireless communication system, comprising: Sending a second message to the first node, where the second message includes predicted slice information of the UE; as well as receiving a nineteenth message from said first node, Wherein, the predicted slice information is used by the first node to select a target node; wherein information about the experience quality parameter associated with the UE is included in a seventeenth message, and the seventeenth message is sent from the first node to the target node; and The slice remapping decision associated with the UE and / or the applicable time of the slice remapping decision are included in an eighteenth message, and the eighteenth message is sent from the target node to the first node.

8. The method according to claim 7, wherein: The nineteenth message includes first information about the target node's support for the slice, The first information includes priority information of the target node, wherein the priority information is determined based on the number of predicted slices included in the predicted slice information that the target node can support.

9. The method according to claim 7, further comprising: receiving a first message from the first node, the first message comprising a request for the predicted slice information, and The second message is sent to the first node based on the first message.

10. The method according to claim 7, wherein: The seventeenth message also includes the predicted slice information and / or slice performance request related information, wherein the slice performance request related information is used to trigger the target node to collect slice performance, and wherein the predicted slice information is used for making switching decisions related to the slice.

11. A method performed by a second node in a wireless communication system, comprising: receiving a seventeenth message from the first node, the seventeenth message including information of a quality of experience parameter associated with a user equipment UE; as well as An eighteenth message is sent to the first node, where the eighteenth message includes a slice remapping decision associated with the UE and / or an applicable time of the slice remapping decision.

12. The method according to claim 11, wherein: The seventeenth message also includes predicted slice information and / or slice performance request related information of the UE, wherein the slice performance request related information is used to trigger the second node to collect slice performance.

13. The method according to claim 11, further comprising: A seventh message is sent to the first node, wherein the seventh message includes information about slice-related performance obtained by the second node.

14. The method according to claim 11, further comprising: receiving a fifth message from a third node, wherein the fifth message includes slice load information acquired by the third node; A slice remapping decision associated with the UE and / or an applicable time of the slice remapping decision is determined based on the quality of experience parameter and / or the slice load information.

15. The method according to claim 11, further comprising: An eighth message and / or a ninth message is received from a third node, wherein the eighth message includes information indicating that the predicted slice load is too large, and the ninth message includes information indicating the amount of load that the second node can receive.

Images