Patent Description:
The Third Generation Partnership Project (3GPP) has developed and is developing standards for Fourth Generation (<NUM>) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (<NUM>) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile wireless devices (WD), as well as communication between network nodes and between WDs.

In 3GPP, it has been described to isolate the usage of network slices by a wireless device where the wireless device is allocated different identities to use with sets of single-network slice selection assistance information, S-NSSAIs, S-NSSAIs, that may require isolation. For example, the wireless device may be allocated subscription permanent identifer1 (SUPI1)/generic public subscription identifier1 (GPSI1) for S-NSSAI1 and SUPI2/GPSI2 for S-NSSAI2 if S-NSSAI1 and S-NSSAI2 require isolation. The wireless device may have to register with the identity corresponding to the S-NSSAI that the wireless device wants to use. This helps ensure that the wireless device can never use the S-NSSAIs requiring isolation simultaneously.

To support the above, the wireless device is provisioned with a User Profile associated with a single subscription, but is also allocated an independent alias SUPI/ GPSI (s) for every set of S-NSSAIs that has be used independently. These additional alias SUPI(s), GPSIs and the compatible S-NSSAI(s) they are bound to can also be used to authenticate the wireless device if the S-NSSAI(s) require secondary authentication. Alias SUPIs have no subscription associated with them and are used for the purpose of slice switching between isolated sets using the registration procedure. Alias SUPIs are received at initial registration of the wireless device, in a registration accept response, and are considered configuration information by the wireless device. Further, in this multiple profiles concept a Unified Data Management (UDM) node is allowed to download multiple SUPIs where only one SUPI is associated with the subscription while, while the other SUPIs are considered as secondary SUPIs, or Alias SUPIs.

Hence, there are constraints on simultaneous use of the network slice, e.g., the wireless device cannot use one set of slices simultaneous with another set of slices due to the "isolation" requirement.

Document "<NPL> may be construed to disclose an update to solution #<NUM> (separate SUPI/GPSI per isolated set of S-NSSAIs) for KI #<NUM> (constraints on simultaneous use of the network slice). In this solution, the UE does not need to indicate its support to network for Associated-Identifiers since the solution uses existing Release <NUM> and <NUM> mechanisms for configured and Allowed S-NSSAI.

Document "<NPL> may be construed to disclose an analysis of solutions for KI #<NUM> and proposes conclusions. For instance, if the UE does not support the feature, the configured NSSAI the AMF sends only includes compatible slices, based on HPLMN decision (they are highlighted in subscription data as the compatible set to be provided in this case).

Some embodiments advantageously provide methods, systems, and apparatuses for profile switching at a wireless device such as based on a profile identifier (PID) concept.

The present disclosure is an extension of the multiple profiles concept which allows a UDM to download multiple SUPIs where only one SUPI is associated with the subscription. The other SUPIs may be considered secondary SUPIs, or Alias SUPIs. One or more embodiments described herein allows for a UE to use S-NSSAIs that cannot be used simultaneously according to, for example, the "isolation" requirement.

In one or more embodiments, a wireless device is allocated multiple profiles. Each profile may be identified with a PID.

Each PID is allocated any number of network slices for use, the network slices can be different, and some can be similar. Each network slice can be associated with different data networks, and other conditions in the profile.

Even if the same slice is used in different profiles, there can be different restrictions, and conditions as to what data network it can be used for per profile. UDM holds the relationships between PIDs, slices, and other relevant information to ensure that the proper profile is enforced.

The charging output includes the PID to ensure that profiles can be charged separately. The same applies for statistical information collected by the network.

Possible advantages for enabling multiple profiles for a subscriber are numerous. As an example, a subscriber may use his/her phone for work and for personal reasons were using configuring multiple profiles, as described herein, allows the subscriber to use separate profiles for different purposes, with separated charges per profile. More specifically, a subscriber may use the same phone, i.e., wireless device, but enable the following at different times: work related profile, personal related profile, profile for streaming, etc. The reasons for these different profiles can be due to any one of network slices with different purpose, cost related, network performance related, etc..

A phone or wireless device can also be shared by different users where the wireless device can also support multiple passwords for different users sharing the same devices so that the password can be a trigger for a profile switch.

In one or more embodiments, the UDM holds the information about the PIDs, and the corresponding profiles. The UDM enables an end user to switch between profiles through the use of the uplink (UL) NAS transport message and is now extended to enable the inclusion of a new information in the information element (IE) payload container, intended to the UDM, to enable the UDM to switch to a target profile. There may always be a default profile that will be the one used at initial wireless device registration.

