Network slicing-aware cell selection

By receiving and using the network slice support information provided by the cell in the user equipment (UE), identifying the coverage area and meeting the predetermined criteria, the problem that the UE cannot determine slice support when selecting a cell is solved, and the service quality is improved and Network performance.

CN115088303BActive Publication Date: 2024-11-08APPLE INC
View PDF 10 Cites 0 Cited by

Patent Information

Application Number
CN202080096294.6
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-02-12
Publication Date
2024-11-08
Estimated Expiration
2040-02-12

AI Technical Summary

Technical Problem

When user equipment (UE) selects a pre-occupying network cell, it is impossible to determine whether the cell supports specific network slices, resulting in pre-occupying unsupported network slices, affecting service quality.

Method used

The network slice-aware cell selection is realized in the UE. By receiving network slice support information from the cell, the coverage area of ​​the cell where the UE is located is identified, and whether the measurement data meets the predetermined standard, and if so, a pre-occupation is made.

Benefits of technology

Ensure that the UE takes into account network slicing support when selecting a cell, avoids pre-occupying unsupported network slicing, and improves service quality and network performance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115088303B_ABST
    Figure CN115088303B_ABST
Patent Text Reader

Abstract

Example embodiments relate to implementing network slice-aware cell selection at a user equipment (UE). This may include receiving information indicating that a cell of a network supports network slicing. The UE may identify that the UE is within a coverage area of ​​the cell and determine whether measurement data corresponding to the cell meets a predetermined criterion. When the measurement data meets the criterion, the UE may camp on the cell.
Need to check novelty before this filing date? Find Prior Art

Description

Background Art

[0001] A user equipment (UE) may be connected to a network including a network slice. In general, a network slice refers to a network architecture in which multiple end-to-end logical networks run on a shared physical network infrastructure. Each network slice may be configured for a specific purpose. For example, a network may include a network slice configured to provide carrier services (e.g., voice, multimedia messaging service (MMS), Internet, etc.), a network slice configured to provide machine type communication (MTC) services, a network slice configured to provide ultra-reliable low latency communication (URLLC) services, etc. Therefore, each network slice may share network resources but facilitate different functions.

[0002] In order to establish a connection with the network and perform the full range of functions generally available to the UE via the network connection, the UE may camp on a cell of the network. In conventional cases, when the UE selects a cell to camp on, the UE does not know whether the cell supports a particular network slice. Therefore, the UE may camp on a cell that does not support the network slice that the UE is configured to utilize. Summary of the invention

[0003] According to some exemplary embodiments, the method is performed at a user equipment (UE). The method includes receiving information indicating that a cell of the network supports network slicing, identifying that the UE is located within a coverage area of ​​the cell, determining whether measurement data corresponding to the cell meets a predetermined criterion, and when the measurement data meets the criterion, the UE camps on the cell.

[0004] Another exemplary embodiment includes a user equipment (UE) having a transceiver and a processor. The transceiver is configured to communicate with a network. The processor is configured to perform operations including receiving information indicating that a cell of the network supports network slicing, identifying that the UE is located within a coverage area of ​​the cell, determining whether measurement data corresponding to the cell meets a predetermined criterion, and when the measurement data meets the criterion, the UE camps on the cell.

[0005] Yet another exemplary embodiment includes an integrated circuit. The integrated circuit includes circuitry configured to receive information indicating that a cell of a network supports network slicing, circuitry configured to identify that a user equipment (UE) is located within a coverage area of ​​the cell, circuitry configured to determine whether measurement data corresponding to the cell meets a predetermined criterion, and circuitry configured to cause the UE to camp on the cell when the measurement data meets the criterion. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] Figure 1 Exemplary network arrangements are shown according to various exemplary embodiments.

[0007] Figure 2An exemplary UE according to various exemplary embodiments is shown.

[0008] Figure 3 An exemplary scenario is shown where a UE is located near multiple cells deployed with overlapping coverage areas.

[0009] Figure 4 Exemplary methods for network-aware cell selection according to various exemplary embodiments are shown. DETAILED DESCRIPTION

[0010] The exemplary embodiments may be further understood with reference to the following description and associated drawings, in which similar elements have the same reference numerals. The present invention discloses exemplary embodiments relating to implementing network slice-aware cell selection at a user equipment (UE). As will be described below, various exemplary mechanisms may be configured to provide information to the UE about which cells and / or frequency bands support access to a particular network slice. The UE may then consider this network slice information when selecting a cell to camp on.

