Target network slice information for a target network slice

Abstract

Apparatuses, methods, and systems are disclosed for target network slice information for a target network slice. One method (900) includes receiving (902), from a communication device, a first message comprising information indicating a request to register for a plurality of network slices. The method (900) includes determining (904) target network slice information corresponding to the plurality of target network slices. The target network slice information comprises information indicating network slices of the plurality of network slices that are not supported in a region in which the communication device is located, and frequency-specific configurations associated with the plurality of target network slices. The method (900) includes sending (906), to a radio network entity, a second message comprising the target network slice information and the associated frequency-specific configurations.

Description

[0001] Cross-references to related applications

[0002] This application claims priority to U.S. Patent Application Serial No. 63 / 011,011, filed April 16, 2020, entitled “Apparatus, Methods, and Systems for Network-Controlled Radio Frequence Band Special Slice Selection,” which is incorporated herein by reference in its entirety. Technical Field

[0003] The topics disclosed in this article generally relate to wireless communication, and more specifically to target network slice information for a target network slice. Background Technology

[0004] In some wireless communication networks, cell selection can be performed using cells operating within a frequency band. The user equipment (“UE”) performing the cell selection may not be aware of certain useful information used to perform the cell selection. Summary of the Invention

[0005] Methods for targeting network slice information for a target network slice are disclosed. Apparatus and systems also perform the functions of these methods. One embodiment of the method includes receiving a first message from a communication device, the first message including information indicating a request to register a plurality of network slices. In some embodiments, the method includes determining target network slice information corresponding to a plurality of target network slices, wherein the target network slice information includes information indicating network slices among the plurality of network slices that are not supported in an area in which the communication device is located, and frequency-specific configurations associated with the plurality of target network slices. In some embodiments, the method includes sending a second message to a radio network entity including the target network slice information and the associated frequency-specific configuration.

[0006] An apparatus for targeting network slice information for a target network slice includes a receiver configured to receive a first message from a communication device, the first message including information indicating a request to register a plurality of network slices. In various embodiments, the apparatus includes a processor configured to determine target network slice information corresponding to a plurality of target network slices, wherein the target network slice information includes information indicating that a network slice is not supported in an area of ​​the plurality of network slices in which the communication device is located, and frequency-specific configurations associated with the plurality of target network slices. In some embodiments, the apparatus includes a transmitter configured to transmit a second message including the target network slice information and the associated frequency-specific configuration to a radio network entity.

[0007] Another embodiment of the method for providing target network slice information for a target network slice includes receiving a first message from a core network entity, wherein the first message includes target network slice information for a target network slice corresponding to a communication device, a frequency-specific configuration associated with the target network slice, or a combination thereof. In some embodiments, the method includes determining a target cell among a plurality of cells that supports the target network slice. In various embodiments, the method includes sending a second message to the communication device, wherein the second message includes target cell information and a request to connect to the target cell.

[0008] Another apparatus for targeting network slice information for a target network slice includes a receiver configured to receive a first message from a core network entity, wherein the first message includes target network slice information corresponding to a target network slice of the communication device, a frequency-specific configuration associated with the target network slice, or a combination thereof. In various embodiments, the apparatus includes a processor configured to determine a target cell among a plurality of cells that supports the target network slice. In some embodiments, the apparatus includes a transmitter configured to send a second message to the communication device, wherein the second message includes target cell information and a request to connect to the target cell.

[0009] Another embodiment of a method for target network slice information for a target network slice includes receiving a first message from a communication device, wherein the first message includes network slice preference auxiliary information indicating target network slices corresponding to a plurality of target network slices of the communication device and frequency-specific configurations associated with the plurality of target network slices. In some embodiments, the method includes determining a mobility configuration based on the network slice preference auxiliary information. In various embodiments, the method includes sending a second message to the communication device, wherein the second message includes the mobility configuration.

[0010] Another apparatus for targeting network slice information for a target network slice includes a receiver configured to receive a first message from a communication device, wherein the first message includes network slice preference assistance information indicating target network slice information corresponding to a plurality of target network slices of the communication device and frequency-specific configurations associated with the plurality of target network slices. In various embodiments, the apparatus includes a processor configured to determine a mobility configuration based on the network slice preference assistance information. In some embodiments, the apparatus includes a transmitter configured to send a second message to the communication device, wherein the second message includes the mobility configuration.

[0011] Another embodiment of the method for targeting network slice information for a target network slice includes sending a first message to a core network entity, wherein the first message includes information indicating a request to register a plurality of network slices. In some embodiments, the method includes receiving a second message including target slice information in response to sending the first message. In some embodiments, the method includes determining a frequency-specific network slice among the plurality of network slices based on the second message. In various embodiments, the method includes performing cell reselection with cells of the frequency-specific network slice. In some embodiments, the method includes sending a third message to the core network, wherein the third message includes information indicating a network slice to be registered, a service to be established, or a combination thereof among the plurality of network slices.

[0012] Another apparatus for targeting network slice information for a target network slice includes a transmitter configured to send a first message to a core network entity, wherein the first message includes information indicating a request to register a plurality of network slices. In various embodiments, the apparatus includes a receiver configured to receive a second message including target slice information in response to sending the first message. In some embodiments, the apparatus includes a processor configured to: determine frequency-specific network slices among the plurality of network slices based on the second message; and perform cell reselection using cells of the frequency-specific network slices. In some embodiments, the transmitter is configured to send a third message to the core network entity, and the third message includes information indicating a network slice to be registered among the plurality of network slices, a service to be established, or a combination thereof.

[0013] Another embodiment of the method for target network slice information for a target network slice includes sending a first message to a radio network entity, wherein the first message includes network slice preference assistance information indicating target network slice information corresponding to a plurality of target network slices of a communication device and frequency-specific configurations associated with the plurality of target network slices. In some embodiments, the method includes receiving a second message including mobility configurations from the radio network entity in response to sending the first message.

[0014] Another apparatus for targeting network slice information for a target network slice includes: a transmitter configured to send a first message to a radio network entity, wherein the first message includes network slice preference assistance information indicating target network slice information corresponding to multiple target network slices of a communication device and frequency-specific configurations associated with the multiple target network slices. In various embodiments, the apparatus includes a receiver configured to receive a second message including mobility configurations from the radio network entity in response to sending the first message. Attached Figure Description

[0015] A more detailed description of the embodiments briefly described above will be presented by referring to the specific embodiments shown in the accompanying drawings. It should be understood that these drawings depict only some embodiments and are not intended to be limiting of the scope; the embodiments will be described and explained with additional specificity and detail using the drawings, wherein:

[0016] Figure 1 This is a schematic block diagram illustrating one embodiment of a wireless communication system for target network slice information.

[0017] Figure 2 This is a schematic block diagram illustrating one embodiment of an apparatus that can be used for target network slice information of a target network slice;

[0018] Figure 3 This is a schematic block diagram illustrating one embodiment of an apparatus that can be used for target network slice information of a target network slice;

[0019] Figure 4 This is a schematic block diagram illustrating one embodiment of communication used for cell selection;

[0020] Figure 5 This is a schematic block diagram illustrating another embodiment of communication used for cell selection;

[0021] Figure 6 This is a communication diagram illustrating yet another embodiment of communication used for cell selection;

[0022] Figure 7 This is a communication diagram illustrating yet another embodiment of communication used for cell selection;

[0023] Figure 8 This is a communication diagram illustrating yet another embodiment of communication used for cell selection;

[0024] Figure 9 This is a flowchart illustrating an embodiment of a method for using target network slice information in target network slicing;

[0025] Figure 10This is a flowchart illustrating another embodiment of a method for using target network slice information in target network slicing;

[0026] Figure 11 This is a flowchart illustrating another embodiment of a method for using target network slice information in target network slicing;

[0027] Figure 12 This is a flowchart illustrating yet another embodiment of a method for using target network slice information in target network slicing; and

[0028] Figure 13 This is a flowchart illustrating another embodiment of a method for using target network slice information in target network slicing. Detailed Implementation

