Method and apparatus for handling a URSP for dual steering UE in a communication system

Abstract

A method for handling a user equipment (UE) route selection policy (URSP) for dual steering UE in a communication system, comprising: registering, by the UE, a first SIM of the UE with a first network apparatus; registering, by the UE, a second SIM of the UE with a second network apparatus; determining, by the UE, whether the UE is configured with a common URSP policy applicable to both the first SIM and the second SIM, or the UE is configured with separate URSP policies for the first SIM and the second SIM; and performing, by the UE, one of: selecting, by the UE, one of the first SIM or the second SIM based on a first additional information provided in the common URSP policy for application data handling, when the UE is configured with the common URSP policy for the first SIM and the second SIM; and determining, by the UE, one of the first SIM and the second SIM to be used for application data handling based on the separate URSP policies, and a second additional information preconfigured at the UE.

Description

METHOD AND APPARATUS FOR HANDLING A URSP FOR DUAL STEERING UE IN A COMMUNICATION SYSTEM

[0001] The present disclosure is related to the field of wireless communication. More particularly, the present disclosure is related to a method and system for handling a user equipment (UE) route selection policy (URSP) for dual steering UE in a communication system.

[0002] 5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in "Sub 6GHz" bands such as 3.5GHz, but also in "Above 6GHz" bands referred to as mmWave including 28GHz and 39GHz. In addition, it has been considered to implement 6G mobile communication technologies (referred to as Beyond 5G systems) in terahertz bands (for example, 95GHz to 3THz bands) in order to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.

[0003] At the beginning of the development of 5G mobile communication technologies, in order to support services and to satisfy performance requirements in connection with enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), there has been ongoing standardization regarding beamforming and massive MIMO for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, supporting numerologies (for example, operating multiple subcarrier spacings) for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of BWP (BandWidth Part), new channel coding methods such as a LDPC (Low Density Parity Check) code for large amount of data transmission and a polar code for highly reliable transmission of control information, L2 pre-processing, and network slicing for providing a dedicated network specialized to a specific service.

[0004] Currently, there are ongoing discussions regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical layer standardization regarding technologies such as V2X (Vehicle-to-everything) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, NR UE Power Saving, Non-Terrestrial Network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.

[0005] Moreover, there has been ongoing standardization in air interface architecture / protocol regarding technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access for simplifying random access procedures (2-step RACH for NR). There also has been ongoing standardization in system architecture / service regarding a 5G baseline architecture (for example, service based architecture or service based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE positions.

[0006] As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks, and it is accordingly expected that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with eXtended Reality (XR) for efficiently supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality) and the like, 5G performance improvement and complexity reduction by utilizing Artificial Intelligence (AI) and Machine Learning (ML), AI service support, metaverse service support, and drone communication.

[0007] Furthermore, such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.

[0008] 5th generation (5G) or new radio (NR) mobile communications is recently gathering increased momentum with all the worldwide technical activities on the various candidate technologies from industry and academia. The candidate enablers for the 5G / NR mobile communications include massive antenna technologies, from legacy cellular frequency bands up to high frequencies, to provide beamforming gain and support increased capacity, new waveform (e.g., a new radio access technology (RAT)) to flexibly accommodate various services / applications with different requirements, new multiple access schemes to support massive connections, and so on.

[0009] The principal object of the embodiments herein is to provide a system and method for handling a URSP for dual steering UE in a communication system.

[0010] Another object of the embodiments herein is to configure the UE with a common policy for SIM-1 and SIM-2, and with separate policies for SIM-1 and SIM-2

[0011] Yet another object of the embodiments herein is to incorporate additional information in the URSP when the UE is configured with the common policy for SIM-1 and SIM-2, allowing the UE to choose between SIM-1 or SIM-2 for managing application data.

[0012] Yet another object of the embodiments herein is to enable the UE to determine whether to utilize SIM-1 and / or SIM-2 for application data handling when the UE is configured with separate policies.

[0013] Yet another object of the embodiment herein is to enable the UE to perform a URSP re-evaluation between the SIM-1 and SIM-2 when the UE is configured with separate policies.

[0014] In line with development of the communication systems, there is a need for system and method for handling a URSP for dual steering UE in a communication system.

[0015] The technical subjects pursued in the disclosure may not be limited to the above mentioned technical subjects, and other technical subjects which are not mentioned may be clearly understood, through the following descriptions, by those skilled in the art to which the disclosure pertains.

[0016] In an aspect, the objectives are achieved by providing a method for handling a URSP for dual steering UE in a communication system.

[0017] Embodiments herein provide a method and system for handling a URSP for dual steering UE in a communication system. The method includes registering a first SIM of the UE with a first network apparatus and a second SIM of the UE with a second network apparatus. Further, the method includes determining whether the UE is configured with a common URSP policy applicable to both the first and second SIM, or with separate URSP policies. Further, the method includes selecting the first or second SIM based on a first additional information provided in the common URSP policy, when the UE is configured with the common URSP policy. Further, the method includes determining one of the first and second SIM based on the separate URSP policies, and a second additional information preconfigured at the UE.

[0018] The method includes registering a first SIM of the UE with a first network apparatus. Further, the method includes registering a second SIM of the UE with a second network apparatus. Further, the method includes determining whether the UE is configured with a common URSP policy applicable to both the first SIM and the second SIM, or the UE is configured with separate URSP policies for the first SIM and the second SIM. Further, the method includes selecting one of the first SIM or the second SIM based on a first additional information provided in the common URSP policy for application data handling, when the UE is configured with the common URSP policy for the first SIM and the second SIM. Further, the method includes determining one of the first SIM and the second SIM to be used for application data handling based on the separate URSP policies, and a second additional information preconfigured at the UE.

[0019] In another aspect, the objectives are achieved by providing a method for handling a URSP for dual steering UE in a communication system. The method includes receiving a registration request message from a first SIM of a UE via a Public Land Mobile Network-1 (PLMN-1). The registration request message comprises a User Policy Selection Identifier (UPSI) associated with the first SIM. Further, the method includes obtaining a common URSP policy or separate URSP policies associated with the first SIM of the UE. Further, the method includes generating a registration accept message that comprises the common URSP policy or separate URSP policies obtained. Further, the method includes transmitting the registration accept message to the first SIM of the UE.

[0020] In another aspect, the objectives are achieved by providing a method for handling a URSP for dual steering UE in a communication system. The method includes receiving a registration request message from a second SIM of a UE via a PLMN-2. The registration request message comprises a UPSI associated with the second SIM. Further, the method includes obtaining a common URSP policy or separate URSP policies associated with the second SIM of the UE. Further, the method includes generating a registration accept message that comprises the common URSP policy or separate URSP policies obtained. Further, the method includes transmitting the registration accept message to the second SIM of the UE.

[0021] In another aspect, the objectives are achieved by providing a UE for handling a URSP for dual steering in a communication system. The UE includes a first memory, a first processor, and a URSP handling controller communicatively coupled to the first memory and the first processor. The URSP handling controller registers a first SIM of the UE with a first network apparatus. Further, the URSP handling controller registers a second SIM of the UE with a second network apparatus. Further, the URSP handling controller determines whether the UE is configured with a common URSP policy applicable to both the first SIM and the second SIM, or the UE is configured with separate URSP policies for the first SIM and the second SIM. Further, the URSP handling controller selects one of the first SIM or the second SIM based on a first additional information provided in the common URSP policy for application data handling, when the UE is configured with the common URSP policy for the first SIM and the second SIM. Further, the URSP handling controller determines one of the first SIM and the second SIM to be used for application data handling based on the separate URSP policies, and a second additional information preconfigured at the UE.

[0022] In another aspect, the objectives are achieved by providing a first network apparatus for handling a URSP for dual steering UE in a communication system. The first network apparatus includes a second memory, a second processor, and a URSP policy obtaining controller communicatively coupled to the second memory and the second processor. The URSP policy obtaining controller receives a registration request message from a first SIM of a UE via a PLMN-1. The registration request message comprises a UPSI associated with the first SIM. Further, the URSP policy obtaining controller obtains a common URSP policy or separate URSP policies associated with the first SIM of the UE. Further, the URSP policy obtaining controller generates a registration accept message that comprises the common URSP policy or separate URSP policies obtained. Further, the URSP policy obtaining controller transmits the registration accept message to the first SIM of the UE.

[0023] In another aspect, the objectives are achieved by providing a second network apparatus for handling a URSP for dual steering UE in a communication system. The second network apparatus includes a third memory, a third processor, and a URSP policy determination controller communicatively coupled to the third memory and the third processor. The URSP policy determination controller receives a registration request message from a second SIM of a UE via a PLMN-2. The registration request message comprises a UPSI associated with the second SIM. Further, the URSP policy determination controller obtains a common URSP policy or separate URSP policies associated with the second SIM of the UE. Further, the URSP policy determination controller generates a registration accept message that comprises the common URSP policy or separate URSP policies obtained. Further, the URSP policy determination controller transmits the registration accept message to the second SIM of the UE.

[0024] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood,however, that the following descriptions, while indicating preferred embodiments and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications be made within the scope of the embodiments herein.

[0025] The present disclosure provides an effective and efficient method for handling a URSP for dual steering UE in a communication system. Advantageous effects obtainable from the disclosure may not be limited to the above mentioned effects, and other effects which are not mentioned may be clearly understood, through the following descriptions, by those skilled in the art to which the disclosure pertains.

[0026] These and other features, aspects, and advantages of the present embodiments are illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the drawings, in which:

[0027] Fig. 1 is a sequence diagram that illustrates a scenario of dual steering service provided by a both a UE-1 and a UE-2 of the UE.

[0028] Fig. 2 is a block diagram that illustrates a schematic of the UE implemented to carry out the disclosed subject matter according to an embodiment as disclosed herein.

[0029] Fig. 3 is a block diagram that illustrates a schematic of a first network apparatus implemented to carry out the disclosed subject matter according to an embodiment as disclosed herein.

[0030] Fig. 4 is a block diagram that illustrates a schematic of a second network apparatus implemented to carry out the disclosed subject matter according to an embodiment as disclosed herein.

[0031] Fig. 5 is a sequence diagram that illustrates a scenario of dual steering service provided by a both the UE-1 and the UE-2 of the UE according to an embodiment as disclosed herein.

[0032] Fig. 6 is a sequence diagram that illustrates a scenario of dual steering service provided by the UE-1 only according to an embodiment as disclosed herein.

[0033] Fig. 7 is a sequence diagram that illustrates a scenario of dual steering service provided by the UE-2 according to an embodiment as disclosed herein.

[0034] Fig. 8 is a sequence diagram that illustrates a scenario of dual steering service provided by the UE-2 according to an embodiment as disclosed herein.

[0035] Fig. 9 is a sequence diagram that illustrates events where the first network apparatus and the second network apparatus indicate a type of URSP policy and its association with the UE according to an embodiment as disclosed herein.

[0036] Fig. 10 is a sequence diagram that illustrates the UE indicating a policy identification to the first network apparatus and the second network apparatus according to an embodiment as disclosed herein.

[0037] Fig. 11 is a sequence diagram that illustrates events of URSP re-evaluation trigger considering dual steering according to an embodiment as disclosed herein.

[0038] Figs. 12A-C is a flow diagram that illustrates a method for handling a URSP for dual steering UE in a communication system according to an embodiment as disclosed herein.

[0039] Fig. 13 is a flow diagram that illustrates a method for determining the common URSP policy or separate URSP policies associated with the UE-1 (102A) / first SIM of the UE (102) according to an embodiment as disclosed herein.

[0040] Fig. 14 is a flow diagram that illustrates a method for determining the common URSP policy or separate URSP policies associated with the UE-2 (102B) / second SIM of the UE (102) according to an embodiment as disclosed herein.

[0041] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. Also, the various embodiments described herein are not necessarily mutually exclusive, as some embodiments can be combined with a plurality of other embodiments to form new embodiments. The term "or" as used herein, refers to a non-exclusive or, unless otherwise indicated. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein can be practiced and to further enable those skilled in the art to practice the embodiments herein. Accordingly, the examples are not be construed as limiting the scope of the embodiments herein.

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

[0043] The accompanying drawings are used to help easily understand various technical features and it is understood that the embodiments presented herein are not limited by the accompanying drawings. As such, the proposed method is construed to extend to any alterations, equivalents and substitutes in addition to those which are particularly set out in the accompanying drawings. Although the terms first, second, etc. used herein to describe various elements, these elements are not be limited by these terms. These terms are generally used to distinguish one element from another.

[0044] Embodiments disclosed herein provide a method for handling URSP for dual steering UE. The method includes dual steering service provided by only one UE. In an embodiment, when the application X is opened or tried to establish data connection, it always try to establish PDU session on the primary UE (UE-1). If PDU session is established as Dual Steer PDU session then only after that UE-2 establishes PDU session establishment.

[0045] A dual steer device refers to a device supporting traffic steering and switching of user data (for different services) across two 3GPP access networks. It can be a single UE, in case of non-simultaneous data transmission over the two networks, or two separate UEs in case of simultaneous data transmission over the two networks.Traffic steering refers to a procedure that selects an access network and transfers traffic over the selected access network. This can apply to traffic of one or multiple services / applications across two 3GPP access networks, including scenarios where all services use the same network connection (no simultaneous data over the two networks) or different services are steered across different networks (with simultaneous data over the two networks).

[0046] Traffic switching refers to a procedure that moves all traffic from one access network to another access network in a way that minimizes service interruption. This can apply to traffic of one or multiple services / applications across two 3GPP access networks, including scenarios where all services use the same network connection (no simultaneous data over the two networks) or different services are moved to different networks (with simultaneous data over the two networks). Non simultaneous data transmission is where all services use the same network connection at a time (no simultaneous data transfer over the two (access) networks) for data communication and can switch between two networks as per traffic switching procedure but does not transmit data over two networks simultaneously.

