Method and device for reconfiguring a data connection

Abstract

The present invention relates to a method and apparatus for reconfiguring a data connection. An apparatus and method for reconfiguring a data connection using new parameters are disclosed. An apparatus (300) includes: a processor (305) and a transceiver (325), the transceiver (325) communicating with a mobile communication network. The processor (305) establishes (605) a data connection with the mobile communication network using a first set of parameters, and receives (610) from the mobile communication network a second set of parameters and an indication of how at least one parameter in the first set corresponds to at least one new parameter in the second set. The processor (305) further determines (615) a third set of parameters from the first set of parameters and the second set of parameters, and reconfigures (620) the data connection using the third set of parameters.

Description

[0001] This application is a divisional application of the application with PCT application number PCT / EP2017 / 060958, international filing date of May 8, 2017, Chinese application number 201780090471.8, and invention title "Method and apparatus for reconfiguring a data connection", which entered the Chinese national phase on November 6, 2019. Technical Field

[0002] The subject matter disclosed herein generally relates to wireless communications, and more particularly to reconfiguring a data connection by using new parameters. Background Art

[0003] The following abbreviations and acronyms are defined herein, at least some of which are referred to in the description below.

[0004] 3rd Generation Partnership Project (“3GPP”), Acknowledgement (“ACK”), Access and Mobility Management Function (“AMF”), Common Control Plane Network Function (“CCNF”), Control Plane Function (“CPF”), Data Network Name (“DNN”), Downlink (“DL”), Enhanced Mobile Broadband (“eMBB”), evolved Node B (“eNB”), European Telecommunications Standards Institute (“ETSI”), Hybrid Automatic Repeat reQuest (“HARQ”), Internet of Things (“IoT”), Internet Protocol (“IP”), Long Term Evolution (“LTE”), LTE-Advanced (“LTE-A”), Media Access Control (“MAC”), Machine Type Communication (“MTC”), massive IoT (“mIoT”), massive MTC (“mMTC”), NarrowBand (“NB”), Negative Acknowledgement (“NACK”) or (“NAK”), Network Function (“NF”), Network Slice Instance (“NSI”), Network Slice Selection Assistance Information (“NSSAI”), Network Slice Selection Function (“NSSF”), Network Slice Selection Policy (“NSSP”), next generation Node B (“gNB”), Non-Access Stratum (“NAS”), Primary Cell (“PCell”), Public Land Mobile Network (“PLMN”), Quality of Service (“QoS”), Radio Access Network (“RAN”), Radio Resource Control (“RRC”), Receive (“RX”), Session Management (“SM”), Session Management Function (“SMF”), Secondary Cell (“SCell”), single NSSAI (“S-NSSAI”), Slice Differentiator (“SD”), Slice / Service Type (“SST”), Transmission Control Protocol (“TCP”), Transmission and Reception Point (“TRP”), Transmit (“TX”), Uplink Control Information (“UCI”), User Datagram Protocol (“UDP”), User Equipment / Device (Mobile Terminal) (“UE”), Uplink (“UL”), User Plane Function (“UPF”), Universal Mobile Telecommunications System (“UMTS”), Ultra-Reliable Low-Latency Communication (“URLLC”), and Worldwide Interoperability for Microwave Access (“WiMAX”). As used herein, “HARQ-ACK” may collectively refer to Acknowledgement (“ACK”) and Negative Acknowledgement (“NAK”). ACK refers to the correct reception of a TB, while NAK refers to the incorrect reception of a TB.

[0005] In a 5G network, network slicing allows network operators to divide the communication network into finer-grained small networks optimized for certain functions. A UE may be configured with network slice-related information (such as a network slice selection policy ("NSSP")) for selecting a specific network slice. During initial UE configuration (e.g., powering on for the first time with a new (U)SIM card), the home public land mobile network (H-PLMN) operator may configure the UE with NSSP policies for the HPLMN itself and specific other PLMNs (e.g., equivalent PLMNs or other visited PLMNs). However, the NSSP is static or semi-static, and if the network configuration changes, the network policy changes, or the UE subscription changes, the NSSP becomes inappropriate. Summary of the Invention

[0006] Disclosed are methods for reconfiguring a data connection using new parameters. Devices and systems also perform the functions of these methods. A method for a UE to reconfigure a data connection using new parameters includes: establishing a data connection with a mobile communication network using a first set of parameters; and the mobile communication network receiving a second set of parameters and an indication of how at least one parameter in the first set corresponds to at least one new parameter in the second set. The method further includes: determining a third set of parameters from the first set and the second set; and reconfiguring the data connection using the third set of parameters.

[0007] A method for a network function to re-register a remote unit using new parameters includes: registering the remote unit with a mobile communication network using a first set of parameters and identifying a second set of parameters to be used by the remote unit in the mobile communication network. The method further includes: sending the second set of parameters and an indication of how at least one parameter in the first set corresponds to at least one new parameter in the second set to the remote unit; and receiving from the remote unit a message including a third set of parameters for registering with the mobile communication network. Here, the third set of parameters is based on the first set and the second set. Brief Description of the Drawings

[0008] A more specific description of the embodiments briefly described above will be presented with reference to specific embodiments illustrated in the drawings. It should be understood that these drawings only depict some embodiments and should not be considered as limiting the scope. The embodiments will be described and illustrated with additional features and details by using the drawings, where:

[0009] Figure 1 is a schematic block diagram illustrating an embodiment of a wireless communication system for reconfiguring a data connection using new parameters;

[0010] Figure 2is a block diagram illustrating an embodiment of a network architecture for reconfiguring a data connection using new parameters;

[0011] Figure 3 is a schematic block diagram illustrating an embodiment of a remote device for reconfiguring a data connection using new parameters;

[0012] Figure 4 is a schematic block diagram illustrating an embodiment of a network function device for re - registering a remote unit using new parameters;

[0013] FIG. 5 is a block diagram illustrating an embodiment of a network process for reconfiguring a data connection using new parameters;

[0014] Figure 6 is a schematic flowchart illustrating an embodiment of a method for reconfiguring a data connection using new parameters; and

[0015] Figure 7 is a schematic flowchart illustrating an embodiment of a method for re - registering a remote unit using new parameters. DETAILED DESCRIPTION

[0016] As will be appreciated by those skilled in the art, various aspects of the embodiments can be embodied as a system, device, method, or program product. Thus, the embodiments can take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, microcode, etc.), or an embodiment combining software and hardware aspects.

[0017] For example, the disclosed embodiments can be implemented as a hardware circuit including custom very - large - scale integration (“VLSI”) circuits or gate arrays, off - the - shelf semiconductors (such as logic chips, transistors, or other discrete components). The disclosed embodiments can also be implemented in programmable hardware devices (such as field - programmable gate arrays, programmable array logic, programmable logic devices, etc.). As another example, the disclosed embodiments can include one or more physical or logical blocks of executable code, which can be organized, for example, as objects, procedures, or functions.

[0018] Furthermore, the embodiments can take the form of a program product embodied in one or more computer - readable storage devices storing machine - readable code, computer - readable code, and / or program code (hereinafter referred to as code). The storage device can be a tangible storage device, a non - transitory storage device, and / or a non - transmissive storage device. The storage device may not contain a signal. In certain embodiments, the storage device only accesses the code using a signal.

[0019] Any combination of one or more computer-readable media can be utilized. The computer-readable media can be a computer-readable storage medium. The computer-readable storage medium can be a storage device that stores code. The storage device can be, by way of example but not limitation: an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, an infrared storage device, a holographic storage device, a micro-mechanical storage device, or a semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

[0020] More specific examples (a non-exhaustive list) of storage devices will include the following: an electrical connection having one or more wires, a portable computer disk, a hard disk, a random access memory (“RAM”), a read-only memory (“ROM”), an erasable programmable read-only memory (“EPROM” or flash memory), a portable compact disc read-only memory (“CD-ROM”), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this disclosure, a computer-readable storage medium can be any tangible medium that can include or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0021] Throughout this specification, references to “one embodiment” or “an embodiment” or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, the phrases “in one embodiment,” “in an embodiment,” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but rather mean “one or more but not all embodiments” unless expressly specified otherwise. The terms “including,” “comprising,” “having,” and variations thereof mean “including but not limited to” unless expressly specified otherwise. A listing of items does not imply that any or all of the items are mutually exclusive unless expressly specified otherwise. The terms “a,” “an,” and “the” also mean “one or more” unless expressly specified otherwise.

[0022] In addition, the described features, structures, or characteristics of the embodiments can be combined in any suitable manner. In the following description, numerous specific details are provided (such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc.) to provide a thorough understanding of the embodiments. However, those of ordinary skill in the relevant art will recognize that the embodiments can be practiced without one or more of these specific details or with other methods, components, materials, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the embodiments.

[0023] Aspects of the embodiments are described below with reference to the schematic flowcharts and / or schematic block diagrams of methods, apparatuses, systems, and program products according to the embodiments. It should be understood that each block in the schematic flowchart and / or schematic block diagram, and combinations of blocks in the schematic flowchart and / or schematic block diagram, can be implemented by code. The code can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine, such that the instructions, when executed via the processor of the computer or other programmable data processing device, create a means for implementing the functions / actions specified in the blocks of the schematic flowchart and / or schematic block diagram.

[0024] The code can also be stored in a storage device that can direct a computer, other programmable data processing device, or other device to operate in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions for implementing the functions / actions specified in the blocks of the schematic flowchart and / or schematic block diagram.

[0025] The code can also be loaded onto a computer or other programmable data processing device or other device to cause a series of operational steps to be performed on the computer, other programmable device, or other device to produce a computer-implemented process, such that the code executed on the computer or other programmable device provides a process for implementing the functions / actions specified in the schematic flowchart and / or schematic block diagram.