Further, in one or more embodiments, at initial wireless device registration, the Access and Mobility Management Function (AMF) receives all PIDs from the UDM, as well as the subscribed S-NSSAIs bound to each PID. This enables the AMF to locate the Allowed S-NSSAI for each PID through interaction with Network Slice Selection Function, NSSF, and store them bound together.

The AMF returns to the wireless device at successful registration the Allowed S-NSSAIs for the current PID which is the default PID at initial wireless device registration. Additionally, the AMF returns to the wireless device all PIDs supported and the S-NSSAIs for each one.

The wireless device stores the PIDs bound to the subscribed S-NSSAIs. The Allowed S-NSSAIs for the PID associated with the default PID is also returned, and saved for the current PID.

For switching PIDs, the wireless device may determine to switch based at least on the selection of an application that requires an S-NSSAI bound to a different PID.

The wireless device proceeds to switch the target PID, through the use of an UL NAS transport message extended to request the UDM to switch to a new target PID.

The UDM notifies the AMF about a PID change. AMF may request the wireless device to re-register. AMF updates the Allowed S-NSSAI to match the target PID. The wireless device may be requested to perform mobility Registration if any S-NSSAI associated with the new PID requires secondary authentication.

Further, the wireless device may be configured with credentials required for secondary authentication for any S-NSSAI belonging to any PID. This will be enforced at Registration, or mobility registration associated with a new target PID.

Hence, one or more embodiments described herein advantageously enables one or more features with a low complexity solution. These one or more features extend wireless device capability using a low complexity framework.

According to the present disclosure, there are provided methods, a wireless device, an AMF node, a UDM node and a computer-readable medium according to the independent claims. Further developments are set forth in the dependent claims.

Before describing in detail example embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to wireless device initiated profile switching. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

For example, in a scenario where a first device communicates a transmission to a second device, where such transmission is destined for a third device, the first device is "in communication with" both the second device and the third device. As another example, a first device may be in communication with a second device where such communication is transmitted (directly or indirectly) via one or more third devices (e.g., intermediate devices).

The term "network node" used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi-standard radio (MSR) radio node such as MSR BS, multi-cell/multicast coordination entity (MCE), relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term "radio node" used herein may be used to also denote a wireless device (WD) such as a wireless device (WD) or a radio network node.

It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell/multicast Coordination Entity (MCE), relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).

Transmitting in downlink may pertain to transmission from the network or network node to the wireless device. Transmitting in uplink may pertain to transmission from the wireless device to the network or network node. Transmitting in sidelink may pertain to (direct) transmission from one wireless device to another. Uplink, downlink and sidelink (e.g., sidelink transmission and reception) may be considered communication directions. In some variants, uplink and downlink may also be used to described wireless communication between network nodes, e.g. for wireless backhaul and/or relay communication and/or (wireless) network communication for example between base stations or similar network nodes, in particular communication terminating at such. It may be considered that backhaul and/or relay communication and/or network communication is implemented as a form of sidelink or uplink communication or similar thereto.

Some embodiments are directed to configuration and implementation of wireless device initiated profile switching such as based on a PID concept.

Referring to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in <FIG> a schematic diagram of a communication system <NUM>, according to an embodiment, such as a 3GPP-type cellular network that may support standards such as LTE and/or NR (<NUM>), which comprises an access network <NUM>, such as a radio access network, and a core network <NUM> including one or more core nodes <NUM> (collectively referred to as core node <NUM>). The access network <NUM> comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes <NUM>), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas <NUM>). Each network node 16a, 16b, 16c is connectable to the core network <NUM> over a wired or wireless connection <NUM>. A first wireless device (WD) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second wireless device 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of wireless devices 22a, 22b (collectively referred to as wireless devices <NUM>) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole wireless device <NUM> is in the coverage area or where a sole wireless device <NUM> is connecting to the corresponding network node <NUM>. Note that although only two wireless devices <NUM> and three network nodes <NUM> are shown for convenience, the communication system may include many more wireless devices <NUM> and network nodes <NUM>.

Also, it is contemplated that a wireless device <NUM> can be in simultaneous communication and/or configured to separately communicate with more than one network node <NUM> and more than one type of network node <NUM>. For example, a wireless device <NUM> can have dual connectivity with a network node <NUM> that supports LTE and the same or a different network node <NUM> that supports NR. As an example, wireless device <NUM> can be in communication with an eNB for LTE/E-UTRAN and a gNB for NR/NG-RAN.

