Methods and systems for prioritizing a PLMN selection for a prioritized UE-service

Abstract

Embodiments herein disclose methods and systems for determining a prioritized PLMN for obtaining at least a required S-NSSAI service for a UE-Application in use. A UE (102) is on the first PLMN (PLMN-1) (104) which can support a network slice-x for a UE-Application1, but first PLMN (PLMN-1) (104) is an unprioritized PLMN for the network slice-x. As per network it is recommended for the UE (102) to use third PLMN (PLMN-3) (108) for the network slice-x. When a user closes the UE-Application1 and immediately opens a new UE-Application2 the UE (102), determines a prioritized Application between the Application1 and the Application2, using a reinforced learning on probability of occurrence of Applications. Based, on the determined prioritized Application a PLMN is prioritized for at least one required S-NSSAI accession.

Description

METHODS AND SYSTEMS FOR PRIORITIZING A PLMN SELECTION FOR A PRIORITIZED UE-SERVICE

[0001] Embodiments disclosed herein relate to the field of wireless communication network, and more particularly to methods and systems for prioritizing a Public Land mobile network (PLMN) selection for a prioritized UE-service.

[0002] In general, only a User Equipment (UE) (102) supporting slice based Steering of Roaming (SoR) feature can receive an enhanced slice-aware SoR information via a Unified Data Management (UDM) entity, wherein the enhanced slice aware information includes preferred Public land mobile networks (PLMNs) for specific Single-Network slice selection information (S-NSSAIs) in a UE (102) subscription. A preferred PLMN list may be a single PLMN that is known by Home PLMN (HPLMN) to support the S-NSSAI, or a list of PLMNs in preference order that differs from the order of the basic SoR information that is also provided.

[0003] Network provides Enhanced Slice Aware SoR information list to help the UE (102) to select or prioritize PLMN based on Services or Slices support. UE (102) may prioritize PLMNs from Slice Aware SoR information list based on UE requirement. Slice Aware SoR information list provides a prioritized PLMN list for each S-NSSAI from which UE (102) may consider a weighted Approach if it needs multiple S-NSSAIs and multiple PLMNs has different priority for each S-NSSAI support. For example if enhanced Slice aware SoR information list has below information:

[0004] S-NSSAI-1: PLMN-1, PLMN-2

[0005] S-NSSAI-2: PLMN-2, PLMN-1

[0006] From the above Slice aware SoR information list UE (102) will consider that a first PLMN (PLMN-1) (104) has higher priority compared to a second PLMN (PLMN-2) (106) when it requires service of S-NSSAI-1. Whereas, the UE (102) will consider the second PLMN (PLMN-2) has higher priority compared to the first PLMN (PLMN-1) (104) when the UE (102) will require service for S-NSSAI-2.

[0007] With support of enhanced Slice Aware SoR information the UE (102) can choose different PLMN for different S-NSSAI(s) as each PLMN can have different priority for a required or a requested S-NSSAI for the UE. However, several drawbacks existing with this current technique of PLMN selection, includes:

[0008] How the UE (102) can decide on the required S-NSSAIs and thus affect a PLMN selection or re-selection.

[0009] How a user of the UE (102) or a network can control the required or requested S-NSSAIs so the right PLMN can be chosen.

[0010] How to select an S-NSSAI when two different S-NSSAIs required by the UE (102) cannot be served by same PLMN.

[0011] Drawbacks in the existing PLMN selection technology are further illustrated through the following figures.

[0012] Problem 1: FIG.s 1A, 1B are respectively a flow chart and a sequence diagram depicting a method for accessing an S-NSSAI from a non-prioritized PLMN, when at least one prioritized PLMN is available.

[0013] At step 102, the method comprises registering by a UE (102) with a first PLMN (PLMN-1) (104). The first PLMN (104) supports a plurality of network slices under a plurality of S-NSSAIs. The UE (102) receives form a network of HPLMN (Home PLMN) an enhanced slice aware information containing a plurality of S-NSSAI supports such as, a first S-NSSAI (S-NSSAI-1), a second S-NSSAI (S-NSSAI-2), and a third S-NSSAI (S-NSSAI-3). Based on the enhanced slice aware information, the UE (102) registers with the first PLMN (104), upon determining that, the first PLMN (PLMN-1) (104) is a prioritized PLMN for the UE (102) for a network slice, to be accessed by the UE (102).

[0014] At step 104, the method comprises using by the UE (102) an application (third application (app3)), wherein the third application uses a network slice x for which a third PLMN (PLMN-3) (108) is prioritized as per the enhanced slice aware SoR information.

[0015] At step 106, the method comprises reselecting by the UE (102) a third PLMN (PLMN-3) (108) as per the enhanced slice aware SoR information. .

[0016] At step 108, the method comprises, closing by a user of the UE (102), the app3 that the UE (102) is using and opens a new application (first application (app1)).

[0017] At step 110, the method comprises reselecting by the UE (102) the first PLMN (PLMN-1) (104) as per the enhanced SoR information received by the UE (102) form the network (112), wherein the SoR information comprises information on, the plurality of S-NSSAIs configured by a plurality of PLMNs, and at least one prioritized PLMN corresponding to each of the plurality of S-NSSAIs.

[0018] At step 112, the method comprises using by the user of the UE (102) both applications (app1 and app3) for which the UE (102) uses two different network slices. In this scenario, the UE (102) shall be registered to one of the first PLMN (PLMN-1) (104) and the third PLMN (PLMN-3) (108). Therefore, at least one of the applications data will not go through a PLMN which is a prioritized PLMN for the application which will lead to bad user experience.

[0019] Therefore, a cycle of PLMN reselections is performed by the UE (102) based on the applications used and user experience is affected as data interruption is observed during the PLMN switches.

[0020] FIG. 1B is the sequence diagram for illustrating the problem 1.

