Managing network slicing capability of UE in wireless network

Abstract

Embodiments herein provide a method and system for managing a network slicing capability of a user equipment (UE) in a wireless network. The method includes determining that the UE is in a condition where it is facing an issue with at least one network service. Further, determining whether the issue is attributable to a result of a network slicing capability of the UE or an incompatibility between the UE and a network apparatus. In addition, changing network slicing parameters of a protocol data unit (PDU) session established by the UE with the network apparatus in response that the issue is attributable as a result of the network slicing capability or the incompatibility between the UE and the network apparatus.

Description

MANAGING NETWORK SLICING CAPABILITY OF UE IN WIRELESS NETWORK

[0001] The disclosure is related to wireless networks, more particularly, the disclosure relates to a system and method for managing a network slicing capability of a user equipment (UE) in a wireless network.

[0002] According to 3rdgeneration partnership project (3GPP) standards, network slicing is a default feature of 5G SA and must be supported by all fifth generation (5G) stand alone (SA)-enabled devices and networks. With multiple deployment choices in 5G SA, network operators, device suppliers, and ecosystems such as operating system (OS) developers have chosen varied methods to effectively implementing 5G SA. Several types of network slicing deployment solutions are now available on the market. For example, the UE and network only support one network slice (single network slice selection assistance information (S-NSSAI)), and all user data traffic is routed through that network slice. The UE control plane (CP) modem can handle multiple network slices, however the access point (AP) OS does not support the capability that allows applications to request individual network slices. Although the UE CP modem and AP OS may handle multiple network slices, operators do not install multiple network slices.

[0003] The UE cannot handle more than one network slice, although the network has implemented many network slices. As a result, the network slicing functionality has not been completely confirmed because the network ecosystem is expanding slowly and unevenly in different parts of the world. In all current market devices supporting 5G SA, UEs do not request any of the slices, but the network allocates the default network slice, such as slice / service type (SST) 1 (enhanced mobile broadband (eMBB)) by default in registration accept or protocol data unit (PDU) session accept, based on network configuration.

[0004] Unexpected difficulties may arise from devices that have not been vetted or tested for interoperability with network settings. If an issue arises after commercially enabling Network slicing capabilities from the network side for 5G SA devices, there is no way to restore the devices to their previous condition. Chipset manufacturers have not provided or implemented any solutions for device recovery.

[0005] Many network operators are already offering 5G SA with minimal default network slicing support, while the majority of the remaining operators are doing 5G SA trials. During the network slicing feature verification on networks where the network has configured more than one network slice, we observed difficulties with devices that are currently on the market owing to the network's support for multiple network slices. The UE has challenges such as internet protocol multimedia subsystem (IMS), internet, and hotspot not working, and devices not recovering even after a power cycle. Currently, many commercially available devices enable 5G SA but are not completely compliant with multi-network slice deployment, and all such devices are susceptible to these issues. Given the type and severity of the difficulties that consumers may encounter, it is necessary to establish a way for these devices to recover from the issue situation.

[0006] Hence, it desirable to address the above mentioned problems and disadvantages or at least provide a useful alternative.

[0007] Additional aspects will be set forth in part in the description which follows and, in part, will be apparent from the description, or may be learned by practice of the presented embodiments.

[0008] According to an example embodiment of the disclosure, a method for managing a network slicing capability of a user equipment (UE) in a wireless network is provided. The method includes determining that the UE is in a condition where the UE is facing an issue with at least one network service associated with the UE. Further, the method includes whether the issue is attributable to a result of at least one of a network slicing capability of the UE or an incompatibility between the UE and a network apparatus. Further, the method includes changing network slicing parameters of a protocol data unit (PDU) session established by the UE with the network apparatus in response that the issue is attributable to the result of at least one of the network slicing capability of the UE or the incompatibility between the UE and the network apparatus.

[0009] According to an example embodiment of the disclosure, a method for managing a network slicing capability of a user equipment (UE) in a wireless network is provided. The method includes determining a plurality of parameters associated with the UE. The plurality of parameters includes a device type of the UE, a model number of the UE, an international mobile equipment identity (IMEI) of the UE, and an IMEI software version (IMEI-SV) of the UE. Further, the method includes determining whether the UE belongs to an allowed list for network slicing provisioning. Further, the method includes configuring network slicing parameters at the UE in response that the UE belongs to the allowed list for network slicing provisioning, and deleting network slicing parameters previously configured by the network apparatus at the UE in response that the UE does not belongs to the allowed list for network slicing provisioning.

[0010] According to an example embodiment of the disclosure, a user equipment (UE) for managing a network slicing capability of a user equipment (UE) in a wireless network is provided. The UE includes memory storing instructions, and at least one processor. The instructions, when executed by the processor (504) individually or collectively, cause the UE to determine that the UE is in a condition where the UE is facing an issue with at least one network service associated with the UE. Further, the instructions, when executed by the processor individually or collectively, cause the UE to determine whether the issue is attributable to a result of at least one of a network slicing capability of the UE or an incompatibility between the UE and a network apparatus. In addition, the instructions, when executed by the processor individually or collectively, cause the UE to change network slicing parameters of a protocol data unit (PDU) session established by the UE with a network apparatus in response that the issue is attributable to the result of at least one of the network slicing capability of the UE or the incompatibility between the UE and the network apparatus.

[0011] According to an example embodiment of the disclosure, a network apparatus for managing a network slicing capability of a user equipment (UE) in a wireless network is provided. The network apparatus includes memory storing instructions, and at least one processor. The instructions, when executed by the processor individually or collectively, cause the network apparatus to determine a plurality of parameters associated with the UE. The plurality of parameters include a device type of the UE, a model number of the UE, an international mobile equipment identity (IMEI) of the UE, and an IMEI software version (IMEI-SV) of the UE. Further, the instructions, when executed by the processor individually or collectively, cause the network apparatus to determine whether the UE belongs to an allowed list for network slicing provisioning. Further, the instructions, when executed by the processor individually or collectively, cause the network apparatus to configure network slicing parameters at the UE in response that the UE belongs to the allowed list for network slicing provisioning, and delete network slicing parameters previously configured by the network apparatus at the UE in response that the UE does not belongs to the allowed list for network slicing provisioning. In an example embodiment, a non-transitory computer-readable storage medium storing one or more programs comprising instructions. The instructions, when executed by at least one processor of a user device individually or collectively, cause a user equipment (UE) to determine that the UE is in a condition where the UE is facing an issue with at least one network service associated with the UE. Further, the instructions, when executed by the processor individually or collectively, cause the UE to determine whether the issue is attributable to a result of at least one of a network slicing capability of the UE or an incompatibility between the UE and a network apparatus. In addition, the instructions, when executed by the processor individually or collectively, cause the UE to change network slicing parameters of a protocol data unit (PDU) session established by the UE with a network apparatus in response that the issue is attributable to the result of at least one of the network slicing capability of the UE or the incompatibility between the UE and the network apparatus.

[0012] In an example embodiment, a non-transitory computer-readable storage medium storing one or more programs comprising instructions. The instructions, when executed by at least one processor of a user device individually or collectively, cause a network apparatus to instructions, when executed by the processor individually or collectively, cause the network apparatus to determine a plurality of parameters associated with a user equipment (UE). The plurality of parameters include a device type of the UE, a model number of the UE, an international mobile equipment identity (IMEI) of the UE, and an IMEI software version (IMEI-SV) of the UE. Further, the instructions, when executed by the processor individually or collectively, cause the network apparatus to determine whether the UE belongs to an allowed list for network slicing provisioning. Further, the instructions, when executed by the processor individually or collectively, cause the network apparatus to configure network slicing parameters at the UE in response that the UE belongs to the allowed list for network slicing provisioning, and delete network slicing parameters previously configured by the network apparatus at the UE in response that the UE does not belongs to the allowed list for network slicing provisioning

[0013] To further clarify the advantages and features of the disclosure, a more particular description of various example embodiments illustrated in the appended drawings is provided. It is appreciated that these drawings depict example embodiments and are therefore not to be considered limiting its scope. The disclosure will be described and explained with additional specificity and detail with reference to the accompanying drawings.