[0011] The exemplary embodiments are described with respect to UE. However, reference to UE is provided for illustration purposes only. The exemplary embodiments may be used with any electronic component configured with hardware, software and / or firmware for exchanging information (e.g., control information) and / or data with a network. Therefore, the UE described herein is used to represent any suitable electronic device.

[0012] Exemplary embodiments are also described with reference to a fifth generation (5G) network including network slicing. In general, network slicing refers to a network architecture in which multiple end-to-end logical networks run on a shared physical network infrastructure. Each network slice can be configured to provide a specific set of capabilities and / or features. Thus, the physical infrastructure of a 5G network can be sliced ​​into multiple virtual networks, each configured for a different purpose.

[0013] Those skilled in the art will appreciate that 5G may support use cases such as enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Each of these types of use cases may involve a variety of different types of applications and / or services. A network slice may be characterized by the type of use case, the type of application and / or service, or the entity providing the application and / or service via the network slice. However, any examples in this specification that characterize network slices in a particular manner are provided for illustrative purposes only. Throughout the specification, references to network slices may represent any type of end-to-end logical network that is configured for a particular purpose and implemented on a 5G physical infrastructure.

[0014] The UE may be configured to perform any of a variety of different tasks. Thus, the UE may be configured to utilize one or more network slices. For example, the UE may use a first network slice for carrier services (e.g., voice, multimedia messaging service (MMS), Internet, etc.) and another network slice for services provided by a third party. To provide an example, the third party may be a manufacturer of the UE that provides services such as, but not limited to, messaging, streaming multimedia, video calls, etc. In another example, the third party may be an entity that manages a digital platform (e.g., social media, e-commerce, streaming media, etc.). In another example, the third party may be an entity that provides services for Internet of Things (IoT) devices.

[0015] As indicated above, network slices can be used for a variety of different purposes. However, the configuration purposes of network slices are beyond the scope of the exemplary embodiments. Therefore, the exemplary embodiments are not limited to any particular type of network slice. Instead, the exemplary embodiments relate to a UE accessing a particular network slice through a radio access network (RAN).

[0016] Slice isolation is one aspect of network slicing. This generally means that the performance of one network slice will not affect the performance of another network slice. To achieve slice isolation, the network can configure a specific network slice to be accessible only via one or more specific frequency bands. For example, the radio spectrum allocated to 5G includes frequency range 1 (FR1) (e.g., 410 megahertz (MHz) to 7125MHz) and frequency range 2 (FR2) (e.g., 24250MHz to 52600MHz). In an exemplary deployment scenario, eMMB slices can be accessed in 2.6 gigahertz (GHz) and 4.9GHz, while URLLC slices can be accessed in 4.9GHZ. In another exemplary deployment scenario, lower frequency bands can be used for mMTC network slices, while higher frequency bands can be used for eMBB network slices. Therefore, in order to access a specific network slice, the UE can pre-occupy a cell of the 5G network. If the cell operates on a frequency band configured to provide access to a specific network slice, the UE can access the network slice via the cell. If the cell does not operate on the frequency band, the UE may not be able to access the network slice via the cell.

[0017] During operation, the UE may be located near multiple cells deployed with overlapping coverage areas. For example, a first 5G RAN may include a first cell that supports communications over frequency band (x), and a second 5G RAN may include a second cell that supports communications over frequency band (y). In this example, frequency band (x) may provide access to network slice (a), and frequency band (y) may provide access to network slice (b). When the UE is within the coverage of both the first cell and the second cell, the UE may perform registration with the first 5G RAN or the second 5G RAN. However, under normal circumstances, the UE does not know whether the network slice is supported by the cell until the UE requests access to the slice and the request is accepted or rejected by the network. Therefore, a scenario may occur in which the UE is configured to utilize network slice (a) but decides to pre-occupy on a second cell of the second 5G RAN. Since the second cell operates on frequency band (y), the UE will not be able to utilize network slice (a) via the second cell.

[0018] Example embodiments relate to implementing network slice-aware cell selection at a UE. As will be explained in more detail below, network slice-aware cell selection may include the UE receiving information from any of a variety of different sources about which one or more network slices are supported by a particular cell and / or frequency band. In some embodiments, the UE may consider this network slice information during cell selection or any other procedure in which the UE directly or indirectly selects a cell to camp on. In other embodiments, this network slice information may trigger the UE to search for different cells to camp on.

[0019] Various exemplary sources of network slicing information are described in detail below. Some exemplary embodiments are described with respect to collecting network slicing information from information broadcast by cells. Other exemplary embodiments are described with respect to collecting network slicing information from information received during a registration procedure. Additional exemplary embodiments involve collecting network slicing information from information received from radio resource control (RRC) signaling. These exemplary network slicing information sources and other exemplary network slicing information sources are described in more detail below. The exemplary embodiments described herein may be used with currently implemented techniques for cell selection, future implementations of techniques for cell selection, or independently of other cell selection techniques.

