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 REGISTERING A USER EQUIPMENT”
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.
2
METHOD AND SYSTEM FOR REGISTERING A USER EQUIPMENT
FIELD OF THE DISCLOSURE
5
[0001]
Embodiments of the present disclosure generally relate to an improved connection management of a user equipment (UE) with a network. More particularly, embodiments of the present disclosure relate to methods and systems for registering the (UE).
10
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 15 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]
In the context of UE registration to networks such as 5G Core (5GC), a 20 significant challenge arises concerning slice selection within the Access and Mobility Management Function (AMF). The AMF is tasked with the critical decision of choosing an appropriate network slice during registration, a process that can be executed either through local mechanisms or by engaging the Network Slice Selection Function (NSSF). A particular issue arises when an AMF, despite 25 supporting local slice selection, encounters an inadequacy of data necessary for precise slice determination. In such scenarios, the AMF faces the predicament of potentially rejecting the registration request due to the inability to make an informed and suitable slice selection. This problem highlights the necessity for seamless data availability and robust decision-making procedures within the core network to 30
3
ensure efficient and uninterrupted user registration while optimizing network
resource allocation.
[0004]
Thus, there exists an imperative need in the art to authorise an allocation of a slice data by an AMF to a UE either locally by the AMF or by fetching 5 authorisation from the NSSF, which the present disclosure aims to address.
SUMMARY
[0005]
This section is provided to introduce certain aspects of the present disclosure 10 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 registering a 15 user equipment (UE). The method comprises receiving, by a transceiver unit at an access and mobility management function (AMF) from the UE, a user equipment (UE) registration request comprising a slice selection request. The method further comprises matching, by a processing unit at the AMF, at least one parameter within the slice selection request with at least one of a network slice availability 20 authorisation data from a set of network slice availability authorisation data. Then the method further comprises identifying, by the processing unit at the AMF, an unsuccessful slice selection match associated with the user equipment (UE) registration request. The method further comprises transmitting, by the transceiver unit from the AMF to a network slice selection function (NSSF), at least the slice 25 selection request based on the unsuccessful slice selection match. The method further comprises fetching, by the transceiver unit at the AMF, an updated set of network slice availability authorisation data from the NSSF. The method further comprises identifying, by the processing unit at the AMF, a successful slice selection match for the slice selection request, based on the updated set of network 30 slice availability authorisation data. The method further comprises registering, by
4
the processing unit at the AMF, the user equipment (UE) based on the successful
slice selection match.
[0007]
In an exemplary aspect of the present disclosure, the method further comprises fetching, by the transceiver unit at the AMF from the NSSF, the set of 5 network slice availability authorisation data associated with one or more network slices, wherein the set of network slice availability authorisation data associated with the one or more network slices is received at the AMF from the NSSF when a network startup event associated with a network is detected at the UE.
10
[0008]
In another exemplary aspect of the present disclosure, the set of network slice availability authorisation data is associated with at least one of the network slice availability authorisation data and one or more tracking area identifiers (TAIs) of the network.
15
[0009]
In another exemplary aspect of the present disclosure, the unsuccessful slice selection match is identified at the AMF based on a failure in matching the slice selection request with the set of network slice availability authorisation data.
[0010]
Another aspect of the present disclosure may relate to a system for 20 registering a user equipment (UE). The system comprises a transceiver unit and a processing unit connected with each other. The transceiver unit is configured to receive, at an access and mobility management function (AMF) from the User equipment (UE), a user equipment (UE) registration request comprising a slice selection request. The processing unit is configured to match, at the AMF, at least 25 one parameter within the slice selection request with at least one of a network slice availability authorisation data from a set of network slice availability authorisation data. Then the processing unit is configured to identify, at the AMF, an unsuccessful slice selection match associated with the user equipment registration request. The transceiver unit is further configured to transmit, from the AMF to a network slice 30 selection function (NSSF), at least the slice selection request based on the
5
unsuccessful slice selection match
. The transceiver unit is also configured to fetch, at the AMF from the NSSF, an updated set of network slice availability authorisation data. The processing unit is further configured to identify a successful slice selection match for the slice selection request, based on the updated set of network slice availability authorisation data. Also, the processing unit is further 5 configured to register, at the AMF, the user equipment (UE) based on the successful slice selection match.
[0011]
Another aspect of the present disclosure relates to a user equipment (UE) comprising a processor. The processor is configured to send a user equipment (UE) 10 registration request comprising a slice selection request to an AMF. Also, the processor may be configured to receive authorisation of the user equipment (UE) registration request from the AMF based on a successful slice selection match. In order to authorise the user equipment (UE) registration request, the processor may be configured to fetch, from a Network Slice Selection Function (NSSF), a set of 15 network slice availability authorisation data associated with one or more network slices. Then the processor matches the slice selection request with at least one of the network slice availability authorisation data from the set of network slice availability authorisation data. The processor then identifies an unsuccessful slice selection match associated with the user equipment registration request. The 20 processor then may transmit, to the NSSF, at least the slice selection request based on the unsuccessful slice selection match. The processor may also fetch, from the NSSF, an updated set of network slice availability authorisation data. Also, the processor identifies a successful slice selection match for the slice selection request, based on the updated set of network slice availability authorisation data. The 25 processor then registers at the AMF the user equipment (UE) based on the successful slice selection match.
[0012]
Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing one or more instructions for registering 30 a user equipment (UE), the one or more instructions include executable code which,
6
when executed by one or more units of a system, causes
the one or more units to perform certain functions. The one or more instructions when executed causes a transceiver unit at an access and mobility management function (AMF) of the system to receive a user equipment (UE) registration request comprising a slice selection request from the UE. The one or more instructions when executed further 5 causes a processing unit at the AMF of the system to match at least one parameter within the slice selection request with at least one of a network slice availability authorisation data from a set of network slice availability authorisation data. The one or more instructions when executed further causes the processing unit at the AMF to identify an unsuccessful slice selection match associated with the user 10 equipment (UE) registration request. The one or more instructions when executed further causes the transceiver unit to transmit from the AMF to a network slice selection function (NSSF), at least the slice selection request based on the unsuccessful slice selection match. The one or more instructions when executed further causes the transceiver unit at the AMF to fetch an updated set of network 15 slice availability authorisation data from the NSSF. The one or more instructions when executed further causes the processing unit at the AMF to identify a successful slice selection match for the slice selection request, based on the updated set of network slice availability authorisation data. The one or more instructions when executed further causes the processing unit at the AMF to register the user 20 equipment (UE) based on the successful slice selection match.
OBJECTS OF THE DISCLOSURE
[0013]
Some of the objects of the present disclosure, which at least one 25 embodiment disclosed herein satisfies are listed herein below.
[0014]
It is an object of the present disclosure to provide a system and a method for registering a user equipment (UE).
30
7
[0015]
It is an object of the present disclosure to provide a system and a method for authorising an allocation of a slice data by an AMF to a UE.
[0016]
It is another object of the present disclosure to provide a solution that authorises an allocation of a slice data by an AMF to a UE either locally by the 5 AMF or by fetching authorisation from the NSSF.
[0017]
It is yet another object of the present disclosure to provide a solution that authorises allocation of the slice data based on the successful slice selection transmitted by the AMF to the UE, wherein the slice data is allocated to the UE by 10 the AMF based on successfully matching the query data with at least one of the set of network slice availability authorisation data and the updated network slice availability authorisation data fetched by the AMF from the NSSF.
BRIEF DESCRIPTION OF THE DRAWINGS 15
[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, 20 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 25 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. 30
8
[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 registering a 5 user equipment (UE), in accordance with exemplary implementations of the present disclosure.
[0022]
FIG. 4 illustrates a method flow diagram for registering the user equipment (UE) in accordance with exemplary implementations of the present disclosure. 10
[0023]
FIG. 5 illustrates an exemplary method for registering the user equipment (UE) in accordance with exemplary implementations of the present disclosure.
[0024]
The foregoing shall be more apparent from the following more detailed 15 description of the disclosure.
DETAILED DESCRIPTION
[0025]
In the following description, for the purposes of explanation, various 20 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 25 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, 30 the ensuing description of the exemplary embodiments will provide those skilled in
9
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.
5
[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 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 10 embodiments in unnecessary detail.
[0028]
It should be noted that the terms "first", "second", "primary", "secondary", "target" and the like, herein do not denote any order, ranking, quantity, or importance, but rather are used to distinguish one element from another. 15
[0029]
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 20 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.
[0030]
The word “exemplary” and/or “demonstrative” is used herein to mean 25 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 30 known to those of ordinary skill in the art. Furthermore, to the extent that the terms
10
“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.
5
[0031]
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 10 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 15 processing unit is a hardware processor.
[0032]
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 20 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 25 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 unit(s) which are required to implement the features of the present disclosure.
[0033]
As used herein, “storage unit” or “memory unit” refers to a machine or 30 computer-readable medium including any mechanism for storing information in a
11
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 5 functions.
[0034]
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 refer to a set of rules or protocols that define 10 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.
[0035]
All modules, units, components used herein, unless explicitly excluded 15 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 20 circuits (FPGA), any other type of integrated circuits, etc.
[0036]
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 25 and/or connected with the system.
[0037]
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 a 30 method and a system of registering a user equipment (UE).
12
[0038]
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 5 (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 10 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. 15
[0039]
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 20 wireless communication.
[0040]
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 25 procedures like handovers and paging.
[0041]
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 30 forwarding and handles IP address allocation and QoS enforcement.
13
[0042]
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. 5
[0043]
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.
10
[0044]
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 authorized.
15
[0045]
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.
[0046]
Network Exposure Function (NEF) [118] is a network function that exposes 20 capabilities and services of the 5G network to external applications, enabling integration with third-party services and applications.
[0047]
Network Repository Function (NRF) [120] is a network function that acts as a central repository for information about available network functions and 25 services. It facilitates the discovery and dynamic registration of network functions.
[0048]
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. 30
14
[0049]
Unified Data Management (UDM) [124] is a network function that centralizes the management of subscriber data, including authentication, authorization, and subscription information.
[0050]
Application Function (AF) [126] is a network function that represents 5 external applications interfacing with the 5G core network to access network capabilities and services.
[0051]
User Plane Function (UPF) [128] is a network function responsible for handling user data traffic, including packet routing, forwarding, and QoS 10 enforcement.
[0052]
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
[0053]
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 20 registering a user equipment (UE) [102] utilising the system [300]. In another implementation, the computing device [200] itself implements the method for registering the user equipment (UE) [102] 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
[0054]
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 30 computing device [200] may also include a main memory [206], such as a random-
15
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 the processor [204]. Such instructions, when stored in non-transitory storage media 5 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 storage device coupled to the bus [202] for storing static information and instructions for the processor [204]. 10
[0055]
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), 15 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 selections to the processor [204]. Another type of user input device may be a cursor controller [216], such as a 20 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]. The 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 to specify positions in a plane. 25
[0056]
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 computing device [200] to be a special-purpose machine. 30 According to one implementation, the techniques herein are performed by the
16
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]. Execution of the sequences of instructions contained in the main memory [206] causes the processor [204] to perform the 5 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.
[0057]
The computing device [200] also may include a communication interface 10 [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]. 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 15 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 implemented. In any such implementation, the communication interface [218] sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing 20 various types of information.
[0058]
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 25 transmit a requested code for an application program through the Internet [228], the ISP [226], the local network [222], a 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. 30
17
[0059]
Referring to FIG. 3, an exemplary block diagram of a system [300] for registering the user equipment (UE) [102], is shown, in accordance with the exemplary implementations of the present disclosure. The system [300] comprises at least one transceiver unit [302] and may also comprise at least one processing unit [304]. Also, all of the components/ units of the system [300] are assumed to be 5 connected to each other unless otherwise indicated below. As shown in the figures, all units shown within the system [300] 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 units or the system [300] may comprise any such numbers of said units, as required to implement the features of the present 10 disclosure. Further, in an implementation, the system [300] may be present in a user device/ user equipment [102] to implement the features of the present disclosure. The system [300] may be a part of the user device [102] or may be independent of but in communication with the user device [102] (may also be referred to herein as a UE). In another implementation, the system [300] may reside in a server or a 15 network entity. In yet another implementation, the system [300] may reside partly in the server/ network entity and partly in the user device.
[0060]
The system [300] is configured for registering the user equipment (UE) [102], with the help of the interconnection between the components/units of the 20 system [300].
[0061]
As is known that the UE [102] is required to be registered with the AMF [106] in order to be connected with the 5GC network. For this various method are being applied, but the same are undesirable, since as discussed in the background 25 section, the AMF [106] faces the predicament of potentially rejecting the registration request due to the inability to make an informed and suitable slice selection thereby interrupting registration of the UE [102] with the AMF [106] and leading to network issues.
30
18
[0062]
Hence, in order to register the user equipment (UE) [102], the transceiver unit [302] receives a user equipment (UE) registration request comprising a slice selection request. The UE registration request is received at an access and mobility management function (AMF) [106] from the User equipment (UE) [102]. The UE registration request is a request that may be used to establish and release signalling 5 connection between the UE [102] and the AMF [106] and may also be used to register or deregister a UE/user with the 5G System (5GS) and establish the user context in the 5GS. Also, the slice selection request may be a request for the set of slices which may be used during the registration process. Further, the slice selection request may indicate preference for certain network slice parameters and the 10 network tries to select a slice that meets the requested criteria.
[0063]
Then once the UE registration request is received, the processing unit [304] matches at least one parameter with at least one of a network slice availability authorisation data. The at least one parameter may be within the slice selection 15 request. Also, the network slice availability authorisation data may be selected from a set of network slice availability authorisation data. The matching may be done at the AMF [106]. The at least one parameter may refer to the preference for certain network slice parameters as may be preferred by the UE [102]. The at least one parameter may comprise the information related to the preferred network slices. 20 The network slice availability authorisation data may refer to information associated with the availability/unavailability of a particular network slice. The set of network slice availability authorisation data may refer to information associated with availability and non-availability of a particular set of network slices. Matching of the at least one parameter and the network slice availability data may provide 25 information for availability or non-availability of the network slices that were preferred by the UE [102].
[0064]
For example, the AMF [106] may transmit a GET request to the NSSF [116]. If the AMF [106] wants to retrieve the slice selection information, one or more of 30 the following parameters shall be included in the slice-info-request-for-registration
19
query parameter:
Requested NSSAI and Subscribed S-NSSAI(s) with the indication if marked as default S-NSSAI and the associated subscribed NSSRG information; optionally UE support of subscription-based restrictions to simultaneous registration of network slice feature Indication; UDM indication to provide all subscribed S-NSSAIs for UEs not indicating support of subscription-based 5 restrictions to simultaneous registration of network slices feature; and Indication of the support of NSAG by the UE.
[0065]
In another example, if the AMF [106] wants to retrieve the slice mapping information, the following parameters shall be included in the slice-info-request-10 for-registration query parameter: sNssaiForMapping IE; and requestMapping IE.
[0066]
The AMF [106] further includes the following parameters in the message: PLMN ID of the SUPI in roaming scenarios; TAI; NF type of the NF service consumer; and Requester ID. 15
[0067]
In an implementation of the present disclosure, the transceiver unit [302] may fetch the set of network slice availability authorisation data associated with one or more network slices from the NSSF [116], and the fetching may be done at the AMF [106]. Further, the set of network slice availability authorisation data 20 associated with the one or more network slices are received at the AMF [106] from the NSSF [116] when a network startup event associated with a network is detected at the UE [102]. The one or more network slices may refer to a logical network that provides specific network capabilities and network characteristics which may support various service properties for network slice customers. The startup event 25 may refer to the event at which a network slice associated with the telecommunication network has been started up. The network may refer to the telecommunication network as a whole.
[0068]
In another implementation of the present disclosure, the set of network slice 30 availability authorisation data is associated with at least one of the network slice
20
availability authorisation data and one or more tracking area identifiers (TAIs) of
the network. The one or more TAIs comprise information associated with a mobile country code (MCC), a mobile network code (MNC), and a tracking area code (TAC). The MCC identifies the country in which the PLMN is located. The MNC is a code identifying the PLMN in that country. The TAC is a fixed length code such 5 as of 2 octets that may be used for identifying a Tracking Area within a PLMN.
[0069]
Continuing further, after the matching of the at least one parameter and the network slice availability authorisation data, the processing unit [304] identifies at the AMF [106], an unsuccessful slice selection match associated with the user 10 equipment (UE) registration request. The unsuccessful slice selection match may refer to the event in which the at least one parameter does not match with network slice availability authorisation data. The unsuccessful slice selection match is the event where the preferred network slice indicated in the UE registration request is not available for connection. 15
[0070]
In one of many implementations of the present disclosure, the unsuccessful slice selection match may be identified at the AMF [106] based on a failure in matching the slice selection request with the set of network slice availability authorisation data. The failure of the matching of the slice selection request with 20 the set of network slice availability authorisation data is the event that the network slice that was preferred by the UE [102] is not available for connection.
[0071]
Continuing further, on identification of the unsuccessful slice selection match, the transceiver unit [302] transmits at least the slice selection request based 25 on the unsuccessful slice selection match. The slice selection request may be transmitted from the AMF [106] to a network slice selection function (NSSF) [116]. The NSSF [116] transmits the slice selection request in order to get information for available slices which may be provided to the AMF [106] for connection to avoid disconnection/ interruption of the registration of the UE [102]. Since, it may be a 30
21
scenario that the availability status for the one or more network slices may be
changed, the NSSF [116] provides the information for available network slices.
[0072]
Thereafter, the transceiver unit [302] receives an updated set of network slice availability authorisation data. The updated set of network slice availability 5 authorisation data may then be transmitted by the NSSF [116] to the AMF [106]. The updated set of network slice availability authorisation data may refer to the information for the one or more network slices along with their availability status which may be then used for updating the set of network slice availability authorisation data. The updated information for the available network slices may be 10 then used for checking the preferences for the UE [102].
[0073]
Once, the updated set of network slice availability authorisation data is received from the NSSF [116], the processing unit [302] identifies a successful slice selection match for the slice selection request, based on the updated set of network 15 slice availability authorisation data. The successful slice selection match may refer to the event that the at least one parameter is matched with the updated set of network slice availability authorisation data. This may be a case that the preferred network slices are found to be available and may be used for further registration.
20
[0074]
Further, after the successful slice selection match is identified, then the processing unit [302] registers the user equipment (UE) based on the successful slice selection match at the AMF [106]. After the preferred network slices are found to be available, the UE is registered with the AMF [106] and the UE [102] is provided with the information associated with the preferred network slices. This 25 process allows for improved registrations success rate by querying slice selection to NSSF [116] even though AMF [106] may be configured to locally decide on slice selection. Rather than the AMF [106] directly rejecting the registration request, in such cases where, due to insufficient data it cannot decide on slice selection, the present disclosure facilitates improved success rate for registration of the UE [102] 30 at the AMF [106].
22
[0075]
Referring to FIG. 4, an exemplary method flow diagram [400] for registering a user equipment (UE) [102], 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 5 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].
[0076]
Initially, at step [404], the method [400] comprises receiving, by a transceiver unit [302] at an access and mobility management function (AMF) [106] 10 from the UE [102], a user equipment (UE) registration request comprising a slice selection request. The UE registration request is a request that may be used to establish and release signalling connection between the UE [102] and the AMF [106] and may also be used to register or deregister a UE/user with the 5G System (5GS) and establish the user context in the 5GS. Also, the slice selection request 15 may be a request for the set of slices which may be used during the registration process. Further the slice selection request may indicate preference for certain network slice parameters and the network tries to select a slice that meets the requested criteria.
20
[0077]
After the UE registration request is received, then at step [406] the method [400] comprises matching, by a processing unit [304] at the AMF [106], at least one parameter within the slice selection request with at least one of a network slice availability authorisation data from a set of network slice availability authorisation data. The matching may be done at the AMF [106]. The at least one parameter may 25 refer to the preference for certain network slice parameters as may be preferred by the UE [102]. The at least one parameter may comprise the information related to the preferred network slices. The network slice availability authorisation data may refer to information associated with the availability/unavailability of a particular network slice. The set of network slice availability authorisation data may refer to 30 information associated with availability and non-availability of a particular set of
23
network slices. Matching of the at least one parameter and the network slice
availability data may provide information for availability or non-availability of the network slices that were preferred by the UE [102].
[0078]
For example, the AMF [106] may transmit a GET request to the NSSF [116]. 5 If the AMF [106] wants to retrieve the slice selection information, one or more of the following parameters shall be included in the slice-info-request-for-registration query parameter: Requested NSSAI and Subscribed S-NSSAI(s) with the indication if marked as default S-NSSAI and the associated subscribed NSSRG information; optionally UE support of subscription-based restrictions to simultaneous 10 registration of network slice feature Indication; UDM indication to provide all subscribed S-NSSAIs for UEs not indicating support of subscription-based restrictions to simultaneous registration of network slices feature; and Indication of the support of NSAG by the UE.
15
[0079]
In another example, if the AMF [106] wants to retrieve the slice mapping information, the following parameters shall be included in the slice-info-request-for-registration query parameter: sNssaiForMapping IE; and requestMapping IE.
[0080]
The AMF [106] further includes the following parameters in the message: 20 PLMN ID of the SUPI in roaming scenarios; TAI; NF type of the NF service consumer; and Requester ID.
[0081]
In an implementation of the present disclosure, the method [400] may also involve fetching, by the transceiver unit [302] at the AMF [106], the set of network 25 slice availability authorisation data associated with one or more network slices from the NSSF [116]. Further, the set of network slice availability authorisation data associated with the one or more network slices are received at the AMF [106] from the NSSF [116] when a network startup event associated with a network is detected at the UE [102]. The one or more network slices may refer to a logical network that 30 provides specific network capabilities and network characteristics which may
24
support
various service properties for network slice customers. The startup event may refer to the event at which the UE [102] attempts to connect to the 5GC and the AMF [106] finds a network slice for registering the UE [102]. The network may refer to the telecommunication network as a whole.
5
[0082]
In another implementation of the present disclosure, the set of network slice availability authorisation data is associated with at least one of the network slice availability authorisation data and one or more tracking area identifiers (TAIs) of the network. The one or more TAIs comprise information associated with a mobile country code (MCC), a mobile network code (MNC), and a tracking area code 10 (TAC). The MCC identifies the country in which the PLMN is located. The MNC is a code identifying the PLMN in that country. The TAC is a fixed length code such as of 2 octets that may be used for identifying a Tracking Area within a PLMN.
[0083]
After the matching of the at least one parameter and the network slice 15 availability authorisation data, then at step [408], the method [400] further comprises identifying, by the processing unit [304] at the AMF [106], an unsuccessful slice selection match associated with the user equipment (UE) registration request. The unsuccessful slice selection match may refer to the event in which the at least one parameter does not match with network slice availability 20 authorisation data. The unsuccessful slice selection match is the event where the preferred network slice indicated in the UE registration request UE registration request is not available for connection.
[0084]
Also, in one implementation of the present disclosure, the unsuccessful slice 25 selection match may be identified at the AMF [106] based on a failure in matching the slice selection request with the set of network slice availability authorisation data. The failure of the matching of the slice selection request with the set of network slice availability authorisation data is the event that the network slice that was preferred by the UE [102] is not available for connection. 30
25
[0085]
On identification of the unsuccessful slice selection match, then at step [410], the method [400] comprises transmitting, by the transceiver unit [302] from the AMF [106] to a network slice selection function (NSSF) [116], at least the slice selection request based on the unsuccessful slice selection match. The NSSF [116] transmits the slice selection request in order to get information for available slices 5 which may be provided to the AMF [106] for connection to avoid disconnection/ interruption of the registration of the UE [102]. Since, it may be a scenario that the availability status for the one or more network slices may be changed, the NSSF [116] provides the information for available network slices.
10
[0086]
Thereafter, at step [412], the method [400] involves transmitting, by the transceiver unit [302], from the NSSF [116], at the AMF [106], an updated set of network slice availability authorisation data. The updated set of network slice availability authorisation data may refer to the information for the one or more network slices along with their availability status which may be then used for 15 updating the set of network slice availability authorisation data. The updated information for the available network slices may be then used for checking the preferences for the UE [102].
[0087]
Once the updated set of network slice availability authorisation data is 20 received from the NSSF [116], then at step [414], the method [400] comprises identifying, by the processing unit [304] at the AMF [106], a successful slice selection match for the slice selection request, based on the updated set of network slice availability authorisation data. The successful slice selection match may refer to the event that the at least one parameter is matched with the updated set of 25 network slice availability authorisation data. This may be a case that the preferred network slices are found to be available and may be used for further registration.
[0088]
Further, after, the identification of the successful slice selection match for the slice selection request, then at step [416], the method [400] comprises 30 registering, by the processing unit [304] at the AMF [106], the user equipment (UE)
26
based on the successful slice selection match.
After the preferred network slices are found to be available, the UE is registered with the AMF [106] and the UE [102] is provided with the information associated with the preferred network slices. This process allows for improved registrations success rate by querying slice selection to NSSF [116] even though AMF [106] may be configured to locally decide on slice 5 selection. Rather than the AMF [106] directly rejecting registration request, in such cases, where due to insufficient data it cannot decide on slice selection, the present disclosure facilitates improved success rate for registration of the UE [102] at the AMF [106].
10
[0089]
Thereafter, at step [418], the method [400] is terminated.
[0090]
Referring to FIG. 5, an exemplary method for registering the user equipment (UE) [102] has been provided in accordance with exemplary implementation of the present disclosure. Further in an implementation of the 15 present disclosure, the system [300] may perform the method [500] as depicted in FIG. 5. In another implementation of the present disclosure, the method [500] may be performed via the one or more components of the system [300].
[0091]
The method [500] is initiated when the UE [102] attempts to register to the 20 telecommunication network such as 5GC. The UE [102] sends a registration request to the AMF [106] and then as shown in the figure, at step [502], the AMF [106] gets network slice availability authorization data at the startup of the registration attempt. Then, the registration procedure keeps on going at step [504]. The AMF [106], being configured to provide the network slice selection locally, tries to select 25 the network slice based on the preference of the UE [102].
[0092]
As shown in the figure at step [506], the AMF [106] is unable to provide the preferred network slice due to insufficient network slice availability authorization data at AMF [106]. Generally, the exemplary method would reject the 30 UE [102] for connection, thereby interrupting the connection. However, as per the
27
present disclosure,
at step [508], the AMF [106] sends a slice selection request to the NSSF [116] and then at step [510], the NSSF [116] responds back positively to the AMF [106] with slice selection data. The AMF [106] is able to accept registration requests for further processing rather than rejecting it and then at step [512], the method [500] may proceed to the registration steps involved in the 5 registration of the UE [102].
[0093]
In another implementation of the present disclosure, a user equipment (UE) [102] comprising a processor is provided. The processor is configured to send a user equipment (UE) registration request comprising a slice selection request to an 10 AMF [106]. Also, the processor may be configured to receive authorisation of the user equipment (UE) registration request from the AMF [106] based on a successful slice selection match. In an implementation of the present disclosure, the UE [102] may be configured to function in conjunction with the system [300].
15
[0094]
In order to authorise the user equipment (UE) registration request, the processor may be configured to fetch, from a Network Slice Selection Function (NSSF) [116], a set of network slice availability authorisation data associated with one or more network slices. Then the processor matches the slice selection request with at least one of the network slice availability authorisation data from the set of 20 network slice availability authorisation data. The processor then identifies an unsuccessful slice selection match associated with the user equipment registration request. The processor may then transmit, to the NSSF [116], at least the slice selection request based on the unsuccessful slice selection match. The processor may also fetch, from the NSSF [116], an updated set of network slice availability 25 authorisation data. Also, the processor identifies a successful slice selection match for the slice selection request, based on the updated set of network slice availability authorisation data. The processor then registers at the AMF [106] the user equipment (UE) registration request based on the successful slice selection match.
30
28
[0095]
The present disclosure further discloses a non-transitory computer readable storage medium storing one or more instructions for registering a user equipment (UE) [102], the one or more instructions include executable code which, when executed by one or more units of a system [300], causes the one or more units to perform certain functions. The one or more instructions when executed causes a 5 transceiver unit [302] at an access and mobility management function (AMF) [106] of the system [300] to receive a user equipment (UE) registration request comprising a slice selection request from the UE [102]. The one or more instructions when executed further causes a processing unit [304] at the AMF [106] of the system [300] to match at least one parameter within the slice selection request 10 with at least one of a network slice availability authorisation data from a set of network slice availability authorisation data. The one or more instructions when executed further causes the processing unit [304] at the AMF [106] to identify an unsuccessful slice selection match associated with the user equipment (UE) registration request. The one or more instructions when executed further causes the 15 transceiver unit [302] to transmit from the AMF [106] to a network slice selection function (NSSF) [116], at least the slice selection request based on the unsuccessful slice selection match. The one or more instructions when executed further causes the transceiver unit [302] at the AMF [106] to fetch an updated set of network slice availability authorisation data from the NSSF [116]. The one or more instructions 20 when executed further causes the processing unit [304] at the AMF [106] to identify a successful slice selection match for the slice selection request, based on the updated set of network slice availability authorisation data. The one or more instructions when executed further causes the processing unit [304] at the AMF [106] to register the user equipment (UE) registration request based on the 25 successful slice selection match.
[0096]
As is evident from the above, the present disclosure provides a technically advanced solution for registering a user equipment (UE). The present solution provides a transformative shift instead of outrightly rejecting registration requests 30 when the Access and Mobility Management Function (AMF) encounters
29
insufficient data to make an informed slice selection decision. By querying the
Network Slice Selection Function (NSSF) for assistance, even in cases where the AMF is designed to locally determine slice selection, the registration success rate sees remarkable improvement. This dynamic strategy allows for seamless adaptation in scenarios where data limitations hinder independent slice selection by 5 the AMF. As a result, the network gains higher resilience and flexibility, ensuring that registration requests are more likely to be accommodated successfully. This innovative approach represents a substantial advancement in 5G Core network management, emphasizing adaptability and cooperation among network components to enhance user experience and optimize resource allocation. 10
[0097]
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 15 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.
[0098]
Further, in accordance with the present disclosure, it is to be acknowledged 20 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 25 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.