[0021] At step 1, the UE (102) has successfully registered with a network and the network (such a UDM (112) of the network) shares the enhanced slice aware SoR information container containing a plurality of S-NSSAI(s) supports (e.g., S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3 along with a plurality of PLMNs over which it is supported and the prioritized PLMN to be chosen while accessing the S-NSSAI.

[0022] At step 2, the UE (102) determines its required network slices by using pre configuration if available on the UE (102) or using UE (102) local policies or UE (102) configurations or UE (102) Applications.

[0023] At step 3, the UE (102) NAS layer selects S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3 as required network slices for the UE (102) based on, such as, a user equipment route selection policy (URSP) configuration or NSSAI configuration.

[0024] At step 4, the UE (102) sends a Registration request towards a network of a first PLMN (PLMN-1) (104) with the S-NSSAI(s) that is required by including in Registration Request message. The registration request message includes registration request for S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3, as the first PLMN (PLMN-1) (104) is prioritized by an UDM (112) for S-NSSAI-1 and S-NSSAI-2 and it can also support S-NSSAI-3.

[0025] At step 5, the network of first PLMN (PLMN-1) (104) accepts the UE registration request and adds S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3 as Allowed NSSAI. The UE (102) has successfully registered with network and accessing the services from the network of first PLMN (PLMN-1) (104).

[0026] Therefore, issue with the existing technology is that, the UE (102) has opened only one Application that requires S-NSSAI-3 to be established. UE (102) is on first PLMN (PLMN-1) (104) and using S-NSSAI-3 for accessing service. But as per network it is recommended for the UE (102) to use third PLMN (PLMN-3) (108) for S-NSSAI-3. But, none of the UE (102) and the network can determine, reselection by the UE (102) to third PLMN (PLMN-3) (108). A user experiences bad services as the Application currently open in the UE, requires an S-NSSAI that is not prioritized for the PLMN with which the UE (102) is registered. Therefore, problem lies in which S-NSSAI the UE (102) need to give priority when the UE (102) is using two S-NSSAIs that were prioritized over different PLMNs.

[0027] FIG. 1C is a diagram depicting a plurality of S-NSSAIs, wherein each S-NSSAI is configured by a PLMN and support one or more UE-services. Further, a plurality of UE-services are depicted, wherein one or more UE-service of the plurality of UE-service, are using at least one S-NSSAIs.

[0028] Problem 2: FIG.s 2A, 2B are respectively a flow chart and a sequence diagram depicting a problem scenario with the existing PLMN selection technique used by the UE, wherein the UE (102) is registered with a PLMN that uses an application for which a required network slice is not supported by the PLMN.

[0029] At 202, the method comprises registering by the UE (102) with a first PLMN (PLMN-1) (104), wherein the first PLMN (104) supports a network slice-1 (S-NSSAI-1) and does not support any other network slices.

[0030] At 204, the method comprises using by the UE (102) uses an application (e.g. a first application (App1)), wherein the first application uses the slice S-NSSAI-1 and the first PLMN (PLMN-1) (104) is a prioritized PLMN for the first application. The UE determines the prioritized PLMN, based on an enhanced slice aware SoR information received from a network of HPLMN.

[0031] At 206, the method comprises sustaining registration by the UE (102) on the first PLMN (PLMN-1) (104) as it is a prioritized PLMN for the first application as informed to the UE (102) through the enhanced slice aware SoR information.

[0032] At 208, the method comprises opening by a user of the UE (102) a new Application (App3) which requires a network slice 3.

[0033] At 210, the method includes as the first PLMN (PLMN-1) (104) to which the UE (102) is registered, does not support the network slice 3 and hence if user does not select the right PLMN the services for app3 may not be available or provided by default network slice which doesn't guarantee a required Quality of service (QoS) for the user.

[0034] FIG. 2B is a sequence diagram for illustrating the problem 2.

[0035] At step 1, the UE (102) is successfully registered with the network and the network (such as an UDM) shares with the UE (102) the enhanced slice aware SoR information container containing information of a plurality of S-NSSAI(s) support along with corresponding a plurality of PLMNs, wherein each PLMN over which each S-NSSAI is supported, has a network (UDM) configured priority index. The UE (102) while accessing an S-NSSAI, chooses a PLMN prioritized with the priority index.

[0036] At step 2, the UE (102) determines its required network slices for a current application open, by using a pre-configuration S-NSSAI information or allowed S-NSSAI information available on the UE, or using UE local policies, or using UE local configurations, or using UE local applications.

[0037] At step 3, the UE NAS layer selects S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3 as required network slices for the UE (102) based on the S-NSSAI configuration (URSP configuration).

[0038] At step 4, the UE (102) sends a NAS message such as for example registration request message towards the network first PLMN (PLMN-1) (104) with the required S-NSSAI-1 included in Registration Request message (RRM) (e.g. RRM configuration: S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3) because first PLMN (PLMN-1) (104) is prioritized by network for S-NSSAI-1.

[0039] At step 5, the network of first PLMN (PLMN-1) (104) accepts the UE registration request and adds S-NSSAI-1 as an allowed S-NSSAI. The UE (102) is successfully registered with network now accessing the services from the network first PLMN (PLMN-1) (104).

[0040] Therefore, the UE has opened an application or started a service that required S-NSSAI-3 to be established. But, the UE (102) is on PLMN1 and uses S-NSSAI-1. But as per the network S-NSSAI-3 is not available in first PLMN (PLMN-1) (104) and UE uses a default slice from first PLMN (PLMN-1) (104) for the new application data leading to poor user experience. Further, first PLMN (PLMN-1) (104) may not have a configuration to support the new application in required QoS.

[0041] Problem 3: FIG.s 3A, 3B are respectively a flow chart and a sequence diagram, depicting a scenario where the UE (102) performs frequent reselections of various PLMNs, due to which the UE (102) suffers from draining in battery power.

[0042] At 302, the method comprises registering by theUE (102) on a network of a first PLMN (PLMN-1) (104) that supports all the network slices (such as S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3) and prioritized for the first PLMN (PLMN-1) (104) for an Application running in the UE.

[0043] At 304, the method comprises using by the UE (102) only one application (such as a third application (App3)), wherein the third application uses a slice x and a third PLMN (PLMN-3) (108) is prioritized PLMN for that Application as per enhanced slice aware SoR information.

[0044] At 306, the method comprises reselecting by the UE (102) the third PLMN (PLMN-3) (108) as per the enhanced slice aware SoR information.

[0045] At 308, the method comprises closing by a user of the UE (102) the third application and opening a new App (such as application 1 (app1).

[0046] At 310, the method comprises reselecting by the UE (102) the first PLMN (PLMN-1) (104), as per the enhanced slice aware SoR information.

[0047] FIG. 3B is a sequence diagram for illustrating problem 3.

[0048] At step 1, the UE (102) has successfully registered with the network and network (e.g. UDM) shares the enhanced slice aware SoR information container containing information on a plurality of S-NSSAI(s) support along with a plurality of PLMNs over which the plurality of S-NSSAI(s) are supported and the prioritized PLMN to be chosen while accessing the S-NSSAI.

[0049] At step 2, the UE (102) determines its required network slices by using a pre-configuration NSSAI information, or an allowed NSSAI information if available on the UE, or using UE local policies such a UE configuration, a UE application.

[0050] At step 3, the UE NAS layer selects S-NSSA-1, S-NSSAI-2 and S-NSSAI-3 as required network slices for the UE (102) based on a NSSAI configuration (or, an URSP configuration).

[0051] At step 4, the UE (102) sends a NAS message such as for example a Registration request message towards a network of first PLMN (PLMN-1) (104) with the required S-NSSAI(s) by including in the Registration Request message. (Example: S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3) because first PLMN (PLMN-1) (104) is prioritized by network for S-NSSAI-1.

[0052] At step 5, the network of first PLMN (PLMN-1) (104) accepts the UE registration request message and adds S-NSSAI-1 as an allowed NSSAI. The UE (102) has successfully registered with the network and accessing the services from the first PLMN (PLMN-1) (104) network.

[0053] At step 6, the UE (102) opens an application or started a service that requires the S-NSSAI-3 to be established.

[0054] At step 7, the UE NAS layer performs a PLMN selection to select and register on the third PLMN (PLMN-3) (108) to get services from S-NSSAI-3.

[0055] At step 8, the UE (102) opens a new application which is mapped to S-NSSAI-2 to be established or registered.

[0056] At step 9, the UE NAS layer further performs a PLMN selection to select and register on a second PLMN (PLMN-2) (106) to get services from S-NSSAI-2

[0057] Therefore, frequent PLMN selections and registrations by the UE may cause increased power consumption by the UE and also generates lot of signaling on core network to store and retrieve a plurality of UE contexts across a plurality of PLMNs.

[0058] Hence, there is a need in the art for solutions which will overcome the above mentioned drawback(s), among others.

[0059] The principal object of embodiments herein is to disclose methods and systems for prioritizing a PLMN selection based on a prioritized UE-service.

[0060] Another object of embodiments herein is to disclose methods and systems for determining using a reinforced learning (RL) module a required S-NSSAI for a UE-service, at a given time instance and location of a UE.

[0061] Another object of embodiments herein is to disclose methods and systems for identifying a UE is registered on a PLMN that is not prioritized for a current UE-service in use and identifying availability of other PLMN where a required S-NSSAI can be supported with highest priority.

[0062] Another object of embodiments herein is to disclose a method and systems for performing a PLMN search and update a stored list of PLMN search results, using incremental scan in order to use the stored list in evaluating and deciding when a PLMN re-selection is required.

[0063] Another object of embodiments herein is to disclose methods and systems for dynamically and optimally selecting and re-selecting a prioritized PLMN based on a plurality of UE-services simultaneously in use without introducing significant impact on the services.

[0064] Another object of embodiments herein is to disclose methods and systems for identifying a UE entered a location where a higher priority PLMN is available for a prioritized UE-service and automatically re-selects to that PLMN based on enhanced slice aware SoR information.

[0065] Another object of embodiments herein is to disclose methods and systems for choosing and determining selection of a prioritized UE-service from a plurality of UE-services simultaneously in use which requires a PLMN re-selection and avoiding PLMN re-selection for other UE-services.

[0066] Accordingly, the embodiments herein provide, a method for Public land mobile network (PLMN) selection, wherein the method receiving, by a User Equipment (UE), at least, an enhanced slice aware Steering of Roaming (SoR) information from a network. The method further comprises, identifying by the UE a user behaviour pattern of a network slice usage for a service currently used by the UE (102). Further, the method comprises, determining, by the UE, whether the UE is registered on a prioritized PLMN for the service currently used by the UE based on the enhanced slice aware SoR information and the user behaviour pattern of the network slice usage. The method further comprises, performing, by the UE, one of: using the current PLMN in response to determining that the UE is registered on the prioritized PLMN for the service currently used by the UE, and modifying a required network slice in response to determining that the UE is not registered on the prioritized PLMN for the service currently used by the UE.

[0067] Accordingly embodiments herein provide, a UE comprising a processor, a memory and a reinforced learning module, wherein the processor is configured to receive, at least one of: an enhanced slice aware Steering of Roaming (SoR) information from a network. Further, the processor of the UE is configured to identify a user behaviour pattern of a network slice usage for a service currently used by the UE. The processor is further configured to determine, whether the UE is registered on a prioritized PLMN for a service currently used by the UE, based on the enhanced slice aware SoR information and the user behaviour pattern of the network slice usage. The processor is further configured to perform, one of: using the current PLMN in response to determining that the UE is registered on the prioritized PLMN for the service currently used by the UE and modify a slice in response to determining that the UE is not registered on the prioritized PLMN for the service currently used by the UE.

[0068] These and other aspects of the example embodiments herein will be better Appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating example embodiments and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the example embodiments herein without departing from the scope thereof, and the example embodiments herein include all such modifications.

[0069] Advantages of the Proposed Solutions are i) UE is always registered on the best possible PLMN based on the S-NSSAIs being used. ii) Performing PLMN re-selection only when required and avoid un necessary PLMN re-selections and reducing overall UE and network signaling and enhanced battery savings. iii) Solutions with or without user knowledge and network dependence.

