Network slice replacement method and device for multimedia service

Abstract

The present disclosure relates to a 5G or 6G communication system supporting a higher data transmission rate. The method includes configuring a first network slice with a first configuration and configuring a first action to avoid network slice replacement. The method also includes receiving an indication of a network slice replacement to replace the first network slice with a second network slice. The method also includes instructing to perform the first action to avoid network slice replacement. Further, the method includes migrating the application flow from the first network slice to a second network slice having a second configuration, the first configuration being different from the second configuration, when a first action for avoiding network slice replacement is not successfully performed. The method also includes monitoring a service using the second network slice.

Description

Technical Field

[0001] This disclosure generally relates to multimedia devices and processes. More specifically, this disclosure relates to network slice replacement technology for multimedia services. Background Technology

[0002] 5G mobile communication technology defines a wide frequency band, enabling high transmission rates and new services. This can be achieved not only in sub-6 GHz bands such as 3.5 GHz, but also in "above 6 GHz" bands known as millimeter wave (mmWave), including 28 GHz and 39 GHz. Furthermore, to achieve transmission rates 50 times faster than 5G and ultra-low latency of 1 / 10, consideration is being given to implementing sixth-generation (6G) mobile communication technology (referred to as "super 5G systems") in terahertz (THz) bands (e.g., the 95 GHz to 3 THz band).

[0003] In the early stages of 5G mobile communication technology development, to support enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC) services and meet performance requirements, standardization work has been ongoing on the following technologies: beamforming and massive MIMO technologies for mitigating radio wave path loss and increasing radio wave transmission distance in millimeter waves; parameter set support (e.g., support for multiple subcarrier spacings) for efficient utilization of millimeter wave resources and dynamic operation of time slot formats; initial access technologies for supporting multi-beam transmission and broadband; definition and operation of bandwidth portion (BWP); novel channel coding methods such as low-density parity-check (LDPC) codes for large-scale data transmission and polar codes for highly reliable transmission of control information; L2 preprocessing; and network slicing technologies for providing dedicated networks for specific services.

[0004] Currently, considering the services that 5G mobile communication technology will support, discussions are underway regarding improvements and performance enhancements to the initial 5G mobile communication technology. Physical layer standardization work is also underway for the following technologies: Vehicle-to-Everything (V2X) technology, which uses vehicle-transmitted location and status information to assist autonomous vehicles in making driving decisions and improve user convenience; New Radio Unlicensed (NR-U) technology, designed to meet various regulatory requirements for system operation in unlicensed frequency bands; NR UE energy-saving technology; UE-satellite direct communication technology (Non-Terrestrial Network (NTN) technology) to provide coverage for areas where communication with terrestrial networks is impossible; and positioning technology.

[0005] In addition, standardization efforts are ongoing for the air interface architecture / protocols of the following technologies: Industrial Internet of Things (IIoT) supporting new services through interconnection and integration with other industries; Integrated Access Backhaul (IAB) providing nodes for network service area extension by unifying support for wireless backhaul and access links; mobility enhancements including conditional handover and Dual Active Protocol Stack (DAPS) handover; and two-step random access (NR two-step RACH) for simplifying random access procedures. Regarding system architecture / services, standardization efforts are also ongoing for 5G baseline architectures combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies (e.g., service-based architectures or service-based interfaces), and for Mobile Edge Computing (MEC) providing services based on UE location.

[0006] With the commercialization of 5G mobile communication systems, an exponentially growing number of interconnected devices will be connected to the communication network. Enhanced functionality and performance of 5G mobile communication systems, as well as integrated operation of interconnected devices, are expected to become essential. To this end, new research in the following related areas is on the agenda: Extended Reality (XR) for efficient support of Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR); leveraging Artificial Intelligence (AI) and Machine Learning (ML) to improve 5G performance and reduce complexity; AI service support; Metaverse service support; and drone communication.

[0007] Furthermore, this development of 5G mobile communication systems will lay the foundation for the development of the following technologies: novel waveforms required for terahertz band coverage in 6G mobile communication technologies; multi-antenna transmission technologies such as full-dimensional MIMO (FD-MIMO), array antennas, and massive MIMO; metamaterial-based lenses and antennas for improving terahertz band signal coverage; high-dimensional spatial multiplexing technologies utilizing orbital angular momentum (OAM); and reconfigurable smart surfaces (RIS) technology. It also lays the foundation for the development of the following technologies: full-duplex technologies to improve the frequency efficiency of 6G mobile communication technologies and enhance system networks; AI-based communication technologies that leverage satellites and AI from the design phase to achieve system optimization and incorporate end-to-end AI support; and next-generation distributed computing technologies that utilize ultra-high-performance communication and computing resources to provide services with complexity exceeding the limits of UE operational capabilities. Summary of the Invention

[0008] [Technical Solution]

[0009] This disclosure provides a network slice replacement solution for multimedia services.

[0010] In one embodiment, the method includes: configuring a first network slice using a first configuration, and configuring a first action to avoid network slice replacement. The method further includes receiving an instruction to replace the first network slice with a second network slice. The method also includes instructing the execution of the first action to avoid network slice replacement. Furthermore, the method includes migrating an application flow from the first network slice to a second network slice having a second configuration, different from the first configuration, when the first action to avoid network slice replacement fails. The method also includes monitoring services using the second network slice.

[0011] In one embodiment, the application functionality includes a transceiver and a processor. The processor is configured to: receive a configuration of a first network slice having a first configuration, and receive a configuration for a first action to avoid network slice replacement. The processor is also configured to receive an instruction to replace the first network slice with a second network slice. The processor is further configured to instruct the execution of the first action to avoid network slice replacement. Furthermore, the processor is configured to migrate the application flow from the first network slice to a second network slice having a second configuration, different from the first configuration, when the first action to avoid network slice replacement fails. The processor is also configured to monitor services using the second network slice.

[0012] Those skilled in the art can clearly understand the technical features of this disclosure from the following drawings, description and claims. Attached Figure Description

[0013] To gain a more complete understanding of this disclosure and its advantages, the following description is given in conjunction with the accompanying drawings, wherein the same reference numerals denote the same parts: Figure 1 An exemplary communication system according to an embodiment of this disclosure is shown; Figure 2 and Figure 3 An exemplary electronic device according to an embodiment of this disclosure is shown; Figures 4A and 4B illustrate an exemplary system for network slice replacement notification according to the present disclosure; Figure 5 An exemplary system for network slice replacement conditions according to this disclosure is shown; Figure 6 An exemplary method for network slice replacement for multimedia services according to this disclosure is shown; Figure 7 An exemplary system for network slice replacement according to this disclosure is shown; Figure 8 An exemplary system for providing information on network slice replacement on demand, according to this disclosure, is shown; Figure 9 An example of a method for dynamic policy invocation according to this disclosure is shown; Figure 10 An exemplary method is shown to illustrate the impact of this disclosure on dynamic policy processes when the ASP is unaware of network slice replacement; Figure 11 An exemplary system for a user equipment (UE) to notify an AF of a network slice replacement, according to the present disclosure, is shown. Figure 12 An exemplary system for a UE to notify an AF of a network slice replacement, according to this disclosure, is shown. Figure 13 An exemplary system for offloading multicast sessions of a portion of users during network slice replacement, according to this disclosure, is shown. Figure 14 An exemplary system for proactively notifying an AF of network slice replacement according to this disclosure is shown; Figures 15A and 15B illustrate an exemplary method for configuring a policy template for alternative list network slice selection assistance information (S-NSSAI) in the event of network slice replacement, according to the present disclosure. Figures 16A and 16B illustrate exemplary methods for configuring a policy template referencing alternative S-NSSAI after network slice replacement, according to the present disclosure. Figure 17 An exemplary system is shown, according to the present disclosure, for facilitating session termination for some users to avoid network slice replacement; Figure 18 An exemplary system according to this disclosure is shown for avoiding network slice replacement by reducing available adapters; Figure 19 An exemplary system for offloading multicast sessions of a portion of users during network slice replacement, according to this disclosure, is shown. Figure 20 An exemplary system for network slice replacement with multiple network slices according to this disclosure is shown; and Figure 21 An exemplary method for network slice replacement for multimedia services is shown according to this disclosure. Detailed Implementation

[0014] In one embodiment of this disclosure, a method for managing network slice replacement in a communication system is provided. The method includes: configuring a first network slice using a first configuration; configuring a first action to avoid network slice replacement; receiving an instruction to replace the first network slice with a second network slice; instructing the execution of the first action to avoid network slice replacement; when the first action to avoid network slice replacement fails, migrating application flows from the first network slice to a second network slice having a second configuration, the first configuration being different from the second configuration; and monitoring services using the second network slice.

[0015] In one embodiment, the method wherein the first action for avoiding network slice replacement is configured based on feedback from the user equipment (UE).

[0016] In one embodiment, the method includes a first action for avoiding network slice replacement, which includes at least one of the following: reducing service availability, narrowing the service area, increasing latency tolerance, reducing throughput per network slice, reducing support for group communication, reducing service adaptation, or reducing the number of supported UEs.

[0017] In one embodiment, the method includes: determining whether a service meets a minimum service level agreement (SLA), and stopping or suspending the service after determining that the minimum SLA is not met.

[0018] In one embodiment, the method further includes: receiving a second configuration and using the second configuration to configure the second network slice prior to a network slice replacement instruction.

[0019] In one embodiment, the method further includes: receiving a second configuration and using the second configuration to configure the second network slice after a network slice replacement instruction.

[0020] In one embodiment, the method further includes: specifying a minimum network slice configuration descriptor that provides an absolute minimum value for a second network slice parameter.

[0021] In one embodiment, the method further includes: configuring a second action to ensure the performance of the service after a network slice replacement; and instructing the second action to be performed after the network slice replacement.

[0022] In one embodiment, the method includes a second action for ensuring service performance, comprising at least one of the following: checking the minimum service level agreement, determining that the degradation is above a threshold, or checking the minimum number of users.

[0023] In one embodiment, the method includes: the indication includes a time for network slice replacement; and the indication to perform the first action includes indicating at least a portion of performing the first action before the time for network slice replacement.

[0024] In one embodiment of this disclosure, an electronic device is provided for managing network slice replacement in a communication system. The electronic device includes: a memory storing one or more instructions; and at least one processor. The at least one processor is configured to execute the one or more instructions to: receive a configuration of a first network slice having a first configuration; receive a configuration for a first action to avoid network slice replacement; receive an instruction to replace the first network slice with a second network slice; instruct to perform the first action to avoid network slice replacement; when the first action to avoid network slice replacement fails, migrate application flows from the first network slice to a second network slice having a second configuration, the first configuration being different from the second configuration; and monitor services using the second network slice.

[0025] In one embodiment, in the electronic device, the first action to avoid network slice replacement is configured based on feedback from the user device.

[0026] In one embodiment, the first action to avoid network slice replacement includes at least one of the following: reducing the availability of the service, narrowing the service area, increasing latency tolerance, reducing the throughput of each network slice, reducing support for group communication, reducing service adaptation, or reducing the number of supported UEs.

[0027] In one embodiment, in the electronic device, for the purpose of monitoring the service, the processor is configured to execute one or more instructions to: determine whether the service meets the minimum service level agreement (SLA), and, upon determining that the minimum SLA is not met, stop or suspend the service.

[0028] In one embodiment, in the electronic device, the processor is further configured to execute the one or more instructions to: receive the second configuration before the network slice replacement instruction, and use the second configuration to configure the second network slice.

[0029] Before proceeding with the following detailed description, it may be helpful to define certain words and phrases in this patent document. The term “coupled” and its derivatives refer to any direct or indirect communication between two or more elements, regardless of whether these elements are physically in contact with each other. The terms “transmit,” “receive,” and “communicate,” and their derivatives cover both direct and indirect communication. The terms “including” and “contains,” and their derivatives refer to, but are not limited to, those including, those including, and / or. The term “associated with” and its derivatives refer to including, being contained within, interconnected with, containing, being included in, connected to or coupled with, able to communicate with, cooperate with, interleaved, juxtaposed, proximate, bound to or bound to, having, possessing the attributes of, having a relationship with, etc. The term “controller” refers to any device, system, or part thereof that controls at least one operation. Such a controller may be implemented by hardware or a combination of hardware and software and / or firmware. The functionality associated with any particular controller may be centralized or distributed, whether local or remote. When used with a list of items, the phrase "at least one" means that different combinations of the listed items may be used, and only one item is required in the list. For example, "at least one of A, B, and C" includes the following combinations: A, B, C, A and B, A and C, B and C, and A, B, and C.

