Method and system for optimizing slice selection in a network

Abstract

METHOD AND SYSTEM FOR OPTIMIZING SLICE SELECTION IN A NETWORK The present disclosure describes a method (400, 500) for optimizing slice selection in a network (106) A request along with a Single Network Slice Selection 5 Assistance Information (S-NSSAI) from a User Equipment (UE) (302) is received. Further, subscription data associated with the UE (302) is retrieved from a network function. An indicator is extracted from the subscription data associated with the requested (S-NSSAI). Further, a flag associated with the extracted indicator is determined to be enabled. Based on the determination, the S-NSSAI received along 10 with the request is used for slice selection. Ref.

Description

METHOD AND SYSTEM FOR OPTIMIZING SLICE SELECTION IN A NETWORK RESERVATION OF RIGHTS

[0001] A portion of the disclosure of this patent document contains material, which is subject to intellectual property rights such as, but are not limited to, copyright, design, trademark, Integrated Circuit (IC) layout design, and / or trade dress protection, belonging to Jio Platforms Limited (JPL) or its affiliates (hereinafter referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner.TECHNICAL FIELD

[0002] The present disclosure relates to a field of telecommunications network. In particular, the present disclosure relates to a method and a system for optimizing slice selection in a network.DEFINITION

[0003] As used in the present disclosure, the following terms are intended to have the meaning as set forth below, except to the extent that the context in which they are used to indicate otherwise.

[0004] The term ‘Network Slice’ used herein in the specification refers to a virtualized, end-to-end logical network that operates on top of a shared physical Fifth Generation (5G) network infrastructure. The network slice is designed to provide customized network services based on specific user or application requirements. Each network slice is independent and optimized for different use cases, ensuring efficient resource allocation, security, and performance.

[0005] The term ‘Public Land Mobile Network (PLMN)’ used herein in the specification refers to a telecommunications network that is established and operated by a mobile network operator (MNO) to provide wireless communicationservices to subscribers. The PLMN plays a critical role in network slicing by allowing different services such as Internet of Things (loT), enterprise, low-latency applications to operate within isolated logical networks while using the same physical infrastructure.

[0006] The term ‘Access and Mobility management Function (AMF)’ used herein in the specification refers to a control-plane entity within the Fifth Generation (5G) network responsible for handling signalling, mobility management, and session control for the UE. The AMF acts as the central point of interaction between the UE and the 5G Core Network, facilitating Protocol Data Unit (PDU) session establishment and routing configuration.

[0007] The term ‘Unified Data Management (UDM)’ used herein in the specification refers to a key 5G Network function responsible for storing, managing, and distributing subscriber data, authentication credentials, and policy information. The UDM provides Data Network Name (DNN) and Slice Selection Assistance Information (S-NSSAI) to enable proper PDU session establishment.

[0008] The term ‘Network Slice Selection Function (NSSF)’ used herein in the specification refers to a key component of the 5G network that is responsible for selecting appropriate network slices for User Equipment (UE) sessions based on the subscriber’s profile, network policies, and requested services. The NSSF ensures that the UEs are connected to the correct network slice, optimizing network performance and resource utilization.

[0009] The term ‘Network Repository Function (NRF)’ used herein in the specification refers to a key component of the 5G network architecture, responsible for maintaining a repository of available network functions and their capabilities. The NRF enables service discovery, load balancing, and efficient network function communication, ensuring dynamic and scalable network operations.

[0010] The term ‘Single Network Slice Selection Assistance Information (S-NSSAI)’ used herein in the specification refers to a key identifier used in the 5G network to specify and select a network slice for a particular service or user. The S-NS SAI enables efficient resource allocation and service differentiation within the 5G network.

[0011] The term ‘N1 interface’ used herein in the specification refers to techniques used to the Non-Access Stratum (NAS) signalling interface use for communication between the UE and the AMF in a 5G Core network. The N 1 interface operates over the control plane, enabling the exchange of session management, mobility management, authentication, and security-related messages between the UE and the core network.

[0012] The term ‘N8 interface’ used herein in the specification refers to an interface in the 5G Core network that facilitates communication between the AMF and the UDM. The N8 interface is responsible for handling subscriber authentication, mobility management, access control, and policy retrieval to ensure seamless network operation.

[0013] The term ‘N22 interface’ used herein in the specification refers to a servicebased interface in the 5G network architecture that facilitates communication between the NSSF and the AMF. The N22 interface is responsible for policy-based network slice selection and enforcement.

[0014] The term ‘N27 interface’ used herein in the specification refers to a servicebased interface in the 5G network architecture that facilitates communication between the NSSF in the serving PLMN and the NSSF in the home PLMN.

[0015] The term ‘N31 interface’ used herein in the specification refers to the communication interface between the NSSF and the NRF. The N31 interface plays a critical role in network slice selection and discovery of NSSF instances within the 5G Service-Based Architecture (SBA).

[0016] These definitions are in addition to those expressed in the art.BACKGROUND

[0017] The following description of related art is intended to provide background information pertaining to the field of the disclosure. This section may includecertain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.

[0018] With the rapid expansion of Fifth Generation (5G) networks, mobile operators are required to manage a growing number of network slices, roaming scenarios, and inter-operator connectivity efficiently. A Public Land Mobile Network (PLMN) consists of multiple network elements that work together to provide seamless wireless communication services. As 5G network evolve, the ability to select and maintain appropriate network slices for different services, applications, and user groups has become a significant challenge.

[0019] In conventional network slice selection mechanisms, an Access and Mobility Management Function (AMF) is responsible for querying a Network Slice Selection Function (NSSF) to determine an appropriate Single Network Slice Selection Assistance Information (S-NSSAI) for a user's session. However, in multi-PLMN environments, this process often results in excessive signalling overhead, increasing latency and reducing overall network efficiency. Every time a user moves between PLMNs, the AMF must query the NSSF to determine slice availability, even if the slice remains unchanged. The repeated signalling causes unnecessary delays, impacts network performance, and complicates inter-PLMN slice continuity.

[0020] Furthermore, the conventional network slice selection mechanisms do not provide an efficient way to manage global network slices across multiple PLMNs, creating challenges for enterprises and mobile users who require consistent network services across different regions. For example, global enterprises, Internet of Things (loT) deployments, and mission-critical applications are required to repeatedly query the NSSF for each new PLMN attachment, leading to fragmented network experiences, affecting service continuity, quality of service (QoS), and network resource allocation.

[0021] There is, therefore, a need in the art to provide a method and a system that can mitigate the disadvantages of the prior art.SUMMARY OF THE DISCLOSURE

[0022] In an embodiment, a method for optimizing slice selection in a network is disclosed. The method includes receiving, by an access and mobility management function (AMF), a registration request from a user equipment (UE). The registration request is a request to access one or more network slices. The method further includes retrieving, by the AMF, subscription data of the UE from a unified data management (UDM) based on the received registration request. Further, the method includes determining, by the AMF, validity of the UE for the one or more requested network slices based on the retrieved subscription data. Upon determining that the one or more requested network slices are valid for the UE, the AMF bypasses a query to a network slice selection function (NSSF) and proceeding with the slice selection for the UE.

[0023] In another embodiment, the retrieval of the subscription data of the UE from the UDM comprises transmitting, by the AMF, a subscription data query to the UDM based on the received registration request. The subscription data query comprises at least one of a UE identifier and one or more single network slice selection assistance information (S-NSSAI) values. The UE identifier includes a subscription permanent identifier (SUPI). The retrieval of the subscription data of the UE from the UDM further comprises receiving, by the AMF, the subscription data comprising a slice indicator associated with each of the one or more S-NSSAI values from the UDM. The slice indicator associated with each of the S-NSSAI values indicates global access or local access of the UE for the one or more network slices.

[0024] In an embodiment, the validity of the UE for the one or more requested network slices is determined based on the slice indicator associated with the received subscription data.

[0025] In one of the embodiments, the slice selection for the UE includes assigning, by the AMF, a network slice to the UE from the one or more requestednetwork slices based on the slice indicator associated with the received subscription data.

[0026] In an embodiment, the AMF performs a network slice selection procedure with the NSSF in response to determining that the one or more requested network slices are not valid based on the slice indicator.

[0027] In an embodiment, the network slice selection procedure includes transmitting, by the AMF, a slice selection request to the NSSF, determining, by the NSSF, one or more allowed network slices for the UE based on at least one of the slice selection request and subscription information associated with the UE, and transmitting, by the NSSF, at least one of the one or more allowed network slices and network slice instance (NSI) information to the AMF based on the determination.

[0028] In an embodiment, the AMF assigns a network slice to the UE based on at least one of the one or more allowed network slices and the NSI information.

[0029] In an embodiment, the NSSF retrieves the subscription information associated with the UE from the UDM.

[0030] In an embodiment, the AMF transmits a registration accept message to the UE after assigning the network slice to the UE based on the received registration request.

[0031] In another embodiment, the AMF bypasses queries to the NSSF for the one or more requested network slices during a mobility event of the UE between one or more Public Land Mobile Networks (PLMNs) based on the slice indicator.

[0032] In an embodiment, the method further comprises provisioning the slice indicator associated with each of the one or more S-NSSAI values in the UDM.

[0033] In an embodiment, a system included in an access and mobility management function (AMF) for optimal network slice selection is disclosed. The system includes a processing engine configured to receive a registration request from a user equipment (UE). The registration request is a request to access one or more networkslices. The processing engine is further configured to retrieve subscription data of the UE from a unified data management (UDM) based on the received registration request. Further, processing engine in the AMF is configured to determine validity of the UE for the one or more requested network slices based on the retrieved subscription data. Upon determining that the one or more requested network slices are valid for the UE, the processing engine in the system is configured to bypass a query to a network slice selection function (NSSF) and proceeding with the slice selection for the UE.

[0034] In embodiment, the processing engine configured to retrieve the subscription data of the UE from the UDM is further configured to transmit a subscription data query to the UDM based on the received registration request. The subscription data query comprises at least one of a UE identifier and one or more single network slice selection assistance information (S-NSSAI) values and the UE identifier comprises a subscription permanent identifier (SUPI). The processing engine is further configured to receive the subscription data comprising a slice indicator associated with each of the one or more S-NSSAI values from the UDM. The slice indicator associated with each of the S-NSSAI values indicates global access or local access of the UE for the one or more network slices.

[0035] In an embodiment, the processing engine determines the validity of the UE for the one or more requested network slices based on the slice indicator associated with the received subscription data.

[0036] In an embodiment, the processing engine is further configured to assign a network slice to the UE from the one or more requested network slices based on the slice indicator associated with the received subscription data.

[0037] In an embodiment, the processing engine is further configured to perform a network slice selection procedure with the NSSF in response to determining that the one or more requested network slices are not valid based on the slice indicator.

[0038] In one of the embodiments, the network slice selection procedure comprises transmitting, by the AMF, a slice selection request to the NSSF. The NSSF, determines one or more allowed network slices for the UE based on at least one ofthe slice selection request and subscription information associated with the UE and transmits at least one of the one or more allowed network slices and network slice instance (NSI) information to the AMF based on the determination.

[0039] In an embodiment, the processing engine assigns a network slice to the UE based on at least one of the one or more allowed network slices and the NSI information.

[0040] In an embodiment, the slice indicator is associated with each of the one or more S-NSSAI values in the UDM.

[0041] In an embodiment, a computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to execute a method for optimizing slice selection in a network, the method comprises receiving, by an access and mobility management function (AMF), a registration request from a user equipment (UE). The registration request is a request to access one or more network slices. The AMF retrieves subscription data of the UE from a unified data management (UDM) based on the received registration request and determines validity of the UE for the one or more requested network slices based on the retrieved subscription data. Upon determining that the one or more requested network slices are valid for the UE, the AMF bypasses a query to a network slice selection function (NSSF) and proceeding with the slice selection for the UE.OBJECTIVES OF THE PRESENT DISCLOSURE

[0042] Some of the objectives of the present disclosure, which at least one embodiment herein satisfies, are as follows:

[0043] An objective of the present disclosure is to provide a method and a system to optimize network slice selection by introducing a Global Slice Indicator, for reducing unnecessary signalling overhead between an Access and Mobility Management Function (AMF) and a Network Slice Selection Function (NSSF).

[0044] Another objective of the present disclosure is to provide a method and a system to minimize latency issues during slice selection by allowing the AMF todirectly select a Single Network Slice Selection Assistance Information (S-NSSAI) without querying the NSSF repeatedly.

[0045] Another objective of the present disclosure is to provide a method, and a system to improve resource utilization by eliminating redundant NSSF validations, thereby optimizing network performance and reducing processing load.

[0046] Another objective of the present disclosure is to provide a method, and a system to enhance Fifth Generation (5G) network scalability by simplifying slice management across multiple Public Land Mobile Networks (PLMNs).

[0047] Another objective of the present disclosure is to provide a method and a system to allow the AMF to determine whether an NSSF query is necessary based on the Global Slice Indicator value.

[0048] Other objects and advantages of the present disclosure will be more apparent from the following description, which is not intended to limit the scope of the present disclosure.BRIEF DESCRIPTION OF THE DRAWINGS

[0049] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes the disclosure of electrical components, electronic components or circuitry commonly used to implement such components.

[0050] FIG. 1 illustrates an exemplary network architecture for optimizing slice selection in a network, in accordance with an embodiment of the present disclosure.

[0051] FIG. 2 illustrates an exemplary block diagram of a system configured for optimizing slice selection in the network, in accordance with an embodiment of the present disclosure.

[0052] FIG. 3 illustrates an exemplary system architecture for optimizing slice selection in the network, in accordance with an embodiment of the present disclosure.

[0053] FIG. 4 illustrates an exemplary process flow for optimizing slice selection in the network, in accordance with an embodiment of the present disclosure.

[0054] FIG. 5 illustrates an exemplary flowchart for optimizing slice selection in the network, in accordance with an embodiment of the present disclosure.

[0055] FIG. 6 illustrates an exemplary computer system in which or with which the embodiments of the present disclosure may be implemented.

[0056] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network architecture102 -User(s)104 - User Equipments (UEs)106 - Network108 - System200 - Block diagram202 - Processor(s)204 - Memory206 -Interface(s)208 - Processing engine210 - Database300 - System Architecture302 - User Equipment (UE)304 - Access and Mobility Management Function (AMF)306 - Unified Data Management (UDM)308 - Network Slice Selection Function (NSSF)310 - Network Repository Function (NRF)400 - Flow Diagram500- Flowchart600 - Computer system610 - External Storage Device620 - Bus630 - Main Memory640 - Read Only Memory650 - Mass Storage Device660 - Communication Port670 - ProcessorDETAILED DESCRIPTION

[0057] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, thatembodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein. Example embodiments of the present disclosure are described below, as illustrated in various drawings in which like reference numerals refer to the same parts throughout the different drawings.

[0058] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.

[0059] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.

[0060] Also, it is noted that individual embodiments may be described as a process that is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure. A process may correspond to a method, a function, a procedure,a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.

[0061] The word “exemplary” and / or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and / or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive like the term “comprising” as an open transition word without precluding any additional or other elements.

[0062] Reference throughout this specification to “one embodiment” or “an embodiment” or “an instance” or “one instance” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0063] The terminology used herein is to describe particular embodiments only and is not intended to be limiting the disclosure. As used herein, the singular forms “a”, “an”, and “the” are intended to include the plural forms as well, unless the context indicates otherwise. It will be further understood that the terms “comprises” and / or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. As used herein, the term “and / or” includes any combinations of one or more of the associated listed items.It should be noted that the terms “mobile device”, “user equipment”, “user device”, “communication device”, “device” and similar terms are used interchangeably for the purpose of describing the invention. These terms are not intended to limit the scope of the invention or imply any specific functionality or limitations on the described embodiments. The use of these terms is solely for convenience and clarity of description. The invention is not limited to any particular type of device or equipment, and it should be understood that other equivalent terms or variations thereof may be used interchangeably without departing from the scope of the invention as defined herein.