[0047] Simultaneous data transmission is where different services are steered across different networks concurrently (with simultaneous data over the two networks). The conditions are as follows: The UE and network both support dual steering and UE is configured with two Subscription Permanent Identifiers SUPIs / UEs which enable dual steering. The UE registered with the Subscription Permanent Identifier-1 / Subscription Concealed Identifier - 1 (SUPI-1 / SUCI-1) on the network for example Public Land Mobile Network (PLMN)-1 / 3rdgeneration Partnership Project (3GPP) acces1 and Radio Access Technology (RAT) 1. The UE registered with the SUPI-2 / SUCI-2 on the network for example PLMN-2 / 3GPP acces2 and RAT2.

[0048] In the multi-access connectivity (through MASSS i.e. Multi-access Steering, Switching and Splitting), the UE will utilize two distinct SUPIs, referred to as SUPI-1 / SIM-1 and SUPI-2 / SIM-2. These SUPIs represent two separate SIM cards under a single subscription. Current specifications are designed for a single SUPI / SIM associated with one subscription, directing all application traffic through the PDU session linked to the active SUPI / SIM. The PDU session for transmitting application data is determined by a policy configured in the UE is known as the URSP rule, which is provisioned by the network. However, the method for the network to deliver the URSP policy to a dual steer UE remains unclear. If the UE possesses the URSP policy for dual steer functionality, it must be established whether this policy consists of a separate URSP rule or a common URSP rule applicable to both SUPI / SIMs. Furthermore, upon receiving the URSP rule, it is essential to assess the rule to associate application data with the appropriate PDU session.

[0049] If the UE is configured such that traffic from an application X is directed to the PDU session associated with DNN-1 and SNSSAI-1. Since the UE possesses two SUPI / SIM, it is essential to manage which SIM is used for transmitting application data. If not defined, the UE can route data through SIM-2, even if SIM-1 is designated as the priority for the application X. Upon the release of the PDU session, the UE reassesses the URSP rules to determine the appropriate SIM for the new PDU session. In instances where the UE supports MASS, it is essential to re-evaluate the URSP if service is lost on SUPI-1 / SIM-1 or if the PDU session for SUPI-1 / SIM-1 is terminated.

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

[0051] In an embodiment, when the application X is opened, PDU session is established on the UE (UE-1 or UE-2) where PDU session establishment is possible and UE has the policy (Dual steer Policy given by the network function (NF) e.g. Policy Control Function (PCF) / Unified Data Management (UDM)) which indicates that PDU session with attributes (e.g. S-NSSAI, DNN) can be established as Dual Steer. The policy to indicate whether Dual Steer PDU session is supported for the matched URSP or its attribute can be in the URSP rule itself (in traffic descriptor or route selection descriptor) and network give additional policy where it says S-NSSAI+DNN can be established as Dual Steer PDU session. I.e. If the UE has the dual steer policy for the DNN-X, S-NSSAI-X then UE can initiate PDU session establishment on any UE (UE-1 or UE-2) with the DNN-X, S-NSSAI-X and if the dual steer policy doesn't have the DNN-X, S-NSSAI-X then UE-1 (primary) is only used for the PDU session establishment with DNN-X, S-NSSAI-X.

[0052] In an embodiment, the UE establishes PDU session establishment on the secondary UE (UE-2) as Dual Steer PDU session (i.e. if PDU session established with URSP of UE-2 with e.g. S-NSSAI-X, DNN-X for the application-X then UE-1 will also have URSP rule with the same attributes and will be able to establish PDU session with e.g. S-NSSAI-X, DNN-X for the application-X)

[0053] In an embodiment, the Dual Steering policy can be sent to the UE from NF (e.g. UDM / PCF) over the NAS (e.g. along with registration accept or UE configuration update command or UE policy Command) message or any other message or ESM message (alone with PDU session modification command, PDU session establishment accept or any other 5GSM message. The policy can be included in PCO / ePCO)

[0054] In an embodiment, each UE can be provided with the URSP rule. Where each URSP rule may be associated with Dual Steer PDU session or Standalone PDU session. When application is opened or initiated data transfer, it can evaluate URSP rule of each UE independently.

[0055] In an embodiment, network function indicates the type of URSP policy and its association with each UE / Stack.

[0056] RAT-Type:

[0057] The term RAT / RAT-type (also referred as access technology) as defined in this embodiment can be at least one of the following: -

[0058] ▶ NG-RAN

[0059] ▶ 5G, 4G, 3G, 2G

[0060] ▶ EPS, 5GS

[0061] ▶ NR

[0062] ▶ satellite E-UTRAN

[0063] ▶ satellite NG-RAN

[0064] ▶ NR in unlicensed bands

[0065] ▶ NR(LEO) satellite access

[0066] ▶ NR(MEO) satellite access

[0067] ▶ NR(GEO) satellite access

[0068] ▶ NR(OTHERSAT) satellite access

[0069] ▶ NR RedCap

[0070] ▶ E-UTRA

[0071] ▶ E-UTRA in unlicensed bands

[0072] ▶ NB-IoT

[0073] ▶ WB-IoT

[0074] ▶ LTE-M

[0075] NASmessages

[0076] Some of the examples of NAS messages comprises:

[0077] ▶ REGISTRATION REQUEST message;

[0078] ▶ DEREGISTRATION REQUEST message;

[0079] ▶ SERVICE REQUEST message; and

[0080] ▶ CONTROL PLANE SERVICE REQUEST.

[0081] ▶ IDENTITY REQUEST

[0082] ▶ AUTHENTICATION REQUEST;

[0083] ▶ AUTHENTICATION RESULT;

[0084] ▶ AUTHENTICATION REJECT;

[0085] ▶ REGISTRATION REJECT

[0086] ▶ REGISTRATION ACCEPT

[0087] ▶ DEREGISTRATION ACCEPT

[0088] ▶ SERVICE REJECT

[0089] ▶ SERVICE ACCEPT

[0090] ▶ UE CONFIGURATION UPDATE command

[0091] ▶ UE PARAMETERS UPDATE command

[0092] The term 5GMM sublayer states in this embodiment are at least one of the below:

[0093] 1)5GMM-NULL

[0094] 2) 5GMM-DEREGISTERED

[0095] a) 5GMM-DEREGISTERED.NORMAL-SERVICE

[0096] b) 5GMM-DEREGISTERED.LIMITED-SERVICE

[0097] c) 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION

[0098] d) 5GMM-DEREGISTERED.PLMN-SEARCH

[0099] e) 5GMM-DEREGISTERED.NO-SUPI

[0100] f) 5GMM-DEREGISTERED.NO-CELL-AVAILABLE

[0101] g) 5GMM-DEREGISTERED.eCALL-INACTIVE

[0102] h) 5GMM-DEREGISTERED.INITIAL-REGISTRATION-NEEDED

[0103] 3) 5GMM-REGISTERED-INITIATED

[0104] 4) 5GMM-REGISTERED

[0105] a) 5GMM-REGISTERED.NORMAL-SERVICE

[0106] b) 5GMM-REGISTERED.NON-ALLOWED-SERVICE

[0107] c) 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE

[0108] d) 5GMM-REGISTERED.LIMITED-SERVICE

[0109] e) 5GMM-REGISTERED.PLMN-SEARCH

[0110] f) 5GMM-REGISTERED.NO-CELL-AVAILABLE

[0111] g) 5GMM-REGISTERED.UPDATE-NEEDED

[0112] 5) 5GMM-DEREGISTERED-INITIATED

[0113] 6) 5GMM-SERVICE-REQUEST-INITIATED

[0114] The term EMM sublayer in this embodiment is at least one of the below:

[0115] 1) EMM-NULL

[0116] 2) EMM-DEREGISTERED

[0117] a) EMM-DEREGISTERED.NORMAL-SERVICE

[0118] b) EMM-DEREGISTERED.LIMITED-SERVICE

[0119] c) EMM-DEREGISTERED.ATTEMPTING-TO-ATTACH

[0120] d) EMM-DEREGISTERED.PLMN-SEARCH

[0121] e) EMM-DEREGISTERED.NO-IMSI

[0122] f) EMM-DEREGISTERED.ATTACH-NEEDED

[0123] g) EMM-DEREGISTERED.NO-CELL-AVAILABLE

[0124] h) EMM-DEREGISTERED.eCALL-INACTIVE

[0125] 3) EMM-REGISTERED-INITIATED

[0126] 4) EMM-REGISTERED

[0127] a) EMM-REGISTERED.NORMAL-SERVICE

[0128] b) EMM-REGISTERED.ATTEMPTING-TO-UPDATE

[0129] c) EMM-REGISTERED.LIMITED-SERVICE

[0130] d) EMM-REGISTERED.PLMN-SEARCH

[0131] e) EMM-REGISTERED.UPDATE-NEEDED

[0132] f) EMM-REGISTERED.NO-CELL-AVAILABLE

[0133] g) EMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM

[0134] h) EMM-REGISTERED.IMSI-DETACH-INITIATED

[0135] 5) EMM-DEREGISTERED-INITIATED

[0136] 6) EMM-TRACKING-AREA-UPDATING-INITIATED

[0137] 7) EMM-SERVICE-REQUEST-INITIATED

[0138] URSP policy:

[0139] UE route selection policy (URSP)

[0140] 4.2.1 General

[0141] The URSP is defined in 3GPP　TS　23.503　[2] and is a set of one or more URSP rules, where a URSP rule is composed of:

[0142] a) A precedence value of the URSP rule identifying the precedence of the URSP rule among all the existing URSP rules;

[0143] b) A traffic descriptor, including either:

[0144] 1) match-all traffic descriptor; or

[0145] 2) At least one of the following components (see table　6.6.2.1-2 in 3GPP　TS　23.503　[2]):

[0146] A) One or more application identifiers;

[0147] B) one or more IP descriptors, each consists of a set of IP 3 tuples as defined in 3GPP　TS　23.503　[2] i.e. the destination IP address, the destination port number, and the protocol in use above the IP;

[0148] C) One or more non-IP descriptors, i.e. destination information of non-IP traffic;

[0149] D) One or more DNNs;

[0150] E) One or more connection capabilities;

[0151] F) One or more domain descriptors, i.e. destination FQDN(s) or a regular expression as a domain name matching criteria;

[0152] G) One PIN ID; and

[0153] H) One or more connectivity group IDs; and

[0154] c) One or more route selection descriptors each consisting of a precedence value of the route selection descriptor and either

[0155] 1) One PDU session type and, optionally, one or more of the followings:

[0156] A) SSC mode;

[0157] B) One or more S-NSSAIs. If the URSP rule is a part of a non-subscribed SNPN signalled URSP, the S-NSSAI is of the non-subscribed SNPN otherwise the S-NSSAI is of the HPLMN or the subscribed SNPN. Mapped HPLMN SST and mapped HPLMN SD are not included in the S-NSSAI;

[0158] C) One or more DNNs;

[0159] D) Void;

[0160] E) preferred access type;

[0161] F) Multi-access preference;

[0162] G) A time window;

[0163] H) Location criteria;

[0164] I) PDU session pair ID;

[0165] J) RSN; and

[0166] K) 5G ProSe multi-path preference;

[0167] 2) Non-seamless non-3GPP offload indication; or

[0168] 3) 5G ProSe layer-3 UE-to-network relay offload indication.

[0169] URSP Evaluation:

[0170] In order to send a PDU of an application, the upper layers require information on the PDU session (e.g. PDU address) via which to send a PDU of an application.

[0171] NOTE　0: If PAP / CHAP is used, it is recommended that the request from the upper layers includes a DNN.

[0172] When the upper layers request information of the PDU session via which to send a PDU of an application;

[0173] - information on the non-3GPP access outside of a PDU session shall be provided to the upper layers, without evaluating the URSP rules, if due to UE local configuration non-seamless non-3GPP offload is requested; or

[0174] - information on the 5G ProSe layer-3 UE-to-network relay shall be provided to the upper layers, without evaluating the URSP rules, if due to UE local configuration 5G ProSe layer-3 UE-to-network relay offload is requested;

[0175] Otherwise, the UE shall proceed in the following order:

[0176] a) The UE shall evaluate the URSP rules, except the default URSP rule, with a traffic descriptor matching the application information in increasing order of their precedence values, if any. If the traffic descriptor contains more than one traffic descriptor component type, each of a different type, all of them shall be matched. If the traffic descriptor contains more than one traffic descriptor component of the same traffic descriptor component type, at least one of the traffic descriptor components of the same traffic descriptor component type shall be matched with the application information. A URSP rule is determined not to be applicable when for any given component in the traffic descriptor no corresponding information from the application is available or the corresponding information from the application does not match any of the values in the traffic descriptor component as specified in clause　6.6.2.1 of 3GPP　TS　23.503　[2].

[0177] If the UE finds the traffic descriptor in a non-default URSP rule matching the application information, and:

[0178] I) if:

[0179] 1) at least one of the route selection descriptors of the URSP rule contains a non-seamless non-3GPP offload indication and the information on the non-3GPP access outside of a PDU session is available;

[0180] The UE shall provide information on the non-3GPP access outside of a PDU session to the upper layers; and

[0181] 2) There is one or more PDU sessions:

[0182] i) matching at least one of the route selection descriptors of the URSP rule except the preferred access type and the multi-access preference, if any, wherein a route selection descriptor with PDU session type IPv4v6 matches also with PDU session type IPv4 if the network has sent 5GSM cause value #50 "PDU session type IPv4 only allowed" in the PDU SESSION ESTABLISHMENT ACCEPT message, a route selection descriptor with PDU session type IPv4v6 matches also with PDU session type IPv6 if the network has sent 5GSM cause value #51 "PDU session type IPv6 only allowed" in the PDU SESSION ESTABLISHMENT ACCEPT message and a route selection descriptor with PDU session type IPv4v6 matches also with PDU session type IPv6 or IPv4 if the UE requested the PDU session type IPv4v6 but the selected PDU session type is set to IPv4 or IPv6 in the PDU SESSION ESTABLISHMENT ACCEPT message; and

[0183] ii) Established without requesting any parameter for which the matching route selection descriptor of the URSP rule does not provide a route selection descriptor component, except:

[0184] A) The preferred access type;

[0185] B) The multi-access preference;

[0186] C) the DNN, if no DNN is included in the route selection descriptor component and the DNN provided by the application is the same as the DNN requested by the UE during the PDU session establishment; and

[0187] D) The S-NSSAI, if the UE has only one S-NSSAI in the allowed NSSAI.

