GENERIC FRAMEWORK FOR SUPPORT OF MULTIPLE PROFILES SUPPORT IN 5G

A method, system and apparatus are disclosed. According to one or more embodiments, a method implemented in a wireless device configured to communicate with an Access and Mobility Management Function, AMF, node and a Unified Data Management, UDM, node is provided. The method includes determining to initiate a switch from a first profile associated with a first profile identifier, PID, to a target profile associated with a target PID. The method further includes causing transmission of a switch request message indicating the switch, the switch request message being configured to initiate the UDM node to activate the target profile. The method further includes causing transmission of or receiving signaling in accordance with the activated target profile associated with the target PID.

FIELD

The present disclosure relates to wireless communications, and in particular, to wireless device initiated profile switching such as based on a profiled ID (PID) concept.

BACKGROUND

The Third Generation Partnership Project (3GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (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.

SUMMARY

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 one aspect of the present disclosure, a wireless device configured to communicate with an AMF node and a UDM node is provided. The wireless device includes processing circuitry configured to determine to initiate a switch from a first profile associated with a first profile identifier, PID, to a target profile associated with a target PID. The processing circuitry is further configured to cause transmission of a switch request message indicating the switch, the switch request message being configured to initiate the UDM node to activate the target profile. The processing circuitry is further configured to at least one of cause transmission of and receive signaling in accordance with the activated target profile associated with the target PID.

According to one or more embodiments of this aspect, the processing circuitry 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 before using the target profile.

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

According to one or more embodiments of this aspect, the processing circuitry is further configured to cause transmission of a registration request message to the AMF node. The processing circuitry is further configured to, in response to the transmission of the registration request message, receive a registration accept message. The processing circuitry 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 is further configured to at least one of cause transmission of and receive signaling in accordance with the allowed S-NSSAI.

According to one or more embodiments of this aspect, the determining of the first PID is based on the first PID being a default PID.

According to one or more embodiments of this aspect, the processing circuitry 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 is further configured to store the target PID and the target S-NSSAI.

According to one or more embodiments of this aspect, 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, 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 of this aspect, the switch request message is an uplink non-access-stratum (NAS) transport message including the target PID.

According to another aspect of the present disclosure, a method implemented in a wireless device configured to communicate with an AMF node and a UDM node is provided. The method includes determining to initiate a switch from a first profile associated with a first profile identifier, PID, to a target profile associated with a target PID. The method further includes causing transmission of a switch request message indicating the switch, the switch request message being configured to initiate the UDM node to activate the target profile. The method further includes at least one of causing transmission of and receiving signaling in accordance with the activated target profile associated with the target PID.

According to one or more embodiments of this aspect, the method further includes receiving a mobility registration message, and performing mobility registration based on the mobility registration message, where the mobility registration is configured to re-register with the AMF node before using the target profile.

According to one or more embodiments of this aspect, the method further includes storing a mapping of users of wireless devices to PIDs, and receiving a login credential associated with a user of the wireless device, the determining the switch from the first profile to the target profile being based on the user being mapped to the target PID.

According to one or more embodiments of this aspect, the method further includes causing transmission of a registration request message to the AMF node. The method further includes, in response to the transmission of the registration request message, receiving a registration accept message. The method further includes determining, 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 method further includes at least one of causing transmission of and receiving signaling in accordance with the allowed S-NSSAI.

According to one or more embodiments of this aspect, the determining of the first PID is based on the first PID being a default PID.

According to one or more embodiments of this aspect, the method further includes determining, 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 method further includes storing the target PID and the target S-NSSAI.

According to one or more embodiments of this aspect, 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, 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 of this aspect, the switch request message is an uplink NAS transport message including the target PID.

According to another aspect of the present disclosure, an AMF node (i.e., a core node that is performing one or more AMF functions) that is configured to communicate with a UDM node (i.e., a core node that is performing one or more UDM functions) and with a wireless device is provided. The AMF node includes processing circuitry configured to receive a switch request message indicating the wireless device is initiating a switch from a first profile associated with a first profile identifier, PID, to a target profile associated with a target PID. The processing circuitry is further configured to receive an activation message indicating that the target profile associated with the target PID has been activated by the UDM node. The processing circuitry is further configured to determine a target single-network slice selection assistance information, S-NSSAI, associated with the wireless device based on the target profile. The processing circuitry is further configured to cause transmission of a configuration update to the wireless device enabling the wireless device to use the target S-NSSAI for signaling.

According to one or more embodiments of this aspect, the processing circuitry is further configured to cause the wireless device to perform mobility registration before the target PID is applied for the target profile.

According to one or more embodiments of this aspect, the processing circuitry is further configured to receive an indication indicating a plurality of PIDs and associated S-NSSAIs. The processing circuitry is further configured to determine a default PID of the plurality of PIDs based on the indication. The processing circuitry is further configured to determine an allowed S-NSSAI associated with the default PID. The processing circuitry is further configured to receive a registration request message from the wireless device. The processing circuitry 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, where the registration accept message indicates the default PID and the allowed S-NSSAI.

According to one or more embodiments of this aspect, the registration accept message further indicates the plurality of PIDs and associated S-NSSAIs. According to one or more embodiments of this aspect, the switch request message is an uplink NAS transport message including the target PID. According to one or more embodiments of this aspect, 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 is 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. According to one or more embodiments of this aspect, the receiving of the switch request message is based on a login credential associated with the target PID being received by the wireless device. 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, where the user setting is at least one of: a work setting, a personal setting, and a streaming setting.

According to another aspect of the present disclosure, a method implemented in an AMF node (i.e., a core node that is performing one or more AMF functions) that is configured to communicate with a UDM node (i.e., a core node that is performing one or more UDM functions) and with a wireless device is provided. The method includes receiving a switch request message indicating the wireless device is initiating a switch from a first profile associated with a first profile identifier, PID, to a target profile associated with a target PID. The method further includes receiving an activation message indicating that the target profile associated with the target PID has been activated by the UDM node. The method further includes determining a target single-network slice selection assistance information, S-NSSAI, associated with the wireless device based on the target profile. The method further includes causing transmission of a configuration update to the wireless device enabling the wireless device to use the target S-NSSAI for signaling.

According to one or more embodiments of this aspect, the method further includes causing the wireless device to perform mobility registration before the target PID is applied for the target profile.

According to one or more embodiments of this aspect, the method further includes receiving an indication indicating a plurality of PIDs and associated S-NSSAIs. The method further includes determining a default PID of the plurality of PIDs based on the indication. The method further includes determining an allowed S-NSSAI associated with the default PID. The method further includes receiving a registration request message from the wireless device. The method further includes, in response to the receiving of the registration request message, causing transmission of a registration accept message to the wireless device, where the registration accept message indicates the default PID and the allowed S-NSSAI.

According to one or more embodiments of this aspect, the registration accept message further indicates the plurality of PIDs and associated S-NSSAIs. According to one or more embodiments of this aspect, the switch request message is an uplink NAS transport message including the target PID. According to one or more embodiments of this aspect, 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 method further includes, in response to the receiving of the switch request message, deactivating the PDU session based on the first S-NSSAI not being associated with the target PID. According to one or more embodiments of this aspect, the receiving of the switch request message is based on a login credential associated with the target PID being received by the wireless device. 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, 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 of this aspect, the first PID is a default PID.

According to another aspect of the present disclosure, a UDM node (i.e., a core node that is performing one or more UDM functions) that is configured to communicate with a AMF node (i.e., a core node that is performing one or more AMF functions) and with a wireless device is provided. The UDM node includes processing circuitry configured to receive a switch request message indicating that the wireless device is initiating a switch from a first profile associated with a first profile identifier, PID, to a target profile associated with a target PID. The processing circuitry is further configured to switch the wireless device to the target profile, the switching including activating the target profile associated with the target PID. The processing circuitry is further configured to cause transmission, to the AMF, of an activation message, the activation message: indicating that the target profile has been activated, and being configured to cause the AMF to determine a target single-network slice selection assistance information, S-NSSAI, associated with the wireless device to allow the target PID to be applied for the target profile.

According to one or more embodiments of this aspect, the receiving of the switch request message is based on a login credential associated with the target PID being received by the wireless device. 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, 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 of this aspect, the first PID is a default PID. According to one or more embodiments of this aspect, the switch request message is an uplink NAS transport message including the target PID.

According to another aspect of the present disclosure, a method implemented in a UDM node (i.e., a core node that is performing one or more UDM functions) that is configured to communicate with a AMF node (i.e., a core node that is performing one or more AMF functions) and with a wireless device is provided. The method includes receiving a switch request message indicating that the wireless device is initiating a switch from a first profile associated with a first profile identifier, PID, to a target profile associated with a target PID. The method further includes switching the wireless device to the target profile, the switching including activating the target profile associated with the target PID. The method further includes causing transmission, to the AMF, of an activation message, the activation message: indicating that the target profile has been activated, and being configured to cause the AMF to determine a target single-network slice selection assistance information, S-NSSAI, associated with the wireless device to allow the target PID to be applied for the target profile.

According to one or more embodiments of this aspect, the receiving of the switch request message is based on a login credential associated with the target PID being received by the wireless device. 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, 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 of this aspect, the first PID is a default PID. According to one or more embodiments of this aspect, the switch request message is an uplink NAS transport message including the target PID.

DETAILED DESCRIPTION

In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication. 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).

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 inFIG.1a schematic diagram of a communication system10, according to an embodiment, such as a 3GPP-type cellular network that may support standards such as LTE and/or NR (5G), which comprises an access network12, such as a radio access network, and a core network14including one or more core nodes15(collectively referred to as core node15). The access network12comprises a plurality of network nodes16a,16b,16c(referred to collectively as network nodes16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area18a,18b,18c(referred to collectively as coverage areas18). Each network node16a,16b,16cis connectable to the core network14over a wired or wireless connection20. A first wireless device (WD)22alocated in coverage area18ais configured to wirelessly connect to, or be paged by, the corresponding network node16a. A second wireless device22bin coverage area18bis wirelessly connectable to the corresponding network node16b. While a plurality of wireless devices22a,22b(collectively referred to as wireless devices22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole wireless device22is in the coverage area or where a sole wireless device22is connecting to the corresponding network node16. Note that although only two wireless devices22and three network nodes16are shown for convenience, the communication system may include many more wireless devices22and network nodes16.

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

Core node15may be configured to include an AMF unit24that is configured to perform one or more AMF functions as described herein such as with respect to profile switching. Core node15may be configured to include a UDM unit25that is configured to perform one or more UDM functions as described herein such as with respect to profile switching. A wireless device22may be configured to include a profile unit26which is configured to perform one or more wireless device22functions such as with respect to profile switching as described herein.

Example implementations, in accordance with an embodiment, of the wireless device22, core node15, and network node16discussed in the preceding paragraphs will now be described with reference toFIG.2.

The communication system10includes a network node16provided in a communication system10and including hardware28enabling it to communicate with the wireless device22and core node15. The hardware28may include a radio interface30for setting up and maintaining at least a wireless connection32with a wireless device22located in a coverage area18served by the network node16. The radio interface30may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers. The radio interface30includes an array of antennas34to radiate and receive signal(s) carrying electromagnetic waves. Further, hardware28may include communication interface31for setting up communication with one or more core nodes15.

In the embodiment shown, the hardware28of the network node16further includes processing circuitry36. The processing circuitry36may include a processor38and a memory40. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry36may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor38may be configured to access (e.g., write to and/or read from) the memory40, which may comprise any kind of volatile and/or nonvolatile 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 node16further has software42stored internally in, for example, memory40, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node16via an external connection. The software42may be executable by the processing circuitry36. The processing circuitry36may 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 node16. Processor38corresponds to one or more processors38for performing network node16functions described herein. The memory40is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software42may include instructions that, when executed by the processor38and/or processing circuitry36, causes the processor38and/or processing circuitry36to perform the processes described herein with respect to network node16.

The communication system10further includes the wireless device22already referred to. The wireless device22may have hardware44that may include a radio interface46configured to set up and maintain a wireless connection32with a network node16serving a coverage area18in which the wireless device22is currently located. The radio interface46may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers. The radio interface46includes an array of antennas48to radiate and receive signal(s) carrying electromagnetic waves.

The hardware44of the wireless device22further includes processing circuitry50. The processing circuitry50may include a processor52and memory54. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry50may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor52may be configured to access (e.g., write to and/or read from) memory54, which may comprise any kind of volatile and/or nonvolatile 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 device22may further comprise software56, which is stored in, for example, memory54at the wireless device22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the wireless device22. The software56may be executable by the processing circuitry50. The software56may include a client application58. The client application58may be operable to provide a service to a human or non-human user via the wireless device22.

The processing circuitry50may 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 device22. The processor52corresponds to one or more processors52for performing wireless device22functions described herein. The wireless device22includes memory54that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software56and/or the client application58may include instructions that, when executed by the processor52and/or processing circuitry50, causes the processor52and/or processing circuitry50to perform the processes described herein with respect to wireless device22. For example, the processing circuitry50of the wireless device22may include profile unit26which is configured to perform one or more wireless device22functions such as with respect to profile switching as described herein.

The communication system10includes core node15that 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 node15, UDM node15, etc. Core node15includes including hardware60enabling it to communicate with network node16and wireless device22such as via network node16. The hardware60may optionally include a radio interface62for performing wireless communications. The radio interface62may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers. Further, hardware60may include communication interface64for setting up communication with one or more core nodes15.

In the embodiment shown, the hardware60of the core node15further includes processing circuitry66. The processing circuitry66may include a processor68and a memory70. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry66may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor68may be configured to access (e.g., write to and/or read from) the memory70, which may comprise any kind of volatile and/or nonvolatile 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 node16further has software72stored internally in, for example, memory70, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the core node15via an external connection. The software72may be executable by the processing circuitry66. The processing circuitry66may 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 node15. Processor68corresponds to one or more processors68for performing core node15functions described herein. The memory70is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software72may include instructions that, when executed by the processor68and/or processing circuitry66, causes the processor68and/or processing circuitry66to perform the processes described herein with respect to core node15. For example, processing circuitry66of core node15may include AMF unit24which 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 node15may act as and/or provide an AMF entity (i.e., AMF node15) if core node15has AMF unit24. For example, processing circuitry66of core node15may include UDM unit25which 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 node15may act as and/or provide a UDM entity (i.e., UDM node15) if core node15has UDM unit25. Core node15may include both units24and25such that core node15provides both an AMF entity (i.e., AMF node15) and UDM node15. Core node15may 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 node15, network node16, and wireless device22may be as shown inFIG.2and independently, the surrounding network topology may be that ofFIG.1.

The wireless connection32between the wireless device22and the network node16is 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.

AlthoughFIGS.1and2show various “units” such as AMF unit24, UDM unit25and profile unit26as 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 unit24and UDM unit25are illustrated as being in a same core node15inFIG.2, respective core nodes15may implement respective core network functions such that a first core node15may be configured with AMF unit24while a second core node15may be configured with UDM unit25.

FIG.3is a flowchart of an example process in a wireless device22according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of wireless device22such as by one or more of processing circuitry50(including the profile unit26), processor52, and/or radio interface46. Wireless device22is configured to cause (Block S100) transmission of a message indicating the wireless device22is 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 node15to activate the first profile, as described herein. Wireless device22is 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 device22to re-register with the AMF node15before using the first profile, and perform mobility registration with the AMF node15for profile switching, as described herein.

FIG.4is a flowchart of an example process in a AMF node15(i.e., a core node15that 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 node15such as by one or more of processing circuitry66(including the AMF unit24), processor68, and/or radio interface62. Core node15(i.e., AMF node15) is configured to receive (Block S104) a message indicating the wireless device22is initiating a switch to a first profile associated with a target profile identifier, PID, as described herein. Core node15is configured to receive (Block S106) an indication that the first profile associated with the target PID has been activated by the UDM node15, as described herein. Core node15is configured to update (Block S108) allowed single-network slice selection assistance information, S-NSSAI, associated with the wireless device22to allow the target PID to be applied for the first profile, as described herein.

According to one or more embodiments, the processing circuitry66is further configured to store a plurality of profiles and a plurality of S-NSSAIs that are usable by the wireless device22for profile switching where the plurality of profiles includes the first profile, as described herein. According to one or more embodiments, the processing circuitry66is further configured to cause the wireless device22to 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 device22is initiating the switch to the first profile associated with the target PID is an uplink NAS transport message including the target PID.

FIG.5is a flowchart of an example process in a core node15that is performing one or more UDM node15functions 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 node15such as by one or more of processing circuitry66(including the UDM unit25), processor68, and/or radio interface62. Core node15(i.e., UDM node15) is configured to receive (Block S110) an indication that the wireless device22is initiating a switch to a first profile associated with a target profile identifier, PID, as described herein. Core node15is configured to switch (Block S112) the wireless device22to the first profile at least in part by activating the first profile associated with the target PID, as described herein. Core node15is configured to indicate (Block S114), to the AMF node15, that the first profile has been activated where the indication that the first profile has been activated is configured to allow the AMF node15to update its allowed single-network slice selection assistance information, S-NSSAI, associated with the wireless device22to allow the target PID to be applied for the first profile, as described herein.

FIG.6is a flowchart of an example process in a wireless device22according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of wireless device22such as by one or more of processing circuitry50(including the profile unit26), processor52, and/or radio interface46. Wireless device22is 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 device22is configured to cause transmission (Block S118) of a switch request message indicating the switch, the switch request message being configured to initiate the UDM node15to activate the target profile, as described herein. Wireless device22is 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 circuitry50is 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 node15before using the target profile, as described herein.

According to one or more embodiments, the processing circuitry50is further configured to store a mapping of users of wireless devices22to PIDs, and to receive a login credential associated with a user of the wireless device22, 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 circuitry50is further configured to cause transmission of a registration request message to the AMF node15. The processing circuitry50is further configured to, in response to the transmission of the registration request message, receive a registration accept message. The processing circuitry50is 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 circuitry50is 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 circuitry50is 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 circuitry50is 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 device22, 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.7is a flowchart of an example process in an AMF node15(i.e., a core node15that 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 node15such as by one or more of processing circuitry66(including the AMF unit24), processor68, and/or radio interface62. AMF node15(i.e., core node15) is configured to receive (Block S122) a switch request message indicating the wireless device22is 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 node15(i.e., core node15) 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 node15(i.e., core node15), as described herein. AMF node15(i.e., core node15) is configured to determine (Block S126) a target single-network slice selection assistance information, S-NSSAI, associated with the wireless device22based on the target profile, as described herein. AMF node15(i.e., core node15) is configured to cause transmission (Block S128) of a configuration update to the wireless device22enabling the wireless device22to use the target S-NSSAI for signaling, as described herein.

According to one or more embodiments, the processing circuitry66is further configured to cause the wireless device22to perform mobility registration before the target PID is applied for the target profile, as described herein.

According to one or more embodiments, the processing circuitry66is further configured to receive an indication indicating a plurality of PIDs and associated S-NSSAIs. The processing circuitry66is further configured to determine a default PID of the plurality of PIDs based on the indication. The processing circuitry66is further configured to determine an allowed S-NSSAI associated with the default PID. The processing circuitry66is further configured to receive a registration request message from the wireless device22. The processing circuitry66is further configured to, in response to the receiving of the registration request message, cause transmission of a registration accept message to the wireless device22, 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 circuitry66being 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 device22, 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 device22, 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.8is a flowchart of an example process in a UDM node (i.e., core node15that 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 node15such as by one or more of processing circuitry66(including the UDM unit25), processor68, and/or radio interface62. UDM node15is configured to receive (Block S130) a switch request message indicating that the wireless device22is 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 node15is configured to switch (Block S132) the wireless device22to the target profile, the switching including activating the target profile associated with the target PID, as described herein. UDM node15is configured to cause transmission (Block S134), to the AMF node15, of an activation message, the activation message: indicating that the target profile has been activated, and being configured to cause the AMF node15to determine a target single-network slice selection assistance information, S-NSSAI, associated with the wireless device22to 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 device22, 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 device22, 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 device22initiated profile switching.

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

FIG.9is a high level diagram of data held in different entities according to one or more embodiments of the present disclosure, including wireless device22and one or more core nodes15including AMF node15(a), SMF node15(d), and UDM node15(f), which may be co-located in a single core node15or distributed across multiple core nodes15. In Step S135, the UDM node15(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 node15(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 device22initiates PID switching. In Step S140, the wireless device22holds PID(s) bound to Subscribed S-NSSAIs, as well as Allowed PID(s) for the Target PID. In Step S142, the AMF node15(a) holds PID(s) bound to Subscribed S-NSSAIs, as well as Allowed PID(s) for the Target PID.

Initial Registration with Default PID

FIGS.10A-10Bare signaling diagrams of the call flow according to the typical registration for 3GPP Technical Report (TR) 23.502. Further, as used herein, one or more core nodes15may provide one or more of new AMF node15(a), old AMF node15(b), Policy Control Function (PCF) node15(c), Session Management Function (SMF) node15(d), Authentication Server Function (AUSF) node15(e), UDM node15(f), and Equipment Identity Register (EIR) node15(g), illustrated inFIGS.10A-10B. For example, one core node15may provide PCF node15(c), SMF node15(d), and UDM node15(f), while another core node15may provide new AMF node15(a) and old AMF node15(b). In another example, core node15can be any one of the nodes illustrated within core node15inFIGS.10A-10B, i.e., a new AMF node15(a), an old AMF node15(b), a UDM node15(f), etc.

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

In Step172, the New AMF node15(a) and the UDM node15(f) exchange Nudm_SDM_Get message(s). In Step S172, the UDM node15(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 node15(a) during the retrieval.

In Step174, the New AMF node15(a) stores ProfileIDs and S-NSSAIs for each PID. The New AMF node15(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 node15(a) may only return to wireless device22the Allowed S-NSSAI for the default PID at initial registration.

In Step S176, the New AMF node15(a) sends a Nudm_SDM_Subscribe176message to the UDM node15(f). In Step S178, the UDM node15(f) sends a Nudm_UECM_DeregistrationNotify message to the PCF node15(c). In Step S180, the New AMF node15(a) performs PCF Selection. In Step S182, the Old AMF node15(b) sends a Nudm_SDM_Unsubscribe message to the UDM node15(f). In Step S184, the New AMF node15(a), Old AMF node15(b), and PCF node15(c) perform AMF Policy Association Establishment/Modification. In Step S186, the New AMF node15(a) transmits a Nsfm_PDUSession_UpdateSMContext/Nsfm_PDUSession_ReleaseSMContext message to the SMF node15(d). In Step S188, the New AMF node15(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) node15(h), which may be part of one or more of core node(s)15. In Step190, the N3IWF/TNGF/W-AGF node15(h) sends a UE Context Modification Response to the New AMF node15(a). In Step S192, the New AMF node15(a) sends a Nudm_UECM_Registration message to the UDM node15(f). In Step S194, the UDM node15(f) sends a Nudm_UECM_DeregistrationNotify message to the Old AMF node15(b). In Step S196, the Old AMF node15(b) sends a Nudm_UECM_Unsubscribe message to the UDM node15(f).

In Step S198, the New AMF node15(a) sends a Registration Accept (ProfileIDs) message to the wireless device22, and/or the PIDS are returned to the wireless device22. 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 device22stores the PIDs. In Step S202, the New AMF node15(a), Old AMF node15(b), and/or PCF node15(c) perform UE Policy Association Establishment. In Step S204, the wireless device22sends a Registration Complete message to the New AMF node15(a). In Step S206, the New AMF node15(a) and UDM node15(f) exchange Nudm_SDM_Info. In Step S208, the New AMF node15(a) sends an N2 Message to the network node16. In Step S210, the New AMF node15(a) and the UDM node15(f) exchange Nudm_UECM_Update messages. In Step S212, the wireless device22, network node16, and/or New AMF node15(a) perform Network Slice-Specific Authentication and Authorization procedures.

In some embodiments, the UDM node15(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.

Switching Profiles

FIG.11is 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:

In Step S214, wireless device22initiates a UL NAS transport message, sent to the AMF, to inform the UDM node15(f) that the wireless device22wants to initiate a profile switch. The existing IE=wireless device parameters update transparent container to activate new profile is extended with a new capability for profile switching and includes the target PID that wireless device22wants to use. This is included in the Payload container IE sent to the UDM node15(f).

In Step S216, the UDM node15(f) receives the instruction from the AMF node15(a).

In Step S218, the UDM node15(f) validates the needed information and performs the profile switch.

In Step S220, the UDM node15(f) informs the AMF node15(a) about the PID that is being activated in an Nudm-SDM_Notification (Nudm Subscriber Data Management) message that is extended to include this information.

In Step S224, the AMF node15(a) updates the Allowed information, e.g., S-NSSAI, and any other info, based on the used profile. The AMF node15(a) may request that the wireless device22re-register if there is a secondary Authentication for one of the Allowed slices for the activated profile. The AMF node15(a) sets up its internal state to associate an upcoming mobility registration with the target PID. The AMF node15(a) informs the wireless device22and may request that it re-registers so the new PID takes effect. This command is extended to support the profile switching

In Step S226, the AMF node15(a) exchanges configuration update(s) with the wireless device22.

In step S228, wireless device22performs 5GC mobility registration to receive the new Allowed S-NSSAIs associated with the new PID. AMF node15(a) knows that this mobility registration is associated with the target PID based at least on Step S224. The mobility registration itself is the same as an existing mobility registration except that there is a new trigger which is a profile switch.

In Step S230, the AMF node15(a) applies the new PID.

While not shown inFIG.11, in one or more embodiments, the AMF node15(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.

Extensions to Support Shared Device Between Multiple Users

Wireless device22can be shared as well by different users and can also support multiple passwords for different users sharing the same wireless device(s)22so 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 node15defines multiple profiles for in a wireless device22subscription 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 device22as well. However, AMF may only indicate allowed NSSAI to wireless device22that is related to the default PID.

In case wireless device22wants to switch to another PID/NSSAI received in the previous registration, wireless device22sends the target PID to the network (i.e., core network15via network node16) and the network applies the new profile and corresponding NSSAI.

In one or more embodiments, other alternatives for wireless device22to 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 node15or may be make round trip to UDM node15optional.

SOME EXAMPLES

Example A1. An Access and Mobility Management Function, AMF, entity configured to communicate with a wireless device22and Unified Data Management, UDM, entity, the AMF configured to, and/or comprising processing circuitry configured to:receive a message indicating the wireless device22is initiating a switch to a first profile associated with a target profile identifier, PID;receive an indication that the first profile associated with the target PID has been activated by the UDM; andupdate allowed single-network slice selection assistance information, S-NSSAI, associated with the wireless device22to allow the target PID to be applied for the first profile.

Example A2. The AMF entity15of Example A1, wherein the processing circuitry is further configured to store a plurality of profiles and a plurality of S-NSSAIs that are usable by the wireless device22for profile switching, the plurality of profiles including the first profile.

Example A3. The AMF entity15of Example A1, wherein the processing circuitry is further configured to cause the wireless device22to perform mobility registration before the target PID is applied for the first profile.

Example B1. A method implemented in an Access and Mobility Management Function, AMF, entity configured to communicate with a wireless device22and Unified Data Management, UDM, entity, the method comprising:receiving a message indicating the wireless device22is initiating a switch to a first profile associated with a target profile identifier, PID;receiving an indication that the first profile associated with the target PID has been activated by the UDM; andupdating allowed single-network slice selection assistance information, S-NSSAI, associated with the wireless device22to allow the target PID to be applied for the first profile

Example B2. The method of Example B1, further comprising storing a plurality of profiles and a plurality of S-NSSAIs that are usable by the wireless device22for profile switching, the plurality of profiles including the first profile.

Example B3. The method of Example B1, further comprising causing the wireless device22to perform mobility registration before the target PID is applied for the first profile.

Example B4. The method of Example B1, wherein the message indicating the wireless device22is initiating the switch to the first profile associated with the target PID is an uplink non-access-stratum, NAS, transport message including the target PID.

Example C1. A Unified Data Management, UDM, entity, that is configured to communicate with an Access and Mobility Management Function, AMF, entity, and a wireless device22, the UDM entity15configured to, and/or comprising processing circuitry configured to:receive an indication that the wireless device22is initiating a switch to a first profile associated with a target profile identifier, PID;switch the wireless device22to the first profile at least in part by activating the first profile associated with the target PID;indicate, to the AMF, that the first profile has been activated, the indication that the first profile has been activated being configured to allow the AMF to update its allowed single-network slice selection assistance information, S-NSSAI, associated with the wireless device22to allow the target PID to be applied for the first profile.

Example C2. The UDM of Example C1, wherein the UDM is configured with a plurality of PIDs where each PID is associated with respective S-NSSAI, the plurality of PIDs including the target PID.

Example D1. A method implemented in a Unified Data Management, UDM, entity that is configured to communicate with an Access and Mobility Management Functions, AMF, entity and a wireless device22, the method comprising:receiving an indication that the wireless device22is initiating a switch to a first profile associated with a target profile identifier, PID;switching the wireless device22to the first profile at least in part by activating the first profile associated with the target PID;indicating, to the AMF, that the first profile has been activated, the indication that the first profile has been activated being configured to allow the AMF to update its allowed single-network slice selection assistance information, S-NSSAI, associated with the wireless device22to allow the target PID to be applied for the first profile.

Example D2. The method of Example D1, wherein the UDM is configured with a plurality of PIDs where each PID is associated with respective S-NSSAI, the plurality of PIDs including the target PID.

Example E1. A wireless device22that is configured to communicate with an Access and Mobility Management Function, AMF, entity, and a Unified Data Management, UDM, entity, the wireless device22configured to, and/or comprising processing circuitry configured to:cause transmission of a message indicating the wireless device22is initiating a switch to a first profile associated with a target profile identifier, PID, the indication of the first profile associated with a target PID configured to initiate the UDM to activate the first profile; andone of cause transmission and receive transmission in accordance with the activated first profile associated with the target PID.

Example E2. The wireless device22of Example E1, wherein the processing circuitry is further configured to:receive mobility registration signaling that is configured to cause the wireless device22to re-register with the AMF before using the first profile; andperform mobility registration with the AMF for profile switching.

Example F1. A method implemented in a wireless device22that is configured to communicate with an Access and Mobility Management Function, AMF, entity, and a Unified Data Management, UDM, entity, the method comprising:causing transmission of a message indicating the wireless device22is initiating a switch to a first profile associated with a target profile identifier, PID, the indication of the first profile associated with a target PID configured to initiate the UDM to activate the first profile; andone of causing transmission and receiving transmission in accordance with the activated first profile associated with the target PID.

Example F2. The method of Example F1, further comprising:receiving mobility registration signaling that is configured to cause the wireless device22to re-register with the AMF before using the first profile; andperforming mobility registration with the AMF for profile switching.