FORM 2
THE PATENTS ACT, 1970 (39 OF 1970) & THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR PROVIDING SLICE INFORMATION IN A COMMUNICATION NETWORK”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

METHOD AND SYSTEM FOR PROVIDING SLICE INFORMATION IN A
COMMUNICATION NETWORK
FIELD OF INVENTION
[0001] Embodiments of the present disclosure generally relate to wireless communication systems. More particularly, embodiments of the present disclosure relate to providing slice information in a communication network.
BACKGROUND OF DISCLOSURE
[0002] The following description of the related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.
[0003] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered only voice services. However, with the advent of the second-generation (2G) technology, digital communication and data services became possible, and text messaging 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 wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. With each generation, wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.
[0004] In the 5G communication system, there is provided a plurality of network functions (NFs), for example an Access and Mobility Management Function (AMF), session

management function (SMF), Authentication Server function (AUSF), a Network Slice Selection Function (NSSF), Policy control function (PCF), a Network Repository Function (NRF), Network Data Analytics Function (NWDAF) and the like. One or more of the aforementioned NFs communicates with each other, to implement multiple activities on the 5G communication system. For example, for data transfer, the AMF communicates with SMF, to initiate the communication. Accordingly, one or more connections are established between two peer NFs, to allow communication therebetween, and thus enable such activities there between.
[0005] Network slicing enables the creation of separate virtualized sub-networks that can be tailored to meet the specific requirements of different applications. In network slicing, a network is divided into multiple logical partitions or slices, where the multiple logical network partitions are optimised for specific uses, service operations, or for specific requirements pertaining to various users. These partitions have the right construct of isolation, resources, and topology. The process of Network slicing creates end-to-end logical networks that have specific characteristics and are operated independently. Thus, for example, where a new service or a new application is needed to be served by the network, a cloud-native core, for example, may be able to create an instance, or slice, of an entire network virtually. This network slice may be fully customized with network resources for the allocated use case. In fact, these resources may even be dedicated for the purpose if required.
[0006] Further, a set of Network Function instances and the required resources (for example, computational machines, storage systems, and other networking resources) form a Network Slice. The different parts of a network slice are grouped as Network Slice Subnets (for example, radio access network, 5G core network, etc.). Also, these network slice subnets or network slice subnet instances can be managed independently from the network slice instance. In other words, the network slice subnet may be viewed or construed as a representation of the management aspects of a set of managed functions and the required resources (e.g. compute, storage and networking resources) in a network slice.
[0007] Normally, the first access and mobility management function (AMF) node that receives the registration request from a user equipment (UE) initiates the network slice

instance selection for a user equipment as part of the registration process. The AMF works with the Network Slice Selection Function (NSSF) to choose the correct Network Slice instance (e.g., based on Allowed S-NSSAIs (Single Network Slice Selection Assistance Information), PLMN ID (Public Land Mobile Network identifier), etc.) after retrieving the slices that the user subscription permits.
[0008] At registration phase, the base station (or gNodeB, or gNB) selects the AMF which supports UE requested slices based on Requested NSSAI (network slice selection assistance information). Otherwise gNB selects default configurable AMF.
[0009] A Network Slice Selection Function (NSSF) is one of the key components of 5G communication system. The 5G communication system can deploy multiple Network Slice Instances delivering exactly the same features for different groups of UEs. The NSSF offers services to the AMF and NSSF in a different PLMN via the NSSF service-based interface. Following are the key Network Slice Selection Function (NSSF) functionalities:
• Authorize the set of network slice instances for AMF Availability (Registration).
• Determining the Allowed Network Slice Selection Assistance Information (NSSAI) for selection of Slice information.
• Determining the AMF Set /Candidate list to be used to serve the UE based on the AMF Availability (registration).
[0010] Network slicing signalling process happens at a few different stages like initial attach, establishment of a packet data unit (PDU) session, policy change, etc. PDU session establishment would be mostly for defining various quality of service (QoS) flow and policy change would be to associate the specific slices to a specific UE/application as specified in the Policy Rules. When UE sends registration request, it specifies NSSAI. By this NSSAI, UE specifies to the network as to what types of slices the UE needs to access. Then this requested slice information is transferred to UDM. UDM checks if the requested slice is allowed for the specific UE. If it is allowed, the UDM accepts the request. If not, it rejects the request. Once the slice request is accepted, the acceptance is notified to the UE with a few additional information like configured NSSI, NSSI inclusion mode, etc. Further, for various use cases, the network slicing can be used with specific slice information. For example, customized QoS parameters and resource allocation, and security policies, etc.