[0026] The schematic flowcharts and / or schematic block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods, and program products according to various embodiments. In this regard, each block in the schematic flowchart and / or schematic block diagram can represent a module, segment, or portion of code, which includes one or more code-executable instructions for implementing the specified logical function(s).

[0027] It should also be noted that in some alternative implementations, the functions recited in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may in fact be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks or portions thereof shown in the figures.

[0028] The description of the elements in each figure may refer to the elements in the figure being described. Like numerals in all figures represent like elements, including alternative embodiments of like elements.

[0029] To provide dynamic NSSAI configuration in a UE, the network may determine that one or more parameters in a first parameter set (e.g., those used for registering the UE and / or establishing a data connection) are not valid for the current network slice instance. The network then provides a second parameter set, whereby the UE may reconfigure its data connection and / or re-register with the network. The network may also send assistance information to indicate how to use the new parameter set.

[0030] Figure 1 FIG. 4 depicts a wireless communication system 100 for reconfiguring a data connection using new parameters, in accordance with an embodiment of the present disclosure. In one embodiment, the wireless communication system 100 includes a remote unit 105, a base station unit 110, and a communication link 115. Even though Figure 1 a specific number of remote units 105, base station units 110, and communication links 115 are depicted in FIG. 4, those skilled in the art will recognize that any number of remote units 105, base station units 110, and communication links 115 may be included in the wireless communication system 100.

[0031] In one implementation, the wireless communication system 100 conforms to a 5G system specified in 3GPP specifications. However, more generally, the wireless communication system 100 may implement some other open or proprietary communication networks, such as LTE or WiMAX, and other networks. The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.

[0032] In one embodiment, the remote unit 105 may include a computing device, such as a desktop computer, a laptop computer, a personal digital assistant (“PDA”), a tablet computer, a smart phone, a smart TV (e.g., a TV connected to the Internet), a smart home appliance (e.g., a home appliance connected to the Internet), a set-top box, a game console, a security system (including security cameras), an in-vehicle computer, a network device (e.g., a router, a switch, a modem), etc. In some embodiments, the remote unit 105 includes a wearable device, such as a smart watch, a fitness band, an optical head-mounted display, etc. Additionally, the remote unit 105 may be referred to as a subscriber unit, a mobile device, a mobile station, a user, a terminal, a mobile terminal, a fixed terminal, a subscriber station, a UE, a user terminal, a device, or by other terminology used in the art. The remote unit 105 may communicate directly with one or more base station units 110 via uplink (“UL”) and downlink (“DL”) communication signals. Additionally, the UL and DL communication signals may be carried via the communication link 115.

[0033] Base station unit 110 can be distributed over a geographical area. In some embodiments, base station unit 110 may also be referred to as an access terminal, a base, a base station, Node B, eNB, gNB, home Node B, relay node, femtocell, access point, device, or by any other terminology used in the art. Base station unit 110 is generally part of a radio access network (“RAN”), which may include one or more controllers communicatively coupled to one or more corresponding base station units 110. These and other elements of the radio access network are not illustrated, but are generally well known to those of ordinary skill in the art. Base station unit 110 is connected to mobile core network 130 via the RAN.

[0034] Base station unit 110 can serve a number of remote units 105 within a service area (e.g., a cell or a cell sector) via a wireless communication link. Base station unit 110 can communicate directly with one or more remote units 105 via communication signals. Generally, base station unit 110 transmits downlink (“DL”) communication signals in the time domain, frequency domain, and / or spatial domain to serve remote units 105. Additionally, the DL communication signals can be carried via communication link 115. Communication link 115 can be any suitable carrier in the licensed or unlicensed radio spectrum. Communication link 115 facilitates communication between one or more remote units 105 and / or one or more base station units 110.

[0035] In one embodiment, mobile core network 130 is a 5G Core (“5GC”), which can be coupled to data network 160, such as the Internet and private data networks and other data networks. In some embodiments, remote unit 105 communicates with remote host 165 via a network connection to mobile core network 130. Each mobile core network 130 belongs to a single public land mobile network (“PLMN”). The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.

[0036] Mobile core network 130 includes a number of network functions (“NFs”) and multiple network slices 155. As depicted, mobile core network 130 includes at least one access and mobility management function (“AMF”) 135, at least one session management function (“SMF”) 140, at least one user plane function (“UPF”) 145, and at least one network slice selection function (“NSSF”) 150. Although a specific number of NFs are depicted Figure 1 in, those skilled in the art will recognize that any number of NFs can be included in mobile core network 130.

[0037] AMF 135 and SMF 140 are examples of control plane network functions of the mobile core network 130. The control plane network functions provide services such as UE registration, UE connection management, UE mobility management, data session management, etc. The UPF 145 provides user plane (e.g., data) services to the remote unit 105. For example, the data connection between the remote unit 105 and the data network 165 is managed through the UPF 145.

[0038] The NSSF 150 selects an appropriate network slice 155 (and network slice instance) for a particular UE connection. The NSSF 150 can be a stand-alone NF or can be collocated with the AMF 135 or another NF (e.g., NRF or PCF). The network slice 155 is a logical network within the mobile core network 130. The network slice 155 is a partition of the resources and / or services of the mobile core network 130. Different network slices 155 can be used to meet different service requirements (e.g., latency, reliability, and capacity). Examples of different types of network slices 155 include enhanced mobile broadband (“eMBB”), massive machine type communication (“mMTC”), and ultra-reliable low latency communication (“URLLC”). The mobile core network 130 can include multiple network slice instances of the same network slice type.

[0039] As depicted, the remote unit 105 can access the mobile core network 130 (including a particular network slice 155 of the mobile core network 130) via the base station unit 110. However, due to its mobility, the remote unit 105 may move to a part of the network topology where the previous network slice 155 instance is no longer available. Here, one or more parameters used to establish the data connection (e.g., using the SMF 140) become invalid, and the data connection terminates. As described in more detail below, the AMF 135 can transmit new parameters to the remote unit 105, where the remote unit 105 uses the new parameters to re-establish the data connection.

[0040] Figure 2FIG. 200 depicts a network architecture for reconfiguring a data connection using new parameters according to an embodiment of the present disclosure. The network architecture 200 may be a simplified embodiment of a wireless communication system 100. As depicted, the network architecture 200 includes a UE 205, a 5G(R)AN 210, a first network slice instance (herein “NSI-1”) 215, a second network slice instance (herein “NSI-2”) 220, and a set of common control plane network functions (“CCNF”) 225. The set of common control plane network functions 225 may at least include an AMF, an NSSF, and a UDM. Each network slice instance also has dedicated network functions. Here, the first network slice instance 215 includes a control plane 230 having a first SMF 235 (“SMF-a”) and other dedicated network functions 240, and a first UPF 245 (“UPF-a”). Additionally, the second network slice instance 220 includes a control plane 230 having a second SMF 250 (“SMF-b”) and other dedicated network functions 240, and a second UPF 255 (“UPF-b”).

[0041] As described above, the UE 205 may be an embodiment of the remote unit 105, and the 5G(R)AN 210 may include one or more base station units 110. The first network slice instance 215 and the second network slice instance 220 may be embodiments of the network slice 155. Additionally, the first SMF 235 and the second SMF 250, and the first UPF 245 and the second UPF 255 may be embodiments of the SMF 140 and the UPF 145, respectively. The 5G(R)AN 210, the set of common control plane network functions 225, and the network slice instances 215, 220 (and their dedicated network functions) together form a mobile communication network with which the UE 205 communicates.

[0042] In the network architecture 200, the UE 205 may communicate with the 5G(R)AN 210 using the Uu interface, the 5G(R)AN 210 may communicate with the set of common control plane network functions 225 using the N2 interface, and communicate with the first UPF 245 and the second UPF 255 using the N3 interface. The first SMF 235 and the first UPF 245 may communicate using the N4 interface. Similarly, the second SMF 250 and the second UPF 255 may also communicate using the N4 interface. The set of common control plane network functions 225 may communicate with the control plane 230 within the first network slice instance 215 and the second network slice instance 220 using the N11 interface.

[0043] The UE 205 may be configured with network slice related information, which is referred to as Network Slice Selection Assistance Information (“NSSAI”). The NSSAI may consist of a single or multiple S-NSSAIs (Single Network Slice Selection Assistance Information). Each S-NSSAI includes a Slice / Service Type (“SST”, which refers to the expected network slice behavior according to characteristics and services) and a Slice Differentiator (“SD”, which allows for further differentiation to select an NSI from multiple potentially available NSIs that conform to the SST).

[0044] In some embodiments, the network operator may provide a Network Slice Selection Policy (“NSSP”) to the UE 205. The NSSP includes one or more NSSP rules, where each rule is associated with a specific S-NSSAI. When an application associated with a specific S-NSSAI on the UE 205 requests data transmission, the UE 205 uses the PDU session established using the S-NSSAI to send the user data of the application. In certain embodiments, the application may provide a Data Network Name (“DNN”). In such embodiments, when determining which PDU session to use (from among the potentially multiple PDU sessions established using the S-NSSAI), the UE 205 also considers the DNN.

[0045] Multiple Network Slice Instances (“NSIs”) are deployed in the network architecture 200, including a first NSI 215 and a second NSI 220. The NSIs do not necessarily cover the entire PLMN area; instead, different NSIs are deployed in different topological regions. The topological regions can be represented by a Tracking Area (“TA”, identified by a Tracking Area Identifier (“TAI”)) or a list of tracking areas or a cell (identified by a cell ID) or a list of cells. Generally, in a given topological network area (e.g., a TA or a list of TAI, or a cell or a list of cell IDs), the configuration of the deployed / instantiated (one or more) NSIs does not change. However, in another topological region, the deployed NSIs will be different.