[0029] As those skilled in the art will understand, aspects of the embodiments can be embodied as a system, apparatus, method, or program product. Therefore, embodiments can take the form of a completely hardware embodiment, a completely software embodiment (including firmware, resident software, microcode, etc.), or an embodiment combining software and hardware aspects, which may generally be referred to herein as "circuit," "module," or "system." Furthermore, embodiments can take the form of a program product embodied in one or more computer-readable storage devices stored in machine-readable code, computer-readable code, and / or program code, hereinafter referred to as "code." The storage device can be tangible, non-transitory, and / or non-transferable. The storage device may not embody signals. In one embodiment, the storage device only employs signals for accessing the code.

[0030] Certain functional units described in this specification may be designated as modules to more specifically emphasize their implementation independence. For example, a module may be implemented as hardware circuitry comprising custom-designed very large-scale integration (“VLSI”) circuitry or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. Modules may also be implemented in programmable hardware devices such as field-programmable gate arrays, programmable array logic, programmable logic devices, etc.

[0031] Modules can also be implemented in code and / or software to be executed by various types of processors. The identified code module may, for example, comprise one or more physical or logical blocks of executable code, which may be organized, for example, as objects, procedures, or functions. However, the executable files of the identified module do not need to be physically located together, but may include unrelated instructions stored in different locations, which, when logically connected together, constitute the module and achieve the module's stated purpose.

[0032] In practice, a code module can be a single instruction or many instructions, and can even be distributed across several different code segments, different programs, and spanning several memory devices. Similarly, in this document, operational data can be identified and visualized within a module, and can be represented in any suitable form and organized within any suitable type of data structure. Operational data can be collected as a single dataset or can be distributed across different locations, including different computer-readable storage devices. Where a module or part of a module is implemented in software, the software portion is stored on one or more computer-readable storage devices.

[0033] Any combination of one or more computer-readable media may be used. A computer-readable medium may be a computer-readable storage medium. A computer-readable storage medium may be a storage device for storing code. A storage device may be, for example, but not limited to, electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor systems, apparatuses, or devices, or any suitable combination thereof.

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

[0035] The code used to perform the operations of the embodiments can be any number of lines and can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Python, Ruby, Java, Smalltalk, C++, and traditional procedural programming languages ​​such as the "C" programming language, and / or machine languages ​​such as assembly language. The code can be executed entirely on the user's computer, partially on the user's computer, or as a standalone software package on the user's computer, partially on a remote computer, or entirely on a remote computer or server. In the latter case, the remote computer can be connected to the user's computer via any type of network, including a local area network ("LAN") or a wide area network ("WAN"), or can be connected to an external computer (e.g., via the Internet through an Internet service provider).

[0036] References to "an embodiment," "embodiment," or similar language in this specification mean that a particular feature, structure, or characteristic described in connection with that embodiment is included in at least one embodiment. Therefore, unless expressly stated otherwise, throughout this specification, the phrases "in an embodiment," "in an embodiment," and similar language may, but not necessarily all refer to the same embodiment, but rather mean "one or more, but not all, embodiments." Unless expressly stated otherwise, the terms "comprising," "including," "having," and variations thereof mean "including, but not limited to,". Unless expressly stated otherwise, the list of enumerated items does not imply that any or all items are mutually exclusive. Unless expressly stated otherwise, the terms "a," "an," and "the" also mean "one or more".

[0037] Furthermore, the features, structures, or characteristics of the described embodiments can be combined in any suitable manner. Numerous specific details, such as examples of programming, software modules, user selection, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., are provided in the following description to provide a thorough understanding of the embodiments. However, those skilled in the art will recognize that the embodiments can be practiced without one or more of these specific details, or using other methods, components, materials, etc. In other instances, well-known structures, materials, or operations have not been shown or described in detail to avoid obscuring some aspects of the embodiments.

[0038] The following description of various aspects of the embodiments is based on schematic flowcharts and / or schematic block diagrams of methods, apparatus, systems, and program products according to the embodiments. It will be understood that each block of the schematic flowcharts and / or schematic block diagrams, and combinations of blocks in the schematic flowcharts and / or schematic block diagrams, can be implemented by code. The code can be provided to a processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to generate machinery, such that instructions executable via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / operations specified in the blocks or blocks of the schematic flowcharts and / or schematic block diagrams.

[0039] The code may also be stored in a storage device that can instruct 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 art including instructions that implement the functions / operations specified in the boxes or some boxes of the schematic flowchart and / or schematic block diagram.

[0040] The code may also be loaded onto a computer, other programmable data processing apparatus or other device, causing a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer-implemented process, such that the code executing on the computer or other programmable apparatus provides a process for implementing the functions / operations specified in the boxes or some boxes of the flowchart and / or block diagram.

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

[0042] It should also be noted that in some alternative implementations, the functions marked in the boxes may occur in a different order than those shown in the figures. For example, depending on the functions involved, two boxes shown consecutively may actually be executed substantially simultaneously, or these boxes may sometimes be executed in reverse order. Other steps and methods that are functionally, logically, or effectively equivalent to one or more boxes or portions thereof in the illustrated figures are conceivable.

[0043] While various arrow and line types may be used in flowcharts and / or block diagrams, it should be understood that they do not limit the scope of the respective embodiments. In fact, some arrows or other connectors may be used solely to indicate the logical flow of the depicted embodiment. For example, an arrow may indicate a wait or monitoring period of unspecified duration between enumeration steps in a depicted embodiment. It will also be noted that each block in the block diagram and / or flowchart, as well as combinations of blocks in the block diagram and / or flowchart, can be implemented by a dedicated hardware-based system performing a specific function or operation, or by a combination of dedicated hardware and code.

[0044] The description of the elements in each figure can be referenced to the elements in the preceding figures. The same numbers refer to the same elements in all figures, including alternative embodiments of the same elements.

[0045] Figure 1 An embodiment of a wireless communication system 100 for targeting network slice information is described. In one embodiment, the wireless communication system 100 includes a remote unit 102 and a network unit 104. Although Figure 1 A specific number of remote units 102 and network units 104 are depicted, but those skilled in the art will recognize that any number of remote units 102 and network units 104 may be included in the wireless communication system 100.

[0046] In one embodiment, remote unit 102 may include computing devices such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smartphones, smart TVs (e.g., internet-connected televisions), set-top boxes, game consoles, security systems (including surveillance cameras), in-vehicle computers, network devices (e.g., routers, switches, modems), aircraft, drones, etc. In some embodiments, remote unit 102 includes wearable devices such as smartwatches, fitness bands, optical head-mounted displays, etc. Furthermore, remote unit 102 may be referred to as a subscriber unit, mobile device, mobile station, user, terminal, mobile terminal, fixed terminal, subscriber station, UE, user terminal, device, or other terms used in the art. Remote unit 102 may communicate directly with one or more network units 104 via UL communication signals. In some embodiments, remote unit 102 may communicate directly with other remote units 102 via sidelink communication.

[0047] Network unit 104 may be distributed across a geographical area. In some embodiments, network unit 104 may also be referred to as and / or may include access point, access terminal, basic, base station, core network (“CN”), radio network entity, node-B, evolved node-B (“eNB”), 5G node-B (“gNB”), home node-B, relay node, device, core network, air server, radio access node, access point (“AP”), new radio (“NR”), network entity, access and mobility management function (“AMF”), unified data management (“UDM”), unified data repository (“UDR”), UDM / UDR, policy control function (“PCF”), radio access network (“RAN”), network slice selection function (“NSSF”), operations, administration and management (“OAM”), session management function (“SMF”), user plane function (“UPF”), application function, authentication server function (“AUSF”), security anchor functionality (“SEAF”), trusted non-3GPP gateway function (“TNGF”), or any other term used in the art. Network unit 104 is typically part of a radio access network that includes one or more controllers communicatively coupled to one or more corresponding network units 104. The radio access network is typically communicatively coupled to one or more core networks, which may be coupled to other networks such as the Internet and the public switched telephone network, etc. These and other elements of the radio access and core networks are not illustrated, but are generally well known to those skilled in the art.

[0048] In one implementation, the wireless communication system 100 conforms to the NR protocol standardized in the 3rd Generation Partnership Project (“3GPP”), wherein network unit 104 transmits using an OFDM modulation scheme on the downlink (“DL”), and remote unit 102 transmits using a single-carrier frequency division multiple access (“SC-FDMA”) scheme or an orthogonal frequency division multiplexing (“OFDM”) scheme on the uplink (“UL”). However, more generally, the wireless communication system 100 may implement other open or proprietary communication protocols, such as WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, and CDMA2000. Protocols such as ZigBee and Sigfoxx. This disclosure is not intended to be limited to any particular wireless communication system architecture or protocol implementation.

