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 RECEIVING TARGET SLICE AUTHORISATION DATA AT AMF FROM NSSF”
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 RECEIVING TARGET SLICE AUTHORISATION DATA AT AMF FROM NSSF
TECHNICAL FIELD
[0001] Embodiments of the present disclosure generally relate to network performance management systems. More particularly, embodiments of the present disclosure relate to method and system for receiving a target slice authorisation data at an Access and Mobility Management Function (AMF) from a Network Slicing Selection Function (NSSF) in a network.
BACKGROUND
[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] The current network standard presents a challenge where obtaining slice authorisation aligns with gNodeB (gNB) provisioning slice support per tracking area identifier (TAI). As used herein, TAI refers to a unique identifier assigned to a specific geographic region within a mobile network, which is used to manage and track the location of user equipment (UE) as it moves across different areas. The TAI helps the network efficiently handle mobility management, ensuring that the UE stays connected and receives services while roaming within various tracking areas of the network. Unfortunately, this approach introduces significant delays in NG (Next Generation) setup and imposes additional burdens. The requirement to continually request and authorize slice availability data from NSSF during each NG setup or RAN configuration update results in prolonged setup times and

unnecessary overhead. This issue is compounded when considering scenarios with a large number of gNBs, as each individual NG setup involving AMF necessitates a separate interaction with NSSF for slice availability data authorisation. This not only hampers efficiency but also raises concerns about scalability and resource allocation within the network infrastructure.
[0004] Thus, there exists an imperative need in the art to receive a target slice authorisation data at an Access and Mobility Management Function (AMF) from a Network Slicing Selection Function (NSSF) in a network, which the present disclosure aims to address.
SUMMARY
[0005] 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.
[0006] An aspect of the present disclosure may relate to a method for receiving a target slice authorisation data at an Access and Mobility Management Function (AMF) from a Network Slicing Selection Function (NSSF) in a network. The method includes transmitting, by a transceiver unit, a slice availability authorisation request, from the AMF to the NSSF. The method further includes fetching, by the transceiver unit, a set of slice authorisation data based on the slice availability authorisation request, from the NSSF, wherein the set of slice authorisation data is associated with one or more tracking areas associated with the network. The method further includes configuring, by a processing unit, the set of slice authorisation data at the AMF. The method further includes receiving, by the transceiver unit, a target tracking area slice availability authorisation request associated with one of the one or more tracking areas, at the AMF. The method includes identifying, by the processing unit, a target slice authorisation data from the set of slice authorisation

data based on the target tracking area slice availability authorisation request. The method includes receiving, by the transceiver unit, the identified target slice authorisation data from the NSSF, at the AMF.
[0007] In an exemplary aspect of the present disclosure, the slice availability authorisation request is transmitted from the AMF to the NSSF in an event an AMF commission event associated with the AMF is detected.
[0008] In an exemplary aspect of the present disclosure, the slice availability authorisation request is associated with a set of tracking area identifiers (TAIs) of one of the one or more tracking areas of the network.
[0009] In an exemplary aspect of the present disclosure, the configuring further comprises storing, by the processing unit, the set of slice authorisation data in a local database at the AMF.
[0010] In an exemplary aspect of the present disclosure, the configuring further comprises organizing, by the processing unit, the set of slice authorisation data according to the set of TAIs and a set of network slice identifiers associated with the set of slice authorisation data.
[0011] In an exemplary aspect of the present disclosure, the identifying further comprises comparing, by a comparing unit, a target TAI with the set of TAIs stored at the AMF, wherein the target TAI is associated with the target tracking area slice availability request to select the target slice authorisation data.
[0012] Another aspect of the present disclosure may relate to a system for receiving a target slice authorisation data at an Access and Mobility Management Function (AMF) from a Network Slicing Selection Function (NSSF) in a network. The system comprises a transceiver unit. The transceiver unit is configured to transmit, a slice availability authorisation request, from the AMF to the NSSF. The

transceiver unit is further configured to fetch, a set of slice authorisation data based on the slice availability authorisation request, from the NSSF, wherein the set of slice authorisation data is associated with one or more tracking areas associated with the network. The system further comprises a processing unit connected to the transceiver unit. The processing unit is configured to configure, the set of slice authorisation data, at the AMF. The transceiver unit is further configured to receive, a target tracking area slice availability authorisation request associated with one of the one or more tracking areas of the network, at the AMF. The processing unit is further configured to identify, a target slice authorisation data from the set of slice authorisation data based on the target tracking area slice availability authorisation request. The transceiver unit is further configured to receive the identified target slice authorisation data from the NSSF at the AMF.
[0013] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for receiving a target slice authorisation data at an Access and Mobility Management Function (AMF) from a Network Slicing Selection Function (NSSF) in a network, the instructions include executable code which, when executed by one or more units of a system, causes: a transceiver unit to transmit, a slice availability authorisation request, from the AMF to the NSSF. The instructions when executed further causes the transceiver unit to fetch, a set of slice authorisation data based on the slice availability authorisation request, from the NSSF, wherein the set of slice authorisation data is associated with one or more tracking areas associated with the network. The instructions when executed further causes a processing unit to configure, the set of slice authorisation data, at the AMF. The instructions when executed further causes the transceiver unit to receive, a target tracking area slice availability authorisation request associated with one of the one or more tracking areas of the network, at the AMF. The instructions when executed further causes the processing unit to identify, a target slice authorisation data from the set of slice authorisation data based on the target tracking area slice availability authorisation request. The instructions when

