Differentiated registration with network slices in wireless communication network

By implementing a differentiated registration process in a wireless communication network, allowing or denying network slice registration according to the registration reasons, the problem of low network slice utilization efficiency in wireless communication networks is solved and resource utilization efficiency is improved.

CN119096601APending Publication Date: 2024-12-06LENOVO (SINGAPORE) PTE LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280095504.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-05-05
Filing Date
2022-06-23
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

The existing wireless communication network cannot effectively control and ensure the proper utilization of network slices, resulting in the inability to determine whether user equipment (UE) is allowed to register with network slices, affecting the efficiency of network resources.

Method used

By implementing a differentiated registration process in wireless communication devices and networks, the reasons for registering with network slices are determined, and registration is allowed or refused based on this reason, ensuring the rational use of network slices.

Benefits of technology

It realizes better control over network resources, ensures that only user equipment that only needs to use network slices is registered, improves the efficiency of network resources and avoids unnecessary waste of resources.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119096601A_ABST
    Figure CN119096601A_ABST
Patent Text Reader

Abstract

A wireless communication device including a processor and a transceiver is provided. The processor is arranged to determine a cause for registration with a first network slice. The transceiver is arranged to transmit an indication of the cause, wherein the indication is transmitted in association with the first network slice. The transceiver is further arranged to receive an identity of a set of permitted network slices.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The subject matter disclosed herein generally relates to the field of implementing differentiated registration to network slices in a wireless communication network. This document defines a wireless communication device, a method in a wireless communication device, a wireless communication network, and a method in a wireless communication network. Background Art

[0002] (Radio) Access Network (R)AN may include 3GPP RAN such as UTRAN, E-UTRAN, NR and non-3GPP RAT such as WLAN, or may also include a 5G Access Network (5G-AN).

[0003] In fifth generation (5G) wireless communication networks, network slicing is a capability that allows network operators to divide (or "slice") a network into smaller complete networks in order to provide customized features to third-party customers (service providers that provide services to user devices). Network slices span across the access network (RAN, NG-RAN or non-3GPP access) and the core network (CN, 5GC). In this sense, a network slice is a logical network that includes a set of network functions and corresponding resources (e.g., computing, storage, networking) necessary to provide certain network capabilities and network characteristics.

[0004] The 3GPP Technical Specification 23.501, v17.4.0 (March 2022) is titled "System Architecture for the 5G System"; the 5G system provides data connectivity and services, and this specification covers all aspects of both roaming and non-roaming scenarios, including interworking between 5GS and EPS, mobility within 5GS, QoS, policy control and billing, authentication, and general 5G system-wide functions such as SMS, location services, and emergency services.

[0005] 3GPP Technical Specification 23.502, v17.4.0 (March 2022) is titled "Procedures for the 5G System" and defines the stage 2 procedures and network function services of the 5G system architecture described in 3GPP TS 23.501, v17.4.0 and the policy and charging control framework described in 3GPP TS 23.503, v17.4.0.

[0006] 3GPP Technical Specification 23.503, v17.4.0 (March 2022) is titled "Policy and charging control framework" and defines the Stage 2 policy and charging control framework for 5G systems as specified in TS 23.501 v17.4.0 and TS 23.502 v17.4.0. Summary of the invention

[0007] One problem with known wireless communication networks is that they are unable to control and ensure proper utilization of network slices.

[0008] Disclosed herein is a process for implementing differentiated registration with a network slice in a wireless communication network. The process may be implemented by a wireless communication device or a wireless communication network.

[0009] Thus, there is provided a wireless communication apparatus comprising a processor and a transceiver. The processor is arranged to determine a reason for registering with a first network slice. The transceiver is arranged to transmit an indication of the reason, wherein the indication is transmitted in association with the first network slice. The transceiver is further arranged to receive identities of a set of allowed network slices.

[0010] Further provided is a method in a wireless communication device, the method comprising: determining a reason for registering with a first network slice; transmitting an indication of the reason, wherein the indication is transmitted in association with the first network slice; and receiving identities of a set of allowed network slices.

[0011] There is further provided a wireless communication network comprising a transceiver arranged to receive an indication of a reason for registering with a first network slice from a wireless communication device, wherein the indication is received in association with the first network slice. In response to the indication, the transceiver is further arranged to send a set of identities of allowed network slices to the wireless communication device.

[0012] Further provided is a method in a wireless communication network, the method comprising: receiving an indication of a reason for registering with a first network slice from a wireless communication device, wherein the indication is received in association with the first network slice; and in response to the indication, sending a set of identities of allowed network slices to the wireless communication device. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] In order to describe the manner in which the advantages and features of the present disclosure are obtained, the description of the present disclosure is presented by reference to certain devices and methods illustrated in the accompanying drawings. Each of these drawings depicts only certain aspects of the present disclosure and therefore should not be considered as limiting the scope thereof. The drawings may have been simplified for clarity and are not necessarily drawn to scale.

[0014] A method and apparatus for implementing differentiated registration with a network slice in a wireless communication network will now be described by way of example only with reference to the accompanying drawings, in which:

[0015] Figure 1 An exemplary 5GS architecture 100 showing a UE 110 associated with two network slices;

[0016] Figure 2 depicts a user equipment device 200 that may be used to implement the methods described herein;

[0017] Figure 3 depicts further details of a network node 300 that may be used to implement the methods described herein;

[0018] Figure 4 Illustrate a method in a wireless communication device;

[0019] Figure 5 illustrates a method in a wireless communication network; and

[0020] Figure 6 The diagrams illustrate further details of exemplary embodiments of the solutions presented herein. DETAILED DESCRIPTION

[0021] As will be appreciated by those skilled in the art, aspects of the present disclosure may be embodied as systems, devices, methods, or program products. Thus, the arrangements described herein may be implemented in full hardware form, full software form (including firmware, resident software, microcode, etc.), or in a form that combines software aspects with hardware aspects.

[0022] For example, the disclosed methods and apparatus may be implemented as hardware circuits including customized very large scale integration ("VLSI") circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors or other discrete components. The disclosed methods and apparatus may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, and the like. As another example, the disclosed methods and apparatus may include one or more physical or logical blocks of executable code that may be organized, for example, as objects, procedures, or functions.

[0023] In addition, the methods and apparatus may take the form of a program product embodied in one or more computer-readable storage devices, the computer-readable storage device storing machine-readable code, computer-readable code and / or program code (hereinafter referred to as code). The storage device may be tangible, non-transitory and / or non-transmissive. The storage device may not include signals. In some arrangements, the storage device only uses signals to access the code.

[0024] Any combination of one or more computer readable media may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, device, or apparatus, or any suitable combination of the foregoing.

[0025] More specific examples of storage devices (a non-exhaustive list) would include the following: an electrical connection having one or more conductors, a portable computer diskette, 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 disk 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 document, a computer-readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0026] Throughout this specification, references to examples or similar language of a particular method or device mean that the specific features, structures or characteristics described in conjunction with that example are included in at least one embodiment of the method and device described herein. Therefore, references to the features of the examples of a particular method or device or similar language may but may not all refer to the same examples, but mean "one or more but not all examples", unless otherwise expressly specified. The terms "comprise", "include", "have" and their variants mean "including but not limited to", unless otherwise expressly specified. The enumerated list of items does not mean that any or all items are mutually exclusive, unless otherwise expressly specified. The terms "a", "an" and "described" also refer to "one or more", unless otherwise expressly specified.

