Patent ID: 12192748

The same reference numerals are used to represent the same elements throughout the drawings.

DETAILED DESCRIPTION

The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of various embodiments of the disclosure as defined by the claims and their equivalents. It includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the various embodiments described herein can be made without departing from the scope and spirit of the disclosure. In addition, descriptions of well-known functions and constructions may be omitted for clarity and conciseness.

The terms and words used in the following description and claims are not limited to the bibliographical meanings, but, are merely used by the inventor to enable a clear and consistent understanding of the disclosure. Accordingly, it should be apparent to those skilled in the art that the following description of various embodiments of the disclosure is provided for illustration purpose only and not for the purpose of limiting the disclosure as defined by the appended claims and their equivalents.

It is to be understood that the singular forms “a,” “an,” and “the” include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to “a component surface” includes reference to one or more of such surfaces.

In the disclosure, the word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any embodiment or implementation of the subject matter described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments.

While the disclosure is susceptible to various modifications and alternative forms, specific embodiment thereof has been shown by way of example in the drawings and will be described below. It should be understood, however, that it is not intended to limit the disclosure to the particular forms disclosed, but on the contrary, the disclosure is to cover all modifications, equivalents, and alternatives falling within the scope of the disclosure.

The terms “comprises”, “comprising”, or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a setup, device or method that comprises a list of components or steps does not include only those components or steps but may include other components or steps not expressly listed or inherent to such setup or device or method. In other words, one or more elements in a system or apparatus proceeded by “comprises . . . a” does not, without more constraints, preclude the existence of other elements or additional elements in the system or apparatus.

Embodiments of the disclosure relate to a method for connecting a user equipment (UE) to a data network name (DNN) in a public network integrated non-public network (NPN). The UE may be moving from one location to another location, when connected to a network. The location may or may not have access to NPN services. When the UE tries to connect to DNN and slice having NPN services from a location with no access to the NPN services, a session management (SM) retry timer is enabled for reconnecting to the DNN, which may cause service discontinuity and latency. The disclosure provides a method in which the UE can identity the DNN and a network slice allocated for the NPN, from a list of DNNs and network slices. The UE can stop the SM retry timer and connect to the DNN and the network slice allocated for the NPN. In addition, when the UE is moving from a location with access to the NPN services to another location with no access to the NPN services, the UE can connect to normal DNNs, based on the list. Hence, the disclosure allows faster connection of the UE to the NPN services and normal data services. In addition, the disclosure ensures continuity of service.

Further embodiments of the disclosure relate to a method for connecting the UE to the DNN, when the UE tries to access higher priority DNNs. The disclosure allows the UE to connect to the higher priority DNN after detecting inactivity of packet transmission for a pre-determined time period. Hence, the UE can connect to highest priority DNN without any intervention from network server.

FIG.1illustrates an environment100for connecting a UE to a DNN in a public network integrated NPN according to an embodiment of the disclosure.

Referring toFIG.1, the environment100comprises a cell101and a UE102. The cell101is a geographical area covered by a frequency emitted by a base station in a in a public network integrated NPN. The UE102may be camped on the cell101. The public network integrated NPN is a NPN made available via public land mobile network (PLMN). The NPN is made available by means of dedicated DNNs and network slice instances allocated for the NPN. The DNN is a reference or identifier to a data network. Network slicing is a network architecture that enables the multiplexing of virtualized and independent logical networks on the same physical network infrastructure. Each network slice is an isolated end-to-end network tailored to fulfil diverse requirements requested by a particular application. The DNN defines the data network to which the UE102requests connectivity to establish access session. This access session is mapped with a network slice allocated for the NPN services. The UE102may be a handheld device associated with a user. For example, the UE102may be a smartphone, a tablet, and the like. The UE102may be any computing device, such as a laptop computer, a desktop computer, a personal computer (PC), a notebook, a smartphone, a tablet, e-book readers, a server, a network server, a cloud-based server, and the like. The UE102may have a subscription for the PLMN to access the NPN services.