[0046] (In the network) The association between the S-NSSAI and the NSI is based on network configuration and deployment. This association between the S-NSSAI and the NSI can change in a timely manner based on network reconfiguration or resource optimization. Different scenarios can exist for the association / relationship between the S-NSSAI and the NSI. In one embodiment, there can be a one-to-one mapping between the S-NSSAI and the NSI. In another embodiment, there can be a many-to-one mapping between the S-NSSAI and the NSI. In yet another embodiment, there can be a one-to-many mapping between the S-NSSAI and the NSI.

[0047] As depicted, the UE 205 exchanges signaling 260 with a set of common control plane network functions 225 (specifically with the AMF 135 within the set of common control plane network functions 225) to register with the network (e.g., using a first set of one or more S-NSSAIs), receive new network parameters (e.g., a new S-NSSAI), and re-register with the network (e.g., using the new S-NSSAI), as described herein. One or more NSIs in the NSI serving the UE 205 may change for several reasons (e.g., the UE moves from an old registration area to a new registration area, or the network configuration changes, etc.). The UE 205 is not aware of the configuration of the NSIs in the old and new registration areas. To notify the UE 205 of the change in the NSIs associated with the UE 205, the network (e.g., the AMF in the set of common control plane network functions 225) assigns a new set of new parameters to the UE (e.g., changes the set of permitted / accepted S-NSSAIs), and also provides usage information indicating to the UE 205 how to use the new set of parameters. As used herein, "usage information" refers to an indication of how the UE 205 uses / applies the new set of parameters. "Usage information" may also be referred to herein as "mapping indication" or "NSSAI assistance information".

[0048] As discussed further below in detail, after receiving the new set of parameters and an indication of how to use the new set of parameters (e.g., receiving usage information for the new set of parameters), the UE 205 re-registers with the set of common control plane network functions 225. In the case where a PDU session has been established upon receiving the new set of parameters, the UE 205 may also use the new set of parameters to re-establish the PDU session (or use the new set of parameters to establish a new PDU session).

[0049] Figure 3 An embodiment of a remote device 300 for reconfiguring a data connection using new parameters in accordance with an embodiment of the present disclosure is depicted. The remote device 300 may be an embodiment of the remote unit 105, the relay unit 120, the remote UE 205, and / or the relay UE 210. Additionally, the remote device 300 includes a processor 305, a memory 310, an input device 315, a display 320, and a transceiver 325. In some embodiments, the input device 315 and the display 320 are combined into a single device, such as a touch screen. In certain embodiments, the remote unit 105 may not include any input device 315 and / or display 320.

[0050] The transceiver 325 allows the remote device 300 to communicate with a mobile communication network (e.g., the mobile core network 130 and / or network slice instances 215, 220) via an access network (e.g., the base station unit 110 and / or 5G(R)AN 210). The transceiver 325 may include at least one transmitter 330 and at least one receiver 335. Additionally, the transceiver 325 may support at least one network interface 340, such as the "Uu" interface for communicating with the base station unit 110 or 5G(R)AN 210.

[0051] In one embodiment, the processor 305 may include any known controller capable of executing computer-readable instructions and / or capable of performing logical operations. For example, the processor 305 may be a microcontroller, a microprocessor, a central processing unit ("CPU"), a graphics processing unit ("GPU"), an auxiliary processing unit, a field-programmable gate array ("FPGA"), or a similar programmable controller. In some embodiments, the processor 305 executes instructions stored in the memory 310 to perform the methods and routines described herein. The processor 305 is communicatively coupled to the memory 310, the input device 315, the display 320, and the transceiver 325.

[0052] In some embodiments, the processor 305 uses a first set of parameters to establish a data connection with the mobile communication network. Here, the first set of parameters may include network slice selection parameters and a data network name. At some point after the data connection is established, the processor 305 receives a second set of parameters from the mobile communication network. Along with the second set of parameters, the processor 305 receives an indication of how at least one parameter in the first set (e.g., the set used to establish the data connection) corresponds to at least one new parameter in the second set. The processor 305 also determines a third set of parameters from the first set of parameters and the second set of parameters. Then, the processor 305 controls the transceiver 325 to reconfigure the data connection using the third set of parameters.

[0053] In some embodiments, the processor 305 receives an indication that at least one parameter in the first set (e.g., the set used to establish the data connection) is no longer valid. For example, a message including the second set of parameters (and corresponding indicators) may indicate that at least one parameter in the first set is no longer valid. In one embodiment, receiving an indication that at least one parameter in the first set is no longer valid includes: the processor receiving an indication that the data connection has been interrupted (e.g., released).

[0054] In some embodiments, reconfiguring a data connection may include: the processor 305 re - establishing the data connection using a third set of parameters. In one embodiment, re - establishing the data connection includes: the processor 305 sending a non - access stratum (“NAS”) session management message including the third set of parameters. In another embodiment, re - establishing the data connection includes: the processor 305 sending a session management (“SM”) message (e.g., N1 session management information message) encapsulated in a NAS transport message. Here, the NAS transport message includes the third set of parameters and the N1 SM message, where the N1 SM message includes at least one new parameter (e.g., a new S - NSSAI) from the second set of parameters.

[0055] In some embodiments, reconfiguring a data connection includes one of the following: the processor 305 re - establishing the data connection using a third set of parameters, the processor 305 establishing a new data connection using a fourth set of parameters based on the second set of parameters, and the processor 305 releasing the data connection. For example, the processor 305 may determine to release the data connection in response to determining that a third set of parameters cannot be created (e.g., an invalid combination / set of parameters is generated).

[0056] In some embodiments, the first set of parameters includes first network slice selection parameters. Here, the second set of parameters includes one or more new network slice selection parameters. In one embodiment, the processor 305 receives an indication of how at least one parameter in the first set corresponds to at least one new parameter in the second set by receiving usage information associating one or more new network slice selection parameters with one or more previously provided network slice selection parameters. Here, the one or more previously provided network slice selection parameters include the first network slice selection parameters. In some embodiments, the processor 305 also updates the device's network slice selection configuration based on the one or more new network slice selection parameters.

[0057] In some embodiments, the processor 305 sends a registration request to update the mobile communication network with a new registration area and receives the second set of parameters in response to the registration request. In such an embodiment, receiving the second set of parameters and an indication of how at least one parameter in the first set corresponds to at least one new parameter in the second set may include: the processor 305 receiving a registration acceptance message (e.g., a NAS registration acceptance message), which includes the second set of parameters and an indication of how at least one parameter in the first set corresponds to at least one new parameter in the second set.

[0058] In one embodiment, receiving a second set of parameters and an indication of how at least one parameter in the first set corresponds to at least one new parameter in the second set includes: the processor 305 receiving a configuration update message. In another embodiment, receiving a second set of parameters and an indication of how at least one parameter in the first set corresponds to at least one new parameter in the second set includes: the processor 305 receiving a NAS notification message. In yet another embodiment, receiving a second set of parameters and an indication of how at least one parameter in the first set corresponds to at least one new parameter in the second set includes: the processor 305 receiving a non-access stratum (“NAS”) registration acceptance message.

[0059] In one embodiment, the memory 310 is a computer-readable storage medium. In some embodiments, the memory 310 includes volatile computer storage media. For example, the memory 310 may include RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). In some embodiments, the memory 310 includes non-volatile computer storage media. For example, the memory 310 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 310 includes both volatile computer storage media and non-volatile computer storage media. In some embodiments, the memory 310 stores data related to reconfiguring a data connection using new parameters, such as storing NSSP, permitted NSSAI, etc. In some embodiments, the memory 310 also stores program code and related data, such as an operating system or other controller algorithms operating on the remote unit 105 and one or more software applications.

[0060] In one embodiment, the input device 315 may include any known computer input device, including a touch panel, buttons, a keyboard, a stylus, a microphone, etc. In some embodiments, the input device 315 may be integrated with the display 320, for example, as a touch screen or a similar touch-sensitive display. In some embodiments, the input device 315 includes a touch screen such that text can be input by using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. In some embodiments, the input device 315 includes two or more different devices, such as a keyboard and a touch panel.

[0061] In one embodiment, the display 320 may include any known electronically controllable display or display device. The display 320 may be designed to output visual signals, auditory signals, and / or tactile signals. In some embodiments, the display 320 includes an electronic display capable of outputting visual data to a user. For example, the display 320 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or a similar display device capable of outputting images, text, etc. to a user. As another non-limiting example, the display 320 may include a wearable display, such as a smartwatch, smart glasses, a heads-up display, etc. Further, the display 320 may be a component of a smartphone, a personal digital assistant, a television, a desktop computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, etc.

[0062] In certain embodiments, the display 320 includes one or more speakers for generating sound. For example, the display 320 may generate an audible alert or notification (e.g., a beep or a ring). In some embodiments, the display 320 includes one or more haptic devices for generating vibration, movement, or other tactile feedback. In some embodiments, all or a portion of the display 320 may be integrated with the input device 315. For example, the input device 315 and the display 320 may form a touchscreen or a similar touch-sensitive display. In other embodiments, the display 320 may be located near the input device 315.

[0063] The transceiver 325 communicates with a mobile communication network via an access network (e.g., base station unit 110 and / or 5G(R)AN 210). The transceiver 325 operates under the control of the processor 305 to transmit messages, data, and other signals, and also to receive messages, data, and other signals. For example, the processor 305 may selectively activate the transceiver 325 (or a portion thereof) at a particular time to transmit and receive messages. The transceiver 325 may include one or more transmitters 330 and one or more receivers 335 for communicating via the access network. As discussed above, the transceiver 325 may support one or more network interfaces 340 for communicating with a mobile communication network (e.g., various network functions in the base station unit 110 and the mobile core network 130).