We Claim:

1.A method for registering a user equipment (UE) [102], the method comprising:
-
receiving, by a transceiver unit [302] at an access and mobility management function (AMF) [106] from the UE [102], a user equipment (UE) registration request comprising a slice selection request;
-
matching, by a processing unit [304] at the AMF [106], at least one parameter within the slice selection request with at least one of a network slice availability authorisation data from a set of network slice availability authorisation data;
-
identifying, by the processing unit [304] at the AMF [106], an unsuccessful slice selection match associated with the user equipment (UE) registration request;
-
transmitting, by the transceiver unit [302] from the AMF [106] to a network slice selection function (NSSF) [116], at least the slice selection request based on the unsuccessful slice selection match;
-
fetching, by the transceiver unit [302] at the AMF [106], an updated set of network slice availability authorisation data from the NSSF [116];
-
identifying, by the processing unit [304] at the AMF [106], a successful slice selection match for the slice selection request, based on the updated set of network slice availability authorisation data; and
-
registering, by the processing unit [304] at the AMF [106], the user equipment (UE) based on the successful slice selection match.

2.The method as claimed in claim 1, wherein the method further comprises fetching, by the transceiver unit [302] at the AMF [106] from the NSSF [116],the set of network slice availability authorisation data associated with one or more network slices, wherein the set of network slice availability authorisation data associated with the one or more network slices is received at the AMF [106] from the NSSF [116] when a network startup event associated 30 with a network is detected at the UE [102].