[0064] As used herein, an “electronic device”, or “portable electronic device”, or “user device” or “communication device” or “user equipment” or “device” refers to any electrical, electronic, electromechanical, and computing device. The user device is capable of receiving and / or transmitting one or parameters, performing function / s, communicating with other user devices, and transmitting data to the other user devices. The user equipment may have a processor, a display, a memory, a battery, and an input-means such as a hard keypad and / or a soft keypad. The user equipment may be capable of operating on any radio access technology including but not limited to IP-enabled communication, Zig Bee, Bluetooth, Bluetooth Low Energy, Near Field Communication, Z-Wave, Wi-Fi, Wi-Fi direct, etc. For instance, the user equipment may include, but not limited to, a mobile phone, smartphone, virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general -purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other device as may be obvious to a person skilled in the art for implementation of the features of the present disclosure.

[0065] Further, the user device may also comprise a “processor” or “processing unit” includes processing unit, wherein processor refers to any logic circuitry for processing instructions. The processor may be a general -purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a Digital Signalling Processing (DSP) core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal codingdata processing, input / output processing, and / or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor is a hardware processor.

[0066] While considerable emphasis has been placed herein on the components and component parts of the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiment, as well as other embodiments of the disclosure, will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be interpreted merely as illustrative of the disclosure and not as a limitation.

