Method and apparatus for enabling a UE to identify dual steering in a wireless communication system

Abstract

The disclosure relates to a fifth generation (5G) or sixth generation (6G) communication system for supporting higher data rates. Embodiments herein disclose methods and systems for enabling a UE to identify that it can act as a DualSteer device. Embodiments herein disclose methods and systems for enabling a network to identify if a device is a DualSteer device. Embodiments herein disclose methods and systems for enabling the UE to identify if the Network supports DualSteering (traffic steering, splitting, and switching). Embodiments herein disclose methods and systems for indicating to a UE that two SUPIs belong to a same subscription profile.

Description

METHOD AND APPARATUS FOR ENABLING A UE TO IDENTIFY DUAL STEERING IN A WIRELESS COMMUNICATION SYSTEM

[0001] This application is based on and derives the benefit of Indian Provisional Application IN 202441000294,　the contents of which are incorporated herein by reference.

[0002] Embodiments disclosed herein relate to wireless communication networks, and more particularly to identifying DualSteering by a UE in wireless communication networks.

[0003] 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.

[0004] 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.

[0005] 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.

[0006] 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.

[0007] 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.

[0008] 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.

[0009] The present disclosure relates to wireless communication systems and, more specifically, the present disclosure relates to enable a UE to identify dual steering in a wireless communication system.

[0010] The principal object of embodiments herein is to disclose methods and systems for enabling a User Equipment (UE) (i.e., a DualSteering Device ) to identify that it can act as a DualSteer device.

[0011] Another object of embodiments herein is to disclose methods and systems for enabling a serving network to identify if a device is a DualSteer device.

[0012] Another object of embodiments herein is to disclose methods and systems for enabling the UE to identify if the Serving Network supports DualSteering (traffic steering, splitting, and switching).

[0013] Another object of embodiments herein is to disclose methods and systems for indicating to a UE that two SUPIs belong to a same subscription profile.

[0014] 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 at least one embodiment and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the spirit thereof, and the embodiments herein include all such modifications.

[0015] According to an embodiment of the disclosure, a wireless communication can be performed efficiently. Especially, enabling a UE to identify dual steering can be performed efficiently.

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

[0017] FIG. 1 depicts the UE indicating that it is capable of acting as a DualSteer device, according to embodiments as disclosed herein;

[0018] FIG. 2 depicts the UE indicating that it is capable of acting as a DualSteer device, according to embodiments as disclosed herein;

[0019] FIG. 3 depicts the UE indicating that it is capable of acting as a DualSteer device, according to embodiments as disclosed herein;

[0020] FIG. 4 depicts the UE indicating that it is capable of acting as a DualSteer device, according to embodiments as disclosed herein;

[0021] FIG. 5 depicts a RAN broadcasting that DualSteer is supported by the network, according to embodiments as disclosed herein;

[0022] FIG. 6 depicts the process for indicating to a UE that two SUPIs belong to a same subscription profile, according to embodiments as disclosed herein;

[0023] FIG. 7 is a flowchart depicting the process of enabling a UE to determine if the UE can act as a DualSteering device, according to embodiments as disclosed herein; and

[0024] FIG. 8 depicts a HPLMN in a serving network, according to embodiments as disclosed herein.

[0025] Requirements as discussed below cover scenarios and functionalities for supporting enhanced traffic steering and switching of a DualSteer device's user data (for different services) across two 3GPP access networks, assuming the ability to differentiate the two connections for the same device and minimize impacts to CN, O&M or IT systems.

[0026] Target scenarios cover two 3GPP access networks belonging to the same PLMN, or between two different PLMNs, or between one PLMN and one PLMN-integrated NPN, over the same or different RATs, which can use terrestrial and / or satellite access (including the case of two different satellite orbits). Scenarios may also include traffic steering and / or switching across LTE / EPC and NR / 5GC, with anchoring in 5GC.

[0027] Traffic policies are intended to be in full control of the home network operator.

[0028] The requirements below can apply to different DualSteer device types (e.g., smartphones, IoT, UAV, VSAT devices) (i.e., a User Equipment (UE)). For the requirements below, the following applies:

[0029] - a subscriber with two subscriptions / SUPIs, sharing one subscription profile from the same operator; and