[0188] The UE shall provide information on the PDU session that matches the route selection descriptor of the lowest precedence value to the upper layers;

[0189] NOTE　1: It is up to the UE implementation which PDU session to select if there exist multiple PDU sessions matching the same route selection descriptor of the lowest precedence value.

[0190] II) Otherwise:

[0191] 1) The UE shall select a route selection descriptor with the next smallest precedence value which has not yet been evaluated;

[0192] 2) If:

[0193] i) The selected route selection descriptor contains a non-seamless non-3GPP offload indication:

[0194] A) If the information on the non-3GPP access outside of a PDU session is available, it shall be provided to the upper layers and the UE shall stop selecting a route selection descriptor matching the application information.

[0195] B) If the information about the non-3GPP access outside of a PDU session is not available, or non-3GPP access is not available the UE shall proceed to step 4);

[0196] IA) the selected route selection descriptor contains a 5G ProSe layer-3 UE-to-network relay offload indication:

[0197] A) if the information on the 5G ProSe layer-3 UE-to-network relay is available and the UE supports acting as ProSe layer-3 UE-to-network remote UE as specified in 3GPP　TS　24.501

[0011] , it shall be provided to the upper layers and the UE shall stop selecting a route selection descriptor matching the application information.

[0198] B) if the information about the 5G ProSe layer-3 UE-to-network relay is not available or the UE does not support acting as ProSe layer-3 UE-to-network remote UE as specified in 3GPP　TS　24.501

[0011] , the UE shall proceed to step 4);

[0199] ii) The selected route selection descriptor includes a PDU session type or an SSC mode which is not supported by the UE, the UE shall proceed to step 4);

[0200] iii) The selected route selection descriptor contains a time window but the time does not match the time window, the UE shall proceed to step 4);

[0201] iv) The selected route selection descriptor contains location criteria but the UE location does not match the location criteria, the UE shall proceed to step 4);

[0202] v) The selected route selection descriptor includes the multi-access preference but the UE does not support ATSSS, the UE shall proceed to step 4);

[0203] va) the selected route selection descriptor includes an SSC mode which either has been rejected by the network with 5GSM cause value #68 "not supported SSC mode" for the same DNN (or no DNN, if no DNN was indicated by the UE) and the same S-NSSAI associated with (if available in roaming scenarios) a mapped S-NSSAI (or no S-NSSAI, if no S-NSSAI was indicated by the UE) or was not included in the Allowed SSC mode IE following a rejection with 5GSM cause value #68 "not supported SSC mode" for the same DNN (or no DNN, if no DNN was indicated by the UE) and the same S-NSSAI associated with (if available in roaming scenarios) a mapped S-NSSAI (or no S-NSSAI, if no S-NSSAI was indicated by the UE), the UE shall proceed to step 4); or

[0204] vi) the selected route selection descriptor does not contain a non-seamless non-3GPP offload indication nor a 5G ProSe layer-3 UE-to-network relay offload indication, the URSP handling layer requests the UE NAS layer to establish a PDU session providing the following PDU session attributes based on the selected route selection descriptor:

[0205] A) SSC mode if there is a SSC mode in the route selection descriptor;

[0206] NOTE　2: The SSC mode 3 is only used when the PDU session type is IPv4, IPv6 or IPv4v6.

[0207] B) One S-NSSAI if the S-NSSAI is in the route selection descriptor; and the S-NSSAI is in the allowed NSSAI. If none of the S-NSSAI(s) in the route selection descriptor is in the allowed NSSAI, the UE shall proceed to step 4);

[0208] NOTE　3: If there are multiple S-NSSAIs in the route selection descriptor, an S-NSSAI is chosen among the S-NSSAIs based on UE implementation.

[0209] C) One DNN, if the DNN is in the route selection descriptor; and if the DNN is an LADN DNN and the UE is in the service area of that LADN;

[0210] NOTE　4: If one or more DNNs are included in the traffic descriptor and no DNN is included in the route selection descriptor, the DNN provided by the application is selected as one of the PDU session attributes by the URSP handling layer to request the UE NAS layer.

[0211] NOTE　5: If there are multiple DNNs in the route selection descriptor, a DNN is chosen based on UE implementation.

[0212] D) The PDU session type of the route selection descriptor;

[0213] E) Preferred access type or multi-access preference, if the preferred access type or the multi-access preference is in the route selection descriptor; and

[0214] NOTE　6: If a preferred access type or a multi-access preference is included in the traffic descriptor of a URSP rule, it is recommended that the UE establishes a PDU session based on the preferred access type or the multi-access preference.

[0215] The UE NAS layer indicates the result of the PDU session establishment. Upon successful completion of the PDU session establishment, the UE NAS layer shall additionally indicate the attributes of the established PDU session (e.g. PDU session identity, SSC mode, S-NSSAI, DNN, PDU session type, access type, PDU address) to the URSP handling layer, and shall provide information (e.g. PDU address) of the successfully established PDU session to the upper layers. The UE shall stop selecting a route selection descriptor matching the application information. If the PDU session establishment is unsuccessful, the UE shall proceed to step 3);

[0216] 3) Based on the rejection cause and if there is another value which can be used for the rejected component in the same route selection descriptor, the UE shall select another combination of values in the currently selected route selection descriptor by using this value of the rejected component and proceed to step 2), otherwise the UE shall proceed to step 4); and

[0217] 4) If there is any route selection descriptor which has not yet been evaluated, the UE shall proceed to step 1). If all route selection descriptors for the matching non-default URSP rule have been evaluated and there is one or more non-default matching URSP rule which has not yet been evaluated, the UE shall proceed to step a). If all non-default matching URSP rules have been evaluated, the UE shall inform the upper layers of the failure.

[0218] URSP Re-evaluation:

[0219] The UE may re-evaluate the URSP rules, to check if the change of the association of an application to a PDU session is needed, when:

[0220] NOTE　11: The time when the UE performs the re-evaluation is up to UE implementation. It is recommended that the UE performs the re-evaluation in a timely manner.

[0221] a) The UE performs periodic URSP rules re-evaluation based on UE implementation;

[0222] b) The UE NAS layer indicates that an existing PDU session used for routing traffic of an application based on a URSP rule is released;

[0223] c) The URSP is updated by the PCF;

[0224] d) The UE NAS layer indicates that the UE performs inter-system change from S1 mode to N1 mode;

[0225] e) The UE NAS layer indicates that the UE is successfully registered in N1 mode over 3GPP access or non-3GPP access;

[0226] f) The UE establishes or releases a connection to a WLAN access and transmission of a PDU of the application via non-3GPP access outside of a PDU session becomes available / unavailable;

[0227] g) The allowed NSSAI or the configured NSSAI is changed; or

[0228] h) The LADN information is changed.

[0229] If the re-evaluation leads to a change of the association of an application to a PDU session, the UE may enforce such change immediately or when UE returns to 5GMM-IDLE mode.

[0230] NOTE　12: The time when the UE enforces the change of the association of an application to a PDU Session is up to UE implementation. It is recommended that the UE performs the enforcement in a timely manner.

[0231] The URSP handling layer may request the UE NAS layer to release an existing PDU session after the re-evaluation.

[0232] In conventional method, the UE evaluates URSP rules received on respective UE stack / SIM / Subscription only and do not consider the URSP rules received on another stack if any due to which it is unknown whether the Dual Steer PDU session can be established for user data steering or switching on another access at later point of time

[0233] In contrast to the conventional method, the present disclosure introduces a novel approach where only one UE will provide the dual steering service. For example, if UE-1 and UE-2 form the dual steering UE. Assume UE-1 is primary UE which support all the application traffic and UE-2 only support Dual Steering PDU session.UE-2 only engage in the establishment of PDU session for the dual steering PDU session established on UE-1 (i.e. if UE-1 have established Dual Steer PDU session then UE-2 establish the PDU session with the same attribute as UE-1).

[0234] Fig. 1 is a sequence diagram that illustrates a scenario of dual steering service provided by a both a UE-1 (102A) and a UE-2 (102B) of a UE (102). As shown in the sequence diagram, the UE (102), an access management function (AMF) (104), an H-PCF (106), and a UDR (108) are in communication with each other. Each step is explained in further detail below.

[0235] At step 1, the UE (102) (dual steer capable) triggers a registration to the AMF (104) (for example, a first access network) and there is an identifier which informs the AMF (104) that the UE (102) is registering for dual steering. The UE (102) sends a 5GMM message e.g. REGISTRATION REQUEST / UL NAS TRANSPORT or any other NAS message and updates it's capability of "dualSteer capable" and registers to a first access network.

[0236] At steps 2 through 4: The AMF (104)) of Home Public Land Mobile Network (HPLMN) / Visited Public LandMobile Network (VPLMN)_1 interacts with the UDM (108) for e.g. using Nudm_UECM_Registration operation or some NF and retrieves the subscription data or policy for the UE (102). At step 5: UE Configuration Update procedure happens and the UE (102) gets the policy based on thee subscription details.

[0237] At steps 6 and 7: The UE (102) triggers a registration to the AMF (104) (for example, a second access network). The UE (102) sends a 5GMM message e.g. REGISTRATION REQUEST / UL NAS TRANSPORT or any other NAS message and registers to the AMF (104).

[0238] At steps 7 through 9: The AMF (104) of second access interacts with the UDM (108) for e.g. using Nudm_UECM_Registration operation or some NF and retrieves the subscription data or policy for this UE. At step 10: UE Configuration Update procedure happens and the UE (102) gets the policy.

[0239] In the current standards, the UE (102) evaluates the URSP rules received on respective UE stack / SIM / Subscription only and do not consider the URSP rules received on another stack if any, due to which it is unknown whether the Dual Steer PDU session can be established for user data steering or switching on another access at later point of time.

[0240] For example, for establishing data session using dual steer capabilities it is unknown Whether :

[0241] a) The UE (102) shall use URSP rules received on only current stack

[0242] b) The UE (102) shall use URSP rules received on both access / stacks

[0243] c) Whether the network will configure URSP rules on only one access or both access.

[0244] In contrast to the conventional method, the present disclosure introduces an approach where the UE (102) (only one) will provide the dual steering service. For example, if the UE-1 (102A) and the UE-2 (102B) form the dual steering UE. Assume the UE-1 (102A) is a primary UE that supports all the application traffic and the UE-2 (102B) only supports the dual steering PDU session. The UE-2 (102B) only engages in the establishment of PDU session for the dual steering PDU session established on the UE-1 (102A) (i.e. if the UE-1 (102A) has established Dual Steer PDU session, then the UE-2 (102B) establishes the PDU session with the same attribute as the UE-1 (102A)).

[0245] Referring now to the drawings, and more particularly to Figs. 2 through X where similar reference characters denote corresponding features consistently throughout the figures, there are shown preferred embodiments.

[0246] Fig. 2 is a block diagram that illustrates a schematic of a UE (102) implemented to carry out the disclosed subject matter according to an embodiment as disclosed herein. Examples of the UE (102) can include, but are not limited to, Consumer Electronics (such as Mobile Phones and Smartphones), Tablets, Wearable Devices, Computing Devices (such as Laptops, Notebooks, Desktops, Workstations, etc.), IoT Devices, Automotive Systems (such as connected cars, Autonomous Vehicles, Vehicle-to-Everything (V2X) communication devices, etc.), Enterprise Devices such as robotics, Specialized Equipment (such as Medical Devices, Public Safety Devices, etc.), Media Devices (such as Gaming Consoles, Streaming Devices, etc.).

[0247] In an embodiment, in Fig. 2, the UE (102) includes a first processor (110), a first memory (112), a first I / O interface (114), and an URSP handling controller (116) coupled to the first processor (110) and the first memory (112). The components are explained in further detail below.

[0248] The first processor (110) communicates with the first memory (112), the first I / O interface (114), and the URSP handling controller (116). The first processor (110) is configured to execute instructions stored in the first memory (112) and to perform various processes. The first processor (110) includes one or a plurality of processors, is a general-purpose processor such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and / or an Artificial Intelligence (AI) dedicated processor such as a neural processing unit (NPU).

[0249] The first memory (112) includes storage locations to be addressable through the first processor (110). The first memory (112) includes information such as the common URSP policy, separate URSP policies, subscription details associated with the UE-1 (102A), subscription details associated with the UE-2 (102B), and the like. The first memory (112) is not limited to a volatile memory and / or a non-volatile memory. Further, the first memory (112) includes a plurality of computer-readable storage media. The first memory (112) includes non-volatile storage elements. For example, non-volatile storage elements includes magnetic hard disks, optical disks, floppy disks, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories.

[0250] The first I / O interface (114) transmits the information between the first memory (112) and external peripheral devices. The peripheral devices are the input-output devices associated with the UE (102). Further, the URSP handling controller (116) communicates with the first I / O interface (114) and the first memory (112). The URSP handling controller (116) is coupled to the first memory (112) and the first processor (110). This coupling allows for efficient data transfer and communication between the components, ensuring that the URSP handling controller (116) determines unavailability information (unavailability type, unavailability period duration, and a start of the unavailability period). The URSP handling controller (116) is an innovative integrated circuit that is implemented in the UE (102). In an embodiment, the structure of such innovative integrated circuit include a multi-core architecture that enables determination of unavailability information. Each core is optimized for specific tasks, such as determining unavailability information that includes an unavailability type, an unavailability period duration, and a start of the unavailability period. The innovative integrated circuit for the determination of the unavailability period is made of a combination of analog and digital components designed to enhance the unavailability period duration for determining power saving parameters and a periodic registration update time value. The analog components include a low-noise amplifier and a high-precision analog-to-digital converter to ensure accurate signal processing. The digital components consist of a microcontroller unit (MCU) and a digital signal processor (DSP) that work in tandem to dynamically determine the unavailability period information associated with the UE (102).

[0251] Fig. 3 is a block diagram that illustrates a schematic of a first network apparatus (302) implemented to carry out the disclosed subject matter according to an embodiment as disclosed herein. As shown, the first network apparatus (302) includes a second processor (304), a second memory (306), a second I / O interface (308), and a URSP policy obtaining controller(310) coupled to the second processor (304) and the second memory (306).