[0064] Figure 4An embodiment of a network function device 400 is depicted that can be used to reconfigure a data connection using new parameters and / or re-register a remote unit using new parameters in accordance with an embodiment of the present disclosure. The network function device 400 can be an embodiment of the AMF 135. Additionally, the network function device 400 includes a processor 405, a memory 410, an input device 415, a display 420, and a transceiver 425. In some embodiments, the input device 415 and the display 425 are combined into a single device, such as a touchscreen. In certain embodiments, the network function device 400 may not include any input device 415 and / or display 420.

[0065] The transceiver 425 allows the network function device 400 to communicate with other network elements within a mobile communication network. As depicted, the transceiver 425 includes at least one transmitter 430 and at least one receiver 435. Additionally, the transceiver 425 may support at least one network interface 440, such as an "N2" interface for communicating with the 5G(R)AN 210 and an "N11" interface for communicating with a control plane network function, such as the SMF 140.

[0066] In one embodiment, the processor 405 can include any known controller capable of executing computer-readable instructions and / or capable of performing logical operations. For example, the processor 405 can be a microcontroller, a microprocessor, a central processing unit ("CPU"), a graphics processing unit ("GPU"), an auxiliary processing unit, a field programmable gate array ("FPGA"), or a similar programmable controller. In some embodiments, the processor 405 executes instructions stored in the memory 410 to perform the methods and routines described herein. The processor 405 is communicatively coupled to the memory 410, the input device 415, the display 420, and the transceiver 425.

[0067] In some embodiments, the processor 405 registers a remote unit with the mobile communication network using a first set of parameters. Here, the processor 405 can receive an initial registration message from the remote unit, the initial registration message including a set of requested network slice selection parameters. In such an embodiment, the processor 405 can return a set of allowed network slice selection parameters to the remote unit. In certain embodiments, the set of allowed network slice selection parameters can include one or more default network slice selection parameters. Here, returning the set of allowed network slice selection parameters includes: the processor sending an indication that the default network slice selection parameter corresponds to one of the following: a data network name and a standardized network slice type. For example, a new S-NSSAI can have a PLMN-specific SST that maps to a well-known standardized SST.

[0068] At a certain moment, the processor 405 identifies a second set of parameters to be used by the remote unit in the mobile communication network. Here, the second set of parameters corresponds to a change in the network slice instance ("NSI") of the remote unit. In one embodiment, the NSI changes due to the mobility of the remote unit. For example, the remote unit may move to a registration area corresponding to a new NSI (e.g., in the network topology). In another embodiment, the change in the NSI may be due to a subscription (e.g., plan) of the remote unit or a change in the network policy rules applicable to the remote unit. Here, the change in the subscription or policy may result in the remote unit no longer being allowed to use the old NSI. In yet another embodiment, the change in the NSI may be due to a change in the network slice deployment within the mobile communication network. For example, the mobile communication network may provide a new network slice serving the area where the remote unit is located online.

[0069] When the NSI changes, one or more parameters in the first set of parameters may no longer be valid. In this case, the processor 405 identifies a second set of parameters to be used by the remote unit in the mobile communication network and sends the second set of parameters to the remote unit together with an indication of how at least one parameter in the first set of parameters corresponds to at least one new parameter in the second set. In one embodiment, the second set of parameters includes the first set of parameters and one or more additional (new) parameters applicable to the new NSI. In another embodiment, the second set of parameters includes a subset of the first set of parameters and one or more additional (new) parameters that replace the parameters in the first subset for the new NSI. In yet another embodiment, the second set of parameters may include a subset of the first set of parameters without any replacement parameters. Note that the size of the second set of parameters may be greater than, less than, or the same as the size of the first set of parameters.

[0070] The indication of how at least one parameter in the first set of parameters corresponds to at least one new parameter in the second set notifies the remote unit of how to use the second set of parameters based on the known usage information related to the first set of parameters. For example, if "Parameter - B" in the second set corresponds to "Parameter - A" in the first set, the remote unit knows that it can use Parameter - B in the same situations where it can use Parameter - A. Here, it is assumed that the remote unit already knows when to use the first set of parameters before receiving the indication of how at least one parameter in the first set of parameters corresponds to at least one new parameter in the second set.

[0071] In response to sending the second set of parameters (and the corresponding indication), the processor 405 may receive a message from the remote unit that includes a third set of parameters for registering with the mobile communication network. Here, the third set of parameters is based on the first set of parameters and the second set of parameters.

[0072] In one embodiment, identifying the second parameter set may include: the processor 405 identifying the second parameter set based on a set of requested network slice selection parameters (e.g., the requested S-NSSAI), subscription parameters of the remote unit (e.g., the subscribed S-NSSAI), and / or a network slice instance associated with the remote unit. In another embodiment, identifying the second parameter set includes: the processor 405 identifying the second parameter set based on the configuration of the remote unit and the network slice instance currently associated with the remote unit.

[0073] In some embodiments, the first parameter set includes first network slice selection parameters. Here, identifying the second parameter set may include: the processor 405 identifying one or more new network slice selection parameters for the network slice instance currently associated with the remote unit. Further, sending an indication of how at least one parameter in the first set corresponds to at least one new parameter in the second set may include: the processor 405 sending usage information associating one or more new network slice selection parameters with one or more previously provided network slice selection parameters, where the one or more previously provided network slice selection parameters include the first network slice selection parameters.

[0074] In some embodiments, the processor 405 receives a registration request from the remote unit and determines that at least one parameter in the first parameter set is no longer valid in response to the registration request. In such an embodiment, sending the second parameter set and an indication of how at least one parameter in the first set corresponds to at least one new parameter in the second set may include: the processor 405 sending a registration acceptance message (e.g., a NAS registration acceptance message), which includes the second parameter set and an indication of how at least one parameter in the first set corresponds to at least one new parameter in the second set. The processor 405 may receive the registration request in response to one of the following: the remote unit changing its registration area, the remote unit changing its public land mobile network (“PLMN”) change, and the remote unit needing to temporarily use a network slice.

[0075] In certain embodiments, the processor 405 sends the second parameter set and an indication of how at least one parameter in the first set corresponds to at least one new parameter in the second set by sending one of the following: a configuration update message and a NAS notification message. In some embodiments, the processor 405 receives a message including a third parameter set from the remote unit by receiving a session management (“SM”) request message encapsulated in a NAS transport message. Here, the NAS transport message includes the third parameter set and a session management message, and the SM request message includes at least one new parameter from the second parameter set.

[0076] In some embodiments, the processor 405 may send a session management (SM) request message to the SM function in response to determining that at least one parameter in the first set is no longer valid. Here, the SM request message may include an indication to release an established data connection and new network slice selection parameters from a second set of parameters, and at least one new parameter included in the session management message may be the new network slice selection parameters. In another embodiment, the processor 405 also receives an SM response message from the SM function, the SM response message including a session release request message for the established data connection, wherein the processor 405 sends the session release request message to the remote unit.

[0077] In some embodiments, in response to receiving a registration request from a remote unit, the processor 405 identifies a second set of parameters to be used by the remote unit in a mobile communication network by sending a query to a network slice selection function (“NSSF”). In such an embodiment, the processor 405 may receive a mapping of network slice selection parameters to network slice instances from the NSSF. Here, identifying the second set of parameters further includes: the processor 405 identifying a set of allowed network slice selection parameters based on the network slice instance currently associated with the remote unit. Note that the NSSF may be a stand-alone NF in the mobile communication network or may be part of another NF (such as, the NRF or the PCF).

[0078] In one embodiment, the memory 410 is a computer-readable storage medium. In some embodiments, the memory 410 includes a volatile computer storage medium. For example, the memory 410 may include RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). In some embodiments, the memory 410 includes a non-volatile computer storage medium. For example, the memory 410 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 410 includes both a volatile computer storage medium and a non-volatile computer storage medium. In some embodiments, the memory 410 stores data related to reconfiguring a data connection and / or re-registering the UE using new parameters, e.g., stores UE configuration, UE context, allowed NSSAI for the UE, etc. In certain embodiments, the memory 410 also stores program code and related data, such as an operating system or other controller algorithms operating on the network function device 400 and one or more software applications.

[0079] In one embodiment, the input device 415 may include any known computer input device, including a touch panel, buttons, a keyboard, a stylus, a microphone, etc. In some embodiments, the input device 415 may be integrated with the display 420, for example, as a touch screen or a similar touch-sensitive display. In some embodiments, the input device 415 includes a touch screen such that text can be input by using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. In some embodiments, the input device 415 includes two or more different devices, such as a keyboard and a touch panel.

[0080] In one embodiment, the display 420 may include any known electronically controllable display or display device. The display 420 may be designed to output visual signals, auditory signals, and / or tactile signals. In some embodiments, the display 420 includes an electronic display capable of outputting visual data to a user. For example, the display 420 may include, but is not limited to: an LCD display, an LED display, an OLED display, a projector, or a similar display device capable of outputting images, text, etc. to a user. As another non-limiting example, the display 420 may include a wearable display, such as a smartwatch, smart glasses, a heads-up display, etc. Further, the display 420 may be a component of a smart phone, a personal digital assistant, a television, a desktop computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, etc.

[0081] In certain embodiments, the display 420 includes one or more speakers for generating sound. For example, the display 420 may generate an audible alert or notification (e.g., a beep or a ring). In some embodiments, the display 420 includes one or more haptic devices for generating vibration, movement, or other haptic feedback. In some embodiments, all or a portion of the display 420 may be integrated with the input device 415. For example, the input device 415 and the display 420 may form a touch screen or a similar touch-sensitive display. In other embodiments, the display 420 may be located near the input device 415.