[0020] Figure 1An exemplary network arrangement 100 according to various exemplary embodiments is shown. The exemplary network arrangement 100 includes a UE 110. Those skilled in the art will appreciate that the UE 110 may be any type of electronic component configured to communicate via a network, such as a mobile phone, a tablet computer, a desktop computer, a smart phone, a phablet, an embedded device, a wearable device, an Internet of Things (IoT) device, an eMTC device, etc. It should also be appreciated that an actual network arrangement may include any number of UEs used by any number of users. Therefore, for purposes of illustration, only an example with a single UE 110 is provided.

[0021] UE 110 may be configured to communicate with one or more networks. In the example of network configuration 100, the networks with which UE 110 may wirelessly communicate are 5G New Air (NR) radio access networks (5G NR-RAN) 120, 122, and LTE-RAN 124. However, it should be understood that UE 110 may also communicate with other types of networks (e.g., traditional cellular networks, WLAN, etc.), and UE 110 may also communicate with the network via a wired connection. With respect to the exemplary embodiment, UE 110 may establish a connection with 5G NR-RAN 120, 5G NR-RAN 122, or LTE-RAN 124.

[0022] The 5G NR-RAN 120, 122 and LTE-RAN 124 may be part of cellular networks that may be deployed by cellular providers such as Verizon, AT&T, Sprint, T-Mobile, etc. These networks 120, 122 may include, for example, cells or base stations (NodeB, eNodeB, HeNB, eNBS, gNB, gNodeB, macrocell base stations, microcell base stations, small cell base stations, femtocell base stations, etc.) configured to send and receive traffic from UEs equipped with appropriate cellular chipsets.

[0023] 5G NR-RAN 120, 122 may include an architecture capable of providing both 5G NR RAT services and LTE RAT services. For example, a next generation radio access network (NG-RAN) (not shown) may include a next generation Node B (gNB) providing 5G NR services and a next generation evolved Node B (ng-eNB) providing LTE services. The NG-RAN may be connected to at least one of an evolved packet core (EPC) or a 5G core (5GC). Therefore, reference to 5G NR-RAN 120, 122 and LTE-RAN 124 is provided only for illustrative purposes, and the exemplary embodiments may be applied to any appropriate type of RAN.

[0024] Returning to the exemplary network arrangement 100, the UE 110 may be connected to the 5G NR-RAN 120 via a next generation Node B (gNB) 120A, to the 5G NR-RAN 122 via a gNB 122A, and to the LTE-RAN 124 via an eNB 124A. Those skilled in the art will appreciate that any relevant procedures may be performed to connect the UE 110 to the 5G NR-RAN 120, 5G NR-RAN 122, or LTE-RAN 124. For example, as described above, the 5G NR-RAN 120 may be associated with a particular cellular provider, where the UE 110 and / or its user has agreement and credential information (e.g., stored on a SIM card). Upon detecting the presence of the 5G NR-RAN 120, the UE 110 may transmit the corresponding credential information in order to associate with the 5G NR-RAN 120. More specifically, UE 110 may be associated with a particular cell, e.g., gNB 120A of 5G NR-RAN 120. Similarly, to access 5G NR-RAN 122, UE 110 may be associated with gNB 122A, and to access LTE-RAN 124, UE 110 may be associated with eNB 124A.

[0025] In addition to the 5G NR-RANs 120, 122 and the LTE-RAN 124, the network arrangement 100 includes a cellular core network 130, the Internet 140, an IP multimedia subsystem (IMS) 150, and a network service backbone 160. The cellular core network 130 can be viewed as an interconnected collection of components that manage the operation / traffic of the cellular network. The cellular core network 130 also manages the traffic flowing between the cellular network and the Internet 140. The IMS 150 can generally be described as an architecture for delivering multimedia services to the UE 110 using the IP protocol. The IMS 150 can communicate with the cellular core network 130 and the Internet 140 to provide multimedia services to the UE 110. The network service backbone 160 communicates directly or indirectly with the Internet 140 and the cellular core network 130. The network service backbone 160 can generally be described as a set of components (e.g., servers, network storage arrangements, etc.) that implement a set of services that can be used to extend the functionality of the UE 110 to communicate with various networks.