[0067] Wireless communication technology has rapidly evolved over the past few decades. The first generation of wireless communication technology was analog, offering only voice services. Further, text messaging and data services became possible when the second-generation (2G) technology was introduced. The third generation (3G) technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth generation (4G) technology revolutionized the wireless communication with faster data speeds, improved network coverage, and security. Currently, fifth generation (5G) technology is being deployed, offering significantly faster data speeds, lower latency, and the ability to connect many devices simultaneously. Further, Sixth Generation (6G) successor to 5G is expected to provide significantly high data speed with reduced latency, which may offer improved connectivity for a vast number of devices concurrently. The capabilities of 6G enable new types of applications and services, such as advanced augmented reality (AR) and virtual reality (VR), holographic communications, and more immersive digital experiences. These advancements represent a significant leap forward from previous generations, enabling enhanced mobile broadband, improved Internet of Things (loT) connectivity, and more efficient use of network resources. The 6G technology promises to build upon these advancements, pushing the boundaries of wireless communication even further. While the 5G technology is still being rolledout globally, research and development into the 6G are rapidly progressing, with the aim of revolutionizing the way of connecting and interacting with technology.

[0068] With the evolution of 5G networks, mobile operators are increasingly adopting network slicing to provide customized services for different applications, such as Internet of Things (loT), autonomous vehicles, enterprise connectivity, and ultra-low-latency applications. Further, a Public Land Mobile Network (PLMN) enables operators to offer wireless communication services, and network slicing allows multiple virtualized networks to run on shared physical infrastructure. However, ensuring efficient slice selection and continuity across different PLMNs has become a critical challenge. Conventional slice selection mechanisms often result in excessive signalling overhead, network inefficiencies, and service disruptions, particularly when users move between different PLMNs.

[0069] In 5G networks, an Access and Mobility Management Function (AMF) is responsible for selecting an appropriate Single Network Slice Selection Assistance Information (S-NSSAI) for a user’s session. This process is typically handled by the Network Slice Selection Function (NSSF), which determines which slices are available for a given subscriber based on subscription data, network policies, and service requirements. When a user moves between PLMNs or re-establishes a session, the AMF must query the NSSF each time, even if the slice selection criteria remain unchanged.

[0070] The querying may result in unnecessary signalling delays and increased network load, reducing overall system efficiency. Additionally, the existing framework does not support a global slice selection mechanism, making it difficult to maintain consistent slice allocation for enterprise users, loT devices, and globally connected services. Enterprises with operations across multiple PLMNs require a way to seamlessly maintain their assigned network slices, ensuring uninterrupted connectivity and quality of service (QoS) without redundant slice selection procedures.

[0071] To address the above-mentioned issues, the present disclosure introduces an optimized slice selection mechanism by incorporating a Global slice indicator thatenables the AMF to recognize globally available slices without querying the NSSF for every PLMN change. The present disclosure allows predefined network slices to persist across different PLMNs, eliminating the need for repetitive slice selection procedures. The Global slice indicator is introduced in a Unified Data Management (UDM) to mark network slices as globally available. When a UE moves to a new PLMN, the AMF first checks the GSI before querying the NSSF. If a slice is globally available, the AMF may assign it directly without redundant signalling, significantly reducing slice selection latency and signalling overhead, and improving network efficiency.