[0082] The transceiver 425 communicates with one or more network functions of a mobile communication network. The transceiver 425 operates under the control of the processor 405 to send messages, data, and other signals, and also to receive messages, data, and other signals. For example, the processor 405 may selectively activate the transceiver (or a portion thereof) at a particular time to send and receive messages. The transceiver 425 may include one or more transmitters 430 and one or more receivers 435. As discussed above, the transceiver 425 may support one or more network interfaces 440 for communicating with one or more network functions, such as the SMF 140.

[0083] Figure 5A and Figure 5B depicts a network procedure 500 for reconfiguring a data connection using new parameters according to an embodiment of the present disclosure. The network procedure 500 starts in Figure 5A and continues in Figure 5B The network procedure 500 involves UE 205, 5G(R)AN 210, AMF 135, a first SMF (“SMF-a”) 235, a first UPF (“UPF-b”) 245, a second SMF (“SMF-b”), and a second UPF (“UPF-b”). In some embodiments, the network procedure 500 involves NSSF 150; however, NSSF 150 is optional.

[0084] The network procedure 500 starts at Figure 5A with an initial registration of UE 205 to AMF 135 (see block 502). In some embodiments, UE 205 sends a NAS registration request message and receives a NAS registration acceptance message. During the initial registration procedure (or attachment procedure), UE 205 registers with a specific PLMN (e.g., to a mobile communication network) and obtains services from the network. The initial registration procedure includes: authenticating UE 205, setting up the required security for the control plane and user plane, etc.

[0085] When registering with the network, UE 205 sends the requested NSSAI to the network. In some embodiments, AMF135 (or optionally, NSSF 150) stores the requested NSSAI in the registration management (RM) context of UE 205. In response, AMF 135 sends an allowed (also referred to as accepted) NSSAI to UE 205. In some embodiments, AMF 135 queries NSSF 150 to determine the allowed NSSAI for UE 205. In some embodiments, when determining the allowed NSSAI for a UE, the network (e.g., AMF 135 and / or NSSF 150) considers the configuration in the UE (e.g., the configured NSSAI per PLMN as part of the NSSP) if available. The set of allowed S-NSSAIs is also stored in AMF 135 together with the RM context of UE 205.

[0086] In some embodiments, the NSSP of the UE 205 (e.g., the configured NSSAI in the UE) is not available in the network. For example, the AMF 135 (or the PCF) may not have information about the NSSAI configured for the roaming UE 205. As another example, the UE 205 may not send the requested NSSAI in the NAS registration request message. In such an embodiment, the AMF 135 includes the allowed NSSAI including one or more default S-NSSAIs in the NAS registration acceptance message for the UE 205. In the case of multiple default S-NSSAIs, the NAS registration acceptance message may include: an indication (e.g., usage information) for the UE 205 on how to use the default allowed S-NSSAI. Here, the usage information (indication) may indicate the mapping of the S-NSSAI to the subscribed DNN or the mapping of the SST value of the S-NSSAI to a well-known standardized SST value known at the UE. For example, STT = "motor vehicle" is mapped to SST = "V2X" because the UE does not understand "motor vehicle" but does understand "V2X".

[0087] For example, in the case where the V-PLMN uses a carrier-specific value for the SST part of the S-NSSAI, the AMF 135 may determine that an additional indication for using the allowed S-NSSAI (e.g., the mapping of the S-NSSAI to the DNN) needs to be sent. As another example, in the case where there are multiple S-NSSAIs with the same SST type and the SD part may not be clear in the UE 205, the AMF 135 may determine that an additional indication for using the S-NSSAI needs to be sent. In yet another example, the usage information indicates that the allowed S-NSSAI (SST = "motor vehicle", SD = "Mercedes") is mapped to the requested S-NSSAI (SST = "V2X", SD = "BMW"), or the allowed S-NSSAI (SST = "motor vehicle", SD = "car") is mapped to the requested S-NSSAI (SST = "V2X", SD = "Mercedes"). The latter example shows a one-to-one mapping. In still another example, the mapping indication may be in a one-to-many format. For example, the allowed S-NSSAI (SST = "motor vehicle", SD = "car") is mapped to the requested S-NSSAI (SST = "V2X", SD = "Mercedes") and the requested S-NSSAI (SST = "mIoT", SD = "Mercedes"). Note that in the protocol implementation, the SST value (e.g., "V2X" or "motor vehicle" or "mIoT") may be represented by a numerical value (e.g., "001", "002"). Similarly applied to the SD value (e.g., "car" or "Mercedes"), which may also be represented by a numerical value.

[0088] After registering with the network, the UE 205 establishes a PDU session to send / receive data (e.g., IP data or non-IP data) via the mobile communication network (see block 504). Here, a first set of parameters (e.g., S-NSSAI, DNN, SSC mode, PDU type, etc.) is used to establish the PDU session. For example, the first set of parameters may include: [S-NSSAI-a, DNN-1, SSC1, PDU IP type, etc.]. Here, "S-NSSAI-a" is the first S-NSSAI including specific values for the [SST; SD] combination. In response to a PDU session establishment request using the first set of parameters, the AMF 135 and / or the NSSF 150 assign an NSI to be used for that specific PDU session. In the depicted embodiment, the assigned NSI includes the first SMF 235 and the first UPF 245 for the PDU session serving the UE 205. Returning to Figure 2 , here, the assigned NSI is the first NSI 215.

[0089] Referring again to Figure 5A , at some point in time, an event occurs that makes one or more of the parameters in the first set of parameters unavailable. This event may occur when the UE 205 is in a connected state (e.g., CM-CONNECTED) or in an idle state (e.g., CM-IDLE). In some embodiments, this event is initiated by the UE 205. For example, the UE 205 may move to a new registration area that does not support all of the parameters in the first set (e.g., does not support S-NSSAI-a) (see block 506), and the UE 205 sends a registration request to update the network with its new registration area (see signaling 508). Here, the registration request includes the requested NSSAI mentioned above. As another example, the UE 205 may move to a new PLMN that does not support all of the parameters in the first set (e.g., does not support S-NSSAI-a).

[0090] In other embodiments, the event that makes one or more parameters unavailable is a network-initiated event (see block 510). For example, the subscription of the UE 205 may change, where the new subscription does not allow the use of one or more of the parameters in the first set (e.g., does not support S-NSSAI-a). As another example, the network policy applicable to the UE 205 may change, where the new policy does not allow the UE 205 to use one or more of the parameters in the first set (e.g., does not support S-NSSAI-a). In yet another example, the deployment of the NSI may change, where the new deployment does not support one or more of the parameters in the first set (e.g., does not support S-NSSAI-a).

[0091] In response to the event, the AMF 135 (and / or together with the NSSF 150) determines one or more parameters in the first set of parameters for establishing a PDU session that can no longer be used (see block 512). By doing so, the AMF 135 (and / or together with the NSSF 150) determines a modification to the set of (one or more) network slices for the UE (e.g., for UE 205). For example, the AMF 135 may determine that in the new registration area of the UE 205, S-NSSAI-a cannot be used. In some embodiments, the data connection (PDU session) of the UE 205 may be interrupted (e.g., released) as a result.

[0092] In some embodiments, the network determines that the set of network slices currently associated with the UE 205 is modified. This determination may occur in a single NF (e.g., the AMF 135) or multiple NFs (including, for example, the AMF 135, the NSSF 150, the PCF, the NRF, etc.). In one embodiment, this determination takes into account the configuration of the UE 205 (e.g., the configured NSSAI per PLMN as part of the NSSP of the UE 205). In another embodiment, this determination takes into account the requested NSSAI (if available) that stores the RM context of the UE 205. In yet another embodiment, this determination takes into account both the configuration of the UE 205 and the requested NSSAI.

[0093] If the network determines that one or more allowed S-NSSAIs may not be known in the UE 205, the serving PLMN provides additional information on how to use the new allowed NSSAIs in the UE 205 (e.g., provides usage information that maps the (one or more) new allowed S-NSSAIs to the corresponding (one or more) old allowed S-NSSAIs or the corresponding (one or more) old requested S-NSSAIs). The network (e.g., the AMF 135 and / or together with the NSSF 150) determines that one or more new allowed S-NSSAIs may not be known in the UE 205 based on the following mechanism.

[0094] The AMF 135 stores the requested NSSAI from the initial registration procedure and, together with the subscribed NSSAI, the AMF 135 determines whether a specific new allowed S-NSSAI to be provided to the UE 205 is known in the UE 205 (e.g., whether the specific allowed S-NSSAI is part of the configured NSSAI of the UE 205 for the serving PLMN). Note that in the serving PLMN, the set of allowed S-NSSAIs provided to the UE 205 may change after the registration time (e.g., due to UE mobility or changed network configuration). The network (e.g., the AMF 135 and / or together with the NSSF 150) determines the set of allowed S-NSSAIs based on the complete set of the requested S-NSSAI and the subscribed S-NSSAI. Also note that one or more of the provided set of (one or more) allowed S-NSSAIs may have a PLMN-specific SST value or SD value that is unknown in the UE 205 because, for example, those S-NSSAIs are not part of the configured S-NSSAI for the PLMN.

[0095] In some embodiments, the network determines that the NSI associated with the UE 205 has changed, but no NSSAI reconfiguration is required in the UE 205. For example, the set of allowed NSSAIs that have been provided to the UE does not change despite the NSI change.