[0049] Network unit 104 can serve multiple remote units 102 within a service area, such as a cell or cell sector, via a wireless communication link. Network unit 104 transmits DL communication signals to serve the remote units 102 in the time, frequency, and / or spatial domains.

[0050] In various embodiments, network unit 104 may receive a first message from a communication device, the first message including information indicating a request to register multiple network slices. In some embodiments, network unit 104 may determine target network slice information corresponding to multiple target network slices, wherein the target network slice information includes information indicating network slices among the multiple network slices that are not supported in the area where the communication device is located, and frequency-specific configurations associated with the multiple target network slices. In some embodiments, network unit 104 may send a second message to a radio network entity including the target network slice information and the associated frequency-specific configuration. Therefore, network unit 104 may be configured to target network slice information for target network slices.

[0051] In some embodiments, network unit 104 may receive a first message from a core network entity, wherein the first message includes target network slice information corresponding to a target network slice of the communication device, a frequency-specific configuration associated with the target network slice, or a combination thereof. In some embodiments, network unit 104 may determine a target cell among a plurality of cells that supports the target network slice. In various embodiments, network unit 104 may send a second message to the communication device, wherein the second message includes target cell information and a request to connect to the target cell. Therefore, network unit 104 can be used for target network slice information for a target network slice.

[0052] In various embodiments, network unit 104 may receive a first message from a communication device, wherein the first message includes network slice preference assistance information indicating target network slice information corresponding to a plurality of target network slices of the communication device, and frequency-specific configurations associated with the plurality of target network slices. In some embodiments, network unit 104 may determine a mobility configuration based on the network slice preference assistance information. In various embodiments, network unit 104 may send a second message to the communication device, wherein the second message includes the mobility configuration. Therefore, network unit 104 can be used for target network slice information for target network slices.

[0053] In some embodiments, remote unit 102 may send a first message to a core network entity, wherein the first message includes information indicating a request to register multiple network slices. In some embodiments, remote unit 102 may receive a second message including target slice information in response to sending the first message. In some embodiments, remote unit 102 may determine a frequency-specific network slice among the multiple network slices based on the second message. In various embodiments, remote unit 102 may perform cell reselection using cells of the frequency-specific network slice. In some embodiments, remote unit 102 may send a third message to the core network entity, wherein the third message includes information indicating a network slice among the multiple network slices to be registered, a service to be established, or a combination thereof. Therefore, remote unit 102 can be used for target network slice information for a target network slice.

[0054] In various embodiments, remote unit 102 may send a first message to a radio network entity, wherein the first message includes network slice preference assistance information indicating target network slice information corresponding to multiple target network slices of a communication device, and frequency-specific configurations associated with the multiple target network slices. In some embodiments, remote unit 102 may receive a second message including mobility configurations from the radio network entity in response to sending the first message. Therefore, remote unit 102 can be used for target network slice information for target network slices.

[0055] Figure 2An embodiment of an apparatus 200 that can be used for target network slice information is depicted. The apparatus 200 includes one embodiment of a remote unit 102. Furthermore, the remote unit 102 may include a processor 202, a memory 204, an input device 206, a display 208, a transmitter 210, and a receiver 212. In some embodiments, the input device 206 and the display 208 are combined into a single device, such as a touchscreen. In some embodiments, the remote unit 102 may not include any input device 206 and / or the display 208. In various embodiments, the remote unit 102 may include one or more of the processor 202, memory 204, transmitter 210, and receiver 212, and may not include the input device 206 and / or the display 208.

[0056] In one embodiment, processor 202 may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, processor 202 may be a microcontroller, microprocessor, central processing unit (“CPU”), graphics processing unit (“GPU”), auxiliary processing unit, field-programmable gate array (“FPGA”), or similar programmable controller. In some embodiments, processor 202 executes instructions stored in memory 204 to perform the methods and routines described herein. Processor 202 is communicatively coupled to memory 204, input device 206, display 208, transmitter 210, and receiver 212.

[0057] In one embodiment, memory 204 is a computer-readable storage medium. In some embodiments, memory 204 includes volatile computer storage media. For example, memory 204 may include RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). In some embodiments, memory 204 includes non-volatile computer storage media. For example, memory 204 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 204 includes both volatile and non-volatile computer storage media. In some embodiments, memory 204 also stores program code and related data, such as operating systems and other controller algorithms operating on remote unit 102.

[0058] In one embodiment, input device 206 may include any known computer input device, including a touchpad, button, keyboard, stylus, microphone, etc. In some embodiments, input device 206 may be integrated with display 208, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, input device 206 includes a touchscreen, enabling text input using a virtual keyboard displayed on the touchscreen and / or by handwriting on the touchscreen. In some embodiments, input device 206 includes two or more distinct devices such as a keyboard and a touchpad.

[0059] In one embodiment, display 208 may include any known electronically controllable display or display device. Display 208 may be designed to output visual, auditory, and / or tactile signals. In some embodiments, display 208 includes an electronic display capable of outputting visual data to a user. For example, display 208 may include, but is not limited to, a liquid crystal display (“LCD”), a light-emitting diode (“LED”) display, an organic light-emitting diode (“OLED”) display, a projector, or similar display devices capable of outputting images, text, etc., to a user. As another non-limiting example, display 208 may include wearable displays such as smartwatches, smart glasses, head-up displays, etc. Furthermore, display 208 may be a component of a smartphone, personal digital assistant, television, desktop computer, laptop computer, personal computer, vehicle dashboard, etc.

[0060] In some embodiments, display 208 includes one or more speakers for generating sound. For example, display 208 may generate an audible alarm or notification (e.g., a buzzer or beep). In some embodiments, display 208 includes one or more haptic devices for generating vibration, motion, or other haptic feedback. In some embodiments, all or part of display 208 may be integrated with input device 206. For example, input device 206 and display 208 may form a touchscreen or similar touch-sensitive display. In other embodiments, display 208 may be located near input device 206.

[0061] In some embodiments, transmitter 210 is configured to send a first message to a core network entity, wherein the first message includes information indicating a request to register a plurality of network slices. In various embodiments, receiver 212 is configured to receive a second message including target slice information in response to sending the first message. In some embodiments, processor 202 is configured to: determine a frequency-specific network slice among the plurality of network slices based on the second message; and perform cell reselection with cells of the frequency-specific network slice. In some embodiments, transmitter 210 is configured to send a third message to the core network entity, and the third message includes information indicating a network slice among the plurality of network slices to be registered, a service to be established, or a combination thereof.

[0062] In various embodiments, transmitter 210 is configured to send a first message to a radio network entity, wherein the first message includes network slice preference assistance information indicating target network slice information corresponding to multiple target network slices of a communication device, and frequency-specific configurations associated with the multiple target network slices. In various embodiments, receiver 212 is configured to receive a second message including mobility configurations from the radio network entity in response to sending the first message.

[0063] Although only one transmitter 210 and one receiver 212 are illustrated, the remote unit 102 may have any suitable number of transmitters 210 and receivers 212. The transmitters 210 and receivers 212 may be of any suitable type. In one embodiment, the transmitters 210 and receivers 212 may be part of a transceiver.

[0064] Figure 3 An embodiment of an apparatus 300 that can be used for target network slice information is depicted. The apparatus 300 includes one embodiment of a network unit 104. Furthermore, the network unit 104 may include a processor 302, a memory 304, an input device 306, a display 308, a transmitter 310, and a receiver 312. It will be understood that the processor 302, memory 304, input device 306, display 308, transmitter 310, and receiver 312 may be substantially similar to the processor 202, memory 204, input device 206, display 208, transmitter 210, and receiver 212 of the remote unit 102, respectively.

[0065] In some embodiments, receiver 312 is configured to receive a first message from a communication device, the first message including information indicating a request to register multiple network slices. In various embodiments, processor 302 is configured to determine target network slice information corresponding to multiple target network slices, wherein the target network slice information includes information indicating network slices among the multiple network slices that are not supported in the area where the communication device is located, and frequency-specific configurations associated with the multiple target network slices. In some embodiments, transmitter 310 is configured to send a second message to a radio network entity including the target network slice information and the associated frequency-specific configuration.