may be various parameters that may be defined in the network slice information and can have different values as per the use cases.
[0011] In multi-Public Land Mobile Network (PLMN) environment, traditionally, each PLMN would require a separate AMF instance. Each single AMF instance caters to single AMF set ID, which supports single PLMN network. For multiple PLMN supports, there is a requirement of multiple AMF set IDs and multiple AMF instances. The AMF Identifier (AMFI) may be constructed from an AMF Region identifier (ID), an AMF Set ID and an AMF Pointer. The AMF Region ID identifies the region, the AMF Set ID uniquely identifies the AMF Set within the AMF Region, and the AMF Pointer identifies one or more AMFs within the AMF Set. Further, an AMF instance ID may be a combination of the AMF Region ID, AMF Set ID, AMF Pointer, mobile network code (MNC), and mobile country code (MCC). An AMF Set consists of some AMFs that serve a given area and Network Slices. AMF Set is unique within an AMF Region, and it comprises of AMFs that support the same Network Slices. Multiple AMF Sets may be defined per AMF Region. Also, multiple instances of AMF are part of same set-ID which serve same slice data. It may be noted for the purpose of clarity that the term “set ID” should be construed as “AMF set ID” throughout this disclosure. For providing services to more than one PLMN network, there are various deployment challenges due to complexity and resource overhead for maintaining the many AMF set-IDs and this process is not cost effective and is time consuming.
[0012] Thus, there exists an imperative need in the art to provide a solution for providing a slice information in a communication network for supporting multi-PLMN environments, which the present disclosure aims to address.
SUMMARY OF THE DISCLOSURE
[0013] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.

[0014] An aspect of the present disclosure may relate to a method for providing slice information in a communication network. The method comprises receiving, at a network slice selection function (NSSF) unit from an access and mobility management function (AMF) unit, a slice information request related to a network slice associated with a public land mobile network (PLMN) in a multi-PLMN environment, wherein the slice information request comprises of an information related to one or more slices provisioned per tracking area code (TAC), an instance identifier and a set identifier. Further, the method comprises querying, by the NSSF unit, a slice database with the instance identifier and the set identifier. Further, the method comprises identifying, by the NSSF unit, a slice information based on a mapping of the instance identifier and the set identifier in a set of data stored in the slice database. Further, the method comprises transmitting, by the NSSF unit, the slice information to the AMF unit in response to the slice information request based on the mapping of the instance identifier and the set identifier in the set of data.
[0015] In an exemplary aspect of the present disclosure, the method further comprises dynamically allocating, by the AMF unit, network resources to one or more user equipment in the PLMN in a multi-PLMN environment based on the slice information.
[0016] In an exemplary aspect of the present disclosure, the set of data is generated based on receiving, at the NSSF unit, a data comprising one or more instance identifiers associated with corresponding one or more set identifiers from the AMF unit, and wherein the set of data is stored by the NSSF unit in the slice database to process one or more slice information requests received from the AMF unit.
[0017] In an exemplary aspect of the present disclosure, the NSSF unit stores slice information for each of the one or more instance identifiers associated with the corresponding one or more set identifiers in the slice database.
[0018] In an exemplary aspect of the present disclosure, the one or more set identifiers are associated with the one or more PLMNs.
[0019] In an exemplary aspect of the present disclosure, the slice information comprises an information indicating a slice availability.

[0020] Another aspect of the present disclosure may relate to a system for providing slice information in a communication network. The system comprises an access and mobility management function (AMF) unit configured to transmit a slice information request related to a network slice associated with a public land mobile network (PLMN) in a multi-PLMN environment, wherein the slice information request comprises of an information related to one or more slices provisioned per tracking area code (TAC), an instance identifier and a set identifier. Further, the system comprises a network slice selection function (NSSF) unit. The NSSF unit is configured to receive the slice information request from the access and mobility management function (AMF) unit. Further, the NSSF unit is configured to query a slice database with the instance identifier and the set identifier. Further, the NSSF unit is configured to identify a slice information based on a mapping of the instance identifier and the set identifier in a set of data stored in the slice database. Further, the NSSF unit is configured to transmit the slice information to the AMF unit in response to the slice information request based on the mapping of the instance identifier and the set identifier in the set of data.
[0021] Yet another aspect of the present disclosure may relate to a user equipment (UE) for availing a service from a communication network. The UE comprises a transceiver unit configured to: (a) transmit to a communication network, a request to avail a service; and (b) receive a response to the request from the communication network. This response is generated by a system configured in the communication network based on: (1) receiving, at a network slice selection function (NSSF) unit of the system from an access and mobility management function (AMF) unit of the system, a slice information request related to a network slice associated with a public land mobile network (PLMN) in a multi-PLMN environment, wherein the slice information request comprises of an information related to one or more slices provisioned per tracking area code (TAC), an instance identifier and a set identifier; (2) querying, by the NSSF unit, a slice database with the instance identifier and the set identifier; (3) identifying, by the NSSF unit, a slice information based on a mapping of the instance identifier and the set identifier in a set of data stored in the slice database; and (4) transmitting, by the NSSF unit, the slice information to the AMF unit in response to the slice information request based on the mapping of the instance identifier and the set identifier in the set of data.