The UE102may move from one location to another location in the cell101and from the cell101to another cell in the public network integrated NPN.FIG.1illustrates the mobility of the UE102from a first location103to a second location104in the cell101. The first location103and the second location104may be a closed access group (CAG) location or a non-CAG location. Closed access group identifies a group of subscribers who are permitted to access a location with the NPN services. CAG is used to prevent UEs which are not allowed to access the NPN services. The location with the NPN services is termed as the CAG location in the description. The location with no access to the NPN services or access to normal data services is termed as the non-CAG location in the description. In an example, the first location103may be the non-CAG location, and the second location104may be the CAG location. In another example, the first location103may be the CAG location, and the second location104may be the non-CAG location. The UE102may attempt to connect to the prioritized DNN from the first location103. The first location103may not have access to the prioritized DNN. A session management (SM) retry timer may be enabled for reconnecting to the prioritized DNN. The SM retry timer indicates a configured UE retry wait time value for the UE102to control session management retry behaviour of the UE102, when prior session management request was rejected by the network. In the disclosure, the UE102is configured to identify a prioritized DNN and a corresponding network slice, instead of waiting for the SM retry timer to expire. Further, the UE102is configured to disable the SM retry timer upon identifying the prioritized DNN and the corresponding network slice. Furthermore, the UE102is configured to evaluate a user route selection policy (URSP) rule. URSP Rules are used to determine whether data detected from an application in the UE102can be associated to an established protocol data unit (PDU) session or there is a need to trigger the establishment of a new PDU session. The UE102evaluates the URSP rule for connecting the UE102to the prioritized DNN and the corresponding network slice.

In an embodiment of the disclosure, the disclosure provides a method for the UE102to connect to the DNN, when the UE102receives a rejection cause from a network server. The UE102may be camped on the cell101. The UE102may send a request to the network server to connect to a higher priority DNN and via a corresponding network slice. The UE102may receive the rejection cause and the SM retry timer may be enabled for re-connecting to the higher priority DNN. The UE102detects inactivity of packet transmission for a pre-determined time period after the SM retry timer is disabled. Further, the UE102re-evaluates the URSP rule, based on the detection. The UE102is connected to the higher priority DNN, and the corresponding network slice based on the evaluation.

FIG.2illustrates a scenario200illustrating connecting a UE102to a DNN in a public network integrated NPN according to the related art.

Referring toFIG.2, the scenario200illustrates UE102connected to a normal DNN referred as DNN2, in the first location103, at time instance1. The normal DNN is not allocated for the NPN services. The normal DNN is also referred as a non-prioritized DNN in the description. In a first example, consider the first location103is the non-CAG location. The UE102may attempt to connect to a prioritized DNN referred as DNN1(not shown inFIG.2). The priority of DNN1may be higher as compared to normal DNN in the URSP rule. In addition, the DNN1is not available the non-CAG location. Hence, the UE102receives a rejection cause from the network server. The common rejection causes may include #8“operator determined barring”, #27“missing or unknown DNN”, #32“service option not supported”, #33“requested service option not subscribed”, #70“missing or unknown DNN in a slice”, and the like. The SM retry timer is enabled for reconnecting to the DNN1. At time instance2, the UE102moves to the second location104. The second location104may be the CAG location. DNN1is available in the CAG location. However, the UE102will not be able to connect to the DNN, since the SM retry timer is enabled. The UE102remains connected to the DNN2. The UE102needs to wait until the SM retry timer expires. The default value of the SM retry timer is 12 minutes. Hence, there is a service discontinuity and latency caused due to waiting for the SM retry timer to expire and connect to the NPN services. In addition, this leads to poor user experience. In a second example, consider the first location103is the CAG location. The priority of the normal DNN i.e., DNN2may be higher as compared to the DNN1. The UE102in the CAG location will receive the rejection cause, when the UE102tries to connect to the normal DNN, as network is providing connectivity through prioritized DNNs in the CAG location. The SM retry timer is enabled for reconnecting to the DNN2. The UE102remains connected to the DNN1. The UE102needs to wait until the SM retry timer expires to connect to the DNN2.