[0066] In some embodiments, receiver 312 is configured to receive a first message from a core network entity, wherein the first message includes target network slice information corresponding to a target network slice of the communication device, a frequency-specific configuration associated with the target network slice, or a combination thereof. In various embodiments, processor 302 is configured to determine a target cell among a plurality of cells that supports the target network slice. In some embodiments, transmitter 310 is configured to send a second message to the communication device, wherein the second message includes target cell information and a request to connect to the target cell.

[0067] In various embodiments, receiver 312 is configured to receive a first message from a communication device, wherein the first message includes network slice preference assistance information indicating target network slice information corresponding to a plurality of target network slices of the communication device, and frequency-specific configurations associated with the plurality of target network slices. In various embodiments, processor 302 is configured to determine a mobility configuration based on the network slice preference assistance information. In some embodiments, transmitter 310 is configured to send a second message to the communication device, wherein the second message includes the mobility configuration.

[0068] In some embodiments, network slicing features enable network operators to optimize the implementation of customized functionality and network operations specific to market needs. In various embodiments, network slicing features can be tools used by network operators to improve support for services and specific deployment scenarios.

[0069] In some embodiments, a network slice can be a logical network that provides specific network capabilities and characteristics (e.g., it allows for customized functionality and optimized network operation implementations specific to market scenarios); it may always consist of a RAN portion and a CN portion; and it can be identified by S-NSSAI. While the network can support a large number of slices (e.g., hundreds), the UE does not need to support more than eight slices simultaneously. Services in different slices can be handled by different Protocol Data Unit (“PDU”) sessions.

[0070] In some embodiments, a network slice instance can be a collection of network function (“NF”) instances and can have the resources required to form a deployed network slice (e.g., compute, storage, and networking resources) and can include CN C-plane and U-plane NFs and / or Next Generation RAN (“NG-RAN”). Furthermore, a network slice instance can be associated with one or more S-NSSAIs. Multiple network slice instances can be associated with the same S-NSSAI and can be deployed in the same or different tracking areas.

[0071] In various embodiments, the network can simultaneously serve a single UE with one or more network slice instances via a fifth-generation access network (“5G-AN”), regardless of the access type the UE has registered on it (e.g., 3GPP access and / or non-3GPP access). In some embodiments, the AMF instance serving the UE can logically belong to each of the network slice instances serving the UE (e.g., this AMF instance can be shared by the network slice instances serving the UE).

[0072] In some embodiments, S-NSSAI uniquely identifies a network slice and may include: 1) a slice and / or service type (“SST”), which may refer to the expected network slice behavior in terms of characteristics and services—the SST field may have normalized and non-normalized values: values ​​0 to 127 belong to the normalized SST range and values ​​128 to 255 belong to the operator-specific range; 2) a slice distinguisher (“SD”), which may be optional information that complements the SST to distinguish multiple network slices of the same SST. For example, for an SST of value-enhanced mobile broadband (“eMBB”), multiple SDs may be defined, such as “Company X eMBB slice”, “Company YeMBB slice”, etc.

[0073] In various embodiments, UE subscription data in the UDM and / or UDR may store a list of S-NSSAIs for which the UE is subscribed to for use in a PLMN (e.g., in the home or visited PLMN). Based on operator policy, one or more subscribed S-NSSAIs may be marked as the default S-NSSAI. If an S-NSSAI is marked as default, the network can be expected to serve the UE with the relevant applicable network slice instance if the UE does not send any permitted S-NSSAIs to the network as part of the requested network slice selection assistance information (“NSSAI”) in the registration request message. The UE can be configured with network slice configurations: 1) Allowed S-NSSAI: derived by the network from subscribed S-NSSAI; includes S-NSSAI valid for the current registration area and the access type provided by the AMF to which the UE has registered; used by the UE (e.g., for the information element ("IE") "Requested NSSAI" in a Non-Access Stratum ("NAS") registration request message); and 2) Configured S-NSSAI: derived by the network from subscribed S-NSSAI; used by the UE if there is no allowed S-NSSAI for the current PLMN; includes only S-NSSAI values ​​from the serving PLMN (e.g., can be either the Home Public Land Mobile Network ("HPLMN") or the Visited Public Land Mobile Network ("VPLMN")); obtained from the AMF upon successful completion of the UE's registration process on the access type or as part of the UE's network slice configuration update process; used by the UE (e.g., for the IE "Requested NSSAI" in a NAS registration request message).

[0074] In some embodiments, PLMN selection and cell selection and / or reselection can be performed by the UE without any slice awareness. This means that when selecting a suitable cell, the UE sends a NAS registration request message, which can be rejected by the AMF if the current area and / or cell does not support any S-NSSAI that the UE wants to register for (e.g., using the IE "Requested NSSAI" in the registration request message).

[0075] In some embodiments, network slicing may support specific frequency bands. In such embodiments, the combination of frequency bands and network slices can be a valuable tool for operators requiring service isolation and / or management, as well as maximizing the use of 5G frequency bands. For example, an eMBB slice (S-NSSAI 1) may only be supported in the 2.6 GHz band (RAN Area 1), while an Ultra-Reliable Low Latency Communication (“URLLC”) slice (S-NSSAI 2) may only be supported in the 4.9 GHz band (RAN Area 2). In various embodiments, lower frequency bands may be used for MIoT, while higher frequency bands may be used for eMBB services. If the UE is within the coverage area of ​​both RAN Area 1 and RAN Area 2, the UE can perform the registration process via a suitable cell in RAN Area 1 or RAN Area 2. If the S-NSSAI subscribed to by the UE only includes S-NSSAI 2 and the UE camps in a cell that does not support S-NSSAI 2, registration to a network that includes S-NSSAI 2 may fail. In such a configuration, the UE may attempt to register from an area and / or cell that supports S-NSSAI 2, which may take some time. However, if the UE cannot successfully register with the intended slice, it cannot register in the network or be reached by the network via paging. Therefore, in various embodiments, the UE can perform cell selection for cells operating in the frequency band of a specific network slice.

[0076] In some embodiments, if the UE can successfully register to any RAN area and if the UE's subscribed S-NSSAI includes both S-NSSAI 1 and S-NSSAI 2, then the frequency band-specific configuration of the network slice can be used. However, if the UE wants to initiate URLLC services while residing on an eMBB slice in RAN area 1, the NAS service request message sent by the UE may be rejected. Therefore, the UE may attempt to register from an area and / or cell that supports URLLC slices, which may take some time. In some embodiments, the UE may be able to perform service-initiated cell selection for cells operating in the frequency band of a specific network slice.

[0077] In various embodiments, the following three network control methods can be used to enable the UE to perform cell selection if a radio band-specific slice configuration exists; or to enable the UE to perform service-initiated cell selection for a cell operating in a specific network slice's band.

[0078] In the first method, the IE “Rejected NSSAI” can be extended with the following options, and for each S-NSSAI value signaled in the IE “Rejected NSSAI”, the AMF can associate: 1) Target frequency information that may contain a list of target carrier frequencies supporting the rejected S-NSSAI value - this list may contain one or more entries, and for each entry, a carrier frequency priority index may also be associated - the carrier frequency priority index may be in an integer range (e.g., 0..7), where a value of 0 indicates the lowest priority and a value of 7 indicates the highest priority - this signaling option can be used if the IE “Rejected NSSAI” is signaled between the AMF and RAN nodes (e.g., as part of an N2 downlink NAS transmission or handover request message), and if the IE “Rejected NSSAI” is signaled between RAN node UEs (e.g., as part of an RRC release or RRC reconfiguration message) - through this target frequency information: i) the RAN node can set system information carrying cell reselection parameters or redirection information in the RRC release message or Accordingly, a handover to the target RAN node is initiated; ii) the UE can trigger priority-based cell reselection or handover on the relevant carrier frequency; and / or 2) the target frequency information can contain a list of target frequency bands that support the rejected S-NSSAI value - the list can contain one or more entries, and for each entry, a frequency band priority index can also be associated - the frequency band priority index can be in the range of integers (e.g., 0..7), where a value of 0 indicates the lowest priority and a value of 7 indicates the highest priority - this signaling option can be used if the IE "Rejected NSSAI" is signaled between the AMF and the UE (e.g., as part of a NAS registration rejection or registration acceptance message) - with this target frequency information, the UE can trigger priority-based cell reselection on the relevant frequency band - furthermore, this signaling option can be used if the IE "Rejected NSSAI" is signaled between the AMF and the RAN node via an N2 message - with this information, the RAN node can determine the UE's mobility (e.g., cell reselection and handover) (e.g., setting system information carrying cell reselection parameters accordingly).