[0072] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings. The various embodiments throughout the disclosure will be explained in more detail with reference to FIG. 1-FIG. 6.

[0073] FIG. 1 illustrates an exemplary network architecture 100 for optimizing slice selection in a network 106, in accordance with an embodiment of the present disclosure. As illustrated in FIG. 1, the network architecture 100 may include one or more UEs 104-1, 104-2... 104-N associated with one or more users 102-1, 102-2... 102-N in an environment. A person of ordinary skill in the art will understand that one or more users 102-1, 102-2... 102-N may be collectively referred to as the users 102. Similarly, a person of ordinary skill in the art will understand that one or more UEs 104-1, 104-2... 104-N may be collectively referred to as the UE 104, the UEs 104. Although only three UE 104 are depicted in FIG. 1, however, any number of the UE 104 may be included without departing from the scope of the ongoing description.

[0074] In an embodiment, the UE 104 may include smart devices operating in a smart environment, for example, an Internet of Things (loT) system. In such an embodiment, the UE 104 may include, but are not limited to, smartphones, smart watches, smart sensors (e.g., a mechanical, a thermal, an electrical, a magnetic, etc.), networked appliances, networked peripheral devices, networked lighting system, communication devices, networked vehicle accessories, networked vehicular devices, smart accessories, tablets, a smart television (TV), computers, asmart security system, a smart home system, other devices for monitoring or interacting with or for the users 102 and / or entities, or any combination thereof. A person of ordinary skill in the art will appreciate that the UE 104 may include, but not limited to, intelligent, multi-sensing, network-connected devices, that may integrate seamlessly with each other and / or with a central server or a cloudcomputing system or any other device that is network-connected.