[0026] Figure 2 An exemplary UE 110 is shown according to various exemplary embodiments. Figure 1UE 110 is described with reference to a network arrangement 100 of FIG. UE 110 may represent any electronic device and may include a processor 205, a memory arrangement 210, a display device 215, an input / output (I / O) device 220, a transceiver 225, and other components 230. Other components 230 may include, for example, an audio input device, an audio output device, a battery, a data acquisition device, a port for electrically connecting UE 110 to other electronic devices, a sensor for detecting a condition of UE 110, and the like.

[0027] The processor 205 may be configured to execute a plurality of engines of the UE 110. For example, the engines may include a network slice awareness engine 235. The network slice awareness engine 235 may be configured to collect information indicating which network slices are supported by a particular cell and / or frequency band from any of a variety of different sources. The UE 110 may then consider this information during cell selection or any other procedure in which the UE 110 directly or indirectly selects a cell to camp on.

[0028] The above engines are each an application (e.g., a program) executed by the processor 205 for exemplary purposes only. The functions associated with the engine may also be represented as an independently integrated component of the UE 110, or may be a modular component coupled to the UE 110, such as an integrated circuit with or without firmware. For example, an integrated circuit may include an input circuit for receiving a signal and a processing circuit for processing the signal and other information. The engine may also be embodied as an application or multiple separate applications. In addition, in some UEs, the functionality described for the processor 205 is shared between two or more processors such as a baseband processor and an application processor. The exemplary embodiments may be implemented in any of these or other configurations of the UE.

[0029] The memory 210 may be a hardware component configured to store data related to operations performed by the UE 110. The display device 215 may be a hardware component configured to display data to a user, and the I / O device 220 may be a hardware component that enables user input. The display device 215 and the I / O device 220 may be separate components or may be integrated together (such as a touch screen). The transceiver 225 may be a hardware component configured to establish a connection with the 5G NR RAN 120, 122, LTE-RAN 124, and other types of wireless networks. Thus, the transceiver 225 may operate on a variety of different frequencies or channels (e.g., a set of continuous frequencies).

[0030] Figure 3 An exemplary scenario 300 is shown in which a UE 110 is located near multiple cells deployed with overlapping coverage areas. The exemplary scenario 300 includes a UE 110, a gNB 120A, and a gNB 122A.

[0031] Example scenario 300 shows gNB 120A with coverage area 305 and gNB 122A with coverage area 310. UE 110 is shown as being located within both coverage areas 305, 310. As described above, gNB 120A corresponds to 5G NR-RAN 120 and gNB 122A corresponds to 5G NR-RAN 122.

[0032] Consider a set of exemplary cases where 5G NR-RAN 120 operates on band (y) via gNB 120A and 5G NR-RAN 122 operates on band (x) via gNB 122A. Band (y) is configured to provide access to a first type of network slice and band (x) is configured to provide access to a second type of network slice. Since UE 110 is located within two coverage areas 305, 310, UE 110 can camp on gNB 120A or gNB 122A. In a conventional case, UE 110 is unaware that band (y) provided by gNB 120A is configured to provide access to a first type of network slice and band (x) provided by gNB 122A is configured to provide access to a second type of network slice. Therefore, when selecting a cell to camp on, UE 110 will not consider the network slice information corresponding to each gNB 120A, 122A.

[0033] An exemplary embodiment involves collecting information about which network slices are supported by a particular cell and / or frequency band. The UE 110 may then consider this information during cell selection or any other instance in which the UE 110 directly or indirectly selects a cell to camp on. For example, with respect to exemplary scenario 300, the UE 110 may collect and store information from network components and / or previous interactions with these cells and / or frequency bands. The information may indicate that the frequency band (y) provided by the gNB 120A is configured to provide access to a first type of network slice, and the frequency band (x) provided by the gNB 122A is configured to provide access to a second type of network slice. Thus, unlike conventional methods, the UE 110 is aware of the network slice information corresponding to these cells and / or frequency bands. Thus, the UE 110 may consider this network slice information during cell selection or any other procedure in which the UE 110 directly or indirectly selects a cell to camp on.

[0034] Figure 4 An exemplary method 400 for network-aware cell selection according to various exemplary embodiments is shown. Figure 3 Example scenario 300, Figure 2 UE 110 and Figure 1The method 400 is described with reference to the network arrangement 100 .