[0022] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for providing slice information in a communication network, the instructions include executable code which, when executed by a one or more units of a system, causes: an access and mobility management function (AMF) unit of the system to transmit a slice information request related to a network slice associated with a public land mobile network (PLMN) in a multi-PLMN environment, wherein the slice information request comprises of an information related to one or more slices provisioned per tracking area code (TAC), an instance identifier and a set identifier. The instructions further include executable code which, when executed causes a network slice selection function (NSSF) unit of the system to: (a) receive the slice information request from the access and mobility management function (AMF) unit, (b) query a slice database with the instance identifier and the set identifier, (c) identify a slice information based on a mapping of the instance identifier and the set identifier in a set of data stored in the slice database, and (d) transmit the slice information to the AMF unit in response to the slice information request based on the mapping of the instance identifier and the set identifier in the set of data.
OBJECTS OF THE DISCLOSURE
[0023] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0024] It is an object of the present disclosure to provide a system and a method for multi-PLMN support in same AMF instance with more than one AMF set-IDs.
[0025] It is another object of the present disclosure to provide a system and a method that enables better hosting and management of diverse AMF set IDs associated with different PLMNs.
[0026] It is another object of the present disclosure to provide a system and a method that reduces complexity and resource overhead required for maintaining multiple AMF set-IDs, resulting in providing a cost effective and time effective solution.

[0027] It is yet another object of the present disclosure to provide a system and a method that eliminates the need for deploying and managing separate AMF instances for each PLMN.
[0028] It is yet another object of the present disclosure to provide a system and a method that simplifies the overall network architecture by consolidating multiple PLMNs into a single AMF instance.
[0029] It is yet another object of the present disclosure to provide a system and a method that enables AMF to dynamically allocate network slices based on the availability of each PLMN.
[0030] It is yet another object of the present disclosure to provide a system and a method that enhances scalability by facilitating NSSF with the ability to support multiple PLMNs within a single AMF instance.
DESCRIPTION OF THE DRAWINGS
[0031] 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. Also, the embodiments shown in the figures are not to be construed as limiting the disclosure, but the possible variants of the method and system according to the disclosure are illustrated herein to highlight the advantages of the disclosure. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components or circuitry commonly used to implement such components.
[0032] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture.

[0033] FIG. 2 illustrates an exemplary block diagram of a computing device upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.
[0034] Fig. 3 illustrates an exemplary block diagram of a system for providing slice information in a communication network, in accordance with exemplary implementations of the present disclosure.
[0035] Fig. 4 illustrates a method flow diagram for providing slice information in a communication network in accordance with exemplary implementations of the present disclosure.
[0036] The foregoing shall be more apparent from the following more detailed description of the disclosure.
DETAILED DESCRIPTION
[0037] 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, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter may 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.
[0038] 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.

[0039] 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, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.
[0040] Also, it is noted that individual embodiments may be described as a process which 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 may 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.
[0041] 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—in a manner similar to the term “comprising” as an open transition word— without precluding any additional or other elements.
[0042] As used herein, a “processing unit” or “processor” or “operating processor” includes one or more processors, wherein processor refers to any logic circuitry for processing instructions. A 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 Signal 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 coding data 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 or processing unit is a hardware processor.
[0043] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and/or computing device or equipment, capable of implementing the features of the present disclosure. The user equipment/device may include, but is not limited to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable of implementing the features of the present disclosure. Also, the user device may contain at least one input means configured to receive an input from any such unit(s) which are required to implement the features of the present disclosure.
[0044] As used herein, “storage unit” or “memory unit” refers to a machine or computer-readable medium including any mechanism for storing information in a form readable by a computer or similar machine. For example, a computer-readable medium includes read¬only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices or other types of machine-accessible storage media. The storage unit stores at least the data that may be required by one or more units of the system to perform their respective functions.
[0045] As used herein “interface” or “user interface refers to a shared boundary across which two or more separate components of a system exchange information or data. The interface may also be referred to a set of rules or protocols that define communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.
[0046] All modules, units, components used herein, unless explicitly excluded herein, may be software modules or hardware processors, the processors being a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a

DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
[0047] As used herein the transceiver unit includes at least one receiver and at least one transmitter configured respectively for receiving and transmitting data, signals, information, or a combination thereof between units/components within the system and/or connected with the system.
[0048] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various components/units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.
[0049] As discussed in the background section, the current known solutions have several shortcomings. The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing method and system of providing slice information in a communication network for supporting multi-PLMN environments. Traditionally, each PLMN would require a separate AMF instance, resulting in increased complexity and resource overhead. The present disclosure provides that the same AMF instance, which caters to multiple AMF Set IDs to support multi-PLMN, hosts different PLMNs within a single AMF instance. As disclosed, this is done by handling different AMF sets in same AMF instance by maintaining map of set ID and AMF instance ID in slice database. This eliminates the need for deploying and managing separate AMF instances for each PLMN. Further, it simplifies the overall network architecture by consolidating multiple PLMNs into a single AMF instance, thereby reducing complexity, minimizing resource overhead, and streamlining network management by storing information of the same AMF instance mapped with different Set IDs, further optimizing