[0030] - for simultaneous transmission over two networks, a DualSteer device is assumed to include two separate UEs.

[0031] Subject to HPLMN policy and network control, the 5G system shall be able to support mechanisms to enable traffic steering and / or switching of a DualSteer device's user data (for different services) across two 3GPP access networks belonging to the same PLMN (either HPLMN or VPLMN), assuming data anchoring in the HPLMN and non-simultaneous transmission over the two networks.

[0032] Subject to HPLMN policy and network control, the 5G system may be able to support mechanisms to enable traffic steering and / or switching with simultaneous transmission of a DualSteer device's user data (for different services) across two 3GPP access networks belonging to the same PLMN (either HPLMN or VPLMN), assuming data anchoring in the HPLMN.

[0033] Subject to HPLMN policy and network control, the 5G system shall be able to support mechanisms to enable traffic steering and / or switching of a DualSteer device's user data (for different services) across two 3GPP access networks belonging to two PLMNs, assuming a business / roaming agreement between PLMN operators (if different), data anchoring in the HPLMN and non-simultaneous transmission over the two networks.

[0034] Subject to HPLMN policy and network control, the 5G system may be able to support mechanisms to enable traffic steering and / or switching with simultaneous transmission of a DualSteer device's user data (for different services) across two 3GPP access networks belonging to two PLMNs, assuming a business / roaming agreement between PLMN operators (if different) and HPLMN data anchoring.

[0035] NOTE 1: Inter-PLMN requirements can apply also to PLMN-NPN scenarios assuming a PLMN-integrated NPN (NPN hosted by a PLMN or offered as a slice of a PLMN).

[0036] For traffic steering and / or switching of user data across two 3GPP access networks, the 5G system shall be able to allow a HPLMN to provide policies and criteria for a DualSteer device to connect to an additional PLMN / NPN, or an additional RAT within the same PLMN.

[0037] NOTE 2: The above requirements assume configuration of traffic policies, under HPLMN control or negotiated between the HPLMN and other network operators, considering e.g., user subscription, application / traffic type, service preference, QoS requirements, location, time, UE capabilities, mobility, and connectivity conditions.

[0038] The following are examples of NAS messages: REGISTRATION REQUEST message; DEREGISTRATION REQUEST message; SERVICE REQUEST message; CONTROL PLANE SERVICE REQUEST; IDENTITY REQUEST; AUTHENTICATION REQUEST; AUTHENTICATION RESULT; AUTHENTICATION REJECT; REGISTRATION REJECT; REGISTRATION ACCEPT; DEREGISTRATION ACCEPT; SERVICE REJECT; SERVICE ACCEPT; UE CONFIGURATION UPDATE command; UE PARAMETERS UPDATE command, and so on.

[0039] Current solutions disclose a DualSteer device that can support traffic steering and switching of user data (for different services) across two 3GPP access networks. However, there is no mention of

[0040] - how a UE identifies itself as DualSteer device; For example, the UE may have 2 or more 2 SIMs. Can the UE perform Dualsteering between the 2 SIMs and which of the 2 SIMs can be used by the UE to perform dual steering;

[0041] - how a serving network can identify a device whether it is a DualSteer device; and

[0042] - how the UE can identify if the serving network supports DualSteering for traffic steering and switching purpose.

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

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

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

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

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

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

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

[0050] The embodiments herein achieve methods and systems for enabling a UE to identify that it can act as a DualSteer device. Referring now to the drawings, and more particularly to FIGS. 1 through 8, where similar reference characters denote corresponding features consistently throughout the figures, there are shown embodiments.

[0051] The following definitions and abbreviations have been referred to herein:

[0052] DualSteer device: A device supporting traffic steering, traffic splitting and traffic 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.

[0053] Traffic steering: 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).

[0054] Traffic switching: 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).

[0055] Traffic splitting: A procedure that splits the traffic between one access network and 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 (with simultaneous data over the two networks).

[0056] The term 'Dualsteering' implies that a UE can perform at least one of traffic steering, traffic splitting and traffic switching of user data (for different or same services) across two or more 3GPP access networks.