[0035] In 405, UE 110 receives network slicing information from the network. The network slicing information may indicate whether a particular network slice is supported by a particular cell and / or frequency band. In one aspect, UE 110 may consider the slicing information to determine whether UE 110 will remain on the currently camped cell or search for a different cell to camp on. For example, UE 110 may receive network slicing information corresponding to a particular cell after UE 110 has camped on the cell. On the other hand, UE 110 may consider the network slicing information during cell selection, cell reselection, or any other procedure in which UE 110 directly or indirectly selects a cell to camp on. For example, at a first location and a first time, UE 110 may receive network slicing information. Then, UE 110 may move to a second location that does not include any of the cells associated with the first location. When UE 110 returns to the first location, UE 110 may consider the network slicing information when determining which cell to camp on. Network slicing information and various different sources of network slicing information will be described in more detail below.

[0036] An exemplary source of network slice information may include a system information block (SIB). Those skilled in the art will appreciate that various different types of SIBs are broadcast by cells. Throughout the specification, any reference to a particular SIB is provided for illustrative purposes only. The exemplary embodiments may be applied to include network slice information in any appropriate SIB.

[0037] In some embodiments, a 5G NR cell may broadcast an indication of a set of network slices supported by the cell. For example, consider a scenario in which UE 110 is camped on gNB 120A and within the coverage area of ​​gNB 122A. UE 110 may tune its transceiver 225 and listen to the SIBs broadcast by gNB 120A or gNB 122A.

[0038] The 5G cell may broadcast SIB 1 or SIB2 including a list of single network slice selection assistance information (s-NSSAI). Each s-NSSAI may correspond to a different network slice, and the s-NSSAI list may indicate whether the corresponding network slice is supported by the cell broadcasting the SIB. Throughout the specification, s-NSSAI refers to a single network slice, and NSSAI may generally refer to one or more network slices.

[0039] Each s-NSSAI may include a slice service type (SST) and a slice descriptor (SD). The SST may identify the type of use case, application, and / or service associated with the corresponding network slice. The SD may identify any one or more entities associated with the network slice. For example, the SD may indicate the owner or entity that manages the network slice (e.g., an operator) and / or the entity that provides applications / services via the network slice (e.g., a third party, an entity that provides applications or services, etc.). In some embodiments, the same entity may own the slice and provide services (e.g., operator services).

[0040] As described above, s-NSSAI can be encoded with both SST and SD. In one example, this encoding can take up to forty bits. In another exemplary embodiment, in order to reduce the number of bits sent over the air, s-NSSAI can be configured to include only SST. Based on the SST information, UE 110 can make an informed decision on whether to remain on the current camped cell or reselect to a neighboring cell.

[0041] In other exemplary embodiments, the 5G NR cell may provide an on-demand SIB that is configured to indicate a set of network slices supported by the cell and / or its neighboring cells. For example, consider a scenario in which UE 110 is camped on gNB 120A. UE 110 may send a request for a SIB to gNB 120A as part of an RRC system information request. UE 110 may be triggered to make the request due to entering a new tracking area, moving to a new public land mobile network (PLMN), or moving from FR1 to FR 2 (or vice versa). In response, gNB 120A may broadcast one or more SIBs that indicate a set of s-NSSAIs supported by gNB 120A and / or a set of s-NSSAIs supported by neighboring cells of gNB 120A.

[0042] In another embodiment, the 5G NR cell may broadcast an indication of a set of network slices supported by a neighboring cell. For example, consider a scenario in which UE 110 is camped on gNB 120A. gNB 120A may broadcast SIB 4 including an s-NSSAI list. The s-NSSAI list may indicate the network slices supported by the neighboring cells of gNB 120A. If there is more than one neighboring cell, the broadcast may include an indication of a set of network slices supported by each neighboring cell.

[0043] In other embodiments, the LTE cell may broadcast an indication of a set of network slices supported at the 5G adjacent frequency. For example, consider a scenario in which UE 110 is camped on eNB 124A. eNB 124A may broadcast SIB 24 including an s-NSSAI list. The s-NSSAI list may indicate which network slices are supported by one or more 5G adjacent frequencies. UE 110 may consider this information when performing reselection from a currently camped LTE cell to a 5G NR cell. As will be described below, UE 110 may consider the network slice information broadcast by the cell when determining whether to remain on the currently camped cell and / or select (directly or indirectly) a cell to camp on.

[0044] Another exemplary source of network slice information may include a non-access stratum (NAS) registration procedure. UE 110 may perform NAS registration for each registration area. During NAS registration, UE 110 may include s-NSSAI information indicating which network slices UE 110 may attempt to access. In response, the network may notify UE 110 in a registration accept message to allow or deny the s-NSSAI requested by UE 110 on the current camped cell.