resource utilization. The ability of the NSSF to support multiple PLMNs within a single AMF instance also enhances scalability.
[0050] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.
[0051] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture, in accordance with exemplary implementation of the present disclosure. As shown in FIG. 1, the 5GC network architecture [100] includes a user equipment (UE) [102], a radio access network (RAN) [104], an access and mobility management function (AMF) [106], a Session Management Function (SMF) [108], a Service Communication Proxy (SCP) [110], an Authentication Server Function (AUSF) [112], a Network Slice Specific Authentication and Authorization Function (NSSAAF) [114], a Network Slice Selection Function (NSSF) [116], a Network Exposure Function (NEF) [118], a Network Repository Function (NRF) [120], a Policy Control Function (PCF) [122], a Unified Data Management (UDM) [124], an application function (AF) [126], a User Plane Function (UPF) [128], a data network (DN) [130], wherein all the components are assumed to be connected to each other in a manner as obvious to the person skilled in the art for implementing features of the present disclosure.
[0052] Radio Access Network (RAN) [104] is the part of a mobile telecommunications system that connects user equipment (UE) [102] to the core network (CN) and provides access to different types of networks (e.g., 5G network). It consists of radio base stations and the radio access technologies that enable wireless communication.
[0053] Access and Mobility Management Function (AMF) [106] is a 5G core network function responsible for managing access and mobility aspects, such as UE registration, connection, and reachability. It also handles mobility management procedures like handovers and paging.
[0054] Session Management Function (SMF) [108] is a 5G core network function responsible for managing session-related aspects, such as establishing, modifying, and

releasing sessions. It coordinates with the User Plane Function (UPF) for data forwarding and handles IP address allocation and QoS enforcement.
[0055] Service Communication Proxy (SCP) [110] is a network function in the 5G core
5 network that facilitates communication between other network functions by providing a
secure and efficient messaging service. It acts as a mediator for service-based interfaces.
[0056] Authentication Server Function (AUSF) [112] is a network function in the 5G core
responsible for authenticating UEs during registration and providing security services. It
10 generates and verifies authentication vectors and tokens.
[0057] Network Slice Specific Authentication and Authorization Function (NSSAAF)
[114] is a network function that provides authentication and authorization services specific
to network slices. It ensures that UEs can access only the slices for which they are
15 authorized.
[0058] Network Slice Selection Function (NSSF) [116] is a network function responsible for selecting the appropriate network slice for a UE based on factors such as subscription, requested services, and network policies. 20
[0059] Network Exposure Function (NEF) [118] is a network function that exposes capabilities and services of the 5G network to external applications, enabling integration with third-party services and applications.
25 [0060] Network Repository Function (NRF) [120] is a network function that acts as a
central repository for information about available network functions and services. It facilitates the discovery and dynamic registration of network functions.
[0061] Policy Control Function (PCF) [122] is a network function responsible for policy
30 control decisions, such as QoS, charging, and access control, based on subscriber
information and network policies.
15

[0062] Unified Data Management (UDM) [124] is a network function that centralizes the management of subscriber data, including authentication, authorization, and subscription information.
5 [0063] Application Function (AF) [126] is a network function that represents external
applications interfacing with the 5G core network to access network capabilities and services.
[0064] User Plane Function (UPF) [128] is a network function responsible for handling
10 user data traffic, including packet routing, forwarding, and QoS enforcement.
[0065] Data Network (DN) [130] refers to a network that provides data services to user equipment (UE) in a telecommunications system. The data services may include but are not limited to Internet services, private data network related services.
15
[0066] FIG. 2 illustrates an exemplary block diagram of a computing device [200] upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure. In an implementation, the computing device [200] may also implement a method for providing slice information in a
20 communication network utilising the system. In another implementation, the computing
device [200] itself implements the method for providing slice information in a communication network using one or more units configured within the computing device [200], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
25
[0067] The computing device [200] may include a bus [202] or other communication mechanism for communicating information, and a hardware processor [204] coupled with bus [202] for processing information. The hardware processor [204] may be, for example, a general-purpose microprocessor. The computing device [200] may also include a main
30 memory [206], such as a random-access memory (RAM), or other dynamic storage device,
coupled to the bus [202] for storing information and instructions to be executed by the processor [204]. The main memory [206] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by
16

the processor [204]. Such instructions, when stored in non-transitory storage media
accessible to the processor [204], render the computing device [200] into a special-purpose
machine that is customized to perform the operations specified in the instructions. The
computing device [200] further includes a read only memory (ROM) [208] or other static
5 storage device coupled to the bus [202] for storing static information and instructions for
the processor [204].
[0068] A storage device [210], such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus [202] for storing information and instructions. The
10 computing device [200] may be coupled via the bus [202] to a display [212], such as a
cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for displaying information to a computer user. An input device [214], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus [202] for communicating information and command
15 selections to the processor [204]. Another type of user input device may be a cursor
controller [216], such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor [204], and for controlling cursor movement on the display [212]. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device
20 to specify positions in a plane.
[0069] The computing device [200] may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computing device [200] causes or programs the
25 computing device [200] to be a special-purpose machine. According to one
implementation, the techniques herein are performed by the computing device [200] in response to the processor [204] executing one or more sequences of one or more instructions contained in the main memory [206]. Such instructions may be read into the main memory [206] from another storage medium, such as the storage device [210].
30 Execution of the sequences of instructions contained in the main memory [206] causes the
processor [204] to perform the process steps described herein. In alternative implementations of the present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions.
17