3.The method as claimed in claim 2, wherein the set of network slice availability authorisation data is associated with at least one of the network slice availability authorisation data and one or more tracking area identifiers (TAIs) of the network.

4.The method as claimed in claim 1, wherein the unsuccessful slice selection match is identified at the AMF [106] based on a failure in matching the slice selection request with the set of network slice availability authorisation data.

5.A system [300] for registering a user equipment (UE) [102], the system [300] comprises:
-
a transceiver unit [302], wherein the transceiver unit [302] is configured to:
•
receive, at an access and mobility management function (AMF) [106] from the User equipment (UE) [102], a user equipment (UE) registration request comprising a slice selection request; and
-
a processing unit [304] connected with at least the transceiver unit [302], wherein the processing unit [304] is configured to:
•
match, at the AMF [106], at least one parameter within the slice selection request with at least one of a network slice availability authorisation data from a set of network slice availability authorisation data;
•
identify, at the AMF [106], an unsuccessful slice selection match associated with the user equipment registration request;
wherein the transceiver unit [302] is further configured to:
•
transmit, from the AMF [106] to a network slice selection function (NSSF) [116], at least the slice selection request based on the unsuccessful slice selection match, and
•
fetch, at the AMF [106] from the NSSF [116], an updated set of network slice availability authorisation data; and
wherein the processing unit [302] is further configured to:
•
identify, a successful slice selection match for the slice selection request, based on the updated set of network slice availability authorisation data;
•
register, at the AMF [106], the user equipment (UE) based on the successful slice selection match.