[0252] The first network apparatus (302) includes various hardware and software components that facilitate communication between user equipment and network infrastructure. Examples of the first network apparatus (302) can include, but is not limited to Base Stations (such as macro cells, small cells, femtocells, Pico cells) for wireless communication, Antennas and RF Units (e.g., MIMO, beamforming) to enhance signal coverage and data throughput, Core Network Equipment (e.g., MMEs, S-GWs, P-GWs in 4G; AMFs, UPFs in 5G) for data routing, mobility, and session control, Network Function Virtualization (NFV) and Software-Defined Networking (SDN) for dynamic resource allocation and scalability, Edge Computing Nodes (e.g., MEC servers) for low-latency processing,　 Backhaul and Transport Equipment (e.g., fiber-optic links, microwave relays, Ethernet switches) to connect base stations to the core network, Network Management Systems (NMS) and Operation Support Systems (OSS) for network configuration, fault management, and optimization, Radio Network Controllers (RNCs) in 3G, Distributed Units (DUs), and Centralized Units (CUs) in 5G, Network Slicing Components for virtualized resource allocation, Security elements (e.g., Firewalls, IDS, AAA Servers) for secure communication.

[0253] The second processor (304) communicates with the second memory (306), the second I / O interface (308), and the URSP policy obtaining controller (310). The second processor (304) is configured to execute instructions stored in the second memory (306) and to perform various processes. The second processor (304) includes one or a plurality of processors, is a general-purpose processor such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and / or an Artificial Intelligence (AI) dedicated processor such as a neural processing unit (NPU).

[0254] The second memory (306) includes storage locations to be addressable through the second processor (304). The second memory (306) includes information such as the common URSP policy, separate URSP policies, subscription details associated with the UE-1 (102A), subscription details associated with the UE-2 (102B), and the like. The second memory (306) is not limited to a volatile memory and / or a non-volatile memory. Further, the second memory (306) includes a plurality of computer-readable storage media. The second memory (306) includes non-volatile storage elements. For example, non-volatile storage elements includes magnetic hard disks, optical disks, floppy disks, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories.

[0255] The second I / O interface (308) transmits the information between the second memory (306) and external peripheral devices. The peripheral devices are the input-output devices associated with the first network apparatus (302). Further, the URSP policy obtaining controller (310) communicates with the second I / O interface (308) and the second memory (306). The URSP policy obtaining controller (310) is coupled to the second memory (306) and the second processor (304). This coupling allows for efficient data transfer and communication between the components, ensuring that the URSP policy obtaining controller (310) obtains the common URSP policy or separate URSP policies associated with the UE (102). The URSP policy obtaining controller (310) is an innovative integrated circuit that is implemented in the first network apparatus (302). In an embodiment, the structure of such innovative integrated circuit include a multi-core architecture that enables determination of unavailability information. Each core is optimized for specific tasks, such as obtains the common URSP policy or separate URSP policies associated with the UE (102). The innovative integrated circuit for the obtains the common URSP policy or separate URSP policies associated with the UE (102) is made of a combination of analog and digital components designed to enhance the determination the common URSP policy or separate URSP policies associated with the UE (102). The analog components include a low-noise amplifier and a high-precision analog-to-digital converter to ensure accurate signal processing. The digital components consist of a microcontroller unit (MCU) and a digital signal processor (DSP) that work in tandem to dynamically obtain the common URSP policy or separate URSP policies associated with the UE (102).

[0256] Fig. 4 is a block diagram that illustrates a schematic of a second network apparatus (402) implemented to carry out the disclosed subject matter according to an embodiment as disclosed herein. As shown, the second network apparatus (402) includes a third processor (404), a third memory (406), a third I / O interface (408), and a URSP policy determination controller(410) coupled to the third processor (404) and the third memory (406).

[0257] The second network apparatus (402) includes various hardware and software components that facilitate communication between user equipment and network infrastructure. Examples of the second network apparatus (402) can include, but is not limited to Base Stations (such as macro cells, small cells, femtocells, Pico cells) for wireless communication, Antennas and RF Units (e.g., MIMO, beamforming) to enhance signal coverage and data throughput, Core Network Equipment (e.g., MMEs, S-GWs, P-GWs in 4G; AMFs, UPFs in 5G) for data routing, mobility, and session control, Network Function Virtualization (NFV) and Software-Defined Networking (SDN) for dynamic resource allocation and scalability, Edge Computing Nodes (e.g., MEC servers) for low-latency processing,　 Backhaul and Transport Equipment (e.g., fiber-optic links, microwave relays, Ethernet switches) to connect base stations to the core network, Network Management Systems (NMS) and Operation Support Systems (OSS) for network configuration, fault management, and optimization, Radio Network Controllers (RNCs) in 3G, Distributed Units (DUs), and Centralized Units (CUs) in 5G, Network Slicing Components for virtualized resource allocation, Security elements (e.g., Firewalls, IDS, AAA Servers) for secure communication.

[0258] The third processor (404) communicates with the third memory (406), the third I / O interface (408), and the URSP policy determination controller (410). The third processor (404) is configured to execute instructions stored in the third memory (406) and to perform various processes. The third processor (404) includes one or a plurality of processors, is a general-purpose processor such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and / or an Artificial Intelligence (AI) dedicated processor such as a neural processing unit (NPU).

[0259] The third memory (406) includes storage locations to be addressable through the third processor (404). The third memory (406) includes information such as the common URSP policy, separate URSP policies, subscription details associated with the UE-1 (102A), subscription details associated with the UE-2 (102B), and the like. The third memory (406) is not limited to a volatile memory and / or a non-volatile memory. Further, the third memory (406) includes a plurality of computer-readable storage media. The third memory (406) includes non-volatile storage elements. For example, non-volatile storage elements includes magnetic hard disks, optical disks, floppy disks, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories.

[0260] The third I / O interface (408) transmits the information between the third memory (406) and external peripheral devices. The peripheral devices are the input-output devices associated with the second network apparatus (402). Further, the URSP policy determination controller (310) communicates with the third I / O interface (408) and the third memory (406). The URSP policy determination controller (410) is coupled to the third memory (406) and the third processor (404). This coupling allows for efficient data transfer and communication between the components, ensuring that the URSP policy determination controller (410) obtains the common URSP policy or separate URSP policies associated with the UE (102). The URSP policy determination controller (410) is an innovative integrated circuit that is implemented in the second network apparatus (402). In an embodiment, the structure of such innovative integrated circuit include a multi-core architecture that enables determination of unavailability information. Each core is optimized for specific tasks, such as obtains the common URSP policy or separate URSP policies associated with the UE (102). The innovative integrated circuit for the obtains the common URSP policy or separate URSP policies associated with the UE (102) is made of a combination of analog and digital components designed to enhance the determination the common URSP policy or separate URSP policies associated with the UE (102). The analog components include a low-noise amplifier and a high-precision analog-to-digital converter to ensure accurate signal processing. The digital components consist of a microcontroller unit (MCU) and a digital signal processor (DSP) that work in tandem to dynamically obtain the common URSP policy or separate URSP policies associated with the UE (102).

[0261] Fig. 5 is a sequence diagram that illustrates a scenario of dual steering service provided by a both the UE-1 (102A) and the UE-2 (102B) of the UE (102) according to an embodiment as disclosed herein. As shown in the sequence diagram, the UE (102), the first network apparatus (302), the H-PCF (106), and the second network apparatus (402) are in communication with each other. Each step is explained in further detail below. Here, the UE-1 (102A) is the primary UE or the first SIM. The first network apparatus (302) for registration (step 1, 2) is an AMF (104). For the PDU session establishment (step 5, 6 and 8, 9), the first network apparatus (302) and the second network apparatus (402) is an SMF.

[0262] At step 1, the UE-1 (102A) on the PLMN-1, performs the registration procedure. The UE-1 (102A) indicates the UPSI it has in the registration request (UPSI of combined / common URSP). The UE (102) may receive updated URSP policy in registration accept off after that through configuration update command. The UE (102) updates the combined / or common URSP with the received URSP rule on the UE-1 (102A).

[0263] At step 2, the UE-2 (102B) is on PLMN-2 and performs the registration procedure. The UE (102) indicates the UPSI in the registration request (the UE-2 (102B) indicates the UPSI of the combined URSP rule). The UE (102) may receive updated URSP policy in registration accept off after that through configuration update command. If received, the UE-2 (102B) updates the combined / or common URSP with the received URSP rule on the UE-1 (102A).

[0264] At step-3, an application X opened. At step 4, a URSP layer check combined / common URSP for the association of application X on the PDU session. I.e. common / combined URSP is evaluated for the association. If the match is found in the URSP rule for the application X. At step 5, the UE-1 (102A) initiates PDU session with the attributes of the matched rules (RSD of the matched URSP rule). Optionally, the UE (102) indicates that the PDU session establishment is for the Dual Steer PDU session

[0265] At step 6, the UE (102) receives a PDU session establishment accept with indication that PDU session is Dual Steer PDU session. The indication can come as new information element or PCO / ePCO or any NAS message. At step 7, an IP address is passed to the application. At step 8, the UE-2 (102B) initiates PDU session establishment with the attributes of the PDU session established in step-5-6 (with the same HPLMN S-NSSAI and DNN). At step 9, the UE-2 (102B) receives the PDU session establishment accept message. At step 10, application-x data is sent over the user plane of the UE-1 (102A) and / or the UE-2 (102B).

[0266] In an embodiment, when the application X is opened, it always attempts to the establish PDU session on the UE-1 (102A). If the PDU session is established as Dual Steer PDU session, then only the UE-2 (102B) establishes the PDU session establishment. In an embodiment, in step 10, application X data will be routed through the user plane of the UE-1 (102A) or the UE-2 (102B) based on the service availability, signal strength, Dual Steer policy (e.g. : the first network apparatus (302) indicates to send data on the UE-1 (102A) when the UE-1 (102A) is available or send data on the UE-1 (102A) and use the UE-2 (102B) to send data when the UE-1 (102A) is out of service or PDU session of the UE-1 (102A) associated with application is released or rejected).

[0267] Fig. 6 is a sequence diagram that illustrates a scenario of dual steering service provided by the UE-1 (102A) only according to an embodiment as disclosed herein. As shown in the sequence diagram, the UE (102), the first network apparatus (302), the H-PCF (106), and the second network apparatus (402) are in communication with each other. Each step is explained in further detail below. Here, the UE-1 (102A) is the primary UE or the first SIM. The first network apparatus (302) for registration (step 1, 2) is an AMF (104). For the PDU session establishment (step 5, 6 and 8, 9), the first network apparatus (302) and the second network apparatus (402) is an SMF.

[0268] At step 1, the UE-1 (102A) on the PLMN-1, performs the registration procedure. The UE-1 (102A) indicates the UPSI it has in the registration request (UPSI of combined / common URSP). The UE (102) may receive updated URSP policy in registration accept off after that through configuration update command. The UE (102) updates the combined / or common URSP with the received URSP rule on the UE-1 (102A).

[0269] At step 2, the UE-2 (102B) is on PLMN-2 and performs the registration procedure. The UE (102) indicates the UPSI in the registration request (the UE-2 (102B) indicates the UPSI of the combined URSP rule). The UE (102) may receive updated URSP policy in registration accept off after that through configuration update command. If received, the UE-2 (102B) updates the combined / or common URSP with the received URSP rule on the UE-1 (102A).

[0270] At step 3, the application X is opened. At step 4, URSP layer check combined / common URSP for the association of application X on the PDU session. I.e. common / combined URSP is evaluated for the association. If the match is found in the URSP rule for the application X.

[0271] At step 5, if the UE-1 (102A) (OOS) or the UE-2 (102B) is in connected state (non-simultaneous UE) or in a state where the PDU session at that time can't be established. The UE (102) has the policy (e.g. Dual steer Policy given by the second network apparatus (402) e.g. PCF / UDM) which indicates that PDU session with the attributes of the matched URSP rule (DNN, S-NSSAI) supports Dual Steer PDU session (i.e. PDU session can be established as Dual steering PDU session).

[0272] At step 6, the UE (102) receives the PDU session establishment accept with indication that PDU session is Dual Steer PDU session. The indication can come as new information element or PCO / ePCO or any NAS message. If the PDU session is established which is of non-Dual Steer PDU session, the UE-2 (102B) shall abort / release the PDU session

[0273] At step 7, the IP address is passed to the application. At step 8, the UE-1 (102A) initiates the PDU session establishment with the attributes of the PDU session established in step 5-6 (with the same HPLMN S-NSSAI and DNN) if it come to state where PDU session can be established. At step 9, the UE-1 (102A) receives the PDU session establishment accept message. At step 10, the application-x data is sent over the user plane of the UE-1 (102A) and / or the UE-2 (102B).

[0274] In an embodiment, when the application X is opened, the PDU session is established on the UE (102) (the UE-1 (102A) or the UE-2 (102B)) where PDU session establishment is possible and the UE (102) has the policy (Dual steer Policy given by the NF e.g. PCF / UDM), which indicates that PDU session with attributes (e.g. S-NSSAI, DNN) can be established as Dual Steer. The policy to indicate whether Dual PDU session is supported for the matched URSP or its attribute can be in the URSP rule itself (in traffic descriptor or route selection descriptor) and network give additional policy where it says S-NSSAI+DNN can be established as Dual Steer PDU session. i.e. If the UE (102) has the dual steer policy for the DNN-X, S-NSSAI-X, then the UE (102) can initiate PDU session establishment on any UE (102) (the UE-1 (102A) or the UE-2 (102B)) with the DNN-X, S-NSSAI-X. If the dual steer policy doesn't have the DNN-X, S-NSSAI-X, then the UE-1 (102A) is only used for the PDU session establishment with DNN-X, S-NSSAI-X.

[0275] Fig. 7 is a sequence diagram that illustrates a scenario of dual steering service provided by the UE-2 (102B) according to an embodiment as disclosed herein. As shown in the sequence diagram, the UE (102), the first network apparatus (302), the H-PCF (106), and the second network apparatus (402) are in communication with each other. Each step is explained in further detail below. Here, the UE-1 (102A) is the primary UE or the first SIM. The first network apparatus (302) for registration (step 1, 2) is an AMF (104). For the PDU session establishment (step 5, 6 and 8, 9), the first network apparatus (302) and the second network apparatus (402) is an SMF.