[0030] Furthermore, the various functions described below may be implemented or supported by one or more computer programs, each computer program being formed by computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, programs, functions, objects, classes, instances, associated data, or portions thereof suitable for implementation in appropriate computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of computer-accessible medium, such as read-only memory (ROM), random access memory (RAM), hard disk drive, optical disc (CD), digital video disc (DVD), or any other type of storage. "Non-transitory" computer-readable media does not include wired, wireless, optical, or other communication links that transmit transient electrical or other signals. Non-transitory computer-readable media includes media that permanently store data and media that store and subsequently rewrite data, such as rewritable optical discs or erasable storage devices.

[0031] This patent document also provides definitions for certain other words and phrases. Those skilled in the art will understand that, in many cases (if not most), such definitions apply to the prior and future use of these words and phrases.

[0032] Network slicing is a promising technology in 5G networks. It allows the deployment of multiple logical networks on the same network hardware. Each logical network can be independently deployed, configured, and managed to handle aspects such as QoS and security, thus creating one or more network slices. Each network slice can provide different levels of QoS or isolation capabilities to end customers. While network slicing offers numerous advantages to network operators and service providers, it involves creating and maintaining multiple software systems, which are prone to errors and reliability issues (as network slices require end-to-end management). Therefore, it is sometimes necessary to replace existing network slices with new ones. Without a proper network slice replacement mechanism, applications relying on these network slices will be significantly impacted.

[0033] The following discussion Figures 1 to 21 The various embodiments used to describe the principles of this disclosure are for illustrative purposes only and should not be construed as limiting the scope of this disclosure in any way. Those skilled in the art will understand that the principles of this disclosure can be implemented in any type of suitably configured device or system.

[0034] To meet the growing demand for wireless data services since the deployment of 4G communication systems and to support various vertical applications, 5G / NR communication systems have been developed and are being deployed. 5G / NR communication systems are expected to be implemented at higher frequency bands (millimeter waves) (e.g., 28 GHz or 60 GHz bands) to achieve higher data rates; or at lower frequency bands (e.g., 6 GHz) to support robust coverage and mobility. To reduce radio wave propagation loss and increase transmission distance, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO technologies are being researched in 5G / NR communication systems.

[0035] In addition, in 5G / NR communication systems, the development and improvement of system networks based on technologies such as advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, cooperative multipoint (CoMP), and receiver interference cancellation are also underway.

[0036] The discussion of 5G systems and their associated frequency bands is for reference only, as some embodiments of this disclosure can be implemented in 5G systems. However, this disclosure is not limited to 5G systems or their associated frequency bands, and embodiments of this disclosure can be used in any frequency band. For example, aspects of this disclosure can also be applied to the deployment of 5G communication systems, 6G, and even later versions, which may use terahertz (THz) frequency bands.

[0037] The application of computing technologies in media processing is expanding significantly, primarily due to the availability, convenience, and computing power of computing devices. Portable electronic devices (such as laptops and smartphones) are becoming increasingly prevalent because they are becoming more compact, while the processing power and resources contained within these devices are constantly increasing. Despite this improvement in processing power, portable electronic devices often struggle to provide the necessary processing capabilities for new services and applications, as these typically require more resources than what is contained within them. Therefore, there is a need for improved methods and apparatus for configuring and deploying media processing within networks.

[0038] Cloud media processing is gaining attention, where media processing workloads are deployed on networks (such as in the cloud) to leverage the advantages offered by the cloud, such as theoretically unlimited computing power, demand-based auto-scaling, and on-demand processing. End-user clients can request the deployment and configuration of media processing capabilities from network media processing providers as needed.

[0039] 5G network slicing is becoming a crucial supporting technology for providing differentiated QoS based on a set of service level agreements (SLAs) for customers / tenants. Mobile network operators (MNOs) deploy network slices according to the service needs of tenants / customers and run the services requested by tenants / customers within these network slices. MNOs, playing different roles, maintain these network slices, including orchestration, liveness monitoring, surveillance, and maintenance. However, because network slice resources are not reliable, network slices may fail to meet their initial deployment requirements, especially when some network slice resources do not provide the expected performance level. Mobile operators may replace these network slices with alternative network slices. Once the original network slices recover their expected performance, the MNO may reactivate them. Appropriate application-layer mechanisms need to be established to assist in maintaining QoS during network slice replacement.

[0040] Mobile network operators (MNOs) can leverage 5G network slicing technology to provide differentiated services to end users. Through network slicing, service providers and content providers (MNO customers) can lease MNO 5G networks to provide services to their end-user customers. However, network slicing is still in the early stages of standardization and deployment. Resources deployed by MNOs within network slices may not remain reliable in the long term, thus network slice performance may degrade periodically. One solution is to migrate application flows of service / content provider services from degraded network slices to alternative network slices. Effective configuration and orchestration capabilities are required to achieve this migration, and adaptive mechanisms can be utilized to avoid network slice replacement if necessary.

[0041] One of the actions performed by network functions is the network slice replacement process. However, the basis for network slice replacement, as well as the preprocessing and post-processing procedures for such replacement tasks, are currently unclear. This disclosure provides methods for configuring and managing the various processes involved in network slice replacement without affecting use cases and applications using the relevant network slices.

[0042] When a 5G network entity detects that certain network slices are not performing as expected, the MNO may decide to replace one or more of these network slices. However, typically, the replaced network slices cannot provide similar performance, thus directly impacting the Service Level Agreement (SLA). This disclosure describes aspects related to avoiding network slice replacement based on information from the UE. This disclosure also describes aspects related to reducing service level requirements using alternative network slices before the original network slices resume operation.

[0043] Resources deployed in a network slice include different types of resources (such as compute resources, storage resources, processing resources, etc.), and network functions, AF 410, data transfer functions, etc., are typically instantiated using these resources in a virtualized environment. However, in a virtualized deployment environment, resources may perform poorly, leading to a degraded network slice performance. One solution to this problem is to replace the primary network slice with an alternative network slice. Application flows can migrate from the primary network slice to the alternative network slice, and if a network entity decides to replace the primary network slice with an alternative network slice, the MNO may require configuration and deployment information from an external application service provider to handle its service traffic. This disclosure discusses methods by which application service providers assist network entities in handling network slice replacement tasks.

[0044] Figure 1 An exemplary communication system 100 according to an embodiment of this disclosure is shown. Figure 1 The illustrated embodiment of the communication system 100 is for illustrative purposes only. Other embodiments of the communication system 100 may be used without departing from the scope of this disclosure.

[0045] Communication system 100 includes network 102, which facilitates communication between various components within communication system 100. For example, network 102 may transmit IP packets, Frame Relay frames, Asynchronous Transfer Mode (ATM) cells, or other information between network addresses. Network 102 may include all or part of one or more local area networks (LANs), metropolitan area networks (MANs), wide area networks (WANs), global networks (such as the Internet), or any other communication system located in one or more locations.

[0046] In this example, network 102 facilitates communication between server 104 and multiple client devices 106-116. Client devices 106-116 may be, for example, smartphones, tablets, laptops, personal computers, wearable devices, HMDs, etc. Server 104 may represent one or more servers. Each server 104 includes any suitable computing or processing device that can provide computing services to one or more client devices (such as client devices 106-116). For example, each server 104 may include one or more processing devices, one or more memories storing instructions and data, and one or more network interfaces facilitating communication via network 102. In some embodiments, each server 104 may include an encoder.

[0047] Each client device 106-116 represents any suitable computing or processing device that interacts with at least one server (such as server 104) or other computing device via network 102. Client devices 106-116 include desktop computers 106, mobile phones or mobile devices 108 (such as smartphones), PDAs 110, laptops 112, tablets 114, and HMDs 116. However, any other or additional client devices may be used in the communication system 100. A smartphone is a type of mobile device 108, a handheld device with a mobile operating system and integrated mobile broadband cellular network connectivity, supporting voice, short message service (SMS), and internet data communication.

[0048] In this example, some client devices 108-116 communicate indirectly with network 102. For example, mobile device 108 and PDA 110 communicate through one or more base stations 118-120 (such as cellular base stations or eNodeBs). Additionally, laptop 112, tablet 114, and HMD 116 communicate through one or more wireless access points 120 (such as IEEE 802.11 wireless access points). It should be noted that these are for illustrative purposes only; each client device 106-116 may communicate directly with network 102 or indirectly through any suitable intermediary device / network.

[0049] In some embodiments, any of client devices 106-114 can securely and efficiently transmit information to another device (such as server 104). Furthermore, any of client devices 106-116 can trigger information transmission between itself and server 104. When connected to a head-mounted device via a bracket, any of client devices 106-114 can function as a VR display, similar to HMD 116. For example, when mobile device 108 is connected via a bracket system and worn in front of a user, it can function similarly to HMD 116. Mobile device 108 (or any other client device 106-116) can trigger information transmission between itself and server 104.

[0050] although Figure 1 An example of a communication system 100 is shown, but it is possible to modify it. Figure 1 Various changes can be made. For example, communication system 100 can include any number of each component and can be arranged in any suitable manner. Typically, computing and communication systems have multiple configurations. Figure 1 This disclosure is not intended to limit the scope to any particular configuration. Although Figure 1 An operating environment is shown that can use the various features disclosed in this patent document, but these features can be used in any other suitable system.

[0051] Figure 2 and Figure 3 An exemplary electronic device according to an embodiment of this disclosure is shown. Specifically, Figure 2 An exemplary server 200 is shown, and the server 200 may represent Figure 1 Server 104 in the context of server 200. Server 200 can represent one or more encoders, decoders, local servers, remote servers, cluster computers, and components operating as a seamless resource pool, cloud-based servers, etc. Server 200 can be... Figure 1 One or more of the client devices 106-116 or another server can access the server.

[0052] like Figure 2 As shown, server 200 includes bus system 205 that supports communication between at least one processing device (such as processor 210), at least one storage device 215, at least one communication interface 220 and at least one input / output (I / O) unit 225.

[0053] Processor 210 executes instructions that can be stored in memory 230. Processor 210 may include any suitable number and type of processors or other devices, and may be arranged in any suitable manner. Exemplary processor types 210 include microprocessors, microcontrollers, digital signal processors, field-programmable gate arrays, application-specific integrated circuits, and discrete circuits.

[0054] Memory 230 and persistent storage device 235 are examples of storage device 215, which represent any structure capable of storing and facilitating the retrieval of information, such as temporary or permanent data, program code, or other suitable information. Memory 230 may represent random access memory or any other suitable volatile or non-volatile storage device. Persistent storage device 235 may include one or more components or devices that support long-term data storage, such as read-only memory, hard disk, flash memory, or optical disk.

[0055] Communication interface 220 supports communication with other systems or devices. For example, communication interface 220 may include a network interface card or a wireless transceiver, facilitating communication via... Figure 1 The communication interface 220 supports communication via any suitable physical or wireless communication link(s). For example, the communication interface 220 can transmit a bit stream containing a three-dimensional point cloud to another device, such as one of client devices 106-116.

[0056] I / O unit 225 allows for data input and output. For example, I / O unit 225 can provide user input connections via a keyboard, mouse, keypad, touchscreen, or other suitable input device. I / O unit 225 can also send output to a display, printer, or other suitable output device. Note that I / O unit 225 can be omitted, for example, when performing I / O interaction with server 200 via a network connection.

[0057] It should be noted that, although Figure 2 Described as representing Figure 1 The server 104 may have the same or similar architecture as one or more of the client devices 106-116. For example, desktop computer 106 or laptop computer 112 may have the same architecture as the server 104. Figure 2 The same or similar structure is shown.

[0058] Figure 3 An exemplary electronic device 300 is shown, which can represent Figure 1 One or more of the client devices 106-116. Electronic device 300 can be a mobile communication device, such as a mobile station, user station, wireless terminal, or desktop computer (similar to...). Figure 1 Desktop computers 106), portable electronic devices (similar to) Figure 1 Mobile devices 108, PDAs 110, laptops 112, tablets 114, or HMDs 116, etc. In some embodiments, Figure 1One or more of the client devices 106-116 may include the same or similar configuration as electronic device 300. In some embodiments, electronic device 300 is an encoder, decoder, or both. For example, electronic device 300 can be used for data transmission, image or video compression, image or video decompression, encoding, decoding, and media rendering applications. Electronic device 300 may be a device for implementing the application functions of this disclosure for managing network slice replacement in a communication system.