[0014] The above and other features, aspects, and advantages of certain embodiments of the disclosure will be more apparent from the following detailed description, taken in conjunction with the accompanying drawings in which like characters represent like parts throughout the drawings, an in which:

[0015] Fig. 1 is a sequence diagram that illustrates a message sequence before network slice provisioning according to the related art.

[0016] Fig. 2 is a sequence diagram that illustrates the message sequence after network slice provisioning according to the related art.

[0017] Fig. 3 is a sequence diagram that illustrates a rejection of a PDU session request on a specific slice according to the related art.

[0018] Fig. 4 is a sequence diagram that illustrates a specific service or DNN using a wrong network slice according to the related art.

[0019] Fig. 5 is a block diagram that illustrates a schematic of a UE implemented to carry out the disclosed subject matter according to the embodiments as disclosed herein.

[0020] Fig. 6 is a block diagram that illustrates a schematic of a network apparatus implemented to carry out the disclosed subject matter according to the embodiments as disclosed herein.

[0021] Fig. 7a and Fig. 7b are sequence diagrams that illustrate identification of a service / slice unavailability according to the embodiments as disclosed herein.

[0022] Fig. 8 is a sequence diagram that illustrates rejection of slice requests according to the embodiments as disclosed herein.

[0023] Fig. 9 is a sequence diagram that illustrates controlling of the network slicing capability based on a model, IMEI, and IMEI-SV according to the embodiments as disclosed herein.

[0024] Fig. 10 is a sequence diagram that illustrates controlling of the network slicing capability based on a reserved bit of UE capability information according to the embodiments as disclosed herein.

[0025] Fig. 11a Fig. 11b are flow charts that illustrate a method for managing the network slicing capability of the user equipment (UE) in a wireless network according to the embodiments as disclosed herein. and

[0026] Fig. 12 is a flow chart that illustrates a method for managing network slicing parameters according to the embodiments as disclosed herein.

[0027] Further, skilled artisans will appreciate that elements in the drawings are illustrated for simplicity and may not have necessarily been drawn to scale. For example, the flowcharts illustrate the method in terms of the steps / operations involved to help to improve understanding of aspects of the disclosure. 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 those specific details that are pertinent to understanding the various embodiments of the disclosure 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.

[0028] It should be understood at the outset that although illustrative implementations of the embodiments of the disclosure are illustrated below, the disclosure may be implemented using any number of techniques, whether currently known or in existence. The disclosure should in no way be limited to the illustrative implementations, drawings, and techniques illustrated below, including the design and implementation illustrated and described herein, but may be modified within the scope of the appended claims along with their full scope of equivalents.

[0029] The term "some" as used herein is defined as "none, or one, or more than one, or all." Accordingly, the terms "none," "one," "more than one," "more than one, but not all" or "all" would all fall under the definition of "some." The term "some embodiments" may refer to no embodiments, to one embodiment or to several embodiments or to all embodiments. Accordingly, the term "some embodiments" is defined as meaning "no embodiment, or one embodiment, or more than one embodiment, or all embodiments."

[0030] The terminology and structure employed herein is for describing, teaching, and illuminating some embodiments and their specific features and elements and does not limit, restrict, or reduce the spirit and scope of the claims or their equivalents.

[0031] More specifically, any terms used herein such as but not limited to "includes," "comprises," "has," "consists," and grammatical variants thereof do NOT specify an exact limitation or restriction and certainly do NOT exclude the possible addition of one or more features or elements, unless otherwise stated, and furthermore must NOT be taken to exclude the possible removal of one or more of the listed features and elements, unless otherwise stated with the limiting language "MUST comprise" or "NEEDS TO include."

[0032] Whether or not a certain feature or element was limited to being used only once, either way, it may still be referred to as "one or more features" or "one or more elements" or "at least one feature" or "at least one element." Furthermore, the use of the terms "one or more" or "at least one" feature or element does NOT preclude there being none of that feature or element, unless otherwise specified by limiting language such as "there NEEDS to be one or more . . ." or "one or more element is REQUIRED."

[0033] Unless otherwise defined, all terms, and especially any technical and / or scientific terms, used herein may be taken to have the same meaning as commonly understood by one having ordinary skill in the art.

[0034] It is to be understood that a singular form of a noun corresponding to an item may include one or more of the things, unless the relevant context clearly indicates otherwise. As used herein, each of such phrases as "A or B," "at least one of A and B," "at least one of A or B," "A, B, or C," "at least one of A, B, and C," and "at least one of A, B, or C," may include any one of, or all possible combinations of the items enumerated together in a corresponding one of the phrases. It is to be understood that if an element (e.g., a first element) is referred to, with or without the term "operatively" or "communicatively", as "coupled with," "coupled to," "connected with," or "connected to" another element (e.g., a second element), it means that the element may be coupled with the other element directly (e.g., wired), wirelessly, or via a third element.

[0035] Fig. 1 is a sequence diagram that illustrates a message sequence before network slice provisioning according to the related art. As shown, the sequence diagram illustrates an application (APP) (100), a user equipment (UE) (102), and a network apparatus (104) in communication with each other.

[0036] At operation S101, the UE (102) sends a registration request without including NSSAI to the network apparatus (104). At operation S102, the network apparatus (104) sends a registration accept message to the UE (102). Here, the network apparatus (104) assigns a default slice (SST-1). At operation S103, the upper layers of the APP (100) request the UE (102) for a PDU establishment. At operation S104, the UE (102) sends the PDU establishment request to the network apparatus (104) without including S-NSSAI. At operation S105, the network apparatus (104) sends a PDU session establishment accept message to the UE (102), where S-NSSAI is set to SST-1. At operation S106, the data is routed over the default slice SST-1.

[0037] Fig. 2 is a sequence diagram that illustrates the message sequence after network slice provisioning according to the related art. As shown, the sequence diagram illustrates the APP (100), the UE (102), and the network apparatus (104) in communication with each other.

[0038] At operation S201, the UE (102) is configured with one or more network slices. For instance, the one or more network slices may include S-NSSAI-D (default slice SST-1), S-NSSAI-B (bandwidth slice SST-1: SD-1), and S-NSSAI-L (latency slice SST-1: SD-2). At operation S202, the UE (102) sends a registration request to the network apparatus (104). The UE (102) registers by requesting network slices S-NSSAI-D, S-NSSAI-B, and S-NSSAI-L. At operation S203, the network apparatus (104) accepts the registration by adding requested network slices as part of an allowed NSSAI list. At operation S204, the network apparatus (104) sends URSP rules to the UE (102). For example, the URSP rules may include the bandwidth slice S-NSSAI-B SST-1: SD-1 mapped to DNN xxx.yyy.

[0039] At operation S205, the upper layers of the APP (100) requests for bandwidth slice dnn_slice information to the UE (102). At operation S206, the UE (102) returns dnn xxx.yyy and slice S-NSSAI-B (e.g.SST1:SD3) to the APP (100). When the APP (100) requests for a specific slice (e.g. bandwidth slice), a modem shall evaluate URSP rules and identifies a network slice id associated with the bandwidth slice. At operation S207, the upper layers of the APP (100) send a PDU activation request for bandwidth slice to the UE (102). At operation S208, the UE (102) sends a PDU session establishment request to the network apparatus (104) by including requested Slice set to S-NSSAI-B (e.g. SST-1:SD-1) and DNN set to xxx.yyy. At operation S209, the network apparatus (104) sends a PDU session establishment accept message to the UE (102) with a slice ID set to S-NSSAI-B. At operation S210, the application data is routed over the bandwidth slice S-NSSAI-B(e.g. SST-1:SD-1)

[0040] Fig. 3 is a sequence diagram that illustrates a rejection of a PDU session request on a specific slice according to the related art. As shown, the sequence diagram illustrates the APP (100), the UE (102), and the network apparatus (104) in communication with each other.

[0041] At operation S301, the UE (102) is registered over the network apparatus (104) with SST1: SD-1 in an allowed NSSAI received. At operation S302, the network apparatus (104) sends URSP rules to the UE (102) that include a match all traffic descriptor. For example, the URSP rules may be:

[0042] TD: Match All

[0043] RSD

[0044] S-NSSAI-M (e.g. SST=1, SD=3)

[0045] DNN: xxx.yyy

[0046] At operation S303, the upper layers of the APP (100) request for a PDU establishment for IMS DNN to the UE (102). At operation S304, the UE (102) determines that the IMS DNN does not match with any of the traffic descriptors. The UE (102) picks a slice from match-all TD e.g. S-NSSAI-M. At operation S305, the sends a PDU session establishment request (with S-NSSAI Set to S-NSSAI-M) to the network apparatus (104). At operation S306, the since the network apparatus (104) is not expecting data and voice services on slice S-NSSAI-M (SST-1: SD-3), it rejects the PDU request with cause 91. At operation S307, the UE (102) retries the PDU establishment with the same slice again and again. IMS PDU won't be established, due to which the UE (102) is left with no voice service. Due to this, the UE (102) will not be able to access basic services even with a power cycle.

[0047] Fig. 4 is a sequence diagram that illustrates a specific service or DNN using a wrong network slice according to the related art. As shown, the sequence diagram illustrates the APP (100), the UE (102), and the network apparatus (104) in communication with each other.

[0048] At operation S401, the UE (102) is registered over the network apparatus (104) with SST1:SD4 in an allowed NSSAI received. At operation S402, the network apparatus (104) sends URSP rules to the UE (102). For example, the URSP rules may be:

[0049] Descriptor;

[0050] TD: DNN = xxx.zzz

[0051] RSD

[0052] S-NSSAI-H (e.g. SST=1, SD=4)

[0053] At operation S403, the upper layers of the APP (100) request for a PDU establishment for DNN "xxx.zzz". At operation S404, the UE (102) determines that S-NSSAI-H matches DNN "xxx.zzz" based on the URSP rules. At operation S405, the UE (102) sends a PDU session establishment request (with S-NSSAI Set to S-NSSAI-H) to the network apparatus (104). At operation S406, the since the network apparatus (104) is not expecting the UE (102) to request network slices for hotspot services, the network apparatus (104) rejects the PDU request with cause with cause 91. At operation S407, the UE (102) retries the PDU establishment for hotspot again. However, the network apparatus (104) keeps rejecting the PDU establishment request. Hotspot service will thus stop working.

[0054] The drawbacks　with the prior art stems from the viewpoint of the modem. Network slicing is a 5G SA default feature that is enabled on all 5G SA-compliant devices. However, because networks are progressively allowing or supporting network slicing technologies, several of these features have yet to be fully proven. All of the devices on the market that support 5G SA are set up so that a network assigns the default network slice―for example, SST 1 (eMBB)―rather than the UE (102) requesting one of the slices. The UE (102) does not have any network slices configured (S-NSSAI), despite network operators beginning to leverage network slicing capabilities to use separate slices for bandwidth and latency purposes.

[0055] Unexpected problems may arise from devices that have not undergone interoperability testing or validation with certain network settings. There is no way to return 5G SA devices to their initial state if a problem arises after commercially enabling the network slicing feature from the network side.

[0056] Currently, SIM provisioning determines whether to deliver the URSP, configured NSSAI, etc. For example, suppose the user inserts a network-slicing supplied SIM card into an earlier 5G SA device. The network sends below match-all URSP rule to this older SA device, like all other 5G SA devices, because network slicing is enabled in older 5G SA devices via the modem. URSP Rule 1

[0057] Precedence:1

[0058] TD: Match All

[0059] RSD

[0060] S-NSSAI-M (e.g. SST=1, SD=4)

[0061] DNN: xxx.yyy

[0062] IP Type: IPv6

[0063] Prior to receiving the URSP rule, the network apparatus　(104) would internally assign the default slice, the EMBB (SST1), in the PDU establishment request. The UE (102) would transmit the PDU establishment　request for internet and the IMS without inquiring for any specific slice. The UE (102) will transmit the PDU establishment request for Internet and IMS after receiving the URSP rule, along with a request for a particular slice S-NSSAI-M (e.g. SST1:SD4).

[0064] The　network apparatus (104) will deliver a PDU session reject with reason 91 (DNN not supported with no slice or in particular slice) if it is not anticipated that the specific slice would be requested for the relevant DNN. If this problem arises, current customers' default PDUs, such as Internet or IMS, would stop functioning and there will be no manual method to restore the device. Given the issues that are currently arising from the network slicing trials and the potential issues that current 5G SA users may face in the future, it is imperative that there be a way to partially disable network slicing functionality and restore the devices to their current state in the field.

[0065] The proposed solution provides a functionality to disable network slicing partially such that the UE (102) will not request for specific slices for any of the PDU sessions. The devices which are provisioned and in agreement with network operators to have network slicing enabled, will request for specific slices for PDU sessions.

[0066] The problem faced in the prior art is for matching all rule exists with DNN, IP Type and SSC modes. Assume network apparatus pushes match-all URSP rule as below. As per the 3GPP spec, there may be one URSP Rule in the device.

[0067] URSP Rule 1

[0068] Precedence:1

[0069] TD: Match All

[0070] RSD

[0071] S-NSSAI-M (e.g. SST=1, SD=4)

[0072] DNN: xxx.yyy

[0073] IP Type: IPv6

[0074] Provided Match-All slice S-NSSAI-M (e.g. SST1:SD4) is associated with DNN "xxx.yyy". If the upper layers requests for internet DNN (xxx.yyy), the UE(102) would send a PDU establishment request with requested slice set to S-NSSAI-M (e.g. SST1:SD4) and DNN set to "xxx.yyy" as per URSP configuration. If the upper layers requests for a PDU connection to a different DNN say for e.g IMS, it's not clearly defined if the PDU should be requested over IMS DNN or DNN "xxx.yyy"from match-all URSP. Furthermore, it, is also not defined, if the slice needs to be considered from match-all rule or not, for IMS PDU request, since DNN is not matching. If the UE (102) wrongly sends IMS PDU request with slice S-NSSAI-M from match-all URSP rule (e.g. SST1:SD4), even though corresponding DNN is not matching, the network apparatus (104) shall reject the PDU session (with cause 91 - DNN not supported with no slice or in specific slice) and IMS PDU may not be established leading to no voice services for user.

[0075] Accordingly, the proposed solution is for the strict parameter matching for match-all TD. Match-all URSP rule is sent by the network apparatus (104) and DNN "xxx.yyy" is associated with match-all URSP rule.

[0076] URSP Rule 1

[0077] Precedence:1

[0078] TD: Match All

[0079] RSD

[0080] S-NSSAI-M (e.g. SST=1, SD=4)

[0081] DNN: xxx.yyy

[0082] IP Type: IPv6

[0083] SSC Mode:2

[0084] During URSP Evaluation of match-all URSP rule, strict check on DNN, IP type, SSC mode values shall be performed. If DNN, IP type, and SSC mode values are matched, corresponding slice from match-all URSP rule shall be requested. If not, the PDU request shall be sent without any slice request.

[0085] Additionally, the DNN, IP type, and SSC modes requested by the upper layers will be included in the PDU session establishment request. For example, the upper layers request for a PDU Session for DNN "ims", which does not match the DNN in match-all URSP rule and does not match other URSP rules as well. The UE (102) shall ignore the match-all URSP rule for the current PDU request and sends a PDU session establishment request without including any slice request in rRequested NSSAI IE of PDU session establishment request message.

[0086] The problem faced in the prior art is for DNN mismatch for DNN based TD and RSD. The network apparatus (104) pushes the below DNN based TD configuration.

[0087] TD:　DNN　=　xxx.zzz

[0088] RSD

[0089] S-NSSAI-H (e.g. SST=1,　SD=3)

[0090] DNN: xxx.yyy

[0091] IP　Type:　IPv6

[0092] The DNN TD "xxx.zzz" is mapped to slice S-NSSAI-H (e.g. SST1:SD3) in RSD, but DNN value is wrongly mapped to "xxx.yyy". It is not defined as if the DNN requested by upper layers need to be used or DNN from RSD should be used.

[0093] Accordingly, the proposed solution ignores the DNN for RSD. The network apparatus (104) pushes the below DNN based TD configuration.