Core node <NUM> may be configured to include an AMF unit <NUM> that is configured to perform one or more AMF functions as described herein such as with respect to profile switching. Core node <NUM> may be configured to include a UDM unit <NUM> that is configured to perform one or more UDM functions as described herein such as with respect to profile switching. A wireless device <NUM> may be configured to include a profile unit <NUM> which is configured to perform one or more wireless device <NUM> functions such as with respect to profile switching as described herein.

Example implementations, in accordance with an embodiment, of the wireless device <NUM>, core node <NUM>, and network node <NUM> discussed in the preceding paragraphs will now be described with reference to <FIG>.

The communication system <NUM> includes a network node <NUM> provided in a communication system <NUM> and including hardware <NUM> enabling it to communicate with the wireless device <NUM> and core node <NUM>. The hardware <NUM> may include a radio interface <NUM> for setting up and maintaining at least a wireless connection <NUM> with a wireless device <NUM> located in a coverage area <NUM> served by the network node <NUM>. The radio interface <NUM> includes an array of antennas <NUM> to radiate and receive signal(s) carrying electromagnetic waves. Further, hardware <NUM> may include communication interface <NUM> for setting up communication with one or more core nodes <NUM>.

The processor <NUM> may be configured to access (e.g., write to and/or read from) the memory <NUM>, which may comprise any kind of volatile and/or non-volatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).

Thus, the network node <NUM> further has software <NUM> stored internally in, for example, memory <NUM>, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node <NUM> via an external connection. The processing circuitry <NUM> may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by network node <NUM>. Processor <NUM> corresponds to one or more processors <NUM> for performing network node <NUM> functions described herein. The memory <NUM> is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software <NUM> may include instructions that, when executed by the processor <NUM> and/or processing circuitry <NUM>, causes the processor <NUM> and/or processing circuitry <NUM> to perform the processes described herein with respect to network node <NUM>.

The communication system <NUM> further includes the wireless device <NUM> already referred to. The wireless device <NUM> may have hardware <NUM> that may include a radio interface <NUM> configured to set up and maintain a wireless connection <NUM> with a network node <NUM> serving a coverage area <NUM> in which the wireless device <NUM> is currently located. The radio interface <NUM> includes an array of antennas <NUM> to radiate and receive signal(s) carrying electromagnetic waves.

The hardware <NUM> of the wireless device <NUM> further includes processing circuitry <NUM>. The processor <NUM> may be configured to access (e.g., write to and/or read from) memory <NUM>, which may comprise any kind of volatile and/or non-volatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).

Thus, the wireless device <NUM> may further comprise software <NUM>, which is stored in, for example, memory <NUM> at the wireless device <NUM>, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the wireless device <NUM>. The client application <NUM> may be operable to provide a service to a human or non-human user via the wireless device <NUM>.

The processing circuitry <NUM> may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by wireless device <NUM>. The processor <NUM> corresponds to one or more processors <NUM> for performing wireless device <NUM> functions described herein. The wireless device <NUM> includes memory <NUM> that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software <NUM> and/or the client application <NUM> may include instructions that, when executed by the processor <NUM> and/or processing circuitry <NUM>, causes the processor <NUM> and/or processing circuitry <NUM> to perform the processes described herein with respect to wireless device <NUM>. For example, the processing circuitry <NUM> of the wireless device <NUM> may include profile unit <NUM> which is configured to perform one or more wireless device <NUM> functions such as with respect to profile switching as described herein.

The communication system <NUM> includes core node <NUM> that is configured to perform one or more core network functions, i.e., provide/function as one or more core network entities such as an AMF node <NUM>, UDM node <NUM>, etc. Core node <NUM> includes including hardware <NUM> enabling it to communicate with network node <NUM> and wireless device <NUM> such as via network node <NUM>. The hardware <NUM> may optionally include a radio interface <NUM> for performing wireless communications. Further, hardware <NUM> may include communication interface <NUM> for setting up communication with one or more core nodes <NUM>.

In the embodiment shown, the hardware <NUM> of the core node <NUM> further includes processing circuitry <NUM>. The processor <NUM> may be configured to access (e.g., write to and/or read from) the memory <NUM>, which may comprise any kind of volatile and/or non-volatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).