[0079] In the second method, the IE "Requested NSSAI" in the NAS registration request message is extended with the parameter "Frequency Band Indication". With this parameter, the UE can request additional information from the AMF regarding the frequency band supporting the requested S-NSSAI. Alternatively, the parameter "Carrier Frequency Indication" can be set in the IE "Requested NSSAI". With this parameter, the UE can request from the AMF to receive additional information regarding the carrier frequency supporting the requested S-NSSAI.

[0080] In the third approach, the UL RRC UE assistance information message is extended with "slice preference assistance" information, which contains frequency information for preferred slice configuration. The UE can derive the frequency information for preferred slice configuration based on target frequency information received from rejected S-NSSAI. This "slice preference assistance" information may contain one or more entries. If more than one entry is contained, the given order reflects the priority of the preference (e.g., the first entry indicates the highest priority, and so on). With the new "slice preference assistance" information, the UE can indicate to the RAN node that its preference has been redirected or switched to the preferred slice configuration. The RAN node can use the information received from the UE as input for slice-specific mobility processing (e.g., setting measurement configuration, etc.). Instead of the UE assistance information message, any other appropriate UL RRC message (e.g., RRCReconfigurationComplete, RRCSetupComplete, etc.) can be used to carry the "slice preference assistance" information.

[0081] It should be noted that although some of the embodiments found herein are described with respect to NR RATs connected to a 5G core network (“5GC”), they can also be applied to Enhanced Universal Terrestrial Radio Access (“E-UTRA”) RATs connected to a 5GC.

[0082] In the first embodiment: there may be RAN area coverage as described herein; the UE's configured NSSAI only contains S-NSSAI 2 (e.g., URLLC slice); after PLMN and initial cell selection, the UE is camped on a suitable cell in the RAN area served by the source RAN node; and the UE attempts to initially register with the network and sends S-NSSAI 2 in the IE "Requested NSSAI" within the registration request message.

[0083] Figure 4 This is a schematic block diagram illustrating one embodiment of communication 400 for cell selection according to a first embodiment. The illustrated communication 400 includes communication between UE 402, source RAN node 404, target RAN node 406, and AMF 408. As will be understood, each of the illustrated communications 400 may include one or more messages.

[0084] In the first communication 410 sent between UE 402 and source RAN node 404, an RRC connection is established between UE 402 and source RAN node 404.

[0085] In the second communication 412, sent from UE 402 to source RAN node 404, and in the third communication 414, sent from source RAN node 404 to AMF 408, UE 402 sends a registration request message (e.g., a NAS registration request message) to AMF 408. The registration request message includes the requested S-NSSAI 2.

[0086] In the fourth communication 416 sent from AMF 408 to source RAN node 404, after successful UE authentication, AMF 408 retrieves UE subscription information from UDM and / or UDR (or from the legacy AMF), where the subscription information contains S-NSSAI 2 as the subscribed S-NSSAI. AMF 408 determines that RAN area 1 does not support S-NSSAI 2, but RAN area 2 does. AMF 408 sends the UE context to source RAN node 404 using an N2 message (e.g., UE initial context setting), which includes information about the rejected S-NSSAI 2 and the target carrier frequency supporting the rejected S-NSSAI 2. Source RAN node 404 establishes AS security with the UE.

[0087] In the fifth communication 418 sent from AMF 408 to UE 402, AMF 408 sends a registration rejection message to UE 402, which includes S-NSSAI 2 in the IE “Rejected S-NSSAI” and the reason value “S-NSSAI is not available in the current registration area”.

[0088] In the sixth communication 420 sent from source RAN node 404 to UE 402, source RAN node 404 releases the RRC connection by sending an RRC release message to UE 402 that includes target carrier frequency information (e.g., related to the rejected S-NSSAI 2). UE 402 accepts the redirection information in the RRC release message.

[0089] In the seventh communication 422 transmitted between UE 402 and target RAN node 406, based on the redirection information in the received RRC release message, UE 402 reselects a suitable cell on the target carrier frequency of RAN area 2 served by target RAN node 406. UE 402 and target RAN node 406 establish an RRC connection.

[0090] In the eighth communication 424 from UE 402 to target RAN node 406 and the ninth communication 426 from target RAN node 406 to AMF 408, UE 402 sends a registration request message (e.g., NAS registration request message) to AMF 408 (including the requested S-NSSAI 2) via target RAN node 406.

[0091] In the tenth communication 428 sent from AMF 408 to UE 402, AMF 408 can re-authenticate UE 402 and retrieve subscription information (e.g., from UDM and / or UDR or from the legacy AMF). AMF 408 determines that RAN Area 2 supports S-NSSAI2 and completes the registration process. AMF 408 sends a request for S-NSSAI2 registration acceptance message to UE 402.

[0092] In the second embodiment: there may be RAN area coverage as described herein; the UE's configured NSSAI only contains S-NSSAI 2 (e.g., URLLC slice); after PLMN and initial cell selection, the UE is camped on a suitable cell in the RAN area served by the source RAN node; and the UE attempts to initially register with the network and sends S-NSSAI 2 in the IE "Requested NSSAI" within the registration request message.

[0093] Figure 5 This is a schematic block diagram illustrating another embodiment of communication 500 for cell selection. The illustrated communication 500 includes communication between UE 502, source RAN node 504, target RAN node 506, and AMF 508. As will be understood, each of the illustrated communications 500 may include one or more messages.

[0094] In the first communication 510 sent between UE 502 and source RAN node 504, an RRC connection is established between UE 502 and source RAN node 504.

[0095] In the second communication 512, sent from UE 502 to source RAN node 504, and in the third communication 514, sent from source RAN node 504 to AMF 508, UE 502 sends a registration request message (e.g., a NAS registration request message) to AMF 508. The registration request message includes the requested S-NSSAI 2.

[0096] In the fourth communication 516 sent from AMF 508 to UE 502, after establishing NAS security and retrieving subscription information from UDM and / or UDR (or from the old AMF), AMF 508 determines that S-NSSAI 2 is not supported by RAN area 1 and sends a registration rejection message to UE 502. The message contains information about the rejected S-NSSAI 2, the reason value "S-NSSAI is not available in the current registration area", and the target frequency band supporting the rejected S-NSSAI 2.

[0097] In the fifth communication 518 sent from the source RAN node 504 to the UE 502, the source RAN node 504 sends an RRC release message to the UE 502 without any redirection information.

[0098] In the sixth communication 520 transmitted between UE 502 and target RAN node 506, based on the target frequency band information received in the registration rejection message, UE 502 reselects a suitable cell on the target frequency band of the indicated RAN area served by target RAN node 506. UE 502 and target RAN node 506 establish an RRC connection.

[0099] In the seventh communication 522, which is sent from the UE 502 to the target RAN node 506, and the eighth communication 524, which is sent from the target RAN node 506 to the AMF 508, the UE 502 sends a registration request message (e.g., a NAS registration request message) to the AMF 508 via the target RAN node 506 (including the requested S-NSSAI 2).

[0100] In the ninth communication 526 sent from AMF 508 to UE 502, AMF 508 determines that S-NSSAI 2 is supported by RAN area 2 and sends a registration acceptance message for the requested S-NSSAI 2 to UE 502.

[0101] In the third embodiment: there may be RAN area coverage as described herein; the UE's configured NSSAI only contains S-NSSAI 2 (e.g., URLLC slice); after PLMN and initial cell selection, the UE is camped on a suitable cell in the RAN area served by the source RAN node; and the UE attempts to initially register with the network and sends S-NSSAI 2 in the IE "Requested NSSAI" within the registration request message.

[0102] Figure 6 This is a communication diagram illustrating another embodiment of communication 600 for cell selection. The illustrated communication 600 includes communication between UE 602, source RAN node 604, target RAN node 606, and AMF 608. As will be understood, each of the illustrated communications 600 may include one or more messages.