[0070] The computing device [200] also may include a communication interface [218]
coupled to the bus [202]. The communication interface [218] provides a two-way data
communication coupling to a network link [220] that is connected to a local network [222].
5 For example, the communication interface [218] may be an integrated services digital
network (ISDN) card, cable modem, satellite modem, or a modem to provide a data
communication connection to a corresponding type of telephone line. As another example,
the communication interface [218] may be a local area network (LAN) card to provide a
data communication connection to a compatible LAN. Wireless links may also be
10 implemented. In any such implementation, the communication interface [218] sends and
receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.
[0071] The computing device [200] can send messages and receive data, including
15 program code, through the network(s), the network link [220] and the communication
interface [218]. In the Internet example, a server [230] might transmit a requested code for
an application program through the Internet [228], the ISP [226], the local network [222],
the host [224], and the communication interface [218]. The received code may be executed
by the processor [204] as it is received, and/or stored in the storage device [210], or other
20 non-volatile storage for later execution.
[0072] Referring to FIG. 3, an exemplary block diagram of a system [300] for providing slice information in a communication network, is shown, in accordance with the exemplary implementations of the present disclosure. The system [300] comprises at least one access
25 and mobility management function (AMF) unit [302], at least a network slice selection
function (NSSF) unit [304], and at least one slice database [306]. Also, all of the components/ units of the system [300] are assumed to be connected to each other unless otherwise indicated below. As shown in the figures all units shown within the system should also be assumed to be connected to each other. Also, in Fig. 3 only a few units are
30 shown, however, the system [300] may comprise multiple such units or the system [300]
may comprise any such numbers of said units, as required to implement the features of the present disclosure. Further, the system [300] resides in a network entity.
18

[0073] The system [300] is configured for providing slice information in a communication network, with the help of the interconnection between the components/units of the system [300].
5 [0074] More specifically, the AMF unit [302] is configured to transmit a slice information
request related to a network slice associated with one or more public land mobile networks
(PLMNs). The slice information request comprises an information related to one or more
slices provisioned per tracking area code (TAC), an instance identifier and a set identifier,
wherein the instance identifier may be an AMF instance identifier, and the set identifier
10 may be an AMF set identifier. The slice information request may be a request for obtaining
a slice information of a network slice. This slice information may comprise an information indicating a slice availability.
[0075] The network slice selection function (NSSF) unit [304] is configured to receive the
15 slice information request from the access and mobility management function (AMF) unit
[302]. The slice information request is related to a network slice associated with one or more public land mobile networks (PLMNs). More particularly, the slice information request is received to identify a network slice for the PLMN(s) to enable the PLMN(s) for providing services to one or more user equipment (UEs). After receiving the request from
20 the AMF unit [302], the NSSF unit [304] is configured to query a slice database [306] with
the instance identifier and the set identifier. In an implementation, the instance identifier may be an AMF instance identifier (AMF instance ID), and the set identifier may be an AMF set identifier (AMF set ID). In an implementation, the one or more set identifiers are associated with the one or more PLMNs. Also, each of the one or more set identifiers
25 corresponds to one PLMN from the one or more PLMNs. It may be pertinent to mention
that as generally known in the art, an AMF may be identified by AMF ID, which is a string composed of AMF Region ID (8 bits), AMF Set ID (10 bits) and AMF Pointer (6 bits). The AMF ID is encoded as a string of 6 hexadecimal characters (i.e., 24 bits). Also, different set IDs may be associated with same AMF instance and are handled by
30 maintaining mapping of set-ID and AMF instance ID in slice database [306]. For this, the
AMF sends a combination of set IDs with same instance ID in multiple availability requests as per configuration of multi PLMNs.
19

[0076] Further, the NSSF unit [304] is configured to identify a slice information based on
a mapping of the instance identifier and the set identifier in a set of data stored in the slice
database [306], wherein the set of data is associated with slice information corresponding
to a data received from the AMF unit [302]. For this purpose, that is, for generating the set
5 of data, in an implementation, the NSSF unit [304] is configured to receive the data
comprising one or more instance identifiers associated with corresponding one or more set
identifiers from the AMF unit [302]. Also, in this implementation, the NSSF unit [304] is
configured to store the set of data in the slice database [306] to process one or more slice
information requests received from the AMF unit [302]. Therefore, in an implementation,
10 the AMF unit [302] sends at the NSSF unit [304], a combination of set IDs with same
instance ID in multiple availability requests as per configuration of multi PLMNs. These received set IDs and the instance ID are stored in a database, that is, the slice database [306].
15 [0077] In an implementation, every time an AMF unit [302] sends a data to the NSSF unit
[304], the data comprising the AMF instance ID and the set ID, the AMF instance ID along with the AMF set ID gets stored as a separate entry in the database [306]. The AMF instance ID for one AMF shall remain the same, however, the set ID received every time may be different. Also, each of these set IDs is associated with one PLMN. Pertinently,
20 maintaining separate entries of set IDs and instance IDs facilitates in keeping track of all
Set-IDs that the AMF unit [302] is a part of. This may further be used to calculate response of subsequent availability update request (i.e., slice information request) in multi-PLMN scenario by correlating separate entries of the set IDs and the instance IDs. An exemplary set of data reflecting maintenance of entries of set IDs and instance IDs in the slice database
25 is provided below in Table 1 for understanding purposes:
[0078] Table 1: Exemplary set of data reflecting maintenance of entries of set IDs and instance IDs