[0027] As used herein, a list with the conjunction "and / or" includes any single item in the list or a combination of items in the list. For example, a list of A, B, and / or C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C, or a combination of A, B, and C. As used herein, a list using the term "one or more of" includes any single item in the list or a combination of items in the list. For example, one or more of A, B, and C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C, or a combination of A, B, and C. As used herein, a list using the term "one of" includes one and only one of any single item in the list. For example, "one of A, B, and C" includes only A, only B, or only C but not a combination of A, B, and C. As used herein, "a member selected from a group consisting of A, B, and C" includes one and only one of A, B, or C but not a combination of A, B, and C. As used herein, “a member selected from the group consisting of A, B, and C and combinations thereof” includes A only, B only, C only, a combination of A and B, a combination of B and C, a combination of A and C, or a combination of A, B, and C.

[0028] In addition, the features, structures or characteristics described herein may be combined in any suitable manner. In the following description, numerous specific details, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., are provided to provide a thorough understanding of the present disclosure. However, those skilled in the art will recognize that the disclosed methods and devices may be practiced without one or more of the specific details, or may be practiced using 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 present disclosure.

[0029] Aspects of the disclosed methods and devices are described below with reference to schematic flow charts and / or schematic block diagrams of methods, devices, systems, and program products. It will be understood that each frame of the schematic flow charts and / or schematic block diagrams and combinations of frames in the schematic flow charts and / or schematic block diagrams can be implemented by code. This 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, so that instructions executed by the processor of the computer or other programmable data processing device create means for implementing the functions / actions specified in the schematic flow charts and / or schematic block diagrams.

[0030] The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus or other device to function in a specific manner so that the instructions stored in the storage device produce a manufactured product containing instructions for implementing the functions / actions specified in the schematic flowchart and / or schematic block diagram.

[0031] The code may also be loaded onto a computer, other programmable data processing device or other apparatus to cause a series of operational steps to be performed on the computer, other programmable device or other apparatus to produce a computer-implemented process, so 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.

[0032] The schematic flowcharts and / or schematic block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of devices, systems, methods, and program products. In this regard, each block in the schematic flowchart or schematic block diagram may represent a module, segment, or code portion, which includes one or more executable instructions for implementing the specified logical functions.

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

[0034] The description of the elements in each figure can refer to the elements in the previous figure. In all figures, like numbers refer to like elements.

[0035] In fifth generation (5G) wireless communication networks, network slicing is a capability that allows network operators to divide (or "slice") a network into smaller complete networks in order to provide customized features to third-party customers (service providers that provide services to user devices). Network slices span across the access network (RAN, NG-RAN or non-3GPP access) and the core network (CN, 5GC). In this sense, a network slice is a logical network that includes a set of network functions and corresponding resources (e.g., computing, storage, networking) necessary to provide certain network capabilities and network characteristics.

[0036] The network operator may wish to control the use of network slices, i.e. limit the number of UEs that register with the network slice or the number of PDU sessions established in the network slice. This is called network slice admission control (NSAC). In addition, the network operator may wish to optimize the performance of its network depending on the current slice load. In general, when the UE has services to be transmitted through the network slice, there may be other reasons why the network operator wants the UE to register with the network slice.

[0037] The UE may be configured with network slice related information called Network Slice Selection Assistance Information (NSSAI). NSSAI may consist of a single or multiple S-NSSAIs (Single Network Slice Selection Assistance Information). The UE requests to register with the network slice by sending a NAS Registration Request message containing the requested NSSAI to the 5GC, wherein the requested NSSAI contains a list of one or more S-NSSAIs with which the UE wants to register. The UE may send a NAS Registration Request message to the AMF in the 5GC. The 5GC may send one or more of the following elements related to the UE's network slice configuration to the UE in a Registration Accept message or a UE Configuration Update Command message: Allowed NSSAI, Configured NSSAI, Rejected NSSAI, or Pending NSSAI. NSSAI is a list of one or more S-NSSAIs. Any of these elements may be sent to the UE by the AMF, but the content of the Allowed NSSAI, Configured NSSAI, and Rejected NSSAI may be created in the AMF or in the Network Slice Selection Function (NSSF) queried to the AMF.

[0038] Figure 1 An exemplary 5GS architecture 100 is shown for a UE 110 associated with two network slices, where the network slices are deployed on a network slice instance 1 ("NSI-1", 140) and a network slice instance 2 ("NSI-2", 160) depicted in dashed lines, respectively. As described herein, the UE 110 may include a user equipment device 200 or a UE 610. According to this exemplary architecture, a (radio) access network "(R)AN" 120 is part of both slices 140, 160 and it is shared. The core network portion of the network slice (or NSI) has a common control plane network function (CCNF) 122 and dedicated CN network functions, such as SMF1 144, UPF1 146 and other NFs 145 belonging to NSI-1 140 and SMF2 164, UPF2 166 and other NFs 165 belonging to NSI-2 160. As described herein, CCNF 122 may include network node 300 or AMF / NSSF 630.

[0039] Please note, Figure 1Not all NFs and all reference points are included. More information about the functionality of NFs (e.g., AMF, NSSF, SMF, UPF, etc.), reference points, and 5GS can be found in references 3GPP TS 23.501, v17.4.0 and 3GPP TS 23.502, v17.4.0.

[0040] When an application executed by a UE requests connectivity for data transfer, the UE determines which network slice (and which PDU session) to use based on the URSP rules or based on the UE local configuration as described in 3GPP TS 23.503 v17.4.0, where further details on the URSP policy can be found. 3GPP TS 23.503 v17.4.0 specifies that if the S-NSSAI present in the routing descriptor (RSD) of the URSP rules is in the allowed NSSAI (e.g., for non-roaming cases, and in the mapping information of allowed NSSAI to HPLMN S-NSSAI for roaming cases), then the RSD is considered valid. Having such a behavior would mean that the UE should include all S-NSSAI from the configured NSSAI in the requested NSSAI.

[0041] The UE has implementation freedom and based on the application the UE wants to use, the UE constructs the requested NSSAI as described in 3GPP TS 23.501, v17.4.0, clause 5.15.5.2.1.

[0042] Furthermore, 3GPP TR 23.700-41 v0.2.0 describes: "The UE registers / deregisters with the network slice and establishes / tears down the PDU session based on its own policy taking into account information provided by the network, e.g. URSP. However, this does not allow an operator, for example, to force the UE to register with an S-NSSAI only when it actually needs to have connectivity in the relevant network slice. In fact, the UE may choose to register with all configured NSSAIs and then just use the URSP to decide which DNNs to connect to at runtime."

[0043] A problem with known network slice registration procedures is that the network cannot determine whether to allow registration to a network slice depending on whether the network slice will be used by the UE. Making such a determination would tend to allow the network to control UE behavior.

[0044] A problem that exists in known wireless communication networks is that the network is unable to control and ensure proper utilization of network slices in the system.

[0045] In a known network, a network function such as AMF may configure a time value associated with S-NSSAI in the UE, indicating that the S-NSSAI will be deregistered when data transmission is inactive. When data connectivity is no longer used, the AMF and the UE start a timer with the configured time value. After the timer expires, both the UE and the network implicitly remove the S-NSSAI from the allowed NSSAI.