[0070] Embodiments herein are illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the following illustratory drawings. Embodiments herein are illustrated by way of examples in the accompanying drawings, and in which:

[0071] FIGs 1A-1B are respectively a flow chart and a sequence diagram, depicting a method for accessing a S-NSSAI from a non-prioritized PLMN, when at least one prioritized PLMN is available, according to existing arts;

[0072] FIG. 1C is a diagram depicting a plurality of S-NSSAIs, wherein each S-NSSAI is configured by a PLMN and support one or more UE-services, according to existing arts;

[0073] FIGs 2A-2B respectively a flow chart and a sequence diagram, depict a problem scenario with the existing PLMN selection technique used by the UE, wherein the UE is registered with a PLMN that uses an application for which a required network slice is not supported by the PLMN, according to existing arts;

[0074] FIGs 3A-3B respectively a flow chart and a sequence diagram, depict a scenario where the UE performs frequent reselections of various PLMNs, due to which the UE suffers from draining in battery power, according to existing arts;

[0075] FIG. 4 are block diagrams depicting a system comprising a UE and a network for prioritizing a PLMN selection for a prioritized UE-service, according to the embodiments disclosed herein;

[0076] FIG. 5 is a flow diagram depicting a method for prioritizing a PLMN selection for a prioritized UE-service, according to embodiments as disclosed herein;

[0077] FIG. 6 is a flowchart depicting an example method for determining when a change in PLMN is required for a UE-service currently used by a user, according to embodiments as disclosed herein;

[0078] FIG. 7A is a flow diagram depicts a method for a user-based selection of prioritized Applications and prioritizing a S-NSSAI and a PLMN, when the prioritized PLMN does not support a plurality of network slices, according to embodiments as disclosed herein;

[0079] FIG. 7B is a diagram, depicting a user can select one or more Applications through a user interface of the UE, according to embodiments as disclosed herein;

[0080] FIG. 8 depicts a flow diagram, of a method for network based S-NSSAI selection and prioritization for a prioritized UE-service, according to various embodiments as disclosed herein;

[0081] FIG. 9 is a flow diagram depicting a method for a PLMN selection, according to embodiments as disclosed herein; and

[0082] FIG. 10 is a sequence diagram depicting a method for selecting by a UE, a network of prioritized PLMN for transmitting a registration request, based on a current application used by the UE, according to embodiments as disclosed herein.

[0083] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.

[0084] For the purposes of interpreting this specification, the definitions (as defined herein) will apply and whenever appropriate the terms used in singular will also include the plural and vice versa. It is to be understood that the terminology used herein is for the purposes of describing particular embodiments only and is not intended to be limiting. The terms "comprising", "having" and "including" are to be construed as open-ended terms unless otherwise noted.

[0085] The words / phrases "exemplary", "example", "illustration", "in an instance", "and the like", "and so on", "etc.", "etcetera", "e.g.," , "i.e.," are merely used herein to mean "serving as an example, instance, or illustration." Any embodiment or implementation of the present subject matter described herein using the words / phrases "exemplary", "example", "illustration", "in an instance", "and the like", "and so on", "etc.", "etcetera", "e.g.," , "i.e.," is not necessarily to be construed as preferred or advantageous over other embodiments.

[0086] Embodiments herein may be described and illustrated in terms of blocks which carry out a described function or functions.　These blocks, which may be referred to herein as managers, units, modules, hardware components or the like, are physically implemented by analog and / or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and may optionally be driven by a firmware. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like.　The circuits constituting a block may be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuitry), or by a combination of dedicated hardware to perform some functions of the block and a processor to perform other functions of the block.　Each block of the embodiments may be physically separated into two or more interacting and discrete blocks without departing from the scope of the disclosure.　Likewise, the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of the disclosure.

[0087] It should be noted that elements in the drawings are illustrated for the purposes of this description and ease of understanding and may not have necessarily been drawn to scale. For example, the flowcharts / sequence diagrams illustrate the method in terms of the steps required for understanding of aspects of the embodiments as disclosed herein. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the present embodiments so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Furthermore, in terms of the system, one or more components / modules which comprise the system may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the present embodiments so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

[0088] The accompanying drawings are used to help easily understand various technical features and it should be understood that the embodiments presented herein are not limited by the accompanying drawings. As such, the present disclosure should be construed to extend to any modifications, equivalents, and substitutes in addition to those which are particularly set out in the accompanying drawings and the corresponding description. Usage of words such as first, second, third etc., to describe components / elements / steps is for the purposes of this description and should not be construed as sequential ordering / placement / occurrence unless specified otherwise.

[0089] The embodiments herein provide methods and systems for prioritizing a PLMN selection for a prioritized UE-service. Referring now to the drawings, and more particularly to FIG.s 4 through 9, where similar reference characters denote corresponding features consistently throughout the figures, there are shown embodiments. In this specification the terminologies "UE-service", "service in use", "Application in use", "Application", "UE- Application" are used interchangeably.

[0090] FIG. 4 is a block diagram of a system comprising a UE (102) and a network (404) for prioritizing a PLMN selection for a prioritized UE-service, according to the embodiments disclosed herein. As shown in FIG. 4, the UE (102) is communicating with the network (404), wherein the network (404) is a wireless network. In an embodiment herein, the network (404) comprises, a group of Public land mobile networks (PLMNs), wherein each group of PLMNs includes such as a home PLMN (HPLMN) (422), a first PLMN (PLMN-1) (104), a second PLMN (PLMN-2) (106), a third PLMN (PLMN-3) (108), a visitor PLMN (VPLMN) (not shown) and so on. The UE (102) is communicating with the at least one PLMN of the group of PLMNs configured within the network (402), based on a requirement of an application currently in use.

[0091] In an embodiment herein, the wireless network (402) can be, for example, but not limited to a fourth generation (4G) network, a fifth generation (5G) network, a 6G network, an Open Radio Access Network (ORAN) or the like. Each PLMN of the network (404), can include an Access and Mobility Management Function (AMF) layer, and a Unified Data Management (UDM) layer with respect to data communication and mobility. Further, each PLMN of the network (404), can include gNB, a eNB, a new radio (NR) trans-receiver or the like.

[0092] In an embodiment herein, The UE (102) can be a portable mobile device such as an electronic equipment with communication facility designed to serve as a medium for facilitating virtual interaction with a network. Further, the UE (102) can be operated by an authenticated user is a portable electronic device, such as a portable computer, a computing device, a laptop, a smart phone, a desktop computer, a notebook, a Device-to-Device (D2D) device, a vehicle to everything (V2X) device, a foldable phone, a smart TV, a tablet, an immersive device, and an internet of things (IoT) device etc. In an embodiment herein, the UE (102) can comprise at least, a processor (412), a memory (414), and a reinforced based learning module (416) and a communication module (418). The UE (102) further, can include functionality for communicating with the network (404) through the communication module (328). In an example embodiment, the UE (102) can be a Smart Phone (iPhone, Android phone, Windows phone and so on), a conventional web-enabled portable computers, a tablet computer or another device capable of communicating through communication module (328) to connect internet or any other conventional network.