executed further causes the transceiver unit to receive the identified target slice authorisation data from the NSSF at the AMF.
OBJECTS OF THE INVENTION
[0014] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0015] It is an object of the present disclosure to provide a system and a method for providing directly by an AMF a target slice authorisation data.
[0016] It is yet another object of the present disclosure to provide a solution that automatically fetches a set of slice authorisation data based on the slice availability authorisation request and stores the set of slice authorisation data at the AMF.
[0017] It is yet another object of the present disclosure to provide a solution that receives a target tracking area slice availability authorisation request associated with the tracking area of the network and identifies, at the AMF itself, target slice authorisation data from the set of slice authorisation data based on the target tracking area slice availability authorisation request.
DESCRIPTION OF THE DRAWINGS
[0018] 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.
[0019] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture.
[0020] 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.
[0021] FIG. 3 illustrates an exemplary block diagram of a system for receiving a target slice authorisation data at an Access and Mobility Management Function (AMF) from a Network Slicing Selection Function (NSSF) in a network, in accordance with exemplary implementations of the present disclosure.
[0022] FIG. 4 illustrates a method flow diagram for receiving a target slice authorisation data at an Access and Mobility Management Function (AMF) from a Network Slicing Selection Function (NSSF) in a network in accordance with exemplary implementations of the present disclosure.
[0023] FIG. 5 illustrates a process flow diagram for receiving a target slice authorisation data at an Access and Mobility Management Function (AMF) from a Network Slicing Selection Function (NSSF) in a network in accordance with exemplary implementations of the present disclosure.
[0024] The foregoing shall be more apparent from the following more detailed description of the disclosure.
DETAILED DESCRIPTION

[0025] 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.
[0026] 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.
[0027] 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 skills 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.
[0028] 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.

[0029] 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.
[0030] 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.
[0031] 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 at least one of a transceiver unit, a processing unit, a storage unit, a detection unit and any other such unit(s) which are required to implement the features of the present disclosure.
[0032] 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.
[0033] 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.
[0034] 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.

[0035] As used herein the transceiver unit include 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.
[0036] 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 for receiving a target slice authorisation data at an Access and Mobility Management Function (AMF) from a Network Slicing Selection Function (NSSF) in a network.
[0037] As used herein, a target slice authorisation data refers to the detailed information about which network slices are authorized and available for use in a specific tracking area. This data helps the AMF efficiently manage network resources and ensure that users in different areas have access to the correct network slices based on their needs and network policies.
[0038] As used herein, tracking areas are geographical areas that are used for tracking and managing the location of mobile devices. The concept of tracking areas facilitates in optimising the mobility management and handover processes in 5G networks.
[0039] As used herein, AMF commission event refers to a specific event or trigger that marks the initiation or commissioning of the AMF in the network. It means AMF has completed its setup and is now ready to participate in managing network functions.
[0040] As used herein, tracking area identifiers refers to a unique identifier within the network to track and manage mobile devices as they move around. In LTE and

5G networks, the coverage area is divided into smaller geographical regions called Tracking Areas (TAs).
[0041] 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 Authorisation 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.
[0042] 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.
[0043] 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.
[0044] 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.
[0045] Service Communication Proxy (SCP) [110] is a network function in the 5G core 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.
[0046] Authentication Server Function (AUSF) [112] is a network function in the 5G core responsible for authenticating UEs during registration and providing security services. It generates and verifies authentication vectors and tokens.
[0047] Network Slice Specific Authentication and Authorisation Function (NSSAAF) [114] is a network function that provides authentication and authorisation services specific to network slices. It ensures that UEs can access only the network slices for which they are authorized.
[0048] 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.
[0049] 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.
[0050] 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.