[0075] Additionally, in some embodiments, the UE 104 may include, but not limited to, a handheld wireless communication device (e.g., a mobile phone, a smartphone, a phablet device, and so on), a wearable computer device (e.g., a headmounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a Global Positioning System (GPS) device, a laptop computer, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, a router, an outdoor device, and / or any other type of computer device with wireless communication capabilities, and the like. In an embodiment, the UE 104 may include, but are not limited to, any electrical, electronic, electromechanical, or equipment, or a combination of one or more of the above devices, such as virtual reality (VR) devices, augmented reality (AR) devices, a laptop, a general -purpose computer, a desktop, a personal digital assistant, a tablet computer, a mainframe computer, or any other computing device. Further, the UE 104 may include one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as a camera, an audio aid, a microphone, a keyboard, and input devices for receiving input from the user 102 or an entity such as a touchpad, a touch-enabled screen, an electronic pen, and the like. A person of ordinary skill in the art will appreciate that the UE 104 may not be restricted to the mentioned devices and various other devices may be used.

[0076] In FIG. 1, the UE 104 may communicate with the system 108 through the network 106 for sending or receiving various types of data. In an embodiment, the network 106 may include at least one of a 5G network, a 6G network, or the like. The network 106 may enable the UE 104 to communicate with other devices in the network architecture 100 and / or with the system 108. The network 106 may include a wireless card or some other transceiver connection to facilitate thiscommunication. In another embodiment, the network 106 may be implemented as, or include any of a variety of different communication technologies such as a wide area network (WAN), a local area network (LAN), a wireless network, a mobile network, a Virtual Private Network (VPN), the Internet, the Public Switched Telephone Network (PSTN), or the like.

[0077] In an embodiment, the network 106 may include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. The network 106 may also include, by way of example but not limitation, one or more of the Radio Access Network (RAN), a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof.

[0078] In an embodiment, the UE 104 is communicatively coupled with the network 106. The network 106 may receive a connection request from the UE 104. The network 106 may send an acknowledgment of the connection request to the UE 104. The UE 104 may transmit a plurality of signals in response to the connection request.

[0079] In an embodiment, the system 108 is implemented in AMF. The UE 104 sends a request along with a Single Network Slice Selection Assistance Information (S-NSSAI) to the system 108. The S-NSSAI is a key identifier that helps the system 108 to allocate the correct network slice based on the UE's subscription, service requirements, and network policies. Although FIG. 1 shows exemplary components of the network architecture 100, in other embodiments, the network architecture 100 may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 1. Additionally, or alternatively, one or more components of the network architecture100 may perform functions described as being performed by one or more other components of the network architecture 100.

[0080] FIG. 2 illustrates an exemplary block diagram 200 of the system 108 configured for optimizing slice selection in the network 106, in accordance with an embodiment of the disclosure. FIG. 2 is explained in conjunction with the FIG. 1.

[0081] In an embodiment, the system 108 may include one or more processor(s) 202. The one or more processor(s) 202 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and / or any devices that process data based on operational instructions. Among other capabilities, the one or more processor(s) 202 may be configured to fetch and execute computer-readable instructions stored in a memory 204 of the system 108. The memory 204 may be configured to store one or more computer-readable instructions or routines in a non-transitory computer readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory 204 may include any non-transitory storage device including, for example, volatile memory such as a Random-Access Memory (RAM), or a non-volatile memory such as an Erasable Programmable Read Only Memory (EPROM), a flash memory, and the like.

[0082] In an embodiment, the system 108 may include an interface(s) 206. The interface(s) 206 may include a variety of interfaces, for example, interfaces for data input and output devices (VO), storage devices, and the like. The interface(s) 206 may facilitate communication through the system 108. The interface(s) 206 may also provide a communication pathway for one or more components of the system 108. Examples of such components include, but are not limited to, a processing engine 208 and a database 210.

[0083] In an embodiment, the system 108 may include a processing engine 208 that may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine 208. In examples described herein, such combinations of hardware and programming may be implemented in several different ways. Forexample, the programming for the processing engine 208 may be processorexecutable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processing engine 208 may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine 208. In such examples, the system 108 may comprise the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the system 108 and the processing resource. In other examples, the processing engine 208 may be implemented by electronic circuitry. In an aspect, the processing engine 208 may be implemented within an Access and Mobility Management Function (AMF) of the network 106.

[0084] In an embodiment, the processing engine (208) is configured to receive a request along with a Single Network Slice Selection Assistance Information (S-NSSAI) from the UE 104. The request may be a registration request sent from the UE 104 towards the AMF. The S-NSSAI is a key identifier that helps the network 106 to allocate the correct network slice based on the UE's subscription, service requirements, and network policies.

[0085] In an embodiment, the processing engine (208) is configured to retrieve subscription data associated with the UE 104 from a network function. The network function may be a Unified Data Management (UDM). The UDM is responsible for storing subscriber profiles, authentication data, policy settings, and network slice access rights. Further, the UDM may store a global slice indicator associated with specific S-NSSAIs that are valid across all PLMNs of the same operator. The processing engine (208) may transmit a Nudm SDM GET request to retrieve the subscription data. In an embodiment, the processing engine (208) requests UE's Subscription data from the UDM by invoking the Nudm SDM Get service operation. Further, the UDM may get the subscription information from a Unified Data Repository (UDR) by Nudr DM Query (SUPI, Slice Selection Subscription data). Further, the UDM respond to the Nudm SDM Get request by a Nudm SDM Get response. The Nudm SDM Get response includes the SliceSelection Subscription data including Subscribed S-NSSAIs along with the associated global slice indicator. In an embodiment, the UDM is provisioned with the slice indicator associated with each of the one or more S-NSSAI values by an administrator or service operator.

[0086] In an embodiment, the processing engine (208) is configured to extract an indicator from the subscription data associated with the requested S-NSSAI. The extracted indicator may be the global slice indicator. The global slice indicator helps to determine whether a particular network slice is globally available across multiple PLMNs. The global slice indicator ensures that the UE 104 may retain the same network slice across different PLMNs, reducing signalling overhead, improving service continuity, and optimizing slice selection efficiency in 5G networks.

[0087] In an embodiment, the processing engine (208) may be configured to determine a flag associated with the extracted indicator is enabled. The flag associated with the global slice indicator is stored in the UDM, indicating whether a specific S-NSSAI (network slice) is globally available across multiple PLMNs. The processing engine (208) may check a status of the flag corresponding to a presence of the requested S-NSSAI in the specific S-NSSAI, indicating the UE 104 may use the same network slice globally.

[0088] In an embodiment, the processing engine (208) is configured to use the S-NSSAI received along with the request for slice selection, based on the determination that the flag associated with the global slice indicator is enabled. For the flag to be enabled, the processing engine (208) is configured to use the requested S-NSSAI to determine the appropriate network slice selection for the UE 104. The slice selection process depends on whether the S-NSSAI is globally available (determined via the Global Slice Indicator) or if further slice selection procedures are required through a Network Slice Selection Function (NSSF). If the global slice indicator indicates that the requested S-NSSAI is globally available, the AMF directly assign the network slice without querying the NSSF.

[0089] In an embodiment, if the flag associated with the global slice indicator is disabled, the AMF queries the NSSF to retrieve the S-NSSAI for the UE 104. TheAMF may query the NSSF using a Nnssf_NSSelection_Get request, requesting the appropriate S-NSSAI for the UE 104. The AMF invokes the Nnssf_NSSelection_Get request from the NSSF by including requested NSSAI, optionally mapping of requested NSSAI, subscribed S-NSSAIs with the default S-NSSAI indication, allowed NSSAI for the other access type (if any), mapping of allowed NSSAI, PLMN ID of the Subscriber Permanent Identifier (SUPI) and the Tracking Area Identity (TAI) of the UE 104. Further, the NSSF transmit a Nnssf_NSSelection_Get response with the appropriate S-NSSAI and Network Slice instance Identifier (NSI) information for the UE 104 to the AMF. Finally, the AMF transmit a registration response corresponding to the registration request to the UE 104. The registration response may include the appropriate S-NSSAI, which is queried from the NSSF. The appropriate S-NSSAI is further used to determine the network slice for the UE 104.

[0090] In an embodiment, the system 108 may include a database 210 that includes data (e.g., session related to UE 104, subscriber details, Subscription Permanent Identifier (SUPI), subscription details etc.) that may be either stored or generated as a result of functionalities implemented by any of the components of the processor 202 or the processing engine 208.

[0091] FIG. 3 illustrates an exemplary system architecture 300 for optimizing slice selection in the network 106, in accordance with an embodiment of the present disclosure. FIG. 3 is explained in conjunction with the FIGs. 1 and 2. The system 300 may include a User Equipment (UE) 302, an Access and Mobility management Function (AMF) 304, a Unified Data Management (UDM) 306, a Network Slice Selection Function (NSSF) 308, and Network Repository Function (NRF) 310.

[0092] In an embodiment, the UE 302 may be a 5G-enabled device such as smartphone, loT device, autonomous vehicle that requires network access and slicing support. The UE 302 may transmit a registration request or a Protocol Data Unit (PDU) session establishment request to the AMF 304 via a N1 interface. The request may include a single network slice selection assistance information (S-NSSAI), which indicates the network slice needed by the UE 302. The N1 interface enables communication between the UE 302 and the AMF 304. The N 1 interface isresponsible for signalling and control message exchange between the UE 302 and AMF 304, responsible for providing slice preferences S-NSSAI to the AMF 304. Further, the N1 interface is based on Non-Access Stratum (NAS) protocol, which handle communication between the UE 302 and the AMF 304.

[0093] In an embodiment, the AMF 304 is responsible for handling mobility management, session management, and access control for UE 302. The AMF 304 may include a global slice handler decision logic which may be responsible for retrieving subscription data from the UDM 306 via the N8 interface. Further, the AMF may extract the global slice indicator to determine if a network slice corresponding to the requested S-NSSAI is globally available. The AMF 304 may perform direct slice selection without needing to consult the NSSF 308 based on the global slice indicator, reducing network signalling overhead and improving efficiency.

[0094] In an embodiment, the UDM 306 is responsible for subscriber management and authentication in the 5G network. The UDM 306 store subscription data, including the global slice indicator. In an embodiment, the UDM 306 may provide the subscription data and the global slice indicator to the AMF 304 via the N8 interface based on the query from the AMF 304. The N8 interface allows the AMF 304 to retrieve subscriber data from the UDM 306, ensuring proper authentication, authorization, and slice allocation. Further, when the UE 302 registers with the network 106, the AMF uses N8 to retrieve subscription data and the global slice indicator from the UDM 306.

[0095] In an embodiment, the NSSF 308 is responsible for selecting network slices based on the requested S-NSSAI, when the global slice indicator is not present in the UDM 306. If the AMF 304 is not able to determine the network slice using global slice indicator, the AMF 304 may send a query over the N22 interface to the NSSF 308. Further, the NSSF 308 consults the NRF 310 and determines the most suitable slice. In an embodiment, the AMF 304 may bypass the NSSF 308, if the global slice indicator confirms slice availability. The NRF 310 may store and manage network slice information. If required, the NSSF 308 may query the NRF using N31 interface to fetch information about available slices.

[0096] Further, the N22 interface is used by the AMF 304 to request network slice selection decisions from the NSSF 308. If the AMF 304 may not determine the slice using the global slice indicator from the UDM 308, the AMF 304 sends a Slice Selection Request to the NSSF 308 over N22. Further, the NSSF 308 returns the selected slice information to the AMF 304 over the N22 interface. The N31 interface is responsible for retrieving network slice service information to assist in selecting the most appropriate slice for a given UE 302 request. If the NSSF 308 lacks sufficient slice selection information, the NSSF 308 queries the NRF 310 using the N31 interface to retrieve slice service details.

[0097] In an embodiment, the NRF 310 may act as a database of available network slices and their attributes, responding to the NSSF 308 with updated information using the N31 interface. Further, aN27 interface enables the AMF 304 to discover and register services available in the NRF 310, specifically related to network slice selection and management. The AMF 304 may query the NRF 310 to discover available network functions that may assist in network slice selection and mobility management. Further, the NRF 310 may responds with a list of relevant network function, including the NSSF 308.

[0098] FIG. 4 illustrates an exemplary process flow 400 for optimizing slice selection in the network 106, in accordance with an embodiment of the present disclosure. FIG. 4 is explained in conjunction with FIGS. 1, 2, and 3. In an embodiment, the method 400 may be implemented by the UE 302, the AMF 304, the UDM 306, and the NSSF 308 of the network 106.

[0099] At step 402, the UE 302 transmit a registration request to the AMF 304. The registration request may include a requested S-NSSAI, indicating desired network slices for the UE 302.

[0100] At step 404, the AMF 304 transmits a request to query the subscription data associated with the UE 302 from the UDM 306. The request may be a Nudm SDM Get request which may contain the SUPI and requested slice information of the UE 302.

[0101] At step 406, the UDM 306 responds with subscription data along with a global slice indicator corresponding to the Nudm SDM Get request. The subscription data may include subscribed S-NSSAIs and the associated global slice indicator. The global slice indicator helps the AMF 304 to decide whether to use direct slice selection or query the NSSF 308.

[0102] At step 408, the AMF 304 determines that a flag corresponding to the global slice indicator is enabled (Global Slice = TRUE). In an embodiment, the flag is enabled when the global slice indicator associated with the requested S-NSSAI is present. Further, the AMF 304 may not query the NSSF 308 and performs direct slice selection. Further, the direct slice selection may represent using the network slice corresponding to the requested S-NSSAI, skipping the NSSF 308 query, reducing signalling overhead.

[0103] Upon determining that the flag corresponding to the global slice indicator is disabled (Global Slice = FALSE), at step 410, the AMF 304 transmits a slice selection request to the NSSF 308 to fetch a network slice. The slice selection request may be the Nnssf_NS Selection _Get request, requesting an appropriated S-NSSAI from the NSSF 308.

[0104] At step 412, the NSSF 308 transmits the appropriate S-NSSAI and NSI information to the AMF 304 corresponding to the Nnssf_NS Selection _Get request. The AMF 304 may determine the network slice to assign to the UE 302 based on the received appropriate S-NSSAI and NSI information.

[0105] At step 414, the AMF 304 transmits a registration accept message to the UE 302 corresponding to the registration request. The registration accept message may include the appropriate S-NSSAI and the associated assigned network slice. Further, the UE 302 may be registered to the network 106 and use the appropriate S-NSSAI and the corresponding network slice for further communication in the network 106.

[0106] In an exemplary embodiment, consider a global enterprise with offices in multiple countries, each connected through a private 5G network slice for secure and high-speed corporate communications. Employees traveling between differentcountries require seamless connectivity to their corporate applications, cloud storage, and secure databases, without experiencing delays due to repeated slice selection processes. With conventional 5G network slice selection, when the employee's UE (302) moves from their home network (PLMN A) to a roaming network (PLMN B), the AMF (304) in PLMN B must query the NSSF (308) to determine the appropriate S-NSSAI, leading to signalling overhead, delays in service activation, and potential disruptions in enterprise applications.

[0107] However, the present disclosure recognizes that the corporate network slice is globally available across all enterprise locations. When the employee’s UE connects to PLMN B, the AMF (304) first checks the global slice indicator in the UDM (306). Since the slice is marked as globally available, the AMF (304) directly assigns the pre-configured slice without querying the NSSF (308) a mobility event, eliminating unnecessary delays and reducing signalling traffic. As a result, the employee experiences uninterrupted corporate access, whether they are in their home country or traveling internationally. The enterprise benefits from reduced network overhead, improved resource efficiency, and seamless multi-PLMN slice continuity, ensuring fast and reliable business operations worldwide. In an embodiment, the mobility event is one of handover, cell reselection, or beam switching..

[0108] FIG. 5 illustrates a flow diagram of a method 500 for optimizing slice selection in the network (106), in accordance with an embodiment of the present disclosure. FIG. 5 is explained in conjunction with FIGS. 1, 2, 3, and 4.

[0109] At step 502 an access and mobility management function (AMF) (304) receives a registration request from a user equipment (UE) (302). The registration request is a request to access one or more network slices. The UE 302 may transmit a registration request or a Protocol Data Unit (PDU) session establishment request to the AMF 304 via a N1 interface. The request may include a single network slice selection assistance information (S-NSSAI), which indicates the network slice needed by the UE 302. The N1 interface enables communication between the UE 302 and the AMF 304.

[0110] At step 504, the AMF (304) retrieves subscription data of the UE (302) from a unified data management (UDM) (306) based on the received registration request. The retrieval of the subscription data of the UE (302) from the UDM (306) includes transmitting, by the AMF (304), a subscription data query to the UDM (306) based on the received registration request. The subscription data query comprises at least one of a UE identifier and one or more single network slice selection assistance information (S-NSSAI) values. The UE identifier comprises a subscription permanent identifier (SUPI). The AMF (304) receives the subscription data comprising a slice indicator associated with each of the one or more S-NSSAI values from the UDM (306). The slice indicator associated with each of the S-NSSAI values indicates global access or local access of the UE (302) for the one or more network slices. In an embodiment, global access indicates that the UE is allowed to access services from all the network slices, including roaming scenarios across multiple PLMNs. Local access indicates that the UE is restricted to accessing services only within a specific PLMN or geographical region or a limited number of slices. For example, in a local access, if there are 5 slices, the UE is allowed to access only 4 slices.[OHl] At step 506, the AMF (304) determines validity of the UE (302) for the one or more requested network slices based on the retrieved subscription data. The validity is determined based on the slice indicator associated with the received subscription data.

[0112] At step 508, upon determining that the one or more requested network slices are valid for the UE (302), the AMF (304) bypasses a query to a network slice selection function (NSSF) (308) and proceeds with the slice selection for the UE (302). The AMF (304) assigns a network slice to the UE (302) from the one or more requested network slices based on the slice indicator associated with the received subscription data. The AMF (304) performs a network slice selection procedure with the NSSF (308) in response to determining that the one or more requested network slices are not valid based on the slice indicator.

[0113] In the network slice selection procedure comprises the AMF (304) transmits a slice selection request to the NSSF (308). The NSSF (308) determines one or moreallowed network slices for the UE (302) based on at least one of the slice selection request and subscription information associated with the UE (302). The NSSF (308) transmits at least one of the one or more allowed network slices and network slice instance (NSI) information to the AMF (304) based on the determination. The AMF (304) assigns a network slice to the UE (302) based on at least one of the one or more allowed network slices and the NSI information.

[0114] FIG. 6 illustrates an exemplary computer system 600 in which or with which embodiments of the present disclosure may be implemented. As shown in FIG. 6, the computer system 600 may include an external storage device 610, a bus 620, a main memory 630, a read-only memory 640, a mass storage device 650, communication port(s) 660, and a processor 670. A person skilled in the art will appreciate that the computer system 600 may include more than one processor and communication ports. The processor 670 may include various modules associated with embodiments of the present disclosure. The communication port(s) 660 may be any of an RS-232 port for use with a modem-based dialup connection, a 10 / 100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication port(s) 660 may be chosen depending on a network, such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system 600 connects.

[0115] The main memory 630 may be a Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory 640 may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chips for storing static information e.g., start-up or Basic Input / Output System (BIOS) instructions for the processor 670. The mass storage device 650 may be any current or future mass storage solution, which can be used to store information and / or instructions. Exemplary mass storage device 650 includes, but is not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and / or Firewire interfaces), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g. an array of disks.