amfInstanceId amfSetId plmnId
"b8987f14-aaf8-43a2-b105-4263a15262b" "405-86-01-94" "{"mcc":"405","mnc":"866"}"
"b8987f14-aaf8-43a2-b105-4263a15262b" "405-85-01-103" "{"mcc":"405","mnc":"865"}"
20

[0079] For example, say at timestamp t1, the data sent from the AMF unit [302] to the NSSF unit [304] comprises NF_instance_id of the AMF unit [302] and set_id_1. Similarly, at timestamp t1 or t2, the data sent from the AMF unit [302] to the NSSF unit [304] comprises NF_instance_id of the AMF unit [302] and set_id_2. Both these information are stored at a database at the NSSF unit [304].
[0080] Also, after identifying the slice information, in an implementation, the NSSF unit [304] is further configured to store the slice information for each of the one or more instance identifiers associated with the corresponding one or more set identifiers in the slice database [306]. This slice information may comprise an information indicating a slice availability.
[0081] Further, the NSSF unit [304] is configured to transmit the slice information to the AMF unit [302] in response to the slice information request based on the mapping of the instance identifier and the set identifier in the set of data. Pertinently, here the mapping refers to a positive match of the instance identifier and set identifier respectively with at least one instance identifier from the one or more instance identifiers and at least one set identifier from the one or more set identifiers to identify the corresponding slice information.
[0082] In an implementation, the AMF unit [302] is further configured to dynamically allocate network resources (i.e., network slices) to one or more user equipment (UEs) in the one or more PLMNs. Pertinently, many network nodes such as access and mobility management function (AMF) node, session management function (SMF) node, user plane function (UPF) node, etc. are part of a network slice. The AMF may provide network slices authorized per TAC to UE after obtaining an indication from a network slice selection function (NSSF) node to complete 5G Registration of the UE. Also, this information may be used by the AMF node to further select the SMF node based on the slices for establishing a packet data unit (PDU) session for providing services. In an exemplary scenario the method comprises sending, by AMF unit [302], a request to provide a subscription resource in the NSSF unit [304], wherein the subscription resource may be a network slice for providing a subscription service to a user equipment, and wherein the request comprises

an information related to one or more slices provisioned per tracking area code (TAC), an AMF instance ID and an AMF set ID. Next, the method in this exemplary scenario comprises encompasses assessing, by the NSSF unit [304], the set ID received in the request to provide a slice information corresponding to the subscription resource from the database [306]. Next, the method in this exemplary scenario comprises sending, by the NSSF unit [304] to the AMF [302], a successful or unsuccessful response based on the assessment in the previous step. Since the database [306] has stored the mapping between the instance ID, the set IDs and the PLMN, a request to provide a subscription resource containing any set ID that has been stored is easily catered to. For example, if set id_1 and set id_2 both have been stored in the database [306], a subscription request for these set IDs shall be catered to. With this, the system [300] will be able to serve multiple PLMNs with single AMF instance and multiple set IDs.
[0083] Referring to FIG. 4, an exemplary method flow diagram [400] for providing slice information in a communication network, in accordance with exemplary implementations of the present disclosure is shown. In an implementation the method [400] is performed by the system [300]. Further, in an implementation, the system [300] may be present in a server device to implement the features of the present disclosure. Also, as shown in Figure 4, the method [400] starts at step [402].
[0084] At step 402, the method comprises receiving, at a network slice selection function (NSSF) unit [304] from an access and mobility management function (AMF) unit [302], a slice information request related to a network slice associated with one or more public land mobile networks (PLMNs), wherein the slice information request comprises of an information related to one or more slices provisioned per tracking area code (TAC), an instance identifier and a set identifier, and wherein the instance identifier may be an AMF instance identifier, and the set identifier may be an AMF set identifier. For this, the AMF unit [302] may transmit the slice information request. More particularly, the slice information request is received to identify a network slice for the PLMN(s) to enable the PLMN(s) for providing services to one or more user equipment (UEs). The slice information request may be a request for obtaining a slice information of a network slice. This slice information request may comprise a request pertaining to a slice availability.

Further, at step 404, the method comprises querying, by the NSSF unit [304], a slice database [306] with the instance identifier and the set identifier. In an implementation, the instance identifier may be an AMF instance identifier (AMF instance ID), and the set identifier may be an AMF set identifier (AMF set ID). In an implementation, the one or more set identifiers are associated with the one or more PLMNs. Also, each of the one or more set identifiers corresponds to one PLMN from the one or more PLMNs. Also, different set IDs may be associated with same AMF instance and are handled by maintaining mapping of set-ID and AMF instance ID in slice database [306]. For this, the AMF sends a combination of set IDs with same instance ID in multiple availability requests as per configuration of multi PLMNs.
[0085] Further, at step 406, the method comprises identifying, by the NSSF unit [304], a slice information based on a mapping of the instance identifier and the set identifier in a set of data stored in the slice database [306], wherein the set of data is associated with slice information corresponding to a data received from the AMF unit [302]. For this purpose, that is, for generating the set of data, in an implementation, the NSSF unit [304] may receive the data comprising one or more instance identifiers associated with corresponding one or more set identifiers from the AMF unit [302]. Also, in this implementation, the NSSF unit [304] may store the set of data in the slice database [306] to process one or more slice information requests received from the AMF unit [302]. Therefore, in an implementation, the AMF unit [302] sends at the NSSF unit [304], a combination of set IDs with same instance ID in multiple availability requests as per configuration of multi PLMNs. These received set IDs and the instance ID are stored in a database, that is, the slice database [306].
[0086] In an implementation, every time an AMF unit [302] sends a data to the NSSF unit [304], the data comprising the AMF instance ID and the set ID, the AMF instance ID along with the AMF set ID gets stored as a separate entry in the database [306]. The AMF instance ID for one AMF shall remain the same, however, the set ID received every time may be different. Also, each of these set IDs is associated with one PLMN. Pertinently, maintaining separate entries of set IDs and instance IDs facilitates in keeping track of all Set-IDs that the AMF is a part of. This may further be used to calculate response of