Thus, the network node <NUM> further has software <NUM> stored internally in, for example, memory <NUM>, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the core node <NUM> via an external connection. The processing circuitry <NUM> may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by core node <NUM>. Processor <NUM> corresponds to one or more processors <NUM> for performing core node <NUM> functions described herein. The memory <NUM> is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software <NUM> may include instructions that, when executed by the processor <NUM> and/or processing circuitry <NUM>, causes the processor <NUM> and/or processing circuitry <NUM> to perform the processes described herein with respect to core node <NUM>. For example, processing circuitry <NUM> of core node <NUM> may include AMF unit <NUM> which is configured to perform one or more AMF functions such as with respect to wireless device initiated profile switching as described herein. That is, core node <NUM> may act as and/or provide an AMF entity (i.e., AMF node <NUM>) if core node <NUM> has AMF unit <NUM>. For example, processing circuitry <NUM> of core node <NUM> may include UDM unit <NUM> which is configured to perform one or more UDM functions such as with respect to wireless device initiated profile switching as described herein. In other words, core node <NUM> may act as and/or provide a UDM entity (i.e., UDM node <NUM>) if core node <NUM> has UDM unit <NUM>. Core node <NUM> may include both units <NUM> and <NUM> such that core node <NUM> provides both an AMF entity (i.e., AMF node <NUM>) and UDM node <NUM>. Core node <NUM> may include other core node entities such as SMF, etc. and corresponding software/hardware to perform respective functionality.

In some embodiments, the inner workings of the core node <NUM>, network node <NUM>, and wireless device <NUM> may be as shown in <FIG> and independently, the surrounding network topology may be that of <FIG>.

The wireless connection <NUM> between the wireless device <NUM> and the network node <NUM> is in accordance with the teachings of the embodiments described throughout this disclosure. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and/or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc. In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.

Although <FIG> and <FIG> show various "units" such as AMF unit <NUM>, UDM unit <NUM> and profile unit <NUM> as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry. Further, while AMF unit <NUM> and UDM unit <NUM> are illustrated as being in a same core node <NUM> in <FIG>, respective core nodes <NUM> may implement respective core network functions such that a first core node <NUM> may be configured with AMF unit <NUM> while a second core node <NUM> may be configured with UDM unit <NUM>.

<FIG> is a flowchart of an example process in a wireless device <NUM> according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of wireless device <NUM> such as by one or more of processing circuitry <NUM> (including the profile unit <NUM>), processor <NUM>, and/or radio interface <NUM>. Wireless device <NUM> is configured to cause (Block S100) transmission of a message indicating the wireless device <NUM> is initiating a switch to a first profile associated with a target profile identifier, PID, where the indication of the first profile associated with a target PID configured to initiate the UDM node <NUM> to activate the first profile, as described herein. Wireless device <NUM> is configured to one of cause transmission and receive transmission (Block S102) in accordance with the activated first profile associated with the target PID, as described herein.

According to one or more embodiments, the processing circuitry is further configured to: receive mobility registration signaling that is configured to cause the wireless device <NUM> to re-register with the AMF node <NUM> before using the first profile, and perform mobility registration with the AMF node <NUM> for profile switching, as described herein.

<FIG> is a flowchart of an example process in a AMF node <NUM> (i.e., a core node <NUM> that is performing one or more AMF functions) in accordance with one or more embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of core node <NUM> such as by one or more of processing circuitry <NUM> (including the AMF unit <NUM>), processor <NUM>, and/or radio interface <NUM>. Core node <NUM> (i.e., AMF node <NUM>) is configured to receive (Block S104) a message indicating the wireless device <NUM> is initiating a switch to a first profile associated with a target profile identifier, PID, as described herein. Core node <NUM> is configured to receive (Block S106) an indication that the first profile associated with the target PID has been activated by the UDM node <NUM>, as described herein. Core node <NUM> is configured to update (Block S108) allowed single-network slice selection assistance information, S-NSSAI, associated with the wireless device <NUM> to allow the target PID to be applied for the first profile, as described herein.

According to one or more embodiments, the processing circuitry <NUM> is further configured to store a plurality of profiles and a plurality of S-NSSAIs that are usable by the wireless device <NUM> for profile switching where the plurality of profiles includes the first profile, as described herein. According to one or more embodiments, the processing circuitry <NUM> is further configured to cause the wireless device <NUM> to perform mobility registration before the target PID is applied for the first profile, as described herein. According to one or more embodiments, the message indicates the wireless device <NUM> is initiating the switch to the first profile associated with the target PID is an uplink NAS transport message including the target PID.