[0046] Figure 2 A user equipment device 200 is depicted that can be used to implement the methods described herein. The user equipment device 200 is used to implement one or more of the solutions described herein. The user equipment device 200 is consistent with one or more of the user equipment devices described in the embodiments herein. In particular, the user equipment device 200 may include a UE 110 or a UE 610 as described herein. The user equipment device 200 includes a processor 205, a memory 210, an input device 215, an output device 220, and a transceiver 225.

[0047] Input device 215 and output device 220 may be combined into a single device, such as a touch screen. In some implementations, user equipment apparatus 200 does not include any input device 215 and / or output device 220. User equipment apparatus 200 may include one or more of the following: processor 205, memory 210, and transceiver 225, and may not include input device 215 and / or output device 220.

[0048] As depicted, the transceiver 225 includes at least one transmitter 230 and at least one receiver 235. The transceiver 225 can communicate with one or more cells (or wireless coverage areas) supported by one or more base units. The transceiver 225 can operate on an unlicensed spectrum. Moreover, the transceiver 225 can include multiple UE panels supporting one or more beams. In addition, the transceiver 225 can support at least one network interface 240 and / or application interface 245. The application interface 245 can support one or more APIs. The network interface 240 can support 3GPP reference points, such as Uu, N1, PC5, etc. As understood by those skilled in the art, other network interfaces 240 can be supported.

[0049] The processor 205 may include any known controller capable of executing computer-readable instructions and / or capable of performing logical operations. For example, the processor 205 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. The processor 205 may execute instructions stored in the memory 210 to perform the methods and routines described herein. The processor 205 is communicatively coupled to the memory 210, the input device 215, the output device 220, and the transceiver 225.

[0050] Processor 205 may control user equipment device 200 to implement the user equipment device behaviors described herein. Processor 205 may include an application processor (also referred to as a "main processor") that manages application domain and operating system ("OS") functions, and a baseband processor (also referred to as a "baseband radio processor") that manages radio functions.

[0051] Memory 210 may be a computer-readable storage medium. Memory 210 may include volatile computer storage media. For example, memory 210 may include RAM, including dynamic RAM ("DRAM"), synchronous dynamic RAM ("SDRAM"), and / or static RAM ("SRAM"). Memory 210 may include non-volatile computer storage media. For example, memory 210 may include a hard drive, flash memory, or any other suitable non-volatile computer storage device. Memory 210 may include volatile and non-volatile computer storage media.

[0052] Memory 210 may store data related to implementing the traffic class fields described herein. Memory 210 may also store program code and related data, such as an operating system or other controller algorithms operating on device 200.

[0053] Input device 215 may include any known computer input device, including a touch panel, buttons, keyboard, stylus, microphone, etc. Input device 215 may be integrated with output device 220, such as a touch screen or similar touch-sensitive display. Input device 215 may include a touch screen so that text can be entered using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. Input device 215 may include two or more different devices, such as a keyboard and a touch panel.

[0054] The output device 220 may be designed to output visual, auditory and / or tactile signals. The output device 220 may include an electronically controllable display or display device capable of outputting visual data to a user. For example, the output device 220 may include, but is not limited to, a liquid crystal display ("LCD"), a light emitting diode ("LED") display, an organic LED ("OLED") display, a projector, or a similar display device capable of outputting images, text, and the like to a user. As another non-limiting example, the output device 220 may include a wearable display that is separate from the rest of the user equipment device 200 but communicatively coupled to the rest, such as a smart watch, smart glasses, a head-up display, and the like. In addition, the output device 220 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, and the like.

[0055] Output device 220 may include one or more speakers for producing sounds. For example, output device 220 may produce an auditory alarm or notification (e.g., a beep or chime). Output device 220 may include one or more haptic devices for producing vibration, motion, or other tactile feedback. All or part of output device 220 may be integrated with input device 215. For example, input device 215 and output device 220 may form a touch screen or similar touch-sensitive display. Output device 220 may be located near input device 215.

[0056] The transceiver 225 communicates with one or more network functions of the mobile communication network via one or more access networks. The transceiver 225 operates under the control of the processor 205 to transmit messages, data, and other signals, and also receives messages, data, and other signals. For example, the processor 205 may selectively activate the transceiver 225 (or a portion thereof) at a specific time in order to send and receive messages.

[0057] The transceiver 225 includes at least one transmitter 230 and at least one receiver 235. The one or more transmitters 230 may be used to provide uplink communication signals to the base unit of the wireless communication network. Similarly, the one or more receivers 235 may be used to receive downlink communication signals from the base unit. Although only one transmitter 230 and one receiver 235 are illustrated, the user equipment device 200 may have any suitable number of transmitters 230 and receivers 235. In addition, the transmitter 230 and the receiver 235 may be any suitable type of transmitter and receiver. The transceiver 225 may include a first transmitter / receiver pair for communicating with a mobile communication network through a licensed radio spectrum and a second transmitter / receiver pair for communicating with a mobile communication network through an unlicensed radio spectrum.

[0058] The first transmitter / receiver pair may be used to communicate with a mobile communication network via a licensed radio spectrum, while the second transmitter / receiver pair used to communicate with a mobile communication network via an unlicensed radio spectrum may be combined into a single transceiver unit, such as a single chip that performs functions for use with both licensed and unlicensed radio spectrum. The first transmitter / receiver pair and the second transmitter / receiver pair may share one or more hardware components. For example, some of the transceivers 225, transmitters 230, and receivers 235 may be implemented as physically separate components that access shared hardware resources and / or software resources, such as the network interface 240.

[0059] One or more transmitters 230 and / or one or more receivers 235 may be implemented and / or integrated into a single hardware component, such as a multi-transceiver chip, a system on a chip, an application specific integrated circuit ("ASIC"), or other type of hardware component. One or more transmitters 230 and / or one or more receivers 235 may be implemented and / or integrated into a multi-chip module. Other components such as network interface 240 or other hardware components / circuits may be integrated into a single chip with any number of transmitters 230 and / or receivers 235. Transmitters 230 and receivers 235 may be logically configured as transceivers 225 using one or more common control signals, or as modular transmitters 230 and receivers 235 implemented in the same hardware chip or multi-chip module.

[0060] Figure 3 Depicts further details of a network node 300 that may be used to implement the methods described herein. The network node 300 may be one implementation of an entity in a wireless communication network, such as in one or more wireless communication networks described herein. In particular, the network node 300 may include a CCNF 122 or an AMF / NSSF 630 as described herein. The network node 300 includes a processor 305, a memory 310, an input device 315, an output device 320, and a transceiver 325.

[0061] The input device 315 and the output device 320 may be combined into a single device, such as a touch screen. In some implementations, the network node 300 does not include any input device 315 and / or output device 320. The network node 300 may include one or more of the following: a processor 305, a memory 310, and a transceiver 325, and may not include an input device 315 and / or an output device 320.

[0062] As depicted, the transceiver 325 includes at least one transmitter 330 and at least one receiver 335. Here, the transceiver 325 communicates with one or more remote units 200. In addition, the transceiver 325 can support at least one network interface 340 and / or an application interface 345. The application interface 345 can support one or more APIs. The network interface 340 can support 3GPP reference points such as Uu, N1, N2, and N3. As understood by those skilled in the art, other network interfaces 340 can be supported.