[0094] TD:　DNN　=　xxx.zzz

[0095] RSD

[0096] S-NSSAI-H (e.g. SST=1,　SD=3)

[0097] DNN: xxx.yyy

[0098] IP　Type:　IPv6

[0099] The DNN TD "xxx.zzz" is mapped to slice S-NSSAI-H (e.g. SST1:SD3) in RSD, but DNN value is wrongly mapped to "xxx.yyy" Since there is the DNN mismatch between the TD and the RSD, the UE (102) shall ignore the DNN from the RSD and choose the DNN from the TD and send the PDU session establishment request by including the DNN from the TD e.g. "xxx.zzz" and Slice from the RSD (S-NSSAI-H).

[0100] Fig. 5 is a block diagram that illustrates a schematic of a UE (102) implemented to carry out the disclosed subject matter according to the embodiments as disclosed herein. As shown, the UE (102) may include a memory (502), a processor (504) (e.g., including processing circuitry), a communicator (506), a network slice capability controller (NSCC) (508). The UE (102) may be an end-user device that connects with a communication network to access services. The UE (102) may include, but not limited to a laptop, a palmtop, a desktop, a mobile phone, a smart phone, a personal digital assistant (PDA), a tablet, a wearable device, an internet of things (IoT) device, a virtual reality device, a video see through (VST), an augmented reality (AR) glass, a foldable device, a flexible device, a display device, an immersive system, and the like.

[0101] The processor (504) communicates with the memory (502), the communicator (506), and the NSCC (508). The processor (504) executes instructions stored in the memory (502) to perform various processes. The processor (504) may include a 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 graphic processing unit (GPU), a visual processing unit (VPU), and / or an Artificial intelligence (AI) dedicated processor such as a neural processing unit (NPU). Further, the memory (502) of the UE (102) may include storage locations to be addressable through the processor (504). The memory (502) is not limited to a volatile memory and / or a non-volatile memory. Further, the memory (502) may include one or more computer-readable storage media. The memory (502) may include non-volatile storage elements. For example, non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories. Furthermore, the processor (603) may include various processing circuitry and / or multiple processors. For example, as used herein, including the claims, the term "processor" may include various processing circuitry, including at least one processor, wherein one or more of at least one processor, individually and / or collectively in a distributed manner, may be configured to perform various functions described herein. As used herein, when "a processor", "at least one processor", and "one or more processors" are described as being configured to perform numerous functions, these terms cover situations, for example and without limitation, in which one processor performs some of recited functions and another processor(s) performs other of recited functions, and also situations in which a single processor may perform all recited functions. Additionally, the at least one processor may include a combination of processors performing various of the recited / disclosed functions, e.g., in a distributed manner. At least one processor may execute program instructions to achieve or perform various functions.

[0102] The communicator (506) may include an electronic circuit specific to a standard that enables wired or wireless communication. The communicator (506) communicates internally between internal hardware components and with external devices via one or more networks. The communicator (506) is to transmit and receive data. The portion designated as the communicator (506) may also contain additional resources, such as voltage translators, registers, impedances, and buffers.

[0103] In an embodiment, the NSCC (508) determines that the UE (102) is in a condition where the UE (102) is facing an issue with a network service associated with the UE (102). For instance, the issue faced with the network services may include unavailability of internet, a mobile data service, a voice service, a hotspot service, or any network slice-specific services.

[0104] In an embodiment, the NSCC (508) determines whether the issue is attributable to a result of a network slicing capability of the UE (102) or an incompatibility between the UE (102) and the network apparatus (104). The network slicing capability refers to an ability of the UE (102) to connect with and utilize different network slices. Different network slices may be customized for various types of services. For example, one slice might be optimized for low latency and high reliability (ideal for critical applications like autonomous vehicles), while another slide might be prioritizes for high data throughput (suitable for video streaming). The UE (102) with network slicing capability may connect to multiple network slices simultaneously or switch between slices based on the requirements of the application it is running. Further, incompatibility between the UE (102) and the network apparatus (104) refers to situations where the UE (102) and the network apparatus (104) cannot fully communicate or function together as expected. The incompatibility may arise due to various technical mismatches, leading to issues like failed connections, reduced performance, or an inability to access certain network features.

[0105] In an embodiment, the NSCC (508) tracks a number of PDU sessions requests sent to the network apparatus (104) and a number of rejections received from the network apparatus (104). The PDU session requests are initiated by the UE (102) when it wants to establish a data connection to access a particular service. This request is sent to the network apparatus (104), which allocates the necessary resources and assigns an IP address or other network identifiers to the session. A PDU session request rejection occurs when the network apparatus (104) denies the request placed by the UE (102) to establish a PDU session. The rejections may occur due to factors such as, resource unavailability, network policies, security concerns, slice unavailability, and the like. When a PDU session request is rejected, the UE (102) cannot establish the desired connection and may be required to retry after a while.

[0106] In an embodiment, the NSCC (508) determines whether the number of PDU sessions requests sent to the network apparatus (104) and the number of rejections received from the network apparatus (104) meets a defined threshold. The threshold may be a fixed number or a percentage. The NSCC (508) first obtains a rejection rate by dividing the number of rejections with the number of PDU session requests. The rejection rate is compared with the threshold.

[0107] In an embodiment, the NSCC (508) determines that the UE (102) is in the condition where the UE (102) is facing an issue with at least one network service associated with the UE (102), when the number of PDU sessions requests sent to the network apparatus (104) and the number of rejections received from the network apparatus (104) meets the defined threshold. If the rejection rate is less than or equal to the threshold, the performance is within acceptable limits. If the rejection rate exceeds the threshold, it indicates that the network apparatus (104) is experiencing higher-than-acceptable rejections, potentially pointing to issues with resources, configurations, or policies.

[0108] In an embodiment, the NSCC (508) changes network slicing parameters of the PDU session established by the UE (102) with the network apparatus (104). For instance, the network slicing parameters may be changed when the issue is attributable to the result of the network slicing capability of the UE (102) or an incompatibility between the UE (102) and the network apparatus (104). Changing of the network slicing parameters involves adjusting the settings and configurations associated with a specific PDU session so that is may be optimized for use in a particular network slice. Changing network slicing parameters may lead to an optimized performance, an enhanced user experience, efficient resource utilization, and flexible service provisioning.

[0109] In an embodiment, the NSCC (508) detects a current state of the UE (102) and the issue associated with the network service associated with the UE (102). Detecting the current state of the UE (102) involves monitoring various parameters and signals to understand the connectivity, performance, and operational status of the UE (102) within the wireless network. For instance, the parameters may include connection status, signal strength, signal quality, data connection status, location information, capability information, and the like associated with the UE (102).

[0110] In an embodiment, the NSCC (508) determines at least one control action based on the current state of the UE (102) and the issue associated with the network service associated with the UE (102). The control action may refer to commands, requests, or signaling messages that the UE (102) sends to the network apparatus (104) to manage its connectivity, operations, and services. These actions are essential for maintaining the proper function of the UE (102) within the wireless network.

[0111] In an example, the control action may include ignoring the network slicing parameters. The network slicing parameters include at least one of the URSP, allowed or configured NSSAI list, or any other NSSAI lists. Further, the control action may include deleting the network slicing parameters, and routing application data over a default network slice assigned by the network apparatus (104). Further, the control action may include rejecting network slice requests from applications internally and routing by the UE application data over a default network slice assigned by the network apparatus (104). Further, the control action may include skipping re-evaluation of the URSP rules when the issue is associated with a network slice service associated with the UE (102). In addition, the control action may include utilizing a reserved bit in one of an uplink non-access stratum (UL NAS) message to indicate the network slicing capability of the UE (102) to ensure a compatibility between the UE (102) and the network apparatus (104).

[0112] In an embodiment, the NSCC (508) directs the UE (102) to transmit a PDU session establishment request message without including a specific network slice identifier to the network apparatus (104). When the PDU session establishment request does not include a specific network slice identifier, the network apparatus (104) may assign the PDU session to a default network slice based on the subscription, policies, and the service type associated with the UE (102). This may happen when the UE (102) is not configured to use network slicing or when it leaves the selection of the appropriate slice to the network apparatus (104). Thus, the network apparatus (104) may optimize resource allocations by selecting or determining the most appropriate slice based on real-time conditions.