<FIG> is a flowchart of an example process in a core node <NUM> that is performing one or more UDM node <NUM> functions in accordance with one or more embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of core node <NUM> such as by one or more of processing circuitry <NUM> (including the UDM unit <NUM>), processor <NUM>, and/or radio interface <NUM>. Core node <NUM> (i.e., UDM node <NUM>) is configured to receive (Block S110) an indication that the wireless device <NUM> is initiating a switch to a first profile associated with a target profile identifier, PID, as described herein. Core node <NUM> is configured to switch (Block S112) the wireless device <NUM> to the first profile at least in part by activating the first profile associated with the target PID, as described herein. Core node <NUM> is configured to indicate (Block S114), to the AMF node <NUM>, that the first profile has been activated where the indication that the first profile has been activated is configured to allow the AMF node <NUM> to update its allowed single-network slice selection assistance information, S-NSSAI, associated with the wireless device <NUM> to allow the target PID to be applied for the first profile, as described herein.

<FIG> is a flowchart of an example process in a wireless device <NUM> according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of wireless device <NUM> such as by one or more of processing circuitry <NUM> (including the profile unit <NUM>), processor <NUM>, and/or radio interface <NUM>. Wireless device <NUM> is configured to determine (Block S116) to initiate a switch from a first profile associated with a first profile identifier, PID, to a target profile associated with a target PID, as described herein. Wireless device <NUM> is configured to cause transmission (Block S118) of a switch request message indicating the switch, the switch request message being configured to initiate the UDM node <NUM> to activate the target profile, as described herein. Wireless device <NUM> is configured to at least one of cause transmission of and receive (Block S120) signaling in accordance with the activated target profile associated with the target PID, as described herein.

According to one or more embodiments, the processing circuitry <NUM> is further configured to receive a mobility registration message, and to perform mobility registration based on the mobility registration message, where the mobility registration is configured to re-register with the AMF node <NUM> before using the target profile, as described herein.

According to one or more embodiments, the processing circuitry <NUM> is further configured to store a mapping of users of wireless devices <NUM> to PIDs, and to receive a login credential associated with a user of the wireless device <NUM>, the determining the switch from the first profile to the target profile being based on the user being mapped to the target PID, as described herein.

According to one or more embodiments, the processing circuitry <NUM> is further configured to cause transmission of a registration request message to the AMF node <NUM>. The processing circuitry <NUM> is further configured to, in response to the transmission of the registration request message, receive a registration accept message. The processing circuitry <NUM> is further configured to determine, based on the registration accept message, the first PID and an allowed first single-network slice selection assistance information, S-NSSAI, associated with the first PID. The processing circuitry <NUM> is further configured to at least one of cause transmission of and receive signaling in accordance with the allowed S-NSSAI, as described herein.

According to one or more embodiments, the determining of the first PID is based on the first PID being a default PID, as described herein.

According to one or more embodiments, the processing circuitry <NUM> is further configured to determine, based on the registration accept message, a plurality of supported PIDs, the plurality of supported PIDs including the first PID and the target PID, where the target PID is associated with a target S-NSSAI. The processing circuitry <NUM> is further configured to store the target PID and the target S-NSSAI, as described herein.

According to one or more embodiments, the determining of the switch from the first profile to the target profile is further based on at least one of: a financial cost associated with the target S-NSSAI, a network performance parameter associated with the target S-NSSAI, a time of day associated with the switch, and a user setting configured by a user of the wireless device <NUM>, where the user setting is at least one of: a work setting, a personal setting, and a streaming setting.

According to one or more embodiments, the switch request message is an uplink NAS transport message including the target PID, as described herein.

<FIG> is a flowchart of an example process in an AMF node <NUM> (i.e., a core node <NUM> that is performing one or more AMF functions) in accordance with one or more embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of core node <NUM> such as by one or more of processing circuitry <NUM> (including the AMF unit <NUM>), processor <NUM>, and/or radio interface <NUM>. AMF node <NUM> (i.e., core node <NUM>) is configured to receive (Block S122) a switch request message indicating the wireless device <NUM> is initiating a switch from a first profile associated with a first profile identifier, PID, to a target profile associated with a target PID, as described herein. AMF node <NUM> (i.e., core node <NUM>) is configured to receive (Block S124) an activation message indicating that the target profile associated with the target PID has been activated by the UDM node <NUM> (i.e., core node <NUM>), as described herein. AMF node <NUM> (i.e., core node <NUM>) is configured to determine (Block S126) a target single-network slice selection assistance information, S-NSSAI, associated with the wireless device <NUM> based on the target profile, as described herein. AMF node <NUM> (i.e., core node <NUM>) is configured to cause transmission (Block S128) of a configuration update to the wireless device <NUM> enabling the wireless device <NUM> to use the target S-NSSAI for signaling, as described herein.

According to one or more embodiments, the processing circuitry <NUM> is further configured to cause the wireless device <NUM> to perform mobility registration before the target PID is applied for the target profile, as described herein.