[0093] In an embodiment herein, the processor (412) can be configured to receive an enhanced slice aware Steering of Roaming (SoR) information from a network, wherein the enhanced slice aware information comprises information comprising, a plurality of Single - Network Slice Selection Assistance Information (S-NSSAIs), and a plurality of Public Land mobile networks (PLMNs) of the group of PLMNs supporting the plurality of S-NSSAIs, wherein an individual S-NSSAI of the plurality of S-NSSAIs, is configured by at least one PLMN prioritized for the UE (102) . In an embodiment herein, the processor (412) can obtain user behavior pattern of a slice usage as determined using the reinforced learning module. In an embodiment herein, the processor (412) can be configured to determine, whether the UE (102) is registered on a prioritized PLMN for a service currently used by the UE based on at least, the enhanced slice aware SoR information and the user behavior pattern of a slice usage. In an embodiment herein, the processor (412) can be configured to perform, one of : using a current PLMN, in response to determining that the current PLMN that the UE (102) is registered on is the prioritized PLMN for the service currently used by the UE (102) and modify a network slice in response to determining that the UE (102) is not registered on the prioritized PLMN for the service currently used by the UE. In an embodiment herein, the processor (412) can be configured to determine priority of the service currently used by the UE (102) using the reinforced learning module (416). Further, in an embodiment herein, the processor (412) can be configured to select at least one PLMN prioritized for the UE (102) (402), along with at least one configured S-NSSAI among the plurality of S-NSSAIs, based on the determined priority of the service currently used by the UE (102) (402).

[0094] In an embodiment herein, the processor (412) can include analog and / or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and may optionally be driven by firmware.

[0095] The processor (412) may further, include one or a plurality of processors. The one or the plurality of processors may be a general-purpose processor, such as a central processing unit (CPU), an Application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and / or an AI-dedicated processor such as a neural processing unit (NPU). The processor (412) may include multiple cores and is configured to execute the instructions stored in the memory (414).

[0096] Further, the processor (412) is configured to execute instructions stored in the memory (414) and to perform various processes. The communication module (418) is configured for communicating internally between internal hardware components of the UE (102) and with the network (404). The memory (414) can also store instructions to be executed by the processor (412). The memory (414) may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory (414) may, in some examples, be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be interpreted that the memory (414) is non-movable. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache).

[0097] In an embodiment, the communication module (418) includes an electronic circuit specific to a standard that enables wired or wireless communication. In an example embodiment herein, the communication module (616) may include at least one of the Internet, a wired network (a Local Area Network (LAN), a Controller Area Network (CAN) network, a Universal Asynchronous Receiver / Transmitter (UART), a bus network, Ethernet and so on), a wireless network (a Wi-Fi network, a cellular network, a Wi-Fi Hotspot, Bluetooth, Zigbee and so on using Wireless Application Protocol), a direct interconnection, and so on.

[0098] In an embodiment herein, the reinforced learning (RL) module (416) of the UE (102) is used to identify a plurality of required slice (S-NSSAI) for the UE (102) using a plurality of Applications simultaneously at any given time instance and at a location. In an embodiment herein, the RL module (416), can evaluate the enhanced slice aware SoR information received from the network based on the identified slices S-NSSAIs required for the plurality of Applications, in order to select a prioritized PLMN for transmitting a registration request. In an embodiment herein, the learning will be based on below parameters such as but not limited to the plurality of Applications in use, configuration of a plurality of slices S-NSSAI in a plurality of URSPs, S-NSSAI to PLMN priority as per the enhanced slice aware SoR information, category of the plurality of Applications, QOS characteristics of the plurality of Applications, usage pattern such as time and duration of usage of the plurality of Applications and so on. In an embodiment herein, the RL module can estimate a probability of occurrence of the plurality of Applications simultaneously used by the UE, based on the learnt parameters. In an embodiment herein, based on the estimation the RL module (416) can evaluate the required slices S-NSSAIs and the enhanced SoR information in order to determine a prioritized PLMN to be registered by the UE (102) (402).

[0099] In an embodiment herein, the RL module (416) is updated every time when an application is opened or re-opened. At any given time the plurality of required S-NSSAI and a prioritized PLMN is selected by the UE (102) using usage characteristics of the plurality of Applications.

[0100] In an example embodiment herein, the RL module (416) based S-NSSAI and PLMN selection includes estimating probability of occurrence of a plurality of applications in a plurality of network slices (S-NSSAIs). Estimating the probability of occurrence of a plurality of applications in the plurality of network slices uses the following technique:

[0101] The UE (102) is initially requesting a plurality of network slices such as S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3, based on a pre-configured enhanced SoR information received from a HPLMN, wherein each S-NSSAI is assigned with at least one application. Further, each S-NSSAI can be assigned with multiple applications. In an embodiment herein, an event of triggering of an Application at any given time-stamp, is counted as 1. Further, when an Application is not triggered for any given time-stamp the RL module count the event as 0. The conditions which are considered for setting a triggering event as count 1 are, time duration of the application used and QOS that is being used by app (such as data rate and so on). Usage probability of an Application using a slice is illustrated in a simplified manner in the following table:

[0102] In order to find the probability distribution of the occurrence of the application in any specific slice (Slice-1, Slice-2, ... Slice-N), an expected reward (called as action-value function) is computed by the RL Module, wherein the expected reward is defined as,

[0103]

[0104] Where in Equation (1), r represents the reward value per action, Q(a) represents the average reward for each action at a time t with action a.

[0105] The action values for each action for each time stamp is determined as,

[0106]

[0107] In an aspect, the action is modelled as the occurrence of application in each slice (as given in the table) as distribution function at a time instance that maximises equation (2), given by:

[0108]

[0109] Math Figure Ri represents the reward value for the time instance i.

[0110] To decide which slice will be utilized further, a user- defined threshold value of probability distribution is mapped with the occurrence of distribution of the application (weightage Wi):

[0111] If the Wi is >= Threshold value, then the slice will be further mapped to another group of slice; and

[0112] If the Wi is <=Threshold value, the slice can be used a default slice in present group of slice.

[0113] Based on the usage of the Application the RL module (416) can decide whether to continue using of the current PLMN though it is not prioritized for an S-NSSAI or a PLMN according to an enhanced Slice aware SoR information which is chosen.

[0114] FIG. 5 is depicting a flow diagram of a method for prioritizing a PLMN selection for a prioritized UE-service, according to embodiments as disclosed herein.

[0115] At step 502, the method comprises registering by the UE (102) to a network of a first PLMN (PLMN-1) (104) which supports a plurality of network slices such as S-NSSAI-1, S-NSSAI-2, S-NSSAI-3, and so on, wherein the network of first PLMN (PLMN-1) (104) is a prioritized PLMN for the UE. The UE (102) uses a UE-service (e.g first application (APP-1)). In an embodiment herein, the UE, determines the first PLMN (PLMN-1) (104) as the prioritized PLMN based on evaluation of a pre-configured enhanced SoR information received from a HPLMN, wherein the pre-configured enhanced SoR information comprises information on a required network slice for the first Application, configured by the first PLMN (PLMN-1) (104) with highest priority.

[0116] At step 504, the method comprises receiving by the UE (102) from the HPLMN (such as an UDM of the HPLMN and so on) an enhanced slice aware SoR information comprising information on a plurality of network slices or S-NSSAI(s), a plurality of PLMNs supporting the plurality of network slices, and priority of the plurality of PLMNs for each network slice. In an example embodiment herein, the enhanced slice aware SoR information contains:

[0117] [{S-NSSAI-1: PLMN-1 Prio 1,

[0118] PLMN-2 Prio 2,

[0119] PLMN-3 Prio 3},

[0120] {S-NSSAI-2 : PLMN-1 Prio 1,

[0121] PLMN-3 Prio 2,

[0122] PLMN-2 Prio 3},

[0123] {S-NSSAI-3 : PLMN-3 Prio 1,

[0124] PLMN-2 Prio 2,

[0125] PLMN-1 Prio 3} ]

[0126] At step 506, the method comprises opening by the UE (102) a new Application (third application (App-3)) which uses a network slice x and a third PLMN (PLMN-3) (108) is a prioritized PLMN, corresponding to the network slice x. In an embodiment herein, the UE (102) uses the network slice x based on information of, a HPLMN pre-configured S-NSSAI, or an available allowed NSSAI for the UE, or UE local policies such as a UE configuration or a UE application, and so on.

[0127] At step 508, the method comprises reselecting by the UE (102) to the third PLMN (PLMN-3) (108) based on the received enhanced slice aware SoR information.

[0128] At step 510, the method comprises opening by the UE, an old UE-service or the first application (App1) at a time instance, wherein the first application uses a pre-configured network slice for which the first PLMN (PLMN-1) (104) is prioritized.