[0096] In some embodiments, the AMF 135 sends an N11 SM request message (see signaling 514) including a trigger for initiating a PDU session release procedure to the first SMF 235 (e.g., SMF-a). In certain embodiments, the AMF 135 includes (among other N11 parameters for identifying the N11 signaling transaction itself, such as including the AMF ID or SMF ID or other transaction ID), a new S-NSSAI (e.g., S-NSSAI-b) to be used by the UE 205 when the UE 205 re-establishes the PDU session. Here, the AMF 135 determines whether to include the new S-NSSAI in the N11 SM request message based on the need to change the allowed S-NSSAI configured in the UE 205. Considering the stored set of allowed S-NSSAIs, the AMF 135 (and / or together with the NSSF 150) can determine whether the UE 205 can continue to use the same set of allowed S-NSSAIs indicated during the initial registration. However, in some embodiments, due to an NSI change (e.g., because one or more parameters for establishing the PDU session become unavailable / invalid), it may be necessary to re-establish a previously established PDU session. For example, the AMF 135 may determine that the stored set of allowed S-NSSAIs has not changed; however, due to the NSI change, it may still be necessary to re-establish the established PDU session with another S-NSSAI that is part of the stored set of allowed S-NSSAIs.

[0097] In response to the N11 SM request message, the first SMF 235 initiates an N4 release procedure with the first UPF 245 (e.g., UPF-a) to release the user plane resources (see box 516). After the N4 release procedure, the first SMF 245 generates an N11 SM response message and sends it to the AMF 135 (see signaling 518). Here, the N11 SM response message includes N11 information (e.g., including the AMF ID or SMF ID or other transaction ID) to be used in the AMF 135 for identifying the N11 signaling transaction itself and an N1 SM information container including a PDU session release request message. The PDU session release request message includes the PDU session ID (and other parameters for identifying the PDU session at the UE 205), and additionally, includes a new parameter set (e.g., S-NSSAI-b) for indicating to the UE 205 that the PDU session can be re-established, for example, with a new parameter set (e.g., new S-NSSAI-b), and an appropriate cause value.

[0098] Now refer to Figure 5BWhen the AMF 135 (and / or NSSF 150) determines that the set of allowed S-NSSAIs associated with the UE 205 needs to be changed, there are several scenarios that may occur regarding the modification of the set of (one or more) network slices for the UE (e.g., UE 205).

[0099] In a first embodiment, a network slice instance (NSI) becomes unavailable for the UE 205 (e.g., due to a change in the set of NSIs for the UE). Here, the network slice instance corresponds to the S-NSSAI that is part of the old allowed NSSAI. In such an embodiment, the AMF 135 initiates, for example, a registration management procedure or a UE configuration update procedure to send the new allowed NSSAI that does not include the unavailable old S-NSSAI (see signaling 520). The UE 205 determines how to use the new parameters based on the usage information included in the new parameters (see block 524). Additionally, the network initiates a PDU session release procedure and indicates that the (one or more) PDU sessions have been released due to the no longer available associated S-NSSAI (see signaling 522). In one embodiment, the UE 205 may re-establish the PDU session using another default S-NSSAI part of the allowed NSSAI (see block 526, signaling 528). In another embodiment, when the associated (one or more) S-NSSAIs are not part of the allowed NSSAI, the UE 205 releases the PDU session and does not initiate a PDU session establishment.

[0100] In a second embodiment, a new additional network slice instance becomes available for the UE 205 (e.g., due to a change in the set of NSIs for the UE). Here, the new network slice instance corresponds to the new S-NSSAI that is not part of the allowed NSSAI in the UE 205. In such an embodiment, the AMF 135 may initiate, for example, a registration management procedure or a UE configuration update procedure to send the new allowed NSSAI that includes the new additional S-NSSAI (see signaling 520). The UE 205 determines how to use the new parameters based on the usage information included in the new parameters (see block 524). Based on the UE configuration (e.g., NSSP policy), the UE 205 may initiate a PDU session release and re-establishment procedure to associate the (one or more) existing PDU sessions with the new S-NSSAI, i.e., establish the (one or more) existing PDU sessions on the new network slice instance (see blocks 526, signaling 528).

[0101] In a third embodiment, a new network slice instance corresponding to an S-NSSAI that is already part of the allowed NSSAI becomes available for UE 205 (e.g., due to a change in the set of NSIs for the UE), where the new NSI replaces the old NSI used by UE 205. Here, the network does not need to assign a new allowed NSSAI to UE 205. However, the network (e.g., SMF 235 based on the corresponding trigger from AMF 135 in signaling 514) initiates a PDU session release procedure for the (one or more) PDU sessions associated with the affected S-NSSAI. The PDU session release request message includes an appropriate cause value (e.g., indicating the NSI change) and an indication of the possibility of re-establishment. In such an indicated case, UE 205 can use the same S-NSSAI to re-establish the (one or more) PDU sessions, and the PDU session will be established on the new network slice instance.

[0102] In a fourth embodiment, due to a change in the NSI, a new network slice instance corresponding to an S-NSSAI that is not part of the allowed NSSAI becomes available for UE 205, where the new NSI replaces the old NSI used by UE 205. In such an embodiment, AMF 135 can initiate, for example, a registration management procedure or a UE configuration update procedure to send the new allowed NSSAI, which includes the new S-NSSAI and indicates that the new S-NSSAI is a replacement for the old S-NSSAI (see signaling 520). The network (e.g., SMF 235 based on the corresponding trigger from AMF 135 in signaling 514) also initiates a PDU session release procedure for the (one or more) PDU sessions associated with the old S-NSSAI (see signaling 522). UE 205 determines how to use the new parameters based on the usage information included in the new parameters (see block 524). In some embodiments, SMF 235 indicates that the PDU session re-establishment should be performed using the new S-NSSAI (see block 526). In such an embodiment, UE 205 uses the new S-NSSAI to re-establish the PDU session associated with the old S-NSSAI (see signaling 528).

[0103] In the first, second, and fourth embodiments above, AMF 135 sends a new (second) set of parameters to be used to UE 205 after determining that one or more parameters in the first set can no longer be used (see signaling 520). In addition to the second set of parameters, the network can also send an indication of how the parameters in the first set can be mapped to the parameters in the second set. This is the usage information discussed above, and UE 205 determines how to use the new parameters from the usage information (see block 524).

[0104] NAS signaling from the network (e.g., AMF 135) to the UE can be performed within different NAS procedures. If an event for NSI reconfiguration is triggered based on a UE-initiated registration, the AMF 135 can use the NAS registration acceptance message to convey the second parameter set (and usage information). Alternatively, if the event for NSI reconfiguration is network-initiated (e.g., due to a deployment change of a network slice instance or a UE subscription change), the AMF 135 can use the NAS UE configuration update procedure, the NAS notification procedure, or any other NAS procedure for UE parameter configuration update. In this scenario, the NAS procedure triggered by the network is used to update / modify the configuration / parameters of the UE 205.

[0105] In one example, the UE 205 receives a NAS registration acceptance message or a NAS notification message (see signaling 520) that includes a second NSAAI parameter set (e.g., S-NSSAI-b) and usage information (e.g., mapping information) that maps S-NSSAI-b to S-NSSAI-a. In another example, the UE 205 receives a NAS registration acceptance message or a NAS notification message that carries a second NSSAI parameter set that includes [S-NSSAI-b, S-NSSAI-c], and the usage information indicates [S-NSSAI-b can be mapped to S-NSSAI-a]. Here, S-NSSAI-c can be a previously permitted S-NSSAI, or it can be a new S-NSSAI that does not replace a part of the previously permitted NSSAI.

[0106] In some embodiments, the UE 205 sends in a NAS registration request message that includes the requested NSSAI parameters [S-NSSAI-a, S-NSSA-c] (refer to signaling 508). Here, the AMF 135 can determine that the network cannot serve [S-NSSAI-a, S-NSSA-c] due to a change in the NSI (refer to box 512). In response, the AMF 135 can send a NAS registration acceptance message with a new permitted NSSAI [S-NSSAI-x, S-NSSA-y] and usage information for mapping the new permitted NSSAI to the old permitted NSSAI. For example, the usage information can indicate that, for example, S-NSSAI-x is mapped to S-NSSAI-a, and S-NSSA-y is mapped to S-NSSAI-c. In the case of a carrier-specific SST value, the usage information can indicate how the SST value in the set of new permitted S-NSSAIs is mapped to a standard SST value or how the SST value in the set of new permitted S-NSSAIs is mapped to the SST value from the requested S-NSSAI (e.g., the SST from S-NSSAI-x will be used as the standardized SST value "eMBB").

[0107] Note that the AMF 135 may send a NAS message carrying a PDU session release request to the UE 205 (see signaling 522), where the PDU session release request originates from a NAS session management (SM) message from the first SMF 235. Here, the AMF 135 may receive a PDU session release request encapsulated within a NAS SM message (e.g., as shown in signaling 518). In some embodiments, the AMF 135 sends an SM PDU session release request message encapsulated within a NAS registration acceptance or encapsulates it within a NAS notification / transfer message (e.g., encapsulated as an N1 SM information container parameter). Here, the N1 SM information container includes a PDU session release request message, which includes: A) an appropriate release cause value indicating a change in network configuration / slice, and B) an existing old S-NSSAI or a new S-NSSAI.

[0108] Based on the signaling received from the network, the UE 205 determines what actions to take. In the case where the NSI corresponding to an S-NSSAI that is part of its old permitted NSSAI becomes unavailable, the UE 205 may release the PDU session associated with the unavailable S-NSSAI. Thereafter, the UE 205 uses another default S-NSSAI part of the permitted NSSAI and decides to re-establish the PDU session according to the NSSP configuration (see box 526).