FIG.3illustrates a flowchart illustrating method operations for connecting a UE102to a DNN in a public network integrated NPN according to an embodiment of the disclosure.

Referring toFIG.3, a method300may comprise one or more operations. The method300may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, and functions, which perform particular functions or implement particular abstract data types.

The order in which the method300is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method. Additionally, individual blocks may be deleted from the methods without departing from the scope of the subject matter described herein. Furthermore, the method can be implemented in any suitable hardware, software, firmware, or combination thereof.

At operation301, the UE102identifies the prioritized DNN and the corresponding network slice, from the list of prioritized DNNs and network slices. Initially, the UE102is in the first location103in the cell101. The UE102connected to the non-prioritized DNN attempts to connect to the prioritized DNN from the first location103. The prioritized DNN may not be available in the first location103. The priority of the prioritized DNN is greater than the priority of a normal DNN in the first location103in the URSP rule. Hence, the UE102receives the rejection cause from the network. The SM retry timer is enabled for reconnecting to the prioritized DNN. The SM retry timer is enabled upon receiving the rejection cause from a network server when the UE102requests to connect to the prioritized DNN in the first location103. For example, the SM retry timer is enabled with a default value of 12 minutes. The UE102moves from the first location103to the second location104in the cell101. The UE102may be configured to identify the prioritized DNN and the corresponding network slice, when the SM retry timer is still running for reconnecting to the prioritized DNN. The UE102is not allowed to send a request for the same DNN i.e., the prioritized DNN until SM retry time expires. The UE102may identity the prioritized DNN and the corresponding network slice from the list of prioritized DNNs and network slices. The list of prioritized DNNs and network slices is stored in the UE102. In an embodiment of the disclosure, the list of prioritized DNNs and network slices is determined based on historical DNN connections associated with the UE102. The UE102may monitor overtime the availability of the prioritized DNNs and corresponding network slices. For example, a user associated with the UE102may have visited a hospital. The hospital may be provided with the NPN services. The UE102may have connected to a DNN1allocated for the NPN services. This information may be stored as a first entry in the list. The first entry may comprise a location (example, the hospital) along with the DNN1and corresponding network slice. After few days or a month, the UE102may visit an airport. The airport may be provided with the NPN services. The UE102may have connected to a DNN2allocated for the NPN services. This information may be stored as a second entry in the list. The second entry may comprise the location (example, the airport) along with the DNN2and corresponding network slice. In this way, the UE102may determine the list of prioritized DNNs and network slices based on historical DNN connections associated with the UE102. The determined list of prioritized DNNs and network slices may be stored in the UE102. A person skilled in the art will appreciate that entries in the list may be associated with any other information associated with the identified DNN and the corresponding slice. In another embodiment of the disclosure, the list of prioritized DNNs and network slices may be preconfigured by the network server in the UE102. For example, the network server may preconfigure the list of prioritized DNNs and network slices during initial registration of the UE102with the NPN services. The UE102may subscribe to the NPN services by sending a registration request to the network server. The network server may preconfigure the list of prioritized DNNs and network slices, upon receiving the registration request. The UE102may be configured to identity the prioritized DNN and corresponding network slice from the list of prioritized DNNs and network slices when in the second location104.

FIGS.4A and4Bshow illustrations for connecting a UE to a DNN in the public network integrated NPN, according to various embodiments of the disclosure.