[0051] Policy Control Function (PCF) [122] is a network function responsible for policy control decisions, such as QoS, charging, and access control, based on subscriber information and network policies.
[0052] Unified Data Management (UDM) [124] is a network function that centralizes the management of subscriber data, including authentication, authorisation, and subscription information.
[0053] Application Function (AF) [126] is a network function that represents external applications interfacing with the 5G core network to access network capabilities and services.
[0054] User Plane Function (UPF) [128] is a network function responsible for handling user data traffic, including packet routing, forwarding, and QoS enforcement.
[0055] 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.
[0056] FIG. 2 illustrates an exemplary block diagram of a computing device [200] (also referred to herein as computer system [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 receiving a target slice authorisation data at an Access and Mobility Management Function (AMF) from a Network Slicing Selection Function (NSSF) in a network utilising the system. In another implementation, the computing device [200] itself implements the method for receiving a target slice authorisation data at an Access and Mobility Management Function (AMF) from a Network Slicing Selection Function (NSSF) in a 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.
[0057] The computing device [200] may include a bus [202] or other
5 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 memory [206], such as a random-
access memory (RAM), or other dynamic storage device, coupled to the bus [202]
10 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 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-
15 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 storage device coupled to the bus [202] for storing static
information and instructions for the processor [204].
20 [0058] 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 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
25 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 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
30 information and command selections to the processor [204], and for controlling
cursor movement on the display [212]. This input device typically has two degrees
15

of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.
[0059] The computing device [200] may implement the techniques described
5 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 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
10 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]. 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
15 disclosure, hard-wired circuitry may be used in place of or in combination with
software instructions.
[0060] The computing device [200] also may include a communication interface
[218] coupled to the bus [202]. The communication interface [218] provides a two-
20 way data communication coupling to a network link [220] that is connected to a
local network [222]. 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
25 local area network (LAN) card to provide a data communication connection to a
compatible LAN. Wireless links may also be 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.
30
16

[0061] The computing device [200] can send messages and receive data, including
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
5 ISP [226], the local network [222], 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 non-volatile storage for later execution.
10 [0062] The computing device [200] encompasses a wide range of electronic
devices capable of processing data and performing computations. Examples of computing device [200] include, but are not limited only to, personal computers, laptops, tablets, smartphones, servers, and embedded systems. The devices may operate independently or as part of a network and can perform a variety of tasks
15 such as data storage, retrieval, and analysis. Additionally, computing device [200]
may include peripheral devices, such as monitors, keyboards, and printers, as well as integrated components within larger electronic systems, highlighting their versatility in various technological applications.
20 [0063] Referring to FIG. 3, an exemplary block diagram of a system [300] for
receiving a target slice authorisation data at an Access and Mobility Management Function (AMF) from a Network Slicing Selection Function (NSSF) in a network, is shown, in accordance with the exemplary implementations of the present disclosure. The system [300] comprises at least one transceiver unit [302], at least
25 processing unit [304], and at least one comparing unit [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 shown, however, the system [300] may comprise multiple such
30 units or the system [300] may comprise any such numbers of said units, as required
to implement the features of the present disclosure. Further, in an implementation,
17

the system [300] may be present in a user device to implement the features of the
present disclosure. The system [300] may be a part of the user device / or may be
independent of but in communication with the user device (may also referred herein
as a UE). In another implementation, the system [300] may reside in a server or a
5 network entity. In yet another implementation, the system [300] may reside partly
in the server/ network entity and partly in the user device.
[0064] The system [300] is configured for receiving a target slice authorisation data at an Access and Mobility Management Function (AMF) from a Network Slicing
10 Selection Function (NSSF) in a network, with the help of the interconnection
between the components/units of the system [300]. The set of slice authorisation data refers to a detailed information about the network slices authorized for different tracking areas within a 5G network. For example, in a network with three distinct tracking areas—an urban area (Tracking Area 1), a rural area (Tracking Area 2),
15 and an industrial zone (Tracking Area 3)—the set of slice authorisation data would
specify the slice identifiers (S-NSSAI) and their associated service types for each area. As used herein, Single Network Slice Selection Assistance Information (S-NSSAI) refers to a key identifier used in 5G networks to represent a specific network slice. It consists of a Slice/Service Type (SST), which defines the type of
20 service the slice offers (e.g., enhanced mobile broadband), and an optional Slice
Differentiator (SD), which distinguishes between different slices of the same service type. In Tracking Area 1, the authorized network slices might include enhanced mobile broadband (eMBB) services and ultra-reliable low-latency communication (URLLC) services, each with high priority and latency
25 requirements to meet the demands of high-data, low-latency urban environments.
In contrast, Tracking Area 2, focused on energy-efficient communication, might authorize network slices for massive machine-type communications (mMTC) services with lower priority and standard mobile broadband with medium priority. Further, Tracking Area 3, serving an industrial zone, might have network slices
30 dedicated to ultra-low latency communication and Industrial IoT, both of which are
crucial for automation and fast, reliable communication in industrial applications.
18

[0065] The system [300] comprises a transceiver unit [302] configured to transmit,
a slice availability authorisation request, from the AMF [106] to the NSSF [116].
The transceiver unit [302] facilitates in establishing a communication link between
5 the AMF [106] and the NSSF [116] to enable the exchange of slice availability data.
The slice availability authorisation request is initiated whenever the AMF [106] requires authorisation for network slices associated with tracking areas in the 5G network. When the AMF [106] is initially commissioned or upon its startup, it triggers the transceiver unit [302] to send the slice availability authorisation request.
10 The slice availability authorisation request enables the AMF [106] to fetch a set of
slice authorisation data. The slice authorisation data retrieved from the NSSF [116] is associated with one or more tracking areas in the network to enable the AMF [106] to manage network slice configuration for gNBs operating within those areas. For example, an AMF [106] manages multiple gNBs across various tracking areas.
15 As each gNB performs NG Setup procedures, the AMF [106] facilitates that the
correct slice availability data is authorized for the specific tracking area associated with the gNB. In this case, the transceiver unit [302] sends the slice availability authorisation request to the NSSF [116], and in response, the AMF [106] receives the required authorisation data. This data may then be stored locally at the AMF
20 [106] and used to respond to future NG Setup requests without the need to query
the NSSF [116] repeatedly.
[0066] The slice availability authorisation request is sent from the AMF [106] to the NSSF [116] within a 5G network. The slice availability authorisation request is
25 used to obtain authorisation and availability information for network slices that are
applicable to tracking areas (such as geographical regions) associated with the AMF [106]. Network slices refers to isolated partitions of network resources configured to handle different types of services, such as but not limited only to enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), or
30 massive machine-type communications (mMTC). When the AMF [106] needs to
allocate network slices for gNBs or user devices within the tracking area, it sends a
19

slice availability authorisation request to the NSSF [116]. The slice availability
authorisation request includes the tracking area identifiers (TAIs) for which the
slice information is being sought. In response, the NSSF [116] provides the AMF
[106] with the relevant slice authorisation data, providing details regarding which
5 network slices are available and authorized for use in those tracking areas. For
example, if the AMF [106] manages a tracking area that is heavily focused on
supporting IoT devices, it may send a slice availability authorisation request to the
NSSF [116] to obtain information on the network slices that are optimized for IoT
services. Once the NSSF [116] responds with the appropriate data, the AMF [106]
10 can allocate resources accordingly, such that the devices in that area are connected
to the correct network slices.
[0067] In an exemplary aspect, the slice availability authorisation request may also
include such as but not limited only to an AMF identifier to identify the AMF [106]
15 making the request, a slice selection criterion that may further include network slice
instance identifier which is specific identifier for the network slice being requested.
[0068] In an exemplary aspect, the slice availability authorisation request is transmitted from the AMF [106] to the NSSF [116] the AMF commission event
20 which refers to a situation where the AMF [106] is being set up or initialized within
the network. This event marks a situation where the AMF [106] gets activated to manage network functions and resources. In an exemplary aspect, when the AMF [106] is being set up and starts operating in a particular network area, this event is triggered.
25
[0069] The transceiver unit [302] is further configured to fetch, a set of slice authorisation data based on the slice availability authorisation request, from the NSSF [116], wherein the set of slice authorisation data is associated with one or more tracking areas associated with the network.
30
20

[0070] The transceiver unit [302] is further configured to fetch a set of slice
authorisation data based on the slice availability authorisation request from the
Network Slice Selection Function (NSSF) [116], wherein the set of slice
authorisation data is associated with one or more tracking areas associated with the
5 network. The fetching operation is initiated after the transceiver unit [302] transmits
the slice availability authorisation request to the NSSF [116]. Once the slice availability authorisation request is processed by the NSSF [116], it responds with the slice authorisation data, which includes information about the network slices that are available within the tracking areas. For example, in a 5G network
10 deployment, the network is divided into multiple tracking areas, each of which may
support different network slices based on the requirements of the users and services in that area. The AMF [106], which manages mobility and connection services, needs information of network slices that are authorized for use in each tracking area. The transceiver unit [302] fetches the slice authorisation data from the NSSF [116]
15 such that the AMF [106] has up-to-date information of the network slices that are
authorized within each tracking area. In an example, a new gNB is added to a specific tracking area. During the NG Setup process, the AMF [106] must determine which network slices are authorized for use by this gNB. The transceiver unit [302] sends a slice availability authorisation request to the NSSF [116],
20 specifying the tracking area of the new gNB. The NSSF [116] responds with the
slice authorisation data for that tracking area, which the transceiver unit [302] fetches and forwards to the AMF [106]. The AMF [106] can then use this data to configure the gNB accordingly such that the correct network slices are utilized for the services in that area.
25
[0071] The set of slice authorisation data fetched by the transceiver unit [302] may include information such as but not limited only to Single Network Slice Selection Assistance Information (S-NSSAI), associated TAIs, and a set of policies associated with the network slices. The set of policies corresponds to protocols or
30 rules associated with the network slices.
21

[0072] In an exemplary embodiment, the slice authorisation data may need to be
updated as the network evolves. For example, if additional network slices are
introduced or if the coverage area of an existing network slices are expanded to
include new tracking areas, the transceiver unit [302] can fetch the updated slice
5 authorisation data from the NSSF [116] upon receiving a new slice availability
authorisation request.
[0073] The system [300] further comprises a processing unit [304] connected to the transceiver unit [302]. The processing unit [304] is configured to configure, the set
10 of slice authorisation data, at the AMF [106]. Once the transceiver unit [302] fetches
the slice authorisation data from the NSSF [116], the processing unit [304] organizes and stores the set of slice authorisation data in a structured manner within the AMF [106]. For example, the AMF [106] receives slice authorisation data that includes multiple slice identifiers such as S-NSSAI associated with different
15 tracking areas (TAIs) in the network. The processing unit [304] categorizes and
stores this data based on the corresponding TAIs.
[0074] In an exemplary aspect, the processing unit [304] configures the set of slice authorisation data by storing the slice authorisation data in a local database or
20 memory structure within the AMF [106]. For example, if a gNB requests
connection within a specific tracking area, the processing unit [304] retrieves the relevant slice data from the local storage and uses it to configure the gNB accordingly. It would be appreciated by the person skilled in the art that the local configuration avoids the need for repeated queries to the NSSF [116], significantly
25 reducing setup times and improving the overall efficiency of the network.
[0075] The transceiver unit [302] is further configured to receive a target tracking
area slice availability authorisation request associated with one of the one or more
tracking areas of the network, at the AMF [106]. The target tracking area slice
30 availability authorization request refers to a request sent by a gNB or user device to
the AMF [106] within a 5G network, requesting for authorization and availability
22

information for network slices in a particular tracking area. The request includes a
Tracking Area Identifier (TAI), which uniquely identifies the geographic region
where the gNB or device is located. The AMF [106], upon receiving this request,
needs to determine which network slices are authorized and available for use in that
5 specific tracking area. Therefore, the network can allocate the appropriate network
slices that align with the service requirements, such as enhanced mobile broadband
(eMBB) or ultra-reliable low-latency communication (URLLC), based on the
specific needs of the devices in that region. The target tracking area slice availability
authorization request is crucial for enabling dynamic and localized network
10 resource management in a 5G environment.
[0076] For example, in a 5G network, different tracking areas (TAs) may support different types of services through network slicing. A tracking area may have network slices optimized for high-speed internet, low-latency applications, or
15 massive IoT connectivity, depending on the services required in that region. When
a gNB located in one of the tracking areas requests a connection, the AMF [106] determines which network slices are authorized for that specific area. The transceiver unit [302] receives the request, which specifies the tracking area where the gNB is located and uses this information to handle the slice authorisation
20 process accordingly.
[0077] For example, a gNB is deployed in Tracking Area 2, which is configured to support low-latency services for real-time applications such as augmented reality (AR) or online gaming. When the gNB in Tracking Area 2 initiates a connection
25 setup, the transceiver unit [302] receives the target tracking area slice availability
authorisation request. The request is specific to Tracking Area 2, and it informs the AMF [106] that slice availability needs to be verified and authorized for this area. Based on this request, the AMF [106] can either retrieve the necessary slice authorisation data from its local database or, if required, fetch updated slice data
30 from the NSSF [116].
23

[0078] The processing unit [304] is further configured to identify a target slice
authorisation data from the set of slice authorisation data based on the target
tracking area slice availability authorisation request. For example, when a gNB
located in a tracking area sends a request to the AMF [106], the transceiver unit
5 [302] first receives this request. The processing unit [304] then analyses the target
tracking area slice availability authorisation request to determine which network
slices are authorized for use in that tracking area. The set of slice authorisation data,
which has been previously stored and organized within the AMF [106], includes
information about all the network slices authorized across various tracking areas in
10 the network. The processing unit [304] uses the tracking area identifier (TAI)
provided in the request to locate and extract the slice authorisation data from the set of slice authorisation data.
[0079] For example, a gNB located in Tracking Area 3, which is part of a 5G
15 network that supports multiple services, such as enhanced mobile broadband
(eMBB) and ultra-reliable low-latency communications (URLLC). When the gNB
in Tracking Area 3 sends a connection request, the AMF [106] identifies which
network slices are available and authorized in that area. The processing unit [304]
examines the request, identifies that it pertains to Tracking Area 3, and retrieves the
20 specific slice authorisation data corresponding to this area. This data might include
slice identifiers for both eMBB and URLLC, such that the gNB can be configured to use the appropriate slice for the service it needs to provide.
[0080] The transceiver unit [302] is further configured to receive the identified
25 target slice authorisation data from the NSSF [116] at the AMF [106]. The AMF
[106] obtains the target slice authorisation data directly from the NSSF [116] in
response to a target tracking area slice availability authorisation request. Once the
processing unit [304] identifies which slice authorisation data is required for a
particular tracking area, the transceiver unit [302] retrieves this data from the NSSF
30 [116]. For example, when a gNB in a tracking area initiates a connection, the AMF
[106] determines which network slices are authorized for use in that area. The
24

transceiver unit [302] first receives the target tracking area slice availability
authorisation request, and the processing unit [304] identifies the relevant slice
authorisation data based on the tracking area. After identifying this target slice data,
the transceiver unit [302] communicates with the NSSF [116] to fetch the latest
5 slice authorisation information for that area. The transceiver unit [302] then
receives the identified target slice authorisation data and passes it to the AMF [106], which uses it to configure the network slices appropriately for the gNB.
[0081] The slice availability authorisation request is transmitted from the AMF
10 [106] to the NSSF [116] when the AMF commission event associated with the AMF
[106] is detected. The AMF commission event refers to a scenario where the AMF
[106] is initialized, reconfigured, or updated, necessitating a fresh configuration of
network slices and their availability within the network. During this event, the AMF
[106] acquires updated slice availability data from the NSSF [116] to enable
15 managing and allocation of network slices for the connected gNBs and devices
within its coverage. For example, when a new AMF [106] is introduced into the
network, or an existing AMF undergoes a significant update, the system needs to
configure the AMF [106] with the latest network slice information. Upon detecting
the commissioning event, the AMF [106] sends a slice availability authorisation
20 request to the NSSF [116]. Once the NSSF [116] responds with the slice data, the
AMF [106] stores this information locally and uses it to manage network slices
effectively for future connections.
[0082] The slice availability authorisation request is associated with a set of
25 Tracking Area Identifiers (TAIs) that correspond to one or more tracking areas
within the network. TAIs are unique identifiers used to represent specific
geographical areas or regions within a mobile network. When the AMF [106] sends
a slice availability authorisation request to the NSSF [116], it includes the TAIs for
the one or more tracking areas associated with the AMF [106]. For example, in a
30 5G network, different tracking areas may be optimized for different services, such
as high-speed data, low-latency communication, or massive IoT connectivity. If the
25

AMF [106] is responsible for managing Tracking Area 1 and Tracking Area 2, the
slice availability authorisation request would specify the TAIs for these areas. The
NSSF [116] then uses these TAIs to determine which network slices are authorized
for use in those regions and provides the relevant slice authorisation data back to
5 the AMF [106].
[0083] The processing unit [304] is further configured to store the set of slice authorisation data in a local database at the AMF [106]. Once the slice authorisation data is received from the NSSF [116], the processing unit [304] organizes and saves
10 this data in the AMF's local database or memory. For example, after receiving slice
authorisation data for several tracking areas, the processing unit [304] stores this data locally within the AMF [106]. This data includes details about which network slices are authorized for each specific tracking area. When a gNB from a particular tracking area requests a connection, the AMF [106] can immediately retrieve the
15 relevant slice authorisation data from its local database, avoiding the need to
repeatedly query the NSSF [116]. This reduces response times and improves the efficiency of network operations.
[0084] The processing unit [304] is further configured to store the set of slice
20 authorisation data in a local database at the AMF [106] and organize the set of slice
authorisation data according to the set of Tracking Area Identifiers (TAIs) and
network slice identifiers (S-NSSAIs) associated with the slice authorisation data.
For example, after receiving slice authorisation data from the NSSF [116], the
processing unit [304] stores the data in a local database within the AMF [106].
25 However, instead of storing the data in a generic or unordered format, the
processing unit [304] organizes it based on the TAIs, which represent specific
geographical regions in the network, and the associated network slice identifiers,
which define the types of services (e.g., enhanced mobile broadband, low-latency
communication) that are available in those regions. This means that when a gNB
30 located in Tracking Area 5 sends a connection request, the AMF [106] can
efficiently retrieve the slice authorisation data specific to that area, including the
slice identifiers that determine the types of services that are authorized.
26

[0085] The system [300] further comprises a comparing unit [306] which is
configured to compare a target Tracking Area Identifier (TAI) with the set of TAIs
stored at the AMF [106], wherein the target TAI is associated with the target
5 tracking area slice availability request to select the target slice authorisation data.
The set of TAIs are associated with one or more tracking areas within the network. The comparing unit [306] is responsible for identifying the correct network slice data by matching the target TAI, which represents a specific area within the network, to the corresponding stored TAIs and their associated slice data. For
10 example, when a gNB located in a particular tracking area initiates a connection
request, the target TAI included in the request specifies the location of that gNB within the network. The comparing unit [306] uses this target TAI to search through the set of TAIs that have been previously stored at the AMF [106] along with their corresponding slice authorisation data. By comparing the target TAI with the stored
15 TAIs, the comparing unit [306] identifies which slice data is applicable to that
specific tracking area and ensures that the AMF [106] selects the correct slice authorisation data to configure the network resources for the gNB. For example, a network where different tracking areas support different types of services. For example, Tracking Area 10 may be optimized for IoT devices, while Tracking Area
20 15 supports high-speed mobile broadband. When a gNB in Tracking Area 10 sends
a connection request, the target TAI for this area is included in the request. The comparing unit [306] takes this target TAI and compares it with the stored TAIs at the AMF [106] to find a match. Upon finding the match, the comparing unit [306] selects the corresponding slice authorisation data that supports IoT services and
25 ensures that this data is used to configure the gNB in Tracking Area 10.
[0086] Referring to FIG. 4, an exemplary method flow diagram [400] for receiving
a target slice authorisation data at an Access and Mobility Management Function
(AMF) from a Network Slicing Selection Function (NSSF) in a network, in
30 accordance with exemplary implementations of the present disclosure is shown. In
an implementation the method [400] is performed by the system [300]. Further, in
27

an implementation, the system [300] may be present in a server device to implement the features of the present disclosure. Also, as shown in FIG. 4, the method [400] starts at step [402].
5 [0087] At step [404], the method [400] comprises transmitting, by a transceiver unit
[302], a slice availability authorisation request, from the AMF [106] to the NSSF [116]. The transceiver unit [302] facilitates in establishing a communication link between the AMF [106] and the NSSF [116] to enable the exchange of slice availability data. The slice availability authorisation request is initiated whenever
10 the AMF [106] requires authorisation for network slices associated with tracking
areas in the 5G network. When the AMF [106] is initially commissioned or upon its startup, it triggers the transceiver unit [302] to send the slice availability authorisation request. The slice availability authorisation request enables the AMF [106] to fetch a set of slice authorisation data. The authorisation data retrieved from
15 the NSSF [116] is associated with one or more tracking areas in the network to
enable the AMF [106] to manage network slice configuration for gNBs operating within those areas. For example, an AMF [106] manages multiple gNBs across various tracking areas. As each gNB performs NG Setup procedures, the AMF [106] facilitates that the correct slice availability data is authorized for the specific
20 tracking area associated with the gNB. In this case, the transceiver unit [302] sends
the slice availability authorisation request to the NSSF [116], and in response, the AMF [106] receives the required authorisation data. This data may then be stored locally at the AMF [106] and used to respond to future NG Setup requests without the need to query the NSSF [116] repeatedly. As used herein, NG Setup requests
25 refer to the signalling messages exchanged between the Next Generation NodeB
(gNB) and the Access and Mobility Management Function (AMF) [106] during the initial setup phase in a 5G network. These requests establish the NG interface, allowing the gNB to communicate with the core network by exchanging configuration information, supported features, and network parameters, enabling
30 the gNB to provide access to the 5G core network for connected devices.
28

[0088] The slice availability authorisation request is sent from the AMF [106] to
the NSSF [116] within a 5G network. The slice availability authorisation request is
used to obtain authorisation and availability information for network slices that are
applicable to tracking areas (such as geographical regions) associated with the
5 AMF. Network slices refers to isolated partitions of network resources configured
to handle different types of services, such as but not limited only to enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), or massive machine-type communications (mMTC). When the AMF [106] needs to allocate network slices for gNBs or user devices within the tracking area, it sends a
10 slice availability authorisation request to the NSSF [116]. The slice availability
authorisation request includes the tracking area identifiers (TAIs) for which the slice information is being sought. In response, the NSSF [116] provides the AMF [106] with the relevant slice authorisation data, providing details regarding which network slices are available and authorized for use in those tracking areas. For
15 example, if the AMF [106] manages a tracking area that is heavily focused on
supporting IoT devices, it may send a slice availability authorisation request to the NSSF [116] to obtain information on the network slices that are optimized for IoT services. Once the NSSF [116] responds with the appropriate data, the AMF [106] can allocate resources accordingly, such that the devices in that area are connected
20 to the correct network slices.
[0089] In an exemplary aspect, the slice availability authorisation request may also
include such as but not limited only to an AMF identifier to identify the AMF [106]
making the request, a slice selection criterion that may further include network slice
25 instance identifier which is specific identifier for the network slice being requested.
[0090] In an exemplary aspect, the slice availability authorisation request is
transmitted from the AMF [106] to the NSSF [116] the AMF commission event
which refers to a situation where the AMF [106] is being set up or initialized within
30 the network. This event marks a situation where the specific AMF [106] gets
activated to manage network functions and resources. In an exemplary aspect, when
29