[0103] In the first communication 610 sent between UE 602 and source RAN node 604, an RRC connection is established between UE 602 and source RAN node 604.

[0104] In the second communication 612, sent from UE 602 to source RAN node 604, and in the third communication 614, sent from source RAN node 604 to AMF 608, UE 602 sends a registration request message (e.g., a NAS registration request message) to AMF 608. The registration request message includes the requested S-NSSAI 2.

[0105] In the fourth communication 616 sent from AMF 608 to source RAN node 604, AMF 608 determines that S-NSSAI 2 is not supported by RAN area 1 and sends information about the rejected S-NSSAI 2 via an N2 message (e.g., N2 downlink NAS transmission), which includes the target carrier frequency supporting the rejected S-NSSAI 2 and the target RAN node identity to source RAN node 604.

[0106] In the fifth communication 618 transmitted between the source RAN node 604 and the target RAN node 606, based on information received from the AMF 608, the source RAN node 604 and the target RAN node 606 prepare for an inter-frequency handover (“HO”), which includes admission control, radio resource configuration in the target RAN node 606, etc. In this context, the following may occur: i) if a signaling radio bearer (“SRB”) has been set up between the UE 602 and the source RAN node 604, a “blind” HO (in the absence of any measurements received from the UE 602) can be performed; and ii) based on the measurement results received by the source RAN node 604 from the UE 602 after the DRB is set up (e.g., in the case of a mobile-only initiated connection (“MICO”) mode).

[0107] In the sixth communication 620 sent from source RAN node 604 to UE 602, source RAN node 604 triggers a handover by sending an RRC reconfiguration message to UE 602. The RRC reconfiguration message contains information about the rejected Single Network Slice Selection Assistance Information (“S-NSSAI”) 2 and the information required for access to the cell of target RAN node 606.

[0108] UE 602 switches 622 to the target RAN node 606's cell.

[0109] In the seventh communication 624 sent from UE 602 to target RAN node 606, UE 602 completes the HO procedure by sending an RRC reconfiguration complete message to target RAN node 606.

[0110] In the eighth communication 626 from UE 602 to target RAN node 606 and the ninth communication 628 from target RAN node 606 to AMF 608, UE 602 sends a registration request message (e.g., NAS registration request message) (including the requested S-NSSAI 2) to AMF 608 via target RAN node 606.

[0111] In the tenth communication 630 sent from AMF 608 to UE 602, AMF 608 determines that S-NSSAI 2 is supported by RAN area 2 and sends a registration acceptance message for the requested S-NSSAI 2 to UE 602.

[0112] In the fourth embodiment, the following configurations may exist: 1) Band-specific slice configuration: Band 1: S-NSSAI 1, S-NSSAI 3, S-NSSAI 4; Band 2: S-NSSAI 2; Band 3: S-NSSAI 3, S-NSSAI 4, S-NSSAI 6; Band 4: S-NSSAI 1, S-NSSAI 2, S-NSSAI 3, S-NSSAI 4, S-NSSAI 5; 2) The UE's configuration NSSAI includes 4 slices (e.g., S-NSSAI 1, S-NSSAI 2, S-NSSAI 3, and S-NSSAI 4); 3) After PLMN and initial cell selection, the UE is camped in a suitable cell in Band 1 served by the source RAN node; and 4) The UE attempts initial registration with the network used for S-NSSAI 1, S-NSSAI 2, S-NSSAI 3, and S-NSSAI 4.

[0113] Figure 7 This is a communication diagram illustrating yet another embodiment of communication 700 for cell selection. The illustrated communication 700 includes communication between UE 702, source RAN node 704, target RAN node 706, and AMF 708. As will be understood, each of the illustrated communications 700 may include one or more messages.

[0114] In the first communication 710 sent between UE 702 and source RAN node 704, an RRC connection is established between UE 702 and source RAN node 704.

[0115] In the second communication 712, sent from UE 702 to source RAN node 704, and in the third communication 714, sent from source RAN node 704 to AMF 708, UE 702 sends a registration request message (e.g., a NAS registration request message) to AMF 708. The registration request message includes requests for S-NSSAI 1, S-NSSAI 2, S-NSSAI 3, and S-NSSAI 4. Additionally, UE 702 sets the "band indication" parameter to the request from AMF 708 to receive additional information about the band supporting the requested S-NSSAI.

[0116] In the fourth communication 716 from AMF 708 to source RAN node 704, AMF 708 determines that source RAN node 704 supports S-NSSAI 1, S-NSSAI 3, and S-NSSAI 4, but not S-NSSAI 2. Therefore, AMF 708 sends information about the allowed S-NSSAI 1, S-NSSAI 3, and S-NSSAI 4, and the rejected S-NSSAI 2, and for S-NSSAI 2, AMF 708 sends band information. Information about allowed and / or rejected S-NSSAIs is sent to source node 704 via N2 messages (e.g., N2 downlink NAS transmission) (e.g., allowed S-NSSAIs: S-NSSAI 1, S-NSSAI 3, S-NSSAI 4; rejected S-NSSAIs: S-NSSAI 2 supported on band 2 and band 4).

[0117] In the fifth communication 718, which is sent from AMF 708 to UE 702, AMF 708 sends a registration acceptance message to UE 702, which contains the same information as the S-NSSAI for allowing and / or denying in the fourth communication 716.

[0118] In the sixth communication 720 from UE 702 to source RAN node 704, UE 702 processes the information received from AMF 708 and decides to send a UE 702 auxiliary information message to source RAN node 704. The auxiliary information message may include "slice preference auxiliary" information set to frequency band 4. Through this, UE 702 indicates to source RAN node 704 its preference to be redirected or switched to a slice configuration on frequency band 4, where all configured S-NSSAI is supported. Source RAN node 704 can then decide whether to take action on the UE 702 preference indication. For example, source RAN node 704 may set a measurement configuration on the relevant frequency band 4.

[0119] In the fifth embodiment, the following configuration may exist: RAN area coverage as described herein may exist; the UE's configured NSSAI includes both S-NSSAI 1 and S-NSSAI 2; after PLMN and initial cell selection, the UE camps on a suitable cell in RAN area 1 served by the source RAN node; and the UE attempts to initially register with the network and sends S-NSSAI 1 and S-NSSAI 2 in the IE "Requested NSSAI" of the registration request message.

[0120] Figure 8 This is a communication diagram illustrating yet another embodiment of communication 800 for cell selection. The illustrated communication 800 includes communication between UE 802, source RAN node 804, target RAN node 806, and AMF 808. As will be understood, each of the illustrated communications 800 may include one or more messages.

[0121] In the first communication 810 sent between UE 802 and source RAN node 804, an RRC connection is established between UE 802 and source RAN node 804.

[0122] In the second communication 812, sent from UE 802 to source RAN node 804, and in the third communication 814, sent from source RAN node 804 to AMF 808, UE 802 sends a registration request message (e.g., a NAS registration request message) to AMF 808. The registration request message includes the requested S-NSSAI 1 and S-NSSAI 2. Additionally, UE 802 sets the parameter "Band Indication" to request additional information from AMF 808 regarding the band supporting the requested S-NSSAI.

[0123] In the fourth communication 816 sent from AMF 808 to UE 802, after successful authentication of UE 802, AMF 808 retrieves UE 802 subscription information from UDM and / or UDR (or from the old AMF), and this subscription information contains S-NSSAI 1 and S-NSSAI 2 as subscribed S-NSSAIs. AMF 808 determines that the source RAN node 804 supports S-NSSAI 1 but not S-NSSAI 2. As a result, AMF 808 sends a registration acceptance message to UE 802, which contains information about the allowed S-NSSAI 1, the rejected S-NSSAI 2, and the frequency band information of the rejected S-NSSAI 2.

[0124] In the fifth communication 818 sent from the source RAN node 804 to the UE 802, the source RAN node 804 sends an RRC release message to the UE 802 without any redirection information.

[0125] UE 802NAS initiates 820URLLC service for S-NSSAI 2.

[0126] Based on the frequency band information for S-NSSAI 2 received in the fourth communication 816, UE 802 performs cell reselection 822 for the appropriate cell served by the target RAN node 806.

[0127] In the sixth communication 824 sent between UE 802 and target RAN node 806, an RRC connection is established between UE 802 and target RAN node 806.