[0059] like Figure 3 As shown, electronic device 300 includes an antenna 305, a radio frequency (RF) transceiver 310, a transmit (TX) processing circuitry 315, a microphone 320, and a receive (RX) processing circuitry 325. The RF transceiver 310 may include, for example, an RF transceiver, a Bluetooth transceiver, a WiFi transceiver, a Zigbee transceiver, an infrared transceiver, and various other wireless communication signals. Electronic device 300 also includes a speaker 330, a processor 340, an input / output (I / O) interface (IF) 345, an input device 350, a display 355, a memory 360, and a sensor 365. The memory 360 includes an operating system (OS) 361 and one or more applications 362.

[0060] RF transceiver 310 receives input RF signals from antenna 305 from an access point (such as a base station, WiFi router, or Bluetooth device) or other devices on network 102 (such as WiFi, Bluetooth, cellular, 5G, LTE, LTE-A, WiMAX, or any other type of wireless network). RF transceiver 310 down-converts the input RF signals to generate an intermediate frequency (IF) or baseband signal. The IF or baseband signal is sent to RX processing circuitry 325, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. RX processing circuitry 325 transmits the processed baseband signal to speaker 330 (e.g., for voice data) or processor 340 for further processing (e.g., for web browsing data).

[0061] The RX processing circuit 315 receives analog or digital voice data from the microphone 320, or other output baseband data from the processor 340. The output baseband data may include web page data, email, or interactive video game data. The TX processing circuit 315 encodes, multiplexes, and / or digitizes the output baseband data to generate a processed baseband or intermediate frequency (IF) signal. The RF transceiver 310 receives the processed baseband or IF signal from the TX processing circuit 315 and up-converts it into an RF signal, which is then transmitted through the antenna 305.

[0062] Processor 340 may include one or more processors or other processing devices. Processor 340 may execute instructions (such as OS 361) stored in memory 360 to control the overall operation of electronic device 300. For example, processor 340 may control the reception of forward channel signals and the transmission of reverse channel signals by RF transceiver 310, TX processing circuitry 325, and TX processing circuitry 315 according to known principles. Processor 340 may include any suitable number and type of processors or other devices, and may be arranged in any suitable manner. For example, in some embodiments, processor 340 includes at least one microprocessor or microcontroller. Exemplary processor types 340 include microprocessors, microcontrollers, digital signal processors, field-programmable gate arrays, application-specific integrated circuits (ASICs), and discrete circuits.

[0063] Processor 340 is also capable of executing other processes and programs residing in memory 360, such as operations for receiving and storing data. Processor 340 may move data into or out of memory 360 as needed by the executing processes. In some embodiments, processor 340 is configured to execute one or more applications 362 based on OS 361 or in response to signals from an external source or operator. Exemplary applications 362 may include encoders, decoders, VR or AR applications, camera applications (for still images and video), video telephony applications, email clients, social media clients, SMS messaging clients, virtual assistants, etc. In some embodiments, processor 340 is configured to receive and transmit media content.

[0064] The processor 340 is also coupled to an I / O interface 345, which provides the electronic device 300 with the ability to connect to other devices, such as client devices 106-114. The I / O unit 345 is the communication path between these accessories and the processor 340.

[0065] Processor 340 is also coupled to input device 350 and display 355. An operator of electronic device 300 can use input device 350 to input data or information to electronic device 300. Input device 350 may be a keyboard, touchscreen, mouse, trackball, voice input, or other device capable of serving as a user interface, allowing a user to interact with electronic device 300. For example, input device 350 may include voice recognition processing, allowing a user to input voice commands. In another example, input device 350 may include a touch panel, (digital) pen sensor, button, or ultrasonic input device. Touch panel may recognize touch input, for example, according to at least one scheme, such as a capacitive scheme, a pressure-sensitive scheme, an infrared scheme, or an ultrasonic scheme. Input device 350 may be associated with sensor 365 and / or camera by providing additional input to processor 340. In some embodiments, sensor 365 includes one or more inertial measurement units (IMUs) (such as accelerometers, gyroscopes, and magnetometers), motion sensors, optical sensors, cameras, pressure sensors, heart rate sensors, altimeters, etc. Input device 350 may also include control circuitry. In a capacitive solution, the input device 350 can recognize touch or proximity.

[0066] Display 355 may be a liquid crystal display (LCD), a light-emitting diode (LED) display, an organic LED (OLED), an active-matrix OLED (AMOLED), or other display capable of displaying text and / or graphics (such as from websites, videos, games, images, etc.). Display 355 may be sized to fit within an HMD. Display 355 may be a single display or multiple displays capable of creating a stereoscopic display. In some embodiments, display 355 is a head-up display (HUD). Display 355 may display three-dimensional objects, such as three-dimensional point clouds.

[0067] Memory 360 is coupled to processor 340. A portion of memory 360 may include RAM, and another portion may include flash memory or other ROM. Memory 360 may include persistent storage devices (not shown), which represent any structure capable of storing and facilitating the retrieval of information such as data, program code, and / or other suitable information. Memory 360 may include one or more components or devices supporting long-term data storage, such as read-only memory, hard disk, flash memory, or optical disk. Memory 360 may also contain media content. Media content may include various types of media, such as images, videos, 3D content, virtual reality content, augmented reality content, 3D point clouds, etc.

[0068] Electronic device 300 also includes one or more sensors 365 that can measure physical quantities or detect the activation state of electronic device 300 and convert the measured or detected information into electrical signals. For example, sensor 365 may include one or more buttons for touch input, a camera, a gesture sensor, an IMU sensor (such as a gyroscope or gyroscope sensor and accelerometer), an eye-tracking sensor, a barometric pressure sensor, a magnetic sensor or magnetometer, a grip sensor, a proximity sensor, a color sensor, a biophysical sensor, a temperature and humidity sensor, an illuminance sensor, an ultraviolet (UV) sensor, an electromyography (EMG) sensor, an electroencephalography (EEG) sensor, an electrocardiography (ECG) sensor, an IR sensor, an ultrasound sensor, an iris sensor, a fingerprint sensor, a color sensor (such as a red-green-blue (RGB) sensor), etc. Sensor 365 may also include control circuitry for controlling any sensors contained therein.

[0069] Electronic device 300 also includes one or more sensors 365 that are capable of measuring physical quantities or detecting the activation state of electronic device 300 and converting the measured or detected information into electrical signals. For example, sensor 365 may include one or more buttons for touch input, a camera, a gesture sensor, an IMU sensor (such as a gyroscope or gyroscope sensor and accelerometer), an eye-tracking sensor, a barometric pressure sensor, a magnetic sensor or magnetometer, a grip sensor, a proximity sensor, a color sensor, a biophysical sensor, a temperature and humidity sensor, an illuminance sensor, an ultraviolet (UV) sensor, an electromyography (EMG) sensor, an electroencephalography (EEG) sensor, an electrocardiography (ECG) sensor, an IR sensor, an ultrasound sensor, an iris sensor, a fingerprint sensor, a color sensor (such as a red-green-blue (RGB) sensor), etc. Sensor 365 may also include control circuitry for controlling any of the sensors contained therein.

[0070] although Figure 2 and Figure 3 An example of an electronic device is shown, but it is possible to... Figure 2 and Figure 3 Make various changes. For example, Figure 2 and Figure 3 The various components within can be combined, further subdivided, omitted, or additional components added according to specific needs. As a specific example, processor 340 can be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). Furthermore, like computing and communication, electronic devices and servers have a variety of configurations. Figure 2 and Figure 3 This disclosure is not intended to limit the scope to any particular electronic device or server.

[0071] Section 4.2.2 of 3GPP TR 26941 describes the network slice replacement procedure when a network slice is unavailable. Section 5.15.19 of 3GPP TS 23501 further details this procedure. As part of this procedure, the Access and Mobility Management Function (AMF) is triggered (either through local configuration or due to notification from the Operation, Management and Maintenance (OAM), Network Slice Selection Function (NSSF), or Policy Control Function (PCF)) to replace the current S-NSSAI with an alternative S-NSSAI. The notification from the OAM, NSSF, or PCF to the AMF may include alternative S-NSSAI information.

[0072] 3GPP TS 26501 and 3GPP TS 26512 define the 5G Media Streaming (5GMS) delivery process, in which 5GMS Application Service Providers (ASPs) perform service deployment at the 5GMS AF via the M1 interface. Section 7.9 of 3GPP TS 26512 describes the data model for policy template resources and the M1 policy template deployment API. The policy template data model includes network slice information as part of the ApplicationSessionContext attribute. The 5GMS AP can obtain this information from the OAM. However, if the network slice replacement process described in Section 5.15.19 of 3GPP TS 23.501 has been previously executed, it is unclear how to perform policy template deployment for the alternative S-NSSAI. This disclosure expands upon aspects relating to network slice replacement, which are described in U.S. Provisional Application No. 63543997 (Application No.: WD-202310-028-1-US0, Title: Managing Network Slice Replacement Using Application Layer Information and a Common Network Slice Template), version 7.0, filed October 13, 2023, and GSM Association Official Document NG.116 (June 17, 2022), the entire contents of which are incorporated herein by reference.

[0073] Through 5G network slicing, service providers or content providers (also known as ASPs) typically negotiate with network operators to deploy services (or introduce content) that are available to the operator's subscribers and the service provider's users. To deploy a service, the service provider negotiates a set of service requirements that the operator must provide so that the service provider can deliver the desired service experience that its users expect. One way to negotiate service requirements is using a Network Slice Template (NEST) standardized by the GSM Association (GSMA).

[0074] GSMA standardizes a set of attributes that characterize network slice types. For details of the standardized attribute set, please see https: / / www.gsma.com / newsroom / wp-content / uploads / NG.116-v7.0.pdf. In this disclosure, GSMA NEST attributes refer to the GSMA NEST specification. Some of the attributes defined by GSMA for NEST are shown in Table 1 below.

[0075] [Table 1]

[0076] Table 1 above lists only some exemplary properties of the GSMA NEST template. For the purposes of this disclosure, all properties specified in GSMA NEST apply.

[0077] Once the ASP negotiates and determines the network slicing parameters, the ASP requests the deployment of services within the carrier network. 3GPP SA4 standardized the interface between the ASP and carrier functions (such as Application Functions (AFs)) in TS 26501 and TS 26512. As specified in TS 26501 and TS 26512, among the multiple service configuration options configured by the ASF at the AF, one service configuration option is the policy template configuration specified in Section 7.9 of TS 26512. Some policy configuration parameters specified in TS 26512 are shown in Table 2 below.

[0078] [Table 2]

[0079] As shown in Table 2, a set of policy templates are configured for the media service. The policy templates are applicable to a given application session context, which contains network slice information (network sliceInfo) and DNN (DNN information).

[0080] 3GPP TR 28.809 is the result of a feasibility study that explores aspects of management data analytics. Section 6 of 3GPP TR 28.809 specifies use cases, potential requirements, and possible solutions for management data analytics. One of the service level specification-related issues described in Section 6.3.2 of 3GPP TR 28.809 is network slice load analysis—"Network slice load may vary over time." Therefore, initially allocated network resources may not always meet traffic requirements; for example, network slices may be overloaded or underutilized. Various factors can affect network slice load, such as the number of UEs accessing the network, the number of PDU sessions, service type, and end-user distribution. Control plane signaling overload and / or user plane data congestion can lead to network performance degradation. Furthermore, allocating too many resources to lightly loaded network slices can reduce resource efficiency.

[0081] Section 5.1 of TR 23700-41 describes the relevant critical issue "Critical Issue #1: Network Slice Service Continuity Support" using terminology similar to that described in the aforementioned 3GPP TR 28.809. Specifically, aspects related to service continuity are being investigated in two scenarios ("No Mobility" scenario and "Inter-RAN Mobility" scenario) when a network slice or network slice instance in the core network (CN) or target core network is overloaded or undergoing planned maintenance (such as network slice termination), and the network performance of the network slice cannot meet the SLA.

[0082] 3GPP SA2 has standardized the network slice replacement function, which is specified in Section 5.15.19 of 3GPP TS 23.501. As part of this process, when the current network slice cannot provide the required performance at a specific time, any of the AMF, PCF, NSSF, or OEM may decide to replace the current network slice for certain PDU sessions with an alternative network slice. However, the standardization and implementation of the network slice concept are still in their early stages, and therefore the network slice replacement process is not yet clearly defined.

[0083] Figures 4A and 4B illustrate exemplary systems 400 and 401 for network slice replacement notification according to the present disclosure. The embodiment of system 400 shown in Figures 4A and 4B is for illustrative purposes only. Figures 4A and 4B do not limit the scope of the present disclosure to any particular implementation of an electronic device.