[0129] At step 512, the method comprises determining by the UE (102) comprising a reinforced learning module, that the first application may not be used for long duration for example the app may exchange few messages with server or user uses the app for just few seconds / minutes as configured and learnt in the model. hence, the first application is not a prioritized app as compared to the third application for the user at the time instance. In an embodiment herein, the reinforced learning module, is configured to receive form the HPLMN, at least, a plurality of URSP rules, the enhanced slice aware SoR information, user preference for a UE-service (Application), Application usage pattern, and QoS of an Application used by the UE. In an embodiment herein, the reinforced learning module can generate a prioritized Application for the UE (102) with respect to the time instance and a prioritized PLMN with respect to the prioritized App, wherein the prioritized PLMN supporting a network slice configured by the HPLMN for providing service to the UE (102) with respect to the prioritized App.

[0130] At step 514, the method comprises continuing by the UE (102) data accession from the third PLMN (PLMN-3) (108) and avoiding reselection to the first PLMN (PLMN-1) (104). As the first application is used by the UE (102) for a negligible time period as determined by the reinforced based module. Therefore, the UE (102) sustaining registration to the third PLMN (PLMN-3) (108), when the UE (102) is using the first application and the third application simultaneously for a given time period, and determines App3 is a prioritized App. Therefore, only the non-preferred App1 data is throttled.

[0131] FIG. 6 is a flowchart depicting an example method for determining when a change in PLMN is required for a UE-service currently used by a user, according to embodiments as disclosed herein.

[0132] At step 602, the method comprises registering by a UE (102) to a PLMN and using at least one S-NSSAI.

[0133] At step 604, the method comprises checking by the UE (102) (402), if a condition to evaluate the registered PLMN is satisfied. In an embodiment herein, the condition to evaluate the registered PLMN can be at least one of a condition includes, a new application opened by a user, an application closed by the user, the UE (102) received new slice aware SoR information container, the UE (102) received configuration update command with change in allowed NSSAI list, the UE (102) or a Network (404) established or disconnected a Packet data unit (PDU) session over a S-NSSAI, and the UE (102) is registered over another access in same or different PLMN.

[0134] At step 606, the method comprises at least one of: determining by the UE (102), if a change in PLMN for a new registration is required, when the condition to evaluate a registered PLMN is satisfied, and accessing by the UE (102), services from the registered PLMN, when the condition to evaluate the registered PLMN is not satisfied.

[0135] In an embodiment herein, determination of a change in the PLMN for a new registration is required, is performed based on at least one of, a new App opened by the user required a S-NSSAI from different PLMN, a new App opened by the user has an average weightage computed is more or equal to current Apps under use, the UE (102) registered on a different network access than the current network access (such as 3GPP / N3GPP) and both supports different set of S-NSSAIs, the UE (102) registered over another access in different PLMN and supported S-NSSAI(s) are different, and a User or a network or a UE (102) has changed the priority for a S-NSSAI.

[0136] Further, in an embodiment herein, determination of a change in the PLMN for a new registration is not required, is performed based on at least one of, an SoR CMCI (CICS management client interface) timer is running, a new app opened by user doesn't have any slice configured, average weight computed from learning model for the app is at least compared to other apps in use, QoS used by new app doesn't require stringent QOS requirements as per reinforced learnt model.

[0137] At step 608, the method comprises, at least one of : sending by the UE (102), a registration request message to a new PLMN with mobility update, when change in the registered PLMN is required, and accessing by the UE (102), services from the registered PLMN, when the change in the registered PLMN is not required.

[0138] FIG. 7A depicts a flow diagram depicts a method for a user-based selection of prioritized Applications and prioritizing a S-NSSAI and a PLMN, when the prioritized PLMN does not support a plurality of network slices, according to embodiments as disclosed herein.

[0139] At step 702, the method comprises registering by a UE (102) a PLMN (a first PLMN (PLMN-1)) (424), wherein the first PLMN (PLMN-1) (104) supports a network slice1 (S-NSSAI-1) but do not support other network slices. The UE (102) receives an enhanced SoR information from a UDM of a HPLMN (422). In an embodiment herein, the SoR information comprises information on configuration of a plurality of S-NSSAI(s), and a plurality of PLMNs supporting the plurality of S-NSSAI(s), and at least one PLMN prioritized for configuring an individual S-NSSAI. In an embodiment herein, the configuration of the plurality of S-NSSAI(s) can be determined by the UDM based on a time zone a location of the UE.

[0140] At step 704, the method comprises using by the UE (102) (402), an application (say first application (app1)) which uses the network slice 1 (S-NSSAI-1). The first PLMN (PLMN-1) (104) is a prioritized PLMN for the app1 as determined by the UE (102) (402). In an embodiment herein, the UE (102) determines the first PLMN (PLMN-1) (104) as the prioritized PLMN for the first application based on information of, a pre-configured S-NSSAI(s), or an available allowed NSSAI for the UE, or UE local policies including a UE configuration or a UE application, and so on.

[0141] At step 706, the method comprises using by the UE (102) registration to the first PLMN (PLMN-1) (104) as it is a prioritized PLMN for the UE (102) and supports the network slice 1.

[0142] At step 708, the method comprises opening by a user a new Application (App3) for a time instance, which requires a network slice-3, wherein the network slice-3 is not supported by the first PLMN (PLMN-1) (104). In an embodiment herein, a UE-NAS layer or a layer which is responsible for selecting a required network slices (S-NSSAI) can utilize information of the Application provided by the user and combine with a plurality of URSP rules configured by the UDM of the HPLMN (422) to the UE (102) with respect to the registered first PLMN (PLMN-1) (104).

[0143] At step 710, the method comprises evaluating by the UE (102) (402), priority of the first application and the third application, in order to determine a prioritized app between the first application and the third application, for the time instance. In an embodiment herein, the prioritized App for the time instance is determined from an RL module (416) and estimating probability of occurrence of the first application and the third application in a required network slice configured by a PLMN.

[0144] At step 712, the method comprises at least one of : performing by the UE (102), a PLMN reselection when the third application is a prioritized application as determined based on the evaluation, and sustaining registration to the first PLMN (PLMN-1) (104), when the first application is a prioritized application as determined based on the evaluation.

[0145] In an embodiment herein, the UE (102) can evaluate the enhanced Slice aware SoR information received from the UDM, based on the determined prioritized Application. Further, in an embodiment herein, the UE (102) can map plurality of URSP rules with the enhanced Slice aware SoR information and the prioritized Application, and obtains the required S-NSSAI present in an allowed NSSAI list and perform a PLMN re-selection when required.

[0146] In an embodiment herein, a user can select separately a plurality of applications to be optimized to get a plurality of S-NSSAI services corresponding to the plurality of Applications any time the app is being used by the user. In an example embodiment herein, the selection of PLMN can be a category based selection for various kind of Applications used by the UE (102) such as, a conversational voice or video applications, an ultra reliable low latency communication (URLLC) applications, a downlink (DL) heavy streaming applications (live session download), an uplink (UL) heavy streaming applications (live session upload), a voice over internet protocol (VOIP) applications (e.g. OTT Apps).

[0147] In an example embodiment herein, FIG. 7B is a diagram, depicting a user can select one or more Applications (user prioritized Applications for various time instances) through a user interface of the UE.

[0148] FIG. 8, depicts a flow diagram of a method for network-based S-NSSAI selection and prioritization for a prioritized UE-service, according to various embodiments as disclosed herein.

[0149] At step 802, the method comprises registering by a UE (102) to a PLMN (a first PLMN (first PLMN (PLMN-1))) (424) which supports a network slice1 but does not support other network slices. The UE (102) receives an enhanced SoR information from a UDM of a HPLMN (422). In an embodiment herein, the enhanced SoR information comprises information on configuration of a plurality of S-NSSAI(s), and a plurality of PLMNs supporting the plurality of S-NSSAI(s), and a prioritized PLMN to be chosen by the UE (102) while accessing each S- NSSAI. In an example embodiment herein, the configuration of the plurality of network S-NSSAI(s) can be determined by the UDM based on a time zone a location of the UE.

[0150] At step 804, the method comprises using by the UE (102) (402), an application (say a first application (App1)) which uses the network slice 1. The first PLMN (PLMN-1) (104) is a prioritized PLMN for the App1 as determined by the UE (102) (402). In an embodiment herein, the UE (402) determines the first PLMN (PLMN-1) (104) as the prioritized PLMN for the App-1 based on information of, a pre-configured S-NSSAI(s), or an available allowed NSSAI for the UE, or UE local policies including a UE configuration or a UE application, and so on.