[0109] However, if the (one or more) S-NSSAIs associated with the released PDU session are not part of the new permitted NSSAI, the UE 205 avoids the corresponding (one or more) applications until a new configuration from the network (e.g., a new NSSP configuration or a new permitted NSSAI configuration) is executed, which will allow the establishment of the corresponding data connection (e.g., a PDU session). Thus, the UE 205 does not re-establish the released PDU session until the permitted NSSAI does not include the S-NSSAI associated with the (one or more) applications.

[0110] In the case where there is a new additional NSI corresponding to an S-NSSAI that is not part of the old permitted NSSAI, the UE 205 may initiate a PDU session release procedure and a PDU session re-establishment procedure to associate an existing (one or more) PDU sessions with the new S-NSSAI based on the UE configuration of the UE 205 (e.g., NSSP policy). Accordingly, the (one or more) PDU sessions are moved from an old NSI to the new NSI. In some embodiments, the UE 205 may also initiate the establishment of (one or more) new PDU sessions using the new specific S-NSSAI, e.g., in the case where there is a configuration in the UE to use the PDU session with the new S-NSSAI.

[0111] In the case where there is a new NSI corresponding to an S-NSSAI that is already part of the old permitted NSSAI and the new NSI replaces the old NSI used by the UE 205, the UE 205 does not change its NSSAI configuration. However, based on the PDU session release procedure (e.g., based on the release reason in the PDU session release request message), the UE 205 determines that an already established PDU session can be re-established using the same S-NSSAI value (see block 526). Here, the UE 205 may release the established PDU session and initiate a PDU session establishment procedure using the same S-NSSAI value.

[0112] In the case where there is a new NSI corresponding to an S-NSSAI that is not part of the old permitted NSSAI and the new NSI replaces the old NSI used by the UE 205, the UE 205 uses the usage information to determine a third parameter set from a first parameter set and a second parameter set. Here, the UE 206 determines how to use the newly signaled parameter set (see block 524). In one embodiment, the UE 205 stores the new second parameter set including the usage information (e.g., mapping information). In some embodiments, the UE 205 updates its configuration related to the NSSAI based on the usage information.

[0113] As depicted in Figure 5B the third parameter set includes [S-NSSAI-b, DNN-1], where internally, the UE 205 maps S-NSSIA-a to S-NSSAI-b for this registration area (or this PLMN). In some embodiments, the third parameter set is equal to the second parameter set.

[0114] Then, UE 205 uses the third parameter set to re - establish a data connection (or uses a fourth parameter set based on the second parameter set to initiate a new data connection). Here, it is assumed that UE 205 has successfully completed the NAS registration process (mobility management process) with the network. To re - establish the data connection, UE 205 initiates NAS session management signaling to the network (e.g., to the SMF).

[0115] The NAS SM signaling message (referred to as N1 SM information) is encapsulated in another NAS message (e.g., NAS transport message) that terminates at the AMF 135. In some embodiments, the NAS message that terminates at the AMF 135 includes both the new PDU session ID and the old PDU session ID to allow the AMF 135 to associate between the old PDU session (which is terminated) and the new requested PDU session. The new (third) parameter set may optionally be included in the PDU session establishment request from UE 205 to the second SMF 250 (e.g., SMF - b).

[0116] As depicted, UE 205 may send a NAS session management message (such as the depicted NAS transport message) that includes the third parameter set (e.g., S - NSSAI - b, DNN - 1, PDU session ID, etc.) and the N1 SM information (e.g., including the new S - NSSAI, SSC mode, PDU type, etc.) that embeds the PDU session establishment request (see signaling 528). Here, the new parameter set may be included in the NAS message targeted at the AMF 135 (e.g., to be processed at the AMF 135), but the new parameter set may also be included in the N1 SM information container targeted at a new SMF (e.g., the second SMF 150) that is transparent to the AMF 135.

[0117] The AMF 135 processes NAS messages (e.g., NAS transport messages) from the UE 205. Based on the new PDU session ID, new S-NSSAI information (e.g., S-NSSAI-b), DNN-1 information, and other parameters, the AMF 135 selects an SMF for serving the PDU session. For example, the AMF 135 may select a new SMF (see block 530), but may also select the SMF-a 235 if a new NSI characterized by the new S-NSSAI is served by the SMF-a 235. As depicted, the AMF 135 selects the second SMF 250 (“SMF-b”). After selecting an SMF to serve the PDU session, the AMF 135 forwards the NAS SM message to the selected second SMF 250 (see signaling 532). As depicted, the AMF 135 may send an N11 SM request message that includes the PDU session ID and N1 SM information embedded in the PDU session establishment request. Note that the PDU session establishment request includes the new S-NSSAI-b, DNN-1, SSC1, PDU type, etc.

[0118] The second SMF 250 processes the NAS SM message and selects an appropriate UPF (here, the second UPF 255). After selecting the new UPF, the second SMF 250 establishes an N4 association with the second UPF 255 and configures the second UPF 255 accordingly (see block 534). After establishing the N4 association, the second SMF 250 generates an N11 SM response message and sends it to the AMF 135. The N11 SM response message includes the PDU session ID, N2 SM information (e.g., PDU session ID, (one or more) QoS profiles, UPF tunnel information, etc.), N1 SM information (e.g., PDU session establishment acceptance (IP configuration information (IP prefix / address)), (one or more) authorized QoS rules, S-NSSAI, NSSAI assistance information, SSC mode, etc.), and other parameters.

[0119] The second SMF 250 sends the N11 message to the AMF 135 (see signaling 536), and the AMF 135 forwards the N2 SM information to the (R)AN and forwards the N1 SM information to the UE (see signaling 538). The usage information (e.g., NSSAI assistance information) in the N1 SM information (e.g., PDU session establishment acceptance) message may be the same as or different from the usage information provided in the NAS registration / mobility signaling (reference signaling 520). For example, the usage information in the N1 SM information message may indicate to the UE 205 which (additional) application IDs can be used together with the S-NSSAI from the PDU session establishment acceptance message.

[0120] In some embodiments, the NSSF 150 is responsible for associating the UE 205 with a particular set of NSIs. For example, in a given registration area, the NSSF 150 may determine which NSI a particular S-NSSAI maps to. Here, the NSSF 150 is responsible for the association between the S-NSSAI and the NSI. Thus, when the UE 205 performs a registration procedure (with or without the requested NSSAI), the AMF 135 may consult the NSSF 150. Here, the AMF 135 requests the NSSF 150 to determine which NSIs are to be used for the UE 205 for the set of allowed NSSAIs.

[0121] In certain embodiments, each NSI is identified by an identifier (e.g., NSI-ID), which can be used internally by the network without being exposed to the UE 205. Here, when the AMF 135 receives a new NAS registration request from the UE 205, the AMF 135 derives a "preliminary set" of allowed S-NSSAIs based on the set of requested S-NSSAIs and the subscription information of the UE 205. Then, the AMF 135 sends this "preliminary set" of allowed S-NSSAIs to the NSSF 150 to request the possible NSIs to be used in this registration area. In response, the NSSF 150 determines the NSIs based on the "preliminary set" of allowed S-NSSAIs and the actual network slice deployment configuration in this area. In certain embodiments, the NSSF 150 determines that two S-NSSAIs from the "preliminary set" of allowed S-NSSAIs map to the same NSI. The NSSF 150 returns the mapping of S-NSSAI to NSI-ID to the AMF 135. Based on this information, the AMF 135 derives the "actual set" of allowed S-NSSAIs to be sent to the UE 205.

[0122] Figure 6 Method 600 for reconfiguring a data connection using new parameters according to an embodiment of the present disclosure is depicted. In some embodiments, method 600 is performed by a device, such as, the remote unit 105, the UE 205, and / or the remote device 300. In certain embodiments, method 600 may be performed by a processor executing program code, such as, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0123] Method 600 begins and establishes a data connection with a mobile communication network using a first set of parameters (605). In one embodiment, the first set of parameters includes network slice selection parameters and a data network name.

[0124] Method 600 includes: receiving (610) a second set of parameters from a mobile communication network and an indication of how at least one parameter in a first set (e.g., a set for establishing a data connection) corresponds to at least one new parameter in the second set. In some embodiments, the first set of parameters includes a first network slice selection parameter. In such an embodiment, the second set of parameters includes one or more new network slice selection parameters.

[0125] In some embodiments, receiving (610) an indication of how at least one parameter in the first set corresponds to at least one new parameter in the second set includes: receiving usage information associating one or more new network slice selection parameters with one or more previously provided network slice selection parameters. Here, the one or more previously provided network slice selection parameters include the first network slice selection parameter. In certain embodiments, receiving (610) the second set of parameters includes: updating the network slice selection configuration of the remote unit based on the one or more new network slice selection parameters.

[0126] In some embodiments, receiving (610) the second set of parameters includes: receiving an indication that at least one parameter in the first set (e.g., a set for establishing a data connection) is no longer valid. In one embodiment, receiving (610) an indication that at least one parameter in the first set is no longer valid includes: receiving an indication that the data connection has been interrupted (e.g., released).

[0127] In certain embodiments, receiving (610) the second set of parameters occurs in response to sending a registration request to update the mobile communication network with a new registration area. In one embodiment, receiving (610) the second set of parameters and an indication of how at least one parameter in the first set corresponds to at least one new parameter in the second set includes: receiving a configuration update message. In another embodiment, receiving (610) the second set of parameters and an indication of how at least one parameter in the first set corresponds to at least one new parameter in the second set includes: receiving a NAS notification message. In yet another embodiment, receiving (610) the second set of parameters and an indication of how at least one parameter in the first set corresponds to at least one new parameter in the second set includes: receiving a NAS registration acceptance message.

[0128] Method 600 includes: determining (615) a third set of parameters from the first set of parameters and the second set of parameters. In one embodiment, determining (615) a third set of parameters from the first set of parameters and the second set of parameters includes: replacing at least one invalid parameter in the first set with at least one corresponding parameter in the second set to form the third set of parameters.