[0045] Throughout this specification, a network slice (or its s-NSSAI) may be characterized as "allowed" or "rejected". Typically, this refers to a scenario in which the UE 110 indicates to the network that the UE 110 is configured to utilize a particular network slice and in response the network indicates that the particular network slice is accessible from the current camping cell (e.g., allowed) or is not accessible from the current camping cell (e.g., rejected). Thus, these terms may refer to feedback from the network as to whether a network slice is accessible from the current camping cell or a set of cells corresponding to a NAS registration area as described below.

[0046] The registration accept message may be configured to provide network slice information in addition to the allowed / rejected designation. In some embodiments, the registration accept message may be configured to also include a Boolean indicator (e.g., true / false) indicating whether each allowed s-NSSAI is supported in the entire registration area. If a specific allowed s-NSSAI is associated with a true value, UE 110 may assume that at least some cells in the current registration area support access to the corresponding network slice. If a specific allowed s-NSSAI is associated with a false value, UE 110 may assume that at least some cells in the current registration area do not support access to the corresponding network slice. A similar indicator may be used to indicate whether each rejected s-NSSAI is not allowed in the entire registration area. For example, if a specific rejected s-NSSAI is associated with a true value, UE 110 may assume that all cells in the current registration area do not support access to the corresponding network slice. If a specific rejected s-NSSAI is associated with a false value, UE 110 may assume that one or more cells in the current registration area support access to the corresponding network slice.

[0047] In other embodiments, the registration accept message may be configured to indicate the supported frequency range of each allowed s-NSSAI. For example, the indication may indicate to UE 110 that the allowed s-NSSAI is supported only by FR1, only by FR2, or by both FR1 and FR2. In another embodiment, the registration accept message may be configured to include a set of cell IDs and / or registration areas, which indicate which s-NSSAIs are allowed or denied for the corresponding cell ID or registration area.

[0048] As will be described below, UE 110 may determine to proactively move (e.g., after receiving a registration accept) to a cell that supports a particular s-NSSAI. For example, UE 110 may prioritize particular network slices. If UE 110 identifies from the NAS registration accept message that the currently camped cell does not support the prioritized network slice, UE 110 may attempt to camp on a different cell that supports the prioritized network slice. Similarly, when a new service flow mapped to an s-NSSAI that is not supported by the currently camped cell is initiated, UE 110 may locally proactively initiate a procedure to camp on a different cell operating within a frequency range that supports the s-NSSAI associated with the new service flow.

[0049] To provide an example of moving to a different cell based on a new traffic flow, consider the following exemplary scenario where UE 110 is located within the coverage area of ​​three different cells. In this example, the first cell supports network slice A, the second cell supports network slices A and B, and the third cell supports network slice B. First, UE 110 camps on the first cell and has an active data transmission of an application served by network slice A. Subsequently, a new application flow mapped to network slice B is initiated. Since the first cell does not support network slice B, UE 110 may be triggered to move to a different cell that supports network slice B. In this example, UE 110 may camp on the second cell because it supports both network slices A and B. Therefore, when camping on the second cell, both the data transmission of the application served by network slice A and the traffic flow of the application mapped to network slice B may be supported. Therefore, when UE 110 is selecting a cell to camp on, UE 110 may consider whether multiple network slices are supported.

[0050] Another exemplary source of network slice information may include radio resource control (RRC) signaling. During RRC connection establishment, UE 110 may include s-NSSAI information indicating which network slices UE 110 may attempt to access. In response, UE 110 may receive an indication of whether s-NSSAI is allowed or denied on the current camped cell.

[0051] In one embodiment, the network slice information may be included in the RRC reject message. For example, consider a scenario in which UE 110 is camped on gNB 120A. First, UE 110 sends an RRC Connection Request to gNB 120A. This may include NSSAI information indicating which network slice or slices UE 110 may utilize. If gNB 120A cannot support the network slice indicated by UE 110, gNB 120A may send an RRC reject message to UE 110. In the RRC reject message, the network may use a cause code to indicate that the requested s-NSSAI is not supported on gNB 120A.

[0052] In other embodiments, continuing with the example provided above, if gNB 120A does not support one or more network slices indicated by UE 110, gNB 120A may initiate an RRC connection release procedure. gNB 120A may also provide a set of 5G frequencies where the requested network slice is supported. Using the network slice information, UE 110 may then target a reselection procedure to a cell operating at the indicated frequency. Similarly, in another example, if UE 110 requests multiple network slices and any of the requested network slices are not supported on the currently camped cell, gNB 120A may initiate a connection release procedure. For each slice requested by UE 110, gNB 120A may indicate a set of 5G frequencies that support the network slice. Based on which network slice has the highest priority for UE 110, UE 110 may initiate a reselection procedure and target a cell operating at the frequency corresponding to the highest priority network slice.