the AMF [106] is being set up and starts operating in a particular network area, this event is triggered.
[0091] At step [406], the method [400] comprises fetching, by the transceiver unit
5 [302], a set of slice authorisation data based on the slice availability authorisation
request, from the NSSF [116], wherein the set of slice authorisation data is associated with one or more tracking areas associated with the network. The transceiver unit [302] is further configured to fetch a set of slice authorisation data based on the slice availability authorisation request from the Network Slice
10 Selection Function (NSSF) [116], wherein the set of slice authorisation data is
associated with one or more tracking areas associated with the network. The fetching operation is initiated after the transceiver unit [302] transmits the slice availability authorisation request to the NSSF [116]. Once the slice availability authorisation request is processed by the NSSF [116], it responds with the slice
15 authorisation data, which includes information about the network slices that are
available within the tracking areas. For example, in a 5G network deployment, the network is divided into multiple tracking areas, each of which may support different network slices based on the requirements of the users and services in that area. The AMF [106], which manages mobility and connection services, needs information
20 of network slices that are authorized for use in each tracking area. The transceiver
unit [302] fetches the slice authorisation data from the NSSF [116] such that the AMF [106] has up-to-date information of the network slices that are authorized within each tracking area. In an example, a new gNB is added to a specific tracking area. During the NG Setup process, the AMF [106] must determine which network
25 slices are authorized for use by this gNB. The transceiver unit [302] sends a slice
availability authorisation request to the NSSF [116], specifying the tracking area of the new gNB. The NSSF [116] responds with the slice authorisation data for that tracking area, which the transceiver unit [302] fetches and forwards to the AMF [106]. The AMF [106] can then use this data to configure the gNB accordingly such
30 that the correct network slices are utilized for the services in that area. The set of
slice authorisation data fetched by the transceiver unit [302] may include
30