[0057] The term area / location / geographical area are used in this embodiment to refer to any of cell / cell ID, TAC / TAI, PLMN, MCC / MNC, Latitude / longitude, CAG cell or any geographical location / coordinates.

[0058] The terms “act as”, “allowed to”, “behave”, or “support” are used interchangeably herein, and may indicate to the UE that it can act as a Dualsteer device which implies that the UE can behave as a device supporting traffic steering and switching of user data (for different services) across two 3GPP access networks. In an embodiment herein, the Dualsteer device can be a single UE, in case of non-simultaneous data transmission over the two networks. In an embodiment herein, the Dualsteer device can be two separate UEs in case of simultaneous data transmission over the two networks. Embodiments herein use the term UE to also refer to a Dualsteer Device.

[0059] UE: User equipment

[0060] PLMN: Public Land Mobile Network

[0061] IE: Information Element

[0062] AMF: Access and Mobility Management Function

[0063] UPU: UE Parameter Update

[0064] UCU: User Configuration Update

[0065] As depicted in FIG. 1, the UE 101 indicates that it is capable of being a DualSteer device; for example, in the existing or new IE in Registration Request / UL NAS transport or any other NAS message. The Serving Network 102 (i.e., VPLMN / HPLMN 102A) (hereinafter also referred to as a network) indicates its support of DualSteering or whether the UE 101 can act as DualSteer device or the UE 101 is subscribed and allowed to act as a DualSteer device in a registration accept message / User Configuration Update (UCU) message / DL NAS TRANSPORT message or any other NAS message.

[0066] As depicted in FIG. 2, consider that the UE 101 is registered on a PLMN. The UE 101 indicates its support of DualSteering for a Data Network Name (DNN) to a Session Management Function (SMF) 102B. Optionally, the UE 101 can also consider the S-NSSAI in a 5GSM message to the SMF 102B. For example, in a PDU Session request message, the UE 101 can indicate to the serving network 102 that it can support DualSteering over at least one of the DNN and S-NSSAI or both DNN and S-NSSAI. For this purpose, the UE 101 can include a new IE DualSteer Capability in a PDU Session request message to the SMF 102B.

[0067] Table 1 depicts an example PDU session establishment request.

[0068]

[0069] Table 1

[0070] The network 102 (i.e., the SMF 102B) indicates its support of DualSteering for a DNN+S-NSSAI combination (or at least one of the DNN and S-NSSAI) in a 5GSM message; for example, in a PDU Session Establishment Accept / PDU session modification / PDU session release / PDU session authentication, the network 102 can indicate to the UE 101 that it can support DualSteering over at least one of the DNN and S-NSSAI in one of the NAS message, or that the UE 101 is allowed to / act as a DualSteer device. For this purpose, the network 102 can include a new IE DualSteer Support in the 5GSM message; e.g. PDU Session Establishment Accept.

[0071] Table 2 depicts an example PDU Session Establishment Accept. It can be any of the messages sent to the UE; for example, in NAS message or using data path etc.

[0072]

[0073] Table 2

[0074] As depicted in FIG. 3, consider that the UE 101 is camped on a gNB 102C. The UE 101 indicates that it is a DualSteer device in an Access Stratum (AS) message to the gNB 102C. For example, the UE 101 indicates that it is a DualSteer device in RRC UE Capability Information. For this purpose, the UE 101 can include a new IE DualSteer capability in an AS message; for e.g., UE Capability Information. Table 3 depicts an example UE capability information message.

[0075]

[0076] Table 3

[0077] The UE 101 can be pre-configured in at least one Universal Subscriber Identity Module (USIM) (currently present in the UE), or a Mobile Equipment (ME) that the UE 101 can act as a DualSteer Device. In an embodiment herein, the UE 101 can use an indication of additional SUPI (or any identifier of any name) to identify that the UE 101 can act as a DualSteer device.

[0078] The SIM Efds / service contains information whether a SIM / ME / UE can support DualSteering or not. This can be updated via a SIM Over The Air (OTA) based on SIM subscription or UE parameter update procedure (UPU) or DL NAS TRANSPORT message; for e.g., using secure packet from the network 102 (HPLMN / VPLMN 102A) into the UE 101.

[0079] Values:

[0080] EFds = 0 (SIM does not support DualSteering)

[0081] EFds = 1 (SIM supports DualSteering)

[0082] The ME can locally store information on whether the UE 101 can / cannot support / act as a DualSteer device.

[0083] As depicted in FIG. 4, consider that the UE 101 is registered on a 5G network (i.e., the serving network 102). It can be indicated to the UE 101 that it can act as a DualSteer device using UE Parameter Update (UPU) Procedure. The network 102 can update the UE 101 that the UE 101 can act as a DualSteer device using a control plane solution via the UE registered AMF 102D. The Unified Data Management (UDM) 102E has information that a UE (SUPI) is subscribed to perform DualSteering. The network 102 can deliver protected UDM Update Data via NAS signalling and update the UE 101 regarding the same. In an example herein, the UDM 102E can include new UE parameters update data set type 'DualSteer update data' in a UPU Container to indicate DualSteering capability to the UE 102.

[0084] In step 401, the UDM 102E decides to perform UE Parameter Update and update the UE 101 as to whether the UE 101 is subscribed / unsubscribed for DualSteering or is the UE 101 allowed to act as / not allowed to act as a DualSteer device. In step 402, the UDM 102E notifies the UE registered AMF 102D of the changes of the information / indication (i.e., whether the UE 101 is subscribed / unsubscribed for DualSteering or is the UE 101 allowed to act as / not allowed to act as a DualSteer device) related to the UE 101 by invoking a signal. For example, the UDM 102E notifies the UE registered AMF 102D of the changes of the information / indication related to the UE 101 by invoking a Nudm_SDM_Notification service operation, wherein the Nudm_SDM_Notification service operation contains the UDM Update Data that needs to be delivered transparently to the UE 101 over NAS within the Access and Mobility Subscription data. If the AMF 102D determines that the UE 101 is not reachable, in step 403, the AMF 102D invokes the Nudm_SDM_Info service operation to the UDM 102E indicating that the transmission of UE Parameters Update data to the UE 101 is not successful. The UDM 102E considers the UE Parameters Update procedure as pending and subsequent steps 404 - 407 are skipped.

[0085] In step 404, the AMF 102D sends a DL NAS TRANSPORT message to the served UE 101. The AMF 102D includes the transparent container received from the UDM 102E in the DL NAS TRANSPORT message, wherein the transparent container includes the information / indication (i.e., whether the UE 101 is subscribed / unsubscribed for DualSteering or is the UE 101 allowed to act as / not allowed to act as a DualSteer device). On receiving the DL NAS TRANSPORT message, the UE stores the received information in one of the ME or USIM and decides whether it can act as a DualSteer device. If the UE 101 has verified that the UDM Update Data is provided by HPLMN, SNPN, or CH and the UDM 102E has requested the UE 101 to send an ack to the UDM, in step 405, the UE 101 sends an UL NAS TRANSPORT message to the serving AMF 102D with a transparent container including the UE acknowledgement. On the AMF 102D receiving an UL NAS TRANSPORT message with a transparent container carrying a UE acknowledgement from the UE 101, in step 406, the AMF 102D sends a Nudm_SDM_Info request message including the transparent container to the UDM 102E. If the UDM has requested the UE to re-register, in step 407, the UE 101 waits until it goes back to RRC_IDLE and initiates a Registration procedure (as defined in TS　24.501).

[0086] A broadcast from Random Access Network (RAN) 501 can indicate if DualSteer is supported by the network 102 (as depicted in FIG. 5). It is possible that RAN cells within the Network 102 can support DualSteering or may not support it, and a respective indication is provided to the UE 101 in one of the broadcast signals. For example, this can be indicated to the UE using a RRC broadcast message in one of the existing or new System Information Broadcast (SIBs); e.g. SIB-1, 2, 3, 18 or SIBX etc.

[0087] Per subscription, this can be configured at the UDM 102E or PCF (per UE) as to whether it is allowed to act as a DualSteer device and indicated to the UE 101 in at least one of the NAS message.

[0088] Per subscription (SUPI):

[0089] The UDM 102E can store information regarding whether a UE (SUPI) is allowed to act as DualSteer device or not. Embodiments herein disclose a field in Access and Mobility Subscription data in below Table.