[0063] 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 CPU, a GPU, an auxiliary processing unit, an FPGA, or a similar programmable controller. The processor 305 may execute 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 output device 320, and the transceiver 325.

[0064] Memory 310 may be a computer-readable storage medium. Memory 310 may include volatile computer storage media. For example, memory 310 may include RAM, including dynamic RAM ("DRAM"), synchronous dynamic RAM ("SDRAM"), and / or static RAM ("SRAM"). Memory 310 may include non-volatile computer storage media. For example, memory 310 may include a hard drive, flash memory, or any other suitable non-volatile computer storage device. Memory 310 may include volatile and non-volatile computer storage media.

[0065] The memory 310 may store data related to establishing a multipath unicast link and / or mobile operation. For example, as described herein, the memory 310 may store parameters, configurations, resource allocations, policies, etc. The memory 310 may also store program code and related data, such as an operating system or other controller algorithm operating on the network node 300.

[0066] Input device 315 may include any known computer input device, including a touch panel, buttons, keyboard, stylus, microphone, etc. Input device 315 may be integrated with output device 320, such as a touch screen or similar touch-sensitive display. Input device 315 may include a touch screen so that text can be entered using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. Input device 315 may include two or more different devices, such as a keyboard and a touch panel.

[0067] The output device 320 may be designed to output visual, auditory and / or tactile signals. The output device 320 may include an electronically controllable display or display device capable of outputting visual data to a user. For example, the output device 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, and the like to a user. As another non-limiting example, the output device 320 may include a wearable display that is separate from the rest of the user equipment device 300 but communicatively coupled to the rest, such as a smart watch, smart glasses, a head-up display, and the like. In addition, the output device 320 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, and the like.

[0068] Output device 320 may include one or more speakers for producing sounds. For example, output device 320 may produce an auditory alarm or notification (e.g., a beep or chime). Output device 320 may include one or more haptic devices for producing vibration, motion, or other tactile feedback. All or part of output device 320 may be integrated with input device 315. For example, input device 315 and output device 320 may form a touch screen or similar touch-sensitive display. Output device 320 may be located near input device 315.

[0069] The transceiver 325 includes at least one transmitter 330 and at least one receiver 335. As described herein, one or more transmitters 330 may be used to communicate with a UE. Similarly, as described herein, one or more receivers 335 may be used to communicate with a network function in a PLMN and / or RAN. Although only one transmitter 330 and one receiver 335 are illustrated, the network node 300 may have any suitable number of transmitters 330 and receivers 335. Furthermore, the transmitter 330 and receiver 335 may be any suitable type of transmitter and receiver.

[0070] Thus, there is provided a wireless communication apparatus comprising a processor and a transceiver. The processor is arranged to determine a reason for registering with a first network slice. The transceiver is arranged to transmit an indication of the reason, wherein the indication is transmitted in association with the first network slice. The transceiver is further arranged to receive identities of a set of allowed network slices.

[0071] Thus, the wireless communication device has the ability to register with different types of network slices, depending on the reason for the network slice registration. Thus, the wireless communication network is able to better control the use of resources within the wireless communication network. The resources may include network slices. Controlling the use of resources within the wireless communication network may include limiting UE registrations to a particular network slice to UEs that need to use the network slice or UEs for which the network slice is the default slice. A particular UE may need to use a particular network slice to implement a user equipment routing policy rule.

[0072] The wireless communication device may be adapted to communicate with a wireless communication network. The reason for registration may be one of: active, immediate use, or default application. The transceiver may be further arranged to transmit a registration request so as to cause the wireless communication device to register with a first network slice in the wireless communication network.

[0073] The processor may further be arranged to determine whether the first network slice is identified in a set of allowed network slices or denied network slices, and if not, and if the first network slice is identified in a routing descriptor of a routing policy rule, the transceiver is arranged to send a registration request for the first network slice.

[0074] The transceiver may further be arranged to receive a configuration from the wireless communication network requiring the wireless communication device to include an indication of a reason for any registration with the network slice. The configuration may be received from an access and mobility management function or from a unified data management function of the wireless communication network.

[0075] The transceiver may further be arranged to transmit an indication of the reason for registration to the first network slice as part of the registration request message.

[0076] The indication of the reason for registering with the first network slice may include at least one of the following: registration due to use of the first network slice indicates that the application service is ready to be sent through the first network slice; or active registration indicates that the application can use the first network slice at any later time; or registration with the first network slice indicates that the default application will use the first network slice.

[0077] The wireless communication device may be user equipment.

[0078] Figure 4 The diagram illustrates a method 400 in a wireless communication device, the method 400 comprising: determining 410 a reason for registering with a first network slice; transmitting 420 an indication of the reason, wherein the indication is transmitted in association with the first network slice; and receiving 430 identities of a set of allowed network slices.

[0079] Further provided is a wireless communication network comprising a transceiver arranged to receive an indication of a reason for registering with a first network slice from a wireless communication device, wherein the indication is received in association with the first network slice. In response to the indication, the transceiver is further arranged to send a set of identities of allowed network slices to the wireless communication device.

[0080] Thus, the wireless communication network is able to create a set of allowed network slices by taking into account the indicated reasons for the network slice registration. Thus, the wireless communication network is able to better control the use of resources within the network. The resources may include network slices. Controlling the use of resources within the wireless communication network may include limiting UE registrations to a particular network slice to UEs that need to use the network slice or UEs for which the network slice is the default slice. A particular UE may need to use a particular network slice to implement a user equipment routing policy rule.

[0081] The wireless communication network may include access and mobility management functionality. The wireless communication device may be a user equipment. The wireless communication device may be adapted to communicate with the wireless communication network. The reason for the registration may be one of: active, immediate use, or default application. The transceiver may be further arranged to receive a registration request in order to register the wireless communication device with a first network slice in the wireless communication network.

[0082] The transceiver may further be arranged to send a configuration to the wireless communication device requiring the wireless communication device to include an indication of the reason for any registration with the network slice. The configuration may be sent to the UE from an access and mobility management function of the wireless communication network.

[0083] The transceiver may be further arranged to receive an indication of a reason for any registration with the network slice as part of the registration request message. The transceiver is further configured to receive a registration request for the first network slice from the wireless communication device.

[0084] The wireless communication network may comprise an access and mobility management function. The wireless communication network may comprise a network slice selection function, and wherein the access and mobility management function forwards a received reason for registering with the network slice to the network slice selection function.

[0085] The wireless communication network may further include a processor, the processor being arranged to determine whether to allow the wireless communication device to register with the first network slice based on the received reason for registering with the first network slice. The determination of whether to allow the wireless communication device to register with the first network slice may be further based on the configuration in the AMF. The configuration in the AMF may mean that the AMF may (1) have received the configuration from the OAM system, or (2) have received a configuration indication from the UDM, or (3) based on the current load situation of the network slice. Therefore, the AMF may know (i.e., be configured to) how to handle the received reason for the UE to register with the slice.

[0086] The transceiver may further be arranged to receive an indication associated with the first network slice as to whether registration with the first network slice is allowed when a request to register with the first network slice is received together with a specific reason for registration. The specific reason for registration may be that the network slice is for immediate use, i.e. data is ready to be sent via the network slice. The indication associated with the first network slice as to whether registration with the first network slice is allowed may be received from the UDM. The indication associated with the first network slice as to whether registration with the first network slice is allowed may be based on the reason for registration provided from the UE. The indication associated with the network slice may be part of the UE subscription data.