subsequent availability update request in multi-PLMN scenario by correlating separate entries of the set IDs and the instance IDs. An exemplary set of data reflecting maintenance of entries of set IDs and instance IDs is provided above in Table 1 for understanding purposes.
[0087] For example, say at timestamp t1, the data sent from the AMF unit [302] to the NSSF unit [304] comprises NF_instance_id of the AMF unit [302] and set_id_1. Similarly, at timestamp t1 or t2, the data sent from the AMF unit [302] to the NSSF unit [304] comprises NF_instance_id of the AMF unit [302] and set_id_2. Both these information are stored at a database at the NSSF unit [304].
[0088] Also, after identification of the slice information, in an implementation, the NSSF unit [304] may store the slice information for each of the one or more instance identifiers associated with the corresponding one or more set identifiers in the slice database [306]. This slice information may comprise an information indicating a slice availability.
[0089] Further, at step 408, the method comprises transmitting, by the NSSF unit [304], the slice information to the AMF unit [302] in response to the slice information request based on a mapping of the instance identifier and the set identifier in the set of data. Pertinently, here the mapping refers to a positive match of the instance identifier and set identifier respectively with at least one instance identifier from the one or more instance identifiers and at least one set identifier from the one or more set identifiers to identify the corresponding slice information.
[0090] In an implementation, the AMF unit [302] may dynamically allocate network resources (i.e., network slices) to one or more user equipment (UEs) in the one or more PLMNs. Pertinently, many network nodes such as access and mobility management function (AMF) node, session management function (SMF) node, user plane function (UPF) node, etc. are part of a network slice. The AMF may provide network slices authorized per TAC to UE after obtaining an indication from a network slice selection function (NSSF) node to complete 5G Registration of the UE. Also, this information may

be used by the AMF node to further select the SMF node based on the slices for establishing a packet data unit (PDU) session for providing services.
[0091] Moreover, the present disclosure further discloses a user equipment (UE) for availing a service from a communication network. The UE comprises a transceiver unit configured to: (a) transmit to a communication network, a request to avail a service; and (b) receive a response to the request from the communication network. This response is generated by a system [300] configured in the communication network based on: (1) receiving, at a network slice selection function (NSSF) unit [304] of the system [300] from an access and mobility management function (AMF) unit [302] of the system [300], a slice information request related to a network slice associated with one or more public land mobile networks (PLMNs), wherein the slice information request comprises of an information related to one or more slices provisioned per tracking area code (TAC), an instance identifier and a set identifier; (2) querying, by the NSSF unit [304], a slice database [306] with the instance identifier and the set identifier; (3) identifying, by the NSSF unit [304], a slice information based on a mapping of the instance identifier and the set identifier in a set of data stored in the slice database [306]; and (4) transmitting, by the NSSF unit [304], the slice information to the AMF unit [302] in response to the slice information request based on the mapping of the instance identifier and the set identifier in the set of data.
[0092] The present disclosure further discloses a non-transitory computer readable storage medium storing instructions for providing slice information in a communication network, the instructions include executable code which, when executed by a one or more units of a system, causes: an access and mobility management function (AMF) unit [302] of the system to transmit a slice information request related to a network slice associated with one or more public land mobile networks (PLMNs), wherein the slice information request comprises of an information related to one or more slices provisioned per tracking area code (TAC), an instance identifier and a set identifier. The instructions further include executable code which, when executed causes a network slice selection function (NSSF) unit [304] of the system to: (a) receive the slice information request from the access and mobility management function (AMF) unit, (b) query a slice database [306] with the instance identifier and the set identifier, (c) identify a slice information based on a mapping