information such as but not limited only to Single Network Slice Selection
Assistance Information (S-NSSAI), associated TAIs, and a set of policies
associated with the network slices. The set of policies corresponds to protocols or
rules associated with the network slices. In an exemplary embodiment, the slice
5 authorisation data may need to be updated as the network evolves. For example, if
additional network slices are introduced or if the coverage area of an existing network slices are expanded to include new tracking areas, the transceiver unit [302] can fetch the updated slice authorisation data from the NSSF [116] upon receiving a new slice availability authorisation request.
10
[0092] At step [408], the method [400] comprises configuring, by a processing unit [304], the set of slice authorisation data at the AMF [106]. Once the transceiver unit [302] fetches the slice authorisation data from the NSSF [116], the processing unit [304] organizes and stores the set of slice authorisation data in a structured manner
15 within the AMF [106]. For example, the AMF [106] receives slice authorisation
data that includes multiple slice identifiers such as S-NSSAI associated with different tracking areas (TAIs) in the network. The processing unit [304] categorizes and stores this data based on the corresponding TAIs. In an exemplary aspect, the processing unit [304] configures the set of slice authorisation data by
20 storing the slice authorisation data in a local database or memory structure within
the AMF [106]. For example, if a gNB requests connection within a specific tracking area, the processing unit [304] retrieves the relevant slice data from the local storage and uses it to configure the gNB accordingly. It would be appreciated by the person skilled in the art that the local configuration avoids the need for
25 repeated queries to the NSSF [116], significantly reducing setup times and
improving the overall efficiency of the network.
[0093] At step [410], the method [400] comprises receiving, by the transceiver unit
[302], a target tracking area slice availability authorisation request associated with
30 one of the one or more tracking areas, at the AMF [106]. For example, in a 5G
network, different tracking areas (TAs) may support different types of services
31