[0151] At step 806, the method comprises using by the UE registration to the first PLMN (PLMN-1) (104) as it is a prioritized PLMN and supports the network slice 1.

[0152] At step 808, the method comprises opening by a user a new Application (App3) for a time instance, which requires a network slice 3, wherein the network slice 3 is not supported by the first PLMN (PLMN-1) (104). In an embodiment herein, a UE-NAS layer or a layer which is responsible for selecting a required network slices (S-NSSAI) can utilize information of the Application provided by the user and combine with a plurality of URSP rules configured by the UDM to the UE with respect to the registered first PLMN (PLMN-1) (104). In an embodiment herein, priority of a network slice is determined from usage pattern of network slice for a prioritized App, wherein priority of the prioritized App is determined by the UE using a reinforced learning module (416) and is identified by the HPLMN.

[0153] At step 810, the method comprises evaluating by the network (UDM), priority of the network slice 3 and the network slice 1, in order to determine a prioritized network slice between the slice3 and slice1, at the time instance.

[0154] At step 812, the method comprises at least one of : performing by the UE a PLMN reselection when the network Slice 3 is a prioritized network slice as determined based on the evaluation, and sustaining registration by the UE, to the first PLMN (PLMN-1) (104), when the network Slice 1 is a prioritized network slice as determined based on the evaluation.

[0155] FIG. 9 is a flow diagram depicting a method for a PLMN selection, according to embodiments as disclosed herein.

[0156] At step 902, the method comprises, receiving, by a UE (102), at least an enhanced slice aware Steering of Roaming (SoR) information from a network.

[0157] At step 904, the method comprises, identifying by the UE (102) a user behaviour pattern of a network slice usage for a service currently used by the UE.

[0158] At step 906, the method comprises, determining, by the UE, whether the UE is registered on a prioritized PLMN for the service currently used by the UE based on the enhanced slice aware SoR information and the user behaviour pattern of the network slice usage.

[0159] At step 908, the method comprises, modifying by the UE (102), a required network slice in response to determining that the UE is not registered on the prioritized PLMN for the service currently used by the UE. Further, in an embodiment herein, the UE uses the current PLMN in response to determining that the UE (102) is registered on the prioritized PLMN for the service currently used by the UE (102).

[0160] In an embodiment, the method comprises maintaining, by the UE (102), the registration with the prioritized PLMN in response to determining that the UE (102) is registered on the prioritized PLMN supporting a required network slice; and transmitting, by the UE (102), a registration request message to the prioritized PLMN in response to determining that the UE (102) is not registered on the prioritized PLMN for the service currently used by the UE.

[0161] In an embodiment, maintaining, by the UE (102), the registration with the prioritized PLMN refers to continuing an existing registration with the prioritized PLMN without initiating a PLMN reselection or a new registration procedure, while the service currently used by the UE is supported by the required network slice on the prioritized PLMN.

[0162] In an embodiment, transmitting, by the UE (102), a registration request message to the prioritized PLMN refers to initiating a registration procedure with the prioritized PLMN in response to determining that the UE is not registered on the prioritized PLMN supporting the required network slice for the service currently used by the UE.

[0163] FIG. 10 is a sequence diagram depicting a method for selecting by a UE (402), a network of prioritized PLMN for transmitting a registration request, based on a current application used by the UE (402), according to embodiments as disclosed herein.

[0164] At step 1, the method comprises receiving by a UE (402), a slice aware SoR information consisting of information on, a plurality of S-NSSAIs, a plurality of networks of a plurality of individual PLMNs supporting the plurality of S-NSSAIs supports and a network-specified prioritized PLMN for each S-NSSAI support, wherein the UE (102) is using multiple services and registered with a HPLMN (424).

[0165] In an example embodiment herein, the SoR information comprises, {S-NSSAI-1: PLMN-1 Prio 1,

[0166] PLMN-2 Prio 2,

[0167] PLMN-3 Prio 3},

[0168] {S-NSSAI-2 : PLMN-1 Prio 1,

[0169] PLMN-3 Prio 2,

[0170] PLMN-2 Prio 3},

[0171] {S-NSSAI-3 : PLMN-3 Prio 1,

[0172] PLMN-2 Prio 2,

[0173] PLMN-1 Prio 3} ]

[0174] At step 2, the method comprises, determining by the UE (402), the plurality of S-NSSAIs required for the multiple services, by using at least, a pre configuration S-NSSAI information available on the UE (402). In an embodiment herein, the at least one required S-NSSAI of the plurality of required S-NSSAIs is rejected by at least one network of an individual PLMN of the plurality of networks of the plurality of individual PLMNs. Further, in an embodiment herein, the UE (102) can determine its required network slices by using an available allowed NSSAI information for the UE, using UE local policies (such as UE configuration or UE applications), and so on.

[0175] At step 3, the method comprises, detecting by the UE (402), the at least one network of an individual PLMN, is a network of prioritized PLMN for more than one Application used by the UE for a time instance, wherein the at least one network of an individual PLMN rejecting the at least one S-NSSAI. In an example embodiment herein the UE can detect a network of first PLMN (PLMN-1) (104) as a prioritized PLMN for more than one Application used by the UE (102) for the time instance.

[0176] At step 4, the method comprises transmitting, by the UE (102) a registration request message to the network of the prioritized PLMN along with the plurality of required S-NSSAIs included in registration request message. In an embodiment herein, the at least one prioritized PLMN from the network of the network-specified prioritized PLMN, is an unprioritized PLMN for the at least one required S-NSSAI. In an example embodiment herein, the UE (102) can transmit a registration request towards network of first PLMN (PLMN-1) (104) with the S-NSSAI(s) (S-NSSAI1, S-NSSAI-2 and S-NSSAI-3) that is required by including in a Registration Request message. The first PLMN (PLMN-1) (104) is prioritized by a HPMN (424) for S-NSSAI-1 and S-NSSAI-2 and first PLMN (PLMN-1) (104) can also support S-NSSAI-3.

[0177] At step 5, the method comprises accepting by the network of first PLMN (PLMN-1) (104) the UE registration request and adding S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3 as Allowed NSSAI for the Applications used by the UE (402). The UE (102) has successfully registered with network now accessing the services from first PLMN (PLMN-1) (104).

[0178] At step 6, the method comprises opening by a user at least one new application on the UE.

[0179] At step 7, the method comprises transmitting by a UDM of the HPLMN (422) a list of S-NSSAI(s), to the UE (102) which the UE (102) need to select in priority order. In an example embodiment herein, the HPLMN can send to the UE (402), a message containing the list of S-NSSAI(s) in priority order, wherein the message can be any transparent container such as SoR message or a configuration update message which is security and integrity protected.

[0180] At step 8, the method comprises evaluating by the UE (402), the plurality of networks of the plurality of PLMNs based on the priority order of the S-NSSAIs in order to re-select a network of prioritized PLMN for the prioritized NSSAI. In an example embodiment herein, the HPLMN (422) determines, a network of prioritized second PLMN (PLMN-2) (106) form the evaluation, wherein the at least one prioritized PLMN from the network of the prioritized PLMN, is an unprioritized PLMN for the at least one required S-NSSAI. In an example embodiment herein, a network of second PLMN (PLMN-2) (106) is prioritized from the evaluation and the UE (102) can register with the network of second PLMN (PLMN-2) (106) as per a received configuration from the HPLMN (422), wherein the second PLMN (PLMN-2) (106) is a network-specified prioritized PLMN for a prioritized NSSAI.

[0181] Further, in an embodiment herein, the HPLMN (422) can send a PLMN that need to be used as prioritized PLMN by the UE (102) when a single common PLMN do not support all required S-NSSAIs at any moment or UE is unable to decide the S-NSSAI+PLMN combination.

[0182] At step 9, a registration request message is transmitted to the network of second PLMN (PLMN-2) with the required a plurality of S-NSSAI(s).

[0183] The various actions, acts, blocks, steps, or the like in the flow charts (500-900) may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some of the actions, acts, blocks, steps, or the like may be omitted, added, modified, skipped, or the like without departing from the scope of the invention.

[0184] Embodiments herein, disclose prioritizing a network of PLMN which can support a maximum number of required S-NSSAI(s), based on the enhanced slice aware SoR information.