6.The system [300] as claimed in claim 5, wherein the transceiver unit [302] is further configured to fetch, at the AMF [106], from the NSSF [116], the set of network slice availability authorisation data associated with one or more network slices, wherein the set of network slice availability authorisation data associated with the one or more network slices is received at the AMF [106] 10 from the NSSF [116] when a network startup event associated with a network is detected at the UE [102].

7.The system [300] as claimed in claim 6, wherein the set of network slice availability authorisation data is associated with at least one of the network slice 15 availability authorisation data and one or more tracking area identifiers (TAIs) of the network.

8.The system [300] as claimed in claim 5, wherein the unsuccessful slice selection match is identified at the AMF [106] based on a failure in matching the slice 20 selection request with the set of network slice availability authorisation data.

9.A user equipment (UE) [102], comprising:
a processor configured to:
send a user equipment (UE) registration request comprising a slice 25 selection request to an AMF [106];
receive authorisation of the user equipment (UE) registration request from the AMF [106] based on a successful slice selection match, wherein to authorise the user equipment (UE) registration request, the processor is configured to:

fetch, from a Network Slice Selection Function (NSSF) [116], a set of network slice availability authorisation data associated with one or more network slices,
match the slice selection request with at least one of the network slice availability authorisation data from the set of network 5 slice availability authorisation data;
identify an unsuccessful slice selection match associated with the user equipment registration request;
transmit, to the NSSF [116], at least the slice selection request based on the unsuccessful slice selection match, and
fetch, from the NSSF [116], an updated set of network slice availability authorisation data;
identify, a successful slice selection match for the slice selection request, based on the updated set of network slice availability authorisation data; and
register, at the AMF [106], the user equipment (UE) based on the successful slice selection match.

Dated this the 5th Day of September, 2023