[0128] In the seventh communication 826, sent from UE 802 to target RAN node 806, and the eighth communication 828, sent from target RAN node 806 to AMF 808, UE 802 sends a service request message (e.g., a NAS service request message) to AMF 808. The service request message may include a requested URLLC service and a NAS registration request message encapsulated with S-NSSAI 2 containing the request via target RAN node 806.

[0129] Figure 9 This is a flowchart illustrating one embodiment of a method 900 for obtaining target network slice information for a target network slice. In some embodiments, method 900 is performed by a device such as network unit 104. In some embodiments, method 900 may be performed by a processor that executes program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0130] In various embodiments, method 900 includes receiving 902 a first message from a communication device, the first message including information indicating a request to register a plurality of network slices. In some embodiments, method 900 includes determining 904 target network slice information corresponding to a plurality of target network slices, wherein the target network slice information includes information indicating that the network slice is not supported in an area of ​​the plurality of network slices in which the communication device is located, and frequency-specific configurations associated with the plurality of target network slices. In some embodiments, method 900 includes sending 906 a second message to a radio network entity, the second message including the target network slice information and the associated frequency-specific configuration.

[0131] In some embodiments, a first message is received from a communication device by means of a first radio network entity. In some embodiments, the area where the communication device is located includes a cell of a tracking area or multiple cells of a tracking area. In various embodiments, the frequency-specific configuration associated with multiple target network slices includes a configuration of frequency carriers, frequency bands, frequency priorities, or some combination thereof.

[0132] In one embodiment, receiving the first message includes receiving the first message at the access and mobility management function. In some embodiments, the first message includes a request for frequency-specific configurations associated with a plurality of network slices to be registered. In some embodiments, a third message is sent to the communication device, and the third message includes target network slice information and associated frequency-specific configurations.

[0133] Figure 10 This is a flowchart illustrating another embodiment of a method 1000 for targeting network slice information for a target network slice. In some embodiments, method 1000 is performed by a device such as network unit 104. In some embodiments, method 1000 may be performed by a processor that executes program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0134] In various embodiments, method 1000 includes receiving 1002 a first message from a core network entity, wherein the first message includes target network slice information corresponding to a target network slice of a communication device, a frequency-specific configuration associated with the target network slice, or a combination thereof. In some embodiments, method 1000 includes determining 1004 a target cell among a plurality of cells that supports the target network slice. In various embodiments, method 1000 includes sending 1006 a second message to the communication device, wherein the second message includes target cell information and a request to connect to the target cell.

[0135] In some embodiments, the second message includes a Radio Resource Control (RRC) connection release message or a RRC connection reconfiguration message. In some embodiments, the core network entity includes access and mobility management functions. In various embodiments, the target network slice information includes information indicating a network slice among a plurality of network slices that is not supported in the area where the communication device is located.

[0136] Figure 11 This is a flowchart illustrating another embodiment of a method 1100 for targeting network slice information for a target network slice. In some embodiments, method 1100 is performed by a device such as network unit 104. In some embodiments, method 1100 may be performed by a processor that executes program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0137] In various embodiments, method 1100 includes receiving 1102 a first message from a communication device, wherein the first message includes network slice preference assistance information indicating target network slice information corresponding to a plurality of target network slices of the communication device, and frequency-specific configurations associated with the plurality of target network slices. In some embodiments, method 1100 includes determining 1104 a mobility configuration based on the network slice preference assistance information. In various embodiments, method 1100 includes sending 1106 a second message to the communication device, wherein the second message includes the mobility configuration.

[0138] In some embodiments, mobility configuration includes configuration information for measurement or switching.

[0139] Figure 12 This is a flowchart illustrating another embodiment of a method 1200 for targeting network slice information for a target network slice. In some embodiments, method 1200 is performed by a device such as remote unit 102. In some embodiments, method 1200 may be performed by a processor that executes program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0140] In various embodiments, method 1200 includes sending a first message 1202 to a core network entity, wherein the first message includes information indicating a request to register a plurality of network slices. In some embodiments, method 1200 includes receiving a second message 1204 including target slice information in response to sending the first message. In some embodiments, method 1200 includes determining a frequency-specific network slice among the plurality of network slices based on the second message 1206. In various embodiments, method 1200 includes performing cell reselection 1208 with cells of the frequency-specific network slice. In some embodiments, method 1200 includes sending a third message 1210 to a core network entity, wherein the third message includes information indicating a network slice among the plurality of network slices to be registered, a service to be established, or a combination thereof.

[0141] In some embodiments, the first message is sent to the core network entity via a first radio network entity. In some embodiments, the first message includes a request for frequency-specific configurations associated with a plurality of network slices to be registered.

[0142] In various embodiments, the second message includes a frequency-specific configuration associated with the target network slice information. In one embodiment, the core network entity includes access and mobility management functions.

[0143] Figure 13This is a flowchart illustrating another embodiment of a method 1300 for targeting network slice information for a target network slice. In some embodiments, method 1300 is performed by a device such as remote unit 102. In some embodiments, method 1300 may be performed by a processor that executes program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0144] In various embodiments, method 1300 includes sending a first message 1302 to a radio network entity, wherein the first message includes network slice preference assistance information indicating target network slice information corresponding to a plurality of target network slices of a communication device, and frequency-specific configurations associated with the plurality of target network slices. In some embodiments, method 1300 includes receiving a second message 1304 including mobility configurations from the radio network entity in response to sending the first message.

[0145] In one embodiment, a method includes: receiving a first message from a communication device, the first message including information indicating a request to register a plurality of network slices; determining target network slice information corresponding to the plurality of target network slices, wherein the target network slice information includes information indicating network slices among the plurality of network slices that are not supported in an area in which the communication device is located, and frequency-specific configurations associated with the plurality of target network slices; and sending a second message including the target network slice information and the associated frequency-specific configurations to a radio network entity.

[0146] In some embodiments, a first message is received from a communication device by means of a first radio network entity.

[0147] In some embodiments, the area in which the communication device is located includes a cell of the tracking area or multiple cells of the tracking area.

[0148] In various embodiments, the frequency-specific configuration associated with multiple target network slices includes configurations of frequency carriers, frequency bands, frequency priorities, or some combination thereof.

[0149] In one embodiment, receiving the first message includes receiving the first message at the access and mobility management function.

[0150] In some embodiments, the first message includes a request for frequency-specific configurations associated with the plurality of network slices to be registered.

[0151] In some embodiments, a third message is sent to the communication device, and the third message includes target network slice information and associated frequency-specific configuration.

[0152] In one embodiment, an apparatus includes: a receiver configured to receive a first message from a communication device, the first message including information indicating a request to register a plurality of network slices; a processor configured to determine target network slice information corresponding to a plurality of target network slices, wherein the target network slice information includes information indicating that a network slice in the plurality of network slices is not supported in an area in which the communication device is located, and frequency-specific configurations associated with the plurality of target network slices; and a transmitter configured to transmit a second message including the target network slice information and the associated frequency-specific configurations to a radio network entity.

[0153] In some embodiments, a first message is received from a communication device by means of a first radio network entity.

[0154] In some embodiments, the area in which the communication device is located includes a cell of the tracking area or multiple cells of the tracking area.

[0155] In various embodiments, the frequency-specific configuration associated with multiple target network slices includes configurations of frequency carriers, frequency bands, frequency priorities, or some combination thereof.

[0156] In one embodiment, the receiver is configured to receive the first message, including the receiver being configured to receive the first message at an access and mobility management function.

[0157] In some embodiments, the first message includes a request for frequency-specific configurations associated with the plurality of network slices to be registered.

[0158] In some embodiments, a third message is sent to the communication device, and the third message includes target network slice information and associated frequency-specific configuration.

[0159] In one embodiment, a method includes: receiving a first message from a core network entity, wherein the first message includes target network slice information corresponding to a target network slice of a communication device, a frequency-specific configuration associated with the target network slice, or a combination thereof; determining a target cell among a plurality of cells, wherein the target network slice is supported; and sending a second message to the communication device, wherein the second message includes target cell information and a request to connect to the target cell.

[0160] In some embodiments, the second message includes a radio resource control connection release message or a radio resource control connection reconfiguration message.

[0161] In some embodiments, the core network entity includes access and mobility management functions.