Referring toFIG.4A, in element400, the UE102moves from the first location103to the second location104. In a first scenario, the first location103is a non-CAG location, and the second location104is a CAG location. At a time instance1, the UE102may be connected to DNN2in the non-CAG location. The UE102may have attempted to connect to a prioritized DNN from the non-CAG location. The prioritized DNN may be a DNN allocated for the NPN services. This is also referred as an NPN-specific DNN. The SM retry timer may be running for reconnecting to the NPN-specific DNN. At a time instance2, the UE102may move from the non-CAG location to the CAG location. The UE102identifies whether the prioritized DNN and the corresponding network slice is present in the list of prioritized DNNs and network slices. The prioritized DNN is illustrated as DNN1. In a second scenario, the first location103is a CAG location, and the second location104is a non-CAG location. At a time instance1, the UE102may be connected to DNN1in the CAG location. The priority of normal DNN may be greater than the NPN-specific DNN. The UE102may have attempted to connect to a prioritized DNN from the CAG location. The SM retry timer may be running for reconnecting to the normal DNN. At a time instance2, the UE102may move from the CAG location to the non-CAG location. The UE102identifies whether the prioritized DNN and the corresponding network slice is not present in the list of prioritized DNNs and network slices.

Referring back toFIG.3, at operation302, the UE102disables the SM retry timer upon identifying the prioritized DNN and the corresponding network slice. The SM retry timer may be implemented as a software timer in the UE102. The SM retry timer may be associated with a value indicated by the network server. The network server may transmit value associated with the SM retry timer in the rejection cause transmitted by the network server. For example, the rejection cause may be an ATTACH REJECT message. The SM retry timer which is enabled for reconnecting to the prioritized DNN may be disabled by the UE102, upon identifying the prioritized DNN and the corresponding network slice. Since the UE102has information on availability of the prioritized DNNs and corresponding network slices from the list, the UE102need not wait for the SM retry timer to expire and then connect to the prioritized DNN. Once the UE102identifies the prioritized DNN and the corresponding network slice, the UE102may disable the SM retry timer. For example, initial value of the SM retry timer may be 12 minutes. The UE102may identify the prioritized DNN and the corresponding network slice. The value associated with the SM retry timer may have decremented to 5 minutes. The UE102may disable the SM retry timer at this point. Referring again to the element400inFIG.4A, the SM retry timer may be disabled in both the first and second scenarios, upon identifying the prioritized DNN and the corresponding network slice.

Referring back toFIG.3, at operation303, the UE102evaluates the URSP rule for connecting the UE102to the prioritized DNN and the corresponding network slice. The URSP rule is used to determine if data detected from an application in the UE102can be associated to an established PDU session or there is a need to trigger the establishment of a new PDU session. The URSP includes a prioritized list of URSP rules. Each URSP rule contains a Traffic descriptor containing one or more components. The traffic descriptor determines when each URSP rule is applicable. A URSP rule is determined to be applicable when every component in the traffic descriptor matches corresponding information from the application in the UE102. Each URSP rule contains a list of route selection descriptors containing one or multiple route selection descriptors each having a different route selection descriptor precedence value. Table 1 illustrates the URSP rules. As seen from the table, the URSP rules are associated with the traffic descriptors containing the one or more components. Table 2 illustrates the route selection descriptors. For example, access type preference indicates preferred Access Type (3GPP or non-3GPP or multi-access) when the UE102establishes the PDU Session for the application. The 3GPP or non-3GGP access for offloading the data of the application may be determined from the access type preference.

TABLE 1PCF permittedInformationto modify in anameDescriptionCategoryUE contextScopeRuleDetermines theMandatoryYesUE contextPrecedenceorder the URSPrule is enforced inthe UE.TrafficThis part definesMandatorydescriptorthe Trafficdescriptorcomponents for theURSP rule.ApplicationIt consists of OSIdOptionalYesUE contextdescriptorsand OSAppId(s).IPDestination IP 3OptionalYesUE contextdescriptorstuple(s) (IP addressor IPv6 networkprefix, portnumber, protocolID of the protocolabove IP).DomainDestinationOptionalYesUE contextdescriptorsFQDN(s)Non-IPDescriptor(s) forOptionalYesUE contextdescriptorsdestinationinformation of non-IP trafficDNNThis is matchedOptionalYesUE contextagainst the DNNinformationprovided by theapplication.ConnectionThis is matchedOptionalYesUE contextCapabilitiesagainst theinformationprovided by a UEapplication when itrequests a networkconnection withcertain capabilities.List of RouteA list of RouteMandatorySelectionSelectionDescriptorsDescriptors.