through network slicing. A tracking area may have network slices optimized for
high-speed internet, low-latency applications, or massive IoT connectivity,
depending on the services required in that region. When a gNB located in one of
the tracking areas requests a connection, the AMF [106] determines which network
5 slices are authorized for that specific area. The transceiver unit [302] receives the
request, which specifies the tracking area where the gNB is located and uses this information to handle the slice authorisation process accordingly. For example, a gNB is deployed in Tracking Area 2, which is configured to support low-latency services for real-time applications such as augmented reality (AR) or online
10 gaming. When the gNB in Tracking Area 2 initiates a connection setup, the
transceiver unit [302] receives the target tracking area slice availability authorisation request. The request is specific to Tracking Area 2, and it informs the AMF [106] that slice availability needs to be verified and authorized for this area. Based on this request, the AMF [106] can either retrieve the necessary slice
15 authorisation data from its local database or, if required, fetch updated slice data
from the NSSF [116].
[0094] At step [412], the method [400] comprises identifying, by the processing unit [304], a target slice authorisation data from the set of slice authorisation data
20 based on the target tracking area slice availability authorisation request. For
example, when a gNB located in a tracking area sends a request to the AMF [106], the transceiver unit [302] first receives this request. The processing unit [304] then analyses the target tracking area slice availability authorisation request to determine which network slices are authorized for use in that tracking area. The set of slice
25 authorisation data, which has been previously stored and organized within the AMF
[106], includes information about all the network slices authorized across various tracking areas in the network. The processing unit [304] uses the tracking area identifier (TAI) provided in the request to locate and extract the slice authorisation data from the set of slice authorisation data. For example, a gNB located in Tracking
30 Area 3, which is part of a 5G network that supports multiple services, such as
enhanced mobile broadband (eMBB) and ultra-reliable low-latency
32