[0276] At step 1, the UE-1 (102A) on the PLMN-1, performs the registration procedure. The UE-1 (102A) indicates the UPSI it has in the registration request (UPSI of combined / common URSP). The UE (102) may receive updated URSP policy in registration accept off after that through configuration update command. This URSP policy is specific for the UE-1 (102A).

[0277] At step 2, the UE-2 (102B) is on PLMN-2 and performs the registration procedure. The UE (102) indicates the UPSI in the registration request (the UE-2 (102B) indicates the UPSI of the combined URSP rule). The UE (102) may receive updated URSP policy in registration accept off after that through configuration update command. If received, the UE-2 (102B) considers the URSP specific to the UE-2 (102B). The URSP associated with the UE -2 (102B) will contain attributes, which supports only Dual Steer PDU session (i.e. if the PDU session is established with URSP / RSD of the UE-2 (102B), it always be a Dual Steer PDU session)

[0278] At step 3, the application X is opened. At step 4, if there is matching URSP rule (non-default) in the UE-1 (102A), then the UE-1 (102A) establishes the PDU session with the attributes of RSD of matched rule. At step 5, the UE-1 (102A) initiates the PDU session with the attributes of the matched rules (RSD of the matched URSP rule). Optionally, the UE (102) indicates that the PDU session establishment is for the Dual Steer PDU session.

[0279] At step 6, the UE (102) receives the PDU session establishment accept with indication that PDU session is Dual Steer PDU session. The indication can come as new information element or PCO / ePCO or any NAS message. At step 7, the IP address is passed to the application.

[0280] At step 8, the UE-2 (102B) independently evaluates the URSP rule of the UE-2 (102B). If matching is found then follows step 9 and 10. If matched URSP rule is not available for the application, the UE-2 (102B) doesn't establish PDU session on the UE-2 (102B). At step 9, the UE-2 (102B) initiates the PDU session establishment with the attributes of RSD of the matched URSP rule of UE-2 (102B). At step 10, the UE-2 (102B) receives the PDU session establishment accept message and application-x data is sent over the user plane of the UE-1 (102A) and / or the UE-2 (102B).

[0281] In an embodiment, when the application X is opened, the UE-1 (102A) and the UE-2 (102B) both evaluate the URSP rule of associated with it (i.e. the UE-1 (102A) evaluates the URSP rule of the UE-1 (102A) and the UE-2 (102B) evaluate the URSP rule of the UE-2 (102B)). The UE (102) establishes the PDU session on the corresponding UE (102) with the RSD of the matched URSP rule and associate application on the established PDU session. For example, application X opened and only matched URSP available in the UE-1 (102A), the UE (102) establishes the PDU session in the UE-1 (102A) and application X is considered associated with the PDU session of matched URSP rule. The Application X opened and the matched URSP available is available in the UE-1 (102A). Then the UE-1 (102A) and the UE-2 (102B) establish the PDU session in the UE-1 (102A) and the UE-2 (102B) and application X is considered associated with the PDU session of matched URSP rule of the UE-1 (102A) and the UE-2 (102B). In this case, the same IP address would be received in the UE-1 (102A) and the UE-2 (102B).

[0282] In an embodiment, the UE (102) establishes the PDU session establishment on the UE-2 (102B) as Dual Steer PDU session (i.e. if the PDU session established with URSP of the UE-2 (102B) with e.g. S-NSSAI-X, DNN-X for the application-X then the UE-1 (102A) will also have URSP rule with the same attributes and will be able to establish PDU session with e.g. S-NSSAI-X, DNN-X for the application-X).

[0283] Fig. 8 is a sequence diagram that illustrates a scenario of dual steering service provided by the UE-2 (102B) according to an embodiment as disclosed herein. As shown in the sequence diagram, the UE (102), the first network apparatus (302), the H-PCF (106), and the second network apparatus (402) are in communication with each other. Each step is explained in further detail below. Here, the UE-1 (102A) is the primary UE or the first SIM. The first network apparatus (302) for registration (step 1, 2) is an AMF (104). For the PDU session establishment (step 5, 6 and 8, 9), the first network apparatus (302) and the second network apparatus (402) is an SMF.

[0284] At step 1, the UE-1 (102A) on the PLMN-1, performs the registration procedure. The UE-1 (102A) indicates the UPSI it has in the registration request (UPSI of combined / common URSP). The UE (102) may receive updated URSP policy in registration accept off after that through configuration update command. The UE (102) updates the combined / or common URSP with the received URSP rule on the UE-1 (102A).

[0285] At step 2, the UE-2 (102B) is on PLMN-2 and performs the registration procedure. The UE (102) indicates the UPSI in the registration request (the UE-2 (102B) indicates the UPSI of the combined URSP rule). The UE (102) may receive updated URSP policy in registration accept off after that through configuration update command. If received, the UE-2 (102B) updates the combined / or common URSP with the received URSP rule on the UE-1 (102A).

[0286] At step 3, the application X is opened. At step 4, URSP layer check combined / common URSP for the association of application X on the PDU session. I.e. common / combined URSP is evaluated for the association. If the match is found in the URSP rule for the application X. Upper layer (or URSP layer indicate the attributes of PDU session to be established for the application X), if its DNN-X, S-NSSAI-X: At step 5, the UE (102) checks if Dual Steering policy is available in the UE (102). If the Dual Steering policy is available in the UE (102), for an example (Dual steer policy may be sent by the NF (e.g. PCF, UDM, SMF etc.) or configured in the UE (102)). DNN-X, S-NSSAI-X - Dual Steer, DNN-Z - Dual Steer, S-NSSAI-A- Dual Steer.

[0287] As the PDU session to be established with DNN-X and S-NSSAI-x are Dual Steering in the policy. In this case, the UE-2 (102B) will also establish the PDU session with the DNN-X and S-NSSAI-X irrespective of the PDU session on the UE-1 (102A) is established or not with the DNN-X and S-NSSAI-X. In this case, step 5-6 and 7-8 are independent and can executed concurrently.

[0288] In an embodiment, the Dual Steering policy can be sent to the UE (102) from NF (e.g. UDM / PCF) over the NAS (e.g. along with registration accept or UE configuration update command) message or any other message or ESM message (alone with PDU session modification command, PDU session establishment accept or any other 5SM message. The policy can be included in PCO / ePCO)

[0289] In an embodiment, if the URSP is evaluated and PDU session is determined to be established with S-NSSAI-X and DNN-X and if these attributes are in the Dual Steering policy, then the UE-2 (102B) may establish the PDU session with DNN-X, S-NSSAI-X on the UE-2 (102B) (e.g. the UE-1 (102A) is OOS-Out of service or UE-2 is RRC connected mode etc.).

[0290] In an embodiment, if the attribute DNN-X, S-NSSAI-x is in the dual steering policy, then the UE-1 (102A) and the UE-2 (102B) always initiate PDU session with dual steer PDU type.

[0291] In an embodiment, if the URSP re-evaluation cause the UE-1 (102) to release the Dual Steer PDU session (e.g. PDU session with PDU session ID-1) then the PDU session with PDU session ID-1 (if available) is released from UE-2 (102B). This can be done either by explicit signaling from the Network (e.g. AMF (104) / SMF release PDU session through PDU session release command) or through the UE initiated PDU session release request. This also applies to a case where the UE-1 (102A) PDU session is released (e.g. due to 5GSM cause).

[0292] In an embodiment, the common / combined URSP policy can come through the UE-1 (102A) and UE-2 (102B) (any of the UE (102)). The UE (102) maintain common URSP layer / or any other layer which handles the received URSP policy through the UE-1 (102A) and the UE-2 (102B).

[0293] In an embodiment, Dual Steering policy, Dual steering PDU type etc. can have different name.

[0294] In an embodiment, the UE (102) can be provided with the URSP rule. In this solution: Each UE (102) can be provided with the URSP rule. Each URSP rule may be associated with Dual Steer PDU session or Standalone PDU session. When application is opened, it can evaluate URSP rule of the UE (102) independently.

[0295] Fig. 9 is a sequence diagram that illustrates events where the first network apparatus (302) and the second network apparatus (402) indicate a type of URSP policy and its association with the UE (102) according to an embodiment as disclosed herein. As shown in the sequence diagram, the UE (102), the first network apparatus (302), the H-PCF (106), and the second network apparatus (402) are in communication with each other. Each step is explained in further detail below.

[0296] At step 1, the UE (102) (Dual Steer Capable) triggers a registration with and identifier that informs the first network apparatus (302) that the UE (102) is registering for dual steering. The UE (102) sends a 5GMM message e.g. REGISTRATION REQUEST / UL NAS TRANSPORT or any other NAS message and updates it's capability of "dualSteer capable" and registers to the first network apparatus (302) (first access network). At steps 2 and 3, the first network apparatus (302) (the AMF (104) of HPLMN / VPLMN_1) interacts with the H-PCF (106) / UDM for e.g. using Nudm_UECM_Registration operation or some NF and retrieves the subscription data or policy for the UE (102). At step 4, UE Configuration Update procedure happens and the UE (102) gets the policy based on the subscription details for the first access / SUPI-1 / UE-1 (102A).

[0297] At step 5, UE (102) (Dual Steer Capable) triggers a registration to the second network apparatus (402) (second access network). The UE (102) sends a 5GMM message e.g. REGISTRATION REQUEST / UL NAS TRANSPORT or any other NAS message and registers to the second apparatus network (402). At steps 6 and 7, the second network apparatus (402) (the AMF (104) of the second access network) interacts with the H-PCF (106) / UDM for e.g. using Nudm_UECM_Registration operation or some NF and retrieves the subscription data or policy for the UE (102). At step 8, the UE Configuration Update procedure happens and the UE (102) gets the policy for the second access / SUPI-2 / UE-2 (102B).

[0298] In steps 4 and / or 8: The first network apparatus (302) and the second network apparatus (402) indicates type of URSP policy and its association with the UE (102) / Stack for example URSP is combined URSP rule or URSP rule is only restricted to the stack on which the UE (102) has received them and if the same is applicable for other access / subscription.

[0299] For example,

[0300] a) NF (e.g. PCF / AMF (104)) indicate to the UE (102) that URSP policy is for the current access / SUPI / UE (102) where it is received. In absence of this such indication, the UE (102) may assume that URSP policy is for the current access / SUPI / UE (102) where the URSP is received.

[0301] b) NF (e.g. PCF / AMF (104)) indicate to the UE (102) that URSP policy is combined URSP and applicable for both the UE (102) / SUPI.

[0302] c) Additionally, the NF (PCF / AMF (104)) indicate to the UE (102) applicable to the UE (102) / SUPI where it is received and combined URSP (policy specified in bullet a + policy specified in bullet b)

[0303] In an embodiment, the UE (102) of the Dual Steer UE is associated with the separate SUPI and can sometime referred as the UE-1 (102A) and the UE-2 (102B). The Network Function (e.g., the H-PCF (106) / UDM) shall add an indication for the UE (102) to identify whether the URSP rule is applicable to both the stacks (consolidated) or independently to each stack. The network can incorporate the below mentioned options for indicating which stack / SUPI / Access the rule is to be used by the dual steer device-

[0304] Option 1: Each URSP rule mentioning which stack it is intended for.

[0305] Rule-1 - intended only for SUPI-1 / Stack-1 / Access-1 / UE-1 (102A)

[0306] Rule-2 - intended only for SUPI-2 / Stack-2 / Access- / UE-2 (102B)

[0307] Rule-3 - Common rules intended for both SUPI-1 / Stack-1 / Access-1 and SUPI-2 / Stack-2 / Access-2

[0308] Option 2: Combined URSP rule with IDs differentiating stacks / Accesses / SUPIs

[0309] URSP-1 (Rule ID1, Rule ID2 .. Rule IDn) - intended only for SUPI-1 / Stack-1 / Access-1

[0310] URSP-2 (Rule ID1, Rule ID2 .. Rule IDn) - intended only for SUPI-2 / Stack-2 / Access-2

[0311] URSP-3 (Rule ID1, Rule ID2 .. Rule IDn) - Common rules intended for both SUPI-1 / Stack-1 / Access-1 and SUPI-2 / Stack-2 / Access-2

[0312] Option 3: Combined URSP rule that is common for both the SUPIs / Accesses / Stacks

[0313] URSP-Common.

[0314] In an embodiment, the network has an option to send all the rules on one of the accesses or independently on both of them. For e.g., in Option 1 & 2 above, the Rule1 / URSP-1 can be sent on the first network apparatus (302) when the UE (102) (dual-steer) registers on the first network apparatus (302) and URSP-2 and Rule-2 / URSP2, Rule-3 / URSP-3 can be sent on the second network apparatus (402) when registration on the second network apparatus (402) is successfully completed.

[0315] Fig. 10 is a sequence diagram that illustrates the UE (102) indicating a policy identification to the first network apparatus (302) and the second network apparatus (402) according to an embodiment as disclosed herein. As shown in the sequence diagram, the UE (102), the first network apparatus (302), the H-PCF (106), and the second network apparatus (402) are in communication with each other. Each step is explained in further detail below.