[0087] Figure 5 The diagram illustrates a method 500 in a wireless communication network, the method 500 comprising: receiving 510 an indication of a reason for registering with a first network slice from a wireless communication device, wherein the indication is received in association with the first network slice; and in response to the indication, sending 520 a set of identities of allowed network slices to the wireless communication device.

[0088] A problem with known network slice registration procedures is that the network is unaware of the reason for the network slice registration request from the UE. For example, it is known that the network cannot know whether the UE requests registration with a network slice due to (a) an immediate need to use the network slice, or (b) proactive registration in order to use the slice at some later point in time. Therefore, the network cannot determine whether registration with a specific requested network slice is allowed or not. According to the arrangements described herein, an access and mobility management function (AMF) or a network slice selection function (NSSF) determines whether registration with a specific requested network slice is allowed or not. It is assumed that the AMF or NSSF can serve the requested network slice in the current area.

[0089] Please note that the terms "network slice", "slice" and "S-NSSAI" have similar meanings in this disclosure and may be used interchangeably. S-NSSAI is an identifier of a network slice in a network. Whenever "S-NSSAI" is used, it means the S-NSSAI value of the home network (e.g., HPLMN or HPLMN S-NSSAI). The UE may also use (i.e., send or receive) the S-NSSAI value of the VPLMN mapped to the HPLMN S-NSSAI value; and in this case, the UE may use both values ​​(i.e., the UE sends or receives both the HPLMN S-NSSAI value and the corresponding mapped VPLMN S-NSSAI value). In other words, whenever sending / receiving S-NSSAI is stated herein, sending / receiving the home network S-NSSAI value and the corresponding serving network S-NSSAI value may also be understood.

[0090] According to a first arrangement presented herein, the UE provides the type of requested S-NSSAI.

[0091] The main principle of this first arrangement is that the UE sends information to the network indicating different reasons for the request to register with the S-NSSAI. In other words, the UE indicates the type of the S-NSSAI registration request to the network (e.g., AMF in the network). The type of the S-NSSAI registration request may include the reason for the S-NSSAI registration request. For example, the UE may indicate that the registration with the S-NSSAI is (a) due to the need to use the S-NSSAI or (b) an active registration.

[0092] Therefore, the UE determines to include the S-NSSAI in the requested NSSAI due to the need to use the S-NSSAI or due to active registration with network slicing. Such reasons may include:

[0093] ● Slice registration for (immediate) use or required: An application may request connectivity, matching the URSP rule to include the S-NSSAI in the RSD. For example, an application (e.g. YouTube) may request connectivity to an application server (e.g. YouTube server). The UE determines that it needs to register with the S-NSSAI of the RSD matching the URSP rule because the application matches the traffic descriptor of the URSP rule. In this sense, the UE requires slice registration for (immediate) use.

[0094] ● Active Slice Registration: Based on the UE implementation, the UE may want to register with the S-NSSAI so that a PDU session can be established immediately in this network slice when needed at some point in time.

[0095] ● Slice registration for default applications (or due to "always on" / default S-NSSAI): The UE knows that the network slice is for default applications (e.g., IMS voice applications for voice-centric UEs), and the UE always includes the S-NSSAI in the requested NSSAI. In one example, at UE power up or during deactivation of airplane mode, the operating system may determine that a certain default application (e.g., IMS, OS update manager) wants connectivity to transfer data.

[0096] The UE includes parameters associated with the requested S-NSSAI in the registration request message. The parameters may include a reason for the registration request. The parameters may indicate that the S-NSSAI registration is active (i.e., the UE is not intended to use the S-NSSAI immediately). In other words, the UE may request a first group of one or more S-NSSAIs to be used immediately and a second group of one or more S-NSSAIs that are not intended to be used immediately.

[0097] Once the UE is registered with the network and stores the allowed NSSAI, the UE can determine that if an application requests connectivity and there is a matching URSP rule where the RSD contains an S-NSSAI that is not part of the allowed NSSAI or a rejected S-NSSAI, the UE can first trigger a registration procedure (of the mobility update type) and include the S-NSSAI in the requested NSSAI. After the S-NSSAI becomes part of the allowed NSSAI, the UE starts establishing a PDU session as requested by the application.

[0098] When processing URSP rules, the meaning in the UE is that after the registration process is completed, the RSD matching the URSP rules can then be evaluated as valid (or invalid), and if the S-NSSAI is included in the allowed NSSAI, the RSD is determined to be valid, otherwise, if the S-NSSAI is not included in the allowed NSSAI, the RSD is determined to be invalid.

[0099] When slice registration or network slice registration or S-NSSAI registration is mentioned in this document, these terms include the S-NSSAI in the requested NSSAI in the NAS Registration Request message.

[0100] Figure 6 The diagram illustrates further details of an exemplary implementation of the solution presented herein. System 600 includes UE 610, 5G access network 620, AMF / NSSF 630, and UDM / UDR 640 (Unified Data Management / Unified Data Repository). As described herein, UE 610 may include UE 110 or user equipment device 200. As described herein, AMF / NSSF 630 may include CCNF 122 or network node 300.

[0101] At 670, the network (e.g., AMF 630 based on local policy) may configure UE 610 to send additional information for slice registration type, i.e., UE 610 is configured to indicate the type or cause of S-NSSAI registration (when sending a registration request for S-NSSAI). The network (e.g., AMF 630) determines whether to configure UE 610 depending on the characteristics of the deployed network slice. For example, if network slice admission control (NSAC) is configured for S-NSSAI or network slice overload, AMF 630 may determine to request / activate reporting of slice registration type or cause in UE 610. The request / activation of reporting network slice registration type from the network to UE 610 may also be described as activation of an operating mode in UE 610, for example, the network activates / deactivates an operating mode referred to as "reporting the cause of S-NSSAI registration request".

[0102] The type or reason for slice registration can be: (a) when S-NSSAI is needed immediately, or (b) when S-NSSAI is not needed immediately but S-NSSAI may be used at any time later (i.e., proactive slice registration), or (c) when S-NSSAI is needed for a default application that is likely to send traffic (e.g., immediately or proactively).

[0103] The AMF 630 may configure the UE 610 to send additional information of the slice registration type (or reason for slice registration) by using at least one of the following procedures. During the registration procedure, by sending a Registration Accept message containing an indication of requesting / activating slice registration type reporting. During the UE 610 Configuration Update (UCU) procedure, by sending a UCU Command message containing an indication of requesting / activating slice registration type reporting to the UE 610. Once the AMF has configured the UE, the AMF may store the successful configuration in the UE's mobility context in the AMF.

[0104] Additionally or alternatively, the UE 610 may indicate (e.g., during a registration procedure) that the UE 610 supports a feature for reporting network slice registration types. For example, the UE 610 may include such support / capability indication in a 5G Mobility Management (5GMM) capability sent in a Registration Request message. In one example, the capability may indicate "support for indicating slice registration type" or an indication of similar meaning.

[0105] Note that in an alternative, the UE may be pre-configured (e.g., locally configured) to always send the type / cause of the S-NSSAI Registration Request to the AMF 630 whenever a new requested NSSAI is sent to the network. The UE may indicate this local configuration to the network in the Registration Request message. In this case, the network may avoid sending a configuration indication to the UE requiring the UE to send the type / cause of the S-NSSAI Registration Request.