communications (URLLC). When the gNB in Tracking Area 3 sends a connection request, the AMF [106] identifies which network slices are available and authorized in that area. The processing unit [304] examines the request, identifies that it pertains to Tracking Area 3, and retrieves the specific slice authorisation data corresponding to this area. This data might include slice identifiers for both eMBB and URLLC, such that the gNB can be configured to use the appropriate slice for the service it needs to provide.
[0095] At step [414], the method [400] comprises receiving, by the transceiver unit [302], the identified target slice authorisation data from the NSSF [116], at the AMF [106]. The AMF [106] obtains the target slice authorisation data directly from the NSSF [116] in response to a target tracking area slice availability authorisation request. Once the processing unit [304] identifies which slice authorisation data is required for a particular tracking area, the transceiver unit [302] retrieves this data from the NSSF [116]. For example, when a gNB in a tracking area initiates a connection, the AMF [106] determines which network slices are authorized for use in that area. The transceiver unit [302] first receives the target tracking area slice availability authorisation request, and the processing unit [304] identifies the relevant slice authorisation data based on the tracking area. After identifying this target slice data, the transceiver unit [302] communicates with the NSSF [116] to fetch the latest slice authorisation information for that area. The transceiver unit [302] then receives the identified target slice authorisation data and passes it to the AMF [106], which uses it to configure the network slices appropriately for the gNB.
[0096] Thereafter, the method [400] terminates at step [416].
[0097] Referring to FIG 5, an exemplary process flow diagram [500] for receiving a target slice authorisation data at an Access and Mobility Management Function (AMF) [106] from a Network Slicing Selection Function (NSSF) [116] in a network, in accordance with exemplary implementations of the present disclosure is shown.

[0098] At step S1, the AMF [106] sends on startup the slice availability authorisation request to the NSSF [116]. In an exemplary aspect, the transceiver unit [302] transmits from the AMF [106] to the NSSF [116], a slice availability authorisation request to determine the availability and authorisation status of network slices. In an exemplary aspect, the slice availability authorisation request is a query sent by the AMF [106] to the NSSF [116] at a startup of a network. In an exemplary aspect, the slice availability authorisation request includes requests about which network slice the AMF [106] wants to access and any relevant context or parameters required for the NSSF [116] to process the request.
[0099] At step S2, the NSSF [116] sends back the slice availability data authorized to the AMF [106]. In an exemplary aspect, the transceiver unit [302] using AMF [106] fetches slice authorisation data by sending a request to the NSSF [116], which identifies available network slices for a specified tracking area. The NSSF [116] returns a set of slice authorisation data, including details like available network slices. This data is stored locally at the AMF [106], allowing it to quickly manage network slices during operations like NG Setup, reducing the need for repeated queries to the NSSF [116] and improving network efficiency.
[0100] In an exemplary aspect, the invention relates to a method implemented within a network that enables the AMF [106] to manage and retrieve network slice authorization data from the NSSF [116]. The process begins with the AMF [106] transmitting a slice availability authorization request (such as Get service operation of the NSSF's Network Slice Selection (Nnssf_NSSelection) service) to the NSSF [116]. Upon receiving the slice availability authorization request, the NSSF [116] processes it and returns the set of slice authorization data, which includes specific information related to one or more tracking areas within the network. the set of slice authorization data is configured at the AMF [106] and may be stored locally to enhance operational efficiency. Based on the slice availability authorisation request if the NSSF [116] locates the set of slice authorization data, a status code (such as

"200 OK") shall be sent from the NSSF [116] to the AMF [106] and along with a response. The response body may include at least payload body including at least the following parameter “AuthorizedNssaiAvailabilityData”. This contains the NSSAI availability data information per TA authorized by the NSSF [116].
[0101] Thereafter, the AMF [106] may receive a target tracking area slice availability authorization request, prompting the AMF [106] to identify the relevant slice authorization data from the previously received set of slice authorization data. The AMF [106] can thus retrieve the target slice authorization data from the NSSF [116], effectively enabling the network to manage and select appropriate network slices for tracking areas. Additionally, the AMF [106] can organize and store this slice authorization data by associating it with tracking area identifiers (TAIs) and network slice identifiers. This facilitates quick access and management of slice data, allowing for dynamic adjustments based on the tracking area or network slice requirements.
[0102] The present disclosure further discloses a non-transitory computer readable storage medium storing instructions for receiving a target slice authorisation data at an Access and Mobility Management Function (AMF) [106] from a Network Slicing Selection Function (NSSF) [116] in a network, the instructions include executable code which, when executed by one or more units of a system, causes: a transceiver unit [302] to transmit, a slice availability authorisation request, from the AMF [106] to the NSSF [116]. The instructions when executed further causes the transceiver unit [302] to fetch, a set of slice authorisation data based on the slice availability authorisation request, from the NSSF [116], wherein the set of slice authorisation data is associated with one or more tracking areas associated with the network. The instructions when executed further causes a processing unit [304] to configure, the set of slice authorisation data, at the AMF [106]. The instructions when executed further causes the transceiver unit [302] to receive, a target tracking area slice availability authorisation request associated with one of the one or more tracking areas of the network, at the AMF [106]. The instructions when executed