[0162] In various embodiments, the target network slice information includes information indicating network slices among a plurality of network slices that are not supported in the area where the communication device is located.

[0163] In one embodiment, an apparatus includes: a receiver configured to receive a first message from a core network entity, wherein the first message includes target network slice information corresponding to a target network slice of a communication device, a frequency-specific configuration associated with the target network slice, or a combination thereof; a processor configured to determine a target cell among a plurality of cells, wherein the target network slice is supported; and a transmitter configured to send a second message to the communication device, wherein the second message includes target cell information and a request to connect to the target cell.

[0164] In some embodiments, the second message includes a radio resource control connection release message or a radio resource control connection reconfiguration message.

[0165] In some embodiments, the core network entity includes access and mobility management functions.

[0166] In various embodiments, the target network slice information includes information indicating network slices among a plurality of network slices that are not supported in the area where the communication device is located.

[0167] In one embodiment, a method includes: receiving a first message from a communication device, wherein the first message includes network slice preference auxiliary information indicating target network slice information corresponding to a plurality of target network slices of the communication device, and frequency-specific configurations associated with the plurality of target network slices; determining a mobility configuration based on the network slice preference auxiliary information; and sending a second message to the communication device, wherein the second message includes the mobility configuration.

[0168] In some embodiments, mobility configuration includes configuration information for measurement or switching.

[0169] In one embodiment, an apparatus includes: a receiver configured to receive a first message from a communication device, wherein the first message includes network slice preference assistance information indicating target network slice information corresponding to a plurality of target network slices of the communication device, and frequency-specific configurations associated with the plurality of target network slices; a processor configured to determine a mobility configuration based on the network slice preference assistance information; and a transmitter configured to send a second message to the communication device, wherein the second message includes the mobility configuration.

[0170] In some embodiments, mobility configuration includes configuration information for measurement or switching.

[0171] In one embodiment, a method includes: sending a first message to a core network entity, wherein the first message includes information indicating a request to register a plurality of network slices; in response to sending the first message, receiving a second message including target slice information; determining a frequency-specific network slice among the plurality of network slices based on the second message; performing cell reselection with cells of the frequency-specific network slice; and sending a third message to the core network entity, wherein the third message includes information indicating a network slice among the plurality of network slices to be registered, a service to be established, or a combination thereof.

[0172] In some embodiments, the first message is sent to the core network entity by means of a first radio network entity.

[0173] In some embodiments, the first message includes a request for frequency-specific configurations associated with the plurality of network slices to be registered.

[0174] In various embodiments, the second message includes a frequency-specific configuration associated with the target network slice information.

[0175] In one embodiment, the core network entity includes access and mobility management functions.

[0176] In one embodiment, an apparatus includes: a transmitter configured to send a first message to a core network entity, wherein the first message includes information indicating a request to register a plurality of network slices; a receiver configured to receive a second message including target slice information in response to sending the first message; and a processor configured to: determine a frequency-specific network slice among the plurality of network slices based on the second message; and perform cell reselection with cells of the frequency-specific network slice; wherein the transmitter is configured to send a third message to the core network entity, and the third message includes information indicating the network slices of the plurality of network slices to be registered, services to be established, or combinations thereof.

[0177] In some embodiments, the first message is sent to the core network entity by means of a first radio network entity.

[0178] In some embodiments, the first message includes a request for frequency-specific configurations associated with the plurality of network slices to be registered.

[0179] In various embodiments, the second message includes a frequency-specific configuration associated with the target network slice information.

[0180] In one embodiment, the core network entity includes access and mobility management functions.

[0181] In one embodiment, a method includes: sending a first message to a radio network entity, wherein the first message includes network slice preference auxiliary information indicating target network slice information corresponding to a plurality of target network slices of a communication device, and frequency-specific configurations associated with the plurality of target network slices; and receiving a second message including mobility configurations from the radio network entity in response to sending the first message.

[0182] In one embodiment, an apparatus includes: a transmitter configured to transmit a first message to a radio network entity, wherein the first message includes network slice preference assistance information indicating target network slice information corresponding to a plurality of target network slices of a communication device, and frequency-specific configurations associated with the plurality of target network slices; and a receiver configured to receive a second message including mobility configurations from the radio network entity in response to transmitting the first message.

[0183] The embodiments may be practiced in other specific forms. The described embodiments are to be regarded in all respects as illustrative rather than restrictive. Therefore, the scope of the invention is indicated by the appended claims rather than the foregoing description. All variations within the meaning and equivalents of the claims are included within their scope.

Claims

1. A method at a first network entity, the method comprising: Receive a first message from the communication device, the first message including information indicating a request to register multiple network slices; Determine target network slice information corresponding to multiple target network slices, wherein the target network slice information includes information indicating network slices among the multiple network slices that are not supported in the area where the communication device is located; as well as A second message including the target network slice information is sent to a second network entity, wherein the second message further indicates a frequency-specific configuration associated with the target network slice information, and wherein the frequency-specific configuration enables the use of the network slice that is not supported in the area in which the communication device is located.

2. The method according to claim 1, wherein, The area in which the communication device is located includes a cell of the tracking area or multiple cells of the tracking area.

3. The method according to claim 1, wherein, The frequency-specific configuration associated with the plurality of target network slices includes configurations of frequency carriers, frequency bands, frequency priorities, or combinations thereof.

4. The method according to claim 1, wherein, Receiving the first message includes receiving the first message at the access and mobility management function.

5. The method according to claim 1, wherein, The first message includes a request for a frequency-specific configuration associated with the plurality of network slices to be registered.

6. The method according to claim 1, wherein, A third message is sent to the communication device, and the third message includes the target network slice information and the associated frequency-specific configuration.

7. The method according to claim 1, wherein, Sending the second message includes sending the second message to a radio network entity.

8. An apparatus for wireless communication, the apparatus comprising: A receiver configured to receive a first message from a communication device, the first message including information indicating a request to register multiple network slices; A processor configured to determine target network slice information corresponding to a plurality of target network slices, wherein the target network slice information includes information indicating network slices among the plurality of network slices that are not supported in the area where the communication device is located; as well as A transmitter configured to send a second message to a second network entity including target network slice information, wherein the second message further indicates a frequency-specific configuration associated with the target network slice information, and wherein the frequency-specific configuration enables the use of network slices that are not supported in the area in which the communication device is located.

9. The apparatus according to claim 8, wherein, The receiver is configured to receive the first message, including: the receiver is configured to receive the first message at the access and mobility management function.

10. The apparatus according to claim 8, wherein, The area in which the communication device is located includes a cell of the tracking area or multiple cells of the tracking area.

11. The apparatus according to claim 8, wherein, The frequency-specific configuration associated with the plurality of target network slices includes configurations of frequency carriers, frequency bands, frequency priorities, or combinations thereof.

12. The apparatus according to claim 8, wherein, The transmitter is configured to send the second message, including the transmitter being further configured to send the second message to a radio network entity.

13. An apparatus for wireless communication, the apparatus comprising: A receiver configured to receive a first message from a first network entity, wherein the first message includes target network slice information corresponding to a target network slice of a communication device, a frequency-specific configuration associated with the target network slice, or a combination thereof; A processor configured to determine a target cell from a plurality of cells that supports the target network slice; and A transmitter configured to send a second message to the communication device, wherein the second message includes target cell information and a request to connect to the target cell, wherein the target network slice information includes information indicating a network slice among a plurality of network slices that is not supported in the area in which the communication device is located, and wherein the frequency-specific configuration enables the use of the network slice that is not supported in the area in which the communication device is located.

14. The apparatus according to claim 13, wherein, The first network entity includes the Access and Mobility Management Function (AMF).

15. The apparatus according to claim 13, wherein, The receiver is configured to receive the first message, including that the receiver is further configured to receive the first message at a radio access entity.

16. The apparatus according to claim 13, wherein, The second message includes a radio resource control connection release message or a radio resource control connection reconfiguration message.

17. The apparatus according to claim 13, wherein, The target network slice information includes information indicating network slices among multiple network slices that are not supported in the area where the communication device is located.

18. The apparatus according to claim 13, wherein, The frequency-specific configuration associated with the plurality of target network slices includes configurations of frequency carriers, frequency bands, frequency priorities, or combinations thereof.

Images