[0053] Another exemplary network slice information source may include a message that explicitly requests supported network slices. For example, consider a scenario in which UE 110 is camped on gNB 120A. In one example, UE 110 may be configured to send an RRC request to gNB 120A for a set of s-NSSAIs supported on the currently camped cell. In response, gNB 120A may provide a list of supported s-NSSAIs. In another example, UE 110 may provide a list of s-NSSAIs and request gNB 120A to indicate whether gNB 120A supports one or more of the s-NSSAIs included in the list. In another example, a NAS layer message may be used. UE 110 may send a request to an access and mobility management function (AMF) for supported s-NSSAIs for each registration area. In response, the AMF may indicate which s-NSSAIs are allowed and / or denied for the registration area. In another example, UE 110 may provide a set of s-NSSAIs and request the AMF to indicate whether one or more of the indicated s-NSSAIs are supported for the registration area.

[0054] Another exemplary network slice information source may include a reason code. For example, when UE 110 initiates a packet data unit (PDU) session establishment procedure by indicating a specific s-NSSAI and the network does not support interworking with the s-NSSAI, a session management function (SMF) may send a reason code indicating that the current camped RAN does not support interworking with the requested s-NSSAI. The reason code may be included in the PDU session establishment reject message.

[0055] Another exemplary source of network slice information may include information collected by UE 110 during operation in the network. For example, during operation, UE 110 may identify the mapping between a 5G cell ID and its allowed s-NSSAI. Similarly, UE 110 may identify the mapping between a frequency range (or frequency band) and its allowed s-NSSAI. In some embodiments, as described above, the information collected by UE 110 may be stored locally at UE 110. In other embodiments, UE 110 may provide this information to a server hosted by a third party. Network slice information provided by UE 110 and other UEs may be collected to generate a crowdsourced database of cell IDs and / or frequencies and their corresponding network slices. When UE 110 registers with a PLMN and / or camps on a particular cell, UE 110 may refer to this database (locally stored or hosted by a third party) to make an informed decision about whether the service of a particular network slice can be started on the currently camped cell.

[0056] Another exemplary network slice information source may include a network slice management function (NSSF) running on the core network 130. For example, the NSSF may maintain an association between which cell IDs in a particular PLMN support access to a particular network slice. The AMF or 5G NR-RAN may consider the NSSF assistance information while providing feedback to the UE 110 about the supported NSSAI on the current call and / or tracking area.

[0057] In 410, UE 110 identifies a cell that supports a particular network slice. UE 110 may identify this cell using information collected from any of the exemplary sources described above or any other suitable source. As described above, in some embodiments, this cell may be identified while UE 110 is currently camped on a different cell. Thus, UE 110 may target the identified cell for a reselection procedure. In other embodiments, this cell may be identified during a cell selection procedure.

[0058] Although reference has been made to cell selection and cell reselection, the exemplary embodiments are not limited to these procedures. For example, UE 110 may attempt to cause the network to perform a handover by selectively providing measurement data corresponding to the identified cell. The exemplary embodiments may be applied to any instance in which UE 110 directly or indirectly selects a cell to camp on.

[0059] In 415, UE 110 collects measurement data corresponding to the identified cell. In 420, UE 110 determines whether the identified cell meets selection criteria. For example, UE 110 may compare the measurement data to a predetermined threshold value in accordance with cell selection or cell reselection. Thus, while UE 110 may consider whether a cell supports a particular network slice when selecting a cell to camp on, whether UE 110 actually camps on a cell may be determined by normal cell selection or reselection criteria.

[0060] If the identified cell does not meet the selection criteria, the method 400 may return to 410, where the UE 110 identifies another cell that supports the particular network slice. If the identified cell meets the selection criteria, the method 400 continues to 425. In 425, the UE 110 registers with the network via the identified cell. Subsequently, the UE 110 may access the particular network slice, and the method 400 ends.

[0061] Those skilled in the art will appreciate that the exemplary embodiments described above may be implemented with any suitable software configuration or hardware configuration or combination thereof. Exemplary hardware platforms for implementing the exemplary embodiments may include, for example, Intel x86-based platforms with compatible operating systems, Windows OS, Mac platforms and MAC OS, mobile devices with operating systems such as iOS, Android, etc. In other examples, the exemplary embodiments of the above methods may be embodied as a program including lines of code stored on a non-transitory computer-readable storage medium, which, when compiled, may be executed on a processor or microprocessor.

[0062] Although this patent application describes various combinations of various embodiments each having different features, those skilled in the art will understand that any feature of an embodiment may be combined with features of other embodiments in any manner not publicly denied or with features that are not functionally or logically inconsistent with the operation or function of the device of the embodiments disclosed in the present invention.