TABLE 2InformationPCF permitted tonameDescriptionCategorymodify in URSPScopeRouteDetermines the orderMandatoryYesUE contextSelectionin which the RouteDescriptorSelection DescriptorsPrecedenceare to be applied.RouteThis part defines theMandatoryselectionroute selectioncomponentscomponentsSSC ModeOne single value ofOptionalYesUE contextSelectionSSC mode. (NOTE 5)Network SliceEither a single valueOptionalYesUE contextSelectionor a list of values ofS-NSSAI(s).DNNEither a single valueOptionalYesUE contextSelectionor a list of values ofDNN(s).PDU SessionOne single value ofOptionalYesUE contextTypePDU Session TypeSelectionNon-SeamlessIndicates if theOptionalYesUE contextOffloadtraffic of theindicationmatching applicationis to be offloaded tonon-3GPP accessoutside of a PDUSession.Access TypeIndicates theOptionalYesUE contextpreferencepreferred AccessType (3GPP or non-3GPP or Multi-Access) when theUE establishes aPDU Session for thematchingapplication.RouteThis part defines theOptionalSelectionRoute ValidationValidationCriteria componentsCriteria (NOTE 6)Time WindowThe time windowOptionalYesUE contextwhen the matchingtraffic is allowed.The RSD is notconsidered to bevalid if the currenttime is not in thetime window.LocationThe UE locationOptionalYesUE contextCriteriawhere the matchingtraffic is allowed.The RSD rule is notconsidered to bevalid if the UElocation does notmatch the locationcriteria.

The UE102receives updated URSP rules and evaluates or evaluates the URSP rules in a timely manner when certain conditions are met. For example, the conditions in the methods of the related art may include the URSP is updated by policy control function (PCF), the UE moves from evolved packet core (EPC) to 5G Core (5GC), change of allowed network slice selection assistance information (NSSAI) or configured NSSAI, change of DNN availability, UE registers over 3GPP or non-3GPP access, and UE establishes connection to a WLAN access. In the systems of the related art, change of DNN availability status, or SM Retry timer expiry is not mentioned as one of the criteria to re-evaluate URSP rule. In the disclosure, the UE102is configured to evaluate the URSP rule for connecting the UE102to the prioritized DNN and the corresponding network slice. The UE102evaluates the URSP rule to determine whether the priority of the prioritized DNN is greater than current DNN. The UE102connects to the prioritized DNN and the corresponding network slice, upon determination. Referring again to the element400inFIG.4A, in the first scenario, the UE connects to DNN1after evaluating the URSP rule. In the second scenario, the UE connects to DNN2after evaluating the URSP rule. Hence, the disclosure allows faster connection of the UE102to the NPN services and the normal data services.

Reference is now made to element401inFIG.4B.FIG.4Billustrates connecting the UE102to the DNN in a public network integrated NPN. At a time instance1, the UE102is in the first location103. The first location103may be an area outside a hospital. The first location103may be a non-CAG location. The UE102attempts to connect to the NPN-specific DNN. The SM retry timer is enable for reconnecting to the NPN-specific DNN. At a time instance2, the UE102moves from the first location103to the second location104. The second location104may be an area inside the hospital. The second location104may be a CAG location. The UE102identifies the NPN-specific DNN and corresponding network slice from the list of prioritized DNNs and network slices, when the SM retry timer is still running. Further, the UE102disables the SM retry timer, upon identifying the NPN-specific DNN and the corresponding network slice. Then, the UE102evaluates the URSP rule to connect to the NPN-specific DNN. Hence, the disclosure allows faster connection of the UE102to the NPN services.