[0090]

[0091] Table 4

[0092] Per subscription(SUPI) for each DNN in S-NSSAI level:

[0093] The UDM 102E can store information regarding whether a UE (SUPI) is allowed to act as DualSteer device or not. Embodiments herein disclose a field in Session Management Subscription data in Table 5.2.3.3.1-1: UE Subscription data types (TS23.502) (as depicted in table 5).

[0094]

[0095] Table 5

[0096] Consider that SUPI-1 and SUPI-2 are configured in a UE 101 which supports DualSteering. Embodiments herein disclose a mechanism to indicate / inform the UE 101 which of these two SUPI(s) belong to the same subscription profile; i.e., the UE 101 can act as a DualSteer device between these two SUPIs / USIM subscriptions. Optionally, SUPI-1 can be the primary SUPI and SUPI-2 can be the secondary SUPI or vice versa. The network 102 can indicate this combination of SUPI's (two or more) using a NAS message; for example, Configuration Update Command (as depicted in FIG. 6) or a registration accept message to the UE 101 or they are pre-configured in the ME or USIM. The UE 101 can be updated by the network 102 in any of the mechanisms using a control plane message or using a PDU session with a data path.

[0097] When the UE 101 is configured with such information, the UE 101 assumes that it is a DualSteer device and it can act as a DualSteer device. The example as depicted in table 6, states that 2 SUPIs or identifiers are indicated to the UE 101, but it can be any plurality of SUPIs / identifiers (i.e., more than 2) which belong to the same subscription profile.

[0098]

[0099] Table 6

[0100] In an embodiment herein, the capability / indicating to the UE that it can act as a DualSteer device / allowed to act / support of DualSteer indication (all methods discussed in this embodiment) are per registration area (TAI list), Location, geographical area, allowed Time configured in the UE 101 or in the network and indicated to the UE 101 in a NAS message (like registration accept, UE configuration update etc.); i.e., the UE 101 can act as a DualSteer device only in a given / configured / supported location (e.g., one or more cell(s), TAI(s), area(s) identified by latitude or longitude or co-ordinates, in a given CAG(s) etc.) or a time slot (e.g., between a configured start and end times (for example, 9 to 12 etc.), wherein the time slot can be indicated in a suitable manner (for example, start time and allowed duration, for the duration when the UE 101 is indicated that it can start acting as a DualSteer device in one of the AS or NAS message, and so on).

[0101] In an example scenario, consider that the UE 101 has moved out of the configured / supported / allowed area. The UE 101 will then again trigger the registration procedure or the NAS procedure and check in a received AS / NAS response message if the UE 101 is allowed to act as a DualSteer device.

[0102] In an example scenario, consider that the UE 101 is out of the allowed time slot. The UE 101 will then not act as a DualSteer device. The UE will act as a DualSteer device only in the allowed time slot. A UE Route Selection Policy (URSP) in the UE 101 can be configured with two DNNs or S-NSSAIs or two SUPIs that the UE 101 can use to act as a DualSteer device. If such a configuration is available in the UE 101, the UE 101 interprets that it can act as a DualSteer device.

[0103] In summary, whether the UE 101 can act as a DualSteer device can be configured as part of the URSP information in the UE or as part of any other possible configuration. The term SUPI is used in this embodiment, but it can be any identifier, or it can be with a different name which identifies to the UE that it can act as a DualSteer device and which identifiers that the UE 101 should use to distinctly identify a given connection.

[0104] When the UE 101 is configured with an indication with the DNN+S-NSSAI which are allowed to do DualSteer, then the UE 101 identifies that it can act as a DualSteer device. In an embodiment herein, the DNN+S-NSSAI combination can be of a type MA PDU session.

[0105] FIG. 7 is a flowchart depicting the process of enabling a UE to determine if the UE can act as a DualSteering device. In step 701, the serving network 102 (i.e., the HPLMN 102A) checks if the UE 101 can act as a DualSteering device. If the UE 101 can act as a DualSteering device, in step 702, the serving network 102 indicates that at least a first SUPI, and a second SUPI (which is currently being used by the UE 101) is authorized to act as a DualSteering device, to the UE 101. In an embodiment herein, the first SUPI, and the second SUPI belong to the same subscription profile. In an embodiment herein, the serving network 102 can also indicate the SUPI that is the primary SUPI of the DualSteering, and the SUPI that is the secondary SUPI of the DualSteering; i.e., one of the first SUPI, and the second SUPI is a primary SUPI of the DualSteering; and the other of the first SUPI, and the second SUPI is a secondary SUPI of the DualSteering. In an embodiment herein, the serving network 102 provides the indication to the UE 101 using one of a NAS message; a registration accept message; and pre-configured in at least one SIM in the UE 101 or it can be indicated using any mechanism to indicate to the UE (for example, using the data path). Further, in step 703, the serving network 102 stores that at least the first SUPI, and the second SUPI being used by the UE 101 is authorized to use DualSteering in at least one of the UDM 102E, and a PCF (per UE). The various actions in method 700 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 7 may be omitted.

[0106] Embodiments herein illustrate the HPLMN indicating the Dualsteer policy to the UE, but it may be obvious to a person of ordinary skill in the art that the Dualsteer policy can also be generated independently by the VPLMN and indicated to the UE.

[0107] The methods described in this embodiment are used by the UE to determine if it can act as a Dualsteer device. On the UE determining that it can act as a Dualsteer device, the UE can start performing Traffic steering or Traffic switching or Traffic splitting procedures between the two SIMs / SUPIs (also called as access network) on which it is allowed to do so. Optionally, only on the at least one of the DNN and S-NSSAI combination which are authorized for Dual steering purposes (i.e., for Traffic steering or Traffic switching or Traffic splitting).

[0108] FIG. 8 depicts a HPLMN in a serving network. The HPLMN 102A, as depicted, comprises a processor 801, a memory 802, and a transceiver 803.

[0109] The processor 801 can be at least one of a single processor, a plurality of processors, multiple homogeneous or heterogeneous cores, multiple Central Processing Units (CPUs) of different kinds, microcontrollers, special media, and other accelerators. The processor 801 may be an Application Processor (AP), 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).