[0116] The bus 620 communicatively couples the processor 670 with the other memory, storage, and communication blocks. The bus 620 may be, e.g. a Peripheral Component Interconnect (PCI)ZPCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), Universal Serial Bus (USB), or the like, for connecting expansion cards, drives, and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor 670 to the computer system 600.

[0117] Optionally, operator and administrative interfaces, e.g. a display, keyboard, joystick, and a cursor control device, may also be coupled to the bus 620 to support direct operator interaction with the computer system. Other operator and administrative interfaces can be provided through network connections connected through the communication port(s) 660. Components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system 600 limit the scope of the present disclosure.

[0118] In an embodiment, the present disclosure provides a method for optimizing slice selection in a network. The method includes receiving a request along with a Single Network Slice Selection Assistance Information (S-NSSAI) from a User Equipment (UE) (302). The method further includes retrieving subscription data associated with the UE (302) from a network function (UDM) (306). Further, the method includes extracting an indicator from the subscription data associated with the requested S-NSSAI. The method includes determining a flag associated with the extracted indicator is enabled. Based on determination, the method includes using the requested S-NSSAI for slice selection.

[0119] In an embodiment, the present disclosure provides a method for optimizing slice selection in a network (106). The present disclosure adds a Global Slice indicator to subscription data of the UE (302). The Global Slice indicator is associated with specific S-NSSAIs. The Global Slice indicator is stored in the UDM (306). Further, the UE (302) initiates registration with requested S-NSSAIs. The AMF (304) retrieves subscription data from the UDM (306). The AMF (304) checks Global Slice indicator for requested S-NSSAIs. Further, IF Global Slice == TRUE, aNSSF query is skipped, and the AMF (304) directly use the S-NSSAI. IF Global Slice == FALSE, a standard NSSF query process is followed by the AMF(304). For Global_Slice=TRUE, the AMF (304) directly proceeds with slice selection, and no NSSF validation is required. Further, the present disclosure maintains Global Slice status during mobility events such as handovers. The present disclosure skips NSSF queries in new areas if Global_Slice=TRUE. Further, the present disclosure enables seamless service continuity.