[0106] At 671, when UE 610 performs a registration procedure and UE 610 constructs the requested NSSAI, UE 610 determines the registration type / reason for each S-NSSAI of the requested NSSAI. The type / reason of S-NSSAI registration may be due to (a) a need for (immediate) use, (b) proactively so that a PDU session can be directly started in this S-NSSAI when needed at some later point in time, or (c) a need for a default application (e.g., an IMS voice application for a voice-centric UE). Further details of different types of S-NSSAI registrations will be further described below.

[0107] At 672, UE 610 sends a NAS Registration Request (RR) message including the requested NSSAI to AMF 630. The RR message may include information indicating the type / cause of S-NSSAI registration.

[0108] In one example, the UE 610 may include a new parameter indicating a list of S-NSSAIs for which active registration is applicable. In another example, the UE may include a new parameter indicating a list of S-NSSAIs for immediate use by slice registration. In yet another example, the requested NSSAI containing a list of one or more S-NSSAIs may contain a flag / marker for the S-NSSAI requested for a specific type of network slice registration, e.g., marking only the S-NSSAI for active registration.

[0109] At 673, the network continues the registration process. This registration process can be based on 23.502v17.4.0 according to Figure 4 .2.2.2.2-1 to perform steps 2 to 19, and the 23.502v17.4.0 is incorporated herein by reference.

[0110] At 674a, the network 630 (e.g., AMF or NSSAF, or both) may determine that some of the network slices that the UE has requested are subject to a specific policy, such as (a) the UE should register with the slice when actual use is required, or (b) should always be requested. "Actual use" means that there is an application in the UE that sends / receives data via a PDU session through this network slice, that is, data is sent / received at least within a given time period (e.g., PDU session inactivity is less than a specific time value Tx). In other words, if the UE does not "actually use" the network slice (e.g., for time Tx), the UE should deregister from the network slice. Another policy for S-NSSAI is to allow "always requested", which means that the S-NSSAI is a default S-NSSAI where there is a default service (e.g., IMS service for voice-centric UEs, or Internet connectivity service for commercial smartphones). Note that in known techniques, the AMF may receive a list of one or more default S-NSSAIs, however, these S-NSSAIs are used in the AMF for inclusion in the allowed NSSAI if the UE does not send the requested NSSAI in the RR message. The proposed solution enhances this concept and when the actual operation mode in the AMF or NSSF is to allow only NSSAI for immediate use, the list of default NSSAIs may also be used to allow such S-NSSAIs to be included in the allowed NSSAI.

[0111] There are several options for how the AMF / NSSF 630 determines such S-NSSAI. In one option, the AMF / NSSF 630 may be locally configured (e.g., from an OAM system) with a list of S-NSSAIs for which a policy applies that the UE should register with the slice when actual use is required. In another option, the UE 610 subscription data from the UDM 640 may include an indication of any of the subscribed S-NSSAIs that the UE should register with when the S-NSSAI is actually used. In this case, when the AMF retrieves the UE subscription data from the UDM (e.g., using a Nudm_SDM_Get service operation, such as Figure 6 ), UDM 640 sends UE subscription data (such as Figure 6 ), the UE subscription data includes a list of S-NSSAIs that the UE should be allowed if the network slice is actually used. For example, such S-NSSAIs may have scarce resources.

[0112] In addition, the AMF / NSSF 630 may determine a time period Tx during which the S-NSSAI is considered to be "actually used". The time period Tx may be configured locally in the AMF 630, or may be included in the UE 610 subscription data stored in the UDM 640 (i.e., the AMF 630 receives the time period Tx from the UDM 640). If the time period Tx expires, the AMF 630 should consider deregistering the UE from the S-NSSAI, i.e., removing the S-NSSAI from the list of allowed NSSAIs of the UE 610. Network slice deregistration may be performed in one of the following ways. Network slice deregistration may be performed via explicit signaling between the AMF 630 and the UE 610 (e.g., the AMF triggers a UE configuration update (UCU) process to send a new allowed NSSAI that excludes the S-NSSAI). Network slice deregistration may be performed via implicit deregistration, where a synchronization timer is run in the UE 610 and the AMF 630, and after the timer expires, the AMF 630 and the UE 610 immediately remove the S-NSSAI from the allowed NSSAI without explicit signaling.

[0113] At 674b, AMF / NSSF 630 determines which S-NSSAIs are included in the allowed NSSAIs. When determining the allowed NSSAIs, AMF / NSSF 630 may consider at least one of the following information:

[0114] • an indication received from the UE 610 regarding the type / cause of the S-NSSAI request;

[0115] • According to step 674a, when UE 610 actually uses S-NSSAI, whether S-NSSAI complies with the policy that allows registration; or

[0116] ● Current conditions in the network, such as current network slice load. That is, if the S-NSSAI is subject to NSAC (e.g., for the number of UEs or the number of PDU sessions), the AMF may consider whether the current number of registered UEs (or the number of established PDU sessions) is close to the maximum number of UEs (or the maximum number of PDU sessions). If so, the AMF may determine to allow registration to the S-NSSAI only if the reason for registration is for immediate use.

[0117] At 675, the AMF 630 sends a Registration Accept message to the UE 610, which includes the allowed NSSAI determined in step 674b.

[0118] The AMF 630 may also use the UE Configuration Update (UCU) update procedure to send a UCU command message to the UE 610 to indicate the new allowed NSSAI.

[0119] At 676, UE 610 processes a known registration accept message, such as in accordance with 23.502 v17.4.0 Figure 4 .2.2.2.2-1 at 21, the 23.502v17.4.0 is incorporated herein by reference.

[0120] At some later time, if the App requests data connectivity and the corresponding S-NSSAI (e.g., from an RSD with a higher priority matching URSP rule or from UE local configuration) is not in the allowed NSSAI, the UE 610 first sends a request to register using the S-NSSAI before processing further RSDs or before concluding that the RSD is invalid.

[0121] according to Figure 6 The solution in

[0013] , tends to provide a benefit of providing the network with the reason for the network slice registration request. Such a reason may include "actual usage", or it may include the network slice being actively (or in advance) registered. The UE provides this information to the network during the registration process. By having this information, the network can improve the use of network slice resources by assigning network slices to UEs that currently need data connectivity.

[0122] According to another embodiment, the UE predicts the need for connectivity.

[0123] According to this further embodiment, the UE is able to "predict" whether an application will require connectivity (or will be used). The UE predicts the required connectivity a short time in advance, before the application triggers (or requires) real / actual connectivity. This can be, for example, a capability of the operating system (OS) running on the UE, or a capability of the application.

[0124] Among them, this prediction is the capability of the OS: the OS can monitor and collect statistics of the activities of different applications. For example, machine learning (ML) or artificial intelligence (AI) technology can be used to predict the connectivity requirements of applications. When the OS predicts / determines the connectivity requirements of applications, the OS can use the connection manager to trigger the establishment of connectivity, that is, the connection manager can trigger the establishment of connectivity and use URSP rules or UE local configuration to determine the S-NSSAI corresponding to the application.

[0125] Where this prediction is the application's capabilities: In this case of application capabilities, intelligent applications can request connectivity before it is actually needed.