According to one or more embodiments, the processing circuitry <NUM> is further configured to receive an indication indicating a plurality of PIDs and associated S-NSSAIs. The processing circuitry <NUM> is further configured to determine a default PID of the plurality of PIDs based on the indication. The processing circuitry <NUM> is further configured to determine an allowed S-NSSAI associated with the default PID. The processing circuitry <NUM> is further configured to receive a registration request message from the wireless device <NUM>. The processing circuitry <NUM> is further configured to, in response to the receiving of the registration request message, cause transmission of a registration accept message to the wireless device <NUM>, where the registration accept message indicates the default PID and the allowed S-NSSAI, as described herein.

According to one or more embodiments, the registration accept message further indicates the plurality of PIDs and associated S-NSSAIs, as described herein. According to one or more embodiments, the switch request message is an uplink NAS transport message including the target PID, as described herein. According to one or more embodiments, the first PID is associated with a first S-NSSAI, the first S-NSSAI is associated with a packet data unit, PDU, session, and the processing circuitry <NUM> being further configured to, in response to the receiving of the switch request message, deactivate the PDU session based on the first S-NSSAI not being associated with the target PID, as described herein. According to one or more embodiments, the receiving of the switch request message is based on a login credential associated with the target PID being received by the wireless device <NUM>, as described herein. According to one or more embodiments, According to one or more embodiments of this aspect, the receiving of the switch request message is based on at least one of: a financial cost associated with the target S-NSSAI, a network performance parameter associated with the target S-NSSAI, a time of day associated with the switch, and a user setting configured by a user of the wireless device <NUM>, where the user setting is at least one of: a work setting, a personal setting, and a streaming setting. According to one or more embodiments, the first PID is a default PID, as described herein.

<FIG> is a flowchart of an example process in a UDM node (i.e., core node <NUM> that is performing one or more UDM functions) in accordance with one or more embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of core node <NUM> such as by one or more of processing circuitry <NUM> (including the UDM unit <NUM>), processor <NUM>, and/or radio interface <NUM>. UDM node <NUM> is configured to receive (Block S130) a switch request message indicating that the wireless device <NUM> is initiating a switch from a first profile associated with a first profile identifier, PID, to a target profile associated with a target PID, as described herein. UDM node <NUM> is configured to switch (Block S132) the wireless device <NUM> to the target profile, the switching including activating the target profile associated with the target PID, as described herein. UDM node <NUM> is configured to cause transmission (Block S134), to the AMF node <NUM>, of an activation message, the activation message: indicating that the target profile has been activated, and being configured to cause the AMF node <NUM> to determine a target single-network slice selection assistance information, S-NSSAI, associated with the wireless device <NUM> to allow the target PID to be applied for the target profile, as described herein.

According to one or more embodiments, the receiving of the switch request message is based on a login credential associated with the target PID being received by the wireless device <NUM>, as described herein. According to one or more embodiments, According to one or more embodiments of this aspect, the receiving of the switch request message is based on at least one of: a financial cost associated with the target S-NSSAI, a network performance parameter associated with the target S-NSSAI, a time of day associated with the switch, and a user setting configured by a user of the wireless device <NUM>, where the user setting is at least one of: a work setting, a personal setting, and a streaming setting. According to one or more embodiments, the first PID is a default PID, as described herein. According to one or more embodiments, the switch request message is an uplink NAS transport message including the target PID, as described herein.

Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for profile switching such as wireless device <NUM> initiated profile switching.

Some embodiments provide wireless device initiated profile switching including configuration and implementation of the profile switching.

<FIG> is a high level diagram of data held in different entities according to one or more embodiments of the present disclosure, including wireless device <NUM> and one or more core nodes <NUM> including AMF node <NUM>(a), SMF node <NUM>(d), and UDM node <NUM>(f), which may be co-located in a single core node <NUM> or distributed across multiple core nodes <NUM>. In Step S135, the UDM node <NUM>(f) is provisioned with the PID and the profiles associated with each PID including Subscribed S-NSSAIs. In Step S136, the wireless device 5GC registration is performed. In Step S137, the AMF node <NUM>(a) holds PID(s) bound to Subscribed S-NSSAI(s), as well as Allowed PID(s)/S-NSSAIs for the default PID. In Step S138, the wireless device <NUM> initiates PID switching. In Step S140, the wireless device <NUM> holds PID(s) bound to Subscribed S-NSSAIs, as well as Allowed PID(s) for the Target PID. In Step S142, the AMF node <NUM>(a) holds PID(s) bound to Subscribed S-NSSAIs, as well as Allowed PID(s) for the Target PID.