[0316] At step 1, the UE (102 (Dual Steer Capable) triggers a registration to the first network apparatus (302) (first access network) and there is an identifier which informs the first network apparatus (302) that the UE (102) is registering for dual steering. The UE (102) sends a 5GMM message e.g. REGISTRATION REQUEST / UL NAS TRANSPORT or any other NAS message and updates it's capability of "dualSteer capable" and registers to the first network apparatus (302). At steps 2 and 3, the AMF (104) of the first network apparatus (302) interacts with the H-PCF (106) / UDM for e.g. using Nudm_UECM_Registration operation or some NF and retrieves the subscription data or policy for the UE (102). At step 4, the UE Configuration Update procedure happens and the UE (102) gets the policy based on the subscription details for the first network apparatus (302).

[0317] At step 5, the UE (102) (Dual Steer Capable) triggers a registration to the second network apparatus (402) (second access network). The UE (102) sends a 5GMM message e.g. REGISTRATION REQUEST / UL NAS TRANSPORT or any other NAS message and registers to the second network apparatus (402). At steps 6 and 7, the AMF (104) of the second network apparatus (402) interacts with the H-PCF (106) / UDM for e.g. using Nudm_UECM_Registration operation or some NF and retrieves the subscription data or policy for the UE (102). At step 8, the UE Configuration Update procedure happens and the UE (102) gets the policy based on the subscription details for the second network apparatus (402).

[0318] At step 9, the UE (102) shall include the policy ID (UPSI) in the subsequent procedures such as for example MM / SM messages to indicate network about the policy being considered by the UE (102) (i.e. combined URSP policy / stack pertaining URSP policy like stack 1 UE policy or stack 2 UE policy).

[0319] In an embodiment, when the UE (102) has the combined / common URSP policy, then the UE (102) indicates the UPSI of the combined / common URSP in the registration of the UE (102) (i.e. the UE-1 (102A) and the UE-2 (102B) indicate the UPSI of the combined / common UE (102)).

[0320] In an embodiment, when the UE-1 (102A) and the UE-2 (102B) has the specific policy for the UE-1 (102A) and the UE-2 (102B), then the UE-1 (102A) indicate UPSI of the UE-1 (102A) in the registration request or any other NAS message. The UE-2 (102B) indicates the UPSI of the UE-2 (102B) in the registration request or any other NAS message.

[0321] In an embodiment, the UE-1 (102A) and the UE-2 (102B) indicates the UPSI of both the UEs even though the UE-1 (102A) and the UE-2 (102B) received the URSP policy in their respective NAS message (e.g. the UE-1 (102A) have the UPIS-1 and the UE-2 (102B) have UPSI-2, then the UE-1 (102A) and the UE-2 (102B) both include UPSI-1 and UPSI-2 in the registration request and another NAS message)

[0322] In an embodiment, if the UE (102) receives (e.g. the UE-1 (102A)) the new policy then the other UE (102) (e.g. the UE-2 (102B)) initiates the registration procedure and indicate the updated UPSI that included the received UPSI in the UE-1 (102A).

[0323] Fig. 11 is a sequence diagram that illustrates events of URSP re-evaluation trigger considering dual steering according to an embodiment as disclosed herein. As shown in the sequence diagram, the UE (102), the first network apparatus (302), the H-PCF (106), and the second network apparatus (402) are in communication with each other. Each step is explained in further detail below.

[0324] In an embodiment, the first network apparatus (302) and the second network apparatus (402) indicates the type of URSP policy and its association with the UE (102) / stack. If the UE (102) received URSP policy for the SUPI-1 / UE-1 (102A) as URSP Rule ID 1: TD1+ RSD1, Precedence 1, and URSP Rule ID 2: TD2+ RSD2, Precedence 2, and URSP Rule ID a: Default. If the UE (102) received URSP policy for the SUPI-2 / UE-2 as URSP Rule ID 3: TD1+ RSD3, Precedence 3, and URSP Rule ID 4: TD2+ RSD2, Precedence 4, URSP Rule ID b: Default. If the Application X is matched with TD1. In step 9, the Application X opened.

[0325] At step 1, the UE (102) evaluates URSP rules associated with both SUPI-1 (say URSP-1) and SUPI-2 (say URSP-2)

[0326] Case 1: If non-default URSP rule is matched for the application X is available only in one of the two policies (e.g., say URSP-2), the UE (102) shall follow the procedure to establish PDU session and route the application X data using the matched rules of the URSP-2 (i.e. associate application x data on PDU session established using the matched RSD of the matched TD of the URSP-2).

[0327] Case 2: If non-default URSP rule is matched for the application X is available in both the URSP rules (i.e... In both URSP-1 and URSP-2). In this case, the UE (102) shall check the precedence. The UE (102) shall select the rule with low precedence value (i.e., higher the precedence). In this case as the TD1 is matched but the precedence value for the URSP rule -1 is lower compared to URSP rule 3, the UE (102) shall follow the procedure to establish PDU session or route the application X data using the matched rules of the URSP-1. Optionally, if the UE-1 (102A) is in Out of service and not able to establish PDU session on the matched TD / RSD, the UE-2 (102B) URSP can be used for the PDU session establishment and associating application X on that established PDU session.

[0328] In this embodiment, for the matched TD-1 for an application X, if the PDU session is established on the UE (102) (say the UE-1 (102A)) with S-NSSAI-H, DNN-H as Dual Steer PDU session, then the UE (102) shall establish the PDU session with the UE-2 (102B) only if the URSP-2 have the policy for the TD-1 and the RSD have the S-NSSAI-H and DNN-x

[0329] In an embodiment, the UE (102) determines the two SUPIs related to dual steering device (in this case URSP-1 and URSP-2).

[0330] In an embodiment, the UE (102) shall do the URSP re-evaluation on both the URSP when event occurs on any of the SUPI / UE (102), to keep the application on the best / optimal URSP rule.

[0331] In an embodiment, the NF shall use the distinct URSP rule id (UPSI) for the URSP-1 and URSP-2 (i.e. there shall not be any common UPSI ID in the URSP-1 and URSP-2 belonging to the two UE) or alternatively, the NF may indicate common UPSI ID and if the UPSI ID is common is URSP-1 and URSP-2, it is assumed that particular policy supports dualSteer PDU session.

[0332] In an embodiment, the UE (102) may re-evaluate the URSP rules, to check if the change of the association of an application or a PIN to a PDU session is needed, when below occurs on any of the UE (102) / USIM and while doing re-evaluation, the UE (102) considers both the UE (102) / USIM policies for the evaluation:

[0333] At step 1, the UE (102) (Dual Steer Capable) triggers a registration to the first network apparatus (302) (first access network) and there is an identifier which informs the first network apparatus (302) that the UE (102) is registering for dual steering. The UE (102) sends a 5GMM message e.g. REGISTRATION REQUEST / UL NAS TRANSPORT or any other NAS message and updates it's capability of "dualSteer capable" and registers to the first network apparatus (302). At steps 2 and 3, the AMF (104) of the first network apparatus (302) interacts with the H-PCF (106) / UDM for e.g. using Nudm_UECM_Registration operation or some NF and retrieves the subscription data or policy for the UE (102). At step 4, the UE Configuration Update procedure happens and the UE (102) gets the policy based on the subscription details for the first network apparatus (302).

[0334] At step 5, the UE (102) (Dual Steer Capable) triggers a registration to the second network apparatus (402) (second access network). The UE (102) sends a 5GMM message e.g. REGISTRATION REQUEST / UL NAS TRANSPORT or any other NAS message and registers to the second network apparatus (402). At steps 6 and 7, the AMF (104) of the second network apparatus (402) interacts with the H-PCF (106) / UDM for e.g. using Nudm_UECM_Registration operation or some NF and retrieves the subscription data or policy for the UE (102). At step 8, the UE Configuration Update procedure happens and the UE (102 gets the policy combined for the first network apparatus (302) & the second network apparatus (402). With properly defined precedence rule in terms of TD or RSD.

[0335] At step 9, the UE (102) now has URSP policies considering both the accesses having properly defined precedence rule. Precedence can be in the TD or RSD. URSP Re-evaluation events defined in TS 24.526 section 4.2.2.2 shall include DualSteer specific scenarios like - OOS on first access / second access, inter-system change on first access / second access, MM / SM related rejects / failures etc.

[0336] NOTE　15: The time when the UE (102) performs the re-evaluation is up to UE implementation. It is recommended that the UE (102) performs the re-evaluation in a timely manner.

[0337] a) The UE (102) performs periodic URSP rules re-evaluation based on UE implementation;

[0338] b) The UE NAS layer indicates that an existing PDU session used for routing traffic of an application or a PIN based on a URSP rule is released;

[0339] c) The URSP is updated by the H-PCF (106);

[0340] d) The UE NAS layer indicates that the UE (102) performs inter-system change from S1 mode to N1 mode;

[0341] e) The UE NAS layer indicates that the UE (102) is successfully registered in N1 mode over 3GPP access or non-3GPP access;

[0342] f) The UE (102) establishes or releases a connection to a WLAN access and transmission of a PDU of the application via non-3GPP access outside of a PDU session becomes available / unavailable;

[0343] g) The allowed NSSAI, the partially allowed NSSA or the configured NSSAI is changed;

[0344] h) The LADN information or the extended LADN information is changed;

[0345] i) The UE NAS layer indicates that back-off timer T3396, T3584 or T3585 (see 3GPP　TS　24.501

[0011] clause　6.2.7 and clause　6.2.8) is stopped or expired;

[0346] j) The UE NAS layer indicates the successful change of the PLMN; or

[0347] k) The UE NAS layer indicates that current TAI is in the list of TAs for which the S-NSSAI is allowed (see 3GPP　TS　24.501

[0011] clause　4.6.3.6).

[0348] If the re-evaluation leads to a change of the association of an application or a PIN to a PDU session, the UE (102) may enforce such change immediately or when UE returns to 5GMM-IDLE mode.

[0349] NOTE　16: The time when the UE (102) enforces the change of the association of an application or a PIN to a PDU Session is up to UE implementation. It is recommended that the UE (102) performs the enforcement in a timely manner. The URSP handling layer may request the UE NAS layer to release an existing PDU session after the re-evaluation.

[0350] In an embodiment, the UE (102), USIM, SUPI is used interchangeably. SUPI / USIM will be different for the UE (102). Current state of Art: The UE (102) and network maintain / support URSP for each SIM / UE (102) separately.

[0351] In an embodiment, in case of dual steer device, as the subscription is common, so dual steer device can have separate URSP or common URSP for the participating two UE / SIM for the dual steering.

[0352] In an embodiment, the UE (102) consider, received URSP on any USIM / UE (102) is valid for the other USIM / UE (102) and use the same rule. In an embodiment, the H-PCF (106) provide the combined URSP rules for the SIM / UE-1 (102A) and the SUM / UE-2 (102B) to the UE (102). Additionally, the H-PCF (106) informs to the UE (102) that the USRP policy is for both the UE (102) / SIM (i.e. both the SIM / UE (102) of the dual steer device)

[0353] In an embodiment, the H-PCF (106) can send URSP rules related to both SUPI / SIM / UE (102) on any one of the 3GPP access or on both 3GPP access with details on which of the rules belongs to which SUPI / SIM / UE (102) / subscription / PNEI.

[0354] New methods shall consider various factors as below-

[0355] Having two different URSP rules for the two accesses / SUPIs / Subscriptions OR add changes in the current URSP to handle DS scenarios. If decided to have two --> the UE (102) should include the policy ID. If single / combined URSP needs to be used, then it shall consider both the accesses & properly define the precedence rule. Precedence can be in the TD (traffic descriptor) or RSD (route selection descriptor), Network function for example PCF can indicate which of the URSP rules are applicable for both SIMs / Stacks and which are the rules are applicable only to respective SIM / stack by including a SUPI identifier associating with each of the URSP rule.

[0356] Re-evaluation criterion doesn't consider dualSteer right now ("3GPP TS 24.526 - 4.2.2.2 Association between an application and a PDU session, non-seamless non-3GPP offload or 5G ProSe layer-3 UE-to-network relay offload by a UE"). Scenarios specific to dualSteer cases like OOS on first access / second access, inter-system change on first access / second access, MM / SM related rejects / failures etc. are to be considered.

[0357] The UE (102) / network maintain one URSP rules. Network (e.g. AMF (104) / PCF) indicates to the UE (102) (e.g., in the Network-requested UE policy management command or any other message) that the URSP policies is for the dual steering device. The UE (102) considers the URSP policies received is valid for both participating UE / USIM (of dual steering device).

[0358] a) If the UE-1 (102A) is registered on PLMN-1 and received the URSP policies with UPSI-1, UPSI-2, etc. The UE (102) shall indicate the availability of the UPSI-1, UPSI-2 etc. when registering on the UE-2 (102B).

[0359] b) Similarly, PCF / AMF (104) / UDM indicate to the UE (102) that VPS, URSP policy, PG policies etc. is for both the UE (102). The UE (102) reports the UPSI list when registering on any of the UE (102) / USIM (i.e. if the UE (102) received policy through the UE-1 (102A), it shall report the available URSP policy to the UE-2 (102B) in the registration)

[0360] c) When the UE (102) is registered on the UE-1 (102A) and the UE-2 (102B) receive URSP policies on the UE (102) (e.g. the UE-1 (102A)). The policy can be additional URSP policy, deletion of URSP policies, then the UE (102) shall update the other network with the updated policies (e.g. the UE-2 (102B) update the updated policies by initiating registration with Updated UPSI list). The UE (102) determines the two UE / SUPI / SIM where common URSP rules to be applied (two UE forming the dual steering device). The UE (102) sends USPI ID received for the UE-1 (102A) in the UE-2 (102B). When the UE (102) receives updated URSP for the UE-1 (102A), the UE-2 (102B) shall initiate the registration procedure and indicate the UPSI received to the network.

[0361] If:

[0362] ▶ The UE (102) registered on the first SIM / UE-1 (102A)

[0363] ▶ The UE (102) registered on the second SIM / UE-2 (102B)

[0364] The problem of TD matching is seen, where application X opened, matching attributed for the application X is available on the UE-1 (102A) (matching TD for the application X is available on the UE-1 (102A)),

[0365] In an embodiment, in case the UE (102) is in the service on the first SIM / UE-1 (102A), the UE (102) shall initiate the PDU session establishment and use the PDU session for the application x. If PDU session is not established, the UE (102) shall stop here and shall not try the second SIM / UE-2 (102B) for the data connection.

[0366] In case if the application X opened, matching attributed for the application X is available on the first SIM / UE-1 (102A) and the second SIM / UE-2 (102B) (matching TD for the application X is available on both the UE (102) / SIM),

[0367] The UE (102) shall re-evaluate and try establishing data on the UE (102) / SIM as below.

[0368] ▶ If both the UE (102) / SIM is in the service, then shall be left for the implementation which one to select

[0369] ▶ If only one UE (102) / SIM is in the service, the UE (102) shall try to establish data session / associate data session on the UE (102) / SIM have the service (i.e. evaluation or re-evaluation of the URSP associated with the UE (102) / SIM which is in the service)