[0084] As shown in Figure 4A, this information is exchanged with AF 410 when any of PCF 404, NSSF 406, or OEM 408 makes a decision to replace network slice 402. AF 410 then exchanges network slice replacement information with ASP 412.

[0085] As shown in Figure 4B, in step 1, ASP 412 can subscribe to network slice change information event notifications from AF 410. When a network slice event occurs in step 2, in step 3, AF 410 notifies ASP 412 of the event.

[0086] As shown in Figures 4A and 4B, if ASP 412 plans to deploy a service in a carrier network, it may become aware of potential network slice replacements. As part of network slice negotiation, OEM 408 may notify ASP 412 of conditions under which a given network slice 402 can be replaced by an alternative network slice 402. In this case, ASP 412 can configure parameters for the primary network slice 402 and the alternative network slice 402.

[0087] In addition to the parameters described in Table 1 and the GSMA-specified NEST template parameters used for primary network slice 402, ASP 412 can also configure the same set of parameters for alternative network slice 402. The network slice parameter configuration for alternative network slice 402 informs OEM 408 that, in the event that the operator decides to implement a network slice replacement procedure, ASP 412 is searching for alternative network slices 402 that can meet a given service requirement. The service requirements or attribute parameter configurations described in the GSMA NEST template for alternative network slice 402 can be lower than those for primary network slice 402. ASP 412 can specify a minimum network slice configuration descriptor that provides an absolute minimum parameter value for each attribute in the GSMA NEST template if the service of UE 414 is moved to alternative network slice 402. ASP 412 may not provide an absolute value for each attribute applicable to alternative network slice 402, but instead configure a network slice offset for that attribute compared to the attribute value of primary network slice 402. For example, if ASP412 configures a downlink throughput of 200 Mbps for each network slice 402, then for the same downlink throughput parameter for each alternative network slice 402, an offset of x% (e.g., 20%) can be specified. In this case, this signals to the network slice provider or operator that if the operator decides to proceed with network slice replacement, ASP 412 can reduce the downlink throughput in the alternative network slice 402 by 20%. This offset can be any mathematical offset (e.g., linear, exponential, etc.). In another option, ASP 412 can simply send a message to AF 410 to match the configuration of the alternative network slice 402 with the configuration of the primary network slice 402. For this option, in the service provision message from ASP 412 to AF 410, ASP 412 includes a Boolean variable called “Match Configuration”, and if this variable is set to true, instructs AF 410 to match the parameters in the alternative network slice 402 with the parameters in the primary network slice 402.

[0088] In addition to the configuration of the parameters for the policy applicable to primary network slice 402 as described in Table 2, ASP 412 can also configure policy parameters for alternative network slice 402. The configuration of the policy parameters for alternative network slice 402 informs the OEM that, in the event that the operator decides to implement a network slice replacement procedure, ASP 412 is looking for alternative network slices 402 that meet the policy requirements. The policy configuration for alternative network slice 402 can be lower than the policy configuration for primary network slice 402; that is, policy parameters that are part of the M1QoSSpecification structure specified in Section 6.5.3.4 of TS 26512 can have values ​​that are relatively lower than the values ​​of the same parameters used for primary network slice 402. ASP 412 can specify a minimum policy configuration descriptor, which provides an absolute minimum parameter value for each of the policy parameters applicable to alternative network slice 402. ASP 412 may not provide absolute values ​​for each of the policy parameters applicable to alternative network slice 402, but rather can provide an offset for the policy configuration compared to the policy value of primary network slice 402. For example, if ASP 412 is configured with a maximum bit rate uplink policy parameter of 50 Mbps, then for the same maximum bit rate uplink parameter, an offset of x% (e.g., 20%) can be specified for the alternative network slice 402. In this case, this signals to the network slice provider or operator that if the operator decides to proceed with the network slice replacement, ASP 412 can reduce the maximum bit rate uplink policy parameter in the alternative network slice 402 by 20%. The offset can be any mathematical offset (e.g., linear, exponential, etc.). In another option, ASP 412 can simply send a message to AF 410 to match the policy configuration of the alternative network slice 402 with the policy configuration of the primary network slice 402. For this option, in the service provision message from ASP 412 to AF 410, ASP 412 includes a Boolean variable called "Match Policy Configuration," and if this variable is set to true, it instructs AF 410 to match the parameters in the alternative network slice 402 with the parameters in the primary network slice 402.

[0089] During the service provision phase, ASP 412 may not be aware of potential network slice replacements. Without this information, ASP 412 continues with service configuration as specified in TS 26501 and TS 26512. Policy parameters are specified only by ASP 412 for the primary network slice 402. AF 410 then deploys and starts the service in network slice 402 as requested. After a period of time, network functions such as PCF 404, NSSF 406, and OEM 408 determine that the primary network slice 402 used for the service needs to be replaced by an alternative network slice 402. In this case, as described above in this disclosure, ASP 412 receives information about the network slice replacement from AF 410. When ASP 412 receives the network slice replacement information from AF 410, ASP 412 can configure parameters for the alternative network slice 402 at AF 410.

[0090] ASP 412 can configure the parameters described in Table 1 for alternative network slice 402 and the GSMA-specified NEST template parameters for updating sessions operating in primary network slice 402. The configuration of the parameters for alternative network slice 402 is similar to the configuration of the parameters for primary network slice 402. The configuration of the service requirements or attribute parameters for alternative network slice 402 described in the GSMA NEST template may be lower than the configuration of the service requirements or attribute parameters for primary network slice 402 described in the GSMA NEST template. ASP 412 can specify a minimum network slice configuration descriptor that provides the absolute minimum parameter value for each of the attributes in the GSMA NEST template compared to the parameters for primary network slice 402. ASP 412 may not provide an absolute value for each of the attributes applicable to alternative network slice 402, but instead configure a network slice offset for that attribute compared to the attribute value for primary network slice 402. For example, if ASP 412 configures a downlink throughput of 200 Mbps for each network slice 402, then for the same downlink throughput parameter for each alternative network slice 402, an offset of x% (e.g., 20%) can be specified. In this case, this signals to the network slice provider or operator that ASP 412 can reduce the downlink throughput by 20% in the alternative network slice 402. This offset can be any mathematical offset (e.g., linear, exponential, etc.). In another option, ASP 412 can simply send a message to AF 410 to match the configuration of the alternative network slice 402 with the configuration of the primary network slice 402. For this option, in the service provision message from ASP 412 to AF 410, ASP 412 includes a Boolean variable called “Match Configuration”, and if this variable is set to true, instructs AF 410 to match the parameters in the alternative network slice 402 with the parameters in the primary network slice 402.

[0091] ASP 412 can configure the policy parameters described in Table 2 for the policies applicable to alternative network slice 402 for updates of sessions operating in primary network slice 402. The configuration of the parameters for alternative network slice 402 is similar to the configuration of the parameters for primary network slice 402. The policy configuration for alternative network slice 402 can be lower than the policy configuration for primary network slice 402; that is, policy parameters that are part of the M1QoSSpecification structure specified in Section 6.5.3.4 of TS 26512 can have values ​​that are relatively lower than the values ​​of the same parameters for primary network slice 402. ASP 412 can specify a minimum policy configuration descriptor that provides the absolute minimum parameter value for each of the policy parameters applicable to alternative network slice 402 compared to the corresponding parameter for primary network slice 402. ASP 412 can choose not to provide absolute values ​​for each of the policy parameters applicable to alternative network slice 402, but instead configure an offset for the policy compared to the policy value for primary network slice 402. For example, if ASP 412 is configured with a maximum bit rate uplink policy parameter of 50 Mbps, then for the same maximum bit rate uplink parameter, an offset of x% (e.g., 20%) can be specified for the alternative network slice 402. In this case, this signals to the network slice provider or operator that ASP 412 can reduce the maximum bit rate uplink policy parameter by 20% in the alternative network slice 402. The offset can be any mathematical offset (e.g., linear, exponential, etc.). In another option, ASP 412 can simply send a message to AF 410 to match the policy configuration of the alternative network slice 402 with the policy configuration of the primary network slice 402. For this option, in the service provision message from ASP 412 to AF 410, ASP 412 includes a Boolean variable called "Match Policy Configuration," and if this variable is set to true, it instructs AF 410 to match the parameters in the alternative network slice 402 with the parameters in the primary network slice 402.

[0092] Although Figures 4A and 4B illustrate an exemplary system 400 for notifying network slice 402, various changes can be made to Figures 4A and 4B. For example, the number and location of the various components of system 400 can be varied as needed or desired. Furthermore, system 400 can be used in any other suitable multimedia process, and is not limited to the specific process described above.

[0093] Figure 5 An exemplary system 500 for network slice replacement according to the present disclosure is shown. Figure 5 The embodiment of system 500 shown is for illustrative purposes only. Figure 5 The scope of this disclosure is not limited to any particular implementation of an electronic device.

[0094] like Figure 5 As shown, network functions in a 5G network can determine whether to execute a network slice replacement procedure based on network slice conditions. However, it is unclear how such a decision is initially made. This disclosure describes a method in which the information used to execute the replacement procedure is specified by ASP 412. Additionally, it may include further information instructing AF 410 how to manage services as a result of executing the network slice replacement. ASP 412 may include the following information to AF 410 when executing the service provisioning procedure. The original procedures for service provisioning are described in TS26501 and TS 26512. The service configuration information from ASP 412 to AF 410 is supplemented below with the following information in Table 3.

[0095] [Table 3]

[0096] although Figure 5 An exemplary system 500 for network slice replacement conditions is shown, but it is possible to modify... Figure 5 Various modifications can be made. For example, the number and location of the various components of system 500 can be varied as needed or desired. Furthermore, system 500 can be used in any other suitable multimedia process, and is not limited to the specific process described above.

[0097] Figure 6 An exemplary method 600 for network slice replacement for multimedia services according to this disclosure is shown. For ease of explanation, Figure 6 Method 600 is described as using Figure 3 The method is performed by electronic device 300. However, method 600 can be used with any other suitable system and any other suitable electronic device, including... Figure 2 Server 200 and Figure 4A to Figure 5 , Figures 7 to 10 and Figures 14 to 20 ASP 412.

[0098] like Figure 6As shown, in step 602, electronic device 300 performs service provisioning and configuration for network slice replacement. The provided and configured information includes the conditions for network slice replacement, actions and conditions for avoiding network slice replacement, and actions after network slice replacement. The electronic device performs service provisioning and configuration at AF 410 within the operator's network. As part of the service configuration information, if ASP 412 is aware of a potential network switching replacement, ASP 412 provides an alternative network slice 402 and a primary network slice 402. Alternatively, if ASP 412 is not aware of a potential network slice replacement, but is subsequently notified by AF 410, ASP 412 may update the configuration for the alternative network slice 402. The types of configurations for the alternative network slice 402 in relation to the primary network slice 402 have been described earlier in this disclosure. Furthermore, as described in this disclosure, ASP 412 configures the conditions for network slice replacement, the conditions for avoiding network replacement, and the actions to be performed after network slice replacement at AF 410. After service provisioning, the service begins and continues as provided by ASP 412.

[0099] In step 604, electronic device 300 determines whether to perform network slice replacement. If network slice replacement is not performed, service continues. When a network (e.g., PCF 404, NSSF 406, OEM 408, etc.) detects that network slice replacement is required, AF 410 performs a condition / action to avoid network slice replacement, as described in this disclosure.

[0100] When it is determined that network slice replacement should be performed, in step 606, electronic device 300 performs actions to avoid network slice replacement. Examples of actions to avoid network slice replacement are shown in Table 5. For example, actions to avoid network slice replacement may include at least one of the following: reducing service availability, reducing service area, increasing latency tolerance, reducing throughput per network slice, reducing support for group communication, reducing service adaptation, and reducing the number of supported UEs 414. Actions to avoid network slice replacement can be configured based on feedback from UEs 414.

[0101] In step 608, the electronic device 300 determines whether the action to avoid network slice replacement negates the need for network slice replacement. The conditions for network slice replacement are compared with service parameters to determine whether network slice replacement can be avoided.

[0102] In step 610, the electronic device 300 performs network slice replacement by moving the application flow to the alternative network slice 402. After performing the action to avoid network slice replacement, if the network still deems network slice replacement necessary, the primary network slice 402 is replaced by the alternative network slice 402, provided that the alternative network slice 402 meets the service requirements provided by ASP 412.