[0120] In an embodiment, a method (500) and system (108) for addition of a flag (i.e., NSSF global slice indicator) and enhanced AMF decision logic for slice selection. The subscription data is enhanced at the UDM (306) by addition of a flag (i.e., Global Slice indicator) to subscription data where Global Slice indicator is associated with specific S-NSSAIs. Further, a UE (302) initiates registration with requested S-NSSAIs with the AMF (304) and AMF (304) retrieves subscription data from UDM (306). The AMF (304) checks flag (i.e., Global Slice indicator) for requested S-NSSAIs in the UDM (306). If flag is true, the AMF (304) skips querying Network Slice Selection Function (NSSF) (308) and directly use S-NSSAI and if the flag is false, AMF (304) follows the standard NSSF query process.

[0121] In an embodiment, the global slice indicator is added in the subscription data that fundamentally changes how network slice selection is performed. The global slice indicator may be a Boolean attribute, when set to TRUE, indicates that a particular S-NSSAI is valid across all PLMNs of the operator, eliminating the need for repeated NSSF queries.

[0122] In an embodiment, a computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to execute a method (500) for optimizing slice selection in a network (106), the method (500) comprises receiving, by an access and mobility management function (AMF) (304), a registration request from a user equipment (UE) (302). The registration request is a request to access one or more network slices. The AMF (304) retrieves subscription data of the UE (302) from a unified data management (UDM) (306) based on the received registration request and determines validity of the UE (302) for the one or more requested network slices based on the retrieved subscription data. Upon determining that the one or more requested network slices are valid for the UE(302), the AMF (304) bypasses a query to a network slice selection function (NSSF) (308) and proceeding with the slice selection for the UE (302).

[0123] While the foregoing describes various embodiments of the invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof. The scope of the invention is determined by the claims that follow. The invention is not limited to the described embodiments, versions or examples, which are included to enable a person having ordinary skill in the art to make and use the invention when combined with information and knowledge available to the person having ordinary skill in the art.

[0124] The method and system of the present disclosure may be implemented in a number of ways. For example, the methods and systems of the present disclosure may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above-described order for the steps of the method is for illustration only, and the steps of the method of the present disclosure are not limited to the order specifically described above unless specifically stated otherwise. Further, in some embodiments, the present disclosure may also be embodied as programs recorded in a recording medium, the programs including machine-readable instructions for implementing the methods according to the present disclosure. Thus, the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.

[0125] While considerable emphasis has been placed herein on the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be implemented merely as illustrative of the disclosure and not as a limitation.TECHNICAL ADVANCEMENTS

[0126] Reduction in Redundant Network Slice Selection Function (NSSF) Queries: The present disclosure introduces a system and a method that enables an Access and Mobility Management Function (AMF) to determine whether a slice is globally available without repeatedly querying the NSSF, reducing signalling overhead.

[0127] Optimized Network Slice Selection: The present disclosure ensures that once a slice is determined to be globally available, the slice can be reused across different Public Land Mobile Networks (PLMNs) without additional selection procedures, improving network efficiency.

[0128] Lower Latency in Slice Assignment: By eliminating unnecessary slice selection delays, the present disclosure accelerates Protocol Data Unit (PDU) session establishment, ensuring faster service activation and seamless mobility.

[0129] Improved Inter-PLMN Roaming and Slice Continuity: The present disclosure allows network slices to persist across multiple PLMNs, making it ideal for global enterprises, Internet of Things (loT) applications, and mission-critical services that require uninterrupted connectivity.

[0130] Efficient Resource Utilization: By preventing unnecessary slice re-evaluation, the present disclosure helps reduce processing load on the NSSF, optimizing the core network's computational resources.

[0131] Better Quality of Service (QoS) Maintenance: Since network slices are maintained globally, services that require low latency, high reliability, or guaranteed bandwidth experience fewer disruptions and improved QoS consistency.