FIG.5illustrates a scenario500illustrating connecting a UE102to a DNN in a public network integrated NPN when a UE102receives a rejection cause according to the related art.

Referring toFIG.5, at time instance1, the UE102sends a request to the network server to connect to the higher priority DNN and via the corresponding network slice. The UE102is connected to DNN2and a corresponding network slice. At time instance2, the UE102receives a rejection cause from the network server. The SM retry timer is enabled for re-connecting to the higher priority DNN, upon receiving the rejection cause. In the systems of the related art, there is no clear approach for retrying to connect to the higher priority DNN, after the SM retry timer expires. Hence, at a time instance3, the UE102remains connected to lower priority DNN i.e., DNN2.

Hence, user will be experiencing poor services even though higher priority DNN with better services may be available.

FIG.6illustrates a flowchart illustrating method operations for connecting a UE102to a DNN in a public network integrated NPN, when a UE102receives a rejection cause according to an embodiment of the disclosure.

Referring toFIG.6, a method600may comprise one or more operations. The method600may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, and functions, which perform particular functions or implement particular abstract data types.

The order in which the method600is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method. Additionally, individual blocks may be deleted from the methods without departing from the scope of the subject matter described herein. Furthermore, the method can be implemented in any suitable hardware, software, firmware, or combination thereof.

At operation601, the UE102receives the rejection cause when the UE102sends a request to the network server to connect to the higher priority DNN and via the corresponding network slice. Common rejection causes from the network server may include #8 “operator determined barring”, #27 “missing or unknown DNN”, #32 “service option not supported”, #33 “requested service option not subscribed, and the like. The rejection cause may be transmitted as a reject message from the network server. For example, the reject message may include an ATTACH REJECT message. The SM retry timer is enabled for re-connecting to the higher priority DNN, upon receiving the rejection cause. A start value of the SM retry timer may be a default value of 12 minutes.

FIG.7illustrates connecting a UE to a DNN in a public network integrated NPN, when a UE receives a rejection cause according to an embodiment of the disclosure.

Referring toFIG.7, in element700, at time instance1, the UE102may be initially connected to DNN2. The UE102may request the network server to connect to the higher priority DNN and via the corresponding network slice. At time instance2, the UE102may receive the rejection cause from the network server.

At operation602, the UE102detects inactivity of packet transmission for a pre-determined time period after the SM retry timer is disabled. The SM retry timer is disabled after a pre-defined time duration. The pre-defined time duration may be a default value of 12 minutes. A person skilled in the art will appreciate that this value may vary, for example, default value may be re-configured by the network server. The UE102may be configured to compare the rejection cause with the list of rejection causes stored in the UE102. The list of rejection causes may be pre-defined rejection causes that determine the UE102connected to the lower priority DNN. The UE102may determine that the UE102is connected to the lower priority DNN, based on the comparison. Further, the UE102may be configured to detect the inactivity of packet transmission upon determining that the UE102is connected to a lower priority DNN. The inactivity of packet transmission is determined to retry to connect to the higher priority DNN, without effecting data transmission in the UE102. The inactivity of packet transmission may be detected for the pre-determined time period. For example, the pre-determined time period may be 2 seconds. Referring to element700, the UE102may detect the inactivity of packet transmission for a pre-determined time period after the SM retry timer is disabled.

At operation603, the UE102evaluates the URSP rule, based on the detection. The UE102retries to connect to the higher priority DNN, upon detecting the inactivity of packet transmission for the pre-determined time period. The UE102is configured to evaluate the URSP rule to determine the priority of the DNNs. The UE102determines the priority of the higher priority DNN to be greater than the priority of current DNN. The UE102is connected to the higher priority DNN, and the corresponding network slice based on the evaluation. The UE102. Referring to element700inFIG.7, at time instance3, the UE102connects to the higher priority DNN i.e., DNN1after evaluating the URSP rule. Hence, the UE102can connect to highest priority DNN with better services, without any intervention from the network server.