[0129] Method 600 includes: reconfiguring (620) a data connection using a third set of parameters. In some embodiments, reconfiguring (620) the data connection includes performing one of the following: re - establishing the data connection using the third set of parameters, establishing a new data connection using a fourth set of parameters based on a second set of parameters, and releasing the data connection.

[0130] In some embodiments, reconfiguring (620) the data connection includes: re - establishing the data connection using the third set of parameters. In one embodiment, re - establishing the data connection includes: sending a NAS session management message that includes the third set of parameters. Method 600 ends.

[0131] Figure 7 Method 700 for re - registering a remote unit using new parameters according to an embodiment of the present disclosure is depicted. In some embodiments, method 700 is executed by a device, such as, AMF 135 and / or network function device 400. In certain embodiments, method 700 may be executed by a processor executing program code, such as, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0132] Method 700 begins and registers (705) the remote unit with a mobile communication network using a first set of parameters. In some embodiments, registering (705) the remote unit includes: receiving an initial registration message from the remote unit and returning a set of allowed network slice selection parameters to the remote unit. Here, the initial registration message includes the requested set of network slice selection parameters. In certain embodiments, the set of allowed network slice selection parameters includes one or more default network slice selection parameters. Further, returning the set of allowed network slice selection parameters may include: sending an indication that the default network slice selection parameters correspond to a data network name and / or a standardized network slice type.

[0133] The method includes: identifying (710) a second set of parameters to be used by the remote unit in the mobile communication network. In one embodiment, identifying (710) the second set of parameters includes: identifying the second set of parameters based on the requested set of network slice selection parameters, the subscription parameters of the remote unit, and / or the network slice instance associated with the remote unit. In another embodiment, identifying (710) the second set of parameters includes: identifying the second set of parameters based on the configuration of the remote unit and the current network slice instance associated with the remote unit.

[0134] In some embodiments, the first parameter set includes first network slice selection parameters, and identifying (710) the second parameter set includes: identifying one or more new network slice selection parameters for a network slice instance currently associated with the remote unit. In some embodiments, identifying (710) the second parameter set to be used by the remote unit in a mobile communication network includes: sending a query to a network slice selection function in response to receiving a registration request from the remote unit, and receiving a mapping of network slice selection parameters to network slice instances from the network slice selection function. Here, identifying (710) the second parameter set further includes: identifying a set of allowed network slice selection parameters based on the network slice instance currently associated with the remote unit.

[0135] In one embodiment, identifying (710) the second parameter set includes: receiving a registration request from the remote unit, and in response to the registration request, determining that at least one parameter in the first parameter set is no longer valid. In certain embodiments, the registration request is received in response to one of the following: the remote unit changes its registration area, the remote unit changes its PLMN change, and the remote unit needs to temporarily use a network slice. In another embodiment, identifying (710) the second parameter set includes: determining that at least one parameter in the first parameter set is no longer valid in response to one of the following: a change in the subscription of the remote unit, a change in the network policy rules applicable to the remote unit, and a change in the network slice deployment.

[0136] The method includes: sending (715) the second parameter set to the remote unit and an indication of how at least one parameter in the first parameter set corresponds to at least one new parameter in the second set. In one embodiment, sending (715) an indication of how at least one parameter in the first set corresponds to at least one new parameter in the second set includes: sending usage information associating one or more new network slice selection parameters with one or more previously provided network slice selection parameters. Here, one or more previously provided network slice selection parameters may include the first network slice selection parameters. In certain embodiments, the usage information is sent in response to determining that the remote unit does not know the new parameters in the second set.

[0137] In some embodiments, sending (715) the second set of parameters and an indication of how at least one parameter in the first set corresponds to at least one new parameter in the second set includes: sending a registration acceptance message (e.g., an NAS registration acceptance message) that includes the second set of parameters and an indication of how at least one parameter in the first set corresponds to at least one new parameter in the second set. In other embodiments, sending (715) the second set of parameters and an indication of how at least one parameter in the first set corresponds to at least one new parameter in the second set includes: sending one of the following: a configuration update message and an NAS notification message.

[0138] The method includes: receiving (720) from a remote unit a message that includes a third set of parameters for registration with a mobile communication network. Here, the third set of parameters is based on the first set of parameters and the second set of parameters. In some embodiments, receiving (720) the message from the remote unit includes: receiving a session management (“SM”) request message encapsulated in an NAS transport message. Here, the NAS transport message includes the third set of parameters and a session management message, where the SM request message includes at least one new parameter from the second set of parameters, such as a new network slice selection parameter.

[0139] In some embodiments, identifying (710) the second set of parameters includes: sending an SM request message to an SM function in response to determining that at least one parameter in the first set is no longer valid. Here, the SM request message includes an indication to release an established data connection and a new network slice selection parameter from the second set of parameters, such as a new network slice selection parameter. Sending the SM request message may include: receiving an SM response message from the SM function that includes a session release request message for the established data connection, and sending the session release request message to the remote unit. Method 700 ends.

[0140] Embodiments may be practiced in other specific forms. The described embodiments should be considered illustrative in all respects and not restrictive. Thus, the scope of the invention is indicated by the appended claims rather than the foregoing description. All changes within the meaning and range of equivalence of the claims will be included within the scope of the claims.

Claims

1. A network function ("NF") configured to: Receive a registration request from a user equipment ("UE"), the registration request indicating a first network slice set; Determine a second network slice set at least partially based on the first network slice set; Determine mapping information indicating a mapping between at least one network slice in the second network slice set and at least one network slice of a home public land mobile network ("HPLMN"); And Output the second network slice set and the mapping information to the UE.

2. The NF according to claim 1, Wherein: The first network slice set includes a set of requested network slice selection parameters, and The second network slice set includes a set of permitted network slice selection parameters.

3. The NF according to claim 2, further configured to: Determine the second network slice set based on at least one of: the set of requested network slice selection parameters, the set of subscribed network slice selection parameters, network slices available in the serving network in the current tracking area of the UE, or a combination thereof.

4. The NF according to claim 1, Wherein, The second network slice set includes one or more network slices that are available in the serving network and not present in the UE's subscribed network slice set.

5. The NF according to claim 4, Wherein, The mapping information includes a mapping of network slices from the second network slice set to network slices from the subscribed network slice set.

6. The NF according to claim 4, Wherein, The mapping information associates the second network slice set with one or more previously provided network slice selection parameters corresponding to the first network slice set, or with one or more standardized network slice types.

7. The NF according to claim 6, further configured to: Determine that the second network slice set corresponds to one or more new network slice selection parameters unknown to the UE; and In response to the second network slice set corresponding to the one or more new network slice selection parameters, output the mapping information and the second network slice set to the UE.

8. The NF according to claim 1, further configured to: Determine that at least one network slice in the first network slice set is an unavailable network slice for the UE in response to the registration information; and Send a registration acceptance message indicating the second network slice set and the mapping information.

9. The NF according to claim 8, Wherein, The registration request is at least one or more of: a change in the registration area associated with the UE, a change in the public land mobile network ("PLMN") associated with the UE, and the UE's need to temporarily use a network slice, or a combination thereof.

10. The NF according to claim 1, further configured to: determining that at least one network slice parameter associated with the first network slice set is no longer valid in response to one of the following: a change in the UE's subscription, a change in network policy rules applicable to the UE, a change in network slice deployment, or a combination thereof.

11. The NF according to claim 1, configured to: send a non-access stratum ("NAS") UE configuration update message or a NAS notification message, the NAS UE configuration update message indicating the second network slice set and the mapping information, the NAS notification message indicating the second network slice set and the mapping information.

12. The NF according to claim 1, further configured to: receive a connection request message from the UE to establish a data connection for an application using the second network slice set and the mapping information.

13. The NF according to claim 12, wherein, the connection request message includes a non-access stratum ("NAS") message including a network slice set based on the second network slice set and the mapping information.

14. The NF according to claim 13, further configured to: send an SM request message to a session management ("SM") function in response to at least one network slice in the first network slice set being no longer valid, wherein, the SM request message includes an indication to release the established data connection and new network slice selection parameters from the second network slice set.

15. The NF according to claim 14, further configured to: receive an SM response message from the SM function, the SM response message including a session release request message for the established data connection; and send the session release request message to the UE.

16. The NF according to claim 1, further configured to: send a query to a network slice selection function in response to receiving a registration request; receive a mapping of network slice selection parameters to network slice instances from the network slice selection function; and determine a set of allowed network slice selection parameters based on the network slice instances currently associated with the UE.

17. The NF according to claim 1, wherein, wherein, the first network slice set includes a first single network slice selection assistance information value ("S-NSSAI") set based on the configuration of the UE.

18. A method of a network node, the method comprising: receiving a registration request from a user equipment ("UE"), the registration request indicating a first set of network slices; determining a second network slice set at least in part based on the first network slice set; determining mapping information indicating a mapping between at least one network slice in the second network slice set and at least one network slice of a home public land mobile network ("HPLMN"); and and outputting the second network slice set and the mapping information to the UE.

19. The method according to claim 18, wherein: the first network slice set includes a set of requested network slice selection parameters, and The second network slice set includes a set of allowed network slice selection parameters.

20. A user equipment ("UE"), comprising: a processor; and a memory coupled to the processor, the memory including instructions that can be executed by the processor to cause the UE; send a registration request indicating a first network slice set; receive mapping information indicating a mapping between at least one network slice in the first network slice set or the second network slice set and at least one network slice of a home public land mobile network ("HPLMN"); and at least partially based on the mapping information, associate at least one application with at least one network slice in the first network slice set or the second network slice set.

Images