[0103] In step 612, for the application flow, electronic device 300 determines whether network slice replacement to alternative network slice 402 has sufficient performance. This determination may be based on conditions for network slice replacement. Electronic device 300 may receive an instruction for network slice replacement. This instruction may be for performing network slice replacement immediately or for performing network slice replacement at a specified time. In step 2108, electronic device 300 may perform a first action to avoid network slice replacement.

[0104] In step 614, electronic device 300 performs the actions following the network slice replacement. After performing the network slice replacement, all actions following the network slice replacement are executed. Electronic device 300 can determine whether the service meets the minimum SLA, and if it is determined that the minimum SLA is not met, it stops or suspends the service.

[0105] although Figure 6 An example of a method 600 for network slice replacement for multimedia services is shown, but it is possible to modify it further. Figure 6 Make various changes. For example, although it is shown as a series of steps, Figure 6 The steps in the process can overlap, occur in parallel, or occur any number of times.

[0106] Figure 7 An exemplary system 700 for network slice replacement possibilities is shown according to this disclosure. Figure 7 The embodiment of system 700 shown is for illustrative purposes only. Figure 7 The scope of this disclosure is not limited to any particular implementation of an electronic device.

[0107] like Figure 7As shown, when a network function anticipates the possibility of a network slice replacement, system 700 can provide a notification of the network slice replacement well in advance. This is in a situation where the conditions for network slice replacement have not yet been met, but the network function (e.g., AF 410, Network Data Analysis Function (NWDAF)) determines that a network slice replacement occurring in the near future is beyond a reasonable probability. In this case, AF 410 can receive a notification of the anticipated network slice replacement from the network function, which includes additional information such as a "replacement time" with a value approximating the expected time of the network slice replacement. When AF 410 receives the message with the expected time of the network switchover replacement, AF 410 can notify ASP 412 of this future event. When ASP 412 receives this message from AF 410, ASP 412 can perform any of the steps described in this disclosure, including providing an alternative network slice 402 (if known) or negotiating a request for an alternative network slice 402 with OAM, etc.

[0108] although Figure 7 An exemplary system 700 is shown, illustrating the possibilities for network slice replacement, but alternatives are possible. Figure 7 Various modifications can be made. For example, the number and location of the various components of system 700 can be varied as needed or desired. Furthermore, system 700 can be used in any other suitable multimedia process, and is not limited to the specific process described above.

[0109] Figure 8 An exemplary system 800 for providing network slice replacement information on demand, according to this disclosure, is shown. Figure 8 The embodiment of system 800 shown is for illustrative purposes only. Figure 8 The scope of this disclosure is not limited to any particular implementation of an electronic device.

[0110] like Figure 8 As shown, System 800 provides a process for on-demand network slice replacement. Using this process, network slice replacement is performed on demand, that is, well before the replacement conditions are met. To facilitate this process, ASP 412 includes the information shown in Table 4 in its service configuration message to AF 410.

[0111] [Table 4]

[0112] although Figure 8 An exemplary system 800 for providing network slice replacement information on demand is shown, but it is possible to provide more detailed information on network slice replacement. Figure 8 Various modifications can be made. For example, the number and location of the various components of system 800 can be varied as needed or desired. Furthermore, system 800 can be used in any other suitable multimedia process, and is not limited to the specific process described above.

[0113] Figure 9 An exemplary method 900 for dynamic policy invocation according to this disclosure is shown. For ease of explanation, Figure 9 Method 900 is described as using Figure 4A to Figure 5 , Figures 7 to 10 as well as Figures 14 to 20 Method 900 can be implemented using UE 414, AF 410, and ASP412. However, it can be used with any other suitable system and any other suitable electronic device.

[0114] As described in Section 4.2.3 of 3GPP TR 26941, Section 5.1 of 3GPP TR 23700-41 examines key issues related to network slice service continuity. Accordingly, network slice 402 or a network slice instance may become overloaded, or the performance of network slice 402 may fall below its SLA requirements.

[0115] The recommendation in Section 8.1 of TR 23700-41 is that 5G systems identify alternative network slices 402 to migrate application flows from PDU sessions in the current network slice 402 to existing or new PDU sessions in the selected alternative network slice 402. When 5G media streaming sessions are carried over PDU sessions that cannot be transparently migrated to the application layer with the support of service continuity procedures, the impact on ongoing 5G media streaming sessions can be investigated. Figure 9 As shown, in step 902, 5GMS ASP 412 is configured to provide a session at 5GMS AF 410.

[0116] In step 904, 5GMS ASP 412 provides service notification information to the 5GMS-aware application in UE 414, as described in steps 4 of Section 5.1 (for downlink stream transmission) and 4 of Section 6.1 (for uplink stream transmission) of TS 26.501. If the 5GMS client in UE 414 only receives a reference to service access information, then in step 906, UE 414 obtains service access information from 5GMS AF 410, as described in step 6 of Section 5.1 of 3GPP TS 26.501.

[0117] Then, in step 908, the media streaming procedure is performed at the reference point as specified in step 8 of section 5.1 (for downlink media streaming) and step 8 of section 6.1 (for uplink media streaming) of 3GPP TS 26.501.