[0113] In an embodiment, the NSCC (508) changes the network slicing capability of the UE (102) based on the current state of the UE (102). The NSCC (508) disables the network slicing capability based on the current state of the UE (102). For instance, the current state of the UE (102) may include service requirements, battery levels, network conditions, policies, and the like associated with the UE (102). When the network slicing capability is disabled, the UE (102) may access and utilize different network slices, each designed to meet specific performance, latency, or reliability requirements. This allows the UE (102) to connect to the most appropriate slice based on its current needs. When the network slicing capability is disabled, the UE (102) either connects to a default network slice or operates without the benefits of specialized slicing, often resulting in a more generic or standard network experience.

[0114] Further, the NSCC (508) performs requests related to the network slicing based on the current state of the UE (102) from application layers or network layers of the UE (102). The application layer interfaces directly with user applications and handles application-specific protocols and data formats. It provides services such as web browsing, messaging, and streaming to the end-user. The network layer manages the transmission and routing of data packets between the UE (102) and the network apparatus (104). It may include the IP layer, bearer management, and connectivity management. The application layer and the network layer are both crucial for enabling the UE (102) to effectively communicate with the network apparatus (104).

[0115] Fig. 6 is a block diagram that illustrates a schematic of the network apparatus (104) implemented to carry out the disclosed subject matter according to the embodiments as disclosed herein. As shown, the network apparatus (104) may include the memory (602), the processor (604), the communicator (606), and a controller (610).

[0116] In an embodiment, the controller (610) determines a plurality of parameters associated with the UE (102). For instance, the plurality of parameters may include a device type, a model number, an international mobile equipment identity (IMEI), and an IMEI software version (IMEI-SV) of the UE (102). The device type refers to the general category or classification of the UE (102) based on its functionality and usage. It describes the kind of device, such as a smartphone, tablet, IoT device, or a mobile hotspot. The model number is a unique identifier assigned by the manufacturer to each specific model of the UE (102). It helps in distinguishing between different versions or configurations of the UE (102). The IMEI is a unique 15-digit number assigned to the UE (102), used to identify the device in the wireless network. The IMEI-SV provides additional information about the software version of the IMEI of the UE (102).

[0117] In an embodiment, the controller (610) determines whether the UE (102) belongs to an allowed list for network slicing provisioning. The allowed list refers to a set of criteria or a list of networks, services, or frequencies that the UE (102) is permitted to connect to or use. For instance, the allowed list may include a network allowed list, a frequency allowed list, a service allowed list, and the like.

[0118] In an embodiment, the controller (610) configures network slicing parameters at the UE (102) when the UE (102) belongs to the allowed list for network slicing provisioning. For instance, the network slicing parameters include the URSP and allowed or configured NSSAI lists or any other NSSAI lists. The URSP provides rules and policies for the UE (102) to select the most appropriate network slice based on service requirements and network conditions. It helps optimize service performance and network resource utilization. The allowed or configured NSSAI lists defines network slices in which the UE (102) is allowed or configured to access. They guide the UE (102) in selecting the appropriate slice for its current needs.

[0119] The allowed NSSAI lists are network slices that the wireless network permits the UE (102) to use is a given area. The configured NSSAI lists refers to network slices configured for the UE (102) by the network apparatus (104). The allowed or configured NSSAI lists or any other NSSAI lists indicates the network slices that the UE (102) supports or requests. NSSAI lists helps to ensure that the network apparatus (104) may duly route and manage traffic based on the specific needs of the UE (102), optimizing performance and resource allocation.

[0120] In an embodiment, the controller (610) deletes network slicing parameters previously configured by the network apparatus (104) at the UE (102) when the UE (102) does not belong to the allowed list in a required NSSAI list. The required NSSAI list indicates which network slices the UE (102) requires for its services. When the UE (102) provides the needed NSSAI list to the network apparatus　(104), it reviews the request. If the network apparatus　(104) supports the requested slices in the specified region and the UE (102) has permission to access them, it will allow access to those network slices.For instance, the network apparatus (104) may assign a default slice for PDU sessions for the UE (102). The default slice is a network slice that is automatically selected and assigned to a PDU session when no specific slice is indicated by the UE (102) or when the UE (102) is not configured with specific slice preferences. The default slice ensures that the UE (102) may still access network services and maintain connectivity, even in the absence of explicit slice requests. The default slice may be determined based on one or more factors, such as network configurations, subscription profiles, network policies, and the like.

[0121] Figs. 7a and 7b are sequence diagrams that illustrate identification of a service / slice unavailability according to the embodiments as disclosed herein. As shown in the sequence diagrams, the UE (102) is in communication with the network apparatus (104) via the APP (100).

[0122] At operation S701, the UE (102) is configured with network slices by the network apparatus (104). Also, the UE (102) receives the URSP from the network apparatus (104). For example, the network slices configured may include:

[0123] Configured NSSAI:

[0124] S-NSSAI-D (Default slice - e.g. EMMB)

[0125] S-NSSAI-B (e.g. SST1:SD1 - Bandwidth slice)

[0126] S-NSSAI-L (e.g. SST1:SD2 - Latency slice)

[0127] URSP:

[0128] TD: PRIORITIZE_BANDWITH

[0129] RSD

[0130] S-NSSAI-B

[0131] DNN: xxx.yyy

[0132] At operation S702, the UE (102) transmits a PDU session establishment request (with slice SST1:SD1) to the network apparatus (104). At operation S703, the network apparatus (104) sends the PDU session establishment Reject with cause 91 (DNN not supported with no slice or in specific slice). The NSCC (508) detects the UE issue state and starts to ignore slicing parameters. At operation S704, the upper layers of the APP (100) request for bandwidth slice dnn_slice information from the UE (102). At operation S705, a modem of the UE (102) ignore the contents of URSP and reports no matching URSP rule available to the APP (100).

[0133] At operation S706, the upper layers of the APP (100) either route APP data over the default DNN if already established or sends PDU request for the present DNN to the UE (102). At operation S707, the UE (102) transmits a PDU session establishment request (without including S-NSSAI) to the network apparatus (104). At operation S708, the network apparatus (104) sends a PDU session establishment Accept with S-NSSAI set to the default slice S-NSSAI-D or EMBB to the UE (102). At operation S709, the APP data is routed over the default slice S-NSSAI-D. At operation S710, the configured NSSAI and allowed NSSAI shall be ignored and requested NSSAIs will not be included, in further registration requests.

[0134] Here, the NSCC (308) detects the issue of the UE (102) after the PDU request is rejected with cause 90 / 91. For instance, the issue may be detected after 5 retries and rejects. The UE (102) shall ignore network slicing parameters, such as the contents of configured NSSAI, allowed NSSAI, and the URSP. If the network apparatus (104) resends the network slicing parameters such as NSSAI lists, URSP rules etc., these shall be ignored by the UE (102). The UE (102) shall not request for any specific slices in Requested NSSAI IE of registration request or PDU session establishment request. The network apparatus (104) will assign the default slice S-NSSAI-D for the PDU sessions, due to which the PDU sessions will not fail. This thus enables the application data to be routed over the default slice S-NSSAI-D.

[0135] Fig. 8 is a sequence diagram that illustrates rejection of slice requests according to the embodiments as disclosed herein. As shown in the sequence diagram, the UE (102) is in communication with the network apparatus (104) via the APP (100) and a RIL (106).

[0136] At operation S801, the UE (102) is configured with network slices by the network apparatus (104). Also, the UE (102) receives the URSP from the network apparatus (104). For example, the network slices configured may include:

[0137] Configured NSSAI:

[0138] S-NSSAI-D (Default slice - e.g. EMMB)

[0139] S-NSSAI-B (e.g. SST1:SD1 - Bandwidth slice)

[0140] S-NSSAI-L (e.g. SST1:SD2 - Latency slice)

[0141] URSP:

[0142] TD: PRIORITIZE_BANDWITH