further causes the processing unit [304] to identify, a target slice authorisation data from the set of slice authorisation data based on the target tracking area slice availability authorisation request. The instructions when executed further causes the transceiver unit [302] to receive the identified target slice authorisation data from the NSSF [116] at the AMF [106].
[0103] As is evident from the above, the present disclosure provides a technically advanced solution for receiving a target slice authorisation data at an Access and Mobility Management Function (AMF) from a Network Slicing Selection Function (NSSF) in a network. The present invention provides an advanced solution for transmitting directly to an AMF target slice authorisation data. As disclosed by the present disclosure, the present novel solution offers several distinct advantages and significant technical advancements. By enabling the AMF to independently configure slice availability data per TAI and storing this data locally, the system gains autonomy and efficiency. The pivotal innovation emerges during AMF startup, where the slice availability data is directly authorised from NSSFs. By responding to NG setups with pre-authorised slice data rather than making repeated trips to NSSF for authorisation, the solution drastically reduces the overall NG setup time. This streamlined process not only expedites network configuration but also eliminates the need for thousands of individual slice availability data authorisations from NSSF. Consequently, this novel approach optimises resource utilisation, minimises delays, and enhances the scalability and responsiveness of the network infrastructure, marking a notable technical advancement in network configuration and management paradigms.
[0104] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various the 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.
[0105] 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 receiving a target slice authorisation data at an Access and
Mobility Management Function (AMF) from a Network Slicing Selection
Function (NSSF) in a network, the method comprising:
- transmitting, by a transceiver unit [302], a slice availability authorisation request, from the AMF [106] to the NSSF [116];
- fetching, by the transceiver unit [302], a set of slice authorisation data based on the slice availability authorisation request, from the NSSF [116], wherein the set of slice authorisation data is associated with one or more tracking areas associated with the network;
- configuring, by a processing unit [304], the set of slice authorisation data at the AMF [106];
- receiving, by the transceiver unit [302], a target tracking area slice availability authorisation request associated with one of the one or more tracking areas, at the AMF [106];
- identifying, by the processing unit [304], a target slice authorisation data from the set of slice authorisation data based on the target tracking area slice availability authorisation request; and
- receiving, by the transceiver unit [302], the identified target slice authorisation data from the NSSF [116], at the AMF [106].

2. The method as claimed in claim 1, wherein the slice availability authorisation request is transmitted from the AMF [106] to the NSSF [116] in an event an AMF commission event associated with the AMF [106] is detected.
3. The method as claimed in claim 1, wherein the slice availability authorisation request is associated with a set of tracking area identifiers (TAIs) of one of the one or more tracking areas of the network.

4. The method as claimed in claim 1, wherein the configuring further comprises storing, by the processing unit [304], the set of slice authorisation data in a local database at the AMF [106].
5. The method as claimed in claims 3 or 4, wherein the configuring further comprises organizing, by the processing unit [304], the set of slice authorisation data according to the set of TAIs and a set of network slice identifiers associated with the set of slice authorisation data.
6. The method as claimed in claim 1, wherein the identifying further comprises comparing, by a comparing unit [306], a target TAI with the set of TAIs stored at the AMF [106], wherein the target TAI is associated with the target tracking area slice availability request to select the target slice authorisation data.
7. A system for receiving a target slice authorisation data at an Access and Mobility Management Function (AMF) from a Network Slicing Selection Function (NSSF) in a network, the system comprises:
- a transceiver unit [302], wherein the transceiver unit [302] is configured to:
• transmit, a slice availability authorisation request, from the AMF [106] to the NSSF [116], and
• fetch, a set of slice authorisation data based on the slice availability authorisation request, from the NSSF [116], wherein the set of slice authorisation data is associated with one or more tracking areas associated with the network; and
- a processing unit [304] connected to the transceiver unit [302], wherein the
processing unit [304] is configured to:
• configure, the set of slice authorisation data, at the AMF [106];
wherein the transceiver unit [302] is further configured to:
• receive, a target tracking area slice availability authorisation request
associated with one of the one or more tracking areas of the network, at
the AMF [106];

wherein the processing unit [304] is further configured to:
• identify, a target slice authorisation data from the set of slice
authorisation data based on the target tracking area slice availability
authorisation request; and
wherein the transceiver unit [302] is further configured to:
• receive the identified target slice authorisation data from the NSSF [116]
at the AMF [106].
8. The system as claimed in claim 7, wherein the slice availability authorisation request is transmitted from the AMF [106] to the NSSF [116] in an event an AMF commission event associated with the AMF [106] is detected.
9. The system as claimed in claim 7, wherein the slice availability authorisation request is associated with a set of tracking area identifiers (TAIs) of one of the one or more tracking areas of the network.
10. The system as claimed in claim 7, wherein the processing unit [304] is further configured to store the set of slice authorisation data in a local database at the AMF [106].
11. The system as claimed in claim 9 or 10, wherein the processing unit [304] is further configured to organise the set of slice authorisation data according to the set of TAIs and a set of network slice identifiers associated with the set of slice authorisation data.
12. The system as claimed in claim 7, wherein a comparing unit [306] is configured to compare a target TAI with the set of TAIs stored at the AMF [106], wherein the target TAI is associated with the target tracking area slice availability request to select the target slice authorisation data.