<FIG> are signaling diagrams of the call flow according to the typical registration for 3GPP Technical Report (TR) <NUM>. Further, as used herein, one or more core nodes <NUM> may provide one or more of new AMF node <NUM>(a), old AMF node <NUM>(b), Policy Control Function (PCF) node <NUM>(c), Session Management Function (SMF) node <NUM>(d), Authentication Server Function (AUSF) node <NUM>(e), UDM node <NUM>(f), and Equipment Identity Register (EIR) node <NUM>(g), illustrated in <FIG>. For example, one core node <NUM> may provide PCF node <NUM>(c), SMF node <NUM>(d), and UDM node <NUM>(f), while another core node <NUM> may provide new AMF node <NUM>(a) and old AMF node <NUM>(b). In another example, core node <NUM> can be any one of the nodes illustrated within core node <NUM> in <FIG>, i.e., a new AMF node <NUM>(a), an old AMF node <NUM>(b), a UDM node <NUM>(f), etc..

In Step S144, the wireless device <NUM> sends a registration request to the network node <NUM>. In Step S146, the network node <NUM> performs AMF selection. In Step S148, the network node <NUM> sends a registration request to the New AMF node <NUM>(a). In Step S150, the New AMF node <NUM>(a) sends a Namf Communication_UEContextTransfer message to the Old AMF node <NUM>(b). In Step S152, the Old AMF Node <NUM>(b) sends a Namf Communication_UEContextTransferResponse message to the New AMF node <NUM>(a). In Step S154, the New AMF node <NUM>(a) transmits an Identity Request to the wireless device <NUM>. In Step S156, the wireless device <NUM> sends an identity response to the New AMF node <NUM>(a). In Step S158, the New AMF node <NUM>(a) performs AUSF selection. In Step S160, the network performs authentication and security procedures. In Step S162, the New AMF node <NUM>(a) sends a Namf_Communication_RegistrationStatusUpdate message to the EIR node <NUM>(g). In Step S164, the wireless device <NUM> and New AMF node <NUM>(a) exchange identity request/response message(s). In Step S166, the New AMF node <NUM>(a) and the PCF node <NUM>(c) exchange N5g-eir_EquipmentIdentityCheck_Get message(s). In Step S168, the New AMF node <NUM>(a) performs UDM Selection. In Step S170, the New AMF node <NUM>(a) and the UDM node <NUM>(f) exchange Nudm_UECM_Registration message(s).

In Step <NUM>, the New AMF node <NUM>(a) and the UDM node <NUM>(f) exchange Nudm_SDM_Get message(s). In Step S172, the UDM node <NUM>(f) is configured with additional PIDs and associated data, e.g., via an Information element (IE), as an additional element in the Access and Mobility subscription related data. Each PID includes the subscribed S-NSSAI for that PID. One PID is considered default for the subscription and will be initially in effect. This is sent to the New AMF node <NUM>(a) during the retrieval.

In Step <NUM>, the New AMF node <NUM>(a) stores ProfileIDs and S-NSSAIs for each PID. The New AMF node <NUM>(a) then interacts with NSSF to fetch the Allowed S-NNSAI for all PIDs. They are stored and bounded to the PID. The New AMF node <NUM>(a) may only return to wireless device <NUM> the Allowed S-NSSAI for the default PID at initial registration.

In Step S176, the New AMF node <NUM>(a) sends a Nudm_SDM_Subscribe <NUM> message to the UDM node <NUM>(f). In Step S178, the UDM node <NUM>(f) sends a Nudm_UECM_DeregistrationNotify message to the PCF node <NUM>(c). In Step S180, the New AMF node <NUM>(a) performs PCF Selection. In Step S182, the Old AMF node <NUM>(b) sends a Nudm_SDM_Unsubscribe message to the UDM node <NUM>(f). In Step S184, the New AMF node <NUM>(a), Old AMF node <NUM>(b), and PCF node <NUM>(c) perform AMF Policy Association Establishment/Modification. In Step S186, the New AMF node <NUM>(a) transmits a Nsfm_PDUSession_UpdateSMContext/Nsfm_PDUSession_ReleaseSMContext message to the SMF node <NUM>(d). In Step S188, the New AMF node <NUM>(a) sends a UE Context Modification Request to the Non-3GPPP Inter-Working Function (N3IWF), Trusted Non-3GPP Gateway Function (TNGF), and/or Wireline Access Gateway Function (W-AGF) node <NUM>(h), which may be part of one or more of core node(s) <NUM>. In Step <NUM>, the N3IWF/TNGF/W-AGF node <NUM>(h) sends a UE Context Modification Response to the New AMF node <NUM>(a). In Step S192, the New AMF node <NUM>(a) sends a Nudm_UECM_Registration message to the UDM node <NUM>(f). In Step S194, the UDM node <NUM>(f) sends a Nudm_UECM_DeregistrationNotify message to the Old AMF node <NUM>(b). In Step S196, the Old AMF node <NUM>(b) sends a Nudm_UECM_Unsubscribe message to the UDM node <NUM>(f).