[0185] It is proposed that once a PLMN is selected UE can perform PLMN re-selection on one of the below situations: (1) Changes in an application / applications selected by the user, (2) Enablement or disablement of a PDU session from over a S-NSSAI (3) Changes in enhanced slice aware SoR information. (4) Change in UE location (5) On checking As per URSP rules time / location criteria one or more PDU sessions or S-NSSAIs are available or not available. (6) On checking user or upper layer indication about the set of S-NSSAI required or not required.

[0186] In another embodiment the UE (102) is configured with priority list of the S-NSSAIs to be used. The configuration can be in the UE / ME / SIM. Further, in another embodiment the UE (102) is always given priority for the standard S-NSSAIs like eMBB, URLLC, V2x etc over non-standard S-NSSAIs. In another embodiment the UE (102) is always given priority for the non standard S-NSSAIs over standard S-NSSAIs like eMBB, URLLC, V2x etc. In another embodiment Applications in foreground are treated as equal priority of S-NSSAI and back ground app is of low priority. In another embodiment it is proposed that an User interface (UI) is presented to user based on the non availability of an S-NSSAI or UE on a non prioritized PLMN and using an S-NSSAI to request that if reselection to best PLMN is desired by user or not and take appropriate action. In another embodiment an UI option is provided with all information under network settings about application to S-NSSAI mapping and enhanced slice aware SoR information and enabling user to select the right PLMN.

[0187] A reinforced learning (RL) module (416) on the UE (102) is implemented which will be used to identify the required slices S-NSSAIs for the user at any given time or location. Based on the identified required slices S-NSSAIs, it will evaluate the enhanced slice aware SoR information received from the network and selects a PLMN to be registered. The learning will be based on below parameters for example and not limited to: (1) Application in use and configuration of slice S-NSSAI in URSP S-NSSAI to PLMN priority as per the enhanced slice aware SoR information. (2) Category of the application and its QOS characteristics, usage pattern such as time and duration of usage of the application. (3) Applications that are used by user the most and applications that are required optimized performances are learnt and treated has highest prioritized PLMNs. (4) The request from applications for S-NSSAIs will be learnt and based this information the S-NSSAI and respective PLMN that has been prioritized for this S-NSSAI will be chosen for registration. (5) The module is enhanced with fall back mechanisms to avoid frequent PLMN reselections when user is switching across applications or locations. (6) The decision for required S-NSSAI on each of the 3GPP access and non 3GPP access is derived from the learnt model and separate registration requests will be sent on each access and thus allows UE to be on optimized PLMN for each of the S-NSSAI (service)

[0188] The RL module (416) further can perform other mechanisms of how to prioritize a S-NSSAI based on user inputs to prioritize an application / network provided list with an S-NSSAI priority indication based on NWDAF analysis from the network derived independently for each user based on user subscription and analytics.

[0189] Embodiments herein disclose, avoiding by the UE (102) moving to a higher priority PLMN based on a OPLMN list instead prioritize Enhanced SoR information until an Application (UE-service) is under use. In an example embodiment herein, the UE (102) currently using S-NSSAI-3 under third PLMN (PLMN-3) (108) and if a user has opened new application which requires S-NSSAI-1, the UE (102) will check from slice aware SoR information whether current PLMN is the highest prioritized PLMN. The UE will further check if the S-NSSAI-1 is part of the allowed NSSAI list of third PLMN (PLMN-3) (108). As per an RL module (416), the UE (102) further identifies whether there is a need to change PLMN to use S-NSSAI on a different PLMN. Based on a prediction using the RL module (416), the UE (102) may change the PLMN to first PLMN (PLMN-1) (104). The new PLMN (PLMN-1) (104) is selected based on the average weights associated with each application (decided by at least one of a user, a network, and a learned module), and by satisfying the max weighted average value in the order of the applications of S-NSSAI.

[0190] Embodiments herein, disclose, a PLMN that is need to be prioritized for the S-NSSAI(s) to be used is defined as part of the enhanced slice aware SoR information, it is important for the UE (102) to identify and request the minimum possible required or requested S-NSSAIs which can affect the selection of the PLMN below possible solutions are proposed to select the S-NSSAI(s). Embodiments herein disclose, without any affect at the user or network end, introducing a reinforced learning module (416) at the UE which will be device and user specific that learns the usage of the application and its respective network slice based on URSP rules received from the network. Based on the RL module and the usage of applications by user the respective network slices S-NSSAIs will be chosen and thus select the correct PLMN at any given time.

[0191] Embodiments herein disclose seeking user inputs about the applications that need to be given highest (optimized) user experience, This selection of applications by user in turn will be mapped to the required S-NSSAIs and thus will be decided and used for PLMN selection at any given point of time. Embodiments herein disclose a network to provide a prioritized S-NSSAI list, the UE (102) supposed to be prioritized and a common PLMN that can be selected if a single PLMN which cannot support all the required network slices.

[0192] Embodiments herein disclose if a PLMN supports maximum number of the S-NSSAIs that will be chosen irrespective of the applications under use or priority of the PLMN if UE decides to use all the required S-NSSAIs. Embodiments herein disclose the UE (102) avoiding PLMN reselections frequently by learning the UE, slice usage behaviour and thus avoid battery drain and unnecessary signaling on the core network.

[0193] Embodiments herein disclose prioritizing by the system the network slices S-NSSAIs that required for the applications in the below order: (1) Foreground application (2) Back ground application (3) Low latency / delay in tolerant applications (4) Probable usage of application based on user past behaviour.

[0194] Advantages of the Proposed Solutions are (1) UE is always registered on the best possible PLMN based on the S-NSSAIs being used. (2) Performing PLMN re-selection only when required and avoid un necessary PLMN re-selections and reducing overall UE and network signaling and enhanced battery savings. (3) Solutions with or without user knowledge and network dependence.

[0195] The embodiment disclosed herein describes methods and systems for prioritizing selection of a PLMN based on a prioritized UE-service. Therefore, it is understood that the scope of the protection is extended to such a program and in addition to a computer readable means having a message therein, such computer readable storage means contain program code means for implementation of one or more steps of the method, when the program runs on a server or mobile device or any suitable programmable device. The method is implemented in at least one embodiment through or together with a software program written in e.g., Very high speed integrated circuit Hardware Description Language (VHDL) another programming language, or implemented by one or more VHDL or several software modules being executed on at least one hardware device. The hardware device can be any kind of portable device that can be programmed. The device may also include means which could be e.g., hardware means like e.g., an ASIC, or a combination of hardware and software means, e.g., an ASIC and an FPGA, or at least one microprocessor and at least one memory with software modules located therein. The method embodiments described herein could be implemented partly in hardware and partly in software. Alternatively, the invention may be implemented on different hardware devices, e.g., using a plurality of CPUs.

[0196] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by Applying current knowledge, readily modify and / or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of embodiments and examples, those skilled in the art will recognize that the embodiments and examples disclosed herein can be practiced with modification within the scope of the embodiments as described herein.

Claims