[0110] In an embodiment herein, the transceiver 803 is configured to enable communication between the HPLMN 102A and at least one external entity (such as, but not limited to, other modules / components in the serving network 102, one or more UEs 101, and so on) through a network or cloud. The server may be configured or programmed to execute the instructions of the HPLMN 102A. The transceiver 803 through which the HPLMN 102A and the at least one external entity communicate may include wired and / or wireless communication medium compatible with one or more different communication protocols. The transceiver 803 may be configured for communication through a network. The network may comprise, but are not limited to, Global Positioning System (GPS), Global System for Mobile Communications (GSM), Local Area Network (LAN), Wireless Fidelity (Wi-Fi) compatibility, Bluetooth Low Energy (BLE), Near-field Communication (NFC), and so on. The wireless communication may further comprise one or more of Bluetooth (registered trademark), Zonal Intercommunication Global Standard (ZigBee) (registered trademark), short-range wireless communication such as Ultra-wideband (UWB), medium-range wireless communication such as Wi-Fi (registered trademark), or long-range wireless communication such as Third Generation (3G), Fourth Generation (4G), or Worldwide Interoperability for Microwave Access (WiMAX) (registered trademark), according to the usage environment.

[0111] In the embodiment shown herein, the memory 802 may comprise one or more volatile and non-volatile memory components that are capable of storing data and instructions to be executed. Examples of the memory 802can be, but are not limited to, NAND, embedded Multimedia Card (eMMC), Secure Digital (SD) cards, Universal Serial Bus (USB), Serial Advanced Technology Attachment (SATA), solid-state drive (SSD), and so on. The memory 802 may also include one or more computer-readable storage media. Examples of non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory 802 may, in some examples, be considered a non-transitory storage medium. The term “non-transitory” may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term “non-transitory” should not be interpreted to mean that the memory 802 is non-movable. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache).