[0143] RSD

[0144] S-NSSAI-B

[0145] DNN: xxx.yyy

[0146] At operation S802, the APP (100) requests for a bandwidth slice from the RIL (106). At operation S803, the RIL (106) transmits a message to the APP (100) stating that the slice is not available. At operation S804, the APP (100) places a request to the RIL (106) requesting for data over the default slice S-NSSAI-D. At operation S805, the RIL (106) routes the APP data over default DNN, if already established. If not, the RIL (106) sends a PDU request for pre-set DNN (for example, ims / internet) to the UE (102). At operation S806, a modem of the UE (102) shall not evaluate the URSP to pick a network slice corresponding to the DNN from the URSP rule.

[0147] At operation S807, the UE (102) sends a PDU session establishment request (without including S-NSSAI) to the network apparatus (104). At operation S808, the network apparatus (104) sends the PDU session establishment accept message with S-NSSAI, which is set to default slice S-NSSAI-D or EMBB. At operation S809, the APP data is routed over the default slice S-NSSAI-D. At operation S810, the configured NSSAI and allowed NSSAI shall be ignored and requested NSSAIs will not be included, in further registration requests.

[0148] Here, when the APP (100) request for a slice, the RIL (106) shall reject the slice request. The APP data shall be routed over the default DNN if already established. If not, the RIL (106) shall send a request for establishment of the PDU for the default DNN. Furthermore, the UE (102) shall not evaluate the URSP to pick a network slice value corresponding to DNN from the URSP rule. Instead, the PDU Session establishment request shall be sent without including any S-NSSAI value. The network apparatus (104) shall map the PDU request to the default slice S-NSSAI-D (SST1 - EMBB).

[0149] Fig. 9 is a sequence diagram that illustrates controlling of the network slicing capability based on a model, IMEI, and IMEI-SV according to the embodiments as disclosed herein. As shown in the sequence diagram, a first UE (102A) and a second UE (102B) are in communication with the network apparatus (104).

[0150] At operation S901, the first UE (102A) sends the registration request (IMEI / IMEI-SV / No Requested NSSAI) to the network apparatus (104). At operation S902, the network apparatus (104) determines that the IMEI / IMEI-SV of the first UE (102A) belongs to the allowed list for network slicing provisioning. At operation S903, the network apparatus (104) sends a registration accept message to the first UE (102A). The registration accept message may include the allowed NSSAI and configured NSSAI set to S-NSSAI-D, S-NSSAI-B, or S-NSSAI-L. At operation S904, the network apparatus pushes the URSP rules to the first UE (102A). At operation S905, the first UE (102A) may request PDU sessions for the configured NSSAIs.

[0151] At operation S906, a network slicing provisioned sim card is inserted into the second UE (102B). The second UE (102B) is not intended to get network slicing provisioning parameters. At operation S907, the second UE (102B) sends a registration request (IMEI / IMEI-SV / No Requested NSSAI) to the network apparatus (104). At operation S908, the network apparatus (104) determines that the IMEI / IMEI-SV of the second UE (102B) does not belong to the allowed list for network slicing provisioning. At operation S909, the network apparatus (104) shall not send the configured NSSAI and the URSP to second UE (102B). The network apparatus (104) shall also delete any existing lists. At operation S910, the network apparatus (104) sends a registration Accept to the second UE (102B). The registration accept message may include the allowed NSSAI IE set to default slice S-NSSAI-D and without any configured NSSAI / URSP. At operation S911, the second UE (102B) cannot request for any slices and all data will be routed over the default slice S-NSSAI-B assigned by the network apparatus (104).

[0152] Here, the network apparatus (104) shall control network slicing provisioning based on model / device IMEI / IMEI-SV of the UE (102) (the first UE (102A) and the second UE (102B)), which is agreed and stored in a list (for example, allowed device list). If the / Model / Device IMEI / IMEI-SV belongs to the allowed list, the UE (102) is provisioned with the URSP, configured NSSAI, and corresponding allowed NSSAI. Thus, the network slices may be requested by the UE (102) as part of the requested NSSAI IE of the registration request or S-NSSAI IE of the PDU Session establishment request. If the Model / Device IMEI / IMEI-SV does not belong to the allowed list or is removed from the allowed list for network slicing provisioning, the network apparatus (104) shall not configure network slicing parameters. If the UE (102) was previously configured with network slicing parameters, all network slicing parameters such as the URSP, the configured NSSAI, and the corresponding allowed NSSAIs shall be deleted. Due to this, the UE (102) shall not request for any specific slices in the requested NSSAI IE of the registration request or S-NSSAI IE of the PDU Session establishment request. The network apparatus (104) will assign the default slice S-NSSAI-B for the PDU sessions, due to which the PDU sessions will not fail.

[0153] Fig. 10 is a sequence diagram that illustrates controlling of the network slicing capability based on a reserved bit of UE capability information according to the embodiments as disclosed herein. As shown in the sequence diagram, the first UE (102A) and the second UE (102B) are in communication with the network apparatus (104).

[0154] At operation S1001, the first UE (102A) sends the registration request (with 5GMM UE Capability reserved bit set to - network slicing ENABLED) to the network apparatus (104). At operation S1002, the network apparatus (104) determines that the network slicing parameters should be provisioned for the first UE (102A), since the first UE (102A) requested for the network slicing to be enabled. At operation S1003, the network apparatus (104) sends a registration accept message to the first UE (102A). The registration accept message may include the allowed NSSAI and the configured NSSAI set to S-NSSAI-D, S-NSSAI-B, or S-NSSAI-L. At operation S1004, the network apparatus (104) pushes the URSP rules to the first UE (102A). At operation S1005, the first UE (102A) may request for PDU sessions for the configured NSSAIs.

[0155] At operation S1006, the second UE (102B) sends a registration request (with 5GMM UE Capability reserved bit set to - network slicing DISABLED) to the network apparatus (104). At operation S1007, the network apparatus (104) determines that the network slicing parameters should not be provisioned for the second UE (102B) since the second UE (102B) requested for the network slicing to be disabled. At operation S1008, the network apparatus (104) sends a registration accept message (with Allowed NSSAI IE set to default slice S-NSSAI-D and without any configured NSSAI / URSP) to the second UE (102B). At operation S1009, the second UE (102B) cannot request any slice and all data will be routed over the default slice S-NSSAI-D assigned by the network apparatus (104).

[0156] Here, the NSCC (508) shall identify that the UE (102) is camped on the network apparatus (104), which is compatible to handle. The UE network slicing capability indicator determines to provision the network slicing parameters. The UE (102) shall report the network slicing capability (enable / disable) to the network apparatus (104) using one of the reserved bits of 5GMM UE capability IE, UE assistance information, or any of the UL NAS messages. If network slicing capability enable is indicated by the UE (102), the network apparatus (104) shall provision the UE (102) with the URSP rules, configured NSSAIs, and corresponding allowed NSSAI list. Further, the UE (102) may establish PDU sessions for the required network slices.

[0157] Figs. 11a and 11b are flow charts that illustrate a method for managing the network slicing capability of the UE (102) in a wireless network according to the embodiments as disclosed herein. The method may include operations 1102-1124. Each operation is explained in detail below.

[0158] At operation 1102, it is determined that the UE (102) is in a condition where it is facing an issue with a network service associated with the UE (102). For instance, the issue faced with the network services may include unavailability of internet, a mobile data service, a voice service, a hotspot service, or any network slice-specific services.

[0159] At operation 1104, it is determined whether the issue is attributable to a result of a network slicing capability of the UE (102) or an incompatibility between the UE (102) and the network apparatus (104). The network slicing capability refers to an ability of the UE (102) to connect with and utilize different network slices. It is possible to customize different network slices for different kinds of services. For instance, one slice may be prioritized for high data throughput (good for video streaming) and another slide might be tuned for low latency and high dependability (perfect for crucial applications like autonomous vehicles). Depending on the needs of the application it is executing, the UE (102) with network slicing functionality may connect too many network slices at once or switch between slices. Moreover, circumstances in which the UE (102) and the network apparatus　(104) are unable to completely interact or perform as intended together are referred to as incompatibilities between the two devices. The incompatibility may arise due to various technical mismatches, leading to issues like failed connections, reduced performance, or an inability to access certain network features.