[0126] If the UE / OS or application implements such capability, then based on the prediction, the UE requests registration with the corresponding S-NSSAI so that when the application triggers data connectivity, the S-NSSAI is already part of the allowed NSSAI.

[0127] As described herein, predicting connectivity needs tends to provide the following benefit: immediately after the application requests actual connectivity, the corresponding S-NSSAI will already be in the allowed NSSAI and the UE can start PDU session establishment. If the UE is capable of implementing such a solution, the UE can always request registration with the network slice by indicating immediate use (i.e., the UE does not need to request active registration with the S-NSSAI).

[0128] In another enhancement of this embodiment, in addition to making an early registration request to the S-NSSAI, the UE may also use the RSD component matching the URSP rule to start the PDU session establishment. In this way, when the application actually triggers the data connectivity (e.g., to the connectivity manager of the operating system), the PDU session may already be established and data transfer may start immediately.

[0129] There is further provided an arrangement in which the network provides configuration information to the UE. Configuration information indicating different types of configured S-NSSAI (i.e., different types of how the UE requests registration with the S-NSSAI) is provided to the UE. The different types of configured S-NSSAI provided to the UE may be: (A) one or more additional configured NSSAI parameters (e.g., referred to as "configured NSSAI for default registration" or "configured NSSAI for registration when used"), or (B) as a new flag for S-NSSAI in an existing configured NSSAI parameter.

[0130] The different types of configured S-NSSAI are described below:

[0131] A. The first type (or first list) of S-NSSAI contains the S-NSSAI that the UE should request to register with when data connectivity is needed (e.g., for data transmission). Data connectivity can be considered as the "actual use" of the network slice in the time period Tx (e.g., Figure 6 (described in step 674a in ).

[0132] B. The second type (or second list) of S-NSSAIs includes S-NSSAIs for which the UE may request registration proactively or at any time (ie, data connectivity on the S-NSSAI is not actually required).

[0133] C. The third type (or third list) of S-NSSAI includes S-NSSAIs that the UE should always request to register. For example, such S-NSSAI may include one or more default S-NSSAIs corresponding to default services, which are activated when the UE is powered on. In one example of a commercial smartphone, the S-NSSAI associated with the default Internet connection (e.g., for OS updates or Internet browsing) may be determined as the default S-NSSAI, which should always be included in the requested NSSAI (i.e., always requested to register).

[0134] Network (e.g. Figure 6 The AMF or NSSF 630 illustrated in FIG. 60 can be configured locally in the network function or by using a method such as Figure 6 The configured S-NSSAI list is constructed based on the UE subscription data indication described in steps 674a-1 and 674a-2 of the AMF / NSSF. In other words, the AMF / NSSF determines or knows the type of S-NSSAI, i.e., type "A" (requested when UE needs to use it), "B" (requested at any time without any specific requirements) or "C" (always requested).

[0135] The UE uses the received configuration information to determine how to construct the requested NSSAI, i.e., which S-NSSAIs are to be included in the requested NSSAI. For example, the S-NSSAI from the first list should be included in the requested NSSAI only when the S-NSSAI is to be used, i.e., at least one application in the UE requires data connectivity for this network slice. The S-NSSAI of the configured S-NSSAI from the second list may be included in the requested NSSAI at any time, i.e., the UE may actively register for such S-NSSAI or when the S-NSSAI is to be used. The NSSAI from the third list should always be included in the requested NSSAI.

[0136] Note that the UE may be provided with existing configured NSSAI information, which includes all NSSAIs that the UE can use (e.g., in the corresponding serving network), and in addition, an additional list of NSSAIs may be provided to the UE, such as when the network slice is to be used for data connectivity (i.e., the first list of NSSAIs) to be requested. In this case, the UE may internally determine another list of S-NSSAIs (e.g., the second list).

[0137] Alternatively or in addition, the network may provide the UE with (general) configuration information indicating whether the UE should request registration with a network slice only when the network slice is to be used for data connectivity. This (general) configuration information is not associated with a specific S-NSSAI, but it applies to all S-NSSAIs from the configured NSSAI or the default configured NSSAI; and may be referred to as "operation mode requesting S-NSSAI registration". As described above, this (general) configuration information may be applied with different types of configured S-NSSAI, for example, if the UE is configured to "request registration with a network slice only when the network slice is to be used", the UE will include in the requested NSSAI only the S-NSSAI required for immediate use (i.e., the UE will not include in the requested NSSAI the S-NSSAI for active slice registration). In one example, the "operation mode requesting S-NSSAI registration" may have the following values:

[0138] • "1" = UE requests registration with S-NSSAI only when an application triggers data connectivity and matches a URSP rule or the UE local configuration contains the associated S-NSSAI.

[0139] • "0" = UE may request registration with any S-NSSAI from the configured NSSAI or the default configured NSSAI.

[0140] Additionally, the network may send configuration information for a (default) S-NSSAI that the UE may always request to register with (e.g., an S-NSSAI of type "C"). During the initial registration procedure, the UE may include such a "default" NSSAI in the requested NSSAI.

[0141] Such (general) configuration information (or "operation mode requesting S-NSSAI registration") may be provided from the network to the UE in at least one of the following ways:

[0142] ● By the AMF by including the configuration information in the NAS Registration Accept message or the NAS UE Configuration Update Command message.

[0143] - By UDM by including the configuration information in the signaling for the UE parameter update procedure, e.g. similar to providing a default configured NSSAI to the UE, but including new configuration parameters, e.g. "Operation mode requesting S-NSSAI registration".

[0144] When the UE receives (general) configuration information indicating "Request S-NSSAI when needed" (or alternatively, "Operation mode requesting S-NSSAI registration" is set to "1" or activated), if the application triggers data connectivity to this S-NSSAI (i.e., matching URSP rules or UE local configuration includes S-NSSAI in NSSP) or possibly corresponding to the S-NSSAI of the default application, and the S-NSSAI is part of the configured NSSAI and not part of the rejected S-NSSAI, the UE includes the S-NSSAI in the requested NSSAI.

[0145] If no (general) configuration information is received or the configuration information indicates "Request S-NSSAI at any time allowed" (or alternatively, "Operation mode for requesting S-NSSAI registration" is set to "0" or deactivated), the UE includes the S-NSSAI in the requested NSSAI at any time as long as the S-NSSAI is part of the configured NSSAI and not part of the rejected S-NSSAI (and of course not part of the allowed NSSAI).

[0146] Thus, the wireless communication device, which may be a user equipment, has the ability to determine different types of S-NSSAI to be requested, i.e., whether for immediate / actual use or for active registration or corresponding to a default application. The wireless communication device may send an indication of whether the registration associated with the network slice (i.e., S-NSSAI) is active or for immediate / actual use. In addition, the wireless communication device may receive configuration information from the network (e.g., AMF) indicating whether the type of S-NSSAI registration (i.e., for immediate / actual use or active S-NSSAI registration) is indicated.

[0147] In addition, the wireless communication network (particularly its access and mobility management function) may be able to receive a new parameter indicating the S-NSSAI registration type. The wireless communication network may create an allowed NSSAI by taking into account the indicated S-NSSAI registration type. In addition, the wireless communication network may perform UE configuration to activate / deactivate reporting of the S-NSSAI registration type.

[0148] A method for registering a user equipment (e.g., UE) with a network slice in a communication network is provided, the method comprising the following steps: determining whether registration with one or more network slices is active or for immediate / actual use; transmitting an indication of whether registration associated with the network slice (i.e., S-NSSAI) is active or for immediate / actual use; receiving a set of allowed NSSAI (e.g., allowed NSSAI).

[0149] The method may further include, after receiving a set of allowed S-NSSAIs, and if the S-NSSAI is not part of the allowed NSSAIs, the UE may determine to request the S-NSSAI if the application requests connectivity and a matching URSP rule includes the S-NSSAI in the RSD.

[0150] The method may further include, before determining a reason to register with one or more network slices, the network (e.g., AMF), configuring the UE to include an indication of the S-NSSAI registration type (i.e., proactive or for immediate use).

[0151] Indications associated with the network slice may be transmitted as part of the requested NSSAI (e.g., a requested S-NSSAI list for active registration).

[0152] It should be noted that the above methods and apparatus illustrate rather than limit the present invention, and that a person skilled in the art will be able to design many alternative arrangements without departing from the scope of the appended claims. The word "comprising" does not exclude the presence of elements or steps other than those listed in the claims, "a" or "an" does not exclude a plurality, and a single processor or other unit may perform the functions of several units described in the claims. Any reference signs in the claims should not be construed as limiting their scope.

[0153] Furthermore, although examples are given in the context of a particular communication standard, these examples are not intended to limit the communication standards to which the disclosed methods and apparatus may be applied. For example, although specific examples have been given in the context of 3GPP, the principles disclosed herein may also be applied to another wireless communication system, and in fact to any communication system that uses wiring rules.

[0154] The method may also be embodied in a set of instructions stored on a computer readable medium, which when loaded into a computer processor, digital signal processor (DSP), etc., causes the processor to perform the method described above.

[0155] The described methods and apparatus may be practiced in other specific forms. The described methods and apparatus should be considered in all respects to be merely illustrative and not restrictive. Therefore, the scope of the present invention is indicated by the appended claims rather than by the above description. All changes within the meaning and scope of the equivalent content of the claims will be included in the scope of the claims.

[0156] The following abbreviations are relevant to the field of the present application.

[0157] 3GPP Third Generation Partnership Project

[0158] 5GS / 5GC Fifth Generation System / Fifth Generation Core Network

[0159] AMF Access and Mobility Management Function

[0160] AS Access Layer

[0161] BS Base Station

[0162] EAP Extensible Authentication Protocol

[0163] EPC / EPS Evolved Packet Core / Evolved Packet System

[0164] FB frequency band

[0165] ID Identity or identifier

[0166] IE Information Elements

[0167] LTE Long Term Evolution

[0168] MM Mobility Management

[0169] NAS Non-Access Layer

[0170] NF Network Function

[0171] NID Network Identifier

[0172] NPN Non Public Network

[0173] PNI-NPN Public Network Integrated Non-Public Network

[0174] NR New Radio

[0175] NSSAA Network Slicing-Specific Authentication and Authorization

[0176] NSSAAF Network slice-specific authentication and authorization functions

[0177] NSSAI Network Slice Selection Assistance Information

[0178] S-NSSAI Single Network Slice Selection Assistance Information

[0179] NSSF network slice selection function

[0180] OAM Operations, Control and Management

[0181] PDU Protocol Data Unit

[0182] PLMN Public Land Mobile Network

[0183] HPLMN Home Public Land Mobile Network

[0184] VPLMN Visited Public Land Mobile Network

[0185] (R)AN (Radio) Access Network

[0186] RAT Radio Access Technology / Type

[0187] RLF Radio Link Failure

[0188] RSD Routing Descriptor

[0189] SM Session Management

[0190] SMF session management functions

[0191] SNPN Standalone Non Public Network

[0192] SOR Roaming Steering

[0193] SP Service Provider

[0194] SUPI Subscription Hidden Identifier

[0195] TA / TAI Tracking Area / Tracking Area Identity

[0196] UDM Unified Data Management

[0197] UDR Unified Data Repository

[0198] UE User Equipment

[0199] URSP User Equipment Routing Selection Strategy.

Claims

1. A wireless communication device, include: a processor arranged to determine a reason for registering with the first network slice; a transceiver arranged to transmit an indication of the cause, wherein the indication is transmitted in association with the first network slice; The transceiver is further arranged to receive the identities of a set of allowed network slices.

2. A wireless communication device according to claim 1, wherein the processor is further arranged to determine whether the first network slice is identified in the set of allowed network slices or denied network slices, and if not, and if the first network slice is identified in a routing descriptor of a routing policy rule, the transceiver is arranged to send a registration request for the first network slice.

3. A wireless communication device according to claim 1 or 2, wherein the transceiver is further arranged to receive a configuration from a wireless communication network requiring the wireless communication device to include an indication of the reason for any registration with a network slice.

4. A wireless communication device according to any of the preceding claims, wherein the transceiver is arranged to transmit the indication of the reason for registering with the first network slice as part of a registration request message.

5. The wireless communication apparatus of any preceding claim, wherein the indication of the reason for registering with a first network slice comprises at least one of: The registration due to use of the first network slice indicates that application traffic is ready to be sent over the first network slice; or Active registration indicates that the application may use the first network slice at any later time; or Registration with the first network slice indicates that the default application will use the first network slice.

6. A wireless communication device according to any one of the preceding claims, wherein the wireless communication device is user equipment.

7. A method in a wireless communication device, the method include: Determining a reason for registering with the first network slice; transmitting an indication of the cause, wherein the indication is transmitted in association with the first network slice; and Receive a set of identities of allowed network slices.

8. A wireless communication network, wherein include: a transceiver arranged to receive, from a wireless communication device, an indication of a reason to register with a first network slice, wherein the indication is received in association with the first network slice; and In response to the indication, the transceiver is further arranged to send a set of identities of allowed network slices to the wireless communication device.

9. A wireless communication network according to claim 8, wherein the transceiver is further arranged to send a configuration to the wireless communication device requiring the wireless communication device to include an indication of the reason for any registration with a network slice.

10. A wireless communication network according to any one of claims 8 or 9, wherein the transceiver is arranged to receive the indication of the reason for any registration with a network slice as part of a registration request message.

11. A wireless communication network according to any one of claims 8 to 10, wherein the transceiver is further configured to receive a registration request for the first network slice from the wireless communication device.

12. A wireless communication network according to any of claims 8 to 11, wherein the wireless communication network comprises access and mobility management functionality.

13. A wireless communication network according to any one of claims 8 to 12, wherein the wireless communication network includes a network slice selection function, and wherein an access and mobility management function forwards the received reason for registering with a network slice to the network slice selection function.

14. A wireless communication network according to any one of claims 8 to 13, further comprising a processor, the processor being arranged to determine whether to allow the wireless communication device to register with the first network slice based on the received reason for registering with the first network slice.

15. A wireless communication network according to any one of claims 8 to 14, wherein the transceiver is further arranged to receive an indication associated with the first network slice as to whether registration with the first network slice is allowed when a request to register with the first network slice is received together with a specific reason for registration.

16. A wireless communication network according to claim 15, wherein the indication associated with the network slice is part of UE subscription data.

17. A method in a wireless communication network, the method include: receiving, from a wireless communication device, an indication of a reason for registering with a first network slice, wherein the indication is received in association with the first network slice; and In response to the indication, a set of identities of allowed network slices are sent to the wireless communication device.