[0132] Backward Compatibility with Existing Standards: The present disclosure integrates seamlessly with existing 5G network slice selection procedures, ensuring that networks can adopt the solution without disrupting existing systems.

Claims

CLAIMSWe Claim1. A method (500) for optimizing slice selection in a network (106), the method (500) comprising:receiving, by an access and mobility management function (AMF) (304), a registration request from a user equipment (UE) (302), wherein the registration request is a request to access one or more network slices;retrieving, by the AMF (304), subscription data of the UE (302) from a unified data management (UDM) (306) based on the received registration request;determining, by the AMF (304), validity of the UE (302) for the one or more requested network slices based on the retrieved subscription data; andupon determining that the one or more requested network slices are valid for the UE (302), bypassing, by the AMF (304), a query to a network slice selection function (NSSF) (308) and proceeding with the slice selection for the UE (302).

2. The method (500) as claimed in claim 1, wherein the retrieval of the subscription data of the UE (302) from the UDM (306) comprising:transmitting, by the AMF (304), a subscription data query to the UDM (306) based on the received registration request, wherein the subscription data query comprises at least one of a UE identifier and one or more single network slice selection assistance information (S-NSSAI) values, wherein the UE identifier comprises a subscription permanent identifier (SUPI); andreceiving, by the AMF (304), the subscription data comprising a slice indicator associated with each of the one or more S-NSSAI values from the UDM (306), wherein the slice indicator associated with each of the one or more S-NSSAI values indicates global access or local access of the UE (302) for the one or more network slices.

3. The method (500) as claimed in claim 2, wherein the validity of the UE (302) for the one or more requested network slices is determined based on the slice indicator associated with the received subscription data.

4. The method (500) as claimed in claim 2, wherein the slice selection for the UE (302) comprises:assigning, by the AMF (304), a network slice to the UE (302) from the one or more requested network slices based on the slice indicator associated with the received subscription data.

5. The method (500) as claimed in claim 2, further comprising:performing, by the AMF (304), a network slice selection procedure with the NSSF (308) in response to determining that the one or more requested network slices are not valid based on the slice indicator.

6. The method (500) as claimed in claim 5, wherein the network slice selection procedure comprising:transmitting, by the AMF (304), a slice selection request to the NSSF (308);determining, by the NSSF (308), one or more allowed network slices for the UE (302) based on at least one of the slice selection request and subscription information associated with the UE (302); andtransmitting, by the NSSF (308), at least one of the one or more allowed network slices and network slice instance (NSI) information to the AMF (304) based on the determination.

7. The method (500) as claimed in claim 6, further comprising:assigning, by the AMF (304), a network slice to the UE (302) based on at least one of the one or more allowed network slices and the NSI information.

8. The method (500) as claimed in claim 6, further comprising retrieving, by the NSSF (308), the subscription information associated with the UE (302) from the UDM (306).

9. The method (500) as claimed in claim 4, further comprising transmitting, by the AMF (304), a registration accept message to the UE (302) after assigning the network slice to the UE (302) based on the received registration request.

10. The method (500) as claimed in claim 2, wherein the AMF (304) bypasses queries to the NSSF (308) for the one or more requested network slices during a mobility event of the UE (302) between one or more Public Land Mobile Networks (PLMNs) based on the slice indicator.

11. The method (500) as claimed in claim 2, further comprising provisioning the slice indicator associated with each of the one or more S-NSSAI values in the UDM (306).

12. A system (108) for optimal network slice selection, the system (108) comprising a processing engine (208) in an access and mobility management function (AMF) (304), the processing engine (208) configured to:receive a registration request from a user equipment (UE) (302), wherein the registration request is a request to access one or more network slices;retrieve subscription data of the UE (302) from a unified data management (UDM) (306) based on the received registration request;determine validity of the UE (302) for the one or more requested network slices based on the retrieved subscription data; andbypass a query to a network slice selection function (NSSF) (308) and proceed with the slice selection for the UE (302) upon determining that the one or more requested network slices are valid for the UE (302).

13. The system (108) as claimed in claim 12, wherein the processing engine (208) configured to retrieve the subscription data of the UE (302) from the UDM (306) is further configured to:transmit a subscription data query to the UDM (306) based on the received registration request, wherein the subscription data query comprises at least one of a UE identifier and one or more single network slice selection assistance information (S-NSSAI) values, wherein the UE identifier comprises a subscription permanent identifier (SUP I); andreceive the subscription data comprising a slice indicator associated with each of the one or more S-NSSAI values from the UDM (306), wherein the slice indicator associated with each of the S-NSSAI values indicates global access or local access of the UE (302) for the one or more network slices.

14. The system (108) as claimed in claim 12, wherein the processing engine (208) determines the validity of the UE (302) for the one or more requested network slices based on the slice indicator associated with the received subscription data.

15. The system (108) as claimed in claim 12, wherein the processing engine (208) is further configured to:assign a network slice to the UE (302) from the one or more requested network slices based on the slice indicator associated with the received subscription data.

16. The system (108) as claimed in claim 12, wherein processing engine (208) is configured to:perform a network slice selection procedure with the NSSF (308) in response to determining that the one or more requested network slices are not valid based on the slice indicator, wherein the NSSF (308) retrieves the subscription information associated with the UE (302) from the UDM (306).

17. The system (108) as claimed in claim 16, wherein to perform the network slice selection procedure:the AMF (304) is configured to transmit a slice selection request to the NSSF (308); andthe NSSF (308) is configured to determine one or more allowed network slices for the UE (302) based on at least one of the slice selection request and subscription information associated with the UE (302) and transmit at least one of the one or more allowed network slices and network slice instance (NSI) information to the AMF (304) based on the determination.

18. The system (108) as claimed in claim 17, the processing engine (208) assigns a network slice to the UE (302) based on at least one of the one or more allowed network slices and the NSI information wherein the processing engine (208) transmits a registration accept message to the UE (302) after assigning the network slice to the UE (302) based on the received registration request.

19. The system (108) as claimed in claim 12, wherein the slice indicator is associated with each of the one or more S-NSSAI values in the UDM (306) and the AMF (304) bypasses queries to the NSSF (308) for the one or more requested network slices during a mobility event of the UE (302) between one or more Public Land Mobile Networks (PLMNs) based on the slice indicator.

20. A computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to execute a method (500) for optimizing slice selection in a network (106), the method (500) comprising:receiving, by an access and mobility management function (AMF) (304), a registration request from a user equipment (UE) (302), wherein the registration request is a request to access one or more network slices;retrieving, by the AMF (304), subscription data of the UE (302) from a unified data management (UDM) (306) based on the received registration request;determining, by the AMF (304), validity of the UE (302) for the one or more requested network slices based on the retrieved subscription data; andupon determining that the one or more requested network slices are valid for the UE (302), bypassing, by the AMF (304), a query to a network slice selection function (NSSF) (308) and proceeding with the slice selection for the UE (302).

Images