FIG.8illustrates overview architecture800of a UE102for connecting the UE to a DNN in a public network integrated NPN according to an embodiment of the disclosure.

Referring toFIG.8, the UE102may comprise a processor801, a memory802, and a communication interface803. In some embodiments of the disclosure, the memory802may be communicatively coupled to the processor801. The memory802stores instructions executable by the processor801. The processor801may comprise at least one data processor for executing program components for executing user or system-generated requests. The memory802may be communicatively coupled to the processor801. The memory802stores instructions, executable by the processor801, which, on execution, may cause the processor801to connect the UE102to the DNN in the public network integrated NPN. The communication interface803is configured to transmit and receive messages/signals/control signaling. For example, the communication interface803may be configured to transmit the request to the network server for connecting to the DNN. The communication interface803may be configured to receive the rejection cause from the network server. Further, the UE102may comprise sub-modules such as application processor, database, timer control module, URSP rule evaluation module and other hardware modules. The application processor may be configured to identify the prioritized DNN and the corresponding network slice, from the list of prioritized DNNs and network slices stored in the database. Further, the application processor may be configured to detect the inactivity of packet transmission for the pre-determined time period. The timer control module may be configured to disable the SM retry timer. The URSP rule evaluation module may be configured to evaluate the URSP rule to connect the UE102to the DNN.

The disclosure allows faster connection of the UE to the NPN services and normal data services. In addition, the disclosure ensures continuity of service.

The disclosure allows the UE to connect to the higher priority DNN after detecting inactivity of packet transmission. Hence, the UE can connect to highest priority DNN with better services, without any intervention from network server.

The terms “an embodiment”, “embodiment”, “embodiments”, “the embodiment”, “the embodiments”, “one or more embodiments”, “some embodiments”, and “one embodiment” mean “one or more (but not all) embodiments of the disclosure(s)” unless expressly specified otherwise.

The terms “including”, “comprising”, “having” and variations thereof mean “including but not limited to”, unless expressly specified otherwise.

The enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise. The terms “a”, “an” and “the” mean “one or more”, unless expressly specified otherwise.

A description of an embodiment with several components in communication with each other does not imply that all such components are required. On the contrary a variety of optional components are described to illustrate the wide variety of possible embodiments of the disclosure.

When a single device or article is described herein, it will be readily apparent that more than one device/article (whether or not they cooperate) may be used in place of a single device/article. Similarly, where more than one device or article is described herein (whether or not they cooperate), it will be readily apparent that a single device/article may be used in place of the more than one device or article or a different number of devices/articles may be used instead of the shown number of devices or programs. The functionality and/or the features of a device may be alternatively embodied by one or more other devices which are not explicitly described as having such functionality/features. Thus, other embodiments of the disclosure need not include the device itself.

The illustrated operations ofFIGS.4A,5, and6show certain events occurring in a certain order. In alternative embodiments of the disclosure, certain operations may be performed in a different order, modified, or removed. Moreover, steps may be added to the above-described logic and still conform to the described embodiments. Further, operations described herein may occur sequentially or certain operations may be processed in parallel. Yet further, operations may be performed by a single processing unit or by distributed processing units.

Finally, the language used in the specification has been principally selected for readability and instructional purposes, and it may not have been selected to delineate or circumscribe the inventive subject matter. It is therefore intended that the scope of the disclosure be limited not by this description, but rather by any claims that issue on an application based here on. Accordingly, the disclosure of the embodiments of the disclosure is intended to be illustrative, but not limiting, of the scope of the disclosure, which is set forth in the following claims.

While the disclosure has been shown and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the disclosure as defined by the appended claims and their equivalents.