[0112] The processor 801 can check if the UE 101 can act as a DualSteering device. If the UE 101 can act as a DualSteering device, the processor 801 can indicate that at least a first SUPI, and a second SUPI (which is currently being used by the UE 101) is authorized to use DualSteering, to the UE 101. In an embodiment herein, the first SUPI, and the second SUPI belong to the same subscription profile. In an embodiment herein, the processor 801 can also indicate the SUPI that is the primary SUPI of the DualSteering, and the SUPI that is the secondary SUPI of the DualSteering; i.e., one of the first SUPI, and the second SUPI is a primary SUPI of the DualSteering; and the other of the first SUPI, and the second SUPI is a secondary SUPI of the DualSteering. In an embodiment herein, the processor 801 can provide the indication to the UE 101 using one of a NAS message; a registration accept message; and pre-configured in at least one SIM in the UE 101. Further, the processor 801 can store that at least the first SUPI, and the second SUPI being used by the UE 101 is authorized to use DualSteering in at least one of the UDM 102E, and a PCF (per UE).

[0113] Although FIG. 8 shows various hardware components of the HPLMN 102A, but it is to be understood that other embodiments are not limited thereto. In other embodiments, the HPLMN 102A may include less or more components. Further, the labels or names of the components are used only for illustrative purposes and do not limit the scope of the invention. One or more components can be combined to perform the same or substantially similar function in the HPLMN 102A.

[0114] The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the network elements. The elements include blocks which can be at least one of a hardware device, or a combination of hardware device and software module.

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

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

Claims

1.A method (700) for enabling a User Equipment (UE) (101) to identify DualSteering, the method comprising:indicating (702), by a serving network (102), that at least a first Subscription Permanent Identifier (SUPI), and a second SUPI being used by a user equipment (UE) (101) is authorized to use DualSteering, to the UE (101).2.The method of claim 1, wherein the method comprises indicating, by the serving network (102), that at least the first SUPI, and the second SUPI being used by the UE (101) is authorized to use DualSteering, to the UE(101), using one of a NAS message; a registration accept message; and pre-configured in at least one Subscriber Identity Module (SIM) in the UE (101).3.The method of claim 1, wherein at least the first SUPI, and the second SUPI belong to same subscription profile.4.The method of claim 1, wherein the method comprises storing (703), by the serving network (102), that at least the first SUPI, and the second SUPI being used by the UE (101) is authorized to use DualSteering in at least one of a Unified Data Management (UDM), and a Policy Control Function (PCF).5.The method of claim 1, wherein one of the first SUPI, and the second SUPI is a primary SUPI of the DualSteering; and the other of the first SUPI, and the second SUPI is a secondary SUPI of the DualSteering.6.The method of claim 1, wherein the method comprises indicating, by the serving network (102), one or more Packet Data Units (PDUs) to be used in DualSteering using a (Data Network Name (DNN), Single - Network Slice Selection Assistance Information (S-NSSAI)) combination list.7.A Home Public Land Mobile Network　(HPLMN) (102A) in a serving network (102), the HPLMN (102A) comprising:a processor (801);a memory (802); anda transceiver (803),wherein the processor (801) is coupled with the memory (802), and the transceiver (803), and configured to:indicate that at least a first Subscription Permanent Identifier (SUPI), and a second SUPI being used by a User Equipment (UE) (101) is authorized to use DualSteering, to the UE (101).8.The HPLMN of claim 7, wherein the processor (801) is configured to indicate that at least the first SUPI, and the second SUPI being used by the UE (101) is authorized to use DualSteering, to the UE (101), using one of a NAS message; a registration accept message; and pre-configured in at least one Subscriber Identity Module (SIM) in the UE (101).9.The HPLMN of claim 7, wherein the processor (801) is configured to store that at least the first SUPI, and the second SUPI being used by the UE (101) is authorized to use DualSteering in at least one of a Unified Data Management (UDM), and a Policy Control Function (PCF).10.The HPLMN of claim 7, wherein one of the first SUPI, and the second SUPI is a primary SUPI of the DualSteering; and the other of the first SUPI, and the second SUPI is a secondary SUPI of the DualSteering.11.The HPLMN of claim 7, wherein the processor (801) is configured to indicate one or more Packet Data Units (PDUs) to be used in DualSteering using a (Data Network Name (DNN), Single - Network Slice Selection Assistance Information (S-NSSAI)) combination list.

Images