[0370] ▶ When the UE (102) / SIM go to OOS, the UE-1 (102A) shall re-evaluate the UE-2 (102B) and if matching URSP rule found, associate application (i.e. if the UE-1 (102A) / SIM-1 is going to out of service then the UE-2 (102B) URSP shall be evaluated or re-evaluated and if the policy is found then UE application can be associated with the matching rule of the URSP of the UE-2 (102B) / SIM-2).

[0371] ▶ in an embodiment, the UE (102) may re-evaluate the URSP for the both the UE-1 (102A) / SIM-1 and the UE-2 (102B) / SIM-2 or the UE (102) or SIM which in the service when below condition happens on any of the SIM / UE (102):

[0372] ▶ a) The UE (102) performs periodic URSP rules re-evaluation based on UE implementation;

[0373] ▶ b) The UE NAS layer indicates that an existing PDU session used for routing traffic of an application or a PIN based on a URSP rule is released;

[0374] ▶ c) The URSP is updated by the H-PCF (106);

[0375] ▶ d) The UE NAS layer indicates that the UE (102) performs inter-system change from S1 mode to N1 mode;

[0376] ▶ e) The UE NAS layer indicates that the UE (102) is successfully registered in N1 mode over 3GPP access or non-3GPP access;

[0377] ▶ f) The UE (102) establishes or releases a connection to a WLAN access and transmission of a PDU of the application via non-3GPP access outside of a PDU session becomes available / unavailable;

[0378] ▶ g) The allowed NSSAI, the partially allowed NSSA or the configured NSSAI is changed;

[0379] ▶ h) The LADN information or the extended LADN information is changed;

[0380] ▶ i) The UE NAS layer indicates that back-off timer T3396, T3584 or T3585 (see 3GPP　TS　24.501

[0011] clause　6.2.7 and clause　6.2.8) is stopped or expired;

[0381] ▶ j) The UE NAS layer indicates the successful change of the PLMN; or

[0382] ▶ k) The UE NAS layer indicates that current TAI is in the list of TAs for which the S-NSSAI is allowed (see 3GPP　TS　24.501

[0011] clause　4.6.3.6).

[0383] In an embodiment, the UE (102) considers precedence of URSP rule from both the UE-1 (102A) and the UE-2 (102B). The URSP rule matched in the USIM / UE-1 (102A) have precedence value 1 and the USIM / UE-2 (102B) have precedence value 2, then the UE (102) will associate application X data on the USIM / UE-1 (102A).

[0384] In another embodiment, the NF indicate combined URSP for the UE-1 (102A) and the UE-2 (102B). The UE-1 (102A) and the UE-2 (102B) use the policy for the URSP evaluation. The NF can update URSP policy on any of the UE (102) (either the UE-1 (102A) or the UE-2 (102B)) in the registration update procedure of UE configuration update command. Additionally, the NF can give VPS URSP policy. VPS URSP policy can be combined policy or specific to the one of the UE(s)

[0385] Case 1: if VPS URSP is combined policy. If it is received on the PLMN-1 on the UE-1 (102A), the UE-2 (102B) also consider the VPS URSP is for the PLMN-1. The UE-1 (102A) and the UE-2 (102B) update (add, delete) their VPS URSP for the PLMN-1.

[0386] Case 2: if the VPS URSP policy is not combined URSP policy (i.e. it is specific to the UE (102)). The UE (102) updates the VPS URSP where it is receive. I.e. if the VPS policy is received on the UE-1 (102A) then corresponding VPS policy is updated in the UE (102). The NF (e.g. AMF (104) / PCF) indicate the URSP policy is combined to specific to the UE (102). The NF (e.g. AMF (104) / PCF) indicate the URSP policy is specific to the UE (102). If any of the UE (102) has the VPS URSP rule for the registered PLMN for e.g. the UE-1 (102A) is registered on PLMN-1 and have the VPS URSP for the PLMN-1, then the UE-1 (102A) will use the VPS URSP as below)

[0387] The UE (102) shall evaluate URSP rules, if available, in accordance with the following order until a matching URSP rule is found:

[0388] 1) If the UE-1 (102A) is registered and the RPLMN is a VPLMN, non-default URSP rules in the VPS URSP of the RPLMN;

[0389] 2) If the UE-1 (102A) is registered and the RPLMN is a VPLMN, non-default URSP rules in the VPS URSP of the equivalent PLMN;

[0390] 3) Non-default URSP rules in the PG URSP;

[0391] 4) The UE-1 (102A) local configuration for the application or the PIN;

[0392] 5) If the UE-1 (102A) is registered and the RPLMN is a VPLMN, default URSP rule in the VPS URSP of the RPLMN;

[0393] 6) If the UE-1 (102A) is and the RPLMN is a VPLMN, default URSP rules in the VPS URSP of the equivalent PLMN of the RPLMN and

[0394] 7) Default URSP rule in the PG.

[0395] In an embodiment, the network function indicate type of URSP policy and its association with the UE (102) / Stack.

[0396] Solution A1) NF (e.g. PCF) sends URSP policies independently on each UE (102) / SUPI / USIM (i.e. the UE-1 (102A) and the UE-2 (102B) which form the DualSteer UE will receive URSP associated with the UE-1 (102A) and the UE-2 (102B) separately). In this case, when application X is opened, the UE (102) will evaluate URSP as follows.

[0397] - evaluate the UE-1 (102A) or the UE-2 (102B) URSP policy (the UE (102) may determine whether to evaluate the UE-1 (102A) or the UE-2 (102B) can be based on the dualSteering policy received from the network or based on the service availability (e.g. the UE (102) select URSP associated with the UE-2 (102B) when the UE-2 (102B) is in service and the UE-1 (102A) is out of service). If TD matches with non-default rule, the UE (102) establishes PDU session with the RSD associated with the matched TD.

[0398] - If none of the URSP is matched with the non-default URSP rules of the UE (102) (e.g. the UE-1 (102A)) then the UE (102) check URSP of the UE-2 (102B)

[0399] - If non-default URSP rules are matched, the UE (102) will establish PDU session with the matched rule.

[0400] - If non-default TD is not matched in either the UE-1 (102A) or the UE-2 (102B) URSP, the UE (102) can use the implementation specific URSP available in the UE (102) (either the UE-1 (102A) or the UE-2 (102B) if available). If PDU session is not successful, the UE (102) uses default rule of the UE-1 (102A) or the UE-2 (102B) where it is available. If default rule is available in both the URSP, the UE (102) can select one based on UE implementation or DualSteer policies

[0401] In an embodiment, additionally the UE (102) evaluates URSP-1 and URSP-2 of the UE-1 (102A) and the UE (102), and if there is matched TD in non-default URSP rule, the UE (102) assume the session can be supported as DualSteer. The UE (102) indicates the e.g. DualSteer when establishing PDU session establishment.

[0402] In an embodiment, additionally, NF (e.g. PCF or the AMF (104)), indicate that the URSP policy is for the UE (102) where policy is being received.

[0403] In an embodiment, in the URSP policy, NF (e.g. PCF or the AMF (104)) indicates that particular URSP policy is of DualSteer (e.g. in the TD or RDS it can specify). If such information is available, then the UE (102) will indicate DualSteer in the PDU session establishment request if triggered because of association of URSP policy having the DualSteer Support indication.

[0404] Solution A2) NF (e.g. PCF) sends combined polices (NF send common URSP policies for the UE-1 (102A) and the UE-2 (102B) that forms the DualSteer UE) for both the dualSteeting UE together. The NF indicate in the URSP policy if it is for the UE-1 (102A) or the UE-2 (102B) or combined. If application x opens and matched the policy with the UE (102) (e.g. the UE-1 (102A)), then the PDU session is established only on the UE-1 (102A) and application is associated with the PDU session. If application X match with common URSP policy, the UE will establish PDU session on the UE-1 (102A) and / or the UE-2 (102B).

[0405] In an embodiment, if the UE-1 (102A) and the UE-2 (102B) are on the different PLMNs and there is VPS URSP policy for the UE (102) for the current PLMN, the UE (102) will use the VPS policy. If the UE-1 (102A) and the UE-2 (102B) are on the same PLMNs and VPS policy is available and common, then UE (102) will the same URSP rule on both the UEs.

[0406] In an embodiment, the UE-1 (102A) is registered on PLMN-1 and the UE-2 (102B) is registered on PLMN-2 and the UE-1 (102A) and the UE-2 (102B) have the combined URSP policy (VPS policy in the UE-1 (102A) is not available for PLMN-1 and VPS policy for the PLMN-2 is not available in UE-2 (102B)). In this case, when application X open, the UE (102) use the combined policy for the PDU session establishment.

[0407] In an embodiment, the UE-1 (102A) is registered on PLMN-1 and the UE-2 (102B) is registered on PLMN-2 and the UE-1 (102A) and the UE-2 (102B) have the combined URSP policy and VPS policy for the PLMN-1 is available for the UE-1 (102A) or combined VPS policy for the PLMN-1. In this case, the UE-1 (102A) will use the VPS policy for the PDU session establishment and the UE-2 (102B) use combined URSP.

[0408] In an embodiment, the URSP re-evaluation is done if there is change in VPS URSP on the UE (102) or the PDU session establishment or release in the UE (102), the URSP re-evaluation shall be done on the UE (102) to identify best rule.

[0409] Figs. 12A-C is a flow diagram that illustrates a method for handling a URSP for dual steering UE in a communication system according to an embodiment as disclosed herein. The method includes steps (1202-1246). Each step is explained in further detail below.

[0410] At step (1202), the UE (102) registers the first SIM / UE-1 (102A) associated with the UE (102) with the first network apparatus (302). This connection facilitates communication with the first network apparatus (302), thereby enabling the UE-1 (102A) to access network services and resources effectively.

[0411] At step (1204), the UE (102) sends a registration request message to the first network apparatus (302). The UE (102) indicates the User Plane Selection Identifier (UPSI) associated with the UE-1 (102A) in the registration request message. The UPSI helps in selecting an appropriate user plane function based on policies, operator preferences, or specific user requirements.

[0412] At step (1206), the UE (102) receives a registration accept message in response to the registration request message. The registration accept message includes the common URSP policy or the separate URSP policies. The common URSP policy refers to a single URSP policy applicable to both the UE-1 (102A) and the UE-2 (102B). It ensures uniform traffic handling for multiple users. The separate URSP policies correspond to different URSP policies assigned based on individual users or groups. The common URSP policy is used for uniform traffic handling and the separate URSP policies provide enhanced routing per user / group for better or improved customization. At step (1208), the UE (102) updates the common URSP policy or the separate URSP policies at the UE-1 (102A).

[0413] At step (1210), the UE (102) registers the second SIM / UE-2 (102B) associated with the UE (102) with the second network apparatus (402). This connection facilitates communication with the second network apparatus (402), thereby enabling the UE-2 (102B) to access network services and resources effectively.

[0414] At step (1212), the UE (102) sends a registration request message to the second network apparatus (402). The UE (102) indicates the UPSI associated with the UE-2 (102B) in the registration request message. The UPSI helps in selecting an appropriate user plane function based on policies, operator preferences, or specific user requirements.

[0415] At step (1214), the UE (102) receives a registration accept message in response to the registration request message. The registration accept message includes the common URSP policy or the separate URSP policies. The common URSP policy refers to a single URSP policy applicable to both the UE-1 (102A) and the UE-2 (102B). It ensures uniform traffic handling for multiple users. The separate URSP policies correspond to different URSP policies assigned based on individual users or groups. The common URSP policy is used for uniform traffic handling and the separate URSP policies provide enhanced routing per user / group for better or improved customization. At step (1216), the UE (102) updates the common URSP policy or the separate URSP policies at the UE-2 (102B).

[0416] At step (1218), the UE (102) determines whether it is configured with the common URSP policy applicable to both the first SIM and the second SIM, or whether it is configured with separate URSP policies for the first SIM and the second SIM. This assessment is essential for ensuring optimal network performance and resource allocation across the different SIMs of the UE (102).

[0417] At step (1220), the UE (102) selects one of the first SIM or the second SIM based on a first additional information provided in the common URSP policy for application data handling. This is selected when the UE (102) is configured with the common URSP policy for the first SIM and the second SIM, as determined in step (1218).

[0418] At step (1222), the UE (102) determines whether a dual steer PDU session is established between the UE (102) and the first network apparatus (302) via the first SIM or between the UE (102) and the second network apparatus (402) via the second SIM based on the common URSP policy. The dual steer PDU session refers to a single PDU session that enables traffic to be simultaneously routed through both the first network apparatus (302) and the second network apparatus (402). This enables seamless data flow and improves network performance by leveraging both the first network apparatus (302) and the second network apparatus (402). The common URSP policy indicates whether the dual steer PDU session is supported for the common URSP policy and includes one or more attributes. The one or more attributes include at least one of a single network slice selection assistance information (S-NSSAI) and a data network name (DNN). These attributes are essential for ensuring that the dual steer PDU session operates effectively and meets the necessary requirements for connectivity and service delivery.

[0419] At step (1224), the UE (102) determines it has the common URSP policy for the DNN and the S-NSSAI for the application data handling. If yes, then at step (1226), the UE (102) selects at least one of the first SIM to establish a PDU session between the UE (102) and the first network apparatus (302), and the second SIM to establish the PDU session between the UE (102) and the second network apparatus (402). If no, then at step (1228), the UE (102) selects only the first SIM to establish the PDU session between the UE (102) and the first network apparatus (302), when the UE (102) does not have the common URSP policy for the DNN and the S-NSSAI for the application data handling

[0420] At step (1230), the UE (102) determines one of the first SIM and the second SIM to be used for application data handling based on the separate URSP policies, and a second additional information preconfigured at the UE (102). This is determined when the UE (102) is configured with the separate URSP policies for the first SIM and the second SIM, as determined in step (1218).

[0421] At step (1232), the UE (102) transmits a first 5GMM request message to the first network apparatus (302). The first registration request message comprises a capability of the first SIM of the UE (102) set as dual steer capable. For instance, the first 5GMM request message is an uplink non-access stratum (UL NAS) transport message.