1.A method for Public land mobile network (PLMN) selection, comprising:receiving, by a User Equipment (UE) (102), an enhanced slice aware Steering of Roaming (SoR) information from a network;identifying by the UE (102) a user behaviour pattern of a network slice usage for a service currently used by the UE (102);determining, by the UE (102), whether the UE (102) is registered on a prioritized PLMN for the service currently used by the UE (102) based on the enhanced slice aware SoR information and the user behaviour pattern of the network slice usage; andmaintaining, by the UE (102), the registration with the prioritized PLMN in response to determining that the UE (102) is registered on the prioritized PLMN for the service currently used by the UE (102); andtransmitting, by the UE (102), a registration request message to the prioritized PLMN in response to determining that the UE (102) is not registered on the prioritized PLMN for the service currently used by the UE.2.The method as claimed in claim 1, wherein, the method comprises:receiving, by the UE (102), from a network system, a plurality of enhanced slice aware steering of roaming (SoR) information comprising, a plurality of Single - Network Slice Selection Assistance Information (S-NSSAIs), and a plurality of Public Land mobile networks (PLMNs) supporting the plurality of S-NSSAIs, wherein an individual S-NSSAI of the plurality of S-NSSAIs, is configured by at least one PLMN prioritized for the UE; andselecting by the UE (102), the at least one PLMN prioritized for the UE (102), along with at least one configured S-NSSAI among the plurality of S-NSSAIs, based on priority of the service currently used by the UE (102).3.The method as claimed in claim 2, wherein selecting the least one PLMN prioritized for the UE (102), comprises:　 evaluating by the UE (102), the enhanced slice aware SoR information received from the network, and usage behaviour pattern of the UE (102) in relation to the plurality of S-NSSAIs, in order to determine the priority of the service currently used by the UE (102);　 evaluating by the UE (102), a registered PLMN is at least one of: a PLMN prioritized for the service currently used by the UE (102) and a PLMN unprioritized for the service currently used by the UE (102), and　 transmitting by the UE (102), a registration request message to a prioritized PLMN when the registered PLMN is the PLMN unprioritized for the service currently used by the UE (102).4.The method as claimed in claim 2, wherein the method comprises, modifying by the UE (102), usage of the plurality of S-NSSAIs for registration to the prioritized PLMN, when the prioritized PLMN is rejecting at least one S-NSSAI of the plurality of S-NSSAIs.5.The method as claimed in claim 1, wherein the method comprises:identifying, by the UE (102), a registered PLMN is an unprioritized PLMN for the service currently used by the UE (102) and the availability of other PLMNs supporting a plurality of S-NSSAIs with highest priority.performing, by the UE (102), a PLMN search and updating a PLMN search result, using an incremental scan of the plurality of PLMNs, wherein the PLMN search result is used for evaluating and deciding requirement of a PLMN re-selection; anddynamically selecting and re-selecting by the UE (102) a prioritized PLMN based on priority of the service currently used by the UE (102).6.The method as claimed in claim 1, wherein the method comprises :identifying by the UE (102), a current location of the UE (102); andselecting by the UE (102), the prioritized PLMN available at the current location of the UE (102), based on the enhanced slice aware SoR information in respect of the current locations.7.The method as claimed in claim 6, wherein the method comprises, determining by the UE (102), at least one service with highest priority from a plurality of services currently used by the UE (102) which requires a PLMN re-selection.8.The method as claimed in claim 2, wherein selecting the at least one PLMN prioritized for the UE (102), based on priority of a service currently used by the UE (102), comprising:generating by the UE (102), a reinforced learning module from at least, a plurality of learnt parameters comprising: a plurality of services simultaneously used by the UE, configuration of the plurality S-NSSAIs in a UE route selection policy (URSP), S-NSSAIs to PLMN priority as per the enhanced slice aware SoR information, category of the plurality of services simultaneously used by the UE and Quality of service (QOS) characteristics for the plurality of services, usage pattern for the plurality of services with respect to time, and duration of usage of the plurality of services;estimating by the UE (102), probability of occurence of the plurality of services simultaneously used by the UE, in a plurality of respective S-NSSAIs, based on the learnt parameters, in order to determine a service from the plurality of services as a prioritized service for a given time; identifying by the UE (102), at least one required S-NSSAI, from the plurality of S-NSSAIs, based on the estimation;evaluating by the UE (102), the enhanced slice aware SoR information received from the network, based on the at least one required S-NSSAI, andselecting by the UE (102), a prioritized PLMN for registration, based on the evaluation, wherein the at least one PLMN is configured to support the at least one required S-NSSAI,wherein the UE (102) determines based on the plurality of learnt parameters, probability of further usage of each service of the plurality of services, at a given time when a service is re-opened.9.The method as claimed in claim 8, wherein the method comprises performing by the UE (102), based on usage of a service currently used by the UE (102), at least one of: sustaining registration with a registered PLMN unprioritized for the at least one required S-NSSAI and reselection of a prioritized PLMN according to Slice aware SoR information.10.The method as claimed in claim 1, wherein the method comprises reselecting a PLMN prioritized for the UE (102), based on a user-input of at least one prioritized service currently used by the UE (102), through a method of:registering, by the UE (102), to a first PLMN, prioritized for a first service used by the UE (102), wherein the first PLMN supporting a first S-NSSAI configuration and rejecting a second S-NSSAI configuration;opening by the UE (102), a second service, wherein the second service requires the second S-NSSAI configuration for operation, wherein the second S-NSSAI configuration is configured by a second PLMN prioritized for the second S-NSSAI;determining by the UE (102), at least one of, the first UE service and the second UE service, is a prioritized service; andperforming by the UE (102), at least one of:reselection of the second PLMN prioritized for the second S-NSSAI, when the second service is a prioritized service, andsustaining registration to the first PLMN prioritized for the first S-NSSAI, when the first service is a prioritized service.11.The method as claimed in claim 1, wherein the method comprises prioritizing at least one S-NSSAI from a plurality of S-NSSAIs configured for a plurality of services simultaneously used by the UE (102), through a method of,registering by the UE (102), to a first PLMN, prioritized for a first service currently used by the UE, wherein the first PLMN supporting a first S-NSSAI configuration and rejecting a second S-NSSAI configuration;opening by the UE (102), a second service, wherein the second service requires a second N-SSAI configuration for operation, wherein the second S-NSSAI configuration is configured by a second PLMN prioritized for the second S-NSSAI;determining by the network system, at least one of: priority of the second N-SSAI is more than priority of the first N-SSAI, and priority of the second N-SSAI is less than priority of the first N-SSAI; andenabling by the network system, the UE to perform at least one of :a PLMN reselection, when priority of the second N-SSAI is more than priority of the first N-SSAI, andsustaining registration with the first N-SSAI, when priority of the second N-SSAI is less than priority of the first N-SSAI,wherein the priority of at least one of the first N-SSSAI and the second N-SSAI is determined by the network, based on a service used by the UE (102) is prioritized by the reinforced learning module.12.The method as claimed in claim 1, wherein the method comprises:receiving by the UE (102), a slice aware SoR information consisting of information on, a plurality of S-NSSAIs, a plurality of networks of a plurality of individual PLMNs supporting the plurality of S-NSSAIs supports and a network-specified prioritized PLMN for each S-NSSAI support, wherein the UE (102) is using multiple services and registered with a network system;determining by the UE (102), the plurality of S-NSSAIs required for the multiple services, by using at least, a pre configuration S-NSSAI information available on the UE (102), wherein at least one required S-NSSAI of the plurality of required S-NSSAIs is rejected by at least one network of an individual PLMN from the plurality of networks of the plurality of individual PLMNs;detecting by the UE (102), the at least one network of an individual PLMN, is a network of prioritized PLMN, wherein the at least one network of an individual PLMN rejecting the at least one S-NSSAI; andtransmitting, by the UE (102), a registration request message to the network of the prioritized PLMN along with the plurality of required S-NSSAIs included in registration request message, wherein the at least one prioritized PLMN from the network of the network-specified prioritized PLMN, is an unprioritized PLMN for the at least one required S-NSSAI.13.The method as claimed in claim 12, wherein the method comprises:evaluating by the network, the plurality of networks of the plurality of individual PLMNs supporting a plurality of S-NSSAIS, based on priority order of the plurality of the S-NSSAIs; anddetermining by the network, the network of prioritized PLMN form the evaluation, wherein the at least one prioritized PLMN from the network of the prioritized PLMN, is an unprioritized PLMN for the at least one required S-NSSAI.14.The method as claimed in claim 1, wherein the method comprises:identifying by the UE (102), a registered PLMN is an un-prioritized PLMN for the service currently used by the UE, and identifying the availability of other PLMN where the S-NSSAI can be supported with highest priority;performing by the UE (102), a PLMN search and storing the search result;updating by the UE (102), a stored list of PLMN search result, using incremental scan in order to use in evaluating and identifying a PLMN re-selection would be required or not; andidentifying, by the UE (102), that the UE has entered a location where a PLMN with highest priority is available and automatically re-selecting the PLMN with highest priority based on the enhanced slice aware SoR information, moving by the UE (102) to the PLMN with highest priority based on at least one of: the stored list of PLMN search result and a prioritized S-NSSAI when a service is under use by the UE.15.A UE (102) comprising a processor (412), a memory (414) and a reinforced learning module (416), wherein the processor (412) is configured to:receive, at least one of: an enhanced slice aware Steering of Roaming (SoR) information from a network;identify, a user behaviour pattern of a network slice usage for a service currently used by the UE (102);determine, whether the UE (102) is registered on a prioritized PLMN for a service currently used by the UE (102) based on, the enhanced slice aware SoR information and the user behaviour pattern of the network slice usage; andmaintain the registration with the prioritized PLMN, in response to determining that the UE (102) is registered on the prioritized PLMN for the service currently used by the UE (102); andtransmit a registration request message to the prioritized PLMN, in response to determining that the UE (102) is not registered on the prioritized PLMN for the service currently used by the UE.

Images