[0063] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0064] It will be apparent to those skilled in the art that various modifications may be made to the present disclosure without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure is intended to cover modifications and variations of the present disclosure, provided that these modifications and variations are within the scope of the appended claims and their equivalents.

Claims

1. A method for performing network slice-aware selection, comprising: At the User Equipment (UE): During non-access stratum (NAS) registration for a registration area, sending single network slice selection assistance information (s-NSSAI) information indicating a plurality of network slices that the UE is allowed to attempt to access; receiving information from the network in a NAS registration accept message indicating whether each of the plurality of network slices is allowed or denied for a set of cells in the registration area, wherein the NAS registration accept message further comprises a Boolean indicator for each of the plurality of network slices; determining, based on the NAS registration accept message, that a first network slice among the plurality of network slices is rejected and is not supported by at least one cell among the set of cells; wherein, when the first Boolean indicator for the first network slice is associated with a true value, the first network slice is not supported by the set of cells in the registration area; wherein, when the first Boolean indicator for the first network slice is associated with a false value, the first network slice is supported by at least one cell of the set of cells in the registration area; identifying that the UE is located within a coverage area of ​​a first cell in the group of cells; determining whether measurement data corresponding to the first cell meets a predetermined criterion; and When the measurement data meets the criterion, the first cell is camped on.

2. The method of claim 1, wherein the NAS registration accept message further includes an indication of whether the network slice is supported by other cells or tracking area identifiers in the registration area.

3. The method of claim 1 , wherein the NAS registration accept message further comprises an indication of one or more frequency ranges associated with the allowed network slice.

4. The method of claim 1, wherein the information is also received from a network function of a core network or a remote database hosted by a third party.

5. A user equipment (UE), comprising: a transceiver configured to communicate with a network; as well as A processor configured to perform operations comprising: During non-access stratum (NAS) registration for a registration area, sending single network slice selection assistance information (s-NSSAI) information indicating a plurality of network slices that the UE is allowed to attempt to access; receiving information from the network in a NAS registration accept message indicating whether each of the plurality of network slices is allowed or denied for a set of cells in the registration area, wherein the NAS registration accept message further comprises a Boolean indicator for each of the plurality of network slices; determining, based on the NAS registration accept message, that a first network slice among the plurality of network slices is rejected and is not supported by at least one cell among the set of cells; wherein, when the first Boolean indicator for the first network slice is associated with a true value, the first network slice is not supported by the set of cells in the registration area; wherein, when the first Boolean indicator for the first network slice is associated with a false value, the first network slice is supported by at least one cell of the set of cells in the registration area; identifying that the UE is located within a coverage area of ​​a first cell in the group of cells; determining whether measurement data corresponding to the first cell meets a predetermined criterion; and When the measurement data meets the criterion, the first cell is camped on.

6. The UE of claim 5, wherein the information is further received from a network function or a remote database hosted by a third party.

7. An integrated circuit comprising: Circuitry configured to send single network slice selection assistance information (s-NSSAI) information during non-access stratum (NAS) registration for a registration area, the s-NSSAI information indicating a plurality of network slices that the UE is allowed to attempt to access; circuitry configured to receive information from a network in a NAS Registration Accept message indicating whether each of the plurality of network slices is allowed or denied for a set of cells in the registration area, wherein the NAS Registration Accept message further comprises a Boolean indicator for each of the plurality of network slices; circuitry configured to determine, based on the NAS registration accept message, that a first network slice of the plurality of network slices is rejected and not supported by at least one cell of the set of cells; wherein, when the first Boolean indicator for the first network slice is associated with a true value, the first network slice is not supported by the set of cells in the registration area; wherein, when the first Boolean indicator for the first network slice is associated with a false value, the first network slice is supported by at least one cell of the set of cells in the registration area; circuitry configured to identify that a user equipment (UE) is located within a coverage area of ​​a first cell in the set of cells; circuitry configured to determine whether measurement data corresponding to the first cell satisfies a predetermined criterion; and When the measurement data meets the criterion, the circuit is configured to cause the UE to camp on the first cell.

8. The integrated circuit of claim 7, wherein the information is further received from a network function of a core network or a remote database hosted by a third party.

Citation Information

Patent Citations

  • Wireless network access method, device and system

    CN106851589A

  • Method and device for accessing target cell

    CN108366365A

  • Communication method, access network equipment, core network equipment and user equipment

    CN109561485A

  • Slice information updating method and device

    CN109951877A

  • Wireless communication method and system for network slicing

    CN110463335A