[0422] At step (1234), the UE (102) receives a first 5GMM response message from the first network apparatus (302) when a UCU procedure occurs. The UCU procedure refers to a signaling procedure that allows the UE (102) to inform the first network apparatus (302) about changes in its configuration or capabilities. The first registration accept message includes a first URSP policy based on subscription details associated with the first SIM of the UE (102).

[0423] At step (1236), the UE (102) transmits a second 5GMM request message to the second network apparatus (402). The second registration request message includes a capability of the second SIM of the UE (102) set as dual steer capable. For instance, the second 5GMM request message is an UL NAS transport message.

[0424] At step (1238), the UE (102) receives a second 5GMM response message from the second network apparatus (402) when the UCU procedure occurs. The UCU procedure refers to a signaling procedure that allows the UE (102) to inform the second network apparatus (402) about changes in its configuration or capabilities. The second registration accept message includes a second URSP policy based on subscription details associated with the second SIM of the UE (102).

[0425] At step (1240), the UE (102) performs an evaluation of the first URSP policy received corresponding to the first SIM of the UE (102) and the second URSP policy received corresponding to the second SIM of the UE (102). This re-evaluation is performed to determine if a change in the application handling or a PDU session is needed. This evaluation is done based on the first URSP policy corresponding to the first SIM of the UE (102) and the second URSP policy received corresponding to the second SIM of the UE (102).

[0426] At step (1242), the UE (102) determines whether to evaluate the first URSP policy and the second URSP policy based on the common URSP policy or the separate URSP policies received from the first network apparatus (302) and the second network apparatus (402), and a service availability of the first SIM and the second SIM. The service availability refers to an ability of the first SIM and the second SIM to access and use network services based on its provisioning, network conditions, and operator policies. It determines whether the first SIM or the second SIM can successfully register, authenticate, and utilize mobile services.

[0427] At step (1244), the UE (102) selects the second URSP policy associated with the second SIM of the UE (102) for evaluation when the second SIM is in service and the first SIM is out of service. Else, at step (1246), the UE (102) selects the first URSP policy associated with the first SIM of the UE (102) for evaluation when the first SIM is in service and the second SIM is out of service. Based on these selections, the PDU session is duly established between the UE (102) and the first network apparatus (302) via the first SIM and the UE (102) and the second network apparatus (402) via the second SIM.

[0428] Fig. 13 is a flow diagram that illustrates a method for determining the common URSP policy or separate URSP policies associated with the UE-1 (102A) / first SIM of the UE (102) according to an embodiment as disclosed herein. The method includes steps (1302-1308). Each step is explained in further detail below.

[0429] At step (1302), the first network apparatus (302) receives a registration request message from the first SIM of the UE (102) via a Public Land Mobile Network-1 (PLMN-1). The registration request message includes the UPSI associated with the first SIM. The PLMN refers to a mobile network operated by a specific carrier within a defined geographic area of the first SIM. The PLMN-1 can provide mobile services such as voice, SMS, and data to its subscribed users.

[0430] At step (1304), the first network apparatus (302) obtains the common URSP policy or separate URSP policies associated with the first SIM of the UE (102). This is obtained upon receiving the registration request message. At step (1306), the first network apparatus (302) generates a registration accept message that includes the common URSP policy or separate URSP policies obtained. At step (1308), the first network apparatus (302) transmits the registration accept message to the first SIM of the UE (102).

[0431] Fig. 14 is a flow diagram that illustrates a method for determining the common URSP policy or separate URSP policies associated with the UE-2 (102B) / second SIM of the UE (102) according to an embodiment as disclosed herein. The method includes steps (1402-1408). Each step is explained in further detail below.

[0432] At step (1402), the second network apparatus (402) receives a registration request message from the second SIM of the UE (102) via the PLMN-2. The registration request message includes the UPSI associated with the second SIM. The PLMN denotes a mobile network managed by a particular carrier within a designated geographic region associated with the second SIM. The PLMN can provide mobile services such as voice, SMS, and data to its subscribed users.

[0433] At step (1404), the second network apparatus (402) obtains the common URSP policy or separate URSP policies associated with the second SIM of the UE (102). This is obtained upon receiving the registration request message. At step (1406), the second network apparatus (402) generates a registration accept message that includes the common URSP policy or separate URSP policies obtained. At step (1408), the second network apparatus (402) transmits the registration accept message to the second SIM of the UE (102).

[0434] 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 handling a user equipment (UE) route selection policy (URSP) for dual steering UE in a communication system, comprising:registering, by the UE (102), a first SIM of the UE (102) with a first network apparatus (302);registering, by the UE (102), a second SIM of the UE (102) with a second network apparatus (402);determining, by the UE (102), whether the UE (102) is configured with a common URSP policy applicable to both the first SIM and the second SIM, or the UE (102) is configured with separate URSP policies for the first SIM and the second SIM; andperforming, by the UE (102), one of:selecting, by the UE (102), one of the first SIM or the second SIM based on a first additional information provided in the common URSP policy for application data handling, when the UE (102) is configured with the common URSP policy for the first SIM and the second SIM; anddetermining, by the UE (102), one of the first SIM and the second SIM to be used for application data handling based on the separate URSP policies, and a second additional information preconfigured at the UE (102).2.The method as claimed in claim 1, wherein registering, by the UE (102), the first SIM of the UE (102) with the first network apparatus (302) comprises:sending, by the UE (102), a registration request message to the first network apparatus (302), wherein the UE (102) indicates a User Plane Selection Identifier (UPSI) associated with the first SIM in the registration request message;receiving, by the UE (102), a registration accept message in response to the registration request message, wherein the registration accept message comprises the common URSP policy or the separate URSP policies, andupdating, by the UE (102), the common URSP policy or the separate URSP policies.3.The method as claimed in claim 1, wherein registering, by the UE (102), the second SIM of the UE (102) with the second network apparatus (402) comprises:sending, by the UE (102), a registration request message to the second network apparatus (402), wherein the UE (102) indicates a UPSI associated with the second SIM in the registration request message;receiving, by the UE (102), a registration accept message in response to the registration request message, wherein the registration accept message comprises the common URSP policy or the separate URSP policies, andupdating, by the UE (102), the common URSP policy or the separate URSP policies,wherein selecting, by the UE (102), one of the first SIM or the second SIM based on the first additional information provided in the common URSP policy for the application data handling comprises:determining, by the UE (102), whether a dual steer PDU session is established between the UE (102) and the first network apparatus (302) via the first SIM or between the UE (102) and the second network apparatus (402) via the second SIM based on the common URSP policy, wherein the common URSP policy indicates whether the dual steer PDU session is supported for the common URSP policy and includes one or more attributes, and wherein the one or more attributes comprise at least one of a single network slice selection assistance information (S-NSSAI) and a data network name (DNN);determining, by the UE (102), whether the UE (102) has the common URSP policy for the DNN and the S-NSSAI for the application data handling; andperforming, by the UE (102), one of:selecting, by the UE (102), at least one of the first SIM to establish a PDU session between the UE (102) and the first network apparatus (302), and the second SIM to establish the PDU session between the UE (102) and the second network apparatus (402), when the UE (102) has the common URSP policy for the DNN and the S-NSSAI for the application data handling; andselecting, by the UE (102), only the first SIM to establish the PDU session between the UE (102) and the first network apparatus (302), when the UE (102) does not have the common URSP policy for the DNN and the S-NSSAI for the application data handling.4.The method as claimed in claim 1, wherein the common URSP policy is generated via at least one of a traffic descriptor (TD) and a route selection descriptor (RSD).5.The method as claimed in claim 1, wherein determining, by the UE (102), whether the UE (102) is configured with the common URSP policy applicable to both the first SIM and the second SIM comprises:providing, by the UE (102), a UPSI of the common URSP policy during the registration of the first SIM and the second SIM, when the common URSP policy is applicable to both the first SIM and the second SIM.6.The method as claimed in claim 1, wherein determining, by the UE (102), one of the first SIM and the second SIM to be used for application data handling based on the separate URSP policies, and the second additional information preconfigured at the UE (102) comprises:transmitting, by the UE (102), a first 5GMM request message to the first network apparatus (302), wherein the first registration request message comprises a capability of the first SIM of the UE (102) set as dual steer capable;receiving, by the UE (102), a first 5GMM response message from the first network apparatus (302) when a UE configuration update (UCU) procedure occurs, wherein the first registration accept message comprises a first URSP policy based on subscription details associated with the first SIM of the UE (102);transmitting, by the UE (102), a second 5GMM request message to the second network apparatus (402), wherein the second registration network (402) comprises a capability of the second SIM of the UE (102) set as dual steer capable;receiving, by the UE (102), a second 5GMM response message from the second network apparatus (402) when the UCU procedure occurs, wherein the second registration accept message comprises a second URSP policy based on subscription details associated with the second SIM of the UE (102); andperforming, by the UE (102), an evaluation of the first URSP policy received corresponding to the first SIM of the UE (102) and the second URSP policy received corresponding to the second SIM of the UE (102) to determine if a change in the application handling or a PDU session is needed, wherein the evaluation is done based on the first URSP policy corresponding to the first SIM of the UE (102) and the second URSP policy received corresponding to the second SIM of the UE (102).7.The method as claimed in claim 6, wherein the first　5GMM message includes a registration request or an uplink non-access stratum (UL NAS) transport message, and wherein the second　5GMM message includes a registration request or the UL NAS transport message.8.The method as claimed in claim 6, wherein performing, by the UE (102), the evaluation of the first URSP policy received corresponding to the first SIM of the UE (102) and the second URSP policy received corresponding to the second of the UE (102) comprises:determining, by the UE (102), whether to evaluate the first URSP policy and the second URSP policy based on a common URSP policy or separate URSP policies received from the first network apparatus (302) and the second network apparatus (402), and a service availability of the first SIM and the second SIM; andperforming, by the UE (102), one of:selecting, by the UE (102), the second URSP policy associated with the second SIM of the UE (102) for evaluation when the second SIM is in service and the first SIM is out of service; andselecting, by the UE (102), the first URSP policy associated with the first SIM of the UE (102) for evaluation when the first SIM is in service and the second SIM is out of service,establishing, by the UE (102), a PDU session between the UE (102) and the first network apparatus (302) via the first SIM upon evaluation of the first URSP policy, and between the UE (102) and the second network apparatus (402) via the second SIM upon evaluation of the second URSP policy,wherein the evaluation of the first URSP policy and the second URSP policy includes dual steer scenarios that comprise at least one of an out of specification (OOS) on the first network apparatus (302) and the second network apparatus (402), an inter-system change of the first network apparatus (302) and the second network apparatus (402), and multi-mode (MM) or single mode (SM) related rejections.9.The method as claimed in claim 8, comprising:determining, by the UE (102), whether a NAS layer of the UE (102) indicates that an existing PDU session used for routing traffic of the application or the PIN based on the first URSP policy or the second URSP policy is released; andperforming, by the UE (102), the evaluation of the first URSP policy and the second URSP policy when the existing PDU session is released.10.A method for handling a URSP for dual steering UE in a communication system, comprising:receiving, by a first network apparatus (302), a registration request message from a first SIM of a UE (102) via a Public Land Mobile Network-1 (PLMN-1), wherein the registration request message comprises a UPSI associated with the first SIM;obtaining, by the first network apparatus (302), a common URSP policy or separate URSP policies associated with the first SIM of the UE (102);generating, by the first network apparatus (302), a registration accept message that comprises the common URSP policy or separate URSP policies obtained; andtransmitting, by the first network apparatus (302), the registration accept message to the first SIM of the UE.11.The method as claimed in claim 10, wherein the common URSP policy indicates whether a dual steer PDU session is supported for the common URSP policy, andwherein the registration request message is a UL NAS transport message.12.A method for handling a URSP for dual steering UE in a communication system, comprising:receiving, by a second network apparatus (402), a registration request message from a second SIM of a UE (102) via a PLMN-2, wherein the registration request message comprises a UPSI associated with the second SIM;obtaining, by the second network apparatus (402), a common URSP policy or separate URSP policies associated with the second SIM of the UE (102);generating, by the second network apparatus (402), a registration accept message that comprises the common URSP policy or separate URSP policies obtained; andtransmitting, by the second network apparatus (402), the registration accept message to the second SIM of the UE (102).13.A UE (102) for handling a URSP for dual steering in a communication system, comprising:a first memory (112);a first processor (110); anda URSP handling controller (116) communicatively coupled to the first memory (112) and the first processor (110), wherein the URSP handling controller (116):receives registers a first SIM of the UE (102) with a first network apparatus (302);registers a second SIM of the UE (102) with a second network apparatus (402);determines whether the UE (102) is configured with a common URSP policy applicable to both the first SIM and the second SIM, or the UE (102) is configured with separate URSP policies for the first SIM and the second SIM;performs one of:selects one of the first SIM or the second SIM based on a first additional information provided in the common URSP policy for application data handling, when the UE (102) is configured with the common URSP policy for the first SIM and the second SIM; anddetermines one of the first SIM and the second SIM to be used for application data handling based on the separate URSP policies, and a second additional information preconfigured at the UE (102).14.A first network apparatus (302) for handling a URSP for dual steering UE in a communication system, comprising:a second memory (306);a second processor (304); anda URSP policy obtaining controller (310) communicatively coupled to the second memory (306) and the second processor (304), wherein the URSP policy obtaining controller (310):receives a registration request message from a first SIM of a UE (102) via a PLMN-1, wherein the registration request message comprises a UPSI associated with the first SIM;obtains a common URSP policy or separate URSP policies associated with the first SIM of the UE (102);generates a registration accept message that comprises the common URSP policy or separate URSP policies obtained; andtransmits the registration accept message to the first SIM of the UE (102).15.A second network apparatus (402) for handling a URSP for dual steering UE in a communication system, comprising:a third memory (406);a third processor (404); anda URSP policy determination controller (410) communicatively coupled to the third memory (406) and the third processor (404), wherein the URSP policy determination controller (410):receives a registration request message from a second SIM of a UE (102) via a PLMN-2, wherein the registration request message comprises a UPSI associated with the second SIM;obtains a common URSP policy or separate URSP policies associated with the second SIM of the UE (102);generates a registration accept message that comprises the common URSP policy or separate URSP policies obtained; andtransmits the registration accept message to the second SIM of the UE (102).

Images