of the instance identifier and the set identifier in a set of data stored in the slice database [306], and (d) transmit the slice information to the AMF unit [302] in response to the slice information request based on the mapping of the instance identifier and the set identifier in the set of data.
[0093] As is evident from the above, the present disclosure provides a technically advanced solution for providing slice information in a communication network. The present solution facilitates a multi-PLMN support in same AMF instance with more than one AMF set-IDs. Further, the present solution enables better hosting and management of diverse AMF set IDs associated with different PLMNs. Further, the present solution reduces complexity and resource overhead required for maintaining multiple AMF set-IDs, resulting in providing a cost effective and time effective solution. Further, the present solution eliminates the need for deploying and managing separate AMF instances for each PLMN. Further, the present solution simplifies the overall network architecture by consolidating multiple PLMNs into a single AMF instance. Further, the present solution enables AMF to dynamically allocate network slices based on the availability document of each PLMN. Further, the present solution enhances scalability by facilitating NSSF with the ability to support multiple PLMNs within a single AMF instance.
[0094] While considerable emphasis has been placed herein on the disclosed implementations, it will be appreciated that many implementations can be made and that many changes can be made to the implementations without departing from the principles of the present disclosure. These and other changes in the implementations of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.

We Claim:
1. A method for providing slice information in a communication network, the method
comprising:
- receiving, at a network slice selection function (NSSF) unit [304] from an access and mobility management function (AMF) unit [302], a slice information request related to a network slice associated with a public land mobile network (PLMN) in a multi-PLMN environment, wherein the slice information request comprises of an information related to one or more slices provisioned per tracking area code (TAC), an instance identifier and a set identifier;
- querying, by the NSSF unit [304], a slice database [306] with the instance identifier and the set identifier;
- identifying, by the NSSF unit [304], a slice information based on a mapping of the instance identifier and the set identifier in a set of data stored in the slice database [306]; and
- transmitting, by the NSSF unit [304], the slice information to the AMF unit [302] in response to the slice information request based on the mapping of the instance identifier and the set identifier in the set of data.

2. The method as claimed in claim 1, the method further comprising dynamically allocating, by the AMF unit [302], network resources to one or more user equipment (UEs) in the PLMN in the multi-PLMN environment based on the slice information.
3. The method as claimed in claim 1, wherein the set of data is generated based on:
- receiving, at the NSSF unit [304], a data comprising one or more instance
identifiers associated with corresponding one or more set identifiers from the
AMF unit [302], and wherein the set of data is stored by the NSSF unit [304]
in the slice database [306] to process one or more slice information requests
received from the AMF unit [302].

4. The method as claimed in claim 3, wherein the NSSF unit [304] stores slice information for each of the one or more instance identifiers associated with the corresponding one or more set identifiers in the slice database [306].
5. The method as claimed in claim 3, wherein the one or more set identifiers are associated with one or more PLMNs in the multi-PLMN environment.
6. The method as claimed in claim 1, wherein the slice information comprises an information indicating a slice availability.
7. A system for providing slice information in a communication network, the system comprising:

- an access and mobility management function (AMF) unit [302] configured to transmit a slice information request related to a network slice associated with a public land mobile network (PLMN) in a multi-PLMN environment, wherein the slice information request comprises of an information related to one or more slices provisioned per tracking area code (TAC), an instance identifier and a set identifier; and
- a network slice selection function (NSSF) unit [304] configured to:
o receive the slice information request from the access and mobility
management function (AMF) unit [302], o query a slice database [306] with the instance identifier and the set
identifier, o identify a slice information based on a mapping of the instance identifier
and the set identifier in a set of data stored in the slice database [306],
and o transmit the slice information to the AMF unit [302] in response to the
slice information request based on the mapping of the instance identifier
and the set identifier in the set of data.
8. The system as claimed in claim 7, wherein the AMF unit [302] is further configured
to dynamically allocate network resources to one or more user equipment (UEs) in
the PLMN in the multi-PLMN environment based on the slice information.

9. The system as claimed in claim 7, wherein the set of data is generated based on:
- receiving, at the NSSF unit [304], a data comprising one or more instance
identifiers associated with corresponding one or more set identifiers from the
AMF unit [302], and wherein the set of data is stored by the NSSF unit [304]
in the slice database [306] to process one or more slice information requests
received from the AMF unit [302].
10. The system as claimed in claim 9, wherein the NSSF unit [304] is further configured to store slice information for each of the one or more instance identifiers associated with the corresponding one or more set identifiers in the slice database [306].
11. The system as claimed in claim 9, wherein the one or more set identifiers are associated with one or more PLMNs in the multi-PLMN environment.
12. The system as claimed in claim 7, wherein the slice information comprises an information indicating a slice availability.
13. A user equipment (UE) for availing a service from a communication network, the UE comprising:
- a transceiver unit configured to:
o transmit to a communication network, a request to avail a service; and o receive a response to the request from the communication network, wherein the response is generated by a system [300] configured in the communication network based on:
▪ receiving, at a network slice selection function (NSSF) unit [304] of the system [300] from an access and mobility management function (AMF) unit [302] of the system [300], a slice information request related to a network slice associated with one or more public land mobile networks (PLMNs), wherein the slice information request comprises of an information related to one or more slices provisioned per

tracking area code (TAC), an instance identifier and a set
identifier; ▪ querying, by the NSSF unit [304], a slice database [306] with
the instance identifier and the set identifier; ▪ identifying, by the NSSF unit [304], a slice information based
on a mapping of the instance identifier and the set identifier in a
set of data stored in the slice database [306]; and ▪ transmitting, by the NSSF unit [304], the slice information to
the AMF unit [302] in response to the slice information request
based on the mapping of the instance identifier and the set
identifier in the set of data.