[0160] At operation 1106, a number of PDU sessions requests sent to the network apparatus (104) and a number of rejections received from the network apparatus (104) are tracked. The UE (102) initiates the PDU session requests when it needs to create a data connection in order to use a certain service. The network apparatus　(104), which receives this request, provides the session an IP address or other network identifiers and sets aside the required resources. When the network apparatus　(104) rejects the request made by the UE (102) to initiate a PDU session, this is known as a PDU session request rejection. Rejects might be the result of things like unavailable resources, network policies, security issues, unavailable slices, and the like. The UE (102) cannot create the needed connection when a PDU session request is denied, and it might be necessary for it to attempt again later.

[0161] At operation 1108, it is determined whether the number of PDU sessions requests sent to the network apparatus (104) and the number of rejections received from the network apparatus (104) meets a defined threshold. The threshold　may　be expressed as a percentage or as a set amount. By dividing the total number of PDU session requests by the total number of rejections, the NSCC (508), first determines its rejection rate. Next, the rejection rate and threshold are contrasted.

[0162] At operation 1110, it is determined that the UE (102) is in the condition where the UE (102) is facing an issue with at least one network service associated with the UE (102), when the number of PDU sessions requests sent to the network apparatus (104) and the number of rejections received from the network apparatus (104) meets the defined threshold. The performance is within allowable bounds if the rejection rate is less than or equal to the threshold. When the rejection rate surpasses the predetermined threshold, it signifies that the network apparatus (104) is encountering more rejections than what is considered reasonable. This might potentially suggest problems with policies, settings, or resources.

[0163] At operation 1112, network slicing parameters of the PDU session established between the UE (102) and the network apparatus (104) are changed. For instance, the network slicing parameters may be changed when the issue is attributable to the result of the network slicing capability of the UE (102) or an incompatibility between the UE (102) and the network apparatus (104). To optimize a PDU session for a certain network slice, it is necessary to modify its settings and configurations. This is known as changing the network slicing parameters. Adjusting the network slicing settings may result in improved user experience, flexible service provisioning, effective resource use, and better performance.

[0164] At operation 1114, a current state of the UE (102) is detected along with the issue associated with the network service associated with the UE (102). Monitoring a range of characteristics and signals is necessary to determine the operational condition, performance, and connection of the UE (102) in the wireless network in order to detect its current state. As an example, the parameters might include the　position information, capability information, signal strength, signal quality, connection status, and the like of the UE　(102).

[0165] At operation 1116, at least one control action is determined based on the current state of the UE (102) and the issue associated with the network service associated with the UE (102). The orders, requests, or signalling messages that the network apparatus　(104) receives from the UE (102) in order to manage its connection, operations, and services may be referred to as control actions. These operations are necessary to keep the UE (102) operating properly within the wireless network.

[0166] In an example, the control action may include ignoring the network slicing parameters. The network slicing parameters include at least one of the URSP, allowed or configured NSSAI list, or any other NSSAI lists. Further, the control action may include deleting the network slicing parameters, and routing application data over a default network slice assigned by the network apparatus (104). Further, the control action may include rejecting network slice requests from applications internally and routing by the UE application data over a default network slice assigned by the network apparatus (104). Further, the control action may include skipping re-evaluation of the URSP rules when the issue is associated with a network slice service associated with the UE (102). In addition, the control action may include utilizing a reserved bit in one of an uplink non-access stratum (UL NAS) message to indicate the network slicing capability of the UE (102) to ensure a compatibility between the UE (102) and the network apparatus (104).

[0167] At operation 1118, the network slicing parameters of the PDU session established by the UE (102) with the network apparatus (104) are changed by performing the at least one control action determined in operation 1116. Changing the network slicing parameters of a PDU session is done to adapt to evolving service requirements, optimize network resource allocation, ensure quality of service, and manage network performance. By dynamically adjusting these parameters, the network apparatus (104) may better meet user needs and maintain efficient and effective operation

[0168] At operation 1120, the network slicing parameters may be changed or modified based on the current state of the UE (102). This is explained in greater details in operations 1122-1124 below.

[0169] At operation 1122, depending on the current state of the UE (102), the NSCC (508) disables　the network slicing capabilities. For example, the service needs, battery level, network circumstances, regulations, and other related information related to the UE (102) may be included in its current status. The UE (102) may access and use several network slices, each created to satisfy certain performance, latency, or reliability requirements, when the network slicing functionality is disabled. As a result, the UE (102) may connect to the slice that best suits its needs at that moment. The UE (102) either connects to a default network slice or functions without the advantages of customized slicing when the network slicing feature is disabled, which frequently results in a more general or standard network experience.

[0170] At operation 1124, based on the current　state of the UE (102), the NSCC (508) handles requests for network slicing from the application or network layers of the UE (102). Application-specific protocols and data formats are handled by the application layer, which also acts as a direct interface with user applications. It offers the user features including chatting, streaming, and online surfing. Between the UE (102) and the network apparatus　(104), the network layer controls packet transmission and routing. It covers bearer management, connection management, and the IP layer. For the UE (102) to be able to connect with the network apparatus　(104), both the application layer and the network layer are essential.

[0171] At operation 1126, a PDU session establishment message is transmitted to the network apparatus (104) without including a specific network slice identifier in a required NSSAI list. The required NSSAI list specifies the exact network slices that the UE (102) needs for its services. When the UE (102) sends the required NSSAI list to the network apparatus (104), the network apparatus (104) evaluates the request. If the network apparatus (104) supports the requested slices in the specific area and the UE (102) is authorized to access them, it will grant access to those network slices. Further, the network apparatus (104) may allocate the PDU session to a default network slice based on the subscription, rules, and service type associated with the UE (102) in cases where the PDU session setup request lacks a specified network slice identification. This might occur if the UE (102) is not set up to employ network slicing or if it allows the network apparatus　(104) to choose the appropriate slice. Thus, by choosing or figuring out the best slice depending on current circumstances, the network apparatus (104) may optimize resource allocations.

[0172] Fig. 12 is a flow chart that illustrates a method for managing network slicing parameters according to the embodiments as disclosed herein. The method may include operations 1202-1208. Each operation is explained in further detail below.

[0173] At operation 1202, a plurality of parameters associated with the UE (102) is determined. For instance, the plurality of parameters may include a device type, a model number, an international mobile equipment identity (IMEI), and an IMEI software version (IMEI-SV) of the UE (102). The term "device type" describes how the UE (102) is often categorized or classified according to its use and capabilities. It specifies the type of device―tablet, smartphone, Internet of Things, or mobile hotspot, for example. The manufacturer gives each distinct model of the UE (102) a unique number known as the model number. It facilitates the differentiation of various UE versions or settings (102). The UE (102) is uniquely identified by a 15-digit number called the IMEI, which is used to identify the device on the wireless network. The IMEI software version of the UE　(102) is further detailed by the IMEI-SV.

[0174] At operation 1204, it is determined whether the plurality of parameters associated with the UE (102) belongs to an allowed list for Network Slicing Provisioning. The allowed list refers to a set of criteria or a list of networks, services, or frequencies that the UE (102) is permitted to connect to or use. For instance, the allowed list may include a network allowed list, a frequency allowed list, a service allowed list, and the like.

[0175] At operation 1206, the network slicing parameters at the UE (102) are configured when the plurality of parameters associated with the UE (102) belongs to the allowed list. For instance, the network slicing parameters include the URSP and allowed or configured NSSAI lists. In order to choose the best network slice for the UE (102) in accordance with service needs and network circumstances, the URSP offers rules and regulations. It facilitates the best possible use of network resources and service performance. The network slices that the UE (102) is permitted or configured to access are defined by the allowed or configured NSSAI lists. They assist the UE (102) in choosing the best slice for its present requirements.