In Step S198, the New AMF node <NUM>(a) sends a Registration Accept (Profile-IDs) message to the wireless device <NUM>, and/or the PIDS are returned to the wireless device <NUM>. In some embodiments, the Allowed S-NSSAI may include only those S-NSSAI(s) which is/are associated with the default PID, since this is an initial Registration.

In Step S200, the wireless device <NUM> stores the PIDs. In Step S202, the New AMF node <NUM>(a), Old AMF node <NUM>(b), and/or PCF node <NUM>(c) perform UE Policy Association Establishment. In Step S204, the wireless device <NUM> sends a Registration Complete message to the New AMF node <NUM>(a). In Step S206, the New AMF node <NUM>(a) and UDM node <NUM>(f) exchange Nudm_SDM_Info. In Step S208, the New AMF node <NUM>(a) sends an N2 Message to the network node <NUM>. In Step S210, the New AMF node <NUM>(a) and the UDM node <NUM>(f) exchange Nudm_UECM_Update messages. In Step S212, the wireless device <NUM>, network node <NUM>, and/or New AMF node <NUM>(a) perform Network Slice-Specific Authentication and Authorization procedures.

In some embodiments, the UDM node <NUM>(f) may be pre-configured with PIDs and/or associated S-NSSAI(s).

PIDS may have a user friendly name and an ID that is used for protocol/profile purposes. The currently applicable PID may also be displayed to the end user.

<FIG> is a signalling diagram of a call flow of how a user can initiate a profile switch to a different profile.

The steps in the call flow are described below:.

While not shown in <FIG>, in one or more embodiments, the AMF node <NUM>(a) may, based on policies, tear down all PDU sessions associated with S-NSSAIs that belong to an old PID and not allowed with the new PID.

Wireless device <NUM> can be shared as well by different users and can also support multiple passwords for different users sharing the same wireless device(s) <NUM> so that the password can be trigger for a profile switch, for example. There may be other user based triggers to initiate or cause the profile switch that are in accordance with the teachings described herein.

Therefore, one or more embodiments described herein relate to a PID concept, profile identifier. The UDM node <NUM> defines multiple profiles for in a wireless device <NUM> subscription where each profile includes PID, corresponding NSSAI information, and other subscription information. All PIDs and corresponding NSSAIs are provided to AMF during first registration, and AMF provides the information to wireless device <NUM> as well. However, AMF may only indicate allowed NSSAI to wireless device <NUM> that is related to the default PID.

In case wireless device <NUM> wants to switch to another PID/NSSAI received in the previous registration, wireless device <NUM> sends the target PID to the network (i.e., core network <NUM> via network node <NUM>) and the network applies the new profile and corresponding NSSAI.

Wireless device <NUM> sends the wanted/target PID to UDM node <NUM> by extending the current parameter "WD parameters update transparent container" and the UDM node <NUM> indicates the wanted PID to AMF. The AMF switches to the new profile and updates wireless device <NUM> with new allowed NSSAI associated with the new PID, via the UCU procedure. An indication is provided to the AMF to remove the PDU sessions related to the previous PID/NSSAI. For certain cases, the AMF may still need to request wireless device <NUM> to perform normal (initial or mobility) Registration Request.

In one or more embodiments, other alternatives for wireless device <NUM> to indicate the wanted PID to AMF with limited impact on NAS message may be used where these alternatives may avoid a round trip via UDM node <NUM> or may be make round trip to UDM node <NUM> optional.

Claim 1:
A method implemented in a wireless device (<NUM>) configured to communicate with an Access and Mobility Management Function, AMF, entity (<NUM>), and a Unified Data Management, UDM, node (<NUM>), the method comprising:
determining (S116) to initiate a switch from a first profile associated with a first profile identifier, PID, to a target profile associated with a target PID;
causing transmission (S118) of a switch request message indicating the switch, the switch request message being configured to initiate the UDM node (<NUM>) to activate the target profile; and
at least one of causing transmission of and receiving (S120) signaling in accordance with the activated target profile associated with the target PID.