[0118] In step 910, the media session processor selects an applicable policy template. Given a set of applicable policy templates (the... ApplicationSessionContext Information and current application flow ApplicationSessionContext Information matching (i.e., matching S-NSSAI and DNN information) is performed, repeating steps 5-8 until 5GMS AF 410 accepts the instantiation of a policy template for the application stream, or until all applicable policy templates have been exhausted. Details of the dynamic policy procedure at reference point M5 are specified in step 7 of Section 5.1 (for downlink media stream transmission) and step 7 of Section 6.1 (for uplink media stream transmission) of 3GPP TS 26.501.

[0119] In step 912, the media session processor transmits data as described in Section 11.5 of 3GPP TS 26.501. policyTemplateId and M5QoS Specification The request is made to 5GMS AF 410 to apply the network QoS described in the policy template to the application flow in the current network slice 402.

[0120] When 5GMS AF 410 determines that the network QoS described by the requested policy template can be applied to the current network slice 402, in step 914, 5GMS AF 410 instantiates and applies the requested dynamic policy and returns a success response to the media session processor.

[0121] When 5GMS AF 410 determines that the network QoS described by the requested policy template cannot be satisfied in the current network slice 402, in step 916, 5GMS AF 410 rejects the instantiation of the requested dynamic policy and returns a rejection response to the media session processor. When the media session processor receives this response, it repeats steps 5-8 using the next adapted policy template.

[0122] In step 918, media streaming at reference point M4 (as specified in step 8 of Section 5.1 (for downlink media streaming) and Section 6.1 (for uplink media streaming) of 3GPP TS 26.501) continues in the current network slice 402, and performance degradation may occur if all applicable policy templates are exhausted and unsuccessful.

[0123] although Figure 9 An example of method 900 for dynamic policy invocation is shown, but it is possible to modify it further. Figure 9 Make various changes. For example, although it is shown as a series of steps, Figure 9 The steps in the process can overlap, occur in parallel, or occur any number of times.

[0124] Figure 10An exemplary method 1000 is shown to illustrate the impact of this disclosure on dynamic policy flows when ASP 412 is unaware of network slice replacement. For ease of explanation, Figure 10 Method 1000 is described as using Figure 4A to Figure 5 , Figures 7 to 10 as well as Figures 14 to 20 The method is implemented using UE 414, AF 410, and ASP 412. However, method 1000 can be used with any other suitable system and any other suitable electronic device.

[0125] like Figure 10 As shown, in step 1002, the primary network slice 402 is provided in the 5G system, and the S-NSSAI of the primary network slice 402 is known to the 5GMS ASP 412 prior to 5GMS service provision. In step 1004, the 5GMS ASP 412 performs service provision at the 5GMS AF 410 as described in Section 7 of TS26.512.

[0126] In step 1006, 5GMS ASP 412 provides service notification information to the 5GMS-aware application in UE 414. The service notification information includes complete service access information (i.e., media session processing details at reference point M5d and media stream transport access details at M4d) or a reference to service access information. When the 5GMS client only receives a reference to the service access information, it obtains the service access information from 5GMS AF 410 in step 1008.

[0127] In step 1010, the network (AMF 1020 in this example call flow, but possibly also PCF 404, NSSF 406, or OAM 408) performs the network slice replacement procedure as described in Section 5.15.19 of TS 23.501. PCF 404 updates the UE Routing Policy (URSP) rules with alternative S-NSSAI information. Section 6.6.2.2 of TS 23.503 describes the procedure for providing URSP rules to UE 414 by PCF 404. Section 6.6.2.3 of TS 23.503 and Section 4.2.2 of this document describe the procedure for associating applications with PDU sessions based on URSP for UE 414. This step may include creating a new PDU session or modifying an existing PDU session as specified in section 4.2.2 of this document, so that the media session processor and the media stream processor can access the 5GMS AF 410 and 5GMS AS instances via reference points M5 and M4, respectively.

[0128] In step 1012, the media session processor invokes the dynamic policy instantiation process on 5GMS AF410 for the application flow in the PDU session of the alternative S-NSSAI. However, because 5GMS ASP 412 has not configured an applicable policy template for the alternative S-NSSAI, the media session processor may not have a suitable policy template to request activation.

[0129] although Figure 10 This illustrates an example of method 1000 that describes the impact on the dynamic policy process when ASP 412 is unaware of network slice replacement, but it is possible to... Figure 10 Make various changes. For example, although it is shown as a series of steps, Figure 10 The steps in the process can overlap, occur in parallel, or occur any number of times.

[0130] Figure 11 An exemplary system 1100 is shown in accordance with this disclosure for a UE to notify an AF 410 about a network slice replacement. Figure 11 The embodiment of system 1100 shown is for illustrative purposes only. Figure 11 The scope of this disclosure is not limited to any particular implementation of an electronic device.

[0131] like Figure 11 As shown, during the UE registration response, or before the network slice replacement procedure using the UE configuration update procedure according to TS 23501 section 5.15.19, the alternative S-NSSAI is notified to UE 414. When UE 414 learns of the network's intention to perform network slice replacement, the UE MSH (Media Session Handler as defined in TS 26501) can notify the 5GMS AF 410 of the network's intention to perform network slice replacement, and may also include the alternative S-NSSAI information. As follows... Figure 6 As shown, such a notification can be sent to 5GMS AF 410 using the M5 interaction described in TS 26512.

[0132] When 5GMS AF 410 receives a notification from UE 414 regarding network slice replacement, 5GMS AF 410 becomes aware of the network slice replacement and is able to provide appropriate services to UE 414 in the new network slice 402. In the notification to 5GMS AF 410, the UE MSH may include the following information from Table 5 as part of the network slice replacement information to be sent to 5GMS AF 410.

[0133] [Table 5]

[0134] although Figure 11 An exemplary system 1100 is shown for a UE to notify the AF 410 about network slice replacement, but it is possible to... Figure 11 Various modifications can be made. For example, the number and location of the various components of system 1100 can be varied as needed or desired. Furthermore, system 1100 can be used in any other suitable multimedia process, and is not limited to the specific process described above.

[0135] Figure 12 An exemplary system 1200 is shown in accordance with this disclosure for a UE to notify an AF 410 about a network slice replacement. Figure 12 The embodiment of system 1200 shown is for illustrative purposes only. Figure 12 The scope of this disclosure is not limited to any particular implementation of an electronic device.

[0136] When one or more UEs 414 receiving services within the primary network slice 402 receive a notification from the network that the primary network slice 402 is being replaced by a backup network slice 402 (backup S-NSSAI), each UE 414 may send a network slice replacement notification as described above to the 5GMS AF 410.

[0137] like Figure 12 As shown, all UEs 414 that have received notification from the network that the primary network slice 402 has been replaced by the alternative network slice 402 (or S-NSSAI) send a notification about the network slice replacement to AF 410. Such a notification from each UE 414 contains the network slice replacement information described in Table 5, which is relevant to that UE 414.

[0138] When AF 410 receives a notification with network slice replacement information from one or more UEs 414, AF 410 may perform the following actions. For example, when a sufficient number of UEs 414 send network slice replacement information with "parameters to avoid slice replacement" indicating a reduction in their service / slice quality requirements, AF 410 checks to see if the primary network slice 402 can continue to provide service to all UEs 414 with reduced requirements. If AF 410 infers that service can continue in the primary network slice 402, AF 410 performs the following sub-actions: AF 410 notifies the network QoS entities (PCF 404, AMF 1020, NSSF406) of the updated QoS requirements for the primary network slice 402. Using this new information, the network entities can cancel the planned network slice replacement and continue service in the primary network slice 402. The network entities send a configuration update message to UEs 414 to revoke the possibility of network slice replacement.

[0139] Another action that AF 410 can perform includes, based on the "parameters for avoiding slice replacement" information from the network slice replacement information of all UEs 414, AF 410 can infer that even if UE 414 reduces its demand, the primary network slice 402 may not be able to accommodate all UEs 414. In this case, network slice replacement can be performed according to the intent of the network entity.

[0140] Another action that AF 410 can perform includes establishing a simple broadcast / multicast session to send messages to all subscribed UEs 414 or to a group of UEs 414 based on a user list received from ASP 412 (information element "List of UEs for Slice Replacement" in Table 6) when a minority of UEs 414 send notifications containing network slice replacement information to AF 410. In this broadcast / multicast message, AF 410 can notify the group of UEs 414 that the current primary network slice 402 is about to be replaced. When the UEs 414 in this broadcast / multicast group receive a message from AF 410 regarding the impending network slice replacement, each UE 414 can respond to AF 410 with the network slice replacement information described in Table 5 above. Based on the network slice replacement information from UE 414 in the broadcast / multicast group, and the information from UE 414 that initially provided the network slice replacement information to AF 410, AF 410 can infer whether the update requirement from UE 414 can avoid network slice replacement (as previously described).

[0141] Additional actions that AF 410 can perform include: if ASP 412 has not configured a "user list for slice replacement" at 5GMS AF 410, then 5GMS AF 410 can randomly select a group of UEs 414 to send a broadcast / multicast message. When these selected UEs 414 receive the message, they send network slice replacement information as previously described in this disclosure.

[0142] Another action that AF 410 can perform includes checking whether a network slice replacement notification from one or more UEs 414 includes a “temporary reduction time” timing information when the notification includes this value. This value is higher than the expected network slice replacement period (e.g., based on network analysis information or information from other 5G network entities). The network slice replacement period is the time during which an alternative S-NSSAI is used before resuming operation of the primary S-NSSAI (e.g., the time required to clear congestion before resuming operation of the primary network slice 402). If the timing information “temporary reduction time” from the UE is higher than the network slice replacement period, this means that UE 414 can reduce its demand for a longer period than the time required to resume operation of the primary network slice 402. In this case, the primary network slice 402 is likely to resume operation and provide service to UE 414 according to the originally requested quality requirements. In this case, AF 410 can disregard the reduced demand from UE 414 in its operations to avoid network slice replacement as described above, because the impact of network slice replacement on UE 414 is minimal. Alternatively, if the "temporary reduction time" is shorter than the expected network slice replacement period, it means that UE 414 needs to revert to the original service requirements before the main network slice 402 returns to operation.

[0143] Another action that AF 410 can perform includes: 5GMS AF 410 can assign a "lower" score to UE 414 with a higher "temporary reduction time" than to UE 414 with a lower "temporary reduction time" to infer the cumulative score for whether to request a halt to the network slice replacement process. This means that UE 414, which cannot provide AF 410 with a higher waiting time to request cancellation of the network slice replacement task from the 5G network entity, is given higher weight.

[0144] although Figure 12 An exemplary system 1200 is shown for a UE to notify the AF 410 about network slice replacement, but it is possible to... Figure 12 Various modifications can be made. For example, the number and location of the various components of system 1200 can be varied as needed or desired. Furthermore, system 1200 can be used in any other suitable multimedia process, and is not limited to the specific process described above.

[0145] Figure 13 An exemplary system 1300 is shown, according to the present disclosure, for unloading multicast sessions of some users during network slice replacement. Figure 13 The embodiment of system 1300 shown is for illustrative purposes only. Figure 13 The scope of this disclosure is not limited to any particular implementation of an electronic device.

[0146] like Figure 13As shown, a network entity may decide to replace the network slice 402 carrying multicast traffic with an alternative network slice 402. Since the alternative network slice 402 cannot guarantee similar performance to the original network slice 402, it may be useful to establish mechanisms to provide enhancements to meet the needs of multicast users. Specifically, the alternative network slice 402 may perform well in the case of a reduced multicast / broadcast user group.

[0147] To help alternative network slice 402 perform as required by the service level agreement, the number of multicast users can be reduced during the network slice replacement process, making the limited capacity of alternative network slice 402 sufficient for multicast sessions. Users removed from multicast sessions can be served using unicast sessions. To facilitate this reduction in multicast user groups, AF 410 can prepare the following information.

[0148] AF 410 can prepare an offload-multicast-user-list. This offload-multicast-user-list includes a list of users that can be removed from the multicast group during the network slice replacement process so that the alternative network slice 402 is sufficient to continue the multicast session.

[0149] AF 410 can also prepare percentage-of-users-for-multicast-offloading information. Based on available network analysis and network slicing analysis information, AF 410 can determine the percentage of users whose membership in the multicast group will be removed during the network slice replacement process. AF 410 selects users whose membership will be removed based on criteria such as the form factor of the user equipment and end-user capabilities, as well as subscriptions. The form factor of the user equipment and end-user capabilities may include, for example, user equipment with specific types of limitations or constraints that may be considered for removal (e.g., devices with limited resolution). Subscriptions may include users with a minimum subscription level that can be selected for removal.

[0150] like Figure 13As shown, the offloading of certain multicast user sessions to unicast can occur as described in the following steps. In step 1302, the network entity, as described in TS 23501, decides to replace the primary network slice 402 with an alternative network slice 402. In step 1304, the network entity notifies the UE 414 of the network slice replacement. In step 1306, the UE 414 (or the MSH within the UE 414 described in TS 26501 and TS 26512) notifies the AF 410 of the network slice replacement performed by the network entity. In step 1308, the AF 410, as described in this disclosure, prepares to offload certain user sessions from multicast to unicast so that the alternative network slice 402 is suitable for continuing multicast for other users.

[0151] ASP 412 can provide service configuration information to 5GMS AF 410 to help manage network slice replacement notifications from user equipment 414. Examples of information elements can be found in Table 6.

[0152] [Table 6]

[0153] although Figure 13 An exemplary system 1300 is shown for offloading multicast sessions of certain users during network slice replacement, but it is possible to... Figure 13 Various modifications can be made. For example, the number and location of the various components of system 1300 can be varied as needed or desired. Furthermore, system 1300 can be used in any other suitable multimedia process, and is not limited to the specific process described above.

[0154] Figure 14 An exemplary system 1400 is shown, according to this disclosure, for proactively notifying AF 410 about network slice replacement. Figure 14 The embodiment of system 1400 shown is for illustrative purposes only. Figure 14 The scope of this disclosure is not limited to any particular implementation of an electronic device.

[0155] like Figure 14As shown, even without explicit notification from network entities such as AMF 1020, PCF 404, NSSF 406, OEM 408, etc., UE 414 periodically sends this notification to 5GMS AF 410. To support this intermittent notification mechanism, ASP 412 can configure the periodic time interval for network slice replacement information notifications from UE 414 to AF 410 during the service configuration phase. The M1 service provisioning API described in TS 26501 and TS 26512 can be used for service configuration at 5GMS AF 410. When AF 410 receives this information as part of the M1 provisioning API, it uses the M5 service access information API specified in TS 26501 and TS 26512 to make this periodic time interval available within the MSH of UE 414. When UE 414 receives this information, it sends a notification to 5GMS AF 410 regarding the replacement of a network slice using the network slice replacement information described above in this disclosure. Such notifications are sent periodically to AF 410, with "periodic time intervals" as the time unit.

[0156] However, to distinguish that the notification is not the result of a notification about network slice replacement from a 5G entity, UE 414 can include the information element "intermittent-notification" and set the value of this element to "true". When AF 410 receives a notification with this information element, it infers that the notification is not due to an impending network slice replacement event, but rather a periodic notification about network slice replacement from UE 414.

[0157] After receiving notifications from some UEs 414, AF 410 can perform broadcast / multicast notifications to check whether some of these UEs can reduce their requirements, thereby potentially avoiding any network slice replacement tasks in the network.

[0158] although Figure 14 An exemplary system 1400 is shown for proactively notifying the AF 410 about network slice replacement, but it is possible to... Figure 14 Various modifications can be made. For example, the number and location of the various components of system 1400 can be varied as needed or desired. Furthermore, system 1400 can be used in any other suitable multimedia process, and is not limited to the specific process described above.

[0159] Figures 15A and 15B illustrate an exemplary method 1500 for configuring a policy template for alternative S-NSSAI in the event of network slice replacement, according to the present disclosure. For ease of explanation, the method 1500 of Figures 15A and 15B is described as using Figures 4A to 15B. Figure 5 , Figures 7 to 10as well as Figures 14 to 20 The method is implemented using UE 414, AF 410, and ASP 412. However, method 1500 can be used with any other suitable system and any other suitable electronic device.

[0160] This candidate solution investigates the impact of network slice replacement on 5GMS procedures (as described in the description of this critical issue and as specified in Section 5.15.19 of TS 23.501). Specifically, prior to the invocation of the network slice replacement procedure, the impact of network slice replacement was examined against the dynamic policy invocation procedure specified in Section 4.7.3 of TS26.512, assuming that the policy template applicable to alternative network slice 402 is provided in 5GMS AF 410.

[0161] The assumptions include: The DN remains unchanged due to the network slice replacement process; that is, both primary network slice 402 and alternative network slice 402 can access the same DN. Another assumption is that the 5GMS AF 410 instance, accessed by the media session processor via primary network slice 402, can also be accessed at reference point M5 via alternative network slice 402. The IP address of the 5GMS AF 410 instance remains unchanged. Another assumption is that the 5GMS AS instance, accessed by the media stream processor via primary network slice 402, can also be accessed at reference point M4 via alternative network slice 402. The IP address of the 5GMS AS instance remains unchanged.

[0162] Figure 15A illustrates the impact on the M5 dynamic policy process when the network replaces the primary S-NSSAI with an alternative S-NSSAI according to the decision specified in Section 5.15.19 of TS 23.501, and the 5GMS ASP 412 is aware of the network slice replacement. This applies to situations where the OAM configures the alternative S-NSSAI information and the 5GMS ASP 412 is aware of the alternative S-NSSAI (e.g., via OAM transmission).

[0163] In step 1502, prior to the provision of 5GMS services, a primary network slice 402 and an alternative network slice 402 are provided in the 5G system, and the S-NSSAI for both is known to the 5GMS ASP 412.

[0164] In step 1504, 5GMS ASP 412 performs service provisioning at reference point M1 in accordance with Section 7 of TS 26.512, together with 5GMSAF 410. The provisioning information from 5GMS ASP 412 includes a policy template that references both the primary S-NSSAI and the alternative S-NSSAI to support the network slice replacement procedure. The DNNs used for both network slices 402 are identical. The provisioning procedure in this step corresponds to either an initial service provisioning request for M1 or an update of existing service provisioning resources. Whether to provide a matching policy template on both the primary and alternative S-NSSAIs is determined by 5GMS ASP 412.

[0165] If 5GMS AF 410 is in a trusted DN, then in step 1506, it uses the method defined in section 5.2.5.3 of TS 23.502. Npcf_ The service interacts directly with PCF 404 to create an appropriate application session context within PCF 404 using alternative S-NSSAI information. ApplicationSessionContext The data model is specified in Section 5.6.2.2 of TS 29.514.

[0166] If the 5GMS AF 410 is in an external DN, then in step 1508, it can use the method defined in section 5.2.6.9 of TS 23.502. Nnef_AFsession The service is used to configure alternative S-NSSAI information. NEF can be invoked on behalf of 5GMS AF 410. Npcf_PolicyAuthorization The service is used to create an appropriate session context in PCF 404 using the provided alternative S-NSSAI information. ApplicationSessionContext The data model is specified in Section 5.6.2.2 of TS 29.514.

[0167] As shown in Figure 15B, in step 1510, 5GMS ASP 412 announces 5GMS services to the 5GMS-aware application running in UE 414. The service announcement includes all service access information (i.e., details of media session processing at reference point M5d and media streaming access at M4d) or a reference to the complete service access information.

[0168] If the 5GMS client only received a reference to service access information in the previous step, in step 1512, it obtains service access information from 5GMS AF 410 via reference point M5.

[0169] In step 1514, the network (PCF 404 in this example call flow, but may also be AMF 1020, NSSF 406, or OEM 408) initiates a network slice replacement procedure as described in Section 5.15.19 of TS 23.501. PCF 404 updates the URSP rules with alternative S-NSSAI information. Section 6.6.6.2.2 of TS 23.503 describes the procedure for providing URSP rules to UE 414 by PCF 404. Section 6.6.2.3 of TS 23.503 and Section 4.2.2 of this document describe the UE procedure for associating applications with PDU sessions based on URSP. This step may involve creating a new PDU session or modifying an existing PDU session as specified in Section 4.2.2 of TR 26.941, enabling the media session processor and media stream processor to access the 5GMS AF 410 and 5GMS AS instances via reference points M5 and M4, respectively. After step 1514, for any subsequent 5G media streaming API request on the M5 reference point that requires 5GMS AF 410 to interact with PCF404 and / or NEF to be used with the PDU session in the alternative S-NSSAI, the appropriate application session context for any application-related processing can be obtained at PCF 404.

[0170] In step 1516, the media session processor, in accordance with Section 11.5 of TS 26.512, invokes a valid S-NSSAI with the appropriate alternative. policyTemplateId The M5 Dynamic Policy API. In step 1518, 5GMS AF 410 interacts with PCF 404 to request the necessary actions to apply the requested dynamic policy. In step 1518, 5GMS AF 410 responds to the 5GMS client that the requested dynamic policy has been successfully applied.

[0171] Although Figures 15A and 15B illustrate an example of a method 1500 for configuring a policy template for the alternative S-NSSAI in the event of network slice replacement, various changes can be made to Figures 15A and 15B. For example, although shown as a series of steps, the individual steps in Figures 15A and 15B can overlap, occur in parallel, or occur any number of times.

[0172] Figures 16A and 16B illustrate an exemplary method 1600 for configuring a policy template referencing alternative S-NSSAI after network slice replacement, according to the present disclosure. For ease of explanation, the method 1600 of Figures 16A and 16B is described as using Figures 4A to 16B. Figure 5 , Figures 7 to 10 as well as Figures 14 to 20The method is implemented using UE 414, AF 410, and ASP 412. However, method 1600 can be used with any other suitable system and any other suitable electronic device.

[0173] This candidate solution investigates the impact of network slice replacement on 5GMS procedures (as described in the description of this critical issue and as specified in Section 5.15.19 of TS 23.501). Specifically, after the network slice replacement procedure is invoked, the impact of network slice replacement is examined against the dynamic policy invocation procedure specified in Section 4.7.3 of TS 26.512, provided that the policy template applicable to alternative network slice 402 is provided in 5GMS AF 410.

[0174] The assumptions include: the DN does not change due to the network slice replacement process; that is, both the primary network slice 402 and the alternative network slice 402 can access the same DN. This corresponds to the example data network in Figure 4.2.1-1 of TR 26.941. This is mapped to both network slice instance X and network slice instance Y. Another assumption includes that the 5GMS AF 410 instance, accessed by the media session processor via the primary network slice 402, can also be accessed at reference point M5 via the alternative network slice 402. The IP address of the 5GMS AF 410 instance remains unchanged. Another assumption includes that the 5GMS AS instance, accessed by the media stream processor via the primary network slice 402, can also be accessed at reference point M4 via the alternative network slice 402. The IP address of the 5GMS AS instance remains unchanged.

[0175] Figures 16A and 16B illustrate the impact on the M5 dynamic policy process when the network replaces the primary network slice 402 with the alternative network slice 402 according to the decision specified in Section 5.15.19 of TS 23.501, and the 5GMS ASP 412 is informed of the network slice replacement after this event.

[0176] As shown in Figure 16A, in step 1602, prior to 5GMS service provision, a primary network slice 402 is provided in the 5G system, and the S-NSSAI for the primary network slice 402 is known to 5GMS ASP 412. In step 1604, 5GMS ASP 412 performs service provisioning at reference point M1 with 5GMS AF 410 as specified in Section 7 of TS 26.512.

[0177] In step 1606, 5GMS ASP 412 announces 5GMS services to the 5GMS-aware applications running in UE 414. The service announcement includes full service access information (i.e., details of media session processing at reference point M5d and media streaming access at M4d) or a reference to the full service access information.

[0178] If the 5GMS client only received a reference to service access information in the previous step, in step 1608, it obtains the service access information from 5GMS AF 410 via reference point M5. In step 1610, the network (PCF 404 in this example call flow, but possibly by AMF 1020, NSSF 406, or OEM 408) performs the network slice replacement procedure as described in Section 5.15.19 of TS 23.501. PCF 404 updates the URSP rules with alternative S-NSSAI information. Section 6.6.6.2.2 of TS 23.503 describes the procedure for providing URSP rules to UE 414 by PCF 404. Section 6.6.2.3 of TS 23.503 and Section 4.2.2 of TR 26.941 describe the UE procedure for associating applications with PDU sessions based on URSP. This step may involve creating a new PDU session or modifying an existing PDU session as specified in Section 4.2.2 of TR 26.941, so that the media session processor and the media stream processor can access the 5GMS AF 410 and 5GMSAS instances via reference points M5 and M4, respectively.

[0179] In step 1612, PCF 404 notifies 5GMS AF 410 of the network slice replacement, including alternative S-NSSAI information. In step 1614, 5GMS AF 410 notifies 5GMS ASP 412 of the network slice replacement, including alternative S-NSSAI information. In step 1616, 5GMS ASP 412 updates the service provisioning information at 5GMS AF 410 using a policy template referencing the alternative S-NSSAI, as described in Section 7 of TS 26.512.

[0180] If 5GMS AF 410 is in a trusted DN, then in step 1608, it uses the method defined in section 5.2.5.3 of TS 23.502. Npcf_Policy The service interacts directly with PCF 404 to create an appropriate application session context within PCF 404 using alternative S-NSSAI information. ApplicationSessionContext The data model is specified in Section 5.6.2.2 of TS 29.514.

[0181] Alternatively, if the 5GMS AF 410 is in an external DN, then in step 1620, it can use the method defined in section 5.2.6.9 of TS 23.502. Nnef_AFsession The service is used to configure alternative S-NSSAI information. NEF can be invoked on behalf of 5GMS AF410. Npcf_PolicyAuthorization The service is used to create an appropriate session context in PCF 404 using the provided alternative S-NSSAI information. ApplicationSessionContext The data model is specified in Section 5.6.2.2 of TS 29.514.

[0182] In step 1622, 5GMS ASP 412 re-advertises 5GMS services to the 5GMS-aware application in UE 414. If the 5GMS client only received a reference to service access information in the previous step, in step 1624, it re-acquires the service access information from 5GMS AF 410 via reference point M5. In step 1626, the media session processor, in accordance with Section 11.5 of TS26.512, invokes a valid [function name] with the applicable alternative S-NSSAI. policyTemplateId The M5 Dynamic Policy API. In step 1628, as described in Section 5.7.1 of TS 26.501, the 5GMS AF 410 interacts with the PCF404 to request the necessary actions to apply the requested dynamic policy. In step 1630, the 5GMS AF 410 successfully responds to the 5GMS client that the requested dynamic policy request has been received.

[0183] Although Figures 16A and 16B illustrate an exemplary method 1600 for configuring a policy template referencing alternative S-NSSAI after network slice replacement, various changes can be made to Figures 16A and 16B. For example, although shown as a series of steps, the individual steps in Figures 16A and 16B can overlap, occur in parallel, or occur any number of times.

[0184] Figure 17 An exemplary system 1700 is shown, according to the present disclosure, for facilitating session termination for some users to avoid network slice replacement. Figure 17 The embodiment of system 1700 shown is for illustrative purposes only. Figure 17 The scope of this disclosure is not limited to any particular implementation of an electronic device.

[0185] like Figure 17 As shown, ASP 412 may not want the primary network slice 402 to be replaced by a different alternative network slice 402. Therefore, ASP 412 may prefer to terminate some user sessions to avoid the network slice replacement process.

[0186] To facilitate such service-oriented user management, ASP 412 can configure UE-terminate list and percentage-of-users-to-be-terminated information at 5GMS AF 410 (e.g., via the API provided by the M1 service as specified in TS 26501 and TS 26512).

[0187] The UE termination list may include a list of users whose sessions can be terminated to avoid network slice replacement (i.e., to avoid replacing primary network slice 402 with alternative network slice 402). When AF 410 receives this information from ASP 412, it continues to wait for network slice replacement notification from UE 414. When one or more UEs 414 send notifications to AF 410 about network slice replacement they have learned of from network entities, AF 410 may attempt to terminate the sessions of users in the list and then request 5G network entities (e.g., PCF 404, AMF 1020, SMF) to reassess the necessity of network slice replacement. Once the sessions of users in the list are terminated, the network may find that the network slice replacement process is no longer needed. To help bring these users back to service, ASP 412 may also configure a "wait period" after which UE 414 can retry joining the service. This information can be transmitted to UE 414 via the M8 interface or M5 service access information API specified in TS 26501 or TS 26512 during the initial session setup phase or subsequently during the middle of the session.

[0188] The percentage of users to be terminated information can include the percentage of users whose sessions are to be terminated, rather than a list of users. When AF 410 receives this information from ASP 412, it can select the list of users whose sessions are to be terminated using either a random method or a priority-based processing method. Once the user list is ready, the sessions are terminated.

[0189] although Figure 17 An exemplary system 1700 is shown for facilitating session termination for some users to avoid network slice replacement, but it is possible to modify the service configuration. Figure 17 Various modifications can be made. For example, the number and location of the various components of system 1700 can be varied as needed or desired. Furthermore, system 1700 can be used in any other suitable multimedia process, and is not limited to the specific process described above.

[0190] Figure 18 An exemplary system 1800 according to this disclosure is shown for avoiding network slice replacement by reducing available adapters. Figure 18 The embodiment of system 1800 shown is for illustrative purposes only. Figure 18 The scope of this disclosure is not limited to any particular implementation of an electronic device.

[0191] like Figure 18 As shown, ASP 412 can optionally reduce the number of adaptations used for media services during network slice replacement. For example, for a simple streaming service, if the media service is currently distributing content at multiple bitrates (e.g., HD, 2K, 4K, 8K, etc.), ASP 412 can instruct AF 410 to temporarily suspend one or more content bitrates during the network slice replacement process, allowing users accessing content at other bitrates to have access to their requested content within the same network slice 402. This restriction on certain adaptations can be performed by AF 410 if the new alternative network slice 402 replacing the primary network slice 402 cannot provide performance guarantees similar to those of the primary network slice 402.

[0192] Because some adaptations are temporarily suspended, UEs 414 accessing these adaptations can stop receiving their desired adaptations. As a result of this temporary suspension, some UEs 414 can use adaptive bitrate techniques to switch to adaptations that continue to be transmitted (i.e., are available). However, some devices choose not to switch to available adaptations for various reasons (unsupported shape factors—e.g., low-resolution devices refusing to upgrade to 4K streaming; insufficient codec support, etc.). For these reasons, user traffic transmitted through the main network slice 402 decreases, and as a result, network entities may deem the network slice 402 replacement process unnecessary due to reduced demand.

[0193] In step 1802, ASP 412 configures a list of all possible adapter sets for the media service. ASP 412 also configures a list of adapters to be discarded during the network slice replacement process. ASP 412 can use the M1-provided API described in TS 26501 and TS 26512 to configure this information at AF 410.

[0194] In step 1804, the network entity, as described in TS 23501, decides to replace the primary network slice 402 with the alternative network slice 402. In step 1806, the network entity notifies the UE 414 of the network slice replacement as described above in this disclosure. In step 1808, the UE 414 (or the MSH within the UE 414 as described in TS 26501 and TS 26512) notifies the AF 410 of the possible network slice replacement by the network entity.

[0195] In step 1810, AF 410 notifies AS (Application Server) to temporarily suspend the adaptations available in network slice 402. AF 410 provides a list of adaptations to be discarded. When AS receives the list of adaptations to be discarded, it stops generating the indicated adaptations. In step 1812, UE 414 may request one or more adaptations. In step 1814, for some adaptations, AS responds with an unavailable adaptation. Some UEs 414 may stop accessing the service. Other UEs 414 may use ABR technology to switch to an available adaptation.

[0196] although Figure 18 An exemplary system 1800 is shown for avoiding network slice replacement by reducing the number of available adapters, but alternatives can be made. Figure 18 Various modifications can be made. For example, the number and location of the various components of system 1800 can be varied as needed or desired. Furthermore, system 1800 can be used in any other suitable multimedia process, and is not limited to the specific process described above.

[0197] Figure 19 An exemplary system 1900 is shown, according to this disclosure, for unloading multicast sessions of some users during network slice replacement. Figure 19 The embodiment of system 1900 shown is for illustrative purposes only. Figure 19 The scope of this disclosure is not limited to any particular implementation of an electronic device.

[0198] The entire contents of Provisional Application No. 63,543,997 (Examination ID: WD-202310-028-1-US0, Title: Managing Network Slice Replacement Using Application Layer Information), filed October 13, 2023, are incorporated herein by reference, which describes a method for offloading certain user sessions from multicast, so that an alternative network slice 402 with limited capabilities can be sufficient to provide multicast for the remaining users. In this disclosure, the above method can be enhanced using service configuration information from ASP 412.

[0199] To facilitate multicast user group reduction, ASP 412 can configure at AF 410 an offload-multicast user list, a cell ID list, a geographic region, a percentage of users used for multicast offloading, and a service delivery to offloaded users using unicast (e.g., using the M1 API as specified in TS 26501 and TS 26512). The offload-multicast user list may include a list of users that can be removed from the multicast group during the network slice replacement process, so that alternative network slice 402 is sufficient to continue the multicast session. The cell ID list may include a list of cell identifiers. All users in the cell identifier list can have their multicast membership removed. The geographic region may include all users in that region whose multicast membership can be removed. The percentage of users used for multicast offloading may include the percentage of users whose membership in their multicast group was removed during the network slice replacement process. ASP 412 can provide further information to identify users to be considered to see if they can be included in a given percentage of users. User equipment shape factors and end-user capabilities: For example, user equipment with specific types of limitations or constraints may be considered for removal—such as devices with limited resolution. Subscriptions may include users with a minimum subscription level who can be selectively removed. Using unicast to deliver services to offloaded users can indicate whether a user removed from a multicast group is delivered services via a unicast session.

[0200] like Figure 19 As shown, it is possible that ASP 412 will be used to configure certain multicast user sessions to be offloaded to unicast. In step 1902, ASP 412 is configured with information for offloading certain multicast user sessions to unicast. In step 1904, the network entity, as described in TS 23501, decides to replace the primary network slice 402 with an alternative network slice 402. In step 1906, the network entity, as described above in this disclosure, notifies the UE 414 about the network slice replacement. In step 1908, the UE 414 (or the MSH within the UE 414 described in TS 26501 and TS 26512) notifies the AF 410 about the network slice replacement performed by the network entity. In step 1910, based on the information from ASP 412, the AF 410, as described in this disclosure, offloads certain user sessions from multicast to unicast so that the alternative network slice 402 is suitable for continuing multicast for other users.

[0201] ASP 412 can provide service configuration information to 5GMS AF 410 to help manage network slice replacement, as shown in Table 7 below.

[0202] [Table 7]

[0203] although Figure 19 An exemplary system 1900 is shown for offloading multicast sessions of some users during network slice replacement, but it is possible to modify... Figure 19 Various modifications can be made. For example, the number and location of the various components of System 1900 can be varied as needed or desired. Furthermore, System 1900 can be used in any other suitable multimedia process, and is not limited to the specific process described above.

[0204] Figure 20 An exemplary system 2000 for network slice replacement using multiple network slices 402 is shown according to the present disclosure. Figure 20 The embodiments of system 2000 shown are for illustrative purposes only. Figure 20 The scope of this disclosure is not limited to any particular implementation of an electronic device.

[0205] like Figure 20 As shown, when media services are delivered to end users using two or more network slices 402, and a network entity decides to replace one of these network slices 402, necessary mechanisms must be set up to manage application flows in the two network slices 402. For this purpose, ASP 412 can configure several service configuration options for use during the network slice replacement process, for example, using the M1 API described in TS 26501 and TS 26512. The options configured by ASP 412 can be any of the following: replace-all-slices option, migrate-flows-to-slices-within-the-service option, provision-new-slice option, etc.

[0206] Replace All Slices Option: If one of the network slices 402 in the media service is being replaced by a network entity, the AF 410 is instructed to replace all network slices 402 with alternative network slices 402, rather than replacing only one network slice 402. When the AF 410 receives this information, it configures this information in the PCF 404. When the network entity decides to replace one network slice 402 with another network slice 402, the network entity replaces all network slices 402 in the media service with the assistance of the PCF 404.

[0207] Migrating Streams to Slices within the Service: If one or more of the network slices 402 of the media service are being replaced by a network entity, and the alternative network slice 402 cannot provide similar performance guarantees as the original primary network slice 402, then the AF 410 is instructed to migrate the application streams in the network slice 402 being replaced to another network slice 402 that is still part of the media service. For each network slice 402, the ASP 412 can configure a mapping that shows which network slice 402 each application stream should migrate to if the network entity decides to replace that network slice 402. The network slices 402 to which the application streams are migrated are in the set of network slices 402 provided for use by the media service. When the original network slice 402 that was replaced resumes operation, the above mapping helps to migrate the application streams back to the original network slice 402. Therefore, before any network slice replacement process, the application streams are sent in the network slice 402 that originally carried them.

[0208] Provide a new slice option: If network slice 402 for media services is being replaced by a network entity, instruct AF 410 that the network must provide a new network slice 402 if the alternative network slice 402 cannot provide similar performance guarantees. When this option is configured and the network entity decides to replace network slice 402, the network continuously checks whether the alternative network slice 402 provides similar performance guarantees. If performance is affected, the network provides a new network slice 402 based on this option configured in ASP 412 until the original primary network slice 402 resumes operation.

[0209] although Figure 20 An exemplary system 2000 is shown for network slice replacement using multiple network slices 402, but it is possible to... Figure 20 Various modifications can be made. For example, the number and location of the various components of System 2000 can be varied as needed or desired. Furthermore, System 2000 can be used in any other suitable multimedia process, and is not limited to the specific process described above.

[0210] Figure 21 An exemplary method 2100 for network slice replacement for multimedia services according to this disclosure is shown. For ease of explanation, Figure 21 Method 2100 is described as using Figure 3 The method is executed by electronic device 300. However, method 2100 can be used with any other suitable system and any other suitable electronic device, including Figure 2 Server 200 and Figure 4A to Figure 5 , Figures 7 to 10 , Figures 14 to 20 ASP 412.

[0211] like Figure 21As shown, in step 2102, the electronic device 300 can use the first configuration to configure the first network slice 402. Examples of attributes for the configuration of the network slice 402 can be found in Table 2 above.

[0212] In step 2104, the electronic device 300 may be configured to perform a first action to avoid network slice replacement. The first action to avoid network slice replacement may be configured based on feedback from the UE 414. This first action to avoid network slice replacement includes at least one of the following: reducing service availability, narrowing the service area, increasing latency tolerance, reducing throughput per network slice 402, reducing support for group communication, reducing service adaptation, and reducing the number of supported UEs 414.

[0213] In step 2106, the electronic device 300 may receive an instruction for network slice replacement. This instruction may be used to perform network slice replacement immediately or to perform network slice replacement at a specified time. In step 2108, the electronic device 300 may perform a first action to avoid network slice replacement.

[0214] In step 2110, the electronic device 300 may receive a second configuration and configure the second network slice 402. The second network slice 402 may be configured based on the second configuration. Alternatively, the second configuration may be received prior to step 2102, and the second network slice 402 may be configured together with the first network slice 402 in step 2102. The second network slice 402 may have a specified minimum network slice configuration descriptor that provides the absolute minimum value for the parameters in the second configuration of the second network slice 402.

[0215] In step 2112, electronic device 300 may perform network slice replacement. Once network slice replacement is performed, electronic device 300 may also perform a second action to ensure service performance on the second network slice 402. The second action includes at least one of the following: checking the minimum service level protocol, determining that drops exceed a threshold, and checking the minimum user count.

[0216] In step 2114, electronic device 300 can monitor services on the second network slice 402. Electronic device 300 can determine whether the service meets the minimum SLA, and if it is determined that the minimum SLA is not met, stop or suspend the service.

[0217] although Figure 21 An exemplary method 2100 for network slice replacement for multimedia services is shown, but it can be applied to... Figure 21 Make various changes. For example, although shown as a series of steps, Figure 21 The various steps in the process can overlap, occur in parallel, or occur any number of times.

[0218] Although this disclosure has been described with reference to exemplary embodiments, various changes and modifications can be made by those skilled in the art. This disclosure is intended to cover such changes and modifications that fall within the scope of the appended claims. Nothing described in this application should be construed as implying that any particular element, step, or function is an essential element that must be included within the scope of the claims. The scope of the patent subject matter is defined by the claims.

[0219] In addition, computer-readable storage media may be provided in the form of non-transitory storage media. "Non-transitory storage media" is a tangible device and simply means that it does not contain signals (e.g., electromagnetic waves). This term does not distinguish between cases where data is stored semi-permanently in a storage medium and cases where data is temporarily stored. For example, a non-transitory recording medium may include a buffer in which data is temporarily stored.

[0220] The specific examples provided to explain embodiments according to this disclosure are merely combinations of each standard, method, detailed method, and operation, and the various embodiments described herein can be performed by a combination of at least two or more of the various techniques described. Furthermore, in this case, the method can be performed according to a method determined by one or more of the above-described techniques. For example, a combination of partial operations of one embodiment and partial operations of another embodiment can be performed.

Claims

1. A method for managing network slice replacement in a communication system, the method comprising: Configure the first network slice using the first configuration; Configure the first action to avoid network slice replacement; Receive an instruction to replace the first network slice with a second network slice; Instruct the execution of the first action to avoid network slice replacement; When the first action to avoid network slice replacement fails, the application flow is migrated from the first network slice to the second network slice with a second configuration, which is different from the second configuration. as well as Monitor services that use the second network slice.

2. The method according to claim 1, wherein, The first action to avoid network slice replacement is configured based on feedback from the user equipment (UE).

3. The method according to claim 1, wherein, The first action for avoiding network slice replacement includes at least one of the following: reducing the availability of the service, narrowing the area of ​​the service, increasing latency tolerance, reducing the throughput of each network slice, reducing support for group communication, reducing service adaptation, or reducing the number of supported UEs.

4. The method according to claim 1, wherein, The monitoring services include: Determine whether the service meets the minimum service level agreement (SLA), and If the minimum SLA is not met, the service is stopped or suspended.

5. The method according to claim 1, further comprising: Before the network slice replacement instruction, the second configuration is received, and the second configuration is used to configure the second network slice.

6. The method according to claim 1, further comprising: Following the instruction to replace the network slice, the second configuration is received, and the second configuration is used to configure the second network slice.

7. The method according to claim 1, further comprising: Specify a minimum network slice configuration descriptor that provides the absolute minimum value of the parameters for the second network slice.

8. The method according to claim 1, further comprising: Configure a second action to ensure the performance of the service after the network slice replacement; as well as The instruction is to perform the second action after the network slice is replaced.

9. The method according to claim 8, wherein, The second action for ensuring the performance of the service includes at least one of the following: checking the minimum service level agreement, determining that the degradation is above a threshold, or checking the minimum number of users.

10. The method according to claim 1, wherein: The indication includes the time for network slice replacement, and Instructing to perform the first action includes instructing at least a portion of the first action to be performed before the time for network slice replacement.

11. An electronic device for managing network slice replacement in a communication system, comprising: Memory, which stores one or more instructions; as well as At least one processor, configured to execute the one or more instructions to: Receive the configuration of the first network slice with the first configuration; Receive configuration for the first action to avoid network slice replacement; Receive an instruction to replace the first network slice with a second network slice; Instruct the execution of the first action to avoid network slice replacement; When the first action to avoid network slice replacement fails, the application flow is migrated from the first network slice to the second network slice with a second configuration, which is different from the second configuration. as well as Monitor services that use the second network slice.

12. The electronic device according to claim 11, wherein, The first action to avoid network slice replacement is configured based on feedback from the user equipment (UE).

13. The electronic device according to claim 11, wherein, The first action for avoiding network slice replacement includes at least one of the following: reducing the availability of the service, narrowing the area of ​​the service, increasing latency tolerance, reducing the throughput of each network slice, reducing support for group communication, reducing service adaptation, or reducing the number of supported UEs.

14. The electronic device according to claim 11, wherein, To monitor the service, the processor is configured to execute one or more instructions to: Determine whether the service meets the minimum service level agreement (SLA), and If the minimum SLA is not met, the service is stopped or suspended.

15. The electronic device according to claim 11, wherein, The processor is also configured to execute the one or more instructions to: Before the network slice replacement instruction, the second configuration is received, and the second configuration is used to configure the second network slice.

Images