[0176] At operation 1208, the network slicing parameters previously configured by the network apparatus (104) at the UE (102) are deleted. When the parameters linked to the UE (102) are not in the permitted list, this deletion takes place. For PDU sessions, the network apparatus　(104) designates a default slice for the UE (102). When the UE (102) is not set with specific slice preferences or does not designate a preferred slice, the default slice is a network slice that is automatically selected and allocated to a PDU session. Even in the lack of explicit slice requests, the default slice makes sure that the UE (102) may continue to connect and utilize network services. The default slice may be determined based on one or more factors, such as network configurations, subscription profiles, network policies, and the like.

[0177] The various actions, acts, blocks, steps, operations or the like in the method is 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 are omitted, added, modified, skipped, or the like without departing from the scope of the proposed method. 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 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 preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the scope of the embodiments as described herein.

Claims

1.A method for managing a network slicing capability of a user equipment (UE) (102) in a wireless network, comprises:determining, by the UE (102), that the UE (102) is in a condition where the UE (102) is facing an issue with at least one network service associated with the UE (102);determining, by the UE (102), whether the issue is attributable to a result of at least one of a network slicing capability of the UE (102) or an incompatibility between the UE (102) and a network apparatus (104); andchanging, by the UE (102), network slicing parameters of a protocol data unit (PDU) session established by the UE (102) with the network apparatus (104) in response that the issue is attributable to the result of at least one of the network slicing capability of the UE (102) or the incompatibility between the UE (102) and the network apparatus (104).2.The method as claimed in claim 1, further comprising:transmitting, by the UE (102), a PDU session establishment request message without including a specific network slice identifier in a required network slice selection assistance information (NSSAI) list to the network apparatus (104).3.The method as claimed in claim 1, wherein the at least one network service comprises at least one of an unavailability of internet at the UE (102), a mobile data service of the UE (102), a voice service of the UE (102), a hotspot service of the UE (102), or network slice-specific services.4.The method as claimed in claim 1, wherein changing the network slicing parameters comprises:detecting, by the UE (102), a current state of the UE (102) and the issue;determining, by the UE (102), at least one control action based on the current state of the UE (102) and the issue; andchanging, by the UE (102), the network slicing parameters of the PDU session established by the UE (102) with the network apparatus (104) by performing the at least one control action.5.The method as claimed in claim 4, wherein the at least one control action comprises at least one of:ignoring, by the UE (102), the network slicing parameters, wherein the network slicing parameters comprises at least one of a user equipment route selection policy (URSP), allowed or configured network slice selection assistance information (NSSAI) list, or other NSSAI lists,deleting, by the UE (102), the network slicing parameters, and routing application data over a default network slice assigned by the network apparatus (104),rejecting, by the UE (102), network slice requests from applications internally and routing by the UE application data over the default network slice assigned by the network apparatus (104),skipping, by the UE (102), re-evaluation of URSP rules based on the issue, orutilizing, by the UE (102), a reserved bit in one of an uplink non-access stratum (UL NAS) message to indicate the network slicing capability of the UE (102) to ensure a compatibility between the UE (102) and the network apparatus (104).6.The method as claimed in claim 1, wherein changing the network slicing capability comprises:detecting, by the UE (102), a current state of the UE (102); andperforming, by the UE (102), one of:disabling the network slicing capability based on the current state of the UE (102), orselectively servicing or performing requests related to network slicing based on the current state of the UE (102) from application layers or network layers of the UE (102),wherein the method further comprising utilizing a reserved bit in one of an uplink non-access stratum (UL NAS) message to indicate disabling of the network slicing capability of the UE (102) to the network apparatus (104).7.The method as claimed in claim 1, wherein determining that the UE (102) is in the condition where the UE (102) is facing the issue with at least one network service associated with the UE (102) comprises:tracking, by the UE (102), a number of PDU sessions requests sent to the network apparatus (104) and a number of rejections received from the network apparatus (104);determining, by the UE (102), whether at least one of the number of PDU sessions requests sent to the network apparatus (104) and the number of rejections received from the network apparatus (104) meets a defined threshold; anddetermining, by the UE (102), that the UE (102) is in the condition where the UE (102) is facing the issue with at least one network service associated with the UE (102), in response that at least one of the number of PDU sessions requests sent to the network apparatus (104) and the number of rejections received from the network apparatus (104) meets the defined threshold.8.A method for managing a network slicing capability of a user equipment (UE) (102) in a wireless network, comprises:determining, by a network apparatus (104), a plurality of parameters associated with the UE (102), wherein the plurality of parameters comprises a device type of the UE (102), a model number of the UE (102), an international mobile equipment identity (IMEI) of the UE (102), and an IMEI software version (IMEI-SV) of the UE (102);determining, by the network apparatus (104), whether the UE (102) belongs to an allowed list for network slicing provisioning;configuring network slicing parameters at the UE (102) in response that the UE (102) belongs to the allowed list for network slicing provisioning; anddeleting network slicing parameters previously configured by the network apparatus (104) at the UE (102) in response that the UE (102) does not belongs to the allowed list for network slicing provisioning.9.The method as claimed in claim 8, wherein the network slicing parameters comprises at least one of a user equipment route selection policy (URSP) and an allowed or configured network slice selection assistance information (NSSAI) list or other NSSAI lists.10.A user equipment (UE) (102) for managing a network slicing capability of the UE in a wireless network, comprises:memory (502) storing instructions; andat least one processor (504)wherein the instructions, when executed by the processor (504) individually or collectively, cause the UE to:determine that the UE (102) is in a condition where the UE (102) is facing an issue with at least one network service associated with the UE (102);determine whether the issue is attributable to a result of at least one of a network slicing capability of the UE (102) or an incompatibility between the UE (102) and a network apparatus (104); andchange network slicing parameters of a protocol data unit (PDU) session established by the NSCC with the network apparatus (104) in response that the issue is attributable to the result of at least one of the network slicing capability of the UE (102) or the incompatibility between the UE (102) and the network apparatus (104).11.The UE (102) as claimed in claim 10, wherein the instructions, when executed by the processor (504) individually or collectively, cause the UE to:transmit a PDU session establishment request message without including a specific network slice identifier in a requested network slice selection assistance information (NSSAI) list to the network apparatus (104).12.The UE (102) as claimed in claim 10, wherein the instructions, when executed by the processor (504) individually or collectively, cause the UE to:detect a current state of the UE (102) and the issue;determine at least one control action based on the current state of the UE (102) and the issue; andchange the network slicing parameters of the PDU session established by the UE (102) with the network apparatus (104) by performing the at least one control action.13.The UE (102) as claimed in claim 10, wherein the instructions, when executed by the processor (504) individually or collectively, cause the UE to:detects a current state of the UE (102); andperforms one of:disables the network slicing capability based on the current state of the UE (102), orservices selectively or performs requests related to network slicing based on the current state of the UE (102) from application layers or network layers of the UE (102).14.The UE (102) as claimed in claim 10, wherein the instructions, when executed by the processor (504) individually or collectively, cause the UE to:tracks a number of PDU sessions requests sent to the network apparatus (104) and a number of rejections received from the network apparatus (104);determines whether at least one of the number of PDU sessions requests sent to the network apparatus (104) and the number of rejections received from the network apparatus (104) meets a defined threshold; anddetermines that the UE (102) is in the condition where the UE (102) is facing the issue with at least one network service associated with the UE (102), in response that at least one of the number of PDU sessions requests sent to the network apparatus (104) and the number of rejections received from the network apparatus (104) meets the defined threshold.15.A network apparatus (104) for managing a network slicing capability of a user equipment (UE) (102) in a wireless network, comprises:memory (502) storing instructions; andat least one processor (504),wherein the instructions, when executed by the processor (504) individually or collectively, cause the network apparatus to:determine a plurality of parameters associated with the UE (102), wherein the plurality of parameters comprises a device type of the UE (102), a model number of the UE (102), an international mobile equipment identity (IMEI) of the UE (102), and an IMEI software version (IMEI-SV) of the UE (102);determine whether the UE (102) belongs to an allowed list for network slicing provisioning;configure network slicing parameters at the UE (102) in response that the UE (102) belongs to the allowed list for network slicing provisioning; anddelete network slicing parameters previously configured by the network apparatus (104) at the UE (102) in response that the UE (102) does not belongs to the allowed list for network slicing provisioning.

Images